GitHub Git handshake slowdown on 9 October 2026
GitHub Git handshake from Mumbai: slower than usual; 2026-10-09 14:00 UTC to 2026-10-09 15:30 UTC: peak Git handshake 0.58 s vs a usual 0.28 s.
- What our checks saw
- Slower than usual
- Cities affected
- Mumbai
- When
- to
- How long
- 90 minutes
- Slowest check
- 581 ms, usually 280 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, Tokyo.
Mumbai
Every check as a table
| Time (UTC) | Check | Reading |
|---|---|---|
| 11:00 | 712 ms | Much slower, or failing |
| 11:30 | 300 ms | Normal |
| 12:00 | 476 ms | Normal |
| 12:30 | 305 ms | Normal |
| 13:00 | 824 ms | Much slower, or failing |
| 13:30 | 600 ms | Slower than usual |
| 14:00 | 561 ms | Slower than usual |
| 14:30 | 285 ms | Normal |
| 15:00 | 353 ms | Normal |
| 15:30 | 270 ms | Normal |
| 16:00 | 324 ms | Normal |
| 16:30 | 292 ms | Normal |
| 17:00 | 274 ms | Normal |
| 17:30 | 287 ms | Normal |
| 18:00 | 279 ms | Normal |
| 18:30 | 338 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.