No it isn't, it's working absolutely fine and has been all afternoon.
githubstatus.com disagrees. Heres the specific incident: https://www.githubstatus.com/incidents/gqx5l06jjxhp I think I'll believe them when they say it's down, no offense.
Uhm, okay.
Rather than looking at a rather noddy status page, have you tried using it?
githubstatus.com disagrees. Heres the specific incident: https://www.githubstatus.com/incidents/gqx5l06jjxhp I think I'll believe them when they say it's down, no offense.
Uhm, okay. Rather than looking at a rather noddy status page, have you tried using it?
https://codeberg.org open source GitHub without Microsoft (it's a German non-profit). You can also host your own lightweight https://forgejo.org instance In case anyone questions whether centralizing literally everything onto GitHub is a good idea, at least as a mirror for things you depend on
Everytime github goes down, and my push/pull is rejected, I immediately assume they’ve discovered I’m incompetent and fired me. And I’m the head of engineering at my company.
Sounds kind of like those dreams where you can only run slowly, punch with noodly arms and trying to turn on a light just has a dim effect.
Pretty much every company has been shown to have fake status pages at this point.
Really? Why? That's so disappointing.
Two technical reasons capstoned by driving business motivation:
-False positives
-Short outages that last a minute or three
Ultimately, SLA's and uptime guarantees. That way, a business can't automatically tally every minute of publicly admitted downtime against the 99.99999% uptime guarantee, and the onus to prove a breach of contract is on the customer
Status pages are updated by humans and the humans need to (1) realize there's a problem and (2) understand the magnitude of the problem and (3) put that on the status page. It's not fake, it's just a human process. And automating this would be error prone just the same.
Very good points. Meanwhile I have clients asking me why they can't have a status page to which I reply: you can, but ultimately to be completely fail proof it will be a human updating it slowly. To which they reply: but GitHub or X does it... Very infuriating, that.
140.82.113.0/24 is visible in the global routing table: route-views>sh bgp 140.82.113.0 BGP routing table entry for 140.82.113.0/24, version 62582026 Paths: (19 available, best #4, table default) The route is verified by RPKI so it's not a route hijack. Edit: deleted traceroute
This is so cool! I'm not at all familiar with any of this network stuff. Any good resources for learning these tools and when to use them?
https://codeberg.org open source GitHub without Microsoft (it's a German non-profit). You can also host your own lightweight https://forgejo.org instance In case anyone questions whether centralizing literally everything onto GitHub is a good idea, at least as a mirror for things you depend on
gitea is also a great self hosted alternative!
I think that's what Forgejo forked from (and Gitea, in turn, forked from Gogs). I am not involved so don't know the details, but yeah basically all of these will do. I ran my own in the Gitea era and was happy with it, 10x lighter and easier than gitlab, I expect Forgejo has a similar experience.