All Systems Operational

Updated a few seconds ago

Back to current status

Status History

Filter: Container Registry (Clear)



August 2022

GitLab.com slow to respond

August 26, 2022 06:21 UTC

GitLab.com slow to respondDegraded Performance

Incident Status

Degraded Performance


Components

Website, API, Git Operations, Container Registry, GitLab Pages, CI/CD - Hosted runners on Linux, CI/CD - Hosted runners on Windows, CI/CD - Hosted runners for GitLab community contributions, SAML SSO - GitLab SaaS, Background Processing, GitLab Customers Portal, Support Services, packages.gitlab.com, version.gitlab.com, forum.gitlab.com, Canary


Locations

Google Compute Engine, Digital Ocean, Zendesk, AWS




August 26, 2022 06:21 UTC
[Resolved] We are no longer seeing connectivity issues for GitLab.com after a period of monitoring. We therefore believe that this incident has been resolved. Details in : gitlab.com/gitlab-com/gl-infra/production/-/issues/7656

August 26, 2022 05:08 UTC
[Monitoring] All the services seems to have recovered. We will continue to monitor the performance and provide the updates here. More information on the root cause can be found here: gitlab.com/gitlab-com/gl-infra/production/-/issues/7656

August 26, 2022 04:57 UTC
[Investigating] We are still investigating the root cause of this issue. More details here: gitlab.com/gitlab-com/gl-infra/production/-/issues/7656

August 26, 2022 04:55 UTC
[Investigating] We are noticing some slow response issues with GitLab.com.

Unexpected locked projects warning

August 23, 2022 21:39 UTC

Incident Status

Service Disruption


Components

Website, API, Git Operations, Container Registry, GitLab Pages


Locations

Google Compute Engine




August 23, 2022 21:39 UTC
[Resolved] This incident is now considered fully resolved and will be closed. Thanks for your patience! Please see the production issue for full details: gitlab.com/gitlab-com/gl-infra/production/-/issues/7638

August 23, 2022 21:06 UTC
[Monitoring] This incident has been resolved. We'll be monitoring for 30 minutes prior to fully closing the incident. See the production issue for details: gitlab.com/gitlab-com/gl-infra/production/-/issues/7638

August 23, 2022 19:05 UTC
[Monitoring] GitLab.com has been operational since we've mitigated the issue. Users should not be impacted at this time. We're currently working towards a full resolution. Details in gitlab.com/gitlab-com/gl-infra/production/-/issues/7638

August 23, 2022 18:39 UTC
[Identified] We'll be providing less updates until there is a material update to report on. Our team is still working towards a resolution. More details in gitlab.com/gitlab-com/gl-infra/production/-/issues/7638

August 23, 2022 17:53 UTC
[Identified] No material updates. Our team is still working on a full resolution to this issue. Details in gitlab.com/gitlab-com/gl-infra/production/-/issues/7638

August 23, 2022 17:20 UTC
[Identified] We're still working towards a full resolution on this issue. Users should not see any impact at this time. gitlab.com/gitlab-com/gl-infra/production/-/issues/7638

August 23, 2022 16:43 UTC
[Identified] We've identified the root cause and we're working towards a full resolution for this issue. Details in the production issue: gitlab.com/gitlab-com/gl-infra/production/-/issues/7638

August 23, 2022 16:15 UTC
[Investigating] While projects should be unblocked, our team is still investigating the root cause. We’ll be moving to a longer cadence for updates during our investigation. More details in gitlab.com/gitlab-com/gl-infra/production/-/issues/7638

August 23, 2022 15:49 UTC
[Investigating] Our team has implemented a temporary fix to this issue. Projects that were previously locked should now be unlocked. Our team is continuing to investigate the root cause. More details are available in our production issue: gitlab.com/gitlab-com/gl-infra/production/-/issues/7638

August 23, 2022 15:28 UTC
[Investigating] Our investigation is still ongoing. More details are available in our production issue: gitlab.com/gitlab-com/gl-infra/production/-/issues/7638

August 23, 2022 15:12 UTC
[Investigating] Our team is continuing to investigate this issue. More details are available in our production issue: gitlab.com/gitlab-com/gl-infra/production/-/issues/7638

August 23, 2022 15:00 UTC
[Investigating] We are still investigating the root cause of this issue. More details here: gitlab.com/gitlab-com/gl-infra/production/-/issues/7638

