GitLab Outage History

Started Jun 08, 2026, 09:17 AM UTC· resolved Jun 08, 2026, 01:22 PM UTC

1. investigating Jun 08, 2026, 09:17 AM UTC

   The GitLab.com credit dashboard fails to load, displaying the error message: "An error occurred while fetching data". This issue is under investigation. Back to current status Status History Subscribe to receive status updates by email Close Subscribe Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates by webhook Each status update will POST a JSON payload to this URL Email address for managing webhook Close Subscribe Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates in Microsoft Teams Enter your Microsoft Teams webhook. View Instructions Email address for managing subscription Close Subscribe Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates via RSS RSS Feed Close Follow our status updates on Twitter/X @gitlabstatus Close Subscribe to receive status updates in Slack Slack channel ID Find the channel ID: Select the channel in your Slack workspace. The channel ID is displayed in the browser URL. Example: https://app.slack.com/client/T04SJBK1C/ C03SKGJ1P Email address Close Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates via iCalendar iCalendar Feed Close

2. investigating Jun 08, 2026, 09:17 AM UTC

   The GitLab.com credit dashboard fails to load, displaying the error message: "An error occurred while fetching data". This issue is under investigation.

3. monitoring Jun 08, 2026, 12:15 PM UTC

   Mitigation has been applied and GitLab Credits dashboards appear to be loading again. We’ll leave affected components marked as Partial Service Disruption as we monitor error rates closely to ensure the service remains stable.

4. monitoring Jun 08, 2026, 12:15 PM UTC

   Mitigation has been applied and GitLab Credits dashboards appear to be loading again. We’ll leave affected components marked as Partial Service Disruption as we monitor error rates closely to ensure the service remains stable.

5. resolved Jun 08, 2026, 01:22 PM UTC

   GitLab Credits dashboards are operating normally again. The issue has been resolved.

Read the full incident report →

Started Jun 05, 2026, 11:58 AM UTC· resolved Jun 05, 2026, 01:46 PM UTC

1. investigating Jun 05, 2026, 11:58 AM UTC

   We are investigating an issue where CI jobs are not processing. For more info, see: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22256 Back to current status Status History Subscribe to receive status updates by email Close Subscribe Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates by webhook Each status update will POST a JSON payload to this URL Email address for managing webhook Close Subscribe Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates in Microsoft Teams Enter your Microsoft Teams webhook. View Instructions Email address for managing subscription Close Subscribe Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates via RSS RSS Feed Close Follow our status updates on Twitter/X @gitlabstatus Close Subscribe to receive status updates in Slack Slack channel ID Find the channel ID: Select the channel in your Slack workspace. The channel ID is displayed in the browser URL. Example: https://app.slack.com/client/T04SJBK1C/ C03SKGJ1P Email address Close Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates via iCalendar iCalendar Feed Close

2. investigating Jun 05, 2026, 11:58 AM UTC

   We are investigating an issue where CI jobs are not processing. For more info, see: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22256

3. identified Jun 05, 2026, 12:08 PM UTC

   We have identified a recent change as a possible root cause and we are working on rolling back the change. For more info, see: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22256

4. identified Jun 05, 2026, 12:08 PM UTC

   We have identified a recent change as a possible root cause and we are working on rolling back the change. For more info, see: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22256

5. identified Jun 05, 2026, 12:51 PM UTC

   We are still working on rolling back the change that we believe is the root cause. This issue impacts GitLab Hosted Runners and Hosted Runners on Linux. For more info, see: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22256

6. identified Jun 05, 2026, 12:51 PM UTC

   We are still working on rolling back the change that we believe is the root cause. This issue impacts GitLab Hosted Runners and Hosted Runners on Linux. For more info, see: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22256

7. identified Jun 05, 2026, 12:53 PM UTC

   We are still working on rolling back the change that we believe is the root cause. This issue impacts GitLab Hosted Runners and Hosted Runners on Linux. For more info, see: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22256

8. identified Jun 05, 2026, 12:53 PM UTC

   We are still working on rolling back the change that we believe is the root cause. This issue impacts GitLab Hosted Runners and Hosted Runners on Linux. For more info, see: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22256

9. identified Jun 05, 2026, 01:04 PM UTC

   The change has been reverted and we are seeing that error rates are recovering. For more info, see: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22256

10. identified Jun 05, 2026, 01:04 PM UTC

    The change has been reverted and we are seeing that error rates are recovering. For more info, see: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22256

