Live Git status: last 24 hours →

Benchmark report

GitHub thumbnail

Is github.com slow?

Homepage load times from 6 cities

Slow from some locations

Singapore waited 1215 ms, about 51× Tokyo. The gap suggests some test locations reach a distant server.

Fastest
24 ms
Tokyo
Slowest
1215 ms
Singapore
Successful requests
100%
6 locations

Response time around the world

Amsterdam 64ms typicalSan Francisco 512ms typicalMontreal 116ms typicalSingapore 1215ms typicalTokyo 24ms typicalMumbai 54ms typical
  • JapanTokyo
    24 ms
  • IndiaMumbai
    54 ms
  • NetherlandsAmsterdam
    64 ms
  • CanadaMontreal
    116 ms
  • United StatesSan Francisco
    512 ms
  • SingaporeSingapore
    1215 ms

Why is Singapore slower?

Singapore waited 1.2 seconds for the homepage and San Francisco half a second, against 24 to 116 ms in Tokyo, Mumbai, Amsterdam and Montreal. Both come from our test network. Our Singapore server’s route to GitHub goes through France and back, about 150 ms per round trip, and in the controlled run of 4 October it took 152 ms to connect, 153 ms to set up the secure connection, 157 ms waiting and 749 ms downloading the page, which arrives over several round trips. San Francisco went to GitHub’s Virginia servers because our DNS server is registered in Virginia, about 65 ms per round trip.

Click the location to see each stage.

ConnectTLSServer waitDownload
SingaporeSingapore
1211 ms
Finding the server
2 ms
Reaching the server
152 ms
Setting up security
153 ms
Waiting for the server
157 ms
Receiving the response: most of the time
749 ms
Total
1211 ms

Finding the server is measured once per location, so it sits outside these bars. Open a city to see it.

Bars show the typical request, so the parts add up to its total. Why

Compare all locations

Click a city to see its stage-by-stage breakdown.

ConnectTLSServer waitDownload
NetherlandsAmsterdam
65 ms
Finding the server
1 ms
Reaching the server
9 ms
Setting up security
10 ms
Waiting for the server
10 ms
Receiving the response: most of the time
36 ms
Total
65 ms
United StatesSan Francisco
502 ms
Finding the server
13 ms
Reaching the server
64 ms
Setting up security
65 ms
Waiting for the server
65 ms
Receiving the response: most of the time
308 ms
Total
502 ms
CanadaMontreal
116 ms
Finding the server
2 ms
Reaching the server
14 ms
Setting up security
20 ms
Waiting for the server
16 ms
Receiving the response: most of the time
66 ms
Total
116 ms
SingaporeSingapore
1211 ms
Finding the server
2 ms
Reaching the server
152 ms
Setting up security
153 ms
Waiting for the server
157 ms
Receiving the response: most of the time
749 ms
Total
1211 ms
JapanTokyo
24 ms
Finding the server
1 ms
Reaching the server
3 ms
Setting up security
5 ms
Waiting for the server: most of the time
8 ms
Receiving the response
8 ms
Total
24 ms
IndiaMumbai
53 ms
Finding the server
2 ms
Reaching the server
7 ms
Setting up security
10 ms
Waiting for the server
10 ms
Receiving the response: most of the time
26 ms
Total
53 ms

The phases come from the controlled run of 4 October 2026. Typical and slower times pool the daily requests. 6 of 6 test locations included: Amsterdam, San Francisco, Montreal, Singapore, Tokyo, Mumbai.

Finding the server is measured once per location, so it sits outside these bars. Open a city to see it.

Bars show the typical request, so the parts add up to its total. Why

GitHub still feels slow?

Check GitHub’s status page
Incidents on GitHub’s side show up there first, and they usually affect every city at once. A gap between cities is not an incident.
This is not a git clone or Actions benchmark
The page measures the logged-out homepage document. Clone and push, Actions, Pages, Codespaces and the signed-in app are separate systems.
Served from GitHub’s own front end
The homepage is marked private, so no shared CDN cache answers it. Each city connects to a GitHub server directly, so the route to that server sets the number.

Response time over the last 30 days

