稼働率の履歴
監視対象機能の正常および低下したチェックの割合。データのない期間は除外します。
稼働率 0.0%
2か月
2026年8月31日 UTC灰色:チェック記録なし現在
オペレーターと開発者向けの Antelope ノード健全性・ステータス・履歴モニタリング。
f16b1833c747c43682f4386fca9cbb327929334a762755ebec17f6f23c9b8a12
このエンドポイントの健全性、鮮度、CORS、最近のチェック履歴。
監視対象機能の正常および低下したチェックの割合。データのない期間は除外します。
稼働率 0.0%
2か月
HTTP 521 on /health instead of a valid atomic-assets-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 /health instead of a valid atomic-assets-api response. The server or its upstream node is failing. Check the node, the proxy and the server logs. | 126 ms | ブロック | |
| 無効 | 不明 | HTTP 521 on /health instead of a valid atomic-assets-api response. The server or its upstream node is failing. Check the node, the proxy and the server logs. | 202 ms | ブロック | |
| 無効 | 不明 | HTTP 521 on /health instead of a valid atomic-assets-api response. The server or its upstream node is failing. Check the node, the proxy and the server logs. | 92 ms | ブロック | |
| 無効 | 不明 | HTTP 521 on /health instead of a valid atomic-assets-api response. The server or its upstream node is failing. Check the node, the proxy and the server logs. | 102 ms | ブロック | |
| 無効 | 不明 | HTTP 521 on /health instead of a valid atomic-assets-api response. The server or its upstream node is failing. Check the node, the proxy and the server logs. | 122 ms | ブロック | |
| 無効 | 不明 | HTTP 521 on /health instead of a valid atomic-assets-api response. The server or its upstream node is failing. Check the node, the proxy and the server logs. | 190 ms | ブロック | |
| 無効 | 不明 | HTTP 521 on /health instead of a valid atomic-assets-api response. The server or its upstream node is failing. Check the node, the proxy and the server logs. | 82 ms | ブロック | |
| 無効 | 不明 | HTTP 521 on /health instead of a valid atomic-assets-api response. The server or its upstream node is failing. Check the node, the proxy and the server logs. | 106 ms | ブロック | |
| 無効 | 不明 | HTTP 521 on /health instead of a valid atomic-assets-api response. The server or its upstream node is failing. Check the node, the proxy and the server logs. | 192 ms | ブロック | |
| 無効 | 不明 | HTTP 521 on /health instead of a valid atomic-assets-api response. The server or its upstream node is failing. Check the node, the proxy and the server logs. | 85 ms | ブロック | |
| 無効 | 不明 | HTTP 521 on /health instead of a valid atomic-assets-api response. The server or its upstream node is failing. Check the node, the proxy and the server logs. | 177 ms | ブロック | |
| 無効 | 不明 | HTTP 521 on /health instead of a valid atomic-assets-api response. The server or its upstream node is failing. Check the node, the proxy and the server logs. | 125 ms | ブロック | |
| 無効 | 不明 | HTTP 521 on /health instead of a valid atomic-assets-api response. The server or its upstream node is failing. Check the node, the proxy and the server logs. | 100 ms | ブロック | |
| 無効 | 不明 | HTTP 521 on /health instead of a valid atomic-assets-api response. The server or its upstream node is failing. Check the node, the proxy and the server logs. | 95 ms | ブロック | |
| 無効 | 不明 | HTTP 521 on /health instead of a valid atomic-assets-api response. The server or its upstream node is failing. Check the node, the proxy and the server logs. | 96 ms | ブロック | |
| 無効 | 不明 | HTTP 521 on /health instead of a valid atomic-assets-api response. The server or its upstream node is failing. Check the node, the proxy and the server logs. | 83 ms | ブロック | |
| 無効 | 不明 | HTTP 521 on /health instead of a valid atomic-assets-api response. The server or its upstream node is failing. Check the node, the proxy and the server logs. | 187 ms | ブロック | |
| 無効 | 不明 | HTTP 521 on /health instead of a valid atomic-assets-api response. The server or its upstream node is failing. Check the node, the proxy and the server logs. | 87 ms | ブロック | |
| 無効 | 不明 | HTTP 521 on /health instead of a valid atomic-assets-api response. The server or its upstream node is failing. Check the node, the proxy and the server logs. | 90 ms | ブロック | |
| 無効 | 不明 | HTTP 521 on /health instead of a valid atomic-assets-api response. The server or its upstream node is failing. Check the node, the proxy and the server logs. | 175 ms | ブロック | |
| 無効 | 不明 | HTTP 521 on /health instead of a valid atomic-assets-api response. The server or its upstream node is failing. Check the node, the proxy and the server logs. | 90 ms | ブロック | |
| 無効 | 不明 | HTTP 521 on /health instead of a valid atomic-assets-api response. The server or its upstream node is failing. Check the node, the proxy and the server logs. | 87 ms | ブロック | |
| 無効 | 不明 | HTTP 521 on /health instead of a valid atomic-assets-api response. The server or its upstream node is failing. Check the node, the proxy and the server logs. | 93 ms | ブロック | |
| 無効 | 不明 | HTTP 521 on /health instead of a valid atomic-assets-api response. The server or its upstream node is failing. Check the node, the proxy and the server logs. | 104 ms | ブロック | |
| 無効 | 不明 | HTTP 521 on /health instead of a valid atomic-assets-api response. The server or its upstream node is failing. Check the node, the proxy and the server logs. | 91 ms | ブロック | |
| 無効 | 不明 | HTTP 521 on /health instead of a valid atomic-assets-api response. The server or its upstream node is failing. Check the node, the proxy and the server logs. | 80 ms | ブロック | |
| 無効 | 不明 | HTTP 521 on /health instead of a valid atomic-assets-api response. The server or its upstream node is failing. Check the node, the proxy and the server logs. | 179 ms | ブロック | |
| 無効 | 不明 | HTTP 521 on /health instead of a valid atomic-assets-api response. The server or its upstream node is failing. Check the node, the proxy and the server logs. | 190 ms | ブロック | |
| 無効 | 不明 | HTTP 521 on /health instead of a valid atomic-assets-api response. The server or its upstream node is failing. Check the node, the proxy and the server logs. | 90 ms | ブロック | |
| 無効 | 不明 | HTTP 521 on /health instead of a valid atomic-assets-api response. The server or its upstream node is failing. Check the node, the proxy and the server logs. | 75 ms | ブロック | |
| 無効 | 不明 | HTTP 521 on /health instead of a valid atomic-assets-api response. The server or its upstream node is failing. Check the node, the proxy and the server logs. | 93 ms | ブロック | |
| 無効 | 不明 | HTTP 521 on /health instead of a valid atomic-assets-api response. The server or its upstream node is failing. Check the node, the proxy and the server logs. | 93 ms | ブロック | |
| 無効 | 不明 | HTTP 521 on /health instead of a valid atomic-assets-api response. The server or its upstream node is failing. Check the node, the proxy and the server logs. | 87 ms | ブロック | |
| 無効 | 不明 | HTTP 521 on /health instead of a valid atomic-assets-api response. The server or its upstream node is failing. Check the node, the proxy and the server logs. | 174 ms | ブロック | |
| 無効 | 不明 | HTTP 521 on /health instead of a valid atomic-assets-api response. The server or its upstream node is failing. Check the node, the proxy and the server logs. | 79 ms | ブロック | |
| 無効 | 不明 | HTTP 521 on /health instead of a valid atomic-assets-api response. The server or its upstream node is failing. Check the node, the proxy and the server logs. | 101 ms | ブロック | |
| 無効 | 不明 | HTTP 521 on /health instead of a valid atomic-assets-api response. The server or its upstream node is failing. Check the node, the proxy and the server logs. | 106 ms | ブロック | |
| 無効 | 不明 | HTTP 521 on /health instead of a valid atomic-assets-api response. The server or its upstream node is failing. Check the node, the proxy and the server logs. | 78 ms | ブロック | |
| 無効 | 不明 | HTTP 521 on /health instead of a valid atomic-assets-api response. The server or its upstream node is failing. Check the node, the proxy and the server logs. | 175 ms | ブロック | |
| 無効 | 不明 | HTTP 521 on /health instead of a valid atomic-assets-api response. The server or its upstream node is failing. Check the node, the proxy and the server logs. | 185 ms | ブロック |