# GitLab: Intermittent 404 errors when accessing GitLab.com repositories

- Impact (vendor’s label): minor
- Status: resolved
- Started: 2026-01-26 15:16 UTC · Resolved: 2026-01-26 20:15 UTC · Duration: 5.0 h
- Updates: 4 · Affected components: Website
- [Vendor status page: https://status.gitlab.com/pages/incident/5b36dc6502d06804c08349f7/6977853888370604dd407356](https://status.gitlab.com/pages/incident/5b36dc6502d06804c08349f7/6977853888370604dd407356)
- [Company: GitLab](https://rewindex.com/company/gitlab.md)

## Timeline of updates

- **investigating** 2026-01-26 15:16 UTC: Some GitLab users and automated monitoring tools may see 404 errors when accessing the infrastructure repository on gitlab.com. Workaround: Clearing your browser cache and logging in again to start a new session may resolve the issue. You might need to clear the cache again after the incident if you use the workaround. We're currently investigating and will provide updates as we learn more.
- **monitoring** 2026-01-26 15:30 UTC: The access GitLab.com has been restored, with users now able to log in and access previously affected pages. Both the sign-in page and repository URLs are working again for users, and monitoring alerts have resolved. The request rate for HTTP Router dropped sharply following the change, confirming the mitigation was effective.
- **monitoring** 2026-01-26 16:19 UTC: No changes since the last update. Access to GitLab.com remains restored, and monitoring alerts continue to show normal operation. We're continuing to monitor before marking this issue as resolved.
- **resolved** 2026-01-26 20:15 UTC: The issue has been resolved and systems have returned to normal.


---
Canonical: https://rewindex.com/company/gitlab/incidents/6977853888370604dd407356 · Markdown: https://rewindex.com/company/gitlab/incidents/6977853888370604dd407356.md · JSON: https://rewindex.com/api/v1/companies/gitlab/incidents/6977853888370604dd407356 · Generated 2026-10-18T11:27:48.987Z