Update rule
Degradation first
Customers should hear about slowed rails before a rail becomes a full outage.
AttnomSolutions
Loading page
Bringing in the next surface without the heavy transition shell.
Loading page
Bringing in the next surface without the heavy transition shell.
Customers get a clear service summary first, with detailed deposit, withdrawal, trading, KYC, and support health available beneath it.
Update rule
Customers should hear about slowed rails before a rail becomes a full outage.
Rail coverage
Deposits, withdrawals, matching, KYC processing, and support backlog are separated instead of flattened into one uptime block.
Trust model
Public messaging and raw rail detail are deliberately split so users can read the right layer quickly.
Customer-facing uptime, maintenance, degraded mode, and incident notices for the exchange route.
Market access, trust, and service updates in one system.
Update rule
Customers should hear about slowed rails before a rail becomes a full outage.
Rail coverage
Deposits, withdrawals, matching, KYC processing, and support backlog are separated instead of flattened into one uptime block.
Trust model
Public messaging and raw rail detail are deliberately split so users can read the right layer quickly.
Operator link
Customer communication, help routing, and operator escalation are wired together by design.
Markets, trust signals, and account entry.
Pairs, spreads, and launch coverage.
Verification standards and monitoring.
Account and wallet protections.
Support lanes and anti-scam guidance.
Service updates and incidents.
Trade, wallets, KYC, tax, and support.
Risk, treasury, and review link.
Update rules, rail coverage, and connections to support and operations.
Status signal
Update rule
Customers should hear about slowed rails before a rail becomes a full outage.
Status signal
Rail coverage
Deposits, withdrawals, matching, KYC processing, and support backlog are separated instead of flattened into one uptime block.
Status signal
Trust model
Public messaging and raw rail detail are deliberately split so users can read the right layer quickly.
Status signal
Operator link
Customer communication, help routing, and operator escalation are wired together by design.
Trust message
Status should start with what users can still do right now, then explain what is degraded or delayed.
Available actions + current delay + next update time
Trust message
Banking, chain, or third-party issues need plain-language summaries that explain impact without leaking sensitive internals.
Impact summary + workaround plan + escalation guidance
Trust message
If a user will likely need help after reading status, the next support option should already be obvious and issue-specific.
Status lane + help lane + operator owner
Rail health
Supported-chain credits and fiat intake remain within normal published windows.
Funding continues normally for most customers.
Rail health
New destinations, password resets, and unusual-device checks may add controlled review time.
Movement is available, but protection rules stay active.
Rail health
Spot market routing is online with extra watch on latency, spread expansion, and partner dependencies.
Orders remain available with tighter operational watch.
Rail health
Automated checks are flowing, while manual review queues remain visible when identity or device checks get more complex.
Onboarding stays gated but legible.
Rail health
Funding, account access, and fraud escalation routes remain staffed to absorb spikes or incident volume.
Priority lanes stay available under pressure.
Connected area
Support linkedStatus updates narrow the next support move rather than dumping users into a generic contact form.
Connected area
Ops linkedOperator ownership and public trust communication need to remain visibly connected during incidents.
Connected area
Product linkedCustomer modules should remain readable even when one rail is degraded, paused, or operating under contingency rules.
Status updates should be posted for material degradation, not only for full outages.
Partner-related incidents need customer-facing summaries without exposing sensitive internals.
Maintenance windows should be announced before trading, funding, or withdrawal changes are applied.
Security incidents require controlled communication paths tied to the incident-response plan.