稼働率の履歴
監視対象機能の正常および低下したチェックの割合。データのない期間は除外します。
稼働率 50.0%
3か月
2026年7月31日 UTC灰色:チェック記録なし現在
オペレーターと開発者向けの Antelope ノード健全性・ステータス・履歴モニタリング。
1064487b3cd1a897ce03ae5b6a865651747e2e152090f99c1d19d44e01aea5a4
このエンドポイントの健全性、鮮度、CORS、最近のチェック履歴。
監視対象機能の正常および低下したチェックの割合。データのない期間は除外します。
稼働率 50.0%
3か月
Chain API responded normally
| ステータス | バージョン | 要約 | レイテンシ | CORS | チェック日時 |
|---|---|---|---|---|---|
| 正常 | Leap v5.0.3wax01 | Chain API responded normally | 620 ms | 許可 | |
| 正常 | Leap v5.0.3wax01 | Chain API responded normally | 617 ms | 許可 | |
| 正常 | Leap v5.0.3wax01 | Chain API responded normally | 609 ms | 許可 | |
| 正常 | Leap v5.0.3wax01 | Chain API responded normally | 620 ms | 許可 | |
| 正常 | Leap v5.0.3wax01 | Chain API responded normally | 618 ms | 許可 | |
| 正常 | Leap v5.0.3wax01 | Chain API responded normally | 620 ms | 許可 | |
| 正常 | Leap v5.0.3wax01 | Chain API responded normally | 607 ms | 許可 | |
| 正常 | Leap v5.0.3wax01 | Chain API responded normally | 601 ms | 許可 | |
| 正常 | Leap v5.0.3wax01 | Chain API responded normally | 625 ms | 許可 | |
| 正常 | Leap v5.0.3wax01 | Chain API responded normally | 624 ms | 許可 |
account-query responded normally
| ステータス | バージョン | 要約 | レイテンシ | CORS | チェック日時 |
|---|---|---|---|---|---|
| 正常 | Leap v5.0.3wax01 | account-query responded normally | 698 ms | 許可 | |
| 正常 | Leap v5.0.3wax01 | account-query responded normally | 684 ms | 許可 | |
| 正常 | Leap v5.0.3wax01 | account-query responded normally | 645 ms | 許可 | |
| 正常 | Leap v5.0.3wax01 | account-query responded normally | 669 ms | 許可 | |
| 正常 | Leap v5.0.3wax01 | account-query responded normally | 647 ms | 許可 | |
| 正常 | Leap v5.0.3wax01 | account-query responded normally | 620 ms | 許可 | |
| 正常 | Leap v5.0.3wax01 | account-query responded normally | 668 ms | 許可 | |
| 正常 | Leap v5.0.3wax01 | account-query responded normally | 655 ms | 許可 | |
| 正常 | Leap v5.0.3wax01 | account-query responded normally | 646 ms | 許可 | |
| 正常 | Leap v5.0.3wax01 | account-query responded normally | 665 ms | 許可 |
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.
| ステータス | バージョン | 要約 | レイテンシ | CORS | チェック日時 |
|---|---|---|---|---|---|
| 無効 | Leap v5.0.3wax01 | 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. | 628 ms | 許可 | |
| 無効 | Leap v5.0.3wax01 | 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. | 619 ms | 許可 | |
| 無効 | Leap v5.0.3wax01 | 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. | 632 ms | 許可 | |
| 無効 | Leap v5.0.3wax01 | 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 ms | 許可 | |
| 無効 | Leap v5.0.3wax01 | 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. | 610 ms | 許可 | |
| 無効 | Leap v5.0.3wax01 | 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. | 606 ms | 許可 | |
| 無効 | Leap v5.0.3wax01 | 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. | 635 ms | 許可 | |
| 無効 | Leap v5.0.3wax01 | 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. | 637 ms | 許可 | |
| 無効 | Leap v5.0.3wax01 | 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. | 628 ms | 許可 | |
| 無効 | Leap v5.0.3wax01 | 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. | 645 ms | 許可 |
Indexer is 688051 blocks behind the chain head (limit 180). Check that it is keeping up with nodeos.
| ステータス | バージョン | 要約 | レイテンシ | CORS | チェック日時 |
|---|---|---|---|---|---|
| 古い | 3.5.0-5 | Indexer is 688051 blocks behind the chain head (limit 180). Check that it is keeping up with nodeos. | 631 ms | 許可 | |
| 古い | 3.5.0-5 | Indexer is 685638 blocks behind the chain head (limit 180). Check that it is keeping up with nodeos. | 608 ms | 許可 | |
| 古い | 3.5.0-5 | Indexer is 683250 blocks behind the chain head (limit 180). Check that it is keeping up with nodeos. | 622 ms | 許可 | |
| 古い | 3.5.0-5 | Indexer is 680850 blocks behind the chain head (limit 180). Check that it is keeping up with nodeos. | 627 ms | 許可 | |
| 古い | 3.5.0-5 | Indexer is 678440 blocks behind the chain head (limit 180). Check that it is keeping up with nodeos. | 626 ms | 許可 | |
| 古い | 3.5.0-5 | Indexer is 676040 blocks behind the chain head (limit 180). Check that it is keeping up with nodeos. | 606 ms | 許可 | |
| 古い | 3.5.0-5 | Indexer is 673637 blocks behind the chain head (limit 180). Check that it is keeping up with nodeos. | 609 ms | 許可 | |
| 古い | 3.5.0-5 | Indexer is 671251 blocks behind the chain head (limit 180). Check that it is keeping up with nodeos. | 613 ms | 許可 | |
| 古い | 3.5.0-5 | Indexer is 668837 blocks behind the chain head (limit 180). Check that it is keeping up with nodeos. | 610 ms | 許可 | |
| 古い | 3.5.0-5 | Indexer is 666450 blocks behind the chain head (limit 180). Check that it is keeping up with nodeos. | 633 ms | 許可 |