11. monitoring Jun 05, 2026, 01:15 PM UTC

    Error rates have recovered back to normal levels and we started processing jobs again. We expect that the job queue should be processed over the next 30 minutes. For more info, see: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22256

12. monitoring Jun 05, 2026, 01:15 PM UTC

    Error rates have recovered back to normal levels and we started processing jobs again. We expect that the job queue should be processed over the next 30 minutes. For more info, see: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22256

13. resolved Jun 05, 2026, 01:46 PM UTC

    The job queue is now cleared and we do not expect any further customer impact. This is considered resolved. For more info, see: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22256

Read the full incident report →

Started Jun 04, 2026, 04:05 PM UTC· resolved Jun 05, 2026, 07:51 AM UTC

1. investigating Jun 04, 2026, 04:05 PM UTC

   We are investigating an issue where Duo Agent Platform Flows, including Duo Code Review, are not working on some projects. See issue for more info: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22251 Back to current status Status History Subscribe to receive status updates by email Close Subscribe Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates by webhook Each status update will POST a JSON payload to this URL Email address for managing webhook Close Subscribe Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates in Microsoft Teams Enter your Microsoft Teams webhook. View Instructions Email address for managing subscription Close Subscribe Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates via RSS RSS Feed Close Follow our status updates on Twitter/X @gitlabstatus Close Subscribe to receive status updates in Slack Slack channel ID Find the channel ID: Select the channel in your Slack workspace. The channel ID is displayed in the browser URL. Example: https://app.slack.com/client/T04SJBK1C/ C03SKGJ1P Email address Close Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates via iCalendar iCalendar Feed Close

2. investigating Jun 04, 2026, 04:05 PM UTC

   We are investigating an issue where Duo Agent Platform Flows, including Duo Code Review, are not working on some projects. See issue for more info: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22251

3. identified Jun 04, 2026, 04:23 PM UTC

   We have identified the root cause of the recent Duo Agent Platform Flow failures and are deploying a fix. Customers should begin seeing improvements as the deployment completes. For more info: gitlab.com/gitlab-com/gl-infra/production/-/work_items/22251

4. identified Jun 04, 2026, 04:23 PM UTC

   We have identified the root cause of the recent Duo Agent Platform Flow failures and are deploying a fix. Customers should begin seeing improvements as the deployment completes. For more info: gitlab.com/gitlab-com/gl-infra/production/-/work_items/22251

5. identified Jun 04, 2026, 04:52 PM UTC

   We have merged a fix for the Duo Agent Platform Flow failures and it is awaiting deployment. Deployment is expected to take several hours. We will share our next update once the deployment is complete. For more info: gitlab.com/gitlab-com/gl-infra/production/-/work_items/22251

6. identified Jun 04, 2026, 04:52 PM UTC

   We have merged a fix for the Duo Agent Platform Flow failures and it is awaiting deployment. Deployment is expected to take several hours. We will share our next update once the deployment is complete. For more info: gitlab.com/gitlab-com/gl-infra/production/-/work_items/22251

7. monitoring Jun 05, 2026, 05:37 AM UTC

   Error rates have decreased significantly following the fix. We are continuing to monitor the situation. For more info: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22251

8. monitoring Jun 05, 2026, 05:37 AM UTC

   Error rates have decreased significantly following the fix. We are continuing to monitor the situation. For more info: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22251

9. resolved Jun 05, 2026, 07:51 AM UTC

   This issue has been resolved and error rates have returned to normal. For more info: gitlab.com/gitlab-com/gl-infra/production/-/work_items/22251

Read the full incident report →

Started Jun 03, 2026, 02:39 PM UTC· resolved Jun 03, 2026, 05:53 PM UTC

1. investigating Jun 03, 2026, 02:39 PM UTC

   We are investigating an issue where Duo Agent Platform Flows fail to start when used with the default Docker image. For more info, see: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22241 Back to current status Status History Subscribe to receive status updates by email Close Subscribe Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates by webhook Each status update will POST a JSON payload to this URL Email address for managing webhook Close Subscribe Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates in Microsoft Teams Enter your Microsoft Teams webhook. View Instructions Email address for managing subscription Close Subscribe Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates via RSS RSS Feed Close Follow our status updates on Twitter/X @gitlabstatus Close Subscribe to receive status updates in Slack Slack channel ID Find the channel ID: Select the channel in your Slack workspace. The channel ID is displayed in the browser URL. Example: https://app.slack.com/client/T04SJBK1C/ C03SKGJ1P Email address Close Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates via iCalendar iCalendar Feed Close

