HerdCheckv0.6.7

Saúde, status e histórico de nós Antelope para operadores e desenvolvedores.

WAX Mainnet

1064487b3cd1a897ce03ae5b6a865651747e2e152090f99c1d19d44e01aea5a4

https://wax.eosrio.io

Saúde, atualidade, CORS e histórico recente de verificações deste endpoint.

Produtor
eosriobrazil
Cadeia
WAX Mainnet
Histórico da cadeia declarado
Parcial
Localização
Rio de Janeiro

Histórico de disponibilidade

Verificações saudáveis e degradadas das funcionalidades monitorizadas. Os períodos sem dados são excluídos.

50.0% de disponibilidade

3 meses

31 de jul. de 2026 UTCCinzento: sem verificações registadasAgora

Estado atual dos serviços

Chain API

Saudável

Chain API responded normally

Verificado
Latência
620 ms
Pedidos do navegador
Permitidos
Versão
Leap v5.0.3wax01
Verificações recentes
Últimas verificações de saúde de Chain API armazenadas.
StatusVersãoResumoLatênciaCORSVerificado
SaudávelLeap v5.0.3wax01Chain API responded normally620 msPermitidos
SaudávelLeap v5.0.3wax01Chain API responded normally617 msPermitidos
SaudávelLeap v5.0.3wax01Chain API responded normally609 msPermitidos
SaudávelLeap v5.0.3wax01Chain API responded normally620 msPermitidos
SaudávelLeap v5.0.3wax01Chain API responded normally618 msPermitidos
SaudávelLeap v5.0.3wax01Chain API responded normally620 msPermitidos
SaudávelLeap v5.0.3wax01Chain API responded normally607 msPermitidos
SaudávelLeap v5.0.3wax01Chain API responded normally601 msPermitidos
SaudávelLeap v5.0.3wax01Chain API responded normally625 msPermitidos
SaudávelLeap v5.0.3wax01Chain API responded normally624 msPermitidos

Account Query

Saudável

account-query responded normally

Verificado
Latência
698 ms
Pedidos do navegador
Permitidos
Versão
Leap v5.0.3wax01
Verificações recentes
Últimas verificações de saúde de Account Query armazenadas.
StatusVersãoResumoLatênciaCORSVerificado
SaudávelLeap v5.0.3wax01account-query responded normally698 msPermitidos
SaudávelLeap v5.0.3wax01account-query responded normally684 msPermitidos
SaudávelLeap v5.0.3wax01account-query responded normally645 msPermitidos
SaudávelLeap v5.0.3wax01account-query responded normally669 msPermitidos
SaudávelLeap v5.0.3wax01account-query responded normally647 msPermitidos
SaudávelLeap v5.0.3wax01account-query responded normally620 msPermitidos
SaudávelLeap v5.0.3wax01account-query responded normally668 msPermitidos
SaudávelLeap v5.0.3wax01account-query responded normally655 msPermitidos
SaudávelLeap v5.0.3wax01account-query responded normally646 msPermitidos
SaudávelLeap v5.0.3wax01account-query responded normally665 msPermitidos

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.

Verificado
Latência
628 ms
Pedidos do navegador
Permitidos
Versão
Leap v5.0.3wax01
Verificações recentes
Últimas verificações de saúde de History API armazenadas.
StatusVersãoResumoLatênciaCORSVerificado
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 msPermitidos
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 msPermitidos
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 msPermitidos
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 msPermitidos
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 msPermitidos
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 msPermitidos
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 msPermitidos
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 msPermitidos
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 msPermitidos
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.645 msPermitidos

Hyperion API

Desatualizado

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

Verificado
Latência
631 ms
Pedidos do navegador
Permitidos
Versão
3.5.0-5
Verificações recentes
Últimas verificações de saúde de Hyperion API armazenadas.
StatusVersãoResumoLatênciaCORSVerificado
Desatualizado3.5.0-5Indexer is 688051 blocks behind the chain head (limit 180). Check that it is keeping up with nodeos.631 msPermitidos
Desatualizado3.5.0-5Indexer is 685638 blocks behind the chain head (limit 180). Check that it is keeping up with nodeos.608 msPermitidos
Desatualizado3.5.0-5Indexer is 683250 blocks behind the chain head (limit 180). Check that it is keeping up with nodeos.622 msPermitidos
Desatualizado3.5.0-5Indexer is 680850 blocks behind the chain head (limit 180). Check that it is keeping up with nodeos.627 msPermitidos
Desatualizado3.5.0-5Indexer is 678440 blocks behind the chain head (limit 180). Check that it is keeping up with nodeos.626 msPermitidos
Desatualizado3.5.0-5Indexer is 676040 blocks behind the chain head (limit 180). Check that it is keeping up with nodeos.606 msPermitidos
Desatualizado3.5.0-5Indexer is 673637 blocks behind the chain head (limit 180). Check that it is keeping up with nodeos.609 msPermitidos
Desatualizado3.5.0-5Indexer is 671251 blocks behind the chain head (limit 180). Check that it is keeping up with nodeos.613 msPermitidos
Desatualizado3.5.0-5Indexer is 668837 blocks behind the chain head (limit 180). Check that it is keeping up with nodeos.610 msPermitidos
Desatualizado3.5.0-5Indexer is 666450 blocks behind the chain head (limit 180). Check that it is keeping up with nodeos.633 msPermitidos