HerdCheckv0.6.7

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

WAX Testnet

f16b1833c747c43682f4386fca9cbb327929334a762755ebec17f6f23c9b8a12

https://api-testnet-wax.eosarabia.net

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

Producteur
eosarabianet
Historique de chaîne déclaré
Complet
Emplacement
Helsinki

Historique de disponibilité

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

0.0 % de disponibilité

3 mois

31 juil. 2026 UTCGris : aucun contrôle enregistréMaintenant

État actuel des services

Chain API

Hors service

No response within 5s. The server is down, overloaded, or a firewall is dropping connections.

Vérifié
Latence
—
Requêtes du navigateur
Bloquées
Version
Inconnue

Request never completed

Contrôles récents
Derniers contrôles de santé Chain API stockés.
ÉtatVersionRésuméLatenceCORSVérifié
Hors serviceInconnueNo response within 5s. The server is down, overloaded, or a firewall is dropping connections.—Bloquées
Hors serviceInconnueNo response within 5s. The server is down, overloaded, or a firewall is dropping connections.—Bloquées
Hors serviceInconnueNo response within 5s. The server is down, overloaded, or a firewall is dropping connections.—Bloquées
Hors serviceInconnueNo response within 5s. The server is down, overloaded, or a firewall is dropping connections.—Bloquées
Hors serviceInconnueNo response within 5s. The server is down, overloaded, or a firewall is dropping connections.—Bloquées
Hors serviceInconnueNo response within 5s. The server is down, overloaded, or a firewall is dropping connections.—Bloquées
Hors serviceInconnueNo response within 5s. The server is down, overloaded, or a firewall is dropping connections.—Bloquées
Hors serviceInconnueNo response within 5s. The server is down, overloaded, or a firewall is dropping connections.—Bloquées
Hors serviceInconnueNo response within 5s. The server is down, overloaded, or a firewall is dropping connections.—Bloquées
Hors serviceInconnueNo response within 5s. The server is down, overloaded, or a firewall is dropping connections.—Bloquées

Account Query

Hors service

No response within 5s. The server is down, overloaded, or a firewall is dropping connections.

Vérifié
Latence
—
Requêtes du navigateur
Bloquées
Version
Inconnue

Request never completed

Contrôles récents
Derniers contrôles de santé Account Query stockés.
ÉtatVersionRésuméLatenceCORSVérifié
Hors serviceInconnueNo response within 5s. The server is down, overloaded, or a firewall is dropping connections.—Bloquées
Hors serviceInconnueNo response within 5s. The server is down, overloaded, or a firewall is dropping connections.—Bloquées
Hors serviceInconnueNo response within 5s. The server is down, overloaded, or a firewall is dropping connections.—Bloquées
Hors serviceInconnueNo response within 5s. The server is down, overloaded, or a firewall is dropping connections.—Bloquées
Hors serviceInconnueNo response within 5s. The server is down, overloaded, or a firewall is dropping connections.—Bloquées
Hors serviceInconnueNo response within 5s. The server is down, overloaded, or a firewall is dropping connections.—Bloquées
Hors serviceInconnueNo response within 5s. The server is down, overloaded, or a firewall is dropping connections.—Bloquées
Hors serviceInconnueNo response within 5s. The server is down, overloaded, or a firewall is dropping connections.—Bloquées
Hors serviceInconnueNo response within 5s. The server is down, overloaded, or a firewall is dropping connections.—Bloquées
Hors serviceInconnueNo response within 5s. The server is down, overloaded, or a firewall is dropping connections.—Bloquées

History API

Invalide

HTTP 502 on /v1/history/get_actions instead of a valid history-v1 response. The server or its upstream node is failing. Check the node, the proxy and the server logs.

Vérifié
Latence
83 ms
Requêtes du navigateur
Bloquées
Version
Inconnue

Response Access-Control-Allow-Origin is missing. It must be "*" or echo the request Origin, otherwise browser apps cannot read the response.

