All Systems Operational

Updated a few seconds ago

Back to current status

Status History

Filter: Website (Clear)



October 2024

Errors on work item updates

October 10, 2024 17:44 UTC

Errors on work item updatesPartial Service Disruption

Incident Status

Partial Service Disruption


Components

Website, API


Locations

Google Compute Engine




October 10, 2024 17:44 UTC
[Resolved] The MR to remove a database foreign key has been deployed to the production. This incident is now resolved. For more details, visit gitlab.com/gitlab-com/gl-infra/production/-/issues/18692.

October 10, 2024 06:21 UTC
[Identified] We are preparing a MR to remove a database foreign key that is causing this issue. The next update will be provided once the incident has been mitigated. For more details, visit gitlab.com/gitlab-com/gl-infra/production/-/issues/18692

October 10, 2024 05:01 UTC
[Investigating] We are currently investigating an error with Work Item updates. More details about this incident can be found in gitlab.com/gitlab-com/gl-infra/production/-/issues/18692

Sidekiq job delays resulting in updates to MR approval policies being ineffective

October 4, 2024 06:59 UTC

Incident Status

Partial Service Disruption


Components

Website, API


Locations

Google Compute Engine




October 4, 2024 06:59 UTC
[Resolved] Our monitoring shows no further issues after the fix was applied. We are resolving this issue and any further updates will be in: gitlab.com/gitlab-com/gl-infra/production/-/issues/18660

October 3, 2024 22:23 UTC
[Monitoring] The fix has been successfully merged, but we are still waiting for the changes to reach production. We will continue to monitor Sidekiq’s performance, and the next update will be provided once the incident has been mitigated. For more details, visit gitlab.com/gitlab-com/gl-infra/production/-/issues/18660

October 3, 2024 21:04 UTC
[Monitoring] The fix has been successfully merged. We will continue to monitor Sidekiq’s performance to ensure everything is functioning as expected. For details, visit gitlab.com/gitlab-com/gl-infra/production/-/issues/18660

October 3, 2024 20:00 UTC
[Monitoring] The fix is expected to be merged soon. In the meantime, we’ll continue monitoring Sidekiq’s performance. Updates to MR approval policies will remain delayed until the issue is fully resolved. For more details, visit gitlab.com/gitlab-com/gl-infra/production/-/issues/18660

October 3, 2024 19:02 UTC
[Monitoring] We are still awaiting the deployment of the fix and will continue to monitor Sidekiq’s performance in the meantime. Updates to MR approval policies are delayed until the issue is resolved. For more details, visit gitlab.com/gitlab-com/gl-infra/production/-/issues/18660

October 3, 2024 18:02 UTC
[Monitoring] We continue to closely monitor Sidekiq’s performance while awaiting the deployment of the fix. In the meantime, updates to MR approval policies remain delayed. More details about this incident can be found at gitlab.com/gitlab-com/gl-infra/production/-/issues/18660

October 3, 2024 17:06 UTC
[Monitoring] We are actively monitoring the performance of Sidekiq until the fix is deployed. Updates to merge request approval policies are still experiencing delays. Details about this incident can be found in gitlab.com/gitlab-com/gl-infra/production/-/issues/18660

October 3, 2024 15:55 UTC
[Monitoring] We're continuing to monitor the performance of Sidekiq until the fix is deployed. Updates to MR approval policies are still processed with delays. The MR to fix the root cause is currently waiting to be merged. More details about this incident can be found in gitlab.com/gitlab-com/gl-infra/production/-/issues/18660

October 3, 2024 14:46 UTC
[Monitoring] We're continuing to see improvements and are monitoring until a fix is deployed. Updates to MR approval policies are still processed with delays. More details about this incident can be found in gitlab.com/gitlab-com/gl-infra/production/-/issues/18660

October 3, 2024 14:28 UTC
[Monitoring] We've identified the root cause and are recovering from a high volume of request traffic and are seeing improvements. Updates to MR approval policies are currently processing but with delays. More details about this incident can be found in gitlab.com/gitlab-com/gl-infra/production/-/issues/18660

October 3, 2024 14:12 UTC
[Investigating] We are currently investigating issues with updating MR Approval policies as a result of Sidekiq performance degradation. More details about this incident can be found in gitlab.com/gitlab-com/gl-infra/production/-/issues/18660.

September 2024

Main DB Upgrade

September 26, 2024 03:54 UTC

Main DB UpgradePlanned Maintenance

Description

