top of page

Baltic & North Sea Under Pressure: What Simultaneous Cable Cuts Would Do to Europe’s ICT, Telecoms & Space- and How to Prepare

  • Writer: Bridge Connect
    Bridge Connect
  • 4 days ago
  • 9 min read

Executive summary

If current peace efforts stall and hybrid pressure escalates, the most logicaldisruptive move is a deniable, multi-point attack on shallow-water subsea cables in the Baltic/North Sea, paired with intensified GNSS jamming/spoofing and opportunistic cyber activity against satellite ground segments. It’s low-cost, high-impact and keeps escalation below a kinetic threshold.


Why you should care:

  • Subsea carries ~95–99% of international data. Hits here move the needle immediately for cloud, finance and mobile.


  • Recent precedents exist. The C-Lion1 (Finland–Germany) cable was cut in Nov 2024 (again over Christmas), and a Latvia–Sweden link was damaged in Jan 2025, prompting sabotage probes and NATO patrols.


  • GNSS interference has surged across the Baltic and Arctic corridors since 2022, with EASA repeatedly warning operators; incident volumes spiked through 2023–2024.


  • Satcom ground segments are vulnerable, as the 24 Feb 2022 Viasat KA-SAT attack showed—tens of thousands of modems bricked, wind farm telemetry sidelined, and European users hit.


This report maps which cables matter, what traffic they carry, how a 3–6-cable cut propagates through networks, and what to stage now across routing, timing (PNT), satcom, and repair logistics.


1) The risk in plain terms: shallow seas, dense traffic, easy deniability

The Baltic and North Sea are crowded with short, repeaterless festoons and regional connectors that knit the Nordics to Germany, the Netherlands, and the UK. Shallow depths and heavy shipping mean anchor drags and trawler incidents are common—and easy to disguise. The ITU and ICPC estimate 150–200 cable faults per year globally, mostly from fishing/anchoring, with repairs typically measured in weeks (weather and permits dependent).

Two trends sharpen the threat:


  • More incidents in the Baltic/North Sea 2023–2025: EE-S1 (Sweden–Estonia) damage alongside the Balticconnector pipeline event; C-Lion1 severed in Nov 2024 (then again around late Dec); Latvia–Sweden cable cut in Jan 2025, with a vessel seized.


  • GNSS interference becoming ambient noise for aviation and maritime across the region, complicating repair ops and port logistics.


2) Anatomy of a European chokepoint: the specific cables to watch

Below are the high-leverage systems whose impairment forces large volumes onto longer, narrower, or less optimal paths:


a) C-Lion1 (“Sea Lion”) — Finland ↔ Germany

Helsinki/Hanko ↔ Rostock. Eight fiber pairs; design 120 Tb/s, max ~144 Tb/s; <20 ms HEL–FRA RTT when up—a prized low-latency route into DE-CIX and Frankfurt DCs. Cut Nov 18, 2024 (and again over year-end). Loss pushes Finland via Sweden/Åland or through the Baltics/Poland.


b) EE-S1 — Sweden ↔ Estonia

Primary westbound path for Estonian transit and peering into Sweden’s big eyeball and carrier networks. Damaged in Oct 2023 around the time of the pipeline incident. Prolonged failure shifts Estonia via Finland or terrestrial south through LV/LT/PL.


c) Latvia–Sweden (LVRTC Gotland route)

Damaged Jan 2025; Sweden opened a sabotage probe; a Malta-flagged vessel was seized. Even with restoration, the episode underlines the Gotland clusteras a tempting shallow-water target.


d) Eastern Light Sweden–Finland I

Stockholm ↔ Helsinki/Hanko/Kotka dark-fibre route that cut Stockholm–Helsinki distance by ~20%, prized for DCI and redundancy versus legacy festoons. Its loss strains Nordic ↔ DE/NL paths.


e) Skagerrak cluster: Skagenfiber West/East + Denmark–Sweden hops

NO↔DK/SE bridges with 48 fiber pairs on Skagenfiber; GlobalConnectfestoons between Denmark and Sweden (e.g., GC2) bind Nordic traffic to continental Europe. Simultaneous hits here isolate Norway toward Swedish routes and congest the Øresund/Kattegat passages.


