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.

Not bad

At the risk of going recursive, how do you define not bad?

Could be worse?

Yes, and honestly, for it's usage, similar feelings for AWS, not bad. Although, I guess I could ask, are you looking for a rubrick that I follow? Not trying to be inflammatory, just trying to understand what exactly you're looking for.

I am mostly going off of overall usage vs downtime.

How often can a service be down and still be considered to have incredible uptime.

Personally, I would define incredible uptime as roughly 5 minutes down per month, or around 99.99% uptime.

GitHub is currently sitting at about 70 hours of downtime per month, on average across all services.

It's not though... it's sitting a hair above 90%

My comment is that I expect it to be more frequent and less given the scale and usage. Quite honestly, we have the most insane expectations about uptime and availability in my opinion. I'm glad that we can meet them. But still, insane.

If something is unfixably broken 1 out of 10 times I use it I will just consider it broken. 1 out of 100 is unreliable but usable.

That goes for most things physical and digital.