IPv6 ignorance is the canary. There's plenty of architecture ignorance below the surface. The real question is why aren't they failing annual security audits?

https://docs.github.com/en/enterprise-cloud@latest/organizat...

I’m surprised it’s even as high as three nines, at one point in 2025 it was below 90%; not even a single nine.[0] (which, to be fair includes co-pilot, which is the worst of availabilities).

People on lobsters a month ago were congratulating Github on achieving a single nine of uptime.[1]

I make jokes about putting all our eggs in one basket under the guise of “nobody got fired for buying x; but there are sure a lot of unemployed people”- but I think there’s an insidious conversation that always used to erupt:

“Hey, take it easy on them, it’s super hard to do ops at this scale”.

Which lands hard on my ears when the normal argument in favour of centralising everything is that “you can’t hope to run things as good as they do, since there’s economies of scale”.

These two things can’t be true simultaneously.. this is the evidence.

[0]: https://mrshu.github.io/github-statuses/

[1]: https://lobste.rs/s/00edzp/missing_github_status_page#c_3cxe...

https://mrshu.github.io/github-statuses/ Even ignoring Copilot, they seem to be barely at 2 nines of uptime for any service component.

the real problem isn't the reliability numbers, it's that GitHub sold itself as an integrated platform, every service you adopt raises the blast radius, teams that treat github like any other external dependency, with fallback runners and artifact mirrors, aren't sweating this

wait they still have 3 ninth, it really doesn't feel like that

but then their status center isn't really trust-able anymore and a lot of temporary issues I have been running into seem to be temporary, partial, localized failures which sometimes fall under temp. slow to a point of usability. Temporary served outdated (by >30min) main/head. etc.

so that won't even show up in this statistics

when GitHub moved to react instead of server rendered pages ie erb/turbolinks/pjax was the start to the end.

the pages got slower, rendering became a nightmare.

then they introduced GitHub actions (half baked) - again very unreliable

then they introduced Copilot - again not very reliable

it's easy to see why availability has gone down the drain.

are they still on the rails monolith ? they speak about it less these days ?

Why have five nines when you can have nine fives?

Embrace, extend, extinguish. Except the last one isn't quite going to plan...

“Microsoft Tentacle” - Now there’s a name for a new product line.

I have a little bit of sympathy for Github because if everyone is like me then they are getting 5-6x the demand they were last year just based on sheer commits alone, not to mention Github Copilot usage.