Provider
GitLabIncident detail
500 errors while accessing projects
We're no longer seeing elevated errors, so we are resolving this incident. If you continue to experience any errors on GitLab.com, please open a ticket. More information: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23015
Timeline window
to
Get alerted the next time GitLab breaks
Free email alerts for the handful of vendors you cannot afford to miss. No card, live in about a minute. Paid plans add Slack, Teams, Discord, and webhook delivery across your whole stack, plus higher API quotas.
Timeline
Incident updates
Every update on the official status source, oldest to newest, exactly as it appeared there.
Investigating
We have received reports that some users are unable to access projects and are encountering 500 error messages. Our team is currently investigating the cause. You can follow developments here: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23015
Investigating
We have received reports that some users are unable to access projects and are encountering 500 error messages. Our team is currently investigating the cause.
Investigating
A temporary mitigation has been implemented however the cause of the incident is still being investigated.
Investigating
The incident team is continuing to investigate the issue to identify its root cause and implement an appropriate resolution.
Investigating
The incident team is continuing to investigate the issue to identify its root cause and implement an appropriate resolution.
Investigating
The incident team continues to investigate the cause of this incident. In the meantime, we are seeing intermittent improvements in the ability to access projects.
Investigating
The incident team continues to investigate the cause of this incident. In the meantime, we are seeing intermittent improvements in the ability to access projects.
Investigating
No material updates at this time. We are continuing our investigation. More information: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23015
Investigating
No material updates at this time. We are continuing our investigation. More information: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23015
Investigating
We're continuing our investigation. More information: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23015
Investigating
We're continuing our investigation. More information: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23015
Identified
The team has identified the potential cause of the spike in 500 errors and is working on the fix. More information: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23015
Identified
The team has identified the potential cause of the spike in 500 errors and is working on the fix. More information: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23015
Identified
The team is still working on the fix. More information: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23015
Identified
The team is still working on the fix. More information: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23015
Resolved
We're no longer seeing elevated errors, so we are resolving this incident. If you continue to experience any errors on GitLab.com, please open a ticket. More information: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23015
Keep exploring
More from GitLab
Neighboring incidents on GitLab's timeline and the rest of their record on OutageDeck.