2. investigating Jun 03, 2026, 02:39 PM UTC

   We are investigating an issue where Duo Agent Platform Flows fail to start when used with the default Docker image. For more info, see: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22241

3. identified Jun 03, 2026, 03:59 PM UTC

   We have identified the issue and we're rolling out a fix to production. Customers should start to see improvement as deployment completes. For more info, see: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22241

4. identified Jun 03, 2026, 03:59 PM UTC

   We have identified the issue and we're rolling out a fix to production. Customers should start to see improvement as deployment completes. For more info, see: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22241

5. resolved Jun 03, 2026, 05:53 PM UTC

   The fix has been deployed, and Duo Agent Platform Flows are working as expected. We will now mark this incident as resolved. For details, see: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22241

Read the full incident report →

Started May 29, 2026, 12:50 PM UTC· resolved May 29, 2026, 11:41 PM UTC

1. investigating May 29, 2026, 12:50 PM UTC

   We're investigating an issue where customers using `@GitLabDuo` mentions in merge requests are receiving access errors. Impact has been reported across GitLab.com, Dedicated, and Self-Managed. Our team is actively investigating. We'll share another update as soon as we have more information. Back to current status Status History Subscribe to receive status updates by email Close Subscribe Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates by webhook Each status update will POST a JSON payload to this URL Email address for managing webhook Close Subscribe Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates in Microsoft Teams Enter your Microsoft Teams webhook. View Instructions Email address for managing subscription Close Subscribe Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates via RSS RSS Feed Close Follow our status updates on Twitter/X @gitlabstatus Close Subscribe to receive status updates in Slack Slack channel ID Find the channel ID: Select the channel in your Slack workspace. The channel ID is displayed in the browser URL. Example: https://app.slack.com/client/T04SJBK1C/ C03SKGJ1P Email address Close Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates via iCalendar iCalendar Feed Close

2. investigating May 29, 2026, 12:50 PM UTC

   We're investigating an issue where customers using `@GitLabDuo` mentions in merge requests are receiving access errors. Impact has been reported across GitLab.com, Dedicated, and Self-Managed. Our team is actively investigating. We'll share another update as soon as we have more information.

3. identified May 29, 2026, 01:33 PM UTC

   We've identified a likely root cause for the `@GitLabDuo` access errors in merge requests and are preparing a revert MR. We'll share another update once it's deployed.

4. identified May 29, 2026, 01:33 PM UTC

   We've identified a likely root cause for the `@GitLabDuo` access errors in merge requests and are preparing a revert MR. We'll share another update once it's deployed.

5. monitoring May 29, 2026, 03:17 PM UTC

   A fix has been deployed via a revert MR. We're moving the incident to Monitoring and will share another update once we can confirm it's fully resolved.

6. monitoring May 29, 2026, 03:17 PM UTC

   A fix has been deployed via a revert MR. We're moving the incident to Monitoring and will share another update once we can confirm it's fully resolved.

7. monitoring May 29, 2026, 05:21 PM UTC

   We are still monitoring the deployed fix. We will share another update once we can confirm it's fully resolved. More info: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22228

8. monitoring May 29, 2026, 05:21 PM UTC

   We are still monitoring the deployed fix. We will share another update once we can confirm it's fully resolved. More info: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22228

9. identified May 29, 2026, 06:58 PM UTC

   After monitoring, our team is still seeing some failures which is prompting additional investigation. While there has been a drop in errors, some users continue to experience issues.

10. identified May 29, 2026, 06:58 PM UTC

    After monitoring, our team is still seeing some failures which is prompting additional investigation. While there has been a drop in errors, some users continue to experience issues.

11. identified May 29, 2026, 08:40 PM UTC

    No material updates at this time. Our team is still seeing some failures which prompted additional investigation. While there has been a drop in errors, some users continue to experience issues.

12. identified May 29, 2026, 08:40 PM UTC

    No material updates at this time. Our team is still seeing some failures which prompted additional investigation. While there has been a drop in errors, some users continue to experience issues.

13. monitoring May 29, 2026, 10:43 PM UTC

    A fix has now been deployed that should remediate the errors. We will continue to monitor, and as long as error rates remain low, we will resolve the incident.

14. monitoring May 29, 2026, 10:43 PM UTC

    A fix has now been deployed that should remediate the errors. We will continue to monitor, and as long as error rates remain low, we will resolve the incident.

