32 points kunley 59 minutes ago 10 comments
b0afc375b5 51 minutes ago | parent
Interesting that the status page was updated immediately. Is this the norm now? I remember back in the day when status pages showed all green even when servers were clearly down for a long time already.
thesh4d0w 48 minutes ago | parent
It took at least 5 minutes, closer to 10. I think the outage is so bad, it got pushed fast.
stack_framer 47 minutes ago | parent
It was not updated immediately. I was seeing 503s for a solid 15 minutes while the status page was all green. This is also their second outage today:
https://status.gitlab.com/pages/history/5b36dc6502d06804c083...
nicholasjarnold 46 minutes ago | parent
Yep, status page was certainly all green when I started noticing it.
seabrookmx 45 minutes ago | parent
As others mentioned, it wasn't that quick.
It's also not accurate. After nearly a half hour the page shows "git operations" as green but I'm not able to push/pull from my repos with SSH or HTTPS (and haven't been able to the whole time).
smalltorch 50 minutes ago | parent
Gasp! immediately builds a complete git alternative to never expirence a single second of downtime ever again
davb 41 minutes ago | parent
Coincidentally (?) we’ve seen a huge uptick in failed login attempts to our MFA-protected admin accounts on our self-hosted Gitlab CE instance today. They’re coming from thousands of IPs across hundreds of networks (VPS providers and, apparently, residential proxies).
deckar01 37 minutes ago | parent
There was a relative lull in GitHub bot activity the last few weeks, but they seem to be back today. I assume the promo token flood gates opened for the new models.