Currently highlighted on the map

Unidentified Iranian cargo vessel — projectile strike off Qeshm

12–13 September 2026 · First reported 23:00 UTC; investigation continuing · Iran

Reported impactIranian media report 1 killed and 4 wounded · vessel and attacker unidentified

Archive

Previous major incidents

36 source-linked records

36 of 36 archived incidents

2026

32 incidents
  1. UnconfirmedDrone / missile attack

    King Khalid International Airport — fuel depot smoke after hostile-threat alert

    Riyadh, Saudi Arabia · Airport Fuel Facility · Middle East

    Saudi civil defense sent overnight phone alerts warning of a "hostile aerial threat" and possible danger in Riyadh and nearby Al-Kharj after residents reported hearing explosions. A large plume of black smoke was subsequently seen rising from a fuel storage depot at King Khalid International Airport, and an all-clear was issued about 30 minutes after the initial alert. FlightRadar24 data showed major delays and several cancelled flights. Photos published by Al Jazeera and Reuters into the afternoon still showed a heavy black smoke column over the depot area and terminal forecourt, indicating an extended fire. Saudi Arabia later confirmed that its defenses intercepted a Houthi ballistic missile targeting Riyadh and said there were no reported casualties or damage from the attempted attack. The Houthis claimed they targeted sensitive sites in Riyadh, while also claiming fires at Aramco facilities in Yanbu; Saudi authorities said attempted attacks on Yanbu and several other locations were thwarted. None of those statements established that the intercepted missile, debris or another weapon struck the airport fuel depot or caused its fire. The visible fire is retained as unconfirmed pending an official cause or damage assessment.

    5 sourcesDetails +

    Saudi civil defense sent overnight phone alerts warning of a "hostile aerial threat" and possible danger in Riyadh and nearby Al-Kharj after residents reported hearing explosions. A large plume of black smoke was subsequently seen rising from a fuel storage depot at King Khalid International Airport, and an all-clear was issued about 30 minutes after the initial alert. FlightRadar24 data showed major delays and several cancelled flights. Photos published by Al Jazeera and Reuters into the afternoon still showed a heavy black smoke column over the depot area and terminal forecourt, indicating an extended fire. Saudi Arabia later confirmed that its defenses intercepted a Houthi ballistic missile targeting Riyadh and said there were no reported casualties or damage from the attempted attack. The Houthis claimed they targeted sensitive sites in Riyadh, while also claiming fires at Aramco facilities in Yanbu; Saudi authorities said attempted attacks on Yanbu and several other locations were thwarted. None of those statements established that the intercepted missile, debris or another weapon struck the airport fuel depot or caused its fire. The visible fire is retained as unconfirmed pending an official cause or damage assessment.

    Why it appears here: this record was previously elevated for its scale, consequences, strategic importance or energy-security risk. Major status can be revised as evidence develops.

  2. DocumentedDrone / missile attack

    Saudi East–West Pipeline — drone attack and precautionary shutdown

    Southeast of Medina, Saudi Arabia (approximate regional marker) · Pipeline · Middle East

    Satellite imagery first showed a large smoke plume and thermal activity close to Saudi Arabia's East–West crude-oil pipeline southeast of Medina. Saudi Arabia subsequently confirmed multiple drone attacks in the Riyadh and Medina regions, reported injuries and material damage, and said the pipeline was shut as a precaution, interrupting its principal crude-export route that bypasses the Strait of Hormuz. On 14 September, two unnamed regional officials briefed on the damage told the Associated Press that most of the pipeline could remain out of service for three to five weeks, including repairs at a major pumping facility; one said partial operation may be possible while work continued. Separate Reuters-sourced reporting cited a five-to-six-week repair estimate while noting a possible earlier restart. On 24 September, Reuters reported that the pipeline had restarted during that week and Saudi Arabia was rebuilding pumping volumes. Industry sources, satellite imagery and shipping data indicated that crude-tanker loadings at Yanbu had not yet resumed, and no restored pipeline-throughput figure was published. The restart therefore marks material recovery but does not establish full pipeline or export-terminal recovery. The Saudi Energy Ministry did not name an attacker, while the Foreign Ministry said several drones had come from Iraq without identifying the responsible group or drone model. No published wreckage analysis currently supports identifying them as Shahed, Sammad or another specific type. Iraq later said the launch site was in Maysan province, dismissed the province's operations commander and ordered an investigation into those responsible; those measures establish an Iraqi launch finding, not the identity of the operators. Iraq also closed two border crossings with Iran, while an Al Jazeera correspondent reported heavily armed forces visible on streets in Maysan. The purpose and targets of that deployment were not established, so it is recorded as a reported security response rather than evidence that any particular group had been identified. Qatar, Jordan and the Gulf Cooperation Council condemned the attack, and the GCC called on Baghdad to prevent further attacks from Iraqi territory. Satellite analysis cited by CNN showed extensive fire effects at one pumping-station site and a smaller fire at another; at least six of nine other detected heat signatures aligned with emergency flare pits and should not be counted as confirmed impacts. Later Vantor-branded high-resolution imagery circulated by MenchOsint shows widespread scorching and visibly damaged above-ground equipment across one pumping-station complex, strengthening the assessment of serious surface fire damage. OSINT613 described the more heavily affected station as completely destroyed, but neither image alone establishes total functional loss or damage to buried pipeline sections. The line has a stated maximum capacity of approximately 7 million barrels per day, but reported actual flows were roughly 4–5 million barrels per day during the first five months of the conflict and about 2 million in August. None of those figures is a confirmed production or export loss caused by the attack. The available evidence does not confirm a pipeline rupture, pollution or the volume of lost throughput. Claims of Houthi responsibility and catastrophic damage remain unverified and are not adopted here. The marker remains approximate because no verified impact coordinate has been published.

    12 sourcesDetails +
    Reported impactMaximum capacity is approximately 7 million barrels per day; reported actual flows were roughly 4–5 million barrels per day earlier in the conflict and about 2 million in August. Reuters reported on 24 September that operations had restarted and pumping volumes were being rebuilt, but did not publish a restored throughput figure; industry sources, satellite imagery and shipping data indicated that Yanbu crude-tanker loadings had not yet resumed. The restart occurred earlier than the initial three-to-five-week and five-to-six-week repair estimates, but it does not establish full pipeline or export-terminal recovery.

    Satellite imagery first showed a large smoke plume and thermal activity close to Saudi Arabia's East–West crude-oil pipeline southeast of Medina. Saudi Arabia subsequently confirmed multiple drone attacks in the Riyadh and Medina regions, reported injuries and material damage, and said the pipeline was shut as a precaution, interrupting its principal crude-export route that bypasses the Strait of Hormuz. On 14 September, two unnamed regional officials briefed on the damage told the Associated Press that most of the pipeline could remain out of service for three to five weeks, including repairs at a major pumping facility; one said partial operation may be possible while work continued. Separate Reuters-sourced reporting cited a five-to-six-week repair estimate while noting a possible earlier restart. On 24 September, Reuters reported that the pipeline had restarted during that week and Saudi Arabia was rebuilding pumping volumes. Industry sources, satellite imagery and shipping data indicated that crude-tanker loadings at Yanbu had not yet resumed, and no restored pipeline-throughput figure was published. The restart therefore marks material recovery but does not establish full pipeline or export-terminal recovery. The Saudi Energy Ministry did not name an attacker, while the Foreign Ministry said several drones had come from Iraq without identifying the responsible group or drone model. No published wreckage analysis currently supports identifying them as Shahed, Sammad or another specific type. Iraq later said the launch site was in Maysan province, dismissed the province's operations commander and ordered an investigation into those responsible; those measures establish an Iraqi launch finding, not the identity of the operators. Iraq also closed two border crossings with Iran, while an Al Jazeera correspondent reported heavily armed forces visible on streets in Maysan. The purpose and targets of that deployment were not established, so it is recorded as a reported security response rather than evidence that any particular group had been identified. Qatar, Jordan and the Gulf Cooperation Council condemned the attack, and the GCC called on Baghdad to prevent further attacks from Iraqi territory. Satellite analysis cited by CNN showed extensive fire effects at one pumping-station site and a smaller fire at another; at least six of nine other detected heat signatures aligned with emergency flare pits and should not be counted as confirmed impacts. Later Vantor-branded high-resolution imagery circulated by MenchOsint shows widespread scorching and visibly damaged above-ground equipment across one pumping-station complex, strengthening the assessment of serious surface fire damage. OSINT613 described the more heavily affected station as completely destroyed, but neither image alone establishes total functional loss or damage to buried pipeline sections. The line has a stated maximum capacity of approximately 7 million barrels per day, but reported actual flows were roughly 4–5 million barrels per day during the first five months of the conflict and about 2 million in August. None of those figures is a confirmed production or export loss caused by the attack. The available evidence does not confirm a pipeline rupture, pollution or the volume of lost throughput. Claims of Houthi responsibility and catastrophic damage remain unverified and are not adopted here. The marker remains approximate because no verified impact coordinate has been published.

    Why it appears here: this record was previously elevated for its scale, consequences, strategic importance or energy-security risk. Major status can be revised as evidence develops.

  3. Reported / attributedOther

    Jizan Aramco oil facilities — reported new strike

    Saudi Arabia · Refinery · Middle East

    Saudi Aramco's oil facilities at Jizan (also spelled Jazan) were struck on 7 September, according to Financial Times reporting cited by Shafaq News. Two people familiar with the matter said damage was still being assessed; one described the attack as similar in scale to the previous strike. At publication, Aramco had not commented and no group had claimed responsibility. The reporting did not establish the weapon used, specific equipment damaged, casualties, pollution or a new shutdown. The complex includes a 400,000 bbl/d refinery and associated energy infrastructure; that capacity is not a confirmed production loss. This is a separate reported event from the July–August attacks and outage recorded under the same facility. The marker is an approximate Jizan-area location, not a verified impact point.

    1 sourceDetails +
    Reported impactComplex includes a 400,000 bbl/d refinery; production impact from the 7 September strike has not been established

    Saudi Aramco's oil facilities at Jizan (also spelled Jazan) were struck on 7 September, according to Financial Times reporting cited by Shafaq News. Two people familiar with the matter said damage was still being assessed; one described the attack as similar in scale to the previous strike. At publication, Aramco had not commented and no group had claimed responsibility. The reporting did not establish the weapon used, specific equipment damaged, casualties, pollution or a new shutdown. The complex includes a 400,000 bbl/d refinery and associated energy infrastructure; that capacity is not a confirmed production loss. This is a separate reported event from the July–August attacks and outage recorded under the same facility. The marker is an approximate Jizan-area location, not a verified impact point.

    Why it appears here: this record was previously elevated for its scale, consequences, strategic importance or energy-security risk. Major status can be revised as evidence develops.

  4. Under investigationFire

    Tungatinah Power Station — major generating-hall fire

    Tarraleah, Central Highlands, Tasmania, Australia · Power Station · Oceania

    A major fire engulfed Hydro Tasmania's Tungatinah Power Station while the remotely operated plant was generating. Emergency services received the first call at about 20:50 AEST on 2 September and found the building fully involved and beginning to collapse; around 45 Fire Service and State Emergency Service personnel responded, and the blaze was contained during the early hours of 3 September. No employees or contractors were present and no injuries were reported. The station has five turbines, 142.2 MW of capacity and supplies just under 5% of Tasmania's electricity at full output. Hydro Tasmania began bringing the gas-fired Tamar Valley Power Station back online to cover the lost generation and said there had been no load shedding, customer impact or threat to statewide system security. TasNetworks separately listed outages affecting roughly 300 customers around Tarraleah, Brady's Lake and Bronte Park as caused by a pole fire; the reviewed evidence does not establish that those distribution outages were caused by the Tungatinah station blaze, so they are not counted as its operational impact. Fire investigators and police were examining the cause, which remained unknown, and no malicious act had been alleged. Firefighting runoff was contained in consultation with the Environment Protection Authority. The station coordinates are sourced from the Global Hydropower Tracker.

    5 sourcesDetails +
    Reported impactThe operating 142.2 MW station was taken out of service; Hydro Tasmania began returning Tamar Valley Power Station to service to cover the loss, while reporting no load shedding or threat to system security

    A major fire engulfed Hydro Tasmania's Tungatinah Power Station while the remotely operated plant was generating. Emergency services received the first call at about 20:50 AEST on 2 September and found the building fully involved and beginning to collapse; around 45 Fire Service and State Emergency Service personnel responded, and the blaze was contained during the early hours of 3 September. No employees or contractors were present and no injuries were reported. The station has five turbines, 142.2 MW of capacity and supplies just under 5% of Tasmania's electricity at full output. Hydro Tasmania began bringing the gas-fired Tamar Valley Power Station back online to cover the lost generation and said there had been no load shedding, customer impact or threat to statewide system security. TasNetworks separately listed outages affecting roughly 300 customers around Tarraleah, Brady's Lake and Bronte Park as caused by a pole fire; the reviewed evidence does not establish that those distribution outages were caused by the Tungatinah station blaze, so they are not counted as its operational impact. Fire investigators and police were examining the cause, which remained unknown, and no malicious act had been alleged. Firefighting runoff was contained in consultation with the Environment Protection Authority. The station coordinates are sourced from the Global Hydropower Tracker.

    Why it appears here: this record was previously elevated for its scale, consequences, strategic importance or energy-security risk. Major status can be revised as evidence develops.

  5. DocumentedDrone / missile attack

    Odesa regional energy infrastructure — missile and drone attack

    Odesa Oblast, Ukraine (regional marker; facilities not publicly named) · Power Grid · Europe

    Ukraine's transmission-system operator Ukrenergo said Russia carried out a massive missile-and-drone attack on energy infrastructure in Odesa region overnight into 2 September. Ukraine's Energy Ministry reported that a large number of consumers were left without electricity, and Reuters described a large part of the region as affected. Emergency repairs began when security conditions allowed. Public Ukrainian reporting did not identify the substations, lines or generating facilities struck, publish a customer total or megawatt loss, or confirm that the entire regional grid failed; this record therefore uses an approximate Odesa regional marker and does not infer individual impact sites. Separate outages were also reported in Sumy, Kharkiv, Chernihiv and Kherson regions, but the reviewed sources did not establish that each resulted from a newly struck named energy facility. This attack is separate from the Odesa combined heat-and-power plant damage recorded for the preceding night, 1 September.

    2 sourcesDetails +
    Reported impactA large number of consumers across a substantial part of Odesa region lost electricity; no customer total, megawatt loss, facility list or full restoration time was published

    Ukraine's transmission-system operator Ukrenergo said Russia carried out a massive missile-and-drone attack on energy infrastructure in Odesa region overnight into 2 September. Ukraine's Energy Ministry reported that a large number of consumers were left without electricity, and Reuters described a large part of the region as affected. Emergency repairs began when security conditions allowed. Public Ukrainian reporting did not identify the substations, lines or generating facilities struck, publish a customer total or megawatt loss, or confirm that the entire regional grid failed; this record therefore uses an approximate Odesa regional marker and does not infer individual impact sites. Separate outages were also reported in Sumy, Kharkiv, Chernihiv and Kherson regions, but the reviewed sources did not establish that each resulted from a newly struck named energy facility. This attack is separate from the Odesa combined heat-and-power plant damage recorded for the preceding night, 1 September.

    Why it appears here: this record was previously elevated for its scale, consequences, strategic importance or energy-security risk. Major status can be revised as evidence develops.

  6. DocumentedDrone / missile attack

    Erbil-area U.S. bases — Iranian drone attack claim and interceptions

    Erbil, Kurdistan Region, Iraq (regional marker; bases not publicly identified) · Logistics Hub · Middle East

    Kurdish authorities said they intercepted 10 explosive-laden drones in the Erbil area early on 2 September. Iranian television reported that American bases in Erbil had been targeted, and the IRGC separately claimed that its ground forces used missiles and drones against U.S. facilities, including a repair facility, technical-equipment warehouses and a surveillance-balloon control system. Iraq and the United States had not confirmed those target or damage claims in the reviewed reporting. This record therefore documents the independently reported interceptions while retaining the claimed U.S.-base targeting and damage as unverified. No casualties, successful impact, base shutdown or energy-infrastructure damage was confirmed. The marker is regional and does not identify a specific U.S. installation.

    2 sourcesDetails +
    Reported impactNo confirmed base damage, casualties, energy-infrastructure impact or operational interruption was reported

    Kurdish authorities said they intercepted 10 explosive-laden drones in the Erbil area early on 2 September. Iranian television reported that American bases in Erbil had been targeted, and the IRGC separately claimed that its ground forces used missiles and drones against U.S. facilities, including a repair facility, technical-equipment warehouses and a surveillance-balloon control system. Iraq and the United States had not confirmed those target or damage claims in the reviewed reporting. This record therefore documents the independently reported interceptions while retaining the claimed U.S.-base targeting and damage as unverified. No casualties, successful impact, base shutdown or energy-infrastructure damage was confirmed. The marker is regional and does not identify a specific U.S. installation.

    Why it appears here: this record was previously elevated for its scale, consequences, strategic importance or energy-security risk. Major status can be revised as evidence develops.

  7. Reported / attributedDrone / missile attack

    Bahrain U.S. base — Iranian drone attack and interceptions

    Bahrain (national marker; targeted U.S. base not publicly identified) · Logistics Hub · Middle East

    Bahrain said its air-defence systems intercepted several Iranian air attacks early on 2 September. Iranian state media said Iran had launched a large-scale drone attack against a U.S. base in Bahrain. Bahrain did not publicly identify the intended installation or report casualties, successful impacts, damage or an operational interruption. The target claim is therefore attributed to Iranian state media rather than presented as a confirmed strike on a base. The marker is national and must not be read as the location of a verified impact.

    2 sourcesDetails +
    Reported impactNo confirmed impact, casualties, base damage or operational interruption was reported

    Bahrain said its air-defence systems intercepted several Iranian air attacks early on 2 September. Iranian state media said Iran had launched a large-scale drone attack against a U.S. base in Bahrain. Bahrain did not publicly identify the intended installation or report casualties, successful impacts, damage or an operational interruption. The target claim is therefore attributed to Iranian state media rather than presented as a confirmed strike on a base. The marker is national and must not be read as the location of a verified impact.

    Why it appears here: this record was previously elevated for its scale, consequences, strategic importance or energy-security risk. Major status can be revised as evidence develops.

  8. Under investigationSabotage

    Bergheim–Rommerskirchen substation — deliberate grid disruption

    Rommerskirchen near Bergheim, North Rhine-Westphalia, Germany (marker approximate) · Power Grid · Europe

    A deliberately caused short circuit near an Amprion substation at Rommerskirchen, close to Bergheim, took several transmission lines and five RWE lignite units off the grid. The affected units were Neurath G and F and Niederaußem H, G and K, with 4,200 megawatts of combined capacity; they were supplying about 3,000 MW when disconnected. RWE said Neurath G and Niederaußem H, totalling about 1,600 MW, returned on 2 September, with Neurath F expected later that day and Niederaußem G and K during the weekend. Reserve capacity prevented a general power outage. Police said the available evidence did not indicate a technical defect and treated the incident as a deliberate crime, but the method, perpetrator and motive remained under investigation. This record does not connect the incident to the separate explosive-device attack at Turnow-Preilack earlier the same day or attribute it to a state or political group. The marker is an approximate substation-area reference rather than a verified damage coordinate.

    2 sourcesDetails +
    Reported impactFive RWE units with 4,200 MW combined capacity went offline while supplying about 3,000 MW; 1,600 MW returned on 2 September and the remaining units were scheduled for a phased restart

    A deliberately caused short circuit near an Amprion substation at Rommerskirchen, close to Bergheim, took several transmission lines and five RWE lignite units off the grid. The affected units were Neurath G and F and Niederaußem H, G and K, with 4,200 megawatts of combined capacity; they were supplying about 3,000 MW when disconnected. RWE said Neurath G and Niederaußem H, totalling about 1,600 MW, returned on 2 September, with Neurath F expected later that day and Niederaußem G and K during the weekend. Reserve capacity prevented a general power outage. Police said the available evidence did not indicate a technical defect and treated the incident as a deliberate crime, but the method, perpetrator and motive remained under investigation. This record does not connect the incident to the separate explosive-device attack at Turnow-Preilack earlier the same day or attribute it to a state or political group. The marker is an approximate substation-area reference rather than a verified damage coordinate.

    Why it appears here: this record was previously elevated for its scale, consequences, strategic importance or energy-security risk. Major status can be revised as evidence develops.

  9. DocumentedSabotage

    Turnow-Preilack substation — explosive and incendiary-device attack

    Turnow-Preilack, Brandenburg, Germany · Power Grid · Europe

    Unknown perpetrators attacked the Turnow-Preilack electrical substation near the Jänschwalde power station using improvised explosive and incendiary devices intended to create short circuits in high-voltage lines. Brandenburg's interior minister said investigators had found a double-digit number of devices or remnants and that, in two cases, conductive material reached the lines. German police and grid operator 50Hertz reported line damage and a brief interruption, after which all lines returned to service; there was no reported impact on the public and no casualty was reported. LEAG described the incident as an attack on the substation through which Jänschwalde generation enters the 50Hertz grid. A 500-megawatt Jänschwalde unit was also temporarily shut, but LEAG said investigators were examining whether that technical fault was connected or coincidental. Brandenburg Police said on 2 September that the investigation includes suspected disruption of public services, causing an explosives explosion, destruction of essential equipment and formation of a terrorist organisation. On 4 September police reported searches linked to an alleged author of claim letters; on 5 September they announced a search for a 48-year-old suspect in connection with substation sabotage in Brandenburg, North Rhine-Westphalia and Saxony. These are investigative allegations, not a finding of guilt. Accounts initially differed over whether rockets were used, while later police reporting described improvised devices and said rockets were not established. The reviewed police statements do not establish a political motive or group attribution. Confidence is high that the infrastructure attack occurred; responsibility and motive remain unresolved. The marker is an approximate substation-area reference, not a verified device location.

    7 sourcesDetails +
    Reported impact50Hertz reported only a brief interruption and restored all affected lines; a temporary Jänschwalde Unit B shutdown was reported, but its connection to the attack was still being examined

    Unknown perpetrators attacked the Turnow-Preilack electrical substation near the Jänschwalde power station using improvised explosive and incendiary devices intended to create short circuits in high-voltage lines. Brandenburg's interior minister said investigators had found a double-digit number of devices or remnants and that, in two cases, conductive material reached the lines. German police and grid operator 50Hertz reported line damage and a brief interruption, after which all lines returned to service; there was no reported impact on the public and no casualty was reported. LEAG described the incident as an attack on the substation through which Jänschwalde generation enters the 50Hertz grid. A 500-megawatt Jänschwalde unit was also temporarily shut, but LEAG said investigators were examining whether that technical fault was connected or coincidental. Brandenburg Police said on 2 September that the investigation includes suspected disruption of public services, causing an explosives explosion, destruction of essential equipment and formation of a terrorist organisation. On 4 September police reported searches linked to an alleged author of claim letters; on 5 September they announced a search for a 48-year-old suspect in connection with substation sabotage in Brandenburg, North Rhine-Westphalia and Saxony. These are investigative allegations, not a finding of guilt. Accounts initially differed over whether rockets were used, while later police reporting described improvised devices and said rockets were not established. The reviewed police statements do not establish a political motive or group attribution. Confidence is high that the infrastructure attack occurred; responsibility and motive remain unresolved. The marker is an approximate substation-area reference, not a verified device location.

    Why it appears here: this record was previously elevated for its scale, consequences, strategic importance or energy-security risk. Major status can be revised as evidence develops.

  10. DocumentedDrone / missile attack

    Ust-Luga Baltic port — September drone strike and fire

    Ust-Luga, Leningrad Oblast, Russia · Port Export Terminal · Russia

    A fresh overnight Ukrainian drone attack caused damage and a fire in the Ust-Luga port zone on Russia's Baltic coast. Leningrad Oblast Governor Alexander Drozdenko said air defences intercepted 52 drones during an approximately four-hour assault and confirmed damage and fire at the port; the fire was reported extinguished later that morning and no casualties were reported. Ukraine subsequently confirmed the strike. Public reporting available at entry time did not identify the exact berth, storage tank, loading equipment or processing unit hit, and did not establish an export suspension or processing outage. The record therefore does not infer that the Transneft oil terminal or Novatek gas-condensate complex was struck merely because both operate within Ust-Luga. This is a separate event from the port attacks already recorded for March, July and 14 August 2026.

    3 sourcesDetails +
    Reported impactThe specific terminal equipment damaged and any interruption to crude, products or gas-condensate handling had not been confirmed in the reviewed reporting

    A fresh overnight Ukrainian drone attack caused damage and a fire in the Ust-Luga port zone on Russia's Baltic coast. Leningrad Oblast Governor Alexander Drozdenko said air defences intercepted 52 drones during an approximately four-hour assault and confirmed damage and fire at the port; the fire was reported extinguished later that morning and no casualties were reported. Ukraine subsequently confirmed the strike. Public reporting available at entry time did not identify the exact berth, storage tank, loading equipment or processing unit hit, and did not establish an export suspension or processing outage. The record therefore does not infer that the Transneft oil terminal or Novatek gas-condensate complex was struck merely because both operate within Ust-Luga. This is a separate event from the port attacks already recorded for March, July and 14 August 2026.

    Why it appears here: this record was previously elevated for its scale, consequences, strategic importance or energy-security risk. Major status can be revised as evidence develops.

  11. Reported / attributedNatural disaster

    Tropical Storm Edouard — Port Arthur, Sabine Pass and Cameron facilities at risk

    Upper Texas and southwest Louisiana Gulf Coast, United States · Refinery · Americas

    FACILITIES AT RISK — NOT A CONFIRMED DAMAGE OR SHUTDOWN EVENT. At 11:00 a.m. CDT on 1 September, the National Hurricane Center placed Tropical Storm Edouard about 40 miles east-southeast of Port Arthur, Texas, and 20 miles south-southwest of Cameron, Louisiana, with maximum sustained winds near 50 mph while moving northwest. The storm was approaching the upper Texas and southwest Louisiana coast after forecasts warned of possible significant strengthening. Its track exposed the Port Arthur–Beaumont refining and petrochemical complex, Sabine Pass shipping and LNG infrastructure, Cameron-area LNG facilities, coastal pipelines, terminals, offshore support operations and local power systems to wind, storm surge, heavy rain and flooding. This marker represents the exposed corridor rather than the storm centre or a damage location. At the time captured here, the reviewed sources did not confirm a refinery or LNG shutdown, production loss, spill, fire or physical damage caused by Edouard. Any later operator-reported impact should be recorded separately or used to update this alert rather than inferred from the forecast.

    3 sourcesDetails +
    Reported impactNo refinery, LNG-terminal or petrochemical shutdown, production curtailment or physical damage was confirmed in the cited reporting at the time of this alert

    FACILITIES AT RISK — NOT A CONFIRMED DAMAGE OR SHUTDOWN EVENT. At 11:00 a.m. CDT on 1 September, the National Hurricane Center placed Tropical Storm Edouard about 40 miles east-southeast of Port Arthur, Texas, and 20 miles south-southwest of Cameron, Louisiana, with maximum sustained winds near 50 mph while moving northwest. The storm was approaching the upper Texas and southwest Louisiana coast after forecasts warned of possible significant strengthening. Its track exposed the Port Arthur–Beaumont refining and petrochemical complex, Sabine Pass shipping and LNG infrastructure, Cameron-area LNG facilities, coastal pipelines, terminals, offshore support operations and local power systems to wind, storm surge, heavy rain and flooding. This marker represents the exposed corridor rather than the storm centre or a damage location. At the time captured here, the reviewed sources did not confirm a refinery or LNG shutdown, production loss, spill, fire or physical damage caused by Edouard. Any later operator-reported impact should be recorded separately or used to update this alert rather than inferred from the forecast.

    Why it appears here: this record was previously elevated for its scale, consequences, strategic importance or energy-security risk. Major status can be revised as evidence develops.

  12. DocumentedDrone / missile attack

    Odesa combined heat and power plant — missile and drone strike

    Odesa, Ukraine · Power Station · Europe

    Ukraine's state energy company Naftogaz said Russia attacked its Odesa combined heat and power plant with missiles and drones overnight into 1 September, damaging part of the main and auxiliary equipment. Debris clearance was continuing when the company reported the strike. Naftogaz did not publish the exact equipment hit, repair timetable, generating-capacity loss or whether heat and electricity service was interrupted, so this record does not claim a full shutdown. The wider overnight attack also damaged port-export infrastructure and temporarily closed the Orlivka ferry border crossing with Romania. Ukraine's emergency service reported one person injured in a fire at a residential building, but did not attribute that injury specifically to the CHP strike. The marker is an approximate Odesa reference rather than a surveyed impact coordinate.

    1 sourceDetails +
    Reported impactNaftogaz reported damage to part of the plant's main and auxiliary equipment; it did not publish a generation-loss figure or confirm a full shutdown

    Ukraine's state energy company Naftogaz said Russia attacked its Odesa combined heat and power plant with missiles and drones overnight into 1 September, damaging part of the main and auxiliary equipment. Debris clearance was continuing when the company reported the strike. Naftogaz did not publish the exact equipment hit, repair timetable, generating-capacity loss or whether heat and electricity service was interrupted, so this record does not claim a full shutdown. The wider overnight attack also damaged port-export infrastructure and temporarily closed the Orlivka ferry border crossing with Romania. Ukraine's emergency service reported one person injured in a fire at a residential building, but did not attribute that injury specifically to the CHP strike. The marker is an approximate Odesa reference rather than a surveyed impact coordinate.

    Why it appears here: this record was previously elevated for its scale, consequences, strategic importance or energy-security risk. Major status can be revised as evidence develops.

  13. Reported / attributedDrone / missile attack

    M/T Sinopa and M/T Hawk — reported U.S. strikes off Jask

    Off Jask, Gulf of Oman (approximate regional marker) · Port or tanker · Middle East

    Axios and Al-Monitor, citing U.S. officials, reported that U.S. forces fired missiles into the engine rooms of two Iranian government tankers anchored off Iran's coast during the wider 1 September strike wave. Axios described the attacks as the first U.S. tanker strikes explicitly framed as retaliation for attacks on commercial shipping under a new 'tanker-for-tanker' policy. Al-Monitor reported that CENTCOM infrared footage shows explosions at the sterns of two separate tankers. TankerTrackers and subsequent maritime analysis identified the vessels as the NITC Suezmax M/T Sinopa, IMO 9172038 and formerly Susangird, and the NITC VLCC M/T Hawk, IMO 9362061 and formerly Honar and Horse, off Jask in the Gulf of Oman. TankerTrackers assessed that both appeared to carry some oil cargo, a departure from the more usual pattern of targeting unladen or ballast vessels, but the public imagery did not quantify the cargoes. The disclosure followed near-simultaneous projectile strikes on the Saudi-flagged SIDR and Liberian-flagged SENEGAL PROSPERITY, two VLCCs carrying Saudi crude; it remains imprecise to describe both damaged commercial vessels as Saudi tankers. Exact strike coordinates, crew status, damage extent, subsequent mobility and pollution remain unpublished. The marker is a broad Jask-area reference and must not be treated as a verified strike coordinate.

    5 sourcesDetails +
    Reported impactBoth tankers' engine rooms were reportedly hit; TankerTrackers assessed that both appeared to carry some oil, while operational status, casualties and pollution remain undisclosed

    Axios and Al-Monitor, citing U.S. officials, reported that U.S. forces fired missiles into the engine rooms of two Iranian government tankers anchored off Iran's coast during the wider 1 September strike wave. Axios described the attacks as the first U.S. tanker strikes explicitly framed as retaliation for attacks on commercial shipping under a new 'tanker-for-tanker' policy. Al-Monitor reported that CENTCOM infrared footage shows explosions at the sterns of two separate tankers. TankerTrackers and subsequent maritime analysis identified the vessels as the NITC Suezmax M/T Sinopa, IMO 9172038 and formerly Susangird, and the NITC VLCC M/T Hawk, IMO 9362061 and formerly Honar and Horse, off Jask in the Gulf of Oman. TankerTrackers assessed that both appeared to carry some oil cargo, a departure from the more usual pattern of targeting unladen or ballast vessels, but the public imagery did not quantify the cargoes. The disclosure followed near-simultaneous projectile strikes on the Saudi-flagged SIDR and Liberian-flagged SENEGAL PROSPERITY, two VLCCs carrying Saudi crude; it remains imprecise to describe both damaged commercial vessels as Saudi tankers. Exact strike coordinates, crew status, damage extent, subsequent mobility and pollution remain unpublished. The marker is a broad Jask-area reference and must not be treated as a verified strike coordinate.

    Why it appears here: this record was previously elevated for its scale, consequences, strategic importance or energy-security risk. Major status can be revised as evidence develops.

  14. DocumentedShipping disruption

    Iran — parliament speaker urges petrol conservation amid blockade

    Iran (national event; marker at Tehran) · Oil or fuel facility · Middle East

    Iranian Parliament Speaker Mohammad Bagher Ghalibaf urged the public to reduce petrol consumption in a televised address, saying Iran faced a daily petrol deficit of about 15 million litres and could meet demand from domestic production if consumption were managed. AFP reporting linked the import difficulty to the US naval blockade, while separate reporting documented queues at Tehran filling stations and official discussion of possible subsidy changes. Ghalibaf said industry, rather than households alone, was responsible for part of the high consumption. The conservation appeal and stated deficit are documented official remarks; they do not establish that national stocks are exhausted, that formal rationing has begun or that a specific refinery has shut. The marker represents a nationwide supply-pressure event and is placed at Tehran for display, not at a physical incident site.

    4 sourcesDetails +
    Reported impactParliament Speaker Mohammad Bagher Ghalibaf reported a daily petrol deficit of about 15 million litres and said conservation could allow domestic production to meet demand

    Iranian Parliament Speaker Mohammad Bagher Ghalibaf urged the public to reduce petrol consumption in a televised address, saying Iran faced a daily petrol deficit of about 15 million litres and could meet demand from domestic production if consumption were managed. AFP reporting linked the import difficulty to the US naval blockade, while separate reporting documented queues at Tehran filling stations and official discussion of possible subsidy changes. Ghalibaf said industry, rather than households alone, was responsible for part of the high consumption. The conservation appeal and stated deficit are documented official remarks; they do not establish that national stocks are exhausted, that formal rationing has begun or that a specific refinery has shut. The marker represents a nationwide supply-pressure event and is placed at Tehran for display, not at a physical incident site.

    Why it appears here: this record was previously elevated for its scale, consequences, strategic importance or energy-security risk. Major status can be revised as evidence develops.

  15. Under investigationExplosion

    Asaluyeh energy hub — explosion reported, impact under investigation

    Asaluyeh, Bushehr Province, Iran (marker approximate) · Gas facility · Middle East

    Fars News Agency, citing the governor of Asaluyeh County, reported that an explosion was heard in the area during a wider round of strikes and explosions across southern Iran. Asaluyeh hosts major South Pars gas-processing, condensate, petrochemical and port infrastructure, making the report directly relevant to energy security. However, the initial account did not identify an impact point or confirm that a gas plant, refinery, petrochemical unit, storage tank, port or pipeline was struck. It also did not confirm the cause, attacking party, weapon, fire, damage, casualties, evacuation, production loss or shutdown. Reports describing explosions 'at the gas complex' go beyond the governor's limited statement and are not treated here as verified. The marker is an approximate reference for the Asaluyeh industrial area, not a confirmed impact coordinate. This is separate from the documented March and April 2026 attacks on South Pars and Asaluyeh facilities.

    3 sourcesDetails +
    Reported impactNo confirmed damage, fire, shutdown or production loss was reported at South Pars processing plants, petrochemical facilities or associated port infrastructure

    Fars News Agency, citing the governor of Asaluyeh County, reported that an explosion was heard in the area during a wider round of strikes and explosions across southern Iran. Asaluyeh hosts major South Pars gas-processing, condensate, petrochemical and port infrastructure, making the report directly relevant to energy security. However, the initial account did not identify an impact point or confirm that a gas plant, refinery, petrochemical unit, storage tank, port or pipeline was struck. It also did not confirm the cause, attacking party, weapon, fire, damage, casualties, evacuation, production loss or shutdown. Reports describing explosions 'at the gas complex' go beyond the governor's limited statement and are not treated here as verified. The marker is an approximate reference for the Asaluyeh industrial area, not a confirmed impact coordinate. This is separate from the documented March and April 2026 attacks on South Pars and Asaluyeh facilities.

    Why it appears here: this record was previously elevated for its scale, consequences, strategic importance or energy-security risk. Major status can be revised as evidence develops.

  16. Reported / attributedDrone / missile attack

    Chabahar–Konarak — four reported US projectile impacts

    Chabahar and Konarak, Sistan and Baluchestan Province, Iran (marker approximate) · Port or tanker · Middle East

    Iran's official IRNA news agency, citing a provincial security official, reported that four projectiles struck locations across Chabahar and neighbouring Konarak during a wider round of acknowledged US strikes on IRGC targets along Iran's southern coast. Iranian media also reported further explosions in Chabahar later in the evening. Authorities said a damage assessment was under way. The reviewed reporting did not identify the four impact points, divide them between the two counties or confirm casualties. It also did not establish a hit on Chabahar's commercial port, fuel storage, maritime traffic systems or other energy infrastructure. Konarak contains naval and aviation facilities, making a military target plausible, but that does not identify the actual targets. Iran's Revolutionary Guard subsequently claimed that ballistic missiles struck the US Marine facility at Camp Titin near Aqaba, Jordan, killing US personnel and destroying installations and helicopters. That claimed base damage and casualty account is not corroborated: Jordan said its air defences intercepted 10 of 13 incoming ballistic missiles, with three falling in unpopulated areas without casualties, and two US officials told Reuters that no US casualties had been reported from the attacks on facilities in Jordan. This is recorded as one grouped Chabahar–Konarak attack event rather than four incidents; the Camp Titin exchange is included only as retaliation context, not as a confirmed successful base strike. The marker is an approximate Chabahar Bay reference and must not be read as a verified impact coordinate. This event is distinct from the July 2026 strike that Iranian port authorities said damaged Chabahar Port's maritime traffic-control centre.

    5 sourcesDetails +
    Reported impactNo verified damage, closure or operating interruption at Chabahar's commercial port, fuel facilities or maritime infrastructure had been reported

    Iran's official IRNA news agency, citing a provincial security official, reported that four projectiles struck locations across Chabahar and neighbouring Konarak during a wider round of acknowledged US strikes on IRGC targets along Iran's southern coast. Iranian media also reported further explosions in Chabahar later in the evening. Authorities said a damage assessment was under way. The reviewed reporting did not identify the four impact points, divide them between the two counties or confirm casualties. It also did not establish a hit on Chabahar's commercial port, fuel storage, maritime traffic systems or other energy infrastructure. Konarak contains naval and aviation facilities, making a military target plausible, but that does not identify the actual targets. Iran's Revolutionary Guard subsequently claimed that ballistic missiles struck the US Marine facility at Camp Titin near Aqaba, Jordan, killing US personnel and destroying installations and helicopters. That claimed base damage and casualty account is not corroborated: Jordan said its air defences intercepted 10 of 13 incoming ballistic missiles, with three falling in unpopulated areas without casualties, and two US officials told Reuters that no US casualties had been reported from the attacks on facilities in Jordan. This is recorded as one grouped Chabahar–Konarak attack event rather than four incidents; the Camp Titin exchange is included only as retaliation context, not as a confirmed successful base strike. The marker is an approximate Chabahar Bay reference and must not be read as a verified impact coordinate. This event is distinct from the July 2026 strike that Iranian port authorities said damaged Chabahar Port's maritime traffic-control centre.

    Why it appears here: this record was previously elevated for its scale, consequences, strategic importance or energy-security risk. Major status can be revised as evidence develops.

  17. Under investigationShipping disruption

    Unnamed tanker — encounter with unidentified military forces

    Indian Ocean, east of the Strait of Hormuz · Port or tanker · Middle East

    UK Maritime Trade Operations Advisory 123-26 said a tanker master reported an incident involving the vessel and military forces in the Indian Ocean. Associated Press reported that maritime-security firm Ambrey said the tanker had reportedly been stopped and remained adrift. No casualties were reported. The advisory did not identify the tanker, flag, owner, cargo, military force, reason for the encounter, damage, pollution or precise position. UKMTO issued an advisory rather than classifying the event as an attack, so this record is an investigating shipping disruption and does not assign responsibility. The map marker is a broad illustrative Gulf of Oman position, not a reported incident coordinate.

    2 sourcesDetails +
    Reported impactThe individual tanker was reportedly stopped and remained adrift; no cargo loss, pollution or wider shipping closure was reported

    UK Maritime Trade Operations Advisory 123-26 said a tanker master reported an incident involving the vessel and military forces in the Indian Ocean. Associated Press reported that maritime-security firm Ambrey said the tanker had reportedly been stopped and remained adrift. No casualties were reported. The advisory did not identify the tanker, flag, owner, cargo, military force, reason for the encounter, damage, pollution or precise position. UKMTO issued an advisory rather than classifying the event as an attack, so this record is an investigating shipping disruption and does not assign responsibility. The map marker is a broad illustrative Gulf of Oman position, not a reported incident coordinate.

    Why it appears here: this record was previously elevated for its scale, consequences, strategic importance or energy-security risk. Major status can be revised as evidence develops.

  18. Reported / attributedExplosion

    Unidentified supertanker — uncorroborated IRGC mine-strike claim

    Southern Strait of Hormuz, near the Omani transit corridor (marker approximate) · Port or tanker · Middle East

    DISPUTED CLAIM — POSSIBLE PROPAGANDA OR MISINFORMATION. Iran's Islamic Revolutionary Guard Corps said an unidentified supertanker caught fire and stopped after striking two naval mines in the southern Strait of Hormuz. CENTCOM directly denied the account, stating that no ships had hit mines in the strait and describing it as IRGC disinformation intended to intimidate commercial shipping. No vessel name, IMO number, operator statement, distress report, exact position, casualty assessment, pollution report, UKMTO notice or other independent maritime-authority confirmation has been identified. Reuters and other outlets documented the allegation but did not independently verify the vessel, mine strikes or fire. 'Supertanker' often denotes a VLCC, but even the vessel class is unconfirmed. The record preserves the information claim and the official denial; it is not presented as an established attack. The marker is only an approximate reference, not a verified incident coordinate.

    4 sourcesDetails +
    Reported impactThe IRGC said the unidentified tanker was brought to a complete stop; cargo, damage, casualties, pollution and wider navigation effects were not published

    DISPUTED CLAIM — POSSIBLE PROPAGANDA OR MISINFORMATION. Iran's Islamic Revolutionary Guard Corps said an unidentified supertanker caught fire and stopped after striking two naval mines in the southern Strait of Hormuz. CENTCOM directly denied the account, stating that no ships had hit mines in the strait and describing it as IRGC disinformation intended to intimidate commercial shipping. No vessel name, IMO number, operator statement, distress report, exact position, casualty assessment, pollution report, UKMTO notice or other independent maritime-authority confirmation has been identified. Reuters and other outlets documented the allegation but did not independently verify the vessel, mine strikes or fire. 'Supertanker' often denotes a VLCC, but even the vessel class is unconfirmed. The record preserves the information claim and the official denial; it is not presented as an established attack. The marker is only an approximate reference, not a verified incident coordinate.

    Why it appears here: this record was previously elevated for its scale, consequences, strategic importance or energy-security risk. Major status can be revised as evidence develops.

  19. DocumentedDrone / missile attack

    Larak Island — US strike on reported sea-mine launchers

    Larak Island, Strait of Hormuz, Iran · Port or tanker · Middle East

    US forces struck two Iranian Revolutionary Guard launchers on Larak Island after US surveillance reportedly observed personnel preparing to launch rockets carrying sea mines into the Strait of Hormuz, according to US Central Command. The strike was the first publicly reported US military action inside Iran in about a month and followed the announced clearance of mines from the strait's main international shipping routes. Iranian media initially reported two people killed and several injured. Tasnim subsequently said one injured person died in hospital, raising the Iranian-reported death toll to three; a stable final injury count has not been published. These casualty figures remain attributed to Iranian reporting rather than independently verified. Iran subsequently launched ballistic missiles toward US sites in Jordan. Iranian state television broadcast what it described as the launches, while Jordan's armed forces said its air defences intercepted eight missiles that entered Jordanian airspace early on 31 August. A US official told Axios that several missiles were launched but none struck a US base and no damage or casualties were reported. The retaliation is therefore documented as a missile launch and interception, not as a successful strike on a base or energy facility. The Larak targets were military, but the reported mine-launch preparations directly concerned the security of the Strait of Hormuz oil-shipping corridor. The public accounts did not establish the weapon used by the United States, damage beyond the two launchers or any strike on oil infrastructure. The marker remains an approximate Larak Island reference rather than a verified impact coordinate.

    9 sourcesDetails +
    Reported impact3 reported killed · several injured · 2 launchers struck · Iranian figures remain provisional

    US forces struck two Iranian Revolutionary Guard launchers on Larak Island after US surveillance reportedly observed personnel preparing to launch rockets carrying sea mines into the Strait of Hormuz, according to US Central Command. The strike was the first publicly reported US military action inside Iran in about a month and followed the announced clearance of mines from the strait's main international shipping routes. Iranian media initially reported two people killed and several injured. Tasnim subsequently said one injured person died in hospital, raising the Iranian-reported death toll to three; a stable final injury count has not been published. These casualty figures remain attributed to Iranian reporting rather than independently verified. Iran subsequently launched ballistic missiles toward US sites in Jordan. Iranian state television broadcast what it described as the launches, while Jordan's armed forces said its air defences intercepted eight missiles that entered Jordanian airspace early on 31 August. A US official told Axios that several missiles were launched but none struck a US base and no damage or casualties were reported. The retaliation is therefore documented as a missile launch and interception, not as a successful strike on a base or energy facility. The Larak targets were military, but the reported mine-launch preparations directly concerned the security of the Strait of Hormuz oil-shipping corridor. The public accounts did not establish the weapon used by the United States, damage beyond the two launchers or any strike on oil infrastructure. The marker remains an approximate Larak Island reference rather than a verified impact coordinate.

    Why it appears here: this record was previously elevated for its scale, consequences, strategic importance or energy-security risk. Major status can be revised as evidence develops.

  20. DocumentedSpill

    Caroline Bezengi — grounded sanctioned tanker breaking up, major oil spill

    Jazirat Al Qibliyyah (Hallaniyat Islands), Dhofar, Oman · Port or tanker · Middle East

    The Cameroon-flagged (a flag it lost in a June deregistration crackdown on sanctioned tankers) Suezmax tanker Caroline Bezengi, sanctioned by the EU, UK, US (OFAC), Canada and Switzerland over alleged links to Russian oil exports and past association with state shipowner Sovcomflot, sailed from Novorossiysk, Russia in April, transited the Suez Canal in May, and first reported difficulties around 8 June while off Yemen/Oman's Dhofar coast, with maritime sources suggesting an onboard blast; the cause remains unresolved and no group has claimed responsibility. The crew was evacuated without injury, and the unmanned, 25-year-old tanker grounded on rocks at Jazirat Al Qibliyyah in the Hallaniyat Islands — a marine nature reserve — on 30 June. An Omani onboard survey on 12 July found the vessel sinking deeper and listing further, with crude leaking into ballast tanks and the double-hull spacing. Oman's Ministry of Transport issued a 24-hour removal directive to Shanghai-based manager Rentoor Ship Management on 23 July, but the company did not respond; the vessel is uninsured by any recognized Western provider, and the International Oil Pollution Compensation Funds (IOPC Funds) declined to become involved, treating the incident as an act of war outside its compensation regime. By 12 August, satellite analyst John Amos told Reuters the slick had grown to roughly 2,000 sq km, warning of 'a nightmare scenario' if no adequate response materializes, versus Oman's official estimate of about 400 sq km and Greenpeace Germany's tracked estimate of roughly 600 sq km in early August; the wide range reflects differing measurement methods and dates rather than a single agreed figure. Oman said it continued monitoring via satellite imagery, field surveys and technical models through 12 August. On 13-14 August, UK-based maritime risk firm Ambrey announced it had been engaged to lead salvage operations, with specialist personnel boarding the vessel (assisted by the Omani air force) to assess its condition and begin stabilising the cargo and additional salvage vessels expected; Ambrey's response director described the effort as complicated by adverse weather from the Khareef monsoon and gave no timeline or cost estimate. By 14 August, Oman's environmental authority confirmed oil had reached the shoreline at Ras Madrakah on the central coast, with officials warning the slick could extend a further 100km-plus north toward Masirah Island.

    5 sourcesDetails +

    The Cameroon-flagged (a flag it lost in a June deregistration crackdown on sanctioned tankers) Suezmax tanker Caroline Bezengi, sanctioned by the EU, UK, US (OFAC), Canada and Switzerland over alleged links to Russian oil exports and past association with state shipowner Sovcomflot, sailed from Novorossiysk, Russia in April, transited the Suez Canal in May, and first reported difficulties around 8 June while off Yemen/Oman's Dhofar coast, with maritime sources suggesting an onboard blast; the cause remains unresolved and no group has claimed responsibility. The crew was evacuated without injury, and the unmanned, 25-year-old tanker grounded on rocks at Jazirat Al Qibliyyah in the Hallaniyat Islands — a marine nature reserve — on 30 June. An Omani onboard survey on 12 July found the vessel sinking deeper and listing further, with crude leaking into ballast tanks and the double-hull spacing. Oman's Ministry of Transport issued a 24-hour removal directive to Shanghai-based manager Rentoor Ship Management on 23 July, but the company did not respond; the vessel is uninsured by any recognized Western provider, and the International Oil Pollution Compensation Funds (IOPC Funds) declined to become involved, treating the incident as an act of war outside its compensation regime. By 12 August, satellite analyst John Amos told Reuters the slick had grown to roughly 2,000 sq km, warning of 'a nightmare scenario' if no adequate response materializes, versus Oman's official estimate of about 400 sq km and Greenpeace Germany's tracked estimate of roughly 600 sq km in early August; the wide range reflects differing measurement methods and dates rather than a single agreed figure. Oman said it continued monitoring via satellite imagery, field surveys and technical models through 12 August. On 13-14 August, UK-based maritime risk firm Ambrey announced it had been engaged to lead salvage operations, with specialist personnel boarding the vessel (assisted by the Omani air force) to assess its condition and begin stabilising the cargo and additional salvage vessels expected; Ambrey's response director described the effort as complicated by adverse weather from the Khareef monsoon and gave no timeline or cost estimate. By 14 August, Oman's environmental authority confirmed oil had reached the shoreline at Ras Madrakah on the central coast, with officials warning the slick could extend a further 100km-plus north toward Masirah Island.

    Why it appears here: this record was previously elevated for its scale, consequences, strategic importance or energy-security risk. Major status can be revised as evidence develops.

  21. DocumentedOperational failure

    Cernavodă NPP — both reactors shut down as record-low Danube cuts cooling water

    Cernavodă, Constanța County, Romania · Nuclear Power Plant · Europe

    A severe drought and heatwave drove the Danube River to record-low levels, cutting the cooling water available to Romania's only nuclear plant, Cernavodă. Unit 1 was shut down and disconnected from the grid on the morning of 28 July 2026; Unit 2 was initially kept online after an analysis found its operating parameters still allowed safe continued operation. Authorities tried several emergency river-diversion measures to keep Unit 2 running, including blowing up an underwater rock formation near Izvoarele and, in early August, using the navy to clear the Bala Canal and sinking four rock-filled barges to build an underwater barrier redirecting flow toward the plant's intake. Those measures ultimately proved insufficient: operator Nuclearelectrica carried out a controlled shutdown of Unit 2 on 13 August 2026, saying the decision was driven by the continued fall in the Danube's level and stressing that keeping both units in a safe shutdown state has no impact on nuclear safety, personnel, the environment or the population. Romania's Ministry of Energy said electricity demand would be fully covered by alternative sources and imports while both reactors remain offline; acting Prime Minister Ilie Bolojan had already declared a nationwide energy-sector state of alert for August, and the same power crunch led Romania's government to ask roughly 80 major industrial electricity users to cut consumption, with Dacia and Ford both temporarily halting production at their Romanian car plants (using the pause for planned maintenance) until 19 August, a step officials said would save about 200 MW. The drought produced parallel effects elsewhere on the Danube: Hungary shut its only nuclear plant, Paks, entirely (see the separate Paks record), while Bulgaria's Kozloduy plant continued operating at planned capacity, with Bulgarian officials coordinating with Serbia to release water from the Djerdap 1 (Iron Gates) dam upstream to keep river levels above Kozloduy's cooling threshold. No radiological release was reported at any of the three plants; this remains a drought-driven operational and cooling-water event, not a nuclear-safety accident. The situation will depend on whether rainfall returns and the Danube recovers enough to allow the reactors to resume operation.

    2 sourcesDetails +
    Reported impactFull plant capacity (two ≈700 MW units) removed from the grid. The plant normally supplies about one-fifth of Romania's electricity

    A severe drought and heatwave drove the Danube River to record-low levels, cutting the cooling water available to Romania's only nuclear plant, Cernavodă. Unit 1 was shut down and disconnected from the grid on the morning of 28 July 2026; Unit 2 was initially kept online after an analysis found its operating parameters still allowed safe continued operation. Authorities tried several emergency river-diversion measures to keep Unit 2 running, including blowing up an underwater rock formation near Izvoarele and, in early August, using the navy to clear the Bala Canal and sinking four rock-filled barges to build an underwater barrier redirecting flow toward the plant's intake. Those measures ultimately proved insufficient: operator Nuclearelectrica carried out a controlled shutdown of Unit 2 on 13 August 2026, saying the decision was driven by the continued fall in the Danube's level and stressing that keeping both units in a safe shutdown state has no impact on nuclear safety, personnel, the environment or the population. Romania's Ministry of Energy said electricity demand would be fully covered by alternative sources and imports while both reactors remain offline; acting Prime Minister Ilie Bolojan had already declared a nationwide energy-sector state of alert for August, and the same power crunch led Romania's government to ask roughly 80 major industrial electricity users to cut consumption, with Dacia and Ford both temporarily halting production at their Romanian car plants (using the pause for planned maintenance) until 19 August, a step officials said would save about 200 MW. The drought produced parallel effects elsewhere on the Danube: Hungary shut its only nuclear plant, Paks, entirely (see the separate Paks record), while Bulgaria's Kozloduy plant continued operating at planned capacity, with Bulgarian officials coordinating with Serbia to release water from the Djerdap 1 (Iron Gates) dam upstream to keep river levels above Kozloduy's cooling threshold. No radiological release was reported at any of the three plants; this remains a drought-driven operational and cooling-water event, not a nuclear-safety accident. The situation will depend on whether rainfall returns and the Danube recovers enough to allow the reactors to resume operation.

    Why it appears here: this record was previously elevated for its scale, consequences, strategic importance or energy-security risk. Major status can be revised as evidence develops.

  22. DocumentedDrone / missile attack

    Zawiya oil complex — multi-day drone attack wave

    Zawiya, Libya · Refinery · Africa

    A series of drone strikes hit critical infrastructure around Zawiya over several days. Libya's National Oil Corporation said weekend strikes damaged a fuel tank and a desalination plant linked to the oil complex. On 10 August, a drone directly struck a gasoline-storage tank at the Zawiya refinery, igniting a major fire that burned overnight; the tank, which held 4.5 million litres of fuel, subsequently collapsed and the operator declared its maximum emergency level. While responders were fighting the blaze on 11 August, another drone landed near a key refinery tank without reported casualties. Two further drones struck Zawiya's power plant: one damaged its firefighting system and another landed close to the main fuel storage and started a fire that was quickly controlled. The National Oil Corporation said emergency and safety teams brought the fires under control earlier than expected by late 11 August, while separately warning it could declare force majeure at the Zawiya complex — which feeds the 300,000-bpd Sharara oilfield and represents a large share of Libya's 120,000-bpd refining capacity — if drone attacks on its energy assets continued. Early on 12 August, a further drone strike destroyed an electricity substation feeding the Zawiya power plant, cutting power to wide areas south of the city; Libya's General Electricity Company (Gecol) warned that continued attacks could trigger a partial or general grid blackout, and the Petroleum Facilities Guard said drone wreckage indicated fibre-optic-guided FPV drones. The Zawiya Municipal Council reported 18 people treated for smoke inhalation from the 12 August strike, with no fatalities. No group had claimed responsibility for any strike in the wave, and the public reporting did not establish an attacker, a complete refinery shutdown, a quantified production loss or pollution. This grouped marker represents the closely spaced attacks across the refinery, associated desalination facilities, power plant and substation rather than implying that every strike hit the same installation.

    3 sourcesDetails +
    Reported impactA gasoline tank containing 4.5 million litres collapsed; an electricity substation feeding the Zawiya power plant was also destroyed, cutting power to wide areas south of the city

    A series of drone strikes hit critical infrastructure around Zawiya over several days. Libya's National Oil Corporation said weekend strikes damaged a fuel tank and a desalination plant linked to the oil complex. On 10 August, a drone directly struck a gasoline-storage tank at the Zawiya refinery, igniting a major fire that burned overnight; the tank, which held 4.5 million litres of fuel, subsequently collapsed and the operator declared its maximum emergency level. While responders were fighting the blaze on 11 August, another drone landed near a key refinery tank without reported casualties. Two further drones struck Zawiya's power plant: one damaged its firefighting system and another landed close to the main fuel storage and started a fire that was quickly controlled. The National Oil Corporation said emergency and safety teams brought the fires under control earlier than expected by late 11 August, while separately warning it could declare force majeure at the Zawiya complex — which feeds the 300,000-bpd Sharara oilfield and represents a large share of Libya's 120,000-bpd refining capacity — if drone attacks on its energy assets continued. Early on 12 August, a further drone strike destroyed an electricity substation feeding the Zawiya power plant, cutting power to wide areas south of the city; Libya's General Electricity Company (Gecol) warned that continued attacks could trigger a partial or general grid blackout, and the Petroleum Facilities Guard said drone wreckage indicated fibre-optic-guided FPV drones. The Zawiya Municipal Council reported 18 people treated for smoke inhalation from the 12 August strike, with no fatalities. No group had claimed responsibility for any strike in the wave, and the public reporting did not establish an attacker, a complete refinery shutdown, a quantified production loss or pollution. This grouped marker represents the closely spaced attacks across the refinery, associated desalination facilities, power plant and substation rather than implying that every strike hit the same installation.

    Why it appears here: this record was previously elevated for its scale, consequences, strategic importance or energy-security risk. Major status can be revised as evidence develops.

  23. DocumentedDrone / missile attack

    Tihamah — double-tap missile attack off al-Makha (Mocha)

    Bab al-Mandeb strait, Yemeni territorial waters near Mokha/al-Makha, approximately 5 NM offshore; precise position not published · Port or tanker · Middle East

    UK Maritime Trade Operations classified Warning 110-26 as an attack after receiving a report that a stationary cargo vessel in the southern Red Sea near al-Makha (Mocha) had been hit by an unknown projectile; it did not name the vessel. Yemeni and international reporting subsequently identified the ship as the Tihamah, a 63-metre, Tanzanian-flagged, Egyptian-owned multipurpose vessel built in 2024 and licensed to carry passengers and commercial goods between Aden, Djibouti, Somalia and Socotra; it was en route to Mokha port with 11 crew (Pakistani and Indonesian nationals) when it was hit. Yemen's Transport Ministry said Houthi forces fired three ballistic missiles at the ship in a first strike that caused a fire, significant damage and an initial reported toll of four dead. As government coastguard and armed-forces personnel evacuated the dead and wounded roughly three hours later, the Houthis fired an additional ballistic missile at the rescue site, killing at least two more people, including two Yemeni rescuers (one named by officials as Abkar Muhammad Mahmoud), for a combined toll of six killed and ten wounded (seven of them crew). Yemen's Transport Ministry and Pakistan's Deputy Prime Minister and Foreign Minister Ishaq Dar both said three Pakistani nationals and one Indonesian national were among the dead; two Yemeni coastguard/rescue personnel were killed in the second strike. Yemen's coastguard separately said it intercepted and destroyed a Houthi 'booby-trapped' drone boat that approached the Tihamah about three hours after the missile strikes. Al Jazeera reported this was the first shipping-related deaths linked to the Houthis since the US-Israel war on Iran began on 28 February 2026. The Houthi-run Saba agency claimed the target was a Saudi military-cargo vessel and did not name it; that claim is disputed by Yemen's government and is not independently verified. The International Maritime Organization's secretary-general condemned the attack. This is the same underlying event UKMTO first reported (previously recorded here as an unidentified vessel); this record has been updated with the vessel's identity and the confirmed double-tap sequence rather than duplicated. It is separate from the missile and drone attacks on al-Makha city and port on 9 August.

    5 sourcesDetails +
    Reported impact6 killed · 10 injured · double-tap missile strike

    UK Maritime Trade Operations classified Warning 110-26 as an attack after receiving a report that a stationary cargo vessel in the southern Red Sea near al-Makha (Mocha) had been hit by an unknown projectile; it did not name the vessel. Yemeni and international reporting subsequently identified the ship as the Tihamah, a 63-metre, Tanzanian-flagged, Egyptian-owned multipurpose vessel built in 2024 and licensed to carry passengers and commercial goods between Aden, Djibouti, Somalia and Socotra; it was en route to Mokha port with 11 crew (Pakistani and Indonesian nationals) when it was hit. Yemen's Transport Ministry said Houthi forces fired three ballistic missiles at the ship in a first strike that caused a fire, significant damage and an initial reported toll of four dead. As government coastguard and armed-forces personnel evacuated the dead and wounded roughly three hours later, the Houthis fired an additional ballistic missile at the rescue site, killing at least two more people, including two Yemeni rescuers (one named by officials as Abkar Muhammad Mahmoud), for a combined toll of six killed and ten wounded (seven of them crew). Yemen's Transport Ministry and Pakistan's Deputy Prime Minister and Foreign Minister Ishaq Dar both said three Pakistani nationals and one Indonesian national were among the dead; two Yemeni coastguard/rescue personnel were killed in the second strike. Yemen's coastguard separately said it intercepted and destroyed a Houthi 'booby-trapped' drone boat that approached the Tihamah about three hours after the missile strikes. Al Jazeera reported this was the first shipping-related deaths linked to the Houthis since the US-Israel war on Iran began on 28 February 2026. The Houthi-run Saba agency claimed the target was a Saudi military-cargo vessel and did not name it; that claim is disputed by Yemen's government and is not independently verified. The International Maritime Organization's secretary-general condemned the attack. This is the same underlying event UKMTO first reported (previously recorded here as an unidentified vessel); this record has been updated with the vessel's identity and the confirmed double-tap sequence rather than duplicated. It is separate from the missile and drone attacks on al-Makha city and port on 9 August.

    Why it appears here: this record was previously elevated for its scale, consequences, strategic importance or energy-security risk. Major status can be revised as evidence develops.

  24. Reported / attributedDrone / missile attack

    TANECO refinery, Nizhnekamsk — mass drone attack

    Nizhnekamsk, Tatarstan, Russia · Refinery · Russia

    Tatarstan authorities said Nizhnekamsk came under a massive drone attack targeting industrial and civilian facilities. They reported 13 people killed, including a child, and at least 75 wounded across the city; nine of the deaths were reported at a hostel. Associated Press described it as one of the deadliest attacks inside Russia during the full-scale war. An RT report updated earlier that day carried the same death toll but an earlier regional-government injury count of 48; the record retains the later figure of at least 75. Ukraine's General Staff said its forces struck Tatneft's TANECO oil refinery and started a fire. Russian officials did not identify the drones' specific targets, and the refinery strike and fire could not be independently verified in the reviewed reporting. The casualty figures apply to the wider Nizhnekamsk attack and must not be attributed specifically to the refinery site. This is a separate attack from the strikes on TANECO and other Nizhnekamsk facilities in June and July 2026.

    3 sourcesDetails +
    Reported impactMajor attack: 13 killed and at least 75 injured; casualties were city-wide, not refinery-specific

    Tatarstan authorities said Nizhnekamsk came under a massive drone attack targeting industrial and civilian facilities. They reported 13 people killed, including a child, and at least 75 wounded across the city; nine of the deaths were reported at a hostel. Associated Press described it as one of the deadliest attacks inside Russia during the full-scale war. An RT report updated earlier that day carried the same death toll but an earlier regional-government injury count of 48; the record retains the later figure of at least 75. Ukraine's General Staff said its forces struck Tatneft's TANECO oil refinery and started a fire. Russian officials did not identify the drones' specific targets, and the refinery strike and fire could not be independently verified in the reviewed reporting. The casualty figures apply to the wider Nizhnekamsk attack and must not be attributed specifically to the refinery site. This is a separate attack from the strikes on TANECO and other Nizhnekamsk facilities in June and July 2026.

    Why it appears here: this record was previously elevated for its scale, consequences, strategic importance or energy-security risk. Major status can be revised as evidence develops.

  25. DocumentedDrone / missile attack

    Al-Makha port — Houthi missile and drone attacks

    Al-Makha (Mocha), Taiz Governorate, Yemen · Port or tanker · Middle East

    Houthi forces attacked the government-held Red Sea port city of al-Makha twice within less than 24 hours using ballistic missiles and drones. Yemen's government-aligned armed forces said residential areas and port facilities were targeted and that air defences intercepted some drones. Yemen's Defence Ministry subsequently reported at least seven people killed — four troops and three civilians — and 30 injured; an earlier account had specified at least 15 civilian injuries. A Yemeni information-ministry official said the attacks severely damaged port buildings and piers as well as commercial goods and food supplies. The Houthis said they targeted weapons depots, military forces and Saudi troop concentrations. The record therefore distinguishes confirmed port damage and reported casualties from the opposing parties' disputed descriptions of the intended targets. Al-Makha is a principal port controlled by Yemen's internationally recognised government and has been renovated to handle shipping diverted from Houthi-held Hodeida.

    2 sourcesDetails +
    Reported impactAt least 7 killed and 30 injured; port buildings and piers severely damaged

    Houthi forces attacked the government-held Red Sea port city of al-Makha twice within less than 24 hours using ballistic missiles and drones. Yemen's government-aligned armed forces said residential areas and port facilities were targeted and that air defences intercepted some drones. Yemen's Defence Ministry subsequently reported at least seven people killed — four troops and three civilians — and 30 injured; an earlier account had specified at least 15 civilian injuries. A Yemeni information-ministry official said the attacks severely damaged port buildings and piers as well as commercial goods and food supplies. The Houthis said they targeted weapons depots, military forces and Saudi troop concentrations. The record therefore distinguishes confirmed port damage and reported casualties from the opposing parties' disputed descriptions of the intended targets. Al-Makha is a principal port controlled by Yemen's internationally recognised government and has been renovated to handle shipping diverted from Houthi-held Hodeida.

    Why it appears here: this record was previously elevated for its scale, consequences, strategic importance or energy-security risk. Major status can be revised as evidence develops.

  26. DocumentedDrone / missile attack

    ADNOC vessel — missile attack, no injuries

    Strait of Hormuz · Port or tanker · Middle East

    A vessel belonging to the Abu Dhabi National Oil Company (ADNOC) was targeted by a missile while transiting the Strait of Hormuz, the UAE's WAM state news agency initially reported without identifying an attacker. The UAE Ministry of Foreign Affairs subsequently accused Iran of the strike, describing it as an act of piracy by Iran's Revolutionary Guard Corps (IRGC) and demanding Tehran halt the attacks and reopen the strait fully and unconditionally; ADNOC confirmed one of its ships was targeted by a missile but did not detail damage or the vessel's exact location. No casualties were reported. The attack drew swift condemnation from Gulf and Arab governments: the Gulf Cooperation Council's secretary-general called it a 'dangerous and unacceptable escalation'; Qatar and Saudi Arabia condemned it and demanded the strait reopen without conditions, with Riyadh calling it a grave breach of international law and UN Security Council Resolution 2817; Jordan called it a flagrant violation of international law; and Bahrain's Ministry of Foreign Affairs said it violated international law, the UN Convention on the Law of the Sea and Resolution 2817, affirmed full solidarity with the UAE, and urged the UN Security Council to take decisive measures. It follows ADNOC's own statement the previous day (7 August) that 15 of its vessels had been attacked by missiles and drones since the war began, including three that week alone, resulting in one fatality and 20 injuries; this new attack is separate from and not yet included in that count.

    1 sourceDetails +

    A vessel belonging to the Abu Dhabi National Oil Company (ADNOC) was targeted by a missile while transiting the Strait of Hormuz, the UAE's WAM state news agency initially reported without identifying an attacker. The UAE Ministry of Foreign Affairs subsequently accused Iran of the strike, describing it as an act of piracy by Iran's Revolutionary Guard Corps (IRGC) and demanding Tehran halt the attacks and reopen the strait fully and unconditionally; ADNOC confirmed one of its ships was targeted by a missile but did not detail damage or the vessel's exact location. No casualties were reported. The attack drew swift condemnation from Gulf and Arab governments: the Gulf Cooperation Council's secretary-general called it a 'dangerous and unacceptable escalation'; Qatar and Saudi Arabia condemned it and demanded the strait reopen without conditions, with Riyadh calling it a grave breach of international law and UN Security Council Resolution 2817; Jordan called it a flagrant violation of international law; and Bahrain's Ministry of Foreign Affairs said it violated international law, the UN Convention on the Law of the Sea and Resolution 2817, affirmed full solidarity with the UAE, and urged the UN Security Council to take decisive measures. It follows ADNOC's own statement the previous day (7 August) that 15 of its vessels had been attacked by missiles and drones since the war began, including three that week alone, resulting in one fatality and 20 injuries; this new attack is separate from and not yet included in that count.

    Why it appears here: this record was previously elevated for its scale, consequences, strategic importance or energy-security risk. Major status can be revised as evidence develops.

  27. DocumentedDrone / missile attack

    Drone explodes near Trans-Balkan gas pipeline, Bulgaria

    Near Kardam, Dobrich Province, Bulgaria (Romanian border) · Pipeline · Europe

    An unidentified explosive-carrying drone entered Bulgarian airspace from Romania and detonated in a field about 100 metres inside Bulgaria and roughly 1,000 metres from a compressor station on the Trans-Balkan gas pipeline near the former Kardam border checkpoint. Bulgarian Prime Minister Rumen Radev said Romanian border police heard the drone before a Bulgarian border patrol heard the explosion; neither country's systems detected it in flight. No casualties or damage to buildings, the pipeline or other infrastructure were reported. Bulgaria's defence ministry said preliminary wreckage analysis indicated a Maya-type decoy drone used by Ukrainian forces and assessed the incident as probably accidental. Ukraine said it was investigating but denied deliberately targeting Bulgaria. Radev ordered counter-drone capabilities moved from the Turkish border to the Romanian frontier, while Bulgaria opened an investigation into the aircraft's origin and flight. The pipeline forms part of a regional gas corridor linking networks in southeastern and central Europe.

    2 sourcesDetails +

    An unidentified explosive-carrying drone entered Bulgarian airspace from Romania and detonated in a field about 100 metres inside Bulgaria and roughly 1,000 metres from a compressor station on the Trans-Balkan gas pipeline near the former Kardam border checkpoint. Bulgarian Prime Minister Rumen Radev said Romanian border police heard the drone before a Bulgarian border patrol heard the explosion; neither country's systems detected it in flight. No casualties or damage to buildings, the pipeline or other infrastructure were reported. Bulgaria's defence ministry said preliminary wreckage analysis indicated a Maya-type decoy drone used by Ukrainian forces and assessed the incident as probably accidental. Ukraine said it was investigating but denied deliberately targeting Bulgaria. Radev ordered counter-drone capabilities moved from the Turkish border to the Romanian frontier, while Bulgaria opened an investigation into the aircraft's origin and flight. The pipeline forms part of a regional gas corridor linking networks in southeastern and central Europe.

    Why it appears here: this record was previously elevated for its scale, consequences, strategic importance or energy-security risk. Major status can be revised as evidence develops.

  28. DocumentedDrone / missile attack

    Leipzig/Halle Airport — explosive-drone attack attempt

    Leipzig/Halle Airport, Saxony, Germany · Logistics Hub · Europe

    An airport employee found a drone carrying professional explosive and a detonator inside Leipzig/Halle Airport's secured cargo area near the southern runway during the night of 4–5 August. Both runways were temporarily closed and flights were diverted while specialists made the device safe. Germany's federal prosecutor said there were sufficient factual indications that an explosion was intended and that a cargo aircraft forced to go around collided in the wider airport area with an object believed to be a second drone. Investigators later recovered further drone material and explosive evidence near the airport. On 1 September, the German government formally attributed the attempted hybrid attack to Russia, citing the device configuration, components, explosive and detonator as matching patterns known from other Russian operations; the underlying intelligence was not published in full. Russia denied involvement and President Vladimir Putin described the event as a false flag. A commentary republished by ZeroHedge advances the same false-flag interpretation, arguing motive and implausibility, but supplies no independently verifiable evidence that German or Ukrainian actors staged the devices. It is retained as a labelled dissenting analysis, not as a competing factual finding or a change to the record's attribution status.

    4 sourcesDetails +
    Reported impactBoth runways were temporarily closed and flights were diverted; no lasting airport shutdown or energy-production impact was reported

    An airport employee found a drone carrying professional explosive and a detonator inside Leipzig/Halle Airport's secured cargo area near the southern runway during the night of 4–5 August. Both runways were temporarily closed and flights were diverted while specialists made the device safe. Germany's federal prosecutor said there were sufficient factual indications that an explosion was intended and that a cargo aircraft forced to go around collided in the wider airport area with an object believed to be a second drone. Investigators later recovered further drone material and explosive evidence near the airport. On 1 September, the German government formally attributed the attempted hybrid attack to Russia, citing the device configuration, components, explosive and detonator as matching patterns known from other Russian operations; the underlying intelligence was not published in full. Russia denied involvement and President Vladimir Putin described the event as a false flag. A commentary republished by ZeroHedge advances the same false-flag interpretation, arguing motive and implausibility, but supplies no independently verifiable evidence that German or Ukrainian actors staged the devices. It is retained as a labelled dissenting analysis, not as a competing factual finding or a change to the record's attribution status.

    Why it appears here: this record was previously elevated for its scale, consequences, strategic importance or energy-security risk. Major status can be revised as evidence develops.

  29. DocumentedShipping disruption

    Unidentified vessel — seized at anchor and taken toward Iranian waters

    38 NM northeast of Fujairah, United Arab Emirates · Port or tanker · Middle East

    The company security officer reported that an unidentified vessel was taken by unauthorised personnel while at anchor approximately 38 nautical miles northeast of Fujairah and was proceeding toward Iranian territorial waters. UKMTO continued to investigate and did not identify the boarding party, report casualties or damage, or attribute responsibility. A later JMIC incident table described the vessel type as fishery research and continued to withhold its name. The identifier #28082035 appears in some web listings for this record, but the official UKMTO warning number is 057-26 and the agency classified it as Suspicious Activity rather than Attack. The marker position is approximate, calculated from the reported distance and direction from Fujairah.

    1 sourceDetails +
    Reported impactUKMTO 057-26 · vessel identity withheld

    The company security officer reported that an unidentified vessel was taken by unauthorised personnel while at anchor approximately 38 nautical miles northeast of Fujairah and was proceeding toward Iranian territorial waters. UKMTO continued to investigate and did not identify the boarding party, report casualties or damage, or attribute responsibility. A later JMIC incident table described the vessel type as fishery research and continued to withhold its name. The identifier #28082035 appears in some web listings for this record, but the official UKMTO warning number is 057-26 and the agency classified it as Suspicious Activity rather than Attack. The marker position is approximate, calculated from the reported distance and direction from Fujairah.

    Why it appears here: this record was previously elevated for its scale, consequences, strategic importance or energy-security risk. Major status can be revised as evidence develops.

  30. DocumentedDrone / missile attack

    Al Taweelah industrial site — attack and emergency shutdown

    Abu Dhabi, United Arab Emirates · Power Grid · Middle East

    Emirates Global Aluminum said Iranian missile and drone attacks caused significant damage at its Al Taweelah site in Khalifa Economic Zone Abu Dhabi. The entire site was evacuated and all listed facilities—including the captive power plant and alumina refinery—entered emergency shutdown. EGA said some alumina-refinery and recycling production might restart earlier, while complete restoration of primary aluminum production could take up to 12 months. The 100% figure describes the confirmed initial site-wide shutdown, not permanent capacity loss. The marker is placed at the Al Taweelah complex.

    1 sourceDetails +
    Reported impactSite-wide emergency shutdown; complete restoration of primary aluminum production initially estimated at up to 12 months

    Emirates Global Aluminum said Iranian missile and drone attacks caused significant damage at its Al Taweelah site in Khalifa Economic Zone Abu Dhabi. The entire site was evacuated and all listed facilities—including the captive power plant and alumina refinery—entered emergency shutdown. EGA said some alumina-refinery and recycling production might restart earlier, while complete restoration of primary aluminum production could take up to 12 months. The 100% figure describes the confirmed initial site-wide shutdown, not permanent capacity loss. The marker is placed at the Al Taweelah complex.

    Why it appears here: this record was previously elevated for its scale, consequences, strategic importance or energy-security risk. Major status can be revised as evidence develops.

  31. DocumentedDrone / missile attack

    Port Shuaiba, Kuwait — Iranian drone strike kills 6 U.S. soldiers, single deadliest incident of the war

    Port Shuaiba, Kuwait · Port or tanker · Middle East

    An Iranian one-way attack drone struck a triple-wide trailer serving as a makeshift U.S. tactical operations center at Port Shuaiba, Kuwait, around 9am on 1 March 2026, flying at low altitude and slow speed to evade air defenses before hitting the trailer's roof directly, destroying the structure and starting a fire. Six U.S. Army Reserve soldiers of the 103rd Expeditionary Sustainment Command were killed and more than 30 others were wounded with traumatic brain injuries, shrapnel wounds and burns. Multiple outlets, including CBS News, the Washington Post and CNN, reported that the operations center lacked counter-rocket-artillery-mortar and drone-defeat systems, relying only on T-walls designed against ground assaults rather than airborne threats, and that detection systems failed to sound a warning before impact; reporting said this violated Army counter-drone doctrine calling for increased overhead protection. The Pentagon defended the facility's setup, while soldiers who survived the attack later told CBS News their unit had been unprepared to defend itself, disputing aspects of the official account. This was the single deadliest incident for U.S. forces of the Iran war according to the Defense Department inspector general's own casualty accounting.

    3 sourcesDetails +
    Reported impact6 US soldiers killed · 30+ wounded · deadliest single incident of the war for US forces · force-protection failures alleged

    An Iranian one-way attack drone struck a triple-wide trailer serving as a makeshift U.S. tactical operations center at Port Shuaiba, Kuwait, around 9am on 1 March 2026, flying at low altitude and slow speed to evade air defenses before hitting the trailer's roof directly, destroying the structure and starting a fire. Six U.S. Army Reserve soldiers of the 103rd Expeditionary Sustainment Command were killed and more than 30 others were wounded with traumatic brain injuries, shrapnel wounds and burns. Multiple outlets, including CBS News, the Washington Post and CNN, reported that the operations center lacked counter-rocket-artillery-mortar and drone-defeat systems, relying only on T-walls designed against ground assaults rather than airborne threats, and that detection systems failed to sound a warning before impact; reporting said this violated Army counter-drone doctrine calling for increased overhead protection. The Pentagon defended the facility's setup, while soldiers who survived the attack later told CBS News their unit had been unprepared to defend itself, disputing aspects of the official account. This was the single deadliest incident for U.S. forces of the Iran war according to the Defense Department inspector general's own casualty accounting.

    Why it appears here: this record was previously elevated for its scale, consequences, strategic importance or energy-security risk. Major status can be revised as evidence develops.

  32. DocumentedSabotage

    Berlin-Lichterfelde power-cable bridge — Vulkangruppe-claimed arson

    Berlin, Germany · Power Grid · Europe

    Unknown perpetrators set fire to a cable bridge over the Teltow Canal at the Lichterfelde combined heat-and-power plant in southwest Berlin, destroying five 110kV high-voltage and ten 10kV medium-voltage cables feeding substations serving Dahlem, Schlachtensee, Lichterfelde, Nikolassee, Wannsee and Zehlendorf. The outage cut power (and, in freezing winter weather, heating) to more than 40,000 households and over 2,000 businesses — roughly 100,000 people — including hospitals, nursing homes, schools and daycare centres; mobile and internet infrastructure was also disrupted. Berlin's Senate declared a major-damage situation and requested Bundeswehr logistical assistance to fuel emergency generators. Power was not fully restored until 7 January, making it, per German reporting, the longest lasting power outage in the city since 1945. A letter of responsibility published on Indymedia by a group calling itself Vulkangruppe described the act as "oriented towards the common good" and a protest against fossil-fuel power generation; investigators considered it likely genuine, though the federal government stopped short of confirming the motive, and rival or disavowing letters muddied the claim. Mayor Kai Wegner called the attack terrorism; the case was transferred to the Federal Prosecutor General over suspected terrorist-organisation membership, and a €1 million reward was later offered for information leading to identification of the perpetrators.

    1 sourceDetails +

    Unknown perpetrators set fire to a cable bridge over the Teltow Canal at the Lichterfelde combined heat-and-power plant in southwest Berlin, destroying five 110kV high-voltage and ten 10kV medium-voltage cables feeding substations serving Dahlem, Schlachtensee, Lichterfelde, Nikolassee, Wannsee and Zehlendorf. The outage cut power (and, in freezing winter weather, heating) to more than 40,000 households and over 2,000 businesses — roughly 100,000 people — including hospitals, nursing homes, schools and daycare centres; mobile and internet infrastructure was also disrupted. Berlin's Senate declared a major-damage situation and requested Bundeswehr logistical assistance to fuel emergency generators. Power was not fully restored until 7 January, making it, per German reporting, the longest lasting power outage in the city since 1945. A letter of responsibility published on Indymedia by a group calling itself Vulkangruppe described the act as "oriented towards the common good" and a protest against fossil-fuel power generation; investigators considered it likely genuine, though the federal government stopped short of confirming the motive, and rival or disavowing letters muddied the claim. Mayor Kai Wegner called the attack terrorism; the case was transferred to the Federal Prosecutor General over suspected terrorist-organisation membership, and a €1 million reward was later offered for information leading to identification of the perpetrators.

    Why it appears here: this record was previously elevated for its scale, consequences, strategic importance or energy-security risk. Major status can be revised as evidence develops.

