GitHub Outage Check
Is GitHub Down Right Now?
✅ GitHub is up and working normally. Checked: 5:10 PM (GMT+8).
Auto-refreshing live data in 60s
| Component | Status |
|---|---|
| Actions | Operational |
| API Requests | Operational |
| Codespaces | Operational |
| Copilot | Operational |
| Copilot AI Model Providers | Operational |
| Git Operations | Operational |
| Issues | Operational |
| Packages | Operational |
| Pages | Operational |
| Pull Requests | Operational |
| Visit www.githubstatus.com for more information | Operational |
| Webhooks | Operational |
99.500%
Uptime
67m
MTTR
6.7
Avg Incidents / Mo
90 Days AgoToday
GitHub Network Congestion in Transit Provider
A major tier-1 network transit provider experienced packet loss in Europe and North America.
Duration: 1h 40m
Affected: Website, DNS Services
GitHub Database Failover and Connection Backlog
A hardware failure on the primary database cluster triggered an automatic failover to the replica.
Duration: 53m
Affected: Core Service, Website
GitHub Network Congestion in Transit Provider
A major tier-1 network transit provider experienced packet loss in Europe and North America.
Duration: 1h 57m
Affected: Website, DNS Services
GitHub Network Congestion in Transit Provider
A major tier-1 network transit provider experienced packet loss in Europe and North America.
Duration: 1h 44m
Affected: Website, DNS Services
GitHub Network Congestion in Transit Provider
A major tier-1 network transit provider experienced packet loss in Europe and North America.
Duration: 1h 47m
Affected: Website, DNS Services
Are you having problems with GitHub?
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.
Uptime Alternatives
GitLab
DevSecOps platform with Git repositories.
Bitbucket
Atlassian Git repository hosting.
Yes, GitHub 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 67 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.