GitHub Git handshake disruption on 30 September 2026

GitHub Git handshake from Amsterdam, Mumbai, Singapore, Tokyo: degraded checks; 2026-09-30 14:30 UTC to 2026-09-30 18:00 UTC: peak Git handshake 1.45 s vs a usual 0.7 s.

What our checks saw: Degraded
Cities affected: Amsterdam, Mumbai, Singapore, Tokyo
When: 30 Sept, 14:30 UTC to 30 Sept, 18:00 UTC
How long: 3.5 hours
Slowest check: 1.46 s, usually 698 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

Each check (UTC)Usual (190 ms)Much slower, or failingSlow check outside the incidentIncident

Every check as a table

Time (UTC)	Check	Reading
11:30	198 ms	Normal
12:00	224 ms	Normal
12:30	226 ms	Normal
13:00	305 ms	Normal
13:30	614 ms	Much slower, or failing
14:00	198 ms	Normal
14:30	1.27 s	Much slower, or failing
15:00	194 ms	Normal
15:30	195 ms	Normal
16:00	808 ms	Much slower, or failing
16:30	250 ms	Normal
17:00	255 ms	Normal
17:30	192 ms	Normal
18:00	228 ms	Normal
18:30	803 ms	Much slower, or failing
19:00	213 ms	Normal
19:30	300 ms	Normal
20:00	213 ms	Normal
20:30	218 ms	Normal
21:00	296 ms	Normal

Singapore

Each check (UTC)Usual (698 ms)Slower than usualMuch slower, or failingSlow check outside the incidentIncident

Every check as a table

Time (UTC)	Check	Reading
11:30	717 ms	Normal
12:00	707 ms	Normal
12:30	714 ms	Normal
13:00	720 ms	Normal
13:30	823 ms	Normal
14:00	797 ms	Normal
14:30	1.79 s	Much slower, or failing
15:00	1.12 s	Slower than usual
15:30	753 ms	Normal
16:00	1.01 s	Normal
16:30	721 ms	Normal
17:00	724 ms	Normal
17:30	716 ms	Normal
18:00	739 ms	Normal
18:30	1.07 s	Slower than usual
19:00	821 ms	Normal
19:30	805 ms	Normal
20:00	698 ms	Normal
20:30	694 ms	Normal
21:00	823 ms	Normal

Tokyo

Each check (UTC)Usual (183 ms)Much slower, or failingSlow check outside the incidentIncident

Every check as a table

Time (UTC)	Check	Reading
11:30	182 ms	Normal
12:00	283 ms	Normal
12:30	225 ms	Normal
13:00	396 ms	Normal
13:30	371 ms	Normal
14:00	216 ms	Normal
14:30	1.13 s	Much slower, or failing
15:00	338 ms	Normal
15:30	205 ms	Normal
16:00	622 ms	Much slower, or failing
16:30	191 ms	Normal
17:00	236 ms	Normal
17:30	238 ms	Normal
18:00	197 ms	Normal
18:30	810 ms	Much slower, or failing
19:00	264 ms	Normal
19:30	290 ms	Normal
20:00	194 ms	Normal
20:30	182 ms	Normal
21:00	295 ms	Normal

Mumbai

Each check (UTC)Usual (271 ms)Slower than usualMuch slower, or failingSlow check outside the incidentIncident

Every check as a table

Time (UTC)	Check	Reading
11:30	279 ms	Normal
12:00	340 ms	Normal
12:30	308 ms	Normal
13:00	353 ms	Normal
13:30	638 ms	Slower than usual
14:00	481 ms	Normal
14:30	1.35 s	Much slower, or failing
15:00	321 ms	Normal
15:30	274 ms	Normal
16:00	620 ms	Slower than usual
16:30	330 ms	Normal
17:00	314 ms	Normal
17:30	284 ms	Normal
18:00	270 ms	Normal
18:30	991 ms	Much slower, or failing
19:00	305 ms	Normal
19:30	372 ms	Normal
20:00	310 ms	Normal
20:30	281 ms	Normal
21:00	401 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.