Public XDC RPC status board

RPCWatch Which public XDC RPC endpoint answers best right now?

Preview · one location

A public board of XDC RPC endpoints: latency and how far behind the chain head they are, measured from one location.

For: Developers and node operators who use public XDC RPC endpoints.

At a glance

Status
Preview. Measured from one location only (the FeedPlumb gateway host).
What it shows
Latency, head block and blocks behind per public endpoint, from the latest measurement
Data
The same figures as the API GET /v1/rpc-watch (free, rate-limited)
Not yet
History, more measuring regions, and alerts are coming soon

Latest data

Loading the latest data. This board needs JavaScript; the same data is at /v1/rpc-watch.

How it works

  1. FeedPlumb sends a read-only eth_blockNumber request to each public endpoint from one location.
  2. The board below shows the latest measured latency and head block. An endpoint that does not answer shows as unavailable.
  3. Before the first measurement the board says so and shows no figures.

Questions

Can results vary by region?

Yes. Latency depends on network routing between your application and each RPC provider. Today we measure from one location only.

Which endpoints?

Public XDC mainnet RPC endpoints, including XinFin eRPC, XDCRPC, and Ankr.

Related

Operational data from public XDC Network sources. Nothing on this page is financial, legal or tax advice.