Bitstamp: vendor-reported critical incident on September 24 (tracked 2d 7h)
Sep 24, 09:28 AM → Sep 26, 04:30 PM · 2d 7h · high
Bitstamp reported a critical-impact incident on its own status page. PulseWatch followed the vendor's status page and did not independently confirm the incident. PulseWatch tracked the incident for 2d 7h, from Thu, 24 Sep 2026 09:28:25 GMT to Sat, 26 Sep 2026 16:30:40 GMT. That is how long PulseWatch kept the incident open, not a measurement of how long the service was affected.
Impact
This high-severity incident affected the Bitstamp service for a duration of 2 days and 7 hours. The disruption was identified through automated monitoring and the vendor's status page. No user-reported data was collected or recorded for this incident.
Incident timeline
- Sep 24, 09:28 AM
The vendor reported a critical-impact incident on its own status page; PulseWatch began tracking it
- Sep 24, 09:28 AM
Status updated: possible issue
- Sep 26, 04:30 PM
PulseWatch closed the incident
Official updates
- Sep 24, 09:28 AM
Bitstamp reported the incident on its status page.
View official source