# GitLab: 403 errors across GitLab.com

- Impact (vendor’s label): critical
- Status: resolved
- Started: 2026-08-21 15:56 UTC · Resolved: 2026-08-21 16:25 UTC · Duration: 29 min
- Updates: 2 · Affected components: CI/CD, Git Operations, Website
- [Vendor status page: https://status.gitlab.com/pages/incident/5b36dc6502d06804c08349f7/6a8875116314b0477dc5b734](https://status.gitlab.com/pages/incident/5b36dc6502d06804c08349f7/6a8875116314b0477dc5b734)
- [Company: GitLab](https://rewindex.com/company/gitlab.md)

## Timeline of updates

- **monitoring** 2026-08-21 15:56 UTC: 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
- **resolved** 2026-08-21 16:25 UTC: 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

## Rewindex changes for this incident

- 2026-08-21 15:56 UTC: [Critical incident: 403 errors across GitLab.com](https://rewindex.com/change/i0b74d395b1edda.md)


---
Canonical: https://rewindex.com/company/gitlab/incidents/6a8875116314b0477dc5b734 · Markdown: https://rewindex.com/company/gitlab/incidents/6a8875116314b0477dc5b734.md · JSON: https://rewindex.com/api/v1/companies/gitlab/incidents/6a8875116314b0477dc5b734 · Generated 2026-10-18T09:36:46.607Z