Uptime history
Healthy and degraded checks across monitored features. Gaps are excluded from uptime.
0.0% uptime
All
Antelope node health, status, and history for operators and developers.
f16b1833c747c43682f4386fca9cbb327929334a762755ebec17f6f23c9b8a12
Health, freshness, CORS, and recent check history for this endpoint.
Healthy and degraded checks across monitored features. Gaps are excluded from uptime.
0.0% uptime
All
No response within 5s. The server is down, overloaded, or a firewall is dropping connections.
Request never completed
| Status | Version | Summary | Latency | CORS | Checked |
|---|---|---|---|---|---|
| Down | Unknown | No response within 5s. The server is down, overloaded, or a firewall is dropping connections. | — | Blocked | |
| Down | Unknown | No response within 5s. The server is down, overloaded, or a firewall is dropping connections. | — | Blocked | |
| Down | Unknown | No response within 5s. The server is down, overloaded, or a firewall is dropping connections. | — | Blocked | |
| Down | Unknown | No response within 5s. The server is down, overloaded, or a firewall is dropping connections. | — | Blocked | |
| Down | Unknown | No response within 5s. The server is down, overloaded, or a firewall is dropping connections. | — | Blocked | |
| Down | Unknown | No response within 5s. The server is down, overloaded, or a firewall is dropping connections. | — | Blocked | |
| Down | Unknown | No response within 5s. The server is down, overloaded, or a firewall is dropping connections. | — | Blocked | |
| Down | Unknown | No response within 5s. The server is down, overloaded, or a firewall is dropping connections. | — | Blocked | |
| Down | Unknown | No response within 5s. The server is down, overloaded, or a firewall is dropping connections. | — | Blocked | |
| Down | Unknown | No response within 5s. The server is down, overloaded, or a firewall is dropping connections. | — | Blocked |
No response within 5s. The server is down, overloaded, or a firewall is dropping connections.
Request never completed
| Status | Version | Summary | Latency | CORS | Checked |
|---|---|---|---|---|---|
| Down | Unknown | No response within 5s. The server is down, overloaded, or a firewall is dropping connections. | — | Blocked | |
| Down | Unknown | No response within 5s. The server is down, overloaded, or a firewall is dropping connections. | — | Blocked | |
| Down | Unknown | No response within 5s. The server is down, overloaded, or a firewall is dropping connections. | — | Blocked | |
| Down | Unknown | No response within 5s. The server is down, overloaded, or a firewall is dropping connections. | — | Blocked | |
| Down | Unknown | No response within 5s. The server is down, overloaded, or a firewall is dropping connections. | — | Blocked | |
| Down | Unknown | No response within 5s. The server is down, overloaded, or a firewall is dropping connections. | — | Blocked | |
| Down | Unknown | No response within 5s. The server is down, overloaded, or a firewall is dropping connections. | — | Blocked | |
| Down | Unknown | No response within 5s. The server is down, overloaded, or a firewall is dropping connections. | — | Blocked | |
| Down | Unknown | No response within 5s. The server is down, overloaded, or a firewall is dropping connections. | — | Blocked | |
| Down | Unknown | No response within 5s. The server is down, overloaded, or a firewall is dropping connections. | — | Blocked |
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.
| Status | Version | Summary | Latency | CORS | Checked |
|---|---|---|---|---|---|
| Invalid | Unknown | 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. | 89 ms | Blocked | |
| Invalid | Unknown | 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. | 241 ms | Blocked | |
| Invalid | Unknown | 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 ms | Blocked | |
| Invalid | Unknown | 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 ms | Blocked | |
| Invalid | Unknown | 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 ms | Blocked | |
| Invalid | Unknown | 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 | Blocked | |
| Invalid | Unknown | 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 ms | Blocked | |
| Invalid | Unknown | 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 ms | Blocked | |
| Invalid | Unknown | 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 ms | Blocked | |
| Invalid | Unknown | 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 | Blocked |
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.
| Status | Version | Summary | Latency | CORS | Checked |
|---|---|---|---|---|---|
| Invalid | Unknown | 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 | Blocked | |
| Invalid | Unknown | 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. | 239 ms | Blocked | |
| Invalid | Unknown | 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 | Blocked | |
| Invalid | Unknown | 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 ms | Blocked | |
| Invalid | Unknown | 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 ms | Blocked | |
| Invalid | Unknown | 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 ms | Blocked | |
| Invalid | Unknown | 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 ms | Blocked | |
| Invalid | Unknown | 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 ms | Blocked | |
| Invalid | Unknown | 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 ms | Blocked | |
| Invalid | Unknown | 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 | Blocked |