6 ms·
Gitlab is down
- hknapp 5y agoSeeing the same error
- totaldude87 5y agoand the status page is all green (sigh)- https://status.gitlab.com/ https://status.gitlab.com/ where as downdetector definitely shows that there are issues - https://downdetector.com/status/gitlab/ https://downdetector.com/status/gitlab/ I guess, the status pages should now have a button to get data from public.. crowd sourced status page?
- dnsmichi 5y agoGitLab team member here - sorry for the delay, SREs are investigating. https://status.gitlab.com/ https://status.gitlab.com/ is updated. Edit: https://status.gitlab.com/pages/incident/5b36dc6502d06804c08349f7/61f7fec31302de053277fa1a https://status.gitlab.com/pages/incident/5b36dc6502d06804c08...
- m4lvin 5y agoIt is updated by now - some seconds delay is fine I think and if they would not cache the status page it might go down in a blink now too ;-)
- teekert 5y agoIt's there now, added seconds ago.
- teddyh 5y agoAnd this is why you self-host on your own instance.
- analogsalad 5y agoIndeed, I can't remember a single time where a self-hosted server crashed. They run for decades with 0 downtime.
- rvz 5y agoExactly. That is the whole point. I keep telling that for GitHub since that goes down once a month. [0][1] GitLab SaSS is the same but a self-hosted backup is better. [0] https://news.ycombinator.com/item?id=29901564 https://news.ycombinator.com/item?id=29901564 [1] https://news.ycombinator.com/item?id=29379648 https://news.ycombinator.com/item?id=29379648
- rovr138 5y agoEveryone should have backups and these things aren't infallible. Gitlab is a perfect example. They had database issues and had to restore from backups already.
- miltonlaxer 5y agoFYI GitHub Enterprise can be self-hosted https://docs.github.com/en/get-started/learning-about-github/githubs-products#github-enterprise https://docs.github.com/en/get-started/learning-about-github...
- sdoering 5y agoNot sure if this is irony (I often don't identify irony as such). But I fatfingered a lot of self hosted stuff in my time.
- analogsalad 5y agoIt's full-blown sarcasm. Sorry for omitting the /s.
- deleted 5y ago[deleted]
- john_cogs 5y agoGitLab team member here. We're aware of the incident and the status page has been updated. We will provide further updates on the status page as they become available. (Edited now that the status page has been updated).
- totaldude87 5y agoAwesome, thank you! Godspeed!
- Dayshine 5y agoIt took (by my measure) 13 minutes for a full outage to be represented on the status page. I was under the impression that gitlab use gitlab.com for their work. Surely someone would have noticed within seconds that it was down? Why have the misleading "updated a few seconds" ago text if it doesn't update on complete failure? :)
- vasco 5y agoAfter you notice I assume you have to declare an incident, get a call going, assess the extent of the issues, get the needed people involved, and then you'd announce on the status page. 13 minutes isn't amazing but it also isn't terrible. Perhaps you have better ways of keeping status pages updated much faster while also not ending up ramping up the posting of false positives.
- aejnsn 5y ago13 minutes is pretty solid compared to anything of recent AWS outages.
- pixl97 5y agoIt doesn't matter if each individual detects the outage because they'll start blame at the local source and move further up the tree rather than assign blame to a full system failure right off the bat. 99.9% of the time it's going to be a local failure affecting the individual. Also, most alerting systems like check multiple times before declaring a public outage, many times 2 to 3 failures some seconds apart are needed.
- simon04 5y agohttps://status.gitlab.com/pages/incident/5b36dc6502d06804c08349f7/61f7fec31302de053277fa1a https://status.gitlab.com/pages/incident/5b36dc6502d06804c08... – January 31, 2022 15:22 UTC – System Wide Outage
- rvz 5y agoFor SaSS, it is down. But not if you are self-hosting your own. Just look at Gnome: [0]. They are doing it right. [0] https://git.gnome.org https://git.gnome.org
- iamcreasy 5y agoIs gitlab.gnome.org/GNOME set to forward to git.gnome.org?
- deleted 5y ago[deleted]
- hobo_mark 5y agoIt's interesting that different pieces of gitlab.com appear to be running on a hodge-podge of GCP, DO, AWS and AZ... I wonder why that would be the case?
- karmakaze 5y agoThis could make good sense if they want to provide service where the customers use it.
- Traubenfuchs 5y agoMaybe they fell for the polynimbus meme.
- temptemptemp111 5y agoBut but CLOUD NATIVE! https://about.gitlab.com/cloud-native/ https://about.gitlab.com/cloud-native/
- routeroff 5y agooverleaf.com is also down, https://status.overleaf.com/ https://status.overleaf.com/ Maybe some common severs ?
- tovej 5y agoDefinitely related, overleaf probably depends on gitlab. The overleaf outage ended right when the gitlab outage did.
- markdog12 5y agoProb just a coincidence, but our Memorystore (hosted redis) instance went down with a "repairing" status around the same time.
- mlvljr 5y ago