15. resolved May 29, 2026, 11:41 PM UTC

    We're no longer seeing errors related to this in the logs, so we are resolving this incident. If you're still experiencing errors when using `@GitLabDuo` mentions in merge requests, please contact support. https://support.gitlab.com

Read the full incident report →

Started May 27, 2026, 07:31 AM UTC· resolved May 27, 2026, 09:55 AM UTC

1. investigating May 27, 2026, 07:31 AM UTC

   We receive report regarding git operation error. Our Gitaly team is investigating the problem. See more detail: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22217 Back to current status Status History Subscribe to receive status updates by email Close Subscribe Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates by webhook Each status update will POST a JSON payload to this URL Email address for managing webhook Close Subscribe Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates in Microsoft Teams Enter your Microsoft Teams webhook. View Instructions Email address for managing subscription Close Subscribe Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates via RSS RSS Feed Close Follow our status updates on Twitter/X @gitlabstatus Close Subscribe to receive status updates in Slack Slack channel ID Find the channel ID: Select the channel in your Slack workspace. The channel ID is displayed in the browser URL. Example: https://app.slack.com/client/T04SJBK1C/ C03SKGJ1P Email address Close Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates via iCalendar iCalendar Feed Close

2. investigating May 27, 2026, 07:31 AM UTC

   We receive report regarding git operation error. Our Gitaly team is investigating the problem. See more detail: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22217

3. investigating May 27, 2026, 08:17 AM UTC

   Our Gitaly team is continuing to investigate the reported Git operation errors. We don't have new information to share at this time, but work is ongoing. Details: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22217

4. investigating May 27, 2026, 08:17 AM UTC

   Our Gitaly team is continuing to investigate the reported Git operation errors. We don't have new information to share at this time, but work is ongoing. Details: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22217

5. investigating May 27, 2026, 08:47 AM UTC

   Investigation into the Git operation errors is ongoing. The team is reviewing logs and has identified a few potential culprits, though we haven't yet confirmed whether any of them are causing the incident. We'll share another update as soon as we have more.

6. investigating May 27, 2026, 08:47 AM UTC

   Investigation into the Git operation errors is ongoing. The team is reviewing logs and has identified a few potential culprits, though we haven't yet confirmed whether any of them are causing the incident. We'll share another update as soon as we have more.

7. monitoring May 27, 2026, 09:27 AM UTC

   We've implemented mitigation rules and are seeing a reduced rate of errors. All signals indicate the incident is resolved. We'll continue monitoring for a bit before marking it as fully resolved.

8. monitoring May 27, 2026, 09:27 AM UTC

   We've implemented mitigation rules and are seeing a reduced rate of errors. All signals indicate the incident is resolved. We'll continue monitoring for a bit before marking it as fully resolved.

9. resolved May 27, 2026, 09:55 AM UTC

   The Git operation errors have been resolved and metrics have returned to normal. Thank you for your patience throughout the incident. Details: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22217

Read the full incident report →

Started May 26, 2026, 04:16 PM UTC· resolved May 26, 2026, 05:21 PM UTC

1. identified May 26, 2026, 04:16 PM UTC

   Some users may see jobs pending while waiting for runners. The team is currently working on the fix. We will update in 30 minutes. More: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22212 Back to current status Status History Subscribe to receive status updates by email Close Subscribe Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates by webhook Each status update will POST a JSON payload to this URL Email address for managing webhook Close Subscribe Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates in Microsoft Teams Enter your Microsoft Teams webhook. View Instructions Email address for managing subscription Close Subscribe Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates via RSS RSS Feed Close Follow our status updates on Twitter/X @gitlabstatus Close Subscribe to receive status updates in Slack Slack channel ID Find the channel ID: Select the channel in your Slack workspace. The channel ID is displayed in the browser URL. Example: https://app.slack.com/client/T04SJBK1C/ C03SKGJ1P Email address Close Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates via iCalendar iCalendar Feed Close

2. identified May 26, 2026, 04:16 PM UTC

   Some users may see jobs pending while waiting for runners. The team is currently working on the fix. We will update in 30 minutes. More: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22212

3. monitoring May 26, 2026, 04:43 PM UTC

   The fix has been deployed. Shared runners should be picking up jobs normally. We will continue to monitor the situation. More: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22212

4. monitoring May 26, 2026, 04:43 PM UTC

   The fix has been deployed. Shared runners should be picking up jobs normally. We will continue to monitor the situation. More: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22212

5. resolved May 26, 2026, 05:21 PM UTC

   The fix has been deployed, and hared runners are picking up jobs normally. We will now mark this incident as resolved. More: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22212

