HerdCheckv0.6.7

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

Vaulta Mainnet

aca376f206b8fc25a6ed44dbdc66547c36c6c33e3a119ffbeaef943642f0e906

https://eospublic.chainrift.com

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

Producer
chainriftxxx
Reported chain history
Partial
Location
Ljubljana

Uptime history

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

0.0% uptime

7 days

23 Oct 2026, 03 UTCGray: no recorded checksNow

Current service health

Chain API

Down

Connection was closed by the server (ECONNRESET). Check the proxy and server logs.

Checked
Latency
—
Browser requests
Blocked
Version
Unknown

Request never completed

Recent checks
Latest stored Chain API health checks.
StatusVersionSummaryLatencyCORSChecked
DownUnknownConnection was closed by the server (ECONNRESET). Check the proxy and server logs.—Blocked
DownUnknownConnection was closed by the server (ECONNRESET). Check the proxy and server logs.—Blocked
DownUnknownConnection was closed by the server (ECONNRESET). Check the proxy and server logs.—Blocked
InvalidUnknownHTTP 404 on /v1/chain/get_info. The server has no route for this chain-api check, so the advertised feature is not actually served. Fix the proxy routing or remove the feature from bp.json.232 msBlocked
InvalidUnknownHTTP 404 on /v1/chain/get_info. The server has no route for this chain-api check, so the advertised feature is not actually served. Fix the proxy routing or remove the feature from bp.json.238 msBlocked
DownUnknownConnection was closed by the server (ECONNRESET). Check the proxy and server logs.—Blocked
DownUnknownConnection was closed by the server (ECONNRESET). Check the proxy and server logs.—Blocked
InvalidUnknownHTTP 404 on /v1/chain/get_info. The server has no route for this chain-api check, so the advertised feature is not actually served. Fix the proxy routing or remove the feature from bp.json.589 msBlocked
InvalidUnknownHTTP 404 on /v1/chain/get_info. The server has no route for this chain-api check, so the advertised feature is not actually served. Fix the proxy routing or remove the feature from bp.json.240 msBlocked
InvalidUnknownHTTP 404 on /v1/chain/get_info. The server has no route for this chain-api check, so the advertised feature is not actually served. Fix the proxy routing or remove the feature from bp.json.355 msBlocked
InvalidUnknownHTTP 404 on /v1/chain/get_info. The server has no route for this chain-api check, so the advertised feature is not actually served. Fix the proxy routing or remove the feature from bp.json.236 msBlocked
InvalidUnknownHTTP 404 on /v1/chain/get_info. The server has no route for this chain-api check, so the advertised feature is not actually served. Fix the proxy routing or remove the feature from bp.json.240 msBlocked
InvalidUnknownHTTP 404 on /v1/chain/get_info. The server has no route for this chain-api check, so the advertised feature is not actually served. Fix the proxy routing or remove the feature from bp.json.234 msBlocked
DownUnknownConnection was closed by the server (ECONNRESET). Check the proxy and server logs.—Blocked
DownUnknownConnection was closed by the server (ECONNRESET). Check the proxy and server logs.—Blocked
InvalidUnknownHTTP 404 on /v1/chain/get_info. The server has no route for this chain-api check, so the advertised feature is not actually served. Fix the proxy routing or remove the feature from bp.json.234 msBlocked
InvalidUnknownHTTP 404 on /v1/chain/get_info. The server has no route for this chain-api check, so the advertised feature is not actually served. Fix the proxy routing or remove the feature from bp.json.236 msBlocked
InvalidUnknownHTTP 404 on /v1/chain/get_info. The server has no route for this chain-api check, so the advertised feature is not actually served. Fix the proxy routing or remove the feature from bp.json.244 msBlocked
InvalidUnknownHTTP 404 on /v1/chain/get_info. The server has no route for this chain-api check, so the advertised feature is not actually served. Fix the proxy routing or remove the feature from bp.json.292 msBlocked
InvalidUnknownHTTP 404 on /v1/chain/get_info. The server has no route for this chain-api check, so the advertised feature is not actually served. Fix the proxy routing or remove the feature from bp.json.233 msBlocked
InvalidUnknownHTTP 404 on /v1/chain/get_info. The server has no route for this chain-api check, so the advertised feature is not actually served. Fix the proxy routing or remove the feature from bp.json.659 msBlocked
InvalidUnknownHTTP 404 on /v1/chain/get_info. The server has no route for this chain-api check, so the advertised feature is not actually served. Fix the proxy routing or remove the feature from bp.json.589 msBlocked
InvalidUnknownHTTP 404 on /v1/chain/get_info. The server has no route for this chain-api check, so the advertised feature is not actually served. Fix the proxy routing or remove the feature from bp.json.237 msBlocked
InvalidUnknownHTTP 404 on /v1/chain/get_info. The server has no route for this chain-api check, so the advertised feature is not actually served. Fix the proxy routing or remove the feature from bp.json.241 msBlocked
InvalidUnknownHTTP 404 on /v1/chain/get_info. The server has no route for this chain-api check, so the advertised feature is not actually served. Fix the proxy routing or remove the feature from bp.json.240 msBlocked
InvalidUnknownHTTP 404 on /v1/chain/get_info. The server has no route for this chain-api check, so the advertised feature is not actually served. Fix the proxy routing or remove the feature from bp.json.239 msBlocked
DownUnknownConnection was closed by the server (ECONNRESET). Check the proxy and server logs.—Blocked
InvalidUnknownHTTP 404 on /v1/chain/get_info. The server has no route for this chain-api check, so the advertised feature is not actually served. Fix the proxy routing or remove the feature from bp.json.568 msBlocked
InvalidUnknownHTTP 404 on /v1/chain/get_info. The server has no route for this chain-api check, so the advertised feature is not actually served. Fix the proxy routing or remove the feature from bp.json.582 msBlocked
InvalidUnknownHTTP 404 on /v1/chain/get_info. The server has no route for this chain-api check, so the advertised feature is not actually served. Fix the proxy routing or remove the feature from bp.json.242 msBlocked
InvalidUnknownHTTP 404 on /v1/chain/get_info. The server has no route for this chain-api check, so the advertised feature is not actually served. Fix the proxy routing or remove the feature from bp.json.236 msBlocked
InvalidUnknownHTTP 404 on /v1/chain/get_info. The server has no route for this chain-api check, so the advertised feature is not actually served. Fix the proxy routing or remove the feature from bp.json.239 msBlocked
InvalidUnknownHTTP 404 on /v1/chain/get_info. The server has no route for this chain-api check, so the advertised feature is not actually served. Fix the proxy routing or remove the feature from bp.json.234 msBlocked
DownUnknownConnection was closed by the server (ECONNRESET). Check the proxy and server logs.—Blocked
InvalidUnknownHTTP 404 on /v1/chain/get_info. The server has no route for this chain-api check, so the advertised feature is not actually served. Fix the proxy routing or remove the feature from bp.json.400 msBlocked
InvalidUnknownHTTP 404 on /v1/chain/get_info. The server has no route for this chain-api check, so the advertised feature is not actually served. Fix the proxy routing or remove the feature from bp.json.234 msBlocked
InvalidUnknownHTTP 404 on /v1/chain/get_info. The server has no route for this chain-api check, so the advertised feature is not actually served. Fix the proxy routing or remove the feature from bp.json.238 msBlocked
DownUnknownConnection was closed by the server (ECONNRESET). Check the proxy and server logs.—Blocked
InvalidUnknownHTTP 404 on /v1/chain/get_info. The server has no route for this chain-api check, so the advertised feature is not actually served. Fix the proxy routing or remove the feature from bp.json.239 msBlocked
InvalidUnknownHTTP 404 on /v1/chain/get_info. The server has no route for this chain-api check, so the advertised feature is not actually served. Fix the proxy routing or remove the feature from bp.json.244 msBlocked