Deriving overall status from live probes…
Component breakdown
Live state pill + adaptive bar (width = real recorded uptime, color follows status, flashes when degraded/down) + per-day timestamped history grid (hover a day for its status breakdown). History is recorded by the status-probe automation.
RPC node status
Live probe of the RPC edge per network. The edge is Cloudflare anycast (one endpoint serves US/EU/ASIA); latency is the real round-trip from your location.
| Network | Region | Endpoint | Status | Latency |
|---|
Live signal log
Real probe results captured this session (client-side). There is no historical uptime store yet, so no synthetic history is shown.
network.json (aggregated from CLRTY_SUBSTRATE/boot/*.json — the same manifests clrty-api serves). Sensitive material (treasury, entropy, entity maps, custody) is excluded by design.
Chain identity
RPC surface
Security posture
Monetization
Sanity (PoS²)
Networks / chainlist
RPC methods
| Method | Group | Params |
|---|
Products suite
| ID | Product | Category | Status |
|---|
Platform sections
| ID | Slug | Group | Function |
|---|
CLRTY SCOPE — Network Monitor (canonical Cyber HUD) — open full screen · ledger HUD: monitor /browser (not the Clarity Wallet browser).
Clarity Browser
Consumer wallet and exchange browser on exchange.clarity-fintech.com —
not the Network Monitor UI. CLARITY.STATUS links out; no monitor iframe here.
Network telemetry: CLRTY SCOPE monitor · live probes: Status tab