HerdCheckv0.6.7

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

WAX Testnet

f16b1833c747c43682f4386fca9cbb327929334a762755ebec17f6f23c9b8a12

https://test.wax.eosusa.io

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

Producer
ivote4waxusa
Reported chain history
Full
Location
Greenville,SC,USA

Uptime history

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

79.8% uptime

7 days

23 Oct 2026, 05 UTCGray: no recorded checksNow

Current service health

Chain API

Healthy

Chain API responded normally

Checked
Latency
329 ms
Browser requests
Allowed
Version
Spring v1.3.1wax02
Recent checks
Latest stored Chain API health checks.
StatusVersionSummaryLatencyCORSChecked
HealthySpring v1.3.1wax02Chain API responded normally329 msAllowed
HealthySpring v1.3.1wax02Chain API responded normally337 msAllowed
HealthySpring v1.3.1wax02Chain API responded normally326 msAllowed
HealthySpring v1.3.1wax02Chain API responded normally359 msAllowed
HealthySpring v1.3.1wax02Chain API responded normally315 msAllowed
HealthySpring v1.3.1wax02Chain API responded normally344 msAllowed
HealthySpring v1.3.1wax02Chain API responded normally318 msAllowed
HealthySpring v1.3.1wax02Chain API responded normally318 msAllowed

Account Query

Healthy

account-query responded normally

Checked
Latency
352 ms
Browser requests
Allowed
Version
Spring v1.3.1wax02
Recent checks
Latest stored Account Query health checks.
StatusVersionSummaryLatencyCORSChecked
HealthySpring v1.3.1wax02account-query responded normally352 msAllowed
HealthySpring v1.3.1wax02account-query responded normally362 msAllowed
HealthySpring v1.3.1wax02account-query responded normally373 msAllowed
HealthySpring v1.3.1wax02account-query responded normally394 msAllowed
HealthySpring v1.3.1wax02account-query responded normally356 msAllowed
HealthySpring v1.3.1wax02account-query responded normally363 msAllowed
HealthySpring v1.3.1wax02account-query responded normally336 msAllowed
HealthySpring v1.3.1wax02account-query responded normally340 msAllowed

History API

Healthy

history-v1 responded normally

Checked
Latency
128 ms
Browser requests
Allowed
Version
Spring v1.3.1wax02
Recent checks
Latest stored History API health checks.
StatusVersionSummaryLatencyCORSChecked
HealthySpring v1.3.1wax02history-v1 responded normally128 msAllowed
HealthySpring v1.3.1wax02history-v1 responded normally131 msAllowed
HealthySpring v1.3.1wax02history-v1 responded normally129 msAllowed
HealthySpring v1.3.1wax02history-v1 responded normally134 msAllowed
HealthySpring v1.3.1wax02history-v1 responded normally350 msAllowed
HealthySpring v1.3.1wax02history-v1 responded normally350 msAllowed
HealthySpring v1.3.1wax02history-v1 responded normally125 msAllowed
HealthySpring v1.3.1wax02history-v1 responded normally128 msAllowed

Hyperion API

Healthy

hyperion-v2 responded normally

Checked
Latency
388 ms
Browser requests
Allowed
Version
3.5.0-3-dirty
Recent checks
Latest stored Hyperion API health checks.
StatusVersionSummaryLatencyCORSChecked
Healthy3.5.0-3-dirtyhyperion-v2 responded normally388 msAllowed
Healthy3.5.0-3-dirtyhyperion-v2 responded normally158 msAllowed
Healthy3.5.0-3-dirtyhyperion-v2 responded normally150 msAllowed
Healthy3.5.0-3-dirtyhyperion-v2 responded normally387 msAllowed
Healthy3.5.0-3-dirtyhyperion-v2 responded normally153 msAllowed
Healthy3.5.0-3-dirtyhyperion-v2 responded normally157 msAllowed
Healthy3.5.0-3-dirtyhyperion-v2 responded normally153 msAllowed
Healthy3.5.0-3-dirtyhyperion-v2 responded normally152 msAllowed

AtomicAssets API

Invalid

HTTP 404 on /atomicassets/v1/config. The server has no route for this atomic-assets-api check, so the advertised feature is not actually served. Fix the proxy routing or remove the feature from bp.json.

Checked
Latency
105 ms
Browser requests
Allowed
Version
Unknown
Recent checks
Latest stored AtomicAssets API health checks.
StatusVersionSummaryLatencyCORSChecked
InvalidUnknownHTTP 404 on /atomicassets/v1/config. The server has no route for this atomic-assets-api check, so the advertised feature is not actually served. Fix the proxy routing or remove the feature from bp.json.105 msAllowed
InvalidUnknownHTTP 404 on /atomicassets/v1/config. The server has no route for this atomic-assets-api check, so the advertised feature is not actually served. Fix the proxy routing or remove the feature from bp.json.114 msAllowed
InvalidUnknownHTTP 404 on /atomicassets/v1/config. The server has no route for this atomic-assets-api check, so the advertised feature is not actually served. Fix the proxy routing or remove the feature from bp.json.114 msAllowed
InvalidUnknownHTTP 404 on /atomicassets/v1/config. The server has no route for this atomic-assets-api check, so the advertised feature is not actually served. Fix the proxy routing or remove the feature from bp.json.107 msAllowed
InvalidUnknownHTTP 404 on /atomicassets/v1/config. The server has no route for this atomic-assets-api check, so the advertised feature is not actually served. Fix the proxy routing or remove the feature from bp.json.111 msAllowed
InvalidUnknownHTTP 404 on /atomicassets/v1/config. The server has no route for this atomic-assets-api check, so the advertised feature is not actually served. Fix the proxy routing or remove the feature from bp.json.113 msAllowed
InvalidUnknownHTTP 404 on /atomicassets/v1/config. The server has no route for this atomic-assets-api check, so the advertised feature is not actually served. Fix the proxy routing or remove the feature from bp.json.106 msAllowed
InvalidUnknownHTTP 404 on /atomicassets/v1/config. The server has no route for this atomic-assets-api check, so the advertised feature is not actually served. Fix the proxy routing or remove the feature from bp.json.112 msAllowed