All Systems Operational

Updated a few seconds ago

Back to current status

Status History

Filter: GitLab Customers Portal (Clear)



November 2022

GitLab Customers Portal Unavailable

November 28, 2022 01:33 UTC

Incident Status

Service Disruption


Components

GitLab Customers Portal


Locations

Google Compute Engine




November 28, 2022 01:33 UTC
[Resolved] This incident has been resolved and Customers Portal is now operational. More information can be found in gitlab.com/gitlab-com/gl-infra/production/-/issues/8088

November 28, 2022 00:46 UTC
[Monitoring] We have restarted the service and are now monitoring Customers Portal for the next hour before marking the incident as resolved. More details can be found in gitlab.com/gitlab-com/gl-infra/production/-/issues/8088

November 28, 2022 00:11 UTC
[Identified] We have identified a problem with the GitLab Customers Portal. More details are available in gitlab.com/gitlab-com/gl-infra/production/-/issues/8088.

Customers Portal Database Migration

November 26, 2022 15:58 UTC

Description

We plan to migrate the database behind the GitLab Customers Portal from a VM to GCP CloudSQL, for better manageability and maintenance. The Customers Portal will be offline for approximately one hour during the maintenance window with an additional 30 minute buffer added in order to verify stability.


Components

GitLab Customers Portal


Locations

Google Compute Engine


Schedule

November 26, 2022 14:30 - November 26, 2022 16:00 UTC



November 26, 2022 15:58 UTC
[Update] The scheduled Customers Portal Database Migration has been completed.

November 26, 2022 15:58 UTC
[Update] The scheduled Customers Portal Database Migration has been completed.

Customers Portal Downtime for 3rd Party Update

November 13, 2022 03:49 UTC

Description

The Customers Portal will be offline for approximately one hour during the maintenance window while our third party subscription management vendor performs scheduled maintenance of their service. We're taking the Customers Portal offline during this period to prevent customers from experiencing any errors while using it that would be caused by our vendor performing maintenance to their own service.


Components

GitLab Customers Portal


Locations

Google Compute Engine


Schedule

November 13, 2022 03:00 - November 13, 2022 04:00 UTC



November 13, 2022 03:49 UTC
[Update] Maintenance has been completed successfully. We are monitoring traffic as a precaution, however everything appears to be back to normal.

November 13, 2022 03:26 UTC
[Update] Maintenance has been completed successfully. We are monitoring traffic as a precaution, however everything appears to be back to normal.

Customers Portal Database Migration

November 12, 2022 15:47 UTC

Description

We plan to migrate the database behind the GitLab Customers Portal from a VM to GCP CloudSQL, for better manageability and maintenance. The Customers Portal will be offline for approximately one hour during the maintenance window with an additional 30 minute buffer added in order to verify stability.


Components

GitLab Customers Portal


Locations

Google Compute Engine


Schedule

November 12, 2022 12:00 - November 12, 2022 13:30 UTC



November 12, 2022 15:47 UTC
[Update] This Maintenance has been canceled for now. It will be rescheduled for a future date.

September 2022

GitLab.com maintenance 2022-09-03 11:00 to 14:00 UTC

September 3, 2022 14:16 UTC

Description

We will be performing maintenance on GitLab.com's production database which is anticipated to include a service downtime of up to 180 minutes between 11:00am to 2:00pm UTC on Saturday 2022-09-03. 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: performing necessary Operating System maintenance to our database clusters. You can read more about this change in our blog: about.gitlab.com/blog/2022/08/12/upgrading-database-os


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, Canary


Locations

Google Compute Engine


Schedule

September 3, 2022 11:00 - September 3, 2022 14:00 UTC



September 3, 2022 14:16 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.

September 3, 2022 14:13 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.

September 3, 2022 13:55 UTC
[Update] We are still performing tests to ensure full functionality of the gitlab.com site before bringing it up. Expect full functionality of gitlab.com in about 30mins

September 3, 2022 10:59 UTC
[Update] GitLab.com is now shutting down for planned maintenance to our database layer for the next 3 hours. See you on the other side! More details in about.gitlab.com/blog/2022/08/12/upgrading-database-os

August 31, 2022 16:00 UTC
[Update] Reminder: We will be performing maintenance on GitLab.com's production database which is anticipated to include a complete service downtime of up to 180 minutes between 11:00am to 2:00pm UTC on Saturday 2022-09-03. You can read more in about.gitlab.com/blog/2022/08/12/upgrading-database-os

