Polygon Amoy Faucet Not Working? Separate the Faucet Failure From the 2026 RPC Change

If a Polygon Amoy faucet is not working in August 2026, first check whether the tutorial you followed is outdated. Polygon's current test-token documentation says its official faucet is no longer available and directs developers to third-party faucets. Polygon also retired the old public Amoy RPC at rpc-amoy.polygon.technology on July 17, 2026. Amoy itself is still active: the current network is chain ID 80002, uses POL for gas and is listed with the Amoy Polygonscan explorer. Diagnose the funding provider and the chain connection separately before requesting more test POL.

Two old Amoy instructions can now fail for different reasons

A 2024 or 2025 tutorial may tell you to use faucet.polygon.technology and rpc-amoy.polygon.technology. As checked on August 8, 2026, Polygon's dedicated test-token page says the official Polygon Faucet is no longer available and lists third-party faucets instead. Separately, Polygon announced that its free public Amoy RPC would stop being maintained after July 17, 2026. A developer can therefore face a dead funding source, a dead RPC, or both.

Amoy itself has not been retired

Do not confuse those service retirements with retirement of the testnet. Polygon's current RPC reference still lists Amoy as the Polygon Chain testnet, with parent chain Sepolia, chain ID 80002, gas token POL and the Amoy Polygonscan explorer.

Use the Amoy Breakpoint Matrix

Find the first layer that does not produce evidence.

• Funding Source — are you using a faucet that Polygon currently lists or a stale first-party URL?
• Provider Gate — did that faucet accept your address under its current cooldown and eligibility rules?
• Dispatch Proof — did the provider return a transaction hash or other evidence that POL was sent?
• Amoy Proof — does the exact address show the resulting POL or transaction on chain ID 80002?
• Wallet/RPC View — does the wallet or development tool read Amoy through a current working RPC and display the same address?

Breakpoint 1 — the tutorial still points to the old Polygon faucet

Polygon's current dedicated faucet documentation says the official Polygon Faucet is no longer available and instructs developers to use third-party faucets. It currently lists Alchemy, QuickNode, GetBlock and StakePool for PoS Amoy. Treat that specialized faucet page as the practical funding directory rather than repeatedly refreshing an old faucet URL.

Polygon's own documentation currently contains a faucet inconsistency

The current RPC reference still says testnet tokens are available from the Polygon faucet, while the dedicated Test token faucets page says the official faucet is no longer available. Because the more specific faucet page explicitly provides replacement providers, this article uses that page for faucet availability and the RPC page for network identity. Recheck both when Polygon updates the documentation.

Do not use a permanent 'best Amoy faucet' ranking

Third-party faucet capacity and anti-abuse rules can change quickly. Use Polygon's current provider directory, then verify the live provider page before relying on an amount, cooldown or eligibility requirement. A provider that works today can be rate-limited or change its rules tomorrow.

Breakpoint 2 — the provider rejected the claim before sending

A cooldown, wallet-history requirement, mainnet-balance requirement, authentication failure or existing-testnet-balance rule is a provider decision. No Amoy transaction has failed yet. Save the exact rejection and either wait for that provider's reset condition or choose another provider currently referenced by Polygon whose independent rules you legitimately satisfy.

Alchemy currently applies wallet eligibility to Amoy

Alchemy's live Polygon Amoy faucet currently advertises 0.1 POL per day. Its published eligibility rules for EVM faucets require at least 0.001 ETH on Ethereum Mainnet, sufficient mainnet activity and a low enough existing testnet balance. A rejection under those rules is not an Amoy outage.

Alchemy's live page and Polygon's directory disagree on the exact drip amount

Polygon's current faucet documentation says Alchemy can provide 0.5 POL per day to signed-in users and 0.2 without an account, while Alchemy's own live Amoy page currently says 0.1 POL per day. Do not hard-code Polygon's summary into a script or tutorial. For a provider-controlled limit, the live provider claim page should be checked immediately before requesting.

QuickNode currently uses a 12-hour per-network cooldown

QuickNode's live Polygon Amoy faucet currently states one drip per network every 12 hours. It asks the user to connect a supported wallet, and Polygon's faucet documentation says sharing the faucet URL on X can increase the drip. A 12-hour limit at QuickNode does not create a network-wide 12-hour Amoy limit.

GetBlock currently has a real-mainnet gate

GetBlock's live Polygon Amoy faucet currently advertises 0.1 POL per day and requires registration or login. Its claim instructions also require the wallet to hold at least 0.005 ETH on Ethereum Mainnet as an anti-abuse measure. If your wallet has zero mainnet ETH, retrying that same provider will not solve the eligibility gate.

Provider requirements are independent

Polygon's directory tells you which services currently support Amoy, but each provider controls its own anti-abuse system. Do not assume that Alchemy's 24-hour rule, QuickNode's 12-hour cooldown or GetBlock's mainnet-balance requirement applies to every Amoy faucet.

