Arc
Chain ID
Native token
Endpoints
responding
Median latency
from one probe location
Last check
Source: The newest check on this network's endpoints and faucets.Endpoints
8 public endpoints listed. 5 of 5 checked responded in the last 24h, median 95 ms from DIA's probe in Nuremberg, Germany. 3 not checked.
8 endpoints listed · DIA probe,
| Endpoint | Provider | Status | Latency |
|---|---|---|---|
https://rpc.blockdaemon.mainnet.arc.io | arc.ioOfficial | Responding | 48 ms |
https://rpc.drpc.mainnet.arc.io | arc.ioOfficial | Responding | 101 ms |
https://rpc.mainnet.arc.io | arc.ioOfficial | Responding | 99 ms |
https://rpc.quicknode.mainnet.arc.io | arc.ioOfficial | Responding | 94 ms |
wss://rpc.blockdaemon.mainnet.arc.io/websocketWSS | arc.ioOfficial | Not checked | – |
wss://rpc.quicknode.mainnet.arc.ioWSS | arc.ioOfficial | Not checked | – |
https://arc.drpc.org | DRPC | Responding | 95 ms |
wss://arc.drpc.orgWSS | DRPC | Not checked | – |
Sources and method
- Network identifier (CAIP-2):
eip155:5042 - Identity listed from docs.arc.io, reviewed 20 Oct 2026.
- Chain ID and native currency are cross-checked against chainid.network (MIT licence). It is a reference, not a check of the endpoints.
DIA's probe sends up to two read-only requests to each listed endpoint, every six hours, from Nuremberg, Germany. Listed endpoints have answered at least once, or cannot be checked yet. One shows as Down only after four failed checks in a row, and the ones the probe cannot check read "Not checked". Read the full method.
