Skip to main content
GitLab

Elevated CI/CD latency on GitLab.com

Degraded Lasted 0m · started · GitLab's page

Level
confirmed
Worst impact
Degraded
Down Index
8of 100

What to do

  • Check whether your product depends on GitLab. Check your stack

    Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.
  • Confirm your retries, queues and scheduled jobs caught up after the 0m it lasted.

    Anything that failed between 2026-11-03 09:51 UTC and 2026-11-03 09:51 UTC may need a replay.
  • Subscribe to GitLab's feed to hear about the next one first. RSS feed

    https://down.guide/feed?provider=gitlab works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from GitLab 1

  1. resolved

    November 3, 2026 05:06 UTC Investigating - We're investigating elevated latency affecting CI/CD on GitLab.com. No user impact has been observed at this time. We'll update as we learn more. November 3, 2026 05:27 UTC Investigating - Some users may have seen intermittent slowness with CI/CD jobs, including slower job updates and artifact uploads. Latency is recovering and we're continuing to investigate. November 3, 2026 06:01 UTC Identified - We've identified a contributing factor to intermittent slowness affecting CI/CD on GitLab.com, including slower job requests, job updates and artifact uploads. We're still investigating the root cause and working to mitigate the issue. November 3, 2026 07:10 UTC Monitoring - We've applied a mitigation for the intermittent slowness affecting CI/CD on GitLab.com, and performance has returned to normal. We're monitoring to make sure the issue doesn't recur. November 3, 2026 08:14 UTC Monitoring - We continue to monitor the incident to ensure the issue doesn't recur. Find more information about the incident here: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23392 November 3, 2026 09:51 UTC Resolved - After continuous monitoring, the latency has returned to baseline. We're marking this incident resolved. Find more information about the incident here: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23392

    provider

Reports count in aggregate; nothing about you is shown.

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Questions about DWN-673c716057

Is GitLab still down?

No, this incident was resolved 2026-11-03 09:51 UTC. For GitLab's live state, see https://down.guide/gitlab.

How long did it last?

0m, from 2026-11-03 09:51 UTC to 2026-11-03 09:51 UTC, by the times GitLab posted.

What caused it?

GitLab hasn't published a root cause. If it does, it shows here.

Where does this come from?

GitLab's official status page, https://status.gitlab.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.