GitHub Git handshake disruption on 1 October 2026
GitHub Git handshake from Amsterdam, Mumbai, Singapore, Tokyo: degraded checks; 2026-10-01 20:00 UTC to 2026-10-01 23:00 UTC: peak Git handshake 1.25 s vs a usual 0.7 s.
- What our checks saw
- Degraded
- Cities affected
- Amsterdam, Mumbai, Singapore, Tokyo
- When
- to
- How long
- 3 hours
- Slowest check
- 1.25 s, usually 700 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: San Francisco, Montreal.
Amsterdam
Every check as a table
| Time (UTC) | Check | Reading |
|---|---|---|
| 17:00 | 215 ms | Normal |
| 17:30 | 277 ms | Normal |
| 18:00 | 349 ms | Normal |
| 18:30 | 187 ms | Normal |
| 19:00 | 234 ms | Normal |
| 19:30 | 522 ms | Much slower, or failing |
| 20:00 | 625 ms | Much slower, or failing |
| 20:30 | 195 ms | Normal |
| 21:00 | 1.32 s | Much slower, or failing |
| 21:30 | 211 ms | Normal |
| 22:00 | 226 ms | Normal |
| 22:30 | 373 ms | Normal |
| 23:00 | 205 ms | Normal |
| 23:30 | 181 ms | Normal |
| 00:00 | 183 ms | Normal |
| 00:30 | 189 ms | Normal |
| 01:00 | 186 ms | Normal |
| 01:30 | 172 ms | Normal |
| 02:00 | 193 ms | Normal |
Singapore
Every check as a table
| Time (UTC) | Check | Reading |
|---|---|---|
| 17:00 | 732 ms | Some requests failed |
| 17:30 | 787 ms | Normal |
| 18:00 | 739 ms | Normal |
| 18:30 | 693 ms | Normal |
| 19:00 | 692 ms | Normal |
| 19:30 | 1.18 s | Slower than usual |
| 20:00 | 1.02 s | Normal |
| 20:30 | 710 ms | Normal |
| 21:00 | 1.78 s | Much slower, or failing |
| 21:30 | 699 ms | Normal |
| 22:00 | 728 ms | Normal |
| 22:30 | 782 ms | Normal |
| 23:00 | 720 ms | Normal |
| 23:30 | 674 ms | Normal |
| 00:00 | 696 ms | Normal |
| 00:30 | 709 ms | Normal |
| 01:00 | 722 ms | Normal |
| 01:30 | 701 ms | Normal |
| 02:00 | 728 ms | Normal |
Tokyo
Every check as a table
| Time (UTC) | Check | Reading |
|---|---|---|
| 17:00 | 190 ms | Normal |
| 17:30 | 266 ms | Normal |
| 18:00 | 212 ms | Normal |
| 18:30 | 174 ms | Normal |
| 19:00 | 248 ms | Normal |
| 19:30 | 575 ms | Much slower, or failing |
| 20:00 | 443 ms | Slower than usual |
| 20:30 | 238 ms | Normal |
| 21:00 | 861 ms | Much slower, or failing |
| 21:30 | 232 ms | Normal |
| 22:00 | 176 ms | Normal |
| 22:30 | 297 ms | Normal |
| 23:00 | 167 ms | Normal |
| 23:30 | 173 ms | Normal |
| 00:00 | 179 ms | Normal |
| 00:30 | 189 ms | Normal |
| 01:00 | 178 ms | Normal |
| 01:30 | 179 ms | Normal |
| 02:00 | 203 ms | Normal |
Mumbai
Every check as a table
| Time (UTC) | Check | Reading |
|---|---|---|
| 17:00 | 287 ms | Normal |
| 17:30 | 378 ms | Normal |
| 18:00 | 296 ms | Normal |
| 18:30 | 258 ms | Normal |
| 19:00 | 311 ms | Normal |
| 19:30 | 800 ms | Much slower, or failing |
| 20:00 | 796 ms | Much slower, or failing |
| 20:30 | 410 ms | Normal |
| 21:00 | 1.54 s | Much slower, or failing |
| 21:30 | 276 ms | Normal |
| 22:00 | 272 ms | Normal |
| 22:30 | 316 ms | Normal |
| 23:00 | 261 ms | Normal |
| 23:30 | 275 ms | Normal |
| 00:00 | 272 ms | Normal |
| 00:30 | 276 ms | Normal |
| 01:00 | 261 ms | Normal |
| 01:30 | 264 ms | Normal |
| 02:00 | 268 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.