Outage tracker
Every outage event we have retracted after finding the original reading was wrong, listed here for as long as this tracker exists. We do not quietly delete a bad verdict; we publish what we claimed, why it was wrong, and when we fixed it.
What we originally claimed: We reported a partial outage for this service. Started Sep 6, 2026, 10:20 AM UTC, ended Sep 6, 2026, 11:09 AM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 5, 2026, 8:53 PM UTC, ended Sep 5, 2026, 9:52 PM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 5, 2026, 8:53 PM UTC, ended Sep 6, 2026, 4:53 AM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 3, 2026, 7:22 PM UTC, ended Sep 3, 2026, 7:42 PM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 5, 2026, 3:47 AM UTC, ended Sep 5, 2026, 4:07 AM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 6, 2026, 5:00 PM UTC, ended Sep 6, 2026, 5:30 PM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 5, 2026, 3:49 AM UTC, ended Sep 5, 2026, 4:09 AM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 6, 2026, 4:44 PM UTC, ended Sep 6, 2026, 7:36 PM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 5, 2026, 3:49 AM UTC, ended Sep 5, 2026, 4:09 AM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 5, 2026, 8:13 PM UTC, ended Sep 6, 2026, 4:52 AM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 5, 2026, 3:29 AM UTC, ended Sep 5, 2026, 4:10 AM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 6, 2026, 10:12 AM UTC, ended Sep 6, 2026, 11:06 AM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 5, 2026, 7:56 PM UTC, ended Sep 6, 2026, 4:56 AM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 5, 2026, 3:50 AM UTC, ended Sep 5, 2026, 4:10 AM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 3, 2026, 7:10 PM UTC, ended Sep 3, 2026, 7:38 PM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 5, 2026, 8:47 PM UTC, ended Sep 6, 2026, 4:18 AM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 5, 2026, 3:31 AM UTC, ended Sep 5, 2026, 3:55 AM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 5, 2026, 8:47 PM UTC, ended Sep 6, 2026, 4:19 AM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 5, 2026, 3:30 AM UTC, ended Sep 5, 2026, 3:55 AM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 3, 2026, 7:20 PM UTC, ended Sep 3, 2026, 7:40 PM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 5, 2026, 3:50 AM UTC, ended Sep 5, 2026, 4:10 AM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 8, 2026, 9:53 PM UTC, ended Sep 8, 2026, 10:41 PM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 5, 2026, 3:49 AM UTC, ended Sep 5, 2026, 4:09 AM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 6, 2026, 4:51 PM UTC, ended Sep 6, 2026, 7:40 PM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 3, 2026, 7:11 PM UTC, ended Sep 3, 2026, 7:36 PM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 8, 2026, 9:55 PM UTC, ended Sep 8, 2026, 10:55 PM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 6, 2026, 10:25 AM UTC, ended Sep 6, 2026, 11:08 AM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 6, 2026, 10:13 AM UTC, ended Sep 6, 2026, 11:11 AM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 5, 2026, 3:41 AM UTC, ended Sep 5, 2026, 4:18 AM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 3, 2026, 7:08 PM UTC, ended Sep 3, 2026, 7:36 PM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 5, 2026, 3:34 AM UTC, ended Sep 5, 2026, 3:55 AM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 5, 2026, 3:40 AM UTC, ended Sep 5, 2026, 4:01 AM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 6, 2026, 10:00 AM UTC, ended Sep 6, 2026, 11:02 AM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 8, 2026, 8:43 AM UTC, ended Sep 8, 2026, 9:44 AM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 8, 2026, 10:37 PM UTC, ended Sep 8, 2026, 11:37 PM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 3, 2026, 7:17 PM UTC, ended Sep 3, 2026, 7:38 PM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 5, 2026, 3:49 AM UTC, ended Sep 5, 2026, 4:09 AM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 5, 2026, 3:41 AM UTC, ended Sep 5, 2026, 4:02 AM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 5, 2026, 3:49 AM UTC, ended Sep 5, 2026, 4:09 AM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 5, 2026, 3:31 AM UTC, ended Sep 5, 2026, 3:55 AM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 5, 2026, 3:50 AM UTC, ended Sep 5, 2026, 4:10 AM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 6, 2026, 9:07 AM UTC, ended Sep 6, 2026, 10:48 AM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 8, 2026, 9:55 PM UTC, ended Sep 8, 2026, 10:55 PM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 5, 2026, 8:58 PM UTC, ended Sep 6, 2026, 4:58 AM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported an outage for this service. Started Sep 8, 2026, 8:45 PM UTC, ended Sep 8, 2026, 11:09 PM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 5, 2026, 7:58 PM UTC, ended Sep 6, 2026, 4:58 AM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 22, 2026, 1:19 AM UTC, ended Sep 22, 2026, 3:15 AM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 5, 2026, 7:59 PM UTC, ended Sep 6, 2026, 4:59 AM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 5, 2026, 9:09 PM UTC, ended Sep 6, 2026, 5:08 AM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 5, 2026, 7:59 PM UTC, ended Sep 6, 2026, 4:59 AM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 5, 2026, 9:23 PM UTC, ended Sep 6, 2026, 5:09 AM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 5, 2026, 8:21 PM UTC, ended Sep 6, 2026, 5:09 AM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 6, 2026, 3:59 PM UTC, ended Sep 6, 2026, 7:20 PM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 6, 2026, 4:42 PM UTC, ended Sep 6, 2026, 7:36 PM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 5, 2026, 8:01 PM UTC, ended Sep 6, 2026, 5:01 AM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 6, 2026, 5:00 PM UTC, ended Sep 6, 2026, 5:40 PM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 6, 2026, 3:50 PM UTC, ended Sep 6, 2026, 7:31 PM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 6, 2026, 9:42 AM UTC, ended Sep 6, 2026, 11:01 AM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 10, 2026, 5:45 PM UTC, ended Sep 10, 2026, 6:05 PM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 5, 2026, 8:14 PM UTC, ended Sep 6, 2026, 4:49 AM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 6, 2026, 5:00 PM UTC, ended Sep 6, 2026, 5:37 PM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 6, 2026, 9:10 AM UTC, ended Sep 6, 2026, 10:50 AM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 6, 2026, 4:00 PM UTC, ended Sep 6, 2026, 7:21 PM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 6, 2026, 4:52 PM UTC, ended Sep 6, 2026, 7:50 PM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 6, 2026, 10:10 AM UTC, ended Sep 6, 2026, 11:09 AM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 6, 2026, 10:10 AM UTC, ended Sep 6, 2026, 11:10 AM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 5, 2026, 8:25 PM UTC, ended Sep 6, 2026, 5:24 AM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 6, 2026, 9:58 AM UTC, ended Sep 6, 2026, 10:58 AM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 6, 2026, 3:30 PM UTC, ended Sep 6, 2026, 7:33 PM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 6, 2026, 9:42 AM UTC, ended Sep 6, 2026, 11:02 AM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 6, 2026, 9:58 AM UTC, ended Sep 6, 2026, 10:58 AM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 6, 2026, 9:23 AM UTC, ended Sep 6, 2026, 11:03 AM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 6, 2026, 3:30 PM UTC, ended Sep 6, 2026, 7:33 PM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 6, 2026, 4:06 PM UTC, ended Sep 6, 2026, 7:27 PM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 5, 2026, 9:09 PM UTC, ended Sep 6, 2026, 5:07 AM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 6, 2026, 9:59 AM UTC, ended Sep 6, 2026, 10:58 AM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 6, 2026, 9:23 AM UTC, ended Sep 6, 2026, 10:55 AM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 6, 2026, 9:59 AM UTC, ended Sep 6, 2026, 10:59 AM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 21, 2026, 10:19 PM UTC, ended Sep 21, 2026, 11:18 PM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 6, 2026, 9:11 AM UTC, ended Sep 6, 2026, 10:54 AM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported an outage for this service. Started Sep 8, 2026, 8:45 PM UTC, ended Sep 8, 2026, 11:16 PM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 6, 2026, 3:58 PM UTC, ended Sep 6, 2026, 7:19 PM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 6, 2026, 9:27 AM UTC, ended Sep 6, 2026, 10:48 AM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 6, 2026, 4:52 PM UTC, ended Sep 6, 2026, 7:52 PM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 6, 2026, 9:27 AM UTC, ended Sep 6, 2026, 10:48 AM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 6, 2026, 5:02 PM UTC, ended Sep 6, 2026, 5:34 PM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 6, 2026, 9:06 AM UTC, ended Sep 6, 2026, 10:48 AM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 6, 2026, 9:40 AM UTC, ended Sep 6, 2026, 11:00 AM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 8, 2026, 9:07 AM UTC, ended Sep 8, 2026, 9:27 AM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 8, 2026, 6:43 PM UTC, ended Sep 8, 2026, 7:03 PM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 6, 2026, 9:24 AM UTC, ended Sep 6, 2026, 11:07 AM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 6, 2026, 10:12 AM UTC, ended Sep 6, 2026, 11:09 AM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 5, 2026, 8:17 PM UTC, ended Sep 6, 2026, 4:57 AM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 6, 2026, 9:27 AM UTC, ended Sep 6, 2026, 10:50 AM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 9, 2026, 6:57 AM UTC, ended Sep 9, 2026, 7:51 AM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 8, 2026, 9:46 PM UTC, ended Sep 8, 2026, 10:40 PM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 5, 2026, 8:18 PM UTC, ended Sep 5, 2026, 10:04 PM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 8, 2026, 8:44 PM UTC, ended Sep 8, 2026, 10:44 PM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 10, 2026, 5:44 PM UTC, ended Sep 10, 2026, 6:04 PM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 8, 2026, 6:24 PM UTC, ended Sep 8, 2026, 7:04 PM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 5, 2026, 9:06 PM UTC, ended Sep 6, 2026, 5:06 AM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 5, 2026, 9:07 PM UTC, ended Sep 6, 2026, 5:06 AM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 5, 2026, 9:07 PM UTC, ended Sep 6, 2026, 5:06 AM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 8, 2026, 8:41 AM UTC, ended Sep 8, 2026, 9:26 AM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 8, 2026, 8:53 AM UTC, ended Sep 8, 2026, 9:33 AM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 6, 2026, 9:05 AM UTC, ended Sep 6, 2026, 10:46 AM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 5, 2026, 9:09 PM UTC, ended Sep 6, 2026, 5:06 AM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 6, 2026, 3:50 PM UTC, ended Sep 6, 2026, 7:31 PM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 6, 2026, 3:36 PM UTC, ended Sep 6, 2026, 7:16 PM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 6, 2026, 3:32 PM UTC, ended Sep 6, 2026, 7:16 PM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 5, 2026, 9:11 PM UTC, ended Sep 6, 2026, 5:08 AM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 9, 2026, 6:52 AM UTC, ended Sep 9, 2026, 7:33 AM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 6, 2026, 3:50 PM UTC, ended Sep 6, 2026, 7:31 PM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 8, 2026, 9:05 AM UTC, ended Sep 8, 2026, 9:26 AM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 8, 2026, 9:14 AM UTC, ended Sep 8, 2026, 9:34 AM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 6, 2026, 3:36 PM UTC, ended Sep 6, 2026, 7:17 PM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 8, 2026, 6:34 PM UTC, ended Sep 8, 2026, 6:54 PM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 5, 2026, 8:05 PM UTC, ended Sep 6, 2026, 4:59 AM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported an outage for this service. Started Sep 8, 2026, 8:25 PM UTC, ended Sep 8, 2026, 11:11 PM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 6, 2026, 4:13 PM UTC, ended Sep 6, 2026, 6:12 PM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 8, 2026, 8:44 AM UTC, ended Sep 8, 2026, 9:28 AM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 8, 2026, 9:58 PM UTC, ended Sep 8, 2026, 10:40 PM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 6, 2026, 3:38 PM UTC, ended Sep 6, 2026, 7:21 PM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 6, 2026, 9:41 AM UTC, ended Sep 6, 2026, 11:00 AM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 6, 2026, 9:13 AM UTC, ended Sep 6, 2026, 10:46 AM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 6, 2026, 4:01 PM UTC, ended Sep 6, 2026, 7:22 PM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 5, 2026, 8:04 PM UTC, ended Sep 6, 2026, 4:55 AM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 9, 2026, 6:49 AM UTC, ended Sep 9, 2026, 7:21 AM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 6, 2026, 9:56 AM UTC, ended Sep 6, 2026, 10:52 AM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 10, 2026, 1:56 AM UTC, ended Sep 10, 2026, 2:35 AM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 8, 2026, 9:01 AM UTC, ended Sep 8, 2026, 9:41 AM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 8, 2026, 9:01 AM UTC, ended Sep 8, 2026, 9:41 AM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 5, 2026, 9:19 PM UTC, ended Sep 6, 2026, 5:08 AM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 8, 2026, 9:01 AM UTC, ended Sep 8, 2026, 9:42 AM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 5, 2026, 7:45 PM UTC, ended Sep 6, 2026, 4:46 AM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 5, 2026, 7:48 PM UTC, ended Sep 6, 2026, 4:50 AM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 8, 2026, 8:42 AM UTC, ended Sep 8, 2026, 9:26 AM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 5, 2026, 8:15 PM UTC, ended Sep 6, 2026, 4:51 AM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported an outage for this service. Started Sep 8, 2026, 8:34 PM UTC, ended Sep 8, 2026, 11:01 PM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 10, 2026, 1:52 AM UTC, ended Sep 10, 2026, 2:31 AM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 6, 2026, 3:50 PM UTC, ended Sep 6, 2026, 7:31 PM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 8, 2026, 9:11 AM UTC, ended Sep 8, 2026, 9:31 AM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 8, 2026, 9:12 AM UTC, ended Sep 8, 2026, 9:32 AM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 8, 2026, 6:43 PM UTC, ended Sep 8, 2026, 7:03 PM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 8, 2026, 6:43 PM UTC, ended Sep 8, 2026, 7:03 PM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 8, 2026, 9:55 PM UTC, ended Sep 8, 2026, 10:28 PM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 10, 2026, 1:54 AM UTC, ended Sep 10, 2026, 2:34 AM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 10, 2026, 5:49 PM UTC, ended Sep 10, 2026, 6:09 PM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 9, 2026, 7:10 AM UTC, ended Sep 9, 2026, 7:31 AM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 6, 2026, 2:27 AM UTC, ended Sep 6, 2026, 5:54 AM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 6, 2026, 5:07 PM UTC, ended Sep 6, 2026, 6:07 PM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 6, 2026, 3:36 PM UTC, ended Sep 6, 2026, 7:17 PM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 12, 2026, 10:02 AM UTC, ended Sep 12, 2026, 2:02 PM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 8, 2026, 6:47 PM UTC, ended Sep 8, 2026, 7:07 PM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 9, 2026, 7:13 AM UTC, ended Sep 9, 2026, 7:33 AM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 26, 2026, 3:37 AM UTC, ended Sep 26, 2026, 4:21 AM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 10, 2026, 2:03 AM UTC, ended Sep 10, 2026, 2:23 AM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 9, 2026, 6:55 AM UTC, ended Sep 9, 2026, 7:21 AM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported an outage for this service. Started Sep 13, 2026, 2:58 PM UTC, ended Sep 13, 2026, 6:14 PM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 8, 2026, 6:27 PM UTC, ended Sep 8, 2026, 6:55 PM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 6, 2026, 3:59 PM UTC, ended Sep 6, 2026, 7:19 PM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 5, 2026, 7:40 PM UTC, ended Sep 6, 2026, 5:00 AM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 10, 2026, 1:57 AM UTC, ended Sep 10, 2026, 2:17 AM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 5, 2026, 7:40 PM UTC, ended Sep 6, 2026, 4:49 AM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 8, 2026, 6:44 PM UTC, ended Sep 8, 2026, 7:04 PM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 8, 2026, 6:27 PM UTC, ended Sep 8, 2026, 6:55 PM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported an outage for this service. Started Sep 8, 2026, 8:52 PM UTC, ended Sep 8, 2026, 11:11 PM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 8, 2026, 6:45 PM UTC, ended Sep 8, 2026, 7:05 PM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 5, 2026, 8:13 PM UTC, ended Sep 6, 2026, 4:54 AM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 5, 2026, 7:39 PM UTC, ended Sep 6, 2026, 4:45 AM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 10, 2026, 2:08 AM UTC, ended Sep 10, 2026, 2:28 AM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 8, 2026, 6:46 PM UTC, ended Sep 8, 2026, 7:06 PM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 6, 2026, 9:58 AM UTC, ended Sep 6, 2026, 10:58 AM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 6, 2026, 9:42 AM UTC, ended Sep 6, 2026, 10:58 AM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 6, 2026, 9:02 AM UTC, ended Sep 6, 2026, 11:00 AM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 10, 2026, 1:55 AM UTC, ended Sep 10, 2026, 2:34 AM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 8, 2026, 9:45 PM UTC, ended Sep 8, 2026, 10:40 PM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 8, 2026, 8:47 PM UTC, ended Sep 8, 2026, 10:41 PM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 6, 2026, 3:44 PM UTC, ended Sep 6, 2026, 7:40 PM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 6, 2026, 4:44 PM UTC, ended Sep 6, 2026, 7:40 PM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 10, 2026, 5:33 PM UTC, ended Sep 10, 2026, 6:13 PM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 9, 2026, 7:12 AM UTC, ended Sep 9, 2026, 7:33 AM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported an outage for this service. Started Sep 8, 2026, 8:54 PM UTC, ended Sep 8, 2026, 11:15 PM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported an outage for this service. Started Sep 8, 2026, 8:34 PM UTC, ended Sep 8, 2026, 11:03 PM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 8, 2026, 9:11 AM UTC, ended Sep 8, 2026, 9:31 AM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 5, 2026, 7:42 PM UTC, ended Sep 6, 2026, 4:47 AM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 8, 2026, 9:11 AM UTC, ended Sep 8, 2026, 9:32 AM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 10, 2026, 5:50 PM UTC, ended Sep 10, 2026, 6:10 PM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 6, 2026, 3:53 PM UTC, ended Sep 6, 2026, 7:14 PM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 8, 2026, 9:11 AM UTC, ended Sep 8, 2026, 9:32 AM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 9, 2026, 6:53 AM UTC, ended Sep 9, 2026, 7:21 AM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 8, 2026, 9:01 AM UTC, ended Sep 8, 2026, 9:42 AM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 8, 2026, 8:41 AM UTC, ended Sep 8, 2026, 9:26 AM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 8, 2026, 9:01 AM UTC, ended Sep 8, 2026, 9:42 AM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 8, 2026, 9:01 AM UTC, ended Sep 8, 2026, 9:42 AM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 8, 2026, 9:04 AM UTC, ended Sep 8, 2026, 9:45 AM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 8, 2026, 6:34 PM UTC, ended Sep 8, 2026, 6:54 PM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 8, 2026, 6:29 PM UTC, ended Sep 8, 2026, 6:54 PM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 5, 2026, 8:00 PM UTC, ended Sep 6, 2026, 5:00 AM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
What we originally claimed: We reported a partial outage for this service. Started Sep 10, 2026, 5:34 PM UTC, ended Sep 10, 2026, 6:14 PM UTC.
Why it was retracted: One of our probe regions lost part of its own network path and reported failures for many unrelated services that every other region was reaching. This event did not happen and has been removed.
Every retraction here follows the same rule described on how this check works: a reading only ever gets retracted when we find concrete evidence the original verdict was wrong, never when a vendor simply disputes it.