This is from a third-party tracker, who took the downtime of every GitHub hosted service and added them together. So a bunch of stuff that was down 0.5% of time and/or some beta+new release services down for longer make it look way worse than the core service uptime actually is.

[–] InnerScientist@lemmy.world 26 points 5 days ago (2 children)

For even more context: That means that 89% of the time all parts that make up github work without issue. 11% of the time at least one component has issues/downtime.

https://mrshu.github.io/github-statuses/ shows the breakdown, git push/pull operations for example have 98.98% uptime.

[–] Fmstrat@lemmy.world 14 points 5 days ago (1 children)

Good info. Either way, switch to Codeberg. 😉

[–] InnerScientist@lemmy.world 9 points 5 days ago (1 children)

Switched to self-hosted Forgejo already so now I'm just waiting for my dependencies to switch.

10 minutes ago my forgejo test failed because github returned a 502 for the home-manager repo •-•

[–] Fmstrat@lemmy.world 4 points 5 days ago

Yea, I run Gitea for my personal work and we run our for our business, mainly because I started before the Forgejo fork. At some point I'll migrate over.

[–] stardreamer@lemmy.blahaj.zone 4 points 4 days ago (1 children)

Of all things, how does core functionality NOT have 4 nines???

[–] InnerScientist@lemmy.world 1 points 4 days ago

Look on the bright side, it's only 3,5 days of downtime a year.

https://uptime.is/98.98