Исследование с проверкой источников: Exchange Status API Maintenance

Decision Matrix

Source Map

• Coinbase Status: Coinbase Status API (coinbase-status-api)
• Kraken Status: Kraken Status API (kraken-status-api)
• OKX: OKX Status (okx-status-page)
• OKX Technical Support: Get system status (okx-system-status-api)

Control Notes

1. Source class

Source class is the decision point where public documentation must become an operating rule. In this package, it means status pages, status APIs and venue announcements have different evidence strength. The practical action is to record which class produced the maintenance or outage signal. The unresolved edge is whether a venue updates all channels at the same speed, so the article keeps that edge explicit instead of turning it into a reward claim, licensing claim, approval claim, recovery guarantee, price implication, settlement guarantee or platform ranking.

2. Component mapping

Component mapping is the decision point where public documentation must become an operating rule. In this package, it means API, website, mobile, deposit and withdrawal components can diverge. The practical action is to map the component to the exact workflow before pausing or resuming. The unresolved edge is hidden dependencies not named as components, so the article keeps that edge explicit instead of turning it into a reward claim, licensing claim, approval claim, recovery guarantee, price implication, settlement guarantee or platform ranking.

The operating test is also narrow. A public page can prove public wording.

3. Maintenance window

Maintenance window is the decision point where public documentation must become an operating rule. In this package, it means scheduled maintenance can start, end, extend or conclude earlier than expected. The practical action is to store start, update and observed recovery timestamps. The unresolved edge is whether the service is stable after the public window ends, so the article keeps that edge explicit instead of turning it into a reward claim, licensing claim, approval claim, recovery guarantee, price implication, settlement guarantee or platform ranking.

The operating test is also narrow. A public page can prove public wording.

4. Account overlay

Account overlay is the decision point where public documentation must become an operating rule. In this package, it means public status does not prove private account eligibility. The practical action is to run account-specific read-only checks after public recovery. The unresolved edge is regional, KYC, subaccount or symbol restrictions, so the article keeps that edge explicit instead of turning it into a reward claim, licensing claim, approval claim, recovery guarantee, price implication, settlement guarantee or platform ranking.

The operating test is also narrow. A public page can prove public wording.

5. Automation pause

Automation pause is the decision point where public documentation must become an operating rule. In this package, it means bots need deterministic stop and resume rules. The practical action is to pause writes on degraded components and resume only after public plus private checks agree. The unresolved edge is manual override authority during partial outages, so the article keeps that edge explicit instead of turning it into a reward claim, licensing claim, approval claim, recovery guarantee, price implication, settlement guarantee or platform ranking.

The operating test is also narrow. A public page can prove public wording.

6. Evidence hygiene

Evidence hygiene is the decision point where public documentation must become an operating rule. In this package, it means status evidence should not expose credentials or balances. The practical action is to log URL, component, status label and timestamp only. The unresolved edge is retention policy for incident evidence, so the article keeps that edge explicit instead of turning it into a reward claim, licensing claim, approval claim, recovery guarantee, price implication, settlement guarantee or platform ranking.

The operating test is also narrow. A public page can prove public wording.

7. Claim boundary

Claim boundary is the decision point where public documentation must become an operating rule. In this package, it means status pages are not compensation, uptime SLA or execution guarantees. The practical action is to report status as operational context only. The unresolved edge is future postmortem details not yet published, so the article keeps that edge explicit instead of turning it into a reward claim, licensing claim, approval claim, recovery guarantee, price implication, settlement guarantee or platform ranking.

The operating test is also narrow. A public page can prove public wording.

Known Unknowns

• whether a venue updates all channels at the same speed
• hidden dependencies not named as components
• whether the service is stable after the public window ends
• regional, KYC, subaccount or symbol restrictions
• manual override authority during partial outages
• retention policy for incident evidence
• future postmortem details not yet published

Practical Takeaway

Exchange status pages and status APIs are useful incident evidence, but they do not prove account-specific execution, withdrawal availability or compensation. Coinbase and Kraken expose Statuspage API documentation for summary, component, incident and maintenance records, while OKX publishes a status page and documents system-status access in its API guide. The decision outcome is to record the status source, component name, timestamp, maintenance window and separate account checks before pausing or resuming automation. 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, callback, policy framework, settlement route or liquidity position will work under every future condition.