BlocksInform
Polygon blockchain explorer polygonscan has recently entered a short, caused by a synchronization error on the polygon backbone.
Based on polygon declarations, the explorer appeared to have no transactions to run, a state that caused confusion across polygon networks and users. This prompted Polygon chief Sandeep Nailwal to issue a statement on the matter, suggesting the use of OKLink, an alternative blockchain explorer.
It was not long before the polygon put out the fire. A polygon spokesman said that its bulk production had not ceased and that the problem was simply on certain ungated nodes. The spokesman also acknowledged that the network's performance may have deteriorated. Only the polygons were touched, not the whole platform. PolygonScan has since been operational and has shown that the issue might have been due to an issue with block reorganization that caused the nodes to go out of sync.
Network analyses indicated that a 157 block redesign was necessary to reorganize the polygon. 'At approximately 8:26 UTC, some knots broke down. It provoked a reaction in which some nodes could not validate blocks for a very short period of time,' said a polygon spokesman, adding that it was possible that "system performance degradation" was observed for a short period of time, impacting other polygon based infrastructure. 157 block redesign requires manual restoration of chain history, based on offline backups.
CryptoDaily recently covered how Polygon announced that it was laying off 20% of its workforce to consolidate its efforts. Breakdowns are certainly not new in the polygon. Unsuspecting users may remember that last year (March 2022) the polygon was reduced by more than 11 hours as a result of a technical upgrade.
Some crypto Twitter critics have also been speculating that the sync errors were somehow connected with the massive lay-off just days ago. This was not corroborated, however, as the oklink search results show an ongoing function for the polygon's main network. There was no statement from the polygon as to whether the outage was actually related to layoffs or whether its internal activities were affected.
