Polygon Outage Sparks Debate: Is Polygon Reliable?

• Polygon’s blockchain explorer went down on Wednesday, February 22, sparking rumors that the entire Polyon blockchain had gone offline.
• The outage was caused by an “unusually large” block reorganization which caused some nodes to fail to validate blocks for a short period of time.
• Co-founder Sandeep Nailwal clarified the situation and most providers were back up within one hour.

PolygonScan Outage Causes Uproar

Polygon’s blockchain explorer went down yesterday, Wednesday, February 22, causing a lot of buzz and numerous rumors on Crypto Twitter (CT). The PolygonScan outage gave the impression that no transactions were taking place, prompting allegations from the Avalanche (AVAX) and Solana (SOL) communities in particular that Polygon was unreliable.

December 2022 Tweet Recalled

Don’t wait! Jump on this Crypto Deal and get a 150% Welcome Bonus plus 100 Free Spins on your deposit today! Critics referred to a December 2022 tweet by Polygon co-founder Sandeep Nailwal who asserted that the fact that “the Solana chain is unstable” is an absolutely irrefutable truth.

Network Continues To Produce Blocks

BitStarz Player Lands $2,459,124 Record Win! Could you be next big winner? 570% up to 12 BTC + 300 Free Spins for new players & 1 BTC in bonuses every day, only at Wild.io. Play Now! However, it turned out to be a minor problem that affected only the blockchain explorer as opposed to the entire network. It was revealed that “some nodes were out of sync” due to an “unusually large” block reorganization two minutes before they went out of sync. Although this caused some disruption in network performance temporarily, it did not affect the network itself as it continued to produce blocks almost flawlessly.

Explorer Back Up After Two Hours

Sandeep Nailwal quickly clarified the situation via Twitter writing: “It seems like PolygonScan is having some issues. You can use OKLink explorer in the meanwhile.” The issue took more than two hours for PolygonScan to resolve whereas Rivet was back up within one hour; however dapp developers relying on affected nodes faced difficulty in getting their services back online again.


Greg Lang from Rivet commented saying most providers didn’t handle this problem gracefully even though it wasn’t really a catastrophe but impacted more people than those who talked about it. In conclusion it can be deduced that while such situations can cause temporary disruptions in network performance they should be handled with care so as not cause unnecessary panic or confusion amongst users of various networks based on EVM technology or explorers related thereto