[Anon1096]

> It looks like they are down to a single 9 at this point across all services

That's not at all how you measure uptime. The per area measures are cool but the top bar measuring across all services is silly.

I'm unsure what they are targeting, seems across the board it's mostly 99.5+ with the exception of Copilot. Just doing math, 3 (independent, which I'm aware they aren't fully) 99.5 services brings you down to an overall "single 9" 98.5 healthy status but it's not meaningful to anyone.

[munk-a]

It depends whether the outages are overlapped or not. If the outages are not overlapped then that is indeed how you do it since some of your services being unavailable means your service is not fully available.

[lxgr]

There's limits to that type of logic. Otherwise, as long as a single elevator or water fountain in any Google satellite office were out of order, would you consider Google "not fully available"?

[reed1234]

They are overlapped. You can hover over the bars and some bars have multiple issues.

[mynameisvlad]

I mean, there's a big difference between primary Git operations being down and Copilot being down. Any SLAs are probably per-service, not as a whole, and I highly doubt that someone just using a subset of services cares that one of the other services is down.

Copilot seems to be the worst offender, and 99% of people using Github likely couldn't care less.