503s on GitLab.comOperational

Resolved

Started

Lasted 5h 35m

View official incident ↗

Updates

  1. Resolved

    This incident has been resolved. GitLab.com is operating normally, and we are continuing to monitor the service.

  2. Monitoring

    GitLab services are operational and we're continuing to monitor the situation. We are assessing any outstanding impacts during the disruption window.

  3. Monitoring

    GitLab services are operational and we're continuing to monitor the situation. We are assessing any outstanding impacts during the disruption window.

  4. Monitoring

    GitLab services are now operational and we're continuing to monitor the situation. We are assessing any outstanding impacts during the disruption window.

  5. Identified

    GitLab remains stable and error rates have decreased. We are still actively engaging in recovery efforts.

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

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

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

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

  10. Identified

    We are seeing some recovery based on our mitigation efforts, which are ongoing. We will update with more details shortly.

  11. Identified

    We are seeing some recovery based on our mitigation efforts, which are ongoing. We will update with more details shortly.

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

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

  14. Investigating

    We are recieving reports of 503 errors on GitLab.com. This is under active investigation. We will update with more details shortly.

  15. Investigating

    We are recieving reports of 503 errors on GitLab.com. This is under active investigation. We will update with more details shortly.