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

3 days

27 Oct 2026, 03 UTCGray: no recorded checksNow

Current service health

Chain API

Healthy

Chain API responded normally

Checked
Latency
624 ms
Browser requests
Allowed
Version
Spring v1.2.2
Recent checks
Latest stored Chain API health checks.
StatusVersionSummaryLatencyCORSChecked
HealthySpring v1.2.2Chain API responded normally624 msAllowed
HealthySpring v1.2.2Chain API responded normally768 msAllowed
HealthySpring v1.2.2Chain API responded normally640 msAllowed
HealthySpring v1.2.2Chain API responded normally614 msAllowed
HealthySpring v1.2.2Chain API responded normally598 msAllowed
HealthySpring v1.2.2Chain API responded normally629 msAllowed
HealthySpring v1.2.2Chain API responded normally595 msAllowed
HealthySpring v1.2.2Chain API responded normally603 msAllowed
HealthySpring v1.2.2Chain API responded normally599 msAllowed
HealthySpring v1.2.2Chain API responded normally616 msAllowed

Account Query

Healthy

account-query responded normally

Checked
Latency
809 ms
Browser requests
Allowed
Version
Spring v1.2.2
Recent checks
Latest stored Account Query health checks.
StatusVersionSummaryLatencyCORSChecked
HealthySpring v1.2.2account-query responded normally809 msAllowed
HealthySpring v1.2.2account-query responded normally943 msAllowed
HealthySpring v1.2.2account-query responded normally841 msAllowed
HealthySpring v1.2.2account-query responded normally840 msAllowed
HealthySpring v1.2.2account-query responded normally809 msAllowed
HealthySpring v1.2.2account-query responded normally849 msAllowed
HealthySpring v1.2.2account-query responded normally868 msAllowed
HealthySpring v1.2.2account-query responded normally854 msAllowed
HealthySpring v1.2.2account-query responded normally869 msAllowed
HealthySpring v1.2.2account-query responded normally852 msAllowed

History API

Healthy

history-v1 responded normally

Checked
Latency
597 ms
Browser requests
Allowed
Version
Spring v1.2.2
Recent checks
Latest stored History API health checks.
StatusVersionSummaryLatencyCORSChecked
HealthySpring v1.2.2history-v1 responded normally597 msAllowed
HealthySpring v1.2.2history-v1 responded normally619 msAllowed
HealthySpring v1.2.2history-v1 responded normally693 msAllowed
HealthySpring v1.2.2history-v1 responded normally623 msAllowed
HealthySpring v1.2.2history-v1 responded normally634 msAllowed
HealthySpring v1.2.2history-v1 responded normally812 msAllowed
HealthySpring v1.2.2history-v1 responded normally595 msAllowed
HealthySpring v1.2.2history-v1 responded normally2262 msAllowed
HealthySpring v1.2.2history-v1 responded normally990 msAllowed
HealthySpring v1.2.2history-v1 responded normally1014 msAllowed

Hyperion API

Healthy

hyperion-v2 responded normally

Checked
Latency
568 ms
Browser requests
Allowed
Version
3.5.0-5
Recent checks
Latest stored Hyperion API health checks.
StatusVersionSummaryLatencyCORSChecked
Healthy3.5.0-5hyperion-v2 responded normally568 msAllowed
Healthy3.5.0-5hyperion-v2 responded normally597 msAllowed
Healthy3.5.0-5hyperion-v2 responded normally634 msAllowed
Healthy3.5.0-5hyperion-v2 responded normally599 msAllowed
Healthy3.5.0-5hyperion-v2 responded normally597 msAllowed
Healthy3.5.0-5hyperion-v2 responded normally781 msAllowed
Healthy3.5.0-5hyperion-v2 responded normally602 msAllowed
Healthy3.5.0-5hyperion-v2 responded normally1714 msAllowed
Healthy3.5.0-5hyperion-v2 responded normally967 msAllowed
Healthy3.5.0-5hyperion-v2 responded normally966 msAllowed