Gitlab outage history

October 23, 2026 16:32 UTC Monitoring - We identified and resolved an issue that caused slowness on GitLab.com. GitLab.com is operating normally, and we are monitoring the platform to ensure the issue remains resolved. More details here: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23320 October 23, 2026 17:04 UTC Resolved - We have resolved the issue that caused slowness on GitLab.com. GitLab.com is operating normally, and we are continuing to monitor the platform. The impact may have included partial degradation to the web UI and Git operations.

October 20, 2026 21:56 UTC Investigating - We've investigating 404s on the customers panel. We'll update as we learn more October 20, 2026 22:47 UTC Investigating - We’re continuing our investigation of 404s on the customers panel. We’ll update you as we learn more. October 20, 2026 23:15 UTC Investigating - We’re continuing our investigation of 404s on the customers panel. We’ll update you as we learn more. October 20, 2026 23:51 UTC Monitoring - The Customers Portal is loading normally again, and we are no longer observing the intermittent 404 errors affecting sign-in and page loading. A redeployment has completed successfully, and we are monitoring the service for any recurrence before resolving the incident. October 21, 2026 01:21 UTC Resolved - The monitoring period has concluded, and the incident has been confirmed resolved. See the issue for more details: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23297

October 20, 2026 07:08 UTC Investigating - We're investigating intermittent HTTP 503 errors when opening project pages. At this time, this issue only occurs in specific projects. More details at: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23288 October 20, 2026 07:37 UTC Monitoring - This issue affects projects and groups using GitLab Secrets Manager. Users saw HTTP 500 errors, not 503 as previously stated. A mitigation has been applied and we're monitoring. Details: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23288 October 20, 2026 07:37 UTC Monitoring - This issue affects projects and groups using GitLab Secrets Manager. Users saw HTTP 500 errors, not 503 as previously stated. A mitigation has been applied and we're monitoring. Details: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23288 October 20, 2026 09:55 UTC Resolved - We have not seen any more HTTP 500 errors for GitLab Secrets Manager since the mitigation was applied. This incident is now resolved. Details: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23288

October 16, 2026 16:10 UTC Investigating - We are investigating the cause of 503s on GitLab.com and the site moving slowly. We will update once we have additional details. October 16, 2026 16:25 UTC Investigating - We are still investigating the cause of 503 on GitLab.com. We are seeing some services return but errors still intermittent. More details at: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23261 October 16, 2026 16:40 UTC Identified - We have identified the cause of 503s on GitLab.com and are working to remediate the issue. We are still seeing intermittent 503s and site slowness as we work to resolve the issue. More details: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23261 October 16, 2026 16:52 UTC Identified - Most services on GitLab.com have recovered but we are seeing slowness with Duo requests and services and are looking to resolve it. More details at: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23261 October 16, 2026 17:05 UTC Monitoring - We have taken steps to resolve the slowness and 503s on GitLab.com and are monitoring the situation. More details at: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23261 October 16, 2026 17:24 UTC Resolved - The issue is fully resolved and operations on GitLab.com and GitLab Duo are operating normally. More details at: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23261

October 16, 2026 11:33 UTC Investigating - We’re investigating an issue affecting CI/CD on GitLab.com for a limited number of customers. Pipelines may fail with the following error, and the UI may be slow: “CI configuration fetch from Gitaly timed out. This may indicate Gitaly service slowness or an outage.” More updates to follow. October 16, 2026 12:28 UTC Monitoring - We've applied a temporary mitigation to address CI/CD failures and UI slowness affecting a limited number of GitLab.com customers. We're monitoring recovery while working on a longer-term solution. October 16, 2026 13:21 UTC Resolved - The issue causing CI/CD failures and UI slowness for a limited number of GitLab.com customers has been resolved. Thank you for your patience.

October 15, 2026 16:19 UTC Investigating - We are investigating an issue affecting GitLab.com CI/CD. Some pipelines may remain in the created state for an extended period or fail to start, causing CI/CD workflows to stall. More Details at https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23234 October 15, 2026 17:23 UTC Identified - We have identified the cause of the issue causing CI/CD delays on GitLab.com and are working to take corrective actions. The issue may persists intermittently as we do so. More details at: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23234 October 15, 2026 19:50 UTC Resolved - We have taken steps to mitigate the delays on CI/CD jobs on GitLab.com and services have returned to normal. More details at: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23234

