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
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
607 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 normally607 msErlaubt
GesundLeap v5.0.3wax01Chain API responded normally601 msErlaubt
GesundLeap v5.0.3wax01Chain API responded normally625 msErlaubt
GesundLeap v5.0.3wax01Chain API responded normally624 msErlaubt
GesundLeap v5.0.3wax01Chain API responded normally705 msErlaubt
GesundLeap v5.0.3wax01Chain API responded normally620 msErlaubt
GesundLeap v5.0.3wax01Chain API responded normally614 msErlaubt
GesundLeap v5.0.3wax01Chain API responded normally624 msErlaubt
GesundLeap v5.0.3wax01Chain API responded normally626 msErlaubt
GesundLeap v5.0.3wax01Chain API responded normally617 msErlaubt

Account Query

Gesund

account-query responded normally

Geprüft
Latenz
668 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 normally668 msErlaubt
GesundLeap v5.0.3wax01account-query responded normally655 msErlaubt
GesundLeap v5.0.3wax01account-query responded normally646 msErlaubt
GesundLeap v5.0.3wax01account-query responded normally665 msErlaubt
GesundLeap v5.0.3wax01account-query responded normally810 msErlaubt
GesundLeap v5.0.3wax01account-query responded normally644 msErlaubt
GesundLeap v5.0.3wax01account-query responded normally681 msErlaubt
GesundLeap v5.0.3wax01account-query responded normally649 msErlaubt
GesundLeap v5.0.3wax01account-query responded normally663 msErlaubt
GesundLeap v5.0.3wax01account-query responded normally672 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
635 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.635 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.637 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.628 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.645 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
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.628 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.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.610 msErlaubt

Hyperion API

Veraltet

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

Geprüft
Latenz
609 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 673637 blocks behind the chain head (limit 180). Check that it is keeping up with nodeos.609 msErlaubt
Veraltet3.5.0-5Indexer is 671251 blocks behind the chain head (limit 180). Check that it is keeping up with nodeos.613 msErlaubt
Veraltet3.5.0-5Indexer is 668837 blocks behind the chain head (limit 180). Check that it is keeping up with nodeos.610 msErlaubt
Veraltet3.5.0-5Indexer is 666450 blocks behind the chain head (limit 180). Check that it is keeping up with nodeos.633 msErlaubt
Veraltet3.5.0-5Indexer is 664051 blocks behind the chain head (limit 180). Check that it is keeping up with nodeos.657 msErlaubt
Veraltet3.5.0-5Indexer is 661640 blocks behind the chain head (limit 180). Check that it is keeping up with nodeos.607 msErlaubt
Veraltet3.5.0-5Indexer is 659237 blocks behind the chain head (limit 180). Check that it is keeping up with nodeos.628 msErlaubt
Veraltet3.5.0-5Indexer is 656850 blocks behind the chain head (limit 180). Check that it is keeping up with nodeos.634 msErlaubt
Veraltet3.5.0-5Indexer is 654438 blocks behind the chain head (limit 180). Check that it is keeping up with nodeos.631 msErlaubt
Veraltet3.5.0-5Indexer is 652094 blocks behind the chain head (limit 180). Check that it is keeping up with nodeos.630 msErlaubt