Monitoring
GitLab.com · outage
Increase of HTTP 50X errors on GitLab.com
Started 13 Oct 07:10 UTC; still ongoing when ChangeIntel last read it, just now.
What it affected
As the provider names itWhat the provider posted
Newest first- today 02:33 UTCMonitoringMonitoring 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 UTCMonitoringWe are seeing improvements across all services on GitLab.com. We are resuming our investigation on identifying the root cause.
- 13 Oct 07:48 UTCInvestigatingGeneral GitLab.com service continues to improve. We're now focused on restoring Duo services.
- 13 Oct 07:30 UTCInvestigatingWe 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 UTCInvestigatingWe are currently investigating reports of an increase of HTTP 50X errors on GitLab.com
Around it
From the sources ChangeIntel reads; a match in time is not a causeElsewhere at the same time
- Cloudflare Audit Logs v2 ingestion is missing multiple Cloudflare products
- Cloudflare Elevated Errors in China Network Colos
- Cloudflare Cloudflare One Clients are incorrectly challenged on some sites
- Cloudflare Network performance issues in Ashburn, US (IAD)
- Microsoft 365 admin center Admin center: Service degradation
- Microsoft 365 admin center Admin center: Service degradation
Earlier incidents in the 14 days before
- GitLab.com: Errors and slow performance on merge requests in the specific groups.Service incident · 10 Oct
Changed in the 14 days before
- GitLab Critical Patch Release: 19.4.2, 19.3.5, 19.2.8Revised by Microsoft · 2 times, latest 12 Oct
- GitLab AI Gateway Critical Patch Release: 19.2.4, 19.3.2, and 19.4.1Security advisory · 2 Oct
What changed
First observed 14 Oct 2026No field changes in the recorded history.
Cite this recorded revision to keep the same title, summary, facts and links when the page changes.
A day selects the latest observation by the end of that UTC day; today's selection can change until midnight. History starts when this installation records it.
Keep track
- Service status now: every provider ChangeIntel reads, with ongoing incidents first.
- Status RSS feed: new and ended incidents as they happen.
- Everything about GitLab: its changes, known issues and incidents on one timeline.