Benchmark report
Is github.com slow?
Homepage load times from 5 cities
Slow from some locations
Singapore waited 1220 ms, about 38× Tokyo. The gap suggests some test locations reach a distant server.
- Fastest
- 32 ms
- Tokyo
- Slowest
- 1220 ms
- Singapore
- Successful requests
- 100%
- 5 locations
Response time around the world
Tokyo32 ms
Amsterdam69 ms
Montreal116 ms
San Francisco500 ms
Singapore1220 ms
Why is Singapore slower?
Singapore waited 1.2 seconds for the homepage, and San Francisco half a second, against 32 to 116 ms in Tokyo, Amsterdam and Montreal. In the slow cities every phase grows together, and the download most of all: 753 ms in Singapore against 10 ms in Tokyo. The page travels a long way to reach them. GitHub's servers answer quickly when a city is near one, and every request from the slow cities was this slow, not just a bad few.
Click the location to see each stage.
Singapore1220 ms
Singapore- Finding the server
- 4 ms
- Reaching the server
- 153 ms
- Setting up security
- 155 ms
- Waiting for the server
- 159 ms
- Receiving the response: most of the time
- 753 ms
- Total
- 1220 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 locationsHide the comparison
Click a city to see its stage-by-stage breakdown.
Amsterdam69 ms
Amsterdam- Finding the server
- 1 ms
- Reaching the server
- 8 ms
- Setting up security
- 13 ms
- Waiting for the server
- 10 ms
- Receiving the response: most of the time
- 38 ms
- Total
- 69 ms
San Francisco500 ms
San Francisco- Finding the server
- 12 ms
- Reaching the server
- 63 ms
- Setting up security
- 65 ms
- Waiting for the server
- 64 ms
- Receiving the response: most of the time
- 308 ms
- Total
- 500 ms
Montreal116 ms
Montreal- Finding the server
- 1 ms
- Reaching the server
- 14 ms
- Setting up security
- 19 ms
- Waiting for the server
- 15 ms
- Receiving the response: most of the time
- 68 ms
- Total
- 116 ms
Singapore1220 ms
Singapore- Finding the server
- 4 ms
- Reaching the server
- 153 ms
- Setting up security
- 155 ms
- Waiting for the server
- 159 ms
- Receiving the response: most of the time
- 753 ms
- Total
- 1220 ms
Tokyo32 ms
Tokyo- Finding the server
- 3 ms
- Reaching the server
- 4 ms
- Setting up security
- 7 ms
- Waiting for the server: most of the time
- 11 ms
- Receiving the response
- 10 ms
- Total
- 32 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
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 of our cities reached a different address, and how far away that address is sets the number.
Response time over the last 16 days
Show the numbers
| Day | Amsterdam | San Francisco | Montreal | Singapore | Tokyo | Mumbai |
|---|---|---|---|---|---|---|
| 27 August 2026 | 73 ms | 524 ms | 120 ms | 1283 ms | 27 ms | — |
| 28 August 2026 | 67 ms | 521 ms | 114 ms | 1219 ms | 26 ms | — |
| 29 August 2026 | 71 ms | 512 ms | 115 ms | 1288 ms | 24 ms | — |
| 30 August 2026 | 65 ms | 496 ms | 112 ms | 1314 ms | 23 ms | — |
| 31 August 2026 | 69 ms | 508 ms | 113 ms | 1222 ms | 31 ms | — |
| 1 September 2026 | 67 ms | 497 ms | 112 ms | 1216 ms | 22 ms | — |
| 2 September 2026 | 67 ms | 497 ms | 132 ms | 1213 ms | 28 ms | — |
| 3 September 2026 | 66 ms | 498 ms | 114 ms | 1213 ms | 24 ms | — |
| 4 September 2026 | 67 ms | 497 ms | 121 ms | 1219 ms | 23 ms | — |
| 5 September 2026 | 71 ms | 503 ms | 117 ms | 1221 ms | 32 ms | — |
| 6 September 2026 | 65 ms | 501 ms | 113 ms | 1218 ms | 43 ms | — |
| 7 September 2026 | 66 ms | 497 ms | 113 ms | 1214 ms | 29 ms | 46 ms |
| 8 September 2026 | 67 ms | 497 ms | 113 ms | 1212 ms | 24 ms | 46 ms |
| 9 September 2026 | 70 ms | 501 ms | 114 ms | 1219 ms | 32 ms | 49 ms |
| 10 September 2026 | 67 ms | 496 ms | 112 ms | 1225 ms | 24 ms | 48 ms |
| 11 September 2026 | 65 ms | 519 ms | 112 ms | 1216 ms | 25 ms | 47 ms |
| 12 September 2026 | 65 ms | 495 ms | 111 ms | 1317 ms | 25 ms | 55 ms |
About this measurement
GET github.com · 20 requests per location · 20 August 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.
The main result measures 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 endpoints. Their results belong in separate sections, because a fast homepage cannot establish that a clone or an API call is fast.
The additional requests in the catalog are /rate_limit on the REST API and a git protocol v2 handshake. The handshake receives a short list of capabilities; it does not download the repository. Pushes need credentials, and this page does not measure Actions queues, Codespaces, Copilot, Pages or the signed-in app.
In the displayed homepage run, Tokyo took 32 ms typical and Singapore about 1.2 seconds. The page download contributes much of Singapore’s wait. That finding applies to this document and these test locations; it does not identify the cause of a slow build or clone.
| Test location | Typical response time | Slower response time | Requests |
|---|---|---|---|
| Amsterdam | 69 ms | 78 ms | 20 |
| San Francisco | 500 ms | 516 ms | 20 |
| Montreal | 116 ms | 121 ms | 20 |
| Singapore | 1220 ms | 1234 ms | 20 |
| Tokyo | 32 ms | 49 ms | 20 |
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
- Requests
- 100 requests · 20 from each of 5 cities · 20 August 2026
- Timings taken
- DNS, connect, TLS, waiting for the server, download
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.
No account required · Takes about 30 seconds.