Read the full incident report →

Started May 26, 2026, 12:50 PM UTC· resolved May 26, 2026, 02:25 PM UTC

1. investigating May 26, 2026, 12:50 PM UTC

   We're currently investigating an issue affecting GitLab Duo. Some customers using the Duo Agent Platform (DAP) may be unable to access the service and are seeing a "Usage quota exceeded" error. Our team is actively looking into the cause. Back to current status Status History Subscribe to receive status updates by email Close Subscribe Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates by webhook Each status update will POST a JSON payload to this URL Email address for managing webhook Close Subscribe Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates in Microsoft Teams Enter your Microsoft Teams webhook. View Instructions Email address for managing subscription Close Subscribe Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates via RSS RSS Feed Close Follow our status updates on Twitter/X @gitlabstatus Close Subscribe to receive status updates in Slack Slack channel ID Find the channel ID: Select the channel in your Slack workspace. The channel ID is displayed in the browser URL. Example: https://app.slack.com/client/T04SJBK1C/ C03SKGJ1P Email address Close Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates via iCalendar iCalendar Feed Close

2. investigating May 26, 2026, 12:50 PM UTC

   We're currently investigating an issue affecting GitLab Duo. Some customers using the Duo Agent Platform (DAP) may be unable to access the service and are seeing a "Usage quota exceeded" error. Our team is actively looking into the cause.

3. investigating May 26, 2026, 01:16 PM UTC

   Our team is continuing to investigate the issue affecting GitLab Duo Agent Platform (DAP). We don't have new information to share at this time, but work is ongoing.

4. investigating May 26, 2026, 01:16 PM UTC

   Our team is continuing to investigate the issue affecting GitLab Duo Agent Platform (DAP). We don't have new information to share at this time, but work is ongoing.

5. investigating May 26, 2026, 01:42 PM UTC

   We've identified a feature flag on the Customers Portal as the likely cause of the issue affecting GitLab DAP. The flag has been disabled, and we're monitoring logs and metrics for recovery. Customers may continue to see errors due to cache duration. We'll confirm full resolution in the following updates.

6. investigating May 26, 2026, 01:42 PM UTC

   We've identified a feature flag on the Customers Portal as the likely cause of the issue affecting GitLab DAP. The flag has been disabled, and we're monitoring logs and metrics for recovery. Customers may continue to see errors due to cache duration. We'll confirm full resolution in the following updates.

7. monitoring May 26, 2026, 02:15 PM UTC

   The cache is refreshed for some users, and we've received confirmation from a few customers that DAP is working again for them. We're keeping a close eye on metrics before marking this as fully mitigated.

8. monitoring May 26, 2026, 02:15 PM UTC

   The cache is refreshed for some users, and we've received confirmation from a few customers that DAP is working again for them. We're keeping a close eye on metrics before marking this as fully mitigated.

9. resolved May 26, 2026, 02:25 PM UTC

   All metrics confirm that the issue impacting GitLab Duo Agent Platform (DAP) is fully resolved, and we're marking this incident as closed. We appreciate your patience while we worked through it.

Read the full incident report →

Started May 21, 2026, 09:42 AM UTC· resolved May 21, 2026, 10:29 AM UTC

1. investigating May 21, 2026, 09:42 AM UTC

   We're investigating for the root cause of elevated error rates for webservice. You can follow the progress and updates here: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22182 Back to current status Status History Subscribe to receive status updates by email Close Subscribe Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates by webhook Each status update will POST a JSON payload to this URL Email address for managing webhook Close Subscribe Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates in Microsoft Teams Enter your Microsoft Teams webhook. View Instructions Email address for managing subscription Close Subscribe Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates via RSS RSS Feed Close Follow our status updates on Twitter/X @gitlabstatus Close Subscribe to receive status updates in Slack Slack channel ID Find the channel ID: Select the channel in your Slack workspace. The channel ID is displayed in the browser URL. Example: https://app.slack.com/client/T04SJBK1C/ C03SKGJ1P Email address Close Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates via iCalendar iCalendar Feed Close

2. investigating May 21, 2026, 09:42 AM UTC

   We're investigating for the root cause of elevated error rates for webservice. You can follow the progress and updates here: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22182

3. investigating May 21, 2026, 10:01 AM UTC

   We're still investigating for the root cause of elevated error rates for webservice. Progress and updates can be followed here: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22182

