GitHub Git handshake disruption on 1 October 2026

GitHub Git handshake from Amsterdam, Mumbai, Singapore, Tokyo: degraded checks; 2026-10-01 15:00 UTC to 2026-10-01 19:00 UTC: peak Git handshake 1.06 s vs a usual 0.7 s.

What our checks saw: Degraded
Cities affected: Amsterdam, Mumbai, Singapore, Tokyo
When: 1 Oct, 15:00 UTC to 1 Oct, 19:00 UTC
How long: 4 hours
Slowest check: 1.06 s, usually 700 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
12:00	380 ms	Normal
12:30	604 ms	Much slower, or failing
13:00	268 ms	Normal
13:30	8.13 s	Some requests failed
14:00	363 ms	Normal
14:30	206 ms	Normal
15:00	712 ms	Much slower, or failing
15:30	182 ms	Normal
16:00	201 ms	Normal
16:30	349 ms	Normal
17:00	215 ms	Normal
17:30	277 ms	Normal
18:00	349 ms	Normal
18:30	187 ms	Normal
19:00	234 ms	Normal
19:30	522 ms	Much slower, or failing
20:00	625 ms	Much slower, or failing
20:30	195 ms	Normal
21:00	1.32 s	Much slower, or failing
21:30	211 ms	Normal
22:00	226 ms	Normal

Singapore

Each check (UTC)Usual (700 ms)Slower than usualSome requests failedSlow check outside the incidentIncident

Every check as a table

Time (UTC)	Check	Reading
12:00	756 ms	Normal
12:30	1.15 s	Slower than usual
13:00	748 ms	Normal
13:30	7.40 s	Some requests failed
14:00	712 ms	Normal
14:30	691 ms	Normal
15:00	1.42 s	Slower than usual
15:30	701 ms	Normal
16:00	713 ms	Normal
16:30	757 ms	Normal
17:00	732 ms	Some requests failed
17:30	787 ms	Normal
18:00	739 ms	Normal
18:30	693 ms	Normal
19:00	692 ms	Normal
19:30	1.18 s	Slower than usual
20:00	1.02 s	Normal
20:30	710 ms	Normal
21:00	1.78 s	Much slower, or failing
21:30	699 ms	Normal
22:00	728 ms	Normal

Tokyo

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

Every check as a table

Time (UTC)	Check	Reading
12:00	201 ms	Normal
12:30	474 ms	Much slower, or failing
13:00	203 ms	Normal
13:30	174 ms	Normal
14:00	290 ms	Normal
14:30	217 ms	Normal
15:00	1.19 s	Much slower, or failing
15:30	186 ms	Normal
16:00	187 ms	Normal
16:30	409 ms	Normal
17:00	190 ms	Normal
17:30	266 ms	Normal
18:00	212 ms	Normal
18:30	174 ms	Normal
19:00	248 ms	Normal
19:30	575 ms	Much slower, or failing
20:00	443 ms	Slower than usual
20:30	238 ms	Normal
21:00	861 ms	Much slower, or failing
21:30	232 ms	Normal
22:00	176 ms	Normal

Mumbai

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

Every check as a table

Time (UTC)	Check	Reading
12:00	426 ms	Normal
12:30	830 ms	Much slower, or failing
13:00	313 ms	Normal
13:30	285 ms	Normal
14:00	409 ms	Normal
14:30	281 ms	Normal
15:00	1.18 s	Much slower, or failing
15:30	296 ms	Normal
16:00	853 ms	Much slower, or failing
16:30	511 ms	Normal
17:00	287 ms	Normal
17:30	378 ms	Normal
18:00	296 ms	Normal
18:30	258 ms	Normal
19:00	311 ms	Normal
19:30	800 ms	Much slower, or failing
20:00	796 ms	Much slower, or failing
20:30	410 ms	Normal
21:00	1.54 s	Much slower, or failing
21:30	276 ms	Normal
22:00	272 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.