Polygon Status Page

May 7, 2026 · resolved May 7

Resolved: Amoy testnet block production restored after planned load test A planned load test on Amoy testnet caused a brief pause in block production while validators worked through a span rotation. Block production has fully resumed and the network is operating normally. Polygon mainnet (PoS) was not affected at any point. This event was isolated to Amoy and was part of ongoing capacity and failover testing. The team identified a recovery path during the event and the network is back to producing blocks as expected.

Apr 29, 2026 · resolved Apr 29

Problem: Some RPC providers and validators reported their Bor / Heimdall nodes stalled and unable to sync following the Phuket Heimdall hardfork. Impact: A small number of third-party RPC providers and validators experienced node syncing stalls. There was no impact to network finality or liveliness, and most RPC nodes / providers experienced no disruption. Causes: The Phuket Heimdall hardfork \(0.7.0 Heimdall\) caused some Bor / Heimdall nodes operated by a small number of RPC providers and validators to stall during syncing. This hard fork introduced an explicit dependency from Heimdall to Bor, so for more complex infrastructure where this dependency didn't exist \(for example Heimdall didn't have Bor configured\) or where the Bor node was not fully synced, Heimdall stalled. Steps to resolve: A new release, heimdall-v2 v0.7.1, was made available to fix the syncing issue by removing this explicit dependency, allowing Heimdall to continue syncing even if it was not connected to a fully synced Bor node. Impacted providers upgraded and resynced their nodes, which resolved the problem for all major providers, and updates have been posted to inform stakeholders.

Mar 7, 2026 · resolved Mar 7

We have resolved token balances not showing accurately in the UI due to a temporary issue on the Balance API on Polygon Portal. There were no impacts to network operations, and the UI is now reflecting all balances.

Feb 28, 2026 · resolved Feb 28

The fix has been implemented and the issue is resolved.

Feb 14, 2026 · resolved Feb 14

This incident has been resolved.