Incident report · 2026040103
Tampnet North cable: latency anomaly, 1 Apr 2026
Resolved · 4h 59m
What we measured
| Cable | Tampnet North |
| Segment | Øygarden, NO → Aberdeen, GB |
| Detected | 2026-04-01 22:33 UTC |
| Resolved | 2026-04-02 03:32 UTC |
| Duration | 4h 59m |
| Observed latency | 23.5 ms |
| Baseline | 27.2 ms · 0.86× |
| Increase | +193% |
| Severity | warning |
Who is affected
Countries where Tampnet North comes ashore, how much of their submarine diversity this cable represents, and what our measurements into them show.
| Country | Dependence on this cable | Other submarine cables | What the measurements show |
|---|---|---|---|
| Norway resilience index: 100 · resilient |
1 of 19 cables (5% of submarine diversity) | Arctic Way, Bodo-Rost Cable, Eviny Digital +15 more | median 64 ms today vs 86 ms over 30 days (103 routes) - faster |
| United Kingdom resilience index: 100 · resilient |
1 of 68 cables (1% of submarine diversity) | 2Africa, Amitie, Apollo +64 more | median 103 ms today vs 74 ms over 30 days (1011 routes) - slower |
Dependence is structural (share of the country's submarine cables), not a traffic share: real traffic distribution across cables is not public.
Path analysis
No usable traceroute data for this window.
Cross-probe verdict. Too few independent vantage points were watching this endpoint to reach a cross-probe verdict.
Timeline
- Alert #35: warning - Aberdeen
- Alert #35 resolved: Aberdeen
Detection method
Latency is sampled continuously from our probe network. An alert opens when round-trip time to a monitored endpoint holds above its rolling baseline, and closes automatically once it returns. Full method is described on the methodology page.
How to cite
GeoCables (2026). Incident 2026040103: Tampnet North. https://geocables.com/incident/2026040103
Embed this map
<iframe src="https://geocables.com/embed.php?type=map&id=tampnet-north" width="640" height="420" frameborder="0" loading="lazy" style="border:0;border-radius:10px"></iframe>