Header Image
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.
Errors on GitLab.com registryDegraded Performance

Incident Status

Degraded Performance

Components

Registry

Locations

Google Compute Engine



March 13, 2019 16:13 UTC
[Monitoring] After recovery of the GCS incident today, if you are still getting an error trying to pull an image from Registry please try rebuilding and pushing it first. This has resolved the error for images we have tried with. For details: https://gitlab.com/gitlab-com/gl-infra/production/issues/723

March 13, 2019 06:04 UTC
[Monitoring] Latest update from GCS is that they are gradually recovering. Our alarms are cleared for now, but we will continue to monitor our metrics closely.

March 13, 2019 04:41 UTC
[Identified] We are continuing to monitor our errors on the GitLab.com registry and expect to hear an update on the GCS issues at 21:45 Pacific.

March 13, 2019 03:46 UTC
[Identified] We have created https://gitlab.com/gitlab-com/gl-infra/production/issues/723 to track the registry problems. At the moment, this appears related to https://status.cloud.google.com/incident/storage/19002.

March 13, 2019 03:38 UTC
[Investigating] We are investigating errors for the registry on GitLab.com

Website




Operational

API




Operational

CI/CD




Operational

Registry




Operational

Background Processing




Operational

Pages




Operational

Support Services




Operational

packages.gitlab.com




Operational

External Services

AWS Route 53

AWS S3

Dyn

Fastly

Mailgun