Search

Changes / GitLab / A MacOS Runner is failing jobs

GitLab: Major incident: A MacOS Runner is failing jobs

Summary

Summary pending. The diff below shows exactly what changed.

Major incidentLabel: outage (model (Jev), 92%)Changed Detected Source: status.gitlab.com (opens in new tab)

Incident page: full timeline of updates →

What changed

AddedTitle#1
Before: not present
After: A MacOS Runner is failing jobs
AddedImpact#2
Before: not present
After: major
AddedStatus#3
Before: not present
After: resolved
AddedStart time#4
Before: not present
After: 2025-11-21 11:56 UTC
AddedResolved time#5
Before: not present
After: 2025-11-21 18:15 UTC
AddedAffected components#6
Before: not present
After: CI/CD, CI/CD - Hosted runners on macOS
AddedUpdateinvestigating#7
Before: not present
After: We've received reports that jobs that run on a specific macOS GitLab Runner (with the tag `saas-macos-large-m2pro`) have been failing with a “context deadline exceeded” error. We are in the process of investigating. As a workaround, you can switch to other runners. See https://gitlab.com/gitlab-com/gl-infra/production/-/issues/20878 for more details
AddedUpdateinvestigating#8
Before: not present
After: Investigation is ongoing, and we're reviewing relevant runbooks for additional troubleshooting steps. See https://gitlab.com/gitlab-com/gl-infra/production/-/issues/20878 for more details
AddedUpdateinvestigating#9
Before: not present
After: No material updates to report. We continue troubleshooting the runner's unavailability. See https://gitlab.com/gitlab-com/gl-infra/production/-/issues/20878 for more details
AddedUpdateinvestigating#10
Before: not present
After: We continue investigating the root cause. See https://gitlab.com/gitlab-com/gl-infra/production/-/issues/20878 for more details
AddedUpdateinvestigating#11
Before: not present
After: Latest troubleshooting results point a networking issue preventing connectivity with the affected macOS Runner. Investigation continues at gitlab.com/gitlab-com/gl-infra/production/-/issues/20878.
AddedUpdateinvestigating#12
Before: not present
After: We continue to troubleshoot network connectivity for the affected Runner, no material updates to report. Follow https://gitlab.com/gitlab-com/gl-infra/production/-/issues/20878 for details.
AddedUpdateinvestigating#13
Before: not present
After: We have identified a misconfiguration in our Runner infrastructure's routing policies as the potential cause for this issue. Follow https://gitlab.com/gitlab-com/gl-infra/production/-/issues/20878 for details.
AddedUpdateinvestigating#14
Before: not present
After: No material updates to share. We appreciate your patience while we continue investigating this issue, please see https://gitlab.com/gitlab-com/gl-infra/production/-/issues/20878 for details.
AddedUpdateidentified#15
Before: not present
After: We have identified the configuration causing network disruption with the affected Runner and we are working on fixing it. See https://gitlab.com/gitlab-com/gl-infra/production/-/issues/20878 for details.
AddedUpdateresolved#16
Before: not present
After: We have completed the infrastructure restoration tasks to fix the connectivity issue with the affected Runner. Since 17:51 UTC jobs on this Runner are being processed normally. This is now resolved.

First version of this incident archived by Rewindex. View the live incident (opens in new tab).

History of this incident

When (UTC)ChangeKind
Major incident: A MacOS Runner is failing jobs (this change)Major incident

All GitLab changes → · GitLab profile · Markdown · JSON