There is a sentence that has run through the wires all week: "Russia and China blocked the UN from protecting shipping in the Strait of Hormuz." It is elegant. It is also not quite what happened — and the distance between the sentence and what happened is the point.

On 7 April 2026 the Security Council took a recorded vote on draft resolution S/2026/273, submitted by Bahrain on behalf of the Gulf Cooperation Council plus Jordan. Eleven members voted in favour; two against; two abstained. The two against were the Russian Federation and the People's Republic of China. The abstentions were Colombia and Pakistan. The text failed for lack of the "concurring vote" of all permanent members under Article 27(3) of the UN Charter. Twenty-four hours later, under the "veto initiative" established by General Assembly resolution A/RES/76/262 (April 2022), the Assembly convened to hear the vetoing states explain themselves — debate record GA/12758. On paper, the transparency mechanism working as designed.

What it does not do — what it was never designed to do — is tell you whether the text on the table was the one you think it was.

The resolution that died, and the one that didn't exist

The Bahraini draft, as voted, "strongly encourages" states "interested in the use of commercial maritime routes in the Strait of Hormuz" to "coordinate efforts, defensive in nature, commensurate to the circumstances," and "demands" that Iran cease attacks on vessels. That is the text that failed. It is not the text that started the month.

The Security Council Report's insider brief, What's in Blue, reconstructs the paper trail. Bahrain circulated the first version on 21 March. That text invoked Chapter VII of the UN Charter — the provision that authorises the Council to approve sanctions or the use of force — and called on member states to deploy "all necessary means" to unblock the strait, the formula that authorised the 1990 coalition against Iraq. Over five revisions, two silence breaks, and closed consultations on 1 April, "all necessary means" became "all defensive means necessary" and finally became a hortatory paragraph that "strongly encourages" defensive coordination. The Chapter VII reference was deleted; a proposed narrowing of the mandate to the strait itself, with a six-month sunset, was stripped out; sanctions language was downgraded from direct imposition to a readiness to "consider further measures." France, a permanent member, had already circulated a competing draft in March to a restricted list of Council members.

By the time the blue version went to a vote, the draft had been negotiated down twice — once because China and Russia threatened a veto against the Chapter VII original, and again because France and Greece broke silence on the scope of even the watered-down text. The resolution that died on 7 April was not a freedom-of-navigation measure. It was the residue of one, hollowed out to avoid the veto it got anyway. That is a distinction the wires have not been eager to draw.

What the vetoing states said, and what gets quoted

The veto initiative exists so that the General Assembly record contains the vetoing state's reasoning. Russia's Ambassador Vassily Nebenzia and China's Ambassador Fu Cong both spoke. Both statements are public. Both were summarised in the mainstream coverage by their second half and stripped of their first.

Fu Cong's argument, from the Chinese mission's published explanation-of-vote of 7 April: "The fundamental reason for the disruption of navigation in the Strait of Hormuz is the illegal military actions taken by the US and Israel against Iran" — strikes launched "without authorization from the Security Council and while negotiations between Iran and the US were underway." The draft "fails to capture the root causes and full picture of the conflict" and "contains one-sided condemnation and pressure." Nebenzia, for Russia, pointed out that "illegal attacks by the United States and Israel" were "not mentioned at all" in the preamble; he called the final text "unbalanced, inaccurate and confrontational." Iran's ambassador Amir Saeid Iravani, speaking under Rule 37, said the resolution sought "to punish the victim for defending its sovereignty," and thanked the vetoing powers for preventing the Council from being "misused to legitimise aggression."

Reuters, AP and the BBC reported the Chinese and Russian statements the same way: as positioning, as a defence of Iran. PBS put "watered-down" in its headline but described Russia and China as blocking a "reopening" of the strait — neither what the text said nor what a text of that weight could do. The US mission's line — that the vetoing states had "turned a blind eye" — was reported straight; the vetoing states' claim that the Council was being asked to ratify, in preamble, the legality of strikes that started the crisis, was reported as rhetoric. That is the sourcing filter in the propaganda model: when "the UN" speaks, it is the permanent three; when the permanent two speak, they are merely vetoing.

