Research date: 2026-08-29. Detector regime-v1.
Sufficient-liquidity period starts 2013-03-01, making this the start of the review window.
Publication floor: 60 minutes, after corroboration or explicit review. Duration selects candidates; it does not necessarily publish a public row.
OHLCV cannot distinguish no trades, omitted minutes, fills, or downtime. Official announced windows often sit a few hours before the observed zero-run on the same UTC date.
DST on the corrected UTC grid was checked across US and EU transitions. It creates no missing UTC minutes and no hour-long zero-volume run from a timestamp discontinuity.
reference on the sidecar)| Observed UTC | Evidence |
|---|---|
| 2014-02-02 09:01–11:12 | Official scheduled unavailability 09:00–12:00 GMT+1 |
| 2014-07-11 04:16–06:14 | Official scheduled unavailability 06:00–08:00 CET |
| 2015-01-05 09:13 – 2015-01-09 21:05 | Hot-wallet hack; CoinDesk + Ars Technica |
| 2019-07-25 09:17–10:29 | Official scheduled platform unavailability from 09:00 UTC |
| 2020-04-25 19:58 – 2020-04-26 00:45 | Official downtime report: matching engine 20:00–00:30 UTC |
| 2020-08-26 10:04–11:52 | Official scheduled unavailability from 10:00 UTC |
| 2021-04-14 08:02–09:39 | Official Bitstamp post, 08:00–10:00 UTC maintenance |
| 2021-10-20 08:02–09:04 | Official scheduled system-wide maintenance 08:00–09:00 UTC |
| 2022-01-05 08:02–10:27 | Official scheduled unavailability from 08:00 UTC |
| 2022-05-11 08:04–09:14 | Official scheduled unavailability from 10:00 CET |
| 2022-07-27 08:02–09:09 | Official scheduled unavailability from 08:00 UTC |
| 2023-03-23 10:04–11:54 | Official scheduled unavailability from 10:00 UTC |
reviewed_unconfirmed)Unexplained silence / possible data-quality, not proved outages.
Liquid-period runs that overlap a Statuspage window. The remainder stays in
the ledger as excluded.
These are not written as scheduled_maintenance (Statuspage remains that
flag’s source) and did not produce a published 60-minute unexplained zero-run.