f) NO-UK — Norway ↔ UK

Stavanger ↔ Newcastle; 8 dark fiber pairs; up to 216 Tb/s. Critical for Norway–UK DC and content paths (e.g., Green Mountain ↔ Stellium). Loss shifts Norway via Sweden/Denmark → NL/DE or toward AEC-2 via Denmark/Ireland.


g) AEC-2 / Havfrue — Transatlantic with Nordic branches

A hyperscaler-heavy trunk linking Denmark/Ireland to the U.S. Nordic detours eventually funnel to these Atlantic gateways; pressure in the North Sea/Baltic pushes more EU↔US load onto southern/UK landings.


h) Tampnet North Sea network — Offshore O&G / wind / maritime

The world’s largest offshore high-capacity network interweaving fibre and 4G/5G across North Sea grids. Damage yields operational degradations on platforms, wind farms, and shipping until microwave/backup paths catch up.


i) SHEFA-2 — Faroes ↔ Shetland ↔ Orkney ↔ Scotland

A true lifeline cable with recent high-impact disruptions (2022; 2025). Outages translate directly to island voice/data slowdowns, cash-only commerce, and court/business delays.


3) What breaks first? Traffic impacts in a 3–6 cable cut scenario

Assume deniable, near-simultaneous “accidents” on 3–6 of the systems above (e.g., C-Lion1 + EE-S1 + Latvia–Sweden + one Skagerrak hop + SHEFA-2). The effects cascade in four layers:


Layer 1 — Latency & path inflation (minutes to hours)

  • Nordic ↔ Frankfurt: With C-Lion1 down, HEL–FRA RTT rises from <20 msto ~30–50 ms as traffic detours via Stockholm → Copenhagen → Hamburg or via the Baltics/Poland; microbursts strain policies until BGP and TE converge.


  • Estonia/Latvia westbound: With EE-S1 and LV–SE degraded, more load goes via Finland (if available) or terrestrial south. Evening peaks show visible throughput dips and increased jitter.


  • Norway ↔ UK/EU: Taking NO-UK or Skagenfiber legs out forces longer NO→SE/DK→NL/DE routes, clipping low-latency enterprise and gaming/video paths.


Layer 2 — Capacity crunch & hot-potato routing (hours to days)

  • Transatlantic spillover: More EU↔US load shifts to UK/FR/ES landings; AEC-2 and other TATs take heat, with CDN cache-fills reprioritized and WAN policies tightened.


  • Channel Tunnel fibres pick up UK↔EU overflow; Colt/EXA upgrades help, but you’re still contending with topology, not just raw lambdas.


Layer 3 — Sector-specific pain (same day)

  • Cloud & DC interconnect: DCI replication shifts onto longer paths; some backup jobs miss windows; cross-region SLOs tighten. (C-Lion1’s sub-20 ms path into Frankfurt is the lost prize.)


  • Financial venues & broker links: Micro-latency arbitrage erodes; jitter breaches transiently nudge order routing.


  • Mobile backhaul & roaming: Baltics lean on Poland/Finland; peering to Swedish eyeballs congests at peak.


  • Offshore O&G/wind: Tampnet customers hit OT/IT slowdowns; condition-monitoring and remote ops degrade.


  • Islands: SHEFA-2 failures manifest as customer-visible outages and degraded payments/911 equivalents.


Layer 4 — Timing degradation (days), especially if GNSS is noisy

2024–2025 saw persistent GNSS jamming/spoofing across the Baltic/Arctic corridors. That challenges PNT-dependent functions (RAN timing, financial timestamping, grid synchrophasors) precisely when you need clean holdover for degraded routes.

Even “regional” cable disruptions ripple quickly into pan-European performance, and if timed with GNSS interference and satcom nuisances, the operational fog thickens.

4) The hybrid kicker: GNSS interference and space/cyber pressure

  • Aviation & maritime: EASA updated its Safety Information Bulletin in July 2024, warning about jamming/spoofing around conflict zones, explicitly including the Baltic and Arctic. Operators recorded tens of thousands of interference events 2023–2024.


  • Satcom ground segments: The Viasat KA-SAT hack on 24 Feb 2022 bricked tens of thousands of modems across Europe and snarled industrial telemetry (e.g., wind turbines in Germany). It’s the template for opportunistic hits against gateways, NMS, and terminal fleets during a cable crisis.


