GitLab Outage

(status.gitlab.com)

30 points | by kunley 50 minutes ago

4 comments

  • davb 32 minutes ago
    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 28 minutes ago
      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.
  • b0afc375b5 42 minutes ago
    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.
    • stack_framer 38 minutes ago
      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 37 minutes ago
        Yep, status page was certainly all green when I started noticing it.
    • seabrookmx 35 minutes ago
      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).

    • thesh4d0w 39 minutes ago
      It took at least 5 minutes, closer to 10. I think the outage is so bad, it got pushed fast.
  • nabeards 47 minutes ago
    Just went to push code and found this out.
    • nicholasjarnold 45 minutes ago
      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.

  • smalltorch 41 minutes ago
    Gasp! immediately builds a complete git alternative to never expirence a single second of downtime ever again