Benchmark report
Is the Stripe API slow?
Response times from 5 cities
Fast globally
Stripe API responds quickly from all 5 test locations. Singapore was fastest at 18 ms; San Francisco took 74 ms.
- Fastest
- 18 ms
- Singapore
- Slowest
- 74 ms
- San Francisco
- Successful requests
- 100%
- 5 locations
Response time around the world
Singapore18 ms
Tokyo20 ms
Amsterdam55 ms
Montreal55 ms
San Francisco74 ms
This measures the front door, not a payment
Most of each request went to connecting and setting up the secure connection. Stripe answered the root request with HTTP 404 without doing any payment work, so its short server wait says nothing about how long a charge or PaymentIntent takes. Read the numbers as the path to Stripe’s API front end from each city: 18 ms from Singapore, 74 ms from San Francisco.
Compare all locationsHide the comparison
Click a city to see its stage-by-stage breakdown.
Amsterdam55 ms
Amsterdam- Finding the server
- 1 ms
- Reaching the server
- 18 ms
- Setting up security: most of the time
- 20 ms
- Waiting for the server
- 16 ms
- Receiving the response
- 1 ms
- Total
- 55 ms
San Francisco74 ms
San Francisco- Finding the server
- 14 ms
- Reaching the server
- 24 ms
- Setting up security: most of the time
- 27 ms
- Waiting for the server
- 22 ms
- Receiving the response
- 1 ms
- Total
- 74 ms
Montreal55 ms
Montreal- Finding the server
- 3 ms
- Reaching the server
- 17 ms
- Setting up security: most of the time
- 22 ms
- Waiting for the server
- 16 ms
- Receiving the response
- 0 ms
- Total
- 55 ms
Singapore18 ms
Singapore- Finding the server
- 7 ms
- Reaching the server
- 5 ms
- Setting up security: most of the time
- 10 ms
- Waiting for the server
- 3 ms
- Receiving the response
- 0 ms
- Total
- 18 ms
Tokyo20 ms
Tokyo- Finding the server
- 35 ms
- Reaching the server: most of the time
- 7 ms
- Setting up security
- 7 ms
- Waiting for the server
- 6 ms
- Receiving the response
- 0 ms
- Total
- 20 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
Stripe still feels slow?
- Check Stripe’s status page
- A slow or failing checkout during an incident is Stripe’s to fix, and the status page says so before any benchmark does.
- This is not a payment benchmark
- Authenticated API calls, Checkout, webhooks and the Dashboard each do work this root request does not. To investigate a slow checkout, time the payment request your application actually makes.
- Where your delay sits
- Check whether your wait is in connecting or after the request reaches Stripe. Our five cities reached four different addresses; those addresses alone do not say where Stripe processes payments.
Response time over the last 16 days
A dot marks a day well above that location’s usual level.
Show the numbers
| Day | Amsterdam | San Francisco | Montreal | Singapore | Tokyo | Mumbai |
|---|---|---|---|---|---|---|
| 28 August 2026 | 58 ms | 77 ms | 55 ms | 19 ms | 20 ms | — |
| 29 August 2026 | 85 ms | 77 ms | 55 ms | 17 ms | 18 ms | — |
| 30 August 2026 | 72 ms | 74 ms | 54 ms | 17 ms | 14 ms | — |
| 31 August 2026 | 54 ms | 78 ms | 54 ms | 15 ms | 14 ms | — |
| 1 September 2026 | 59 ms | 74 ms | 53 ms | 16 ms | 14 ms | — |
| 2 September 2026 | 62 ms | 73 ms | 53 ms | 16 ms | 19 ms | — |
| 3 September 2026 | 85 ms | 73 ms | 52 ms | 15 ms | 388 ms ▲ | — |
| 4 September 2026 | 55 ms | 73 ms | 53 ms | 17 ms | 15 ms | — |
| 5 September 2026 | 91 ms | 73 ms | 54 ms | 18 ms | 15 ms | — |
| 6 September 2026 | 56 ms | 75 ms | 54 ms | 16 ms | 21 ms | — |
| 7 September 2026 | 56 ms | 72 ms | 53 ms | 18 ms | 13 ms | 195 ms |
| 8 September 2026 | 85 ms | 73 ms | 54 ms | 15 ms | 18 ms | 197 ms |
| 9 September 2026 | 55 ms | 75 ms | 55 ms | 24 ms | 18 ms | 196 ms |
| 10 September 2026 | 53 ms | 73 ms | 52 ms | 17 ms | 15 ms | 194 ms |
| 11 September 2026 | 51 ms | 72 ms | 53 ms | 15 ms | 12 ms | 195 ms |
| 12 September 2026 | 53 ms | 77 ms | 53 ms | 15 ms | 17 ms | 190 ms |
About this measurement
GET api.stripe.com · 20 requests per location · 20 August 2026
What we tested · API response. A request to api.stripe.com/ returning HTTP 404. These times show how quickly the API front end answered that request.
How LatencyRadar measures response time →
Technical details
Doesn’t measure: A payment, Checkout, an authenticated API call, or the /healthcheck request in the daily history.
This page measures a request to the root of api.stripe.com. Stripe returned HTTP 404 in the saved run on 20 August 2026. That response is useful for timing the trip to the API front end, but it does not run a payment operation. A quick reply here cannot tell you how long a charge or PaymentIntent will take.
The daily history uses a different request: /healthcheck. It returns a small plain-text response without a key. We label it separately because its timings cannot replace the root request in the table above. The Dashboard sign-in page is also a separate request, with its own results when available.
Singapore and Tokyo received the root response in 18 and 20 ms typical in the published run; San Francisco took 74 ms. Those are front-end response times. Checkout, webhook delivery, authenticated API calls and the signed-in Dashboard each involve work this test does not perform.
| Test location | Typical response time | Slower response time | Requests |
|---|---|---|---|
| Amsterdam | 55 ms | 80 ms | 20 |
| San Francisco | 74 ms | 76 ms | 20 |
| Montreal | 55 ms | 57 ms | 20 |
| Singapore | 18 ms | 21 ms | 20 |
| Tokyo | 20 ms | 25 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 api.stripe.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
Stripe API root
https://api.stripe.com
Independent measurement by LatencyRadar. Not affiliated with Stripe. · How we measure (v1.3)
How fast is your API compared to Stripe?
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.
