稼働率の履歴
監視対象機能の正常および低下したチェックの割合。データのない期間は除外します。
稼働率 0.0%
2か月
オペレーターと開発者向けの Antelope ノード健全性・ステータス・履歴モニタリング。
f16b1833c747c43682f4386fca9cbb327929334a762755ebec17f6f23c9b8a12
このエンドポイントの健全性、鮮度、CORS、最近のチェック履歴。
監視対象機能の正常および低下したチェックの割合。データのない期間は除外します。
稼働率 0.0%
2か月
No response within 5s. The server is down, overloaded, or a firewall is dropping connections.
Request never completed
| ステータス | バージョン | 要約 | レイテンシ | CORS | チェック日時 |
|---|---|---|---|---|---|
| ダウン | 不明 | No response within 5s. The server is down, overloaded, or a firewall is dropping connections. | — | ブロック | |
| ダウン | 不明 | No response within 5s. The server is down, overloaded, or a firewall is dropping connections. | — | ブロック | |
| ダウン | 不明 | No response within 5s. The server is down, overloaded, or a firewall is dropping connections. | — | ブロック | |
| ダウン | 不明 | No response within 5s. The server is down, overloaded, or a firewall is dropping connections. | — | ブロック | |
| ダウン | 不明 | No response within 5s. The server is down, overloaded, or a firewall is dropping connections. | — | ブロック | |
| ダウン | 不明 | No response within 5s. The server is down, overloaded, or a firewall is dropping connections. | — | ブロック | |
| ダウン | 不明 | No response within 5s. The server is down, overloaded, or a firewall is dropping connections. | — | ブロック | |
| ダウン | 不明 | No response within 5s. The server is down, overloaded, or a firewall is dropping connections. | — | ブロック | |
| ダウン | 不明 | No response within 5s. The server is down, overloaded, or a firewall is dropping connections. | — | ブロック | |
| ダウン | 不明 | No response within 5s. The server is down, overloaded, or a firewall is dropping connections. | — | ブロック |
No response within 5s. The server is down, overloaded, or a firewall is dropping connections.
Request never completed
| ステータス | バージョン | 要約 | レイテンシ | CORS | チェック日時 |
|---|---|---|---|---|---|
| ダウン | 不明 | No response within 5s. The server is down, overloaded, or a firewall is dropping connections. | — | ブロック | |
| ダウン | 不明 | No response within 5s. The server is down, overloaded, or a firewall is dropping connections. | — | ブロック | |
| ダウン | 不明 | No response within 5s. The server is down, overloaded, or a firewall is dropping connections. | — | ブロック | |
| ダウン | 不明 | No response within 5s. The server is down, overloaded, or a firewall is dropping connections. | — | ブロック | |
| ダウン | 不明 | No response within 5s. The server is down, overloaded, or a firewall is dropping connections. | — | ブロック | |
| ダウン | 不明 | No response within 5s. The server is down, overloaded, or a firewall is dropping connections. | — | ブロック | |
| ダウン | 不明 | No response within 5s. The server is down, overloaded, or a firewall is dropping connections. | — | ブロック | |
| ダウン | 不明 | No response within 5s. The server is down, overloaded, or a firewall is dropping connections. | — | ブロック | |
| ダウン | 不明 | No response within 5s. The server is down, overloaded, or a firewall is dropping connections. | — | ブロック | |
| ダウン | 不明 | No response within 5s. The server is down, overloaded, or a firewall is dropping connections. | — | ブロック |
HTTP 502 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.
Response Access-Control-Allow-Origin is missing. It must be "*" or echo the request Origin, otherwise browser apps cannot read the response.
| ステータス | バージョン | 要約 | レイテンシ | CORS | チェック日時 |
|---|---|---|---|---|---|
| 無効 | 不明 | HTTP 502 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. | 71 ms | ブロック | |
| 無効 | 不明 | HTTP 502 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. | 148 ms | ブロック | |
| 無効 | 不明 | HTTP 502 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. | 155 ms | ブロック | |
| 無効 | 不明 | HTTP 502 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. | 74 ms | ブロック | |
| 無効 | 不明 | HTTP 502 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. | 151 ms | ブロック | |
| 無効 | 不明 | HTTP 502 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. | 203 ms | ブロック | |
| 無効 | 不明 | HTTP 502 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. | 69 ms | ブロック | |
| 無効 | 不明 | HTTP 502 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. | 77 ms | ブロック | |
| 無効 | 不明 | HTTP 502 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. | 82 ms | ブロック | |
| 無効 | 不明 | HTTP 502 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. | 188 ms | ブロック |
HTTP 502 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.
Response Access-Control-Allow-Origin is missing. It must be "*" or echo the request Origin, otherwise browser apps cannot read the response.
| ステータス | バージョン | 要約 | レイテンシ | CORS | チェック日時 |
|---|---|---|---|---|---|
| 無効 | 不明 | HTTP 502 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. | 73 ms | ブロック | |
| 無効 | 不明 | HTTP 502 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. | 143 ms | ブロック | |
| 無効 | 不明 | HTTP 502 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. | 150 ms | ブロック | |
| 無効 | 不明 | HTTP 502 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. | 69 ms | ブロック | |
| 無効 | 不明 | HTTP 502 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. | 71 ms | ブロック | |
| 無効 | 不明 | HTTP 502 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. | 187 ms | ブロック | |
| 無効 | 不明 | HTTP 502 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. | 70 ms | ブロック | |
| 無効 | 不明 | HTTP 502 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. | 70 ms | ブロック | |
| 無効 | 不明 | HTTP 502 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. | 81 ms | ブロック | |
| 無効 | 不明 | HTTP 502 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. | 167 ms | ブロック |