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-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. 7 of 11 HTTP endpoints were working.

Working HTTP endpoints

Endpoint	Latency	Behind best	eth_getLogs	State
https://manta-pacific.drpc.org	28 ms	1 blocks	under 1,000	archive (1M+)
https://manta-pacific-mainnet.rpc.sentio.xyz	168 ms	0 blocks	under 1,000	archive (1M+)
https://manta-pacific-gascap.calderachain.xyz/http	172 ms	1 blocks	10,000+	archive (1M+)
https://manta-pacific.calderachain.xyz/http	179 ms	0 blocks	10,000+	archive (1M+)
https://pacific-rpc.manta.network/http	192 ms	1 blocks	10,000+	archive (1M+)
https://rpc.swiftnodes.io/rpc/manta (SwiftNodes, keyless: 2 req/s)	224 ms	1 blocks	under 1,000	archive (1M+)
https://r1.pacific.manta.systems/http	312 ms	46 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 manta-pacific.drpc.org: first head after 4880 ms
streams manta-pacific.calderachain.xyz/ws: first head after 5927 ms
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

public.1rpc.io/manta: chainId: You've reached the usage limit for your current plan. To continue with higher limits and un
endpoints.omniatech.io/v1/manta-pacific/mainnet/public: no answer (HTTP 521)
lb.routeme.sh/rpc/evm/169: chainId: rate limited
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.