October 15, 2026 04:43 UTC Investigating - We're investigating an issue that's stopping pages on customers.gitlab.com from loading. Purchasing, renewing, and managing subscriptions may be affected. GitLab.com itself is not affected. October 15, 2026 05:10 UTC Investigating - We have received reports that some groups on GitLab.com are experiencing HTTP 500 errors because the group is unable to sync with customers.gitlab.com. We are continuing to investigate the issue. October 15, 2026 05:27 UTC Investigating - No material updates to report. We are still investigating the root cause. October 15, 2026 05:50 UTC Investigating - No material updates to report. We'll share another update when we have more information. October 15, 2026 08:35 UTC Monitoring - Mitigations have been applied to customers.gitlab.com, and we are monitoring service availability. Intermittent errors may continue to affect Customers Portal pages and GitLab.com groups that rely on the portal for subscription-related operations. We are continuing to investigate the underlying cause and will provide another update when more information is available. More details: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23240 October 15, 2026 09:02 UTC Resolved - The issue affecting customers.gitlab.com has been resolved. Customers Portal pages and subscription-related operations have returned to normal. More details: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23240

October 13, 2026 07:10 UTC Investigating - We are currently investigating reports of an increase of HTTP 50X errors on GitLab.com October 13, 2026 07:30 UTC Investigating - We are seeing an improvement in errors rates in our monitoring, starting from 07:14 UTC. We are still identifying the root cause. October 13, 2026 07:48 UTC Investigating - General GitLab.com service continues to improve. We're now focused on restoring Duo services. October 13, 2026 07:59 UTC Monitoring - We are seeing improvements across all services on GitLab.com. We are resuming our investigation on identifying the root cause. October 14, 2026 02:33 UTC Monitoring - Monitoring confirms that GitLab.com services have remained stable. We are continuing to monitor for any recurrence of the issues before marking this incident as resolved. October 14, 2026 23:40 UTC Resolved - We have been monitoring this issue for a few days with no reported occurrences.

October 14, 2026 14:33 UTC Investigating - We are investigating an issue affecting GitLab.com merge trains. Some merge train pipelines may remain in the created state for an extended period or fail to start, causing merge trains and related CI/CD workflows to stall. More details: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23192 October 14, 2026 15:22 UTC Investigating - We are investigating an issue affecting GitLab.com CI/CD. Merge train, scheduled, and child/downstream pipelines may be delayed, remain in a created or pending state, or fail to start. Mergeability analysis and webhook notifications may also be delayed. More details: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23192 October 14, 2026 16:40 UTC Investigating - We are investigating an issue affecting GitLab.com and general site errors and slowness related to the initial issue. We are actively investigating the issue. More details: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23192 October 14, 2026 16:50 UTC Identified - We identified the issue affecting GitLab.com and general site errors and slowness related to the initial issue. We are actively working to resolve the issue. More details: gitlab.com/gitlab-com/gl-infra/production/-/work_items/23192 October 14, 2026 18:30 UTC Resolved - The source of the issue has been identified and we have taken steps to remediate and resolve the issue. GitLab.com is stable now. More details: gitlab.com/gitlab-com/gl-infra/production/-/work_items/23192

October 12, 2026 11:30 UTC Identified - We’re investigating an issue affecting some GitLab Duo Workflow operations. Duo Code Review results may be incomplete or lower quality than expected. Our engineering teams are working on mitigation and will provide further updates. More details: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23158 October 12, 2026 13:37 UTC Identified - We've identified the cause of the issue affecting GitLab Duo Workflow operations. Duo Code Review remains available, but reviews may contain less context than expected. Our engineering teams are expediting a fix and will continue monitoring until service is fully restored. For more details: gitlab.com/gitlab-com/gl-infra/production/-/work_items/23158 October 13, 2026 00:28 UTC Monitoring - Errors affecting Code Review tools have decreased, and the tools appear to be operating normally. We’re monitoring error rates and investigating the improvement. A fix is merged but not yet in production, so recovery is still being validated. October 13, 2026 00:29 UTC Monitoring - Errors affecting Code Review tools have decreased, and the tools appear to be operating normally. We’re monitoring error rates and investigating the improvement. A fix is merged but not yet in production, so recovery is still being validated. October 13, 2026 02:11 UTC Identified - Monitoring shows failures are still occurring in a tool used by Duo Code Review. The service remains available, but reviews may contain less context than expected. A fix is merged and awaiting deployment; we’ll update once recovery is confirmed. October 14, 2026 01:16 UTC Resolved - The fix was deployed and continued monitoring has shown that the identified tool failure has been addressed. This issue is now resolved. Details in https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23158

