CheckUpstream measured GitHub at 99.773% availability across 2201 independent checks (global · api). 129 incidents were recorded in the past 12 months; the most recent resolved earlier today after 45 minutes. Status signals are polled from GitHub's official Atlassian Statuspage status page, alongside independent probes and community reports. GitHub publishes 1 product-level SLA uptime commitment (up to 99.9%), and service credits must be claimed within 30 days of a breach.
Share of our own checks against GitHub endpoints that returned GitHub's expected response. Evidence that their API edge is answering correctly — not that every product behind it works.
Vendor disclosed: 129 incidents · 347 of 365 days with none posted · 2d 12h of declared impact
Fewer incidents in the last 30 days than 3% of 232 tracked services.
Share of each window with no impact declared by GitHub
7d
100.000%
30d
99.885%
90d
99.922%
180d
98.609%
1y
99.314%
Downtime like this can be refundable
If you're a paying GitHub customer, outages in these windows may count against GitHub's SLA — vendors owe service credits for missed uptime targets, but only if you file inside the deadline. CheckUpstream tracks the entitlement, drafts the claim, and hands you the filing link.
A GitHub outage only matters if something you ship depends on it. Point us at a public repository and we will read its dependencies and tell you — no account, nothing stored.
Time to resolve, from GitHub's own incident posts (1 year)
Median time to resolve
1h 29m
Slowest 10% take longer than
6h 20m
From 129 incidents GitHub published and resolved in the last 1 year, measured between their own start and resolution times. It describes how long GitHub takes to close an incident they have acknowledged — not how often they have them, and not how available they were.
GitHub READMEs, GitLab, MDX docs — links to the live reliability page.
Frequently Asked Questions
›Is GitHub currently down?
GitHub is currently Operational. CheckUpstream tracks GitHub in real-time across the official status page, RSS / Atom feeds, and community telemetry. Refresh this page for the latest reading.
›When did GitHub last have an outage?
GitHub's last resolved incident started earlier today and lasted 45 minutes (degraded performance).
GitHub's 30-day measured availability is 99.773%, from CheckUpstream's own probes against GitHub endpoints. It is the share of checks that returned the expected response, not a figure taken from GitHub's status page.
›How do I monitor GitHub in production?
Sign up to CheckUpstream and add GitHub to a watchlist. We send incident alerts via Slack, email, webhook, or PagerDuty within seconds of detection, covering both the official status page and community signals (HN, Reddit, Bluesky, Cloudflare Radar).
›How does CheckUpstream track GitHub?
We poll GitHub's official status page on a 1-5 minute cadence, parse its RSS / Atom feed as a fallback, ingest community signals from social platforms, and aggregate per-org SDK telemetry. Multiple sources reduce false positives versus any single feed alone.