Global weekly brief — 4 October 2026
In several modules something physical moved this week while the system around it stayed where it was. Gulf crude left the region at its pre-war rate in September, but on state-company shuttles, transfers and US-facilitated passage rather than through a reopened market. Independent counts of other traffic stayed in single digits, and six tankers were struck in the strait in five days, by no one who claimed it. Taiwan received its first two new F-16s, which is delivery, not a fielded capability. Poland changed how its pilots may identify a target before engaging. It did so after Russian drones struck beside the Dorohusk crossing three times in September, close to NATO territory and never inside it, and by an announced military procedure with no published order. Syria's gas supply to its power stations was cut twice in three days, once with a cause claimed by the operator and once with none. Russia, for its part, answered the refinery campaign by acting on the evidence rather than the fuel: a decree of 28 September stops publication of refinery, export and customs data. In the same week its drones reached Kyiv's river crossings for the first time. The common thread is a reading of what changed the record. It is not a claim that these cases are connected. Reviewed and not elevated: the Caucasus, and the Sahel, whose brief leads on a correction of its own record.
Selected developments this week
Gulf oil left at its pre-war rate, through a strait that is still not commercially open
Kpler reported on 29 September that crude exports from the Gulf, excluding Iran, were at least 16.5 million barrels a day in September, the pre-war average. About 60 per cent (9.9 million) physically crossed the strait, mostly on shuttle tankers; 23 per cent loaded on the Gulf of Oman coast, mainly at Fujairah; and 17 per cent left through the Red Sea. Before the war 83 per cent crossed the strait. Kpler states its figures are minimum confirmed volumes. S&P Global counted 19 LNG cargoes through the strait in September, 13 Qatari and 6 Emirati, and Kpler counted 21. Both are the highest month of the war, against 15 in June and no visible Qatar-linked transit in August. Many carriers crossed with transponders off. The Joint Maritime Information Center recorded 113 US-facilitated transits in the four days to 30 September, while independent tracking of other cargo vessels showed single digits each way. Its 2025 baseline is about 138 a day. UKMTO and the trade press reported six tankers struck by unknown projectiles inside the strait. One was on 28 September, three on 29 September, one on 1 October (crew evacuated) and one on 2 October, that last resting on a security firm and trade press only. Security firms and the IMO's list named two Kuwait Oil Tanker Company VLCCs and three ADNOC- or Anglo-Eastern-managed tankers. No party claimed any of the strikes. Iran's Strait Authority said the ships targeted included vessels on its non-compliant list, which reached 82 and now carries warnings to charterers. No war-risk cover was found written, no Joint War Committee change was identified, and the Salalah ministerial had not reconvened.
Why it matters. Volume and access have separated. Crude is leaving the Gulf at the pre-war rate because the route was rebuilt around the strait's risk. State-company shuttles run short legs to transfer points outside it, under US facilitation, and the rest goes by the bypasses. That is what the independent count shows: almost nothing else moves. LNG is the cleaner test, because it has no bypass. It rose, but to about a fifth of pre-war. The strikes fell on exactly the cargo that makes up the recovery, national oil company tankers, and the week's six are the most in the strait in any window this module has recorded since August. Commercial access did not move, and legal access hardened as the Strait Authority extended its pressure to service providers. The strait is used more and is still not open, and nothing here says when a market will return to it. The item does not establish who fired: no party claimed a strike, and no authority attributed one.
- Update 101 to JMIC Advisory Note: Regional Tension — Impact on Maritime Security
- Explainer: How Mideast Gulf crude exports returned to pre-war levels
- LNG shipments through Strait of Hormuz hit post-war high in September
- Defying conflict, Qatar-linked LNG tankers return to the Strait of Hormuz
- Four vessels struck in Hormuz in 24 hours
- Three Oil Tankers Come Under Fire in Strait of Hormuz
- Two More Tankers in Hormuz Report Strikes, Bringing Total to Six in a Week
Read this item in the Iran–Gulf brief Full Iran–Gulf weekly brief
On 28 September President Putin signed a decree restricting publication of refinery-level processing volumes and output, refined-product export slates, quantities and prices, sellers, buyers and intermediaries, transport routes, terminals and storage, customs data and exchange volumes for gasoline and diesel, unless the company involved discloses them; it cites "unfriendly acts" by the United States and states aligned with it. On 30 September the government extended the ban on diesel, marine-fuel and gasoil exports by producers, due to lapse that day, to 31 October, citing harvest-season demand; the non-producer diesel ban and the full gasoline ban run to 31 January 2027 and the jet-fuel ban to 30 November. On 2 October Deputy Prime Minister Alexander Novak said the diesel market was balanced, that a partial reopening of exports would be considered if output exceeded demand, and that protection measures had shortened restoration after strikes. Ukraine's General Staff confirmed a strike on the Lukoil refinery at Volgograd on the night of 1–2 October; the Volgograd governor confirmed a mass drone attack on industrial infrastructure. A Samara target struck the same night was an oil distribution station, not a refinery.
Why it matters. Every earlier Russian act on the refining constraint — the bans, the eased standards, the imported cargoes — acted on the fuel. This one acts on the evidence, and it removes exactly the Russian-side figures against which the module reads the campaign's effect: refinery output and export detail now reach the record only through company disclosure and independent tracking. The extension, read beside it, shows the constraint still managed rather than relieved. Novak's account of a balanced market and faster repair is the first official statement in the absorption direction, and it comes from the party with every reason to make it; it is recorded as his. The external channel is product exports, which the bans have held back since August — exposure, not a measured effect. The refinery series slowed to one marker strike this week, against five the week before.
- Russian presidential decree tightens control over info, stats in fuel and energy sector
- Putin restricts publication of Russian refinery, energy data amid Ukrainian strikes
- Russia extends diesel export ban for producers to Oct 31
- Russia Will Consider Partial Lifting of Diesel Export Ban in Case of Overproduction, Novak Says
- Ukrainian forces strike oil facilities in Russia's Volgograd, Samara regions, General Staff says
- Ukrainian Drones Target Volgograd, Krasnodar Industrial Sites
Read this item in the Ukraine–Russia brief Full Ukraine–Russia weekly brief
Poland announced it would drop visual identification before engaging, after drones struck beside the Dorohusk crossing without entering its airspace
On the evening of 28 September a Russian jet-powered drone struck on the Ukrainian side of the Yahodyn–Dorohusk border crossing. Poland's Operational Command said a Russian drone had again come down near the crossing. Poland's defence minister said it hit about two kilometres from the crossing, inside Ukraine, and that there was no violation of Polish airspace. Ukrainian regional authorities said the blast damaged a checkpoint building at the terminal entrance; Ukraine's border guard said the crossing itself was undamaged. Polish fighters flew in Polish airspace, ground-based air defence was brought to readiness, Lublin and Rzeszów airports suspended operations, and an air-attack alert for Lublin province was issued and withdrawn. Drones had also struck near the same crossing, on Ukrainian territory, on 13 and 17 September. Also on 28 September, Deputy Defence Minister Cezary Tomczyk announced that the peacetime requirement to identify a target visually before engaging it would be replaced by positive identification from radar and other sensors, flight parameters, the absence of a friend-or-foe reply and data provided by Ukraine. The decision rests with the pilot or the Operational Commander. The defence minister was reported on 30 September and 1 October as saying the procedures were ready and would apply from 1 October. They are set at military level; no order has been published and no law was changed.
Why it matters. Of everything near the flank this week, this is the only change to a standing response, and it is national, not NATO's. It changes how quickly a Polish decision to engage can be taken, not what Poland may engage, and it adds to rather than alters the alliance air defence mission that replaced Baltic Air Policing in August. The strikes are recorded as what they were: Russian action close to NATO territory. None was an entry into NATO airspace, and none enters this module's airspace series. What the change does not establish is any engagement under the new rule. A published instrument, or a first engagement under the rule, is the evidence that would show how it works in practice.
- Poland to ease rules for shooting down drones, missiles entering from Russia
- Poland changes rules of engagement for firing on foreign aircraft amid growing Russia threat
- Poland implements new response rules for air defence amid Russian attacks on Ukraine from 1 October
- Russian drone strikes near Yahodyn border crossing with Poland
- Alert RCB na Lubelszczyźnie. DORSZ: dron rozbił się niedaleko polskiej granicy, po stronie Ukrainy
- Poland sounds air attack alert over Russian drone
Read this item in the NATO Eastern Flank brief Full NATO Eastern Flank weekly brief
The first new F-16s reached Taiwan: a case at delivery, not yet a capability
On 2 October the first two single-seat F-16 Block 70 aircraft of the 66 Taiwan ordered in 2019 landed at an air base in Taitung. They had left the United States on 17 August and staged through Hawaii and Guam. The Air Force said it would carry out acceptance and conversion training on plan, and that later aircraft would return against milestones set with the US programme office. Its release describes 63 aircraft on the US production line, some of them at the delivery stage. President Lai Ching-te called the delivery an important milestone for air defence. The defence minister said more than two aircraft would be delivered this year. Separately, 21 Democratic senators led by Jeanne Shaheen, as reported on 2 October, called for congressionally approved assistance to Taiwan to be delivered immediately. No US approval, notification or refusal of the $14bn package was reported in the window.
Why it matters. This module counts a case milestone only when a government reports it. The 17 August departure rested on unnamed sources, and the arrival rests on the Air Force's own release. That makes it the second case on the record to change state in the arms question's life, after the Abrams tanks completed in April, and the first under the fighter sale, which had been due to complete by the end of 2026. It establishes delivery and nothing beyond it. The aircraft still have to be accepted, crews trained on them and the type integrated into a wing, and no schedule for the other aircraft has been published. It also says nothing about the package now under review. That is a different case at an earlier stage, and the senators' statement adds pressure without a decision. The observables now are the next delivery and any statement of when the first aircraft enter service.
- 空軍司令部發布新聞稿,針對「首批兩架F-16 BLK 70戰機返國」乙情說明 (Air Force Command press release on the return of the first two F-16 Block 70 aircraft)
- Taiwan receives first 2 F-16V Block 70s
- Taiwan receives first 2 F-16V Block 70s
- US senators urge speedy arms delivery to Taiwan
Read this item in the Taiwan Strait brief Full Taiwan Strait weekly brief
Gas to Syria's power stations was cut twice in three days, and the recurrence the records watched for has happened
Late on 28 September an explosion at a sectional valve on the gas line between al-Shola and Deir ez-Zor started a fire and stopped gas flowing from the Jbeissa plant to power stations. The state news agency, citing the Syrian Petroleum Company, called it sabotage; the company's gas-sector head, Hisham al-Saleh, said the supply to generation had stopped completely, and crews isolated the line on both sides of the fire. A local oil official told The National it appeared to be a theft gone wrong. No group has claimed it and no plant or megawatt figure was given. On the evening of 30 September a separate explosion on a gas line near Haran al-Awamid, east of Damascus, cut gas to the Deir Ali, al-Nasiriyah and Tishreen stations and took all three offline, the Syrian Electricity Company said. The energy ministry said the cause was unclear and did not link the two; one outlet quoted it as saying Daraa lost about 60 MW and imposed temporary cuts. No restoration of either line had been announced by 4 October.
Why it matters. Since the August blast at al-Jabsa the module's energy records have named one indicator: whether interruptions to the north-eastern infrastructure the state took over recur, and whether generation shortfalls follow. The first half has now happened on the same supply chain, about six weeks later. What it does not establish is who: sabotage is the operator's attribution, made twice and supported by no named party, and a local official offered theft instead. The two incidents are kept apart because they say different things — a claimed attack at the supply end in the east, and an unexplained failure at the consuming end near Damascus — and several aggregators merged them. Neither tells the reader how many hours of power a household lost, which is the measure the module watches, and none was published. A third interruption, an investigation finding or a published repair time would each move the reading; another statement of sabotage would not.
Where this fits
Vigil publishes one global Monday-to-Sunday digest and one dated review for every active module. A module brief may carry one item or several, and a quiet module records that no material change was identified alongside the standing watch items it reviewed — silence and "nothing changed" are different claims, and only one of them is checkable. How Vigil grades, dates and sources its claims is set out in the methodology, and anything later found wrong is recorded in the corrections log.
Vigil Dispatch
Follow the analysis
Get Vigil’s Weekly Briefs and new Analytical Notes by email.
One confirmation email, then Weekly Briefs and new Analytical Notes. Unsubscribe at any time.
← Previous global brief — 2026-09-27View all weekly briefs All conflict coverage