RPC unavailable during a swap: what did the chain receive?

An unavailable RPC endpoint means the wallet cannot reliably communicate with that endpoint. It does not establish whether a previously signed swap executed. Diagnose communication and transaction state separately.

Preserve the evidence before switching

Save the hash, chain, sender and approximate submission time. Check the network’s appropriate explorer and any official application status view. A wallet can lose connectivity after broadcast, leaving its activity display behind the chain.

The Ethereum provider standard distinguishes connection state from individual request outcomes. A successful connection also does not mean every contract call will succeed.

Use trusted network information

If you change RPC settings, use the network or wallet’s official documentation. Confirm the chain identifier; a familiar network name in a settings form is just a label.

Private transactions need special care. Flashbots warns that switching RPCs in MetaMask before confirmation can rebroadcast a pending private transaction publicly. Do not apply a generic switch-endpoint remedy without considering how the request was submitted.

Once connectivity returns, reconcile the original transaction before signing a new one. If it confirmed, inspect the receipt. If it remains pending, manage that request. If it never reached a provider, the application may need a freshly reviewed submission.

Repeated errors across several applications may indicate a wallet or network connection problem; an error affecting one token route may instead be contract-related. Record that distinction for support.