August 23, 2022 14:35 UTC
[Investigating] We are currently investigating an issue with projects displaying a "locked project" warning. More details here: gitlab.com/gitlab-com/gl-infra/production/-/issues/7638

July 2022

Scheduled GitLab.com production database maintenance

July 2, 2022 08:51 UTC

Description

We will be performing maintenance on GitLab.com's production database which is anticipated to include a service downtime of up to 120 minutes between Saturday, 2022-07-02, 06:00am to 08:00am UTC. During this time users will experience complete service disruption. Improving the performance and reliability of GitLab.com has always been a top priority for GitLab. While we continuously make iterative improvements to GitLab and our production architecture, we anticipate making a larger change to improve the scalability and reliability of GitLab.com: We are splitting our single PostgreSQL database into a main and a ci database. You can read more about this change in our blog: about.gitlab.com/blog/2022/06/02/splitting-database-into-main-and-ci


Components

Website, API, Git Operations, Container Registry, GitLab Pages, CI/CD - Hosted runners on Linux, CI/CD - Hosted runners on Windows, CI/CD - Hosted runners for GitLab community contributions, SAML SSO - GitLab SaaS, Background Processing, GitLab Customers Portal


Locations

Google Compute Engine


Schedule

July 2, 2022 05:00 - July 2, 2022 09:00 UTC



July 2, 2022 08:51 UTC
[Update] GitLab.com's database layer maintenance upgrade is complete now, and we're back up and running. We'll be monitoring the platform to ensure all systems are functioning correctly. Thank you for your patience.

July 2, 2022 07:43 UTC
[Update] GitLab.com planned maintenance for the database layer is almost complete. The site is back up and running although we're continuing to verify that all systems are functioning correctly. Thank you for your patience.

July 2, 2022 06:00 UTC
[Update] GitLab.com is now shutting down for planned maintenance for database layer improvements for the next 2 hours. See you on the other side!

July 2, 2022 05:00 UTC
[Update] GitLab.com will undergo maintenance in 1 hour. Please note that any CI jobs that start before the maintenance window but complete during the window period (up to 2 hours) will fail and may need to be started again.

July 1, 2022 05:45 UTC
[Update] Reminder: Tomorrow we will be undergoing scheduled maintenance to our database layer. We expect the GitLab.com site to be unavailable for up to 2 hours. Starting time: 2022-07-02 06:00 UTC.

June 29, 2022 10:01 UTC
[Update] We wanted to clarify that this scheduled maintenance will also impact Pages hosted with GitLab Pages on GitLab.com. Pages will be unavailable for up to 2 hours starting from 2022-07-02 06:00 UTC. We apologize in advance for any inconvenience this may cause.

June 29, 2022 05:50 UTC
[Update] In 3 days time, we will be undergoing some scheduled maintenance to our database layer so we expect the GitLab.com site to be unavailable for up to 2 hours starting from 2022-07-02 06:00 UTC. We apologize in advance for any inconvenience this may cause.

June 2022

Spike in error rate on gitlab.com

June 23, 2022 07:19 UTC

Incident Status

Operational


Components

Website, API, Git Operations, Container Registry, GitLab Pages, CI/CD - Hosted runners on Linux, CI/CD - Hosted runners on Windows, CI/CD - Hosted runners for GitLab community contributions, SAML SSO - GitLab SaaS, Background Processing, GitLab Customers Portal, Support Services, packages.gitlab.com, version.gitlab.com, forum.gitlab.com, Canary


Locations

Google Compute Engine, Digital Ocean, Zendesk, AWS




June 23, 2022 07:19 UTC
[Resolved] Error rates have returned to normal levels. Follow-up discussion and actions are being discussed here: gitlab.com/gitlab-com/gl-infra/production/-/issues/7310

June 23, 2022 06:46 UTC
[Monitoring] We are investigating a brief spike in errors that lasted about 20 minutes, we are monitoring the recovery and will put more detail in gitlab.com/gitlab-com/gl-infra/production/-/issues/7310

Connectivity issues for GitLab.com

June 21, 2022 08:43 UTC

Incident Status

Service Disruption


Components

