HerdCheckv0.6.7

Salud, estado e historial de nodos Antelope para operadores y desarrolladores.

Jungle Testnet

73e4385a2708e6d7048834fbc1079f2fabb17b3c125b146af438971e90716c4d

https://jungle.eosusa.io

Salud, frescura, CORS e historial reciente de comprobaciones de este endpoint.

Productor
ivote4eosusa
Historial de cadena declarado
Completo
Ubicación
Greenville,SC,USA

Historial de disponibilidad

Comprobaciones saludables y degradadas de las funciones supervisadas. Se excluyen los periodos sin datos.

49.8% de disponibilidad

14 días

16 oct 2026, 10 UTCGris: sin comprobaciones registradasAhora

Estado actual de los servicios

Chain API

Saludable

Chain API responded normally

Comprobado
Latencia
105 ms
Solicitudes del navegador
Permitidas
Versión
Spring v1.2.3-alpha1
Comprobaciones recientes
Últimas comprobaciones de salud de Chain API almacenadas.
EstadoVersiónResumenLatenciaCORSComprobado
SaludableSpring v1.2.3-alpha1Chain API responded normally105 msPermitidas
SaludableSpring v1.2.3-alpha1Chain API responded normally113 msPermitidas
SaludableSpring v1.2.3-alpha1Chain API responded normally108 msPermitidas
SaludableSpring v1.2.3-alpha1Chain API responded normally113 msPermitidas
SaludableSpring v1.2.3-alpha1Chain API responded normally112 msPermitidas
SaludableSpring v1.2.3-alpha1Chain API responded normally114 msPermitidas
SaludableSpring v1.2.3-alpha1Chain API responded normally113 msPermitidas
SaludableSpring v1.2.3-alpha1Chain API responded normally114 msPermitidas
SaludableSpring v1.2.3-alpha1Chain API responded normally347 msPermitidas
SaludableSpring v1.2.3-alpha1Chain API responded normally109 msPermitidas

Account Query

Saludable

account-query responded normally

Comprobado
Latencia
360 ms
Solicitudes del navegador
Permitidas
Versión
Spring v1.2.3-alpha1
Comprobaciones recientes
Últimas comprobaciones de salud de Account Query almacenadas.
EstadoVersiónResumenLatenciaCORSComprobado
SaludableSpring v1.2.3-alpha1account-query responded normally360 msPermitidas
SaludableSpring v1.2.3-alpha1account-query responded normally358 msPermitidas
SaludableSpring v1.2.3-alpha1account-query responded normally344 msPermitidas
SaludableSpring v1.2.3-alpha1account-query responded normally375 msPermitidas
SaludableSpring v1.2.3-alpha1account-query responded normally347 msPermitidas
SaludableSpring v1.2.3-alpha1account-query responded normally350 msPermitidas
SaludableSpring v1.2.3-alpha1account-query responded normally367 msPermitidas
SaludableSpring v1.2.3-alpha1account-query responded normally350 msPermitidas
SaludableSpring v1.2.3-alpha1account-query responded normally873 msPermitidas
SaludableSpring v1.2.3-alpha1account-query responded normally389 msPermitidas

History API

Inválido

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

Comprobado
Latencia
344 ms
Solicitudes del navegador
Bloqueadas
Versión
Spring v1.2.3-alpha1

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

Comprobaciones recientes
Últimas comprobaciones de salud de History API almacenadas.
EstadoVersiónResumenLatenciaCORSComprobado
InválidoSpring v1.2.3-alpha1HTTP 503 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.344 msBloqueadas
InválidoSpring v1.2.3-alpha1HTTP 503 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.328 msBloqueadas
InválidoSpring v1.2.3-alpha1HTTP 503 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.104 msBloqueadas
InválidoSpring v1.2.3-alpha1HTTP 503 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.328 msBloqueadas
InválidoSpring v1.2.3-alpha1HTTP 503 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.112 msBloqueadas
InválidoSpring v1.2.3-alpha1HTTP 503 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.111 msBloqueadas
InválidoSpring v1.2.3-alpha1HTTP 503 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.115 msBloqueadas
InválidoSpring v1.2.3-alpha1HTTP 503 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.112 msBloqueadas
InválidoSpring v1.2.3-alpha1HTTP 503 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.113 msBloqueadas
InválidoSpring v1.2.3-alpha1HTTP 503 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.339 msBloqueadas

Hyperion API

Inválido

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

Comprobado
Latencia
106 ms
Solicitudes del navegador
Bloqueadas
Versión
Desconocida

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

Comprobaciones recientes
Últimas comprobaciones de salud de Hyperion API almacenadas.
EstadoVersiónResumenLatenciaCORSComprobado
InválidoDesconocidaHTTP 503 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.106 msBloqueadas
InválidoDesconocidaHTTP 503 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.326 msBloqueadas
InválidoDesconocidaHTTP 503 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.323 msBloqueadas
InválidoDesconocidaHTTP 503 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.318 msBloqueadas
InválidoDesconocidaHTTP 503 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.327 msBloqueadas
InválidoDesconocidaHTTP 503 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.339 msBloqueadas
InválidoDesconocidaHTTP 503 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.365 msBloqueadas
InválidoDesconocidaHTTP 503 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.342 msBloqueadas
InválidoDesconocidaHTTP 503 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.317 msBloqueadas
InválidoDesconocidaHTTP 503 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.109 msBloqueadas