SODAX Status

Operational status

SODAX infrastructure

Liveness of SODAX-operated software, derived from backend health signals. Components without a backend-observable signal are marked Not monitored rather than assumed healthy.

Money market reserves

Current on-chain reserve inventory (Aave v3 on the Sonic hub). This is protocol config state, not liveness — reserves don't have “uptime.”

0 reserves listed

Per-reserve state (active / frozen / paused) and the deliberate-vs-incident distinction are not yet ingested by the backend — tracked as a gap. Until then, reserves are shown as listed only.

Networks

Supported chains and the assets configured on each. Each card leads with the solver-enabled count and then lists only the exceptions — tokens the solver currently has disabled. Tokens the solver feed doesn't list are counted separately rather than assumed enabled, and chains the feed doesn't cover at all carry no enablement signal.

Live per-network reachability (operational / paused / down) is not observable by the backend today (hub-only indexer, no spoke-chain RPC) — tracked as a gap. Per-reserve money-market state (active / frozen / paused) awaits backend ingestion (#912).

Active notices & recent history

✓ No incidents or maintenance reported in the last 90 days.

Operational Degraded / scheduled Incident Not monitored yet

Data source: SODAX backend read API (…). Backend … · ….
Operational status reflects only backend-observable infrastructure liveness. The availability map reflects protocol config state, not uptime. Uptime history, per-reserve state, per-network health, and a dedicated solver signal are tracked gaps. Notices below are operator-authored and served from this app's own store.