MetaMask “Failed to Fetch” Error on Token Balances: What It Means and How to Fix It

09 October 2026

When MetaMask displays a “Failed to fetch” error on your token balances, it means the wallet’s built-in price and balance data provider (typically CoinGecko or a similar API) could not retrieve current information for that specific token. This is a data connection issue, not a problem with your funds. Your tokens remain safe in your wallet. The fix usually involves clearing your browser cache, switching RPC endpoints, or manually refreshing token data - steps that take less than a minute.

Why the error happens

MetaMask relies on third-party APIs to fetch token prices, logos, and balances. The “failed to fetch” error occurs when:

• Your internet connection is intermittent or blocked (VPNs, firewalls, or ad blockers can interfere).
• The API server is temporarily down or rate-limiting requests.
• The token contract address is unrecognized by the default data provider.
• Your browser cache or MetaMask extension data is stale or corrupted.

The error does not mean the network rejected your transaction or that your tokens are lost. It is purely a display issue.

Step-by-Step Fixes

Try these in order. Most users find success with step 1 or step 2.

1. Refresh the Token List

• Open MetaMask and click the Assets tab.
• If you see only one token showing the error, click the token name to open its detail page. Wait 10 - 15 seconds - MetaMask will retry the fetch automatically.
• If the entire token list is affected, click the three-dot menu (top right) and select Refresh list. This forces a full reload of token data from the API.

2. Clear Browser Cache and Reload

Cached data can become outdated or corrupted.

• In your browser, go to settings → privacy & security → clear browsing data.
• Select Cached images and files (do not clear cookies or site data unless you want to lose other site logins).
• Close and reopen the browser. Reload the page with MetaMask open.

3. switch RPC endpoint

If the error persists, the RPC node MetaMask uses to query on-chain balances may be slow or unresponsive.

• Go to Settings → Networks → select the network (Ethereum mainnet, for example).
• Under RPC URL, replace the default endpoint with a public alternative. For Ethereum mainnet, you can use:
• https://eth.llamarpc.com
• https://rpc.ankr.com/eth
• Save the change. The token balances should reload within 30 seconds.

Note: Changing the RPC only affects how MetaMask reads on-chain data. It does not change the network you’re transacting on.

4. Re-Add the Token Manually

For tokens that fail to fetch even after the above steps, remove and re-add them:

• In MetaMask, click the token that shows the error → Remove token.
• Click Import tokens (at the bottom of the Assets tab).
• Paste the token’s contract address (copy it from a trusted source like Etherscan or the project’s official site).
• MetaMask will attempt to fetch the token details again. If it succeeds, the balance and price will appear.

5. Disable Ad Blockers and VPNs Temporarily

Ad blockers or privacy extensions sometimes block the API requests MetaMask makes from your browser.

• Disable any ad blocker (uBlock Origin, AdBlock, etc.) on the MetaMask extension page or on the dApp site you’re using.
• If you’re using a VPN, try turning it off or switching to a different server location. Reconnect MetaMask.

6. Reset MetaMask Extension (Last Resort)

This clears all cached data and resets the extension to a clean state without affecting your seed phrase or accounts.

• In your browser’s extension manager, find MetaMask.
• Click Remove (or disable, then re-enable).
• Reinstall MetaMask from the official Chrome Web Store or Firefox Add-ons page. Log in with your seed phrase.
• Your token list will be empty, but your balances are intact. Re-add tokens as needed.

When to Worry

You do not need to worry if the error only appears in the MetaMask extension but your tokens show correctly on a block explorer (e.g., Etherscan for Ethereum, BscScan for BNB Chain). To verify:

• Copy your public wallet address (starting with 0x).
• Paste it into the appropriate block explorer.
• Check the token balances listed there.

If the block explorer shows the correct balance, your funds are safe. The “failed to fetch” error is a cosmetic glitch.

Preventing Future Errors

• Keep MetaMask updated to the latest version.
• Use a reliable internet connection when checking balances.
• Avoid adding obscure tokens with non-standard contract implementations - they are more likely to trigger API failures.
• If you consistently see this error on a specific network, consider switching your default RPC to a more stable provider (see step 3).

The “failed to fetch” error is one of the most common and least alarming MetaMask issues. It never means your funds are gone or your wallet is compromised. The fixes above will restore your display in minutes.

Back to metamask