Increase of HTTP 50X errors on GitLab.com
degraded
GitLab · Ongoing · 2h 5m
Recovery estimateSimilar GitLab incidents typically clear in 2h 52m–9h 40m (median ~4h 56m).
Recorded timeline
- Started · investigatingOctober 13, 2026 07:10 UTC Investigating - We are currently investigating reports of an increase of HTTP 50X errors on GitLab.com
- Update · investigatingOctober 13, 2026 07:10 UTC Investigating - We are currently investigating reports of an increase of HTTP 50X errors on GitLab.com October 13, 2026 07:30 UTC Investigating - We are seeing an improvement in errors rates in our monitoring, starting from 07:14 UTC. We are still identifying the root cause.
- Update · investigatingOctober 13, 2026 07:10 UTC Investigating - We are currently investigating reports of an increase of HTTP 50X errors on GitLab.com October 13, 2026 07:30 UTC Investigating - We are seeing an improvement in errors rates in our monitoring, starting from 07:14 UTC. We are still identifying the root cause. October 13, 2026 07:48 UTC Investigating - General GitLab.com service continues to improve. We're now focused on restoring Duo services.
- Update · investigatingOctober 13, 2026 07:10 UTC Investigating - We are currently investigating reports of an increase of HTTP 50X errors on GitLab.com October 13, 2026 07:30 UTC Investigating - We are seeing an improvement in errors rates in our monitoring, starting from 07:14 UTC. We are still identifying the root cause. October 13, 2026 07:48 UTC Investigating - General GitLab.com service continues to improve. We're now focused on restoring Duo services. October 13, 2026 07:59 UTC Monitoring - We are seeing improvements across all services on GitLab.com. We are resuming our investigation on identifying the root cause.