4. investigating May 21, 2026, 10:01 AM UTC

   We're still investigating for the root cause of elevated error rates for webservice. Progress and updates can be followed here: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22182

5. resolved May 21, 2026, 10:29 AM UTC

   We've identified that the scope of impact is limited to gitlab-org. We will continue to investigate this but as we're not seeing impact outside of gitlab-org, we're moving this to an internal incident with the incident issue marked confidential.

Read the full incident report →

Started May 18, 2026, 11:03 AM UTC· resolved May 18, 2026, 12:41 PM UTC

1. identified May 18, 2026, 11:03 AM UTC

   We've identified the root cause of some jobs not getting picked up due to runner pool exhaustion. We're working on getting more runners added to the pool. More details about the incident here: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22145 Back to current status Status History Subscribe to receive status updates by email Close Subscribe Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates by webhook Each status update will POST a JSON payload to this URL Email address for managing webhook Close Subscribe Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates in Microsoft Teams Enter your Microsoft Teams webhook. View Instructions Email address for managing subscription Close Subscribe Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates via RSS RSS Feed Close Follow our status updates on Twitter/X @gitlabstatus Close Subscribe to receive status updates in Slack Slack channel ID Find the channel ID: Select the channel in your Slack workspace. The channel ID is displayed in the browser URL. Example: https://app.slack.com/client/T04SJBK1C/ C03SKGJ1P Email address Close Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates via iCalendar iCalendar Feed Close

2. identified May 18, 2026, 11:03 AM UTC

   We've identified the root cause of some jobs not getting picked up due to runner pool exhaustion. We're working on getting more runners added to the pool. More details about the incident here: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22145

3. monitoring May 18, 2026, 11:35 AM UTC

   We're seeing improvements in job queueing after additional runner allocations to the runner resource pool. We will continue to monitor until the the jobs are getting picked up at normal rates. More details about the incident here: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22145

4. monitoring May 18, 2026, 11:35 AM UTC

   We're seeing improvements in job queueing after additional runner allocations to the runner resource pool. We will continue to monitor until the the jobs are getting picked up at normal rates. More details about the incident here: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22145

5. resolved May 18, 2026, 12:41 PM UTC

   We've continued to monitor the job queues following the additional provisioning of runners to the resource pool and we observe that the queueing is back to normal. This incident is moved to resolved. More details about the incident here: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22145

Read the full incident report →

Started May 15, 2026, 03:37 PM UTC· resolved May 15, 2026, 06:11 PM UTC

1. investigating May 15, 2026, 03:37 PM UTC

   We’re investigating an issue affecting GitLab Duo Agent Platform workflows across GitLab.com, and GitLab Dedicated. Some code review and custom flows may fail or show “Session failed.” More details at https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22135 Back to current status Status History Subscribe to receive status updates by email Close Subscribe Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates by webhook Each status update will POST a JSON payload to this URL Email address for managing webhook Close Subscribe Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates in Microsoft Teams Enter your Microsoft Teams webhook. View Instructions Email address for managing subscription Close Subscribe Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates via RSS RSS Feed Close Follow our status updates on Twitter/X @gitlabstatus Close Subscribe to receive status updates in Slack Slack channel ID Find the channel ID: Select the channel in your Slack workspace. The channel ID is displayed in the browser URL. Example: https://app.slack.com/client/T04SJBK1C/ C03SKGJ1P Email address Close Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates via iCalendar iCalendar Feed Close

2. investigating May 15, 2026, 03:37 PM UTC

   We’re investigating an issue affecting GitLab Duo Agent Platform workflows across GitLab.com, and GitLab Dedicated. Some code review and custom flows may fail or show “Session failed.” More details at https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22135

3. investigating May 15, 2026, 04:07 PM UTC

   We’re continuing to investigate an issue affecting GitLab Duo Agent Platform workflows on GitLab.com and GitLab Dedicated. We have identified a likely cause and are testing a revert. More details at https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22135

4. investigating May 15, 2026, 04:07 PM UTC

   We’re continuing to investigate an issue affecting GitLab Duo Agent Platform workflows on GitLab.com and GitLab Dedicated. We have identified a likely cause and are testing a revert. More details at https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22135

5. identified May 15, 2026, 04:32 PM UTC

   We’ve identified the issue affecting GitLab Duo Agent Platform workflows across GitLab.com, and GitLab Dedicated. Some code review and custom flows may fail or show “Session failed.” We are working on a revert to correct the issue. More details at https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22135

