HerdCheckv0.6.7

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

Vaulta Mainnet

aca376f206b8fc25a6ed44dbdc66547c36c6c33e3a119ffbeaef943642f0e906

https://filter.eoseco.com

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

Producteur
eosecoeoseco
Historique de chaîne déclaré
Partiel
Emplacement
Tokyo

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é

1 an

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

État actuel des services

Chain API

Hors service

Connection was closed by the server (ECONNRESET). Check the proxy and server logs.

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 serviceInconnueConnection was closed by the server (ECONNRESET). Check the proxy and server logs.—Bloquées
Hors serviceInconnueConnection was closed by the server (ECONNRESET). Check the proxy and server logs.—Bloquées
InvalideInconnueHTTP 404 on /v1/chain/get_info. The server has no route for this chain-api check, so the advertised feature is not actually served. Fix the proxy routing or remove the feature from bp.json.243 msBloquées
Hors serviceInconnueConnection was closed by the server (ECONNRESET). Check the proxy and server logs.—Bloquées
Hors serviceInconnueConnection was closed by the server (ECONNRESET). Check the proxy and server logs.—Bloquées
InvalideInconnueHTTP 404 on /v1/chain/get_info. The server has no route for this chain-api check, so the advertised feature is not actually served. Fix the proxy routing or remove the feature from bp.json.242 msBloquées
Hors serviceInconnueConnection was closed by the server (ECONNRESET). Check the proxy and server logs.—Bloquées
Hors serviceInconnueConnection was closed by the server (ECONNRESET). Check the proxy and server logs.—Bloquées
Hors serviceInconnueConnection was closed by the server (ECONNRESET). Check the proxy and server logs.—Bloquées
InvalideInconnueHTTP 404 on /v1/chain/get_info. The server has no route for this chain-api check, so the advertised feature is not actually served. Fix the proxy routing or remove the feature from bp.json.235 msBloquées
Hors serviceInconnueConnection was closed by the server (ECONNRESET). Check the proxy and server logs.—Bloquées
InvalideInconnueHTTP 404 on /v1/chain/get_info. The server has no route for this chain-api check, so the advertised feature is not actually served. Fix the proxy routing or remove the feature from bp.json.491 msBloquées
InvalideInconnueHTTP 404 on /v1/chain/get_info. The server has no route for this chain-api check, so the advertised feature is not actually served. Fix the proxy routing or remove the feature from bp.json.234 msBloquées
Hors serviceInconnueConnection was closed by the server (ECONNRESET). Check the proxy and server logs.—Bloquées
Hors serviceInconnueConnection was closed by the server (ECONNRESET). Check the proxy and server logs.—Bloquées
InvalideInconnueHTTP 404 on /v1/chain/get_info. The server has no route for this chain-api check, so the advertised feature is not actually served. Fix the proxy routing or remove the feature from bp.json.240 msBloquées
InvalideInconnueHTTP 404 on /v1/chain/get_info. The server has no route for this chain-api check, so the advertised feature is not actually served. Fix the proxy routing or remove the feature from bp.json.241 msBloquées
InvalideInconnueHTTP 404 on /v1/chain/get_info. The server has no route for this chain-api check, so the advertised feature is not actually served. Fix the proxy routing or remove the feature from bp.json.645 msBloquées
InvalideInconnueHTTP 404 on /v1/chain/get_info. The server has no route for this chain-api check, so the advertised feature is not actually served. Fix the proxy routing or remove the feature from bp.json.586 msBloquées
Hors serviceInconnueConnection was closed by the server (ECONNRESET). Check the proxy and server logs.—Bloquées
InvalideInconnueHTTP 404 on /v1/chain/get_info. The server has no route for this chain-api check, so the advertised feature is not actually served. Fix the proxy routing or remove the feature from bp.json.237 msBloquées
Hors serviceInconnueConnection was closed by the server (ECONNRESET). Check the proxy and server logs.—Bloquées
InvalideInconnueHTTP 404 on /v1/chain/get_info. The server has no route for this chain-api check, so the advertised feature is not actually served. Fix the proxy routing or remove the feature from bp.json.237 msBloquées
InvalideInconnueHTTP 404 on /v1/chain/get_info. The server has no route for this chain-api check, so the advertised feature is not actually served. Fix the proxy routing or remove the feature from bp.json.236 msBloquées
InvalideInconnueHTTP 404 on /v1/chain/get_info. The server has no route for this chain-api check, so the advertised feature is not actually served. Fix the proxy routing or remove the feature from bp.json.544 msBloquées
Hors serviceInconnueConnection was closed by the server (ECONNRESET). Check the proxy and server logs.—Bloquées
InvalideInconnueHTTP 404 on /v1/chain/get_info. The server has no route for this chain-api check, so the advertised feature is not actually served. Fix the proxy routing or remove the feature from bp.json.235 msBloquées
InvalideInconnueHTTP 404 on /v1/chain/get_info. The server has no route for this chain-api check, so the advertised feature is not actually served. Fix the proxy routing or remove the feature from bp.json.235 msBloquées
InvalideInconnueHTTP 404 on /v1/chain/get_info. The server has no route for this chain-api check, so the advertised feature is not actually served. Fix the proxy routing or remove the feature from bp.json.235 msBloquées
Hors serviceInconnueConnection was closed by the server (ECONNRESET). Check the proxy and server logs.—Bloquées
Hors serviceInconnueConnection was closed by the server (ECONNRESET). Check the proxy and server logs.—Bloquées
InvalideInconnueHTTP 404 on /v1/chain/get_info. The server has no route for this chain-api check, so the advertised feature is not actually served. Fix the proxy routing or remove the feature from bp.json.537 msBloquées
Hors serviceInconnueConnection was closed by the server (ECONNRESET). Check the proxy and server logs.—Bloquées
Hors serviceInconnueConnection was closed by the server (ECONNRESET). Check the proxy and server logs.—Bloquées
InvalideInconnueHTTP 404 on /v1/chain/get_info. The server has no route for this chain-api check, so the advertised feature is not actually served. Fix the proxy routing or remove the feature from bp.json.357 msBloquées
Hors serviceInconnueConnection was closed by the server (ECONNRESET). Check the proxy and server logs.—Bloquées
Hors serviceInconnueConnection was closed by the server (ECONNRESET). Check the proxy and server logs.—Bloquées
Hors serviceInconnueConnection was closed by the server (ECONNRESET). Check the proxy and server logs.—Bloquées
InvalideInconnueHTTP 404 on /v1/chain/get_info. The server has no route for this chain-api check, so the advertised feature is not actually served. Fix the proxy routing or remove the feature from bp.json.541 msBloquées
InvalideInconnueHTTP 404 on /v1/chain/get_info. The server has no route for this chain-api check, so the advertised feature is not actually served. Fix the proxy routing or remove the feature from bp.json.234 msBloquées