Disruption with Some GitHub Services – Resolved

blimmer 258 points 156 comments August 26, 2026
www.githubstatus.com · View on Hacker News

Discussion Highlights (20 comments)

CerebralCoding

Must be a day ending in Y

acedTrex

Oh thank god my pink unicorn site is back online, its had great uptime lately so thats nice.

ad_fontes

> 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?

zackify

Can't even run self hosted github actions lol

time0ut

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.

nr378

GitHub needs to completely bifurcate their enterprise/paid services from their free services at the infra level.

frenchie4111

I noticed earlier this week that my URL bar now pre-fills githubstatus.com instead of github.com when I type "gith"

xray42

So a normal Wednesday

everfrustrated

> 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.

qkwrv

We can't keep living like this.

xbryanx

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.

inigyou

I should make a business selling git hosting. Apparently it's really easy because it doesn't have to actually work.

everfrustrated

>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.

tomw1808

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...

igleria

must feel bad that at this point every dev checks github status before going to work like it was the weather app.

iso1631

Must be a weekday

kelvinjps10

I have switched off from github to my own server besides two websites that depend on gitbub integration to deploy to clpudfare pages

shepardrtc

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.

Elfener

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"

stalfosknight

So what’s stopping you (or your org) from leaving GitHub?

Semantic search powered by Rivestack pgvector
4,560 stories · 41,176 chunks indexed