Provider
GitLabIncident detail
503s on GitLab.com
This incident has been resolved. GitLab.com is operating normally, and we are continuing to monitor the service.
Resolved incidentMajor1 affected service
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 are recieving reports of 503 errors on GitLab.com. This is under active investigation. We will update with more details shortly.
Investigating
We are recieving reports of 503 errors on GitLab.com. This is under active investigation. We will update with more details shortly.
Investigating
We are recieving reports of 503 errors on GitLab.com. This is under active investigation. We will update with more details shortly.
Investigating
We are recieving reports of 503 errors on GitLab.com. This is under active investigation. We will update with more details shortly.
Identified
We've identified the cause of 503 errors on GitLab.com and are working on mitigating the issue. We will update with more details shortly.
Identified
We've identified the cause of 503 errors on GitLab.com and are working on mitigating the issue. We will update with more details shortly.
Identified
We've identified the cause of 503 errors on GitLab.com and are working on mitigating the issue. We're aware that the API is also affected. We will update with more details shortly.
Identified
We've identified the cause of 503 errors on GitLab.com and are working on mitigating the issue. We're aware that the API is also affected. We will update with more details shortly.
Identified
We are seeing some recovery based on our mitigation efforts, which are ongoing. We will update with more details shortly.
Identified
We are seeing some recovery based on our mitigation efforts, which are ongoing. We will update with more details shortly.
Identified
We are seeing some recovery based on our mitigation efforts, which are ongoing. We will update with more details shortly.
Identified
We are seeing some recovery based on our mitigation efforts, which are ongoing. We will update with more details shortly.
Identified
Error rate is decreasing after active mitigation efforts. We're still actively working on addressing the root cause. We will update with more details shortly.
Identified
Error rate is decreasing after active mitigation efforts. We're still actively working on addressing the root cause. We will update with more details shortly.
Identified
Error rate is decreasing after active mitigation efforts. We're still actively working on addressing the root cause. We will update with more details shortly.
Identified
Error rate is decreasing after active mitigation efforts. We're still actively working on addressing the root cause. We will update with more details shortly.
Identified
Error rates are decreasing, but some customers may still see errors. We are continuing to address the remaining impact and will update again soon.
Identified
Error rates are decreasing, but some customers may still see errors. We are continuing to address the remaining impact and will update again soon.
Identified
Error rates are decreasing, but some customers may still see errors. We are continuing to address the remaining impact and will update again soon.
Identified
Error rates are decreasing, but some customers may still see errors. We are continuing to address the remaining impact and will update again soon.
Identified
GitLab remains stable and error rates have decreased. We are still actively engaging in recovery efforts.
Identified
GitLab remains stable and error rates have decreased. We are still actively engaging in recovery efforts.
Monitoring
GitLab services are now operational and we're continuing to monitor the situation. We are assessing any outstanding impacts during the disruption window.
Monitoring
GitLab services are now operational and we're continuing to monitor the situation. We are assessing any outstanding impacts during the disruption window.
Monitoring
GitLab services are operational and we're continuing to monitor the situation. We are assessing any outstanding impacts during the disruption window.
Monitoring
GitLab services are operational and we're continuing to monitor the situation. We are assessing any outstanding impacts during the disruption window.
Monitoring
GitLab services are operational and we're continuing to monitor the situation. We are assessing any outstanding impacts during the disruption window.
Monitoring
GitLab services are operational and we're continuing to monitor the situation. We are assessing any outstanding impacts during the disruption window.
Resolved
This incident has been resolved. GitLab.com is operating normally, and we are continuing to monitor the service.
Keep exploring
More from GitLab
Neighboring incidents on GitLab's timeline and the rest of their record on OutageDeck.