Website, API, Git Operations, Container Registry, GitLab Pages, CI/CD - Hosted runners on Linux, CI/CD - Hosted runners on Windows, CI/CD - Hosted runners for GitLab community contributions, SAML SSO - GitLab SaaS, Background Processing, GitLab Customers Portal, Support Services, packages.gitlab.com, version.gitlab.com, forum.gitlab.com, Canary


Locations

Google Compute Engine, Digital Ocean, Zendesk, AWS




June 21, 2022 08:43 UTC
[Resolved] We are no longer seeing connectivity issues for GitLab.com after a period of monitoring. We therefore believe that this incident has been resolved. Details in: gitlab.com/gitlab-com/gl-infra/production/-/issues/7288

June 21, 2022 08:00 UTC
[Monitoring] Services seem to be back to normal, and we continue monitoring. Details in: gitlab.com/gitlab-com/gl-infra/production/-/issues/7288

June 21, 2022 07:45 UTC
[Identified] We are seeing services slowly recovering and continue monitoring issues with our CDN provider.

June 21, 2022 07:22 UTC
[Identified] No material updates at this point. We are continuing to monitor issues with our CDN provider

June 21, 2022 07:02 UTC
[Identified] We are continuing to monitor connectivity issues from some regions due to connectivity problems from our CDN provider.

June 21, 2022 06:52 UTC
[Investigating] We are investigating connectivity issues for GitLab.com, this is affecting all services.

Gitlab.com is having slowness issues

June 15, 2022 23:28 UTC

Incident Status

Degraded Performance


Components

Website, API, Git Operations, Container Registry, GitLab Pages, CI/CD - Hosted runners on Linux, CI/CD - Hosted runners on Windows, CI/CD - Hosted runners for GitLab community contributions, SAML SSO - GitLab SaaS, Background Processing, GitLab Customers Portal, Support Services, packages.gitlab.com, version.gitlab.com, forum.gitlab.com, Canary


Locations

Google Compute Engine, Digital Ocean, Zendesk, AWS




June 15, 2022 23:28 UTC
[Resolved] We are no longer seeing performance issues on GitLab.com after a period of monitoring. We believe the incident has now been resolved. More details can be found here: gitlab.com/gitlab-com/gl-infra/production/-/issues/7258

June 15, 2022 23:12 UTC
[Identified] Our teams had identified the root cause of the slowness and are discussing preventive actions for it. Performance is back to normal.

June 15, 2022 22:53 UTC
[Investigating] Our teams detected a performance degradation for all components for GitLab.com, it appears this degradation is now stabilizing back to normal performance. We are still investigating.

June 15, 2022 22:36 UTC
[Investigating] Requests to GitLab.com are seeing elevated error rates and slowness, we are investigating.

April 2022

Elevated Error Rate for Registry on GitLab.com

April 30, 2022 01:18 UTC

Incident Status

Service Disruption


Components

Container Registry


Locations

Google Compute Engine




April 30, 2022 01:18 UTC
[Resolved] After a period of monitoring, error rates have remained stable. This incident has been marked as resolved. A full timeline is available in gitlab.com/gitlab-com/gl-infra/production/-/issues/6950

April 30, 2022 00:28 UTC
[Monitoring] We experienced an elevated rate of errors for Registry on GitLab.com for a short period of time. The service has automatically recovered but we are monitoring and investigating the cause. gitlab.com/gitlab-com/gl-infra/production/-/issues/6950

Elevated Error Rate on GitLab.com

April 28, 2022 07:37 UTC

Incident Status

Service Disruption


Components

Website, API, Git Operations, Container Registry, GitLab Pages, CI/CD - Hosted runners on Linux, CI/CD - Hosted runners on Windows, CI/CD - Hosted runners for GitLab community contributions, SAML SSO - GitLab SaaS, Background Processing, GitLab Customers Portal, Support Services, packages.gitlab.com, version.gitlab.com, forum.gitlab.com, Canary


Locations

Google Compute Engine, Digital Ocean, Zendesk, AWS




April 28, 2022 07:37 UTC
[Resolved] We transitioned this incident to resolved. Check the issue for more details: gitlab.com/gitlab-com/gl-infra/production/-/issues/6933

April 28, 2022 07:23 UTC
[Monitoring] We have identified the cause to this incident and do not anticipate any additional impacts at this time. We are continuing to monitor services as well as complete additional investigation. More details here: gitlab.com/gitlab-com/gl-infra/production/-/issues/6933