We will be undergoing scheduled maintenance to our database layer. GitLab.com will continue to be available during the maintenance window. For more details, see gitlab.com/gitlab-com/gl-infra/dbre/-/issues/227


Components

Website, API, Git Operations, CI/CD - Hosted runners on Linux, CI/CD - Hosted runners on Windows, CI/CD - Hosted runners on macOS, CI/CD - Hosted runners for GitLab community contributions


Locations

Google Compute Engine, AWS


Schedule

October 25, 2024 00:00 - October 30, 2024 01:00 UTC



September 26, 2024 03:54 UTC
[Update] Scheduled maintenance on October 25 to our database layer has now been cancelled. For more details, see gitlab.com/gitlab-com/gl-infra/dbre/-/issues/227

CI DB upgrade

September 26, 2024 03:50 UTC

CI DB upgradePlanned Maintenance

Description

Next week, we will be undergoing scheduled maintenance to our CI database layer. The maintenance will start at 2024-09-29 00:00 UTC and should finish at 2024-10-02 02:00 UTC (including performance regression observability period). GitLab.com will be available during the whole period as the maintenance should be seamless and transparent for the application. We apologize in advance for any inconvenience this may cause. See <gitlab.com/gitlab-com/gl-infra/production/-/issues/18593>


Components

Website, API, Git Operations, CI/CD - Hosted runners on Linux, CI/CD - Hosted runners on Windows, CI/CD - Hosted runners on macOS, CI/CD - Hosted runners for GitLab community contributions


Locations

Google Compute Engine, AWS


Schedule

September 27, 2024 00:00 - October 2, 2024 01:00 UTC



September 26, 2024 03:50 UTC
[Update] Maintenance scheduled for 2024-09-29 on our CI database layer, has now been cancelled. For more information: gitlab.com/gitlab-com/gl-infra/production/-/issues/18593

Slowness on GitLab.com

September 21, 2024 17:55 UTC

Slowness on GitLab.comPartial Service Disruption

Incident Status

Partial Service Disruption


Components

Website, API, Git Operations


Locations

Google Compute Engine




September 21, 2024 17:55 UTC
[Resolved] Our monitoring has show no further issues after our change. We are resolving this issue and any further updates will be in: gitlab.com/gitlab-com/gl-infra/production/-/issues/18596

September 21, 2024 14:44 UTC
[Monitoring] We have identified the issue, and have made a change. We continue to see improvements. We will now continue to monitor, and if nothing changes, the next update can be expected in 3 hours. More details in: gitlab.com/gitlab-com/gl-infra/production/-/issues/18596

September 21, 2024 14:09 UTC
[Identified] We are recovering from a high volume of request traffic and are seeing improvements. More information in: gitlab.com/gitlab-com/gl-infra/production/-/issues/18596

September 21, 2024 13:45 UTC
[Investigating] We are seeing slow responses from our API, and we are still investigating. More information in: gitlab.com/gitlab-com/gl-infra/production/-/issues/18596

September 21, 2024 13:27 UTC
[Investigating] No material updates at this point. Our Engineers are still investigating. More information in: gitlab.com/gitlab-com/gl-infra/production/-/issues/18596

September 21, 2024 13:10 UTC
[Investigating] We are currently investigating problems with slowness on GitLab.com. More information in: gitlab.com/gitlab-com/gl-infra/production/-/issues/18596

Intermittent 503 errors

September 20, 2024 21:40 UTC

Incident Status

Operational


Components

Website, API, Canary


Locations

Google Compute Engine




September 20, 2024 21:40 UTC
[Resolved] GitLab has not seen any further errors related to this incident in our monitoring and we are resolving the incident. Any further updates are in the incident issue: gitlab.com/gitlab-com/gl-infra/production/-/issues/18591.

September 20, 2024 20:53 UTC
[Monitoring] Our rollout has completed and we believe that the issue is mitigated. We are moving the incident to Monitoring to validate the fix. gitlab.com/gitlab-com/gl-infra/production/-/issues/18591

September 20, 2024 15:08 UTC
[Identified] No material updates to report. The roll out of the fix is still ongoing. More details are available in gitlab.com/gitlab-com/gl-infra/production/-/issues/18591.

September 20, 2024 13:54 UTC
[Identified] We are seeing an uptick in errors with git operations. The roll out of the fix is still ongoing. More details are available in gitlab.com/gitlab-com/gl-infra/production/-/issues/18591.

