I sat down to write about the wedding. Then, while I was still drafting that paragraph, Iran's military announced it had just hit two more American-run bases in the Gulf, and the story I thought I was writing turned into a different, bigger one before I'd finished a cup of coffee. That's more or less how this war has worked for six months now — you start reporting on one tragedy and a second front opens before you can publish. Thursday was no exception, and it packed a full week's worth of escalation into about eighteen hours.
In Brief
- Iran's army says it hit two American-run air bases early Thursday, widening a six-month war less than 24 hours after a US missile strike on a wedding in southern Iran killed four people, wounded dozens more, and became the subject of a formal complaint asking the International Criminal Court to investigate.
- I sat down to write about the wedding.
- Then, while I was still drafting that paragraph, Iran's military announced it had just hit two more American-run bases in the Gulf, and the story I thought I was writing turned into a different, bigger one before I'd finished a cup of coffee.
Two bases, two countries, one predawn statement
Iran's army said Thursday morning that its forces had struck the Ahmad al-Jaber Air Base in Kuwait and the Al Minhad Air Base in the United Arab Emirates with a combination of missiles and drones, describing the operation as the 31st phase of a campaign it calls "Thunder." According to the statement, the strikes on al-Jaber hit satellite communications systems, equipment warehouses, and a hangar housing American fighter jets, damaging the communications equipment and the hangar itself. At Al Minhad, the army said it targeted radar systems and areas where US personnel and forces are based. The statement described al-Jaber as a key logistics and support hub for American air operations and surveillance in the region, and called Al Minhad an important center for air support and the movement of foreign troops.
Kuwait's General Staff confirmed its air defenses engaged incoming missiles and drones and said the country was facing what it called "ongoing Iranian aggression," with air-raid sirens sounding nationwide. Kuwait's Foreign Ministry condemned the attack as a violation of its sovereignty and said the country reserves the right to defend its territory under international law. Neither Kuwait nor the United Arab Emirates immediately disclosed whether any of the incoming fire got through, and the US military had not, as of Thursday afternoon, confirmed that any of its facilities were actually damaged. Iran, for its part, offered no evidence to support its claims, which is its normal practice after these operations — the details tend to arrive as an official statement, not as verifiable footage.
The wedding that keeps this war from being an abstraction
All of that happened against the backdrop of a story that, on its own, would already be the most important thing I've written about this conflict in weeks. On Tuesday night, at roughly 9:30pm local time, a missile struck a home in the town of Kuhestak, in Sirik county, Hormozgan province — a house where a fisherman's family had gathered to celebrate his daughter's wedding. The Iranian Red Crescent Society says at least four people were killed: two women and two children, ages four and sixteen. It says around 67 others were wounded, many of them also women and children, and has warned the death toll could still climb because some of the injured remain in critical condition. The Red Crescent published photos of children being treated in a hospital and footage of a building with its walls and windows blown outward, debris scattered across what had been, hours earlier, a celebration.
The location is not incidental to why this strike has landed so hard, even inside a war that has already produced plenty of civilian casualties. Kuhestak sits roughly 23 miles from Minab, where, on February 28 — the very first day of this war — a missile hit an elementary school in an incident the Pentagon has never fully explained. Six months later, in almost the same stretch of coastline, a wedding became the latest single event this conflict will be remembered by. Iran's Foreign Ministry spokesman, Esmaeil Baghaei, wrote on social media that the reality on the ground was "so horrifying that even American propaganda has never dared make the claim" the US was making, adding a line that's stuck with me since I read it: "Sirik is not a story. The civilians are real. The victims are real."
CENTCOM's public response, at least initially, was thin. A spokesman, Capt. Tim Hawkins, told reporters the command was "aware of the reports, which originated from Iranian state media," and added that the US military "never targets civilians, unlike the IRGC" — a statement that neither confirmed nor denied a strike occurred, and offered no detail about what military target might have justified hitting a residential address. By Wednesday, CENTCOM's tone had shifted from pointing at Iranian state media to saying it was "looking into" the circumstances, and a weapons expert who reviewed the available imagery for the Associated Press said the damage pattern was consistent with an American air-delivered guided munition. That's not a confirmation either, but it's a meaningfully different posture than a flat denial.
A court that neither government actually answers to
On Wednesday, the Iranian Red Crescent formally asked the International Criminal Court to open an investigation, arguing in its letter that the "civilian character of the location" and the presence of families at a wedding warrant "an independent, impartial, thorough, and effective investigation," and that the strike could meet the legal threshold for a war crime under the Rome Statute. It's worth being precise about what that filing can and can't do. Neither the United States nor Iran has ratified the Rome Statute, so the court has no automatic jurisdiction over either country, and it cannot compel Washington to cooperate with anything it decides — a UN Security Council referral could theoretically change that, but the US holds a veto over exactly that kind of referral. Human rights researchers have pointed out that Iran could still unlock the court's jurisdiction over its own territory by filing a separate declaration accepting it retroactively to the war's first day, which would put every strike since February under the same legal umbrella. Tehran hasn't done that yet. What the Red Crescent's letter accomplishes right now, realistically, is putting Kuhestak on the record, generating diplomatic pressure, and preserving evidence for a case that may or may not ever be heard — which is a smaller thing than justice, but not nothing.
The president says he likes his position "much better" now
Away from Sirik and the Gulf bases, President Trump spent this week talking about the war in the register he's used most of the summer — part scoreboard, part provocation. In a Truth Social post, he wrote that he wasn't trying to force Iran back to the negotiating table and "couldn't care less" if Tehran signs what he called a "worthless" agreement, adding: "I like our position now much better, with almost total control of the Hormuz Strait, and their economy totally collapsing. They are just playing out the inevitable." He closed by asking, again, "When are the Iranian people going to rise up and fight?" — a line he's repeated at several points since the war began, each time without any visible effect on the ground. Speaking later in the Oval Office, he added that the regime was "getting weaker and weaker by the day, and at some point they're not gonna be able to shoot so easily because I think the people aren't going to take it."
I want to flag the gap between that rhetoric and Thursday morning's news, because it's a wide one. A government that has "almost total control" of a waterway does not typically watch that same waterway's neighboring air bases get hit for the second and third time in a week, in two different countries. Iran's ability to keep reaching Jordan, Bahrain, Kuwait, and now the UAE with drones and missiles — regardless of how much of that materiel gets intercepted — is not the profile of a side that's finished fighting. Both things can be true: Iran's economy is genuinely under severe strain, and Iran is also, six months in, still capable of launching coordinated strikes across four countries in a single week.
What all of this costs somewhere that isn't the Gulf
The oil market, at least, isn't pretending any of this is settling down. Brent crude touched just above $97 a barrel on Thursday before easing slightly to trade near $96.20, and US crude was changing hands above $91 — both benchmarks up more than 7% for the week. US Energy Secretary Chris Wright told reporters this week that roughly 17 million barrels of oil transited the Strait of Hormuz on Monday alone, which the administration is citing as proof the strait remains functionally open despite the fighting. Tanker-tracking firms tell a slightly different story: actual crossings remain below their ten-day average, and war-risk insurance premiums for ships willing to make the trip have climbed to some of their highest levels of the entire war. Both of those figures can be accurate at once, and both matter — supply is getting through, but at a cost that keeps showing up anywhere fuel gets priced, gas pumps in the US included.
Six months in, that's the shape this war keeps taking: a strike, a retaliation, a body count somewhere that most of the world will read about for a day and move past, and a market reaction that outlasts the news cycle by weeks. Thursday added a new wrinkle — a formal international legal complaint — to a conflict that has mostly settled disputes with missiles instead of courtrooms. Whether that complaint goes anywhere is genuinely uncertain. That it was filed at all tells you something about how far this war has already gone.
BracksterNews
