HerdCheckv0.6.7

Antelope-Knoten-Gesundheit, Status und Verlauf für Betreiber und Entwickler.

WAX Mainnet

1064487b3cd1a897ce03ae5b6a865651747e2e152090f99c1d19d44e01aea5a4

https://wax.eosrio.io

Gesundheit, Aktualität, CORS und aktueller Prüfungsverlauf für diesen Endpoint.

Produzent
eosriobrazil
Kette
WAX Mainnet
Gemeldeter Chain-Verlauf
Teilweise
Standort
Rio de Janeiro

Verfügbarkeitsverlauf

Gesunde und beeinträchtigte Prüfungen aller überwachten Funktionen. Lücken werden ausgeschlossen.

52.5 % Verfügbarkeit

1 Monat

1. Okt. 2026 UTCGrau: keine aufgezeichneten PrüfungenJetzt

Aktueller Dienstzustand

Chain API

Gesund

Chain API responded normally

Geprüft
Latenz
598 ms
Browser-Anfragen
Erlaubt
Version
Leap v5.0.3wax01
Letzte Prüfungen
Zuletzt gespeicherte Chain API-Gesundheitsprüfungen.
StatusVersionZusammenfassungLatenzCORSGeprüft
GesundLeap v5.0.3wax01Chain API responded normally598 msErlaubt
GesundLeap v5.0.3wax01Chain API responded normally613 msErlaubt
GesundLeap v5.0.3wax01Chain API responded normally628 msErlaubt
GesundLeap v5.0.3wax01Chain API responded normally596 msErlaubt
GesundLeap v5.0.3wax01Chain API responded normally623 msErlaubt
GesundLeap v5.0.3wax01Chain API responded normally620 msErlaubt
GesundLeap v5.0.3wax01Chain API responded normally616 msErlaubt
GesundLeap v5.0.3wax01Chain API responded normally621 msErlaubt
GesundLeap v5.0.3wax01Chain API responded normally621 msErlaubt
GesundLeap v5.0.3wax01Chain API responded normally618 msErlaubt

Account Query

Gesund

account-query responded normally

Geprüft
Latenz
653 ms
Browser-Anfragen
Erlaubt
Version
Leap v5.0.3wax01
Letzte Prüfungen
Zuletzt gespeicherte Account Query-Gesundheitsprüfungen.
StatusVersionZusammenfassungLatenzCORSGeprüft
GesundLeap v5.0.3wax01account-query responded normally653 msErlaubt
GesundLeap v5.0.3wax01account-query responded normally623 msErlaubt
GesundLeap v5.0.3wax01account-query responded normally1698 msErlaubt
GesundLeap v5.0.3wax01account-query responded normally675 msErlaubt
GesundLeap v5.0.3wax01account-query responded normally675 msErlaubt
GesundLeap v5.0.3wax01account-query responded normally888 msErlaubt
GesundLeap v5.0.3wax01account-query responded normally687 msErlaubt
GesundLeap v5.0.3wax01account-query responded normally634 msErlaubt
GesundLeap v5.0.3wax01account-query responded normally652 msErlaubt
GesundLeap v5.0.3wax01account-query responded normally650 msErlaubt

History API

Ungültig

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.

Geprüft
Latenz
632 ms
Browser-Anfragen
Erlaubt
Version
Leap v5.0.3wax01
Letzte Prüfungen
Zuletzt gespeicherte History API-Gesundheitsprüfungen.
StatusVersionZusammenfassungLatenzCORSGeprüft
UngültigLeap v5.0.3wax01HTTP 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 msErlaubt
UngültigLeap v5.0.3wax01HTTP 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 msErlaubt
UngültigLeap v5.0.3wax01HTTP 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 msErlaubt
UngültigLeap v5.0.3wax01HTTP 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 msErlaubt
UngültigLeap v5.0.3wax01HTTP 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 msErlaubt
UngültigLeap v5.0.3wax01HTTP 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 msErlaubt
UngültigLeap v5.0.3wax01HTTP 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 msErlaubt
UngültigLeap v5.0.3wax01HTTP 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 msErlaubt
UngültigLeap v5.0.3wax01HTTP 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 msErlaubt
UngültigLeap v5.0.3wax01HTTP 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 msErlaubt

Hyperion API

Veraltet

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

Geprüft
Latenz
626 ms
Browser-Anfragen
Erlaubt
Version
3.5.0-5
Letzte Prüfungen
Zuletzt gespeicherte Hyperion API-Gesundheitsprüfungen.
StatusVersionZusammenfassungLatenzCORSGeprüft
Veraltet3.5.0-5Indexer is 714437 blocks behind the chain head (limit 180). Check that it is keeping up with nodeos.626 msErlaubt
Veraltet3.5.0-5Indexer is 712051 blocks behind the chain head (limit 180). Check that it is keeping up with nodeos.627 msErlaubt
Veraltet3.5.0-5Indexer is 709640 blocks behind the chain head (limit 180). Check that it is keeping up with nodeos.610 msErlaubt
Veraltet3.5.0-5Indexer is 707240 blocks behind the chain head (limit 180). Check that it is keeping up with nodeos.613 msErlaubt
Veraltet3.5.0-5Indexer is 704850 blocks behind the chain head (limit 180). Check that it is keeping up with nodeos.635 msErlaubt
Veraltet3.5.0-5Indexer is 702437 blocks behind the chain head (limit 180). Check that it is keeping up with nodeos.627 msErlaubt
Veraltet3.5.0-5Indexer is 700038 blocks behind the chain head (limit 180). Check that it is keeping up with nodeos.613 msErlaubt
Veraltet3.5.0-5Indexer is 697650 blocks behind the chain head (limit 180). Check that it is keeping up with nodeos.606 msErlaubt
Veraltet3.5.0-5Indexer is 695238 blocks behind the chain head (limit 180). Check that it is keeping up with nodeos.627 msErlaubt
Veraltet3.5.0-5Indexer is 692840 blocks behind the chain head (limit 180). Check that it is keeping up with nodeos.601 msErlaubt