Aere Network · live status
Status you compute yourself.
Most status pages show you a green dot their operator painted. Every check below runs in your browser, right now, against the real public endpoints: if something is down, no one can paint over it.
Method: JSON-RPC endpoints are asked for the chain head and judged on answering with a well-formed block number; the Cloud API is judged on its health route; WebSocket is judged on a real subscription handshake. Latency is measured from your device, so it includes your own network path.
Chain 2800
…chain head, read live
…seconds per block, measured over 10 blocks
…validators in the live QBFT set
…Falcon seals on the latest PQ anchor
Public endpoints
Availability, measured every minute
The checks above are yours, right now. The history below is ours: every minute the AERE site host calls the same endpoints through the public edge, on the path a client uses, and keeps the answers. Availability is the share of successful probes in the window; latency is p50 and p95 over the successful probes of the last 24 hours; an incident is at least two consecutive failed probes. Raw feed:
/cloud-status.json. The served copy can lag the prober by up to five minutes; if the feed is older than ten minutes this section says so instead of showing stale figures.
Loading the measured history…
Anything red? It is either genuinely down or blocked on your network path: try the same check from another connection, then tell us: [email protected]. The live checks have no server-side component to fail independently of what they measure; the measured history does (our prober), and says when it is stale.