https://geocables.comSubmarine cable incidents and latency anomalies detected by the GeoCables measurement network. Honest verdicts: not every anomaly is a fault.enSun, 11 Oct 2026 06:15:01 +0300https://geocables.com/incident/2026101101https://geocables.com/incident/2026101101Sun, 11 Oct 2026 03:08:19 +0300Round-trip time 81ms against a baseline of 112ms. Verdict: insufficient_witness_context. Resolved 2026-10-11 06:03 (UTC+3). Measured timeline and evidence on the incident page.https://geocables.com/incident/2026100902https://geocables.com/incident/2026100902Fri, 09 Oct 2026 21:01:48 +0300Round-trip time 103ms against a baseline of 33ms. Verdict: routing_event_non_cable. Measured timeline and evidence on the incident page.https://geocables.com/incident/2026100901https://geocables.com/incident/2026100901Fri, 09 Oct 2026 03:02:05 +0300Round-trip time 8ms against a baseline of 12ms. Verdict: routing_event_non_cable. Resolved 2026-10-09 14:32 (UTC+3). Measured timeline and evidence on the incident page.https://geocables.com/incident/2026100801https://geocables.com/incident/2026100801Thu, 08 Oct 2026 19:01:58 +0300Round-trip time 50ms against a baseline of 25ms. Verdict: widespread. Resolved 2026-10-09 01:02 (UTC+3). Measured timeline and evidence on the incident page.https://geocables.com/incident/2026100701https://geocables.com/incident/2026100701Wed, 07 Oct 2026 09:01:39 +0300Round-trip time 138ms against a baseline of 66ms. Verdict: routing_event_non_cable. Measured timeline and evidence on the incident page.https://geocables.com/incident/2026100602https://geocables.com/incident/2026100602Tue, 06 Oct 2026 17:02:12 +0300Round-trip time 23ms against a baseline of 25ms. Verdict: probe_specific_likely_fp. Resolved 2026-10-07 01:03 (UTC+3). Measured timeline and evidence on the incident page.https://geocables.com/incident/2026100601https://geocables.com/incident/2026100601Tue, 06 Oct 2026 15:31:54 +0300Round-trip time 20ms against a baseline of 20ms. Verdict: insufficient_witness_context. Resolved 2026-10-06 23:02 (UTC+3). Measured timeline and evidence on the incident page.https://geocables.com/incident/2026100101https://geocables.com/incident/2026100101Thu, 01 Oct 2026 10:32:45 +0300Round-trip time 12ms against a baseline of 33ms. Verdict: probe_specific_likely_fp. Resolved 2026-10-01 12:34 (UTC+3). Measured timeline and evidence on the incident page.https://geocables.com/incident/2026093001https://geocables.com/incident/2026093001Wed, 30 Sep 2026 01:31:04 +0300Round-trip time 119ms against a baseline of 128ms. Verdict: insufficient_witness_context. Resolved 2026-09-30 03:03 (UTC+3). Measured timeline and evidence on the incident page.https://geocables.com/incident/2026092903https://geocables.com/incident/2026092903Tue, 29 Sep 2026 21:31:34 +0300Verdict: insufficient_witness_context. Resolved 2026-09-29 23:31 (UTC+3). Measured timeline and evidence on the incident page.https://geocables.com/incident/2026092902https://geocables.com/incident/2026092902Tue, 29 Sep 2026 09:31:32 +0300Verdict: probe_specific_likely_fp. Resolved 2026-09-29 11:32 (UTC+3). Measured timeline and evidence on the incident page.https://geocables.com/incident/2026092901https://geocables.com/incident/2026092901Tue, 29 Sep 2026 01:31:43 +0300Round-trip time 71ms against a baseline of 55ms. Verdict: insufficient_witness_context. Resolved 2026-09-29 04:02 (UTC+3). Measured timeline and evidence on the incident page.https://geocables.com/incident/2026092802https://geocables.com/incident/2026092802Mon, 28 Sep 2026 15:02:41 +0300Round-trip time 11ms against a baseline of 31ms. Verdict: probe_specific_likely_fp. Resolved 2026-09-28 16:32 (UTC+3). Measured timeline and evidence on the incident page.https://geocables.com/incident/2026092801https://geocables.com/incident/2026092801Mon, 28 Sep 2026 09:02:36 +0300Verdict: insufficient_witness_context. Resolved 2026-09-28 11:31 (UTC+3). Measured timeline and evidence on the incident page.https://geocables.com/incident/2026092701https://geocables.com/incident/2026092701Sun, 27 Sep 2026 20:32:02 +0300Verdict: insufficient_witness_context. Resolved 2026-09-27 22:32 (UTC+3). Measured timeline and evidence on the incident page.https://geocables.com/incident/2026092603https://geocables.com/incident/2026092603Sat, 26 Sep 2026 21:02:25 +0300Verdict: probe_specific_likely_fp. Resolved 2026-09-26 23:02 (UTC+3). Measured timeline and evidence on the incident page.https://geocables.com/incident/2026092602https://geocables.com/incident/2026092602Sat, 26 Sep 2026 21:02:23 +0300Round-trip time 216ms against a baseline of 108ms. Verdict: probe_specific_likely_fp. Resolved 2026-09-27 02:34 (UTC+3). Measured timeline and evidence on the incident page.https://geocables.com/incident/2026092601https://geocables.com/incident/2026092601Sat, 26 Sep 2026 09:01:50 +0300Verdict: insufficient_witness_context. Resolved 2026-09-26 21:02 (UTC+3). Measured timeline and evidence on the incident page.https://geocables.com/incident/2026092501https://geocables.com/incident/2026092501Fri, 25 Sep 2026 18:32:29 +0300Round-trip time 11ms against a baseline of 40ms. Verdict: probe_specific_likely_fp. Resolved 2026-09-25 20:32 (UTC+3). Measured timeline and evidence on the incident page.https://geocables.com/incident/2026091901https://geocables.com/incident/2026091901Sat, 19 Sep 2026 17:31:21 +0300Round-trip time 83ms against a baseline of 51ms. Verdict: probe_specific_likely_fp. Resolved 2026-09-19 18:33 (UTC+3). Measured timeline and evidence on the incident page.https://geocables.com/incident/2026091801https://geocables.com/incident/2026091801Fri, 18 Sep 2026 21:31:38 +0300Round-trip time 60ms against a baseline of 63ms. Verdict: probe_specific_likely_fp. Resolved 2026-09-18 23:32 (UTC+3). Measured timeline and evidence on the incident page.https://geocables.com/incident/2026091701https://geocables.com/incident/2026091701Thu, 17 Sep 2026 10:02:30 +0300Round-trip time 16ms against a baseline of 42ms. Verdict: probe_specific_likely_fp. Resolved 2026-09-17 13:02 (UTC+3). Measured timeline and evidence on the incident page.https://geocables.com/incident/2026091601https://geocables.com/incident/2026091601Wed, 16 Sep 2026 12:32:34 +0300Round-trip time 14ms against a baseline of 32ms. Verdict: probe_specific_likely_fp. Resolved 2026-09-16 14:32 (UTC+3). Measured timeline and evidence on the incident page.https://geocables.com/incident/2026091101https://geocables.com/incident/2026091101Fri, 11 Sep 2026 12:03:11 +0300Round-trip time 9ms against a baseline of 10ms. Verdict: insufficient_witness_context. Resolved 2026-09-13 04:06 (UTC+3). Measured timeline and evidence on the incident page.https://geocables.com/incident/2026090903https://geocables.com/incident/2026090903Wed, 09 Sep 2026 19:31:32 +0300Round-trip time 9ms against a baseline of 6ms. Verdict: probe_specific_likely_fp. Resolved 2026-09-10 06:32 (UTC+3). Measured timeline and evidence on the incident page.https://geocables.com/incident/2026090902https://geocables.com/incident/2026090902Wed, 09 Sep 2026 11:31:29 +0300Round-trip time 192ms against a baseline of 38ms. Verdict: insufficient_witness_context. Resolved 2026-09-16 11:32 (UTC+3). Measured timeline and evidence on the incident page.https://geocables.com/incident/2026090901https://geocables.com/incident/2026090901Wed, 09 Sep 2026 10:32:09 +0300Round-trip time 89ms against a baseline of 107ms. Verdict: insufficient_witness_context. Resolved 2026-09-09 20:32 (UTC+3). Measured timeline and evidence on the incident page.https://geocables.com/incident/2026090701https://geocables.com/incident/2026090701Mon, 07 Sep 2026 00:32:30 +0300Round-trip time 35ms against a baseline of 42ms. Verdict: probe_specific_likely_fp. Resolved 2026-09-07 04:32 (UTC+3). Measured timeline and evidence on the incident page.https://geocables.com/incident/2026090510https://geocables.com/incident/2026090510Sat, 05 Sep 2026 21:01:56 +0300Round-trip time 193ms against a baseline of 73ms. Verdict: probe_specific_likely_fp. Resolved 2026-09-12 21:02 (UTC+3). Measured timeline and evidence on the incident page.https://geocables.com/incident/2026090509https://geocables.com/incident/2026090509Sat, 05 Sep 2026 16:32:02 +0300Round-trip time 200ms against a baseline of 115ms. Verdict: insufficient_witness_context. Resolved 2026-09-12 04:03 (UTC+3). Measured timeline and evidence on the incident page.https://geocables.com/incident/2026090508https://geocables.com/incident/2026090508Sat, 05 Sep 2026 11:33:08 +0300Round-trip time 290ms against a baseline of 154ms. Verdict: insufficient_witness_context. Resolved 2026-09-05 16:01 (UTC+3). Measured timeline and evidence on the incident page.https://geocables.com/incident/2026090507https://geocables.com/incident/2026090507Sat, 05 Sep 2026 07:31:22 +0300Round-trip time 168ms against a baseline of 117ms. Verdict: probe_specific_likely_fp. Resolved 2026-09-19 18:01 (UTC+3). Measured timeline and evidence on the incident page.https://geocables.com/incident/2026090506https://geocables.com/incident/2026090506Sat, 05 Sep 2026 07:31:22 +0300Round-trip time 27ms against a baseline of 134ms. Verdict: insufficient_witness_context. Resolved 2026-09-05 20:32 (UTC+3). Measured timeline and evidence on the incident page.https://geocables.com/incident/2026090505https://geocables.com/incident/2026090505Sat, 05 Sep 2026 04:32:21 +0300Round-trip time 14ms against a baseline of 157ms. Verdict: insufficient_witness_context. Resolved 2026-09-05 12:32 (UTC+3). Measured timeline and evidence on the incident page.https://geocables.com/incident/2026090504https://geocables.com/incident/2026090504Sat, 05 Sep 2026 04:32:19 +0300Round-trip time 189ms against a baseline of 129ms. Verdict: routing_event_non_cable. Resolved 2026-09-06 00:01 (UTC+3). Measured timeline and evidence on the incident page.https://geocables.com/incident/2026090501https://geocables.com/incident/2026090501Sat, 05 Sep 2026 01:31:46 +0300Round-trip time 256ms against a baseline of 156ms. Verdict: probe_specific_likely_fp. Resolved 2026-09-09 11:02 (UTC+3). Measured timeline and evidence on the incident page.https://geocables.com/incident/2026090502https://geocables.com/incident/2026090502Sat, 05 Sep 2026 01:31:46 +0300Round-trip time 315ms against a baseline of 118ms. Verdict: insufficient_witness_context. Resolved 2026-09-12 02:01 (UTC+3). Measured timeline and evidence on the incident page.https://geocables.com/incident/2026090503https://geocables.com/incident/2026090503Sat, 05 Sep 2026 01:31:46 +0300Round-trip time 106ms against a baseline of 153ms. Verdict: insufficient_witness_context. Resolved 2026-09-05 12:32 (UTC+3). Measured timeline and evidence on the incident page.https://geocables.com/incident/2026090404https://geocables.com/incident/2026090404Fri, 04 Sep 2026 23:02:19 +0300Round-trip time 192ms against a baseline of 87ms. Verdict: probe_specific_likely_fp. Resolved 2026-09-11 23:02 (UTC+3). Measured timeline and evidence on the incident page.https://geocables.com/incident/2026090403https://geocables.com/incident/2026090403Fri, 04 Sep 2026 16:31:57 +0300Round-trip time 262ms against a baseline of 138ms. Verdict: probe_specific_likely_fp. Resolved 2026-09-09 12:01 (UTC+3). Measured timeline and evidence on the incident page.