April 28, 2022 06:34 UTC
[Investigating] We are still investigating the root cause. The error rates on affected systems recovering, and we are monitoring to ensure that the issue does not recur.

April 28, 2022 06:12 UTC
[Investigating] We're investigating increased error rates across GitLab-com services, some users might be experiencing 500 errors intermittently, more info can be found in here: gitlab.com/gitlab-com/gl-infra/production/-/issues/6933

Elevated Error Rate on GitLab

April 26, 2022 02:26 UTC

Elevated Error Rate on GitLab Partial Service Disruption

Incident Status

Partial Service Disruption


Components

Website, API, Git Operations, Container Registry, GitLab Pages


Locations

Google Compute Engine




April 26, 2022 02:26 UTC
[Resolved] After a period of monitoring, error rates have remained stable. This incident has been marked as resolved. A full timeline is available in gitlab.com/gitlab-com/gl-infra/production/-/issues/6910

April 26, 2022 01:51 UTC
[Monitoring] We experienced an elevated rate of errors for gitlab.com for a short period of time. The service has automatically recovered but we are monitoring and investigating the cause. Details in gitlab.com/gitlab-com/gl-infra/production/-/issues/6910

March 2022

Gitlab.com Degraded Performance

March 14, 2022 20:43 UTC

Incident Status

Degraded Performance


Components

Website, API, Git Operations, Container Registry, GitLab Pages, CI/CD - Hosted runners on Linux, CI/CD - Hosted runners on Windows, CI/CD - Hosted runners for GitLab community contributions, SAML SSO - GitLab SaaS, Background Processing, Canary


Locations

Google Compute Engine




March 14, 2022 20:43 UTC
[Resolved] We can confirm that degraded services have recovered to expected levels and we have identified the steps required to mitigate the issue. To follow along or review the full timeline see: gitlab.com/gitlab-com/gl-infra/production/-/issues/6586. status.gitlab.com

March 14, 2022 18:42 UTC
[Monitoring] We have identified a root cause and mitigating steps have been performed. We are currently monitoring site performance. You can follow along with this issue here: gitlab.com/gitlab-com/gl-infra/production/-/issues/6586

March 14, 2022 18:18 UTC
[Identified] We are still continuing to investigate. You can follow along with this issue here: gitlab.com/gitlab-com/gl-infra/production/-/issues/6586

March 14, 2022 17:55 UTC
[Identified] We are seeing site performance return to expected levels, but we are currently investigating some async job issues. You can follow along with this issue here: gitlab.com/gitlab-com/gl-infra/production/-/issues/6586

March 14, 2022 17:25 UTC
[Investigating] We are currently seeing degraded performance for Gitlab.com and are investigating. We will update with an impact shortly.

February 2022

Performance degradation across multiple services

February 19, 2022 22:01 UTC

Incident Status

Degraded Performance


Components

API, Git Operations, Container Registry, GitLab Pages, Background Processing, Canary


Locations

Google Compute Engine




February 19, 2022 22:01 UTC
[Resolved] Mitigating updates have been applied and performance has returned to normal. Gitlab.com is fully operational.

February 19, 2022 21:46 UTC
[Monitoring] We have taken some mitigation steps and are seeing improvement in performance. We are continuing to monitor and investigate.

February 19, 2022 21:29 UTC
[Investigating] We’re currently investigating a performance degradation across multiple services. More information as we investigate in gitlab.com/gitlab-com/gl-infra/production/-/issues/6388

Performance degradation across multiple services

February 19, 2022 06:45 UTC

Incident Status

Degraded Performance


Components

API, Git Operations, Container Registry, GitLab Pages, Background Processing, Canary


Locations

Google Compute Engine




February 19, 2022 06:45 UTC
[Resolved] GitLab.com is currently fully operational

February 19, 2022 04:37 UTC
[Resolved] Mitigation steps have restored services. GitLab.com is currently fully operational.

February 19, 2022 04:14 UTC
[Monitoring] Mitigating updates have been applied and performance has been restored. We are continuing to monitor the situation.

February 19, 2022 04:09 UTC
[Monitoring] We have taken some mitigation steps and are seeing improvement in performance. We are continuing to monitor and investigate.

