System status
Gully RPC status
Checking the gateway and every served network.
Gateway probed every 10 s from your browser; chain heads read every 15 s from each chain's public RPC; traffic from gateway metering; product state from status.json.
Gateway round trip
Connecting
–ms from your browser
POST eth_chainId to rpc.gullyrpc.xyz without a key: 401 means up and enforcing auth.
Requests / min
–
now, 5 min rateLatency p50
–ms
gateway side, 5 minLatency p95
–ms
gateway side, 5 minSuccess, 24 h
–%
answered without errorNetworks up
–
fresh blocks, this browserUptime
Every network and service
Rows fill in while this page is open: one cell per check, newest on the right.
Networks
Connecting
Green: the chain produced a fresh block. Red: no answer or stalled. Checked every 15 s from this browser.
Gully RPC services
Connecting
From the Gully Labs hub (gullylabs.xyz/api/hub), polled every 30 s.
Traffic
loading meteringGateway, last 30 minutes
All keys together, from gateway metering. No per-key data leaves the portal.
Requests / min
Connecting
Latency
Errors / min
Connecting
Received minus successful requests, per minute.
Latency per network
Last 5 min, ms. Networks without traffic are left out.
Components
What is live and what is coming
From status.json, the single source every Gully RPC surface reads.
| Component | State | Note |
|---|---|---|
| Loading status.json | ||