Historique de disponibilité
Contrôles sains et dégradés des fonctions surveillées. Les périodes sans données sont exclues.
0.0 % de disponibilité
6 mois
Santé, état et historique des nœuds Antelope pour les opérateurs et les développeurs.
f16b1833c747c43682f4386fca9cbb327929334a762755ebec17f6f23c9b8a12
Santé, fraîcheur, CORS et historique récent des contrôles pour cet endpoint.
Contrôles sains et dégradés des fonctions surveillées. Les périodes sans données sont exclues.
0.0 % de disponibilité
6 mois
No response within 5s. The server is down, overloaded, or a firewall is dropping connections.
Request never completed
| État | Version | Résumé | Latence | CORS | Vérifié |
|---|---|---|---|---|---|
| Hors service | Inconnue | No response within 5s. The server is down, overloaded, or a firewall is dropping connections. | — | Bloquées | |
| Hors service | Inconnue | No response within 5s. The server is down, overloaded, or a firewall is dropping connections. | — | Bloquées | |
| Hors service | Inconnue | No response within 5s. The server is down, overloaded, or a firewall is dropping connections. | — | Bloquées | |
| Hors service | Inconnue | No response within 5s. The server is down, overloaded, or a firewall is dropping connections. | — | Bloquées | |
| Hors service | Inconnue | No response within 5s. The server is down, overloaded, or a firewall is dropping connections. | — | Bloquées | |
| Hors service | Inconnue | No response within 5s. The server is down, overloaded, or a firewall is dropping connections. | — | Bloquées | |
| Hors service | Inconnue | No response within 5s. The server is down, overloaded, or a firewall is dropping connections. | — | Bloquées | |
| Hors service | Inconnue | No response within 5s. The server is down, overloaded, or a firewall is dropping connections. | — | Bloquées | |
| Hors service | Inconnue | No response within 5s. The server is down, overloaded, or a firewall is dropping connections. | — | Bloquées | |
| Hors service | Inconnue | No response within 5s. The server is down, overloaded, or a firewall is dropping connections. | — | Bloquées |
No response within 5s. The server is down, overloaded, or a firewall is dropping connections.
Request never completed
| État | Version | Résumé | Latence | CORS | Vérifié |
|---|---|---|---|---|---|
| Hors service | Inconnue | No response within 5s. The server is down, overloaded, or a firewall is dropping connections. | — | Bloquées | |
| Hors service | Inconnue | No response within 5s. The server is down, overloaded, or a firewall is dropping connections. | — | Bloquées | |
| Hors service | Inconnue | No response within 5s. The server is down, overloaded, or a firewall is dropping connections. | — | Bloquées | |
| Hors service | Inconnue | No response within 5s. The server is down, overloaded, or a firewall is dropping connections. | — | Bloquées | |
| Hors service | Inconnue | No response within 5s. The server is down, overloaded, or a firewall is dropping connections. | — | Bloquées | |
| Hors service | Inconnue | No response within 5s. The server is down, overloaded, or a firewall is dropping connections. | — | Bloquées | |
| Hors service | Inconnue | No response within 5s. The server is down, overloaded, or a firewall is dropping connections. | — | Bloquées | |
| Hors service | Inconnue | No response within 5s. The server is down, overloaded, or a firewall is dropping connections. | — | Bloquées | |
| Hors service | Inconnue | No response within 5s. The server is down, overloaded, or a firewall is dropping connections. | — | Bloquées | |
| Hors service | Inconnue | No response within 5s. The server is down, overloaded, or a firewall is dropping connections. | — | Bloquées |
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.
| État | Version | Résumé | Latence | CORS | Vérifié |
|---|---|---|---|---|---|
| Invalide | Inconnue | 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 | Bloquées | |
| Invalide | Inconnue | 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 | Bloquées | |
| Invalide | Inconnue | 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 | Bloquées | |
| Invalide | Inconnue | 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 | Bloquées | |
| Invalide | Inconnue | 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 | Bloquées | |
| Invalide | Inconnue | 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 | Bloquées | |
| Invalide | Inconnue | 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 | Bloquées | |
| Invalide | Inconnue | 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 | Bloquées | |
| Invalide | Inconnue | 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 | Bloquées | |
| Invalide | Inconnue | 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 ms | Bloquées |
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.
| État | Version | Résumé | Latence | CORS | Vérifié |
|---|---|---|---|---|---|
| Invalide | Inconnue | 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 | Bloquées | |
| Invalide | Inconnue | 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 | Bloquées | |
| Invalide | Inconnue | 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 | Bloquées | |
| Invalide | Inconnue | 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 | Bloquées | |
| Invalide | Inconnue | 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 | Bloquées | |
| Invalide | Inconnue | 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 | Bloquées | |
| Invalide | Inconnue | 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 | Bloquées | |
| Invalide | Inconnue | 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 | Bloquées | |
| Invalide | Inconnue | 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 | Bloquées | |
| Invalide | Inconnue | 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 ms | Bloquées |