HerdCheckv0.6.7

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

Vaulta Mainnet

aca376f206b8fc25a6ed44dbdc66547c36c6c33e3a119ffbeaef943642f0e906

https://api.eos.detroitledger.tech

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

Productor
eosiodetroit
Historial de cadena declarado
Parcial
Ubicación
eos-api1-dlt

Historial de disponibilidad

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

74.7% de disponibilidad

6 meses

1 may 2026 UTCGris: sin comprobaciones registradasAhora

Estado actual de los servicios

Chain API

Saludable

Chain API responded normally

Comprobado
Latencia
401 ms
Solicitudes del navegador
Permitidas
Versión
Spring v1.2.2
Comprobaciones recientes
Últimas comprobaciones de salud de Chain API almacenadas.
EstadoVersiónResumenLatenciaCORSComprobado
SaludableSpring v1.2.2Chain API responded normally401 msPermitidas
SaludableSpring v1.2.2Chain API responded normally359 msPermitidas
SaludableSpring v1.2.2Chain API responded normally361 msPermitidas
SaludableSpring v1.2.2Chain API responded normally401 msPermitidas
SaludableSpring v1.2.2Chain API responded normally397 msPermitidas
SaludableSpring v1.2.2Chain API responded normally363 msPermitidas
SaludableSpring v1.2.2Chain API responded normally373 msPermitidas
SaludableSpring v1.2.2Chain API responded normally362 msPermitidas
SaludableSpring v1.2.2Chain API responded normally375 msPermitidas
SaludableSpring v1.2.2Chain API responded normally356 msPermitidas

Account Query

Saludable

account-query responded normally

Comprobado
Latencia
508 ms
Solicitudes del navegador
Permitidas
Versión
Spring v1.2.2
Comprobaciones recientes
Últimas comprobaciones de salud de Account Query almacenadas.
EstadoVersiónResumenLatenciaCORSComprobado
SaludableSpring v1.2.2account-query responded normally508 msPermitidas
SaludableSpring v1.2.2account-query responded normally491 msPermitidas
SaludableSpring v1.2.2account-query responded normally487 msPermitidas
SaludableSpring v1.2.2account-query responded normally526 msPermitidas
SaludableSpring v1.2.2account-query responded normally524 msPermitidas
SaludableSpring v1.2.2account-query responded normally490 msPermitidas
SaludableSpring v1.2.2account-query responded normally510 msPermitidas
SaludableSpring v1.2.2account-query responded normally509 msPermitidas
SaludableSpring v1.2.2account-query responded normally515 msPermitidas
SaludableSpring v1.2.2account-query responded normally497 msPermitidas

History API

Inválido

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.

Comprobado
Latencia
350 ms
Solicitudes del navegador
Permitidas
Versión
Spring v1.2.2
Comprobaciones recientes
Últimas comprobaciones de salud de History API almacenadas.
EstadoVersiónResumenLatenciaCORSComprobado
InválidoSpring v1.2.2HTTP 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.350 msPermitidas
InválidoSpring v1.2.2HTTP 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.360 msPermitidas
InválidoSpring v1.2.2HTTP 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.354 msPermitidas
InválidoSpring v1.2.2HTTP 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.356 msPermitidas
InválidoSpring v1.2.2HTTP 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.395 msPermitidas
InválidoSpring v1.2.2HTTP 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.360 msPermitidas
InválidoSpring v1.2.2HTTP 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.361 msPermitidas
InválidoSpring v1.2.2HTTP 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.360 msPermitidas
InválidoSpring v1.2.2HTTP 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.368 msPermitidas
InválidoSpring v1.2.2HTTP 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.354 msPermitidas

AtomicAssets API

No declaradoDegradado

Atomic API modules unavailable: /atomictools/v1/config not found (HTTP 404/405). Enable the atomicassets, atomicmarket and atomictools namespaces and expose them through the proxy.

Comprobado
Latencia
528 ms
Solicitudes del navegador
Permitidas
Versión
1.3.24
Comprobaciones recientes
Últimas comprobaciones de salud de AtomicAssets API almacenadas.
EstadoVersiónResumenLatenciaCORSComprobado
Degradado1.3.24Atomic API modules unavailable: /atomictools/v1/config not found (HTTP 404/405). Enable the atomicassets, atomicmarket and atomictools namespaces and expose them through the proxy.528 msPermitidas
Degradado1.3.24Atomic API modules unavailable: /atomictools/v1/config not found (HTTP 404/405). Enable the atomicassets, atomicmarket and atomictools namespaces and expose them through the proxy.506 msPermitidas
Degradado1.3.24Atomic API modules unavailable: /atomictools/v1/config not found (HTTP 404/405). Enable the atomicassets, atomicmarket and atomictools namespaces and expose them through the proxy.518 msPermitidas
Degradado1.3.24Atomic API modules unavailable: /atomictools/v1/config not found (HTTP 404/405). Enable the atomicassets, atomicmarket and atomictools namespaces and expose them through the proxy.549 msPermitidas
Degradado1.3.24Atomic API modules unavailable: /atomictools/v1/config not found (HTTP 404/405). Enable the atomicassets, atomicmarket and atomictools namespaces and expose them through the proxy.539 msPermitidas
Degradado1.3.24Atomic API modules unavailable: /atomictools/v1/config not found (HTTP 404/405). Enable the atomicassets, atomicmarket and atomictools namespaces and expose them through the proxy.489 msPermitidas
Degradado1.3.24Atomic API modules unavailable: /atomictools/v1/config not found (HTTP 404/405). Enable the atomicassets, atomicmarket and atomictools namespaces and expose them through the proxy.528 msPermitidas
Degradado1.3.24Atomic API modules unavailable: /atomictools/v1/config not found (HTTP 404/405). Enable the atomicassets, atomicmarket and atomictools namespaces and expose them through the proxy.518 msPermitidas
Degradado1.3.24Atomic API modules unavailable: /atomictools/v1/config not found (HTTP 404/405). Enable the atomicassets, atomicmarket and atomictools namespaces and expose them through the proxy.538 msPermitidas
Degradado1.3.24Atomic API modules unavailable: /atomictools/v1/config not found (HTTP 404/405). Enable the atomicassets, atomicmarket and atomictools namespaces and expose them through the proxy.479 msPermitidas