Fun read about Azure and having 173 agents running a node: https://isolveproblems.substack.com/p/how-microsoft-vaporize...
Probably just a coincidence that Github started to have issues after beginning their move to Azure at the end of last year.
Things can go wrong, but really, its been a lot and we're normalizing that to an unhealthy degree...
I wonder if it was down that much, if users would get credits the way we pay when we use the services - its kind of ridiculous for a critical service to be down that much and all we do is "ah okay, its just github". Like, as if that was normal to be down that much...
GitHub needs to completely bifurcate their enterprise/paid services from their free services at the infra level.
I should make a business selling git hosting. Apparently it's really easy because it doesn't have to actually work.
The historical uptime has been getting better but it is on a downwards trajectory in August:
>Update - primary failover briefly improved performance but did not fully mitigate, we've throttled inbound traffic and are investigating upstream Vitess issues
And now they're blaming their upstream vendor! Embarrassing stuff to be writing on a public page.
GitHub Actions upkeep is down to one 9. I miss the days big tech aimed for four or five 9s of reliability :(
> Update - We've identified an issue with a database primary and are failing over to a replica immediately
Seems like a weird thing to post on a status page. Shouldn't this have happened automatically and therefore precluded the need to inform users of it?
Honestly?
If the problem is scalability, just rate limit git commands on free accounts already. Nobody realistically need to push multiple times per minute, and that alone is bound to trickle down to anything that triggers on commits and pushes.
Unbelievable! Just this morning I was thinking to myself, hey Github's due for a downtime soon or they are finally getting their act together.
Can't wait for Anthropic's downtime tomorrow
I spent a bunch of time during the outage last week setting up forgejo and some custom action runners. At the time, I was worried I was wasting time and getting distracted from my real work...alas, I guess not. Gonna finish up that work and complete the move today.
at this rate this is a FEATURE!
So a normal Wednesday
Same time next week?
Ah so that's why I got a random "github-merge-queue Bot removed this pull request from the merge queue due to no response for status checks"
Oh thank god my pink unicorn site is back online, its had great uptime lately so thats nice.
Was wondering why all my Actions just stopped running
I have switched off from github to my own server besides two websites that depend on gitbub integration to deploy to clpudfare pages
The joke was a good one the first, second, or third time. It's not even funny anymore...
Scaling is a dream or theory we think we solved. Distance between ... to practice. So ... should be reconsidered again.
must feel bad that at this point every dev checks github status before going to work like it was the weather app.
Notice odd behavior on GitHub. Get gaslit by a green status page. Notice more odd behavior on GitHub. Think it must be me this time. See unusual action queuing. Ah, an incident on the status page. Go for a walk and check HN on my phone. The AI SDLC.
> We've identified an issue with a database primary and are failing over to a replica immediately
This is why it's hard to take GitHub seriously. How can a single database cause an outage for everyone? This is amateur stuff. Have they no sharding or partitioning internally? Paying customers should not be impacted in the same way as free ones are.
Must be Wednesday
How can you do so badly with Git when its architecture is basically so friendly to partitioning and horizontal scaling?
This is unacceptable for paying customers.
Either 1) infrastructure for paying and non paying customers must be separated, 2) excessive load must be ended by not offering the free tier anymore or 3) they must fix their broken monolith but they are seemingly incapable of doing so.
Cursor had better not miss this opportunity.
So what’s stopping you (or your org) from leaving GitHub?
Must be a weekday
Can't even run self hosted github actions lol
I have been very happy with github for _years_. Lately, not so much. Now I want to try a self-hosting alternative again. I tried gitlab years ago (pre-pandemic, IIRC), and it wasn't for me (they had _serious_ security issues as well, which of course didn't affect my self-hosting thing, but still...).
So - where do we stand in August 2026?
*EDIT:* No, I don't want anything related to Felon Musk.
Another outage, this time with GitHub Actions. Last time that happened was 5 days ago [0] and another outage happened on the postmortem announcement as well. [1]
While GitHub is imploding itself, maybe you should think about self-hosting.
[dead]
I noticed earlier this week that my URL bar now pre-fills githubstatus.com instead of github.com when I type "gith"