Root cause from last weeks 503 errors?

Last week there was a major outage with most of the system down giving 503 errors.

It is noted on status history, but there is no root cause and no link to further details. There was some vague implication it was to do with GCP.

This issue caused us to abort a major release, so we are very interested to know why it happened and when we can be sure about Gitlab again.

I expect to see a root cause analysis on any major outage.

I don’t see any work item listed, how come such a major outage has no record?

Do you have a paid subscription? If so, then open a support ticket here if you need more information: Sign in to GitLab Support

If you are a free user, perhaps you should think about taking up a paid subscription if you require guaranteed service and SLA? Or perhaps run your own Gitlab server for free?

We do have a (probably quite large) paid subscription. However, I haven’t managed to get signed into Gitlab Support because we are on SSO and it just asks “someone” for permission.

If you are using SSO internally, that has nothing to do with Gitlabs support system. In my other post, the subscription that was purchased by your organisation will be tied to the email address of the person who placed the order. So that person will need to login with their email address to Gitlabs support system.

Whether you use SSO or not, has nothing to do with it. But you do have the option to login with Google or Microsoft depending on whether you use their services for SSO or not. And if you cannot login with your SSO because it requires authorisation from your IT Support team, then you’ll need to ask them to allow you to login.