Skip to content
RichseenAtlas← AtlasSign in

A sinking ship's anchor severs Red Sea cables

node

The bulk carrier Rubymar, struck by Houthi missiles on 18 February 2024 and drifting before it sank, is generally assessed to have dragged its anchor across the seabed and damaged several cables in the southern Red Sea; the systems reported affected were SEACOM, AAE-1, EIG and TGN. Regional traffic between Asia, the Gulf and Europe was disrupted, and repair was complicated by the security situation and by the permissions required to work in those waters. The general manager of the ICPC noted publicly that a dragged anchor is among the leading causes of cable damage — which is the point: the mechanism was entirely ordinary, and only the reason the anchor was down was not.

A node is not a place. Drawing it on a map would assert something about the world that no stored fact supports.

Read in · 1

Evidence · 1
Timeline

No dated observations are stored for this object. Atlas shows what was observed and when — it does not infer a history.

Connections · 2
Assembled narrative · 1

Assembled from 21 blocks · 1 evidence · 15 related

  1. Story
  2. The bulk carrier Rubymar, struck by Houthi missiles on 18 February 2024 and drifting before it sank, is generally assessed to have dragged its anchor across the seabed and damaged several cables in the southern Red Sea; the systems reported affected were SEACOM, AAE-1, EIG and TGN. Regional traffic between Asia, the Gulf and Europe was disrupted, and repair was complicated by the security situation and by the permissions required to work in those waters. The general manager of the ICPC noted publicly that a dragged anchor is among the leading causes of cable damage — which is the point: the mechanism was entirely ordinary, and only the reason the anchor was down was not.
  3. Knowledge
  4. The Red Sea cable corridor
  5. International Cable Protection Committee
  6. A sinking ship's anchor severs Red Sea cables
  7. Connections
  8. The Red Sea cable corridor
  9. International Cable Protection Committee
  10. SEA-ME-WE 5
  11. The cable chokepoint
  12. The Egyptian cable land crossing
  13. SEA-ME-WE 5 is ready for service
  14. A sinking ship's anchor severs Red Sea cables
  15. SMW4 and IMEWE are cut near Jeddah
  16. An international advisory body for cable resilience is created
  17. The Cable Damage Committee is established
  18. A sinking ship's anchor severs Red Sea cables
  19. An international advisory body for cable resilience is created
  20. Evidence
  21. Supports the 2024 and 2025 Red Sea incidents as described here: the cables reported affected, the assessed anchor-drag mechanism in 2024 with ICPC comment, the 05:45 UTC start of the September 2025 latency effects, and Microsoft's statement that traffic previously routed through the Middle East would see higher latency. V55 verification basis: contemporaneous journalism retrieved in summary, not primary incident reports. Cause attribution for the 2024 damage is an assessment, not a finding; the Houthi movement denied involvement in the 2025 cuts and no cause has been established here.
Close the narrative
Observed changes · 0

No public Signals are attached to this object. Signals show what changed and when it was observed — never a direction or a rank.

Actions

Read the assembled narrativeContinue in StudioOpen TwinTwin does not start a decision from this kind of object.ShareSaveSaved objects are part of the authenticated projection, which is declared and not yet built.

/atlas?object=EVT_RED_SEA_CUTS_2024&experience=EVT_RED_SEA_CUTS_2024