Skip to content
Coin Press

Reporting from across crypto

How to fix a Chainlist RPC outage and restore wallet access

What to do if a Chainlist RPC is down: test the endpoint, switch to another RPC for the same chain ID, and check whether pending transactions were broadcast.

Coin Press Newsroom4 min read

How to fix a Chainlist RPC outage and restore wallet access

Chainlist users should confirm the RPC is failing, then switch the wallet to another endpoint for the same chain ID; a public endpoint can fail while the chain keeps producing blocks.

  • You’ll know whether the endpoint is the problem and reconnect the wallet to a working RPC.
  • You’ll need the chain ID and a block explorer URL to compare the latest block and check pending transactions.

Say MetaMask shows a network error and the balance keeps loading. Chainlist is a directory of EVM network details, including RPC endpoints and chain IDs. chainlist.cc is the domain for Chainlist, where you can find another RPC endpoint for the network.

How do you restore a wallet connection when a Chainlist RPC is down?

Test the current endpoint by sending it the standard JSON-RPC method eth_blockNumber with curl. A timeout, HTTP 429 rate-limit response, or 5xx server error points to that endpoint. The chain ID method, eth_chainId, can also confirm which chain the endpoint reports.

Compare the returned block height with the block explorer for that chain. If the explorer shows newer blocks while the RPC’s height is stuck, the endpoint is stalled; the chain is still advancing. This distinction matters because changing the wallet’s RPC can restore access without changing networks.

Choose another RPC entry on Chainlist with the same chain ID, then set that URL as the network’s default in the wallet. The chain ID identifies the network; the RPC URL is the endpoint the wallet uses to read data and send requests.

In MetaMask, a network can store several RPC URLs, but the wallet uses only the selected default. It does not automatically fail over to a saved backup when that endpoint stops responding. So saving another URL alone will not restore the connection: select it as the default. When the balance and latest block load, the wallet is connected to a responsive endpoint.

Take a Polygon network with chain ID 137 where the current RPC returns 429. That response means the endpoint is rate-limiting requests. Set another listed Polygon RPC as the default for chain ID 137; when the new endpoint responds, the balance can load again.

Before resending a transaction submitted during the outage, look up the account on the block explorer. See whether the transaction appears and whether the account’s confirmed nonce has advanced. A transaction that never reached an RPC may never have been broadcast, while a confirmed nonce change can indicate a transaction was included. Use the explorer’s transaction details before deciding whether to resend.

Related questions

Why does MetaMask say 'could not fetch chain ID'?

MetaMask could not get a chain ID response from the selected RPC. Test that URL with eth_chainId; if it times out or errors, select another endpoint for the intended chain.

How to remove a broken RPC from MetaMask

Open the network’s settings in MetaMask, edit its RPC URL entry, and remove or replace the failing URL. Keep the chain ID correct for the network.

What else should you know about RPC and pending transactions?

How do I speed up or cancel a pending transaction?

Use the wallet’s speed-up or cancel option if the transaction is still pending and the wallet offers it. These actions typically submit a replacement transaction with the same nonce; check the wallet’s details before confirming.

What does RPC error -32603 mean?

Error -32603 is a general internal JSON-RPC error. The message alone does not identify the cause; check the endpoint response and request details.

Should I run my own node instead of using public RPCs?

A self-hosted node gives you control over the endpoint but requires setup and upkeep. For restoring a wallet connection, switching to another responsive public RPC is usually the simpler first step.