Brent Tops $115 as Houthis Claim Strike on Saudi Refinery
Oil markets jolted higher Wednesday after Yemen’s Houthi movement claimed a ballistic missile hit Saudi Arabia’s Ras Tanura refinery, bringing the widening regional war to the doorstep of one of the world’s most important energy hubs.
The claim demands caution. Houthi military spokesperson Yahya Saree said the missile caused a fire at the complex on Tuesday, October 27. Saudi authorities did not confirm a strike on the refinery. The Associated Press said it could not independently verify the Houthi account, while Saudi officials reported that air defenses destroyed three ballistic missiles heading toward the kingdom’s eastern region.
That uncertainty did not calm traders. Brent crude rose 1.4 percent to $115.47 a barrel by 04:35 GMT Wednesday, while West Texas Intermediate climbed 1.4 percent to $101.33. The move reversed part of Tuesday’s nearly $2 drop and showed how quickly even an unverified battlefield claim can place a war premium back into every barrel.
A critical node, not just another refinery
Ras Tanura sits on Saudi Arabia’s Gulf coast, west of the Strait of Hormuz. Its refinery can process 550,000 barrels a day, making it the kingdom’s largest. The same sprawling complex includes a major crude-export terminal, connecting Saudi production to tankers bound for Asia and beyond.
That makes the site economically consequential even when physical damage remains unclear. The Wall Street Journal reported that Saudi Arabia said it contained a fire near its largest export terminal following an attack in the area. That report does not independently prove the Houthis’ “direct hit” claim, but it sharpens the central question: how close did the attack come to interrupting operations?
Saudi Arabia has not disclosed a production or export outage. There were no immediate independently verified reports of casualties at Ras Tanura. Those absences matter. A responsible account must distinguish a claimed strike, a reported nearby fire and a confirmed supply disruption. Only the first two have entered the public record.
The market is pricing vulnerability
The price spike reflects more than one missile. The Houthis have intensified attacks on Saudi targets as the US-Israeli war on Iran and Yemen’s conflict spread across the region. Saudi defenses also intercepted missiles over Riyadh on Tuesday, while debris damaged a building, a construction site and a vehicle, according to civil-defense authorities cited by AP.
For oil buyers, Ras Tanura represents concentration risk. A large share of Saudi exports moves through two outlets: Ras Tanura on the Gulf and Yanbu on the Red Sea. Both sit inside an expanding battlespace. A prolonged shutdown at either would force buyers to compete for alternative grades and routes; simultaneous pressure on both would test spare capacity and shipping insurance across the region.
ING commodity strategists said the market was pricing a “greater likelihood of re-escalation.” That assessment explains why crude rose even as diplomatic talks created brief hopes of de-escalation and US inventory estimates offered no clear shortage signal.
OPEC+ is expected to keep December production targets unchanged when it meets Sunday. Yet several core producers already pump below their quotas. A paper target cannot replace barrels lost to damaged infrastructure, closed shipping lanes or precautionary shutdowns.
What comes next
The immediate test is operational transparency. Saudi Aramco and the Saudi Energy Ministry should disclose whether the refinery, storage tanks, pipelines or marine terminal sustained damage and whether loadings continue on schedule. Satellite imagery and shipping data may eventually answer what official silence has not.
Until then, the clean conclusion is narrower than the loudest war claims but still serious: the Houthis say they reached Ras Tanura; Saudi Arabia confirms missiles approached the eastern region; oil traders believe the threat is credible enough to pay more. The attack’s precise impact remains contested. The vulnerability it exposed does not.
Comments