In their defense, they dramatically "over"-report sev-2/3's (things like, avatar urls are not loading in saudi arabia), which makes their cumulative uptime look much worse than it is.

If you filter for major/critical outages, their uptime of core services in trailing 12 months all have two 9's.

https://isgithubcooked.com/?severities=major.critical

Also, a huge part of their cumulatively-bad availability story is copilot, which is a functionality (LLM inference) that most organizations have struggled to get two 9's of availability in for the last 9 months.

As someone who relies on it for all of my workflows at a normal job, core functionality issues result in me not being able to get work done on at least a weekly basis reliably at this point, and it's been that way for months.

The things aren't profile pictures not loading in saudi, they're botching merge jobs, git/api operations being down, pull requests not loading, etc. And that's on top of the plethora of UI bugs that have been pervasive for years that aren't blocking functionality.

Two 9’s? You have to work pretty hard to do that badly. That’s like bragging you graduated with a C average from Harvard after your father endowed a chair to get you in.

Given GitHub has become a utility service globally this should be frankly worrisome to everyone let alone the developer community actively using it. It’s intertwined into many things now beyond simply source code hosting and PRs. And I am surprised GitHub leadership is ok with the state of things. Having worked at a lot of 5-6 9’s shops, this would have been all hands on deck, all roadmaps paused, figure it out or perish sorts of stuff.