Live status of every public XDC RPC endpoint
Live: the table refreshes every 30 seconds
XDC Network chain ID 50 · 0x32
Answering correctly
6 of 6
Tested by our server every minute
Fastest right now
70 ms
XinFin eRPC
Highest block seen
109,525,796
Lag is measured against this block
XDCScan latest block
109,525,796
Cross-check from the explorer
| Endpoint | Status | Response | Latest block | Uptime (24 h) | Last 30 days |
|---|---|---|---|---|---|
| XinFin eRPCDefaulthttps://erpc.xinfin.networkThe RPC URL the XDC docs give for adding the network to a wallet. | Online | 70 msmedian 53 ms (24 h)p95 76 ms (24 h) | 109,525,796in sync24 h max lag 1,718 | 98.22%7 d 98.47%30 d 98.54% | |
| XinFin RPChttps://rpc.xinfin.network | Online | 252 msmedian 316 ms (24 h)p95 749 ms (24 h) | 109,525,796in sync24 h max lag 8 | 100%7 d 99.82%30 d 99.8% | |
| XinFin RPC 1https://rpc1.xinfin.network | Online | 121 msmedian 137 ms (24 h)p95 266 ms (24 h) | 109,525,796in sync24 h max lag 4 | 100%7 d 99.85%30 d 99.66% | |
| XDCRPC eRPChttps://erpc.xdcrpc.com | Online | 75 msmedian 76 ms (24 h)p95 111 ms (24 h) | 109,525,796in sync24 h max lag 856 | 60.32%7 d 64.54%30 d 65.08% | |
| XinFin eaRPChttps://earpc.xinfin.networkListed by the XDC docs as an alternative. | Behind | 113 msmedian 123 ms (24 h)p95 208 ms (24 h) | 109,524,1861,610 blocks behind24 h max lag 1,610 | 100%7 d 99.77%30 d 99.78% | |
| XDCRPChttps://rpc.xdcrpc.com | Online | 111 msmedian 76 ms (24 h)p95 112 ms (24 h) | 109,525,796in sync24 h max lag 856 | 60.32%7 d 64.41%30 d 64.82% | |
| XDC.org RPCNot recommendedChecked from your browserhttps://rpc.xdc.orgListed by the XDC docs. Not recommended here: check its live status before you rely on it. | Checking… | —from your browser | — | —no history | No history: our server cannot call this host |
| Ankr public RPCNot recommendedChecked from your browserhttps://rpc.ankr.com/xdcRun by Ankr, not by the XDC Network. Not recommended here. | Checking… | —from your browser | — | —no history | No history: our server cannot call this host |
XDC Apothem Testnet chain ID 51 · 0x33
Answering correctly
3 of 3
Tested by our server every minute
Fastest right now
96 ms
Apothem RPC
Highest block seen
85,565,275
Lag is measured against this block
| Endpoint | Status | Response | Latest block | Uptime (24 h) | Last 30 days |
|---|---|---|---|---|---|
| Apothem RPCDefaulthttps://rpc.apothem.networkThe Apothem RPC URL in the XDC docs. | Online | 96 msmedian 119 ms (24 h)p95 363 ms (24 h) | 85,565,275in sync24 h max lag 2 | 99.79%7 d 99.94%30 d 99.94% | |
| Apothem eRPChttps://erpc.apothem.network | Online | 144 msmedian 164 ms (24 h)p95 340 ms (24 h) | 85,565,275in sync24 h max lag 2 | 99.79%7 d 99.86%30 d 99.86% | |
| Apothem eaRPChttps://earpc.apothem.network | Online | 217 msmedian 242 ms (24 h)p95 396 ms (24 h) | 85,565,275in sync24 h max lag 2 | 99.79%7 d 99.9%30 d 99.9% |
Checked from the xdcnetwork.org server · updated 24s ago
Response time is measured from our server, not from your connection: it runs from the end of the TLS handshake to the last byte of the answer to eth_blockNumber. Uptime is the share of checks in which an endpoint returned a valid block number and the right chain ID, counted since . An endpoint is Behind when its block is more than 10 blocks (well under a minute) under the highest block seen, and Slow at 1,500 ms or more. Endpoints our server may not call are checked in your browser when you open this page, so their results depend on your network and have no history.
Response time of an XDC RPC endpoint over time
52 ms
Median response time
xdcnetwork.org server checks · updated 24s ago
The line is the median response time of the endpoint in each period (five minutes in the 24 h view, one hour in 7 d, three hours in 30 d). Where the line crosses a straight stretch, the endpoint gave no valid answer in between: check the uptime bar in the table for the days it was down.
XDC RPC settings for MetaMask and other wallets
XDC Network
| Network name | XDC Network |
|---|---|
| RPC URL | https://erpc.xinfin.network |
| Chain ID | 50 |
| Chain ID (hex) | 0x32 |
| Currency symbol | XDC |
| Block explorer | https://xdcscan.com |
XDC Apothem Testnet
| Network name | XDC Apothem Testnet |
|---|---|
| RPC URL | https://rpc.apothem.network |
| Chain ID | 51 |
| Chain ID (hex) | 0x33 |
| Currency symbol | TXDC |
| Block explorer | https://testnet.xdcscan.com |
Works with MetaMask and other browser wallets. Your wallet asks you to approve before anything is added.
Apothem coins have no value. Get test coins from the Apothem faucet.
How the XDC RPC status check works
An RPC endpoint is the server address a wallet or app calls to read the XDC chain and send transactions. The XDC docs list the public ones for mainnet and for the Apothem testnet, and the chain registry behind chainlist.org lists more. We took our list from the XDC docs for mainnet, the XDC docs for Apothem and the registry files for chain 50 and chain 51, and called every URL ourselves before listing it.
What our server tests on each check
For each endpoint our server is allowed to call, it asks for the latest block number (eth_blockNumber) and for the chain ID (eth_chainId), with a five-second limit. An endpoint counts as up only when it returns a valid block number and the chain ID is 50 for mainnet or 51 for Apothem. The chain ID is re-checked at most every ten minutes, because it does not change between checks.
Response time
Response time runs from the end of the secure connection handshake to the last byte of the answer to eth_blockNumber. It is measured from our server, so it shows how an endpoint answers a server, not how fast it is from your phone or office. The median and the 95th percentile are taken over the last 24 hours; the chart shows the median in five-minute, one-hour or three-hour steps.
Block lag
Block lag is how many blocks an endpoint is behind the highest block seen on the same network in the same check. Blocks come a few seconds apart, so up to 10 blocks (well under a minute) counts as in sync; more than that is shown as Behind. When an XDCScan API key is set on our side, the explorer's latest block joins the comparison as a cross-check.
Uptime
Uptime is the share of checks in which an endpoint was up. Single check results are kept for 48 hours and then rolled up to hourly figures kept for 90 days, so the 24-hour, 7-day and 30-day numbers and the daily bars come from our own stored history. The page shows the date our measuring started; before that there is no data, and days without data are drawn as short grey bars.
Rate-limited endpoints
Some public endpoints answer HTTP 429 (too many requests) when one address calls them often. We show that as Rate limited and leave it out of the uptime figures, because the limit applies to our server's address and says nothing about whether the endpoint works for you.
Endpoints checked in your browser
Our server may only call a fixed list of hosts. Endpoints outside that list are called from your browser when you open this page, and the result is labelled as coming from your browser. It depends on your network, has no history, and an endpoint that refuses browser requests shows as No reply in your browser rather than as down.
What the status does not tell you
These figures describe how endpoints answered our checks. They do not promise how an endpoint will behave for your wallet or app.
Free public endpoints come without a promise
The XDC docs list these endpoints but we found no rate limit or service level stated for them (XDC docs, wallet configuration). An app that needs steady capacity should run its own XDC node or use a provider it has an agreement with.
One location, one kind of call
We measure from one place with two simple calls. Heavy calls such as log queries or archive reads can fail on an endpoint that answers block numbers perfectly.
A match does not mean the data is right
We compare block numbers and chain IDs only. We do not check balances or transaction results, so an endpoint that reports a current block can still return wrong data. Use URLs from the XDC docs or this page, and never one from a message you did not ask for. A bad RPC URL cannot move your funds without your signature, but it can show wrong balances. More in the safety center.
Which XDC RPC URL should I use?
To add XDC to a wallet
Use https://erpc.xinfin.network with chain ID 50, the address the XDC docs give for wallets (XDC docs). The docs also suggest choosing the endpoint with the lowest latency for your region. Our add XDC to MetaMask tool does it in one click.
For an app, a bot or a script
Use more than one URL and fall back to the next when a call fails or returns HTTP 429. Keep calls to what you need: public endpoints are shared. Check eth_chainId once when you start, so a wrong URL cannot slip in.
For the Apothem testnet
Use https://rpc.apothem.network with chain ID 51 and test XDC from the Apothem faucet (XDC docs). Test XDC has no value.
URLs marked not recommended
rpc.xdc.org is still listed by the XDC docs but we do not recommend it, and rpc.ankr.com/xdc is run by a third party, not by the XDC Network. Both are checked in your browser so you can see how they answer today.
XDC RPC FAQ
The XDC docs give https://erpc.xinfin.network for XDC mainnet (chain ID 50) and https://rpc.apothem.network for the Apothem testnet (chain ID 51). The table above shows which public endpoints answer right now.
50, which is 0x32 in hexadecimal. The Apothem testnet is 51 (0x33).
Look at the Status column above. Online means the endpoint answered our last check with a valid block and the right chain ID. Offline means it did not, and Rate limited means it refused our server because of too many requests. If one endpoint is down, switch your wallet to another one from the table.
It changes from minute to minute. The board shows the fastest endpoint right now and each one's 24-hour median and 95th percentile, measured from our server. Your own best choice depends on where you are, so try two or three.
Open Settings, Networks, Add a network, and enter the network name, an RPC URL from the table, chain ID 50 and the symbol XDC, or press the button in the wallet settings above and approve the request in your wallet.
https://rpc.apothem.network, with chain ID 51 and the symbol TXDC. Test XDC comes from the Apothem faucet and has no value.
The endpoint is limiting how many calls your address can make. Wait a few minutes, send fewer calls, or add a second endpoint to fall back on. Heavy use needs your own node or a provider.
The XDC docs still list it, but we do not recommend it. The table checks it from your browser, so you can see how it answers today.
Our server checks every endpoint it can reach on a fixed schedule, and the board shows the interval under Answering correctly. The page looks for new results every 30 seconds. Single check results are kept for 48 hours and hourly results for 90 days.
It is how many blocks an endpoint is behind the highest block seen in the same check. A node that lags returns old balances and can reject transactions that depend on the latest state.
The ones listed here can be called without an account or API key. Some limit how often one address may call them, and none of them comes with a service promise that we could find.