Outage tracker
Every probe event we have retracted, listed here for as long as this tracker exists. We do not quietly delete an event; we keep it and publish what we showed, why we retracted it, and when.
What we originally showed: We reported a partial outage for this service. Started Aug 22, 2026, 4:31 PM UTC, ended Aug 22, 2026, 5:01 PM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Aug 22, 2026, 9:09 PM UTC, ended Aug 22, 2026, 10:11 PM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Aug 22, 2026, 11:43 PM UTC, ended Aug 23, 2026, 12:13 AM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Aug 23, 2026, 10:15 PM UTC, ended Aug 23, 2026, 11:15 PM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Aug 24, 2026, 11:35 PM UTC, ended Aug 25, 2026, 12:35 AM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Aug 26, 2026, 7:30 PM UTC, ended Aug 26, 2026, 7:41 PM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Aug 28, 2026, 9:10 AM UTC, ended Aug 28, 2026, 9:42 AM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Aug 28, 2026, 4:29 PM UTC, ended Aug 28, 2026, 4:39 PM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Aug 29, 2026, 10:22 PM UTC, ended Aug 29, 2026, 10:54 PM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Aug 30, 2026, 5:13 PM UTC, ended Aug 30, 2026, 5:43 PM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Aug 31, 2026, 1:34 AM UTC, ended Aug 31, 2026, 2:04 AM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Aug 31, 2026, 12:15 PM UTC, ended Aug 31, 2026, 12:46 PM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Aug 31, 2026, 5:30 PM UTC, ended Aug 31, 2026, 6:31 PM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Sep 1, 2026, 2:51 AM UTC, ended Sep 1, 2026, 3:22 AM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Sep 1, 2026, 5:09 PM UTC, ended Sep 1, 2026, 5:39 PM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Sep 1, 2026, 10:04 PM UTC, ended Sep 1, 2026, 10:07 PM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Sep 2, 2026, 6:07 AM UTC, ended Sep 2, 2026, 6:17 AM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Sep 3, 2026, 10:37 AM UTC, ended Sep 3, 2026, 10:54 AM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Sep 3, 2026, 6:48 PM UTC, ended Sep 3, 2026, 11:21 PM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Sep 4, 2026, 12:21 AM UTC, ended Sep 4, 2026, 2:07 AM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Sep 4, 2026, 3:09 AM UTC, ended Sep 4, 2026, 6:11 AM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Sep 4, 2026, 4:33 AM UTC, ended Sep 4, 2026, 5:03 AM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Sep 4, 2026, 9:13 AM UTC, ended Sep 4, 2026, 9:55 AM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Sep 4, 2026, 11:57 AM UTC, ended Sep 4, 2026, 1:21 PM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Sep 4, 2026, 7:09 PM UTC, ended Sep 4, 2026, 8:33 PM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Sep 4, 2026, 10:57 PM UTC, ended Sep 4, 2026, 11:59 PM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Sep 5, 2026, 2:01 AM UTC, ended Sep 5, 2026, 2:22 AM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Sep 5, 2026, 4:26 AM UTC, ended Sep 5, 2026, 5:26 AM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Sep 5, 2026, 7:30 AM UTC, ended Sep 5, 2026, 7:32 AM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Sep 5, 2026, 7:57 AM UTC, ended Sep 5, 2026, 10:43 AM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Sep 5, 2026, 11:53 AM UTC, ended Sep 5, 2026, 12:55 PM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Sep 5, 2026, 12:04 PM UTC, ended Sep 5, 2026, 12:26 PM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Sep 5, 2026, 2:27 PM UTC, ended Sep 5, 2026, 4:09 PM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Sep 5, 2026, 6:11 PM UTC, ended Sep 5, 2026, 6:33 PM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Sep 6, 2026, 1:00 AM UTC, ended Sep 6, 2026, 1:04 AM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Sep 6, 2026, 5:09 AM UTC, ended Sep 6, 2026, 5:38 AM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Sep 6, 2026, 11:04 AM UTC, ended Sep 6, 2026, 11:51 AM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Sep 6, 2026, 11:42 AM UTC, ended Sep 6, 2026, 12:03 PM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Sep 6, 2026, 1:03 PM UTC, ended Sep 6, 2026, 3:50 PM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Sep 6, 2026, 5:50 PM UTC, ended Sep 7, 2026, 2:01 AM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Sep 7, 2026, 8:00 AM UTC, ended Sep 7, 2026, 9:01 AM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Sep 7, 2026, 11:58 AM UTC, ended Sep 7, 2026, 12:08 PM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Sep 7, 2026, 1:03 PM UTC, ended Sep 7, 2026, 4:05 PM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Sep 7, 2026, 5:59 PM UTC, ended Sep 7, 2026, 6:09 PM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Sep 7, 2026, 6:25 PM UTC, ended Sep 7, 2026, 6:47 PM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Sep 7, 2026, 6:46 PM UTC, ended Sep 7, 2026, 7:36 PM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Sep 7, 2026, 7:48 PM UTC, ended Sep 7, 2026, 11:33 PM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Sep 8, 2026, 12:36 AM UTC, ended Sep 8, 2026, 12:57 AM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Sep 8, 2026, 2:39 AM UTC, ended Sep 8, 2026, 3:01 AM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Sep 8, 2026, 3:24 AM UTC, ended Sep 8, 2026, 4:09 AM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Sep 8, 2026, 5:07 AM UTC, ended Sep 8, 2026, 5:55 AM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Sep 8, 2026, 6:21 AM UTC, ended Sep 8, 2026, 7:42 AM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported an outage for this service. Started Sep 8, 2026, 7:05 AM UTC, ended Sep 8, 2026, 7:10 AM UTC.
Why it was retracted: Our checks failed only from check regions on one continent. We need checks to fail from two continents before we call an outage, so we no longer present it as one.
What we originally showed: We reported an outage for this service. Started Sep 8, 2026, 7:13 AM UTC, ended Sep 8, 2026, 5:41 PM UTC.
Why it was retracted: This event stayed open for more than 6 hours with no incident declared by the service behind it. Our checks alone are not enough to keep an outage standing that long, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Sep 8, 2026, 10:25 AM UTC, ended Sep 8, 2026, 10:35 AM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Sep 8, 2026, 11:24 AM UTC, ended Sep 8, 2026, 1:05 PM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Sep 8, 2026, 2:45 PM UTC, ended Sep 8, 2026, 3:05 PM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Sep 8, 2026, 4:25 PM UTC, ended Sep 8, 2026, 5:05 PM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Sep 8, 2026, 6:25 PM UTC, ended Sep 8, 2026, 7:05 PM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Sep 8, 2026, 9:45 PM UTC, ended Sep 8, 2026, 10:46 PM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Sep 9, 2026, 12:47 AM UTC, ended Sep 9, 2026, 1:20 AM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Sep 9, 2026, 3:49 AM UTC, ended Sep 9, 2026, 4:48 AM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Sep 9, 2026, 7:09 AM UTC, ended Sep 9, 2026, 7:58 AM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Sep 9, 2026, 7:10 AM UTC, ended Sep 9, 2026, 7:30 AM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Sep 9, 2026, 8:52 AM UTC, ended Sep 9, 2026, 9:32 AM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Sep 9, 2026, 10:54 AM UTC, ended Sep 9, 2026, 11:51 AM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Sep 9, 2026, 12:54 PM UTC, ended Sep 9, 2026, 1:52 PM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Sep 9, 2026, 10:37 PM UTC, ended Sep 9, 2026, 10:58 PM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Sep 9, 2026, 10:59 PM UTC, ended Sep 9, 2026, 11:04 PM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Sep 10, 2026, 12:17 AM UTC, ended Sep 10, 2026, 12:58 AM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Sep 10, 2026, 2:03 AM UTC, ended Sep 10, 2026, 2:43 AM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Sep 10, 2026, 5:19 AM UTC, ended Sep 10, 2026, 5:59 AM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Sep 10, 2026, 10:44 AM UTC, ended Sep 10, 2026, 11:04 AM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Sep 10, 2026, 1:04 PM UTC, ended Sep 10, 2026, 1:45 PM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Sep 10, 2026, 3:05 PM UTC, ended Sep 10, 2026, 3:25 PM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Sep 11, 2026, 3:47 AM UTC, ended Sep 11, 2026, 4:46 AM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Sep 11, 2026, 3:48 AM UTC, ended Sep 11, 2026, 4:09 AM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Sep 11, 2026, 5:50 AM UTC, ended Sep 11, 2026, 6:11 AM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Sep 11, 2026, 7:51 AM UTC, ended Sep 11, 2026, 8:32 AM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Sep 11, 2026, 7:52 AM UTC, ended Sep 11, 2026, 8:13 AM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Sep 11, 2026, 3:48 PM UTC, ended Sep 11, 2026, 3:58 PM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Sep 11, 2026, 5:01 PM UTC, ended Sep 11, 2026, 5:21 PM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Sep 11, 2026, 6:21 PM UTC, ended Sep 11, 2026, 7:22 PM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Sep 12, 2026, 12:56 AM UTC, ended Sep 12, 2026, 2:47 AM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Sep 12, 2026, 4:56 AM UTC, ended Sep 12, 2026, 5:48 AM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Sep 12, 2026, 8:08 AM UTC, ended Sep 12, 2026, 9:28 AM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Sep 12, 2026, 11:01 AM UTC, ended Sep 12, 2026, 11:11 AM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Sep 12, 2026, 2:11 PM UTC, ended Sep 12, 2026, 3:47 PM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Sep 12, 2026, 9:27 PM UTC, ended Sep 12, 2026, 9:31 PM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Sep 13, 2026, 10:42 AM UTC, ended Sep 13, 2026, 11:22 AM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Sep 13, 2026, 5:50 PM UTC, ended Sep 13, 2026, 6:50 PM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Sep 13, 2026, 9:42 PM UTC, ended Sep 13, 2026, 10:23 PM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Sep 14, 2026, 1:50 AM UTC, ended Sep 14, 2026, 4:48 AM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Sep 14, 2026, 5:25 AM UTC, ended Sep 14, 2026, 5:45 AM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Sep 14, 2026, 8:46 AM UTC, ended Sep 14, 2026, 9:46 AM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Sep 14, 2026, 10:46 AM UTC, ended Sep 14, 2026, 11:06 AM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Sep 14, 2026, 11:16 AM UTC, ended Sep 14, 2026, 12:00 PM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Sep 14, 2026, 11:21 AM UTC, ended Sep 14, 2026, 11:31 AM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Sep 14, 2026, 1:27 PM UTC, ended Sep 14, 2026, 1:48 PM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Sep 14, 2026, 6:50 PM UTC, ended Sep 14, 2026, 8:48 PM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Sep 15, 2026, 1:50 AM UTC, ended Sep 15, 2026, 2:11 AM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Sep 15, 2026, 8:31 AM UTC, ended Sep 15, 2026, 9:11 AM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Sep 15, 2026, 10:11 AM UTC, ended Sep 15, 2026, 10:31 AM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Sep 15, 2026, 7:52 PM UTC, ended Sep 15, 2026, 8:31 PM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported an outage for this service. Started Sep 16, 2026, 12:36 AM UTC, ended Sep 16, 2026, 8:59 AM UTC.
Why it was retracted: This event stayed open for more than 6 hours with no incident declared by the service behind it. Our checks alone are not enough to keep an outage standing that long, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Sep 16, 2026, 10:19 AM UTC, ended Sep 16, 2026, 11:39 AM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Sep 16, 2026, 2:39 PM UTC, ended Sep 16, 2026, 3:19 PM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Sep 16, 2026, 4:19 PM UTC, ended Sep 16, 2026, 4:59 PM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Sep 16, 2026, 10:43 PM UTC, ended Sep 17, 2026, 1:23 AM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Sep 17, 2026, 3:24 AM UTC, ended Sep 17, 2026, 4:05 AM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Sep 17, 2026, 6:06 AM UTC, ended Sep 17, 2026, 7:07 AM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported an outage for this service. Started Sep 17, 2026, 8:08 AM UTC, ended Sep 17, 2026, 9:46 AM UTC.
Why it was retracted: Our checks failed only from check regions on one continent. We need checks to fail from two continents before we call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Sep 17, 2026, 9:12 PM UTC, ended Sep 17, 2026, 9:32 PM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Sep 18, 2026, 12:02 AM UTC, ended Sep 18, 2026, 1:58 AM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Sep 18, 2026, 3:14 AM UTC, ended Sep 18, 2026, 3:33 AM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Sep 18, 2026, 9:52 AM UTC, ended Sep 18, 2026, 10:50 AM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Sep 18, 2026, 4:18 PM UTC, ended Sep 18, 2026, 4:28 PM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Sep 18, 2026, 5:57 PM UTC, ended Sep 18, 2026, 6:38 PM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Sep 18, 2026, 11:07 PM UTC, ended Sep 18, 2026, 11:27 PM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Sep 18, 2026, 11:18 PM UTC, ended Sep 18, 2026, 11:38 PM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Sep 19, 2026, 1:45 AM UTC, ended Sep 19, 2026, 2:04 AM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Sep 19, 2026, 4:04 AM UTC, ended Sep 19, 2026, 4:52 AM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Sep 19, 2026, 7:45 AM UTC, ended Sep 19, 2026, 8:27 AM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Sep 19, 2026, 3:48 PM UTC, ended Sep 19, 2026, 4:09 PM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Sep 19, 2026, 5:49 PM UTC, ended Sep 19, 2026, 6:10 PM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Sep 19, 2026, 7:10 PM UTC, ended Sep 19, 2026, 7:31 PM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Sep 19, 2026, 7:52 PM UTC, ended Sep 19, 2026, 8:50 PM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Sep 19, 2026, 11:11 PM UTC, ended Sep 19, 2026, 11:31 PM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Sep 20, 2026, 4:53 AM UTC, ended Sep 20, 2026, 5:50 AM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Sep 20, 2026, 10:34 AM UTC, ended Sep 20, 2026, 10:40 AM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Sep 20, 2026, 5:53 PM UTC, ended Sep 20, 2026, 6:50 PM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported an outage for this service. Started Sep 20, 2026, 7:53 PM UTC, ended Sep 20, 2026, 10:19 PM UTC.
Why it was retracted: Our checks failed only from check regions on one continent. We need checks to fail from two continents before we call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Sep 21, 2026, 2:51 PM UTC, ended Sep 21, 2026, 3:01 PM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Sep 22, 2026, 4:09 AM UTC, ended Sep 22, 2026, 4:30 AM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Sep 23, 2026, 1:02 AM UTC, ended Sep 23, 2026, 6:32 AM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Sep 23, 2026, 10:13 AM UTC, ended Sep 23, 2026, 10:34 AM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Sep 23, 2026, 4:26 PM UTC, ended Sep 23, 2026, 4:36 PM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Sep 23, 2026, 5:00 PM UTC, ended Sep 23, 2026, 5:36 PM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Sep 23, 2026, 7:37 PM UTC, ended Sep 23, 2026, 8:37 PM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Sep 23, 2026, 11:16 PM UTC, ended Sep 24, 2026, 12:16 AM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Sep 24, 2026, 1:17 AM UTC, ended Sep 24, 2026, 1:57 AM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Sep 24, 2026, 9:37 AM UTC, ended Sep 24, 2026, 9:57 AM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Sep 24, 2026, 11:16 AM UTC, ended Sep 24, 2026, 11:36 AM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Sep 24, 2026, 2:10 PM UTC, ended Sep 24, 2026, 2:19 PM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Sep 25, 2026, 5:50 AM UTC, ended Sep 25, 2026, 5:52 AM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Sep 25, 2026, 9:20 AM UTC, ended Sep 25, 2026, 9:41 AM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Sep 25, 2026, 5:40 PM UTC, ended Sep 25, 2026, 6:40 PM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Sep 25, 2026, 7:40 PM UTC, ended Sep 25, 2026, 8:40 PM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Sep 25, 2026, 7:51 PM UTC, ended Sep 25, 2026, 8:01 PM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Sep 25, 2026, 9:05 PM UTC, ended Sep 25, 2026, 9:25 PM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Sep 26, 2026, 7:22 PM UTC, ended Sep 26, 2026, 7:32 PM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Sep 26, 2026, 8:10 PM UTC, ended Sep 26, 2026, 8:33 PM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported an outage for this service. Started Sep 27, 2026, 10:21 AM UTC, ended Sep 27, 2026, 11:20 AM UTC.
Why it was retracted: Our checks failed only from check regions on one continent. We need checks to fail from two continents before we call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Sep 27, 2026, 2:56 PM UTC, ended Sep 27, 2026, 3:55 PM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Sep 28, 2026, 5:56 AM UTC, ended Sep 28, 2026, 7:56 AM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Sep 28, 2026, 5:56 PM UTC, ended Sep 28, 2026, 6:56 PM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Sep 28, 2026, 8:56 PM UTC, ended Sep 29, 2026, 12:55 AM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Sep 28, 2026, 9:58 PM UTC, ended Sep 28, 2026, 10:18 PM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Sep 29, 2026, 6:40 AM UTC, ended Sep 29, 2026, 7:00 AM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Sep 29, 2026, 12:38 PM UTC, ended Sep 29, 2026, 12:58 PM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Sep 29, 2026, 4:26 PM UTC, ended Sep 29, 2026, 4:46 PM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Sep 29, 2026, 6:01 PM UTC, ended Sep 29, 2026, 6:22 PM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Sep 30, 2026, 12:00 AM UTC, ended Sep 30, 2026, 12:10 AM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Sep 30, 2026, 6:29 AM UTC, ended Sep 30, 2026, 6:59 AM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Sep 30, 2026, 10:18 AM UTC, ended Sep 30, 2026, 10:38 AM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Sep 30, 2026, 1:41 PM UTC, ended Sep 30, 2026, 2:01 PM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Oct 1, 2026, 2:06 AM UTC, ended Oct 1, 2026, 2:46 AM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Oct 1, 2026, 3:46 AM UTC, ended Oct 1, 2026, 4:07 AM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Oct 1, 2026, 9:29 AM UTC, ended Oct 1, 2026, 10:10 AM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Oct 1, 2026, 12:10 PM UTC, ended Oct 1, 2026, 1:10 PM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Oct 1, 2026, 4:30 PM UTC, ended Oct 1, 2026, 7:50 PM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Oct 1, 2026, 6:50 PM UTC, ended Oct 1, 2026, 7:11 PM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Oct 1, 2026, 11:11 PM UTC, ended Oct 1, 2026, 11:51 PM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Oct 2, 2026, 7:31 AM UTC, ended Oct 2, 2026, 8:12 AM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Oct 2, 2026, 10:11 AM UTC, ended Oct 2, 2026, 11:52 AM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Oct 2, 2026, 1:28 PM UTC, ended Oct 2, 2026, 1:38 PM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Oct 2, 2026, 3:34 PM UTC, ended Oct 2, 2026, 3:54 PM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Oct 3, 2026, 4:34 PM UTC, ended Oct 3, 2026, 6:14 PM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported an outage for this service. Started Oct 3, 2026, 11:17 PM UTC, ended Oct 4, 2026, 2:19 AM UTC.
Why it was retracted: Our checks failed only from check regions on one continent. We need checks to fail from two continents before we call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Oct 4, 2026, 5:20 AM UTC, ended Oct 4, 2026, 5:41 AM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Oct 4, 2026, 10:21 AM UTC, ended Oct 4, 2026, 10:52 AM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Oct 4, 2026, 3:41 PM UTC, ended Oct 4, 2026, 5:21 PM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Oct 4, 2026, 8:21 PM UTC, ended Oct 4, 2026, 8:42 PM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Oct 5, 2026, 12:21 AM UTC, ended Oct 5, 2026, 1:02 AM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Oct 5, 2026, 5:42 AM UTC, ended Oct 5, 2026, 7:42 AM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Oct 5, 2026, 12:03 PM UTC, ended Oct 5, 2026, 1:23 PM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Oct 5, 2026, 5:43 PM UTC, ended Oct 5, 2026, 6:23 PM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported an outage for this service. Started Oct 5, 2026, 9:13 PM UTC, ended Oct 6, 2026, 9:39 AM UTC.
Why it was retracted: This event stayed open for more than 6 hours with no incident declared by the service behind it. Our checks alone are not enough to keep an outage standing that long, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Oct 6, 2026, 12:25 AM UTC, ended Oct 6, 2026, 12:45 AM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Oct 6, 2026, 1:25 AM UTC, ended Oct 6, 2026, 3:05 AM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Oct 6, 2026, 9:25 AM UTC, ended Oct 6, 2026, 11:05 AM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Oct 6, 2026, 9:46 PM UTC, ended Oct 6, 2026, 10:06 PM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Oct 7, 2026, 2:06 AM UTC, ended Oct 7, 2026, 2:46 AM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Oct 7, 2026, 5:24 AM UTC, ended Oct 8, 2026, 12:58 AM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Oct 7, 2026, 2:44 PM UTC, ended Oct 7, 2026, 3:24 PM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Oct 7, 2026, 10:46 PM UTC, ended Oct 7, 2026, 11:47 PM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Oct 8, 2026, 1:57 AM UTC, ended Oct 8, 2026, 2:30 AM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Oct 8, 2026, 2:02 AM UTC, ended Oct 8, 2026, 3:37 AM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Oct 8, 2026, 6:57 AM UTC, ended Oct 8, 2026, 7:30 AM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
What we originally showed: We reported a partial outage for this service. Started Oct 8, 2026, 7:26 AM UTC, ended Oct 8, 2026, 8:07 AM UTC.
Why it was retracted: Our checks failed from only one check region. One region is not enough to call an outage, so we no longer present it as one.
Every retraction here follows the rules described on how this check works. An event is retracted when we find evidence the original reading was wrong, and when it fails the rules for a published event: checks failed from only one region, the failing regions were all on one continent, the fault was in one of our own probe regions, or it stayed open more than 6 hours with no live vendor incident behind it. A retracted event is kept and listed here. A vendor disputing an event is not a reason to retract it.