Rendered at 10:10:36 GMT+0000 (Coordinated Universal Time) with Cloudflare Workers.
davb 11 hours 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 11 hours 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.
physicallyIllfr 10 hours ago [-]
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.
TZubiri 9 hours ago [-]
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.
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 11 hours 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:
Yep, status page was certainly all green when I started noticing it.
seabrookmx 11 hours 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 11 hours ago [-]
It took at least 5 minutes, closer to 10. I think the outage is so bad, it got pushed fast.
theplumber 2 hours ago [-]
Maybe Sam or Dario is playing hide and seek again with the agents….
delf 10 hours ago [-]
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`
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.
mitxela 8 hours ago [-]
You don't really need one of these systems. You can just host git.
hk1337 2 hours ago [-]
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.
lampcord 9 hours ago [-]
Another day, another reminder why we self-host our GitLab instance. Cloud convenience always has these kinds of trade-offs.
zer0x4d 9 hours ago [-]
We self host ours too. 100% uptime ;)
gib444 4 hours ago [-]
How do you do upgrades?
TZubiri 9 hours ago [-]
what host are you using that gets 100%uptime? A hyperscaler like AWS?
mitxela 8 hours ago [-]
Just means it hasn't crashed yet.
zer0x4d 9 hours ago [-]
I run it on Digital Ocean but AWS should be fine too.
firesteelrain 8 hours ago [-]
VMWare Cloud Foundation with Dell R7725s
nabeards 11 hours ago [-]
Just went to push code and found this out.
nicholasjarnold 11 hours 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.
https://www.aikido.dev/blog/gitlab-email-push-to-main
https://status.gitlab.com/pages/history/5b36dc6502d06804c083...
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).
https://gitsocial.org/
git+ssh also seems affected, as I'm unable to push/pull right now.
https://status.gitlab.com/pages/incident/5b36dc6502d06804c08...
https://status.gitlab.com/pages/incident/5b36dc6502d06804c08...
Do you remember Mercurial?
Pepperidge Farm remembers.