February 19, 2022 03:59 UTC
[Investigating] We’re currently investigating a performance degradation across multiple services. More information as we investigate in gitlab.com/gitlab-com/gl-infra/production/-/issues/6386

System Wide Outage

February 1, 2022 06:37 UTC

System Wide OutageService Disruption

Incident Status

Service Disruption


Components

Website, API, Git Operations, Container Registry, GitLab Pages, CI/CD - Hosted runners on Linux, CI/CD - Hosted runners on Windows, CI/CD - Hosted runners for GitLab community contributions, SAML SSO - GitLab SaaS, Background Processing


Locations

Google Compute Engine




February 1, 2022 06:37 UTC
[Resolved] We have transitioned this incident to Resolved. All services continue to be fully operational. We have some additional investigation and follow up pending, but no further impact or user action is expected at this time.

January 31, 2022 20:04 UTC
[Monitoring] Our team is currently investigating data integrity with our cloud provider. Further updates will be minimal but more information can be found in the production issue gitlab.com/gitlab-com/gl-infra/production/-/issues/6253

January 31, 2022 18:22 UTC
[Monitoring] We've confirmed the root cause with our cloud provider and expect to call the issue resolved shortly. Details in gitlab.com/gitlab-com/gl-infra/production/-/issues/6253

January 31, 2022 16:43 UTC
[Monitoring] Our team is continuing to investigate the root cause in gitlab.com/gitlab-com/gl-infra/production/-/issues/6253

January 31, 2022 16:12 UTC
[Monitoring] GitLab.com remains available and our team is investigating the root cause. For details see gitlab.com/gitlab-com/gl-infra/production/-/issues/6253

January 31, 2022 15:52 UTC
[Monitoring] GitLab.com is accessible again. The mitigation is in place, and we are continuing to work on restoring full capacity.

January 31, 2022 15:35 UTC
[Investigating] Our team is seeing some recovery on Gitlab.com. However, we are still investigating the issue as it is on-going.

January 31, 2022 15:22 UTC
[Investigating] GitLab.com is unavailable and users are getting 500 errors.

December 2021

GitLab.com production database reliability update

December 18, 2021 16:46 UTC

Description

During this maintenance we will be upgrading our GitLab.com production database to a minor version of PostgreSQL 12.9 to improve overall reliability. This maintenance will not require downtime and is not expected to otherwise impact performance or availability of GitLab.com functionality. We are providing notice of this work due to the critical nature of the database to our operations, even though we anticipate no impact.


Components

Website, API, Container Registry, GitLab Pages, CI/CD - Hosted runners on Linux, CI/CD - Hosted runners on Windows, CI/CD - Hosted runners for GitLab community contributions, SAML SSO - GitLab SaaS, Background Processing, Canary


Locations

Google Compute Engine


Schedule

December 18, 2021 15:00 - December 18, 2021 17:00 UTC



December 18, 2021 16:46 UTC
[Update] Maintenance work is now completed. The full anticipated work was not successfully completed, but no further changes will be executed today.

December 18, 2021 16:02 UTC
[Update] Maint Started 15:00 UTC

November 2021

Increased elevated error rates and latency

November 22, 2021 18:37 UTC

Incident Status

Partial Service Disruption


Components

Website, API, Git Operations, Container Registry


Locations

Google Compute Engine




November 22, 2021 18:37 UTC
[Resolved] We believe to have identified the reason for this performance slowness and performance has continued to be normal, more details provided here: gitlab.com/gitlab-com/gl-infra/production/-/issues/5952

November 22, 2021 17:42 UTC
[Monitoring] Operations should be returning to normal, we're currently monitoring recovery, more details provided here: gitlab.com/gitlab-com/gl-infra/production/-/issues/5952

November 22, 2021 17:30 UTC
[Investigating] Rollback has completed and traffic blocks removed, we've seen a return to normal traffic, currently confirming resolution, more details provided here: gitlab.com/gitlab-com/gl-infra/production/-/issues/5952

November 22, 2021 17:12 UTC
[Investigating] Rollback as a correct as a corrective action is currently 15-20 minutes to completion, more details provided here: gitlab.com/gitlab-com/gl-infra/production/-/issues/5952

November 22, 2021 17:01 UTC
[Investigating] Rollback as a correct as a corrective action is progressing currently, more details provided here: gitlab.com/gitlab-com/gl-infra/production/-/issues/5952

