Benchmark report
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
Tokyo
24 msMumbai
54 msAmsterdam
64 msMontreal
116 msSan Francisco
512 msSingapore
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.
Singapore1211 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 locationsHide the comparison
Click a city to see its stage-by-stage breakdown.
Amsterdam65 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
San Francisco502 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
Montreal116 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
Singapore1211 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
Tokyo24 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
Mumbai53 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
Show the numbers
| Day | Amsterdam | San Francisco | Montreal | Singapore | Tokyo | Mumbai |
|---|---|---|---|---|---|---|
| 21 September 2026 | 65 ms | 496 ms | 111 ms | 1211 ms | 27 ms | 51 ms |
| 22 September 2026 | 66 ms | 531 ms | 115 ms | 1234 ms | 25 ms | 53 ms |
| 23 September 2026 | 69 ms | 521 ms | 115 ms | 1212 ms | 23 ms | 52 ms |
| 24 September 2026 | 64 ms | 515 ms | 112 ms | 1211 ms | 23 ms | 46 ms |
| 25 September 2026 | 66 ms | 491 ms | 121 ms | 1206 ms | 23 ms | 49 ms |
| 26 September 2026 | 64 ms | 493 ms | 111 ms | 1213 ms | 21 ms | 48 ms |
| 27 September 2026 | 64 ms | 497 ms | 116 ms | 1213 ms | 24 ms | 55 ms |
| 28 September 2026 | 64 ms | 493 ms | 120 ms | 1208 ms | 22 ms | 55 ms |
| 29 September 2026 | 65 ms | 507 ms | 115 ms | 1210 ms | 26 ms | 54 ms |
| 30 September 2026 | 65 ms | 508 ms | 117 ms | 1210 ms | 23 ms | 53 ms |
| 1 October 2026 | 65 ms | 514 ms | 120 ms | 1211 ms | 22 ms | 52 ms |
| 2 October 2026 | 64 ms | 529 ms | 130 ms | 1209 ms | 23 ms | 49 ms |
| 3 October 2026 | 67 ms | 500 ms | 116 ms | 1213 ms | 22 ms | 52 ms |
| 4 October 2026 | 65 ms | 503 ms | 126 ms | 1217 ms | 24 ms | 55 ms |
| 5 October 2026 | 65 ms | 510 ms | 125 ms | 1211 ms | 26 ms | 54 ms |
| 6 October 2026 | 66 ms | 510 ms | 112 ms | 1211 ms | 23 ms | 53 ms |
| 7 October 2026 | 67 ms | 511 ms | 112 ms | 1210 ms | 34 ms | 49 ms |
| 9 October 2026 | 64 ms | 504 ms | 115 ms | 1213 ms | 24 ms | 53 ms |
| 10 October 2026 | 65 ms | 531 ms | 114 ms | 1209 ms | 23 ms | 57 ms |
| 11 October 2026 | 64 ms | 526 ms | 118 ms | 1285 ms | 24 ms | 55 ms |
| 12 October 2026 | 65 ms | 544 ms | 119 ms | 1209 ms | 31 ms | 58 ms |
| 13 October 2026 | 64 ms | 512 ms | 118 ms | 1308 ms | 25 ms | 57 ms |
| 14 October 2026 | 65 ms | 501 ms | 113 ms | 1213 ms | 23 ms | 54 ms |
| 15 October 2026 | 63 ms | 526 ms | 121 ms | 1213 ms | 20 ms | 56 ms |
| 17 October 2026 | 64 ms | 514 ms | 116 ms | 1217 ms | 22 ms | 53 ms |
| 18 October 2026 | 64 ms | 499 ms | 112 ms | 1228 ms | 25 ms | 55 ms |
| 19 October 2026 | 66 ms | 504 ms | 118 ms | 1235 ms | 25 ms | 54 ms |
| 20 October 2026 | 64 ms | 528 ms | 114 ms | 1212 ms | 22 ms | 53 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 location | Typical response time | Slower response time | Requests |
|---|---|---|---|
| Amsterdam | 64 ms | 68 ms | 60 |
| San Francisco | 512 ms | 542 ms | 60 |
| Montreal | 116 ms | 127 ms | 60 |
| Singapore | 1215 ms | 1308 ms | 60 |
| Tokyo | 24 ms | 40 ms | 60 |
| Mumbai | 54 ms | 61 ms | 60 |
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.
No account required · Takes about 30 seconds.