稼働率の履歴
監視対象機能の正常および低下したチェックの割合。データのない期間は除外します。
稼働率 0.0%
3日
2026年10月27日 6時 UTC灰色:チェック記録なし現在
オペレーターと開発者向けの Antelope ノード健全性・ステータス・履歴モニタリング。
1064487b3cd1a897ce03ae5b6a865651747e2e152090f99c1d19d44e01aea5a4
このエンドポイントの健全性、鮮度、CORS、最近のチェック履歴。
監視対象機能の正常および低下したチェックの割合。データのない期間は除外します。
稼働率 0.0%
3日
HTTP 521 on /api/status instead of a valid light-api 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 521 on /api/status instead of a valid light-api response. The server or its upstream node is failing. Check the node, the proxy and the server logs. | 82 ms | ブロック | |
| 無効 | 不明 | HTTP 521 on /api/status instead of a valid light-api response. The server or its upstream node is failing. Check the node, the proxy and the server logs. | 84 ms | ブロック | |
| 無効 | 不明 | HTTP 521 on /api/status instead of a valid light-api response. The server or its upstream node is failing. Check the node, the proxy and the server logs. | 69 ms | ブロック | |
| 無効 | 不明 | HTTP 521 on /api/status instead of a valid light-api response. The server or its upstream node is failing. Check the node, the proxy and the server logs. | 61 ms | ブロック | |
| 無効 | 不明 | HTTP 521 on /api/status instead of a valid light-api response. The server or its upstream node is failing. Check the node, the proxy and the server logs. | 58 ms | ブロック | |
| 無効 | 不明 | HTTP 521 on /api/status instead of a valid light-api response. The server or its upstream node is failing. Check the node, the proxy and the server logs. | 79 ms | ブロック | |
| 無効 | 不明 | HTTP 521 on /api/status instead of a valid light-api response. The server or its upstream node is failing. Check the node, the proxy and the server logs. | 83 ms | ブロック | |
| 無効 | 不明 | HTTP 521 on /api/status instead of a valid light-api response. The server or its upstream node is failing. Check the node, the proxy and the server logs. | 88 ms | ブロック | |
| 無効 | 不明 | HTTP 521 on /api/status instead of a valid light-api response. The server or its upstream node is failing. Check the node, the proxy and the server logs. | 66 ms | ブロック | |
| 無効 | 不明 | HTTP 521 on /api/status instead of a valid light-api response. The server or its upstream node is failing. Check the node, the proxy and the server logs. | 75 ms | ブロック | |
| 無効 | 不明 | HTTP 521 on /api/status instead of a valid light-api response. The server or its upstream node is failing. Check the node, the proxy and the server logs. | 88 ms | ブロック | |
| 無効 | 不明 | HTTP 521 on /api/status instead of a valid light-api response. The server or its upstream node is failing. Check the node, the proxy and the server logs. | 78 ms | ブロック | |
| 無効 | 不明 | HTTP 521 on /api/status instead of a valid light-api response. The server or its upstream node is failing. Check the node, the proxy and the server logs. | 87 ms | ブロック | |
| 無効 | 不明 | HTTP 521 on /api/status instead of a valid light-api response. The server or its upstream node is failing. Check the node, the proxy and the server logs. | 97 ms | ブロック | |
| 無効 | 不明 | HTTP 521 on /api/status instead of a valid light-api response. The server or its upstream node is failing. Check the node, the proxy and the server logs. | 76 ms | ブロック | |
| 無効 | 不明 | HTTP 521 on /api/status instead of a valid light-api response. The server or its upstream node is failing. Check the node, the proxy and the server logs. | 96 ms | ブロック | |
| 無効 | 不明 | HTTP 521 on /api/status instead of a valid light-api response. The server or its upstream node is failing. Check the node, the proxy and the server logs. | 89 ms | ブロック | |
| 無効 | 不明 | HTTP 521 on /api/status instead of a valid light-api response. The server or its upstream node is failing. Check the node, the proxy and the server logs. | 82 ms | ブロック | |
| 無効 | 不明 | HTTP 521 on /api/status instead of a valid light-api response. The server or its upstream node is failing. Check the node, the proxy and the server logs. | 87 ms | ブロック | |
| 無効 | 不明 | HTTP 521 on /api/status instead of a valid light-api response. The server or its upstream node is failing. Check the node, the proxy and the server logs. | 85 ms | ブロック | |
| 無効 | 不明 | HTTP 521 on /api/status instead of a valid light-api response. The server or its upstream node is failing. Check the node, the proxy and the server logs. | 89 ms | ブロック | |
| 無効 | 不明 | HTTP 521 on /api/status instead of a valid light-api response. The server or its upstream node is failing. Check the node, the proxy and the server logs. | 80 ms | ブロック | |
| 無効 | 不明 | HTTP 521 on /api/status instead of a valid light-api response. The server or its upstream node is failing. Check the node, the proxy and the server logs. | 76 ms | ブロック | |
| 無効 | 不明 | HTTP 521 on /api/status instead of a valid light-api response. The server or its upstream node is failing. Check the node, the proxy and the server logs. | 95 ms | ブロック | |
| 無効 | 不明 | HTTP 521 on /api/status instead of a valid light-api response. The server or its upstream node is failing. Check the node, the proxy and the server logs. | 70 ms | ブロック | |
| 無効 | 不明 | HTTP 521 on /api/status instead of a valid light-api response. The server or its upstream node is failing. Check the node, the proxy and the server logs. | 66 ms | ブロック | |
| 無効 | 不明 | HTTP 521 on /api/status instead of a valid light-api response. The server or its upstream node is failing. Check the node, the proxy and the server logs. | 186 ms | ブロック | |
| 無効 | 不明 | HTTP 521 on /api/status instead of a valid light-api response. The server or its upstream node is failing. Check the node, the proxy and the server logs. | 88 ms | ブロック | |
| 無効 | 不明 | HTTP 521 on /api/status instead of a valid light-api response. The server or its upstream node is failing. Check the node, the proxy and the server logs. | 92 ms | ブロック | |
| 無効 | 不明 | HTTP 521 on /api/status instead of a valid light-api response. The server or its upstream node is failing. Check the node, the proxy and the server logs. | 95 ms | ブロック | |
| 無効 | 不明 | HTTP 521 on /api/status instead of a valid light-api response. The server or its upstream node is failing. Check the node, the proxy and the server logs. | 101 ms | ブロック | |
| 無効 | 不明 | HTTP 521 on /api/status instead of a valid light-api response. The server or its upstream node is failing. Check the node, the proxy and the server logs. | 98 ms | ブロック | |
| 無効 | 不明 | HTTP 521 on /api/status instead of a valid light-api response. The server or its upstream node is failing. Check the node, the proxy and the server logs. | 197 ms | ブロック | |
| 無効 | 不明 | HTTP 521 on /api/status instead of a valid light-api response. The server or its upstream node is failing. Check the node, the proxy and the server logs. | 104 ms | ブロック | |
| 無効 | 不明 | HTTP 521 on /api/status instead of a valid light-api response. The server or its upstream node is failing. Check the node, the proxy and the server logs. | 115 ms | ブロック | |
| 無効 | 不明 | HTTP 521 on /api/status instead of a valid light-api response. The server or its upstream node is failing. Check the node, the proxy and the server logs. | 106 ms | ブロック | |
| 無効 | 不明 | HTTP 521 on /api/status instead of a valid light-api response. The server or its upstream node is failing. Check the node, the proxy and the server logs. | 97 ms | ブロック | |
| 無効 | 不明 | HTTP 521 on /api/status instead of a valid light-api response. The server or its upstream node is failing. Check the node, the proxy and the server logs. | 85 ms | ブロック | |
| 無効 | 不明 | HTTP 521 on /api/status instead of a valid light-api response. The server or its upstream node is failing. Check the node, the proxy and the server logs. | 113 ms | ブロック | |
| 無効 | 不明 | HTTP 521 on /api/status instead of a valid light-api response. The server or its upstream node is failing. Check the node, the proxy and the server logs. | 93 ms | ブロック |