GitLab Outage

2 days ago (status.gitlab.com)

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).

  • 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.

    • I dont think bots need bonus/trials. There are lots and lots of ways to get free, or virtually free tokens. Hell half the vibe coded AI chrome extensions send store their openrouter keys client side.

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.

I like what tangled seems like it could be but it's still too new to really use. It'd be nice if it was more of an aggregator for git servers where still access a git server whether tangled is up or not.

  • You don't really need one of these systems. You can just host git.

    • True, my thought was a site that just makes it easier to see all the various users. Like GitHub but links to users and orgs actually go to each person’s server.

Just went to push code and found this out.

  • Code review for me... Hit the 503. The status page lagged the event by ~10 mins or so it seems.

    git+ssh also seems affected, as I'm unable to push/pull right now.

Gasp! immediately builds a complete git alternative to never expirence a single second of downtime ever again