November 22, 2021 16:46 UTC
[Investigating] We're currently performing a rollback as a correct as a corrective action, more details provided here: gitlab.com/gitlab-com/gl-infra/production/-/issues/5952

November 22, 2021 16:20 UTC
[Investigating] We are now taking further troubleshooting actions to mitigate the issue. More details here: gitlab.com/gitlab-com/gl-infra/production/-/issues/5952

November 22, 2021 15:32 UTC
[Investigating] Issues with some features including the API, git, container registry and merge button are still under investigation. gitlab.com/gitlab-com/gl-infra/production/-/issues/5952

November 22, 2021 15:00 UTC
[Investigating] Mitigated some impact but are still seeing some issues with some features including the API, git, container registry and merge button. gitlab.com/gitlab-com/gl-infra/production/-/issues/5952

November 22, 2021 14:28 UTC
[Investigating] We have mitigated some of the impact but are still seeing some issues with some features including the merge button. gitlab.com/gitlab-com/gl-infra/production/-/issues/5952

November 22, 2021 14:16 UTC
[Investigating] Site wide increased elevated error rates and latency. More details here: gitlab.com/gitlab-com/gl-infra/production/-/issues/5952

September 2021

Increased error rates across all GitLab services

September 12, 2021 21:48 UTC

Incident Status

Service Disruption


Components

Website, API, Git Operations, Container Registry, GitLab Pages, CI/CD - Hosted runners on Linux, CI/CD - Hosted runners on Windows, CI/CD - Hosted runners for GitLab community contributions, SAML SSO - GitLab SaaS, Background Processing, GitLab Customers Portal, Support Services, packages.gitlab.com, version.gitlab.com, forum.gitlab.com, Canary


Locations

Google Compute Engine, Azure, Digital Ocean, Zendesk, AWS




September 12, 2021 21:48 UTC
[Resolved] After investigation we determined that the elevated error rates were caused by database connection saturation; further details will be in this issue: gitlab.com/gitlab-com/gl-infra/production/-/issues/5514

September 12, 2021 21:23 UTC
[Monitoring] GitLab performance and error rates have returned to normal; we are investigating the root cause to understand the likelyhood it will reoccur.

September 12, 2021 21:04 UTC
[Investigating] We are investigating slow response times and increased error rates across all GitLab services. Incident: gitlab.com/gitlab-com/gl-infra/production/-/issues/5514

August 2021

Elevated error rates on GitLab.com

August 11, 2021 17:51 UTC

Elevated error rates on GitLab.comPartial Service Disruption

Incident Status

Partial Service Disruption


Components

Website, API, Git Operations, Container Registry, GitLab Pages, CI/CD - Hosted runners on Linux, CI/CD - Hosted runners on Windows, CI/CD - Hosted runners for GitLab community contributions, SAML SSO - GitLab SaaS, Background Processing, GitLab Customers Portal, Support Services, packages.gitlab.com, version.gitlab.com, forum.gitlab.com, Canary


Locations

Google Compute Engine, Azure, Digital Ocean, Zendesk, AWS




August 11, 2021 17:51 UTC
[Resolved] As GitLab.com is operating normally, we'll now be marking this incident as resolved. Further investigation efforts and details surrounding the issue can be found in: gitlab.com/gitlab-com/gl-infra/production/-/issues/5333

August 11, 2021 17:44 UTC
[Investigating] No material updates to report - our investigation is still ongoing. Details in: gitlab.com/gitlab-com/gl-infra/production/-/issues/5333

August 11, 2021 17:27 UTC
[Investigating] All GitLab.com services are operating normally, but our investigation into the cause of the errors continues. Details in: gitlab.com/gitlab-com/gl-infra/production/-/issues/5333

August 11, 2021 17:18 UTC
[Investigating] At 17:04 UTC, there was a 5 minute elevated error ratio event for all GitLab.com services. It has recovered, but we are investigating. Details in: gitlab.com/gitlab-com/gl-infra/production/-/issues/5333

Increased error rates across all services

August 10, 2021 10:39 UTC

Incident Status

Partial Service Disruption


Components

Website, API, Git Operations, Container Registry, GitLab Pages, CI/CD - Hosted runners on Linux, CI/CD - Hosted runners on Windows, CI/CD - Hosted runners for GitLab community contributions, SAML SSO - GitLab SaaS, Background Processing, GitLab Customers Portal, Support Services, packages.gitlab.com, version.gitlab.com, forum.gitlab.com, Canary


