WAX Mainnet

1064487b3cd1a897ce03ae5b6a865651747e2e152090f99c1d19d44e01aea5a4

https://wax.eosrio.io

Saúde, atualidade, CORS e histórico recente de verificações deste endpoint.

Produtor: eosriobrazil
Cadeia: WAX Mainnet
Histórico da cadeia declarado: Parcial
Localização: Rio de Janeiro

Histórico de disponibilidade

Verificações saudáveis e degradadas das funcionalidades monitorizadas. Os períodos sem dados são excluídos.

57.2% de disponibilidade

14 dias

16 de out. de 2026, 11 UTCCinzento: sem verificações registadasAgora

Estado atual dos serviços

Chain API

Saudável

Chain API responded normally

Verificado: 30 de out. de 2026, 11:30
Latência: 623 ms
Pedidos do navegador: Permitidos
Versão: Leap v5.0.3wax01

Verificações recentes

Últimas verificações de saúde de Chain API armazenadas.
Status	Versão	Resumo	Latência	CORS	Verificado
Saudável	Leap v5.0.3wax01	Chain API responded normally	623 ms	Permitidos	30 de out. de 2026, 11:30
Saudável	Leap v5.0.3wax01	Chain API responded normally	595 ms	Permitidos	30 de out. de 2026, 11:10
Saudável	Leap v5.0.3wax01	Chain API responded normally	626 ms	Permitidos	30 de out. de 2026, 10:50
Saudável	Leap v5.0.3wax01	Chain API responded normally	598 ms	Permitidos	30 de out. de 2026, 10:30
Saudável	Leap v5.0.3wax01	Chain API responded normally	613 ms	Permitidos	30 de out. de 2026, 10:10
Saudável	Leap v5.0.3wax01	Chain API responded normally	628 ms	Permitidos	30 de out. de 2026, 09:50
Saudável	Leap v5.0.3wax01	Chain API responded normally	596 ms	Permitidos	30 de out. de 2026, 09:30
Saudável	Leap v5.0.3wax01	Chain API responded normally	623 ms	Permitidos	30 de out. de 2026, 09:10
Saudável	Leap v5.0.3wax01	Chain API responded normally	620 ms	Permitidos	30 de out. de 2026, 08:50
Saudável	Leap v5.0.3wax01	Chain API responded normally	616 ms	Permitidos	30 de out. de 2026, 08:30

Account Query

Saudável

account-query responded normally

Verificado: 30 de out. de 2026, 11:30
Latência: 642 ms
Pedidos do navegador: Permitidos
Versão: Leap v5.0.3wax01

Verificações recentes

Últimas verificações de saúde de Account Query armazenadas.
Status	Versão	Resumo	Latência	CORS	Verificado
Saudável	Leap v5.0.3wax01	account-query responded normally	642 ms	Permitidos	30 de out. de 2026, 11:30
Saudável	Leap v5.0.3wax01	account-query responded normally	693 ms	Permitidos	30 de out. de 2026, 11:10
Saudável	Leap v5.0.3wax01	account-query responded normally	666 ms	Permitidos	30 de out. de 2026, 10:50
Saudável	Leap v5.0.3wax01	account-query responded normally	653 ms	Permitidos	30 de out. de 2026, 10:30
Saudável	Leap v5.0.3wax01	account-query responded normally	623 ms	Permitidos	30 de out. de 2026, 10:10
Saudável	Leap v5.0.3wax01	account-query responded normally	1698 ms	Permitidos	30 de out. de 2026, 09:50
Saudável	Leap v5.0.3wax01	account-query responded normally	675 ms	Permitidos	30 de out. de 2026, 09:30
Saudável	Leap v5.0.3wax01	account-query responded normally	675 ms	Permitidos	30 de out. de 2026, 09:10
Saudável	Leap v5.0.3wax01	account-query responded normally	888 ms	Permitidos	30 de out. de 2026, 08:50
Saudável	Leap v5.0.3wax01	account-query responded normally	687 ms	Permitidos	30 de out. de 2026, 08:30

History API

Inválido

HTTP 404 on /v1/history/get_actions. The server has no route for this history-v1 check, so the advertised feature is not actually served. Fix the proxy routing or remove the feature from bp.json.

Verificado: 30 de out. de 2026, 11:30
Latência: 637 ms
Pedidos do navegador: Permitidos
Versão: Leap v5.0.3wax01

Verificações recentes

