Today's Trends
minorArchivedGitLab

GitLab.com CI/CD Incident

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

Executive summary

A GitLab.com incident affecting a limited number of customers resulted in CI/CD pipelines failing with the error 'CI configuration fetch from Gitaly timed out'. The UI may also be slow. A temporary mitigation has been applied to address these issues.

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
    GitLab.com CI/CD Incident(opens official status page in a new tab)

    October 16, 2026 11:33 UTC Investigating - We’re investigating an issue affecting CI/CD on GitLab.com for a limited number of customers. Pipelines may fail with the following error, and the UI may be slow: “CI configuration fetch from Gitaly timed out. This may indicate Gitaly service slowness or an outage.” More updates to follow. October 16, 2026 12:28 UTC Monitoring - We've applied a temporary mitigation to address CI/CD failures and UI slowness affecting a limited number of GitLab.com…

    by gitlab status

Timeline

  1. First report on status page

    GitLab.com CI/CD Incident

    Source
  2. Official statement

    October 16, 2026 11:33 UTC Investigating - We’re investigating an issue affecting CI/CD on GitLab.com for a limited number of customers.

    Source
  3. Status changed

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