⚪ Unknown
Increase of HTTP 50X errors on GitLab.com
Investigating
- Started
- 2026-10-13 07:10 UTC
24 days ago - Last update
- 2026-10-14 23:40 UTC
22 days ago - Running for
- 24d 13h
Timeline
-
14 Oct · 23:40 UTC
⚪ Investigating
rss
October 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.
October 14, 2026 02:33 UTC
Monitoring - 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.
October 14, 2026 23:40 UTC
Resolved - We have been monitoring this issue for a few days with no reported occurrences. -
14 Oct · 02:33 UTC
⚪ Investigating
rss
October 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.
October 14, 2026 02:33 UTC
Monitoring - 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. -
13 Oct · 07:59 UTC
⚪ Investigating
rss
October 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. -
13 Oct · 07:48 UTC
⚪ Investigating
rss
October 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. -
13 Oct · 07:30 UTC
⚪ Investigating
rss
October 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. -
13 Oct · 07:10 UTC
⚪ Investigating
rss
October 13, 2026 07:10 UTC
Investigating - We are currently investigating reports of an increase of HTTP 50X errors on GitLab.com
Source
Official GitLab status — view original incident ↗
IT Status normalizes vendor wording into a common vocabulary and rewrites machine-shaped titles for readability. The vendor's page remains authoritative.