Between December 17 & December 18, 2025, the Polygon PoS network experienced a partial service disruption affecting Bor, the block-producing & transaction execution client. The issue primarily impacted RPC availability, leading to stalled responses across several infrastructure providers.

Importantly, the chain itself never went offline. Block production continued uninterrupted, validators remained active, & transactions continued to be processed throughout the incident.

• What Exactly Failed
• Response Timeline & Mitigation
• Broader Takeaways for the Polygon Ecosystem

What Exactly Failed

The incident was not a consensus failure. Instead, it emerged at the execution layer, where multiple Bor nodes stalled simultaneously. This resulted in:

• RPC request failures across several providers
• Temporary desynchronization among some validator nodes
• Block explorers lagging due to delayed node synchronization

Despite these disruptions, the block producer remained operational, confirming that Polygon’s consensus path was never compromised. Several core components of the Polygon PoS network remained stable throughout the incident:

• Blocks continued to be produced
• A subset of RPC nodes stayed fully operational
• Transactions were accepted & executed
• No chain halts or reorgs occurred

This afternoon, Polygon PoS experienced an issue affecting a subset of RPC nodes. The network remained online and continued producing blocks throughout the incident, with no chain downtime.

The team quickly identified and rolled out a patch to operators to restore full service…— Polygon Foundation (@0xPolygonFdn) December 17, 2025

This distinction is critical. The incident exposed infrastructure fragility, not protocol-level failure.

Response Timeline & Mitigation

Once the issue was detected, Polygon engineers activated a war room to coordinate investigation & remediation across teams & node operators.

A targeted patch was deployed to affected operators, after which nodes began resynchronizing & validators progressively returned to quorum. For most users, RPC availability defines whether a blockchain feels online.

Even though Polygon PoS continued producing blocks, degraded RPC access impacted wallets, dApps, explorers, & exchanges that depended on affected endpoints. This incident highlights a broader industry reality, i.e., execution infrastructure & access layers are now as critical as consensus itself.

Broader Takeaways for the Polygon Ecosystem

The Bor incident reinforces several structural lessons:

1. Redundant RPC providers reduce user impact
2. Client concentration increases correlated failure risk
3. Observability gaps can distort outage perception
4. Rapid operator coordination remains a strength

Polygon’s transparent updates & swift mitigation prevented escalation, but the event underscores the need for continued investment in infra-level resilience alongside protocol upgrades.

The December Bor incident was not a failure of Polygon PoS consensus, but a stress test of its execution & access layers. Polygon passed the most critical test, i.e., no chain halt, no data loss, no consensus break while also exposing areas that require further hardening as the network scales toward higher institutional & application load.

If you find any issues in this blog or notice any missing information, please feel free to reach out at yash@etherworld.co for clarifications or updates.

Related Articles

1. Polygon PoS Hard Fork
2. Polygon's L2 Solution
3. How to Use Polygon testnet?
4. Polygon announces to launch zKEVM mainnet beta
5. How Polygon is helping Blockchain Movement in India?