September 20, 2024 13:12 UTC
[Identified] We are seeing an increased number of 503 errors in the UI and API. We have identified the issue and are rolling out a fix. More details are available in gitlab.com/gitlab-com/gl-infra/production/-/issues/18591.

Slowness on GitLab.com

September 17, 2024 02:19 UTC

Incident Status

Operational


Components

Website


Locations

Google Compute Engine




September 17, 2024 02:19 UTC
[Resolved] This issue is now resolved. Details can be found in gitlab.com/gitlab-com/gl-infra/production/-/issues/18562.

September 13, 2024 21:21 UTC
[Monitoring] No further updates at this time. We're monitoring the situation. Please see the issue here: gitlab.com/gitlab-com/gl-infra/production/-/issues/18562

September 13, 2024 19:46 UTC
[Monitoring] The cause of the slowness has been identified and corrected. We're monitoring the situation. Please see the issue here: gitlab.com/gitlab-com/gl-infra/production/-/issues/18562

September 13, 2024 19:03 UTC
[Investigating] We've received reports of slowness on GitLab.com. We're currently investigating. Please see the issue here: gitlab.com/gitlab-com/gl-infra/production/-/issues/18562

September 13, 2024 19:03 UTC
[Investigating] We've received reports of slowness on GitLab.com. We're currently investigating. Please see the issue here: gitlab.com/gitlab-com/gl-infra/production/-/issues/18562

PDF rendering issues on GitLab.com

September 16, 2024 17:56 UTC

Incident Status

Degraded Performance


Components

Website


Locations

Google Compute Engine




September 16, 2024 17:56 UTC
[Resolved] GitLab has resolved PDF rendering issues. We are following up to prevent this kind of issue in the future; futher details in gitlab.com/gitlab-com/gl-infra/production/-/issues/18574

September 16, 2024 17:50 UTC
[Investigating] GitLab is investigating PDF rendering issues on GitLab.com. gitlab.com/gitlab-com/gl-infra/production/-/issues/18574

Registry DB upgrade

September 11, 2024 22:51 UTC

Registry DB upgradePlanned Maintenance

Description

We will be undergoing scheduled maintenance to our database layer. GitLab.com will continue to be available during the maintenance window. For more details, see gitlab.com/gitlab-com/gl-infra/dbre/-/issues/225


Components

Website, API, Git Operations, CI/CD - Hosted runners on Linux, CI/CD - Hosted runners on Windows, CI/CD - Hosted runners on macOS, CI/CD - Hosted runners for GitLab community contributions


Locations

Google Compute Engine, AWS


Schedule

September 6, 2024 00:00 - September 11, 2024 01:00 UTC



September 11, 2024 22:51 UTC
[Update] Planned maintenance for the registry database layer on GitLab.com is complete. Registry database is now running Postgres v16. The rollback window for the Registry database was closed on approximately 2024-09-12 1:00 UTC.

September 8, 2024 01:51 UTC
[Update] Planned maintenance for the registry database layer on GitLab.com is complete. Registry database is now running Postgres v16. Rollback window for this planned maintenance ends 2024-09-11 00:00 UTC. We'll be monitoring the platform during this time to ensure all systems are functioning correctly.

September 8, 2024 00:11 UTC
[Update] Scheduled maintenance to our registry database layer has started. The maintenance should finish at 2024-09-11 02:00 UTC UTC (including performance regression observability period). GitLab.com will be available during the whole period as the maintenance should be seamless and transparent for the application. We apologize in advance for any inconvenience this may cause. See issue for more information: gitlab.com/gitlab-com/gl-infra/production/-/issues/18447

September 5, 2024 05:53 UTC
[Update] In 3 days, we will be undergoing scheduled maintenance to our registry database layer. The maintenance will start at 2024-09-08 00:00 UTC UTC and should finish at 2024-09-11 02:00 UTC UTC (including performance regression observability period). GitLab.com will be available during the whole period as the maintenance should be seamless and transparent for the application. We apologize in advance for any inconvenience this may cause. See <gitlab.com/gitlab-com/gl-infra/production/-/issues/18447>

GitLab connectivity issues

September 10, 2024 13:40 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 on macOS, CI/CD - Hosted runners for GitLab community contributions


Locations

Google Compute Engine




September 10, 2024 13:40 UTC
[Resolved] This incident has been resolved. More information can be found in gitlab.com/gitlab-com/gl-infra/production/-/issues/18535.