Daily median of 5 requests per location, 21 September 2026 to 20 October 2026.
010002000 ms21 Sept20 Oct
Show the numbers
DayAmsterdamSan FranciscoMontrealSingaporeTokyoMumbai
21 September 202665 ms496 ms111 ms1211 ms27 ms51 ms
22 September 202666 ms531 ms115 ms1234 ms25 ms53 ms
23 September 202669 ms521 ms115 ms1212 ms23 ms52 ms
24 September 202664 ms515 ms112 ms1211 ms23 ms46 ms
25 September 202666 ms491 ms121 ms1206 ms23 ms49 ms
26 September 202664 ms493 ms111 ms1213 ms21 ms48 ms
27 September 202664 ms497 ms116 ms1213 ms24 ms55 ms
28 September 202664 ms493 ms120 ms1208 ms22 ms55 ms
29 September 202665 ms507 ms115 ms1210 ms26 ms54 ms
30 September 202665 ms508 ms117 ms1210 ms23 ms53 ms
1 October 202665 ms514 ms120 ms1211 ms22 ms52 ms
2 October 202664 ms529 ms130 ms1209 ms23 ms49 ms
3 October 202667 ms500 ms116 ms1213 ms22 ms52 ms
4 October 202665 ms503 ms126 ms1217 ms24 ms55 ms
5 October 202665 ms510 ms125 ms1211 ms26 ms54 ms
6 October 202666 ms510 ms112 ms1211 ms23 ms53 ms
7 October 202667 ms511 ms112 ms1210 ms34 ms49 ms
9 October 202664 ms504 ms115 ms1213 ms24 ms53 ms
10 October 202665 ms531 ms114 ms1209 ms23 ms57 ms
11 October 202664 ms526 ms118 ms1285 ms24 ms55 ms
12 October 202665 ms544 ms119 ms1209 ms31 ms58 ms
13 October 202664 ms512 ms118 ms1308 ms25 ms57 ms
14 October 202665 ms501 ms113 ms1213 ms23 ms54 ms
15 October 202663 ms526 ms121 ms1213 ms20 ms56 ms
17 October 202664 ms514 ms116 ms1217 ms22 ms53 ms
18 October 202664 ms499 ms112 ms1228 ms25 ms55 ms
19 October 202666 ms504 ms118 ms1235 ms25 ms54 ms
20 October 202664 ms528 ms114 ms1212 ms22 ms53 ms

About this measurement

GET github.com · 60 requests per location over 12 daily runs · 7 October 2026 to 20 October 2026

What we tested · Website document. The github.com logged-out homepage, about 575 KB of HTML from GitHub's own front end, no shared cache in between.

How LatencyRadar measures response time →Also measured: GitHub API →

Technical details

Doesn’t measure: git clone or push, Actions, Pages, the signed-in app or the REST API. A git handshake surface is planned.

This page covers the logged-out github.com homepage. It times the HTML document arriving at our test location, before a browser runs scripts or loads the rest of the page. GitHub’s REST API and the first request of a git clone are separate requests in our catalog, and the GitHub API has its own report. A fast homepage does not mean a clone or an API call is fast. This page does not measure pushes, Actions queues, Codespaces, Copilot, Pages or the signed-in app.

Between 7 and 20 October 2026 the typical time was 24 ms in Tokyo, 54 ms in Mumbai and 64 ms in Amsterdam, 116 ms in Montreal, 512 ms in San Francisco and 1,215 ms in Singapore. Every day looked the same. Amsterdam’s daily medians stayed between 63 and 67 ms, Tokyo’s between 20 and 34 ms, San Francisco’s between 499 and 544 ms and Singapore’s between 1,209 and 1,308 ms, so the slow cities are slow every day rather than in a bad week. Both are about our test network, not GitHub: a Singapore network that reaches Microsoft directly, where GitHub’s Singapore server runs, should get much closer to Tokyo’s time.

Test locationTypical response timeSlower response timeRequests
Amsterdam64 ms68 ms60
San Francisco512 ms542 ms60
Montreal116 ms127 ms60
Singapore1215 ms1308 ms60
Tokyo24 ms40 ms60
Mumbai54 ms61 ms60

Typical: half of the requests finished within this time (technical: p50). Slower: 95% of requests finished within this time (technical: p95). Statistics

Request
GET github.com
Measured from
Amsterdam · San Francisco · Montreal · Singapore · Tokyo · Mumbai
Requests
Daily measurements from 7 October 2026 to 20 October 2026. 6 of 6 test locations included: Amsterdam, San Francisco, Montreal, Singapore, Tokyo, Mumbai. · 7 October 2026 to 20 October 2026
Timings taken
DNS, connect, TLS, waiting for the server, download
Report coverage
6 of 6 test locations included: Amsterdam, San Francisco, Montreal, Singapore, Tokyo, Mumbai.
Daily requests in each location
Amsterdam: 60 · San Francisco: 60 · Montreal: 60 · Singapore: 60 · Tokyo: 60 · Mumbai: 60
Typical response time
Median of the eligible daily requests in each included location.
Slower response time
The 95th percentile of the same eligible daily requests in each included location.

GitHub

https://github.com/

Independent measurement by LatencyRadar. Not affiliated with GitHub. · How we measure (v1.3)

How fast does your site load 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 site

No account required · Takes about 30 seconds.

More benchmarks

All benchmarks →