Carnival Submarine Network-1 (CSN-1): latency up to 2.7× normal, 5 Nov 2026
What we measured
| Cable | Carnival Submarine Network-1 (CSN-1) |
| Segment | Ancon, EC → Naples, US |
| Detected | 2026-11-05 23:01 UTC |
| Resolved | 2026-11-06 01:31 UTC |
| Duration | 2h 30m |
| Observed latency | 87.1 ms |
| Baseline | 112.8 ms · 2.7× |
| Increase | +170% |
| Severity | warning |
Who is affected
Countries where Carnival Submarine Network-1 (CSN-1) 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 |
|---|---|---|---|
| Colombia resilience index: 100 · resilient |
1 of 12 cables (8% of submarine diversity) | America Movil Submarine Cable System-1 (AMX-1), ARCOS, Colombia-Florida Express (CFX-1) +8 more | median 194 ms today vs 158 ms over 30 days (536 routes) - slower |
| Ecuador resilience index: 84 · resilient |
1 of 6 cables (17% of submarine diversity) | Galapagos Cable System, Pacific Caribbean Cable System (PCCS), PanAm South +2 more | median 174 ms today vs 218 ms over 30 days (1117 routes) - faster |
| Mexico resilience index: 100 · resilient |
1 of 12 cables (8% of submarine diversity) | America Movil Submarine Cable System-1 (AMX-1), ARCOS, Bifrost +8 more | median 182 ms today vs 166 ms over 30 days (1009 routes) - unchanged |
| Panama resilience index: 85 · resilient |
1 of 10 cables (10% of submarine diversity) | Alisios, ARCOS, Curie +6 more | median 199 ms today vs 199 ms over 30 days (15 routes) - unchanged |
| United States resilience index: 100 · resilient |
1 of 123 cables (1% of submarine diversity) | ACS Alaska-Oregon Network (AKORN), AEC-1, Airraq +119 more | median 143 ms today vs 126 ms over 30 days (9904 routes) - unchanged |
Dependence is structural (share of the country's submarine cables), not a traffic share: real traffic distribution across cables is not public.
Vessels nearby at the time of the incident
- MSC TAKORADI VIII (cargo): slow drift over the route, 0.3 km from the route, 21.8 h before the start
- CTI QUEEN (cargo): anchored, 0.3 km from the route, 3.9 h after the start
- OOCL SOUTHAMPTON (cargo): slow drift over the route, 0.3 km from the route, 4.4 h after the start
- ECO TRAMONTANE (cargo): anchored, 0.6 km from the route, 15.7 h before the start
- NORDICO: anchored, 1.1 km from the route, 47.5 h before the start
Vessels near a cable route are seen before incidents about as often as on ordinary days: 61% against 57% over 79 incidents since 6 Aug 2026. How this is counted
Alert check
Not confirmed. We asked other measurement points, and they did not see the trouble. The alert stays on record but is not counted as an incident. what this means
Path analysis
Traffic kept the same route. Latency rose without a visible path change, which points at congestion or a fault on the existing route rather than a reroute.
Cross-probe verdict. Our own cross-check concluded this was an operator reroute, not a cable fault. We publish it anyway, labelled as such.
Timeline
- Alert 2026110502: warning - ratio 2.7x
- Alert #246 improving: 1/3 consecutive OK
- Alert #246 improving: 2/3 consecutive OK
- Alert #246 resolved: RTT 87.09ms (baseline 112.76ms), 3 consecutive OK
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.