HerdCheckv0.6.7

Santé, état et historique des nœuds Antelope pour les opérateurs et les développeurs.

WAX Mainnet

1064487b3cd1a897ce03ae5b6a865651747e2e152090f99c1d19d44e01aea5a4

https://wax.eosrio.io

Santé, fraîcheur, CORS et historique récent des contrôles pour cet endpoint.

Producteur
eosriobrazil
Chaîne
WAX Mainnet
Historique de chaîne déclaré
Partiel
Emplacement
Rio de Janeiro

Historique de disponibilité

Contrôles sains et dégradés des fonctions surveillées. Les périodes sans données sont exclues.

48.3 % de disponibilité

1 an

31 oct. 2025 UTCGris : aucun contrôle enregistréMaintenant

État actuel des services

Chain API

Sain

Chain API responded normally

Vérifié
Latence
651 ms
Requêtes du navigateur
Autorisées
Version
Leap v5.0.3wax01
Contrôles récents
Derniers contrôles de santé Chain API stockés.
ÉtatVersionRésuméLatenceCORSVérifié
SainLeap v5.0.3wax01Chain API responded normally651 msAutorisées
SainLeap v5.0.3wax01Chain API responded normally620 msAutorisées
SainLeap v5.0.3wax01Chain API responded normally617 msAutorisées
SainLeap v5.0.3wax01Chain API responded normally609 msAutorisées
SainLeap v5.0.3wax01Chain API responded normally620 msAutorisées
SainLeap v5.0.3wax01Chain API responded normally618 msAutorisées
SainLeap v5.0.3wax01Chain API responded normally620 msAutorisées
SainLeap v5.0.3wax01Chain API responded normally607 msAutorisées
SainLeap v5.0.3wax01Chain API responded normally601 msAutorisées
SainLeap v5.0.3wax01Chain API responded normally625 msAutorisées

Account Query

Sain

account-query responded normally

Vérifié
Latence
669 ms
Requêtes du navigateur
Autorisées
Version
Leap v5.0.3wax01
Contrôles récents
Derniers contrôles de santé Account Query stockés.
ÉtatVersionRésuméLatenceCORSVérifié
SainLeap v5.0.3wax01account-query responded normally669 msAutorisées
SainLeap v5.0.3wax01account-query responded normally698 msAutorisées
SainLeap v5.0.3wax01account-query responded normally684 msAutorisées
SainLeap v5.0.3wax01account-query responded normally645 msAutorisées
SainLeap v5.0.3wax01account-query responded normally669 msAutorisées
SainLeap v5.0.3wax01account-query responded normally647 msAutorisées
SainLeap v5.0.3wax01account-query responded normally620 msAutorisées
SainLeap v5.0.3wax01account-query responded normally668 msAutorisées
SainLeap v5.0.3wax01account-query responded normally655 msAutorisées
SainLeap v5.0.3wax01account-query responded normally646 msAutorisées

History API

Invalide

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.

Vérifié
Latence
662 ms
Requêtes du navigateur
Autorisées
Version
Leap v5.0.3wax01
Contrôles récents
Derniers contrôles de santé History API stockés.
ÉtatVersionRésuméLatenceCORSVérifié
InvalideLeap 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 msAutorisées
InvalideLeap 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 msAutorisées
InvalideLeap 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 msAutorisées
InvalideLeap 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 msAutorisées
InvalideLeap 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 msAutorisées
InvalideLeap 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 msAutorisées
InvalideLeap 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 msAutorisées
InvalideLeap 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 msAutorisées
InvalideLeap 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 msAutorisées
InvalideLeap 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 msAutorisées

Hyperion API

Périmé

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

Vérifié
Latence
656 ms
Requêtes du navigateur
Autorisées
Version
3.5.0-5
Contrôles récents
Derniers contrôles de santé Hyperion API stockés.
ÉtatVersionRésuméLatenceCORSVérifié
Périmé3.5.0-5Indexer is 690461 blocks behind the chain head (limit 180). Check that it is keeping up with nodeos.656 msAutorisées
Périmé3.5.0-5Indexer is 688051 blocks behind the chain head (limit 180). Check that it is keeping up with nodeos.631 msAutorisées
Périmé3.5.0-5Indexer is 685638 blocks behind the chain head (limit 180). Check that it is keeping up with nodeos.608 msAutorisées
Périmé3.5.0-5Indexer is 683250 blocks behind the chain head (limit 180). Check that it is keeping up with nodeos.622 msAutorisées
Périmé3.5.0-5Indexer is 680850 blocks behind the chain head (limit 180). Check that it is keeping up with nodeos.627 msAutorisées
Périmé3.5.0-5Indexer is 678440 blocks behind the chain head (limit 180). Check that it is keeping up with nodeos.626 msAutorisées
Périmé3.5.0-5Indexer is 676040 blocks behind the chain head (limit 180). Check that it is keeping up with nodeos.606 msAutorisées
Périmé3.5.0-5Indexer is 673637 blocks behind the chain head (limit 180). Check that it is keeping up with nodeos.609 msAutorisées
Périmé3.5.0-5Indexer is 671251 blocks behind the chain head (limit 180). Check that it is keeping up with nodeos.613 msAutorisées
Périmé3.5.0-5Indexer is 668837 blocks behind the chain head (limit 180). Check that it is keeping up with nodeos.610 msAutorisées