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
Cadena
Vaulta Mainnet
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.9% de disponibilidad

2 meses

31 ago 2026 UTCGris: sin comprobaciones registradasAhora

Estado actual de los servicios

Chain API

Saludable

Chain API responded normally

Comprobado
Latencia
373 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 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
SaludableSpring v1.2.2Chain API responded normally361 msPermitidas
SaludableSpring v1.2.2Chain API responded normally361 msPermitidas
SaludableSpring v1.2.2Chain API responded normally360 msPermitidas
SaludableSpring v1.2.2Chain API responded normally368 msPermitidas
SaludableSpring v1.2.2Chain API responded normally414 msPermitidas
SaludableSpring v1.2.2Chain API responded normally361 msPermitidas

Account Query

Saludable

account-query responded normally

Comprobado
Latencia
510 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 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
SaludableSpring v1.2.2account-query responded normally504 msPermitidas
SaludableSpring v1.2.2account-query responded normally503 msPermitidas
SaludableSpring v1.2.2account-query responded normally460 msPermitidas
SaludableSpring v1.2.2account-query responded normally512 msPermitidas
SaludableSpring v1.2.2account-query responded normally632 msPermitidas
SaludableSpring v1.2.2account-query responded normally479 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
361 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.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
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.359 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.266 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.358 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.369 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.362 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.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
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.494 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.493 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.483 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.487 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.623 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.509 msPermitidas