稼働率の履歴
監視対象機能の正常および低下したチェックの割合。データのない期間は除外します。
稼働率 48.3%
1年
2025年10月31日 UTC灰色:チェック記録なし現在
オペレーターと開発者向けの Antelope ノード健全性・ステータス・履歴モニタリング。
1064487b3cd1a897ce03ae5b6a865651747e2e152090f99c1d19d44e01aea5a4
このエンドポイントの健全性、鮮度、CORS、最近のチェック履歴。
監視対象機能の正常および低下したチェックの割合。データのない期間は除外します。
稼働率 48.3%
1年
Chain API responded normally
| ステータス | バージョン | 要約 | レイテンシ | CORS | チェック日時 |
|---|---|---|---|---|---|
| 正常 | Leap v5.0.3wax01 | Chain API responded normally | 598 ms | 許可 | |
| 正常 | Leap v5.0.3wax01 | Chain API responded normally | 613 ms | 許可 | |
| 正常 | Leap v5.0.3wax01 | Chain API responded normally | 628 ms | 許可 | |
| 正常 | Leap v5.0.3wax01 | Chain API responded normally | 596 ms | 許可 | |
| 正常 | Leap v5.0.3wax01 | Chain API responded normally | 623 ms | 許可 | |
| 正常 | Leap v5.0.3wax01 | Chain API responded normally | 620 ms | 許可 | |
| 正常 | Leap v5.0.3wax01 | Chain API responded normally | 616 ms | 許可 | |
| 正常 | Leap v5.0.3wax01 | Chain API responded normally | 621 ms | 許可 | |
| 正常 | Leap v5.0.3wax01 | Chain API responded normally | 621 ms | 許可 | |
| 正常 | Leap v5.0.3wax01 | Chain API responded normally | 618 ms | 許可 |
account-query responded normally
| ステータス | バージョン | 要約 | レイテンシ | CORS | チェック日時 |
|---|---|---|---|---|---|
| 正常 | Leap v5.0.3wax01 | account-query responded normally | 653 ms | 許可 | |
| 正常 | Leap v5.0.3wax01 | account-query responded normally | 623 ms | 許可 | |
| 正常 | Leap v5.0.3wax01 | account-query responded normally | 1698 ms | 許可 | |
| 正常 | Leap v5.0.3wax01 | account-query responded normally | 675 ms | 許可 | |
| 正常 | Leap v5.0.3wax01 | account-query responded normally | 675 ms | 許可 | |
| 正常 | Leap v5.0.3wax01 | account-query responded normally | 888 ms | 許可 | |
| 正常 | Leap v5.0.3wax01 | account-query responded normally | 687 ms | 許可 | |
| 正常 | Leap v5.0.3wax01 | account-query responded normally | 634 ms | 許可 | |
| 正常 | Leap v5.0.3wax01 | account-query responded normally | 652 ms | 許可 | |
| 正常 | Leap v5.0.3wax01 | account-query responded normally | 650 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. | 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. | 612 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. | 612 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. | 631 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. | 604 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. | 624 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. | 631 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. | 612 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. | 608 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 | 許可 |
Indexer is 714437 blocks behind the chain head (limit 180). Check that it is keeping up with nodeos.
| ステータス | バージョン | 要約 | レイテンシ | CORS | チェック日時 |
|---|---|---|---|---|---|
| 古い | 3.5.0-5 | Indexer is 714437 blocks behind the chain head (limit 180). Check that it is keeping up with nodeos. | 626 ms | 許可 | |
| 古い | 3.5.0-5 | Indexer is 712051 blocks behind the chain head (limit 180). Check that it is keeping up with nodeos. | 627 ms | 許可 | |
| 古い | 3.5.0-5 | Indexer is 709640 blocks behind the chain head (limit 180). Check that it is keeping up with nodeos. | 610 ms | 許可 | |
| 古い | 3.5.0-5 | Indexer is 707240 blocks behind the chain head (limit 180). Check that it is keeping up with nodeos. | 613 ms | 許可 | |
| 古い | 3.5.0-5 | Indexer is 704850 blocks behind the chain head (limit 180). Check that it is keeping up with nodeos. | 635 ms | 許可 | |
| 古い | 3.5.0-5 | Indexer is 702437 blocks behind the chain head (limit 180). Check that it is keeping up with nodeos. | 627 ms | 許可 | |
| 古い | 3.5.0-5 | Indexer is 700038 blocks behind the chain head (limit 180). Check that it is keeping up with nodeos. | 613 ms | 許可 | |
| 古い | 3.5.0-5 | Indexer is 697650 blocks behind the chain head (limit 180). Check that it is keeping up with nodeos. | 606 ms | 許可 | |
| 古い | 3.5.0-5 | Indexer is 695238 blocks behind the chain head (limit 180). Check that it is keeping up with nodeos. | 627 ms | 許可 | |
| 古い | 3.5.0-5 | Indexer is 692840 blocks behind the chain head (limit 180). Check that it is keeping up with nodeos. | 601 ms | 許可 |