HerdCheckv0.6.7

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

WAX Mainnet

1064487b3cd1a897ce03ae5b6a865651747e2e152090f99c1d19d44e01aea5a4

https://wax.eosrio.io

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

出块节点
eosriobrazil
链
WAX Mainnet
声明的链历史
部分
位置
Rio de Janeiro

可用性历史

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

可用性 60.9%

7天

2026年10月23日 6时 UTC灰色：无检查记录现在

当前服务健康

Chain API

正常

Chain API responded normally

检查时间
延迟
620 毫秒
浏览器请求
允许
版本
Leap v5.0.3wax01
近期检查
最新存储的 Chain API 健康检查。
状态版本摘要延迟CORS检查时间
正常Leap v5.0.3wax01Chain API responded normally620 毫秒允许
正常Leap v5.0.3wax01Chain API responded normally618 毫秒允许
正常Leap v5.0.3wax01Chain API responded normally620 毫秒允许
正常Leap v5.0.3wax01Chain API responded normally607 毫秒允许
正常Leap v5.0.3wax01Chain API responded normally601 毫秒允许
正常Leap v5.0.3wax01Chain API responded normally625 毫秒允许
正常Leap v5.0.3wax01Chain API responded normally624 毫秒允许
正常Leap v5.0.3wax01Chain API responded normally705 毫秒允许
正常Leap v5.0.3wax01Chain API responded normally620 毫秒允许
正常Leap v5.0.3wax01Chain API responded normally614 毫秒允许

Account Query

正常

account-query responded normally

检查时间
延迟
669 毫秒
浏览器请求
允许
版本
Leap v5.0.3wax01
近期检查
最新存储的 Account Query 健康检查。
状态版本摘要延迟CORS检查时间
正常Leap v5.0.3wax01account-query responded normally669 毫秒允许
正常Leap v5.0.3wax01account-query responded normally647 毫秒允许
正常Leap v5.0.3wax01account-query responded normally620 毫秒允许
正常Leap v5.0.3wax01account-query responded normally668 毫秒允许
正常Leap v5.0.3wax01account-query responded normally655 毫秒允许
正常Leap v5.0.3wax01account-query responded normally646 毫秒允许
正常Leap v5.0.3wax01account-query responded normally665 毫秒允许
正常Leap v5.0.3wax01account-query responded normally810 毫秒允许
正常Leap v5.0.3wax01account-query responded normally644 毫秒允许
正常Leap v5.0.3wax01account-query responded normally681 毫秒允许

History API

无效

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.

检查时间
延迟
615 毫秒
浏览器请求
允许
版本
Leap v5.0.3wax01
近期检查
最新存储的 History API 健康检查。
状态版本摘要延迟CORS检查时间
无效Leap v5.0.3wax01HTTP 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.615 毫秒允许
无效Leap v5.0.3wax01HTTP 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.610 毫秒允许
无效Leap v5.0.3wax01HTTP 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.606 毫秒允许
无效Leap v5.0.3wax01HTTP 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.635 毫秒允许
无效Leap v5.0.3wax01HTTP 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.637 毫秒允许
无效Leap v5.0.3wax01HTTP 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.628 毫秒允许
无效Leap v5.0.3wax01HTTP 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.645 毫秒允许
无效Leap v5.0.3wax01HTTP 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.608 毫秒允许
无效Leap v5.0.3wax01HTTP 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.635 毫秒允许
无效Leap v5.0.3wax01HTTP 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.628 毫秒允许

Hyperion API

过期

Indexer is 680850 blocks behind the chain head (limit 180). Check that it is keeping up with nodeos.

检查时间
延迟
627 毫秒
浏览器请求
允许
版本
3.5.0-5
近期检查
最新存储的 Hyperion API 健康检查。
状态版本摘要延迟CORS检查时间
过期3.5.0-5Indexer is 680850 blocks behind the chain head (limit 180). Check that it is keeping up with nodeos.627 毫秒允许
过期3.5.0-5Indexer is 678440 blocks behind the chain head (limit 180). Check that it is keeping up with nodeos.626 毫秒允许
过期3.5.0-5Indexer is 676040 blocks behind the chain head (limit 180). Check that it is keeping up with nodeos.606 毫秒允许
过期3.5.0-5Indexer is 673637 blocks behind the chain head (limit 180). Check that it is keeping up with nodeos.609 毫秒允许
过期3.5.0-5Indexer is 671251 blocks behind the chain head (limit 180). Check that it is keeping up with nodeos.613 毫秒允许
过期3.5.0-5Indexer is 668837 blocks behind the chain head (limit 180). Check that it is keeping up with nodeos.610 毫秒允许
过期3.5.0-5Indexer is 666450 blocks behind the chain head (limit 180). Check that it is keeping up with nodeos.633 毫秒允许
过期3.5.0-5Indexer is 664051 blocks behind the chain head (limit 180). Check that it is keeping up with nodeos.657 毫秒允许
过期3.5.0-5Indexer is 661640 blocks behind the chain head (limit 180). Check that it is keeping up with nodeos.607 毫秒允许
过期3.5.0-5Indexer is 659237 blocks behind the chain head (limit 180). Check that it is keeping up with nodeos.628 毫秒允许