Cronos RPC Status
Live health and block heights for curated public Cronos Mainnet RPC endpoints.
Response times are measured from Silex infrastructure.
Cronos Mainnet
Collecting network observations
- Chain ID
- 25 (0x19)
- Currency
- CRO
- Observed
- Waiting for data
- Monitored RPCs
- 5
- Healthy
- 0
- Degraded
- 0
- Behind
- 0
- Down
- 0
Public RPC endpoints
Read-only observations from lightweight eth_chainId and eth_blockNumber checks.
Loading current status…
Loading RPC observations…
How Silex classifies an RPC
Healthy means the endpoint returned chain ID 25, joined the current block consensus, stayed within three blocks of the derived head, and responded within 1.5 seconds.
Degraded means the endpoint works but is slow, four to eleven blocks behind, or outside the trusted block cluster. Behind means it is at least twelve blocks behind. Transport failures, timeouts, malformed responses, and wrong-chain responses are Down. Unknown is used when trustworthy comparison data is not yet sufficient or has gone stale.
- Reference head
- Highest block in a majority cluster whose observations are within 12 blocks.
- Check cadence
- Every 5 minutes, with two providers checked concurrently.
- Timeout
- 5 seconds per endpoint, with no automatic retries.
- 24h uptime
- Valid chain-and-block responses divided by completed checks; shown after 12 checks spanning at least 55 minutes.