2025

1 incident
  1. DocumentedDrone / missile attack

    Operation Spiderweb — covert drone assault on 4 Russian bomber bases

    Olenya, Belaya, Ivanovo Severny and Dyagilevo airbases, Russia · Airport / Air Base · Russia

    Ukraine's Security Service (SBU) carried out a coordinated covert drone assault on four Russian strategic-bomber bases on 1 June 2025 — Olenya (Murmansk Oblast), Belaya (Irkutsk Oblast, 4,300km from Ukraine), Ivanovo Severny (Ivanovo Oblast) and Dyagilevo (Ryazan Oblast) — with a fifth attempt at Ukrainka (Amur Oblast) failing when the delivery truck caught fire early. Over 100 Ukrainian-made Osa quadcopter drones were smuggled into Russia hidden under the raised roofs of shipping containers loaded onto flatbed trucks, driven unwittingly by Russian drivers and launched remotely by phone command once in position; a Ukrainian national running a freight business allegedly coordinated the scheme, and four detained drivers face terrorism charges, with a fifth killed when his truck exploded. Independent OSINT analysis of satellite imagery confirmed roughly 10-11 Tu-95 and Tu-22M3 strategic bombers destroyed and two A-50 airborne early-warning aircraft targeted at Ivanovo Severny, against Ukraine's own claim of 41 aircraft hit and a US official estimate of about 20 hit with 10 destroyed. Russia's Defense Ministry confirmed damage at Olenya and Belaya; Financial Times reporting, drawing on satellite analysis, put the damaged and destroyed aircraft at roughly 20% of Russia's operational long-range aviation fleet, most of it types out of production since 1991 and effectively irreplaceable. Ukrainian officials estimated $7 billion in damage inflicted using drones costing about $2,000 each. No Russian deaths were reported in the admitted strikes. This record adds one of the single most significant airbase-strike events of the war to the site's coverage, corroborated by BBC, Reuters, Financial Times and Washington Post satellite-imagery analysis.

    1 sourceDetails +
    Reported impact100+ drones smuggled into Russia in truck-mounted containers hit 4 bases across 5 time zones · OSINT confirms roughly 10-11 Tu-95/Tu-22M3 bombers destroyed · Ukraine claims $7 billion in damage from $2,000 drones

    Ukraine's Security Service (SBU) carried out a coordinated covert drone assault on four Russian strategic-bomber bases on 1 June 2025 — Olenya (Murmansk Oblast), Belaya (Irkutsk Oblast, 4,300km from Ukraine), Ivanovo Severny (Ivanovo Oblast) and Dyagilevo (Ryazan Oblast) — with a fifth attempt at Ukrainka (Amur Oblast) failing when the delivery truck caught fire early. Over 100 Ukrainian-made Osa quadcopter drones were smuggled into Russia hidden under the raised roofs of shipping containers loaded onto flatbed trucks, driven unwittingly by Russian drivers and launched remotely by phone command once in position; a Ukrainian national running a freight business allegedly coordinated the scheme, and four detained drivers face terrorism charges, with a fifth killed when his truck exploded. Independent OSINT analysis of satellite imagery confirmed roughly 10-11 Tu-95 and Tu-22M3 strategic bombers destroyed and two A-50 airborne early-warning aircraft targeted at Ivanovo Severny, against Ukraine's own claim of 41 aircraft hit and a US official estimate of about 20 hit with 10 destroyed. Russia's Defense Ministry confirmed damage at Olenya and Belaya; Financial Times reporting, drawing on satellite analysis, put the damaged and destroyed aircraft at roughly 20% of Russia's operational long-range aviation fleet, most of it types out of production since 1991 and effectively irreplaceable. Ukrainian officials estimated $7 billion in damage inflicted using drones costing about $2,000 each. No Russian deaths were reported in the admitted strikes. This record adds one of the single most significant airbase-strike events of the war to the site's coverage, corroborated by BBC, Reuters, Financial Times and Washington Post satellite-imagery analysis.

    Why it appears here: this record was previously elevated for its scale, consequences, strategic importance or energy-security risk. Major status can be revised as evidence develops.

