A macOS runner failure

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

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

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

We continue investigating the root cause. See https://gitlab.com/gitlab-com/gl-infra/production/-/issues/20878 for more details

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.

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.

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.

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.

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.