Review: how to read an exchange status page
Incidents are a product. This is a review of the public artifact — the status page — not a ranking of venues.
Dextape does not assign a venue a “trust score.” We assess whether a public status surface does its job. That job is to name the affected subsystem, the start time, the effect users can see (deposits, trading, withdrawals) and the time of the next update.
Pass and fail
- Pass: a timestamped incident with a list of affected components and a sentence a non-engineer can act on.
- Pass: updates at the promised times, ending with a note that says the incident is resolved and what users should check.
- Fail: an all-green grid with a banner that says “investigating” and a screenshot of a social-media post.
- Fail: a marketing blog post published as the only incident record.
Reading a status page during an outage
- Find the component that matches your problem: deposits, withdrawals, trading or a specific network.
- Note the start time, and whether the page says funds are affected or only access to them.
- Check whether deposits on a particular network are paused before sending more funds there.
- Wait for the next scheduled update rather than relying on social-media reports.
When we file a company note after an outage, we will link the status page we actually read. If we could not find one, we will say so.