This has gotten to a point where it doesn't really matter anymore. When a service crosses a certain reliability threshold it's like a phase change. The customer base eventually adapts to the situation. Anyone who still genuinely cares has moved to self hosted enterprise or something else by now. It was most tenuous for me when they almost met the SLA. Now that they've blown so far beyond it, the stress is mostly gone.
> Following investigation, we are seeing that impact is limited to unauthenticated users when accessing Pull Requests or Issues. Our team continues to work towards mitigation with more updates to follow as we have them.
The Google SRE book offers the following as one of the reasons to not gun for 100% reliability (emphasis added):
> users typically don’t notice the difference between high reliability and extreme reliability in a service, because the user experience is dominated by less reliable components like the cellular network or the device they are working with. Put simply, a user on a 99% reliable smartphone cannot tell the difference between 99.99% and 99.999% service reliability!
I've been on a shaky relationship with my ISP of late. What brought me to this thread today is that I couldn't push to Github. Notably this isn't covered by their downtime report so, going by the available facts, it's _probably_ not Github's fault I couldn't push; and I've just been on my daily stand-up call and I got disconnected so frequently.
But looking beyond today's available facts, odds are there's a bigger problem GH is not mentioning in their status page. They say the current incident has to do with "unauthorized users" and I wonder if pushing a commit from my IDE client counts as an operation from an "unauthorized user" as I still have to authorize with my SSH key.
It's just insane I can't decide which between Github or German o2 should be the more reliable service!
People seem to miss entirely that this is not (only) some slop code that makes github go down, but its the fact that they get 100x the number of requests since AI tools came to the devs daily workflow.
17 comments
[ 4.0 ms ] story [ 36.7 ms ] threadwhy i am keep seeing github down news in HN?
Could not have happened on a worse day (Monday) and you can see how unreliable GitHub has been.
Better of self-hosting.
[0] https://news.ycombinator.com/item?id=48418183
API Requests with 4 nines of availability??
Issues with 99.96 uptime?
PR with 99.61% uptime last 90 days??
https://mrshu.github.io/github-statuses/ marks PRs at 95.89% in the same period as an example.
> users typically don’t notice the difference between high reliability and extreme reliability in a service, because the user experience is dominated by less reliable components like the cellular network or the device they are working with. Put simply, a user on a 99% reliable smartphone cannot tell the difference between 99.99% and 99.999% service reliability!
I've been on a shaky relationship with my ISP of late. What brought me to this thread today is that I couldn't push to Github. Notably this isn't covered by their downtime report so, going by the available facts, it's _probably_ not Github's fault I couldn't push; and I've just been on my daily stand-up call and I got disconnected so frequently.
But looking beyond today's available facts, odds are there's a bigger problem GH is not mentioning in their status page. They say the current incident has to do with "unauthorized users" and I wonder if pushing a commit from my IDE client counts as an operation from an "unauthorized user" as I still have to authorize with my SSH key.
It's just insane I can't decide which between Github or German o2 should be the more reliable service!