Дослідження з перевіркою джерел: Exchange Status PAGE Incident

Decision Matrix

Source Map

• OKX: OKX Status (okx-status)
• Kraken: Kraken Status (kraken-status)
• Kraken: Kraken Status API (kraken-status-api)
• Coinbase: Coinbase Status (coinbase-status)
• Coinbase: Coinbase Exchange Status (coinbase-exchange-status)

Control Notes

1. Affected service

Affected service is the part of the decision where the reader must turn a public source into an operating rule. In this package, it means which product or component is degraded. The useful action is to match the status item to the user's action. The unresolved edge is unlisted dependency, so this article does not convert that uncertainty into a promise, ranking, reward, approval, safety claim or future-availability claim.

For an operator, affected service should be recorded before funds, account access, wallet recovery, API order flow, whitelist changes, cross-chain transfers 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, API keys, recovery phrases, private keys, passphrases, verification codes and support-ticket private data.

2. Affected asset

Affected asset is the part of the decision where the reader must turn a public source into an operating rule. In this package, it means which token, chain or funding rail is named. The useful action is to avoid assuming all assets are affected. The unresolved edge is asset-specific recovery, so this article does not convert that uncertainty into a promise, ranking, reward, approval, safety claim or future-availability claim.

For an operator, affected asset should be recorded before funds, account access, wallet recovery, API order flow, whitelist changes, cross-chain transfers or tokenized-asset decisions become material.

3. Incident state

Incident state is the part of the decision where the reader must turn a public source into an operating rule. In this package, it means investigating, identified, monitoring, resolved or maintenance. The useful action is to wait for the correct state before retrying. The unresolved edge is state lag, so this article does not convert that uncertainty into a promise, ranking, reward, approval, safety claim or future-availability claim.

For an operator, incident state should be recorded before funds, account access, wallet recovery, API order flow, whitelist changes, cross-chain transfers or tokenized-asset decisions become material.

4. Timestamp

Timestamp is the part of the decision where the reader must turn a public source into an operating rule. In this package, it means when the update was posted and in which timezone. The useful action is to record the latest timestamp. The unresolved edge is late updates, so this article does not convert that uncertainty into a promise, ranking, reward, approval, safety claim or future-availability claim.

For an operator, timestamp should be recorded before funds, account access, wallet recovery, API order flow, whitelist changes, cross-chain transfers or tokenized-asset decisions become material.

5. Maintenance window

Maintenance window is the part of the decision where the reader must turn a public source into an operating rule. In this package, it means scheduled start and completion scope. The useful action is to avoid trading or transfer actions inside window. The unresolved edge is overrun risk, so this article does not convert that uncertainty into a promise, ranking, reward, approval, safety claim or future-availability claim.

For an operator, maintenance window should be recorded before funds, account access, wallet recovery, API order flow, whitelist changes, cross-chain transfers or tokenized-asset decisions become material.

6. Component scope

Component scope is the part of the decision where the reader must turn a public source into an operating rule. In this package, it means web, app, API, WebSocket, custody or funding. The useful action is to separate UI outage from API or funding outage. The unresolved edge is shared infrastructure, so this article does not convert that uncertainty into a promise, ranking, reward, approval, safety claim or future-availability claim.

For an operator, component scope should be recorded before funds, account access, wallet recovery, API order flow, whitelist changes, cross-chain transfers or tokenized-asset decisions become material.

7. Retry rule

Retry rule is the part of the decision where the reader must turn a public source into an operating rule. In this package, it means when a user should retry an action. The useful action is to retry only after relevant component recovery. The unresolved edge is private account restrictions, so this article does not convert that uncertainty into a promise, ranking, reward, approval, safety claim or future-availability claim.

For an operator, retry rule should be recorded before funds, account access, wallet recovery, API order flow, whitelist changes, cross-chain transfers or tokenized-asset decisions become material.

8. API evidence

API evidence is the part of the decision where the reader must turn a public source into an operating rule. In this package, it means machine-readable status data. The useful action is to use API only as supporting evidence. The unresolved edge is API caching, so this article does not convert that uncertainty into a promise, ranking, reward, approval, safety claim or future-availability claim.

For an operator, api evidence should be recorded before funds, account access, wallet recovery, API order flow, whitelist changes, cross-chain transfers or tokenized-asset decisions become material.

9. Evidence packet

Evidence packet is the part of the decision where the reader must turn a public source into an operating rule. In this package, it means official URL, checked date, service, asset and state. The useful action is to do not publish account screenshots or balances. The unresolved edge is privacy retention, so this article does not convert that uncertainty into a promise, ranking, reward, approval, safety claim or future-availability claim.

10. Stop rule

Stop rule is the part of the decision where the reader must turn a public source into an operating rule. In this package, it means when radar should remain unknown. The useful action is to stop if the page does not name service, asset, state or time. The unresolved edge is future page redesign, so this article does not convert that uncertainty into a promise, ranking, reward, approval, safety claim or future-availability claim.

Known Unknowns

• unlisted dependency
• asset-specific recovery
• state lag
• late updates
• overrun risk
• shared infrastructure
• private account restrictions
• API caching
• privacy retention
• future page redesign

Practical Takeaway

The safest version of this article is the one that stays boring and exact. NexuAlpha Radar scores exchange status pages as operational disclosure tools, not as trust badges. OKX Status says it displays system maintenance information, issue descriptions and deposit/withdrawal status. Kraken Status is the public status page for Kraken Digital Asset Exchange and exposes component status, past incidents and API documentation. Coinbase publishes consumer and exchange status pages with incident and component information. The useful radar question is whether the page tells a user the affected service, asset or network, current state, timestamps, maintenance window, component scope and next update path before the user retries a deposit, withdrawal, API order or account action. The user outcome is a clearer next inspection step, not a promise that a platform, API, transfer route or tokenized asset will work under every future condition.