Benchmark report
Is the Coinbase Exchange API slow?
Response times from 6 cities
Mixed by location
Response times ranged from 73 ms in Montreal to 271 ms in Singapore. Where you are matters.
- Fastest
- 73 ms
- Montreal
- Slowest
- 271 ms
- Singapore
- Successful requests
- 100%
- 6 locations
Response time around the world
Montreal73 ms
San Francisco100 ms
Amsterdam147 ms
Tokyo191 ms
Mumbai225 ms
Singapore271 ms
Why is Singapore nearly four times slower than Montreal?
Every city reached a nearby Cloudflare site, and connecting plus the secure handshake took under 25 ms everywhere in the controlled run of 4 October. The rest is waiting: the response is marked not to be stored, so each request travels on to Coinbase and back. That wait was 66 ms from Montreal, 82 ms from San Francisco, 127 ms from Amsterdam, 179 ms from Tokyo, 219 ms from Mumbai and 253 ms from Singapore. It grows with distance from Montreal, which suggests the API is answered from eastern North America.
Click the location to see each stage.
Singapore267 ms
Singapore- Finding the server
- 12 ms
- Reaching the server
- 4 ms
- Setting up security
- 9 ms
- Waiting for the server: most of the time
- 253 ms
- Receiving the response
- 1 ms
- Total
- 267 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.
Amsterdam149 ms
Amsterdam- Finding the server
- 20 ms
- Reaching the server
- 8 ms
- Setting up security
- 13 ms
- Waiting for the server: most of the time
- 127 ms
- Receiving the response
- 1 ms
- Total
- 149 ms
San Francisco93 ms
San Francisco- Finding the server
- 13 ms
- Reaching the server
- 5 ms
- Setting up security
- 5 ms
- Waiting for the server: most of the time
- 82 ms
- Receiving the response
- 1 ms
- Total
- 93 ms
Montreal74 ms
Montreal- Finding the server
- 5 ms
- Reaching the server
- 3 ms
- Setting up security
- 4 ms
- Waiting for the server: most of the time
- 66 ms
- Receiving the response
- 1 ms
- Total
- 74 ms
Singapore267 ms
Singapore- Finding the server
- 12 ms
- Reaching the server
- 4 ms
- Setting up security
- 9 ms
- Waiting for the server: most of the time
- 253 ms
- Receiving the response
- 1 ms
- Total
- 267 ms
Tokyo186 ms
Tokyo- Finding the server
- 6 ms
- Reaching the server
- 2 ms
- Setting up security
- 5 ms
- Waiting for the server: most of the time
- 179 ms
- Receiving the response
- 0 ms
- Total
- 186 ms
Mumbai230 ms
Mumbai- Finding the server
- 2 ms
- Reaching the server
- 3 ms
- Setting up security
- 8 ms
- Waiting for the server: most of the time
- 219 ms
- Receiving the response
- 0 ms
- Total
- 230 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
Coinbase Exchange still feels slow?
- Check Coinbase’s status page
- Exchange and API incidents are posted there. A slow response during one is not your network.
- This is not a trading benchmark
- We call the public server-time endpoint, 57 bytes of JSON with no key. Placing orders, market data, the WebSocket feed and the Coinbase app take other paths and are not measured.
- Mumbai's slow requests
- Mumbai's typical time was a steady 206 to 237 ms a day, but its slowest 5% took about 800 ms, the widest tail of the six cities. Montreal was the steadiest city, at 70 to 76 ms on every run.
Response time over the last 29 days
A dot marks a day well above that location’s usual level.
Show the numbers
| Day | Amsterdam | San Francisco | Montreal | Singapore | Tokyo | Mumbai |
|---|---|---|---|---|---|---|
| 11 September 2026 | 143 ms | 112 ms | 79 ms | 285 ms | 190 ms | 232 ms |
| 12 September 2026 | 150 ms | 98 ms | 42 ms | 281 ms | 189 ms | 230 ms |
| 13 September 2026 | 149 ms | 102 ms | 36 ms | 275 ms | 196 ms | 224 ms |
| 14 September 2026 | 153 ms | 111 ms | 47 ms | 262 ms | 188 ms | 224 ms |
| 15 September 2026 | 143 ms | 106 ms | 80 ms | 264 ms | 197 ms | 211 ms |
| 16 September 2026 | 151 ms | 114 ms | 81 ms | 278 ms | 187 ms | 209 ms |
| 17 September 2026 | 148 ms | 107 ms | 76 ms | 270 ms | 191 ms | 226 ms |
| 18 September 2026 | 147 ms | 106 ms | 73 ms | 264 ms | 200 ms | 216 ms |
| 19 September 2026 | 151 ms | 128 ms | 82 ms | 268 ms | 192 ms | 220 ms |
| 20 September 2026 | 143 ms | 102 ms | 72 ms | 273 ms | 188 ms | 221 ms |
| 21 September 2026 | 147 ms | 103 ms | 73 ms | 286 ms | 194 ms | 222 ms |
| 22 September 2026 | 152 ms | 100 ms | 69 ms | 275 ms | 204 ms | 220 ms |
| 23 September 2026 | 145 ms | 106 ms | 213 ms ▲ | 286 ms | 184 ms | 215 ms |
| 24 September 2026 | 148 ms | 97 ms | 73 ms | 268 ms | 190 ms | 237 ms |
| 25 September 2026 | 148 ms | 100 ms | 71 ms | 273 ms | 197 ms | 215 ms |
| 26 September 2026 | 145 ms | 100 ms | 75 ms | 263 ms | 191 ms | 226 ms |
| 27 September 2026 | 147 ms | 103 ms | 73 ms | 277 ms | 205 ms | 216 ms |
| 28 September 2026 | 145 ms | 99 ms | 70 ms | 270 ms | 179 ms | 228 ms |
| 29 September 2026 | 150 ms | 95 ms | 70 ms | 268 ms | 197 ms | 209 ms |
| 30 September 2026 | 146 ms | 102 ms | 71 ms | 281 ms | 188 ms | 206 ms |
| 1 October 2026 | 148 ms | 100 ms | 72 ms | 271 ms | 193 ms | 222 ms |
| 2 October 2026 | 144 ms | 100 ms | 74 ms | 270 ms | 176 ms | 236 ms |
| 3 October 2026 | 152 ms | 98 ms | 72 ms | 274 ms | 192 ms | 225 ms |
| 4 October 2026 | 143 ms | 97 ms | 75 ms | 273 ms | 188 ms | 224 ms |
| 5 October 2026 | 155 ms | 99 ms | 76 ms | 257 ms | 191 ms | 222 ms |
| 6 October 2026 | 148 ms | 102 ms | 73 ms | 269 ms | 182 ms | 228 ms |
| 7 October 2026 | 148 ms | 100 ms | 71 ms | 268 ms | 192 ms | 230 ms |
| 9 October 2026 | 146 ms | 103 ms | 72 ms | 280 ms | 188 ms | 237 ms |
| 10 October 2026 | 143 ms | 101 ms | 73 ms | 277 ms | 185 ms | 222 ms |
About this measurement
GET api.exchange.coinbase.com/time · 65 requests per location over 13 daily runs · 27 September 2026 to 10 October 2026
What we tested · API response. GET api.exchange.coinbase.com/time: a 57-byte JSON server time, marked no-store, behind Cloudflare, no key.
How LatencyRadar measures response time →
Technical details
Doesn’t measure: Order placement, market data, the WebSocket feed, or the Coinbase consumer app.
One Coinbase Exchange surface: GET api.exchange.coinbase.com/time, a 57-byte JSON server time behind Cloudflare, marked no-store and called without a key. Trading clients call it to line up their clock with the exchange before signing requests, and because nothing caches it, it shows the round trip from each city to where the API runs.
Between 27 September and 10 October 2026 the typical time was 73 ms in Montreal, 100 ms in San Francisco, 147 ms in Amsterdam, 191 ms in Tokyo, 225 ms in Mumbai and 271 ms in Singapore. Montreal was the fastest city and Singapore the slowest on all 13 days. Apart from Mumbai's tail, the slower times sit close to the typical ones: at most 294 ms, in Singapore.
| Test location | Typical response time | Slower response time | Requests |
|---|---|---|---|
| Amsterdam | 147 ms | 156 ms | 65 |
| San Francisco | 100 ms | 109 ms | 65 |
| Montreal | 73 ms | 79 ms | 65 |
| Singapore | 271 ms | 294 ms | 65 |
| Tokyo | 191 ms | 207 ms | 65 |
| Mumbai | 225 ms | 809 ms | 65 |
Typical: half of the requests finished within this time (technical: p50). Slower: 95% of requests finished within this time (technical: p95). Statistics
- Request
- GET api.exchange.coinbase.com/time
- Measured from
- Amsterdam · San Francisco · Montreal · Singapore · Tokyo · Mumbai
- Requests
- Daily measurements from 27 September 2026 to 10 October 2026. 6 of 6 test locations included: Amsterdam, San Francisco, Montreal, Singapore, Tokyo, Mumbai. · 27 September 2026 to 10 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: 65 · San Francisco: 65 · Montreal: 65 · Singapore: 65 · Tokyo: 65 · Mumbai: 65
- 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.
Coinbase Exchange API
https://api.exchange.coinbase.com/time
Independent measurement by LatencyRadar. Not affiliated with Coinbase Exchange API. · How we measure (v1.3)
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.
