GitLab Outage

hckrnws

(status.gitlab.com)

by kunley

davb
31d
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).
1. deckar01
  11d
  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.
  1. physicallyIllfr
    01d
    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.
2. TZubiri
  01d
  It's probably related to the issue published by aikidolabs where leaked per-user gitlab issued emails were being used as a sort of credential.
  https://www.aikido.dev/blog/gitlab-email-push-to-main
b0afc375b5
51d
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.
1. stack_framer
  11d
  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...
delf
21d
You can use GitSocial to mirror to your own bucket for situations like this: `gitsocial mirror https://gitlab.com/owner/repo s3://s3.example.com/mybucket/repo`
https://gitsocial.org/
1. PhilippGille
  11d
  It would be nice to disclose that you're the creator of the tool which you are promoting here.
hk1337
21d
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.
1. mitxela
  11d
  You don't really need one of these systems. You can just host git.
theplumber
01d
Maybe Sam or Dario is playing hide and seek again with the agents….
lampcord
61d
Another day, another reminder why we self-host our GitLab instance. Cloud convenience always has these kinds of trade-offs.
1. zer0x4d
  51d
  We self host ours too. 100% uptime ;)
nabeards
11d
Just went to push code and found this out.
1. nicholasjarnold
  01d
  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.
ChrisArchitect
01d
Incident link(s):
https://status.gitlab.com/pages/incident/5b36dc6502d06804c08...
https://status.gitlab.com/pages/incident/5b36dc6502d06804c08...
smalltorch
41d
Gasp! immediately builds a complete git alternative to never expirence a single second of downtime ever again
1. JonChesterfield
  31d
  Well, git is already distributed, so you could use _any other computer_ instead of gitlab.com...
lemonish97
11d
Right, on to another alternative now
1. Towaway69
  023h
  Back to GitHub /s
tibbon
11d
Seems they can compete with GitHub after all! /s
1. Towaway69
  023h
  Reminds me of LibreOffice cloning the bugs of Office because folks relied on those bugs being there ...