Is GitHub Down?
Real-time status monitoring
As of 7/16/2026, 9:51:10 PM, GitHub is experiencing issues.
📡 Monitor GitHub uptime every 30 seconds — get alerted in under a minute
Trusted by 100,000+ websites · Free tier available
🚨 GitHub is experiencing issues
Stop refreshing this page. Get instant email alerts when GitHub recovers.
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
Claude Fable 5 experiencing degraded performance
Jul 16, 09:05 PM
We are experiencing degraded availability for the Claude Fable 5 model in Copilot products and IDE surfaces. This is due to an issue with an upstream model provider. While we work with them to resolve the issue, we recommend choosing another model or selecting 'Auto' to continue using Copilot.
Disruption with some GitHub services
Jul 16, 09:13 AM — Resolved Jul 16, 12:20 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 Webhooks
Jul 14, 05:38 PM — Resolved Jul 14, 06:01 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.
Disruption with some GitHub services
Jul 14, 08:21 AM — Resolved Jul 14, 09:56 AM
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 runs are experiencing failures to start
Jul 13, 01:32 PM — Resolved Jul 13, 01:53 PM
On July 13, 2026, between 13:11 and 13:53 UTC, some customers experienced failures starting and running GitHub Actions workflows, which also affected Copilot cloud agent sessions and GitHub Pages builds since they depend on Actions. During the peak of the incident, 30% of Actions jobs failed to start and 2% were delayed more than 5 minutes. The incident was triggered by a configuration change in an internal autoscaling component that contained outdated capacity threshold values. This caused a critical Actions service to scale below its required baseline, reducing capacity for workflow processing. We identified the regression, rolled back the change, and restored service capacity. New workflow executions recovered by 13:39 UTC. Full recovery was reached by 13:53 UTC after the queued backlog was drained. To prevent recurrence, we have added deployment guardrails to validate that autoscaling inputs are current and to detect drift between planned and live scaling state before autoscaling changes are applied.
Get GitHub Outage Alerts
Be the first to know when GitHub go down.
Alert Pro
14-day free trialStop checking — get alerted instantly
Next time GitHub goes down, you'll know in under 60 seconds — not when your users start complaining.
- Email alerts for GitHub + 9 more APIs
- $0 due today for trial
- Cancel anytime — $9/mo after trial
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.
⚡ GitHub Outage Response Kit
ACTIVE INCIDENTGet alerted the instant GitHub recovers — and catch the next outage before your users do.
Trusted by 100,000+ websites · Free tier available
Better Stack — Start FreeOutages can expose API keys and tokens. Rotate credentials now — don't wait for the post-mortem.
Trusted by 150,000+ businesses · From $2.99/mo
1Password — Try FreeGet email alerts for GitHub + 100 other APIs. Know instantly when services go down or recover.
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.