According to the data from the block explorer, the Avalanche protocol has not produced any blocks for approximately 2 hours, with the latest block being stuck at 20:02 UTC+8. The developers are currently conducting repair tests in the network and working hard to fix the issue.
Regarding this matter, Kevin Sekniqi, co-founder of Ava Labs, initially believed that the problem was caused by a newly released script being too popular, leading to issues in the network memory pool. However, he later clarified that the downtime was not related to the script and that the problem stemmed from a memory pool management error related to gossip.
Kevin Sekniqi stated, “This is purely a code-related error and not a performance handling issue. The script seems to have touched upon an edge case but did not affect the network’s performance.”
