GitHub Outage Tracker: Is GitHub Cooked?

Post by vrosas » Thu, Aug 27, 2026, 12:54 AM UTC

rpearl wrote: post #87

kashnote wrote: post #12

I think we need to have a little more sympathy for GitHub. You could justify the jabs when we could all blame any outage on the migration to Azure, but then they shared numbers around the scale they're dealing with now that everyone is constantly building and pushing with AI. I think it's commendable that they're not limiting access to the site or (intentionally) throttling newcomers. Yes, they need to get this figur…

If you do the math, their numbers are something like 1000 commits per second. That's not pushes per second either, it's just the total number of commits summed up over a week, not all of which trigger much of anything to happen. Yes, that is scale. And yes, that's not actual requests per second. But it's the sort of scale that big (and even mid-sized) tech has known how to deal with for decades. Microsoft doesn't hav…

Post by iamflimflam1 » Thu, Aug 27, 2026, 1:01 AM UTC

Waterluvian wrote: post #84

joshuahedlund wrote: post #57

Given that the outages are caused by record traffic, so far they are only cooked in the Yogi Berra sense of “Nobody goes there anymore, it’s too crowded”

Gets me wondering… if I get used to the fact that some location is busy, I stop going there. Other people might do the same. Could this create a detectable wavy signal over time? People stop going because it’s busy. It stops being busy. People go because it’s not busy. Repeat. Is this a known phenomenon?

Post by Bratmon » Thu, Aug 27, 2026, 1:03 AM UTC

xyzzy_plugh wrote: post #66

Is GitHub Cooked? Decidedly yes. Migrating to something else has been raised as a concern during every engagement with clients and prospective clients in the past year. "Do you use GitHub?" "Yes though we'd like to move to something else, we just don't know what yet." As soon as the next big thing shows up, they're done. And they know it.

Post by jeremyjh » Thu, Aug 27, 2026, 1:27 AM UTC

gogobio wrote: post #23

kashnote wrote: post #12

I think we need to have a little more sympathy for GitHub. You could justify the jabs when we could all blame any outage on the migration to Azure, but then they shared numbers around the scale they're dealing with now that everyone is constantly building and pushing with AI. I think it's commendable that they're not limiting access to the site or (intentionally) throttling newcomers. Yes, they need to get this figur…

Sympathy? It's a Microsoft company that is being ran with a consistency of a startup in early seed rounds. Their downtime is abhorrent and unacceptable as far as enterprise goes. Their engineers look like absolute amateurs allowing for such low class work it results in their customers experiencing industry leading downtime.

Post by jeremyjh » Thu, Aug 27, 2026, 1:29 AM UTC

Bratmon wrote: post #96

xyzzy_plugh wrote: post #66

Is GitHub Cooked? Decidedly yes. Migrating to something else has been raised as a concern during every engagement with clients and prospective clients in the past year. "Do you use GitHub?" "Yes though we'd like to move to something else, we just don't know what yet." As soon as the next big thing shows up, they're done. And they know it.

I wonder if this is a Microsoft Excel situation where everyone 1. Hates the status quo 2. Only uses a handful of the 10,000 features the status quo has 3. Uses a different handful than everyone else Because that model kept Excel as the center of buisnesses around the world for 30 years and counting