Outage in GitLab

Jobs not being picked up/stuck pending

Resolved Minor

May 18, 2026 - Started about 17 hours ago - Lasted 36 minutes

Incident Report

Summary AI Generated

GitLab experienced CI/CD pipeline disruptions where jobs were stuck in pending status and not being executed due to runner pool exhaustion. The incident affected shared runners, private runners, and Windows shared runners across GitLab SaaS. The issue was resolved by adding more runners to the pool, with the incident lasting 36 minutes.

We've identified the root cause of some jobs not getting picked up due to runner pool exhaustion. We're working on getting more runners added to the pool.

More details about the incident here: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22145

Components affected

GitLab CI/CD - SaaS Shared Runners GitLab CI/CD - SaaS Private Runners GitLab CI/CD - Windows Shared Runners (Beta)

Trusted by 1,000+ teams

Never miss outages in third-party dependencies

Stop finding out about outages from your users. Monitor 6,320+ cloud services and get alerted the second something breaks.

Start Free Trial Learn More

Latest Updates ( sorted recent to last )

about 17 hours ago - at 05/18/2026 11:03AM

Latest GitLab outages

Degraded performance affecting Duo features - 4 days ago

Slowed pipelines and CI/CD Jobs - 5 days ago

Elevated 5xx Errors on GitLab.com - 6 days ago

Elevated error rates on GitLab.com - 6 days ago

500 errors accessing repositories - 8 days ago

Never miss outages in third-party dependencies

With IsDown, you can monitor all your critical services' official status pages from one centralized dashboard and receive instant alerts the moment an outage is detected. Say goodbye to constantly checking multiple sites for updates and stay ahead of outages with IsDown.

Start free trial

No credit card required · Cancel anytime · 6320 services available

Integrations with Slack Microsoft Teams Google Chat Datadog PagerDuty Zapier Discord Webhook