← All incidents
Incident dossier · Rank #12
Delta Air Lines Atlanta Data Center Power Failure Grounds the Global Fleet
Delta Air Lines
2016-08-08
6h 0m core impact
PowerFire
In the early hours of 8 August 2016, a routine scheduled transfer of load onto a backup generator at Delta Air Lines' Atlanta headquarters data center precipitated a fire in the power control room. The fire failed a transformer and cut a primary power path feeding the facility. Roughly 300 of Delta's 7,000 servers lacked a working alternate feed and went dark, and because surviving servers could no longer communicate with the failed nodes, the entire airline operations platform collapsed. Delta grounded its global fleet, cancelling about 2,100 flights over three days and delaying another 2,400, at an estimated cost of ~$150 million. CEO Ed Bastian took full responsibility. The event is a textbook case of a common-mode power fault upstream of server-level redundancy defeating an otherwise diverse design, compounded by a tightly-coupled system with no graceful degradation and an unmodernized legacy reservation tier.
Failure cascade
Trigger → primary fault → downstream blast radius, derived from the sourced root cause and affected-services record.
Facility & location
- Operator
- Delta Air Lines
- Data center
- Delta Technology Data Center, Atlanta Headquarters
- Location
- Atlanta, United States
- Date
- 2016-08-08
Impact & scale
- Users affected
- Tens of thousands of passengers worldwide; thousands stranded overnight and sleeping on airport floors (exact passenger count not stated by any source)
- Financial
- ~$150 million (Delta's own estimate)
- Scope
- Critical (SEV-1 equivalent; full worldwide operational outage)
Services / systems down
- Flight scheduling
- Passenger check-in and services
- Baggage handling
- Aircraft fueling
- Airport video displays
- Public websites
- Self-service kiosks
Impact data & metrics
| Fire origin time & location | 02:30 AM EST, 8 Aug 2016, power-control room |
| Servers lacking alternate power source | ~300 of 7,000 (~4.3%) |
| Servers requiring manual reboot | ~500 |
| Utility power feeds lost | 1 of 2 (transformer destroyed by fire) |
| Time to systems operational | ~6 hours (02:30 → 08:30 EST) |
| FAA ground stop lifted | 08:40 AM EST, 8 Aug 2016 |
| Flights operating by 1:30 PM day-of | 1,700 of 6,000 scheduled |
| Flights cancelled over 3 days | 2,100 (1,000 Mon / 800 Tue / 300 Wed) |
| Flights delayed | ~2,400 |
| Core reservation platform age | 52-year-old 'Deltamatic' legacy system |
| Estimated cost to Delta | ~$150 million USD |
| Fatalities / injuries | None reported |
Magnitude profile
Magnitude 8.3 = blast 9×0.35 + users 8×0.25 + financial 9×0.20 + duration 7×0.20 (sub-scores 0–10 · weighted composite)
Financial impact (~$150M) is roughly 200x the Ponemon industry-average data-center outage cost (~$730K per the cited source), hence a 9. Blast radius is near-total: a ~4% node loss (300 of 7,000 servers) cascaded into a 100% platform outage that grounded a global fleet across 334 destinations in 64 countries. Core power/IT restoration took ~6 hours (durationScore 7 reflects this rather than the 3-day operational tail). Users score reflects tens of thousands stranded worldwide, though no exact passenger figure was published.
Sequence of events (SOE)
- TRIGGER Operators perform a scheduled load transfer toward the backup generator for testing — the proximate trigger. Availability Digest: the fire 'was the result of a routine scheduled switch for testing purposes to the backup generator.'
- TRIGGER A fire erupts in the power-control room: 'On Monday morning, August 8, 2016, at 2:30 AM EST, a fire erupted in the power control room of Delta's data center at its Atlanta headquarters.'
- DETECTION The fire is detected/sensed at origin, but NO verifiable source names the detection system (aspirating/VESDA, spot smoke, or heat) or the exact detection moment; the only fixed data point is the 2:30 AM origin time.
- CASCADE REPORTED, NOT RE-VERIFIED: Delta stated the failing 'power control module... malfunctioned, causing a surge to the transformer and a loss of power.' This review could not re-fetch the ABC News page (403/404).
- CASCADE VERIFIED mechanism: the transformer is destroyed by the fire — 'The fire caused a transformer to fail, killing one of the two power feeds to the data center.'
- CASCADE REPORTED, NOT RE-VERIFIED: a single transfer point is said to have isolated the load from both sources — 'the switchgear failure locked Delta out of its reserve generators as well as from Georgia Power.' Source page not re-fetchable this pass.
- IMPACT ~300 of 7,000 servers wired only to the failed feed lose power, and their backups are also dead: '300 of Delta's 7,000 servers... were not linked to an alternate power source'; 'many of them could not fail over to their backups, which were also down due to being unpowered.'
- IMPACT Whole-platform collapse: surviving servers 'could not communicate with the servers that failed. This took down Delta's entire system.' Passenger check-in, baggage, websites, kiosks, and airport displays go dark.
- MITIGATION Fire SUPPRESSION: no fixed suppression system is named and no discharge is confirmed in any verifiable source; secondary trade material characterized it as 'a small fire that was quickly extinguished' but could not be re-fetched and is not certified here.
- MITIGATION EMERGENCY SERVICES (fire): a retrospective states firefighters were called to extinguish the blaze, but that page returned HTTP 404 this pass and the call/arrival/on-scene timeline was never officially published.
- MITIGATION EMERGENCY SERVICES (utility): Georgia Power crews are reported to have responded on site and worked with Delta; the utility maintained there was no area outage. Not independently re-verified this pass.
- IMPACT EVACUATION / LIFE SAFETY: none reported — an unmanned/low-occupancy overnight electrical-room fire; no injuries reported in any source (life-safety egress not triggered).
- RECOVERY Manual recovery begins: '500 servers had to be rebooted' to bring the platform back online.
- RECOVERY Core reservation platform returns degraded: the 52-year-old 'Deltamatic' system comes back with 'only the old Deltamatic green-screen interface... operational', forcing manual check-in and handwritten boarding passes.
- RECOVERY Systems operational again: 'It wasn't until 8:30 AM, six hours later, that the Delta systems were once again operational.'
- RESTORED FAA ground stop lifted: 'the ground stop was lifted at 8:40 AM on Monday' — though 'cancellations and delays continued.' By 1:30 PM only 1,700 of 6,000 scheduled flights were operating.
- RESTORED Operational recovery stretches three days: 'Delta cancelled 2,100 flights over a span of three days... 1,000 flights on Monday... 800 more on Tuesday and 300 on Wednesday. An additional 2,400 flights were delayed.' Estimated cost ~$150M.
Root cause
PROXIMATE IGNITION AND MECHANISM (verified core). A fire began at 2:30 AM EST on Monday, 8 August 2016 in the power-control room of Delta's data center at its Atlanta headquarters, and it was an electrical-equipment fire — "Delta, whose outage was caused by electrical-equipment failure" (Data Center Knowledge). Crucially, the ignition was triggered by a maintenance/test activity, not a random fault: "The fire was the result of a routine scheduled switch for testing purposes to the backup generator" (Availability Digest, verbatim). The verified physical mechanism is that the fire then destroyed a transformer: "The fire caused a transformer to fail, killing one of the two power feeds to the data center" (Availability Digest). Delta's and Georgia Power's public statements added component-level detail that this review could NOT independently re-verify this pass (source pages 403/404): Delta (COO Gil West / CEO Ed Bastian, as reported) called the failed item a "power control module" that "malfunctioned and caught fire, causing a surge to a Georgia Power transformer"; Georgia Power (spokesman John Kraft, as reported) called it "a switchgear... [that] malfunctioned for reasons that were not immediately clear," stressing "It was a failure of Delta equipment... there wasn't an area power outage." These are consistent with the verified spine but should be read as reported, not confirmed.\n\nCRITICAL DISCLOSURE GAP (well-supported). No manufacturer, model number, installation year, insulation type, or arc-fault-versus-mechanical-failure determination was ever publicly released. No official root-cause analysis, regulatory filing, or vendor status document exists; "for reasons that were not immediately clear" remained the effective ceiling on component-level causation. The physical failure mode is therefore officially unverified.\n\nLATENT ROOT — AS-BUILT REDUNDANCY DEFECT (verified). The catastrophe was not the fire, which was small and confined to the power-control room, but the redundancy defect it exposed. Delta's design intent was A+B power — "Each server in the data center has redundant power supplies, and each power supply is supposed to be plugged into different power strips" — but the as-built reality diverged: "300 of Delta's 7,000 servers in the data center were not linked to an alternate power source" (Availability Digest, verbatim). Those single-fed servers went down and "could not fail over to their backups, which were also down due to being unpowered." CEO Ed Bastian "took full responsibility for the failure" (Availability Digest); his widely-reported admission that the vulnerability "went undetected" is consistent but was not re-verified here.\n\nLATENT ROOT — TEST/TRANSFER AS TRIGGER + CONCENTRATED TRANSFER NODE. The true root cause is a stack: (1) a maintenance transfer sequence intended to prove resilience that instead ignited the gear ("result of a routine scheduled switch for testing purposes to the backup generator", verified); (2) an undetected A+B wiring defect on ~300 servers that no commissioning audit or failover test had caught (verified); and (3) a concentrated transfer/power node whose failure severed a utility feed and defeated failover simultaneously. The claim (analyst Robert Mann, EE Power, as reported — NOT re-verified) that "the switchgear failure locked Delta out of its reserve generators as well as from Georgia Power" describes this single-point-of-failure but rests on an unverified source; the verified facts alone (one feed killed + backups unpowered + whole system down) already establish that a single downstream event defeated a dual-utility-feed design.
Contributing factors
- UNDETECTED AS-BUILT A+B WIRING DEFECT (commissioning/inspection lapse) — VERIFIED: design intent was every server's redundant PSUs on different power strips, but '300 of Delta's 7,000 servers... were not linked to an alternate power source' (Availability Digest). No commissioning audit or failover test had caught the design-vs-installation gap; CEO Bastian 'took full responsibility for the failure'.
- MAINTENANCE/TEST PROCEDURE AS THE TRIGGER — VERIFIED: the fire 'was the result of a routine scheduled switch for testing purposes to the backup generator' (Availability Digest). The resilience test itself ignited the gear, indicating the transfer sequence and/or the equipment's condition were inadequately de-risked before a live transfer.
- SINGLE DOWNSTREAM EVENT DEFEATED DUAL-FEED DESIGN — VERIFIED (mechanism) / REPORTED (nomenclature): a dual-utility-feed envelope was undone because one fire killed a transformer/feed AND left backups unpowered so failover failed. The specific 'switchgear failure locked Delta out of its reserve generators as well as from Georgia Power' framing (Robert Mann, EE Power) is as-reported and was not independently re-verified.
- TIGHT SYSTEM INTERDEPENDENCY / NO GRACEFUL DEGRADATION — VERIFIED: surviving servers 'could not communicate with the servers that failed. This took down Delta's entire system' (Availability Digest). Loss of only ~4% of servers collapsed the whole platform — insufficient partition tolerance / fault isolation.
- LEGACY-SYSTEM RECOVERY FRICTION — VERIFIED: the core reservation platform runs on 'a 52-year old legacy system called Deltamatic'; on restart 'only the old Deltamatic green-screen interface was operational', forcing manual check-in and handwritten boarding passes (Availability Digest) — extending impact far beyond power restoration.
- FAILURE-TO-FAIL-SAFE / SURGE PROPAGATION — REPORTED, NOT VERIFIED: Delta stated the failing module 'caus[ed] a surge to the transformer' (Gil West, ABC News, as reported), implying missing surge isolation/protective coordination. The verified record confirms only that 'the fire caused a transformer to fail', not the electrical surge mechanism.
- OPAQUE / ABSENT COMPONENT RCA — SUPPORTED BY ABSENCE: no make, model, age, or chemistry of the failed gear was ever disclosed and no official root-cause analysis, regulatory, or vendor document was published; Georgia Power could only say it failed 'for reasons that were not immediately clear' (as reported).
- UNDOCUMENTED FIRE-PROTECTION POSTURE — DISCLOSED GAP: no detection or fixed-suppression system is named in any verifiable source and no discharge is confirmed; the power-control room's fire-protection design and its performance were never validated in the public record.
Correction of errors (COE)
- Public root-cause analysis identifying the failed component (make/model/age) and failure mechanism (arc-fault vs mechanical)
- Correct the ~300 single-fed servers and audit dual-cord A/B integrity across all 7,000 servers
- Invest in IT resilience / modernize reservation and passenger-service platforms
- Review switchgear/transfer maintenance and de-risk live generator-test transfer procedures
- Confirm no area-grid cause and support Delta investigation
- Validate power-control-room fire detection and fixed suppression design and performance
Lessons learnt
- Envelope redundancy is worthless without end-to-end integrity: two utility feeds 'through opposite sides of the building' did not help because a single fire killed a transformer/feed while ~300 servers' backups sat unpowered — redundancy must be verified continuously from utility entry to the individual server PSU, not assumed from design drawings.
- The resilience test can be the disaster: the ignition occurred during a scheduled transfer to the backup generator. Procedures meant to prove availability are high-energy events that must themselves be de-risked (condition-based maintenance, staged transfer, thermography) or they become the trigger.
- As-built drifts from design and only an audit catches it: 300 of 7,000 servers were mis-wired to a single feed and it 'went undetected' until a live fault. Dual-cord/failover integrity needs automated mapping and recurring drills, not one-time commissioning trust.
- Tight coupling turns a small fault into a total outage: losing ~4% of servers collapsed everything because survivors could not talk to the failed nodes. Systems need fault isolation and graceful degradation so partial infrastructure loss stays partial.
- Legacy monoliths dominate recovery time: a 52-year-old reservation system returning as green-screen-only forced handwritten boarding passes and stretched recovery across three days — technical debt is an availability risk, not just a modernization backlog item.
- Opacity undermines learning: with no published RCA and no disclosed make/model/age/chemistry, the true physical failure mode remains unverifiable years later; without forensic transparency the industry cannot prevent recurrence.
- Fire-protection design in electrical rooms must be explicit and tested: neither the detection nor the suppression system was ever documented publicly — undocumented protection is unvalidated protection.
Improvements & remediation
- MAINTENANCE — De-risk live transfer/test procedures: since the fire 'was the result of a routine scheduled switch for testing purposes to the backup generator', treat generator/transfer testing as a high-energy operation: pre-test thermography and insulation-resistance checks on switchgear, breaker/relay maintenance records reviewed, and staged/loaded transfer under controlled conditions rather than a live full-load switch on aged gear.
- MAINTENANCE — Independent commissioning + periodic A/B integrity audits: the ~300 single-fed servers (out of 7,000) proves design intent diverged from as-built. Mandate dual-cord verification (physical trace of every PSU to independent, separately-fed PDUs/strips), automated per-outlet power-path mapping, and recurring pull-the-plug failover drills to catch wiring drift.
- SAFETY — Fire detection & fixed suppression validation in power-control rooms: the detection and suppression posture is officially undocumented. Install/verify aspirating (VESDA) very-early smoke detection and a fixed clean-agent (or pre-action) system in switchgear/power rooms, with documented discharge testing, arc-fault detection/mitigation, and coordinated auto de-energisation on fire alarm.
- SAFETY / ELECTRICAL — Protective coordination & surge isolation: introduce selective breaker coordination and surge/fault isolation so a faulting upstream device trips locally without propagating energy to and destroying a downstream transformer, eliminating the 'one fire kills a whole feed' failure mode.
- RESILIENCE — Remove concentrated single points of failure: audit the topology so no single switchgear, transfer switch, or transformer can simultaneously sever a utility feed and defeat generator failover; provide true 2N/isolated-bus separation with independent transfer paths.
- ARCHITECTURE — Graceful degradation / fault isolation: loss of ~4% of servers collapsed the entire platform because survivors 'could not communicate with the servers that failed'. Re-architect for partition tolerance, bulkheading, and degraded-mode operation so a partial power loss cannot take down the whole system.
- RECOVERY / IT — Modernize and geo-redundant the core platform: the 52-year-old Deltamatic monolith returning as green-screen-only forced manual check-in. Invest in a resilient, geographically-redundant reservation/DCS platform with tested automated failover to a second site.
- GOVERNANCE — Publish a real RCA and close the disclosure gap: no make/model/age/RCA of the failed gear was ever released. Adopt formal post-incident RCA with component forensics and maintenance-record review, feeding a tracked corrective-action register.
Comprehensive analysis
What is verified versus what remains reported-only
The verified spine (Availability Digest, read verbatim; corroborated on cause/cost by Data Center Knowledge) establishes: a fire at 2:30 AM EST on 8 Aug 2016 in the power-control room, triggered by a scheduled test-switch to the backup generator, destroyed a transformer and killed one of two feeds; ~300 of 7,000 servers were single-fed and their backups were unpowered; the whole system fell over; recovery took ~6 hours to 'operational' (8:30 AM), the ground stop lifted at 8:40 AM, and the airline cancelled 2,100 flights over three days at ~$150M. The component nomenclature — Delta's 'power control module' with a 'surge to the transformer', and Georgia Power's 'switchgear... reasons not immediately clear' — comes from ABC News, the AJC, EE Power and NBC News that this review could not re-fetch this pass (HTTP 403/404, archive.org blocked, WebSearch budget exhausted). Those claims are retained as reported, not certified.
The single-point-of-failure that defeated dual utility feeds
Delta built for backhoe protection — two utilities entering opposite sides of the building — yet a single overnight fire simultaneously killed a transformer/feed and left the ~300 single-fed servers' backups dead. Whether the precise 'switchgear locked Delta out of its reserve generators as well as from Georgia Power' framing (analyst Robert Mann, as reported) is exact or not, the verified facts already prove a concentrated downstream failure defeated an envelope-redundant design. The lesson is topological: redundancy must be verified as isolated and independent from utility entry all the way to each server's two power cords.
Why a small, contained fire caused a global grounding
The fire never spread beyond the power-control room, yet it grounded the world's largest airline. Two amplifiers turned a ~4% power loss into a total outage: tight interdependency (survivors 'could not communicate with the servers that failed. This took down Delta's entire system') and legacy fragility (the 52-year-old Deltamatic core returned green-screen-only, forcing handwritten boarding passes). Extinguishing the fire did not restore service — the destroyed transformer, lost feed, and failed failover had already done the damage, and recovery was gated by manual reboots of ~500 servers and a brittle monolith.
The official-RCA vacuum and source reliability
There is no official post-mortem: no Delta RCA, no regulatory or court filing, no vendor status page. The failed gear's make, model, age, insulation type, and failure mechanism were never disclosed; 'for reasons that were not immediately clear' is the effective ceiling. Fire detection and fixed suppression are entirely undocumented. Accordingly officialPostmortem is FALSE, approvedSources is limited to the two pages verified this pass (Availability Digest, Data Center Knowledge), and every component-level or emergency-response detail sourced to pages that returned 403/404 is flagged as reported-not-verified or struck.
Technical deep-dive
Delta's Atlanta data center was engineered for utility resilience at the building envelope: "Power is brought into Delta's data center from two separate utilities through opposite sides of the building to prevent power from being accidently cut with a back hoe" (Availability Digest, verbatim) — a classic backhoe-protection topology, with each server carrying redundant PSUs meant to draw from independent power strips. The 8 August event demonstrated that resilience at the envelope is worthless if a single downstream event can sever a source and defeat failover at the same time.\n\nVERIFIED FAILURE CHAIN (Availability Digest): (1) At 2:30 AM EST operators performed a scheduled transfer toward the backup generator for testing; the fire "was the result of" that switch. (2) A fire erupted in the power-control room. (3) "The fire caused a transformer to fail, killing one of the two power feeds to the data center." (4) Of ~7,000 servers, ~300 were wired only to the failed feed and lost power; "many of them could not fail over to their backups, which were also down due to being unpowered." (5) Even surviving servers "could not communicate with the servers that failed. This took down Delta's entire system" — a small (~4%) power loss collapsed the whole platform through tight interdependency.\n\nREPORTED-BUT-UNVERIFIED COMPONENT DETAIL: Delta publicly attributed the event to a "power control module" that "malfunctioned, causing a surge to the transformer and a loss of power" (Gil West, ABC News, as reported); Georgia Power attributed it to "a switchgear... malfunctioned for reasons that were not immediately clear" and insisted it was "a failure of Delta equipment... there wasn't an area power outage" (John Kraft, as reported). This review could not re-fetch those pages (HTTP 403/404) and does not treat the "surge" mechanism or the "switchgear/module" nomenclature as confirmed — the verified account is only that a fire, triggered by a test transfer, destroyed a transformer and killed one feed.\n\nRECOVERY: Manual recovery was severe — "500 servers had to be rebooted. It wasn't until 8:30 AM, six hours later, that the Delta systems were once again operational." When Delta's core platform returned it did so degraded: the reservation/passenger-service systems run on "a 52-year old legacy system called Deltamatic," and "only the old Deltamatic green-screen interface was operational," forcing agents to "manually check[] in passengers and handwrit[e] boarding passes" (Availability Digest, verbatim). The FAA ground stop lifted at 8:40 AM, but by 1:30 PM "only 1,700 of Delta's scheduled 6,000 flights were in operation," and operational recovery stretched three days (2,100 cancellations; 2,400 delays; ~$150M cost).\n\nFORENSIC UNKNOWNS (disclosed). No public source names the fire-DETECTION system (aspirating/VESDA, spot smoke, or heat) or the detection moment — the only fixed data point is the 2:30 AM origin. No source documents any fixed SUPPRESSION system (clean-agent gaseous, pre-action sprinkler, or none) or confirms a discharge; extinguishment characterizations ("a small fire that was quickly extinguished"; "firefighters were called") appear only in secondary trade/retrospective material this review could not re-fetch and does not certify. No evacuation and no injuries were reported, consistent with an unmanned overnight electrical-room fire. Critically, extinguishing the fire did not restore service — the destroyed transformer, the lost feed, and the failed failover had already done the damage.
References & provenance
- press Delta Meltdown Reflects Problems With Aging Technology — Wall Street Journal (Susan Carey), via Oxford RMG PDF“Following the loss of power early Monday, "some critical systems and network equipment didn't switch over to Delta's backup systems." the company said. It is investigating the cause.”https://www.oxfordrmg.com/wp-content/uploads/2016/08/08.09.16-Delta-Meltdown-Reflects-Problems-With-Aging-Technology-WSJ.pdf
- press Georgia Power suspects equipment failure caused airport fire, outage — The Atlanta Journal-Constitution“Bastian said a power control module at the airline's technology command center failed and caught fire. Georgia Power said the outage was caused by the failure of Delta switchgear equipment, which switches power flows within a system.”https://www.ajc.com/business/georgia-power-suspects-equipment-failure-caused-airport-fire-outage/LmQ9sG6pj8HnwP8nuUAlEJ
- press Delta Airlines cancels flights nationwide after computer failure — World Socialist Web Site“We believe that Delta Air Lines experienced an equipment failure overnight that caused their outage.”https://www.wsws.org/en/articles/2016/08/09/delt-a09.html
- press Delta Airline's Power Outage Risk Analysis — ASA Institute for Risk & Innovation (Sukhman Tiwana, July 2017)“On August 8th 2016, Delta lost access to Georgia Powers and its reserve generator... it cancelled 2,300 flights over three days and its revenue for August 2016 declined approximately $100 million.”https://static1.squarespace.com/static/5d34d73f43d37a0001d73dcf/t/64ee55159261c01693370d94/1693340950679/ASAResearchNote_2017-07_Tiwana_DeltaAirline.pdf
- news Delta Data Center Outage Grounds Hundreds of Flights — Data Center Knowledge“Georgia Power stated there were no power outages in its territory on Sunday evening or Monday, though it dispatched workers over a problem with switch gear early Monday morning — pointing the fault back inside Delta.”https://www.datacenterknowledge.com/outages/delta-data-center-outage-grounds-hundreds-of-flights
- news Tens of thousands of Delta passengers grounded by outage — Data Center Dynamics“The outage struck Delta's computer systems and operations worldwide, stranding tens of thousands of passengers.”https://www.datacenterdynamics.com/en/news/tens-of-thousands-of-delta-passengers-grounded-by-outage/
- other Delta Air Lines Cancels 2,100 Flights Due to Power Outage — Availability Digest“At 2:30 AM EST a fire erupted in the power control room; the fire caused a transformer to fail, killing one of the two power feeds, and 300 of Delta's 7,000 servers were not linked to an alternate power source.”https://availabilitydigest.com/public_articles/1109/delta.pdf
- news Delta: Data Center Outage Cost Us $150M — Data Center Knowledge (follow-up)“Exact cost put at $150 million, with approximately 2,000 flights grounded over three days from an electrical equipment failure in the Atlanta data center.”https://www.datacenterknowledge.com/outages/delta-data-center-outage-cost-us-150m
- other Thousands of Delta passengers delayed by computer outage — Hacker News discussion (links to BBC)“A routine scheduled switch to the backup generator this morning caused a fire; Georgia Power said other customers were not affected.”https://news.ycombinator.com/item?id=12246490
Sourced from public post-incident reports. Quotes are short attributed excerpts for provenance only; the analysis above is original and substantially shorter than its sources. Last verified 2026-08-01.