可用性历史
所有监控功能中健康和降级检查的比例。无数据时段不计入可用性。
可用性 0.0%
1年
面向运营者与开发者的 Antelope 节点健康、状态与历史监控。
f16b1833c747c43682f4386fca9cbb327929334a762755ebec17f6f23c9b8a12
此端点的健康、新鲜度、CORS 与近期检查历史。
所有监控功能中健康和降级检查的比例。无数据时段不计入可用性。
可用性 0.0%
1年
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. | 70 毫秒 | 阻止 | |
| 无效 | 未知 | 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. | 247 毫秒 | 阻止 | |
| 无效 | 未知 | 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. | 165 毫秒 | 阻止 | |
| 无效 | 未知 | 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 毫秒 | 阻止 | |
| 无效 | 未知 | 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. | 141 毫秒 | 阻止 | |
| 无效 | 未知 | 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. | 105 毫秒 | 阻止 | |
| 无效 | 未知 | 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. | 138 毫秒 | 阻止 | |
| 无效 | 未知 | 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 毫秒 | 阻止 | |
| 无效 | 未知 | 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. | 158 毫秒 | 阻止 | |
| 无效 | 未知 | 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. | 159 毫秒 | 阻止 |
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. | 70 毫秒 | 阻止 | |
| 无效 | 未知 | 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. | 192 毫秒 | 阻止 | |
| 无效 | 未知 | 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. | 130 毫秒 | 阻止 | |
| 无效 | 未知 | 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. | 137 毫秒 | 阻止 | |
| 无效 | 未知 | 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. | 92 毫秒 | 阻止 | |
| 无效 | 未知 | 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. | 79 毫秒 | 阻止 | |
| 无效 | 未知 | 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. | 109 毫秒 | 阻止 | |
| 无效 | 未知 | 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 毫秒 | 阻止 | |
| 无效 | 未知 | 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. | 153 毫秒 | 阻止 | |
| 无效 | 未知 | 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. | 130 毫秒 | 阻止 |