GitLab
MistyDegraded
Degraded since — Increase of HTTP 50X errors on GitLab.com
Recent incidents latest 10 by start time · newest first
Recovery estimateSimilar GitLab incidents typically clear in 2h 52m–9h 40m (median ~4h 56m).
Latest official update · 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.
Resolved · lasted 20h 44m
Resolved · lasted 7h 40m
Resolved · lasted 2h 35m
Resolved · lasted 3h 19m
Resolved · lasted 11h 39m
Resolved · lasted 18h 14m
Resolved · lasted 5h 20m
Resolved · lasted 4h 56m
Resolved · lasted 7h 7m
Last 30 days worst confirmed state per UTC day · newest first
Questions from the forecast desk
Is GitLab down right now?
GitLab is degraded. Checked . Since . Incident: Increase of HTTP 50X errors on GitLab.com
Where does this data come from?
Tech Weather checks GitLab's official status page every five minutes.
How are unconfirmed signals handled?
Early signals need two independent sources and are always labeled unconfirmed. They never become a confirmed outage without the official status page.