Do not bypass faucet limits with wallet farms, VPN rotation or scripted retries

A cooldown or eligibility rule is a completed provider diagnosis. Creating multiple identities, cycling addresses solely to evade limits or automating aggressive retries attacks the provider's anti-abuse controls and can make access worse. Use another legitimate provider only under that provider's own rules.

Breakpoint 3 — the provider says success but gives no chain proof

A green browser message is weaker evidence than an Amoy transaction. If the provider says the claim was sent, save any transaction hash or sender record. Polygon's current faucet instructions for Alchemy and QuickNode explicitly tell users to inspect the transaction on Amoy Polygonscan.

If there is no hash and the Amoy balance never changes, classify it as not dispatched

Do not repair MetaMask first when there is no chain evidence. Check the faucet's status or support channel, then verify the exact receiving address independently on Amoy. If the address never receives POL, the funding path failed before wallet display became relevant.

Breakpoint 4 — prove the claim on chain ID 80002

Polygon currently identifies Amoy with chain ID 80002. Search the exact receiving address or faucet transaction on Amoy Polygonscan. If the transaction succeeded and the address balance increased there, the faucet step is complete. Stop requesting more POL and move to wallet or RPC diagnosis.

Polygon mainnet is not Amoy

Polygon mainnet uses chain ID 137. Amoy uses 80002. The same 0x address can exist on both networks with independent balances. Test POL arriving on Amoy does not create POL on Polygon mainnet.

Mumbai instructions are obsolete for new Polygon PoS testing

Amoy replaced the older Mumbai environment for Polygon PoS testing. If a tutorial still uses Mumbai chain ID 80001, a Mumbai faucet or Mumbai explorer, do not patch individual fields one by one. Replace the network configuration with current Amoy settings from Polygon documentation.

The native Amoy gas asset is now POL

Current Polygon documentation identifies POL as Amoy's gas token. Older tutorials and even some third-party pages can still use the former MATIC name. Do not search for an ERC-20 'test MATIC' contract merely because an old guide uses that label when the task requires native Amoy gas.

A ticker mismatch can be cosmetic, but the chain balance is decisive

A wallet configuration created before the POL transition may still display an old currency symbol. The important checks are chain ID 80002, the exact address and its native balance through a current Amoy explorer or RPC. Fix the wallet label after proving which chain it is actually reading.

Breakpoint 5 — the old Polygon-operated Amoy RPC was retired

Polygon announced that rpc-amoy.polygon.technology would be deprecated after July 17, 2026 and stop responding. If your wallet, Hardhat config, Foundry command, backend or tutorial still uses that endpoint, a faucet can send successfully while your application continues to show zero or throws RPC errors.

Polygon's current Amoy reference uses dRPC

As checked on August 8, 2026, Polygon's RPC reference lists https://polygon-amoy.drpc.org as the Amoy RPC endpoint and wss://polygon-amoy.drpc.org as the WSS endpoint. Use the current Polygon reference rather than copying rpc-amoy.polygon.technology from an old tutorial.

Do not confuse RPC failure with faucet failure

The faucet submits a blockchain transfer. Your wallet or development stack then reads chain state through an RPC. If Amoy Polygonscan proves the receiving address owns POL but your application shows zero, the faucet has already succeeded. Repair the network data source instead of spending another faucet claim.

A public RPC can still rate-limit you

Polygon's current RPC documentation warns that public RPCs can have rate limits or traffic restrictions. A working endpoint can therefore intermittently return 429, timeout or stale-looking application behavior under load. For repeated automated testing, use a provider whose limits match the workload.

Check the wallet account as well as the network

A browser wallet can hold several 0x accounts. Confirm that the address submitted to the faucet is the exact account currently selected in the wallet. Changing to Amoy cannot make POL appear under a different address.

If Amoy Polygonscan shows POL but the wallet does not, stop touching the faucet

At that point the funding incident is solved. Check the selected account, chain ID, current RPC, hidden test-network settings and wallet refresh. The existing testnet-token visibility guide owns the broader post-chain-proof problem.

If the faucet transaction is pending, do not request duplicates immediately

A provider can dispatch a transaction that has not yet confirmed. Track the returned Amoy hash first. A second claim adds noise, may trigger a cooldown and does not make the original transaction confirm faster.

If a transaction failed on Amoy, inspect the receipt rather than the faucet button

A failed on-chain transaction is different from a provider rejection. Preserve the transaction hash and receipt. The failure may involve sender gas, nonce, contract behavior or provider infrastructure. Repeatedly changing the receiving wallet cannot change the already-recorded transaction result.

If Amoy itself stalls, every faucet can appear broken

Testnets can have network-wide disruptions. Amoy had a documented block-production stall in May 2026 that was later resolved. When multiple independent faucets dispatch nothing and the explorer stops advancing, check Polygon's current status and community announcements before debugging individual wallets.

