Red Sea A tracked procurement-relevant organisation, company, supplier, country, region, port, commodity, regulator, route or similar subject.
- Type The kind of entity being tracked, such as Company, Country, Port, Commodity or Regulator.
- Shipping Route
- Record status The current record state of the entity, such as active, merged or archived.
- Active
- Review status The internal editorial review state of the entity record.
- Pending
- Description
- Major shipping chokepoint/route between the Mediterranean (via Suez) and the Gulf of Aden; canonical name is already the safe, unambiguous form.
- Procurement relevance
- —
- Importance An analyst-assigned input describing how strategically important the entity is. This is one of the inputs used to calculate Entity Criticality below -- Importance is the judgement call an analyst makes; Entity Criticality is the deterministic score calculated from it.
- —
- Strategic
- No
- Critical supplier
- No
- Watchlist Marks an entity for closer monitoring when new relevant signals or events mention it.
- Not watched
- Mentions The number of distinct real collected signals in which the entity has been identified.
- 17
- First seen
- 2026-08-16 06:40:43
- Last seen
- 2026-08-20 19:00:05
- Record type
- REAL
ENTITY CRITICALITY: 4 — TIER 1, PERIPHERAL Highest contributor: Shipping Route type baseline (no specific chokepoint significance recorded) (+4 of 25). Limiting factor: Importance level not set (70 points below its maximum). DATA QUALITY: no curated inputs have been set for this entity yet -- this score reflects the absence of assessment, not a confirmed low-criticality finding.
Calculated 2026-08-15 06:30:30 (calculation version v1).
Current Status
1 open event Canonical events linked to this entity that are still Breaking, Active or Monitoring -- not yet Closed, rejected or merged into another event. · 1 total linked event · 0 Developing Intelligence threads · 0 report appearances · Not watched
Events Canonical events linked to this entity that are still Breaking, Active or Monitoring -- not yet Closed, rejected or merged into another event.
| Headline The concise title of the canonical procurement event. | Type The kind of real-world development identified, such as a supply shortage, contract award, regulatory change or production disruption. | Significance Significance estimates the potential procurement impact of the event, including factors such as supply, cost, operations, geography and strategic importance. | Confidence Confidence indicates how reliable ProcIntel considers the event assessment based on the quality, quantity and independence of the supporting evidence. It does not measure the event's importance. | Lifecycle Lifecycle shows the current state of the development: Breaking is newly detected, Active remains current, Monitoring is being watched for further changes, and Closed is no longer actively developing. | Review The internal review status of the event record. It is separate from the real-world lifecycle of the underlying development. | Articles The number of source articles linked to this canonical event. Several articles may describe the same underlying development. | Evidence strength A plain-language assessment of how much independent evidence supports the Developing Intelligence thread. |
|---|---|---|---|---|---|---|---|
| Houthis Claim Third Attack on Saudi Aramco Refinery in Two Weeks | Production disruption | 3 · Material | 2 · Low | Breaking | Pending | 1 | Low |
Developing Intelligence An evolving procurement situation made up of several distinct but clearly related events over time.
No Developing Intelligence threads
Reports Weekly Intelligence Report editions in which an event or Developing Intelligence thread linked to this entity has appeared.
No report appearances
Relationships A structured link between two entities, such as a company operating at a port or a regulator overseeing an industry.
No relationships recorded yet
Timeline Every recorded action involving this entity -- source mentions, linked events being created or updated, Developing Intelligence links, report appearances and entity-record actions such as merges -- in one dated feed. Nothing here is inferred; each entry is drawn from an existing record.
| Date | What happened | Detail |
|---|---|---|
| 2026-08-20 19:00:05 | Mentioned in "Explainer: Is there any Saudi Arabia’s quiet pivot?" | The text "Red Sea" in the article matched a known alias of Red Sea. |
| 2026-08-19 20:04:09 | Mentioned in "Beyond Tariffs: Geopolitics & Climate Reroute Global Freight" | The text "Red Sea" in the article matched a known alias of Red Sea. |
| 2026-08-19 16:30:00 | Mentioned in "Saudi Aramco Gives Full September Oil Allocations to 3 European Refiners" | The text "Red Sea" in the article matched a known alias of Red Sea. |
| 2026-08-19 15:03:47 | Mentioned in "Liners and Red Sea: Damn the Houthis, full speed ahead!" | The text "Red Sea" in the article matched a known alias of Red Sea. |
| 2026-08-19 05:29:00 | Mentioned in "Saudi Arabia opens new Red Sea resort despite tourism downturn" | The text "Red Sea" in the article matched a known alias of Red Sea. |
| 2026-08-18 23:00:37 | Mentioned in "Alliance strategies diverge amid Middle East crisis" | The text "Red Sea" in the article matched a known alias of Red Sea. |
| 2026-08-18 20:51:09 | Mentioned in "Cargo Ship Destroyed in New Attack Off Yemen" | The text "Red Sea" in the article matched a known alias of Red Sea. |
| 2026-08-18 20:17:14 | Mentioned in "Crippling port delays at Jeddah disrupt project cargo schedules" | The text "Red Sea" in the article matched a known alias of Red Sea. |
| 2026-08-18 12:51:48 | Mentioned in "Race back to Suez gathers pace as MSC increases Red Sea sailings" | The text "Red Sea" in the article matched a known alias of Red Sea. |
| 2026-08-18 11:11:07 | Created — "Houthis Claim Third Attack on Saudi Aramco Refinery in Two Weeks" | Production disruption: 'Houthis Claim Third Attack on Saudi Aramco Refinery in Two Weeks' (lifecycle=Breaking) |
| 2026-08-18 11:11:07 | Pri Recalculated — "Houthis Claim Third Attack on Saudi Aramco Refinery in Two Weeks" | PRI: 1 — MINIMAL Base risk 5/100 × Very Low confidence multiplier (0.15). Highest contributor: A single event -- not yet corroborated by a separate clustered event (neutral baseline, not a penalty) (+5 of 15). Limiting factor: No Significance score yet (event has no linked articles) (40 points below its maximum). DATA QUALITY WARNING: no eligible entities. |
| 2026-08-18 11:11:07 | Pri Recalculated — "Houthis Claim Third Attack on Saudi Aramco Refinery in Two Weeks" | PRI: 1 — MINIMAL Base risk 6/100 × Very Low confidence multiplier (0.15). Highest contributor: A single event -- not yet corroborated by a separate clustered event (neutral baseline, not a penalty) (+5 of 15). Limiting factor: No Significance score yet (event has no linked articles) (40 points below its maximum). DATA QUALITY WARNING: all linked entities data insufficient. |
| 2026-08-18 11:11:07 | Article Linked — "Houthis Claim Third Attack on Saudi Aramco Refinery in Two Weeks" | source_item #9723 |
| 2026-08-18 11:11:07 | Significance Changed — "Houthis Claim Third Attack on Saudi Aramco Refinery in Two Weeks" | 3 |
| 2026-08-18 11:11:07 | Confidence Changed — "Houthis Claim Third Attack on Saudi Aramco Refinery in Two Weeks" | 2 |
| 2026-08-18 11:11:07 | Pri Recalculated — "Houthis Claim Third Attack on Saudi Aramco Refinery in Two Weeks" | PRI: 17 — MINIMAL Base risk 38/100 × Low confidence multiplier (0.45). Highest contributor: Significance 63/100, normalised to this factor's 40-point cap (+25 of 40). Limiting factor: Linked-entity criticality 4/100, normalised to this factor's 30-point cap -- DATA QUALITY WARNING: all linked entities data insufficient (29 points below its maximum). DATA QUALITY WARNING: all linked entities data insufficient. |
| 2026-08-18 10:30:00 | Mentioned in "Houthis Claim Third Attack on Saudi Aramco Refinery in Two Weeks" | The text "Red Sea" in the article matched a known alias of Red Sea. |
| 2026-08-17 14:45:00 | Mentioned in "PIF one of world’s most impactful investors: Al-Rumayyan" | The text "Red Sea" in the article matched a known alias of Red Sea. |
| 2026-08-17 11:33:22 | Mentioned in "Asian Refiners Ask to Pick Up Saudi Oil Outside Risky Red Sea" | The text "Red Sea" in the article matched a known alias of Red Sea. |
| 2026-08-17 11:13:43 | Mentioned in "OceanX: Carrier earnings pushed up by rates – what is the value of ‘premium strategy’?" | The text "Red Sea" in the article matched a known alias of Red Sea. |
| 2026-08-17 10:45:38 | Mentioned in "Red Sea transits: selectivity rules for liners as the arithmetic changes" | The text "Red Sea" in the article matched a known alias of Red Sea. |
| 2026-08-17 08:55:00 | Mentioned in "Asian Refiners Seek Alternative Pickup Point for Saudi Crude" | The text "Red Sea" in the article matched a known alias of Red Sea. |
| 2026-08-17 04:53:23 | Mentioned in "Top maritime news stories for week ended 16 August" | The text "Red Sea" in the article matched a known alias of Red Sea. |
| 2026-08-16 06:40:43 | Mentioned in "India must strengthen shipping capacity, naval protection amid growing chokepoints: GTRI" | The text "Red Sea" in the article matched a known alias of Red Sea. |
| 2026-08-15 06:30:30 | Created | Red Sea |
| 2026-08-15 06:30:30 | Criticality Recalculated | ENTITY CRITICALITY: 4 — TIER 1, PERIPHERAL Highest contributor: Shipping Route type baseline (no specific chokepoint significance recorded) (+4 of 25). Limiting factor: Importance level not set (70 points below its maximum). DATA QUALITY: no curated inputs have been set for this entity yet -- this score reflects the absence of assessment, not a confirmed low-criticality finding. |
Aliases
No alternate names recorded yet.
Review History
| Date | Action | Previous | New | Reviewer | Note |
|---|---|---|---|---|---|
| 2026-08-15 06:30:30 | Created | — | Red Sea | — | — |
| 2026-08-15 06:30:30 | Criticality Recalculated | score=None, tier=None | score=4, tier=1 | — | ENTITY CRITICALITY: 4 — TIER 1, PERIPHERAL Highest contributor: Shipping Route type baseline (no specific chokepoint significance recorded) (+4 of 25). Limiting factor: Importance level not set (70 points below its maximum). DATA QUALITY: no curated inputs have been set for this entity yet -- this score reflects the absence of assessment, not a confirmed low-criticality finding. |