The network, live.

Every number on this page is read from the coordinator, which recomputes it every 60 seconds from the same records the operator dashboard uses. Nothing here is typed in by hand. The raw feed is coordinator.obsideo.io/network, public JSON, no key needed.

Could not reach the coordinator from your browser. The feed at coordinator.obsideo.io/network may still answer directly; if it does not, the coordinator itself is down and /health will say so.
…
active storage providers · … failure domains
…
objects under contract
…
logical data · … on disk with replicas
3×
replication target, every object
…
merkle proofs passed, last cycle · …
…
fleet capacity · … used
4 h
proof cadence · every object, every cycle
…
coordinator version · refreshed …

Loading live figures from the coordinator

A replica counts as live only if its provider is active and has heartbeated in the last 10 minutes; "on disk with replicas" is logical data multiplied by the live copies actually held. Objects under contract are objects the network holds today.

Storage providers

nodefailure domainpathroleheartbeat
loading…

Rows are numbered in registration order and carry no identity: which operator runs a node, where it is, how big it is and what it runs are the operator's business, not the public's. A letter marks a failure domain, so two nodes with the same letter share a facility. "direct" nodes terminate TLS themselves on a public address; "tunneled" nodes sit behind a relay and take secondary replicas only. Per-node proof pass rates are not published. Providers earn only for proofs they pass.

Refresh cadence 60 s on the coordinator, 60 s in this page. Aggregates only: the feed carries no account names, no object keys and no key material, and it is computed on a timer rather than per request, so nobody can use it to make the coordinator walk the object table on demand. Last generated: ….