Benchmark report
Is Maven Central slow?
Repository response times from 6 cities
Fast globally
Maven Central responds quickly from all 6 test locations. Montreal was fastest at 26 ms; Amsterdam took 45 ms.
- Fastest
- 26 ms
- Montreal
- Slowest
- 45 ms
- Amsterdam
- Successful requests
- 100%
- 6 locations
Response time around the world
Montreal26 ms
Tokyo30 ms
San Francisco32 ms
Mumbai34 ms
Singapore41 ms
Amsterdam45 ms
Why is Amsterdam slower?
Maven Central's repository is served through Cloudflare, and every city reached a Cloudflare site in its own region except Amsterdam, whose requests were answered in London. In the controlled run of 27 September Amsterdam took 9 ms to connect and 12 ms for the secure handshake, against 2 to 5 ms and 6 to 9 ms from the other cities. Amsterdam was the slowest city on 11 of the 14 days. unpkg, also behind Cloudflare, shows the same route from Amsterdam.
Click the location to see each stage.
Amsterdam44 ms
Amsterdam- Finding the server
- 1 ms
- Reaching the server
- 9 ms
- Setting up security
- 12 ms
- Waiting for the server: most of the time
- 23 ms
- Receiving the response
- 0 ms
- Total
- 44 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.
Amsterdam44 ms
Amsterdam- Finding the server
- 1 ms
- Reaching the server
- 9 ms
- Setting up security
- 12 ms
- Waiting for the server: most of the time
- 23 ms
- Receiving the response
- 0 ms
- Total
- 44 ms
San Francisco28 ms
San Francisco- Finding the server
- 29 ms
- Reaching the server
- 3 ms
- Setting up security
- 9 ms
- Waiting for the server: most of the time
- 16 ms
- Receiving the response
- 0 ms
- Total
- 28 ms
Montreal22 ms
Montreal- Finding the server
- 55 ms
- Reaching the server
- 2 ms
- Setting up security
- 7 ms
- Waiting for the server: most of the time
- 12 ms
- Receiving the response
- 1 ms
- Total
- 22 ms
Singapore43 ms
Singapore- Finding the server
- 94 ms
- Reaching the server
- 5 ms
- Setting up security
- 6 ms
- Waiting for the server: most of the time
- 32 ms
- Receiving the response
- 0 ms
- Total
- 43 ms
Tokyo32 ms
Tokyo- Finding the server
- 37 ms
- Reaching the server
- 3 ms
- Setting up security
- 7 ms
- Waiting for the server: most of the time
- 22 ms
- Receiving the response
- 0 ms
- Total
- 32 ms
Mumbai27 ms
Mumbai- Finding the server
- 2 ms
- Reaching the server
- 2 ms
- Setting up security
- 8 ms
- Waiting for the server: most of the time
- 17 ms
- Receiving the response
- 0 ms
- Total
- 27 ms
The phases come from the controlled run of 27 September 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
Maven Central still feels slow?
- Check Maven Central’s status page
- Repository incidents are posted there. A slow build during one is not your network.
- This is not a Maven build benchmark
- We fetch one pom file, slf4j-api 2.0.13 (2.8 KB of XML). Jar downloads, resolving a whole dependency tree, the search API and private repositories are not measured. A build fetches many files like this one, so small per-file times add up.
- Served from a Cloudflare cache
- The file comes from Cloudflare's cache, so the site nearest you usually answers. Every city's daily median stayed under 60 ms across the 14 days.
Response time over the last 18 days
Show the numbers
| Day | Amsterdam | San Francisco | Montreal | Singapore | Tokyo | Mumbai |
|---|---|---|---|---|---|---|
| 9 September 2026 | 47 ms | 35 ms | 29 ms | 46 ms | 31 ms | 35 ms |
| 10 September 2026 | 47 ms | 43 ms | 28 ms | 56 ms | 31 ms | 58 ms |
| 11 September 2026 | 46 ms | 36 ms | 27 ms | 36 ms | 31 ms | 39 ms |
| 12 September 2026 | 47 ms | 29 ms | 35 ms | 50 ms | 31 ms | 32 ms |
| 13 September 2026 | 48 ms | 26 ms | 29 ms | 40 ms | 31 ms | 26 ms |
| 14 September 2026 | 48 ms | 29 ms | 25 ms | 44 ms | 28 ms | 25 ms |
| 15 September 2026 | 48 ms | 33 ms | 24 ms | 41 ms | 33 ms | 56 ms |
| 16 September 2026 | 45 ms | 41 ms | 36 ms | 49 ms | 29 ms | 34 ms |
| 17 September 2026 | 43 ms | 33 ms | 32 ms | 33 ms | 26 ms | 31 ms |
| 18 September 2026 | 42 ms | 35 ms | 19 ms | 50 ms | 32 ms | 38 ms |
| 19 September 2026 | 48 ms | 31 ms | 25 ms | 36 ms | 33 ms | 27 ms |
| 20 September 2026 | 42 ms | 30 ms | 30 ms | 35 ms | 33 ms | 27 ms |
| 21 September 2026 | 42 ms | 39 ms | 31 ms | 41 ms | 29 ms | 25 ms |
| 22 September 2026 | 45 ms | 33 ms | 26 ms | 37 ms | 33 ms | 34 ms |
| 23 September 2026 | 53 ms | 39 ms | 32 ms | 42 ms | 27 ms | 36 ms |
| 24 September 2026 | 44 ms | 31 ms | 22 ms | 36 ms | 29 ms | 33 ms |
| 25 September 2026 | 58 ms | 28 ms | 23 ms | 48 ms | 29 ms | 54 ms |
| 26 September 2026 | 55 ms | 28 ms | 22 ms | 47 ms | 38 ms | 38 ms |
| 27 September 2026 | 48 ms | 28 ms | 26 ms | 47 ms | 30 ms | 36 ms |
About this measurement
GET repo1.maven.org/maven2/org/slf4j/slf4j-api/2.0.13/slf4j-api-2.0.13.pom · 70 requests per location over 14 daily runs · 14 September 2026 to 27 September 2026
What we tested · Package registry. The slf4j-api 2.0.13 pom from repo1.maven.org: 2.8 KB of XML from a Cloudflare cache. One metadata fetch of a Maven or Gradle build.
How LatencyRadar measures response time →
Technical details
Doesn’t measure: Jar downloads, resolving a whole dependency tree, the Maven Central search API, or a private repository.
One Maven Central surface: the pom for slf4j-api 2.0.13 from repo1.maven.org, 2.8 KB of XML from a Cloudflare cache. Maven and Gradle read a pom like this for every dependency they resolve, so it stands for one metadata fetch of a Java build.
Not measured: jar downloads, resolving a whole dependency tree, the Maven Central search API, or a private repository manager in front of it.
Between 14 and 27 September 2026 the typical time was 26 ms in Montreal, 30 ms in Tokyo, 32 ms in San Francisco, 34 ms in Mumbai, 41 ms in Singapore and 45 ms in Amsterdam. Day to day it barely moved: every city's daily median stayed between 19 and 58 ms. Compare npm, PyPI and crates.io, the other package registries we measure.
| Test location | Typical response time | Slower response time | Requests |
|---|---|---|---|
| Amsterdam | 45 ms | 58 ms | 20 |
| San Francisco | 32 ms | 55 ms | 20 |
| Montreal | 26 ms | 45 ms | 20 |
| Singapore | 41 ms | 69 ms | 20 |
| Tokyo | 30 ms | 48 ms | 20 |
| Mumbai | 34 ms | 58 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 repo1.maven.org/maven2/org/slf4j/slf4j-api/2.0.13/slf4j-api-2.0.13.pom
- Measured from
- Amsterdam · San Francisco · Montreal · Singapore · Tokyo · Mumbai
- Requests
- Daily measurements from 14 September 2026 to 27 September 2026. 6 of 6 test locations included: Amsterdam, San Francisco, Montreal, Singapore, Tokyo, Mumbai. · 14 September 2026 to 27 September 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: 70 · San Francisco: 70 · Montreal: 70 · Singapore: 70 · Tokyo: 70 · Mumbai: 70
- 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.
Maven Central
https://repo1.maven.org/maven2/org/slf4j/slf4j-api/2.0.13/slf4j-api-2.0.13.pom
Independent measurement by LatencyRadar. Not affiliated with Maven Central. · How we measure (v1.2)
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.
No account required · Takes about 30 seconds.