August 2022

customers.gitlab.com is Unavailable

August 31, 2022 15:04 UTC

Incident Status

Service Disruption


Components

GitLab Customers Portal


Locations

Google Compute Engine




August 31, 2022 15:04 UTC
[Resolved] This incident has been resolved and customers.gitlab.com is now operational. More information can be found in gitlab.com/gitlab-com/gl-infra/production/-/issues/7670.

August 31, 2022 14:10 UTC
[Monitoring] We have mitigated the incident by restarting the customers.gitlab.com node. The service is now back online, and we are monitoring it. We are still investigating the root cause. For more details read incident issue: gitlab.com/gitlab-com/gl-infra/production/-/issues/7670

August 31, 2022 14:00 UTC
[Investigating] The incident is ongoing. We are still investigating reasons of customers.gitlab.com unavailability. For more details, review the incident issue at gitlab.com/gitlab-com/gl-infra/production/-/issues/7670

August 31, 2022 13:50 UTC
[Investigating] We are currently investigating issues with customers.gitlab.com. More details about this incident can be found in issue gitlab.com/gitlab-com/gl-infra/production/-/issues/7670

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.

Intermittent service disruption on customers.gitlab.com

August 12, 2022 20:30 UTC

Incident Status

Service Disruption


Components

GitLab Customers Portal


Locations

Google Compute Engine




August 12, 2022 20:30 UTC
[Resolved] After monitoring we've found that customers.gitlab.com production instance solution has resolved this issue. We will follow-up on this incident with a post-mortem review in the future.

August 12, 2022 20:08 UTC
[Monitoring] We've successfully deployed this solution for the customers.gitlab.com production instance. Now we are monitoring that this solution allows customers.gitlab.com to remain stable as expected.

August 12, 2022 19:57 UTC
[Identified] We're in process of deploying this solution for the customers.gitlab.com production instance. We expect ~10 minutes of production downtime. Once completed we will begin monitoring it's success toward resolution.

August 12, 2022 19:41 UTC
[Identified] We're now working to deploy this solution for customers.gitlab.com next. Production stability remains stable but may be intermittent until this solution is deployed to production. We're working to deploy this as soon as possible. We expect ~10 minutes of production downtime.

August 12, 2022 19:30 UTC
[Identified] We're now working to deploy this solution for customers.gitlab.com next. Production stability may be intermittent until deployed to production. We will create a maintenance issue for it's deployment to production. We expect ~10 minutes of production downtime.

August 12, 2022 19:17 UTC
[Identified] We've deployed this solution in customer.gitlab.com staging environment successfully. Production stability may be intermittent until deployed to production. We will create a maintenance issue for it's deployment to production. We expect ~10 minutes of production downtime.

August 12, 2022 19:05 UTC
[Identified] We're begun deployment of this solution in customer.gitlab.com staging environment now. Stability has returned but we could continue to see intermittent issues until our solution is deployed to production. We will create a maintenance issue for it's deployment to production.

August 12, 2022 18:53 UTC
[Identified] We're still testing this solution in customer.gitlab.com staging environment now. Stability has returned but we could continue to see intermittent issues until our solution is deployed to production. We will create a maintenance issue for it's deployment to production.

August 12, 2022 18:38 UTC
[Investigating] We're still testing a solution in customer.gitlab.com staging environment. Once verified successful we will deploy it to customers.gitlab.com production as soon as possible. A scheduled maintenance for customers.gitlab.com production will be created when performed.

August 12, 2022 18:23 UTC
[Investigating] We're in the process of testing our intermediate solution in staging and will deploy it to customers.gitlab.com as soon as possible. We expect a brief ~10 minutes downtime when we apply the change in production. Intermittent downtime has subsided but it still present.

August 12, 2022 18:09 UTC
[Investigating] We're working to apply an intermediate solution for the recent service disruption on customers.gitlab.com as we continue investigating. We expect a brief ~10 minutes downtime while we apply the change.

August 12, 2022 17:55 UTC
[Investigating] We've identified more details for our continuing investigation to identify root cause for customers.gitlab.com intermittent responsiveness. We're working to identify root cause and solutions. Intermittent service disruption still may continue as we continue investigating.

August 12, 2022 17:43 UTC
[Investigating] We're continuing our investigation to identify root cause for customers.gitlab.com intermittent responsiveness. Intermittent service disruption still may continue as we continue investigating.

