HerdCheckv0.6.7

面向运营者与开发者的 Antelope 节点健康、状态与历史监控。

Jungle Testnet

73e4385a2708e6d7048834fbc1079f2fabb17b3c125b146af438971e90716c4d

https://jungle.eosusa.io

此端点的健康、新鲜度、CORS 与近期检查历史。

出块节点
ivote4eosusa
声明的链历史
完整
位置
Greenville,SC,USA

可用性历史

所有监控功能中健康和降级检查的比例。无数据时段不计入可用性。

可用性 49.8%

3天

2026年10月27日 7时 UTC灰色:无检查记录现在

当前服务健康

Chain API

正常

Chain API responded normally

检查时间
延迟
107 毫秒
浏览器请求
允许
版本
Spring v1.2.3-alpha1
近期检查
最新存储的 Chain API 健康检查。
状态版本摘要延迟CORS检查时间
正常Spring v1.2.3-alpha1Chain API responded normally107 毫秒允许
正常Spring v1.2.3-alpha1Chain API responded normally111 毫秒允许
正常Spring v1.2.3-alpha1Chain API responded normally101 毫秒允许
正常Spring v1.2.3-alpha1Chain API responded normally111 毫秒允许
正常Spring v1.2.3-alpha1Chain API responded normally113 毫秒允许
正常Spring v1.2.3-alpha1Chain API responded normally107 毫秒允许
正常Spring v1.2.3-alpha1Chain API responded normally109 毫秒允许
正常Spring v1.2.3-alpha1Chain API responded normally105 毫秒允许
正常Spring v1.2.3-alpha1Chain API responded normally110 毫秒允许
正常Spring v1.2.3-alpha1Chain API responded normally110 毫秒允许

Account Query

正常

account-query responded normally

检查时间
延迟
449 毫秒
浏览器请求
允许
版本
Spring v1.2.3-alpha1
近期检查
最新存储的 Account Query 健康检查。
状态版本摘要延迟CORS检查时间
正常Spring v1.2.3-alpha1account-query responded normally449 毫秒允许
正常Spring v1.2.3-alpha1account-query responded normally369 毫秒允许
正常Spring v1.2.3-alpha1account-query responded normally346 毫秒允许
正常Spring v1.2.3-alpha1account-query responded normally366 毫秒允许
正常Spring v1.2.3-alpha1account-query responded normally364 毫秒允许
正常Spring v1.2.3-alpha1account-query responded normally335 毫秒允许
正常Spring v1.2.3-alpha1account-query responded normally357 毫秒允许
正常Spring v1.2.3-alpha1account-query responded normally362 毫秒允许
正常Spring v1.2.3-alpha1account-query responded normally370 毫秒允许
正常Spring v1.2.3-alpha1account-query responded normally349 毫秒允许

History API

无效

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.

检查时间
延迟
105 毫秒
浏览器请求
阻止
版本
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.

近期检查
最新存储的 History API 健康检查。
状态版本摘要延迟CORS检查时间
无效Spring 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.105 毫秒阻止
无效Spring 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.318 毫秒阻止
无效Spring 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.337 毫秒阻止
无效Spring 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.320 毫秒阻止
无效Spring 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 毫秒阻止
无效Spring 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.106 毫秒阻止
无效Spring 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.109 毫秒阻止
无效Spring 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.337 毫秒阻止
无效Spring 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.342 毫秒阻止
无效Spring 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.341 毫秒阻止

Hyperion API

无效

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.

检查时间
延迟
111 毫秒
浏览器请求
阻止
版本
未知

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

近期检查
最新存储的 Hyperion API 健康检查。
状态版本摘要延迟CORS检查时间
无效未知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.111 毫秒阻止
无效未知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.112 毫秒阻止
无效未知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.104 毫秒阻止
无效未知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.112 毫秒阻止
无效未知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.332 毫秒阻止
无效未知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.323 毫秒阻止
无效未知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.334 毫秒阻止
无效未知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.105 毫秒阻止
无效未知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.114 毫秒阻止
无效未知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.119 毫秒阻止