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.
90 days measured availability how this is computed
99.773%
global · api · n=2201 · p95 198ms (30d)
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: 77 incidents · 88 of 90 days with none posted · 1h 40m 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.
Track your GitHub entitlement →Does GitHub actually matter to you?
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.
Check a repository →From 77 incidents GitHub published and resolved in the last 90 days, 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.
Aug 31, 09:15 UTC · resolved in 45m · Resolved
Aug 27, 10:04 UTC · resolved in 2h 10m · Resolved
Aug 26, 23:37 UTC · resolved in 20h 7m · Resolved
6signals across 1 source
HN 6
Live GitHub status for your README or docs. Updates itself — no API key, no maintenance.
[](https://checkupstream.com/reliability/github)GitHub READMEs, GitLab, MDX docs — links to the live reliability page.
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.
GitHub's last resolved incident started earlier today and lasted 45 minutes (degraded performance).
Looking for the live "is GitHub down" view? See the GitHub Live status page.
Aug 26, 22:56 UTC · resolved in 1h 37m · Resolved
Aug 24, 07:12 UTC · resolved in 7m · Resolved
Aug 18, 09:36 UTC · resolved in 48m · Resolved
Aug 18, 07:40 UTC · resolved in 4h 9m · Resolved
Aug 17, 13:40 UTC · resolved in 7h 40m · Resolved
Aug 13, 16:21 UTC · resolved in 8m · Resolved
Aug 13, 16:21 UTC · resolved in 2h 13m · Resolved
Aug 13, 14:45 UTC · resolved in 54m · Resolved
Aug 13, 14:43 UTC · resolved in 1h 11m · Resolved
Aug 12, 21:40 UTC · resolved in 10m · Resolved
Aug 12, 21:39 UTC · resolved in 1h 26m · Resolved
Aug 12, 16:16 UTC · resolved in 34m · Resolved
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.
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).
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.