Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Gitlab is down

gitlab.com

Post reply on HN
Print view View original

21–30 of 65 posts

Re: Gitlab is down

#21

Post by Dayshine »

john_cogs wrote: post #7

GitLab 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).

It 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? :)

Re: Gitlab is down

#22

Post by karmakaze »

hobo_mark wrote: post #17

It'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?

This could make good sense if they want to provide service where the customers use it.

Re: Gitlab is down

#23

Post by rvz »

analogsalad wrote: post #14
teddyh wrote: post #4

And this is why you self-host on your own instance.

Indeed, I can't remember a single time where a self-hosted server crashed. They run for decades with 0 downtime.

Exactly. 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

[1] https://news.ycombinator.com/item?id=29379648

Re: Gitlab is down

#25

Post by vasco »

Dayshine wrote: post #21
john_cogs wrote: post #7

GitLab 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).

It 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? :)

After 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.

Re: Gitlab is down

#26

Post by sdoering »

analogsalad wrote: post #14
teddyh wrote: post #4

And this is why you self-host on your own instance.

Indeed, I can't remember a single time where a self-hosted server crashed. They run for decades with 0 downtime.

Not 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.

Re: Gitlab is down

#28

Post by pixl97 »

Dayshine wrote: post #21
john_cogs wrote: post #7

GitLab 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).

It 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? :)

It 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.

Re: Gitlab is down

#29

Post by analogsalad »

sdoering wrote: post #26
analogsalad wrote: post #14

Earlier quoted context omitted.

Indeed, I can't remember a single time where a self-hosted server crashed. They run for decades with 0 downtime.

Not 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.

It's full-blown sarcasm. Sorry for omitting the /s.
Post reply on HN