GitLab Outage History

Started Oct 23, 2026, 04:32 PM UTC· resolved Oct 23, 2026, 05:04 PM UTC

1. monitoring Oct 23, 2026, 04:32 PM UTC

   We identified and resolved an issue that caused slowness on GitLab.com. GitLab.com is operating normally, and we are monitoring the platform to ensure the issue remains resolved. More details here: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23320 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 Oct 23, 2026, 04:32 PM UTC

   We identified and resolved an issue that caused slowness on GitLab.com. GitLab.com is operating normally, and we are monitoring the platform to ensure the issue remains resolved. More details here: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23320

3. resolved Oct 23, 2026, 05:04 PM UTC

   We have resolved the issue that caused slowness on GitLab.com. GitLab.com is operating normally, and we are continuing to monitor the platform. The impact may have included partial degradation to the web UI and Git operations.

Read the full incident report →

Started Oct 20, 2026, 09:56 PM UTC· resolved Oct 21, 2026, 01:21 AM UTC

1. investigating Oct 20, 2026, 09:56 PM UTC

   We've investigating 404s on the customers panel. We'll update as we learn more 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 Oct 20, 2026, 09:56 PM UTC

   We've investigating 404s on the customers panel. We'll update as we learn more

3. investigating Oct 20, 2026, 10:47 PM UTC

   We’re continuing our investigation of 404s on the customers panel. We’ll update you as we learn more.

4. investigating Oct 20, 2026, 10:47 PM UTC

   We’re continuing our investigation of 404s on the customers panel. We’ll update you as we learn more.

5. investigating Oct 20, 2026, 11:15 PM UTC

   We’re continuing our investigation of 404s on the customers panel. We’ll update you as we learn more.

6. investigating Oct 20, 2026, 11:15 PM UTC

   We’re continuing our investigation of 404s on the customers panel. We’ll update you as we learn more.

7. monitoring Oct 20, 2026, 11:51 PM UTC

   The Customers Portal is loading normally again, and we are no longer observing the intermittent 404 errors affecting sign-in and page loading. A redeployment has completed successfully, and we are monitoring the service for any recurrence before resolving the incident.

8. monitoring Oct 20, 2026, 11:51 PM UTC

   The Customers Portal is loading normally again, and we are no longer observing the intermittent 404 errors affecting sign-in and page loading. A redeployment has completed successfully, and we are monitoring the service for any recurrence before resolving the incident.

9. resolved Oct 21, 2026, 01:21 AM UTC

   The monitoring period has concluded, and the incident has been confirmed resolved. See the issue for more details: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23297

Read the full incident report →

Started Oct 20, 2026, 07:08 AM UTC· resolved Oct 20, 2026, 09:55 AM UTC

1. investigating Oct 20, 2026, 07:08 AM UTC

   We're investigating intermittent HTTP 503 errors when opening project pages. At this time, this issue only occurs in specific projects. More details at: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23288 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 Oct 20, 2026, 07:08 AM UTC

   We're investigating intermittent HTTP 503 errors when opening project pages. At this time, this issue only occurs in specific projects. More details at: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23288

3. monitoring Oct 20, 2026, 07:37 AM UTC

   This issue affects projects and groups using GitLab Secrets Manager. Users saw HTTP 500 errors, not 503 as previously stated. A mitigation has been applied and we're monitoring. Details: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23288

4. monitoring Oct 20, 2026, 07:37 AM UTC

   This issue affects projects and groups using GitLab Secrets Manager. Users saw HTTP 500 errors, not 503 as previously stated. A mitigation has been applied and we're monitoring. Details: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23288

5. monitoring Oct 20, 2026, 07:37 AM UTC

   This issue affects projects and groups using GitLab Secrets Manager. Users saw HTTP 500 errors, not 503 as previously stated. A mitigation has been applied and we're monitoring. Details: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23288

6. resolved Oct 20, 2026, 09:55 AM UTC

   We have not seen any more HTTP 500 errors for GitLab Secrets Manager since the mitigation was applied. This incident is now resolved. Details: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23288

Read the full incident report →

Started Oct 16, 2026, 04:10 PM UTC· resolved Oct 16, 2026, 05:24 PM UTC

1. investigating Oct 16, 2026, 04:10 PM UTC

   We are investigating the cause of 503s on GitLab.com and the site moving slowly. We will update once we have additional details. 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 Oct 16, 2026, 04:10 PM UTC

   We are investigating the cause of 503s on GitLab.com and the site moving slowly. We will update once we have additional details.

3. investigating Oct 16, 2026, 04:25 PM UTC

   We are still investigating the cause of 503 on GitLab.com. We are seeing some services return but errors still intermittent. More details at: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23261

4. investigating Oct 16, 2026, 04:25 PM UTC

   We are still investigating the cause of 503 on GitLab.com. We are seeing some services return but errors still intermittent. More details at: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23261

5. identified Oct 16, 2026, 04:40 PM UTC

   We have identified the cause of 503s on GitLab.com and are working to remediate the issue. We are still seeing intermittent 503s and site slowness as we work to resolve the issue. More details: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23261

6. identified Oct 16, 2026, 04:40 PM UTC

   We have identified the cause of 503s on GitLab.com and are working to remediate the issue. We are still seeing intermittent 503s and site slowness as we work to resolve the issue. More details: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23261

7. identified Oct 16, 2026, 04:52 PM UTC

   Most services on GitLab.com have recovered but we are seeing slowness with Duo requests and services and are looking to resolve it. More details at: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23261

8. identified Oct 16, 2026, 04:52 PM UTC

   Most services on GitLab.com have recovered but we are seeing slowness with Duo requests and services and are looking to resolve it. More details at: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23261

9. monitoring Oct 16, 2026, 05:05 PM UTC

   We have taken steps to resolve the slowness and 503s on GitLab.com and are monitoring the situation. More details at: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23261

10. monitoring Oct 16, 2026, 05:05 PM UTC

    We have taken steps to resolve the slowness and 503s on GitLab.com and are monitoring the situation. More details at: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23261

11. resolved Oct 16, 2026, 05:24 PM UTC

    The issue is fully resolved and operations on GitLab.com and GitLab Duo are operating normally. More details at: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23261

Read the full incident report →

Started Oct 16, 2026, 11:33 AM UTC· resolved Oct 16, 2026, 01:21 PM UTC

1. investigating Oct 16, 2026, 11:33 AM UTC

   We’re investigating an issue affecting CI/CD on GitLab.com for a limited number of customers. Pipelines may fail with the following error, and the UI may be slow: “CI configuration fetch from Gitaly timed out. This may indicate Gitaly service slowness or an outage.” More updates to follow. 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 Oct 16, 2026, 11:33 AM UTC

   We’re investigating an issue affecting CI/CD on GitLab.com for a limited number of customers. Pipelines may fail with the following error: “CI configuration fetch from Gitaly timed out. This may indicate Gitaly service slowness or an outage.” More updates to follow.

3. monitoring Oct 16, 2026, 12:28 PM UTC

   We've applied a temporary mitigation to address CI/CD failures and UI slowness affecting a limited number of GitLab.com customers. We're monitoring recovery while working on a longer-term solution.

4. monitoring Oct 16, 2026, 12:28 PM UTC

   We've applied a temporary mitigation to address CI/CD failures and UI slowness affecting a limited number of GitLab.com customers. We're monitoring recovery while working on a longer-term solution.

5. resolved Oct 16, 2026, 01:21 PM UTC

   The issue causing CI/CD failures and UI slowness for a limited number of GitLab.com customers has been resolved. Thank you for your patience.

Read the full incident report →

Started Oct 15, 2026, 04:18 PM UTC· resolved Oct 15, 2026, 07:50 PM UTC

1. investigating Oct 15, 2026, 04:19 PM UTC

   We are investigating an issue affecting GitLab.com CI/CD. Some pipelines may remain in the created state for an extended period or fail to start, causing CI/CD workflows to stall. More Details at https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23234 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 Oct 15, 2026, 04:19 PM UTC

   We are investigating an issue affecting GitLab.com CI/CD. Some pipelines may remain in the created state for an extended period or fail to start, causing CI/CD workflows to stall. More Details at https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23234

3. identified Oct 15, 2026, 05:23 PM UTC

   We have identified the cause of the issue causing CI/CD delays on GitLab.com and are working to take corrective actions. The issue may persists intermittently as we do so. More details at: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23234

4. identified Oct 15, 2026, 05:23 PM UTC

   We have identified the cause of the issue causing CI/CD delays on GitLab.com and are working to take corrective actions. The issue may persists intermittently as we do so. More details at: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23234

5. resolved Oct 15, 2026, 07:50 PM UTC

   We have taken steps to mitigate the delays on CI/CD jobs on GitLab.com and services have returned to normal. More details at: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23234

Read the full incident report →

Started Oct 15, 2026, 04:43 AM UTC· resolved Oct 15, 2026, 09:02 AM UTC

1. investigating Oct 15, 2026, 04:43 AM UTC

   We're investigating an issue that's stopping pages on customers.gitlab.com from loading. Purchasing, renewing, and managing subscriptions may be affected. GitLab.com itself is not affected. 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 Oct 15, 2026, 04:43 AM UTC

   We're investigating an issue that's stopping pages on customers.gitlab.com from loading. Purchasing, renewing, and managing subscriptions may be affected. GitLab.com itself is not affected.

3. investigating Oct 15, 2026, 05:10 AM UTC

   We have received reports that some groups on GitLab.com are experiencing HTTP 500 errors because the group is unable to sync with customers.gitlab.com. We are continuing to investigate the issue.

4. investigating Oct 15, 2026, 05:10 AM UTC

   We have received reports that some groups on GitLab.com are experiencing HTTP 500 errors because the group is unable to sync with customers.gitlab.com. We are continuing to investigate the issue.

5. investigating Oct 15, 2026, 05:27 AM UTC

   No material updates to report. We are still investigating the root cause.

6. investigating Oct 15, 2026, 05:27 AM UTC

   No material updates to report. We are still investigating the root cause.

7. investigating Oct 15, 2026, 05:50 AM UTC

   No material updates to report. We'll share another update when we have more information.

8. investigating Oct 15, 2026, 05:50 AM UTC

   No material updates to report. We'll share another update when we have more information.

9. monitoring Oct 15, 2026, 08:35 AM UTC

   Mitigations have been applied to customers.gitlab.com, and we are monitoring service availability. Intermittent errors may continue to affect Customers Portal pages and GitLab.com groups that rely on the portal for subscription-related operations. We are continuing to investigate the underlying cause and will provide another update when more information is available. More details: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23240

10. monitoring Oct 15, 2026, 08:35 AM UTC

    Mitigations have been applied to customers.gitlab.com, and we are monitoring service availability. Intermittent errors may continue to affect Customers Portal pages and GitLab.com groups that rely on the portal for subscription-related operations. We are continuing to investigate the underlying cause and will provide another update when more information is available. More details: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23240

11. resolved Oct 15, 2026, 09:02 AM UTC

    The issue affecting customers.gitlab.com has been resolved. Customers Portal pages and subscription-related operations have returned to normal. More details: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23240

Read the full incident report →

Started Oct 14, 2026, 02:33 PM UTC· resolved Oct 14, 2026, 06:30 PM UTC

1. investigating Oct 14, 2026, 02:33 PM UTC

   We are investigating an issue affecting GitLab.com merge trains. Some merge train pipelines may remain in the created state for an extended period or fail to start, causing merge trains and related CI/CD workflows to stall. More details: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23192 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 Oct 14, 2026, 02:33 PM UTC

   We are investigating an issue affecting GitLab.com merge trains. Some merge train pipelines may remain in the created state for an extended period or fail to start, causing merge trains and related CI/CD workflows to stall. More details: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23190

3. investigating Oct 14, 2026, 03:22 PM UTC

   We are investigating an issue affecting GitLab.com CI/CD. Merge train, scheduled, and child/downstream pipelines may be delayed, remain in a created or pending state, or fail to start. Mergeability analysis and webhook notifications may also be delayed. More details: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23192

4. investigating Oct 14, 2026, 03:22 PM UTC

   We are investigating an issue affecting GitLab.com CI/CD. Merge train, scheduled, and child/downstream pipelines may be delayed, remain in a created or pending state, or fail to start. Mergeability analysis and webhook notifications may also be delayed. More details: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23192

5. investigating Oct 14, 2026, 04:40 PM UTC

   We are investigating an issue affecting GitLab.com and general site errors and slowness related to the initial issue. We are actively investigating the issue. More details: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23192

6. investigating Oct 14, 2026, 04:40 PM UTC

   We are investigating an issue affecting GitLab.com and general site errors and slowness related to the initial issue. We are actively investigating the issue. More details: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23192

7. identified Oct 14, 2026, 04:50 PM UTC

   We identified the issue affecting GitLab.com and general site errors and slowness related to the initial issue. We are actively working to resolve the issue. More details: gitlab.com/gitlab-com/gl-infra/production/-/work_items/23192

8. identified Oct 14, 2026, 04:50 PM UTC

   We identified the issue affecting GitLab.com and general site errors and slowness related to the initial issue. We are actively working to resolve the issue. More details: gitlab.com/gitlab-com/gl-infra/production/-/work_items/23192

9. resolved Oct 14, 2026, 06:30 PM UTC

   The source of the issue has been identified and we have taken steps to remediate and resolve the issue. GitLab.com is stable now. More details: gitlab.com/gitlab-com/gl-infra/production/-/work_items/23192

Read the full incident report →

Started Oct 13, 2026, 02:27 PM UTC· resolved Oct 13, 2026, 08:59 PM UTC

1. investigating Oct 13, 2026, 02:27 PM UTC

   We are investigating increased queue times for CI/CD jobs using GitLab.com small Linux x86-64 hosted runners. Affected jobs may remain pending longer than usual before starting. We have identified errors and delays when provisioning runner capacity and are working to restore normal job start times. More details: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23176 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 Oct 13, 2026, 02:27 PM UTC

   We are investigating increased queue times for CI/CD jobs using GitLab.com small Linux x86-64 hosted runners. Affected jobs may remain pending longer than usual before starting. We have identified errors and delays when provisioning runner capacity and are working to restore normal job start times. More details: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23176

3. identified Oct 13, 2026, 03:46 PM UTC

   We have identified an ongoing Google Cloud Compute Engine issue affecting runner-capacity provisioning in us-east1. Some GitLab.com CI/CD jobs using small Linux x86-64 hosted runners may remain pending longer than usual before starting. Our engineering teams are working with Google Cloud to restore normal job start times. More details: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23176

4. identified Oct 13, 2026, 03:46 PM UTC

   We have identified an ongoing Google Cloud Compute Engine issue affecting runner-capacity provisioning in us-east1. Some GitLab.com CI/CD jobs using small Linux x86-64 hosted runners may remain pending longer than usual before starting. Our engineering teams are working with Google Cloud to restore normal job start times. More details: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23176

5. monitoring Oct 13, 2026, 07:31 PM UTC

   Job start times for CI/CD jobs on GitLab.com small Linux x86-64 hosted runners have returned to normal, and the backlog of pending jobs has been processed. The delays were caused by errors and capacity constraints from our cloud provider when provisioning runner capacity in one region, between approximately 13:17 and 19:15 UTC. Jobs that were delayed are now starting as usual. We are monitoring to make sure performance remains stable and will post an update when this incident is resolved.

6. monitoring Oct 13, 2026, 07:31 PM UTC

   Job start times for CI/CD jobs on GitLab.com small Linux x86-64 hosted runners have returned to normal, and the backlog of pending jobs has been processed. The delays were caused by errors and capacity constraints from our cloud provider when provisioning runner capacity in one region, between approximately 13:17 and 19:15 UTC. Jobs that were delayed are now starting as usual. We are monitoring to make sure performance remains stable and will post an update when this incident is resolved.

7. resolved Oct 13, 2026, 08:59 PM UTC

   Job start times for CI/CD jobs on GitLab.com small Linux x86-64 hosted runners have returned to normal, and the backlog of pending jobs has been processed. The issue with the provider persists, but we are not seeing any impact on our systems. More details: gitlab.com/gitlab-com/gl-infra/production/-/work_items/23176

Read the full incident report →

Started Oct 13, 2026, 07:10 AM UTC· resolved Oct 14, 2026, 11:40 PM UTC

1. investigating Oct 13, 2026, 07:10 AM UTC

   We are currently investigating reports of an increase of HTTP 50X errors on GitLab.com 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 Oct 13, 2026, 07:10 AM UTC

   We are currently investigating reports of an increase of HTTP 50X errors on GitLab.com

3. investigating Oct 13, 2026, 07:30 AM UTC

   We are seeing an improvement in errors rates in our monitoring, starting from 07:14 UTC. We are still identifying the root cause.

4. investigating Oct 13, 2026, 07:30 AM UTC

   We are seeing an improvement in errors rates in our monitoring, starting from 07:14 UTC. We are still identifying the root cause.

5. investigating Oct 13, 2026, 07:48 AM UTC

   General GitLab.com service continues to improve. We're now focused on restoring Duo services.

6. investigating Oct 13, 2026, 07:48 AM UTC

   General GitLab.com service continues to improve. We're now focused on restoring Duo services.

7. monitoring Oct 13, 2026, 07:59 AM UTC

   We are seeing improvements across all services on GitLab.com. We are resuming our investigation on identifying the root cause.

8. monitoring Oct 13, 2026, 07:59 AM UTC

   We are seeing improvements across all services on GitLab.com. We are resuming our investigation on identifying the root cause.

9. monitoring Oct 14, 2026, 02:33 AM UTC

   Monitoring confirms that GitLab.com services have remained stable. We are continuing to monitor for any recurrence of the issues before marking this incident as resolved.

10. monitoring Oct 14, 2026, 02:33 AM UTC

    Monitoring confirms that GitLab.com services have remained stable. We are continuing to monitor for any recurrence of the issues before marking this incident as resolved.

11. resolved Oct 14, 2026, 11:40 PM UTC

    We have been monitoring this issue for a few days with no reported occurrences.

Read the full incident report →

Started Oct 12, 2026, 11:30 AM UTC· resolved Oct 14, 2026, 01:16 AM UTC

1. identified Oct 12, 2026, 11:30 AM UTC

   We’re investigating an issue affecting some GitLab Duo Workflow operations. Duo Code Review results may be incomplete or lower quality than expected. Our engineering teams are working on mitigation and will provide further updates. More details: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23158 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 Oct 12, 2026, 11:30 AM UTC

   We’re investigating an issue affecting some GitLab Duo Workflow operations. Duo Code Review results may be incomplete or lower quality than expected. Our engineering teams are working on mitigation and will provide further updates. More details: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23158

3. identified Oct 12, 2026, 01:37 PM UTC

   We've identified the cause of the issue affecting GitLab Duo Workflow operations. Duo Code Review remains available, but reviews may contain less context than expected. Our engineering teams are expediting a fix and will continue monitoring until service is fully restored. For more details: gitlab.com/gitlab-com/gl-infra/production/-/work_items/23158

4. identified Oct 12, 2026, 01:37 PM UTC

   We've identified the cause of the issue affecting GitLab Duo Workflow operations. Duo Code Review remains available, but reviews may contain less context than expected. Our engineering teams are expediting a fix and will continue monitoring until service is fully restored. For more details: gitlab.com/gitlab-com/gl-infra/production/-/work_items/23158

5. monitoring Oct 13, 2026, 12:28 AM UTC

   Errors affecting Code Review tools have decreased, and the tools appear to be operating normally. We’re monitoring error rates and investigating the improvement. A fix is merged but not yet in production, so recovery is still being validated.

6. monitoring Oct 13, 2026, 12:28 AM UTC

   Errors affecting Code Review tools have decreased, and the tools appear to be operating normally. We’re monitoring error rates and investigating the improvement. A fix is merged but not yet in production, so recovery is still being validated.

7. monitoring Oct 13, 2026, 12:29 AM UTC

   Errors affecting Code Review tools have decreased, and the tools appear to be operating normally. We’re monitoring error rates and investigating the improvement. A fix is merged but not yet in production, so recovery is still being validated.

8. monitoring Oct 13, 2026, 12:29 AM UTC

   Errors affecting Code Review tools have decreased, and the tools appear to be operating normally. We’re monitoring error rates and investigating the improvement. A fix is merged but not yet in production, so recovery is still being validated.

9. identified Oct 13, 2026, 02:11 AM UTC

   Monitoring shows failures are still occurring in a tool used by Duo Code Review. The service remains available, but reviews may contain less context than expected. A fix is merged and awaiting deployment; we’ll update once recovery is confirmed.

10. identified Oct 13, 2026, 02:11 AM UTC

    Monitoring shows failures are still occurring in a tool used by Duo Code Review. The service remains available, but reviews may contain less context than expected. A fix is merged and awaiting deployment; we’ll update once recovery is confirmed.

11. resolved Oct 14, 2026, 01:16 AM UTC

    The fix was deployed and continued monitoring has shown that the identified tool failure has been addressed. This issue is now resolved. Details in https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23158

Read the full incident report →

Started Oct 10, 2026, 04:49 AM UTC· resolved Oct 12, 2026, 10:15 AM UTC

1. investigating Oct 10, 2026, 04:49 AM UTC

   We are investigating reports of errors and slow performance on merge request and pipeline pages for projects in the specific groups. Details in https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23150 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 Oct 10, 2026, 04:49 AM UTC

   We are investigating reports of errors and slow performance on merge request and pipeline pages for projects in the specific groups. Details in https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23150

3. monitoring Oct 10, 2026, 06:26 AM UTC

   We have applied a mitigation and are seeing sustained recovery in error rates and performance on merge request and pipeline pages for the affected projects. We are continuing to monitor. Details in https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23150

4. monitoring Oct 10, 2026, 06:26 AM UTC

   We have applied a mitigation and are seeing sustained recovery in error rates and performance on merge request and pipeline pages for the affected projects. We are continuing to monitor. Details in https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23150

5. monitoring Oct 10, 2026, 06:27 AM UTC

   We have applied a mitigation and are seeing sustained recovery in error rates and performance on merge request and pipeline pages for the affected projects. We are continuing to monitor. Details in gitlab.com/gitlab-com/gl-infra/production/-/work_items/23150

6. monitoring Oct 10, 2026, 06:27 AM UTC

   We have applied a mitigation and are seeing sustained recovery in error rates and performance on merge request and pipeline pages for the affected projects. We are continuing to monitor. Details in gitlab.com/gitlab-com/gl-infra/production/-/work_items/23150

7. resolved Oct 12, 2026, 10:15 AM UTC

   The issue has been resolved, and systems have returned to normal operation.

Read the full incident report →

Started Oct 08, 2026, 03:59 PM UTC· resolved Oct 08, 2026, 06:33 PM UTC

1. investigating Oct 08, 2026, 03:59 PM UTC

   We are currently investigating delays in job completion: CI jobs remain running after success, delaying pipeline progression. Details https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23133 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 Oct 08, 2026, 03:59 PM UTC

   We are currently investigating delays in job completion: CI jobs remain running after success, delaying pipeline progression. Details https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23133

3. investigating Oct 08, 2026, 04:19 PM UTC

   Job completion delays are still being observed and we are actively working to address the issue. Details in: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23133

4. investigating Oct 08, 2026, 04:19 PM UTC

   Job completion delays are still being observed and we are actively working to address the issue. Details in: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23133

5. investigating Oct 08, 2026, 04:35 PM UTC

   Our investigation is ongoing and we are actively working to identify the root cause. We will provide further updates as more information becomes available. Details in: gitlab.com/gitlab-com/gl-infra/production/-/work_items/23133

6. investigating Oct 08, 2026, 04:35 PM UTC

   Our investigation is ongoing and we are actively working to identify the root cause. We will provide further updates as more information becomes available. Details in: gitlab.com/gitlab-com/gl-infra/production/-/work_items/23133

7. identified Oct 08, 2026, 05:11 PM UTC

   We are continuing to investigate. In addition to delays, users may experience job timeouts or failures during this time. If affected, please retry the job. Details in: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23133

8. identified Oct 08, 2026, 05:11 PM UTC

   We are continuing to investigate. In addition to delays, users may experience job timeouts or failures during this time. If affected, please retry the job. Details in: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23133

9. identified Oct 08, 2026, 05:34 PM UTC

   We are continuing to investigate the root cause and will provide further updates as they become available. Details in: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23131

10. identified Oct 08, 2026, 05:34 PM UTC

    We are continuing to investigate the root cause and will provide further updates as they become available. Details in: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23131

11. monitoring Oct 08, 2026, 05:45 PM UTC

    We are beginning to see signs of recovery and are continuing to monitor the situation closely while we investigate the root cause. If you have been affected, please retry any failed or timed out jobs. Details in: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23131

12. monitoring Oct 08, 2026, 05:45 PM UTC

    We are beginning to see signs of recovery and are continuing to monitor the situation closely while we investigate the root cause. If you have been affected, please retry any failed or timed out jobs. Details in: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23131

13. resolved Oct 08, 2026, 06:33 PM UTC

    After continued monitoring, services remain stable. The incident has been resolved.

Read the full incident report →

Started Oct 01, 2026, 12:35 AM UTC· resolved Oct 01, 2026, 12:12 PM UTC

1. investigating Oct 01, 2026, 12:35 AM UTC

   We’ve detected email delivery delays affecting a small number of email service providers. The team is actively investigating to identify the full scope and impact. The incident is being tracked in https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23061 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 Oct 01, 2026, 12:35 AM UTC

   We’ve detected email delivery delays affecting a small number of email service providers. The team is actively investigating to identify the full scope and impact. The incident is being tracked in https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23061

3. investigating Oct 01, 2026, 12:51 AM UTC

   We are escalating this issue directly with our email delivery provider. The team continues to monitor the impact and will provide another update as more information becomes available. The incident is being tracked in https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23061

4. investigating Oct 01, 2026, 12:51 AM UTC

   We are escalating this issue directly with our email delivery provider. The team continues to monitor the impact and will provide another update as more information becomes available. The incident is being tracked in https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23061

5. investigating Oct 01, 2026, 02:06 AM UTC

   We are continuing to escalate with our email delivery provider, and other affected email service providers directly. The team continues to monitor the impact and will provide another update as more information becomes available. The incident is being tracked in https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23061

6. investigating Oct 01, 2026, 02:06 AM UTC

   We are continuing to escalate with our email delivery provider, and other affected email service providers directly. The team continues to monitor the impact and will provide another update as more information becomes available. The incident is being tracked in https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23061

7. investigating Oct 01, 2026, 03:42 AM UTC

   We have taken additional measures to reduce elevated email volumes and improve platform stability. The team continues to monitor the impact and will provide another update as more information becomes available. The incident is being tracked in https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23061

8. investigating Oct 01, 2026, 03:42 AM UTC

   We have taken additional measures to reduce elevated email volumes and improve platform stability. The team continues to monitor the impact and will provide another update as more information becomes available. The incident is being tracked in https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23061

9. investigating Oct 01, 2026, 06:51 AM UTC

   Our monitoring has not observed any bounced emails since 02:29 UTC. We are seeing early signs of improvement in email delivery, but some messages may continue to be delayed or fail for certain email service providers. The team continues to monitor delivery performance and work with our email delivery provider to understand and address the issue. We will provide another update as more information becomes available.

10. investigating Oct 01, 2026, 06:51 AM UTC

    Our monitoring has not observed any bounced emails since 02:29 UTC. We are seeing early signs of improvement in email delivery, but some messages may continue to be delayed or fail for certain email service providers. The team continues to monitor delivery performance and work with our email delivery provider to understand and address the issue. We will provide another update as more information becomes available.

11. monitoring Oct 01, 2026, 08:49 AM UTC

    There were no new bounced emails since 02:29 UTC. We will continue to monitor the logs and provide updates when new information is available.

12. monitoring Oct 01, 2026, 08:49 AM UTC

    There were no new bounced emails since 02:29 UTC. We will continue to monitor the logs and provide updates when new information is available.

13. resolved Oct 01, 2026, 12:12 PM UTC

    We have not seen new failures, so we are marking this as solved. More information is available in gitlab.com/gitlab-com/gl-infra/production/-/work_items/23061.

Read the full incident report →

Started Sep 29, 2026, 06:15 PM UTC· resolved Sep 30, 2026, 12:26 PM UTC

1. investigating Sep 29, 2026, 06:15 PM UTC

   Security and vulnerability reports are not loading or being ingested for some users. We are investigating now. For more info: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23024 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 Sep 29, 2026, 06:15 PM UTC

   Security and vulnerability reports are not loading or being ingested for some users. We are investigating now. For more info: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23024

3. identified Sep 29, 2026, 06:36 PM UTC

   We've identified the cause and are working on mitigation. More info: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23024

4. identified Sep 29, 2026, 06:36 PM UTC

   We've identified the cause and are working on mitigation. More info: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23024

5. monitoring Sep 29, 2026, 07:06 PM UTC

   The mitigation we implemented is reducing the backlog of events. We are now monitoring the situation, see also: gitlab.com/gitlab-com/gl-infra/production/-/work_items/23024

6. monitoring Sep 29, 2026, 07:06 PM UTC

   The mitigation we implemented is reducing the backlog of events. We are now monitoring the situation, see also: gitlab.com/gitlab-com/gl-infra/production/-/work_items/23024

7. monitoring Sep 29, 2026, 08:01 PM UTC

   We continue to see improvements across our graphs, see also: gitlab.com/gitlab-com/gl-infra/production/-/work_items/23024

8. monitoring Sep 29, 2026, 08:01 PM UTC

   We continue to see improvements across our graphs, see also: gitlab.com/gitlab-com/gl-infra/production/-/work_items/23024

9. monitoring Sep 29, 2026, 09:12 PM UTC

   We continue to see improvements across our graphs and reduced backlog, more info: gitlab.com/gitlab-com/gl-infra/production/-/work_items/23024

10. monitoring Sep 29, 2026, 09:12 PM UTC

    We continue to see improvements across our graphs and reduced backlog, more info: gitlab.com/gitlab-com/gl-infra/production/-/work_items/23024

11. monitoring Sep 29, 2026, 10:29 PM UTC

    Monitoring continues. A backlog of ingestion events is currently being processed, which we expect will take some time. We will keep posting updates as we have them. See: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23024

12. monitoring Sep 29, 2026, 10:29 PM UTC

    Monitoring continues. A backlog of ingestion events is currently being processed, which we expect will take some time. We will keep posting updates as we have them. See: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23024

13. monitoring Sep 30, 2026, 12:02 AM UTC

    Monitoring continues. A backlog of ingestion events is currently being processed, which we expect will take some time. See: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23024

14. monitoring Sep 30, 2026, 12:02 AM UTC

    Monitoring continues. A backlog of ingestion events is currently being processed, which we expect will take some time. See: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23024

15. monitoring Sep 30, 2026, 07:19 AM UTC

    No material updates to report. We are continuing to monitor the report-ingestion backlog and working on mitigation. More info: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23024

16. monitoring Sep 30, 2026, 07:19 AM UTC

    No material updates to report. We are continuing to monitor the report-ingestion backlog and working on mitigation. More info: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23024

17. monitoring Sep 30, 2026, 09:17 AM UTC

    No material updates to report. We are continuing to monitor the report-ingestion backlog and working on mitigation. More info: gitlab.com/gitlab-com/gl-infra/production/-/work_items/23024

18. monitoring Sep 30, 2026, 09:17 AM UTC

    No material updates to report. We are continuing to monitor the report-ingestion backlog and working on mitigation. More info: gitlab.com/gitlab-com/gl-infra/production/-/work_items/23024

19. resolved Sep 30, 2026, 12:26 PM UTC

    We observed that the backlog of jobs have been processed and new reports should be coming in on the normal schedule. With this update the incident is resolved. More info: gitlab.com/gitlab-com/gl-infra/production/-/work_items/23024

Read the full incident report →

Started Sep 24, 2026, 01:48 PM UTC· resolved Sep 24, 2026, 08:50 PM UTC

1. investigating Sep 24, 2026, 01:48 PM UTC

   We have received reports that some users are unable to access projects and are encountering 500 error messages. Our team is currently investigating the cause. You can follow developments here: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23015 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 Sep 24, 2026, 01:48 PM UTC

   We have received reports that some users are unable to access projects and are encountering 500 error messages. Our team is currently investigating the cause.

3. investigating Sep 24, 2026, 02:10 PM UTC

   A temporary mitigation has been implemented however the cause of the incident is still being investigated.

4. investigating Sep 24, 2026, 02:44 PM UTC

   The incident team is continuing to investigate the issue to identify its root cause and implement an appropriate resolution.

5. investigating Sep 24, 2026, 02:44 PM UTC

   The incident team is continuing to investigate the issue to identify its root cause and implement an appropriate resolution.

6. investigating Sep 24, 2026, 03:17 PM UTC

   The incident team continues to investigate the cause of this incident. In the meantime, we are seeing intermittent improvements in the ability to access projects.

7. investigating Sep 24, 2026, 03:17 PM UTC

   The incident team continues to investigate the cause of this incident. In the meantime, we are seeing intermittent improvements in the ability to access projects.

8. investigating Sep 24, 2026, 04:13 PM UTC

   No material updates at this time. We are continuing our investigation. More information: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23015

9. investigating Sep 24, 2026, 04:13 PM UTC

   No material updates at this time. We are continuing our investigation. More information: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23015

10. investigating Sep 24, 2026, 05:21 PM UTC

    We're continuing our investigation. More information: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23015

11. investigating Sep 24, 2026, 05:21 PM UTC

    We're continuing our investigation. More information: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23015

12. identified Sep 24, 2026, 06:32 PM UTC

    The team has identified the potential cause of the spike in 500 errors and is working on the fix. More information: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23015

13. identified Sep 24, 2026, 06:32 PM UTC

    The team has identified the potential cause of the spike in 500 errors and is working on the fix. More information: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23015

14. identified Sep 24, 2026, 08:03 PM UTC

    The team is still working on the fix. More information: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23015

15. identified Sep 24, 2026, 08:03 PM UTC

    The team is still working on the fix. More information: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23015

16. resolved Sep 24, 2026, 08:50 PM UTC

    We're no longer seeing elevated errors, so we are resolving this incident. If you continue to experience any errors on GitLab.com, please open a ticket. More information: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23015

Read the full incident report →

Started Sep 21, 2026, 12:10 PM UTC· resolved Sep 21, 2026, 08:18 PM UTC

1. investigating Sep 21, 2026, 12:10 PM UTC

   We're experiencing degraded package, artifact, and registry download speed in APAC/Singapore region due to elevated CDN/Cloudflare latency. More details in https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22981. 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 Sep 21, 2026, 12:10 PM UTC

   We're experiencing degraded package, artifact, and registry download speed in APAC/Singapore region due to elevated CDN/Cloudflare latency. More details in https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22981.

3. investigating Sep 21, 2026, 12:51 PM UTC

   We are still investigating the cause for the performance degradation. There are no material updates at the moment. The problem is tracked under https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22981.

4. investigating Sep 21, 2026, 12:51 PM UTC

   We are still investigating the cause for the performance degradation. There are no material updates at the moment. The problem is tracked under https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22981.

5. monitoring Sep 21, 2026, 03:17 PM UTC

   Cloudflare confirmed the traffic degradation was resolved, with recovery observed at approximately 13:40 UTC. Our application and backend checks remained healthy during the degradation, supporting that the impact was outside the GitLab application stack. We will continue to monitor the situation. More details in gitlab.com/gitlab-com/gl-infra/production/-/work_items/22981.

6. monitoring Sep 21, 2026, 03:17 PM UTC

   Cloudflare confirmed the traffic degradation was resolved, with recovery observed at approximately 13:40 UTC. Our application and backend checks remained healthy during the degradation, supporting that the impact was outside the GitLab application stack. We will continue to monitor the situation. More details in gitlab.com/gitlab-com/gl-infra/production/-/work_items/22981.

7. monitoring Sep 21, 2026, 05:14 PM UTC

   No material updates at this time. We will continue to monitor the situation. More details in gitlab.com/gitlab-com/gl-infra/production/-/work_items/22981.

8. monitoring Sep 21, 2026, 05:14 PM UTC

   No material updates at this time. We will continue to monitor the situation. More details in gitlab.com/gitlab-com/gl-infra/production/-/work_items/22981.

9. monitoring Sep 21, 2026, 06:16 PM UTC

   At this time the situation is unchanged. We will continue to monitor. More details in gitlab.com/gitlab-com/gl-infra/production/-/work_items/22981.

10. monitoring Sep 21, 2026, 06:16 PM UTC

    At this time the situation is unchanged. We will continue to monitor. More details in gitlab.com/gitlab-com/gl-infra/production/-/work_items/22981.

11. monitoring Sep 21, 2026, 07:16 PM UTC

    We're still monitoring this incident. More details in gitlab.com/gitlab-com/gl-infra/production/-/work_items/22981.

12. monitoring Sep 21, 2026, 07:16 PM UTC

    We're still monitoring this incident. More details in gitlab.com/gitlab-com/gl-infra/production/-/work_items/22981.

13. resolved Sep 21, 2026, 08:18 PM UTC

    At this time we are resolving this incident. If you continue to experience performance degradation in the Singapore area, please open a support ticket. More details in gitlab.com/gitlab-com/gl-infra/production/-/work_items/22981.

Read the full incident report →

Started Sep 17, 2026, 08:44 PM UTC· resolved Sep 18, 2026, 01:45 PM UTC

1. investigating Sep 17, 2026, 08:44 PM UTC

   We're investigating reports of customers unable to open projects, receiving error 500 instead. 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 Sep 17, 2026, 08:44 PM UTC

   We're investigating reports of customers unable to open projects, receiving error 500 instead. Details in https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22925.

3. investigating Sep 17, 2026, 09:32 PM UTC

   No material updates are available at this time. Our team continues to investigate the root cause of the issue.

4. investigating Sep 17, 2026, 09:32 PM UTC

   No material updates are available at this time. Our team continues to investigate the root cause of the issue.

5. identified Sep 17, 2026, 09:56 PM UTC

   We’ve identified an abuse vector as the root cause and begun mitigation efforts. Early signs indicate that the service is recovering.

6. identified Sep 17, 2026, 09:56 PM UTC

   We’ve identified an abuse vector as the root cause and begun mitigation efforts. Early signs indicate that the service is recovering.

7. identified Sep 17, 2026, 11:23 PM UTC

   We’re continuing mitigation efforts and have observed some recovery. Customers may still encounter HTTP 500 errors in the UI and during Git operations when accessing certain projects.

8. identified Sep 17, 2026, 11:23 PM UTC

   We’re continuing mitigation efforts and have observed some recovery. Customers may still encounter HTTP 500 errors in the UI and during Git operations when accessing certain projects.

9. identified Sep 18, 2026, 12:29 AM UTC

   We are continuing mitigation and monitoring recovery. Customers may still encounter HTTP 500 errors in the UI and during Git operations for certain projects. We will provide a further update as mitigation progresses.

10. identified Sep 18, 2026, 12:29 AM UTC

    We are continuing mitigation and monitoring recovery. Customers may still encounter HTTP 500 errors in the UI and during Git operations for certain projects. We will provide a further update as mitigation progresses.

11. investigating Sep 18, 2026, 01:25 AM UTC

    Mitigation has not yet fully restored the GitLab UI and Git operations in certain projects. We are still investigating HTTP 500 errors and will provide a further update as more information becomes available.

12. investigating Sep 18, 2026, 01:25 AM UTC

    Mitigation has not yet fully restored the GitLab UI and Git operations in certain projects. We are still investigating HTTP 500 errors and will provide a further update as more information becomes available.

13. investigating Sep 18, 2026, 02:01 AM UTC

    Investigation continues. We will shortly be restarting the affected Gitaly node after reconfiguration. Further updates will be provided accordingly.

14. investigating Sep 18, 2026, 02:01 AM UTC

    Investigation continues. We will shortly be restarting the affected Gitaly node after reconfiguration. Further updates will be provided accordingly.

15. investigating Sep 18, 2026, 02:34 AM UTC

    The restart of the affected Gitaly node did not improve the issue; HTTP 500 errors continue affecting the GitLab UI and Git operations in certain projects. We are investigating and will provide further updates as the situation changes.

16. investigating Sep 18, 2026, 02:34 AM UTC

    The restart of the affected Gitaly node did not improve the issue; HTTP 500 errors continue affecting the GitLab UI and Git operations in certain projects. We are investigating and will provide further updates as the situation changes.

17. investigating Sep 18, 2026, 03:02 AM UTC

    Further mitigation is being rolled out while we continue to investigate HTTP 500 errors affecting the GitLab UI and Git operations. We will provide further updates as the mitigation progresses.

18. investigating Sep 18, 2026, 03:02 AM UTC

    Further mitigation is being rolled out while we continue to investigate HTTP 500 errors affecting the GitLab UI and Git operations. We will provide further updates as the mitigation progresses.

19. investigating Sep 18, 2026, 04:00 AM UTC

    A further mitigation change has been applied, and we are assessing its impact. HTTP 500 errors continue affecting the GitLab UI and Git operations in certain projects. Further updates will follow.

20. investigating Sep 18, 2026, 04:00 AM UTC

    A further mitigation change has been applied, and we are assessing its impact. HTTP 500 errors continue affecting the GitLab UI and Git operations in certain projects. Further updates will follow.

21. investigating Sep 18, 2026, 06:28 AM UTC

    Further mitigation change are currently being applied, and we are continuing to investigate the issue. HTTP 500 errors may continue affecting the GitLab UI and Git operations in certain projects. Further updates will follow.

22. investigating Sep 18, 2026, 06:28 AM UTC

    Further mitigation change are currently being applied, and we are continuing to investigate the issue. HTTP 500 errors may continue affecting the GitLab UI and Git operations in certain projects. Further updates will follow.

23. investigating Sep 18, 2026, 07:59 AM UTC

    We are currently rolling back the deployment of Gitaly. We're waiting for the deploy to land, and we are continuing the investigation.

24. investigating Sep 18, 2026, 07:59 AM UTC

    We are currently rolling back the deployment of Gitaly. We're waiting for the deploy to land, and we are continuing the investigation.

25. monitoring Sep 18, 2026, 09:01 AM UTC

    A rollback release has been deployed to all Gitaly nodes. They are stable at present. However, we are continuing to monitor the situation.

26. monitoring Sep 18, 2026, 09:01 AM UTC

    A rollback release has been deployed to all Gitaly nodes. They are stable at present. However, we are continuing to monitor the situation.

27. monitoring Sep 18, 2026, 11:07 AM UTC

    Gitaly nodes have stabilized following the completed rollback deployment. The incident has been mitigated and we remain focused on continued monitoring.

28. monitoring Sep 18, 2026, 11:07 AM UTC

    Gitaly nodes have stabilized following the completed rollback deployment. The incident has been mitigated and we remain focused on continued monitoring.

29. resolved Sep 18, 2026, 01:45 PM UTC

    The incident has been resolved following the completion of the rollback deployment across the Gitaly nodes. All nodes have returned to a stable state, repository access has been restored. Incident team is currently investigating the root cause.

Read the full incident report →

Started Sep 11, 2026, 05:50 AM UTC· resolved Sep 11, 2026, 07:22 PM UTC

1. investigating Sep 11, 2026, 05:50 AM UTC

   We’ve detected issues affecting a small subset of users attempting artifact uploads. The team is actively investigating to identify the full scope of the impact, and we’ll provide another update as soon as we have findings to share. Thank you for your patience. 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 Sep 11, 2026, 05:50 AM UTC

   We’ve detected issues affecting artifact uploads. The team is actively investigating, and we’ll provide another update as soon as we have findings to share. Thank you for your patience.

3. monitoring Sep 11, 2026, 12:16 PM UTC

   We are still seeing cases but tat a much less frequent rate. We will continue looking for the root cause and monitor the error rate.

4. monitoring Sep 11, 2026, 12:16 PM UTC

   We are still seeing cases but tat a much less frequent rate. We will continue looking for the root cause and monitor the error rate.

5. resolved Sep 11, 2026, 07:22 PM UTC

   We are no longer observing elevated error rates and have identified the root cause. We are marking this incident as resolved while we implement additional fixes behind the scenes.

Read the full incident report →

Started Sep 10, 2026, 03:24 PM UTC· resolved Sep 10, 2026, 08:10 PM UTC

1. investigating Sep 10, 2026, 03:24 PM UTC

   We are seeing delays in Security Policy Evaluation which are affecting MR approvals. The cause is under investigation. More details in https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22904. 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 Sep 10, 2026, 03:24 PM UTC

   We are seeing delays in Security Policy Evaluation which are affecting MR approvals. The cause is under investigation. More details in https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22904.

3. investigating Sep 10, 2026, 04:02 PM UTC

   Our product team is still working on finding the cause and potential mitigation steps for this issue. More info: gitlab.com/gitlab-com/gl-infra/production/-/work_items/22904.

4. investigating Sep 10, 2026, 04:02 PM UTC

   Our product team is still working on finding the cause and potential mitigation steps for this issue. More info: gitlab.com/gitlab-com/gl-infra/production/-/work_items/22904.

5. investigating Sep 10, 2026, 04:34 PM UTC

   We are still investigating this issue. Users may still experience delays in Security Policy Evaluations, impacting MR approvals. Details in: More info: gitlab.com/gitlab-com/gl-infra/production/-/work_items/22904

6. investigating Sep 10, 2026, 04:34 PM UTC

   We are still investigating this issue. Users may still experience delays in Security Policy Evaluations, impacting MR approvals. Details in: More info: gitlab.com/gitlab-com/gl-infra/production/-/work_items/22904

7. identified Sep 10, 2026, 05:20 PM UTC

   We believe we have identified the underlying problem and are working to implement mitigating changes. More info: gitlab.com/gitlab-com/gl-infra/production/-/work_items/22904

8. identified Sep 10, 2026, 05:20 PM UTC

   We believe we have identified the underlying problem and are working to implement mitigating changes. More info: gitlab.com/gitlab-com/gl-infra/production/-/work_items/22904

9. monitoring Sep 10, 2026, 07:21 PM UTC

   Policy evaluations and MR approvals are executing normally. We're continuing to monitor the situation while working on improvements to prevent this in the future. More: http://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22904

10. monitoring Sep 10, 2026, 07:21 PM UTC

    Policy evaluations and MR approvals are executing normally. We're continuing to monitor the situation while working on improvements to prevent this in the future. More: http://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22904

11. resolved Sep 10, 2026, 08:10 PM UTC

    We'll now mark this as resolved while we look at additional changes as preventative measures for the future.

Read the full incident report →

Started Sep 09, 2026, 04:32 PM UTC· resolved Sep 09, 2026, 06:12 PM UTC

1. investigating Sep 09, 2026, 04:32 PM UTC

   We're observing an increase in CI job queues. Users may see jobs stuck in a pending state for longer than usual. Jobs may not fire their associated webhooks or integrations. Details in: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22897 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 Sep 09, 2026, 04:32 PM UTC

   We're observing an increase in CI job queues. Users may see jobs stuck in a pending state for longer than usual. Jobs may not fire their associated webhooks or integrations. Details in: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22897

3. investigating Sep 09, 2026, 04:58 PM UTC

   We're still observing elevated CI job queues and are working to address the problem. Details in: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22897

4. investigating Sep 09, 2026, 04:58 PM UTC

   We're still observing elevated CI job queues and are working to address the problem. Details in: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22897

5. monitoring Sep 09, 2026, 05:35 PM UTC

   CI job execution delays have improved significantly, and the backlog of pending jobs is shrinking. We're continuing to monitor the situation.

6. monitoring Sep 09, 2026, 05:35 PM UTC

   CI job execution delays have improved significantly, and the backlog of pending jobs is shrinking. We're continuing to monitor the situation.

7. resolved Sep 09, 2026, 06:12 PM UTC

   We are no longer observing delays in CI job execution and the backlog of pending jobs has been worked through. We'll now be marking this as resolved.

Read the full incident report →

Started Sep 08, 2026, 08:54 AM UTC· resolved Sep 08, 2026, 09:57 AM UTC

1. identified Sep 08, 2026, 08:54 AM UTC

   Starting a new chat with an agent from the AI catalog does not work, and the websocket connection is immediately dropped. We are reverting the merge request that introduced the failure. The incident is being tracked in https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22880. 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 Sep 08, 2026, 08:54 AM UTC

   Starting a new chat with an agent from the AI catalog does not work, and the websocket connection is immediately dropped. We are reverting the merge request that introduced the failure. The incident is being tracked in https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22880.

3. resolved Sep 08, 2026, 09:57 AM UTC

   The merge request that introduced the failure was reverted, and custom/catalog agents are working again. More information is available in gitlab.com/gitlab-com/gl-infra/production/-/work_items/22880.

Read the full incident report →

Started Sep 02, 2026, 11:54 AM UTC· resolved Sep 02, 2026, 12:43 PM UTC

1. identified Sep 02, 2026, 11:54 AM UTC

   We are investigating an incident affecting GitLab.com CI/CD jobs using instance runners. Some jobs may remain pending longer than expected or may not be picked up by a runner, which can delay pipelines and deployments. More info: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22845 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 Sep 02, 2026, 11:54 AM UTC

   We are investigating an incident affecting GitLab.com CI/CD jobs using instance runners. Some jobs may remain pending longer than expected or may not be picked up by a runner, which can delay pipelines and deployments.

3. resolved Sep 02, 2026, 12:43 PM UTC

   The incident affecting GitLab.com CI/CD jobs using instance runners is now resolved. Some jobs were delayed or remained pending while a manually initiated pg_repack database maintenance operation caused contention on the CI database, affecting runner communication and job pickup. The maintenance operation was terminated and runner metrics recovered. More info: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22845

Read the full incident report →

Started Aug 27, 2026, 11:46 AM UTC· resolved Aug 27, 2026, 03:34 PM UTC

1. investigating Aug 27, 2026, 11:46 AM UTC

   There are elevated HTTP 500 errors affecting users accessing their Pipelines. Our engineers are actively investigating the issue and working to 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 Aug 27, 2026, 11:46 AM UTC

   There are elevated HTTP 500 errors affecting users accessing their Pipelines. Our engineers are actively investigating the issue and working to restore normal service.

3. monitoring Aug 27, 2026, 11:53 AM UTC

   The issue has been identified and resolved. We are monitoring for changes. More information here: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22807

4. monitoring Aug 27, 2026, 11:53 AM UTC

   The issue has been identified and resolved. We are monitoring for changes. More information here: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22807

5. resolved Aug 27, 2026, 03:34 PM UTC

   Performance remains stable and prevention steps are being implemented. Find more information here: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22807

Read the full incident report →

Started Aug 27, 2026, 07:12 AM UTC· resolved Aug 27, 2026, 09:35 AM UTC

1. investigating Aug 27, 2026, 07:12 AM UTC

   We are currently investigating reports of connectivity issues affecting some users accessing GitLab.com. 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 27, 2026, 07:12 AM UTC

   We are currently investigating reports of connectivity issues affecting some users accessing GitLab.com.

3. monitoring Aug 27, 2026, 07:41 AM UTC

   We have identified a temporary filtering event by an upstream provider that affected some traffic to GitLab.com. The event has ended, and we are working with our service provider to investigate the cause and prevent recurrence. We are monitoring the situation to ensure that services have returned to normal.

4. monitoring Aug 27, 2026, 07:41 AM UTC

   We have identified a temporary filtering event by an upstream provider that affected some traffic to GitLab.com. The event has ended, and we are working with our service provider to investigate the cause and prevent recurrence. We are monitoring the situation to ensure that services have returned to normal.

5. resolved Aug 27, 2026, 09:35 AM UTC

   Our upstream provider mitigated a genuine distributed HTTP DDoS attack against gitlab.com, but incorrectly blocked a small amount of legitimate traffic. This has now been resolved.

Read the full incident report →