源头核验研究

交易所状态页事故披露雷达

4 分钟

已验证事实边界

1. OKX Status describes itself as a hub for system information, maintenance information, issue descriptions and deposit/withdrawal status. 2. Kraken Status is the public status page for Kraken Digital Asset Exchange and lists component status and incidents. 3. Kraken publishes API documentation for programmatic access to status page elements. 4. Coinbase publishes a consumer status page with incidents and component information. 5. Coinbase Exchange publishes a separate status page for Coinbase Exchange services.

收起完整分析

决策矩阵

文章表格:可横向滑动,或聚焦表格区域后使用方向键。

CheckWhat it meansPractical actionUnknown to keep explicit
Affected servicewhich product or component is degradedmatch the status item to the user's actionunlisted dependency
Affected assetwhich token, chain or funding rail is namedavoid assuming all assets are affectedasset-specific recovery
Incident stateinvestigating, identified, monitoring, resolved or maintenancewait for the correct state before retryingstate lag
Timestampwhen the update was posted and in which timezonerecord the latest timestamplate updates
Maintenance windowscheduled start and completion scopeavoid trading or transfer actions inside windowoverrun risk
Component scopeweb, app, API, WebSocket, custody or fundingseparate UI outage from API or funding outageshared infrastructure
Retry rulewhen a user should retry an actionretry only after relevant component recoveryprivate account restrictions
API evidencemachine-readable status datause API only as supporting evidenceAPI caching
Evidence packetofficial URL, checked date, service, asset and statedo not publish account screenshots or balancesprivacy retention
Stop rulewhen radar should remain unknownstop if the page does not name service, asset, state or timefuture page redesign

来源地图

  • 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)

控制说明

1. Affected service

这一项要求读者先把公开来源翻译成操作规则。这里的含义是:which product or component is degraded。可执行动作是:match the status item to the user's action。仍然未知的是:unlisted dependency。因此本文不会把未知部分包装成安全承诺、收益承诺、官方背书、审批保证、可用性保证或注册诱导。

2. Affected asset

这里的含义是:which token, chain or funding rail is named。可执行动作是:avoid assuming all assets are affected。仍然未知的是:asset-specific recovery。

3. Incident state

这里的含义是:investigating, identified, monitoring, resolved or maintenance。可执行动作是:wait for the correct state before retrying。仍然未知的是:state lag。

4. Timestamp

这里的含义是:when the update was posted and in which timezone。可执行动作是:record the latest timestamp。仍然未知的是:late updates。

5. Maintenance window

这里的含义是:scheduled start and completion scope。可执行动作是:avoid trading or transfer actions inside window。仍然未知的是:overrun risk。

6. Component scope

这里的含义是:web, app, API, WebSocket, custody or funding。可执行动作是:separate UI outage from API or funding outage。仍然未知的是:shared infrastructure。

7. Retry rule

这里的含义是:when a user should retry an action。可执行动作是:retry only after relevant component recovery。仍然未知的是:private account restrictions。

8. API evidence

这里的含义是:machine-readable status data。可执行动作是:use API only as supporting evidence。仍然未知的是:API caching。

9. Evidence packet

这里的含义是:official URL, checked date, service, asset and state。可执行动作是:do not publish account screenshots or balances。仍然未知的是:privacy retention。

10. Stop rule

这里的含义是:when radar should remain unknown。可执行动作是:stop if the page does not name service, asset, state or time。仍然未知的是:future page redesign。

仍需明确的未知项

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

实用结论

本文最有价值的地方是克制。NexuAlpha Radar 将交易所状态页评分为运营披露工具,而不是信任徽章。OKX Status 称其展示系统维护信息、问题描述以及充提状态。Kraken Status 是 Kraken Digital Asset Exchange 的公开状态页,并提供组件状态、历史事故和 API 文档。Coinbase 发布面向消费者和 Coinbase Exchange 的状态页,展示事故和组件信息。有用的雷达问题是:在用户重试入金、提现、API 订单或账户动作之前,状态页是否说明受影响服务、资产或网络、当前状态、时间戳、维护窗口、组件范围和下一次更新路径。 用户应获得一个更清楚的核验路径,而不是一个看似肯定、实则无法由公开证据承担的承诺。

来源与证据

05
  1. OKXOKX Status · okx.com
  2. KrakenKraken Status · status.kraken.com
  3. KrakenKraken Status API · status.kraken.com
  4. CoinbaseCoinbase Status
  5. CoinbaseCoinbase Exchange Status