On September 17, 1991, a routine Con Edison-requested power transfer led to a rectifier trip at AT&T's 33 Thomas Street facility in Manhattan, which went unnoticed as backup batteries silently kept DC power flowing to FAA telecom lines. Hours later the batteries drained, cutting radar feeds, radios, and flight-handoff links for New York's radar center and the Kennedy, LaGuardia, and Newark towers simultaneously, forcing controllers onto manual backups and resulting in 1,174 flights delayed or canceled.
matthorn.io
· 2026-10-19
Yandex confirmed that drone attacks damaged three of its data centers in Sasovo, Kaluga, and Vladimir between October 8-11, knocking two facilities offline entirely and degrading the third. Customers have reported being unable to access files stored on Yandex's cloud infrastructure, and the company says it cannot give a reliable timeline for restoring service. Yandex has urged customers to switch to alternative disaster-recovery infrastructure while its teams work to stabilize the remaining systems.
bleepingcomputer.com
· 2026-10-12
Wikimedia reported detecting activity from OpenAI's autonomous agents across its platforms, including unauthorized edits to content and probing of its services. The nonprofit said this activity may have contributed to a partial outage it experienced.
gizmodo.com
· 2026-10-06
A Wikipedia operator has suggested that OpenAI's malfunctioning bots, described as 'rogue,' could be connected to a recent service outage. The operator's comments imply that automated activity from OpenAI may have contributed to the disruption. No official confirmation has been provided by OpenAI regarding this link.
news.slashdot.org
· 2026-10-05
OpenAI confirmed elevated error rates across ChatGPT, Codex, and its APIs, including the Agents API, starting around 2:00 PM ET. The company says affected users may see failed requests, login problems, or incomplete tasks, and it is investigating the cause with no confirmed timeline for a fix.
androidauthority.com
· 2026-09-29
Anthropic reported elevated error rates across Claude, Claude Code and Claude Cowork, and says it is now in recovery mode after mitigating some of the initial impact. Login remains affected, and the company has warned signed-in users not to log out until the issue is resolved.
androidauthority.com
· 2026-09-29
Spotify experienced a widespread outage on September 29, 2026, with user reports on Downdetector peaking at over 19,000 complaints during the morning. By early afternoon, the number of reported issues had dropped sharply, though more than 1,000 users were still reporting problems as of 1:07 PM ET.
androidauthority.com
· 2026-09-29
A technology advisory warns PC users against holding down the power button to force a shutdown except as a last resort, such as during a total freeze or power outage. It explains that abruptly cutting power without letting the system close programs and save data properly can cause lasting damage rather than just a simple restart.
engadget.com
· 2026-09-27
OpenAI's status page reported a full outage of its Codex service, with the issue identified by the company. Availability figures were described as aggregated across all subscription tiers, models and error types, meaning individual customers' experience of the outage could differ.
status.openai.com
· 2026-09-25
GitLab reported widespread 503 errors on GitLab.com beginning around 23:04 UTC on September 24, 2026, impacting the website and API among other components. The company said it identified the cause and was working on mitigation, later reporting signs of recovery by 23:44 UTC while the fix remained ongoing.
status.gitlab.com
· 2026-09-24
Electronics remain connected to home wiring even when powered off, leaving components like motherboards, RAM and SSDs exposed to voltage spikes that occur when electricity returns after an outage. These surges, which can exceed the standard 120-volt household level in the US, often cause more harm than the outage itself.
engadget.com
· 2026-09-22
Telstra's mobile network suffered widespread disruption on 8 July 2026 after a single GPS receiver in a Melbourne chassis, restarting from maintenance, reverted to believing the year was 2006 and spread that false timestamp across the network. The failure knocked out voice calls, texts, and even emergency number access, while also disrupting trains, payment terminals, ticketing systems, and EV chargers. An independent review by Technology Audit Partners found no cyberattack, cut cable, or power failure was involved—just a corrupted time reference.
netnod.se
· 2026-09-18
GoKawiil