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.

75.0% de disponibilidad

1 mes

1 oct 2026 UTCGris: sin comprobaciones registradasAhora

Estado actual de los servicios

Chain API

Saludable

Chain API responded normally

Comprobado
Latencia
355 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 normally355 msPermitidas
SaludableSpring v1.2.2Chain API responded normally402 msPermitidas
SaludableSpring v1.2.2Chain API responded normally360 msPermitidas
SaludableSpring v1.2.2Chain API responded normally363 msPermitidas
SaludableSpring v1.2.2Chain API responded normally360 msPermitidas
SaludableSpring v1.2.2Chain API responded normally359 msPermitidas
SaludableSpring v1.2.2Chain API responded normally362 msPermitidas
SaludableSpring v1.2.2Chain API responded normally358 msPermitidas
SaludableSpring v1.2.2Chain API responded normally358 msPermitidas
SaludableSpring v1.2.2Chain API responded normally361 msPermitidas

Account Query

Saludable

account-query responded normally

Comprobado
Latencia
504 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 normally504 msPermitidas
SaludableSpring v1.2.2account-query responded normally505 msPermitidas
SaludableSpring v1.2.2account-query responded normally498 msPermitidas
SaludableSpring v1.2.2account-query responded normally505 msPermitidas
SaludableSpring v1.2.2account-query responded normally500 msPermitidas
SaludableSpring v1.2.2account-query responded normally468 msPermitidas
SaludableSpring v1.2.2account-query responded normally496 msPermitidas
SaludableSpring v1.2.2account-query responded normally512 msPermitidas
SaludableSpring v1.2.2account-query responded normally504 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
269 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.269 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.363 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.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.371 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
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.366 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.359 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
494 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.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.527 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.530 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.491 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.508 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.504 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.547 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.537 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.482 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