Active Incident

Updated a few seconds ago

This status page is exclusively intended for monitoring GitLab.com and its associated services. If there are any performance or service interruptions, an update will be posted here. If you are experiencing an issue that is not related to an active GitLab.com incident, or if you are encountering service interruptions on GitLab Dedicated, please submit a request via https://support.gitlab.com.
We are experiencing 5XX errorsOperational

Incident Status

Operational

Components

Website, API, Git Operations

Locations

Google Compute Engine


March 11, 2026 16:35 UTC
MONITORING

GitLab is currently operational and the incident has been mitigated. We're currently monitoring and will provide an update at a later time.

March 11, 2026 16:11 UTC
IDENTIFIED

Our team has taken steps to mitigate the issue and services are back to normal. Our team is monitoring and discussing next steps.

March 11, 2026 15:56 UTC
INVESTIGATING

We are experiencing 5XX errors. The cause for the errors is under investigation.
Users reporting 403 Forbidden responses when downloading NuGet packagesOperational

Incident Status

Operational

Components

Website, API

Locations

Google Compute Engine


March 11, 2026 16:51 UTC
MONITORING

The MR in question has been reverted and error rates have decreased. We are currently monitoring this endpoint.

March 11, 2026 03:29 UTC
IDENTIFIED

Starting from approximately 08:00 UTC on 2026-03-10, multiple users were unable to download NuGet packages due to 403 Forbidden errors. We have identified the cause, and are going through the process of reverting the MR.
CI/CD Job processing delayOperational

Incident Status

Operational

Components

Background Processing

Locations

Google Compute Engine


March 10, 2026 18:31 UTC
MONITORING

Background processing has recovered and CI wait times are back to normal. Our team is continuing to monitor for stability.

March 10, 2026 17:28 UTC
MONITORING

We're seeing stabilization and recovery but are still monitoring and discussing next steps. More info in: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/21498

March 10, 2026 16:43 UTC
IDENTIFIED

Our team has identified the issue as PgBouncer saturation and are looking at mitigation efforts. Users may see small delays in background processing. More information in: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/21498

March 10, 2026 16:16 UTC
INVESTIGATING

No material updates at this time. Our team is still investigating this issue.

March 10, 2026 16:01 UTC
INVESTIGATING

Our team is investigating potential delays with background job processing. This could impact CI/CD job processing.

Website




Operational

API




Operational

Git Operations




Operational

Container Registry




Operational

GitLab Pages




Operational

CI/CD




Operational

CI/CD - Hosted runners on Linux




Operational

CI/CD - Hosted runners on Windows




Operational

CI/CD - Hosted runners on macOS




Operational

CI/CD - Hosted runners for GitLab community contributions




Operational

CI/CD - Self-managed runners




Operational

SAML SSO - GitLab SaaS




Operational

Background Processing




Operational

GitLab Customers Portal




Operational

Support Services




Operational

packages.gitlab.com




Operational

version.gitlab.com




Operational

forum.gitlab.com




Operational

docs.gitlab.com




Operational

Canary




Operational

GitLab Duo




Operational

GitLab agent server for Kubernetes




Operational