Benchmark report

Stripe thumbnail

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

Amsterdam 309ms typicalSan Francisco 199ms typicalMontreal 230ms typicalSingapore 289ms typicalTokyo 231ms typicalMumbai 670ms typical
  • United StatesSan Francisco
    199 ms
  • CanadaMontreal
    230 ms
  • JapanTokyo
    231 ms
  • SingaporeSingapore
    289 ms
  • NetherlandsAmsterdam
    309 ms
  • IndiaMumbai
    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.

ConnectTLSServer waitDownload
IndiaMumbai
628 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 locations

Click a city to see its stage-by-stage breakdown.

ConnectTLSServer waitDownload
NetherlandsAmsterdam
286 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
United StatesSan Francisco
200 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
CanadaMontreal
220 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
SingaporeSingapore
260 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
JapanTokyo
183 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
IndiaMumbai
628 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

Daily median of 5 requests per location, 21 September 2026 to 20 October 2026.
05001000 ms21 Sept20 Oct
Show the numbers
DayAmsterdamSan FranciscoMontrealSingaporeTokyoMumbai
21 September 2026284 ms202 ms253 ms355 ms251 ms636 ms
22 September 2026389 ms198 ms235 ms262 ms190 ms695 ms
23 September 2026312 ms196 ms221 ms351 ms266 ms641 ms
24 September 2026328 ms191 ms256 ms360 ms245 ms736 ms
25 September 2026342 ms198 ms228 ms381 ms178 ms693 ms
26 September 2026398 ms199 ms246 ms255 ms185 ms649 ms
27 September 2026303 ms239 ms219 ms436 ms183 ms638 ms
28 September 2026312 ms203 ms252 ms334 ms186 ms636 ms
29 September 2026346 ms198 ms219 ms259 ms178 ms646 ms
30 September 2026352 ms193 ms218 ms261 ms186 ms635 ms
1 October 2026284 ms195 ms221 ms257 ms188 ms642 ms
2 October 2026284 ms203 ms222 ms258 ms174 ms642 ms
3 October 2026281 ms198 ms222 ms262 ms194 ms633 ms
4 October 2026284 ms202 ms220 ms258 ms180 ms621 ms
5 October 2026274 ms195 ms217 ms251 ms176 ms635 ms
6 October 2026290 ms214 ms218 ms252 ms188 ms621 ms
7 October 2026299 ms203 ms235 ms290 ms235 ms665 ms
9 October 2026309 ms194 ms229 ms274 ms272 ms671 ms
10 October 2026326 ms196 ms241 ms426 ms282 ms674 ms
11 October 2026311 ms203 ms247 ms294 ms199 ms697 ms
12 October 2026302 ms212 ms228 ms286 ms271 ms695 ms
13 October 2026304 ms200 ms224 ms296 ms205 ms667 ms
14 October 2026331 ms202 ms224 ms299 ms202 ms656 ms
15 October 2026306 ms198 ms227 ms293 ms207 ms748 ms
16 October 2026303 ms201 ms231 ms300 ms231 ms681 ms
17 October 2026341 ms200 ms230 ms286 ms259 ms673 ms
18 October 2026321 ms199 ms228 ms288 ms272 ms665 ms
19 October 2026307 ms195 ms244 ms273 ms311 ms656 ms
20 October 2026297 ms204 ms226 ms283 ms196 ms629 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 locationTypical response timeSlower response timeRequests
Amsterdam309 ms398 ms65
San Francisco199 ms221 ms65
Montreal230 ms267 ms65
Singapore289 ms426 ms65
Tokyo231 ms317 ms65
Mumbai670 ms802 ms65

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.

Test my site

No account required · Takes about 30 seconds.

More benchmarks

All benchmarks →