稼働率の履歴
監視対象機能の正常および低下したチェックの割合。データのない期間は除外します。
稼働率 0.0%
6か月
2026年5月1日 UTC灰色：チェック記録なし現在
Vaulta Mainnet
aca376f206b8fc25a6ed44dbdc66547c36c6c33e3a119ffbeaef943642f0e906
https://eu.eosdac.io
このエンドポイントの健全性、鮮度、CORS、最近のチェック履歴。
- プロデューサー
- eosdacserver
- チェーン
- Vaulta Mainnet
- 申告されたチェーン履歴
- 部分
- 場所
- Bucharest
現在のサービス状態
Chain API
無効HTTP 503 on /v1/chain/get_info instead of a valid chain-api response. The server or its upstream node is failing. Check the node, the proxy and the server logs.
- チェック日時
- レイテンシ
- 108 ms
- ブラウザーのリクエスト
- ブロック
- バージョン
- 不明
Response Access-Control-Allow-Origin is missing. It must be "*" or echo the request Origin, otherwise browser apps cannot read the response.
最近のチェック
| ステータス | バージョン | 要約 | レイテンシ | CORS | チェック日時 |
|---|---|---|---|---|---|
| 無効 | 不明 | HTTP 503 on /v1/chain/get_info instead of a valid chain-api response. The server or its upstream node is failing. Check the node, the proxy and the server logs. | 108 ms | ブロック | |
| 無効 | 不明 | HTTP 503 on /v1/chain/get_info instead of a valid chain-api response. The server or its upstream node is failing. Check the node, the proxy and the server logs. | 110 ms | ブロック | |
| 無効 | 不明 | HTTP 503 on /v1/chain/get_info instead of a valid chain-api response. The server or its upstream node is failing. Check the node, the proxy and the server logs. | 112 ms | ブロック | |
| 無効 | 不明 | HTTP 503 on /v1/chain/get_info instead of a valid chain-api response. The server or its upstream node is failing. Check the node, the proxy and the server logs. | 116 ms | ブロック | |
| 無効 | 不明 | HTTP 503 on /v1/chain/get_info instead of a valid chain-api response. The server or its upstream node is failing. Check the node, the proxy and the server logs. | 135 ms | ブロック | |
| 無効 | 不明 | HTTP 503 on /v1/chain/get_info instead of a valid chain-api response. The server or its upstream node is failing. Check the node, the proxy and the server logs. | 128 ms | ブロック | |
| 無効 | 不明 | HTTP 503 on /v1/chain/get_info instead of a valid chain-api response. The server or its upstream node is failing. Check the node, the proxy and the server logs. | 118 ms | ブロック | |
| 無効 | 不明 | HTTP 503 on /v1/chain/get_info instead of a valid chain-api response. The server or its upstream node is failing. Check the node, the proxy and the server logs. | 130 ms | ブロック | |
| 無効 | 不明 | HTTP 503 on /v1/chain/get_info instead of a valid chain-api response. The server or its upstream node is failing. Check the node, the proxy and the server logs. | 109 ms | ブロック | |
| 無効 | 不明 | HTTP 503 on /v1/chain/get_info instead of a valid chain-api response. The server or its upstream node is failing. Check the node, the proxy and the server logs. | 131 ms | ブロック | |
| 無効 | 不明 | HTTP 503 on /v1/chain/get_info instead of a valid chain-api response. The server or its upstream node is failing. Check the node, the proxy and the server logs. | 130 ms | ブロック | |
| 無効 | 不明 | HTTP 503 on /v1/chain/get_info instead of a valid chain-api response. The server or its upstream node is failing. Check the node, the proxy and the server logs. | 124 ms | ブロック | |
| 無効 | 不明 | HTTP 503 on /v1/chain/get_info instead of a valid chain-api response. The server or its upstream node is failing. Check the node, the proxy and the server logs. | 114 ms | ブロック | |
| 無効 | 不明 | HTTP 503 on /v1/chain/get_info instead of a valid chain-api response. The server or its upstream node is failing. Check the node, the proxy and the server logs. | 106 ms | ブロック | |
| 無効 | 不明 | HTTP 503 on /v1/chain/get_info instead of a valid chain-api response. The server or its upstream node is failing. Check the node, the proxy and the server logs. | 116 ms | ブロック | |
| 無効 | 不明 | HTTP 503 on /v1/chain/get_info instead of a valid chain-api response. The server or its upstream node is failing. Check the node, the proxy and the server logs. | 106 ms | ブロック | |
| 無効 | 不明 | HTTP 503 on /v1/chain/get_info instead of a valid chain-api response. The server or its upstream node is failing. Check the node, the proxy and the server logs. | 112 ms | ブロック | |
| 無効 | 不明 | HTTP 503 on /v1/chain/get_info instead of a valid chain-api response. The server or its upstream node is failing. Check the node, the proxy and the server logs. | 121 ms | ブロック | |
| 無効 | 不明 | HTTP 503 on /v1/chain/get_info instead of a valid chain-api response. The server or its upstream node is failing. Check the node, the proxy and the server logs. | 107 ms | ブロック | |
| 無効 | 不明 | HTTP 503 on /v1/chain/get_info instead of a valid chain-api response. The server or its upstream node is failing. Check the node, the proxy and the server logs. | 107 ms | ブロック | |
| 無効 | 不明 | HTTP 503 on /v1/chain/get_info instead of a valid chain-api response. The server or its upstream node is failing. Check the node, the proxy and the server logs. | 111 ms | ブロック | |
| 無効 | 不明 | HTTP 503 on /v1/chain/get_info instead of a valid chain-api response. The server or its upstream node is failing. Check the node, the proxy and the server logs. | 110 ms | ブロック | |
| 無効 | 不明 | HTTP 503 on /v1/chain/get_info instead of a valid chain-api response. The server or its upstream node is failing. Check the node, the proxy and the server logs. | 134 ms | ブロック | |
| 無効 | 不明 | HTTP 503 on /v1/chain/get_info instead of a valid chain-api response. The server or its upstream node is failing. Check the node, the proxy and the server logs. | 122 ms | ブロック | |
| 無効 | 不明 | HTTP 503 on /v1/chain/get_info instead of a valid chain-api response. The server or its upstream node is failing. Check the node, the proxy and the server logs. | 122 ms | ブロック | |
| 無効 | 不明 | HTTP 503 on /v1/chain/get_info instead of a valid chain-api response. The server or its upstream node is failing. Check the node, the proxy and the server logs. | 127 ms | ブロック | |
| 無効 | 不明 | HTTP 503 on /v1/chain/get_info instead of a valid chain-api response. The server or its upstream node is failing. Check the node, the proxy and the server logs. | 139 ms | ブロック | |
| 無効 | 不明 | HTTP 503 on /v1/chain/get_info instead of a valid chain-api response. The server or its upstream node is failing. Check the node, the proxy and the server logs. | 130 ms | ブロック | |
| 無効 | 不明 | HTTP 503 on /v1/chain/get_info instead of a valid chain-api response. The server or its upstream node is failing. Check the node, the proxy and the server logs. | 139 ms | ブロック | |
| 無効 | 不明 | HTTP 503 on /v1/chain/get_info instead of a valid chain-api response. The server or its upstream node is failing. Check the node, the proxy and the server logs. | 135 ms | ブロック | |
| 無効 | 不明 | HTTP 503 on /v1/chain/get_info instead of a valid chain-api response. The server or its upstream node is failing. Check the node, the proxy and the server logs. | 116 ms | ブロック | |
| 無効 | 不明 | HTTP 503 on /v1/chain/get_info instead of a valid chain-api response. The server or its upstream node is failing. Check the node, the proxy and the server logs. | 137 ms | ブロック | |
| 無効 | 不明 | HTTP 503 on /v1/chain/get_info instead of a valid chain-api response. The server or its upstream node is failing. Check the node, the proxy and the server logs. | 115 ms | ブロック | |
| 無効 | 不明 | HTTP 503 on /v1/chain/get_info instead of a valid chain-api response. The server or its upstream node is failing. Check the node, the proxy and the server logs. | 128 ms | ブロック | |
| 無効 | 不明 | HTTP 503 on /v1/chain/get_info instead of a valid chain-api response. The server or its upstream node is failing. Check the node, the proxy and the server logs. | 146 ms | ブロック | |
| 無効 | 不明 | HTTP 503 on /v1/chain/get_info instead of a valid chain-api response. The server or its upstream node is failing. Check the node, the proxy and the server logs. | 141 ms | ブロック | |
| 無効 | 不明 | HTTP 503 on /v1/chain/get_info instead of a valid chain-api response. The server or its upstream node is failing. Check the node, the proxy and the server logs. | 156 ms | ブロック | |
| 無効 | 不明 | HTTP 503 on /v1/chain/get_info instead of a valid chain-api response. The server or its upstream node is failing. Check the node, the proxy and the server logs. | 124 ms | ブロック | |
| 無効 | 不明 | HTTP 503 on /v1/chain/get_info instead of a valid chain-api response. The server or its upstream node is failing. Check the node, the proxy and the server logs. | 150 ms | ブロック | |
| 無効 | 不明 | HTTP 503 on /v1/chain/get_info instead of a valid chain-api response. The server or its upstream node is failing. Check the node, the proxy and the server logs. | 143 ms | ブロック |