Manta Pacific public RPC endpoints, tested

Every keyless Manta Pacific (chain ID 169) endpoint listed on Chainlist and chainid.network, tested the same way on 2026-10-11: 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. 7 of 11 HTTP endpoints were working.

Working HTTP endpoints

EndpointLatencyBehind besteth_getLogsState
https://manta-pacific-mainnet.rpc.sentio.xyz162 ms0 blocks10,000+archive (1M+)
https://manta-pacific.calderachain.xyz/http171 ms0 blocks10,000+archive (1M+)
https://manta-pacific-gascap.calderachain.xyz/http180 ms1 blocks10,000+archive (1M+)
https://pacific-rpc.manta.network/http193 ms2 blocks10,000+archive (1M+)
https://rpc.swiftnodes.io/rpc/manta (SwiftNodes, keyless: 2 req/s)198 ms1 blocks10,000+archive (1M+)
https://manta-pacific.drpc.org24 ms5 blocksunder 1,000archive (1M+)
https://r1.pacific.manta.systems/http298 ms19 blocks10,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 manta-pacific.calderachain.xyz/ws: first head after 7038 ms
  • does not stream manta-pacific.drpc.org: subscribe rejected: method is not available on free plan, please upgrade to paid plan
  • does not stream rpc.swiftnodes.io/ws/manta (SwiftNodes): subscribe rejected: WebSocket subscriptions require an API key. Get a free key at https://swiftnodes

Listed but not working

  • lb.routeme.sh/rpc/evm/169: chainId: rate limited
  • public.1rpc.io/manta: chainId: timeout
  • endpoints.omniatech.io/v1/manta-pacific/mainnet/public: no answer (HTTP 521)
  • www.tencentcloud-rpc.com/v2/manta/manta-rpc: chainId: timeout

Test any endpoint yourself with the RPC tester. Our Manta Pacific endpoint, limits and status: Manta Pacific RPC, uptime history.