October 13, 2026 14:27 UTC Investigating - We are investigating increased queue times for CI/CD jobs using GitLab.com small Linux x86-64 hosted runners. Affected jobs may remain pending longer than usual before starting. We have identified errors and delays when provisioning runner capacity and are working to restore normal job start times. More details: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23176 October 13, 2026 15:46 UTC Identified - We have identified an ongoing Google Cloud Compute Engine issue affecting runner-capacity provisioning in us-east1. Some GitLab.com CI/CD jobs using small Linux x86-64 hosted runners may remain pending longer than usual before starting. Our engineering teams are working with Google Cloud to restore normal job start times. More details: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23176 October 13, 2026 19:31 UTC Monitoring - Job start times for CI/CD jobs on GitLab.com small Linux x86-64 hosted runners have returned to normal, and the backlog of pending jobs has been processed. The delays were caused by errors and capacity constraints from our cloud provider when provisioning runner capacity in one region, between approximately 13:17 and 19:15 UTC. Jobs that were delayed are now starting as usual. We are monitoring to make sure performance remains stable and will post an update when this incident is resolved. October 13, 2026 20:59 UTC Resolved - Job start times for CI/CD jobs on GitLab.com small Linux x86-64 hosted runners have returned to normal, and the backlog of pending jobs has been processed. The issue with the provider persists, but we are not seeing any impact on our systems. More details: gitlab.com/gitlab-com/gl-infra/production/-/work_items/23176

October 10, 2026 04:49 UTC Investigating - We are investigating reports of errors and slow performance on merge request and pipeline pages for projects in the specific groups. Details in https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23150 October 10, 2026 06:26 UTC Monitoring - We have applied a mitigation and are seeing sustained recovery in error rates and performance on merge request and pipeline pages for the affected projects. We are continuing to monitor. Details in https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23150 October 10, 2026 06:27 UTC Monitoring - We have applied a mitigation and are seeing sustained recovery in error rates and performance on merge request and pipeline pages for the affected projects. We are continuing to monitor. Details in gitlab.com/gitlab-com/gl-infra/production/-/work_items/23150 October 12, 2026 10:15 UTC Resolved - The issue has been resolved, and systems have returned to normal operation.

October 8, 2026 15:59 UTC Investigating - We are currently investigating delays in job completion: CI jobs remain running after success, delaying pipeline progression. Details https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23133 October 8, 2026 16:19 UTC Investigating - Job completion delays are still being observed and we are actively working to address the issue. Details in: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23133 October 8, 2026 16:35 UTC Investigating - Our investigation is ongoing and we are actively working to identify the root cause. We will provide further updates as more information becomes available. Details in: gitlab.com/gitlab-com/gl-infra/production/-/work_items/23133 October 8, 2026 17:11 UTC Identified - We are continuing to investigate. In addition to delays, users may experience job timeouts or failures during this time. If affected, please retry the job. Details in: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23133 October 8, 2026 17:34 UTC Identified - We are continuing to investigate the root cause and will provide further updates as they become available. Details in: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23131 October 8, 2026 17:45 UTC Monitoring - We are beginning to see signs of recovery and are continuing to monitor the situation closely while we investigate the root cause. If you have been affected, please retry any failed or timed out jobs. Details in: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23131 October 8, 2026 18:33 UTC Resolved - After continued monitoring, services remain stable. The incident has been resolved.

October 7, 2026 16:51 UTC Monitoring - An incident affecting CI/CD jobs on GitLab.com instance runners has been resolved. Job pickup delays should no longer be occurring and we are continuing to monitor to confirm full recovery. Details in: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23117 October 7, 2026 18:04 UTC Resolved - The incident affecting CI/CD jobs on GitLab.com instance runners has been resolved. Following a period of monitoring, everything has remained stable. Details in: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23117

