Benchmark report
Is the Stripe dashboard slow?
Load times from 6 cities
Slow from some locations
Mumbai waited 670 ms, about 3.4× San Francisco. The gap suggests some test locations reach a distant server.
- Fastest
- 199 ms
- San Francisco
- Slowest
- 670 ms
- Mumbai
- Successful requests
- 100%
- 6 locations
Response time around the world
San Francisco
199 msMontreal
230 msTokyo
231 msSingapore
289 msAmsterdam
309 msMumbai
670 ms
Why does Mumbai take 670 ms?
Distance and Stripe’s own wait add up. The Stripe server that answered Mumbai was about 63 ms away, against 5 ms for Singapore, and a new connection crosses that gap several times. In the controlled run of 4 October, Mumbai spent 63 ms connecting, 67 ms setting up the secure connection and 187 ms receiving the 147 KB page, with one more round trip inside the wait. Waiting for Stripe to send the page took most of the time in every city. Take one round trip off that wait and it was 58 ms in San Francisco, 113 ms in Montreal and 150 to 250 ms in Tokyo, Amsterdam, Singapore and Mumbai. That pattern suggests Stripe builds the page in one place, nearer San Francisco than our other cities, and sends it back through a server near each city.
Click the location to see each stage.
Mumbai628 ms
- Finding the server
- 7 ms
- Reaching the server
- 63 ms
- Setting up security
- 67 ms
- Waiting for the server: most of the time
- 311 ms
- Receiving the response
- 187 ms
- Total
- 628 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.
Amsterdam286 ms
- Finding the server
- 3 ms
- Reaching the server
- 17 ms
- Setting up security
- 21 ms
- Waiting for the server: most of the time
- 190 ms
- Receiving the response
- 58 ms
- Total
- 286 ms
San Francisco200 ms
- Finding the server
- 18 ms
- Reaching the server
- 24 ms
- Setting up security
- 28 ms
- Waiting for the server: most of the time
- 82 ms
- Receiving the response
- 66 ms
- Total
- 200 ms
Montreal220 ms
- Finding the server
- 11 ms
- Reaching the server
- 19 ms
- Setting up security
- 20 ms
- Waiting for the server: most of the time
- 132 ms
- Receiving the response
- 49 ms
- Total
- 220 ms
Singapore260 ms
- Finding the server
- 7 ms
- Reaching the server
- 5 ms
- Setting up security
- 8 ms
- Waiting for the server: most of the time
- 236 ms
- Receiving the response
- 11 ms
- Total
- 260 ms
Tokyo183 ms
- Finding the server
- 3 ms
- Reaching the server
- 6 ms
- Setting up security
- 8 ms
- Waiting for the server: most of the time
- 158 ms
- Receiving the response
- 11 ms
- Total
- 183 ms
Mumbai628 ms
- Finding the server
- 7 ms
- Reaching the server
- 63 ms
- Setting up security
- 67 ms
- Waiting for the server: most of the time
- 311 ms
- Receiving the response
- 187 ms
- Total
- 628 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
Stripe still feels slow?
- Check Stripe’s status page
- Dashboard incidents are posted there. When the dashboard is slow for everyone at once, that is where it shows first.
- This is the sign-in page, not the signed-in dashboard
- We time the HTML of the login page. After you sign in, the dashboard loads scripts and calls Stripe’s API from your browser, and none of those requests are part of this measurement.
- Distance from San Francisco adds time
- In our checks the page took about 200 ms in San Francisco, about 300 ms in Amsterdam and Singapore, and 670 ms in Mumbai. Your browser reuses its connection after the first page, so later pages skip the connection setup, but not Stripe’s wait.
Response time over the last 30 days
Show the numbers
| Day | Amsterdam | San Francisco | Montreal | Singapore | Tokyo | Mumbai |
|---|---|---|---|---|---|---|
| 21 September 2026 | 284 ms | 202 ms | 253 ms | 355 ms | 251 ms | 636 ms |
| 22 September 2026 | 389 ms | 198 ms | 235 ms | 262 ms | 190 ms | 695 ms |
| 23 September 2026 | 312 ms | 196 ms | 221 ms | 351 ms | 266 ms | 641 ms |
| 24 September 2026 | 328 ms | 191 ms | 256 ms | 360 ms | 245 ms | 736 ms |
| 25 September 2026 | 342 ms | 198 ms | 228 ms | 381 ms | 178 ms | 693 ms |
| 26 September 2026 | 398 ms | 199 ms | 246 ms | 255 ms | 185 ms | 649 ms |
| 27 September 2026 | 303 ms | 239 ms | 219 ms | 436 ms | 183 ms | 638 ms |
| 28 September 2026 | 312 ms | 203 ms | 252 ms | 334 ms | 186 ms | 636 ms |
| 29 September 2026 | 346 ms | 198 ms | 219 ms | 259 ms | 178 ms | 646 ms |
| 30 September 2026 | 352 ms | 193 ms | 218 ms | 261 ms | 186 ms | 635 ms |
| 1 October 2026 | 284 ms | 195 ms | 221 ms | 257 ms | 188 ms | 642 ms |
| 2 October 2026 | 284 ms | 203 ms | 222 ms | 258 ms | 174 ms | 642 ms |
| 3 October 2026 | 281 ms | 198 ms | 222 ms | 262 ms | 194 ms | 633 ms |
| 4 October 2026 | 284 ms | 202 ms | 220 ms | 258 ms | 180 ms | 621 ms |
| 5 October 2026 | 274 ms | 195 ms | 217 ms | 251 ms | 176 ms | 635 ms |
| 6 October 2026 | 290 ms | 214 ms | 218 ms | 252 ms | 188 ms | 621 ms |
| 7 October 2026 | 299 ms | 203 ms | 235 ms | 290 ms | 235 ms | 665 ms |
| 9 October 2026 | 309 ms | 194 ms | 229 ms | 274 ms | 272 ms | 671 ms |
| 10 October 2026 | 326 ms | 196 ms | 241 ms | 426 ms | 282 ms | 674 ms |
| 11 October 2026 | 311 ms | 203 ms | 247 ms | 294 ms | 199 ms | 697 ms |
| 12 October 2026 | 302 ms | 212 ms | 228 ms | 286 ms | 271 ms | 695 ms |
| 13 October 2026 | 304 ms | 200 ms | 224 ms | 296 ms | 205 ms | 667 ms |
| 14 October 2026 | 331 ms | 202 ms | 224 ms | 299 ms | 202 ms | 656 ms |
| 15 October 2026 | 306 ms | 198 ms | 227 ms | 293 ms | 207 ms | 748 ms |
| 16 October 2026 | 303 ms | 201 ms | 231 ms | 300 ms | 231 ms | 681 ms |
| 17 October 2026 | 341 ms | 200 ms | 230 ms | 286 ms | 259 ms | 673 ms |
| 18 October 2026 | 321 ms | 199 ms | 228 ms | 288 ms | 272 ms | 665 ms |
| 19 October 2026 | 307 ms | 195 ms | 244 ms | 273 ms | 311 ms | 656 ms |
| 20 October 2026 | 297 ms | 204 ms | 226 ms | 283 ms | 196 ms | 629 ms |
About this measurement
GET dashboard.stripe.com/login · 65 requests per location over 13 daily runs · 7 October 2026 to 20 October 2026
What we tested · Website document. The dashboard.stripe.com/login page: 147 KB of HTML from Stripe's own front end, sent uncached. It is the sign-in screen every Stripe user loads.
How LatencyRadar measures response time →Also measured: Stripe API →
Technical details
Doesn’t measure: Signing in, the dashboard after login, the API at api.stripe.com, webhooks or Checkout.
This page covers the Stripe dashboard’s sign-in page, dashboard.stripe.com/login: about 147 KB of HTML that Stripe sends uncached from its own servers. Every Stripe user loads it first, and it shows how quickly Stripe answers a browser in each of our cities. It does not cover signing in, the dashboard after login, Checkout, webhooks or Stripe.js. The API is measured on its own: the Stripe API report times a request that does no payment work, which came back in 13 ms from Tokyo.
Between 7 and 20 October 2026 the typical time was 199 ms in San Francisco, 230 ms in Montreal, 231 ms in Tokyo, 289 ms in Singapore, 309 ms in Amsterdam and 670 ms in Mumbai. Most days looked alike. San Francisco’s daily medians stayed between 194 and 212 ms and Amsterdam’s between 297 and 341 ms; Mumbai’s ran from 629 to 748 ms, slowest on 15 October. Tokyo and Singapore moved more, Tokyo from 196 to 311 ms and Singapore from 273 to 426 ms, with Singapore’s slowest day on 10 October. The slower time, which 95% of requests finished within, was 221 ms in San Francisco and 802 ms in Mumbai.
| Test location | Typical response time | Slower response time | Requests |
|---|---|---|---|
| Amsterdam | 309 ms | 398 ms | 65 |
| San Francisco | 199 ms | 221 ms | 65 |
| Montreal | 230 ms | 267 ms | 65 |
| Singapore | 289 ms | 426 ms | 65 |
| Tokyo | 231 ms | 317 ms | 65 |
| Mumbai | 670 ms | 802 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 dashboard.stripe.com/login
- 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: 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.
Stripe dashboard login
https://dashboard.stripe.com/login
Independent measurement by LatencyRadar. Not affiliated with Stripe. · 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.