GitLab: 500 Errors on GitLab-org Repository
Affected components: Website
Timeline of updates
- identified
The gitlab-org group are seeing 500 errors due to a specific Gitaly node. We are working to bring things back online but anyone accessing that repository, such as through pipelines or other tasks, will experience errors accessing it.
- monitoring
We are seeing things recover now and users should now be able to access the gitlab-org namespace. We are doing integrity checks to understand if there is any lingering impact on the impacted system.
- resolved
Operations have returned to normal and the gitlab-org repository is accessible as normal.
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves this record existed by then and has not been changed since, by anyone, Rewindex included.
How the archive is checked, and what it cannot prove.
First version captured
In the 2026-10-18 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
920b9927bdc814bb…
Impact, status and times are the vendor’s own, as last archived. View on status.gitlab.com (opens in new tab).
Cite this
Status incident (vendor impact label: minor) posted by GitLab, started 2026-03-24 17:39 UTC, resolved after 46 min, 3 update(s).
- Title
- 500 Errors on GitLab-org Repository
- Vendor
- GitLab
- Date
- URL
- https://rewindex.com/company/gitlab/incidents/69c2cc4d27d5a90a0618bfca
GitLab profileRecent GitLab incidentsAll outages on March 24, 2026GitLab in March 2026MarkdownJSON