September 10, 2024 13:33 UTC
[Monitoring] The website has recovered are and we are now monitoring before marking as resolved. More details can be found in gitlab.com/gitlab-com/gl-infra/production/-/issues/18535.

September 10, 2024 13:24 UTC
[Investigating] No material updates at this time - our investigation is ongoing. More details can be found in gitlab.com/gitlab-com/gl-infra/production/-/issues/18535

September 10, 2024 13:10 UTC
[Investigating]

September 10, 2024 13:08 UTC
[Investigating] We are currently investigating connectivity issues to GitLab.com. For more information see gitlab.com/gitlab-com/gl-infra/production/-/issues/18535

Some projects and repositories are not accessible

September 6, 2024 11:19 UTC

Incident Status

Partial Service Disruption


Components

Website


Locations

Google Compute Engine




September 6, 2024 11:19 UTC
[Resolved] This incident has been resolved and projects are accessible. More details can be found in gitlab.com/gitlab-com/gl-infra/production/-/issues/18514.

September 6, 2024 10:46 UTC
[Monitoring] We have taken action to mitigate the issue and are now monitoring before marking as resolved. More details about this incident can be found in gitlab.com/gitlab-com/gl-infra/production/-/issues/18514.

September 6, 2024 10:35 UTC
[Identified] We've identified the cause of the issue and are working on resolving it. More details about this incident can be found in gitlab.com/gitlab-com/gl-infra/production/-/issues/18514.

September 6, 2024 10:15 UTC
[Investigating] We are currently investigating issues where some projects and repositories are not accessible. More details about this incident can be found in gitlab.com/gitlab-com/gl-infra/production/-/issues/18514.

GitLab.com Connectivity Issues

September 3, 2024 05:34 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 on macOS, 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, docs.gitlab.com, Canary, Product Analytics - Configurator (Beta), Product Analytics - Collector (Beta), Product Analytics - Background processing (Beta), Product Analytics - Queries (Beta), GitLab Duo


Locations

Google Compute Engine, Digital Ocean, Zendesk, AWS




September 3, 2024 05:34 UTC
[Resolved] All GitLab services have been restored. We are actively monitoring the system, and everything appears normal at this time. For more details, please follow the issue at: gitlab.com/gitlab-com/gl-infra/production/-/issues/18490

September 3, 2024 05:19 UTC
[Monitoring] We've identified and addressed the root cause of the issue. All GitLab services have been restored, and we are actively monitoring the system. Follow the issue for more details : gitlab.com/gitlab-com/gl-infra/production/-/issues/18490

September 3, 2024 05:09 UTC
[Investigating] GitLab.com is currently experiencing connectivity issues due to a high error rate. Our infrastructure team is investigating. Issue: gitlab.com/gitlab-com/gl-infra/production/-/issues/18490

August 2024

Embedding DB Upgrade

August 31, 2024 04:58 UTC

Embedding DB UpgradePlanned Maintenance

Description

We will be undergoing scheduled maintenance to our database layer. GitLab.com will continue to be available during the maintenance window. For more details, see gitlab.com/gitlab-com/gl-infra/dbre/-/issues/228


Components

Website, API, Git Operations, CI/CD - Hosted runners on Linux, CI/CD - Hosted runners on Windows, CI/CD - Hosted runners on macOS, CI/CD - Hosted runners for GitLab community contributions


Locations

Google Compute Engine, AWS


Schedule

October 25, 2024 00:00 - October 30, 2024 01:00 UTC



August 31, 2024 04:58 UTC
[Update] We are cancelling the Embedding database upgrade. See gitlab.com/gitlab-com/gl-infra/dbre/-/issues/228 for details. All other DB upgrade schedules will go ahead as planned.

CI/CD token allowlist selection failing

August 27, 2024 14:52 UTC

CI/CD token allowlist selection failingPartial Service Disruption

Incident Status

Partial Service Disruption


Components

Website, CI/CD - Hosted runners on Linux, CI/CD - Hosted runners on Windows, CI/CD - Hosted runners on macOS, CI/CD - Hosted runners for GitLab community contributions


Locations

Google Compute Engine, AWS




August 27, 2024 14:52 UTC
[Resolved] The revert MR has been deployed to production, and we see that CI/CD token allowlist project selection renders properly now. Details will be provided in the incident issue: gitlab.com/gitlab-com/gl-infra/production/-/issues/18446

August 27, 2024 03:55 UTC
[Identified] We have identified an issue that is causing CI/CD token allowlist project selection to fail. We are in the process of reverting the change that caused this. For more details see gitlab.com/gitlab-com/gl-infra/production/-/issues/18446.

