lukevmorris

I wrote a blog [1] last week about what we've been doing at Depot to work around GitHub's instability. I wrestled with how to present their downtime in a way that communicates its real impact to users, and I landed on a similar approach as the author. But I think even this doesn't state it strongly enough. Their uptime stat comes from their public status page, so it's conservative by definition. And it's important to remember that their downtime comes almost exclusively during business hours, when people are relying on the platform to get work done.

There are projects like The Missing GitHub Status Page [2] that attempt a more accurate reporting, but taking 98.31% for granted, I think the more impactful framing would be _a floor_ of 1.5 business days lost every month. At 22 business days per month, that can feel more like 7+% downtime.

[1] https://depot.dev/blog/github-actions-without-github

[2] https://mrshu.github.io/github-statuses/

Hello, one of the Era devs here! As mentioned in the article, we launched our EraSearch Cloud private beta today. If you're interested, you can signup for our waitlist here: https://cloud.era.co/waitlist