Developer platforms
Is GitHub down?
Live GitHub status, measured independently. We probe 10 GitHub endpoints from monitoring regions on every continent and record every outage we detect.
GitHub is having problems
Some of our probes are failing. GitHub may be partially down or degraded in specific regions.
Checked every minute from 6 regions on every continent.
- Uptime, 24 hoursUptime, last 24 hours
- Uptime, 7 daysUptime, last 7 days
- Uptime, 30 daysUptime, last 30 days
- Website99.78% uptime, 30 days6 regions, 15 to 413 msUnknownp50median response119 msp95slowest 5% of checks253 ms200 ms100024 h ago12 h agonow
- Git Operations100% uptime, 30 days6 regions, 171 to 305 msUnknownp50median response245 msp95slowest 5% of checks421 ms500 ms250024 h ago12 h agonow
- API Requests95.38% uptime, 30 days6 regions, 46 to 394 msUnknownp50median response261 msp95slowest 5% of checks739 ms500 ms250024 h ago12 h agonow
- Issues99.99% uptime, 30 days6 regions, 576 to 703 msUnknownp50median response650 msp95slowest 5% of checks839 ms1000 ms500024 h ago12 h agonow
- Pull Requests99.98% uptime, 30 days6 regions, 696 to 856 msUnknownp50median response776 msp95slowest 5% of checks994 ms2000 ms1000024 h ago12 h agonow
- Packages100% uptime, 30 days6 regions, 151 to 331 msUnknownp50median response235 msp95slowest 5% of checks364 ms500 ms250024 h ago12 h agonow
- Pages100% uptime, 30 days6 regions, 7 to 10 msUnknownp50median response9 msp95slowest 5% of checks72 ms20 ms10024 h ago12 h agonow
- Raw content99.26% uptime, 30 days6 regions, 7 to 10 msUnknownp50median response9 msp95slowest 5% of checks182 ms20 ms10024 h ago12 h agonow
- Official status feed83.32% uptime, 30 days6 regions, 158 to 507 msUnknownp50median response308 msp95slowest 5% of checks507 ms500 ms250024 h ago12 h agonow
- DNS100% uptime, 30 days6 regions, 0 to 15 msUnknownp50median response4 msp95slowest 5% of checks67 ms10 ms5024 h ago12 h agonow
Daily strip:99.9% or better95–99.9%below 95%no data yet
Get notified when GitHub goes down
Follow these 10 checks from your own workspace and get alerted through Slack, email, webhooks, or on-call the moment GitHub goes down. They don't count against your monitor quota. Free plan, no card required.
About GitHub outages
GitHub hosts source code, reviews, and CI for a very large share of software teams, so a GitHub outage rarely stays a GitHub problem. Pushes fail, pull requests will not merge, Actions runs queue for an hour, and deploy pipelines that pull from GitHub stall silently.
GitHub incidents are often partial: git operations work while Actions is degraded, or the website is fine while the API returns errors. We probe each surface separately, the website, Git over HTTPS, the REST API, Issues and Pull Requests, Packages on ghcr.io, Pages, and raw file downloads, plus GitHub's own status feed, so you can tell which part is affected.
What we check
Every row is a real monitor in upti.my, running from each of our regions. A failure in some regions marks the row degraded; failures from every region mark it down and open an outage.
| Check | Target | Expects | Interval |
|---|---|---|---|
Website github.com itself is unreachable or erroring. Browsing repositories and reviewing pull requests is affected. | httpgithub.com | HTTP 200 | 1 min |
Git Operations The Git smart-HTTP handshake fails. git clone, fetch, and push over HTTPS are broken. | httpgithub.com/octocat/Hello-World.git/info/refs | HTTP 200 | 1 min |
API Requests A real REST API call fails. CLI tools, integrations, Dependabot, and anything using the API break. | httpapi.github.com/repos/octocat/Hello-World | HTTP 200 | 5 min |
Issues Issue pages are not loading. | httpgithub.com/octocat/Hello-World/issues | HTTP 200 | 2 min |
Pull Requests Pull request pages are not loading. Code review is blocked. | httpgithub.com/octocat/Hello-World/pulls | HTTP 200 | 2 min |
Packages The GitHub Container Registry is not answering its normal authentication challenge. docker pull from ghcr.io fails. | httpghcr.io/v2/ | HTTP 401 | 1 min |
Pages GitHub Pages hosting is unreachable. Project and documentation sites hosted on Pages are down. | httppages.github.com | HTTP 200 | 2 min |
Raw content raw.githubusercontent.com is failing. Install scripts, CI, and tools that fetch files directly break. | httpraw.githubusercontent.com/octocat/Hello-World/master/README | HTTP 200 | 1 min |
Official status feed GitHub's Statuspage-hosted status feed is unreachable. Rare, but it means you cannot rely on the official page either. | httpwww.githubstatus.com/api/v2/status.json | HTTP 200 | 5 min |
DNS github.com is not resolving. Every GitHub service is unreachable by name. | dnsgithub.com | A record resolves | 1 min |
For component-level detail and incident write-ups from the vendor, see GitHub's official status page.
Recent GitHub outages we detected
An outage is recorded when a probe fails from every monitoring region and closed when it recovers. Partial and single-region problems show as degraded above but are not listed here.
GitHub is up. Is your GitHub integration?
The incidents that actually hurt are usually not global outages. They are the parts of your own system that depend on GitHub and fail quietly. Here is what teams that rely on GitHub monitor on their side.
Scheduled Actions workflows that quietly stop
GitHub disables scheduled workflows in inactive repositories after 60 days and delays cron triggers under load. A heartbeat on each scheduled workflow tells you when a run did not happen, whatever the cause.
Heartbeat monitoring for scheduled jobsDeploys that pull from GitHub
If your deploy pipeline clones from GitHub, a GitHub outage becomes a deploy outage. Monitor the deploy result, not only the trigger.
Why started does not mean finishedWebhooks from GitHub into your systems
Push and PR webhooks are retried only briefly. If your receiver relies on them, watch for the gap when they stop arriving.
Webhook monitoringGitHub status: frequently asked questions
Partially. GitHub runs Actions, git operations, the API, Packages, and Pages as separate systems and they degrade independently. Our API and website probes can both be green while Actions queues are backed up, which is why we also link GitHub's official component-level status.
api.github.com allows 60 unauthenticated requests per hour per IP address, and that budget is shared with anyone else behind the same address. A one-minute probe would sit at the limit and produce false alarms, so we check less often from each region.
Look at the per-region results above. If our probes fail from every region, GitHub has a real outage and it will appear in the outage list. If they succeed everywhere, the problem is most likely on your side: your network, DNS resolver, a browser extension, a corporate proxy, or your own integration. If only some regions fail, GitHub may have a regional incident that does not affect you.
Every probe runs at least every five minutes from each monitoring region, and most run every minute. This page refreshes its data every minute. Uptime figures are calculated from all checks across all regions.
Official status is updated by people after an incident is confirmed and often lags the first failures by many minutes; our probes react within a minute or two. In the other direction, we only see public endpoints, so an internal incident may not show on our probes. Use both.
Yes. Use "Notify me about GitHub" above: your upti.my workspace follows these exact checks, free plan included, and every outage opens an incident there and routes alerts to Slack, email, webhooks, or on-call. Nothing is duplicated and it doesn't use your monitor quota. Better still, also monitor your own dependency on GitHub: the API route, webhook receiver, or scheduled job that calls it, so you learn about the failure that actually affects your users.
Related
GitHub Actions scheduled workflows stop silently
How to catch skipped and delayed scheduled runs.
Uptime monitoring checklist
What to monitor beyond the homepage.
Other developer platforms
upti.my is not affiliated with GitHub. GitHub and related marks are the property of their respective owners and are used here only to identify the service being measured. Results reflect the reachability of public endpoints from our monitoring regions and may differ from the vendor's own reporting.