Who was actually on the Council — and for whom

Eleven of fifteen Council members voted yes — a real majority, and it matters. But the yes column does not tell you which states were campaigning for the text and which were being campaigned on. Bahrain did not draft S/2026/273 in a vacuum; it hosts the US Navy's Fifth Fleet. Its Kuwaiti, Qatari, Emirati and Saudi co-sponsors are parties to a US-led Combined Maritime Forces architecture whose legal cover for escorting tankers would have been materially strengthened by any text mentioning "coordinated defensive efforts." The US mission argued exactly that in its explanation-of-vote. That is not a hidden agenda. It is a stated one. The question was not whether Iranian gunboats were firing on tankers — they were — but whether a chapter-less, sanction-less hortatory text was, in practice, a permission slip for a US-flagged coalition operating in a strait that is also Iranian territorial sea along its northern shore.

Colombia and Pakistan abstained for reasons the wires largely ignored. Pakistan — which shares a long land border with Iran — flagged the text's failure to condemn the US and Israeli strikes that precipitated the crisis. Colombia, governed by a left coalition that has spent two years dissenting from US hemispheric policy, echoed the concern about the preambular framing.

The institution the reader is told exists, and the one that does

When Western editorials speak of "the UN," the reader is meant to hear the General Assembly's moral voice joined to the Council's coercive power. That institution has never existed. What exists is an organ in which five states hold an unconditional negative — the other ten rotate. The Security Council Report's "In Hindsight: Living with the Veto" review, published with the April 2026 forecast, shows the structural picture. 2024 recorded the most vetoed drafts since 1986: seven blocked, eight vetoes cast — four by Russia, three by the US, one by China. Of the four 2025 vetoes, two were US vetoes of Gaza ceasefire drafts and two were Russian vetoes of Ukraine amendments. 2026's first quarter adds Hormuz.

Over three years, the largest source of vetoed humanitarian and ceasefire texts has been the United States, on Gaza; second, the Russian Federation, on Ukraine; China, once. The Chomskian reading writes itself. In the Gaza file, "the UN" is Washington; in the Ukraine file, Moscow; in the Hormuz file, Beijing and Moscow — but only in that file, only that week. The institution is not a single speaker. It is a register of who has the structural power to say no, applied selectively by a press that reaches for the passive voice whenever the right capital vetoes.

The International Crisis Group's Daniel Forti, in rare Western think-tank commentary that read the draft as a draft, put it neutrally: Russia and China saw the resolution "as too escalatory and not capturing the need for impartial and consistent diplomacy." Chatham House's Hormuz legal briefing, published the same week, went further: resolution 2817 (2026), adopted on 11 March, already confirmed the right of states to "defend their vessels from attacks and provocations." S/2026/273 added no new legal authority. It added political cover for a specific coalition, framed as if the opposite were true.

What's being hidden

Three things. The drafting history — the vote version was the third climb-down of a text whose first draft asked the Council to authorise force against Iranian naval assets in territorial waters. The legal redundancy — UNSC 2817 (2026), adopted 11 March, already encoded the freedom-of-navigation principle S/2026/273 ostensibly protected; the new text was political, not legal, architecture. And the symmetry — the same press infrastructure that calls a Russia–China veto of a Gulf-sponsored Western-backed text "obstruction" calls a US veto of a Gaza ceasefire, one week later, "concerns." The filter is not that vetoes go unreported. The filter is which are coded as the system functioning and which as the system being abused.

Key questions

• If S/2026/273 had been adopted, what Council authority would have existed for a US-led maritime coalition in Iranian territorial waters beyond what UNCLOS Article 38 and UNSC 2817 already provide?
• Why did France circulate a parallel draft in March and then accept amendments to the Bahraini text without publishing its own?
• Is the A/RES/76/262 "veto initiative" doing real accountability work, or has it become transparency theatre that costs the P5 nothing?
• Which of the seven 2024 and four 2025 vetoes did the reader ever hear about by resolution number, rather than as "the UN failed to adopt"?

The kicker

