GitHub Git handshake disruption on 7 October 2026
GitHub Git handshake from Tokyo: degraded checks; 2026-10-07 01:00 UTC to 2026-10-07 03:00 UTC: peak Git handshake 0.49 s vs a usual 0.19 s.
- What our checks saw
- Degraded
- Cities affected
- Tokyo
- When
- to
- How long
- 2 hours
- Slowest check
- 487 ms, usually 188 ms
- GitHub's status page
- Open it
Where our checks saw it
Each glowing city had slow or failing checks during the incident, shown at its worst. We test from 6 cities, so other places may have been hit too.
Our checks, city by city
Each point is one check every 30 minutes, from three hours before the incident to three hours after. Coloured points are the checks we counted as slower or failing. The shaded area shows how far above the usual time they were. Not affected: Amsterdam, San Francisco, Montreal, Singapore, Mumbai.
Tokyo
Every check as a table
| Time (UTC) | Check | Reading |
|---|---|---|
| 22:00 | 196 ms | Normal |
| 22:30 | 181 ms | Normal |
| 23:00 | 200 ms | Normal |
| 23:30 | 192 ms | Normal |
| 00:00 | 901 ms | Much slower, or failing |
| 00:30 | 189 ms | Normal |
| 01:00 | 774 ms | Much slower, or failing |
| 01:30 | 199 ms | Normal |
| 02:00 | 229 ms | Normal |
| 02:30 | 173 ms | Normal |
| 03:00 | 197 ms | Normal |
| 03:30 | 171 ms | Normal |
| 04:00 | 198 ms | Normal |
| 04:30 | 507 ms | Much slower, or failing |
| 05:00 | 203 ms | Normal |
| 05:30 | 208 ms | Normal |
| 06:00 | 246 ms | Normal |
How fast is your API around the world?
Run a free speed test from multiple cities and find out where your users are waiting. No setup, no account required.
Test my API
No account required · Takes about 30 seconds.