GitLab Outage History
GitLab is up right nowPingoru has recorded 75 incidents for GitLab: 75 in the last 12 months and 37 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 2 | 4 of 720 (1%) |
| May 2026 | 13 | 132 of 744 (18%) |
| June 2026 | 11 | 56 of 720 (8%) |
| July 2026 | 7 | 65 of 744 (9%) |
| August 2026 | 13 | 75 of 744 (10%) |
| September 2026 | 11 | 83 of 720 (12%) |
| October 2026 | 16 | 150 of 744 (20%) |
| November 2026 | 2 | 6 of 99 (6%) |
Incidents, newest first
Minor November 3, 2026 Issues Running Pipelines 1h 30m CI/CD, CI/CD (CI/CD — Google Compute Engine)
Started Nov 03, 2026, 05:20 PM UTC· resolved Nov 03, 2026, 06:51 PM UTC
- investigating Nov 03, 2026, 05:20 PM UTC
We're investigating reports of customers being unable to run pipelines on GitLab.com without encountering Gitaly-related errors. Details in https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23401.
- investigating Nov 03, 2026, 05:52 PM UTC
We’re continuing to investigate this issue and don’t have any new information to share at this time. Our team is working to identify the cause, and we’ll provide another update within an hour.
- monitoring Nov 03, 2026, 06:20 PM UTC
We’re seeing recovery, and CI/CD pipelines should be running normally again. We’re continuing to monitor to confirm the issue doesn’t return while we investigate the root cause.
- resolved Nov 03, 2026, 06:51 PM UTC
This incident is now resolved, as we didn’t see the issue return during our monitoring period and CI/CD pipelines are running normally. We’re continuing to investigate the root cause internally with details in https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23401.
Minor November 3, 2026 Elevated CI/CD latency on GitLab.com 4h 45m CI/CD, CI/CD (CI/CD — Google Compute Engine)
Started Nov 03, 2026, 05:06 AM UTC· resolved Nov 03, 2026, 09:51 AM UTC
- investigating Nov 03, 2026, 05:06 AM UTC
We're investigating elevated latency affecting CI/CD on GitLab.com. No user impact has been observed at this time. We'll update as we learn more.
- investigating Nov 03, 2026, 05:27 AM UTC
Some users may have seen intermittent slowness with CI/CD jobs, including slower job updates and artifact uploads. Latency is recovering and we're continuing to investigate.
- identified Nov 03, 2026, 06:01 AM UTC
We've identified a contributing factor to intermittent slowness affecting CI/CD on GitLab.com, including slower job requests, job updates and artifact uploads. We're still investigating the root cause and working to mitigate the issue.
- monitoring Nov 03, 2026, 07:10 AM UTC
We've applied a mitigation for the intermittent slowness affecting CI/CD on GitLab.com, and performance has returned to normal. We're monitoring to make sure the issue doesn't recur.
- monitoring Nov 03, 2026, 08:14 AM UTC
We continue to monitor the incident to ensure the issue doesn't recur. Find more information about the incident here: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23392
- resolved Nov 03, 2026, 09:51 AM UTC
After continuous monitoring, the latency has returned to baseline. We're marking this incident resolved. Find more information about the incident here: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23392
Minor October 23, 2026 General slowness on Gitlab.com 31m Website, Website (Website — Google Compute Engine), Git Operations, Git Operations (Git Operations — Google Compute Engine)
Started Oct 23, 2026, 04:32 PM UTC· resolved Oct 23, 2026, 05:04 PM UTC
- monitoring Oct 23, 2026, 04:32 PM UTC
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
- resolved Oct 23, 2026, 05:04 PM UTC
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.
Major October 20, 2026 404s on customers.gitlab.com 3h 24m GitLab Customers Portal, GitLab Customers Portal (GitLab Customers Portal — Google Compute Engine)
Started Oct 20, 2026, 09:56 PM UTC· resolved Oct 21, 2026, 01:21 AM UTC
- investigating Oct 20, 2026, 09:56 PM UTC
We've investigating 404s on the customers panel. We'll update as we learn more
- investigating Oct 20, 2026, 10:47 PM UTC
We’re continuing our investigation of 404s on the customers panel. We’ll update you as we learn more.
- investigating Oct 20, 2026, 11:15 PM UTC
We’re continuing our investigation of 404s on the customers panel. We’ll update you as we learn more.
- monitoring Oct 20, 2026, 11:51 PM UTC
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.
- resolved Oct 21, 2026, 01:21 AM UTC
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
Minor October 20, 2026 Intermittent 500 on GitLab.com 2h 46m Website, Website (Website — Google Compute Engine)
Started Oct 20, 2026, 07:08 AM UTC· resolved Oct 20, 2026, 09:55 AM UTC
- investigating Oct 20, 2026, 07:08 AM UTC
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
- monitoring Oct 20, 2026, 07:37 AM UTC
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
- monitoring Oct 20, 2026, 07:37 AM UTC
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
- resolved Oct 20, 2026, 09:55 AM UTC
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
Major October 16, 2026 503s on GitLab.com 1h 14m Website, Website (Website — Google Compute Engine), API, API (API — Google Compute Engine) and 43 more
Started Oct 16, 2026, 04:10 PM UTC· resolved Oct 16, 2026, 05:24 PM UTC
- investigating Oct 16, 2026, 04:10 PM UTC
We are investigating the cause of 503s on GitLab.com and the site moving slowly. We will update once we have additional details.
- investigating Oct 16, 2026, 04:25 PM UTC
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
- identified Oct 16, 2026, 04:40 PM UTC
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
- identified Oct 16, 2026, 04:52 PM UTC
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
- monitoring Oct 16, 2026, 05:05 PM UTC
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
- resolved Oct 16, 2026, 05:24 PM UTC
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/23402
Minor October 16, 2026 GitLab.com CI/CD Incident 1h 48m CI/CD, CI/CD (CI/CD — Google Compute Engine)
Started Oct 16, 2026, 11:33 AM UTC· resolved Oct 16, 2026, 01:21 PM UTC
- investigating Oct 16, 2026, 11:33 AM UTC
We’re investigating an issue affecting CI/CD on GitLab.com for a limited number of customers. Pipelines may fail with the following error: “CI configuration fetch from Gitaly timed out. This may indicate Gitaly service slowness or an outage.” More updates to follow.
- monitoring Oct 16, 2026, 12:28 PM UTC
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.
- resolved Oct 16, 2026, 01:21 PM UTC
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.
Minor October 15, 2026 CI/CD Job Delays on GitLab.com 3h 32m CI/CD, CI/CD (CI/CD — Google Compute Engine), CI/CD - Hosted runners on Linux, CI/CD - Hosted runners on Linux (CI/CD - Hosted runners on Linux — Google Compute Engine) and 7 more
Started Oct 15, 2026, 04:18 PM UTC· resolved Oct 15, 2026, 07:50 PM UTC
- investigating Oct 15, 2026, 04:19 PM UTC
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
- identified Oct 15, 2026, 05:23 PM UTC
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
- resolved Oct 15, 2026, 07:50 PM UTC
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
Major October 15, 2026 Error loading GitLab.com and customers.gitlab.com 4h 19m Website, Website (Website — Google Compute Engine), API, API (API — Google Compute Engine) and 2 more
Started Oct 15, 2026, 04:43 AM UTC· resolved Oct 15, 2026, 09:02 AM UTC
- investigating Oct 15, 2026, 04:43 AM UTC
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.
- investigating Oct 15, 2026, 05:10 AM UTC
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.
- investigating Oct 15, 2026, 05:27 AM UTC
No material updates to report. We are still investigating the root cause.
- investigating Oct 15, 2026, 05:50 AM UTC
No material updates to report. We'll share another update when we have more information.
- monitoring Oct 15, 2026, 08:35 AM UTC
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
- resolved Oct 15, 2026, 09:02 AM UTC
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
Minor October 14, 2026 GitLab.com CI/CD pipelines delayed or not starting 3h 57m CI/CD, CI/CD (CI/CD — Google Compute Engine)
Started Oct 14, 2026, 02:33 PM UTC· resolved Oct 14, 2026, 06:30 PM UTC
- investigating Oct 14, 2026, 02:33 PM UTC
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/23190
- investigating Oct 14, 2026, 03:22 PM UTC
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
- investigating Oct 14, 2026, 04:40 PM UTC
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
- identified Oct 14, 2026, 04:50 PM UTC
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
- resolved Oct 14, 2026, 06:30 PM UTC
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
Minor October 13, 2026 Job delays on saas-linux-small-amd64 hosted runners 6h 31m CI/CD, CI/CD (CI/CD — Google Compute Engine), CI/CD - Hosted runners on Linux, CI/CD - Hosted runners on Linux (CI/CD - Hosted runners on Linux — Google Compute Engine)
Started Oct 13, 2026, 02:27 PM UTC· resolved Oct 13, 2026, 08:59 PM UTC
- investigating Oct 13, 2026, 02:27 PM UTC
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
- identified Oct 13, 2026, 03:46 PM UTC
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
- monitoring Oct 13, 2026, 07:31 PM UTC
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.
- resolved Oct 13, 2026, 08:59 PM UTC
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
Major October 13, 2026 Increase of HTTP 50X errors on GitLab.com 1d 16h Website, Website (Website — Google Compute Engine), API, API (API — Google Compute Engine) and 8 more
Started Oct 13, 2026, 07:10 AM UTC· resolved Oct 14, 2026, 11:40 PM UTC
- investigating Oct 13, 2026, 07:10 AM UTC
We are currently investigating reports of an increase of HTTP 50X errors on GitLab.com
- investigating Oct 13, 2026, 07:30 AM UTC
We are seeing an improvement in errors rates in our monitoring, starting from 07:14 UTC. We are still identifying the root cause.
- investigating Oct 13, 2026, 07:48 AM UTC
General GitLab.com service continues to improve. We're now focused on restoring Duo services.
- monitoring Oct 13, 2026, 07:59 AM UTC
We are seeing improvements across all services on GitLab.com. We are resuming our investigation on identifying the root cause.
- monitoring Oct 14, 2026, 02:33 AM UTC
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.
- resolved Oct 14, 2026, 11:40 PM UTC
We have been monitoring this issue for a few days with no reported occurrences.
Minor October 12, 2026 GitLab Duo Workflow Issues 1d 13h GitLab Duo, GitLab Duo (GitLab Duo — Google Compute Engine)
Started Oct 12, 2026, 11:30 AM UTC· resolved Oct 14, 2026, 01:16 AM UTC
- identified Oct 12, 2026, 11:30 AM UTC
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
- identified Oct 12, 2026, 01:37 PM UTC
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
- monitoring Oct 13, 2026, 12:28 AM UTC
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.
- monitoring Oct 13, 2026, 12:29 AM UTC
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.
- identified Oct 13, 2026, 02:11 AM UTC
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.
- resolved Oct 14, 2026, 01:16 AM UTC
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
Minor October 10, 2026 Errors and slow performance on merge requests in the specific groups. 2d 5h Website, Website (Website — Google Compute Engine), API, API (API — Google Compute Engine) and 4 more
Started Oct 10, 2026, 04:49 AM UTC· resolved Oct 12, 2026, 10:15 AM UTC
- investigating Oct 10, 2026, 04:49 AM UTC
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
- monitoring Oct 10, 2026, 06:26 AM UTC
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
- monitoring Oct 10, 2026, 06:27 AM UTC
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
- resolved Oct 12, 2026, 10:15 AM UTC
The issue has been resolved, and systems have returned to normal operation.
Minor October 8, 2026 Delayed job completion 2h 33m CI/CD, CI/CD (CI/CD — Google Compute Engine)
Started Oct 08, 2026, 03:59 PM UTC· resolved Oct 08, 2026, 06:33 PM UTC
- investigating Oct 08, 2026, 03:59 PM UTC
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
- investigating Oct 08, 2026, 04:19 PM UTC
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
- investigating Oct 08, 2026, 04:35 PM UTC
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
- identified Oct 08, 2026, 05:11 PM UTC
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
- identified Oct 08, 2026, 05:34 PM UTC
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
- monitoring Oct 08, 2026, 05:45 PM UTC
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
- resolved Oct 08, 2026, 06:33 PM UTC
After continued monitoring, services remain stable. The incident has been resolved.
Minor October 7, 2026 Job delays on saas-linux-small-amd64 hosted runners 1h 12m CI/CD, CI/CD (CI/CD — Google Compute Engine), CI/CD - Hosted runners on Linux, CI/CD - Hosted runners on Linux (CI/CD - Hosted runners on Linux — Google Compute Engine)
Started Oct 07, 2026, 04:51 PM UTC· resolved Oct 07, 2026, 06:04 PM UTC
- monitoring Oct 07, 2026, 04:51 PM UTC
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
- resolved Oct 07, 2026, 06:04 PM UTC
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
Minor October 1, 2026 Job delays on saas-linux-small-amd64 hosted runners 3h 17m CI/CD, CI/CD (CI/CD — Google Compute Engine), CI/CD - Hosted runners on Linux, CI/CD - Hosted runners on Linux (CI/CD - Hosted runners on Linux — Google Compute Engine)
Started Oct 01, 2026, 06:30 PM UTC· resolved Oct 01, 2026, 09:48 PM UTC
- investigating Oct 01, 2026, 06:30 PM UTC
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.
- monitoring Oct 01, 2026, 06:47 PM UTC
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.
- monitoring Oct 01, 2026, 07:53 PM UTC
Job processing is stable; monitoring continues. Details: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23077
- monitoring Oct 01, 2026, 09:12 PM UTC
No material updates, monitoring continues. Details: gitlab.com/gitlab-com/gl-infra/production/-/work_items/23077
- resolved Oct 01, 2026, 09:48 PM UTC
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
Minor October 1, 2026 Delayed email delivery for some email service providers 11h 36m Background Processing, Background Processing (Background Processing — Google Compute Engine)
Started Oct 01, 2026, 12:35 AM UTC· resolved Oct 01, 2026, 12:12 PM UTC
- investigating Oct 01, 2026, 12:35 AM UTC
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
- investigating Oct 01, 2026, 12:51 AM UTC
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
- investigating Oct 01, 2026, 02:06 AM UTC
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
- investigating Oct 01, 2026, 03:42 AM UTC
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
- investigating Oct 01, 2026, 06:51 AM UTC
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.
- monitoring Oct 01, 2026, 08:49 AM UTC
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.
- resolved Oct 01, 2026, 12:12 PM UTC
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.
Minor September 29, 2026 Security Reports not loading for some users 18h 10m CI/CD, CI/CD (CI/CD — Google Compute Engine)
Started Sep 29, 2026, 06:15 PM UTC· resolved Sep 30, 2026, 12:26 PM UTC
- investigating Sep 29, 2026, 06:15 PM UTC
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
- identified Sep 29, 2026, 06:36 PM UTC
We've identified the cause and are working on mitigation. More info: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23024
- monitoring Sep 29, 2026, 07:06 PM UTC
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
- monitoring Sep 29, 2026, 08:01 PM UTC
We continue to see improvements across our graphs, see also: gitlab.com/gitlab-com/gl-infra/production/-/work_items/23024
- monitoring Sep 29, 2026, 09:12 PM UTC
We continue to see improvements across our graphs and reduced backlog, more info: gitlab.com/gitlab-com/gl-infra/production/-/work_items/23024
- monitoring Sep 29, 2026, 10:29 PM UTC
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
- monitoring Sep 30, 2026, 12:02 AM UTC
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
- monitoring Sep 30, 2026, 07:19 AM UTC
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
- monitoring Sep 30, 2026, 09:17 AM UTC
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
- resolved Sep 30, 2026, 12:26 PM UTC
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
Minor September 25, 2026 Security Reports not loading for some users 5h 16m CI/CD, CI/CD (CI/CD — Google Compute Engine)
Started Sep 25, 2026, 06:39 PM UTC· resolved Sep 25, 2026, 11:56 PM UTC
- identified Sep 25, 2026, 06:39 PM UTC
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
- identified Sep 25, 2026, 07:08 PM UTC
No material updates at this time. Mitigation efforts are ongoing. More info: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23024
- identified Sep 25, 2026, 07:36 PM UTC
The team is still working on the fix. More info: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23024
- identified Sep 25, 2026, 08:09 PM UTC
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
- identified Sep 25, 2026, 08:45 PM UTC
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
- identified Sep 25, 2026, 09:18 PM UTC
The team is still working on the fix. More info: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23024
- identified Sep 25, 2026, 09:54 PM UTC
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
- identified Sep 25, 2026, 10:26 PM UTC
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
- monitoring Sep 25, 2026, 11:01 PM UTC
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
- resolved Sep 25, 2026, 11:56 PM UTC
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
Major September 24, 2026 503s on GitLab.com 5h 34m Website, Website (Website — Google Compute Engine), API, API (API — Google Compute Engine) and 43 more
Started Sep 24, 2026, 11:02 PM UTC· resolved Sep 25, 2026, 04:37 AM UTC
- investigating Sep 24, 2026, 11:02 PM UTC
We are recieving reports of 503 errors on GitLab.com. This is under active investigation. We will update with more details shortly.
- investigating Sep 24, 2026, 11:04 PM UTC
We are recieving reports of 503 errors on GitLab.com. This is under active investigation. We will update with more details shortly.
- identified Sep 24, 2026, 11:27 PM UTC
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.
- identified Sep 24, 2026, 11:39 PM UTC
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.
- identified Sep 24, 2026, 11:44 PM UTC
We are seeing some recovery based on our mitigation efforts, which are ongoing. We will update with more details shortly.
- identified Sep 25, 2026, 12:01 AM UTC
We are seeing some recovery based on our mitigation efforts, which are ongoing. We will update with more details shortly.
- identified Sep 25, 2026, 12:19 AM UTC
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.
- identified Sep 25, 2026, 12:31 AM UTC
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.
- identified Sep 25, 2026, 12:41 AM UTC
Error rates are decreasing, but some customers may still see errors. We are continuing to address the remaining impact and will update again soon.
- identified Sep 25, 2026, 01:02 AM UTC
Error rates are decreasing, but some customers may still see errors. We are continuing to address the remaining impact and will update again soon.
- identified Sep 25, 2026, 01:43 AM UTC
GitLab remains stable and error rates have decreased. We are still actively engaging in recovery efforts.
- monitoring Sep 25, 2026, 02:03 AM UTC
GitLab services are now operational and we're continuing to monitor the situation. We are assessing any outstanding impacts during the disruption window.
- monitoring Sep 25, 2026, 02:34 AM UTC
GitLab services are operational and we're continuing to monitor the situation. We are assessing any outstanding impacts during the disruption window.
- monitoring Sep 25, 2026, 03:36 AM UTC
GitLab services are operational and we're continuing to monitor the situation. We are assessing any outstanding impacts during the disruption window.
- resolved Sep 25, 2026, 04:37 AM UTC
This incident has been resolved. GitLab.com is operating normally, and we are continuing to monitor the service.
Minor September 24, 2026 500 errors while accessing projects 7h 11m Website, Website (Website — Google Compute Engine), Git Operations, Git Operations (Git Operations — Google Compute Engine)
Started Sep 24, 2026, 01:43 PM UTC· resolved Sep 24, 2026, 08:55 PM UTC
- investigating Sep 24, 2026, 01:48 PM UTC
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.
- investigating Sep 24, 2026, 02:10 PM UTC
A temporary mitigation has been implemented however the cause of the incident is still being investigated.
- investigating Sep 24, 2026, 02:44 PM UTC
The incident team is continuing to investigate the issue to identify its root cause and implement an appropriate resolution.
- investigating Sep 24, 2026, 03:17 PM UTC
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.
- investigating Sep 24, 2026, 04:13 PM UTC
No material updates at this time. We are continuing our investigation. More information: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23015
- investigating Sep 24, 2026, 05:21 PM UTC
We're continuing our investigation. More information: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23015
- identified Sep 24, 2026, 06:32 PM UTC
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
- identified Sep 24, 2026, 08:03 PM UTC
The team is still working on the fix. More information: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23015
- resolved Sep 24, 2026, 08:50 PM UTC
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
Minor September 21, 2026 Performance degradation in APAC/Singapore 8h 7m Website, Website (Website — Google Compute Engine), API, API (API — Google Compute Engine) and 8 more
Started Sep 21, 2026, 12:10 PM UTC· resolved Sep 21, 2026, 08:18 PM UTC
- investigating Sep 21, 2026, 12:10 PM UTC
We're experiencing degraded package, artifact, and registry download speed in APAC/Singapore region due to elevated CDN/Cloudflare latency. More details in https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22981.
- investigating Sep 21, 2026, 12:51 PM UTC
We are still investigating the cause for the performance degradation. There are no material updates at the moment. The problem is tracked under https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22981.
- monitoring Sep 21, 2026, 03:17 PM UTC
Cloudflare confirmed the traffic degradation was resolved, with recovery observed at approximately 13:40 UTC. Our application and backend checks remained healthy during the degradation, supporting that the impact was outside the GitLab application stack. We will continue to monitor the situation. More details in gitlab.com/gitlab-com/gl-infra/production/-/work_items/22981.
- monitoring Sep 21, 2026, 05:14 PM UTC
No material updates at this time. We will continue to monitor the situation. More details in gitlab.com/gitlab-com/gl-infra/production/-/work_items/22981.
- monitoring Sep 21, 2026, 06:16 PM UTC
At this time the situation is unchanged. We will continue to monitor. More details in gitlab.com/gitlab-com/gl-infra/production/-/work_items/22981.
- monitoring Sep 21, 2026, 07:16 PM UTC
We're still monitoring this incident. More details in gitlab.com/gitlab-com/gl-infra/production/-/work_items/22981.
- resolved Sep 21, 2026, 08:18 PM UTC
At this time we are resolving this incident. If you continue to experience performance degradation in the Singapore area, please open a support ticket. More details in gitlab.com/gitlab-com/gl-infra/production/-/work_items/22981.
Minor September 17, 2026 Errors Opening Repositories 17h 1m Website, Website (Website — Google Compute Engine), Git Operations, Git Operations (Git Operations — Google Compute Engine)
Started Sep 17, 2026, 08:44 PM UTC· resolved Sep 18, 2026, 01:45 PM UTC
- investigating Sep 17, 2026, 08:44 PM UTC
We're investigating reports of customers unable to open projects, receiving error 500 instead. Details in https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22925.
- investigating Sep 17, 2026, 09:32 PM UTC
No material updates are available at this time. Our team continues to investigate the root cause of the issue.
- identified Sep 17, 2026, 09:56 PM UTC
We’ve identified an abuse vector as the root cause and begun mitigation efforts. Early signs indicate that the service is recovering.
- identified Sep 17, 2026, 11:23 PM UTC
We’re continuing mitigation efforts and have observed some recovery. Customers may still encounter HTTP 500 errors in the UI and during Git operations when accessing certain projects.
- identified Sep 18, 2026, 12:29 AM UTC
We are continuing mitigation and monitoring recovery. Customers may still encounter HTTP 500 errors in the UI and during Git operations for certain projects. We will provide a further update as mitigation progresses.
- investigating Sep 18, 2026, 01:25 AM UTC
Mitigation has not yet fully restored the GitLab UI and Git operations in certain projects. We are still investigating HTTP 500 errors and will provide a further update as more information becomes available.
- investigating Sep 18, 2026, 02:01 AM UTC
Investigation continues. We will shortly be restarting the affected Gitaly node after reconfiguration. Further updates will be provided accordingly.
- investigating Sep 18, 2026, 02:34 AM UTC
The restart of the affected Gitaly node did not improve the issue; HTTP 500 errors continue affecting the GitLab UI and Git operations in certain projects. We are investigating and will provide further updates as the situation changes.
- investigating Sep 18, 2026, 03:02 AM UTC
Further mitigation is being rolled out while we continue to investigate HTTP 500 errors affecting the GitLab UI and Git operations. We will provide further updates as the mitigation progresses.
- investigating Sep 18, 2026, 04:00 AM UTC
A further mitigation change has been applied, and we are assessing its impact. HTTP 500 errors continue affecting the GitLab UI and Git operations in certain projects. Further updates will follow.
- investigating Sep 18, 2026, 06:28 AM UTC
Further mitigation change are currently being applied, and we are continuing to investigate the issue. HTTP 500 errors may continue affecting the GitLab UI and Git operations in certain projects. Further updates will follow.
- investigating Sep 18, 2026, 07:59 AM UTC
We are currently rolling back the deployment of Gitaly. We're waiting for the deploy to land, and we are continuing the investigation.
- monitoring Sep 18, 2026, 09:01 AM UTC
A rollback release has been deployed to all Gitaly nodes. They are stable at present. However, we are continuing to monitor the situation.
- monitoring Sep 18, 2026, 11:07 AM UTC
Gitaly nodes have stabilized following the completed rollback deployment. The incident has been mitigated and we remain focused on continued monitoring.
- resolved Sep 18, 2026, 01:45 PM UTC
The incident has been resolved following the completion of the rollback deployment across the Gitaly nodes. All nodes have returned to a stable state, repository access has been restored. Incident team is currently investigating the root cause.
Minor September 11, 2026 Artifact upload failures and timeouts 13h 32m CI/CD, CI/CD (CI/CD — Google Compute Engine)
Started Sep 11, 2026, 05:50 AM UTC· resolved Sep 11, 2026, 07:22 PM UTC
- investigating Sep 11, 2026, 05:50 AM UTC
We’ve detected issues affecting artifact uploads. The team is actively investigating, and we’ll provide another update as soon as we have findings to share. Thank you for your patience.
- monitoring Sep 11, 2026, 12:16 PM UTC
We are still seeing cases but tat a much less frequent rate. We will continue looking for the root cause and monitor the error rate.
- resolved Sep 11, 2026, 07:22 PM UTC
We are no longer observing elevated error rates and have identified the root cause. We are marking this incident as resolved while we implement additional fixes behind the scenes.