[stefankuehnel]

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.

[12_throw_away]

14 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-a...

[chrisandchris]

An 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.

[jeffrallen]

At this point they are probably going to crash their status system. "No one ever expected more than 50 incidents in a month!"

[munk-a]

You know what I think would reverse the trend? More vibe coding!

[slyzmud]

I 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.

[alansaber]

All the cool kids move fast and break things. Why not the same for core infrastructure providers? Let's replace our engineers with markdown files named after them.

[brookst]

This kind of thing never happened before LLMs!

[akulbe]

No, the reason it's happening is because they must be vibe coding! :P

[re-thc]

That's not good enough. You need SKILLS!

[elondemirock]

I'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]

I was sort of hoping this would be a year-to-date visualization similar to Github profile contribution graphs...

[melodyogonna]

I think this will continue to happen until they finish migrating to Azure

[ygouzerh]

The main root cause of the incident on their actions was actually due to Azure: https://www.githubstatus.com/incidents/xwn6hjps36ty points to https://azure.status.microsoft/en-us/status/history/?trackin...

[re-thc]

Haven't they been shown the front door?

[hnthrowaway0315]

Someone should make a timeline chart from that, lol.

[jakub_g]

https://updog.ai/status/github

[mrshu]

Here it is. It looks like they are down to a single 9 at this point across all services:

https://mrshu.github.io/github-statuses/

[bckmn]

Prompting

> Let's make a timeline chart of 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.githubuserconten...)

219 total incidents across 12 full months, averaging 18.3/month. January 2026 was the worst month, and August 2025 was the calmest.

[stefankuehnel]

Haha, that would be awesome!

[gowld]

Light work for an LLM