Is GitLab down?

Some users are not able to generate security reports in pipelines. We've indetified the cause and are working on mitigation. More info: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23024 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

Some users are not able to generate security reports in pipelines. We've indetified the cause and are working on mitigation. More info: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23024

No material updates at this time. Mitigation efforts are ongoing. More info: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23024

No material updates at this time. Mitigation efforts are ongoing. More info: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23024

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

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

A fix is being implemented and we will update here once it's complete. More info: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23024

A fix is being implemented and we will update here once it's complete. More info: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23024

The changes we've tried have so far been ineffective. The fix is still in progress. More info: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23024

The changes we've tried have so far been ineffective. The fix is still in progress. More info: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23024

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

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

The fix is still being implemented and progress is being made on resolving the problem. More info: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23024

The fix is still being implemented and progress is being made on resolving the problem. More info: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23024

The team continues to work on mitigating the underlying cause of the issue. More info: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23024

The team continues to work on mitigating the underlying cause of the issue. More info: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23024

The fix has been deployed and we're seeing our graphs return to normal. Users should no longer be seeing missing security reports. We'll continue to monitor for now. More info: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23024

The fix has been deployed and we're seeing our graphs return to normal. Users should no longer be seeing missing security reports. We'll continue to monitor for now. More info: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23024

Graphs continue to drop and security report functionality should now be normal. We're resolving this incident. If you have further issues with security reports, please contact support. More info: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23024

We are recieving reports of 503 errors on GitLab.com. This is under active investigation. We will update with more details shortly. 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 recieving reports of 503 errors on GitLab.com. This is under active investigation. We will update with more details shortly.

We are recieving reports of 503 errors on GitLab.com. This is under active investigation. We will update with more details shortly.

We are recieving reports of 503 errors on GitLab.com. This is under active investigation. We will update with more details shortly.

We've identified the cause of 503 errors on GitLab.com and are working on mitigating the issue. We will update with more details shortly.

We've identified the cause of 503 errors on GitLab.com and are working on mitigating the issue. We will update with more details shortly.

We've identified the cause of 503 errors on GitLab.com and are working on mitigating the issue. We're aware that the API is also affected. We will update with more details shortly.

We've identified the cause of 503 errors on GitLab.com and are working on mitigating the issue. We're aware that the API is also affected. We will update with more details shortly.

We are seeing some recovery based on our mitigation efforts, which are ongoing. We will update with more details shortly.

We are seeing some recovery based on our mitigation efforts, which are ongoing. We will update with more details shortly.

We are seeing some recovery based on our mitigation efforts, which are ongoing. We will update with more details shortly.

We are seeing some recovery based on our mitigation efforts, which are ongoing. We will update with more details shortly.

Error rate is decreasing after active mitigation efforts. We're still actively working on addressing the root cause. We will update with more details shortly.

Error rate is decreasing after active mitigation efforts. We're still actively working on addressing the root cause. We will update with more details shortly.

Error rate is decreasing after active mitigation efforts. We're still actively working on addressing the root cause. We will update with more details shortly.

Error rate is decreasing after active mitigation efforts. We're still actively working on addressing the root cause. We will update with more details shortly.

Error rates are decreasing, but some customers may still see errors. We are continuing to address the remaining impact and will update again soon.

Error rates are decreasing, but some customers may still see errors. We are continuing to address the remaining impact and will update again soon.

Error rates are decreasing, but some customers may still see errors. We are continuing to address the remaining impact and will update again soon.

Error rates are decreasing, but some customers may still see errors. We are continuing to address the remaining impact and will update again soon.

GitLab remains stable and error rates have decreased. We are still actively engaging in recovery efforts.

GitLab remains stable and error rates have decreased. We are still actively engaging in recovery efforts.

GitLab services are now operational and we're continuing to monitor the situation. We are assessing any outstanding impacts during the disruption window.

GitLab services are now operational and we're continuing to monitor the situation. We are assessing any outstanding impacts during the disruption window.

GitLab services are operational and we're continuing to monitor the situation. We are assessing any outstanding impacts during the disruption window.

GitLab services are operational and we're continuing to monitor the situation. We are assessing any outstanding impacts during the disruption window.

GitLab services are operational and we're continuing to monitor the situation. We are assessing any outstanding impacts during the disruption window.

GitLab services are operational and we're continuing to monitor the situation. We are assessing any outstanding impacts during the disruption window.

This incident has been resolved. GitLab.com is operating normally, and we are continuing to monitor the service.

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

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.

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

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

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

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.

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.

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

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

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

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

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

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

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

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

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

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.

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. Website Google Compute Engine Partial Service Disruption API Google Compute Engine Operational Git Operations Google Compute Engine Partial Service Disruption Package Registry Google Compute Engine Operational Container Registry Google Compute Engine Operational GitLab Pages Google Compute Engine Operational CI/CD Google Compute Engine Operational CI/CD - Hosted runners on Linux Google Compute Engine Operational CI/CD - Hosted runners on Windows Google Compute Engine Operational CI/CD - Hosted runners on macOS Google Compute Engine AWS Operational CI/CD - Hosted runners for GitLab community contributions Google Compute Engine Operational CI/CD - Self-managed runners Self-Managed Runner Connectivity Operational SAML SSO - GitLab SaaS Google Compute Engine Operational Background Processing Google Compute Engine Operational GitLab Customers Portal Google Compute Engine Operational Support Services Zendesk Operational packages.gitlab.com AWS Operational version.gitlab.com AWS Operational forum.gitlab.com Digital Ocean Operational docs.gitlab.com Google Compute Engine Operational Canary Google Compute Engine Operational GitLab Duo Google Compute Engine Operational GitLab agent server for Kubernetes Google Compute Engine Operational 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 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 Website Google Compute Engine Partial Service Disruption API Google Compute Engine Operational Git Operations Google Compute Engine Partial Service Disruption Package Registry Google Compute Engine Operational Container Registry Google Compute Engine Operational GitLab Pages Google Compute Engine Operational CI/CD Google Compute Engine Operational CI/CD - Hosted runners on Linux Google Compute Engine Operational CI/CD - Hosted runners on Windows Google Compute Engine Operational CI/CD - Hosted runners on macOS Google Compute Engine AWS Operational CI/CD - Hosted runners for GitLab community contributions Google Compute Engine Operational CI/CD - Self-managed runners Self-Managed Runner Connectivity Operational SAML SSO - GitLab SaaS Google Compute Engine Operational Background Processing Google Compute Engine Operational GitLab Customers Portal Google Compute Engine Operational Support Services Zendesk Operational packages.gitlab.com AWS Operational version.gitlab.com AWS Operational forum.gitlab.com Digital Ocean Operational docs.gitlab.com Google Compute Engine Operational Canary Google Compute Engine Operational GitLab Duo Google Compute Engine Operational GitLab agent server for Kubernetes Google Compute Engine Operational 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

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

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

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.

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

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.

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.

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.

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.

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.

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.

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.

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.

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.

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

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

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.