by HonkWatch

Internet routes & submarine cables

Find slow routes, inspect the evidence and explore the cables connecting the world.

Checks continue when this page is closed. Loading the latest check times…

Cable drawings and landing places. Line colours identify cables; they do not show cable health.

World view

Loading cable routes…

Each colour = a cableLanding place

Click a line or dot · Drag to move · Scroll to zoom

Loading the cable map…

Routes combine OpenStreetMap sections and HonkWatch schematic drawings. The catalogue also includes Wikidata records without map geometry. Public measurements and reports provide context; they do not establish physical cable health.

All cable checks

Search for a cable or country. Select a cable to view its findings beside the map.

Network-path evidence · Physical cable health: unconfirmed · BGP: on-demand snapshots

Loading worldwide coverage…

Reading saved evidence…

Cable catalogue network evidence and coverage gaps
Cable recordNetwork evidenceDetails
Technical measurement details

Inspect network measurements

This display updates every five minutes. Background monitoring continues independently.
Choose a cable above, then inspect one of its related network corridors.

Loading measurement history…

Below thresholdsLatency increasePacket lossInsufficient data
Detection rules and coverage

Existing public RIPE Atlas IPv4 anchor-mesh pings are compared with a 20-hour baseline. The following four hours are grouped into ten-minute buckets. Two consecutive abnormal buckets trigger a path anomaly. Concurrent anomalies on two endpoint pairs, using different networks at each end, produce a correlated disruption.

Latency must rise by the greatest of 20 ms, 50% of the baseline median, or six median absolute deviations. Loss must reach 90%, or at least 30% with a 20 percentage-point increase. Each bucket needs two results and six sent packets. Baselines need 30 results across at least 36 buckets, with replies and no more than 10% loss. Recovery needs two normal buckets. Missing evidence is never counted as recovery.

Each cable record lists related country paths or an explicit coverage gap. Geographic association does not verify that traffic traverses the named cable. These are network paths, not verified submarine cable paths. A correlated disruption is not confirmation of a cable break. BGP snapshots and operator reports remain separate supporting evidence.

RIPE collects continuously. HonkWatch evaluates the available public measurements in the background on each corridor’s displayed schedule. This page refreshes saved coverage every five minutes while visible and loads detailed measurements only when selected. Choose a corridor and alert channel under Get network alerts to receive notifications. Times use your browser’s timezone.

Published cable reports

Source-linked reports and recovery notices. Check each report’s date and source.

Loading source reports…

How do we identify a cable break?
  1. Detect a network change. Compare anchor-to-anchor latency, loss, and traceroutes against a normal baseline, using several probes and networks.
  2. Corroborate the disruption. Compare BGP changes and independent reports. A reroute or a failed ping can have other causes; traffic may also reroute successfully after a break.
  3. Confirm the physical fault. Seek a cable operator notice or optical fault-test evidence. An operator’s C-OTDR test can locate a fault along an amplified submarine cable; public internet probes cannot pinpoint the seabed break.

The detection panel automatically compares existing RIPE anchor-mesh history against a baseline. Routing snapshots and news reports support investigation; they do not confirm a physical cable break.

Investigate RIPE anchor mesh · Compare network paths · Optical fault location explained

Loading…Select a report to inspect sources and connected cables.
StatusReport & regionCablesPublishedRecoveryEvidence
Landing places and advanced network tools

Landing places

Reported coastal locations and the cables connected there. Coordinates describe places, not surveyed station buildings.

Advanced network tools

Nearby probe measurements, routing lookups and cable-news searches.

Worldwide public anchors

Select a cable to find nearby public RIPE Atlas anchors.

IPv4 ping measurement 1001 targets k.root-servers.net. It measures reachability to that anycast server; it does not test or identify a specific submarine cable.

Loading public anchor data…

RIPE Atlas measurement documentation

Sources and coverage

The worldwide open catalogue combines OpenStreetMap, Wikidata, and the owner’s existing HonkWatch cable drawings. It includes historical and planned records, and is not an exhaustive commercial cable inventory.

— named systems in the worldwide open catalogue; — have route drawings.

Loading RIPE Atlas public anchors…

Reading routes and checks

Solid lines show available OpenStreetMap sections; dashed lines are schematic connections. An unmapped catalogue record remains searchable. Distances are calculated from the displayed geometry and are not authoritative system lengths.

The route-performance view combines existing RIPE Atlas anchor-to-anchor ping measurements with matching traceroute history. These describe network delay, packet loss and responding IP hops. The advanced nearby-probe tool separately uses measurement 1001 to an anycast DNS server; it does not test a cable. RIPE RIS supplies routing visibility for an ASN or prefix. No new measurements are scheduled, and these observations do not confirm a particular cable’s physical condition or utilisation.

Data and attribution

Catalogue assembled: —
OpenStreetMap contributors · ODbL 1.0
Wikidata structured facts · CC0
Owner-supplied HonkWatch schematic routes
Natural Earth geography · Public domain

Observation panels show source timestamps and fetch failures. News titles link to the original publisher; older events are clearly historical. Saved routes stay in this browser.