WAX Mainnet

1064487b3cd1a897ce03ae5b6a865651747e2e152090f99c1d19d44e01aea5a4

https://wax.eosrio.io

Salud, frescura, CORS e historial reciente de comprobaciones de este endpoint.

Productor: eosriobrazil
Cadena: WAX Mainnet
Historial de cadena declarado: Parcial
Ubicación: Rio de Janeiro

Historial de disponibilidad

Comprobaciones saludables y degradadas de las funciones supervisadas. Se excluyen los periodos sin datos.

48.3% de disponibilidad

1 año

31 oct 2025 UTCGris: sin comprobaciones registradasAhora

Estado actual de los servicios

Chain API

Saludable

Chain API responded normally

Comprobado: 30 oct 2026, 10:30
Latencia: 598 ms
Solicitudes del navegador: Permitidas
Versión: Leap v5.0.3wax01

Comprobaciones recientes

Últimas comprobaciones de salud de Chain API almacenadas.
Estado	Versión	Resumen	Latencia	CORS	Comprobado
Saludable	Leap v5.0.3wax01	Chain API responded normally	598 ms	Permitidas	30 oct 2026, 10:30
Saludable	Leap v5.0.3wax01	Chain API responded normally	613 ms	Permitidas	30 oct 2026, 10:10
Saludable	Leap v5.0.3wax01	Chain API responded normally	628 ms	Permitidas	30 oct 2026, 9:50
Saludable	Leap v5.0.3wax01	Chain API responded normally	596 ms	Permitidas	30 oct 2026, 9:30
Saludable	Leap v5.0.3wax01	Chain API responded normally	623 ms	Permitidas	30 oct 2026, 9:10
Saludable	Leap v5.0.3wax01	Chain API responded normally	620 ms	Permitidas	30 oct 2026, 8:50
Saludable	Leap v5.0.3wax01	Chain API responded normally	616 ms	Permitidas	30 oct 2026, 8:30
Saludable	Leap v5.0.3wax01	Chain API responded normally	621 ms	Permitidas	30 oct 2026, 8:10
Saludable	Leap v5.0.3wax01	Chain API responded normally	621 ms	Permitidas	30 oct 2026, 7:50
Saludable	Leap v5.0.3wax01	Chain API responded normally	618 ms	Permitidas	30 oct 2026, 7:30

Account Query

Saludable

account-query responded normally

Comprobado: 30 oct 2026, 10:30
Latencia: 653 ms
Solicitudes del navegador: Permitidas
Versión: Leap v5.0.3wax01

Comprobaciones recientes

Últimas comprobaciones de salud de Account Query almacenadas.
Estado	Versión	Resumen	Latencia	CORS	Comprobado
Saludable	Leap v5.0.3wax01	account-query responded normally	653 ms	Permitidas	30 oct 2026, 10:30
Saludable	Leap v5.0.3wax01	account-query responded normally	623 ms	Permitidas	30 oct 2026, 10:10
Saludable	Leap v5.0.3wax01	account-query responded normally	1698 ms	Permitidas	30 oct 2026, 9:50
Saludable	Leap v5.0.3wax01	account-query responded normally	675 ms	Permitidas	30 oct 2026, 9:30
Saludable	Leap v5.0.3wax01	account-query responded normally	675 ms	Permitidas	30 oct 2026, 9:10
Saludable	Leap v5.0.3wax01	account-query responded normally	888 ms	Permitidas	30 oct 2026, 8:50
Saludable	Leap v5.0.3wax01	account-query responded normally	687 ms	Permitidas	30 oct 2026, 8:30
Saludable	Leap v5.0.3wax01	account-query responded normally	634 ms	Permitidas	30 oct 2026, 8:10
Saludable	Leap v5.0.3wax01	account-query responded normally	652 ms	Permitidas	30 oct 2026, 7:50
Saludable	Leap v5.0.3wax01	account-query responded normally	650 ms	Permitidas	30 oct 2026, 7: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.

Comprobado: 30 oct 2026, 10:30
Latencia: 632 ms
Solicitudes del navegador: Permitidas
Versión: Leap v5.0.3wax01

Comprobaciones recientes

Últimas comprobaciones de salud de History API almacenadas.
Estado	Versión	Resumen	Latencia	CORS	Comprobado
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	Permitidas	30 oct 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	Permitidas	30 oct 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	Permitidas	30 oct 2026, 9: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	Permitidas	30 oct 2026, 9: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	Permitidas	30 oct 2026, 9: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	Permitidas	30 oct 2026, 8: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	Permitidas	30 oct 2026, 8: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	Permitidas	30 oct 2026, 8: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	Permitidas	30 oct 2026, 7: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	Permitidas	30 oct 2026, 7:30

Hyperion API

Obsoleto

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

Comprobado: 30 oct 2026, 10:30
Latencia: 626 ms
Solicitudes del navegador: Permitidas
Versión: 3.5.0-5

Comprobaciones recientes

Últimas comprobaciones de salud de Hyperion API almacenadas.
Estado	Versión	Resumen	Latencia	CORS	Comprobado
Obsoleto	3.5.0-5	Indexer is 714437 blocks behind the chain head (limit 180). Check that it is keeping up with nodeos.	626 ms	Permitidas	30 oct 2026, 10:30
Obsoleto	3.5.0-5	Indexer is 712051 blocks behind the chain head (limit 180). Check that it is keeping up with nodeos.	627 ms	Permitidas	30 oct 2026, 10:10
Obsoleto	3.5.0-5	Indexer is 709640 blocks behind the chain head (limit 180). Check that it is keeping up with nodeos.	610 ms	Permitidas	30 oct 2026, 9:50
Obsoleto	3.5.0-5	Indexer is 707240 blocks behind the chain head (limit 180). Check that it is keeping up with nodeos.	613 ms	Permitidas	30 oct 2026, 9:30
Obsoleto	3.5.0-5	Indexer is 704850 blocks behind the chain head (limit 180). Check that it is keeping up with nodeos.	635 ms	Permitidas	30 oct 2026, 9:10
Obsoleto	3.5.0-5	Indexer is 702437 blocks behind the chain head (limit 180). Check that it is keeping up with nodeos.	627 ms	Permitidas	30 oct 2026, 8:50
Obsoleto	3.5.0-5	Indexer is 700038 blocks behind the chain head (limit 180). Check that it is keeping up with nodeos.	613 ms	Permitidas	30 oct 2026, 8:30
Obsoleto	3.5.0-5	Indexer is 697650 blocks behind the chain head (limit 180). Check that it is keeping up with nodeos.	606 ms	Permitidas	30 oct 2026, 8:10
Obsoleto	3.5.0-5	Indexer is 695238 blocks behind the chain head (limit 180). Check that it is keeping up with nodeos.	627 ms	Permitidas	30 oct 2026, 7:50
Obsoleto	3.5.0-5	Indexer is 692840 blocks behind the chain head (limit 180). Check that it is keeping up with nodeos.	601 ms	Permitidas	30 oct 2026, 7:30