Re:GitHub incident 2022-03-23
by thaeli on Wednesday March 23, 2022 @11:49AM
(#30779720)
Also, looking at this it seems like GitHub isn't doing the common SaaS thing of just lying on their status page. Many providers, both internal and external, would look a lot worse if they had honest status pages.
[ Parent
| on HN ]
Re:GitHub incident 2022-03-23
by mirekrusin on Wednesday March 23, 2022 @12:17PM
(#30780051)
They are green for good 15 minutes from first moment i see problems, not the first time, it happens actually quite often. Maybe that's the time they need to confirm/cross check/write status update, don't know.
Re:GitHub incident 2022-03-23
by georgemcbay on Wednesday March 23, 2022 @12:24PM
(#30780154)
While quicker reporting would be better, 15 minutes is anecdotally a lot better than I see from most other services where their status pages will report all-clear hours into full outages.
Yeah, I'm legit impressed with a 15 minute time here.
They probably allow regular SREs to trigger an incident on the status page on their own, when the likes of AWS and other bigger cloud providers are rumored to need approval from a VP[0] to update the status page.
Several of the recent outages were much longer (at least for us, here in Asia) than they admitted on their status page. In one case I started work, noticed I couldn't push to or pull from GitHub, that situation persisted all day, and around 5pm local time (so morning-ish in the US) suddenly their status page acknowledged the problem and a discussion started on HN.
Re:GitHub incident 2022-03-23
by ishanjain28 on Wednesday March 23, 2022 @01:18PM
(#30780845)
They do intentionally or not lie about this on their status page.
From December 25th to December 31st 2021, Github actions had network problems almost every single day for hours and the status page was green out through out that period.
Same thing also happened few months back.
It feels like they do this manually and it's only done when enough people are effected.