Scroll public RPC endpoints, tested
Every keyless Scroll (chain ID 534352) endpoint listed on Chainlist and chainid.network, tested the same way on 2026-11-08: does it answer on the right chain, how fast, how far behind the best head, how large an eth_getLogs range it accepts, whether it keeps archive state, and whether its WebSocket actually streams. 9 of 20 HTTP endpoints were working.
Working HTTP endpoints
| Endpoint | Latency | Behind best | eth_getLogs | State |
|---|---|---|---|---|
| https://rpc.swiftnodes.io/rpc/scroll (SwiftNodes, keyless: 2 req/s) | 6 ms | 1 blocks | under 1,000 | archive (1M+) |
| https://scroll-rpc.publicnode.com | 25 ms | 2 blocks | 10,000+ | archive (1M+) |
| https://scroll.api.pocket.network | 28 ms | 1 blocks | 10,000+ | archive (1M+) |
| https://scroll.drpc.org | 50 ms | 1 blocks | under 1,000 | archive (1M+) |
| https://rpc-scroll.blockmachine.io | 64 ms | 1 blocks | under 1,000 | none |
| https://lb.routeme.sh/rpc/evm/534352 | 67 ms | 0 blocks | under 1,000 | none |
| https://scroll.rpc.sentio.xyz | 162 ms | 1 blocks | under 1,000 | archive (1M+) |
| https://scroll.api.onfinality.io/public | 211 ms | 1 blocks | under 1,000 | archive (1M+) |
| https://rpc.scroll.io | 1193 ms | 2 blocks | 10,000+ | archive (1M+) |
Order: endpoints within 3 blocks of the best head first, then by median latency. Latency is measured from one server, so yours will differ by region; lag and limits do not.
WebSocket endpoints
- streams
scroll-rpc.publicnode.com: first head after 244 ms - streams
scroll.drpc.org: first head after 8223 ms - does not stream
rpc.swiftnodes.io/ws/scroll(SwiftNodes): subscribe rejected: WebSocket subscriptions require an API key. Get a free key at https://swiftnodes
Listed but not working
rpc.ankr.com/scroll: chainId: message: API key is not allowed to access blockchain, json-rpc code: -32052, rest code: 403scroll-mainnet.chainstacklabs.com: chainId: fetch failedscroll-rpc.blockreq.com/v1/rpc/public: no answer (HTTP 410)rpc.hostdefi.com/api/rpc/scroll: no answer (HTTP 403)rpc-scroll.icecreamswap.com: chainId: fetch failedscroll-mainnet.public.blastapi.io: chainId: Blast API is no longer available. Please update your integration to use Alchemy's API instepublic.1rpc.io/scroll: chainId: You've reached the usage limit for your current plan. To continue with higher limits and unscroll-public.nodies.app: no answer (HTTP 403)endpoints.omniatech.io/v1/scroll/mainnet/public: no answer (HTTP 521)scroll.therpc.io: no answer (HTTP 200)api-scroll-mainnet.n.dwellir.com/2ccf18bf-2916-4198-8856-42172854353c: chainId: rate limited
Test any endpoint yourself with the RPC tester. Our Scroll endpoint, limits and status: Scroll RPC, uptime history.