GitLab lists these components: CI/CD, Google Compute Engine.

When did the incident start and end?

It started at 2026-11-03 05:06 UTC. This page shows the end time when GitLab marks it resolved.

How do I get alerts for GitLab?

Subscribe to the GitLab live feed over RSS or in Slack, or add the outages.live MCP server to your coding agent.

Where does this information come from?

From the official status page of GitLab. outages.live reads it every few minutes and keeps every update. A language model writes the summary from those updates.

GitLabIncident · 2026-11-03 05:06 UTC

Elevated CI/CD latency on GitLab.com

Q: What happened?

GitLab reported "Elevated CI/CD latency on GitLab.com" on its status page at 2026-11-03 05:06 UTC. GitLab CI/CD on GitLab.com has elevated latency. This affects CI/CD and Google Compute Engine. Some users may have slower job requests, job updates, and artifact uploads. GitLab identified a contributing factor and continues to investigate the root cause. The incident is not resolved.

DegradedOfficial update

GitLab CI/CD on GitLab.com has elevated latency. This affects CI/CD and Google Compute Engine. Some users may have slower job requests, job updates, and artifact uploads. GitLab identified a contributing factor and continues to investigate the root cause. The incident is not resolved.

State

Investigating

Started

2 h ago

2026-11-03 05:06 UTC

Ongoing for

1 h 53 min

Worst impact

Degraded

Timeline

3 updates

05:0605:3406:0306:3106:59

DegradedUpdate postedTimes in UTC

Investigating

1 h 53 min 100%

Updates

Times in UTC

As posted by GitLab

Investigating2026-11-03 06:03 UTC

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.

Investigating2026-11-03 05:30 UTC

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.

Investigating2026-11-03 05:09 UTC

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.

Affected components

CI/CDGoogle Compute Engine

GitLab in the last 90 days

Full history

90 days agoToday

Incidents in 90 days

Days with an incident

Median duration

Not enough data

This incident

Not comparable

Follow GitLab

Your coding agent knows when GitLab is down, and tells you when a failure is theirs, not yours. You can also get GitLab incidents in a feed reader or in Slack.

Prompt

Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.live/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "gitlab" and tell me if GitLab has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS

https://outages.live/feed.xml?providers=gitlab

Slack

/feed subscribe https://outages.live/feed.xml?providers=gitlab

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane