GitLab Outage History

Started Aug 25, 2026, 09:59 AM UTC· resolved Aug 26, 2026, 12:12 AM UTC

1. investigating Aug 25, 2026, 09:59 AM UTC

   We are currently investigating reports of slowness and 502 errors. More information here: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22783 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 Aug 25, 2026, 09:59 AM UTC

   We are currently investigating reports of slowness and 502 errors. More information here: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22783

3. investigating Aug 25, 2026, 01:43 PM UTC

   Slowness & 502s have been bursty with not much impact. A revert MR is under way while we are investigating other possible root causes. More information here: gitlab.com/gitlab-com/gl-infra/production/-/work_items/22783

4. investigating Aug 25, 2026, 01:43 PM UTC

   Slowness & 502s have been bursty with not much impact. A revert MR is under way while we are investigating other possible root causes. More information here: gitlab.com/gitlab-com/gl-infra/production/-/work_items/22783

5. monitoring Aug 25, 2026, 02:48 PM UTC

   We have not seen active user impact for several hours and we have identified the possible root cause. We are monitoring for changes. More information here: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22783

6. monitoring Aug 25, 2026, 02:48 PM UTC

   We have not seen active user impact for several hours and we have identified the possible root cause. We are monitoring for changes. More information here: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22783

7. monitoring Aug 25, 2026, 06:34 PM UTC

   We continue to monitor and have not observed any active user impact. We are working towards a permanent fix and will provide our next update once it has been implemented. More information here: gitlab.com/gitlab-com/gl-infra/production/-/work_items/22783

8. monitoring Aug 25, 2026, 06:34 PM UTC

   We continue to monitor and have not observed any active user impact. We are working towards a permanent fix and will provide our next update once it has been implemented. More information here: gitlab.com/gitlab-com/gl-infra/production/-/work_items/22783

9. resolved Aug 26, 2026, 12:12 AM UTC

   The fix has been implemented and the issue is now resolved. We have not observed any active user impact. More information: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22783

Read the full incident report →

Started Aug 24, 2026, 09:22 PM UTC· resolved Aug 24, 2026, 10:45 PM UTC

1. investigating Aug 24, 2026, 09:22 PM UTC

   We are currently investigating reports of deployment failures affecting GitLab Agent for Kubernetes (KAS). Our team is actively looking into the root cause and will provide updates as the investigation progresses. Details in: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22777 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 Aug 24, 2026, 09:22 PM UTC

   We are currently investigating reports of deployment failures affecting GitLab Agent for Kubernetes (KAS). Our team is actively looking into the root cause and will provide updates as the investigation progresses. Details in: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22777

3. identified Aug 24, 2026, 09:37 PM UTC

   We have identified a recent change believed to be contributing to the deployment failures affecting KAS. We are actively reverting this change and will provide an update once complete. Details in: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22777

4. identified Aug 24, 2026, 09:37 PM UTC

   We have identified a recent change believed to be contributing to the deployment failures affecting KAS. We are actively reverting this change and will provide an update once complete. Details in: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22777

5. monitoring Aug 24, 2026, 10:28 PM UTC

   The rollback has been completed and we are actively monitoring to confirm resolution of the deployment failures affecting KAS. Details in: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22777

6. monitoring Aug 24, 2026, 10:28 PM UTC

   The rollback has been completed and we are actively monitoring to confirm resolution of the deployment failures affecting KAS. Details in: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22777

7. resolved Aug 24, 2026, 10:45 PM UTC

   The deployment failures affecting the GitLab Agent for Kubernetes (KAS) have been resolved. Details in: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22777

Read the full incident report →

Started Aug 21, 2026, 03:56 PM UTC· resolved Aug 21, 2026, 04:25 PM UTC

1. monitoring Aug 21, 2026, 03:56 PM UTC

   We're monitoring an incident where 403s were seen across GitLab.com. The fix for this is already in place. More about the incident here: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22762 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. monitoring Aug 21, 2026, 03:56 PM UTC

   We're monitoring an incident where 403s were seen across GitLab.com. The fix for this is already in place. More about the incident here: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22762

3. resolved Aug 21, 2026, 04:25 PM UTC

   The elevated 403 errors affecting GitLab.com have been resolved and error rates have returned to normal levels. More details in: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22762

Read the full incident report →

Started Aug 18, 2026, 01:55 PM UTC· resolved Aug 18, 2026, 05:30 PM UTC

1. investigating Aug 18, 2026, 01:55 PM UTC

   We are investigating an issue causing a subset of requests to GitLab.com receiving 500 errors. We will provide updates as we learn more from our investigation. More information here: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22729 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 Aug 18, 2026, 01:55 PM UTC

   We are investigating an issue causing a subset of requests to GitLab.com receiving 500 errors. We will provide updates as we learn more from our investigation. More information here: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22729

3. investigating Aug 18, 2026, 02:16 PM UTC

   We are still investigating the root cause for 500 errors while fetching commits on GitLab.com. More information here: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22729

4. investigating Aug 18, 2026, 02:16 PM UTC

   We are still investigating the root cause for 500 errors while fetching commits on GitLab.com. More information here: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22729

5. investigating Aug 18, 2026, 02:31 PM UTC

   Investigation for the root cause of 500 errors while fetching commits on GitLab.com is still ongoing. More information here: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22729

6. investigating Aug 18, 2026, 02:31 PM UTC

   Investigation for the root cause of 500 errors while fetching commits on GitLab.com is still ongoing. More information here: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22729

7. monitoring Aug 18, 2026, 02:49 PM UTC

   Our monitoring shows the error rate decreasing towards normal thresholds. We're continuing to monitor the incident. More information here: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22729

8. monitoring Aug 18, 2026, 02:49 PM UTC

   Our monitoring shows the error rate decreasing towards normal thresholds. We're continuing to monitor the incident. More information here: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22729

9. monitoring Aug 18, 2026, 04:11 PM UTC

   The error rate has continued to remain within normal thresholds. We're continuing to monitor the error rate. Further developments can be read here: gitlab.com/gitlab-com/gl-infra/production/-/work_items/22729

10. monitoring Aug 18, 2026, 04:11 PM UTC

    The error rate has continued to remain within normal thresholds. We're continuing to monitor the error rate. Further developments can be read here: gitlab.com/gitlab-com/gl-infra/production/-/work_items/22729

11. resolved Aug 18, 2026, 05:30 PM UTC

    The error rate remains within normal thresholds and the issue is now resolved. Further details: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22729

Read the full incident report →

Started Aug 17, 2026, 07:24 AM UTC· resolved Aug 17, 2026, 01:56 PM UTC

1. investigating Aug 17, 2026, 07:24 AM UTC

   We are currently investigating an issue affecting project and group deletions on GitLab.com. Immediate and scheduled deletion of projects and groups may not complete as expected. Projects and groups that have been scheduled for deletion may remain visible past their expected deletion date. 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 Aug 17, 2026, 07:24 AM UTC

   We are currently investigating an issue affecting project and group deletions on GitLab.com. Immediate and scheduled deletion of projects and groups may not complete as expected. Projects and groups that have been scheduled for deletion may remain visible past their expected deletion date.

3. investigating Aug 17, 2026, 08:18 AM UTC

   We are still investigating the issue affecting project and group deletions on GitLab.com. Immediate and scheduled deletion of projects and groups may not complete as expected. Projects and groups that have been scheduled for deletion may remain visible past their expected deletion date. More information here: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22714

4. investigating Aug 17, 2026, 08:18 AM UTC

   We are still investigating the issue affecting project and group deletions on GitLab.com. Immediate and scheduled deletion of projects and groups may not complete as expected. Projects and groups that have been scheduled for deletion may remain visible past their expected deletion date. More information here: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22714

5. investigating Aug 17, 2026, 08:56 AM UTC

   We are still investigating the issue affecting project and group deletions on GitLab.com. Immediate and scheduled deletion of projects and groups may not complete as expected. Projects and groups that have been scheduled for deletion may remain visible past their expected deletion date. More information here: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22714

6. investigating Aug 17, 2026, 08:56 AM UTC

   We are still investigating the issue affecting project and group deletions on GitLab.com. Immediate and scheduled deletion of projects and groups may not complete as expected. Projects and groups that have been scheduled for deletion may remain visible past their expected deletion date. More information here: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22714

7. investigating Aug 17, 2026, 09:16 AM UTC

   We are still investigating the issue affecting project and group deletions on GitLab.com. Immediate and scheduled deletion of projects and groups may not complete as expected. Ones that have been scheduled for deletion may remain visible past their expected deletion date. More information here: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22714

8. investigating Aug 17, 2026, 09:16 AM UTC

   We are still investigating the issue affecting project and group deletions on GitLab.com. Immediate and scheduled deletion of projects and groups may not complete as expected. Ones that have been scheduled for deletion may remain visible past their expected deletion date. More information here: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22714

9. investigating Aug 17, 2026, 09:37 AM UTC

   We are still investigating the issue affecting project and group deletions on GitLab.com. Immediate and scheduled deletion of projects and groups may not complete as expected. Ones that have been scheduled for deletion may remain visible past their expected deletion date. More information here: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22714

10. investigating Aug 17, 2026, 09:37 AM UTC

    We are still investigating the issue affecting project and group deletions on GitLab.com. Immediate and scheduled deletion of projects and groups may not complete as expected. Ones that have been scheduled for deletion may remain visible past their expected deletion date. More information here: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22714

11. investigating Aug 17, 2026, 09:58 AM UTC

    We are still investigating the issue affecting project and group deletions on GitLab.com. Immediate and scheduled deletion of projects and groups may not complete as expected. Ones that have been scheduled for deletion may remain visible past their expected deletion date. More information here: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22714

12. investigating Aug 17, 2026, 09:58 AM UTC

    We are still investigating the issue affecting project and group deletions on GitLab.com. Immediate and scheduled deletion of projects and groups may not complete as expected. Ones that have been scheduled for deletion may remain visible past their expected deletion date. More information here: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22714

13. investigating Aug 17, 2026, 10:22 AM UTC

    We are still investigating the issue affecting project and group deletions on GitLab.com. Immediate and scheduled deletion of projects and groups may not complete as expected. Ones that have been scheduled for deletion may remain visible past their expected deletion date. More information here: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22714

14. investigating Aug 17, 2026, 10:22 AM UTC

    We are still investigating the issue affecting project and group deletions on GitLab.com. Immediate and scheduled deletion of projects and groups may not complete as expected. Ones that have been scheduled for deletion may remain visible past their expected deletion date. More information here: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22714

15. investigating Aug 17, 2026, 10:44 AM UTC

    We are still investigating the issue affecting project and group deletions on GitLab.com. Immediate and scheduled deletion of projects and groups may not complete as expected. Ones that have been scheduled for deletion may remain visible past their expected deletion date. More information here: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22714

16. investigating Aug 17, 2026, 10:44 AM UTC

    We are still investigating the issue affecting project and group deletions on GitLab.com. Immediate and scheduled deletion of projects and groups may not complete as expected. Ones that have been scheduled for deletion may remain visible past their expected deletion date. More information here: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/2271

17. investigating Aug 17, 2026, 11:02 AM UTC

    We are still investigating the issue affecting project and group deletions on GitLab.com. Immediate and scheduled deletion of projects and groups may not complete as expected. Ones that have been scheduled for deletion may remain visible past their expected deletion date. More information here: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22714

18. investigating Aug 17, 2026, 11:02 AM UTC

    We are still investigating the issue affecting project and group deletions on GitLab.com. Immediate and scheduled deletion of projects and groups may not complete as expected. Ones that have been scheduled for deletion may remain visible past their expected deletion date. More information here: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/2271

19. identified Aug 17, 2026, 11:20 AM UTC

    We've identified a fix for the issue affecting project and group deletions on GitLab.com. Due to routine DB maintenance there will be a delay for when the fix will land in production. Given the current state of a known fix and the known delay, we will post status updates every hour for this incident. More information here: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22714

20. identified Aug 17, 2026, 11:20 AM UTC

    We've identified a fix for the issue affecting project and group deletions on GitLab.com. Due to routine DB maintenance there will be a delay for when the fix will land in production. Given the current state of a known fix and the known delay, we will post status updates every hour for this incident. More information here: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/2271

