Is GitHub Down?
Real-time status monitoring
As of 5/21/2026, 3:09:11 AM, GitHub is operational.
📡 Monitor GitHub uptime every 30 seconds — get alerted in under a minute
Trusted by 100,000+ websites · Free tier available
⚡ Get notified instantly when GitHub goes down
Email alerts in under 60 seconds. 14-day free trial — $0 today.
Embed GitHub Status Badge
Show live GitHub status in your README, documentation, or website
[](https://apistatuscheck.com/api/github)<a href="https://apistatuscheck.com/api/github"><img src="https://apistatuscheck.com/api/badge/github" alt="GitHub Status" /></a>Response Time (24h)
Recent Incidents
Incident with Actions
May 20, 04:58 PM — Resolved May 20, 08:14 PM
This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.
Actions is experiencing degraded availability
May 15, 08:13 AM — Resolved May 15, 08:48 AM
On May 15, 2026, from approximately 07:43 UTC to 08:48 UTC, GitHub Actions experienced a degradation that caused workflow runs to fail or experience delayed starts for a subset of customers. The incident was triggered by a planned failover of supporting infrastructure used by GitHub Actions. During that operation, an automated service discovery update did not propagate correctly, which caused traffic to be routed incorrectly and increased request timeouts in a core dependency for workflow orchestration. At peak impact, 42% of Actions runs failed. Downstream services that depend on Actions workflow execution were also impacted, including GitHub Pages and Copilot cloud services. At 08:12 UTC, responders manually corrected the service discovery routing issue. Timeout and failure rates recovered shortly after, and we continued monitoring until full stabilization was confirmed across all affected services. The incident was marked resolved at 08:48 UTC. To prevent recurrence, we are implementing failover guardrails that validate service discovery state before completing failover operations, strengthening pre-flight and post-flight verification checks, and improving dependency resilience to reduce timeout cascades during infrastructure events.
[Retroactive] Incident with GitHub.com
May 15, 01:30 AM — Resolved May 15, 02:30 AM
Beginning at 02:49 UTC on May 15 2026 and lasting until 03:04 UTC, GitHub.com was unavailable for a subset of customers. This impact has been mitigated and normal service resumed. The issue was rooted in a sudden spike in traffic, with intermittent impact. We've identified the source of the traffic and prevented further disruption.
Incident with CodeQL
May 13, 02:41 PM — Resolved May 13, 04:03 PM
This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.
Incident with CodeQL, Webhooks, Notifications, and Slack Integration
May 12, 02:38 PM — Resolved May 12, 05:43 PM
This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.
Get GitHub Outage Alerts
Be the first to know when GitHub go down.
GitHub Down? Try These Steps
- Check the official GitHub status page for announcements
- Try refreshing your browser or clearing cache
- Check your internet connection
- Try accessing from a different network or VPN
- Check social media for reports from other users
- Set up automated monitoring so you know before your users do — Better Stack monitors every 30 seconds
Is GitHub down for everyone or just me?
To determine whether it's a widespread GitHub outage or a problem specific to your account or location:
- Check the status indicator above — if this page shows a major outage, it's confirmed global.
- Try a different device or network — if it works on mobile data but not Wi-Fi, it's likely a local network issue, not GitHub.
- Clear cache and cookies — browser issues can mimic service outages.
- Check community reports — Downdetector and social media will show whether hundreds of other users are reporting the same issue.
- Test the API directly (for developers) — a raw request returning 5xx errors confirms a service-side outage; a 429 means you've hit your personal rate limit.
Official source: GitHub Status Page
The average API outage costs $5,600 per minute
Gartner estimates downtime costs $5,600/min on average. 98% of organizations say a single hour of downtime costs over $100,000. Proactive monitoring catches issues in under 30 seconds.
🔧 Recommended Tools
Know when GitHub goes down before your users complain. 30-second checks, instant alerts.
Trusted by 100,000+ websites · Free tier available
Better Stack — Start FreeManage API keys, database passwords, and service tokens securely. Rotate automatically when breaches occur.
Trusted by 150,000+ businesses · From $2.99/mo
1Password — Try FreeMonitor GitHub and 100+ APIs with instant email alerts. 14-day free trial.
Complete GitHub Troubleshooting Guide
In-depth guide with step-by-step troubleshooting, common error codes, workarounds, and what to do during GitHub outages.
Read the full guideRelated Services
Check the status of other developer-tools services and APIs
More for GitHub
Complete GitHub Guide
In-depth troubleshooting with step-by-step instructions, common error codes, workarounds, and alternatives during outages.
Read the full guideRecommended Tools
See all →Monitors your APIs every 30 seconds with instant alerts via Slack, email, SMS, and phone calls.
Securely manage API keys, database passwords, and service tokens with CLI integration and auto-rotation.
Helpful Resources
Never get caught off guard by an outage
Get instant email alerts when APIs go down. Monitor up to 10 APIs for $9/mo — that's less than 1 minute of downtime costs.
14-day free trial. $0 due today. Cancel anytime.