HerdCheckv0.6.7

Salud, estado e historial de nodos Antelope para operadores y desarrolladores.

WAX Mainnet

1064487b3cd1a897ce03ae5b6a865651747e2e152090f99c1d19d44e01aea5a4

https://wax.eosrio.io

Salud, frescura, CORS e historial reciente de comprobaciones de este endpoint.

Productor
eosriobrazil
Cadena
WAX Mainnet
Historial de cadena declarado
Parcial
Ubicación
Rio de Janeiro

Historial de disponibilidad

Comprobaciones saludables y degradadas de las funciones supervisadas. Se excluyen los periodos sin datos.

50.8% de disponibilidad

2 meses

31 ago 2026 UTCGris: sin comprobaciones registradasAhora

Estado actual de los servicios

Chain API

Saludable

Chain API responded normally

Comprobado
Latencia
651 ms
Solicitudes del navegador
Permitidas
Versión
Leap v5.0.3wax01
Comprobaciones recientes
Últimas comprobaciones de salud de Chain API almacenadas.
EstadoVersiónResumenLatenciaCORSComprobado
SaludableLeap v5.0.3wax01Chain API responded normally651 msPermitidas
SaludableLeap v5.0.3wax01Chain API responded normally620 msPermitidas
SaludableLeap v5.0.3wax01Chain API responded normally617 msPermitidas
SaludableLeap v5.0.3wax01Chain API responded normally609 msPermitidas
SaludableLeap v5.0.3wax01Chain API responded normally620 msPermitidas
SaludableLeap v5.0.3wax01Chain API responded normally618 msPermitidas
SaludableLeap v5.0.3wax01Chain API responded normally620 msPermitidas
SaludableLeap v5.0.3wax01Chain API responded normally607 msPermitidas
SaludableLeap v5.0.3wax01Chain API responded normally601 msPermitidas
SaludableLeap v5.0.3wax01Chain API responded normally625 msPermitidas

Account Query

Saludable

account-query responded normally

Comprobado
Latencia
669 ms
Solicitudes del navegador
Permitidas
Versión
Leap v5.0.3wax01
Comprobaciones recientes
Últimas comprobaciones de salud de Account Query almacenadas.
EstadoVersiónResumenLatenciaCORSComprobado
SaludableLeap v5.0.3wax01account-query responded normally669 msPermitidas
SaludableLeap v5.0.3wax01account-query responded normally698 msPermitidas
SaludableLeap v5.0.3wax01account-query responded normally684 msPermitidas
SaludableLeap v5.0.3wax01account-query responded normally645 msPermitidas
SaludableLeap v5.0.3wax01account-query responded normally669 msPermitidas
SaludableLeap v5.0.3wax01account-query responded normally647 msPermitidas
SaludableLeap v5.0.3wax01account-query responded normally620 msPermitidas
SaludableLeap v5.0.3wax01account-query responded normally668 msPermitidas
SaludableLeap v5.0.3wax01account-query responded normally655 msPermitidas
SaludableLeap v5.0.3wax01account-query responded normally646 msPermitidas

History API

Inválido

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.

Comprobado
Latencia
662 ms
Solicitudes del navegador
Permitidas
Versión
Leap v5.0.3wax01
Comprobaciones recientes
Últimas comprobaciones de salud de History API almacenadas.
EstadoVersiónResumenLatenciaCORSComprobado
InválidoLeap 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.662 msPermitidas
InválidoLeap 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 msPermitidas
InválidoLeap 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.619 msPermitidas
InválidoLeap 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.632 msPermitidas
InválidoLeap 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 msPermitidas
InválidoLeap 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 msPermitidas
InválidoLeap 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 msPermitidas
InválidoLeap 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 msPermitidas
InválidoLeap 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 msPermitidas
InválidoLeap 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 msPermitidas

Hyperion API

Obsoleto

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

Comprobado
Latencia
656 ms
Solicitudes del navegador
Permitidas
Versión
3.5.0-5
Comprobaciones recientes
Últimas comprobaciones de salud de Hyperion API almacenadas.
EstadoVersiónResumenLatenciaCORSComprobado
Obsoleto3.5.0-5Indexer is 690461 blocks behind the chain head (limit 180). Check that it is keeping up with nodeos.656 msPermitidas
Obsoleto3.5.0-5Indexer is 688051 blocks behind the chain head (limit 180). Check that it is keeping up with nodeos.631 msPermitidas
Obsoleto3.5.0-5Indexer is 685638 blocks behind the chain head (limit 180). Check that it is keeping up with nodeos.608 msPermitidas
Obsoleto3.5.0-5Indexer is 683250 blocks behind the chain head (limit 180). Check that it is keeping up with nodeos.622 msPermitidas
Obsoleto3.5.0-5Indexer is 680850 blocks behind the chain head (limit 180). Check that it is keeping up with nodeos.627 msPermitidas
Obsoleto3.5.0-5Indexer is 678440 blocks behind the chain head (limit 180). Check that it is keeping up with nodeos.626 msPermitidas
Obsoleto3.5.0-5Indexer is 676040 blocks behind the chain head (limit 180). Check that it is keeping up with nodeos.606 msPermitidas
Obsoleto3.5.0-5Indexer is 673637 blocks behind the chain head (limit 180). Check that it is keeping up with nodeos.609 msPermitidas
Obsoleto3.5.0-5Indexer is 671251 blocks behind the chain head (limit 180). Check that it is keeping up with nodeos.613 msPermitidas
Obsoleto3.5.0-5Indexer is 668837 blocks behind the chain head (limit 180). Check that it is keeping up with nodeos.610 msPermitidas