Acurast Pulse

Loading live view

Syncing chain state, reward ledgers, and fleet telemetry.

Resolving route12%

Status | Acurast Pulse

Retained Tip Progress#3,235,768->#3,235,768

Block tip

#3,235,768

Retained lag

Indexed #3,235,768

Block time

Epoch

3,595

30% complete

Indexer lag

Services

Indexer

Block ingestion and event processing

Operational

Block ingestion current

Acurast parachain

Live chain RPC and block finality

Operational

Tip #3,235,768

Hyperbridge relay

Cross-chain message relay

Operational

Last activity 44m ago

Public API

REST endpoints for chain and fleet data

Unknown

No probe data yet

acurastpulse.com

Web frontend

Unknown

No probe data yet

Indexer backend

Subsquid processor

Operational

Block ingestion current

Archive shards

4 archive Postgres shards on home-box · refreshed 1103s ago

Shard	State	Rows	Max block	Last write	5m writes	1h writes	chain_blocks size
shard-a:55432	Stale	2,303,182	#2,345,400	19m ago	49	1,296	1.26 GB
shard-b:55434	Stale	237,949	#2,172,136	31d ago	0	0	128.6 MB
shard-c:55435	Stale	688,769	#2,860,617	15d ago	0	0	368.8 MB
shard-d:55436	Stale	453,880	#3,235,604	18m ago	299	1,805	375.6 MB

FAQ

What does retained lag mean?

Retained lag is the block distance between the latest finalized chain tip and the latest retained block the explorer has indexed and made queryable.

Why can services be healthy while retained lag is non-zero?

The API and frontend can stay responsive while the indexer catches up. Small lag is normal near tip; larger lag means fresh explorer data is delayed.

What do degraded and down mean here?

Degraded means data freshness or block production is slower than expected. Down means the chain, relay, or indexer is not updating reliably enough to trust near-tip data.