GitHub Outage History
This page tracks recent GitHub availability checks, current status, and short outage history for github.com. We detect outages from anonymous aggregated status checks only, then use the timeline below to show whether failures look isolated or widespread.
A failed check does not always mean a global outage. Local DNS issues, ISP routing, captive portals, or firewall policy can block you while the service remains reachable elsewhere.
Current status
Live status uses the existing status checker and shows whether the latest probe was up or down, along with response time and the most recent check timestamp.
Refreshing status...
Status is a practical signal, not a global guarantee. A host can appear up here while local DNS, ISP routing, or firewall rules still block your path.
Checking...
Recent outages
Recent outage history is inferred from aggregated check history only. We do not collect user reports, login data, or personal identifiers.
| Date | Duration | Status |
|---|---|---|
| Last 72 hours | No outages | Stable |
24-hour status timeline
Green means reachable, red means unreachable, and grey means no recent aggregated check was available for that hour bucket.
Recent checks over the last 24 hours
A red block means the site appeared unreachable during that check. This does not always mean a global outage.
No recent checks yet
Latest checks
No recent check data yet. Use “Check Again” to generate a fresh entry.
What causes outages
Server overload
Traffic spikes can overwhelm front-end or API capacity.
Infrastructure failure
Load balancers, databases, or edge networks can fail.
DNS issues
Resolver or DNS propagation problems can break access before HTTP.
Regional outages
A service may fail in one geography while staying up elsewhere.
Cloud provider issues
Shared cloud incidents can impact many services at once.
For GitHub, developer platforms often have partial incidents where package registries, ci, or dashboards degrade separately from the primary website.
Troubleshooting
- Refresh the page and run the live check again.
- Try another network connection to separate local issues from broader outages.
- Check the official GitHub status page if one is published.
- Flush DNS cache or switch resolvers if name resolution looks inconsistent.
- Try again later if recent checks show an ongoing outage or unstable recovery.