status.io Open in urlscan Pro
13.225.87.123  Public Scan

URL: https://status.io/pages/incident/5b36dc6502d06804c08349f7/615160682a1c540539ae6441
Submission Tags: falconsandbox
Submission: On October 04 via api from US — Scanned from DE

Form analysis 0 forms found in the DOM

Text Content

 * SUBSCRIBESUBSCRIBE

INTERMITTENT NETWORKING ISSUES WITH SOME SHARED RUNNER JOBSOPERATIONAL

Components

CI/CD - GitLab SaaS Shared Runners

Locations

Google Compute Engine

--------------------------------------------------------------------------------


September 29, 2021 19:03 CEST
September 29, 2021 17:03 UTC
[Resolved] Further testing after vendors issued changes has indicated that the
networking issues in shared runners have been resolved, and pipelines should
complete successfully. Details can be found in the issue:
gitlab.com/gitlab-com/gl-infra/production/-/issues/5590

September 27, 2021 21:45 CEST
September 27, 2021 19:45 UTC
[Identified] Based on our investigation of the issue we have downgraded severity
as we continue working with vendors to resolve the intermittent issues with our
GitLab Shared Runners. This will be the last update on this incident via our
status page. Additional details and workarounds at
gitlab.com/gitlab-com/gl-infra/production/-/issues/5590.

September 27, 2021 20:17 CEST
September 27, 2021 18:17 UTC
[Investigating] Engineers are continuing to investigate a few possible root
causes. Workarounds are available along with more details about the incident in
the issue here: gitlab.com/gitlab-com/gl-infra/production/-/issues/5590

September 27, 2021 19:19 CEST
September 27, 2021 17:19 UTC
[Investigating] Investigation is still ongoing, and engineers continue to look
for a root cause. There are workarounds and more details about the investigation
in the issue here: gitlab.com/gitlab-com/gl-infra/production/-/issues/5590

September 27, 2021 18:16 CEST
September 27, 2021 16:16 UTC
[Investigating] Engineers are still investigating to determine the root cause.
No material updates yet but the available workaround and details may be found in
the issue: gitlab.com/gitlab-com/gl-infra/production/-/issues/5590

September 27, 2021 17:10 CEST
September 27, 2021 15:10 UTC
[Investigating] Investigation into the root cause of the networking issue
continues. The current workaround and further details are available in this
issue: gitlab.com/gitlab-com/gl-infra/production/-/issues/5590

September 27, 2021 16:17 CEST
September 27, 2021 14:17 UTC
[Investigating] The engineers are still investigating the root cause of the
issue. Please use the workaround presented at the issue:
gitlab.com/gitlab-com/gl-infra/production/-/issues/5590

September 27, 2021 15:03 CEST
September 27, 2021 13:03 UTC
[Investigating] We’re reverting the last changes as they were causing unexpected
issues. The engineers are still investigating the root cause of the issue. The
workaround is presented at the issue:
gitlab.com/gitlab-com/gl-infra/production/-/issues/5590

September 27, 2021 14:05 CEST
September 27, 2021 12:05 UTC
[Monitoring] The changes are rolled out publicly. We’re monitoring the current
state of the shared runners.

September 27, 2021 13:15 CEST
September 27, 2021 11:15 UTC
[Investigating] With the latest changes, our initial tests look promising. We
are working on making these changes globally.

September 27, 2021 12:27 CEST
September 27, 2021 10:27 UTC
[Investigating] Our engineers are working on implementing the changes that may
help mitigate the issue. We’re working on the rollout plan and monitoring the
current state of the problem.

September 27, 2021 11:13 CEST
September 27, 2021 09:13 UTC
[Investigating] Our engineers are able to reproduce the problem. We’re
investigating the reason for the connection resets on the Shared Runners.

September 27, 2021 10:27 CEST
September 27, 2021 08:27 UTC
[Investigating] Our engineers are attempting to make the consistently
reproducible case as the issue is rather intermittent. The investigation is in
the progress.

September 27, 2021 09:26 CEST
September 27, 2021 07:26 UTC
[Investigating] Our engineers are still investigating the root cause of the
issue. See details in issue:
gitlab.com/gitlab-com/gl-infra/production/-/issues/5590

September 27, 2021 08:37 CEST
September 27, 2021 06:37 UTC
[Investigating] No material updates, our engineers are still investigating the
root cause. Details in issue:
gitlab.com/gitlab-com/gl-infra/production/-/issues/5590

September 27, 2021 08:10 CEST
September 27, 2021 06:10 UTC
[Investigating] We are currently seeing intermittent networking issues with some
of the shared runner jobs. Our infrastructure team is currently investigating
this. Please see: gitlab.com/gitlab-com/gl-infra/production/-/issues/5590

Back to current status
StatusHistory

 * 
 * 
 * 
 * 
 * 
 * 

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 VIA RSS


RSS Feed
Close

FOLLOW OUR STATUS UPDATES ON TWITTER


@gitlabstatus
Close
Subscribe to receive status updates in Slack




Slack channel ID

Find the channel ID: Select the channel in your Slack workspace. The channel ID
is displayed in the browser URL.

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