mrshu

> They're at 93.91% uptime over the past 90 days, according to https://mrshu.github.io/github-statuses/ , and that doesn't even include today's outage yet. I don’t love GitHub, but that number is a little misleading… That’s the intersection uptime of all GitHub services, most of which I (and most users) do not care about; code spaces, copilot, packages etc… When you take out those uptimes, it becomes a lot higher. I’ll admit there seems to be a lot more incidents than usual though…

https://mrshu.github.io/github-statuses/ says they are down to 88.15% uptime. Even when you consider uptime of individual components, their best is 99.78%, so two nines.

Business will start accepting bad uptime to be the norm. Following the lead of Github: https://mrshu.github.io/github-statuses/

Define incredible. https://mrshu.github.io/github-statuses/ Overall uptime is 90% (single nine), and the best individual service at 99.8% (two nines). The core git functionality itself is at 98.98%, which works out to being down roughly a full business day each month.

You can. GitHub is about to hit zero nines of uptime[0]. But feedback like that is far too late to be useful. Maybe (principal or senior) engineers should be the ones to judge, and be trusted by management that their foresight is worth pushing the deadline? [0]: https://mrshu.github.io/github-statuses/

Nice! I still remember the old GitHub status page which showed and reported on their uptime. No surprises they took it offline and replaced it with the current one when it started reporting the truth. EDIT: You mention this with archive.org links! Love it! https://mrshu.github.io/github-statuses/#about

It really has been remarkable watching GitHub just crumble as an organization. There's a lot of discussion about why: the switch from being independent to being part of Microsoft, having resources pushed to Copilot instead of core service, the organization structure itself, a reliance on vibe coding, etc etc. Regardless of the reason, it's undeniable that GitHub is facing some serious issues. The unofficial status page[1] tells a horrifying story. I would absolutely love to get some insider perspective on this (if only to learn how to prevent it from happening anywhere I work), but I think it's clear to anyone who has been paying any attention that GitHub is a sinking ship and the only reason people haven't abandoned it already is inertia. Considering how much else is changing in software right now I don't think inertia is enough to sustain a company. 1. https://mrshu.github.io/github-statuses/

Opinion based on stated facts. Please share the information you have which contradicts the conclusions I have drawn from Github's statement. (And we know they're liars. They report very few of the actual incidents they have; see for example https://mrshu.github.io/github-statuses/)

https://mrshu.github.io/github-statuses/ They're struggling to maintain a single nine these days.

The Missing GitHub Status Page https://mrshu.github.io/github-statuses/ Would you know it, they're actually UP to the ... One-nines. 93.40%

Yeah who knows, would be interesting to hear an inside take if any readers here are also GH devs! They're at 93.91% uptime over the past 90 days, according to https://mrshu.github.io/github-statuses/ , and that doesn't even include today's outage yet. A glorious one nine of reliability.

Not even hitting 1 nine at the moment - https://mrshu.github.io/github-statuses/

Am I hallucinating or did they do a "cleanup" of the GH status in their status page? https://www.githubstatus.com/ 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.

https://mrshu.github.io/github-statuses/ https://blog.incidenthub.cloud/github-reliability-outage-history-2025-… https://damrnelson.github.io/github-historical-uptime/ And here's GH admitting to it: https://github.blog/news-insights/company-news/an-update-on-github-ava…

Fair, with all the traffic they are dealing with due to agent code gen, perhaps it's not surprising. It's interesting to see the gap between the numbers on that website (https://mrshu.github.io/github-statuses/) and the official one.

Someone linked this third-party "honest" status page: https://mrshu.github.io/github-statuses/ Seems more accurate with my experience of GitHub.

The Missing GitHub Status Page (https://mrshu.github.io/github-statuses/) gives a better overview of their frequent outages.

The subjective experience I and others report is that GitHub feels to have gotten significantly worse over the last few months. If you look at the month over month view of "Uptime history" in the cited link[1], it confirms this: it's been sub-90 (even sub-80 last month) essentially since the start of this year (i.e. when GitHub says that commit activity 10xed). Go back even a year and it's all in the high 9s. I honestly can't explain the discrepancy between the graph in the article and the month over month stats on the same page, but the latter tracks both to my own subjective experience of GitHub and their own internal metrics. [1]: https://mrshu.github.io/github-statuses/

Contrast between official [0] and third party status pages [1] is huge. How their terms of service for SLA are legal if they are so different from real world usage of their product? I really like GitHub and their services but every time when it’s broken and their status page is green something screams inside me. [0] https://www.githubstatus.com/ [1] https://mrshu.github.io/github-statuses/

Please tell me this makes sense This website has no overused ai-generated animations and... I quite enjoy it. The original website[1] has a fade-in animation, big round cards, shadows, all the jazz you can think of, it's there. This site is very readable, very honest and sober. I don't need to sift through buzzwords to figure out tiny details. Thank you, OP! 1: https://mrshu.github.io/github-statuses/

The missing status page [1] treats it as downtime any time any component of the system is down, and calculates the overall uptime based on the time that doesn't overlap with any individual category outages, and the overall downtime as any time overlapping with at least one individual category outage to avoid double-counting They show 24h of minor outage on that date. I'm guessing that this site is taking the downtime in a given day across all services and adding it up, which would mean the worst possible day has 10 days of downtime (a day of downtime for each major category). 1: https://mrshu.github.io/github-statuses/

Github has 84.92% uptime in the last 90 days according to https://mrshu.github.io/github-statuses I don't know how this is even remotely close to acceptable.

Mainly this https://mrshu.github.io/github-statuses/ But also product decisions that don't seem to be aligned with the preferences of users... see https://mitchellh.com/writing/ghostty-leaving-github

Their stability and reliability has deteriorated significantly. So much so that they stopped posting uptime metrics for a while on their status page and an independent 3rd party created a website just for this: https://mrshu.github.io/github-statuses/ (not my website) According to that website, which unsurprisingly reports a lower number than what Github themselves claim, Github uptime is down to ~86%. And if you work in the space, you know how terrible that is, but even more so for such a critical piece of infrastructure.

It's the devops team can manage a measly 87% uptime [1] you're talking about, you can do a lot better on your homeserver. [1]: https://mrshu.github.io/github-statuses/

Github has frequent downtime: https://mrshu.github.io/github-statuses/

Yes. https://mrshu.github.io/github-statuses/ 94 incidents in 90 days.

Availability is priority? Does not seem like it is https://mrshu.github.io/github-statuses/

Their uptime for just Git operations has been hit pretty hard in the past 90 days: https://mrshu.github.io/github-statuses/

https://mrshu.github.io/github-statuses/ suggests that their combined uptime doesn't even meet 1 nine, let alone 2.