2024

1 incident
  1. Reported / attributedSabotage

    Oleksiivka rail sabotage and HIMARS strike destroys Russian fuel train

    Russian-occupied Bilmak district, Zaporizhzhia Oblast, Ukraine · Railway · Europe

    Ukrainian sources said a joint SBU, HUR, Special Operations Forces and Tavria group operation destroyed a Russian train hauling 40 fuel tankers from Crimea toward occupied territory near Oleksiivka in the Bilmak district. According to the account, the SBU first sabotaged the track, derailing the train and igniting some tankers, after which HIMARS rockets struck the locomotive and outer cars, destroying it along with the 40 tankers. No casualties were reported. This is a Ukrainian military-intelligence claim; independent confirmation of the full 40-tanker toll has not been established.

    1 sourceDetails +

    Ukrainian sources said a joint SBU, HUR, Special Operations Forces and Tavria group operation destroyed a Russian train hauling 40 fuel tankers from Crimea toward occupied territory near Oleksiivka in the Bilmak district. According to the account, the SBU first sabotaged the track, derailing the train and igniting some tankers, after which HIMARS rockets struck the locomotive and outer cars, destroying it along with the 40 tankers. No casualties were reported. This is a Ukrainian military-intelligence claim; independent confirmation of the full 40-tanker toll has not been established.

    Why it appears here: this record was previously elevated for its scale, consequences, strategic importance or energy-security risk. Major status can be revised as evidence develops.

