GitHub Git handshake incidents in October 2026
Slowdowns and failures our checks confirmed, newest first. Shorter slow spells only show on the live status page.
- Slower than usualMumbai
, lasted 90 minutes · peak 581 ms, usually 280 ms
What happened → - DegradedAmsterdam, Mumbai, Singapore
, lasted 4 hours · peak 1.20 s, usually 711 ms
What happened →
- DegradedAmsterdam, Mumbai, Singapore, Tokyo
, lasted 3 hours · peak 1.21 s, usually 709 ms
What happened → - DegradedAmsterdam, Mumbai, Singapore
, lasted 2.5 hours · peak 1.19 s, usually 708 ms
What happened → - DegradedAmsterdam, Mumbai, Tokyo
, lasted 2 hours · peak 657 ms, usually 280 ms
What happened → - DegradedAmsterdam, Mumbai, San Francisco, Tokyo
, lasted 2 hours · peak 940 ms, usually 190 ms
What happened →
- DegradedAmsterdam, Mumbai, Singapore, Tokyo
, lasted 2 hours · peak 1.39 s, usually 707 ms
What happened → - DegradedAmsterdam, Mumbai, San Francisco, Singapore, Tokyo, Montreal
, lasted 7.5 hours · peak 1.29 s, usually 708 ms
What happened → - DegradedTokyo
, lasted 2 hours · peak 487 ms, usually 188 ms
What happened →
- DegradedAmsterdam, Mumbai, Singapore, Tokyo
, lasted 2 hours · peak 1.09 s, usually 708 ms
What happened →
- DegradedAmsterdam, Mumbai, Tokyo
, lasted 2 hours · peak 882 ms, usually 190 ms
What happened → - DegradedAmsterdam, Mumbai, Tokyo
, lasted 2 hours · peak 539 ms, usually 276 ms
What happened →
- DegradedAmsterdam, Mumbai, Singapore, Tokyo
, lasted 3 hours · peak 1.25 s, usually 700 ms
What happened → - DegradedAmsterdam, Mumbai, Singapore, Tokyo
, lasted 4 hours · peak 1.06 s, usually 700 ms
What happened →
GitHub Git handshake status right now
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.
No account required · Takes about 30 seconds.