Is GitHub Down?
Real-time status monitoring
As of 3/3/2026, 3:22:51 AM, GitHub is experiencing issues.
🚨 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
Delayed visibility of newly added issues on project boards
Mar 2, 11:10 PM
Project board updates — including adding issues, pull requests, and changing fields such as "Status" — are currently delayed by 1–2 hours. Normal behavior is near-real-time. We're actively investigating the root cause.
Incident with Pull Requests /pulls
Mar 2, 07:11 PM — Resolved Mar 2, 10:04 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 Copilot agent sessions
Feb 27, 11:18 PM — Resolved Feb 27, 11:49 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.
Code view fails to load when content contains some non-ASCII characters
Feb 27, 03:08 AM — Resolved Feb 27, 06:04 AM
Starting February 26, 2026 at 22:10 UTC through February 27, 05:50 UTC, the repository browsing UI was degraded and users were unable to load pages for files and directories with non-ASCII characters (including Japanese, Chinese, and other non-Latin scripts). On average, the error rate was 0.014% and peaked at 0.06% of requests to the service. Affected users saw 404 errors when navigating to repository directories and files with non-ASCII names. This was due to a code change that altered how file and directory names were processed, which caused incorrectly formatted data to be stored in an application cache.We mitigated the incident by deploying a fix that invalidated the affected cache entries and progressively rolling it out across all production environments.We are working to improve our pre-production testing to cover non-ASCII character handling, establish better cache invalidation mechanisms, and enhance our monitoring to detect this type of failure mode earlier, to reduce our time to detection and mitigation of issues like this one in the future.
High latency on webhook API requests
Feb 27, 12:01 AM — Resolved Feb 27, 12:04 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.
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
Related Services
Check the status of other developer-tools services and APIs
More for GitHub
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.
Free tier available. No credit card required.