Testnet Chain Freshness

Polls the testnet CometBFT RPC /status endpoint every minute, comparing sync_info.latest_block_time to wall-clock now. Goes DEGRADED at 5 minutes of staleness, DOWN (and pages on Telegram via the 2-consecutive-failure flow) at 30 minutes. This is the canonical signal that explorer.testnet is showing live-but-stale data.

Operational

Environment

dev

Response Time

Average

67ms

Min

13ms

Max

399ms

p99

390ms

Uptime History

120 checks agoNow

Direct Links

Troubleshooting

Possible causes:

Validator set has no active producer (jailed, offline, or paused)— Fix: SSH into the testnet validator host; check `intgd query staking validators`; unjail if needed: `intgd tx slashing unjail` (testnet keys)
Genuine consensus halt — quorum lost— Fix: Review CometBFT logs on the gateway: `journalctl -u intgd -n 200`. Restart the daemon if peers can't be reached.
RPC reachable but lying about timestamp (clock skew)— Fix: Compare blockHeight here vs testnet-cosmos-rpc — if heights match but ages differ, the host clock is wrong; sync NTP.

Dependencies

Depends on Required by