A faucet does not need your seed phrase

Legitimate faucet flows can ask for a public 0x address, wallet connection, provider account, social action or anti-abuse proof. They do not need the wallet recovery phrase or private key to send test POL. Close any page that asks you to reveal signing secrets.

Do not buy Amoy POL from a stranger

Polygon describes testnet tokens as having no real value and being used only for testing. If a public faucet is unavailable, use another current provider or reduce the development loop. Do not send mainnet crypto to an unknown seller for test POL.

For heavy testing, solve the development loop rather than harvesting faucets

Public faucets are intentionally constrained shared infrastructure. Unit tests, fuzzing and many deployment iterations can run against local EVM environments or forks. Reserve Amoy POL for integrations that actually need shared public testnet state.

Use six final Amoy verdicts

Finish the diagnosis with one explicit state.

• OUTDATED FAUCET — the tutorial points to the retired first-party Polygon faucet; choose a provider from Polygon's current faucet directory.
• PROVIDER REJECTED — cooldown, mainnet-balance gate, wallet activity or another anti-abuse rule stopped the claim before dispatch.
• NOT DISPATCHED — the provider claimed success but no transaction or Amoy balance evidence exists.
• CONFIRMED ON AMOY — chain ID 80002 shows the POL; the remaining problem is wallet or RPC visibility.
• LEGACY RPC — the app still points to the retired rpc-amoy.polygon.technology endpoint; migrate to a current Amoy RPC.
• WRONG NETWORK / LEGACY MUMBAI — chain ID, explorer or network configuration is not current Amoy.

The practical 2026 Amoy recovery sequence

Use this order and stop as soon as the failed layer is proven.

• 1. Confirm that the target network is Polygon Amoy, chain ID 80002, and the native test gas asset is POL.
• 2. Replace an old first-party Polygon faucet bookmark with a provider from Polygon's current Test token faucets page.
• 3. Read that provider's live eligibility and cooldown rules before claiming.
• 4. Save the exact response and transaction hash if one is returned.
• 5. Verify the receiving address and transaction on Amoy Polygonscan.
• 6. If POL exists on-chain, stop requesting and inspect the wallet account and RPC.
• 7. Replace rpc-amoy.polygon.technology if it remains in any configuration; Polygon retired it in July 2026.
• 8. If several independent services fail and Amoy block production looks abnormal, check current Polygon status before changing more code.

Why this page is not a duplicate of the Sepolia faucet guide

The Ethereum Sepolia article owns Ethereum L1 faucet failures, chain ID 11155111 and Sepolia-specific providers. This page owns Polygon Amoy chain ID 80002, native POL, Polygon's first-party faucet retirement, the July 2026 Amoy RPC retirement and the specific third-party providers listed by Polygon.

Why this page is not a duplicate of Base Sepolia troubleshooting

Base Sepolia is a separate L2 with chain ID 84532 and ETH as its native test gas asset. Amoy is Polygon's PoS testnet with chain ID 80002 and POL. The provider lists, RPC transition and legacy-network mistakes are different even though both networks use EVM-style 0x addresses.

Why this page stops after Amoy proves the balance

Once the exact address owns the expected POL on Amoy, the faucet has done its job. Generic wallet visibility, custom tokens, hidden testnets and stale UI state belong to the separate testnet-token visibility guide. Keeping that boundary prevents this page from becoming another generic 'wallet shows zero' article.

What can change after August 8, 2026

Faucet providers, drip sizes, mainnet-balance gates, cooldowns, RPC endpoints and Polygon documentation can change quickly. This article therefore uses a seven-day review window. The durable logic is the Breakpoint Matrix: current funding source, provider acceptance, dispatch evidence, Amoy chain proof and wallet/RPC view.

Sources checked on August 8, 2026

Current Polygon documentation and live provider pages were prioritized. Where Polygon's faucet summary conflicts with a provider's current live limit, the discrepancy is stated rather than silently reconciled.

• Polygon Developer Docs — Test token faucets — https://docs.polygon.technology/tools/gas/matic-faucet
• Polygon Developer Docs — RPC endpoints — https://docs.polygon.technology/pos/reference/rpc-endpoints
• Polygon Community Forum — Deprecation of Polygon public RPC endpoints, July 2026 — https://forum.polygon.technology/t/deprecation-of-polygons-public-rpc-endpoints-mainnet-amoy/22014
• Alchemy — Polygon Amoy Faucet — https://www.alchemy.com/faucets/polygon-amoy
• QuickNode — Polygon Amoy Faucet — https://faucet.quicknode.com/polygon/amoy
• GetBlock — Polygon Amoy Faucet — https://getblock.io/faucet/matic-amoy/
• Polygon — Introducing the Amoy Testnet for Polygon PoS — https://polygon.technology/blog/introducing-the-amoy-testnet-for-polygon-pos

FAQ