Implication: Expect layered effects—not just fibre cuts. Your resilience plan must assume noisy PNT and satcom fragility at the same time as subsea impairment.


5) Preparedness you can implement now


5.1 Network architecture & contracts

  1. Prove physical diversity, don’t assume it.Audit for common-corridor risk (Baltic festoons; Skagerrak; Gotland). Buy capacity on non-collinear routes and separate landing stations/consortia (e.g., split between C-Lion1/Eastern Light/terrestrial via PL). Document with route maps and CLS names in MSAs.


  2. Pre-negotiate restoration (RFS/priority clauses).If a cable fails, you want guaranteed expedited restoration windows and burst rights on alternates. Check the fine print for force majeureambiguity in state-linked sabotage scenarios.


  3. Engineer for graceful degradation.


  4. BGP/TE runbooks to shift hot prefixes away from Baltics/Skagerrak cuts; pre-stage policies for HEL/ARN/OSL DCs toward DK/NL/DE.


  5. CDN/cache policy ready to bias toward London/Paris if Nordic origins congest; stage QoS for trading/OT traffic.


  6. Testing: quarterly “Baltic Cut Day” chaos drill: withdraw specific MED/LP paths; measure convergence, SLOs, packet loss.


  7. Channel Tunnel capacity as a safety valve.Colt/EXA deployments add multi-Tbps UK↔FR resilience; fold these into your re-route graph and SLA calculations.


5.2 Timing (PNT) hardening

  1. Dual-source PNT: multi-constellation GNSS plus terrestrial (e.g., eLoranif available) and disciplined oscillators to hold time through outages/spoofing. EASA’s SIBs assume interference will persist.


  2. Spoofing detection & alarms integrated with NOC workflows; fall back to PTP with boundary clocks and holdover for RAN/finance workloads.


  3. Aviation/maritime ops: anticipate NOTAM spikes; brief logistics teams repairing cables on GNSS-denied procedures.


5.3 Satcom resilience

  1. LEO+GEO mix, alternate gateways, and segmented terminal fleets to avoid monocultures; scrutinize NMS access control and firmware updatepipelines.

  2. Red-team ground segments using KA-SAT TTPs as injects; verify offline recovery paths for disabled modems.


5.4 Subsea repair readiness

  1. Know the repair queue. ICPC notes ~3 repairs/week worldwide; permit lead times can stretch 1–6+ weeks depending on jurisdiction—pre-arrange documentation.


  2. Weather windows & spares: stage jointing kits, spare repeaters/SLTE where applicable; maintain on-call vessel arrangements where possible.


  3. Incident liaison: pre-write playbooks with coastguards/NAVWARN and hydrographic offices to secure temporary safety zones and speed up ALRS/Notice to Mariners updates.


6) Case notes: recent incidents and why they matter

  • C-Lion1 (HEL–ROSTOCK): cut around 02:00 GMT 18 Nov 2024, again at year-end; restored early Jan 2025. Shows how a single strategic festoon can move Finland⇄Frankfurt from sub-20 ms to materially higher RTTs.


  • EE-S1 (SE–EE): Oct 2023 damage “by external force or tampering”; coincident with Balticconnector incident—textbook hybrid timing.


  • Latvia–Sweden (Gotland): Jan 2025 damage; Sweden seized a vessel; FT and Reuters framed it as the fourth Baltic incident in short order—pattern, not a one-off.


  • SHEFA-2: Oct 2022 Shetland outage (major incident), plus July 2025Orkney/Shetland disruptions—illustrates island brittleness and the real-world impact on payments, courts, and emergency services.


7) What to monitor (and automate) in the next 90 days

  1. Vessels loitering on cable corridors (Baltic, Skagerrak, Gotland): look for AIS gaps, low-speed anchor-drag tracks, and sanctioned/shadow fleet patterns. (Authorities have already detained suspect ships after cable cuts.)


  2. GNSS anomaly spikes (EASA bulletins, airline reports, LEO-RF analytics). A jamming burst before spoofing is common; expect concentration near Kaliningrad and northern corridors.


  3. Repair asset allocation: where are the cable ships, and who has permit priority this quarter? ICPC/industry comms will telegraph queues.


  4. Ground-segment chatter: TTPs referencing satcom NMS, modem configs, or landing-station OT deserve priority triage (KA-SAT playbook).