October 1, 2026 18:30 UTC Investigating - Some CI/CD jobs using saas-linux-small-amd64 hosted runners are experiencing delays before starting. We are restoring affected runner capacity and monitoring recovery. Delays may continue while the backlog clears. The root cause remains under investigation. For details, see https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23077. October 1, 2026 18:47 UTC Monitoring - Jobs are processing as expected at this time, and graphs have returned to normal. We are now monitoring the situation. For details, see gitlab.com/gitlab-com/gl-infra/production/-/work_items/23077. October 1, 2026 19:53 UTC Monitoring - Job processing is stable; monitoring continues. Details: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23077 October 1, 2026 21:12 UTC Monitoring - No material updates, monitoring continues. Details: gitlab.com/gitlab-com/gl-infra/production/-/work_items/23077 October 1, 2026 21:48 UTC Resolved - Jobs on saas-linux-small-amd64 hosted runners have been processing as expected, and this incident is now resolved. Details at: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23077

October 1, 2026 00:35 UTC Investigating - We’ve detected email delivery delays affecting a small number of email service providers. The team is actively investigating to identify the full scope and impact. The incident is being tracked in https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23061 October 1, 2026 00:51 UTC Investigating - We are escalating this issue directly with our email delivery provider. The team continues to monitor the impact and will provide another update as more information becomes available. The incident is being tracked in https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23061 October 1, 2026 02:06 UTC Investigating - We are continuing to escalate with our email delivery provider, and other affected email service providers directly. The team continues to monitor the impact and will provide another update as more information becomes available. The incident is being tracked in https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23061 October 1, 2026 03:42 UTC Investigating - We have taken additional measures to reduce elevated email volumes and improve platform stability. The team continues to monitor the impact and will provide another update as more information becomes available. The incident is being tracked in https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23061 October 1, 2026 06:51 UTC Investigating - Our monitoring has not observed any bounced emails since 02:29 UTC. We are seeing early signs of improvement in email delivery, but some messages may continue to be delayed or fail for certain email service providers. The team continues to monitor delivery performance and work with our email delivery provider to understand and address the issue. We will provide another update as more information becomes available. October 1, 2026 08:49 UTC Monitoring - There were no new bounced emails since 02:29 UTC. We will continue to monitor the logs and provide updates when new information is available. October 1, 2026 12:12 UTC Resolved - We have not seen new failures, so we are marking this as solved. More information is available in gitlab.com/gitlab-com/gl-infra/production/-/work_items/23061.

September 29, 2026 18:15 UTC Investigating - Security and vulnerability reports are not loading or being ingested for some users. We are investigating now. For more info: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23024 September 29, 2026 18:36 UTC Identified - We've identified the cause and are working on mitigation. More info: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23024 September 29, 2026 19:06 UTC Monitoring - The mitigation we implemented is reducing the backlog of events. We are now monitoring the situation, see also: gitlab.com/gitlab-com/gl-infra/production/-/work_items/23024 September 29, 2026 20:01 UTC Monitoring - We continue to see improvements across our graphs, see also: gitlab.com/gitlab-com/gl-infra/production/-/work_items/23024 September 29, 2026 21:12 UTC Monitoring - We continue to see improvements across our graphs and reduced backlog, more info: gitlab.com/gitlab-com/gl-infra/production/-/work_items/23024 September 29, 2026 22:29 UTC Monitoring - Monitoring continues. A backlog of ingestion events is currently being processed, which we expect will take some time. We will keep posting updates as we have them. See: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23024 September 30, 2026 00:02 UTC Monitoring - Monitoring continues. A backlog of ingestion events is currently being processed, which we expect will take some time. See: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23024 September 30, 2026 07:19 UTC Monitoring - No material updates to report. We are continuing to monitor the report-ingestion backlog and working on mitigation. More info: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23024 September 30, 2026 09:17 UTC Monitoring - No material updates to report. We are continuing to monitor the report-ingestion backlog and working on mitigation. More info: gitlab.com/gitlab-com/gl-infra/production/-/work_items/23024 September 30, 2026 12:26 UTC Resolved - We observed that the backlog of jobs have been processed and new reports should be coming in on the normal schedule. With this update the incident is resolved. More info: gitlab.com/gitlab-com/gl-infra/production/-/work_items/23024

