The operations desk, open to the public.
Real-time validator uptime, signed-block cadence, and regional RPC latency. Seeded from production telemetry, refreshed continuously. No login required.
Per-network uptime · last 30 days
12 of 50+ shownSigned-block cadence
A rolling window of the last 100 blocks on a representative mainnet. Violet cells are blocks our validators signed. Alert cells are misses, rare by design.
Regional RPC latency
Median and tail latency across our 12 regions, measured against public JSON-RPC endpoints. Numbers below are current-hour rolling averages.
| Region | Code | p50 | p95 | Status |
|---|---|---|---|---|
| US — West (Oregon) | us-west-2 | 34 | 71 | live |
| US — Central (Iowa) | us-central-1 | 29 | 62 | live |
| US — East (N. Virginia) | us-east-1 | 31 | 68 | live |
| SA — East (São Paulo) | sa-east-1 | 52 | 108 | live |
| EU — West (Ireland) | eu-west-1 | 33 | 70 | live |
| EU — Central (Frankfurt) | eu-central-1 | 28 | 59 | live |
| EU — North (Stockholm) | eu-north-1 | 41 | 84 | live |
| ME — Central (Dubai) | me-central-1 | 49 | 97 | live |
| AP — South (Mumbai) | ap-south-1 | 47 | 96 | live |
| AP — SE (Singapore) | ap-southeast-1 | 38 | 79 | live |
| AP — NE (Tokyo) | ap-northeast-1 | 42 | 88 | live |
| AP — Oceania (Sydney) | ap-southeast-2 | 44 | 91 | live |
Status page, answered.
Don't see your question? A named engineer replies within one business day.
Real-time validator uptime, signed-block cadence per network, regional RPC latency across 12 regions, and active incident count. All numbers come from production telemetry rather than synthetic checks, and refresh continuously without requiring a page reload.
Uptime equals signed_blocks divided by scheduled_blocks over a trailing 30-day window per network. The denominator counts every slot or block height where our validator was expected to participate. The numerator counts the slots we signed. Missed slots count against uptime regardless of cause, including network reorgs, peer-level connectivity issues, and our own incidents.
Yes. Active sev-1 incidents surface on the status page with affected networks and a timestamp. Resolved sev-1 incidents move to the post-mortem archive within 48 hours of resolution. Sev-2 and lower incidents do not surface on the public status page but are documented internally and available to counterparties on request.
No. The status page is fully public and indexable. We treat the operations data as a contractual claim that should be verifiable by counterparties, regulators, and prospective customers without gating.
All timestamps display in the viewer's local time zone, derived client-side from the browser. The underlying data is stored and transmitted in UTC. Hovering any timestamp reveals the UTC equivalent.
Validator block telemetry streams continuously, with the visible cadence rolling forward as new blocks confirm. RPC latency samples every 60 seconds from synthetic clients in each region. Uptime aggregates refresh every minute. The OpsDesk summary updates on a 5-second cadence.
Put your workload on infrastructure that's built to run it.
One conversation. A named engineer. A reply within one business day. No custody transfer. No lock-in.