Acurast Pulse

Loading live view

Syncing chain state, reward ledgers, and fleet telemetry.

Resolving route12%

Status | Acurast Pulse

Retained Tip Progress#3,749,502->#3,749,502

Block tip

#3,749,502

Retained lag

Indexed #3,749,502

Block time

Epoch

4,166

11% complete

Indexer lag

203s

Services

Indexer

Block ingestion and event processing

Operational

Block ingestion current

Acurast parachain

Live chain RPC and block finality

Operational

Tip #3,749,502

Hyperbridge relay

Cross-chain message relay

Down

Relay offline

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 17530s ago

Shard	State	Rows	Max block	Last write	5m writes	1h writes	chain_blocks size
shard-a:55432	Stale	2,345,401	#2,345,402	13d ago	0	0	1.28 GB
shard-b:55434	Stale	237,949	#2,172,136	69d ago	0	0	128.6 MB
shard-c:55435	Stale	1,155,863	#3,420,109	5h ago	0	13	621.9 MB
shard-d:55436	Stale	635,336	#3,746,667	5h ago	50	584	402.9 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.