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
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.

50.8 % de disponibilité

2 mois

31 août 2026 UTCGris : aucun contrôle enregistréMaintenant

État actuel des services

Chain API

Sain

Chain API responded normally

Vérifié
Latence
620 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 normally620 msAutorisées
SainLeap v5.0.3wax01Chain API responded normally616 msAutorisées
SainLeap v5.0.3wax01Chain API responded normally621 msAutorisées
SainLeap v5.0.3wax01Chain API responded normally621 msAutorisées
SainLeap v5.0.3wax01Chain API responded normally618 msAutorisées
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

Account Query

Sain

account-query responded normally

Vérifié
Latence
888 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 normally888 msAutorisées
SainLeap v5.0.3wax01account-query responded normally687 msAutorisées
SainLeap v5.0.3wax01account-query responded normally634 msAutorisées
SainLeap v5.0.3wax01account-query responded normally652 msAutorisées
SainLeap v5.0.3wax01account-query responded normally650 msAutorisées
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

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
624 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.624 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.631 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.612 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.608 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.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

Hyperion API

Périmé

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

Vérifié
Latence
627 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 702437 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 700038 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 697650 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 695238 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 692840 blocks behind the chain head (limit 180). Check that it is keeping up with nodeos.601 msAutorisées
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