6. identified May 15, 2026, 04:32 PM UTC

   We’ve identified the issue affecting GitLab Duo Agent Platform workflows across GitLab.com, and GitLab Dedicated. Some code review and custom flows may fail or show “Session failed.” We are working on a revert to correct the issue. More details at https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22135

7. identified May 15, 2026, 05:05 PM UTC

   We have identified the cause and have created an MR to revert. We are waiting for that MR to deploy. We will provide further updates once that has merged and deployed. More details at gitlab.com/gitlab-com/gl-infra/production/-/work_items/22135

8. identified May 15, 2026, 05:05 PM UTC

   We have identified the cause and have created an MR to revert. We are waiting for that MR to deploy. We will provide further updates once that has merged and deployed. More details at gitlab.com/gitlab-com/gl-infra/production/-/work_items/22135

9. monitoring May 15, 2026, 05:44 PM UTC

   The revert has been deployed and we are now monitoring the situation. Error rates look to be returning to normal. More details at gitlab.com/gitlab-com/gl-infra/production/-/work_items/22135

10. monitoring May 15, 2026, 05:44 PM UTC

    The revert has been deployed and we are now monitoring the situation. Error rates look to be returning to normal. More details at gitlab.com/gitlab-com/gl-infra/production/-/work_items/22135

11. resolved May 15, 2026, 06:11 PM UTC

    The revert has been merged and deployed and we are seeing error rates return to normal and flows running. This issue has been resolved. More details at gitlab.com/gitlab-com/gl-infra/production/-/work_items/22135

Read the full incident report →

Started May 13, 2026, 04:23 PM UTC· resolved May 13, 2026, 05:33 PM UTC

1. investigating May 13, 2026, 04:23 PM UTC

   We are seeing a high backlog of jobs which may be experienced as slowed pipelines and ci/cd jobs. We will provide more information when it is available. Back to current status Status History Subscribe to receive status updates by email Close Subscribe Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates by webhook Each status update will POST a JSON payload to this URL Email address for managing webhook Close Subscribe Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates in Microsoft Teams Enter your Microsoft Teams webhook. View Instructions Email address for managing subscription Close Subscribe Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates via RSS RSS Feed Close Follow our status updates on Twitter/X @gitlabstatus Close Subscribe to receive status updates in Slack Slack channel ID Find the channel ID: Select the channel in your Slack workspace. The channel ID is displayed in the browser URL. Example: https://app.slack.com/client/T04SJBK1C/ C03SKGJ1P Email address Close Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates via iCalendar iCalendar Feed Close

2. investigating May 13, 2026, 04:23 PM UTC

   We are seeing a high backlog of jobs which may be experienced as slowed pipelines and ci/cd jobs. We will provide more information when it is available.

3. resolved May 13, 2026, 05:33 PM UTC

   The backlogs of jobs has dropped and this issue has been resolved.

Read the full incident report →

Started May 12, 2026, 09:04 PM UTC· resolved May 12, 2026, 09:33 PM UTC

1. investigating May 12, 2026, 09:04 PM UTC

   We are seeing an increase in 5xx errors on GitLab.com and are investigating the issue. User may experience issues on GitLab.com. We will provide updates as we have them. Back to current status Status History Subscribe to receive status updates by email Close Subscribe Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates by webhook Each status update will POST a JSON payload to this URL Email address for managing webhook Close Subscribe Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates in Microsoft Teams Enter your Microsoft Teams webhook. View Instructions Email address for managing subscription Close Subscribe Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates via RSS RSS Feed Close Follow our status updates on Twitter/X @gitlabstatus Close Subscribe to receive status updates in Slack Slack channel ID Find the channel ID: Select the channel in your Slack workspace. The channel ID is displayed in the browser URL. Example: https://app.slack.com/client/T04SJBK1C/ C03SKGJ1P Email address Close Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates via iCalendar iCalendar Feed Close

2. investigating May 12, 2026, 09:04 PM UTC

   We are seeing an increase in 5xx errors on GitLab.com and are investigating the issue. User may experience issues on GitLab.com. We will provide updates as we have them.

3. identified May 12, 2026, 09:22 PM UTC

   We have identified the issue as a frozen Gitaly node and are working to correct the issue.

4. identified May 12, 2026, 09:22 PM UTC

   We have identified the issue as a frozen Gitaly node and are working to correct the issue.

5. resolved May 12, 2026, 09:33 PM UTC

   This issue has resolved and error rates have returned to normal. More information can be found in https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22107

Read the full incident report →

