ONE-IN-A-MILLION COMMUNICATIONS FAILURE IN SANCTUM REPAIRED
1/12/121: Tar III - Secure Commerce Commission Depository
A cascading failure of the fluid router network affected civilian and military communications in the Sanctum constellation, as well as nearby systems in Genesis, Verge Vendor, Everyshore, Sinq Laison, and Essence, causing a momentary shutdown and emergency systems recovery process two weeks ago, The Federal Times has recently learned.
CRC investigators and response teams pinpointed the source of the failure as the SCC Depository station above Tar III and were on the scene in minutes, but have since determined the cause to have been accidental.
“The incident was a result of poor maintenance and sheer ill fortune,” explained CRC Sanctum Public Relations Liaison, Onre Loucaille. “The station utilized an old and accident-prone design which located the emergency battery backup near the router relay control to save money on superconductive conduit. The station was also using legacy software which predated interconstellation address indexing. This initiated a localized reassortment in the index systems in the event of a sudden forced reset of the relay subnet, resetting all index systems to their factory defaults and touching off competing cascading address conflicts through Sanctum and beyond until CRC technical employees decoupled the network racks.”
“Even so, the circumstances which led to this accident are exceedingly rare. It’s a million-to-one breakdown in our fluid router network, which even in other similar circumstances was highly unlikely to ever occur.”
Improper battery maintenance was described to have led to leakage from the battery stack onto the router relay control, causing a small but damaging electrical fire. The resulting plasmated surge began to repeatedly restart the router relay, misallocating more and more system indexes, causing further repeated competing reassortments. With the subnet experiencing address conflicts for several jumps in every direction which could not automatically self correct, it became necessary to completely reset the affected systems. Further failures were thus averted and the fluid router network central hub afterwards automatically reallocated the existing protocol addresses.
CRC repair crews worked overnight to fix the damage on the SCC Depository station and replace the aging router relay and battery backup system. Basic service through the rest of the constellation systems was restored within ten minutes and the Tar III SCC Depository Station was returned to full communications functionality within thirty minutes. The SCC reported that the thirty minute shutdown cost the equivalent of 50 billion ISK in transactional delays and 25 million ISK in physical damage to the router relay. Still, the news was mostly positive in the wake of the accident.
“In a way, we were very lucky,” said Korut Thimnasan, Cybersecurity Investigations Division II lead for the Tar Police division of CONCORD. "Had it been a bad actor attempting to take advantage of the relay failure, we could have had a very serious problem on our hands. The communications breakdown could have created temporary false transactions to steal money from legitimate companies through the SCC, or even to hide funds in a manner that they could never be recovered.
"Thankfully, after having compared the frozen transactions with the archival data of company systems, we have determined that neither of these worst case scenarios occurred. CONCORD and local police authorities from all four major empires participated in this investigation and are satisfied of the accidental nature of the communications breakdown and that no ISK was taken nor hidden anywhere. We have jointly and universally concluded, after extended investigation of all affected communications systems, that no security breach has occurred and the circumstances which led to these communications failures were a terrible accident. In seeing this situation incidentally, we thus can prevent it from being initiated intentionally.
“So much worse could have happened, and we have thoroughly examined all relevant data and footage to determine if any foul play occurred. However, with all transactional communications accounted for, we can all breath easier tonight.”
“Communications service was restored easily by enabling the onboard reset of all affected systems,” stated Loucaille. “Within a half-hour, all addresses were automatically reallocated. All customer issues, if they encounter any, should be easily resolved by restarting their in-house router.”
Restarting the in-house router, Loucaille explained, will download the new CRC firmware patch which will prevent further failures of this variety. The CRC recommends this patch be downloaded as soon as possible to prevent failures of this type from reoccurring. Further issues should be solved through CRC’s 24/7 hotline, which provides localized repair services and technical support.
“We would like our citizens and our partners to know how seriously we take these incidents and how we value the safety and security of their communications and their money,” Thimnesen read in his joint statement with other local law enforcement leaders in the investigation and the CRC investigation team. "CONCORD and law enforcement entities approach these matters with experience and professionalism, and we care deeply about the communities we serve.
“Even if this particular incident was simply an unfortunate accident, I’m proud of the way our response services reacted. We will always safeguard your access your communications with the same zeal with which we protect their homes and lives. Rest assured, this accident and the circumstances which cause it have been rectified, and should pose no further issue to our citizens or their service.”
As of noon today, the criminal case has been closed, and all further questions are asked to be directed to the CRC Public Relations Bureau in the locality of origin.