Contrôles récents
Derniers contrôles de santé History API stockés.
ÉtatVersionRésuméLatenceCORSVérifié
InvalideInconnueHTTP 502 on /v1/history/get_actions instead of a valid history-v1 response. The server or its upstream node is failing. Check the node, the proxy and the server logs.83 msBloquées
InvalideInconnueHTTP 502 on /v1/history/get_actions instead of a valid history-v1 response. The server or its upstream node is failing. Check the node, the proxy and the server logs.127 msBloquées
InvalideInconnueHTTP 502 on /v1/history/get_actions instead of a valid history-v1 response. The server or its upstream node is failing. Check the node, the proxy and the server logs.71 msBloquées
InvalideInconnueHTTP 502 on /v1/history/get_actions instead of a valid history-v1 response. The server or its upstream node is failing. Check the node, the proxy and the server logs.94 msBloquées
InvalideInconnueHTTP 502 on /v1/history/get_actions instead of a valid history-v1 response. The server or its upstream node is failing. Check the node, the proxy and the server logs.89 msBloquées
InvalideInconnueHTTP 502 on /v1/history/get_actions instead of a valid history-v1 response. The server or its upstream node is failing. Check the node, the proxy and the server logs.241 msBloquées
InvalideInconnueHTTP 502 on /v1/history/get_actions instead of a valid history-v1 response. The server or its upstream node is failing. Check the node, the proxy and the server logs.70 msBloquées
InvalideInconnueHTTP 502 on /v1/history/get_actions instead of a valid history-v1 response. The server or its upstream node is failing. Check the node, the proxy and the server logs.247 msBloquées
InvalideInconnueHTTP 502 on /v1/history/get_actions instead of a valid history-v1 response. The server or its upstream node is failing. Check the node, the proxy and the server logs.165 msBloquées
InvalideInconnueHTTP 502 on /v1/history/get_actions instead of a valid history-v1 response. The server or its upstream node is failing. Check the node, the proxy and the server logs.155 msBloquées

Hyperion API

Invalide

HTTP 502 on /v2/health instead of a valid hyperion-v2 response. The server or its upstream node is failing. Check the node, the proxy and the server logs.

Vérifié
Latence
71 ms
Requêtes du navigateur
Bloquées
Version
Inconnue

Response Access-Control-Allow-Origin is missing. It must be "*" or echo the request Origin, otherwise browser apps cannot read the response.

Contrôles récents
Derniers contrôles de santé Hyperion API stockés.
ÉtatVersionRésuméLatenceCORSVérifié
InvalideInconnueHTTP 502 on /v2/health instead of a valid hyperion-v2 response. The server or its upstream node is failing. Check the node, the proxy and the server logs.71 msBloquées
InvalideInconnueHTTP 502 on /v2/health instead of a valid hyperion-v2 response. The server or its upstream node is failing. Check the node, the proxy and the server logs.91 msBloquées
InvalideInconnueHTTP 502 on /v2/health instead of a valid hyperion-v2 response. The server or its upstream node is failing. Check the node, the proxy and the server logs.72 msBloquées
InvalideInconnueHTTP 502 on /v2/health instead of a valid hyperion-v2 response. The server or its upstream node is failing. Check the node, the proxy and the server logs.70 msBloquées
InvalideInconnueHTTP 502 on /v2/health instead of a valid hyperion-v2 response. The server or its upstream node is failing. Check the node, the proxy and the server logs.71 msBloquées
InvalideInconnueHTTP 502 on /v2/health instead of a valid hyperion-v2 response. The server or its upstream node is failing. Check the node, the proxy and the server logs.239 msBloquées
InvalideInconnueHTTP 502 on /v2/health instead of a valid hyperion-v2 response. The server or its upstream node is failing. Check the node, the proxy and the server logs.70 msBloquées
InvalideInconnueHTTP 502 on /v2/health instead of a valid hyperion-v2 response. The server or its upstream node is failing. Check the node, the proxy and the server logs.192 msBloquées
InvalideInconnueHTTP 502 on /v2/health instead of a valid hyperion-v2 response. The server or its upstream node is failing. Check the node, the proxy and the server logs.130 msBloquées
InvalideInconnueHTTP 502 on /v2/health instead of a valid hyperion-v2 response. The server or its upstream node is failing. Check the node, the proxy and the server logs.137 msBloquées