GeoCables internet latency, routing events and route stretch

Version 2026-09. Latency observations 2026-06-02 to 2026-09-23; route stretch window 2026-09-06 to 2026-09-23. GeoCables (https://geocables.com) is an independent monitor of internet connectivity and submarine cables. It runs traceroutes around the clock from its own distributed network of measurement points, several of them in Central Asia, the Caucasus and Eastern Europe, regions that are under-represented in public measurement datasets. This record is a frozen, citable snapshot. The live dataset is updated daily at https://geocables.com/dataset and covers only a recent window; each version here contains the full history up to its cut-off date. geocables-latency-daily.csv Round-trip latency from our measurement points to targets, aggregated per day and per measurement-point and target pair. geocables-route-events.csv Routing events detected from the same measurements: latency spikes on a hop, detours, path changes and recoveries. description is free text with IP addresses replaced by [ip]. cable_name and cable_page are set when the event was associated with a submarine cable. geocables-route-stretch.csv Route stretch for every measurement-point and target pair with at least five successful traceroutes in the window and more than 100 km between them. This file is the data behind the article "Closer is not faster: route stretch between Central and South Asia". Pairs whose best time is more than 10% below the physical floor are excluded: that can only mean the target's geolocation is wrong. The minimum rather than the mean is used because queueing only ever adds delay. manifest.json Row counts, sizes and SHA-256 checksums of the files. Method and caveats Measurements are traceroutes (UDP by default, ICMP where only mtr is available, one probe per hop, up to 20 hops) run on a fixed schedule against a rotating list of targets that have answered before. Target locations come from city-level IP geolocation and are cross-checked against the operator at the end of the path. Router locations along a path are not published because IP geolocation of transit routers is often wrong. A round trip includes the return path, which may differ from the forward path. IP addresses of measurement points, routers and targets are deliberately omitted. Cable names are labels only. The cable inventory itself is not redistributed. Methodology: https://geocables.com/methodology Licence and citation Creative Commons Attribution 4.0 International (CC BY 4.0). Please cite this record by its DOI and credit GeoCables with a link to https://geocables.com. Also available, updated daily: https://geocables.com/dataset, Hugging Face (geocables/internet-latency-and-routing-events), Kaggle (geocables/geocables-internet-latency-and-routing-events). Column definitions are in README.md inside this record.