Cardano Nodes go offline for half an hour
At least half of the nodes on the Cardano network went down for a short period over the weekend, according to reports from stake pool operators (SPOs) and users of the cryptocurrency. An abnormality caused fifty percent of Cardano nodes to disconnect and restart, according to a message published on January 22 and posted on SPO for Telegram by Input Output Global, the engineering and research company responsible for the Cardano blockchain . The unexpected outage was explained in a post stating that “This appears to have been caused by a transient anomaly that triggered two reactions in the node,” which said some nodes had detached from a peer, while others had thrown an exception and resumed.
Despite a brief drop in performance, the Cardano network was able to recover without help from outside sources.
The article states that “such temporary difficulties” were taken into account during the node design and consensus process, and that “the systems performed exactly as predicted.”
During the irregularity, 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 small, comparable to the delays encountered during normal operations,” according to the report. ” Depending on the SPO selected, most nodes recovered automatically.
At the time this article was written, the underlying issue that led to the anomaly and the subsequent node disconnections and reboots was still being investigated. According to the official message, “We are currently investigating the underlying cause of this anomalous activity and are adopting additional logging measures along with our normal monitoring methods.”
Tom Stokes, who is also a Cardano SPO and co-founder of Node Shark, said in a post on January 22 that well over half of the nodes listed were affected by the issue.
Additionally, he presented a graphic illustrating the point at which network synchronization dropped from 100% to just over 40% for more than 300 reporting nodes.
According to Stokes’ chart, after the drop in performance, the network synchronization was able to recover to a level of around 87%, but it did not immediately return to the original level of 100%. Another SPO reported similar concerns to Stoke in a January 22 post, but said “several SPOs experienced no effect.” “Others experienced a restart of the relays and blood pressures.
The SPOs, devs and IOG are now debugging on Discord.
It is not a fundamental reason as of now” They said that.
