GitLab incident

503s on GitLab.com

Resolved after 5 hours 34 minutes, affecting Website and Website (Website — Google Compute Engine) and 1 more, on September 24, 2026.

resolved Sep 25, 2026, 04:37 AM UTC

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

Started
Sep 24, 2026, 11:02 PM UTC
Resolved
Sep 25, 2026, 04:37 AM UTC
Duration
5h 34m
Detected by Pingoru
Sep 24, 2026, 11:02 PM UTC

Affected components

WebsiteWebsite (Website — Google Compute Engine)APIAPI (API — Google Compute Engine)Git OperationsGit Operations (Git Operations — Google Compute Engine)Package RegistryPackage Registry (Package Registry — Google Compute Engine)Container RegistryContainer Registry (Container Registry — Google Compute Engine)

Update timeline

  1. investigating Sep 24, 2026, 11:02 PM UTC

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

  2. investigating Sep 24, 2026, 11:04 PM UTC

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

  3. identified Sep 24, 2026, 11:27 PM UTC

    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.

  4. identified Sep 24, 2026, 11:39 PM UTC

    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.

  5. identified Sep 24, 2026, 11:44 PM UTC

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

  6. identified Sep 25, 2026, 12:01 AM UTC

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

  7. identified Sep 25, 2026, 12:19 AM UTC

    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.

  8. identified Sep 25, 2026, 12:31 AM UTC

    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 Sep 25, 2026, 12:41 AM UTC

    Error rates are decreasing, but some customers may still see errors. We are continuing to address the remaining impact and will update again soon.

  10. identified Sep 25, 2026, 01:02 AM UTC

    Error rates are decreasing, but some customers may still see errors. We are continuing to address the remaining impact and will update again soon.

  11. identified Sep 25, 2026, 01:43 AM UTC

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

  12. monitoring Sep 25, 2026, 02:03 AM UTC

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

  13. monitoring Sep 25, 2026, 02:34 AM UTC

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

  14. monitoring Sep 25, 2026, 03:36 AM UTC

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

  15. resolved Sep 25, 2026, 04:37 AM UTC

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

Your product runs on more than GitLab

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.

Add your stack →