Today's Trends
minorArchivedGitLab

GitLab: 503s on GitLab.com

  1. Investigating(done)
  2. Trending(skipped)
  3. Workaround available(skipped)
  4. Resolved(done)
  5. Archived

Executive summary

GitLab.com is experiencing intermittent 503 errors, causing slow service and site issues. The incident has been identified but ongoing investigation is required.

No verified workaround yet

This incident was resolved upstream without a reported workaround.

Official fix
Technical root cause

Under active investigation. No report has identified a root cause yet.

Evidence

1 report · 1 StatusShow
  1. [1]
    Status First report
    503s on GitLab.com(opens official status page in a new tab)

    October 16, 2026 16:10 UTC Investigating - We are investigating the cause of 503s on GitLab.com and the site moving slowly. We will update once we have additional details. October 16, 2026 16:25 UTC Investigating - We are still investigating the cause of 503 on GitLab.com. We are seeing some services return but errors still intermittent. More details at: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23402 October 16, 2026 16:40 UTC Identified - We have identified the cause of…

    by gitlab status

Timeline

  1. First report on status page

    503s on GitLab.com

    Source
  2. Official statement

    October 16, 2026 16:10 UTC Investigating - We are investigating the cause of 503s on GitLab.com and the site moving slowly.

    Source
  3. Status changed

    Status changed: new → archived (resolved more than 14 days ago).