Exchange Status-Page Maintenance and Incident Disclosure Radar

Decision Matrix

Source Map

• Coinbase: Coinbase Status (coinbase-status)
• Kraken: Kraken Status (kraken-status)
• OKX: OKX Status (okx-status)
• Binance: Latest Binance News (binance-announcements)

Control Notes

1. Incident object

Incident object is the point where public documentation must become an operating rule. In this package, it means status evidence must name the product or system that is impaired. The practical action is to record product, chain, API, funding rail or trading surface before drawing conclusions. The unresolved edge is whether a private account is affected by a separate hold or review, so the article keeps that edge explicit instead of turning it into a reward claim, licensing claim, approval claim, safety guarantee, recovery promise, platform ranking or price implication.

2. Update cadence

Update cadence is the point where public documentation must become an operating rule. In this package, it means an incident without updates leaves operational uncertainty. The practical action is to capture last update time and next expected check time. The unresolved edge is delayed updates, incomplete incident scope and future recurrence, so the article keeps that edge explicit instead of turning it into a reward claim, licensing claim, approval claim, safety guarantee, recovery promise, platform ranking or price implication.

The operating test is narrow.

3. Recovery marker

Recovery marker is the point where public documentation must become an operating rule. In this package, it means resolved status is a public service marker, not proof of private transaction completion. The practical action is to verify account-level state after the public marker changes. The unresolved edge is pending withdrawals, orphan deposits, partial fills and private support queues, so the article keeps that edge explicit instead of turning it into a reward claim, licensing claim, approval claim, safety guarantee, recovery promise, platform ranking or price implication.

The operating test is narrow.

4. Evidence hygiene

Evidence hygiene is the point where public documentation must become an operating rule. In this package, it means incident evidence should not expose balances, IDs, tax data or full account screenshots. The practical action is to store public URL, timestamp and non-secret ticket label only when needed. The unresolved edge is support attachments, screenshots and logs that reveal private data, so the article keeps that edge explicit instead of turning it into a reward claim, licensing claim, approval claim, safety guarantee, recovery promise, platform ranking or price implication.

The operating test is narrow.

5. Stop condition

Stop condition is the point where public documentation must become an operating rule. In this package, it means automation should pause when the public status and private account state disagree. The practical action is to stop retries or resubmissions until product status and account state are reconciled. The unresolved edge is rate-limit side effects, duplicate transfers and support-side reversals, so the article keeps that edge explicit instead of turning it into a reward claim, licensing claim, approval claim, safety guarantee, recovery promise, platform ranking or price implication.

The operating test is narrow.

Known Unknowns

• whether a private account is affected by a separate hold or review
• delayed updates, incomplete incident scope and future recurrence
• pending withdrawals, orphan deposits, partial fills and private support queues
• support attachments, screenshots and logs that reveal private data
• rate-limit side effects, duplicate transfers and support-side reversals

Practical Takeaway

Exchange status evidence should be separated from product marketing and from account-specific support outcomes. Coinbase, Kraken and OKX publish public status pages, while Binance publishes support announcements for service and product updates. The useful radar output is to record incident object, affected product, start time, update cadence, recovery marker, account-specific unknowns and the stop condition before treating a deposit, withdrawal, order, API stream or transfer problem as resolved. The article stops at the evidence boundary. It helps the reader decide what to inspect next without converting public documentation into a promise that a private account, wallet, API key, pool route, stablecoin balance, tokenized asset or policy framework will work under every future condition.