HerdCheckv0.6.7

Saúde, status e histórico de nós Antelope para operadores e desenvolvedores.

Vaulta Mainnet

aca376f206b8fc25a6ed44dbdc66547c36c6c33e3a119ffbeaef943642f0e906

https://api.eos.detroitledger.tech

Saúde, atualidade, CORS e histórico recente de verificações deste endpoint.

Produtor
eosiodetroit
Histórico da cadeia declarado
Parcial
Localização
eos-api1-dlt

Histórico de disponibilidade

Verificações saudáveis e degradadas das funcionalidades monitorizadas. Os períodos sem dados são excluídos.

74.9% de disponibilidade

2 meses

31 de ago. de 2026 UTCCinzento: sem verificações registadasAgora

Estado atual dos serviços

Chain API

Saudável

Chain API responded normally

Verificado
Latência
373 ms
Pedidos do navegador
Permitidos
Versão
Spring v1.2.2
Verificações recentes
Últimas verificações de saúde de Chain API armazenadas.
StatusVersãoResumoLatênciaCORSVerificado
SaudávelSpring v1.2.2Chain API responded normally373 msPermitidos
SaudávelSpring v1.2.2Chain API responded normally362 msPermitidos
SaudávelSpring v1.2.2Chain API responded normally375 msPermitidos
SaudávelSpring v1.2.2Chain API responded normally356 msPermitidos
SaudávelSpring v1.2.2Chain API responded normally361 msPermitidos
SaudávelSpring v1.2.2Chain API responded normally361 msPermitidos
SaudávelSpring v1.2.2Chain API responded normally360 msPermitidos
SaudávelSpring v1.2.2Chain API responded normally368 msPermitidos
SaudávelSpring v1.2.2Chain API responded normally414 msPermitidos
SaudávelSpring v1.2.2Chain API responded normally361 msPermitidos

Account Query

Saudável

account-query responded normally

Verificado
Latência
510 ms
Pedidos do navegador
Permitidos
Versão
Spring v1.2.2
Verificações recentes
Últimas verificações de saúde de Account Query armazenadas.
StatusVersãoResumoLatênciaCORSVerificado
SaudávelSpring v1.2.2account-query responded normally510 msPermitidos
SaudávelSpring v1.2.2account-query responded normally509 msPermitidos
SaudávelSpring v1.2.2account-query responded normally515 msPermitidos
SaudávelSpring v1.2.2account-query responded normally497 msPermitidos
SaudávelSpring v1.2.2account-query responded normally504 msPermitidos
SaudávelSpring v1.2.2account-query responded normally503 msPermitidos
SaudávelSpring v1.2.2account-query responded normally460 msPermitidos
SaudávelSpring v1.2.2account-query responded normally512 msPermitidos
SaudávelSpring v1.2.2account-query responded normally632 msPermitidos
SaudávelSpring v1.2.2account-query responded normally479 msPermitidos

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.

Verificado
Latência
361 ms
Pedidos do navegador
Permitidos
Versão
Spring v1.2.2
Verificações recentes
Últimas verificações de saúde de History API armazenadas.
StatusVersãoResumoLatênciaCORSVerificado
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 msPermitidos
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 msPermitidos
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 msPermitidos
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 msPermitidos
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 msPermitidos
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 msPermitidos
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 msPermitidos
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 msPermitidos
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 msPermitidos
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 msPermitidos

AtomicAssets API

Não 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.

Verificado
Latência
528 ms
Pedidos do navegador
Permitidos
Versão
1.3.24
Verificações recentes
Últimas verificações de saúde de AtomicAssets API armazenadas.
StatusVersãoResumoLatênciaCORSVerificado
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 msPermitidos
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 msPermitidos
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 msPermitidos
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 msPermitidos
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 msPermitidos
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 msPermitidos
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 msPermitidos
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 msPermitidos
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 msPermitidos
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 msPermitidos