Active Incident

Updated a few seconds ago

We continuously monitor gitlab.com and all its services. If there are any performance or service interruptions, an update will be posted here.

Incident Status

Operational

Components

CI/CD

Locations

Google Compute Engine



February 25, 2021 21:10 CET
February 25, 2021 20:10 UTC
[Monitoring] We've implemented a change that should mitigate this issue moving forward. We'll continue to monitor the situation and provide further updates here as needed. More details can be found here: https://gitlab.com/gitlab-com/gl-infra/production/-/issues/3800

February 25, 2021 19:44 CET
February 25, 2021 18:44 UTC
[Monitoring] Shared Runners are processing jobs nominally. We're now working to implement changes that will mitigate long job queue duration in the future - details in: https://gitlab.com/gitlab-com/gl-infra/production/-/issues/3800

February 25, 2021 19:03 CET
February 25, 2021 18:03 UTC
[Identified] We've identified the cause of the growing job queues, and jobs should now start being picked up in a timely manner. We're still investigating ways this can be mitigated in the future - details in: https://gitlab.com/gitlab-com/gl-infra/production/-/issues/3800

February 25, 2021 18:31 CET
February 25, 2021 17:31 UTC
[Investigating] We're currently investigating performance issues with our Shared Runners. Users may see their jobs in a pending state for an extended period of time. Details in: https://gitlab.com/gitlab-com/gl-infra/production/-/issues/3800

Website




Operational

API




Operational

Git (ssh and https)




Operational

Pages




Operational

Registry




Operational

CI/CD




Operational

Background Processing




Operational

Support Services




Operational

packages.gitlab.com




Operational

customers.gitlab.com




Operational

version.gitlab.com




Operational

forum.gitlab.com




Operational

Windows Runners (beta)




Operational

Canary




Operational

dashboards.gitlab.com




Operational

External Services