← Back to GitHub's live status
We started measuring GitHub on August 8, 2026, which is 60 days ago. Everything below covers that period, not the full 90 days a longer-tracked service would show.
Email me the next time we see GitHub go down
The last 24 hours
What happened most recently, on one time axis: our own probe readings by surface, how many people reported a problem, and what GitHub's own status page declared. Below it, any public chatter we saw about GitHub and the extra probe it triggered.
The last 24 hours on one axis: what our probes read for each surface we check, how many people reported a problem, and what GitHub's own status page declared. Three records side by side; none of them changes another.
- Incident with Actions: major outage, from 19:00 UTC to now, still open per their page.
Each probe cell is the worst reading across every region in that quarter hour: one region that did not answer colours the cell, never an average. An amber cell is a reading that answered, but at three times or more its 7-day median for three checks running: slow is not down, and we say which. A filtered reading stays neutral, because a refused probe is not an outage. Report bars count unverified reports, not people we verified; they never change our reading. The status-page lane is GitHub's own declaration, shown as they made it.
Third-party chatter, labeled
Public posts from the last hour that mention GitHub next to an outage word (“down”, “outage”, “not working”). This is what other people said in public, collected by keyword: not something we measured, and not the user reports above. It never affects the verdict.
- Bluesky posts3 in the last hour (prior day averaged 0.4/hour)
- Confirmation probe20:55 UTC, Europe: their own status feed changing prompted an extra probe. Result: GitHub answered normally.
- Confirmation probe20:55 UTC, UK: their own status feed changing prompted an extra probe. Result: GitHub answered normally.
- Confirmation probe20:55 UTC, Australia: their own status feed changing prompted an extra probe. Result: GitHub answered normally.
- Confirmation probe20:55 UTC, US-West: their own status feed changing prompted an extra probe. Result: GitHub answered normally.
- Confirmation probe20:55 UTC, US-East: their own status feed changing prompted an extra probe. Result: GitHub answered normally.
Availability by region
Availability is measured probes that succeeded, divided by every probe we attempted, per region. Not interpolated, not smoothed, and never computed for a region with zero recorded samples.
| Region | Availability | Probes recorded |
|---|---|---|
| US-East | 99.84% | 32845 |
| US-West | 99.83% | 32084 |
| Europe | 99.83% | 30527 |
| Asia-Pacific | 99.76% | 27073 |
| US-Central | 99.37% | 11898 |
| Canada | 99.89% | 11927 |
| UK | 99.43% | 11855 |
| Southeast Asia | 99.13% | 11477 |
| Australia | 99.69% | 11424 |
| South America | 99.91% | 11703 |
Monthly summary
Tracking GitHub since Aug 8, 2026. In that time our probes detected 1 outage, 5 min in total. Months before that date are not tracked and carry no figure.
| Month | Uptime | Outages | Downtime |
|---|---|---|---|
| Nov 2025 | not tracked | ||
| Dec 2025 | not tracked | ||
| Jan 2026 | not tracked | ||
| Feb 2026 | not tracked | ||
| Mar 2026 | not tracked | ||
| Apr 2026 | not tracked | ||
| May 2026 | not tracked | ||
| Jun 2026 | not tracked | ||
| Jul 2026 | not tracked | ||
| Aug 2026 from Aug 8, 2026 | 100% | 0 | 0 min |
| Sep 2026 | 99.99% | 1 | 5 min |
| Oct 2026 | 100% | 0 | 0 min |
Uptime here is the share of each month in which our probes had no outage open for GitHub: two consecutive failed readings from a region opens one, the first clean reading closes it. Any detected outage counts, including one seen from a single region, and an outage that crosses midnight on the first of a month is counted in both months with its minutes split. User reports, public posts and GitHub's own status page contribute nothing to these figures.
Our incident log
Every outage our own probes detected for GitHub in the last 90 days, or since we started measuring it if that is more recent. This list is probe-only: GitHub's own declared incidents appear further down this page in their own attributed section, never merged with what we measured here. User reports live on the live page, in their own labeled block.
Permanent incident records
Every closed GitHub incident RealUptime has ever detected gets its own permanent, citable page: the region-by-region timeline, exactly as measured, that stays up even after the incident log above ages out of this 90-day window.
Their declared record
GitHub's own incident history, taken from their public status feed. This is their account of what happened, not our measurement, and it never changes the incident log above or the other way around.
Showing the 10 most recent of 77 incidents GitHub has declared in the history we hold.
These entries are GitHub's own declarations, taken from their public status feed, shown separately from the outages we detected ourselves. Their page publishes what they choose to publish: an incident missing here means they did not declare one, not that nothing happened, and an incident here is their account, not our measurement. Neither record ever changes the other.
The scorecard
How GitHub's status page compared with what we measured, for every outage above that falls inside the window we have been capturing their claims.
We started recording GitHub's own status page on August 20, 2026, 46 days ago. This comparison covers that period only, we do not reconstruct what they said before it, and we compare only inside outages we measured ourselves.
GitHub's status page reported all systems operational for 5 minutes while we measured GitHub down in 2 of our regions.
GitHub decides what their status page covers, and it may report per component while our check reaches one surface from ten regions. We state what each side measured and leave the conclusion to you. If GitHub believes a figure here is wrong, we publish corrections as prominently as the original.
Full detail on what a probe does and does not prove is in the methodology page.