2020

1 incident
  1. DocumentedDrone / missile attack

    Camp Taji airbase — rocket attacks kill 3 coalition troops, prompt US-UK retaliatory strikes

    Baghdad Governorate, Iraq · Airport / Air Base · Middle East

    Iraq's Camp Taji, a base north of Baghdad hosting coalition and U.S. forces, was struck by roughly 29 Iranian-made 107mm rockets on 11 March 2020, killing two U.S. service members and one British Royal Army Medical Corps soldier attached to the Irish Guards, and wounding at least 14 coalition personnel, including a Polish soldier, five of them critically. A second barrage of more than 25 Chinese-made Type 63 rockets struck the same compound and adjacent Iraqi air-defense facilities on 14 March, wounding three more coalition soldiers and two Iraqi soldiers without further deaths. U.S. and Iraqi officials widely blamed the Iranian-backed Kata'ib Hezbollah militia, while a little-known group calling itself the League of Revolutionaries separately claimed responsibility, an attribution the reviewed reporting treats as unconfirmed. In retaliation, U.S. warplanes struck weapons depots and missile facilities near Al-Bukamal, Syria, and in Iraq's Al-Anbar province on 11 March, and U.S. and British aircraft struck Kata'ib Hezbollah and Popular Mobilization Forces sites in Karbala and Babylon on 13 March, reportedly killing several Iraqi soldiers, police and a civilian in the process; Iraq's government condemned the retaliatory strikes and summoned the U.S. and U.K. ambassadors in protest.

    1 sourceDetails +
    Reported impact3 killed (2 US, 1 UK) · 18+ wounded · triggered US-UK airstrikes on Kata'ib Hezbollah sites

    Iraq's Camp Taji, a base north of Baghdad hosting coalition and U.S. forces, was struck by roughly 29 Iranian-made 107mm rockets on 11 March 2020, killing two U.S. service members and one British Royal Army Medical Corps soldier attached to the Irish Guards, and wounding at least 14 coalition personnel, including a Polish soldier, five of them critically. A second barrage of more than 25 Chinese-made Type 63 rockets struck the same compound and adjacent Iraqi air-defense facilities on 14 March, wounding three more coalition soldiers and two Iraqi soldiers without further deaths. U.S. and Iraqi officials widely blamed the Iranian-backed Kata'ib Hezbollah militia, while a little-known group calling itself the League of Revolutionaries separately claimed responsibility, an attribution the reviewed reporting treats as unconfirmed. In retaliation, U.S. warplanes struck weapons depots and missile facilities near Al-Bukamal, Syria, and in Iraq's Al-Anbar province on 11 March, and U.S. and British aircraft struck Kata'ib Hezbollah and Popular Mobilization Forces sites in Karbala and Babylon on 13 March, reportedly killing several Iraqi soldiers, police and a civilian in the process; Iraq's government condemned the retaliatory strikes and summoned the U.S. and U.K. ambassadors in protest.

    Why it appears here: this record was previously elevated for its scale, consequences, strategic importance or energy-security risk. Major status can be revised as evidence develops.

