The Polygon Mumbai explorer no longer shows live data because Mumbai itself is gone. Polygon deprecated the Mumbai testnet (chain ID 80001) on 13 April 2024, after Ethereum's Goerli testnet shut down. Its replacement is Amoy, chain ID 80002, which you can explore on amoy.polygonscan.com or in the Amoy tab of our live Polygon explorer.
If you landed here from an old tutorial, a bookmark to mumbai.polygonscan.com or a config file that suddenly stopped working, you're in the right place. We'll cover what happened, what's still visible, and how to migrate without losing a day.
The date Polygon deprecated the Mumbai PoS testnet. Amoy has been the official testnet since.
What was the Mumbai testnet?
For several years, Mumbai was the place where Polygon developers tested everything. It ran the same PoS stack as mainnet, with test MATIC for gas, and its checkpoints went to Ethereum's Goerli testnet the way mainnet checkpoints go to Ethereum. Mumbai PolygonScan was the Polygon testnet explorer most tutorials pointed to, and "Mumbai" became almost a synonym for "Polygon testing".
That dependency on Goerli is what sealed its fate. A PoS testnet needs a live Ethereum testnet underneath to anchor checkpoints and run bridge contracts. When the Ethereum community retired Goerli in favour of Sepolia and Holesky, Mumbai couldn't continue.
Why Polygon shut Mumbai down
The shutdown was planned and announced well ahead. Polygon launched Amoy in late 2023, anchored to Sepolia, and encouraged teams to move. Mumbai was then deprecated in April 2024. After that date, the network stopped being maintained, faucets were switched off and infrastructure providers dropped their Mumbai endpoints.
Goerli retired
Ethereum's Goerli testnet, which anchored Mumbai's checkpoints, was shut down by the Ethereum community.
Amoy launched
A new PoS testnet on Sepolia went live in late 2023 with chain ID 80002.
Mumbai deprecated
On 13 April 2024, Mumbai lost official support; explorers and RPCs followed.
There was also a practical side. Mumbai had accumulated years of state, spam and abandoned contracts, and test MATIC had become hard to get, with faucets drained and a grey market for "testnet tokens". A fresh testnet solved those problems as well.
Can you still use a Mumbai explorer?
Short answer: not for anything important. In our September 2026 checks:
| Where | Mumbai status |
|---|---|
| mumbai.polygonscan.com | No live data served |
| OKLink Mumbai | Dropped or frozen |
| Public Mumbai RPCs | Offline at major providers |
| Our explorer | No Mumbai tab; Amoy instead |
The underlying chain data isn't "deleted" in any dramatic sense. But without running nodes and indexers, nobody has a strong reason to keep serving it, and archived explorer pages can vanish at any time. If a search result still shows a cached Mumbai page, treat it as a curiosity, not a source of truth.
For contracts that matter, the standard advice applies: keep the source code, compiler settings and deployment scripts in version control. With those, you can redeploy on Amoy in minutes and point anyone who asks to a live, verified contract.
What happened to test MATIC and the Mumbai faucets
Mumbai's gas token was test MATIC, handed out by the official Polygon faucet and by faucets from infrastructure providers. Once the network was deprecated, those faucets were switched off or pointed at Amoy instead. Any test MATIC left in your wallet is stranded on a chain that no longer runs, and that's fine: it never had value.
You may still see offers to "buy Mumbai MATIC" or "buy testnet tokens" on forums and chat groups. Ignore them. Test tokens are free by design, Mumbai tokens are now useless, and these offers are a common way to trick newcomers into sending real crypto. The same goes for anyone offering to "recover" Mumbai balances.
Why Mumbai still shows up in wallets and search results
Two years after the shutdown, Mumbai hasn't fully disappeared from the internet, which confuses people who are new to Polygon.
Wallets keep old networks. If you added Mumbai to MetaMask years ago, it stays in your network list until you remove it. Selecting it now usually produces RPC errors or endless loading, because the endpoints behind it are gone. Some wallets and chain lists still include Mumbai as a legacy entry.
Search engines keep old pages. Tutorials, videos and forum threads from 2021–2023 still rank for "Polygon testnet". Many show screenshots of the Mumbai explorer with test MATIC balances. The code in them is often still useful, but the network details are wrong.
Libraries keep old constants. Some older versions of SDKs and chain-list packages still export a Mumbai config. If you pin an old dependency, you may silently inherit it. Upgrading to a current version, or defining Amoy explicitly in your own config, avoids surprises.
If you want to check that a network entry in your wallet is really Amoy and not a leftover, look at the chain ID: it must be 80002. Our live explorer's Amoy tab is a quick way to confirm that a test transaction you just sent actually landed.
Mumbai vs Amoy: key differences
Amoy isn't a clone of Mumbai. It's a new testnet with a few important changes.
| Mumbai (retired) | Amoy (current) | |
|---|---|---|
| Chain ID | 80001 | 80002 |
| Anchored to | Goerli | Sepolia |
| Gas token | Test MATIC | Test POL |
| Explorer | mumbai.polygonscan.com | amoy.polygonscan.com |
| Status | Deprecated Apr 2024 | Active |
The switch from test MATIC to test POL mirrors what happened on mainnet, where POL replaced MATIC as the gas token in September 2024. If your code or UI hard-codes the "MATIC" symbol, now is the time to change it. The Polygon PoS explorer page explains the MATIC to POL story in detail.
Amoy also follows the mainnet upgrade path. The Heimdall v2 hard fork, which cut PoS finality to about five seconds, and the throughput upgrades of 2025 all shipped on Amoy first. Tests on Amoy therefore reflect mainnet behaviour far better than anything you ran on Mumbai.
Migration checklist: Mumbai to Amoy
We've migrated our own test tooling and helped readers do the same. This is the checklist we use.
- Search your codebase for 80001. Also look for "mumbai", "0x13881" (Mumbai's hex chain ID) and old RPC hosts. They hide in
.envfiles, CI secrets, Hardhat and Foundry configs, and frontend constants. - Replace network settings. Chain ID 80002, currency POL, explorer URL
https://amoy.polygonscan.com/, and a working Amoy RPC. Our network settings page has tested endpoints and an "Add to MetaMask" button. - Fund a deployer on Amoy. Claim test POL from the Polygon faucet. Mumbai test MATIC can't be moved.
- Redeploy contracts. Run your deployment scripts against Amoy. Expect new contract addresses; nothing is carried over.
- Re-verify source code. Use an Etherscan API V2 key with chain ID 80002 so contracts show as verified on Amoy PolygonScan.
- Update addresses everywhere. Frontend config, subgraph manifests, backend services, docs and READMEs. Stale Mumbai addresses in docs are the most common leftover we see.
- Redeploy test tokens and mocks. If your app depended on Mumbai test tokens or third-party test contracts, check whether they exist on Amoy or deploy your own mocks.
- Update wallets and team docs. Remove Mumbai from team wallets to avoid confusion, and add Amoy.
After the move, run your full test suite against Amoy rather than assuming it behaves exactly like your old Mumbai setup. Two things tend to show up. First, gas settings: scripts that hard-coded a low priority fee on Mumbai can hit "transaction underpriced" errors on Amoy, so let your tooling estimate fees. Second, timing: finality on Amoy follows today's PoS rules, so tests that waited dozens of blocks for "safety" can be shortened, while tests that assumed reorgs might need rethinking. Paste a couple of fresh Amoy transaction hashes into an explorer to confirm the basics (status, gas used, emitted events) before you tick the migration off.
The detailed Amoy workflow, including faucets and verification commands, is in our Amoy testnet explorer guide. Polygon's own developer documentation lists the current testnet parameters if you want to double-check against the source.
Old tutorials that still say "Mumbai"
A lot of Polygon tutorials, courses and Stack Overflow answers were written between 2021 and early 2024, so they tell you to add Mumbai, use test MATIC and open mumbai.polygonscan.com. The Solidity and tooling parts are usually still fine. Swap the network details as follows and most tutorials work unchanged:
- Mumbai → Amoy
- 80001 → 80002
- Test MATIC → test POL
- mumbai.polygonscan.com → amoy.polygonscan.com
- Goerli (for bridging tests) → Sepolia
polygon-rpc.comor old Mumbai endpoints → a current public or provider RPC
One more trap: some tutorials use the old public polygon-rpc.com endpoint for mainnet. It now returns an authentication error, so replace it too.
Moving from testnet to mainnet
Once your contracts behave on Amoy, the step to Polygon PoS mainnet (chain ID 137) is small: change the chain ID and RPC, fund the deployer with real POL, deploy and verify on PolygonScan. Mainnet gas costs fractions of a cent for most transactions, though deploying a large contract costs more. If you need real POL for that deployment, buy it on a regulated exchange that holds licences in several jurisdictions and withdraw it directly to the Polygon PoS network, not Ethereum.
After launch, you'll want a good mainnet explorer. Our ranking of the best Polygon explorers compares PolygonScan, Blockscout, OKLink and others on data depth, API access and developer features, so you can pick the one that fits your workflow.