23 ms·
You can literally watch GitHub explode bit by bit. Take a look at the GitHub Status History; it's hilarious: https://www.githubstatus.com/history https://www.gi
by stefankuehnel 7mo ago
You can literally watch GitHub explode bit by bit. Take a look at the GitHub Status History; it's hilarious: https://www.githubstatus.com/history https://www.githubstatus.com/history.
- hnthrowaway0315 7mo agoSomeone should make a timeline chart from that, lol.
- stefankuehnel 7mo agoHaha, that would be awesome!
- gowld 7mo agoLight work for an LLM
- nozzlegear 7mo agoBut not Copilot.
- peartickle 7mo agoCopilot is shown as having policy issues in the latest reports. Oh my, the irony. Satya is like "look ma, our stock is dropping...", Gee I wonder why Mr!!
- jakub_g 7mo agohttps://updog.ai/status/github https://updog.ai/status/github
- mrshu 7mo agoHere it is. It looks like they are down to a single 9 at this point across all services: https://mrshu.github.io/github-statuses/ https://mrshu.github.io/github-statuses/
- dreadnip 7mo agoCan you add a line graph with incidents per month? Would be useful to see if the number of incidents are going up or down over time.
- matt_kantor 7mo agoI threw together <https://mkantor.github.io/github-incident-timeline/ https://mkantor.github.io/github-incident-timeline/>. It's by day rather than month, and only shows the last 50 incidents since that's all their API returns.
- bckmn 7mo agoPrompting > Let's make a timeline chart of https://www.githubstatus.com/history https://www.githubstatus.com/history for the past 1yr and upload it as a gist yields [GitHub Status Incident Timeline — Feb 2025 to Feb 2026](https://htmlpreview.github.io/?https://gist.githubusercontent.com/joshbeckman/adda6f3e573e005b433e598471de192d/raw/d3bd5d4a89c44cb05e2f9f2ba1bd5f0422fd880a/github-status-timeline.html https://htmlpreview.github.io/?https://gist.githubuserconten...) 219 total incidents across 12 full months, averaging 18.3/month. January 2026 was the worst month, and August 2025 was the calmest.
- munk-a 7mo agoYou know what I think would reverse the trend? More vibe coding!
- akulbe 7mo agoNo, the reason it's happening is because they must be vibe coding! :P
- akulbe 7mo ago[flagged]
- badgersnake 7mo agoNo because you missed the joke.
- slyzmud 7mo agoI know you are joking but I'm sure that there is at least one director or VP inside GitHub pushing a new salvation project that must use AI to solve all the problems, when actually the most likely reason is engineers are drawing in tech debt.
- OtomotO 7mo agoBetter to replace management by AI. Computers can produce spreadsheets even better and they can warm the air around you even faster.
- chrisjj 7mo agoPlus they don't take stock options!
- mrweasel 7mo agoHonestly AI management would probably be better. "You're a competent manager, you're not allowed to break or circumvent workers right laws, you must comply with our CSR and HR policies, provide realistic estimates and deliver stable and reliable products to our customers." Then just watch half the tech sector break down, due to a lack of resources, or watch as profit is just cut in half.
- melodyogonna 7mo agoI think this will continue to happen until they finish migrating to Azure
- re-thc 7mo agoHaven't they been shown the front door?
- ghostly_s 7mo agowut
- bob1029 7mo agohttps://learn.microsoft.com/en-us/azure/frontdoor/front-door-overview https://learn.microsoft.com/en-us/azure/frontdoor/front-door...
- ludwigvan 7mo agoProbably referring to the fact that they no longer are independent, do not have a CEO and are a division of a division within Microsoft.
- ygouzerh 7mo agoThe main root cause of the incident on their actions was actually due to Azure: https://www.githubstatus.com/incidents/xwn6hjps36ty https://www.githubstatus.com/incidents/xwn6hjps36ty points to https://azure.status.microsoft/en-us/status/history/?trackingId=FNJ8-VQZ https://azure.status.microsoft/en-us/status/history/?trackin...
- 12_throw_away 7mo ago14 incidents in February! It's February 9th! Glad to see the latest great savior phase of the AI industrial complex [1] is going just as well as all the others! [1] https://www.theverge.com/tech/865689/microsoft-claude-code-anthropic-partnership-notepad https://www.theverge.com/tech/865689/microsoft-claude-code-a...
- jeffrallen 7mo agoAt this point they are probably going to crash their status system. "No one ever expected more than 50 incidents in a month!"
- chrisandchris 7mo agoAn interesting thing I notice now is that people do not like companies that only post about outages if half the world have them ... and also not companies that also post about "minor issues", e.g.: > During this time, workflows experienced an average delay of 49 seconds, and 4.7% of workflow runs failed to start within 5 minutes. That's for sure not perfect, but there was also a 95% chance that if you have re-run the job, it will run and not fail to start. Another one is about notificatiosn being late. I'm sure all others do have similar issues people notice, but nobody writes about them. So a simple "to many incidents" does bot make the stats bad - only an unstable service the service.
- BrouteMinou 7mo agoDude, that's just a reason to scream at the clouds... Literally...
- elondemirock 7mo agoI'm happy that they're being transparent about it. There's no good way to take downtime, but at least they don't try to cover it up. We can adjust and they'll make it better. I'm sure a retro is on its way it's been quite the bumpy month.
- krrishd 7mo agoI was sort of hoping this would be a year-to-date visualization similar to Github profile contribution graphs...