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.

92.5% uptime

1 year

31 Oct 2025 UTCGray: no recorded checksNow

Current service health

Chain API

Healthy

Chain API responded normally

Checked
Latency
605 ms
Browser requests
Allowed
Version
Spring v1.2.2
Recent checks
Latest stored Chain API health checks.
StatusVersionSummaryLatencyCORSChecked
HealthySpring v1.2.2Chain API responded normally605 msAllowed
HealthySpring v1.2.2Chain API responded normally577 msAllowed
HealthySpring v1.2.2Chain API responded normally607 msAllowed
HealthySpring v1.2.2Chain API responded normally574 msAllowed
HealthySpring v1.2.2Chain API responded normally579 msAllowed
HealthySpring v1.2.2Chain API responded normally577 msAllowed
HealthySpring v1.2.2Chain API responded normally576 msAllowed
HealthySpring v1.2.2Chain API responded normally624 msAllowed
HealthySpring v1.2.2Chain API responded normally768 msAllowed
HealthySpring v1.2.2Chain API responded normally640 msAllowed

Account Query

Healthy

account-query responded normally

Checked
Latency
783 ms
Browser requests
Allowed
Version
Spring v1.2.2
Recent checks
Latest stored Account Query health checks.
StatusVersionSummaryLatencyCORSChecked
HealthySpring v1.2.2account-query responded normally783 msAllowed
HealthySpring v1.2.2account-query responded normally812 msAllowed
HealthySpring v1.2.2account-query responded normally802 msAllowed
HealthySpring v1.2.2account-query responded normally816 msAllowed
HealthySpring v1.2.2account-query responded normally798 msAllowed
HealthySpring v1.2.2account-query responded normally802 msAllowed
HealthySpring v1.2.2account-query responded normally824 msAllowed
HealthySpring v1.2.2account-query responded normally809 msAllowed
HealthySpring v1.2.2account-query responded normally943 msAllowed
HealthySpring v1.2.2account-query responded normally841 msAllowed

History API

Healthy

history-v1 responded normally

Checked
Latency
624 ms
Browser requests
Allowed
Version
Spring v1.2.2
Recent checks
Latest stored History API health checks.
StatusVersionSummaryLatencyCORSChecked
HealthySpring v1.2.2history-v1 responded normally624 msAllowed
HealthySpring v1.2.2history-v1 responded normally636 msAllowed
HealthySpring v1.2.2history-v1 responded normally601 msAllowed
HealthySpring v1.2.2history-v1 responded normally603 msAllowed
HealthySpring v1.2.2history-v1 responded normally580 msAllowed
HealthySpring v1.2.2history-v1 responded normally725 msAllowed
HealthySpring v1.2.2history-v1 responded normally594 msAllowed
HealthySpring v1.2.2history-v1 responded normally597 msAllowed
HealthySpring v1.2.2history-v1 responded normally619 msAllowed
HealthySpring v1.2.2history-v1 responded normally693 msAllowed

Hyperion API

Healthy

hyperion-v2 responded normally

Checked
Latency
659 ms
Browser requests
Allowed
Version
3.5.0-5
Recent checks
Latest stored Hyperion API health checks.
StatusVersionSummaryLatencyCORSChecked
Healthy3.5.0-5hyperion-v2 responded normally659 msAllowed
Healthy3.5.0-5hyperion-v2 responded normally573 msAllowed
Healthy3.5.0-5hyperion-v2 responded normally576 msAllowed
Healthy3.5.0-5hyperion-v2 responded normally579 msAllowed
Healthy3.5.0-5hyperion-v2 responded normally599 msAllowed
Healthy3.5.0-5hyperion-v2 responded normally745 msAllowed
Healthy3.5.0-5hyperion-v2 responded normally572 msAllowed
Healthy3.5.0-5hyperion-v2 responded normally568 msAllowed
Healthy3.5.0-5hyperion-v2 responded normally597 msAllowed
Healthy3.5.0-5hyperion-v2 responded normally634 msAllowed