21. identified Aug 17, 2026, 12:37 PM UTC

    The fix is now in production and we're now working on processing the deletion queue via the deletion workers. The last 4 status updates were missing a "4" infrastructure work item link shared; this has been corrected on the status page. More information here: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22714

22. identified Aug 17, 2026, 12:37 PM UTC

    The fix is now in production and we're now working on processing the deletion queue via the deletion workers. The last 4 status updates were missing a "4" infrastructure work item link shared; this has been corrected on the status page. More information here: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22714

23. monitoring Aug 17, 2026, 01:24 PM UTC

    We're continuing to monitor the deletion queue being processed via the deletion workers. Delay of deletions and visibility of scheduled/queued deletions would be experienced until the queue is cleared. More information here: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22714

24. monitoring Aug 17, 2026, 01:24 PM UTC

    We're continuing to monitor the deletion queue being processed via the deletion workers. Delay of deletions and visibility of scheduled/queued deletions would be experienced until the queue is cleared. More information here: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22714

25. resolved Aug 17, 2026, 01:56 PM UTC

    All deletion queues have been processed for projects, we expect the same to continue for group deletions. This incident is moved to resolved. More information here: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22714

Read the full incident report →

Started Aug 13, 2026, 01:58 PM UTC· resolved Aug 13, 2026, 05:47 PM UTC

1. investigating Aug 13, 2026, 01:58 PM UTC

   We are seeing a growing queue of pending jobs on the saas-linux-medium-arm64 hosted runner on GitLab.com. We are rolling out a mitigation. Details: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22702 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 Aug 13, 2026, 01:58 PM UTC

   We are seeing a growing queue of pending jobs on the saas-linux-medium-arm64 hosted runner on GitLab.com. We are rolling out a mitigation. Details: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22702

3. monitoring Aug 13, 2026, 03:22 PM UTC

   The issue is mitigated and the queue of pending jobs on saas-linux-medium-arm64 is going down. We are monitoring recovery. Details: gitlab.com/gitlab-com/gl-infra/production/-/work_items/22702

4. monitoring Aug 13, 2026, 03:22 PM UTC

   The issue is mitigated and the queue of pending jobs on saas-linux-medium-arm64 is going down. We are monitoring recovery. Details: gitlab.com/gitlab-com/gl-infra/production/-/work_items/22702

5. monitoring Aug 13, 2026, 04:48 PM UTC

   The queue of pending jobs on the affected runners has returned to normal and we are monitoring recovery. Details: gitlab.com/gitlab-com/gl-infra/production/-/work_items/22702

6. monitoring Aug 13, 2026, 04:48 PM UTC

   The queue of pending jobs on the affected runners has returned to normal and we are monitoring recovery. Details: gitlab.com/gitlab-com/gl-infra/production/-/work_items/22702

7. resolved Aug 13, 2026, 05:47 PM UTC

   The queue of pending jobs on the affected runners has returned to normal and has stayed at that level. This incident is now resolved. Please open a ticket with support if you are still seeing job delays. Details: gitlab.com/gitlab-com/gl-infra/production/-/work_items/22702

Read the full incident report →

Started Aug 06, 2026, 02:01 PM UTC· resolved Aug 06, 2026, 04:22 PM UTC

1. investigating Aug 06, 2026, 02:01 PM UTC

   We are investigating an issue affecting background jobs, including webhook delivery and pipelines. For more info, see: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22661 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 Aug 06, 2026, 02:01 PM UTC

   We are investigating an issue affecting background jobs, including webhook delivery and pipelines. For more info, see: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22661

3. identified Aug 06, 2026, 02:26 PM UTC

   We have identified the cause of the issue and we are taking action to mitigate customer impact. For more info, see: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22661

4. identified Aug 06, 2026, 02:26 PM UTC

   We have identified the cause of the issue and we are taking action to mitigate customer impact. For more info, see: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22661

5. resolved Aug 06, 2026, 04:22 PM UTC

   We're seeing consistent background job and webhook delivery. The issue is now resolved.

Read the full incident report →

Started Aug 05, 2026, 10:13 PM UTC· resolved Aug 05, 2026, 11:47 PM UTC

1. investigating Aug 05, 2026, 10:13 PM UTC

   We're investigating reports of pipelines failing and becoming stuck. Details in https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22654. 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 Aug 05, 2026, 10:13 PM UTC

   We're investigating reports of pipelines failing and becoming stuck. Details in https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22654.

3. investigating Aug 05, 2026, 10:39 PM UTC

   We've disabled a worker, which should let the job queue begin recovering while we continue investigating the root cause. Details in https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22654.

4. investigating Aug 05, 2026, 10:39 PM UTC

   We've disabled a worker, which should let the job queue begin recovering while we continue investigating the root cause. Details in https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22654.

5. identified Aug 05, 2026, 11:26 PM UTC

   We've identified a likely root cause, and the job queue has remained healthy. Details in https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22654.

6. identified Aug 05, 2026, 11:26 PM UTC

   We've identified a likely root cause, and the job queue has remained healthy. Details in https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22654.

7. resolved Aug 05, 2026, 11:47 PM UTC

   We've applied mitigations that have stabilized the job queue. The issue is now resolved. Details in https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22654.

Read the full incident report →

Started Aug 04, 2026, 04:42 PM UTC· resolved Aug 05, 2026, 03:19 PM UTC

1. investigating Aug 04, 2026, 04:42 PM UTC

   We are investigating reports of webhook deliveries from GitLab.com originating from IP addresses outside our documented ranges. Details in https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22637. 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 Aug 04, 2026, 04:42 PM UTC

   We are investigating reports of webhook deliveries from GitLab.com originating from IP addresses outside our documented ranges. Details in https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22637.

3. investigating Aug 04, 2026, 06:49 PM UTC

   Our investigation is ongoing. We will provide another update by 21:00 UTC.

4. investigating Aug 04, 2026, 06:49 PM UTC

   Our investigation is ongoing. We will provide another update by 21:00 UTC.

5. identified Aug 04, 2026, 09:07 PM UTC

   We've traced the issue to a recent network change and are preparing a fix. Another update will be provided by 23:00 UTC.

6. identified Aug 04, 2026, 09:07 PM UTC

   We've traced the issue to a recent network change and are preparing a fix. Another update will be provided by 23:00 UTC.

7. identified Aug 04, 2026, 11:14 PM UTC

   Deployment of the fix is progressing steadily. Another update will be provided once deployed. Details in https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22637.

8. identified Aug 04, 2026, 11:14 PM UTC

   Deployment of the fix is progressing steadily. Another update will be provided once deployed. Details in https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22637.

9. monitoring Aug 05, 2026, 03:26 AM UTC

   A fix has been deployed and checks have confirmed that unexpected IP addresses are no longer being used.

10. monitoring Aug 05, 2026, 03:26 AM UTC

    A fix has been deployed and checks have confirmed that unexpected IP addresses are no longer being used.

11. resolved Aug 05, 2026, 03:19 PM UTC

    Webhook delivery failures have subsided in logs, and customer reports indicate no further errors. This incident is considered resolved.

Read the full incident report →

Started Aug 04, 2026, 01:56 PM UTC· resolved Aug 04, 2026, 05:54 PM UTC

1. investigating Aug 04, 2026, 01:56 PM UTC

   We are investigating an issue which may be affecting Duo Code Review Flows. For more info, see: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22633 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 Aug 04, 2026, 01:56 PM UTC

   We are investigating an issue which may be affecting Duo Code Review Flows. For more info, see: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22633

3. identified Aug 04, 2026, 04:30 PM UTC

   We've identified the cause of the issue and have temporarily reverted the default Agentic Chat model to Sonnet 4.6 while we continue to investigate. Details in https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22633.

4. identified Aug 04, 2026, 04:30 PM UTC

   We've identified the cause of the issue and have temporarily reverted the default Agentic Chat model to Sonnet 4.6 while we continue to investigate. Details in https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22633.

5. resolved Aug 04, 2026, 05:54 PM UTC

   Duo Code Review sessions on GitLab.com have returned to normal operation. This issue is now resolved.

Read the full incident report →

Started Aug 03, 2026, 02:31 PM UTC· resolved Aug 04, 2026, 12:07 AM UTC

1. investigating Aug 03, 2026, 02:31 PM UTC

   The team is investigating an issue related to a Gitaly node. Customers may experience errors or slowness when performing git operations. For more info see: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22625 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 Aug 03, 2026, 02:31 PM UTC

   The team is investigating an issue related to a Gitaly node. Customers may experience errors or slowness when performing git operations. For more info see: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22625

3. investigating Aug 03, 2026, 02:59 PM UTC

   Impact is limited to projects on a single Gitaly node. The team is currently focused on relieving pressure from the overloaded Gitaly node to mitigate impact in the affected projects. For more info, see: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22625

4. investigating Aug 03, 2026, 02:59 PM UTC

   Impact is limited to projects on a single Gitaly node. The team is currently focused on relieving pressure from the overloaded Gitaly node to mitigate impact in the affected projects. For more info, see: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22625

5. investigating Aug 03, 2026, 03:57 PM UTC

   The team is still working on actions to mitigate impact from the affected Gitaly node. For more info, see: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22625

6. investigating Aug 03, 2026, 03:57 PM UTC

   The team is still working on actions to mitigate impact from the affected Gitaly node. For more info, see: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22625

7. monitoring Aug 03, 2026, 05:25 PM UTC

   Restarting the affected Gitaly node relieved pressure on it, and error rates have dropped significantly. We're monitoring for continued stability. Details in https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22625.

8. monitoring Aug 03, 2026, 05:25 PM UTC

   Restarting the affected Gitaly node relieved pressure on it, and error rates have dropped significantly. We're monitoring for continued stability. Details in https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22625.

9. resolved Aug 04, 2026, 12:07 AM UTC

   After a period of monitoring we have seen continued Gitaly stability and consider the incident resolved. Details in https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22625.

Read the full incident report →

Started Jul 27, 2026, 08:09 PM UTC· resolved Jul 27, 2026, 09:11 PM UTC

1. investigating Jul 27, 2026, 08:09 PM UTC

   We observed a spike in 5xx errors on GitLab.com. These have subsided, but we are investigating the root 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 Jul 27, 2026, 08:09 PM UTC

   We observed a spike in 5xx errors on GitLab.com. These have subsided, but we are investigating the root cause.

3. monitoring Jul 27, 2026, 08:28 PM UTC

   We have confirmed these errors are no longer occurring. We've identified the cause of this incident and are working to prevent this from occurring in the future. We'll now move this incident to monitoring. Details: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22579

4. resolved Jul 27, 2026, 09:11 PM UTC

   We have continued to observe normal error rates. We will now be marking this incident as resolved. Details surrounding the incident can be seen here: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22579

Read the full incident report →

Started Jul 22, 2026, 09:47 PM UTC· resolved Jul 24, 2026, 03:50 AM UTC

1. investigating Jul 22, 2026, 09:47 PM UTC

   We are currently receiving reports and investigating issues with signing into GitLab.com. We will provide more information once 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 Jul 22, 2026, 09:47 PM UTC

   We are currently receiving reports and investigating issues with signing into GitLab.com. We will provide more information once it is available.

3. monitoring Jul 22, 2026, 11:08 PM UTC

   We are still monitoring the situation with possible issues logging into GitLab.com and will provide further updates when they are available.

4. monitoring Jul 22, 2026, 11:08 PM UTC

   We are still monitoring the situation with possible issues logging into GitLab.com and will provide further updates when they are available.

5. monitoring Jul 23, 2026, 12:49 AM UTC

   We're aware of previous login problems for GitLab.com and are monitoring the situation. For details: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22551

6. monitoring Jul 23, 2026, 12:49 AM UTC

   We're aware of previous login problems for GitLab.com and are monitoring the situation. For details: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22551

7. resolved Jul 24, 2026, 03:50 AM UTC

   Earlier login problems have been resolved and logins are working normally again. This incident is now considered closed. Details: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22551

Read the full incident report →

Started Jul 17, 2026, 04:10 PM UTC· resolved Jul 17, 2026, 05:36 PM UTC

1. investigating Jul 17, 2026, 04:10 PM UTC

   We're investigating an issue affecting GitLab Duo Custom Agents on GitLab.com. Our team is actively working to identify the cause and restore normal service. 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 Jul 17, 2026, 04:10 PM UTC

   We're investigating an issue affecting GitLab Duo Custom Agents on GitLab.com. Our team is actively working to identify the cause and restore normal service.

3. investigating Jul 17, 2026, 04:26 PM UTC

   Our team is actively investigating the root cause of this issue. We'll continue to share updates as we learn more.

4. investigating Jul 17, 2026, 04:26 PM UTC

   Our team is actively investigating the root cause of this issue. We'll continue to share updates as we learn more.

5. investigating Jul 17, 2026, 04:44 PM UTC

   We continue to investigate the root cause of this issue. There are no material updates at this time, and we'll share additional information as it becomes available.

6. investigating Jul 17, 2026, 04:44 PM UTC

   We continue to investigate the root cause of this issue. There are no material updates at this time, and we'll share additional information as it becomes available.

7. investigating Jul 17, 2026, 05:09 PM UTC

   We're seeing signs of recovery, but our investigation into the root cause remains ongoing. We'll continue to provide updates as more information becomes available.

8. investigating Jul 17, 2026, 05:09 PM UTC

   We're seeing signs of recovery, but our investigation into the root cause remains ongoing. We'll continue to provide updates as more information becomes available.

9. monitoring Jul 17, 2026, 05:22 PM UTC

   We're seeing service recover and error rates return to expected levels. We'll continue to monitor the environment to ensure the recovery is sustained.

10. monitoring Jul 17, 2026, 05:22 PM UTC

    We're seeing service recover and error rates return to expected levels. We'll continue to monitor the environment to ensure the recovery is sustained.

11. resolved Jul 17, 2026, 05:36 PM UTC

    We've identified and mitigated the root cause of this issue. Service has remained stable throughout the monitoring period, and this incident is now resolved.

Read the full incident report →

Started Jul 15, 2026, 02:12 PM UTC· resolved Jul 15, 2026, 09:29 PM UTC

1. identified Jul 15, 2026, 02:12 PM UTC

   We are investigating degraded performance affecting package pulls from our registry. Users may experience slow or failed Omnibus package downloads while we investigate. Currently, the engineering team has identified the cause of the degraded performance and is currently working to resolve the issue. Users may continue to experience slow or failed Omnibus package downloads while mitigation is in progress. 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 Jul 15, 2026, 02:12 PM UTC

   We are investigating degraded performance affecting package pulls from our registry. Users may experience slow or failed Omnibus package downloads while we investigate. Currently, the engineering team has identified the cause of the degraded performance and is currently working to resolve the issue. Users may continue to experience slow or failed Omnibus package downloads while mitigation is in progress.

3. identified Jul 15, 2026, 03:33 PM UTC

   We continue to work on resolving the issue with package pulls from our registry. Users may still experience slow or failed Omnibus package downloads. We will share another update as soon as we have more information.

4. identified Jul 15, 2026, 03:33 PM UTC

   We continue to work on resolving the issue with package pulls from our registry. Users may still experience slow or failed Omnibus package downloads. We will share another update as soon as we have more information.

5. identified Jul 15, 2026, 04:21 PM UTC

   Work to resolve the package registry issue is ongoing. During this time, some users may continue to experience slow or unsuccessful Omnibus package downloads.

6. identified Jul 15, 2026, 04:21 PM UTC

   Work to resolve the package registry issue is ongoing. During this time, some users may continue to experience slow or unsuccessful Omnibus package downloads.

7. identified Jul 15, 2026, 04:54 PM UTC

   Recovery efforts remain in progress for the issue impacting package pulls from our registry. Some Omnibus package downloads may continue to be slow or fail until the issue is resolved.

8. identified Jul 15, 2026, 04:54 PM UTC

   Recovery efforts remain in progress for the issue impacting package pulls from our registry. Some Omnibus package downloads may continue to be slow or fail until the issue is resolved.

9. identified Jul 15, 2026, 05:25 PM UTC

   No material updates to report at this time. We are continuing to investigate the current issue and engineers are working to determine remediation steps.

10. identified Jul 15, 2026, 05:25 PM UTC

    No material updates to report at this time. We are continuing to investigate the current issue and engineers are working to determine remediation steps.

11. identified Jul 15, 2026, 06:19 PM UTC

    Mitigation efforts are ongoing to address the issue affecting package pulls from our registry. Slow or failed Omnibus package downloads may still occur.

12. identified Jul 15, 2026, 06:19 PM UTC

    Mitigation efforts are ongoing to address the issue affecting package pulls from our registry. Slow or failed Omnibus package downloads may still occur.

13. identified Jul 15, 2026, 06:57 PM UTC

    We've identified the root cause of the issue and are continuing to implement mitigation measures. We'll provide additional updates as progress is made.

14. identified Jul 15, 2026, 06:57 PM UTC

    We've identified the root cause of the issue and are continuing to implement mitigation measures. We'll provide additional updates as progress is made.

15. identified Jul 15, 2026, 07:36 PM UTC

    We have no material updates at this time. Our team remains focused on mitigation efforts and will continue to share updates as we make progress.

16. identified Jul 15, 2026, 07:36 PM UTC

    We have no material updates at this time. Our team remains focused on mitigation efforts and will continue to share updates as we make progress.

17. identified Jul 15, 2026, 08:12 PM UTC

    There are no significant updates to share at this time. Mitigation efforts are still underway, and we will continue to provide updates as they become available.

18. identified Jul 15, 2026, 08:12 PM UTC

    There are no significant updates to share at this time. Mitigation efforts are still underway, and we will continue to provide updates as they become available.

19. identified Jul 15, 2026, 08:44 PM UTC

    Mitigation efforts remain in progress. We're continuing to monitor the implementation and will provide another update once additional progress has been made.

20. identified Jul 15, 2026, 08:44 PM UTC

    Mitigation efforts remain in progress. We're continuing to monitor the implementation and will provide another update once additional progress has been made.

21. resolved Jul 15, 2026, 09:29 PM UTC

    Mitigation efforts have been successfully completed, and service has returned to normal. This incident has been resolved.

Read the full incident report →

Started Jul 14, 2026, 10:47 PM UTC· resolved Jul 15, 2026, 12:47 AM UTC

1. investigating Jul 14, 2026, 10:47 PM UTC

   We're aware of elevated errors affecting AI Gateway health checks. We've identified a likely cause and are actively working on a fix. Details in: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22519 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 Jul 14, 2026, 10:47 PM UTC

   We're aware of elevated errors affecting AI Gateway health checks. We've identified a likely cause and are actively working on a fix. Details in: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22519

3. identified Jul 14, 2026, 11:02 PM UTC

   We have identified the problematic change causing this behavior and are working to revert it. Details will be shared in: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22519

4. identified Jul 14, 2026, 11:02 PM UTC

   We have identified the problematic change causing this behavior and are working to revert it. Details will be shared in: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22519

5. identified Jul 14, 2026, 11:37 PM UTC

   We're continuing to work on reverting the change causing this issue. Details will be shared in: gitlab.com/gitlab-com/gl-infra/production/-/work_items/22519

6. identified Jul 14, 2026, 11:37 PM UTC

   We're continuing to work on reverting the change causing this issue. Details will be shared in: gitlab.com/gitlab-com/gl-infra/production/-/work_items/22519

7. identified Jul 15, 2026, 12:00 AM UTC

   The revert remains in progress. Additional updates will be shared in: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22519

8. identified Jul 15, 2026, 12:00 AM UTC

   The revert remains in progress. Additional updates will be shared in: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22519

9. monitoring Jul 15, 2026, 12:24 AM UTC

   Deployment for the revert has reached production. Manual verification is successful with error rates trending down. We are continuing to monitor. Details: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22519

10. monitoring Jul 15, 2026, 12:24 AM UTC

    Deployment for the revert has reached production. Manual verification is successful with error rates trending down. We are continuing to monitor. Details: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22519

11. monitoring Jul 15, 2026, 12:37 AM UTC

    We are monitoring the situation to ensure that services have returned to normal. Details: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22519

12. monitoring Jul 15, 2026, 12:37 AM UTC

    We are monitoring the situation to ensure that services have returned to normal. Details: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22519

13. resolved Jul 15, 2026, 12:47 AM UTC

    We are seeing error rates return to normal. This issue has been resolved. Details at https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22519

Read the full incident report →

Started Jul 07, 2026, 05:47 PM UTC· resolved Jul 08, 2026, 03:59 PM UTC

1. identified Jul 07, 2026, 05:47 PM UTC

   We've discovered that attempts to delete newly created MR approval rules may fail in certain cases. The cause has been identified and the fix is in the works. More: https://gitlab.com/gitlab-org/gitlab/-/work_items/605117 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 Jul 07, 2026, 05:47 PM UTC

   We've discovered that attempts to delete newly created MR approval rules may fail in certain cases. The cause has been identified and the fix is in the works. More: https://gitlab.com/gitlab-org/gitlab/-/work_items/605117

3. identified Jul 07, 2026, 05:48 PM UTC

   We've discovered that attempts to delete newly created MR approval rules may fail in certain cases. The cause has been identified and the fix is in the works. More: gitlab.com/gitlab-org/gitlab/-/work_items/605117

4. identified Jul 07, 2026, 05:48 PM UTC

   We've discovered that attempts to delete newly created MR approval rules may fail in certain cases. The cause has been identified and the fix is in the works. More: gitlab.com/gitlab-org/gitlab/-/work_items/605117

5. identified Jul 07, 2026, 06:35 PM UTC

   The fix is still in progress, no updates at this time. More: https://gitlab.com/gitlab-org/gitlab/-/work_items/605117

6. identified Jul 07, 2026, 06:35 PM UTC

   The fix is still in progress, no updates at this time. More: https://gitlab.com/gitlab-org/gitlab/-/work_items/605117

7. identified Jul 07, 2026, 07:29 PM UTC

   A merge request fix has been created and is currently being worked on. We will update as the situation changes. More: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22470

8. identified Jul 07, 2026, 07:29 PM UTC

   A merge request fix has been created and is currently being worked on. We will update as the situation changes. More: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22470

9. identified Jul 07, 2026, 08:00 PM UTC

   No updates at this time. A merge request fix has been created and is currently being worked on. More: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22470

10. identified Jul 07, 2026, 08:00 PM UTC

    No updates at this time. A merge request fix has been created and is currently being worked on. More: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22470

11. identified Jul 07, 2026, 08:42 PM UTC

    No further updates at this time. The merge request is in progress. More: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22470

12. identified Jul 07, 2026, 08:42 PM UTC

    No further updates at this time. The merge request is in progress. More: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22470

13. identified Jul 07, 2026, 10:40 PM UTC

    The fix will merge as soon as it's pipeline completes. The status will change to monitoring at that time. More: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22470

14. identified Jul 07, 2026, 10:40 PM UTC

    The fix will merge as soon as it's pipeline completes. The status will change to monitoring at that time. More: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22470

15. monitoring Jul 07, 2026, 11:02 PM UTC

    The fix has been merged and we are now monitoring. If you still experience the issues, please open a ticket with support. More: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22470

16. monitoring Jul 07, 2026, 11:02 PM UTC

    The fix has been merged and we are now monitoring. If you still experience the issues, please open a ticket with support. More: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22470

17. resolved Jul 08, 2026, 03:59 PM UTC

    The fix has been completed in production. This incident is now resolve. More: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22470

Read the full incident report →

Started Jul 01, 2026, 01:14 PM UTC· resolved Jul 01, 2026, 02:04 PM UTC

1. investigating Jul 01, 2026, 01:14 PM UTC

   We are currently investigating the cause of CI pipelines being stuck in pending state. More details can be found here: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22433 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 Jul 01, 2026, 01:14 PM UTC

   We are currently investigating the cause of CI pipelines being stuck in pending state. More details can be found here: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22433

3. investigating Jul 01, 2026, 01:58 PM UTC

   We are continuing to investigate and look into CI pipelines being stuck in pending state.

4. investigating Jul 01, 2026, 01:58 PM UTC

   We are continuing to investigate and look into CI pipelines being stuck in pending state.

5. resolved Jul 01, 2026, 02:04 PM UTC

   Incident has now been mitigated. CI pipelines are now resuming. Engineers will continue to monitor this recovery.

Read the full incident report →

Started Jun 30, 2026, 09:53 PM UTC· resolved Jun 30, 2026, 11:59 PM UTC

1. investigating Jun 30, 2026, 09:53 PM UTC

   We are investigating errors with code suggestion not completing. 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 30, 2026, 09:53 PM UTC

   We are investigating errors with code suggestion not completing.

3. investigating Jun 30, 2026, 10:08 PM UTC

   We are continuing to investigate the issue, but it appears to be isolated to specific models and we recommend for the time being switching to Claude Sonnet 4.5 for code completion while we continue to investigate the matter. Details on how to do that can be found at https://docs.gitlab.com/user/gitlab_duo/model_selection/#select-a-model-for-a-feature

4. investigating Jun 30, 2026, 10:08 PM UTC

   We are continuing to investigate the issue, but it appears to be isolated to specific models and we recommend for the time being switching to Claude Sonnet 4.5 for code completion while we continue to investigate the matter. Details on how to do that can be found at https://docs.gitlab.com/user/gitlab_duo/model_selection/#select-a-model-for-a-feature

5. identified Jun 30, 2026, 11:06 PM UTC

   We have identified the issue and are pushing a fix. While this fix is pushed we still recommend switching to Claude Sonnet 4.5 until the fix is fully pushed.

6. identified Jun 30, 2026, 11:06 PM UTC

   We have identified the issue and are pushing a fix. While this fix is pushed we still recommend switching to Claude Sonnet 4.5 until the fix is fully pushed.

7. monitoring Jun 30, 2026, 11:30 PM UTC

   The fix is pushed and systems appear to be operating normally. We are monitoring the situation to ensure that services have returned to normal.

8. monitoring Jun 30, 2026, 11:30 PM UTC

   The fix is pushed and systems appear to be operating normally. We are monitoring the situation to ensure that services have returned to normal.

9. resolved Jun 30, 2026, 11:59 PM UTC

   Operations have returned to normal and this issue is resolved.

Read the full incident report →

Started Jun 30, 2026, 04:08 PM UTC· resolved Jun 30, 2026, 07:46 PM UTC

1. investigating Jun 30, 2026, 04:08 PM UTC

   We are investigating the cause, but the symptoms are: 500 errors, CI jobs can't check out repos, slow merge request page loading, slow page loading 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 30, 2026, 04:08 PM UTC

   We are investigating the cause, but the symptoms are: 500 errors, CI jobs can't check out repos, slow merge request page loading, slow page loading

3. investigating Jun 30, 2026, 04:44 PM UTC

   We are continuing to investigate and look into the increased errors on GitLab.com

4. investigating Jun 30, 2026, 04:44 PM UTC

   We are continuing to investigate and look into the increased errors on GitLab.com

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

   We have identified the cause of the increased error rate and are taking corrective action and monitoring the incident.

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

   We have identified the cause of the increased error rate and are taking corrective action and monitoring the incident.

7. identified Jun 30, 2026, 05:39 PM UTC

   We are continuing to investigate and work to resolve the degraded performance on GitLab.com

8. identified Jun 30, 2026, 05:39 PM UTC

   We are continuing to investigate and work to resolve the degraded performance on GitLab.com

9. monitoring Jun 30, 2026, 06:26 PM UTC

   We have identified the issue and taken action to correct the matter and are monitoring GitLab.com. We will provide further updates as information is available or when the issue is confirmed resolved.

10. monitoring Jun 30, 2026, 06:26 PM UTC

    We have identified the issue and taken action to correct the matter and are monitoring GitLab.com. We will provide further updates as information is available or when the issue is confirmed resolved.

11. resolved Jun 30, 2026, 07:46 PM UTC

    This issue is resolved and performance on GitLab.com has returned to normal.

Read the full incident report →

Started Jun 30, 2026, 08:52 AM UTC· resolved Jun 30, 2026, 12:07 PM UTC

1. investigating Jun 30, 2026, 08:52 AM UTC

   We are currently investigating an issue affecting CI pipelines not starting on merge requests. Our team is actively investigating the root 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 Jun 30, 2026, 08:52 AM UTC

   We are currently investigating an issue affecting CI pipelines not starting on merge requests. Our team is actively investigating the root cause.

3. identified Jun 30, 2026, 09:37 AM UTC

   We have identified that the sidekiq workers processing the jobs are getting deferred. The team is working on identifying the remediation steps.

4. identified Jun 30, 2026, 09:37 AM UTC

   We have identified that the sidekiq workers processing the jobs are getting deferred. The team is working on identifying the remediation steps.

5. identified Jun 30, 2026, 10:51 AM UTC

   No material updates to report. We are continuing to investigate the current issue and engineers are working to determine remediation steps.

6. identified Jun 30, 2026, 10:51 AM UTC

   No material updates to report. We are continuing to investigate the current issue and engineers are working to identify the cause.

7. identified Jun 30, 2026, 11:19 AM UTC

   Our engineers are still investigating the issue but jobs are starting to be processed with a delay. More details can be found here: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22412

8. identified Jun 30, 2026, 11:19 AM UTC

   Our engineers are still investigating the issue but jobs are starting to be processed with a delay. More details can be found here: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22412

9. monitoring Jun 30, 2026, 11:39 AM UTC

   Queues and runner backlog are trending back towards normal, while systems continue to work through the remaining backlog. Engineers are continuing to monitor this.

10. monitoring Jun 30, 2026, 11:39 AM UTC

    Queues and runner backlog are trending back towards normal, while systems continue to work through the remaining backlog. Engineers are continuing to monitor this.

11. resolved Jun 30, 2026, 12:07 PM UTC

    Incident has now been mitigated and runner backlogs are now back to normal. CI pipelines are now resuming. Engineers will continue to monitor this recovery.

Read the full incident report →

Started Jun 23, 2026, 05:33 PM UTC· resolved Jun 23, 2026, 07:52 PM UTC

1. investigating Jun 23, 2026, 05:33 PM UTC

   We are investigating ongoing errors when attempting to interact with repositories via SSH. HTTPS does not appear to be impacted at this time. We are investigating. Details in: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22364 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 23, 2026, 05:33 PM UTC

   We are investigating ongoing errors when attempting to interact with repositories via SSH. HTTPS does not appear to be impacted at this time. We are investigating. Details in: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22364

3. identified Jun 23, 2026, 05:52 PM UTC

   We have identified the problematic change causing this behavior and are working to revert it. Details will be posted in: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22364

4. identified Jun 23, 2026, 05:52 PM UTC

   We have identified the problematic change causing this behavior and are working to revert it. Details will be posted in: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22364

5. identified Jun 23, 2026, 06:09 PM UTC

   We are still working to revert this problematic change as quickly as possible. Once reverted, we will post an update here. Details will be made available in: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22364

6. identified Jun 23, 2026, 06:09 PM UTC

   We are still working to revert this problematic change as quickly as possible. Once reverted, we will post an update here. Details will be made available in: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22364

7. monitoring Jun 23, 2026, 06:25 PM UTC

   We've addressed the underlying issue and are observing SSH interactions succeed. We will place this incident in a monitoring state as we keep an eye on things. Details: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22364

8. monitoring Jun 23, 2026, 06:25 PM UTC

   We've addressed the underlying issue and are observing SSH interactions succeed. We will place this incident in a monitoring state as we keep an eye on things. Details: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22364

9. resolved Jun 23, 2026, 07:52 PM UTC

   We have continued to observe successful SSH interactions after implementing our mitigating changes. We will now mark this as resolved. Details in: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22364

Read the full incident report →

Started Jun 18, 2026, 02:02 PM UTC· resolved Jun 18, 2026, 04:48 PM UTC

1. identified Jun 18, 2026, 02:02 PM UTC

   We've identified a recent code change as the likely cause of elevated Sidekiq job execution errors on the low-urgency-cpu-bound shard, which may delay processing of some background jobs. Mitigations are in progress. We'll continue to update as soon as the mitigation is merged and deployed. 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 Jun 18, 2026, 02:02 PM UTC

   We've identified a recent code change as the likely cause of elevated Sidekiq job execution errors on the low-urgency-cpu-bound shard, which may delay processing of some background jobs. Mitigations are in progress. We'll continue to update as soon as the mitigation is merged and deployed.

3. resolved Jun 18, 2026, 04:48 PM UTC

   A recent code change was rolled back and the error rates have subsided since it was merged. Our team has been monitoring and performance has returned to expected levels. This incident is now resolved. https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22335

Read the full incident report →

Started Jun 13, 2026, 03:53 AM UTC· resolved Jun 13, 2026, 07:56 AM UTC

1. monitoring Jun 13, 2026, 03:53 AM UTC

   Claude Fable is not available through GitLab.com. Please see the notice from the upstream provider: https://status.claude.com/incidents/s9w82lp9dcn9 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. monitoring Jun 13, 2026, 03:53 AM UTC

   Claude Fable is not available through GitLab.com. Please see the notice from the upstream provider: https://status.claude.com/incidents/s9w82lp9dcn9

3. monitoring Jun 13, 2026, 04:13 AM UTC

   Although Claude Fable is not available on GitLab.com, it still appears in the model selection menu. Customers who are currently using it should manually select a different model. Please see the notice from the upstream provider: https://status.claude.com/incidents/s9w82lp9dcn9

4. monitoring Jun 13, 2026, 04:13 AM UTC

   Although Claude Fable is not available on GitLab.com, it still appears in the model selection menu. Customers who are currently using it should manually select a different model. Please see the notice from the upstream provider: https://status.claude.com/incidents/s9w82lp9dcn9

5. monitoring Jun 13, 2026, 07:22 AM UTC

   The revert MR to remove the Claude Fable was merged and deployed to production. While the GitLab.com service is back to normal, Fable remains unavailable due to an upstream suspension. Customers need continue to select a different model. We are monitoring the situation closely.

6. monitoring Jun 13, 2026, 07:22 AM UTC

   The revert MR to remove the Claude Fable was merged and deployed to production. While the GitLab.com service is back to normal, Fable remains unavailable due to an upstream suspension. Customers need continue to select a different model. We are monitoring the situation closely.

7. resolved Jun 13, 2026, 07:56 AM UTC

   GitLab.com is currently operating normally. The issue has been resolved. For more info, please see: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22308

Read the full incident report →

Started Jun 11, 2026, 07:08 AM UTC· resolved Jun 11, 2026, 08:19 PM UTC

1. investigating Jun 11, 2026, 07:08 AM UTC

   We are currently investigating 5XX errors when accessing GitLab.com. 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 Jun 11, 2026, 07:08 AM UTC

   We are currently investigating 5XX errors when accessing GitLab.com. We'll share another update as soon as we have more information.

3. investigating Jun 11, 2026, 07:11 AM UTC

   We are currently investigating 5XX errors when accessing GitLab.com. We'll share another update as soon as we have more information.

4. investigating Jun 11, 2026, 07:11 AM UTC

   We are currently investigating 5XX errors when accessing GitLab.com. We'll share another update as soon as we have more information.

5. investigating Jun 11, 2026, 07:23 AM UTC

   We changed the status title to reflect the intermittent nature of this incident. We'll share another update as soon as we have more information.

6. investigating Jun 11, 2026, 07:23 AM UTC

   We changed the status title to reflect the intermittent nature of this incident. We'll share another update as soon as we have more information.

7. monitoring Jun 11, 2026, 08:06 AM UTC

   The GitLab.com service is now operational. We are keep investigating why it is occurring intermittently.

8. monitoring Jun 11, 2026, 08:06 AM UTC

   The GitLab.com service is now operational. We are keep investigating why it is occurring intermittently.

9. monitoring Jun 11, 2026, 12:16 PM UTC

   GitLab.com is currently operating normally. We have confirmed the root cause was a Cloud provider incident affecting a disk backing our primary database, and we are continuing to monitor closely.

10. monitoring Jun 11, 2026, 12:16 PM UTC

    GitLab.com is currently operating normally. We have confirmed the root cause was a Cloud provider incident affecting a disk backing our primary database, and we are continuing to monitor closely.

11. resolved Jun 11, 2026, 08:19 PM UTC

    GitLab.com is currently operating normally. We have confirmed the root cause was a Cloud provider incident affecting a disk backing our primary database and the issue should be resolved now.

Read the full incident report →