Started May 11, 2026, 08:41 AM UTC· resolved May 11, 2026, 11:16 AM UTC

1. investigating May 11, 2026, 08:41 AM UTC

   We are currently investigating 500 errors when accessing repositories and Gitaly errors when pushing to a repository. More details at https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22041

2. monitoring May 11, 2026, 09:12 AM UTC

   To restore the service, we restarted the Gitaly process. We will monitor for any recurrence. More details at https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22041

3. resolved May 11, 2026, 11:16 AM UTC

   The issue has been resolved. The 500 errors when accessing repositories should not seen anymore and affected Git operations should work as expected. More details at https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22041

Read the full incident report →

Started May 07, 2026, 03:44 PM UTC· resolved May 11, 2026, 11:56 PM UTC

1. investigating May 07, 2026, 03:44 PM UTC

   We are investigating an issue background jobs being processed with delay. The problem is being tracked in https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22017. Back to current status Status History Subscribe to receive status updates by email Close Subscribe Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates by webhook Each status update will POST a JSON payload to this URL Email address for managing webhook Close Subscribe Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates in Microsoft Teams Enter your Microsoft Teams webhook. View Instructions Email address for managing subscription Close Subscribe Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates via RSS RSS Feed Close Follow our status updates on Twitter/X @gitlabstatus Close Subscribe to receive status updates in Slack Slack channel ID Find the channel ID: Select the channel in your Slack workspace. The channel ID is displayed in the browser URL. Example: https://app.slack.com/client/T04SJBK1C/ C03SKGJ1P Email address Close Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates via iCalendar iCalendar Feed Close

2. investigating May 07, 2026, 03:44 PM UTC

   We are investigating an issue background jobs being processed with delay. The problem is being tracked in https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22017.

3. identified May 07, 2026, 04:45 PM UTC

   We have identified the cause of the background job processing delays. We are working to identify mitigating measures.

4. identified May 07, 2026, 04:45 PM UTC

   We have identified the cause of the background job processing delays. We are working to identify mitigating measures.

5. monitoring May 07, 2026, 05:52 PM UTC

   The background job backlog has mostly cleared and merge train delays should be significantly reduced. We're keeping this incident in monitoring while we implement performance improvements. More: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22017

6. monitoring May 07, 2026, 05:52 PM UTC

   The background job backlog has mostly cleared and merge train delays should be significantly reduced. We're keeping this incident in monitoring while we implement performance improvements. More: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22017

7. resolved May 11, 2026, 11:56 PM UTC

   Background job processing has returned to normal and this issue is resolved. More information available at https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22017

Read the full incident report →

Started May 06, 2026, 07:01 PM UTC· resolved May 06, 2026, 08:49 PM UTC

1. identified May 06, 2026, 07:01 PM UTC

   A configuration update may cause some intermittent error messages on GitLab Next (Canary). We have identified the cause and the fix is in progress. More: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22008

2. identified May 06, 2026, 07:44 PM UTC

   The fix is still in progress. For now, the workaround is to use GitLab - Current instead of GitLab - Next. More: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22008

Read the full incident report →

Started Apr 30, 2026, 03:51 PM UTC· resolved Apr 30, 2026, 05:10 PM UTC

1. investigating Apr 30, 2026, 03:51 PM UTC

   We are currently investigating issues with hosted `saas-linux-small-amd64` GitLab runners. More details about this incident can be found in gitlab.com/gitlab-com/gl-infra/production/-/work_items/21936

2. identified Apr 30, 2026, 04:10 PM UTC

   Our team has identified a resource issue that has lead to a delay in pending jobs on Small GitLab Hosted Runners. Users with CI jobs tagged for small runners (saas-linux-small-amd64) might experience some delays. Our team is continuing to work on this.

3. identified Apr 30, 2026, 04:38 PM UTC

   Our team is working on configuration changes to improve resourcing. We're still seeing a job backlog and are continuing to monitor with these changes.

Read the full incident report →

Started Apr 28, 2026, 11:05 AM UTC· resolved Apr 28, 2026, 01:27 PM UTC

1. investigating Apr 28, 2026, 11:05 AM UTC

   We are currently investigating issues with dependency scanning. More details about this incident can be found in `gitlab.com/gitlab-com/gl-infra/production/-/work_items/21905`.

2. identified Apr 28, 2026, 12:02 PM UTC

   We've identified cause of the issue and are working on resolving it. More details can be found in gitlab.com/gitlab-com/gl-infra/production/-/work_items/21905.

Read the full incident report →