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.
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`
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.
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).
Incident link: https://status.gitlab.com/pages/incident/5b36dc6502d06804c08...
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.
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
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/
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.
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...
Yep, status page was certainly all green when I started noticing it.
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).
It took at least 5 minutes, closer to 10. I think the outage is so bad, it got pushed fast.
Another day, another reminder why we self-host our GitLab instance. Cloud convenience always has these kinds of trade-offs.
We self host ours too. 100% uptime ;)
what host are you using that gets 100%uptime? A hyperscaler like AWS?
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.
Right, on to another alternative now
Gasp! immediately builds a complete git alternative to never expirence a single second of downtime ever again
Well, git is already distributed, so you could use _any other computer_ instead of gitlab.com...
I'm only kidding, although it could be a good excersise to learn. I think a pure TUI git front end / back end project would be fun to make.
or go back to Mercurial...
Do you remember Mercurial?
Pepperidge Farm remembers.