Acurast Pulse

Loading live view

Syncing chain state, reward ledgers, and fleet telemetry.

Resolving route12%

Retained Tip Progress#3,137,421->#3,137,421

Block tip

#3,137,421

Retained lag

Indexed #3,137,421

Block time

Epoch

3,486

2% complete

Indexer lag

11s

Services

Indexer

Block ingestion and event processing

Operational

Block ingestion current

Acurast parachain

Live chain RPC and block finality

Operational

Tip #3,137,421

Hyperbridge relay

Cross-chain message relay

Operational

Last activity 11m 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 5s ago

Shard	State	Rows	Max block	Last write	5m writes	1h writes	chain_blocks size
shard-a:55432	OK	2,058,214	#2,345,400	6s ago	142	1,619	1.18 GB
shard-b:55434	Stale	237,949	#2,172,136	24d ago	0	0	128.6 MB
shard-c:55435	Stale	688,769	#2,860,617	8d ago	0	0	368.8 MB
shard-d:55436	OK	451,001	#3,137,421	10s ago	50	1,000	372.2 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.

Status | Acurast Pulse