Changes / GitLab / Increase of HTTP 50X errors on GitLab.com
GitLab: Critical incident: Increase of HTTP 50X errors on GitLab.com
Summary
Summary pending. The diff below shows exactly what changed.
Incident page: full timeline of updates →
What changed
Before: not present
After: Increase of HTTP 50X errors on GitLab.com
Before: not present
After: critical
Before: not present
After: resolved
Before: not present
After: 2026-10-13 07:10 UTC
Before: not present
After: 2026-10-14 23:40 UTC
Before: not present
After: API, Container Registry, GitLab Duo, Git Operations, Package Registry, Website
Before: not present
After: We are currently investigating reports of an increase of HTTP 50X errors on GitLab.com
Before: not present
After: We are seeing an improvement in errors rates in our monitoring, starting from 07:14 UTC. We are still identifying the root cause.
Before: not present
After: General GitLab.com service continues to improve. We're now focused on restoring Duo services.
Before: not present
After: We are seeing improvements across all services on GitLab.com. We are resuming our investigation on identifying the root cause.
Before: not present
After: Monitoring confirms that GitLab.com services have remained stable. We are continuing to monitor for any recurrence of the issues before marking this incident as resolved.
Before: not present
After: We have been monitoring this issue for a few days with no reported occurrences.
First version of this incident archived by Rewindex. View the live incident (opens in new tab).
History of this incident
| When (UTC) | Change | Kind |
|---|---|---|
| Critical incident: Increase of HTTP 50X errors on GitLab.com (this change) | Major incident |