2019

1 incident
  1. DocumentedDrone / missile attack

    K-1 Air Base, Kirkuk — rocket attack that triggered the Soleimani-killing chain of events

    Kirkuk Governorate, Iraq · Airport / Air Base · Middle East

    A rocket barrage struck K-1 Air Base in Iraq's Kirkuk Governorate, which hosted Operation Inherent Resolve personnel, on the evening of 27 December 2019, with at least one rocket hitting a munitions storage facility and causing a significant secondary explosion. The attack killed U.S. civilian contractor and linguist Nawres Waleed Hamid and wounded four U.S. service members and two Iraqi security personnel. The United States attributed the attack to the Iranian-backed Kata'ib Hezbollah militia based on undisclosed intelligence and intercepted communications; the group denied responsibility, and Iraqi officials later suggested the Islamic State could have been responsible given the area's Sunni-majority population and known IS activity, an attribution dispute not resolved in the reviewed reporting. The attack set off a rapid escalation chain recorded in detail elsewhere on this site: US retaliatory airstrikes killed roughly 25 Kata'ib Hezbollah fighters at facilities in Iraq and Syria, prompting militia-linked protesters to storm the US Embassy compound in Baghdad, which in turn preceded the 3 January 2020 US strike near Baghdad International Airport that killed Iranian Quds Force commander Qasem Soleimani and Popular Mobilization Forces commander Abu Mahdi al-Muhandis — the event that directly triggered Iran's 8 January ballistic-missile retaliation against Al-Asad airbase and Erbil International Airport, both recorded separately on this site.

    2 sourcesDetails +
    Reported impact1 US contractor killed · triggered US strikes on Kata'ib Hezbollah, then the Soleimani killing days later

    A rocket barrage struck K-1 Air Base in Iraq's Kirkuk Governorate, which hosted Operation Inherent Resolve personnel, on the evening of 27 December 2019, with at least one rocket hitting a munitions storage facility and causing a significant secondary explosion. The attack killed U.S. civilian contractor and linguist Nawres Waleed Hamid and wounded four U.S. service members and two Iraqi security personnel. The United States attributed the attack to the Iranian-backed Kata'ib Hezbollah militia based on undisclosed intelligence and intercepted communications; the group denied responsibility, and Iraqi officials later suggested the Islamic State could have been responsible given the area's Sunni-majority population and known IS activity, an attribution dispute not resolved in the reviewed reporting. The attack set off a rapid escalation chain recorded in detail elsewhere on this site: US retaliatory airstrikes killed roughly 25 Kata'ib Hezbollah fighters at facilities in Iraq and Syria, prompting militia-linked protesters to storm the US Embassy compound in Baghdad, which in turn preceded the 3 January 2020 US strike near Baghdad International Airport that killed Iranian Quds Force commander Qasem Soleimani and Popular Mobilization Forces commander Abu Mahdi al-Muhandis — the event that directly triggered Iran's 8 January ballistic-missile retaliation against Al-Asad airbase and Erbil International Airport, both recorded separately on this site.

    Why it appears here: this record was previously elevated for its scale, consequences, strategic importance or energy-security risk. Major status can be revised as evidence develops.