交易所状态 API 与维护披露雷达
本文正文暫以英文原文展示，翻譯版本需完成來源複核後再發布。
已验证事实边界
1. Coinbase Status API documentation exposes programmatic status endpoints such as status and components through its public status page API. 2. Kraken Status API documentation exposes summary, status, components, incidents and scheduled-maintenance endpoint examples. 3. OKX publishes a public status page for system maintenance, issue descriptions and deposit or withdrawal status. 4. OKX API documentation includes a system-status API route for exchange status data. 5. A green component status does not prove that a private account, symbol, region, wallet route or API key can act successfully. 6. A responsible status radar separates public component status, scheduled maintenance, private account checks and incident stop rules.
收起完整分析
决策矩阵
文章表格：可橫向滑動，或聚焦表格區域後使用方向鍵。
| Check | What it means | Practical action | Unknown to keep explicit |
|---|---|---|---|
| Source class | status pages, status APIs and venue announcements have different evidence strength | record which class produced the maintenance or outage signal | whether a venue updates all channels at the same speed |
| Component mapping | API, website, mobile, deposit and withdrawal components can diverge | map the component to the exact workflow before pausing or resuming | hidden dependencies not named as components |
| Maintenance window | scheduled maintenance can start, end, extend or conclude earlier than expected | store start, update and observed recovery timestamps | whether the service is stable after the public window ends |
| Account overlay | public status does not prove private account eligibility | run account-specific read-only checks after public recovery | regional, KYC, subaccount or symbol restrictions |
| Automation pause | bots need deterministic stop and resume rules | pause writes on degraded components and resume only after public plus private checks agree | manual override authority during partial outages |
| Evidence hygiene | status evidence should not expose credentials or balances | log URL, component, status label and timestamp only | retention policy for incident evidence |
| Claim boundary | status pages are not compensation, uptime SLA or execution guarantees | report status as operational context only | future postmortem details not yet published |
来源地图
- 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）
控制说明
1. Source class
这一项要求读者先把公开来源翻译成操作规则。这里的含义是：status pages, status APIs and venue announcements have different evidence strength。可执行动作是：record which class produced the maintenance or outage signal。仍然未知的是：whether a venue updates all channels at the same speed。因此本文不会把未知部分包装成收益承诺、牌照承诺、审批保证、恢复保证、结算保证、可用性保证、价格暗示或平台排名。
2. Component mapping
这里的含义是：API, website, mobile, deposit and withdrawal components can diverge。可执行动作是：map the component to the exact workflow before pausing or resuming。仍然未知的是：hidden dependencies not named as components。
操作测试也必须很窄。这就是本节保留边界的原因。
3. Maintenance window
这里的含义是：scheduled maintenance can start, end, extend or conclude earlier than expected。可执行动作是：store start, update and observed recovery timestamps。仍然未知的是：whether the service is stable after the public window ends。
操作测试也必须很窄。这就是本节保留边界的原因。
4. Account overlay
这里的含义是：public status does not prove private account eligibility。可执行动作是：run account-specific read-only checks after public recovery。仍然未知的是：regional, KYC, subaccount or symbol restrictions。
操作测试也必须很窄。这就是本节保留边界的原因。
5. Automation pause
这里的含义是：bots need deterministic stop and resume rules。可执行动作是：pause writes on degraded components and resume only after public plus private checks agree。仍然未知的是：manual override authority during partial outages。
操作测试也必须很窄。这就是本节保留边界的原因。
6. Evidence hygiene
这里的含义是：status evidence should not expose credentials or balances。可执行动作是：log URL, component, status label and timestamp only。仍然未知的是：retention policy for incident evidence。
操作测试也必须很窄。这就是本节保留边界的原因。
7. Claim boundary
这里的含义是：status pages are not compensation, uptime SLA or execution guarantees。可执行动作是：report status as operational context only。仍然未知的是：future postmortem details not yet published。
操作测试也必须很窄。这就是本节保留边界的原因。
仍需明确的未知项
- 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
实用结论
交易所状态页和状态 API 是有用的事故证据，但不能证明账户级执行、提现可用性或补偿结果。Coinbase 与 Kraken 提供 Statuspage API 文档，用于 summary、component、incident 与 maintenance 记录；OKX 发布状态页，并在 API guide 中说明 system-status 访问。实用结论是：在暂停或恢复自动化前，记录状态来源、component name、timestamp、maintenance window，并把账户检查单独处理。 本文停在证据边界内，帮助读者决定下一步核验什么，而不是把公开文档改写成私人账户、钱包、回调、政策框架、结算路径或流动性头寸在任何未来条件下都能成功的承诺。
相關專題與工具:交易所 API 與行情資料核查
來源與證據
04- Coinbase Status API
- Kraken Status API · status.kraken.com
- OKX Status · okx.com
- Get system status · okx.com