Some requests timing out

August 23, 2024 03:59 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 on macOS, 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, docs.gitlab.com, Canary, Product Analytics - Configurator (Beta), Product Analytics - Collector (Beta), Product Analytics - Background processing (Beta), Product Analytics - Queries (Beta), GitLab Duo


Locations

Google Compute Engine, Digital Ocean, Zendesk, AWS




August 23, 2024 03:59 UTC
[Resolved] The issue has been resolved and all functionality on GitLab.com is nominal. Please see gitlab.com/gitlab-com/gl-infra/production/-/issues/18435 for more details.

August 23, 2024 01:53 UTC
[Monitoring] The issue has been identified and the incident resolved. We will continue monitoring for a while.

August 23, 2024 01:27 UTC
[Identified] We have identified an underlying cause and are working to mitigate it. See gitlab.com/gitlab-com/gl-infra/production/-/issues/18435 for more details.

August 23, 2024 00:34 UTC
[Investigating] We have noticed that there are delays in web UI updates for example, MRs not showing up after submission, We are continuing to investigate - please see gitlab.com/gitlab-com/gl-infra/production/-/issues/18435 for more details.

August 23, 2024 00:27 UTC
[Investigating] Some requests are slow or timing out due to DB saturation. We are investigating. Please see [this issue](gitlab.com/gitlab-com/gl-infra/production/-/issues/18435) for further details.

Sidekiq processing delays

August 16, 2024 20:29 UTC

Sidekiq processing delaysDegraded Performance

Incident Status

Degraded Performance


Components

Website, Background Processing


Locations

Google Compute Engine




August 16, 2024 20:29 UTC
[Resolved] This incident is considered resolved. Thanks for your patience! Details will be provided in the incident issue: gitlab.com/gitlab-com/gl-infra/production/-/issues/18407

August 16, 2024 20:05 UTC
[Identified] While background processing has stabilized, our team is still investigating the root cause. Updates will be provided when more information is available.

August 16, 2024 19:40 UTC
[Identified] Our team has identified and disabled a worker that was impacting performance. Sidekiq processing is improving and we are continuing to monitor the state of the background processing.

August 16, 2024 19:27 UTC
[Investigating] Our team is still investigating the processing delays. Some users might experience some errors with creating merge requests or other delays with processing background jobs.

August 16, 2024 19:07 UTC
[Investigating] Our team is currently investigating some sidekiq performance issues which is causing some delays in jobs processing. More information will be in the incident issue gitlab.com/gitlab-com/gl-infra/production/-/issues/18407

All CVEs on the GitLab Advisory Database are returning 404s

August 8, 2024 04:18 UTC

Incident Status

Partial Service Disruption


Components

Website


Locations

Google Compute Engine




August 8, 2024 04:18 UTC
[Resolved] We have determined that while CVEs on advisories.gitlab.com are returning 404s, this has no impact on the operations of gitlab.com. For more details, see gitlab.com/gitlab-com/gl-infra/production/-/issues/18374.

August 8, 2024 03:48 UTC
[Investigating] We are currently seeing that every CVE on advisories.gitlab.com is returning a 404. Investigation continues. For more details, see gitlab.com/gitlab-com/gl-infra/production/-/issues/18374

August 8, 2024 00:44 UTC
[Investigating] We are currently seeing that every CVE on advisories.gitlab.com is returning a 404. We are investigating the cause. For more details, see gitlab.com/gitlab-com/gl-infra/production/-/issues/18374

July 2024

Signup with OAuth cannot be completed

July 30, 2024 13:19 UTC

Signup with OAuth cannot be completedPartial Service Disruption

Incident Status

Partial Service Disruption


Components

Website


Locations

Google Compute Engine




July 30, 2024 13:19 UTC
[Resolved] The rollback has now completed. Users signing up with OAuth are now able to complete the verification process.

July 30, 2024 12:47 UTC
[Identified] There are no material updates at this time. The rollback is in progress, and we will post again, once complete.

July 30, 2024 12:07 UTC
[Identified] There are no material updates to report. Our engineers are still working on rolling back the change that introduced the issue.

July 30, 2024 11:25 UTC
[Identified] No material updates to report. The rollback of the change that introduced the issue is still ongoing.

July 30, 2024 10:40 UTC
[Identified] There are no material updates to report. We are still in the process of rolling back the change that introduced the issue.

