How to Verify Exchange Status Pages and Proof of Reserves

When an exchange freezes withdrawals, posts a “maintenance” notice, or publishes a proof‑of‑reserves report, the immediate question is: can I trust this information? The answer is rarely a simple yes or no. Status pages and reserve disclosures are useful, but they are not neutral verification tools. This review explains how to read them critically, where they fall short, and what steps you can take to verify claims before acting on them.

Exchange status pages (e.g., `status.binance.com`, `status.kraken.com`) are the first place users check during a withdrawal delay. They list ongoing incidents, scheduled maintenance, and resolved problems. For a reader trying to decide whether to wait or escalate, a status page provides a single source of truth—if the page is accurate and up to date.

The problem is that status pages are controlled by the same organization that could be experiencing a crisis. A delay may be caused by a security issue, a liquidity shortfall, or a technical failure, but the status page may only say “temporary maintenance.” In the past, exchanges have used vague language to mask internal problems. A status page alone is not enough; it must be cross‑checked.

Source-tracked CryptoRescue article.

• Timestamp and update history. Every entry should show when it was last updated. A page that hasn’t been updated in hours while users report ongoing issues is a red flag.
• Incident labels. Some status pages classify incidents as “monitoring,” “identified,” “resolved,” etc. If the page says “resolved” but withdrawals are still frozen, that discrepancy needs an explanation.
• API status. For advanced users, many exchanges expose a separate API status endpoint. Compare the web page with the API response if possible.
• Third‑party mirrors. Services like CoinGecko’s exchange status page aggregate live status from multiple exchanges. While not a primary source, they can reveal whether other users are reporting the same issue.

A status page that is transparent about the type of issue (e.g., “wallet maintenance” vs. “network congestion”) and provides regular updates is more trustworthy than one that uses generic one‑liners.

Proof of reserves (PoR) reports are designed to show that an exchange holds enough assets to cover customer balances. Exchanges like Binance and Kraken publish periodic PoR reports, often with Merkle‑tree snapshots that allow users to verify their own balances are included.

The catch is that a PoR report is a snapshot. It proves the exchange held certain assets at a specific moment, but it does not guarantee those assets are still there or that the exchange has not used them as collateral somewhere else. The methodology matters: a PoR that includes only the exchange’s own wallet addresses without full liability data is incomplete. Look for reports that include both asset and liability sides, and check whether the report is audited by a reputable third party.

Kraken’s PoR page, for example, provides a list of wallet addresses and a balance summary, but users must verify the addresses independently. Binance’s PoR uses a Merkle‑tree implementation that allows users to check their own balance. Neither approach is perfect, but both are better than no disclosure at all.

No single source should be trusted alone. For withdrawal claims, cross‑reference the exchange’s status page with:

• Social media and forums. Reddit, X (Twitter), and Telegram groups often have real‑time user reports. Look for multiple independent accounts of the same issue.
• Blockchain explorer. If the exchange uses a hot wallet for withdrawals, you can check the wallet’s on‑chain activity. A sudden drop in outgoing transactions may indicate a withdrawal freeze.
• Regulatory warnings. Check if the exchange has been flagged by a regulator (e.g., FCA, SEC, or MiCA bodies). A warning does not automatically mean a withdrawal freeze, but it raises the risk profile.
• Third‑party data aggregators. CoinGecko, CoinMarketCap, and Nansen provide exchange health indicators, but they rely on the same official status pages. Use them as a secondary check, not a primary source.

Source-tracked CryptoRescue article.

• No status page at all. Any exchange that handles withdrawals should have a public status page. Missing one is a major trust deficit.
• Status page offline during a crisis. If the page is unreachable or returns a generic error, that is often a deliberate choice.
• Proof of reserves without wallet addresses. A self‑report without verifiable on‑chain addresses is worthless.
• Vague language in incident descriptions. “We are experiencing issues” without specifying the nature or scope is not transparency.
• Demands for private keys or seed phrases. A legitimate exchange will never ask for your private keys. If a support channel asks for them, it is a scam—regardless of what the status page says.

No single source is foolproof. A status page, a proof of reserves report, and a regulator warning each tell part of the story. The responsible step is to collect all available pieces, compare them, and only then decide whether to trust a withdrawal claim or a support channel. When in doubt, wait for independent confirmation from multiple sources.