August 12, 2022 17:33 UTC
[Investigating] We're seeing unresponsiveness subside for customers.gitlab.com and are still continuing to monitor and investigate. Intermittent service disruption still may continue as we continue investigating.

August 12, 2022 17:20 UTC
[Investigating] customers.gitlab.com was unresponsive for a short time. We may see further intermittent service disruption as we investigate.

Degraded Performance on the GitLab Customer Portal

August 5, 2022 01:26 UTC

Incident Status

Degraded Performance


Components

GitLab Customers Portal


Locations

Google Compute Engine




August 5, 2022 01:26 UTC
[Resolved] The issues with our 3rd party API provider has been addressed and they are monitoring to ensure the problem does not recur. Customers Portal is now fully operational. Further Details in gitlab.com/gitlab-com/gl-infra/production/-/issues/7550

August 4, 2022 21:14 UTC
[Monitoring] We are continuing to monitor the status of our 3rd-party API provider for the Customer Portal in order to ensure its stability. Details in gitlab.com/gitlab-com/gl-infra/production/-/issues/7550.

August 4, 2022 19:00 UTC
[Monitoring] We've been notified by the 3rd-party API that a fix for the issue has been applied and they are monitoring to ensure the problem does not recur. The Customer Portal is currently operational. Details in gitlab.com/gitlab-com/gl-infra/production/-/issues/7550.

August 4, 2022 18:21 UTC
[Identified] The Customers Portal (customers.gitlab.com) is experiencing intermittent 503 errors due to a partial outage on a 3rd-party API. Details in gitlab.com/gitlab-com/gl-infra/production/-/issues/7550.

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.

May 2022

Maintenance on Customers Portal and Billing page on GitLab.com

May 20, 2022 20:48 UTC

Description

Due to maintenance in one of our 3rd-party APIs, the Customers Portal and the Billing page on GitLab.com will be unavailable from 13:00 UTC to 21:00 UTC on 2022-05-20. We aim to restore the service as soon as possible. You can find more information in this link: gitlab.com/gitlab-com/business-technology/enterprise-apps/intake/-/issues/616


Components

GitLab Customers Portal


Locations

Google Compute Engine


Schedule

May 20, 2022 13:00 - May 20, 2022 21:00 UTC



May 20, 2022 20:48 UTC
[Update]

May 20, 2022 20:48 UTC
[Update] The maintenance to one of our 3rd-party APIs is complete and the Customers Portal and the Billing page on GitLab.com are now available.

May 20, 2022 13:00 UTC
[Update] Scheduled maintenance is starting.

April 2022

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

customers.gitlab.com outage

April 11, 2022 02:35 UTC

customers.gitlab.com outageService Disruption

Incident Status

Service Disruption


Components

GitLab Customers Portal


Locations

Google Compute Engine




April 11, 2022 02:35 UTC
[Resolved] customers.gitlab.com is back on line after a brief outage. Further information about this: gitlab.com/gitlab-com/gl-infra/production/-/issues/6803.

April 11, 2022 02:10 UTC
[Investigating] customers.gitlab.com is currently down and will be affecting new purchases. Investigation is underway in: gitlab.com/gitlab-com/gl-infra/production/-/issues/6803

March 2022

Issues when purchasing with VISA branded credit cards

March 31, 2022 14:34 UTC

Incident Status

Partial Service Disruption


Components

Website, GitLab Customers Portal


Locations

Google Compute Engine




March 31, 2022 14:34 UTC
[Resolved] Note that if you're still seeing a failure when attempting to pay with a Visa card, you may need to call your bank to confirm or allow the transaction.

March 31, 2022 14:14 UTC
[Resolved] We have now completed our work to mitigate the problem and can confirm that payments with Visa cards are now going through successfully. Huge thanks to our vendors who helped us troubleshoot and fix the issue.

March 30, 2022 20:51 UTC
[Identified] Work continues on mitigating the root cause with Visa and other third party vendors. The workaround is still to use a card from another issuer. The next update will be in 12-24 hours unless new information becomes available sooner.

March 29, 2022 18:23 UTC
[Identified] GitLab team members continue to work with Visa and other vendors to address payment failures with newly added Visa cards. The best workaround is to use a card from another issuer. The next update will be in 12-24 hours unless new information becomes available sooner.

March 28, 2022 23:16 UTC
[Identified] The title of this incident has been updated to better reflect the problem. GitLab team members and third party vendors continue to work together to resolve the underlying issue. The next update will be in 12-24 hours unless new information becomes available.

