Changes / GitLab / 403 errors impacting CI/CD pipelines
GitLab: Major incident: 403 errors impacting CI/CD pipelines
Summary
Summary pending. The diff below shows exactly what changed.
Major incidentLabel: outage (model (Jev), 94%)Changed Detected Source: status.gitlab.com (opens in new tab)
Incident page: full timeline of updates →
What changed
Before: not present
After: 403 errors impacting CI/CD pipelines
Before: not present
After: major
Before: not present
After: resolved
Before: not present
After: 2026-02-25 19:36 UTC
Before: not present
After: 2026-02-25 21:14 UTC
Before: not present
After: CI/CD, Git Operations
Before: not present
After: We observed increased 403 errors on Git HTTPS requests affecting some CI/CD pipelines on GitLab.com. The underlying issue has been corrected and we are monitoring to ensure stability. Details in: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/21389
Before: not present
After: We observed increased 403 and 429 errors on Git HTTPS requests affecting some CI/CD pipelines on GitLab.com. We have adjusted our protection rules to alleviate these errors and are monitoring to ensure stability. Details: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/21389
Before: not present
After: We have not seen any further reports of 403 or 429 errors on Git HTTPS requests, and customers should no longer be experiencing related CI/CD pipeline issues. As the service has remained stable, we will now resolve this incident. Details in: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/21389
First version of this incident archived by Rewindex. View the live incident (opens in new tab).
History of this incident
| When (UTC) | Change | Kind |
|---|---|---|
| Major incident: 403 errors impacting CI/CD pipelines (this change) | Major incident |