In spite of a brief drop in performance, the Cardano network was able to recover without any assistance from outside sources.
In the article, it is stated that “such temporary difficulties” were taken into consideration during the node design and consensus process, and that “the systems operated precisely as predicted.”
During the anomaly, which took place between blocks 8300569 and 8300570, it was claimed that block production continued, although it was delayed for a few minutes. The “effect was minor, comparable to the delays that occur during regular operations,” according to the report. ” Depending on the SPO that was selected, the majority of nodes automatically recovered.
At the time this article was written, the underlying problem that led to the anomaly and the subsequent node disconnections and restarts was still being investigated. According to the official notice, “We are presently researching the underlying reason for this aberrant activity and adopting more logging measures alongside our normal monitoring methods.”
Tom Stokes, who is also a Cardano SPO and the co-founder of Node Shark, said in a post on January 22 that much over half of the nodes that were listed were impacted by the issue.
In addition to that, he presented a graphic that illustrated the point at which the network sync dropped from 100% to just slightly over 40% for more than 300 reporting nodes.
According to Stokes’ chart, following the decline in performance, the network sync was able to recover to a level of around 87%, but it did not instantly return to its original level of 100%. An other SPO reported similar concerns to Stoke in a post on January 22, but said that “several SPOs experienced no effect.” “Others experienced a restart of their relays and BPs.
The SPOs, Developers, and IOG are now debugging on Discord.
There is not a fundamental reason as of now “They said that.