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.

52.5% 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, 08:50
Latência: 620 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	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
Saudável	Leap v5.0.3wax01	Chain API responded normally	621 ms	Permitidos	30 de out. de 2026, 08:10
Saudável	Leap v5.0.3wax01	Chain API responded normally	621 ms	Permitidos	30 de out. de 2026, 07:50
Saudável	Leap v5.0.3wax01	Chain API responded normally	618 ms	Permitidos	30 de out. de 2026, 07:30
Saudável	Leap v5.0.3wax01	Chain API responded normally	651 ms	Permitidos	30 de out. de 2026, 07:10
Saudável	Leap v5.0.3wax01	Chain API responded normally	620 ms	Permitidos	30 de out. de 2026, 06:50
Saudável	Leap v5.0.3wax01	Chain API responded normally	617 ms	Permitidos	30 de out. de 2026, 06:30
Saudável	Leap v5.0.3wax01	Chain API responded normally	609 ms	Permitidos	30 de out. de 2026, 06:10
Saudável	Leap v5.0.3wax01	Chain API responded normally	620 ms	Permitidos	30 de out. de 2026, 05:50

Account Query

Saudável

account-query responded normally

Verificado: 30 de out. de 2026, 08:50
Latência: 888 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	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
Saudável	Leap v5.0.3wax01	account-query responded normally	634 ms	Permitidos	30 de out. de 2026, 08:10
Saudável	Leap v5.0.3wax01	account-query responded normally	652 ms	Permitidos	30 de out. de 2026, 07:50
Saudável	Leap v5.0.3wax01	account-query responded normally	650 ms	Permitidos	30 de out. de 2026, 07:30
Saudável	Leap v5.0.3wax01	account-query responded normally	669 ms	Permitidos	30 de out. de 2026, 07:10
Saudável	Leap v5.0.3wax01	account-query responded normally	698 ms	Permitidos	30 de out. de 2026, 06:50
Saudável	Leap v5.0.3wax01	account-query responded normally	684 ms	Permitidos	30 de out. de 2026, 06:30
Saudável	Leap v5.0.3wax01	account-query responded normally	645 ms	Permitidos	30 de out. de 2026, 06:10
Saudável	Leap v5.0.3wax01	account-query responded normally	669 ms	Permitidos	30 de out. de 2026, 05:50

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, 08:50
Latência: 624 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.	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
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, 08: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.	608 ms	Permitidos	30 de out. de 2026, 07: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.	635 ms	Permitidos	30 de out. de 2026, 07: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.	662 ms	Permitidos	30 de out. de 2026, 07: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.	628 ms	Permitidos	30 de out. de 2026, 06: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.	619 ms	Permitidos	30 de out. de 2026, 06: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.	632 ms	Permitidos	30 de out. de 2026, 06: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.	615 ms	Permitidos	30 de out. de 2026, 05:50

Hyperion API

Desatualizado

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

Verificado: 30 de out. de 2026, 08:50
Latência: 627 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 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
Desatualizado	3.5.0-5	Indexer is 697650 blocks behind the chain head (limit 180). Check that it is keeping up with nodeos.	606 ms	Permitidos	30 de out. de 2026, 08:10
Desatualizado	3.5.0-5	Indexer is 695238 blocks behind the chain head (limit 180). Check that it is keeping up with nodeos.	627 ms	Permitidos	30 de out. de 2026, 07:50
Desatualizado	3.5.0-5	Indexer is 692840 blocks behind the chain head (limit 180). Check that it is keeping up with nodeos.	601 ms	Permitidos	30 de out. de 2026, 07:30
Desatualizado	3.5.0-5	Indexer is 690461 blocks behind the chain head (limit 180). Check that it is keeping up with nodeos.	656 ms	Permitidos	30 de out. de 2026, 07:10
Desatualizado	3.5.0-5	Indexer is 688051 blocks behind the chain head (limit 180). Check that it is keeping up with nodeos.	631 ms	Permitidos	30 de out. de 2026, 06:50
Desatualizado	3.5.0-5	Indexer is 685638 blocks behind the chain head (limit 180). Check that it is keeping up with nodeos.	608 ms	Permitidos	30 de out. de 2026, 06:30
Desatualizado	3.5.0-5	Indexer is 683250 blocks behind the chain head (limit 180). Check that it is keeping up with nodeos.	622 ms	Permitidos	30 de out. de 2026, 06:10
Desatualizado	3.5.0-5	Indexer is 680850 blocks behind the chain head (limit 180). Check that it is keeping up with nodeos.	627 ms	Permitidos	30 de out. de 2026, 05:50