# Polygon PoS Incident Post-Mortem Source: https://etherworld.co/polygon-pos-incident-post-mortem Kiwi News: https://news.kiwistand.com/stories/Polygon-PoS-Incident-Post-Mortem?index=0x6945d8840064cab7fdffbf56cf32e480d2eda6a6b4f06f308d7d2fe5c521210312041345 Submitted by misha on 2025-12-19 UTC, 1 upvote, 0 comments ## Summary On December 17-18, 2025, Polygon PoS suffered a partial service disruption in Bor, its block-producing and transaction execution client, which mainly degraded RPC availability across several infrastructure providers. The chain itself stayed online: block production continued, validators remained active, and transactions were still processed, with no halts or reorgs. Multiple Bor nodes stalled at the execution layer, causing RPC request failures, temporary validator desynchronization, and lagging block explorers. Polygon engineers set up a war room and deployed a targeted patch to affected operators, after which nodes resynchronized and validators returned to quorum. ## Article 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: Redundant RPC providers reduce user impact Client concentration increases correlated failure risk Observability gaps can distort outage perception 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 Polygon PoS Hard Fork Polygon's L2 Solution How to Use Polygon testnet? Polygon announces to launch zKEVM mainnet beta How Polygon is helping Blockchain Movement in India? Disclaimer: The information contained in this website is for general informational purposes only. The content provided on this website, including articles, blog posts, opinions, & analysis related to blockchain technology & cryptocurrencies, is not intended as financial or investment advice. The website & its content should not be relied upon for making financial decisions. Read full disclaimer & privacy policy. For Press Releases, project updates & guest posts publishing with us, email contact@etherworld.co. Subscribe to EtherWorld YouTube channel for ELI5 content. Share if you like the content. Donate at avarch.eth. You've something to share with the blockchain community, join us on Discord! Follow us on Twitter, Facebook, LinkedIn & Instagram.