Saturday, September 12, 2026

Two Months Ago, Saudi Arabia Told Washington It Didn't Need Help With the Houthis. This Week, MBS Called Trump Twice Asking for It.

 



In July, when Saudi Arabia asked Trump for political backing to strike Sanaa's airport after blocking an Iranian plane from landing there, Crown Prince Mohammed bin Salman made a point of telling Washington one specific thing: Saudi Arabia didn't need US military assistance to handle it. Trump gave his support anyway. Two months later, with the Houthis seizing the strategic port of Mokha and closing in on the final two islands controlling the Bab el-Mandeb Strait, MBS called Trump twice in a single day asking for exactly the help he'd previously said Riyadh didn't require. That reversal, according to sources who spoke to multiple outlets, is the real story behind this week's headlines.

What changed in between was a rapid, real battlefield collapse. The Houthis' advance along Yemen's Red Sea coast has moved fast enough that Yemen's own government confirmed the group now controls every island at the mouth of the strait, giving them functional command over one of the world's most important shipping chokepoints. Combine that with Iran's continued disruption of the Strait of Hormuz on the other side of the Arabian Peninsula, a corridor that used to carry roughly a fifth of the world's oil, and Saudi Arabia is suddenly facing a pincer: its usual eastern export route choked by Iran directly, its alternative western route through the Red Sea now threatened by Iran's own proxy force. Riyadh had actually been relying on the Red Sea path specifically because Hormuz was already compromised. Losing both simultaneously is a considerably worse outcome for Saudi oil exports than either problem alone.

Trump's answer, delivered across at least two phone calls Thursday, was a clear no on direct American military action, paired with a yes on everything short of it. According to CBS News and Axios, both citing sources familiar with the calls, the US will provide Saudi Arabia with intelligence and targeting support rather than putting American forces or aircraft into the fight directly. Adm. Bradley Cooper, CENTCOM's commander, was in Saudi Arabia the same day for coordination talks, which by itself signals how seriously the Pentagon is treating the request even while declining the most direct version of it. A senior administration official's public framing stuck to a now-familiar script: protecting freedom of navigation while "empowering our regional partners to take the lead" rather than fighting the Houthis for them.

There's an obvious domestic pressure sitting underneath Washington's caution here, and it's worth naming directly. The broader US-Iran war has now run seven months with no clear end point, oil prices have pushed toward $100 a barrel with some analysts warning of $120 if the fighting in both the Gulf and the Red Sea continues, and that's landed directly on gas prices heading into November's midterm elections, with Trump's own approval ratings reportedly at a record low as a result. Committing American forces to a third active front, on top of Iran and whatever comes next in Hormuz, is a considerably harder sell to voters already feeling the price impact of the current conflict than intelligence-sharing and targeting support is.

Whatever Washington eventually decides, the reversal itself, a crown prince who insisted in July he had this handled now personally calling the American president twice in one day two months later, tells you how much worse Saudi Arabia's own assessment of the situation has gotten in a short window. Smoke was separately reported over a key east-west Saudi oil pipeline this same week, though the source of that damage wasn't confirmed in the reporting. Between an unconfirmed pipeline incident, a lost strait, and an ally now explicitly asking for the help it previously declined, this looks less like a contained regional flare-up and more like a conflict that keeps finding new fronts faster than anyone involved seems able to close the old ones.

"Be Quiet, Small Man." That Insult From Elon Musk Might Be Why Poland Is Now Building Its Own Satellite Network.

 



"Be quiet, small man. You pay a tiny fraction of the cost." That's what Elon Musk posted at Poland's foreign minister earlier this year, after Radosław Sikorski suggested Warsaw might look for other suppliers if Starlink proved unreliable for Ukraine. Poland had, at that point, spent roughly $50 million a year covering Starlink subscriptions for Ukraine's military and civilian users, and provided half of the country's 42,000 terminals. Musk's response wasn't a policy dispute, it was contempt, aimed at a NATO ally's foreign minister over a service that Ukrainian officials themselves have said the front line depends on. Prime Minister Donald Tusk stepped in publicly without naming Musk directly: "True leadership means respect for partners and allies. Even for the smaller and weaker ones. Never arrogance."

That exchange is the emotional backdrop against which Tusk announced, at the MSPO defense show in Kielce on September 9, that Poland intends to build its own version of the network it's been paying to keep Ukraine connected to. "The culmination of the process that began today can and will be a Polish Starlink," he said, framing communications as the single thing that determines whether a modern military has anything at all. The Polish government has separately complained that new SpaceX usage rules effectively treat Poland as a second-class country, a grievance that's clearly still live regardless of how the specific technical dispute over those rules gets resolved.

What actually got signed this week is more modest than "Polish Starlink" suggests, and it's worth being precise about that gap. Finnish company ICEYE and Poland's state defense conglomerate PGZ signed a letter of intent, not a contract, to jointly develop a military satellite communications system, with the program timeline running 2026 to 2030. ICEYE is taking the harder technical half: designing the satellite architecture, building the space platforms, and running satellite operations. PGZ's job is organizing Poland's own industrial base, identifying which of its companies can actually contribute manufacturing capacity, expertise, and infrastructure to the effort. This is closer to laying the foundation for a Polish satellite communications capability than announcing a finished constellation.

The relationship between these two companies didn't start this week either. ICEYE already runs an ongoing program with PGZ supplying synthetic aperture radar satellites for Earth observation under something called MikroSAR, giving Poland's military a reconnaissance capability that isn't dependent on any foreign government's goodwill. This new satcom project is explicitly described as the first piece of a broader "military space capabilities toolkit" Warsaw plans to build out over the coming years, meaning the communications system is one module in a larger push rather than a standalone reaction to the Musk dispute alone.

Russia's own contribution to this story is worth a brief mention, mostly because of how it's being read rather than taken at face value. Moscow recently announced mass production of an electronic warfare system it claims can disrupt Starlink communications, timed suspiciously close to renewed debate over whether Ukrainian drones should be allowed to use Starlink beyond Ukraine's own borders, a use Musk himself said in late August he'd be open to allowing. Analysts at the Institute for the Study of War have read Russia's jamming-system announcement as part of a broader information campaign aimed at shaping American decisions on Ukraine's Starlink access, rather than a straightforward capability disclosure. Whether or not that system works as advertised, it adds one more reason for a country like Poland, already burned once by a billionaire's public contempt for its own foreign minister, to want a satellite network it doesn't have to ask anyone's permission to keep running.