GitHub logo

GitHub Git handshake disruption on 7 October 2026

GitHub Git handshake from Amsterdam, Mumbai, Singapore, Tokyo: degraded checks; 2026-10-07 22:00 UTC to 2026-10-08 00:00 UTC: peak Git handshake 1.39 s vs a usual 0.71 s.

What our checks saw
Degraded
Cities affected
Amsterdam, Mumbai, Singapore, Tokyo
When
to
How long
2 hours
Slowest check
1.39 s, usually 707 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

Incident0 ms1.00 s2.00 s19:0022:0001:00
Each check (UTC)Usual (190 ms)Much slower, or failingSlow check outside the incidentIncident
Every check as a table
Time (UTC)CheckReading
19:00207 msNormal
19:30225 msNormal
20:00208 msNormal
20:30261 msNormal
21:00847 msMuch slower, or failing
21:30191 msNormal
22:001.00 sMuch slower, or failing
22:30254 msNormal
23:00304 msNormal
23:30196 msNormal
00:00221 msNormal
00:301.69 sMuch slower, or failing
01:00191 msNormal
01:30182 msNormal
02:00229 msNormal
02:30179 msNormal
03:00189 msNormal

Singapore

Incident0 ms1.25 s2.50 s19:0022:0001:00
Each check (UTC)Usual (707 ms)Much slower, or failingIncident
Every check as a table
Time (UTC)CheckReading
19:00825 msNormal
19:30754 msNormal
20:00747 msNormal
20:30774 msNormal
21:001.02 sNormal
21:30682 msNormal
22:002.06 sMuch slower, or failing
22:30713 msNormal
23:00784 msNormal
23:30689 msNormal
00:00718 msNormal
00:301.06 sNormal
01:00696 msNormal
01:30695 msNormal
02:00728 msNormal
02:30678 msNormal
03:00716 msNormal

Tokyo

Incident0 ms750 ms1.50 s19:0022:0001:00
Each check (UTC)Usual (188 ms)Much slower, or failingSlow check outside the incidentIncident
Every check as a table
Time (UTC)CheckReading
19:00263 msNormal
19:30196 msNormal
20:00202 msNormal
20:30266 msNormal
21:00535 msMuch slower, or failing
21:30197 msNormal
22:00876 msMuch slower, or failing
22:30208 msNormal
23:00355 msNormal
23:30189 msNormal
00:00190 msNormal
00:30993 msMuch slower, or failing
01:00177 msNormal
01:30198 msNormal
02:00205 msNormal
02:30182 msNormal
03:00182 msNormal

Mumbai

Incident0 ms750 ms1.50 s19:0022:0001:00
Each check (UTC)Usual (279 ms)Much slower, or failingSlow check outside the incidentIncident
Every check as a table
Time (UTC)CheckReading
19:00447 msNormal
19:30298 msNormal
20:00418 msNormal
20:30357 msNormal
21:00966 msMuch slower, or failing
21:30270 msNormal
22:001.33 sMuch slower, or failing
22:30350 msNormal
23:00460 msNormal
23:30271 msNormal
00:00325 msNormal
00:301.22 sMuch slower, or failing
01:00275 msNormal
01:30282 msNormal
02:00313 msNormal
02:30294 msNormal
03:00344 msNormal

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.