Companies / GitLab / incidents

GitLab: 503s on GitLab.com

Affected components: APIBackground ProcessingCanaryCI/CDCI/CD - Hosted runners for GitLab community contributionsCI/CD - Hosted runners on LinuxCI/CD - Hosted runners on macOSCI/CD - Hosted runners on WindowsCI/CD - Self-managed runnersContainer Registrydocs.gitlab.comforum.gitlab.comGitLab agent server for KubernetesGitLab Customers PortalGitLab DuoGitLab PagesGit OperationsPackage Registrypackages.gitlab.comSAML SSO - GitLab SaaSSupport Servicesversion.gitlab.comWebsite

Timeline of updates

1. investigating2026-09-24 23:02 UTC

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

2. investigating2026-09-24 23:04 UTC

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

3. identified2026-09-24 23:27 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. identified2026-09-24 23:39 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. identified2026-09-24 23:44 UTC

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

6. identified2026-09-25 00:01 UTC

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

7. identified2026-09-25 00:19 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. identified2026-09-25 00:31 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. identified2026-09-25 00:41 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. identified2026-09-25 01:02 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. identified2026-09-25 01:43 UTC

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

12. monitoring2026-09-25 02:03 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. monitoring2026-09-25 02:34 UTC

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

14. monitoring2026-09-25 03:36 UTC

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

15. resolved2026-09-25 04:37 UTC

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

Rewindex changes for this incident

• Critical incident: 503s on GitLab.com 2026-09-24 23:02 UTC

Impact, status and times are the vendor’s own, as last archived. View on status.gitlab.com (opens in new tab). GitLab profile · Recent GitLab incidents · Markdown · JSON