GitHub Git handshake disruption on 8 October 2026
GitHub Git handshake from Amsterdam, Mumbai, Singapore: degraded checks; 2026-10-08 13:00 UTC to 2026-10-08 15:30 UTC: peak Git handshake 1.19 s vs a usual 0.71 s.
- What our checks saw
- Degraded
- Cities affected
- Amsterdam, Mumbai, Singapore
- When
- to
- How long
- 2.5 hours
- Slowest check
- 1.19 s, usually 708 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, Tokyo.
Amsterdam
Every check as a table
| Time (UTC) | Check | Reading |
|---|---|---|
| 10:00 | 333 ms | Normal |
| 10:30 | 260 ms | Normal |
| 11:00 | 373 ms | Normal |
| 11:30 | 232 ms | Normal |
| 12:00 | 760 ms | Much slower, or failing |
| 12:30 | 392 ms | Normal |
| 13:00 | 628 ms | Much slower, or failing |
| 13:30 | 350 ms | Normal |
| 14:00 | 260 ms | Normal |
| 14:30 | 279 ms | Normal |
| 15:00 | 190 ms | Normal |
| 15:30 | 507 ms | Much slower, or failing |
| 16:00 | 518 ms | Much slower, or failing |
| 16:30 | 366 ms | Normal |
| 17:00 | 1.00 s | Much slower, or failing |
| 17:30 | 290 ms | Normal |
| 18:00 | 279 ms | Normal |
| 18:30 | 185 ms | Normal |
Singapore
Every check as a table
| Time (UTC) | Check | Reading |
|---|---|---|
| 10:00 | 759 ms | Normal |
| 10:30 | 764 ms | Normal |
| 11:00 | 794 ms | Normal |
| 11:30 | 741 ms | Normal |
| 12:00 | 716 ms | Normal |
| 12:30 | 858 ms | Normal |
| 13:00 | 1.31 s | Slower than usual |
| 13:30 | 1.07 s | Slower than usual |
| 14:00 | 722 ms | Normal |
| 14:30 | 763 ms | Normal |
| 15:00 | 1.01 s | Normal |
| 15:30 | 1.31 s | Slower than usual |
| 16:00 | 1.04 s | Normal |
| 16:30 | 714 ms | Normal |
| 17:00 | 1.66 s | Slower than usual |
| 17:30 | 759 ms | Normal |
| 18:00 | 769 ms | Normal |
| 18:30 | 699 ms | Normal |
Mumbai
Every check as a table
| Time (UTC) | Check | Reading |
|---|---|---|
| 10:00 | 344 ms | Normal |
| 10:30 | 459 ms | Normal |
| 11:00 | 503 ms | Normal |
| 11:30 | 407 ms | Normal |
| 12:00 | 930 ms | Much slower, or failing |
| 12:30 | 757 ms | Much slower, or failing |
| 13:00 | 333 ms | Normal |
| 13:30 | 811 ms | Much slower, or failing |
| 14:00 | 418 ms | Normal |
| 14:30 | 500 ms | Normal |
| 15:00 | 325 ms | Normal |
| 15:30 | 613 ms | Slower than usual |
| 16:00 | 671 ms | Slower than usual |
| 16:30 | 369 ms | Normal |
| 17:00 | 1.22 s | Much slower, or failing |
| 17:30 | 368 ms | Normal |
| 18:00 | 532 ms | Slower than usual |
| 18:30 | 288 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.