← Back to GitLab.com History
unknown✓ Resolved
503s on GitLab.com
Status
resolved
Duration
5h 35m
Updates
15
Coverage
0 articles
INCIDENT TIMELINE
✓ Resolved
This incident has been resolved.
resolved
This incident has been resolved. GitLab.com is operating normally, and we are continuing to monitor the service.
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 now operational and we're continuing to monitor the situation. We are assessing any outstanding impacts during the disruption window.
identified
GitLab remains stable and error rates have decreased. We are still actively engaging in recovery efforts.
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 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
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'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 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.
📊 TECHNICAL DETAILS
Internal ID
c4025e9e-4ca4-49c5-a522-36ebdd0044e9
External ID
6ab5ac13c927d205640922b7
🕐 First reported
🔄 Last Updated
✓ Resolved
UNKNOWN
Impact Level
5h 35m
Total Duration
15
Status Updates
REQUEST COVERAGE
No article has been written for this incident yet. When 100 people request coverage, we request generation of one.
0 / 100 requests100 more needed