Am I hallucinating or did they do a "cleanup" of the GH status in their status page? <a href="https://www.githubstatus.com/" rel="nofollow">https://www.githubstatus.com/</a><p>API Requests with 4 nines of availability??<p>Issues with 99.96 uptime?<p>PR with 99.61% uptime last 90 days??<p><a href="https://mrshu.github.io/github-statuses/" rel="nofollow">https://mrshu.github.io/github-statuses/</a> marks PRs at 95.89% in the same period as an example.
<a href="https://www.githubstatus.com/incidents/x69zbgdyfzg0" rel="nofollow">https://www.githubstatus.com/incidents/x69zbgdyfzg0</a> took three days to resolve and isn't being counted as an outage on the official page.
Seems like if they changed the criteria of downtime. If you hover over the individual days you’ll see lot of degraded messages, but still green.
I had checked that page not long ago, and as far as I remember there were many "red" or "orange" days in the past 3 months. Now it's all green. That's concerning
They have an incident reported today, but the status page for actions shows green :D that's fun.
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.
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.
Soon we'll have to track when Github is up.
The Google SRE book offers the following as one of the reasons to not gun for 100% reliability (emphasis added):<p>> users typically don’t notice the difference between high reliability and extreme reliability in a service, <i>because the user experience is dominated by less reliable components like the cellular network or the device they are working with</i>. Put simply, a user on a 99% reliable smartphone cannot tell the difference between 99.99% and 99.999% service reliability!<p>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.<p>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.<p>It's just insane I can't decide which between Github or German o2 should be the more reliable service!
"unauthorized" is a bit different than "unauthenticated". The former suggests trying to access something you don't have permission for while the latter suggests you're just not logged in.<p>At a guess, I could imagine some sort of failure of cached pages, which can be cached for signed out users but probably not for signed in users (as the rendered HTML would need to have user context like their avatar etc)
Github isn't having a debate over how many 9s they have, they're having a zero 9s problem.<p>I think there's 3 big themes with this, thought not<p>1. LLM tools have added considerable load.<p>2. LLM used by developers to increase velocity seem to be leading more outages. This calls into question the increased velocity.<p>3. Roadmaps focused on pushing features that aren't reliability problems. i.e. github moving to azure, or adding AI features.<p>All these same problems happen to orgs with other fads that aren't AI. Following fads is not good engineering.
Apparently Github is experiencing a huge increase in usage due to LLMs and this is the cause for a lot of their instability as of late.
> Put simply, a user on a 99% reliable smartphone cannot tell the difference between 99.99% and 99.999% service reliability!<p>Sure they can. If Google loads and Github doesn't, then it's clearly Github being down, not the mobile network.<p>Also not everyone uses a phone. My desktop & fibre internet has way better than 99% reliability.
First time that GitHub has ever been down for me (London, UK):<p><pre><code> 504 Gateway Time-out
The server didn't respond in time.</code></pre>
I just got the same in Western EU, refreshed and got a site, and now it's gone again with intermittent hiccups of life.<p>Honestly it's pretty mad to see, especially without a crisp failover.
And it came back for me, at least for a refresh or two...
> 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.
We should have a pinned post, just for GitHub outages.
Waiting for someone to say this was always the case, not just post Microsoft's takeover.
GitHub is down for like the nth time this week? Time for some truly ground breaking statements like this is the result of LLM (yes it is I know)
What's going on with GitHub lately? I've never seen them having so much issues over the years as they do have now.
Slophub is vibing strong
Welcome back everyone
Now self-hosting, left the dumpster fire.
shit i thought it was because my browser. sorry firefox..<p>why i am keep seeing github down news in HN?
Simply because of being a dependency of many things.<p><a href="https://www.githubstatus.com/history" rel="nofollow">https://www.githubstatus.com/history</a><p><a href="https://isgithubcooked.com/" rel="nofollow">https://isgithubcooked.com/</a>
Because majority of the audience spend large parts of their day on GitHub and it keeps going down.
Once again, GitHub is down. Last time an incident happened was 2 days ago [0].<p>Could not have happened on a worse day (Monday) and you can see how unreliable GitHub has been.<p>Better of self-hosting.<p>[0] <a href="https://news.ycombinator.com/item?id=48418183">https://news.ycombinator.com/item?id=48418183</a>
In my employment from the last 3 years, I saw twice that there were two migrations from internal systems to GitHub. I would think that companies are doing this for cost-cutting measures. It's not like something I am going to research but it'd be interesting that their recent issues are related to large migrations from in-house installations to github and doubly, if that is related to how large companies might be tightening up their spending in the past few years.
Monday is probably the best day for an outage? Everyone's in the office, so you're not disturbing them, and hung over, so you're not hurting their productivity much.
Anything I'd self-host would be down way more often than github.
Ah, here we go again. A weekly (daily?) <i>github is down</i> thread