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

When did the incident start and end?

It started at 2026-11-03 17:20 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 ·

Issues Running Pipelines

Q: What happened?

GitLab reported "Issues Running Pipelines" on its status page at 2026-11-03 17:20 UTC. GitLab CI/CD pipelines do not run on GitLab.com. The issue affects the CI/CD and Google Compute Engine components. GitLab reports some recovery and continues to monitor the issue.

DegradedOfficial update

GitLab CI/CD pipelines do not run on GitLab.com. The issue affects the CI/CD and Google Compute Engine components. GitLab reports some recovery and continues to monitor the issue.

State

Investigating

Started

Ongoing for

1 h 10 min

Worst impact

Degraded

Timeline

3 updates

17:2017:3817:5518:1318:30

DegradedUpdate postedTimes in UTC

Investigating

1 h 10 min 100%

Updates

Times in UTC

As posted by GitLab

Investigating

We’re seeing recovery, and CI/CD pipelines should be running normally again. We’re continuing to monitor to confirm the issue doesn’t return while we investigate the root cause.

Investigating

We’re continuing to investigate this issue and don’t have any new information to share at this time. Our team is working to identify the cause, and we’ll provide another update within an hour.

Investigating

We're investigating reports of customers being unable to run pipelines on GitLab.com without encountering Gitaly-related errors. Details in https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23401.

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

4 h 47 min

This incident

76% shorter than the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

4 h 47 min

median 4 h 47 min

90 days agoToday

Other GitLab incidents

All incidents

GitLab·Elevated CI/CD latency on GitLab.com

GitLab reported elevated latency that affected CI/CD on GitLab.com. Some users saw intermittent slowness with CI/CD jobs, slower job updates and artifact uploads. The incident is resolved and it lasted 4 hours and 47 minutes.

Resolved

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.cc/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.cc/feed.xml?providers=gitlab

Slack

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

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane