Is GitLab down?

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

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

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

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

We are currently receiving reports and investigating issues with signing into GitLab.com. We will provide more information once it is available. Back to current status Status History Subscribe to receive status updates by email Close Subscribe Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates by webhook Each status update will POST a JSON payload to this URL Email address for managing webhook Close Subscribe Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates in Microsoft Teams Enter your Microsoft Teams webhook. View Instructions Email address for managing subscription Close Subscribe Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates via RSS RSS Feed Close Follow our status updates on Twitter/X @gitlabstatus Close Subscribe to receive status updates in Slack Slack channel ID Find the channel ID: Select the channel in your Slack workspace. The channel ID is displayed in the browser URL. Example: https://app.slack.com/client/T04SJBK1C/ C03SKGJ1P Email address Close Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates via iCalendar iCalendar Feed Close

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

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

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

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

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

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

We're investigating an issue affecting GitLab Duo Custom Agents on GitLab.com. Our team is actively working to identify the cause and restore normal service. Back to current status Status History Subscribe to receive status updates by email Close Subscribe Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates by webhook Each status update will POST a JSON payload to this URL Email address for managing webhook Close Subscribe Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates in Microsoft Teams Enter your Microsoft Teams webhook. View Instructions Email address for managing subscription Close Subscribe Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates via RSS RSS Feed Close Follow our status updates on Twitter/X @gitlabstatus Close Subscribe to receive status updates in Slack Slack channel ID Find the channel ID: Select the channel in your Slack workspace. The channel ID is displayed in the browser URL. Example: https://app.slack.com/client/T04SJBK1C/ C03SKGJ1P Email address Close Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates via iCalendar iCalendar Feed Close

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

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

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

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

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

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

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

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

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

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

We are investigating degraded performance affecting package pulls from our registry. Users may experience slow or failed Omnibus package downloads while we investigate. Currently, the engineering team has identified the cause of the degraded performance and is currently working to resolve the issue. Users may continue to experience slow or failed Omnibus package downloads while mitigation is in progress. Back to current status Status History Subscribe to receive status updates by email Close Subscribe Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates by webhook Each status update will POST a JSON payload to this URL Email address for managing webhook Close Subscribe Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates in Microsoft Teams Enter your Microsoft Teams webhook. View Instructions Email address for managing subscription Close Subscribe Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates via RSS RSS Feed Close Follow our status updates on Twitter/X @gitlabstatus Close Subscribe to receive status updates in Slack Slack channel ID Find the channel ID: Select the channel in your Slack workspace. The channel ID is displayed in the browser URL. Example: https://app.slack.com/client/T04SJBK1C/ C03SKGJ1P Email address Close Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates via iCalendar iCalendar Feed Close

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

We're aware of elevated errors affecting AI Gateway health checks. We've identified a likely cause and are actively working on a fix. Details in: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22519 Back to current status Status History Subscribe to receive status updates by email Close Subscribe Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates by webhook Each status update will POST a JSON payload to this URL Email address for managing webhook Close Subscribe Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates in Microsoft Teams Enter your Microsoft Teams webhook. View Instructions Email address for managing subscription Close Subscribe Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates via RSS RSS Feed Close Follow our status updates on Twitter/X @gitlabstatus Close Subscribe to receive status updates in Slack Slack channel ID Find the channel ID: Select the channel in your Slack workspace. The channel ID is displayed in the browser URL. Example: https://app.slack.com/client/T04SJBK1C/ C03SKGJ1P Email address Close Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates via iCalendar iCalendar Feed Close

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

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

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

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

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

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

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

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

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

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

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

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