HerdCheckv0.6.7

Antelope node health, status, and history for operators and developers.

WAX Mainnet

1064487b3cd1a897ce03ae5b6a865651747e2e152090f99c1d19d44e01aea5a4

https://wax.eosrio.io

Health, freshness, CORS, and recent check history for this endpoint.

Producer
eosriobrazil
Chain
WAX Mainnet
Reported chain history
Partial
Location
Rio de Janeiro

Uptime history

Healthy and degraded checks across monitored features. Gaps are excluded from uptime.

50.0% uptime

3 days

27 Oct 2026, 05 UTCGray: no recorded checksNow

Current service health

Chain API

Healthy

Chain API responded normally

Checked
Latency
620 ms
Browser requests
Allowed
Version
Leap v5.0.3wax01
Recent checks
Latest stored Chain API health checks.
StatusVersionSummaryLatencyCORSChecked
HealthyLeap v5.0.3wax01Chain API responded normally620 msAllowed
HealthyLeap v5.0.3wax01Chain API responded normally618 msAllowed
HealthyLeap v5.0.3wax01Chain API responded normally620 msAllowed
HealthyLeap v5.0.3wax01Chain API responded normally607 msAllowed
HealthyLeap v5.0.3wax01Chain API responded normally601 msAllowed
HealthyLeap v5.0.3wax01Chain API responded normally625 msAllowed
HealthyLeap v5.0.3wax01Chain API responded normally624 msAllowed
HealthyLeap v5.0.3wax01Chain API responded normally705 msAllowed
HealthyLeap v5.0.3wax01Chain API responded normally620 msAllowed
HealthyLeap v5.0.3wax01Chain API responded normally614 msAllowed

Account Query

Healthy

account-query responded normally

Checked
Latency
669 ms
Browser requests
Allowed
Version
Leap v5.0.3wax01
Recent checks
Latest stored Account Query health checks.
StatusVersionSummaryLatencyCORSChecked
HealthyLeap v5.0.3wax01account-query responded normally669 msAllowed
HealthyLeap v5.0.3wax01account-query responded normally647 msAllowed
HealthyLeap v5.0.3wax01account-query responded normally620 msAllowed
HealthyLeap v5.0.3wax01account-query responded normally668 msAllowed
HealthyLeap v5.0.3wax01account-query responded normally655 msAllowed
HealthyLeap v5.0.3wax01account-query responded normally646 msAllowed
HealthyLeap v5.0.3wax01account-query responded normally665 msAllowed
HealthyLeap v5.0.3wax01account-query responded normally810 msAllowed
HealthyLeap v5.0.3wax01account-query responded normally644 msAllowed
HealthyLeap v5.0.3wax01account-query responded normally681 msAllowed

History API

Invalid

HTTP 404 on /v1/history/get_actions. The server has no route for this history-v1 check, so the advertised feature is not actually served. Fix the proxy routing or remove the feature from bp.json.

Checked
Latency
615 ms
Browser requests
Allowed
Version
Leap v5.0.3wax01
Recent checks
Latest stored History API health checks.
StatusVersionSummaryLatencyCORSChecked
InvalidLeap v5.0.3wax01HTTP 404 on /v1/history/get_actions. The server has no route for this history-v1 check, so the advertised feature is not actually served. Fix the proxy routing or remove the feature from bp.json.615 msAllowed
InvalidLeap v5.0.3wax01HTTP 404 on /v1/history/get_actions. The server has no route for this history-v1 check, so the advertised feature is not actually served. Fix the proxy routing or remove the feature from bp.json.610 msAllowed
InvalidLeap v5.0.3wax01HTTP 404 on /v1/history/get_actions. The server has no route for this history-v1 check, so the advertised feature is not actually served. Fix the proxy routing or remove the feature from bp.json.606 msAllowed
InvalidLeap v5.0.3wax01HTTP 404 on /v1/history/get_actions. The server has no route for this history-v1 check, so the advertised feature is not actually served. Fix the proxy routing or remove the feature from bp.json.635 msAllowed
InvalidLeap v5.0.3wax01HTTP 404 on /v1/history/get_actions. The server has no route for this history-v1 check, so the advertised feature is not actually served. Fix the proxy routing or remove the feature from bp.json.637 msAllowed
InvalidLeap v5.0.3wax01HTTP 404 on /v1/history/get_actions. The server has no route for this history-v1 check, so the advertised feature is not actually served. Fix the proxy routing or remove the feature from bp.json.628 msAllowed
InvalidLeap v5.0.3wax01HTTP 404 on /v1/history/get_actions. The server has no route for this history-v1 check, so the advertised feature is not actually served. Fix the proxy routing or remove the feature from bp.json.645 msAllowed
InvalidLeap v5.0.3wax01HTTP 404 on /v1/history/get_actions. The server has no route for this history-v1 check, so the advertised feature is not actually served. Fix the proxy routing or remove the feature from bp.json.608 msAllowed
InvalidLeap v5.0.3wax01HTTP 404 on /v1/history/get_actions. The server has no route for this history-v1 check, so the advertised feature is not actually served. Fix the proxy routing or remove the feature from bp.json.635 msAllowed
InvalidLeap v5.0.3wax01HTTP 404 on /v1/history/get_actions. The server has no route for this history-v1 check, so the advertised feature is not actually served. Fix the proxy routing or remove the feature from bp.json.628 msAllowed

Hyperion API

Stale

Indexer is 680850 blocks behind the chain head (limit 180). Check that it is keeping up with nodeos.

Checked
Latency
627 ms
Browser requests
Allowed
Version
3.5.0-5
Recent checks
Latest stored Hyperion API health checks.
StatusVersionSummaryLatencyCORSChecked
Stale3.5.0-5Indexer is 680850 blocks behind the chain head (limit 180). Check that it is keeping up with nodeos.627 msAllowed
Stale3.5.0-5Indexer is 678440 blocks behind the chain head (limit 180). Check that it is keeping up with nodeos.626 msAllowed
Stale3.5.0-5Indexer is 676040 blocks behind the chain head (limit 180). Check that it is keeping up with nodeos.606 msAllowed
Stale3.5.0-5Indexer is 673637 blocks behind the chain head (limit 180). Check that it is keeping up with nodeos.609 msAllowed
Stale3.5.0-5Indexer is 671251 blocks behind the chain head (limit 180). Check that it is keeping up with nodeos.613 msAllowed
Stale3.5.0-5Indexer is 668837 blocks behind the chain head (limit 180). Check that it is keeping up with nodeos.610 msAllowed
Stale3.5.0-5Indexer is 666450 blocks behind the chain head (limit 180). Check that it is keeping up with nodeos.633 msAllowed
Stale3.5.0-5Indexer is 664051 blocks behind the chain head (limit 180). Check that it is keeping up with nodeos.657 msAllowed
Stale3.5.0-5Indexer is 661640 blocks behind the chain head (limit 180). Check that it is keeping up with nodeos.607 msAllowed
Stale3.5.0-5Indexer is 659237 blocks behind the chain head (limit 180). Check that it is keeping up with nodeos.628 msAllowed