July 30, 2024 10:01 UTC
[Identified] No material updates at this point. We have identified the MR that introduced the issue, and are still rolling back. More details in: gitlab.com/gitlab-com/gl-infra/production/-/issues/18341

July 30, 2024 09:25 UTC
[Identified] We are currently seeing issues for customers using Signup with OAuth SSO. We are in the process of reverting the change that introduced this issue. More details in: gitlab.com/gitlab-com/gl-infra/production/-/issues/18341

Merge Request incorrectly rejected by expression in merge commit message

July 23, 2024 11:04 UTC

Incident Status

Partial Service Disruption


Components

Website


Locations

Google Compute Engine




July 23, 2024 11:04 UTC
[Resolved] We have confirmed that the fix has resolved the incident, and it's reflected in the number of errors we monitored. This incident is now resolved. More information in this issue: gitlab.com/gitlab-com/gl-infra/production/-/issues/18313

July 23, 2024 10:09 UTC
[Monitoring] We've now merged the fix to the production environment and are currently monitoring for errors. The progress could be followed in this issue: gitlab.com/gitlab-com/gl-infra/production/-/issues/18313

July 23, 2024 06:52 UTC
[Identified] The rollback has been merged and deployed to our staging environment. We are currently awaiting the next release to production, which should resolve the issue. For more details and workarounds, please refer to this issue: gitlab.com/gitlab-com/gl-infra/production/-/issues/18313

July 22, 2024 21:33 UTC
[Identified] The rollback is merged and in our staging environment, and the next release that will allow it to go to production is tomorrow, 2024-07-23. For details: gitlab.com/gitlab-com/gl-infra/production/-/issues/18313

July 22, 2024 20:18 UTC
[Identified] The rollback of the change causing merge requests to be blocked by commit message rules incorrectly is currently in staging and awaiting release to production. gitlab.com/gitlab-com/gl-infra/production/-/issues/18313

July 22, 2024 10:01 UTC
[Identified] Some users are seeing MRs being incorrectly rejected by commit message rules. We have identified the cause and are in the process of rolling back the relevant MR. For further details see gitlab.com/gitlab-com/gl-infra/production/-/issues/18313

Repository tree not loading all contents

July 17, 2024 14:00 UTC

Incident Status

Degraded Performance


Components

Website


Locations

Google Compute Engine




July 17, 2024 14:00 UTC
[Resolved] We have confirmed that the fix allows the repository content to fully load. The incident is resolved. For more details, see gitlab.com/gitlab-com/gl-infra/production/-/issues/18286

July 17, 2024 03:17 UTC
[Identified] A fix has been pushed and is currently in the process of being deployed. More details: gitlab.com/gitlab-com/gl-infra/production/-/issues/18286

July 17, 2024 01:30 UTC
[Identified] We have identified an MR that we believe introduced the issue. We are performing tests locally to confirm. More details: gitlab.com/gitlab-com/gl-infra/production/-/issues/18286

July 16, 2024 21:18 UTC
[Investigating] Investigation is still ongoing to fix this issue. We will post the next update once we have identified the cause. Please follow gitlab.com/gitlab-com/gl-infra/production/-/issues/18286 for more details.

July 16, 2024 20:03 UTC
[Investigating] We're investigating the possibility of a recent change to gitaly as related to this issue. Please continue to follow gitlab.com/gitlab-com/gl-infra/production/-/issues/18286 for more details.

July 16, 2024 19:04 UTC
[Investigating] We continue to investigate the cause of this repository content visibility issue. Make sure to enable notifications at gitlab.com/gitlab-com/gl-infra/production/-/issues/18286 to track progress.

July 16, 2024 17:55 UTC
[Investigating] We are working across different teams to narrow down the cause of this issue. We will be updating this incident every hour or as soon as we have material updates to share. See gitlab.com/gitlab-com/gl-infra/production/-/issues/18286.

July 16, 2024 17:11 UTC
[Investigating] No material updates to provide. We continue to investigate this issue at gitlab.com/gitlab-com/gl-infra/production/-/issues/18286.

July 16, 2024 16:51 UTC
[Investigating] We continue to investigate the cause for this issue. Please follow gitlab.com/gitlab-com/gl-infra/production/-/issues/18286 for more details.

July 16, 2024 15:33 UTC
[Investigating] A issue has been identified where listings of repository files are truncated after a hundred entries. We are currently investigating the cause. For more details, see gitlab.com/gitlab-com/gl-infra/production/-/issues/18286





Back to current status