Últimas verificações de saúde de History API armazenadas.
Status	Versão	Resumo	Latência	CORS	Verificado
Inválido	Leap v5.0.3wax01	HTTP 404 on /v1/history/get_actions. The server has no route for this history-v1 check, so the advertised feature is not actually served. Fix the proxy routing or remove the feature from bp.json.	637 ms	Permitidos	30 de out. de 2026, 11:30
Inválido	Leap v5.0.3wax01	HTTP 404 on /v1/history/get_actions. The server has no route for this history-v1 check, so the advertised feature is not actually served. Fix the proxy routing or remove the feature from bp.json.	633 ms	Permitidos	30 de out. de 2026, 11:10
Inválido	Leap v5.0.3wax01	HTTP 404 on /v1/history/get_actions. The server has no route for this history-v1 check, so the advertised feature is not actually served. Fix the proxy routing or remove the feature from bp.json.	636 ms	Permitidos	30 de out. de 2026, 10:50
Inválido	Leap v5.0.3wax01	HTTP 404 on /v1/history/get_actions. The server has no route for this history-v1 check, so the advertised feature is not actually served. Fix the proxy routing or remove the feature from bp.json.	632 ms	Permitidos	30 de out. de 2026, 10:30
Inválido	Leap v5.0.3wax01	HTTP 404 on /v1/history/get_actions. The server has no route for this history-v1 check, so the advertised feature is not actually served. Fix the proxy routing or remove the feature from bp.json.	612 ms	Permitidos	30 de out. de 2026, 10:10
Inválido	Leap v5.0.3wax01	HTTP 404 on /v1/history/get_actions. The server has no route for this history-v1 check, so the advertised feature is not actually served. Fix the proxy routing or remove the feature from bp.json.	612 ms	Permitidos	30 de out. de 2026, 09:50
Inválido	Leap v5.0.3wax01	HTTP 404 on /v1/history/get_actions. The server has no route for this history-v1 check, so the advertised feature is not actually served. Fix the proxy routing or remove the feature from bp.json.	631 ms	Permitidos	30 de out. de 2026, 09:30
Inválido	Leap v5.0.3wax01	HTTP 404 on /v1/history/get_actions. The server has no route for this history-v1 check, so the advertised feature is not actually served. Fix the proxy routing or remove the feature from bp.json.	604 ms	Permitidos	30 de out. de 2026, 09:10
Inválido	Leap v5.0.3wax01	HTTP 404 on /v1/history/get_actions. The server has no route for this history-v1 check, so the advertised feature is not actually served. Fix the proxy routing or remove the feature from bp.json.	624 ms	Permitidos	30 de out. de 2026, 08:50
Inválido	Leap v5.0.3wax01	HTTP 404 on /v1/history/get_actions. The server has no route for this history-v1 check, so the advertised feature is not actually served. Fix the proxy routing or remove the feature from bp.json.	631 ms	Permitidos	30 de out. de 2026, 08:30

Hyperion API

Desatualizado

Indexer is 721650 blocks behind the chain head (limit 180). Check that it is keeping up with nodeos.

Verificado: 30 de out. de 2026, 11:30
Latência: 640 ms
Pedidos do navegador: Permitidos
Versão: 3.5.0-5

Verificações recentes

Últimas verificações de saúde de Hyperion API armazenadas.
Status	Versão	Resumo	Latência	CORS	Verificado
Desatualizado	3.5.0-5	Indexer is 721650 blocks behind the chain head (limit 180). Check that it is keeping up with nodeos.	640 ms	Permitidos	30 de out. de 2026, 11:30
Desatualizado	3.5.0-5	Indexer is 719251 blocks behind the chain head (limit 180). Check that it is keeping up with nodeos.	671 ms	Permitidos	30 de out. de 2026, 11:10
Desatualizado	3.5.0-5	Indexer is 716852 blocks behind the chain head (limit 180). Check that it is keeping up with nodeos.	627 ms	Permitidos	30 de out. de 2026, 10:50
Desatualizado	3.5.0-5	Indexer is 714437 blocks behind the chain head (limit 180). Check that it is keeping up with nodeos.	626 ms	Permitidos	30 de out. de 2026, 10:30
Desatualizado	3.5.0-5	Indexer is 712051 blocks behind the chain head (limit 180). Check that it is keeping up with nodeos.	627 ms	Permitidos	30 de out. de 2026, 10:10
Desatualizado	3.5.0-5	Indexer is 709640 blocks behind the chain head (limit 180). Check that it is keeping up with nodeos.	610 ms	Permitidos	30 de out. de 2026, 09:50
Desatualizado	3.5.0-5	Indexer is 707240 blocks behind the chain head (limit 180). Check that it is keeping up with nodeos.	613 ms	Permitidos	30 de out. de 2026, 09:30
Desatualizado	3.5.0-5	Indexer is 704850 blocks behind the chain head (limit 180). Check that it is keeping up with nodeos.	635 ms	Permitidos	30 de out. de 2026, 09:10
Desatualizado	3.5.0-5	Indexer is 702437 blocks behind the chain head (limit 180). Check that it is keeping up with nodeos.	627 ms	Permitidos	30 de out. de 2026, 08:50
Desatualizado	3.5.0-5	Indexer is 700038 blocks behind the chain head (limit 180). Check that it is keeping up with nodeos.	613 ms	Permitidos	30 de out. de 2026, 08:30