Benchmark report

Coinbase Exchange API thumbnail

Is the Coinbase Exchange API slow?

Response times from 6 cities

Mixed by location

Response times ranged from 74 ms in Montreal to 271 ms in Singapore. Where you are matters.

Fastest
74 ms
Montreal
Slowest
271 ms
Singapore
Successful requests
100%
6 locations

Response time around the world

Amsterdam 148ms typicalSan Francisco 105ms typicalMontreal 74ms typicalSingapore 271ms typicalTokyo 193ms typicalMumbai 220ms typical
  • CanadaMontreal
    74 ms
  • United StatesSan Francisco
    105 ms
  • NetherlandsAmsterdam
    148 ms
  • JapanTokyo
    193 ms
  • IndiaMumbai
    220 ms
  • SingaporeSingapore
    271 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 27 September. 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, 84 ms from San Francisco, 123 ms from Amsterdam, 186 ms from Tokyo, 206 ms from Mumbai and 266 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.

ConnectTLSServer waitDownload
SingaporeSingapore
278 ms
Finding the server
12 ms
Reaching the server
4 ms
Setting up security
8 ms
Waiting for the server: most of the time
266 ms
Receiving the response
0 ms
Total
278 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
148 ms
Finding the server
21 ms
Reaching the server
8 ms
Setting up security
16 ms
Waiting for the server: most of the time
123 ms
Receiving the response
1 ms
Total
148 ms
United StatesSan Francisco
95 ms
Finding the server
15 ms
Reaching the server
3 ms
Setting up security
7 ms
Waiting for the server: most of the time
84 ms
Receiving the response
1 ms
Total
95 ms
CanadaMontreal
73 ms
Finding the server
5 ms
Reaching the server
2 ms
Setting up security
5 ms
Waiting for the server: most of the time
66 ms
Receiving the response
0 ms
Total
73 ms
SingaporeSingapore
278 ms
Finding the server
12 ms
Reaching the server
4 ms
Setting up security
8 ms
Waiting for the server: most of the time
266 ms
Receiving the response
0 ms
Total
278 ms
JapanTokyo
196 ms
Finding the server
5 ms
Reaching the server
2 ms
Setting up security
8 ms
Waiting for the server: most of the time
186 ms
Receiving the response
0 ms
Total
196 ms
IndiaMumbai
215 ms
Finding the server
2 ms
Reaching the server
3 ms
Setting up security
6 ms
Waiting for the server: most of the time
206 ms
Receiving the response
0 ms
Total
215 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

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 209 to 237 ms a day, but its slowest 5% took about 800 ms, the widest tail of the six cities. Montreal had one slow day, 213 ms on 23 September against 47 to 82 ms on the others.

Response time over the last 30 days

Daily median of 5 requests per location, 29 August 2026 to 27 September 2026.
0250500 ms29 Aug27 SeptMumbai joinedMontreal, 23 September 2026: 213 ms, well above its usual level.

A dot marks a day well above that location’s usual level.

Show the numbers
DayAmsterdamSan FranciscoMontrealSingaporeTokyoMumbai
29 August 2026157 ms103 ms77 ms262 ms186 ms—
30 August 2026148 ms102 ms80 ms269 ms181 ms—
31 August 2026148 ms121 ms83 ms267 ms188 ms—
1 September 2026160 ms99 ms113 ms290 ms195 ms—
2 September 2026157 ms103 ms72 ms287 ms192 ms—
3 September 2026149 ms104 ms70 ms283 ms199 ms—
4 September 2026153 ms107 ms72 ms279 ms203 ms—
5 September 2026150 ms101 ms110 ms287 ms191 ms—
6 September 2026150 ms98 ms114 ms273 ms193 ms—
7 September 2026148 ms98 ms112 ms283 ms196 ms213 ms
8 September 2026148 ms101 ms74 ms269 ms196 ms223 ms
9 September 2026146 ms106 ms116 ms274 ms195 ms223 ms
10 September 2026149 ms112 ms72 ms305 ms200 ms245 ms
11 September 2026143 ms112 ms79 ms285 ms190 ms232 ms
12 September 2026150 ms98 ms42 ms281 ms189 ms230 ms
13 September 2026149 ms102 ms36 ms275 ms196 ms224 ms
14 September 2026153 ms111 ms47 ms262 ms188 ms224 ms
15 September 2026143 ms106 ms80 ms264 ms197 ms211 ms
16 September 2026151 ms114 ms81 ms278 ms187 ms209 ms
17 September 2026148 ms107 ms76 ms270 ms191 ms226 ms
18 September 2026147 ms106 ms73 ms264 ms200 ms216 ms
19 September 2026151 ms128 ms82 ms268 ms192 ms220 ms
20 September 2026143 ms102 ms72 ms273 ms188 ms221 ms
21 September 2026147 ms103 ms73 ms286 ms194 ms222 ms
22 September 2026152 ms100 ms69 ms275 ms204 ms220 ms
23 September 2026145 ms106 ms213 ms ▲286 ms184 ms215 ms
24 September 2026148 ms97 ms73 ms268 ms190 ms237 ms
25 September 2026148 ms100 ms71 ms273 ms197 ms215 ms
26 September 2026145 ms100 ms75 ms263 ms191 ms226 ms
27 September 2026147 ms103 ms73 ms277 ms205 ms216 ms

About this measurement

GET api.exchange.coinbase.com/time · 70 requests per location over 14 daily runs · 14 September 2026 to 27 September 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.

Not measured: order placement, market data, the WebSocket feed, authenticated endpoints, or the Coinbase consumer app.

Between 14 and 27 September 2026 the typical time was 74 ms in Montreal, 105 ms in San Francisco, 148 ms in Amsterdam, 193 ms in Tokyo, 220 ms in Mumbai and 271 ms in Singapore. Montreal was the fastest city on 13 of the 14 days and Singapore the slowest on all 14. Apart from Mumbai's tail, the slower times sit close to the typical ones: at most 290 ms, in Singapore.

Test locationTypical response timeSlower response timeRequests
Amsterdam148 ms156 ms20
San Francisco105 ms128 ms20
Montreal74 ms209 ms20
Singapore271 ms290 ms20
Tokyo193 ms208 ms20
Mumbai220 ms806 ms20

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 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.

Coinbase Exchange API

https://api.exchange.coinbase.com/time

Independent measurement by LatencyRadar. Not affiliated with Coinbase Exchange API. · 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.

Test my API

No account required · Takes about 30 seconds.

More benchmarks

All benchmarks →