Attached: 2 images
IT'S HAPPENING
GITHUB, THE FIRST ENTERPRISE CLOUD SOLUTION TO REACH ZERO NINES RELIABILITY
https://mrshu.github.io/github-statuses/
#github
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.
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.
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.
For context, this isn’t 100% true.
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.
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.
Of all things, how does core functionality NOT have 4 nines???
Look on the bright side, it’s only 3,5 days of downtime a year.
https://uptime.is/98.98
Good info. Either way, switch to Codeberg. 😉
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 •-•
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.