GitLab System Status
SUBSCRIBESUBSCRIBE
Active Incident<br>Updated a few seconds ago
Updated a few seconds ago
This status page is exclusively intended for monitoring GitLab.com and its associated services. If there are any performance or service interruptions, an update will be posted here. If you are experiencing an issue that is not related to an active GitLab.com incident, or if you are encountering service interruptions on GitLab Dedicated, please submit a request via https://support.gitlab.com.
CI pipelines not starting on merge requests.Partial Service Disruption
Incident Status
Partial Service Disruption
Components
Website, CI/CD
Locations
Google Compute Engine
June 30, 2026 11:19 UTC<br>IDENTIFIED
Our engineers are still investigating the issue but jobs are starting to be processed with a delay. More details can be found here:<br>https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22412
June 30, 2026 10:51 UTC<br>IDENTIFIED
No material updates to report. We are continuing to investigate the current issue and engineers are working to determine remediation steps.
June 30, 2026 09:37 UTC<br>IDENTIFIED
We have identified that the sidekiq workers processing the jobs are getting deferred. The team is working on identifying the remediation steps.
June 30, 2026 08:52 UTC<br>INVESTIGATING
We are currently investigating an issue affecting CI pipelines not starting on merge requests. Our team is actively investigating the root cause.
Website<br>Google Compute Engine
Partial Service Disruption
API<br>Google Compute Engine
Operational
Git Operations<br>Google Compute Engine
Operational
Package Registry<br>Google Compute Engine
Operational
Container Registry<br>Google Compute Engine
Operational
GitLab Pages<br>Google Compute Engine
Operational
CI/CD<br>Google Compute Engine
Partial Service Disruption
CI/CD - Hosted runners on Linux<br>Google Compute Engine
Operational
CI/CD - Hosted runners on Windows<br>Google Compute Engine
Operational
CI/CD - Hosted runners on macOS<br>Google Compute Engine AWS
Operational
CI/CD - Hosted runners for GitLab community contributions<br>Google Compute Engine
Operational
CI/CD - Self-managed runners<br>Self-Managed Runner Connectivity
Operational
SAML SSO - GitLab SaaS<br>Google Compute Engine
Operational
Background Processing<br>Google Compute Engine
Operational
GitLab Customers Portal<br>Google Compute Engine
Operational
Support Services<br>Zendesk
Operational
packages.gitlab.com<br>AWS
Operational
version.gitlab.com<br>AWS
Operational
forum.gitlab.com<br>Digital Ocean
Operational
docs.gitlab.com<br>Google Compute Engine
Operational
Canary<br>Google Compute Engine
Operational
GitLab Duo<br>Google Compute Engine
Operational
GitLab agent server for Kubernetes<br>Google Compute Engine
Operational
Status History
Subscribe to receive status updates by email
CloseSubscribeManage Subscription
Manage Existing SubscriptionCreate New Subscription
Subscribe to receive status updates by webhook
Each status update will POST a JSON payload to this URL
Email address for managing webhook
CloseSubscribeManage Subscription
Manage Existing SubscriptionCreate New Subscription
Subscribe to receive status updates in Microsoft Teams
Enter your Microsoft Teams webhook. View Instructions
Email address for managing subscription
CloseSubscribeManage Subscription
Manage Existing SubscriptionCreate New Subscription
Subscribe to receive status updates via RSS
RSS Feed
Close
Follow our status updates on Twitter/X
@gitlabstatus
Close
Subscribe to receive status updates in Slack
Slack channel ID<br>Find the channel ID: Select the channel in your Slack workspace. The channel ID is displayed in the browser URL.<br>Example: https://app.slack.com/client/T04SJBK1C/C03SKGJ1P
Email address
CloseManage Subscription
Manage Existing SubscriptionCreate New Subscription
Subscribe to receive status updates via iCalendar
iCalendar Feed
Close