The history of computing includes several major scandals in which companies cited routine maintenance or a technical bug—or simply remained silent—to cover up a serious cyberattack or internal negligence.
Here are the most notable precedents:
1. Sony PlayStation Network (2011): "External maintenance"
• What was initially stated: When the PlayStation online network stopped working in April 2011, Sony first referred to a vague "external intrusion," then to "necessary maintenance" that might last a day or two.
• The hidden truth: The network ended up being paralyzed for 23 days. Under pressure from governments, Sony was forced to admit that it had been one of the largest cyberattacks in history at the time: hackers had stolen the personal (and potentially banking) data of 77 million users. Sony had shut down its servers as an emergency measure while buying time to assess the extent of the damage.
2. Yahoo (2013–2014): An attack denied for years
• What was initially stated: For years, whenever slowdowns or connection issues occurred, Yahoo reported no major security incidents to its users.
• The hidden truth: In 2016—while negotiating its acquisition by Verizon—the company was forced to reveal that two separate cyberattacks in 2013 and 2014 had compromised all 3 billion of its accounts. The management at the time was aware of the 2014 intrusion but chose not to inform the public or the authorities. 3. Uber (2016): A ransom disguised as a bug bounty program
• What was initially stated: Nothing. No public incident was reported to users or regulators when the breach was discovered.
• The hidden truth: In November 2017, Uber’s new leadership revealed that hackers had stolen data belonging to 57 million customers and drivers a year earlier. To hush up the matter, Uber’s former head of security had secretly paid the hackers $100,000, framing the payment as an official "bug bounty" reward and requiring them to sign a non-disclosure agreement.
4. British Airways (2017): The "power surge" excuse
• What was initially stated: In May 2017, a global IT failure grounded hundreds of British Airways flights, leaving 75,000 passengers stranded. The airline immediately blamed an unforeseen "power surge" at its data center.
• The hidden truth: Union and technical investigations revealed that it was not an external electrical anomaly; a contractor had accidentally disconnected the main power supply to a data center and then reconnected it in an uncontrolled manner, physically damaging the servers. The company had outsourced a large portion of its IT staff to cut costs, which exacerbated the crisis. 5. Rogers in Canada (2022): The Wall of Corporate Secrecy
• The initial account: During the historic outage on July 8, 2022—which left more than 12 million Canadians without mobile service, internet access, or the ability to use Interac payments—Rogers attributed the incident to a "maintenance update" that had gone wrong.
• What fueled distrust: Although the event was indeed caused by human error during a router update, Rogers invoked "commercial secrecy" before the CRTC to redact entire pages of its technical reports. It took two years for an independent report to confirm that Rogers’ own engineers did not even have access to their own error logs during the first 14 hours of the crisis—revealing a critical lack of redundancy.
Why this reflex persists
In almost all such cases, the company’s initial reaction is not necessarily part of a grand conspiracy, but rather a matter of legal and financial crisis management: until an internal investigation is complete, a publicly traded company will avoid using terms like "cyberattack" or "negligence" to prevent market panic, class-action lawsuits, or immediate regulatory fines.