GitHub incident: 2022/03/24
githubstatus.com
GitHub incident: 2022/03/24
1–10 of 103 posts
Re: GitHub incident: 2022/03/24
#2Another day, another Github incident...
Re: GitHub incident: 2022/03/24
#3I came up with what I thought was an appropriate riff on XKCD 303, but I fear we might be running out of excuses now :(
Re: GitHub incident: 2022/03/24
#4Not one, but three outages in a row [0], if you went 'all in' on GitHub (Including GitHub Actions). Even under 'scheduled maintenance' something else unexpectedly goes down.
From [0]:
>> Until the next time GitHub goes down again (hopefully that won't be in another month's time).
>> That says it all really. Lets reset the counter and try this again.
Going to reset the counter once again. Hopefully GitHub won't have another outage in a week's (or even a months) time.
It turns out that my whole comment chain in [0] was right in the 'long term' of not 'centralizing everything' [1] on GitHub since 2020.
Re: GitHub incident: 2022/03/24
#5How does GitLab compare in terms of it's CI/CD reliability?
Re: GitHub incident: 2022/03/24
#6Re: GitHub incident: 2022/03/24
#7How does GitLab compare in terms of it's CI/CD reliability?
Our on-prem instance hasn't had any downtime I'm aware of in the past year at least.
Re: GitHub incident: 2022/03/24
#8How does GitLab compare in terms of it's CI/CD reliability?
Our on-prem instance hasn't had any downtime I'm aware of in the past year at least.
Same uptime as my development environment of GitHub then! (And similarly, my statement is as relevant as yours when it comes to the services CI uptime)
Re: GitHub incident: 2022/03/24
#9Well this time looks different than the last.
* We get a non-machine message that migrations to GitHub are temporarily disabled.
* We get an exact message that the delivery of webhooks and action kickoff is delayed.
So while there are no 500s - I just have to wait a few more minutes for builds to kick off. So at least I can still review code in the meantime.
Re: GitHub incident: 2022/03/24
#10https://www.githubstatus.com/
at the time of posting, webhooks and actions are still struggling :(
there have now been 23 incident outages in 90 days. if anyone from Microsoft is reading this, you need to start considering this degradation as the companies highest priority. At this point, Gitea, Gitlab and others (self hosted or otherwise) are beginning to gain traction as a more reliable and performant alternative.
Youre facing the very real possibility of spending nearly eight billion dollars to capture the developer mindshare of the internet, only to lose it in just four years.