Search

Changes / GitLab / 403 errors across GitLab.com

GitLab: Critical incident: 403 errors across GitLab.com

Summary

Summary pending. The diff below shows exactly what changed.

Major incidentLabel: critical (vendor)Changed Detected Source: status.gitlab.com (opens in new tab)

Incident page: full timeline of updates →

What changed

AddedTitle#1
Before: not present
After: 403 errors across GitLab.com
AddedImpact#2
Before: not present
After: critical
AddedStatus#3
Before: not present
After: resolved
AddedStart time#4
Before: not present
After: 2026-08-21 15:56 UTC
AddedResolved time#5
Before: not present
After: 2026-08-21 16:25 UTC
AddedAffected components#6
Before: not present
After: CI/CD, Git Operations, Website
AddedUpdatemonitoring#7
Before: not present
After: We're monitoring an incident where 403s were seen across GitLab.com. The fix for this is already in place. More about the incident here: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22762
AddedUpdateresolved#8
Before: not present
After: The elevated 403 errors affecting GitLab.com have been resolved and error rates have returned to normal levels. More details in: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22762

First version of this incident archived by Rewindex. View the live incident (opens in new tab).

History of this incident

When (UTC)ChangeKind
Critical incident: 403 errors across GitLab.com (this change)Major incident

All GitLab changes → · GitLab profile · Markdown · JSON