At least half of the Cardano network nodes went down for a brief period of time over the weekend, according to reports from SPOs and cryptocurrency users. An anomaly caused fifty percent of Cardano nodes to go offline and reboot, according to a message posted on Jan. 22 and posted to SPO for Telegram by Input Output Global, the engineering and research firm responsible for the Cardano blockchain. Cardano. The unexpected outage was explained in a post with the statement that “This seems to have been caused by a transient anomaly that triggered two reactions in the node”, which said that some nodes had broken out of a peer, while others threw an exception. and resumed

Despite a brief drop in performance, the Cardano network was able to recover without any help from outside sources.

In the article, it is stated that “such temporary difficulties” were taken into account during the node design and consensus process, and that “the systems operated exactly as predicted.”

During the anomaly, which occurred between blocks 8300569 and 8300570, block production was claimed to continue, although it was delayed for a few minutes. The “effect was minor, comparable to delays that occur during regular operations,” according to the report. “Depending on the SPO that was selected, most nodes recovered automatically.

At the time this article was written, the underlying issue that led to the failure and subsequent node disconnections and reboots was still being investigated. According to the official notice, “We are currently investigating the underlying reason for this aberrational activity and taking further logging measures alongside our normal monitoring methods.”

Tom Stokes, who is also Cardano SPO and co-founder of Node Shark, said in a post on Jan. 22 that well over half of the nodes that were listed were affected by the issue.

On top of that, he presented a graph illustrating the point at which network synchronization dropped from 100% to just over 40% for 300+ reporting nodes.

Based on the Stokes plot, after the performance drop, network synchronization was able to recover to a level of around 87%, but it did not instantly return to its original level of 100%. Another SPO reported similar concerns to Stoke in a post on January 22, but said “a number of SPOs did not experience any effects”. “Others experienced a reset of their relays and BP.

SPOs, developers, and the IOG are now debugging on Discord.

There is no fundamental reason as of now “They said that.