The Security Council selectivity, the Iran War, and Hormuz threshold

The AnewZ Opinion section provides a platform for independent voices to share expert perspectives on global and regional issues. The views expressed are solely those of the authors and do not represent the official position of AnewZ

The United Nations Security Council did not fail because it was silent after the war against Iran began on 28 February 2026. 

It failed because it produced a binding response only once the conflict had become a threat not just to regional security, but to the circulation system on which that security rests.

The Council met in emergency session as soon as the United States and Israel launched strikes on Iran, yet its only adopted resolution on this crisis was S/RES/2817, passed on 11 March 2026. That sequence is not incidental. It is the clearest indicator of what the Council was actually prepared to prioritise.

At the outset, the Security Council did what it often does in moments of acute escalation: it convened, heard warnings, and called for restraint. But it did not produce a binding text addressing the initial U.S.-Israeli attack in comparable terms to the resolution it would later adopt on Iranian retaliation.

In other words, the Council recognised the danger of the war without establishing a symmetrical institutional position on its origin. That is the first asymmetry, and it matters because it reveals that emergency procedure was not matched by normative clarity.

The UNSC Resolution 2817

When the Council finally acted in binding form on 11 March, it did so through a Bahrain-led text adopted by 13 votes in favor, none against, with China and Russia abstaining. According to the UN’s official meeting coverage, Resolution 2817 condemned Iran’s “egregious attacks” against Bahrain, Kuwait, Oman, Qatar, Saudi Arabia, the United Arab Emirates and Jordan, demanded that such attacks cease, and addressed attacks on civilians and civilian objects.

Formally, then, the Council’s definitive action was directed at the retaliatory phase of the war. The official Security Council resolutions record confirms that S/RES/2817 (2026), dated 11 March 2026, is the adopted resolution on this crisis sequence.

That formal description, however, is not enough. It would be too simple to say that the Council moved merely because GCC states and Jordan were attacked. Those attacks were the explicit subject of the resolution, but they do not fully explain why a binding text became politically possible only on 11 March and not earlier, when the retaliation started. By then, the crisis was no longer just about retaliation against regional states. It had become a wider emergency involving damaged energy infrastructure, disrupted maritime routes, and the real danger of a sustained closure of the Strait of Hormuz.

Contemporary summaries of the adopted text indicate that the resolution also referenced freedom of navigation, drew attention to threats to maritime navigation in the Strait of Hormuz and Bab al-Mandab, and underscored the importance of the region for global energy supplies and international trade.

Hormuz was not the sole object of the text, but neither was it marginal. It was part of the political logic of the resolution.

The Hormuz threshold and double standards

The timing is what makes the point unavoidable. On 10 March, the UN Secretary-General’s office, citing UNCTAD, stated that ship traffic through the Strait of Hormuz had fallen by 97 per cent since 28 February. On 11 March, the Security Council adopted Resolution 2817.

• The real power of the Strait of Hormuz
• Trump’s call to guard Hormuz shipping faces reluctant global response

Greece’s explanation of vote after adoption made the systemic dimension explicit, warning of the conflict’s consequences for global trade and energy supply and stating that “The Straits of Hormuz must open again and freedom of navigation must be restored without delay.” That reaction strongly suggests that the Council moved not simply when violence spread, but when it threatened the infrastructure itself.

That matters because it shifts the centre of the story. The Council did not move from debate to decision when the prohibition on the use of force was first breached. Nor did it move when retaliation merely widened the battlefield. It moved when the war endangered shipping, energy flows, and the functioning of one of the world’s most strategic chokepoints. Put differently, the decisive threshold was not illegality but systemic disruption.

Markets registered the same threshold. As disruption in and around Hormuz deepened, Brent crude rose above $100 per barrel, later reaching $119.50 per barrel, while analysts tied the surge directly to war-related energy disruption and the effective shutdown of the strait. That does not mean oil prices alone “caused” the Council’s vote.

But it does reinforce the broader point. By the time Resolution 2817 was adopted, the conflict had ceased to be only a regional military confrontation. It had become a systemic economic-security shock. The Council acted when the costs of inaction were no longer confined to the battlefield.

The voting pattern deepens the argument. The United States supported the Bahrain-led resolution; China and Russia abstained. China said the United States and Israel had launched military strikes against Iran without Security Council authorisation, that the war lacked “justification and legitimacy.”

Beijing also highlighted that “the fundamental way” to prevent further deterioration was for Washington and Tel Aviv to cease their military operations. Yet China still stopped short of blocking the text.

That decision is revealing. Even powers that considered the text politically distorted were unwilling to assume responsibility for blocking a resolution once the crisis had been recast around attacks on Gulf states, civilian infrastructure, maritime routes and strategic chokepoints.

From legal principle to systemic stability

This is where the broader significance of the episode becomes clear. The issue is not only hypocrisy, though the double standard is evident. The deeper issue is that the Council’s operational threshold is no longer the original illegality alone. It is the point at which illegality begins to endanger the system.

The initiating U.S.-Israeli attack generated emergency diplomacy, warnings and argument. The later threat to GCC security, maritime navigation and Hormuz generated a resolution. That is not just selective enforcement, it is a hierarchy of urgency, and therefore a hierarchy of enforcement.

Seen this way, the Security Council did not uphold a rule-based order in any universal sense. It upheld a narrower imperative: the containment of systemic risk for aligned states and strategic circulation networks. Rules remained present in the rhetoric.

International law still shaped the language of abstention, condemnation and self-defense. But legal principle alone was not enough to produce binding action. What produced action was the risk that the war would choke one of the world’s essential arteries of trade and energy.

That is the real lesson of Resolution 2817. The Council did not move when war began. It moved when war became expensive for the system. This is why the episode fits the broader shift toward a less rule-based and more selectively managed regional order. The rules have not disappeared. They have been subordinated, some violations are debated, others are condemned.

Binding action comes when circulation, markets and aligned security architectures are at risk. In that sense, the Council’s response to the Iran war was not merely selective, it was diagnostic. It revealed, with unusual clarity, the order that is replacing the one the international community still claims to defend.

• 'Utterly unlawful': Iran slams UN resolution criticising attacks on U.S. bases

Tags

Opinion Iran Strait of Hormuz Middle East conflict