According to the indications, due to an anomaly, regarding half of Cardano’s nodes were disconnected and restarted over the weekend, the root cause is still being investigated.
Cardano’s stake pool operators (SPO – stake pool operator) and users also reported that at least half of the network’s nodes were down for a short time over the weekend.
Input Output Global, the development company behind the Cardano blockchain, shared on its Telegram SPO on January 22 registration According to an anomaly, 50% of Cardano nodes were disconnected and restarted.
“This appears to have been triggered by a transient anomaly that caused two reactions at the nodes. Some detached from a peer, others threw an exception and restarted.” the post explained the sudden break.
Despite the momentary outage, Cardano’s network recovered without external intervention. As explained in the post, “such emerging issues have been taken into account in node design and consensus, and systems now behave exactly as expected“.
During the anomaly, which occurred between blocks 8300569 and 8300570, block production reportedly continued. However, the whole process slowed down a lot for a few minutes. But that “its effect was low, similar to the delays occurring during normal operation”.
Nodes are automatically restored
But most nodes are auto-restored depending on the SPO you choose.
At the time of writing, the root cause of the anomaly and the resulting disconnection and restart of the nodes is still being investigated.
“Now we are still analyzing the root cause of this process causing the anomaly. In addition to our regular monitoring procedures, we have set up more detailed logging.“, the official statement reads.
Tom Stokes, co-founder of Node Shark and one of Cardano’s SPOs, reported in a January 22 post that more than half of the listed nodes were affected.
He also shared a graph showing that the network had dropped from 100% sync to just over 40% for over 300 nodes.
According to Stokes’ chart, network synchronization recovered to around 87% following the drop, but did not immediately return to the previous 100% level.
Another SPO reported similar problems in a January 22 post. However, he also claimed that “some SPOs did not experience this negative effect”.
https://www.youtube.com/watch?v=videoseries