The veto is a structural feature of the Charter, not a bug the current P5 introduced. It is how the 1945 settlement encoded the fact that the great powers would not be bound by the institution they built. What the past week in New York makes visible is not that the veto exists — everyone knows it exists — but that the press's grammar has a veto of its own. It decides which texts the reader sees and which are reduced to "the draft"; which explanations become positions and which become obstruction; which capitals speak on behalf of "the international community" and which speak only for themselves. On 18 April we are still being told the UN did not protect shipping in Hormuz. The UN did not do that because the UN, in that sentence, is not a thing. The Security Council is a thing, and on 7 April eleven of its members wanted one text, two vetoed it, two abstained, and five members of the next maritime coalition were its sponsors. That is the story. The rest is framing.

Sources:

• United Nations Meetings Coverage, "China, Russian Federation Veto Security Council Draft Resolution by Gulf States to Safeguard International Shipping through Strait of Hormuz," press release SC/16330, 7 April 2026.
• United Nations Meetings Coverage, "General Assembly Debates Strait of Hormuz Closure after China, Russian Federation Veto Security Council Draft Resolution Presented by Gulf States," press release GA/12758, 8 April 2026.
• UN News, "Security Council: Russia and China veto resolution on Strait of Hormuz," 7 April 2026.
• Draft resolution S/2026/273, submitted by Bahrain, Jordan, Kuwait, Qatar, Saudi Arabia and the United Arab Emirates.
• UN Security Council resolution 2817 (2026), adopted 11 March 2026; UN Charter Article 27(3) and Chapter VII; UN General Assembly resolution A/RES/76/262 (the "veto initiative," 26 April 2022).
• Permanent Mission of the People's Republic of China to the UN, Explanation of Vote by Ambassador Fu Cong, 7 April 2026.
• Security Council Report, "Middle East Crisis: Vote on a Draft Resolution on the Strait of Hormuz," What's in Blue, April 2026.
• Security Council Report, "In Hindsight: Living with the Veto," April 2026 Monthly Forecast.
• Al Jazeera, "Russia and China block UN resolution on Strait of Hormuz," 7 April 2026.
• Al-Monitor, "China, Russia veto scaled-back Hormuz resolution at UN Security Council," April 2026.
• Chatham House, "The Strait of Hormuz, shipping, and law," April 2026, and expert commentary from Daniel Forti, International Crisis Group UN Affairs.

Author's Note: This analysis reflects the perspective of Moemedi Michael Poncana. The propaganda model's sourcing filter is not a conspiracy; it is a structural bias in which capitals have the standing to be quoted neutrally and which are quoted as partisans. Hormuz this week was a textbook case.

Sources

• United Nations Meetings Coverage, "China, Russian Federation Veto Security Council Draft Resolution by Gulf States to Safeguard International Shipping through Strait of Hormuz," press release SC/16330, 7 April 2026.
• United Nations Meetings Coverage, "General Assembly Debates Strait of Hormuz Closure after China, Russian Federation Veto Security Council Draft Resolution Presented by Gulf States," press release GA/12758, 8 April 2026.
• UN News, "Security Council: Russia and China veto resolution on Strait of Hormuz," 7 April 2026.
• Draft resolution S/2026/273, submitted by Bahrain, Jordan, Kuwait, Qatar, Saudi Arabia and the United Arab Emirates.
• UN Security Council resolution 2817 (2026), adopted 11 March 2026; UN Charter Article 27(3) and Chapter VII; UN General Assembly resolution A/RES/76/262 (the "veto initiative," 26 April 2022).
• Permanent Mission of the People's Republic of China to the UN, Explanation of Vote by Ambassador Fu Cong, 7 April 2026.
• Security Council Report, "Middle East Crisis: Vote on a Draft Resolution on the Strait of Hormuz," *What's in Blue*, April 2026.
• Security Council Report, "In Hindsight: Living with the Veto," April 2026 Monthly Forecast.
• Al Jazeera, "Russia and China block UN resolution on Strait of Hormuz," 7 April 2026.
• Al-Monitor, "China, Russia veto scaled-back Hormuz resolution at UN Security Council," April 2026.
• Chatham House, "The Strait of Hormuz, shipping, and law," April 2026, and expert commentary from Daniel Forti, International Crisis Group UN Affairs.