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

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

Estado atual dos serviços

Chain API

Saudável

Chain API responded normally

Verificado: 30 de out. de 2026, 05:50
Latência: 111 ms
Pedidos do navegador: Permitidos
Versão: Spring v1.2.3-alpha1

Verificações recentes

Últimas verificações de saúde de Chain API armazenadas.
Status	Versão	Resumo	Latência	CORS	Verificado
Saudável	Spring v1.2.3-alpha1	Chain API responded normally	111 ms	Permitidos	30 de out. de 2026, 05:50
Saudável	Spring v1.2.3-alpha1	Chain API responded normally	113 ms	Permitidos	30 de out. de 2026, 05:30
Saudável	Spring v1.2.3-alpha1	Chain API responded normally	107 ms	Permitidos	30 de out. de 2026, 05:10
Saudável	Spring v1.2.3-alpha1	Chain API responded normally	109 ms	Permitidos	30 de out. de 2026, 04:50
Saudável	Spring v1.2.3-alpha1	Chain API responded normally	105 ms	Permitidos	30 de out. de 2026, 04:30
Saudável	Spring v1.2.3-alpha1	Chain API responded normally	110 ms	Permitidos	30 de out. de 2026, 04:10
Saudável	Spring v1.2.3-alpha1	Chain API responded normally	110 ms	Permitidos	30 de out. de 2026, 03:50
Saudável	Spring v1.2.3-alpha1	Chain API responded normally	116 ms	Permitidos	30 de out. de 2026, 03:30
Saudável	Spring v1.2.3-alpha1	Chain API responded normally	109 ms	Permitidos	30 de out. de 2026, 03:10
Saudável	Spring v1.2.3-alpha1	Chain API responded normally	103 ms	Permitidos	30 de out. de 2026, 02:50

Account Query

Saudável

account-query responded normally

Verificado: 30 de out. de 2026, 05:50
Latência: 366 ms
Pedidos do navegador: Permitidos
Versão: Spring v1.2.3-alpha1

Verificações recentes

Últimas verificações de saúde de Account Query armazenadas.
Status	Versão	Resumo	Latência	CORS	Verificado
Saudável	Spring v1.2.3-alpha1	account-query responded normally	366 ms	Permitidos	30 de out. de 2026, 05:50
Saudável	Spring v1.2.3-alpha1	account-query responded normally	364 ms	Permitidos	30 de out. de 2026, 05:30
Saudável	Spring v1.2.3-alpha1	account-query responded normally	335 ms	Permitidos	30 de out. de 2026, 05:10
Saudável	Spring v1.2.3-alpha1	account-query responded normally	357 ms	Permitidos	30 de out. de 2026, 04:50
Saudável	Spring v1.2.3-alpha1	account-query responded normally	362 ms	Permitidos	30 de out. de 2026, 04:30
Saudável	Spring v1.2.3-alpha1	account-query responded normally	370 ms	Permitidos	30 de out. de 2026, 04:10
Saudável	Spring v1.2.3-alpha1	account-query responded normally	349 ms	Permitidos	30 de out. de 2026, 03:50
Saudável	Spring v1.2.3-alpha1	account-query responded normally	349 ms	Permitidos	30 de out. de 2026, 03:30
Saudável	Spring v1.2.3-alpha1	account-query responded normally	374 ms	Permitidos	30 de out. de 2026, 03:10
Saudável	Spring v1.2.3-alpha1	account-query responded normally	338 ms	Permitidos	30 de out. de 2026, 02:50

History API

Inválido

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.

Verificado: 30 de out. de 2026, 05:50
Latência: 320 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

Últimas verificações de saúde de History API armazenadas.
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.	320 ms	Bloqueados	30 de out. de 2026, 05:50
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	30 de out. de 2026, 05:30
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.	106 ms	Bloqueados	30 de out. de 2026, 05:10
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.	109 ms	Bloqueados	30 de out. de 2026, 04:50
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.	337 ms	Bloqueados	30 de out. de 2026, 04:30
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.	342 ms	Bloqueados	30 de out. de 2026, 04:10
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.	341 ms	Bloqueados	30 de out. de 2026, 03:50
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.	332 ms	Bloqueados	30 de out. de 2026, 03:30
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.	343 ms	Bloqueados	30 de out. de 2026, 03:10
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.	102 ms	Bloqueados	30 de out. de 2026, 02:50

Hyperion API

Inválido

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.

Verificado: 30 de out. de 2026, 05:50
Latência: 112 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

Últimas verificações de saúde de Hyperion API armazenadas.
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.	112 ms	Bloqueados	30 de out. de 2026, 05:50
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.	332 ms	Bloqueados	30 de out. de 2026, 05:30
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	30 de out. de 2026, 05:10
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.	334 ms	Bloqueados	30 de out. de 2026, 04:50
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.	105 ms	Bloqueados	30 de out. de 2026, 04:30
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	30 de out. de 2026, 04:10
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.	119 ms	Bloqueados	30 de out. de 2026, 03:50
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.	110 ms	Bloqueados	30 de out. de 2026, 03:30
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.	108 ms	Bloqueados	30 de out. de 2026, 03:10
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.	322 ms	Bloqueados	30 de out. de 2026, 02:50