Web3 Pi · Arkiv RPC · Public dashboard

Your RPC fleet. Live.

Arkiv Tiramisu testnet·chain ID 7738577·router up —

Ready Lagging · syncing · stale Offline · stalled Paused
Available nodes

—

—

Requests / seclast 5 s

—

—

Response timep95 · 60 s

—

histogram bucket bound

RPC errorssince start

—

—

Current block

—

—

Cluster map

Traffic is routed only to ready nodes

— nodes
Web3 Pi RPC ProxyLoad balancer · health-aware

Chain status

A shared reference point

Current block

—

—

Allowed lag
—
Max block age
—
Health checks
—
In-flight requests
—
Router build
—

RPC traffic

Client requests per second · last 60 s

Last 60 s

Average response time · ms

Traffic distribution

Requests per node since router start

Fleet telemetry

Hardware and client state from a separate, read-only monitoring path · sampled every 15 s

—
Per-node hardware and client telemetry
Node Telemetry CPU CPU temp · 10 min Memory Disk · NVMe Network ↓ / ↑ Clients EL · CL

Health events

Changes in node eligibility, newest first

    About this data

    What you are looking at

    • Live from the proxy. Routing state is refreshed every 2 s; telemetry every 15 s.
    • Counters reset on restart. Request totals and history are kept in memory since the router started.
    • p95 is a bucket bound. Response time is the upper bound of the histogram bucket containing the 95th percentile.
    • Privacy first. This view leaves out network addresses, credentials, serial numbers and logs.
    • Proof of concept. Arkiv Tiramisu testnet; not a service-level guarantee.
    How the proxy works