https://geocables.comSubmarine cable incidents and latency anomalies detected by the GeoCables measurement network. Honest verdicts: not every anomaly is a fault.enSun, 13 Sep 2026 03:00:01 +0300https://geocables.com/incident/2026091101https://geocables.com/incident/2026091101Fri, 11 Sep 2026 12:03:11 +0300Round-trip time 9ms against a baseline of 10ms. 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. 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 117ms against a baseline of 38ms. 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. 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. 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. 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. 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. 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 315ms against a baseline of 117ms. 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. 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. 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. Resolved 2026-09-06 00: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. Resolved 2026-09-05 12:32 (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. Resolved 2026-09-12 02: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. Resolved 2026-09-09 11:02 (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. 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. Resolved 2026-09-09 12:01 (UTC+3). Measured timeline and evidence on the incident page.https://geocables.com/incident/2026090402https://geocables.com/incident/2026090402Fri, 04 Sep 2026 16:31:57 +0300Round-trip time 229ms against a baseline of 145ms. Resolved 2026-09-06 16:31 (UTC+3). Measured timeline and evidence on the incident page.https://geocables.com/incident/2026090401https://geocables.com/incident/2026090401Fri, 04 Sep 2026 12:31:44 +0300Round-trip time 260ms against a baseline of 181ms. Resolved 2026-09-04 21:03 (UTC+3). Measured timeline and evidence on the incident page.https://geocables.com/incident/2026090201https://geocables.com/incident/2026090201Wed, 02 Sep 2026 15:01:37 +0300Round-trip time 370ms against a baseline of 201ms. Resolved 2026-09-02 17:31 (UTC+3). Measured timeline and evidence on the incident page.https://geocables.com/incident/2026083101https://geocables.com/incident/2026083101Mon, 31 Aug 2026 10:31:17 +0300Round-trip time 41ms against a baseline of 736ms. Resolved 2026-09-01 06:32 (UTC+3). Measured timeline and evidence on the incident page.https://geocables.com/incident/2026082901https://geocables.com/incident/2026082901Sat, 29 Aug 2026 17:01:25 +0300Round-trip time 111ms against a baseline of 115ms. Resolved 2026-08-29 19:30 (UTC+3). Measured timeline and evidence on the incident page.https://geocables.com/incident/2026082701https://geocables.com/incident/2026082701Thu, 27 Aug 2026 05:01:46 +0300Round-trip time 214ms against a baseline of 228ms. Resolved 2026-08-27 07:31 (UTC+3). Measured timeline and evidence on the incident page.https://geocables.com/incident/2026082601https://geocables.com/incident/2026082601Wed, 26 Aug 2026 09:31:41 +0300Round-trip time 78ms against a baseline of 59ms. Resolved 2026-08-27 22:00 (UTC+3). Measured timeline and evidence on the incident page.https://geocables.com/incident/2026082501https://geocables.com/incident/2026082501Tue, 25 Aug 2026 23:01:34 +0300Round-trip time 8ms against a baseline of 10ms. Resolved 2026-08-26 00:32 (UTC+3). Measured timeline and evidence on the incident page.https://geocables.com/incident/2026082301https://geocables.com/incident/2026082301Sun, 23 Aug 2026 22:31:35 +0300Round-trip time 7ms against a baseline of 40ms. Resolved 2026-08-24 00:32 (UTC+3). Measured timeline and evidence on the incident page.https://geocables.com/incident/2026082102https://geocables.com/incident/2026082102Fri, 21 Aug 2026 14:31:44 +0300Round-trip time 12ms against a baseline of 35ms. Resolved 2026-08-21 19:02 (UTC+3). Measured timeline and evidence on the incident page.https://geocables.com/incident/2026082101https://geocables.com/incident/2026082101Fri, 21 Aug 2026 00:02:44 +0300Round-trip time 112ms against a baseline of 326ms. Resolved 2026-08-21 02:32 (UTC+3). Measured timeline and evidence on the incident page.https://geocables.com/incident/2026081901https://geocables.com/incident/2026081901Wed, 19 Aug 2026 03:05:11 +0300Round-trip time 132ms against a baseline of 195ms. Resolved 2026-08-19 05:01 (UTC+3). Measured timeline and evidence on the incident page.https://geocables.com/incident/2026081702https://geocables.com/incident/2026081702Mon, 17 Aug 2026 21:02:25 +0300Round-trip time 181ms against a baseline of 172ms. Resolved 2026-08-18 00:01 (UTC+3). Measured timeline and evidence on the incident page.https://geocables.com/incident/2026081701https://geocables.com/incident/2026081701Mon, 17 Aug 2026 17:02:07 +0300Round-trip time 114ms against a baseline of 292ms. Resolved 2026-08-18 10:01 (UTC+3). Measured timeline and evidence on the incident page.https://geocables.com/incident/2026081502https://geocables.com/incident/2026081502Sat, 15 Aug 2026 23:02:42 +0300Round-trip time 45ms against a baseline of 47ms. Resolved 2026-08-16 01:31 (UTC+3). Measured timeline and evidence on the incident page.https://geocables.com/incident/2026081501https://geocables.com/incident/2026081501Sat, 15 Aug 2026 11:01:45 +0300Round-trip time 14ms against a baseline of 20ms. Resolved 2026-08-21 21:02 (UTC+3). Measured timeline and evidence on the incident page.https://geocables.com/incident/2026081401https://geocables.com/incident/2026081401Fri, 14 Aug 2026 12:31:46 +0300Round-trip time 12ms against a baseline of 33ms. Resolved 2026-08-14 17:02 (UTC+3). Measured timeline and evidence on the incident page.https://geocables.com/incident/2026080601https://geocables.com/incident/2026080601Thu, 06 Aug 2026 21:02:24 +0300Round-trip time 28ms against a baseline of 48ms. Resolved 2026-08-07 00:01 (UTC+3). Measured timeline and evidence on the incident page.https://geocables.com/incident/2026080502https://geocables.com/incident/2026080502Wed, 05 Aug 2026 21:02:05 +0300Round-trip time 30ms against a baseline of 48ms. Resolved 2026-08-05 22:32 (UTC+3). Measured timeline and evidence on the incident page.https://geocables.com/incident/2026080501https://geocables.com/incident/2026080501Wed, 05 Aug 2026 09:32:01 +0300Round-trip time 21ms against a baseline of 20ms. Resolved 2026-08-05 11:32 (UTC+3). Measured timeline and evidence on the incident page.https://geocables.com/incident/2026080201https://geocables.com/incident/2026080201Sun, 02 Aug 2026 23:32:15 +0300Round-trip time 35ms against a baseline of 51ms. Resolved 2026-08-03 02:00 (UTC+3). Measured timeline and evidence on the incident page.https://geocables.com/incident/2026073101https://geocables.com/incident/2026073101Fri, 31 Jul 2026 15:32:01 +0300Round-trip time 231ms against a baseline of 135ms. Resolved 2026-07-31 18:33 (UTC+3). Measured timeline and evidence on the incident page.https://geocables.com/incident/2026073003https://geocables.com/incident/2026073003Thu, 30 Jul 2026 15:02:03 +0300Round-trip time 36ms against a baseline of 71ms. Resolved 2026-07-31 00:02 (UTC+3). Measured timeline and evidence on the incident page.