connecting to the coordinator
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.
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
| provider | failure domain | path | role | capacity | used | fill | last heartbeat | version |
|---|---|---|---|---|---|---|---|---|
| loading… | ||||||||
Provider ids are the first eight characters of the coordinator's id, the same handle the operator tools use. "direct" providers terminate TLS themselves on a public address; "tunneled" providers sit behind a relay and are used for secondary replicas only. Per-provider proof pass rates are not published: rates vary by node and publishing them per node is a claim we have chosen not to make in public. 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: ….