HerdCheckv0.6.7

Antelope node health, status, and history for operators and developers.

Vaulta Mainnet

aca376f206b8fc25a6ed44dbdc66547c36c6c33e3a119ffbeaef943642f0e906

https://eos.hyperion.eosrio.io

Health, freshness, CORS, and recent check history for this endpoint.

Producer
eosriobrazil
Reported chain history
Partial
Location
Rio de Janeiro

Uptime history

Healthy and degraded checks across monitored features. Gaps are excluded from uptime.

100.0% uptime

1 day

29 Oct 2026, 08 UTCGray: no recorded checksNow

Current service health

Chain API

Healthy

Chain API responded normally

Checked
Latency
598 ms
Browser requests
Allowed
Version
Spring v1.2.2
Recent checks
Latest stored Chain API health checks.
StatusVersionSummaryLatencyCORSChecked
HealthySpring v1.2.2Chain API responded normally598 msAllowed
HealthySpring v1.2.2Chain API responded normally602 msAllowed
HealthySpring v1.2.2Chain API responded normally579 msAllowed
HealthySpring v1.2.2Chain API responded normally597 msAllowed
HealthySpring v1.2.2Chain API responded normally574 msAllowed
HealthySpring v1.2.2Chain API responded normally597 msAllowed
HealthySpring v1.2.2Chain API responded normally597 msAllowed
HealthySpring v1.2.2Chain API responded normally580 msAllowed
HealthySpring v1.2.2Chain API responded normally605 msAllowed
HealthySpring v1.2.2Chain API responded normally577 msAllowed

Account Query

Healthy

account-query responded normally

Checked
Latency
813 ms
Browser requests
Allowed
Version
Spring v1.2.2
Recent checks
Latest stored Account Query health checks.
StatusVersionSummaryLatencyCORSChecked
HealthySpring v1.2.2account-query responded normally813 msAllowed
HealthySpring v1.2.2account-query responded normally804 msAllowed
HealthySpring v1.2.2account-query responded normally832 msAllowed
HealthySpring v1.2.2account-query responded normally817 msAllowed
HealthySpring v1.2.2account-query responded normally819 msAllowed
HealthySpring v1.2.2account-query responded normally780 msAllowed
HealthySpring v1.2.2account-query responded normally802 msAllowed
HealthySpring v1.2.2account-query responded normally830 msAllowed
HealthySpring v1.2.2account-query responded normally783 msAllowed
HealthySpring v1.2.2account-query responded normally812 msAllowed

History API

Healthy

history-v1 responded normally

Checked
Latency
580 ms
Browser requests
Allowed
Version
Spring v1.2.2
Recent checks
Latest stored History API health checks.
StatusVersionSummaryLatencyCORSChecked
HealthySpring v1.2.2history-v1 responded normally580 msAllowed
HealthySpring v1.2.2history-v1 responded normally662 msAllowed
HealthySpring v1.2.2history-v1 responded normally648 msAllowed
HealthySpring v1.2.2history-v1 responded normally741 msAllowed
HealthySpring v1.2.2history-v1 responded normally599 msAllowed
HealthySpring v1.2.2history-v1 responded normally575 msAllowed
HealthySpring v1.2.2history-v1 responded normally574 msAllowed
HealthySpring v1.2.2history-v1 responded normally659 msAllowed
HealthySpring v1.2.2history-v1 responded normally624 msAllowed
HealthySpring v1.2.2history-v1 responded normally636 msAllowed

Hyperion API

Healthy

hyperion-v2 responded normally

Checked
Latency
570 ms
Browser requests
Allowed
Version
3.5.0-5
Recent checks
Latest stored Hyperion API health checks.
StatusVersionSummaryLatencyCORSChecked
Healthy3.5.0-5hyperion-v2 responded normally570 msAllowed
Healthy3.5.0-5hyperion-v2 responded normally573 msAllowed
Healthy3.5.0-5hyperion-v2 responded normally645 msAllowed
Healthy3.5.0-5hyperion-v2 responded normally591 msAllowed
Healthy3.5.0-5hyperion-v2 responded normally565 msAllowed
Healthy3.5.0-5hyperion-v2 responded normally592 msAllowed
Healthy3.5.0-5hyperion-v2 responded normally735 msAllowed
Healthy3.5.0-5hyperion-v2 responded normally711 msAllowed
Healthy3.5.0-5hyperion-v2 responded normally659 msAllowed
Healthy3.5.0-5hyperion-v2 responded normally573 msAllowed