System status
Live operational state of the Robyn AnyGas relay — read straight from /svc/api/status and /svc/health. No fabricated uptime figures; if a rail is degraded or rate-limited, it says so.
Checking…
contacting the relay…
Uptime · measured from outside
—loading /svc/api/uptime…
Probed every 10 minutes by an independent relay in Iceland (different operator and jurisdiction). A probe that never reached us counts against uptime. Derived from the request log — nothing declared. Raw data: /svc/api/uptime.
History & service levels · last 90 days
—
uptime · 30 d target ≥ 99.5%
—
API error rate · 30 d target ≤ 5% (self-probes incl.)
—
routes settled · 30 d target ≥ 95%
—
delivery p95 float lane · target ≤ 60 s
—
front-end integrity live pages vs served scripts · every 10 min
API requests per day —
—daily · UTC · includes the box's own 10-minute self-teststoday
Error rate per day —
4xx + 5xx as a share of requests · negative tests in the self-test count as errors
Cross-chain routes started per day —
from the route ledger · settled share in the tile above
History is aggregate per-day counts computed on the origin from its own request log. No caller data exists in it (addresses are never persisted). Raw data: /svc/api/status/history.
Bridge rails
Aggregators…
Best-of-N EVM routing — LI.FI, Bungee, deBridge, Socket.
Allbridge…
Stellar & Solana legs via Allbridge Core.
Chainflip…
Native Bitcoin delivery via Chainflip — no wrapping.
Node mesh
—
nodes live
—
EVM chains up
—
non-EVM nodes up
—
directed routes
Rail health is derived from live daemon state. A rail marked degraded is still routable through its healthy legs; a rail marked down is temporarily unavailable and routes will fail over or return an honest error rather than a fake transaction.
Robyn AnyGas · operational status
On-chain proof →
Live routes →
API docs →
Terms
Privacy
anygas.xyz