GitLab Outage Check
Is GitLab Down Right Now?
✅ GitLab is up and working normally. Checked: 4:05 AM (GMT+8).
Auto-refreshing live data in 60s
GitLab's Official Status Page
- CI/CD pipelines and GitLab Runners
- Merge requests and code reviews
- Container Registry pulls
- Third-party OAuth via GitLab login
| Component | Status |
|---|---|
| API Portal | Operational |
| Core Service | Operational |
| OAuth Integrations | Operational |
| Website | Operational |
SLA Grade: A+
Based on 90-day verified uptime
100.000%
Uptime
66m
Mean Resolution Time (MTTR)
6.7
Avg Incidents / Month
69d ago
Last Incident
90 Days AgoToday
GitLab Network Congestion in Transit Provider
A major tier-1 network transit provider experienced packet loss in Europe and North America.
Duration: 52m
Affected: Website, DNS Services
GitLab Network Congestion in Transit Provider
A major tier-1 network transit provider experienced packet loss in Europe and North America.
Duration: 1h 54m
Affected: Website, DNS Services
GitLab Database Failover and Connection Backlog
A hardware failure on the primary database cluster triggered an automatic failover to the replica.
Duration: 57m
Affected: Core Service, Website
GitLab Network Congestion in Transit Provider
A major tier-1 network transit provider experienced packet loss in Europe and North America.
Duration: 1h 58m
Affected: Website, DNS Services
GitLab Network Congestion in Transit Provider
A major tier-1 network transit provider experienced packet loss in Europe and North America.
Duration: 34m
Affected: Website, DNS Services
Are you having problems with GitLab?
Submit your report to help alert other developers.
Downtime Reports: Last 2 Hours
2 Hours AgoNow
Troubleshooting Guide
- 1Hard RefreshBypass cache (Ctrl+F5 or Cmd+Shift+R).
- 2Flush DNSRun
ipconfig /flushdns. - 3Check with alternative networkTry loading the site on a mobile cellular network or over a VPN. If it loads, the issue lies in your local ISP provider network routing.
Uptime Alternatives
GitHub
Leading developer platform.
Slack
Real-time team communication.
Yes, GitLab maintains an official status page. However, our real-time tracker aggregates reports faster.
Historical records indicate that the mean time to resolve (MTTR) is approximately 66 minutes.
Outages can happen due to configuration mistakes, database freezes, edge network issues, or infrastructure drops.
You can subscribe to live alerts on this page. We send emails on status updates.
Try bypass caching by executing hard refresh, flush local DNS, or use alternatives listed below.
Bitbucket Status
npm Registry Status
Vercel Status
Netlify Status