How complete is this?

No gap ledger covers this dataset, so nothing here can say when its producer was not looking.

Append-only and NOT backfillable: it starts on 2026-08-18, the day polling began, and there is no source to rebuild the days before it from. The venues listed as UNMONITORED publish no status this site can read at all — see /coverage/.

When we were not looking

No gap ledger covers this dataset.

Days that are not a day’s worth

This dataset is not a continuous record: a day with nothing on it is a quiet day in the world rather than a gap in ours, so no per-day expectation is stated.

What produced these rows

• coinbase 1 row(s)https://status.coinbase.com/api/v2/summary.json
• kraken 1 row(s)https://status.kraken.com/api/v2/summary.json
• gemini 1 row(s)https://status.gemini.com/api/v2/summary.json
• bitstamp 1 row(s)https://status.bitstamp.net/api/v2/summary.json
• crypto-com 1 row(s)https://status.crypto.com/api/v2/summary.json
• bitfinex 1 row(s)https://bitfinex.statuspage.io/api/v2/summary.json
• bitmex 1 row(s)https://status.bitmex.com/api/v2/summary.json
• bitflyer 1 row(s)https://status.bitflyer.com/api/v2/summary.json
• binance 1 row(s)https://api.binance.com/sapi/v1/system/status
• okx 1 row(s)https://www.okx.com/api/v5/system/status
• bybit 0 row(s)UNMONITORED — Bybit publishes no status page we can read. The one at bybit.statuspage.io belongs to somebody else — it is headed "Login" and lists another company's systems — so we refuse it rather than report it as theirs. Their own announcements feed mixes marketing with outage notices and never states whether the exchange is up, so a dot drawn from it would be our guess rather than their statement.
• kucoin 0 row(s)UNMONITORED — KuCoin's status address does not exist. Their announcements feed does, and it never says whether the exchange is up right now.
• bitget 0 row(s)UNMONITORED — Bitget's status page is private and will not open for us.
• gate-io 0 row(s)UNMONITORED — Gate's status address does not exist, and their announcements feed will not answer anyone without an account.
• htx 0 row(s)UNMONITORED — HTX's status address does not exist, and we could find no other source that states whether the exchange is up without an account.
• upbit 0 row(s)UNMONITORED — Upbit's status address does not exist. Their announcements feed does, and it never says whether the exchange is up right now.
• deribit 0 row(s)UNMONITORED — Deribit's status page is private and will not open for us.

Corrections

None issued against this dataset.

Our own downtime, inside this window

• 2026-10-07 38 min degraded · The wire wrote no ledger row for 38 minutes (stage 'budget') not written up yet
• 2026-10-06 44 min degraded · The wire wrote no ledger row for 44 minutes (stage 'budget') not written up yet
• 2026-10-06 107 min degraded · The wire wrote no ledger row for 107 minutes (stage 'budget') not written up yet
• 2026-10-06 47 min degraded · The wire wrote no ledger row for 47 minutes (stage 'budget') not written up yet
• 2026-10-03 39 min degraded · The wire wrote no ledger row for 39 minutes (stage 'budget') not written up yet
• 2026-10-03 46 min degraded · The wire wrote no ledger row for 46 minutes (stage 'budget') not written up yet
• 2026-10-02 65 min degraded · The wire wrote no ledger row for 65 minutes (stage 'budget') not written up yet
• 2026-09-29 57 min degraded · The wire wrote no ledger row for 57 minutes (stage 'budget') not written up yet
• 2026-09-28 44 min degraded · The wire wrote no ledger row for 44 minutes (stage 'budget') not written up yet
• 2026-09-28 39 min degraded · The wire wrote no ledger row for 39 minutes (stage 'budget') not written up yet
• 2026-09-28 37 min degraded · The wire wrote no ledger row for 37 minutes (stage 'budget') not written up yet
• 2026-09-28 31 min degraded · The wire wrote no ledger row for 31 minutes (stage 'budget') not written up yet
• 2026-09-25 31 min degraded · The wire wrote no ledger row for 31 minutes (stage 'budget') not written up yet
• 2026-09-24 31 min degraded · The wire wrote no ledger row for 31 minutes (stage 'budget') not written up yet

Anything known to be wrong?

5 problems are open in this site’s own checks; none of them is about this dataset.

Assembled from records this site already keeps — the gap ledgers, the corrections record, the incident record and the gate’s own tally. It adds no new collection. The same report ships with the download as /api/v1/exchange-incidents.integrity.txt and inside the JSON. What this site cannot see at all.