On Tuesday, July 28, 2026, at 5:45 p.m. Eastern, U.S. Central Command said Iran’s Islamic Revolutionary Guard Corps launched multiple ballistic missiles from Iranian territory at U.S. forces in the Middle East. The missiles were aimed at facilities used by American troops in Jordan, including Muwaffaq Salti Air Base. CENTCOM reported that every missile was intercepted and that U.S. forces remained on high alert.
Hours later came the second half of the sequence. CENTCOM and the Saudi Armed Forces announced joint precision strikes in Iraq against what they called IRGC-directed militia logistics and weapons sites. The command said U.S. and Saudi fighter aircraft hit targets across eastern Iraq in response to more than 30 drone attacks over the previous 72 hours against U.S. forces and Saudi energy infrastructure. Those drone attacks, Washington said, failed. CENTCOM warned that further attacks would bring further response.
That is the official order of events: Iran fired; U.S. defenses stopped the missiles; the United States and Saudi Arabia then struck the proxy infrastructure they blamed for the preceding drone campaign.
The scale of militia activity earlier in the year is part of why Washington framed the night as more than a one-off exchange. CENTCOM itself said that from February through April 2026, Iran-aligned militias in Iraq made more than 600 attempted attacks on U.S. citizens and facilities. Independent reporting from that spring cited similar figures for attacks on U.S. diplomatic and military sites after the wider regional war began in late February. Those numbers describe a sustained campaign, not a handful of freelance incidents.
Saudi Arabia’s role was the other distinctive feature. Riyadh was not only intercepting drones aimed at its oil facilities; Saudi fighters flew with American aircraft against targets inside Iraq. The Saudi Defense Ministry presented the strikes as self-defense after two days of drone attacks launched from Iraqi territory, while saying it did not seek escalation. For Washington, the joint raid was evidence of a working coalition rather than a U.S.-only response. Iraq’s government denounced the strikes as a violation of sovereignty. The Popular Mobilization Forces said at least 20 of their members were killed and dozens wounded; some reports also cited Iranian advisers among the dead. Results on the U.S. and Saudi side were not described as American casualties from the Tuesday missile salvo.
The night also sat inside a larger diplomatic and military grind. A brief lull had followed weeks of fighting over the Strait of Hormuz and related shipping. Mediators were trying to pull both sides back toward talks even as Tehran kept pressing sanctions relief and Washington kept striking what it called IRGC-directed networks. The original commentary treated a prior Trump warning — that attacks on ships, bridges, or power plants would be answered — as the test Iran chose to run by firing ballistic missiles at U.S. forces instead. CENTCOM’s reply was narrower and operational: intercept first, then hit the logistics sites tied to the drone wave, then warn that the pattern would not be tolerated.
What the Tuesday sequence showed, stripped of campaign language, was a three-step policy in practice. Incoming ballistic missiles were stopped. Proxy launch-and-supply nodes in eastern Iraq were struck in coordination with Saudi Arabia. And the warning that followed was written as a military statement, not a speech: stop the attacks, or face another response. Whether that deters the next salvo is a separate question. The sequence itself is no longer in dispute.
0 commentaires:
Enregistrer un commentaire