Acurast Pulse
Loading live view
Loading the latest available information.
Loading page data…
Loading the latest available information.
A clear view of service health and data freshness.
Review the current notices below. Missing checks are never shown as healthy.
Connecting to live updatesCurrent observations and 30-day probe history.
Block ingestion and event processing
Chain progress and live RPC
Cross-chain message activity
Status endpoint for this page
This page in your browser
History refresh is delayed; showing the last available observations.
A status snapshot is not an uptime guarantee.
Worker update 1h ago
Historical bars use recorded website probes
Archive snapshot is 1h ago; current reachability is unverified.
Lag trend appears after three observations.
| Shard | Reachability | Latest stored block | Rows | Last write | Writes 5m / 1h | Stored blocks size |
|---|---|---|---|---|---|---|
| shard-a | Reachable | #2,345,402 | 2,345,401 | 92d ago | 0 / 0 | 1.28 GiB |
| shard-b | Reachable | #2,172,136 | 237,949 | 147d ago | 0 / 0 | 0.13 GiB |
| shard-c | Reachable | #4,764,409 | 2,606,254 | 4d ago | 0 / 0 | 1.36 GiB |
| shard-d | Reachable | #4,827,994 | 753,062 | 1h ago | 51 / 592 | 0.54 GiB |
No recent writes does not by itself mean an outage. A failed check leaves storage figures unverified.
The block distance between the observed chain tip and the latest block indexed for the explorer. Small gaps are normal. The API and website can remain responsive while the indexer catches up.
Successful recorded probes divided by all recorded probes for each service across the displayed UTC days. Missing observations stay gray and are excluded from the percentage. A partial day is calculated from its actual checks. Daily bars: green at 99% or above, amber from 90%, red below 90%. Latency covers successful probes. Current Status API and Website signals describe this page’s observed response, not every route or every visitor.
Recent requests can use the independent pruned node. Older state may require the archive; during an interruption, a request can show timestamped cached data or explicit temporary unavailability. Historical data must not be replaced with current state.