GitLab System Status

2 min read Original article ↗

Components

Background Processing

Locations

Google Compute Engine


July 14, 2021 01:06 UTC

RESOLVED

The incident has now been resolved and systems have normalised. Our engineers will continue to perform root-cause analysis to reduce chance of re-occurrence. You can follow along here: https://gitlab.com/gitlab-com/gl-infra/production/-/issues/5158


July 14, 2021 00:36 UTC

MONITORING

While the issue has been mitigated and queue backlogs have been processed, our engineers will continue to monitor and conduct root-cause analysis. More details: More details: gitlab.com/gitlab-com/gl-infra/production/-/issues/5158


July 13, 2021 23:50 UTC

INVESTIGATING

Queue backlogs are continuing to be processed. Next update in 30mins. Thank you for your patience and understanding! More details: gitlab.com/gitlab-com/gl-infra/production/-/issues/5158


July 13, 2021 23:30 UTC

INVESTIGATING

The post-receive queue backlogs are continuing to be processed. We are focusing on helping other queues to catch up as well. More details: https://gitlab.com/gitlab-com/gl-infra/production/-/issues/5158


July 13, 2021 23:10 UTC

INVESTIGATING

We are starting to see some recovery and queue backlogs are being processed now. See gitlab.com/gitlab-com/gl-infra/production/-/issues/5158 for details and ongoing discussion.


July 13, 2021 22:45 UTC

INVESTIGATING

We thank you again for your patience as our engineers continue to investigate the root cause of the degraded performance. More details in: gitlab.com/gitlab-com/gl-infra/production/-/issues/5158


July 13, 2021 22:29 UTC

INVESTIGATING

No material updates at this time. Our engineers continue to investigate the degraded state of background processing. For more information please see https://gitlab.com/gitlab-com/gl-infra/production/-/issues/5158


July 13, 2021 22:12 UTC

INVESTIGATING

Our engineers continue to investigate the root cause of the degraded performance. For more information please see https://gitlab.com/gitlab-com/gl-infra/production/-/issues/5158


July 13, 2021 21:56 UTC

INVESTIGATING

No material updates to report. We appreciate your patience as we continue to investigate the cause of the degraded performance. More details in: https://gitlab.com/gitlab-com/gl-infra/production/-/issues/5158


July 13, 2021 21:41 UTC

INVESTIGATING

We are continuing to investigate delays in Background Processing. For details, please see https://gitlab.com/gitlab-com/gl-infra/production/-/issues/5158


July 13, 2021 21:26 UTC

INVESTIGATING

We appreciate your patience as we continue to investigate the root cause of the degraded performance. At this time, pipeline processing and merge requests are still affected. More details in: https://gitlab.com/gitlab-com/gl-infra/production/-/issues/5158


July 13, 2021 21:08 UTC

INVESTIGATING

We continue to see degraded performance in background processing. Our engineers are still investigating the root cause. More details in: https://gitlab.com/gitlab-com/gl-infra/production/-/issues/5158


July 13, 2021 20:51 UTC

INVESTIGATING

Our team continues to investigate the cause of the degraded performance. We appreciate your patience as we continue to investigate. For more information please see https://gitlab.com/gitlab-com/gl-infra/production/-/issues/5158


July 13, 2021 20:33 UTC

INVESTIGATING

GitLab.com is currently experiencing delays in background jobs. This has affected all runners picking up jobs. We expect things to be cleared up in the next 15 minutes. More details in https://gitlab.com/gitlab-com/gl-infra/production/-/issues/5158