8) Operator checklist (use today)

Routing & capacity

  • Validate physical diversity to the cable-pair and landing-station level (e.g., C-Lion1 vs Eastern Light vs terrestrial via PL). Document in MSAs.


  • Stage BGP communities/MED templates for a “Baltic Cut Day”.

  • Pre-approve temporary QoS tiers for trading/SCADA/911-equivalents during congestion.

Timing (PNT)

  • Deploy multi-constellation + terrestrial timing with alarms; test spoofing detection and holdover durations aligned to your worst-case reroute times.


Satcom

  • Mix constellations and gateways; harden NMS access; rehearse modem fleet recovery offline (post-KA-SAT lessons).


Subsea repair

  • Maintain spares and repair vessel options; compile permit packs for each EEZ you traverse. Expect weeks rather than days if weather/permits bite.


Communications

  • Draft customer-facing latency/throughput advisories tied to specific corridors (“Baltic/Skagerrak impairment” language), plus investor-safe disclosures if material.


9) Appendix: what each highlighted cable typically carries (rule-of-thumb)

  • C-Lion1 / Eastern Light (FI–DE/SE): DCI replication, cloud backbones, some low-latency finance; connects HEL/Hanko directly to Frankfurt/DE-CIX in <20 ms.


  • EE-S1 / LV–SE: Baltic eyeball ISP transit, gov/enterprise VPNs, MNO roaming/peering into Sweden; cut pushes load via Finland/Poland.


  • Skagenfiber / GlobalConnect: High-count (NO↔DK/SE) pathways anchoring Norway (and parts of Sweden) to continental Europe—big for content and enterprise.


  • NO-UK: Norway ↔ UK shortest path; 216 Tb/s headroom; DC-to-DC and content distribution; a key low-latency link.


  • Havfrue/AEC-2: Hyperscaler-heavy transatlantic; EU↔US bulk and content; becomes hotter when Baltic/North Sea routes constrict.


  • Tampnet: OT/IT for offshore energy, wind, maritime; loss causes visible industrial slowdowns until alternates engage.


  • SHEFA-2: Island last-mile backhaul/voice; outages equal service loss, not just higher latency.



10) The strategic context: why this matters beyond “a few fibres”

  • The ITU and partners have moved to formalize subsea resilience workstreams, repeatedly emphasizing that >95–99% of international data rides these cables. That’s not a niche risk—it’s the internet’s backbone.


  • Repair logistics are finite. Average global fault volumes and the specialized fleet mean simultaneous hits can outstrip response capacity. Permit friction adds days to weeks.


  • Hybrid convergence is here: maritime “accidents,” GNSS interference, and satcom ground-segment pressure overlap by design. Your response should too.



11) What we recommend you do next - Bridge Connect playbook

  1. Commission a route-level diversity audit (30–45 days work effort): enumerate every leased wave and IP blend down to CLS/duct; score against Baltic/Skagerrak/Gotland exposure.


  2. Run a live failover exercise (“Baltic Cut Day”): rotate preferreds for your Nordic prefixes; measure convergence, jitter, loss, and customer-visible SLOs; fix what breaks.


  3. Stand up a PNT tiger team: align GNSS alarms with NOC; model holdover by service (RAN, trading, grid telemetry).


  4. Harden satcom ground-segment: credential hygiene, network segmentation, golden-image rebuilds tested offline; escrow firmware; tabletop a KA-SAT-style incident.


  5. Repair-chain readiness: pre-qualify yards/ships, spares, jointing kits; assemble permit dossiers for Sweden, Finland, Denmark, Germany, Baltics, UK; rehearse comms with maritime authorities.



“In Europe, a few shallow cuts can push the Nordics from <20 ms to 30–50 ms into Frankfurt - enough to bruise cloud and finance.”


Sources & further reading (selected)



 
 

Related Posts

See All

Subscribe for more Insights

Thanks for submitting!

bottom of page