March 28, 2022 21:06 UTC
[Identified] We have narrowed the failures to Visa cards not used for prior GItLab purchases. We continue to engage vendors for further assistance, and in the meantime a workaround is to use a card from another issuer.

March 28, 2022 17:44 UTC
[Investigating] No material updates, we are still working with our third party vendors to troubleshoot the payment issues. The issue seems isolated to Visa cards, using a card from another issuer may allow your purchase to be completed.

March 28, 2022 15:44 UTC
[Investigating] Investigation into the payment issues continues. Additional GitLab team members have been engaged and we are contacting third party vendors for further assistance.

March 28, 2022 14:38 UTC
[Investigating] No material updates to report at this point. We're actively engaging more team members.

March 28, 2022 13:09 UTC
[Investigating] We continue investigating the payments issues. We suspect that in addition to CI/CD minutes purchase, the incident affects the ability to renew subscriptions and verify identity with VISA cards. We'll keep you posted.

March 28, 2022 10:53 UTC
[Investigating] No material updates at the moment. We are still investigating the payment issues. We are going to provide further update in an hour.

March 28, 2022 09:47 UTC
[Investigating] It seems like only payments with VISA cards are affected by this issue. In the meantime, please use a different card to purchase CI/CD minutes if you can. We continue with investigation.

March 28, 2022 09:18 UTC
[Investigating] We are receiving reports of issues during payment processing when buying CI/CD minutes. We are investigating it and will keep you updated on our progress.

February 2022

customers.gitlab.com brief outage

February 23, 2022 16:38 UTC

Incident Status

Operational


Components

GitLab Customers Portal


Locations

Google Compute Engine




February 23, 2022 16:38 UTC
[Resolved] customers.gitlab.com is operating normally and we are resolving this incident. Details here: gitlab.com/gitlab-com/gl-infra/production/-/issues/6413

February 23, 2022 13:26 UTC
[Monitoring] customers.gitlab.com was briefly unavailable. We quickly identified and rectified the issue with further investigation happening here: gitlab.com/gitlab-com/gl-infra/production/-/issues/6413

Customers.gitlab.com maintenance

February 5, 2022 16:10 UTC

Description

The Customers Portal will be in maintenance mode on Saturday February 5th for 2 hours. We will be performing a server migration


Components

GitLab Customers Portal


Locations

Azure


Schedule

February 5, 2022 14:00 - February 5, 2022 16:00 UTC



February 5, 2022 16:10 UTC
[Update] customers.gitlab.com maintenance finished successfully. Thank you for your patience!

February 5, 2022 15:35 UTC
[Update] customers.gitlab.com maintenance is complete now. Site is back up, and we're continuing to verify that all systems are functioning correctly.

February 5, 2022 14:00 UTC
[Update] customers.gitlab.com planned maintenance is starting now. See you on the other side!

January 10, 2022 11:34 UTC
[Update] The maintenance taking place on the 5th of February from 14:00 UTC to 16:00 UTC will only affect the Customers Portal; customers.gitlab.com. All other GitLab services are expected to be functioning as usual.

January 10, 2022 09:07 UTC
[Update] We have decided to reschedule the server migration for February the 5th. The maintenance will start at 14:00 UTC and last for 2 hrs.

November 2021

Scheduled Maintenance on customers.gitlab.com

November 14, 2021 06:21 UTC

Description

customers.gitlab.com will be unavailable during the maintenance window due to a 3rd-party API set to maintenance mode. Customers won't be able to manage their subscriptions or purchase new ones.


Components

GitLab Customers Portal


Locations

Azure


Schedule

November 13, 2021 02:00 - November 13, 2021 05:00 UTC



November 14, 2021 06:21 UTC
[Update] All testing has been completed and customers.gitlab.com is now fully functional. Thank you for your patience.

November 14, 2021 05:22 UTC
[Update] We are still testing to ensure full functionality of the customers.gitlab.com site. Next update when testing is completed.

November 14, 2021 04:45 UTC
[Update] Maintenance is completed on 3rd party API, we are completing tests. Expect full functionality of customers.gitlab.com in about 30mins.

November 14, 2021 03:02 UTC
[Update] The customers.gitlab.com site is unavailable due to a 3rd-party API set to maintenance mode. You will not be able to manage subscriptions or purchase new one during this time.





Back to current status