Exchange Status Page, API 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 Developers: System Status (binance-system-status)

Control Notes

1. Component

Component is the part of the decision where a public source has to become an operating rule. In this package, it means status pages divide incidents by products or components. The useful action is to match the exact API, wallet, market or chain surface. The unresolved edge is undocumented internal dependency, so this article does not convert that uncertainty into a promise, ranking, reward, approval, recovery guarantee, safety claim or future-availability claim.

For an operator, component should be recorded before funds, account access, wallet recovery, API order flow, document exports, tax records, whitelist changes, chain transfers, event-contract trades or tokenized-asset decisions become material. The record can stay simple: the official source URL, the date checked, the product or network under review, and a non-secret note describing why the next step is acceptable. Screenshots should avoid balances, identity documents, tax identifiers, API keys, recovery phrases, private keys, passphrases, verification codes and support-ticket private data.

2. Incident state

Incident state is the part of the decision where a public source has to become an operating rule. In this package, it means unresolved, investigating, scheduled and resolved states mean different actions. The useful action is to record status text and timestamp before retrying. The unresolved edge is late incident classification, so this article does not convert that uncertainty into a promise, ranking, reward, approval, recovery guarantee, safety claim or future-availability claim.

For an operator, incident state should be recorded before funds, account access, wallet recovery, API order flow, document exports, tax records, whitelist changes, chain transfers, event-contract trades or tokenized-asset decisions become material.

3. Maintenance window

Maintenance window is the part of the decision where a public source has to become an operating rule. In this package, it means scheduled maintenance can make a normal retry unsafe. The useful action is to pause automation until the announced window ends and checks pass. The unresolved edge is extension beyond planned time, so this article does not convert that uncertainty into a promise, ranking, reward, approval, recovery guarantee, safety claim or future-availability claim.

For an operator, maintenance window should be recorded before funds, account access, wallet recovery, API order flow, document exports, tax records, whitelist changes, chain transfers, event-contract trades or tokenized-asset decisions become material.

4. Private symptoms

Private symptoms is the part of the decision where a public source has to become an operating rule. In this package, it means a public green status does not prove a private account is healthy. The useful action is to compare with non-secret local logs and endpoint responses. The unresolved edge is account-specific restriction, so this article does not convert that uncertainty into a promise, ranking, reward, approval, recovery guarantee, safety claim or future-availability claim.

For an operator, private symptoms should be recorded before funds, account access, wallet recovery, API order flow, document exports, tax records, whitelist changes, chain transfers, event-contract trades or tokenized-asset decisions become material.

5. Order risk

Order risk is the part of the decision where a public source has to become an operating rule. In this package, it means retrying through an incident can duplicate or race orders. The useful action is to reconcile existing order state before resubmission. The unresolved edge is delayed fill report, so this article does not convert that uncertainty into a promise, ranking, reward, approval, recovery guarantee, safety claim or future-availability claim.

For an operator, order risk should be recorded before funds, account access, wallet recovery, API order flow, document exports, tax records, whitelist changes, chain transfers, event-contract trades or tokenized-asset decisions become material.

6. Asset or network scope

Asset or network scope is the part of the decision where a public source has to become an operating rule. In this package, it means a status incident can affect only one asset, network or product. The useful action is to avoid broad claims from a narrow notice. The unresolved edge is venue-specific naming, so this article does not convert that uncertainty into a promise, ranking, reward, approval, recovery guarantee, safety claim or future-availability claim.

For an operator, asset or network scope should be recorded before funds, account access, wallet recovery, API order flow, document exports, tax records, whitelist changes, chain transfers, event-contract trades or tokenized-asset decisions become material.

7. Stop rule

Stop rule is the part of the decision where a public source has to become an operating rule. In this package, it means stop when status, logs or account evidence conflict. The useful action is to freeze automated retries and escalate with evidence. The unresolved edge is support response timing, so this article does not convert that uncertainty into a promise, ranking, reward, approval, recovery guarantee, safety claim or future-availability claim.

Known Unknowns

• undocumented internal dependency
• late incident classification
• extension beyond planned time
• account-specific restriction
• delayed fill report
• venue-specific naming
• support response timing

Practical Takeaway

The safest version of this article is the one that stays boring and exact. An exchange status page is useful evidence, but it is not a complete private-account diagnosis. Coinbase, Kraken and OKX publish public status surfaces, and Binance developer documentation exposes system-status material for wallet/API checks. The decision outcome is to compare affected product, API surface, component status, maintenance window, unresolved incident state, update timestamp, asset or network scope and private account symptoms before deciding whether to retry, pause, cancel orders or escalate support. The user outcome is a clearer next inspection step, not a promise that a platform, API, transfer route, report, market contract or tokenized asset will work under every future condition.