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.

52.5 % de disponibilité

1 mois

1 oct. 2026 UTCGris : aucun contrôle enregistréMaintenant

État actuel des services

Chain API

Sain

Chain API responded normally

Vérifié
Latence
619 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 normally619 msAutorisées
SainLeap v5.0.3wax01Chain API responded normally623 msAutorisées
SainLeap v5.0.3wax01Chain API responded normally595 msAutorisées
SainLeap v5.0.3wax01Chain API responded normally626 msAutorisées
SainLeap v5.0.3wax01Chain API responded normally598 msAutorisées
SainLeap v5.0.3wax01Chain API responded normally613 msAutorisées
SainLeap v5.0.3wax01Chain API responded normally628 msAutorisées
SainLeap v5.0.3wax01Chain API responded normally596 msAutorisées
SainLeap v5.0.3wax01Chain API responded normally623 msAutorisées
SainLeap v5.0.3wax01Chain API responded normally620 msAutorisées

Account Query

Sain

account-query responded normally

Vérifié
Latence
689 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 normally689 msAutorisées
SainLeap v5.0.3wax01account-query responded normally642 msAutorisées
SainLeap v5.0.3wax01account-query responded normally693 msAutorisées
SainLeap v5.0.3wax01account-query responded normally666 msAutorisées
SainLeap v5.0.3wax01account-query responded normally653 msAutorisées
SainLeap v5.0.3wax01account-query responded normally623 msAutorisées
SainLeap v5.0.3wax01account-query responded normally1698 msAutorisées
SainLeap v5.0.3wax01account-query responded normally675 msAutorisées
SainLeap v5.0.3wax01account-query responded normally675 msAutorisées
SainLeap v5.0.3wax01account-query responded normally888 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
612 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.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.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.633 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.636 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.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.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.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.604 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.624 msAutorisées

Hyperion API

Périmé

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

Vérifié
Latence
616 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 724040 blocks behind the chain head (limit 180). Check that it is keeping up with nodeos.616 msAutorisées
Périmé3.5.0-5Indexer is 721650 blocks behind the chain head (limit 180). Check that it is keeping up with nodeos.640 msAutorisées
Périmé3.5.0-5Indexer is 719251 blocks behind the chain head (limit 180). Check that it is keeping up with nodeos.671 msAutorisées
Périmé3.5.0-5Indexer is 716852 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 714437 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 712051 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 709640 blocks behind the chain head (limit 180). Check that it is keeping up with nodeos.610 msAutorisées
Périmé3.5.0-5Indexer is 707240 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 704850 blocks behind the chain head (limit 180). Check that it is keeping up with nodeos.635 msAutorisées
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