Histórico de disponibilidade
Verificações saudáveis e degradadas das funcionalidades monitorizadas. Os períodos sem dados são excluídos.
49.2% de disponibilidade
1 mês
1 de out. de 2026 UTCCinzento: sem verificações registadasAgora
Jungle Testnet
73e4385a2708e6d7048834fbc1079f2fabb17b3c125b146af438971e90716c4d
https://jungle.eosusa.io
Saúde, atualidade, CORS e histórico recente de verificações deste endpoint.
- Produtor
- ivote4eosusa
- Cadeia
- Jungle Testnet
- Histórico da cadeia declarado
- Completo
- Localização
- Greenville,SC,USA
Estado atual dos serviços
Chain API
SaudávelChain API responded normally
- Verificado
- Latência
- 113 ms
- Pedidos do navegador
- Permitidos
- Versão
- Spring v1.2.3-alpha1
Verificações recentes
| Status | Versão | Resumo | Latência | CORS | Verificado |
|---|---|---|---|---|---|
| Saudável | Spring v1.2.3-alpha1 | Chain API responded normally | 113 ms | Permitidos | |
| Saudável | Spring v1.2.3-alpha1 | Chain API responded normally | 108 ms | Permitidos | |
| Saudável | Spring v1.2.3-alpha1 | Chain API responded normally | 113 ms | Permitidos | |
| Saudável | Spring v1.2.3-alpha1 | Chain API responded normally | 112 ms | Permitidos | |
| Saudável | Spring v1.2.3-alpha1 | Chain API responded normally | 114 ms | Permitidos | |
| Saudável | Spring v1.2.3-alpha1 | Chain API responded normally | 113 ms | Permitidos | |
| Saudável | Spring v1.2.3-alpha1 | Chain API responded normally | 114 ms | Permitidos | |
| Saudável | Spring v1.2.3-alpha1 | Chain API responded normally | 347 ms | Permitidos | |
| Saudável | Spring v1.2.3-alpha1 | Chain API responded normally | 109 ms | Permitidos | |
| Saudável | Spring v1.2.3-alpha1 | Chain API responded normally | 345 ms | Permitidos |
Account Query
Saudávelaccount-query responded normally
- Verificado
- Latência
- 358 ms
- Pedidos do navegador
- Permitidos
- Versão
- Spring v1.2.3-alpha1
Verificações recentes
| Status | Versão | Resumo | Latência | CORS | Verificado |
|---|---|---|---|---|---|
| Saudável | Spring v1.2.3-alpha1 | account-query responded normally | 358 ms | Permitidos | |
| Saudável | Spring v1.2.3-alpha1 | account-query responded normally | 344 ms | Permitidos | |
| Saudável | Spring v1.2.3-alpha1 | account-query responded normally | 375 ms | Permitidos | |
| Saudável | Spring v1.2.3-alpha1 | account-query responded normally | 347 ms | Permitidos | |
| Saudável | Spring v1.2.3-alpha1 | account-query responded normally | 350 ms | Permitidos | |
| Saudável | Spring v1.2.3-alpha1 | account-query responded normally | 367 ms | Permitidos | |
| Saudável | Spring v1.2.3-alpha1 | account-query responded normally | 350 ms | Permitidos | |
| Saudável | Spring v1.2.3-alpha1 | account-query responded normally | 873 ms | Permitidos | |
| Saudável | Spring v1.2.3-alpha1 | account-query responded normally | 389 ms | Permitidos | |
| Saudável | Spring v1.2.3-alpha1 | account-query responded normally | 358 ms | Permitidos |
History API
InválidoHTTP 503 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.
- Verificado
- Latência
- 328 ms
- Pedidos do navegador
- Bloqueados
- Versão
- Spring v1.2.3-alpha1
Response Access-Control-Allow-Origin is missing. It must be "*" or echo the request Origin, otherwise browser apps cannot read the response.
Verificações recentes
| Status | Versão | Resumo | Latência | CORS | Verificado |
|---|---|---|---|---|---|
| Inválido | Spring v1.2.3-alpha1 | HTTP 503 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. | 328 ms | Bloqueados | |
| Inválido | Spring v1.2.3-alpha1 | HTTP 503 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. | 104 ms | Bloqueados | |
| Inválido | Spring v1.2.3-alpha1 | HTTP 503 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. | 328 ms | Bloqueados | |
| Inválido | Spring v1.2.3-alpha1 | HTTP 503 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. | 112 ms | Bloqueados | |
| Inválido | Spring v1.2.3-alpha1 | HTTP 503 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. | 111 ms | Bloqueados | |
| Inválido | Spring v1.2.3-alpha1 | HTTP 503 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. | 115 ms | Bloqueados | |
| Inválido | Spring v1.2.3-alpha1 | HTTP 503 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. | 112 ms | Bloqueados | |
| Inválido | Spring v1.2.3-alpha1 | HTTP 503 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. | 113 ms | Bloqueados | |
| Inválido | Spring v1.2.3-alpha1 | HTTP 503 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. | 339 ms | Bloqueados | |
| Inválido | Spring v1.2.3-alpha1 | HTTP 503 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. | 113 ms | Bloqueados |
Hyperion API
InválidoHTTP 503 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.
- Verificado
- Latência
- 326 ms
- Pedidos do navegador
- Bloqueados
- Versão
- Desconhecida
Response Access-Control-Allow-Origin is missing. It must be "*" or echo the request Origin, otherwise browser apps cannot read the response.
Verificações recentes
| Status | Versão | Resumo | Latência | CORS | Verificado |
|---|---|---|---|---|---|
| Inválido | Desconhecida | HTTP 503 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. | 326 ms | Bloqueados | |
| Inválido | Desconhecida | HTTP 503 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. | 323 ms | Bloqueados | |
| Inválido | Desconhecida | HTTP 503 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. | 318 ms | Bloqueados | |
| Inválido | Desconhecida | HTTP 503 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. | 327 ms | Bloqueados | |
| Inválido | Desconhecida | HTTP 503 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. | 339 ms | Bloqueados | |
| Inválido | Desconhecida | HTTP 503 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. | 365 ms | Bloqueados | |
| Inválido | Desconhecida | HTTP 503 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. | 342 ms | Bloqueados | |
| Inválido | Desconhecida | HTTP 503 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. | 317 ms | Bloqueados | |
| Inválido | Desconhecida | HTTP 503 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 | Bloqueados | |
| Inválido | Desconhecida | HTTP 503 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. | 114 ms | Bloqueados |