Polygonscan was “stagnant” for several hours on the morning of February 23, causing many people to mistakenly believe that Polygon was the problem.
In the early morning of February 23 (Vietnam time), rumors that the Polygon network was down for many hours made the crypto community stand still.
Specifically, Polygonscan data shows that this blockchain has not generated new blocks or processed any transactions since about 03:30 this morning.
However, about 2 hours later, Polygon co-founder Sandeep Nailwal corrected that blockchain activity tracker Polygonscan had problems, not the entire network.
It seems like Polygonscan is having some issues. You can use OKLink explorer in the meanwhilehttps://t.co/nt6vhGdF62
— Sandeep | Polygon Top 3 by impact (@sandeepnailwal) February 22, 2023
Founder Sandeep also recommends that users switch to OKLink temporarily to check transactions.
Exchange with Decrypt, Polygon representative said:
“New block generation never stops, however it is possible that the network has experienced a temporary drop in performance. The nodes were then synchronized and the system was back to normal.”
Although it did not cause a loss of money, the incident still caused panic in the crypto community on Twitter.
Why is no one talking about the fact that polygon’s last block was 2 hours ago? #Polygon #avax #Ethereum pic.twitter.com/8yKw22whfY
— ayman.avax🔺 (@avaxayman) February 22, 2023
am I reading this wrong or was the last polygon block 45 minutes ago? pic.twitter.com/uXHA8SeYHs
— mad mert | helius.xyz (@0xMert_) February 22, 2023
Someone took this opportunity to criticize Polygon and advise the above developers to consider moving to the rival Solana network.
The fact that Polygon is literally down right now is an absolutely UNDENIABLE TRUTH
There is a literal exodus of devs to Solana (check dev growth rates)
oops! 😉 https://t.co/ogqwQsWMXN
— macbrennan ️ (@macbrennan) February 22, 2023
Others have tried to link the incident to the decision to cut 20% of staff from Polygon that Kyptos reported on February 21.
As of the time of writing, the problem appears to have been completely fixed and Polygonscan is back up and running.
But in the past there was a time Polygon “silent” for 9 hours straight. Meanwhile, the community has become so used to the “stuck” problem on Solana network.