Polygon Outage History

26 incidents recorded over the last 365 days, 26 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.

Live Polygon status100.00% uptime history

Every Recorded Polygon Incident

Polygon incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Sep 19, 2026Degraded Performance on Block ProducerThe degraded block producer has been rotated and the fix has been applied. The network is healthy again. We've confirmed the network has remained healthy and stable.-30 minResolved
Jul 30, 2026Wallet values showing $0 on Polygon PortalThe issue is now resolved.3h 57mResolved
Jul 16, 2026OMSX Dashboard LoginThe issue affecting the OMS X dashboard, caused by a global CloudFront outage, has been resolved. Dashboard functionality is back to normal, and we've confirmed there's no ongoing impact. For further details, you can…20 minResolved
Jun 23, 2026Heimdall V1 → V2 migration(Amoy)**Date:** June 24–25, 2025**Time:** **19:00 UTC \(June 24\) – 02:30 UTC \(June 25\)Status:** Resolved**Affected Services:** • Amoy Heimdall Services \(Validator Sync, APIs\) • Amoy Staking Dashboard **Summary** On…-523985 minResolved
Jun 23, 2026Planned Migration – Heimdall V1 → V2Date: Thursday, July 10, 2025Incident Window: 14:00 – 23:00 UTCStatus: ResolvedAffected Services:portal.polygon.technology \(User Portal\)staking.polygon.technology \(Staking Dashboard\)heimdall-api.polygon.technology…-501245 minResolved
Jun 23, 2026Polygon portal(Amoy)This incident has been resolved.-472419 minResolved
Jun 23, 2026Mainnet heimdall haltedThis incident has been resolved.-472623 minResolved
Jun 23, 2026Amoy heimdall haltedThis has been fixed and a new release containing the fix is out: https://forum.polygon.technology/t/heimdall-v2-v0-2-13-beta-amoy/21158/1-482895 minResolved
Jun 23, 2026Polygon portal**Date:** July 20, 2025**Time:** 01:47 UTC – ~02:47 UTC**Status:** Resolved **Affected Services** • [https://portal.polygon.technology/bridge](https://portal.polygon.technology/bridge) **Summary** At approximately…-485805 minResolved
Jun 23, 2026USDC Bridging on Polygon PortalResolved: The issue affecting USDC bridging via the CCTP bridge on Polygon Portal has been fixed. All bridging functions are now fully operational.-430945 minResolved
Jun 23, 2026Polygon PortalDate: August 08, 2025 Time: 04:00 UTC Status: Resolved Affected Services https://portal.polygon.technology/bridge Summary As of 04:00 UTC on August 08, 2025, the bridge on the Polygon Portal has been impacted. A…-460085 minResolved
Jun 23, 2026Network UpdateAll RPC services have now been fully restored, and user-facing services are back to normal. We’ve implemented a fix for the root cause to prevent recurrence. A full post-mortem will be published soon. Huge thanks to all…-471348 minResolved
Jun 23, 2026Amoy Testnet --> Heimdall stalledImpact: Heimdall halted on amoy testnet which lead to an interruption for the heimdall-api, tendermint-api and related transaction activities. Status: The issue has been resolved and the services on heimdall and…-430445 minResolved
Jun 23, 2026Amoy → Sepolia Checkpoint DelaysThe checkpointing issue between Amoy and Sepolia has been resolved. Recent checkpoints have processed successfully and bridging is operating as expected. We will continue routine monitoring, but no further impact is…-430523 minResolved
Jun 23, 2026Polygon to Ethereum Asset Withdrawals ImpactedOn September 10, 2025, at 04:30 UTC, the Polygon network experienced a degradation in its milestone finalization mechanism.   A rare race condition between milestone processing and block importing caused an…-410882 minResolved
Jun 23, 2026Consensus Finalization Delay – Temporary IssueThis incident has been resolved.-411065 minResolved
Jun 23, 2026Amoy Testnet – Erigon Performance IssueThe incident has been resolved and we continue to monitor-315963 minResolved
Jun 23, 2026Token balance issue on Polygon portalUpdate: we have resolved token balances not showing accurately in the UI due to a temporary issue on the Balance API. There were no impacts to network operations, and the UI is now reflecting all balances. Thank you for…-352865 minResolved
Jun 23, 2026Rio Upgrade & HardforkThis incident has been resolved.-370330 minResolved
Jun 23, 2026Amoy Testnet Bor Halt**Summary** On **Dec 10, 2025**, the **Amoy Testnet** stopped producing blocks starting at **~09:44 UTC** \(halt occurred at **block** 30,273,158\). The network recovered once the affected block producer's Heimdall and…-281138 minResolved
Jun 23, 2026Intermittent Stuck TransactionsThis incident has been resolved.-276905 minResolved
Jun 23, 2026Amoy Testnet – Erigon Performance IssueWe have release a new version (v3.3.1-beta3) for Erigon amoy that resolves the issue.-308140 minResolved
Jun 23, 2026Partial Bor Halt**Overview** • On 17th Dec 2025, there were reports of multiple Mainnet Bor nodes at RPC providers stuck at a few particular blocks in the range from `80440819` to `80443486` but the block production remained healthy…-269818 minResolved
Jun 23, 2026Amoyscan Explorer Degraded ServiceThe fix has been implemented and the issue is resolved.-166113 minResolved
Jun 23, 2026Polygonscan Explorer Degraded ServiceThis incident has been resolved.-185668 minResolved
Jun 23, 2026Finality Delay**Summary** On Jan 12th, 2026, the Polygon PoS Mainnet experienced a delay in block finalization starting at approximately 16.00 **UTC**, caused by repeated proposal rejections at the consensus layer. The incident was…-233182 minResolved

Hear about the next one while it is open

Everything above is a record written after the fact. We can email you when the next Polygon incident opens instead, at the point where knowing still changes what you do.

Free, no password, no card. Unsubscribe in one click.

How to Read This Polygon Incident Log

Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Polygon acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.

Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.

The longest single Polygon outage in this window ran 3h 57m, against a mean recovery of 2h 9m. If you depend on Polygon in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.