Is Bitstamp down?
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 passingchecked 1 minute ago
Our checks of Bitstamp pass from all 4 regions we check.
As of Nov 5, 2026, 2:53 PM UTC, RealUptime's checks of Bitstamp passed in all 4 regions that returned a reading.
Bitstamp reports: Minor incident (“Partially Degraded Service”)
Bitstamp reports an active incident: Delayed crypto transfers (minor incident, since Nov 4, 2026, 8:19 PM UTC)
Bitstamp's own component breakdown, as they publish it
- ADADegraded performance
- ADADegraded performance
- WebOperational
- ALGODegraded performance
- ALGODegraded performance
- FIXOperational
- AVAXDegraded performance
- AVAXDegraded performance
- RESTOperational
- BCHDegraded performance
- BCHDegraded performance
- Mobile appOperational
- WebsocketOperational
- BTCDegraded performance
- BTCDegraded performance
- TradingOperational
- DOGEDegraded performance
- DOGEDegraded performance
- DOTDegraded performance
- DOTDegraded performance
- ETH & ERC20Degraded performance
- ETH & ERC20Degraded performance
- FLRDegraded performance
- FLRDegraded performance
- HBARDegraded performance
- HBARDegraded performance
- LTCDegraded performance
- LTCDegraded performance
- NEARDegraded performance
- NEARDegraded performance
- SGBDegraded performance
- SGBDegraded performance
- SOL & SPL tokensDegraded performance
- SOL & SPL tokensDegraded performance
- SUIDegraded performance
- SUIDegraded performance
- XLMDegraded performance
- XLMDegraded performance
- XRPDegraded performance
- XRPDegraded performance
- CSPRDegraded performance
- CSPRDegraded performance
- EGLDDegraded performance
- EGLDDegraded performance
- ICPDegraded performance
- ICPDegraded performance
- XDCDegraded performance
- XDCDegraded performance
- APTDegraded performance
- APTDegraded performance
- ARBDegraded performance
- ARBDegraded performance
- ATOMDegraded performance
- ATOMDegraded performance
- BNBDegraded performance
- BNBDegraded performance
- CCDegraded performance
- CCDegraded performance
- ETCDegraded performance
- ETCDegraded performance
- HYPEDegraded performance
- HYPEDegraded performance
- INJDegraded performance
- INJDegraded performance
- MNTDegraded performance
- MNTDegraded performance
- MEGADegraded performance
- MEGADegraded performance
- MONDegraded performance
- MONDegraded performance
- OPDegraded performance
- OPDegraded performance
- POLDegraded performance
- POLDegraded performance
- SEIDegraded performance
- SEIDegraded performance
- SDegraded performance
- SDegraded performance
- TAODegraded performance
- TAODegraded performance
- TONDegraded performance
- TONDegraded performance
- TRXDegraded performance
- TRXDegraded performance
- XPLDegraded performance
- XPLDegraded performance
- XTZDegraded performance
- XTZDegraded performance
- ZECDegraded performance
- ZECDegraded performance
These are Bitstamp's components, named and scored by Bitstamp. We do not map them onto the functions we check above, because we have no way to know which of their components our checks touch. Two lists, side by side, neither one rewriting the other.
This is Bitstamp's own claim about their service, shown separately from what we measured. We never change our own numbers based on what a vendor reports, and this reading never changes theirs. Read both.
Bitstamp response time, by region
Check your own site while you wait on Bitstamp
Watching an outage above does not tell you whether your own connection or site is also having a problem. Enter your own URL for one live check, right now, no signup. This checks the site you enter, not Bitstamp. It cannot diagnose Bitstamp's own systems.
What we measured, function by function
Bitstamp answers on more than one surface, and they can fail apart. Each row is one surface, checked from the same regions. The verdict above follows the api row, because that is the surface we treat as this service's own; a failure on any other row is a partial outage, not a full one.
- WebUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Not monitored from this regionCanada: Not monitored from this regionUK: Not monitored from this regionSoutheast Asia: Not monitored from this regionAustralia: Not monitored from this regionSouth America: Not monitored from this region
- APIprimaryUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Not monitored from this regionCanada: Not monitored from this regionUK: Not monitored from this regionSoutheast Asia: Not monitored from this regionAustralia: Not monitored from this regionSouth America: Not monitored from this region
Email me when Bitstamp reports an incident on its status page, and again when it reports it resolved.
Get an email when Bitstamp reports an incident
Email me when Bitstamp reports an incident on its status page, and again when it reports it resolved. No account, no card.
What our checks show, and what people reported
- North AmericaNot monitored from this regionUS-East, US-West, US-Central, Canada
- US-EastChecks passinglatency: 621msstatus code: 200checked: Nov 5, 2026, 2:53 PM UTC0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach Bitstamp normally. We do not have enough reports from US-East to say anything about what people there are seeing.
- US-WestChecks passinglatency: 1339msstatus code: 200checked: Nov 5, 2026, 2:53 PM UTC0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach Bitstamp normally. We do not have enough reports from US-West to say anything about what people there are seeing.
- US-CentralNot monitored from this regionBitstamp is not monitored from this region.0 people in the last 5 minutesNot enough reports to say
- CanadaNot monitored from this regionBitstamp is not monitored from this region.0 people in the last 5 minutesNot enough reports to say
- South AmericaNot monitored from this regionBitstamp is not monitored from this region.0 people in the last 5 minutesNot enough reports to say
- EuropeNot monitored from this regionEurope, UK
- EuropeChecks passinglatency: 1191msstatus code: 200checked: Nov 5, 2026, 2:41 PM UTC0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach Bitstamp normally. We do not have enough reports from Europe to say anything about what people there are seeing.
- UKNot monitored from this regionBitstamp is not monitored from this region.0 people in the last 5 minutesNot enough reports to say
- Asia PacificNot monitored from this regionAsia-Pacific, Southeast Asia, Australia
- Asia-PacificChecks passinglatency: 1958msstatus code: 200checked: Nov 5, 2026, 2:48 PM UTC0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach Bitstamp normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
- Southeast AsiaNot monitored from this regionBitstamp is not monitored from this region.0 people in the last 5 minutesNot enough reports to say
- AustraliaNot monitored from this regionBitstamp is not monitored from this region.0 people in the last 5 minutesNot enough reports to say
Somewhere else or not sure: 0 people in the last 5 minutes
These are unverified reports from people using Bitstamp, counted separately from what our own probes measure. Anyone can file one, no account is needed, and the region on a report is chosen by the person filing it. We never open, extend or close an outage in our record based on report volume: only our own measurements do that. We have not received any reports for Bitstamp yet, which is not evidence that nothing is wrong.
Recent probe events
check entries are our own probes' readings; declared entries are the vendor's. How this check works
We have been measuring Bitstamp since November 2, 2026. We show nothing from before that date, and we never add an outage we did not observe ourselves, from any source.
Need this in writing? Generate an SLA evidence report for Bitstamp covering any window you pick, with our check readings and Bitstamp's own claim at the time, side by side.
Full check history for Bitstamp: 90 days of check results by region, month-by-month uptime by our checks, and every probe event on record.
Monitor your own site the same way
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
Put this badge in your README
Live, from this page's own readings.[](https://realuptime.io/outages/bitstamp)<a href="https://realuptime.io/outages/bitstamp"><img src="https://realuptime.io/outages/bitstamp/badge.svg?days=30" alt="Bitstamp uptime by RealUptime's checks" height="20"></a>Share of checks passed over 30 days; the window is printed on it. If our readings go stale it says stale, and if we have no readings it says so and shows no color. How the badge works.
To cite this page: RealUptime, "Is Bitstamp down?", https://realuptime.io/outages/bitstamp. The readings change with every check, so give the date you read them.
What we check
What our check can and cannot see
A pass means a public route of the service's API answered our request normally. We do not check what it returned, so it does not show that the data is right, that sign-in works or that the rest of the product works.
Host checked: www.bitstamp.net