September 25, 2026 18:39 UTC Identified - Some users are not able to generate security reports in pipelines. We've indetified the cause and are working on mitigation. More info: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23024 September 25, 2026 19:08 UTC Identified - No material updates at this time. Mitigation efforts are ongoing. More info: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23024 September 25, 2026 19:36 UTC Identified - The team is still working on the fix. More info: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23024 September 25, 2026 20:09 UTC Identified - A fix is being implemented and we will update here once it's complete. More info: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23024 September 25, 2026 20:45 UTC Identified - The changes we've tried have so far been ineffective. The fix is still in progress. More info: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23024 September 25, 2026 21:18 UTC Identified - The team is still working on the fix. More info: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23024 September 25, 2026 21:54 UTC Identified - The fix is still being implemented and progress is being made on resolving the problem. More info: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23024 September 25, 2026 22:26 UTC Identified - The team continues to work on mitigating the underlying cause of the issue. More info: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23024 September 25, 2026 23:01 UTC Monitoring - The fix has been deployed and we're seeing our graphs return to normal. Users should no longer be seeing missing security reports. We'll continue to monitor for now. More info: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23024 September 25, 2026 23:56 UTC Resolved - Graphs continue to drop and security report functionality should now be normal. We're resolving this incident. If you have further issues with security reports, please contact support. More info: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23024

September 24, 2026 23:02 UTC Investigating - We are recieving reports of 503 errors on GitLab.com. This is under active investigation. We will update with more details shortly. September 24, 2026 23:04 UTC Investigating - We are recieving reports of 503 errors on GitLab.com. This is under active investigation. We will update with more details shortly. September 24, 2026 23:27 UTC Identified - We've identified the cause of 503 errors on GitLab.com and are working on mitigating the issue. We will update with more details shortly. September 24, 2026 23:39 UTC Identified - We've identified the cause of 503 errors on GitLab.com and are working on mitigating the issue. We're aware that the API is also affected. We will update with more details shortly. September 24, 2026 23:44 UTC Identified - We are seeing some recovery based on our mitigation efforts, which are ongoing. We will update with more details shortly. September 25, 2026 00:01 UTC Identified - We are seeing some recovery based on our mitigation efforts, which are ongoing. We will update with more details shortly. September 25, 2026 00:19 UTC Identified - Error rate is decreasing after active mitigation efforts. We're still actively working on addressing the root cause. We will update with more details shortly. September 25, 2026 00:31 UTC Identified - Error rate is decreasing after active mitigation efforts. We're still actively working on addressing the root cause. We will update with more details shortly. September 25, 2026 00:41 UTC Identified - Error rates are decreasing, but some customers may still see errors. We are continuing to address the remaining impact and will update again soon. September 25, 2026 01:02 UTC Identified - Error rates are decreasing, but some customers may still see errors. We are continuing to address the remaining impact and will update again soon. September 25, 2026 01:43 UTC Identified - GitLab remains stable and error rates have decreased. We are still actively engaging in recovery efforts. September 25, 2026 02:03 UTC Monitoring - GitLab services are now operational and we're continuing to monitor the situation. We are assessing any outstanding impacts during the disruption window. September 25, 2026 02:34 UTC Monitoring - GitLab services are operational and we're continuing to monitor the situation. We are assessing any outstanding impacts during the disruption window. September 25, 2026 03:36 UTC Monitoring - GitLab services are operational and we're continuing to monitor the situation. We are assessing any outstanding impacts during the disruption window. September 25, 2026 04:37 UTC Resolved - This incident has been resolved. GitLab.com is operating normally, and we are continuing to monitor the service.

September 24, 2026 13:48 UTC Investigating - We have received reports that some users are unable to access projects and are encountering 500 error messages. Our team is currently investigating the cause. You can follow developments here: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23015 September 24, 2026 14:10 UTC Investigating - A temporary mitigation has been implemented however the cause of the incident is still being investigated. September 24, 2026 14:44 UTC Investigating - The incident team is continuing to investigate the issue to identify its root cause and implement an appropriate resolution. September 24, 2026 15:17 UTC Investigating - The incident team continues to investigate the cause of this incident. In the meantime, we are seeing intermittent improvements in the ability to access projects. September 24, 2026 16:13 UTC Investigating - No material updates at this time. We are continuing our investigation. More information: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23015 September 24, 2026 17:21 UTC Investigating - We're continuing our investigation. More information: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23015 September 24, 2026 18:32 UTC Identified - The team has identified the potential cause of the spike in 500 errors and is working on the fix. More information: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23015 September 24, 2026 20:03 UTC Identified - The team is still working on the fix. More information: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23015 September 24, 2026 20:50 UTC Resolved - We're no longer seeing elevated errors, so we are resolving this incident. If you continue to experience any errors on GitLab.com, please open a ticket. More information: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23015