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.

52.5% uptime

1 month

1 Oct 2026 UTCGray: no recorded checksNow

Current service health

Chain API

Healthy

Chain API responded normally

Checked
Latency
705 ms
Browser requests
Allowed
Version
Leap v5.0.3wax01
Recent checks
Latest stored Chain API health checks.
StatusVersionSummaryLatencyCORSChecked
HealthyLeap v5.0.3wax01Chain API responded normally705 msAllowed
HealthyLeap v5.0.3wax01Chain API responded normally620 msAllowed
HealthyLeap v5.0.3wax01Chain API responded normally614 msAllowed
HealthyLeap v5.0.3wax01Chain API responded normally624 msAllowed
HealthyLeap v5.0.3wax01Chain API responded normally626 msAllowed
HealthyLeap v5.0.3wax01Chain API responded normally617 msAllowed
HealthyLeap v5.0.3wax01Chain API responded normally628 msAllowed
HealthyLeap v5.0.3wax01Chain API responded normally622 msAllowed
HealthyLeap v5.0.3wax01Chain API responded normally689 msAllowed
HealthyLeap v5.0.3wax01Chain API responded normally591 msAllowed

Account Query

Healthy

account-query responded normally

Checked
Latency
810 ms
Browser requests
Allowed
Version
Leap v5.0.3wax01
Recent checks
Latest stored Account Query health checks.
StatusVersionSummaryLatencyCORSChecked
HealthyLeap v5.0.3wax01account-query responded normally810 msAllowed
HealthyLeap v5.0.3wax01account-query responded normally644 msAllowed
HealthyLeap v5.0.3wax01account-query responded normally681 msAllowed
HealthyLeap v5.0.3wax01account-query responded normally649 msAllowed
HealthyLeap v5.0.3wax01account-query responded normally663 msAllowed
HealthyLeap v5.0.3wax01account-query responded normally672 msAllowed
HealthyLeap v5.0.3wax01account-query responded normally720 msAllowed
HealthyLeap v5.0.3wax01account-query responded normally656 msAllowed
HealthyLeap v5.0.3wax01account-query responded normally683 msAllowed
HealthyLeap v5.0.3wax01account-query responded normally641 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
608 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.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
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.631 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.631 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.633 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.607 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.639 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.648 msAllowed

Hyperion API

Stale

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

Checked
Latency
657 ms
Browser requests
Allowed
Version
3.5.0-5
Recent checks
Latest stored Hyperion API health checks.
StatusVersionSummaryLatencyCORSChecked
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
Stale3.5.0-5Indexer is 656850 blocks behind the chain head (limit 180). Check that it is keeping up with nodeos.634 msAllowed
Stale3.5.0-5Indexer is 654438 blocks behind the chain head (limit 180). Check that it is keeping up with nodeos.631 msAllowed
Stale3.5.0-5Indexer is 652094 blocks behind the chain head (limit 180). Check that it is keeping up with nodeos.630 msAllowed
Stale3.5.0-5Indexer is 649698 blocks behind the chain head (limit 180). Check that it is keeping up with nodeos.637 msAllowed
Stale3.5.0-5Indexer is 647299 blocks behind the chain head (limit 180). Check that it is keeping up with nodeos.636 msAllowed
Stale3.5.0-5Indexer is 644898 blocks behind the chain head (limit 180). Check that it is keeping up with nodeos.608 msAllowed
Stale3.5.0-5Indexer is 642485 blocks behind the chain head (limit 180). Check that it is keeping up with nodeos.607 msAllowed