Mainnet Explorer Sync

Monitors the Explorer v2 (Callisto/Hasura) sync status by querying the latest indexed block via GraphQL and comparing against the actual chain head from the EVM RPC. Detects Callisto indexer stalls, PostgreSQL issues, or chain node disconnections. A lag of >100 blocks triggers DOWN status. This is the early warning system for explorer data staleness.

Down

Environment

prod

Response Time

Average

0ms

Min

0ms

Max

0ms

p99

0ms

Uptime History

2 checks agoNow

Direct Links

Troubleshooting

Possible causes:

BullMQ blockSync job stuck in active state— Fix: SSH to server, clear queue: docker exec <backend> node -e "...Queue('blockSync')...obliterate()..."; restart workers
PM2 sync process crashed— Fix: Check PM2 logs: docker exec <pm2> pm2 logs --lines 50; restart: docker compose restart pm2
EVM indexer disabled on chain node— Fix: Set enable-indexer = true in app.toml, restart node, run: intgd index-eth-tx backward && intgd index-eth-tx forward
Workers disconnected from Redis/RPC— Fix: docker compose restart high_priority_worker medium_priority_worker low_priority_worker
Missing DB columns causing silent INSERT failures— Fix: Run migration: docker exec <backend> npx sequelize-cli db:migrate

Dependencies

Depends on Required by