Metis public RPC endpoints, tested

Every keyless Metis (chain ID 1088) endpoint listed on Chainlist and chainid.network, tested the same way on 2026-09-24: 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 12 HTTP endpoints were working.

Working HTTP endpoints

Endpoint	Latency	Behind best	eth_getLogs	State
https://metis-rpc.publicnode.com	21 ms	1 blocks	10,000+	archive (1M+)
https://metis.drpc.org	28 ms	1 blocks	under 1,000	archive (1M+)
https://rpc.swiftnodes.io/rpc/metis (SwiftNodes, keyless: 2 req/s)	85 ms	1 blocks	10,000+	archive (1M+)
https://metis-public.nodies.app	109 ms	1 blocks	under 1,000	archive (1M+)
https://andromeda.metis.io/?owner=1088	110 ms	1 blocks	10,000+	archive (1M+)
https://metis.api.onfinality.io/public	206 ms	1 blocks	under 1,000	archive (1M+)
https://metis-andromeda.rpc.thirdweb.com	278 ms	0 blocks	under 1,000	none

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 rpc.swiftnodes.io/ws/metis (SwiftNodes): first head after 4293 ms
subscribed metis.drpc.org: accepted; this chain produced no block during the 15 s window
subscribed metis-rpc.publicnode.com: accepted; this chain produced no block during the 15 s window

Listed but not working

metis-mainnet.public.blastapi.io: chainId: Blast API is no longer available. Please update your integration to use Alchemy's API inste
metis.rpc.hypersync.xyz: chainId: fetch failed
api.blockeden.xyz/metis/67nCBdZQSH9z3YqDDjdm: chainId: A paid plan is required
metis-andromeda.gateway.tenderly.co: chainId: rate limited
lb.routeme.sh/rpc/evm/1088: eth_blockNumber failed

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