Locations

Google Compute Engine, Azure, Digital Ocean, Zendesk, AWS




August 10, 2021 10:39 UTC
[Resolved] The issue has been resolved, and we can confirm that all services on GitLab.com are fully operational. A full timeline of this incident and more details are available in gitlab.com/gitlab-com/gl-infra/production/-/issues/5324

August 10, 2021 10:05 UTC
[Monitoring] We are back to normal error rates across all services. We keep monitoring the situation. Refer to gitlab.com/gitlab-com/gl-infra/production/-/issues/5324 for more updates.

August 10, 2021 09:52 UTC
[Investigating] We are investigating increased error rates across all services, see gitlab.com/gitlab-com/gl-infra/production/-/issues/5324 for more details

GitLab performance degraded

August 6, 2021 12:48 UTC

Incident Status

Operational


Components

Website, API, Git Operations, Container Registry, GitLab Pages, CI/CD - Hosted runners on Linux, CI/CD - Hosted runners on Windows, CI/CD - Hosted runners for GitLab community contributions, Background Processing, GitLab Customers Portal, Support Services, packages.gitlab.com, version.gitlab.com, forum.gitlab.com, Canary


Locations

Google Compute Engine, Azure, Digital Ocean, Zendesk, AWS




August 6, 2021 12:48 UTC
[Resolved] From 12:05 - 12:15 UTC, we saw a system degradation across all of our components, which seems to have recovered at the moment. Our engineers are investigating. Further details are available in: gitlab.com/gitlab-com/gl-infra/production/-/issues/5306

July 2021

GitLab pages is down

July 21, 2021 09:32 UTC

Incident Status

Operational


Components

Container Registry, GitLab Pages


Locations

Google Compute Engine




July 21, 2021 09:32 UTC
[Resolved] GitLab Pages (as well as docs.gitlab.com) and GitLab Registry are back to an operational state. We’ll continue the root cause analysis over at gitlab.com/gitlab-com/gl-infra/production/-/issues/5196

July 21, 2021 09:01 UTC
[Identified] GitLab Pages and Registry are operational. We’ll continue to investigate the root cause of this incident at gitlab.com/gitlab-com/gl-infra/production/-/issues/5196

July 21, 2021 08:49 UTC
[Identified] We’ve identified a mitigation path and are actively applying this to affected services. GitLab Pages and Registry should now be at least partially available. During mitigation, the affected services (GitLab Services, docs.gitlab.com and GitLab Registry) will be unstable. Investigation is ongoing at gitlab.com/gitlab-com/gl-infra/production/-/issues/5196

July 21, 2021 08:43 UTC
[Identified] We’ve identified a mitigation path and are actively applying this to affected services. GitLab Registry should now be at least partially available. During mitigation, the affected services (GitLab Services, docs.gitlab.com and GitLab Registry) will be unstable. Investigation is ongoing at gitlab.com/gitlab-com/gl-infra/production/-/issues/5196

July 21, 2021 08:29 UTC
[Investigating] The investigation of the load balancer issue is still ongoing, and we’ve engaged support from a third-party vendor in investigating. The affected services (GitLab Services, docs.gitlab.com and GitLab Registry) remain unavailable for the time being. Investigation is ongoing at gitlab.com/gitlab-com/gl-infra/production/-/issues/5196

July 21, 2021 08:01 UTC
[Investigating] We’re still investigating the load balancer issue. The affected services (GitLab Services, docs.gitlab.com and GitLab Registry) remain unavailable for the time being. Investigation is ongoing at gitlab.com/gitlab-com/gl-infra/production/-/issues/5196

July 21, 2021 07:34 UTC
[Investigating] Specific load-balanced services (GitLab Pages, GitLab Registry and docs.gitlab.com) are currently unavailable. We are looking into the cause and determining steps to mitigate. Investigation is ongoing at gitlab.com/gitlab-com/gl-infra/production/-/issues/5196

July 21, 2021 07:14 UTC
[Investigating] GitLab Pages is currently unavailable and the cause is currently under investigation at gitlab.com/gitlab-com/gl-infra/production/-/issues/5196 and we will post further updates.





Back to current status