Is Bitstamp down in the US?
Vendor reports an incidentWhat Bitstamp reports
Bitstamp reports an incident on its status page: Delayed crypto transfers.
Impact: minor. Since 2026-11-04 20:19 UTC.
Latest update, 2026-11-04 20:19 UTC: Crypto transfers may be delayed due to a compliance vendor's outage. All customer funds are safe, and we are working to restore normal operations. Trading is not impacted.
Our regional reading
This is our own reading from outside, shown beside the vendor's statement. It is not counted as a separate outage.
Checks passingin the US, measured from Ashburn and San Jose
All 2 of our probes in the US, in Ashburn and San Jose, read checks passing when they last checked Bitstamp at Nov 5, 2026, 6:07 PM UTC.
Over the last 24 hours we completed 253 checks from Ashburn and San Jose and 253 answered cleanly, 100.00% availability.
Of the 2 other regions we check Bitstamp from, all 2 read checks passing right now.
Email me when Bitstamp reports an incident on its status page, and again when it reports it resolved.
What our Ashburn and San Jose probes measured
Last checked Nov 5, 2026, 6:07 PM UTC.
Bitstamp from Ashburn and San Jose over the last 30 days
Over the last 30 days, Bitstamp answered our Ashburn probe in 1,315 ms on average, and 1 check in 20 took longer than 1,999 ms.
Over the last 30 days, Bitstamp answered our San Jose probe in 1,651 ms on average, and 1 check in 20 took longer than 2,482 ms.
Ranked by average response time across the 4 cities we check Bitstamp from, Ashburn 1st, San Jose 3rd; Ashburn was fastest at 1,315 ms and Tokyo slowest at 1,716 ms.
From Ashburn and San Jose we ran 787 checks of Bitstamp in 4 days, and 784 answered cleanly: 99.61% availability.
2 of the 4 days had at least one failed check. The weakest was Nov 4 (UTC), at 99.20% across 252 checks.
In Ashburn local time (EST), Bitstamp was slowest around 12 AM, at 1,912 ms on average over the last 14 days, and quickest around 9 AM, at 806 ms.
| Day (UTC) | Checks | Availability | Average response |
|---|---|---|---|
| Thu, Nov 5 | 186 | 100.00% | 1,551 ms |
| Wed, Nov 4 | 252 | 99.20% | 1,182 ms |
| Tue, Nov 3 | 246 | 99.59% | 1,568 ms |
| Mon, Nov 2 | 103 | 100.00% | 1,724 ms |
Bitstamp outages measured from the US
Our Ashburn and San Jose probes measured no confirmed Bitstamp outage in the last 90 days.
How the other regions read right now
Of the 2 other regions we check Bitstamp from, all 2 read checks passing right now.
| Probe city | Right now | Last 24h |
|---|---|---|
| Frankfurt | Checks passing | 100.00% of 99 checks |
| Tokyo | Checks passing | 100.00% of 60 checks |
Other countries we check Bitstamp from
How we measured this
The US readings on this page come from RealUptime's own Ashburn and San Jose probes against Bitstamp's public endpoints. They are not user reports, and they are not Bitstamp's own status page.
See Bitstamp's full check readings, the 90-day history by region, or the outage tracker methodology.
The US readings here are taken from that country and show the time of the last one, but Bitstamp has not yet accumulated enough continuous history for us to publish this page to search engines.
Check your own site from Ashburn
This page shows what we see when we check this service, using the same ten regions, for a site you run. RealUptime Monitor watches your own servers from inside your network, and it starts free.
Start monitoring your own serversRun a service people depend on? Give them a status page on your own domain, checked every minute from six regions, for $9 a month. Get Starter