diff --git a/.deploy-probe b/.deploy-probe deleted file mode 100644 index e6e11d42c2ef3e32c0db36222ef88981ea42bb33..0000000000000000000000000000000000000000 --- a/.deploy-probe +++ /dev/null @@ -1 +0,0 @@ -2026-09-04T10:06:03Z diff --git a/api/snapshot.json b/api/snapshot.json index 15d8d99493e50d840a511f8d811a81ee617bd7fd..c04694a2cb809a6acc48150ecce80b5c98978a8e 100644 --- a/api/snapshot.json +++ b/api/snapshot.json @@ -1,5 +1,5 @@ { -"generated_at": "2026-09-04T09:06:33Z", +"generated_at": "2026-09-04T10:17:20Z", "count": 792, "vendors": [ { @@ -11,7 +11,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:06:34Z", +"checked_at": "2026-09-04T10:17:21Z", "page_id": "z5s8xghvb0vf" }, { @@ -23,7 +23,7 @@ "description": "unknown", "open": 0, "error": "http 401", -"checked_at": "2026-09-04T09:06:35Z", +"checked_at": "2026-09-04T10:17:23Z", "page_id": null }, { @@ -35,7 +35,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:06:34Z", +"checked_at": "2026-09-04T10:17:21Z", "page_id": "ntqy1wz94gjv" }, { @@ -47,7 +47,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:06:34Z", +"checked_at": "2026-09-04T10:17:21Z", "page_id": "7mwbz6m7xrh4" }, { @@ -57,9 +57,9 @@ "status_url": "https://status.acquia.com", "state": "ok", "description": "All Systems Operational", -"open": 1, +"open": 0, "error": null, -"checked_at": "2026-09-04T09:06:34Z", +"checked_at": "2026-09-04T10:17:21Z", "page_id": "c3bdbqpxhzcc" }, { @@ -71,7 +71,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:06:35Z", +"checked_at": "2026-09-04T10:17:24Z", "page_id": "04c0bjwv889z" }, { @@ -83,7 +83,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:06:34Z", +"checked_at": "2026-09-04T10:17:21Z", "page_id": "36wq37z91g4s" }, { @@ -95,7 +95,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:06:34Z", +"checked_at": "2026-09-04T10:17:21Z", "page_id": "bbbyh7gsckvq" }, { @@ -107,7 +107,7 @@ "description": "UP", "open": 0, "error": null, -"checked_at": "2026-09-04T09:06:34Z", +"checked_at": "2026-09-04T10:17:21Z", "page_id": null }, { @@ -119,7 +119,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:06:34Z", +"checked_at": "2026-09-04T10:17:21Z", "page_id": "csj35ggbsfvm" }, { @@ -131,7 +131,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:06:34Z", +"checked_at": "2026-09-04T10:17:22Z", "page_id": "ynwjrw9b4wnq" }, { @@ -143,7 +143,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:06:34Z", +"checked_at": "2026-09-04T10:17:22Z", "page_id": "jq64r4cdpggk" }, { @@ -155,7 +155,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:06:34Z", +"checked_at": "2026-09-04T10:17:22Z", "page_id": "01H0FX8N7BG3M9PMMX0J0HENJF" }, { @@ -167,7 +167,7 @@ "description": "Partially Degraded Service", "open": 1, "error": null, -"checked_at": "2026-09-04T09:06:35Z", +"checked_at": "2026-09-04T10:17:23Z", "page_id": "tmd0zfspxwvp" }, { @@ -179,7 +179,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:06:34Z", +"checked_at": "2026-09-04T10:17:22Z", "page_id": "0zvvm4fhtzrw" }, { @@ -191,7 +191,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:06:34Z", +"checked_at": "2026-09-04T10:17:22Z", "page_id": "bkbjcmdhhfbp" }, { @@ -203,7 +203,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:06:34Z", +"checked_at": "2026-09-04T10:17:22Z", "page_id": "pzy6hz1kgshk" }, { @@ -215,7 +215,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:06:34Z", +"checked_at": "2026-09-04T10:17:22Z", "page_id": "7qd3dtddrfkh" }, { @@ -227,7 +227,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:06:34Z", +"checked_at": "2026-09-04T10:17:22Z", "page_id": "bn2d4b3wgfdd" }, { @@ -239,7 +239,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:06:35Z", +"checked_at": "2026-09-04T10:17:22Z", "page_id": "pdsx8yrymckt" }, { @@ -251,7 +251,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:06:35Z", +"checked_at": "2026-09-04T10:17:22Z", "page_id": "b86rbb4mp0v3" }, { @@ -263,7 +263,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:06:36Z", +"checked_at": "2026-09-04T10:17:23Z", "page_id": "tymt9n04zgry" }, { @@ -275,7 +275,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:06:35Z", +"checked_at": "2026-09-04T10:17:23Z", "page_id": "hcqkdmz37wjt" }, { @@ -287,7 +287,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:06:35Z", +"checked_at": "2026-09-04T10:17:23Z", "page_id": "n3hgl6zkw55g" }, { @@ -299,7 +299,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:06:36Z", +"checked_at": "2026-09-04T10:17:24Z", "page_id": "j23nkrf8p8p8" }, { @@ -311,7 +311,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:06:36Z", +"checked_at": "2026-09-04T10:17:24Z", "page_id": "sgktglt7lk13" }, { @@ -323,7 +323,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:06:37Z", +"checked_at": "2026-09-04T10:17:24Z", "page_id": "01JP7XTY7X5FN8960B9XM5EXHT" }, { @@ -335,7 +335,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:06:37Z", +"checked_at": "2026-09-04T10:17:24Z", "page_id": "glkwkjr35b94" }, { @@ -347,7 +347,7 @@ "description": "unknown", "open": 0, "error": "http 401", -"checked_at": "2026-09-04T09:06:38Z", +"checked_at": "2026-09-04T10:17:25Z", "page_id": null }, { @@ -359,7 +359,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:06:37Z", +"checked_at": "2026-09-04T10:17:24Z", "page_id": "dgb87srq2spv" }, { @@ -371,7 +371,7 @@ "description": "operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:06:40Z", +"checked_at": "2026-09-04T10:17:27Z", "page_id": null }, { @@ -383,7 +383,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:06:37Z", +"checked_at": "2026-09-04T10:17:24Z", "page_id": "fmwgqnbnbc4r" }, { @@ -395,7 +395,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:06:37Z", +"checked_at": "2026-09-04T10:17:24Z", "page_id": "p82kbnklccrz" }, { @@ -407,7 +407,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:06:37Z", +"checked_at": "2026-09-04T10:17:24Z", "page_id": "j2qygk57nnl6" }, { @@ -419,7 +419,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:06:37Z", +"checked_at": "2026-09-04T10:17:24Z", "page_id": "hm146k9xwhkt" }, { @@ -431,7 +431,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:06:37Z", +"checked_at": "2026-09-04T10:17:24Z", "page_id": "7j2kbp2pqp51" }, { @@ -443,7 +443,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:06:37Z", +"checked_at": "2026-09-04T10:17:24Z", "page_id": "z4btwrl32bd8" }, { @@ -455,7 +455,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:06:37Z", +"checked_at": "2026-09-04T10:17:24Z", "page_id": "8q71nnwms4k6" }, { @@ -467,7 +467,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:06:37Z", +"checked_at": "2026-09-04T10:17:24Z", "page_id": "kv6mqq586ny1" }, { @@ -479,7 +479,7 @@ "description": "Partially Degraded Service", "open": 1, "error": null, -"checked_at": "2026-09-04T09:06:37Z", +"checked_at": "2026-09-04T10:17:24Z", "page_id": "sw35q6stcxxq" }, { @@ -491,7 +491,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:06:37Z", +"checked_at": "2026-09-04T10:17:24Z", "page_id": "0f54fx204jpt" }, { @@ -503,7 +503,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:06:40Z", +"checked_at": "2026-09-04T10:17:26Z", "page_id": "5qmgwsxwsz78" }, { @@ -515,7 +515,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:06:38Z", +"checked_at": "2026-09-04T10:17:25Z", "page_id": "6b7xgjptl20c" }, { @@ -527,7 +527,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:06:38Z", +"checked_at": "2026-09-04T10:17:25Z", "page_id": "n8766lc3ybbs" }, { @@ -539,7 +539,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:06:38Z", +"checked_at": "2026-09-04T10:17:26Z", "page_id": "tfc0vzc0cq1n" }, { @@ -551,7 +551,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:06:39Z", +"checked_at": "2026-09-04T10:17:26Z", "page_id": "3tbw4lb9t3qp" }, { @@ -563,7 +563,7 @@ "description": "Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:06:39Z", +"checked_at": "2026-09-04T10:17:26Z", "page_id": "53979231f2385e505000033b" }, { @@ -575,7 +575,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:06:40Z", +"checked_at": "2026-09-04T10:17:26Z", "page_id": "tlqktjfqgmc7" }, { @@ -587,7 +587,7 @@ "description": "unknown", "open": 0, "error": "moved: not a statuspage any more", -"checked_at": "2026-09-04T09:06:42Z", +"checked_at": "2026-09-04T10:17:29Z", "page_id": null }, { @@ -599,7 +599,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:06:40Z", +"checked_at": "2026-09-04T10:17:27Z", "page_id": "1lsq0nr637fk" }, { @@ -611,7 +611,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:06:40Z", +"checked_at": "2026-09-04T10:17:27Z", "page_id": "5lrkwtr34xq6" }, { @@ -623,7 +623,7 @@ "description": "unknown", "open": 0, "error": "http 401", -"checked_at": "2026-09-04T09:06:41Z", +"checked_at": "2026-09-04T10:17:29Z", "page_id": null }, { @@ -635,7 +635,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:06:40Z", +"checked_at": "2026-09-04T10:17:27Z", "page_id": "01J0VAVZ0BTSKKFA355BE0BQWC" }, { @@ -647,7 +647,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:06:40Z", +"checked_at": "2026-09-04T10:17:27Z", "page_id": "01HCZ3S2R51YVXFTHGAZ1ZYJK2" }, { @@ -659,7 +659,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:06:40Z", +"checked_at": "2026-09-04T10:17:27Z", "page_id": "jw8c5ywzkwjn" }, { @@ -671,7 +671,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:06:40Z", +"checked_at": "2026-09-04T10:17:27Z", "page_id": "73fvt51hstb9" }, { @@ -683,7 +683,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:06:40Z", +"checked_at": "2026-09-04T10:17:27Z", "page_id": "wvck0tgxwsyn" }, { @@ -695,7 +695,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:06:40Z", +"checked_at": "2026-09-04T10:17:27Z", "page_id": "5b4dcn321xtp" }, { @@ -707,7 +707,7 @@ "description": "Partial System Outage", "open": 2, "error": null, -"checked_at": "2026-09-04T09:06:39Z", +"checked_at": "2026-09-04T10:17:27Z", "page_id": "nlrgjx1zrcyr" }, { @@ -719,7 +719,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:06:40Z", +"checked_at": "2026-09-04T10:17:27Z", "page_id": "k481728pjqn6" }, { @@ -731,7 +731,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:06:40Z", +"checked_at": "2026-09-04T10:17:27Z", "page_id": "fcr8fj24mch8" }, { @@ -743,7 +743,7 @@ "description": "UP", "open": 0, "error": null, -"checked_at": "2026-09-04T09:06:40Z", +"checked_at": "2026-09-04T10:17:27Z", "page_id": null }, { @@ -755,7 +755,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:06:40Z", +"checked_at": "2026-09-04T10:17:27Z", "page_id": "08qslcq6kdy1" }, { @@ -767,7 +767,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:06:40Z", +"checked_at": "2026-09-04T10:17:27Z", "page_id": "stbh0t87fyjr" }, { @@ -779,7 +779,7 @@ "description": "Minor Service Outage", "open": 1, "error": null, -"checked_at": "2026-09-04T09:06:40Z", +"checked_at": "2026-09-04T10:17:28Z", "page_id": "5t5kfdrl9rr6" }, { @@ -791,7 +791,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:06:41Z", +"checked_at": "2026-09-04T10:17:27Z", "page_id": "31040ffjj9v4" }, { @@ -803,7 +803,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:06:41Z", +"checked_at": "2026-09-04T10:17:28Z", "page_id": "7mk10hxcdn88" }, { @@ -815,7 +815,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:06:40Z", +"checked_at": "2026-09-04T10:17:28Z", "page_id": "bqlf8qjztdtr" }, { @@ -827,7 +827,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:06:41Z", +"checked_at": "2026-09-04T10:17:28Z", "page_id": "d9v90pqn3hl2" }, { @@ -839,7 +839,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:06:41Z", +"checked_at": "2026-09-04T10:17:29Z", "page_id": "j9mv27b7rk0m" }, { @@ -851,7 +851,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:06:42Z", +"checked_at": "2026-09-04T10:17:29Z", "page_id": "hr0hbjty1ljs" }, { @@ -863,7 +863,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:06:42Z", +"checked_at": "2026-09-04T10:17:29Z", "page_id": "01KJCF76BZQTKAX0RAKW0B6C5C" }, { @@ -875,7 +875,7 @@ "description": "Partial System Outage", "open": 0, "error": null, -"checked_at": "2026-09-04T09:06:42Z", +"checked_at": "2026-09-04T10:17:29Z", "page_id": "b7j8pgdry84j" }, { @@ -887,7 +887,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:06:42Z", +"checked_at": "2026-09-04T10:17:29Z", "page_id": "1q8r4n02vb2k" }, { @@ -899,7 +899,7 @@ "description": "All Systems Operational (scheduled maintenance in progress)", "open": 1, "error": null, -"checked_at": "2026-09-04T09:06:42Z", +"checked_at": "2026-09-04T10:17:29Z", "page_id": "rly693fnw753" }, { @@ -911,7 +911,7 @@ "description": "All Systems Operational", "open": 1, "error": null, -"checked_at": "2026-09-04T09:06:42Z", +"checked_at": "2026-09-04T10:17:30Z", "page_id": "j7rr7nybf3h1" }, { @@ -923,7 +923,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:06:42Z", +"checked_at": "2026-09-04T10:17:30Z", "page_id": "w5wttjzcd1y1" }, { @@ -935,7 +935,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:06:42Z", +"checked_at": "2026-09-04T10:17:30Z", "page_id": "wwxp49vpw84s" }, { @@ -947,7 +947,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:06:42Z", +"checked_at": "2026-09-04T10:17:30Z", "page_id": "wp6n3nr9gm7w" }, { @@ -959,7 +959,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:06:42Z", +"checked_at": "2026-09-04T10:17:30Z", "page_id": "6byk36z41l3r" }, { @@ -971,7 +971,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:06:44Z", +"checked_at": "2026-09-04T10:17:31Z", "page_id": "01J3FHWFKD070K60YHZ3R7MB1Q" }, { @@ -983,7 +983,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:06:43Z", +"checked_at": "2026-09-04T10:17:30Z", "page_id": "fh4pp8ysntrr" }, { @@ -995,7 +995,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:06:43Z", +"checked_at": "2026-09-04T10:17:30Z", "page_id": "hgyc600tg2jq" }, { @@ -1007,7 +1007,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:06:44Z", +"checked_at": "2026-09-04T10:17:30Z", "page_id": "0j5kz323tn26" }, { @@ -1019,7 +1019,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:06:43Z", +"checked_at": "2026-09-04T10:17:30Z", "page_id": "208q92hckwws" }, { @@ -1031,7 +1031,7 @@ "description": "operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:06:43Z", +"checked_at": "2026-09-04T10:17:31Z", "page_id": null }, { @@ -1043,7 +1043,7 @@ "description": "downtime", "open": 0, "error": null, -"checked_at": "2026-09-04T09:06:45Z", +"checked_at": "2026-09-04T10:17:33Z", "page_id": null }, { @@ -1055,7 +1055,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:06:43Z", +"checked_at": "2026-09-04T10:17:30Z", "page_id": "72dqsh6xk9jf" }, { @@ -1067,7 +1067,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:06:43Z", +"checked_at": "2026-09-04T10:17:30Z", "page_id": "k2nlg36q7ljw" }, { @@ -1079,7 +1079,7 @@ "description": "All Systems Operational", "open": 2, "error": null, -"checked_at": "2026-09-04T09:06:44Z", +"checked_at": "2026-09-04T10:17:32Z", "page_id": "ct9fvwv20c1l" }, { @@ -1091,7 +1091,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:06:44Z", +"checked_at": "2026-09-04T10:17:30Z", "page_id": "d78dwx4kpwsm" }, { @@ -1103,7 +1103,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:06:44Z", +"checked_at": "2026-09-04T10:17:31Z", "page_id": "40ngtf1pqfk1" }, { @@ -1115,7 +1115,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:06:45Z", +"checked_at": "2026-09-04T10:17:33Z", "page_id": "6xl1gdp6yn0x" }, { @@ -1127,7 +1127,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:06:44Z", +"checked_at": "2026-09-04T10:17:31Z", "page_id": "jggkjgplmcdc" }, { @@ -1139,7 +1139,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:06:46Z", +"checked_at": "2026-09-04T10:17:33Z", "page_id": "01KP8VNZ4875P13EBFGV3KNJFV" }, { @@ -1151,7 +1151,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:06:45Z", +"checked_at": "2026-09-04T10:17:32Z", "page_id": "g9xp2l4g1mhf" }, { @@ -1163,7 +1163,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:06:45Z", +"checked_at": "2026-09-04T10:17:32Z", "page_id": "tw97vr0hd4qr" }, { @@ -1175,7 +1175,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:06:45Z", +"checked_at": "2026-09-04T10:17:32Z", "page_id": "jfhnkhllbpdl" }, { @@ -1187,7 +1187,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:06:45Z", +"checked_at": "2026-09-04T10:17:32Z", "page_id": "prqhzr47m677" }, { @@ -1199,7 +1199,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:06:45Z", +"checked_at": "2026-09-04T10:17:32Z", "page_id": "vz6rclzjdt41" }, { @@ -1211,7 +1211,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:06:45Z", +"checked_at": "2026-09-04T10:17:32Z", "page_id": "bztxc6j3xm4f" }, { @@ -1223,7 +1223,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:06:45Z", +"checked_at": "2026-09-04T10:17:32Z", "page_id": "s51vcv9qcqnm" }, { @@ -1235,7 +1235,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:06:45Z", +"checked_at": "2026-09-04T10:17:33Z", "page_id": "m3gf8s9htt9k" }, { @@ -1247,7 +1247,7 @@ "description": "Fully Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:06:45Z", +"checked_at": "2026-09-04T10:17:32Z", "page_id": "5717834e3f22d07560001c1b" }, { @@ -1259,7 +1259,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:06:45Z", +"checked_at": "2026-09-04T10:17:33Z", "page_id": "1fkb7yl9sw87" }, { @@ -1271,7 +1271,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:06:45Z", +"checked_at": "2026-09-04T10:17:32Z", "page_id": "dwky76gz3s50" }, { @@ -1283,7 +1283,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:06:45Z", +"checked_at": "2026-09-04T10:17:33Z", "page_id": "dwtdw9wx918h" }, { @@ -1295,7 +1295,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:06:45Z", +"checked_at": "2026-09-04T10:17:33Z", "page_id": "bkz9pvyggn1d" }, { @@ -1307,7 +1307,7 @@ "description": "Partial System Outage", "open": 8, "error": null, -"checked_at": "2026-09-04T09:06:46Z", +"checked_at": "2026-09-04T10:17:33Z", "page_id": "23tk2y3t5qh7" }, { @@ -1319,7 +1319,7 @@ "description": "operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:06:47Z", +"checked_at": "2026-09-04T10:17:34Z", "page_id": null }, { @@ -1331,7 +1331,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:06:46Z", +"checked_at": "2026-09-04T10:17:33Z", "page_id": "fztzpg81spr6" }, { @@ -1343,7 +1343,7 @@ "description": "Minor Service Outage", "open": 2, "error": null, -"checked_at": "2026-09-04T09:06:46Z", +"checked_at": "2026-09-04T10:17:33Z", "page_id": "j4q3p7shm2wt" }, { @@ -1355,7 +1355,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:06:46Z", +"checked_at": "2026-09-04T10:17:33Z", "page_id": "6w4r0ttlx5ft" }, { @@ -1367,7 +1367,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:06:47Z", +"checked_at": "2026-09-04T10:17:34Z", "page_id": "vs0hl9vkhkvc" }, { @@ -1379,7 +1379,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:06:47Z", +"checked_at": "2026-09-04T10:17:34Z", "page_id": "3yxh1wq71f3n" }, { @@ -1391,7 +1391,7 @@ "description": "Partially Degraded Service", "open": 1, "error": null, -"checked_at": "2026-09-04T09:06:47Z", +"checked_at": "2026-09-04T10:17:34Z", "page_id": "mphpnftfsb8m" }, { @@ -1403,7 +1403,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:06:49Z", +"checked_at": "2026-09-04T10:17:35Z", "page_id": "s22gv0yzh9xy" }, { @@ -1415,7 +1415,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:06:49Z", +"checked_at": "2026-09-04T10:17:36Z", "page_id": "v4rz4qn04rt3" }, { @@ -1423,11 +1423,11 @@ "vendor": "Clerk", "platform": "statuspage", "status_url": "https://status.clerk.com", -"state": "ok", -"description": "All Systems Operational", -"open": 0, +"state": "degraded", +"description": "Partial System Degradation", +"open": 1, "error": null, -"checked_at": "2026-09-04T09:06:48Z", +"checked_at": "2026-09-04T10:17:34Z", "page_id": "01JT6C46FMYD9THW380GCVV2XJ" }, { @@ -1439,7 +1439,7 @@ "description": "Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:06:48Z", +"checked_at": "2026-09-04T10:17:34Z", "page_id": "5b6e0963c662144d00913a09" }, { @@ -1451,7 +1451,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:06:48Z", +"checked_at": "2026-09-04T10:17:35Z", "page_id": "plmhhdckmdbg" }, { @@ -1463,7 +1463,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:06:48Z", +"checked_at": "2026-09-04T10:17:35Z", "page_id": "mpfrt81d47gt" }, { @@ -1475,7 +1475,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:06:48Z", +"checked_at": "2026-09-04T10:17:35Z", "page_id": "2126xm8ctzlk" }, { @@ -1487,7 +1487,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:06:48Z", +"checked_at": "2026-09-04T10:17:36Z", "page_id": "nknppjkdpnhk" }, { @@ -1499,7 +1499,7 @@ "description": "unknown", "open": 0, "error": "moved: not a statuspage any more", -"checked_at": "2026-09-04T09:06:51Z", +"checked_at": "2026-09-04T10:17:38Z", "page_id": null }, { @@ -1511,7 +1511,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:06:48Z", +"checked_at": "2026-09-04T10:17:35Z", "page_id": "kw8sx4b5g26z" }, { @@ -1523,7 +1523,7 @@ "description": "UP", "open": 0, "error": null, -"checked_at": "2026-09-04T09:06:48Z", +"checked_at": "2026-09-04T10:17:35Z", "page_id": null }, { @@ -1535,7 +1535,7 @@ "description": "Minor Service Outage", "open": 3, "error": null, -"checked_at": "2026-09-04T09:06:49Z", +"checked_at": "2026-09-04T10:17:36Z", "page_id": "yh6f0r4529hb" }, { @@ -1547,7 +1547,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:06:49Z", +"checked_at": "2026-09-04T10:17:35Z", "page_id": "2vylpc2bvdd4" }, { @@ -1559,7 +1559,7 @@ "description": "Partially Degraded Service", "open": 1, "error": null, -"checked_at": "2026-09-04T09:06:49Z", +"checked_at": "2026-09-04T10:17:36Z", "page_id": "cvrjpvzxt7rd" }, { @@ -1571,7 +1571,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:06:49Z", +"checked_at": "2026-09-04T10:17:36Z", "page_id": "3wlgh0qb53fx" }, { @@ -1583,7 +1583,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:06:49Z", +"checked_at": "2026-09-04T10:17:36Z", "page_id": "r3f773swz03t" }, { @@ -1595,7 +1595,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:06:49Z", +"checked_at": "2026-09-04T10:17:36Z", "page_id": "7k11xygtyyyg" }, { @@ -1607,7 +1607,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:06:49Z", +"checked_at": "2026-09-04T10:17:36Z", "page_id": "n7spgf9dkl62" }, { @@ -1619,7 +1619,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:06:50Z", +"checked_at": "2026-09-04T10:17:37Z", "page_id": "x5rpkhzf3pps" }, { @@ -1631,7 +1631,7 @@ "description": "unknown", "open": 0, "error": "http 401", -"checked_at": "2026-09-04T09:06:50Z", +"checked_at": "2026-09-04T10:17:37Z", "page_id": null }, { @@ -1643,7 +1643,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:06:50Z", +"checked_at": "2026-09-04T10:17:37Z", "page_id": "z52x112kjqtb" }, { @@ -1655,7 +1655,7 @@ "description": "unknown", "open": 0, "error": "moved: not a statuspage any more", -"checked_at": "2026-09-04T09:06:50Z", +"checked_at": "2026-09-04T10:17:37Z", "page_id": null }, { @@ -1667,7 +1667,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:06:51Z", +"checked_at": "2026-09-04T10:17:38Z", "page_id": "01HEBDXXA856JY0M3E46GZHCH8" }, { @@ -1679,7 +1679,7 @@ "description": "All Systems Operational", "open": 3, "error": null, -"checked_at": "2026-09-04T09:06:50Z", +"checked_at": "2026-09-04T10:17:37Z", "page_id": "f7d99y0lq7q7" }, { @@ -1691,7 +1691,7 @@ "description": "Partially Degraded Service", "open": 2, "error": null, -"checked_at": "2026-09-04T09:06:51Z", +"checked_at": "2026-09-04T10:17:37Z", "page_id": "kr0djjh0jyy9" }, { @@ -1703,7 +1703,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:06:51Z", +"checked_at": "2026-09-04T10:17:37Z", "page_id": "fq04kyc42vyn" }, { @@ -1715,7 +1715,7 @@ "description": "All Systems Operational", "open": 3, "error": null, -"checked_at": "2026-09-04T09:06:51Z", +"checked_at": "2026-09-04T10:17:37Z", "page_id": "9nkgss4bjxs5" }, { @@ -1727,7 +1727,7 @@ "description": "unknown", "open": 0, "error": "moved: not a statuspage any more", -"checked_at": "2026-09-04T09:06:54Z", +"checked_at": "2026-09-04T10:17:40Z", "page_id": null }, { @@ -1739,7 +1739,7 @@ "description": "operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:06:52Z", +"checked_at": "2026-09-04T10:17:39Z", "page_id": null }, { @@ -1751,7 +1751,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:06:51Z", +"checked_at": "2026-09-04T10:17:38Z", "page_id": "y0w10tnj9nq1" }, { @@ -1763,7 +1763,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:06:51Z", +"checked_at": "2026-09-04T10:17:38Z", "page_id": "m7rqth81zw45" }, { @@ -1775,7 +1775,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:06:51Z", +"checked_at": "2026-09-04T10:17:38Z", "page_id": "4p503jwl1j2w" }, { @@ -1787,7 +1787,7 @@ "description": "Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:06:51Z", +"checked_at": "2026-09-04T10:17:38Z", "page_id": "56e4295370fe4ece420002bb" }, { @@ -1799,7 +1799,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:06:51Z", +"checked_at": "2026-09-04T10:17:39Z", "page_id": "rbmtnxrh34rs" }, { @@ -1811,7 +1811,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:06:51Z", +"checked_at": "2026-09-04T10:17:38Z", "page_id": "4g2my7tbhjsq" }, { @@ -1823,7 +1823,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:06:51Z", +"checked_at": "2026-09-04T10:17:38Z", "page_id": "3yz1tdpdnjl3" }, { @@ -1835,7 +1835,7 @@ "description": "Degraded Performance", "open": 2, "error": null, -"checked_at": "2026-09-04T09:06:51Z", +"checked_at": "2026-09-04T10:17:38Z", "page_id": "619cf82551fec9053d612f09" }, { @@ -1847,7 +1847,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:06:52Z", +"checked_at": "2026-09-04T10:17:39Z", "page_id": "g83kktkx21mx" }, { @@ -1859,7 +1859,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:06:52Z", +"checked_at": "2026-09-04T10:17:39Z", "page_id": "4bv17htq00cz" }, { @@ -1871,7 +1871,7 @@ "description": "Planned Maintenance", "open": 2, "error": null, -"checked_at": "2026-09-04T09:06:52Z", +"checked_at": "2026-09-04T10:17:39Z", "page_id": "5e126e998f2f032e1f8f0f4b" }, { @@ -1883,7 +1883,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:06:52Z", +"checked_at": "2026-09-04T10:17:39Z", "page_id": "g09ns8sfg8zg" }, { @@ -1895,7 +1895,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:06:52Z", +"checked_at": "2026-09-04T10:17:39Z", "page_id": "jgdmnlhfjdlf" }, { @@ -1907,7 +1907,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:06:52Z", +"checked_at": "2026-09-04T10:17:39Z", "page_id": "3h72wtpg5fqs" }, { @@ -1919,7 +1919,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:06:52Z", +"checked_at": "2026-09-04T10:17:39Z", "page_id": "8w6hqx5zmgxv" }, { @@ -1931,7 +1931,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:06:52Z", +"checked_at": "2026-09-04T10:17:39Z", "page_id": "pvbm341xnpgm" }, { @@ -1943,7 +1943,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:06:53Z", +"checked_at": "2026-09-04T10:17:40Z", "page_id": "vgwkvtzgb38y" }, { @@ -1955,7 +1955,7 @@ "description": "All Systems Operational", "open": 2, "error": null, -"checked_at": "2026-09-04T09:06:53Z", +"checked_at": "2026-09-04T10:17:40Z", "page_id": "fsr7n9twq7sf" }, { @@ -1967,7 +1967,7 @@ "description": "All Systems Operational", "open": 4, "error": null, -"checked_at": "2026-09-04T09:06:53Z", +"checked_at": "2026-09-04T10:17:40Z", "page_id": "0fyr5zwm29g2" }, { @@ -1979,7 +1979,7 @@ "description": "UP", "open": 1, "error": null, -"checked_at": "2026-09-04T09:06:53Z", +"checked_at": "2026-09-04T10:17:40Z", "page_id": null }, { @@ -1991,7 +1991,7 @@ "description": "UP", "open": 0, "error": null, -"checked_at": "2026-09-04T09:06:53Z", +"checked_at": "2026-09-04T10:17:40Z", "page_id": null }, { @@ -2003,7 +2003,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:06:53Z", +"checked_at": "2026-09-04T10:17:40Z", "page_id": "ltbd5k60rm48" }, { @@ -2015,7 +2015,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:06:53Z", +"checked_at": "2026-09-04T10:17:40Z", "page_id": "01KGCBHTPN1MVW4GBN40JA4YNX" }, { @@ -2027,7 +2027,7 @@ "description": "unknown", "open": 0, "error": "moved: not a statuspage any more", -"checked_at": "2026-09-04T09:07:06Z", +"checked_at": "2026-09-04T10:17:47Z", "page_id": null }, { @@ -2039,7 +2039,7 @@ "description": "Operational", "open": 1, "error": null, -"checked_at": "2026-09-04T09:06:57Z", +"checked_at": "2026-09-04T10:17:40Z", "page_id": "5aabcb89fccc4b04d3774443" }, { @@ -2051,7 +2051,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:06:57Z", +"checked_at": "2026-09-04T10:17:43Z", "page_id": "ktt0qmt8vm7t" }, { @@ -2063,7 +2063,7 @@ "description": "Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:06:57Z", +"checked_at": "2026-09-04T10:17:44Z", "page_id": "5cf02dde58a00904bda41926" }, { @@ -2075,7 +2075,7 @@ "description": "UP", "open": 0, "error": null, -"checked_at": "2026-09-04T09:06:59Z", +"checked_at": "2026-09-04T10:17:50Z", "page_id": null }, { @@ -2087,7 +2087,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:06:55Z", +"checked_at": "2026-09-04T10:17:43Z", "page_id": "1k6wzpspjf99" }, { @@ -2099,7 +2099,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:06:57Z", +"checked_at": "2026-09-04T10:17:43Z", "page_id": "x8rxwpfsx4lk" }, { @@ -2111,7 +2111,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:06:57Z", +"checked_at": "2026-09-04T10:17:43Z", "page_id": "rh4wvy7s0k6b" }, { @@ -2123,7 +2123,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:06:57Z", +"checked_at": "2026-09-04T10:17:45Z", "page_id": "pv3q3cx4y1f0" }, { @@ -2135,7 +2135,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:06:57Z", +"checked_at": "2026-09-04T10:17:43Z", "page_id": "g7gr6xc89b8z" }, { @@ -2145,9 +2145,9 @@ "status_url": "https://status.datto.com", "state": "degraded", "description": "Partially Degraded Service", -"open": 6, +"open": 5, "error": null, -"checked_at": "2026-09-04T09:07:08Z", +"checked_at": "2026-09-04T10:17:45Z", "page_id": "43vzbh696nvp" }, { @@ -2159,7 +2159,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:07:01Z", +"checked_at": "2026-09-04T10:17:46Z", "page_id": "01JBH53RGT63T7EM45RY826C4H" }, { @@ -2171,7 +2171,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:06:57Z", +"checked_at": "2026-09-04T10:17:50Z", "page_id": "69bkvcrzfm6n" }, { @@ -2183,7 +2183,7 @@ "description": "unknown", "open": 0, "error": "http 526", -"checked_at": "2026-09-04T09:07:01Z", +"checked_at": "2026-09-04T10:17:50Z", "page_id": null }, { @@ -2195,7 +2195,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:07:04Z", +"checked_at": "2026-09-04T10:17:46Z", "page_id": "w2twxzzspryy" }, { @@ -2207,7 +2207,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:07:01Z", +"checked_at": "2026-09-04T10:17:43Z", "page_id": "jq6h7xsl4fgb" }, { @@ -2219,7 +2219,7 @@ "description": "UP", "open": 0, "error": null, -"checked_at": "2026-09-04T09:07:07Z", +"checked_at": "2026-09-04T10:17:47Z", "page_id": null }, { @@ -2231,7 +2231,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:07:10Z", +"checked_at": "2026-09-04T10:17:52Z", "page_id": "7dvn5lr1wn2r" }, { @@ -2243,7 +2243,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:07:12Z", +"checked_at": "2026-09-04T10:17:51Z", "page_id": "qph9g2zr8lfm" }, { @@ -2251,11 +2251,11 @@ "vendor": "DigiCert", "platform": "statuspage", "status_url": "https://status.digicert.com", -"state": "ok", -"description": "All Systems Operational", -"open": 0, +"state": "partial", +"description": "Partial System Outage", +"open": 1, "error": null, -"checked_at": "2026-09-04T09:07:01Z", +"checked_at": "2026-09-04T10:17:50Z", "page_id": "63gng2lz2kw8" }, { @@ -2267,7 +2267,7 @@ "description": "All Systems Operational", "open": 2, "error": null, -"checked_at": "2026-09-04T09:07:03Z", +"checked_at": "2026-09-04T10:17:51Z", "page_id": "sbyt1kvnjbd6" }, { @@ -2279,7 +2279,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:07:01Z", +"checked_at": "2026-09-04T10:17:49Z", "page_id": "t6dhqw1vh35j" }, { @@ -2291,7 +2291,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:07:01Z", +"checked_at": "2026-09-04T10:17:56Z", "page_id": "w4cz49tckxhp" }, { @@ -2303,7 +2303,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:07:01Z", +"checked_at": "2026-09-04T10:17:46Z", "page_id": "srhpyqt94yxb" }, { @@ -2315,7 +2315,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:07:02Z", +"checked_at": "2026-09-04T10:17:53Z", "page_id": "wgmzn7kc741k" }, { @@ -2327,7 +2327,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:07:06Z", +"checked_at": "2026-09-04T10:17:47Z", "page_id": "3thm1ndd6lgx" }, { @@ -2339,7 +2339,7 @@ "description": "Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:07:08Z", +"checked_at": "2026-09-04T10:17:49Z", "page_id": "5f0f1641e8578204c4e2eec7" }, { @@ -2351,7 +2351,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:07:06Z", +"checked_at": "2026-09-04T10:17:49Z", "page_id": "pp1lkj6mpx59" }, { @@ -2363,7 +2363,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:07:04Z", +"checked_at": "2026-09-04T10:17:54Z", "page_id": "tjym90yyv2zt" }, { @@ -2375,7 +2375,7 @@ "description": "operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:07:08Z", +"checked_at": "2026-09-04T10:17:53Z", "page_id": null }, { @@ -2387,7 +2387,7 @@ "description": "UP", "open": 0, "error": null, -"checked_at": "2026-09-04T09:07:04Z", +"checked_at": "2026-09-04T10:17:55Z", "page_id": null }, { @@ -2399,7 +2399,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:07:08Z", +"checked_at": "2026-09-04T10:18:01Z", "page_id": "01K74XC4TMWXW51JZXNY729350" }, { @@ -2411,7 +2411,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:07:10Z", +"checked_at": "2026-09-04T10:17:55Z", "page_id": "cnpxcswwjr5s" }, { @@ -2423,7 +2423,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:07:06Z", +"checked_at": "2026-09-04T10:17:59Z", "page_id": "72xq6x6pmpfd" }, { @@ -2435,7 +2435,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:07:08Z", +"checked_at": "2026-09-04T10:17:56Z", "page_id": "h7z4rgm54b5c" }, { @@ -2447,7 +2447,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:07:15Z", +"checked_at": "2026-09-04T10:17:59Z", "page_id": "01K86CDD4VEV800QXFVPJP4NNZ" }, { @@ -2459,7 +2459,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:07:12Z", +"checked_at": "2026-09-04T10:17:54Z", "page_id": "rzvhv6t2bhzc" }, { @@ -2471,7 +2471,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:07:12Z", +"checked_at": "2026-09-04T10:17:56Z", "page_id": "05hwsyqkr9z7" }, { @@ -2483,7 +2483,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:07:14Z", +"checked_at": "2026-09-04T10:17:58Z", "page_id": "03cyk0207v03" }, { @@ -2495,7 +2495,7 @@ "description": "unknown", "open": 0, "error": "moved: not a statuspage any more", -"checked_at": "2026-09-04T09:07:18Z", +"checked_at": "2026-09-04T10:18:02Z", "page_id": null }, { @@ -2507,7 +2507,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:07:14Z", +"checked_at": "2026-09-04T10:17:54Z", "page_id": "ftd21120x69r" }, { @@ -2519,7 +2519,7 @@ "description": "Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:07:12Z", +"checked_at": "2026-09-04T10:18:01Z", "page_id": "575f0f606826303142000510" }, { @@ -2531,7 +2531,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:07:14Z", +"checked_at": "2026-09-04T10:17:59Z", "page_id": "6spyc20yyldc" }, { @@ -2543,7 +2543,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:07:12Z", +"checked_at": "2026-09-04T10:18:01Z", "page_id": "g56bb5vqcws9" }, { @@ -2555,7 +2555,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:07:10Z", +"checked_at": "2026-09-04T10:17:56Z", "page_id": "t34htyd6jblf" }, { @@ -2567,7 +2567,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:07:12Z", +"checked_at": "2026-09-04T10:17:58Z", "page_id": "qrxf5mzbrsxw" }, { @@ -2579,7 +2579,7 @@ "description": "Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:07:20Z", +"checked_at": "2026-09-04T10:18:01Z", "page_id": "546d8cb6af8407b6730000cb" }, { @@ -2591,7 +2591,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:07:10Z", +"checked_at": "2026-09-04T10:18:00Z", "page_id": "n1jtz5983249" }, { @@ -2603,7 +2603,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:07:19Z", +"checked_at": "2026-09-04T10:18:05Z", "page_id": "mfxfkx5qk6zd" }, { @@ -2615,7 +2615,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:07:12Z", +"checked_at": "2026-09-04T10:18:01Z", "page_id": "7m38g1wgl80m" }, { @@ -2627,7 +2627,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:07:14Z", +"checked_at": "2026-09-04T10:18:03Z", "page_id": "jr196z1ns266" }, { @@ -2639,7 +2639,7 @@ "description": "Partial System Outage", "open": 2, "error": null, -"checked_at": "2026-09-04T09:07:12Z", +"checked_at": "2026-09-04T10:18:02Z", "page_id": "8wpbdv4sl8gv" }, { @@ -2651,7 +2651,7 @@ "description": "Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:07:21Z", +"checked_at": "2026-09-04T10:18:02Z", "page_id": "57df7189b0a7b27e32000999" }, { @@ -2663,7 +2663,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:07:18Z", +"checked_at": "2026-09-04T10:18:03Z", "page_id": "dj4s2jtd2j0x" }, { @@ -2675,7 +2675,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:07:19Z", +"checked_at": "2026-09-04T10:18:05Z", "page_id": "gsjmhyqknvj0" }, { @@ -2687,7 +2687,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:07:20Z", +"checked_at": "2026-09-04T10:18:04Z", "page_id": "lvdy5bw80hl4" }, { @@ -2699,7 +2699,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:07:18Z", +"checked_at": "2026-09-04T10:18:05Z", "page_id": "tkm3h0p3b2zc" }, { @@ -2711,7 +2711,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:07:21Z", +"checked_at": "2026-09-04T10:18:05Z", "page_id": "76sphw1bc50q" }, { @@ -2723,7 +2723,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:07:19Z", +"checked_at": "2026-09-04T10:18:06Z", "page_id": "hmvfjl5qxtmb" }, { @@ -2735,7 +2735,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:07:21Z", +"checked_at": "2026-09-04T10:18:07Z", "page_id": "df4fh7v5k4sb" }, { @@ -2747,7 +2747,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:07:26Z", +"checked_at": "2026-09-04T10:18:07Z", "page_id": "ft308v428dv3" }, { @@ -2759,7 +2759,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:07:23Z", +"checked_at": "2026-09-04T10:18:05Z", "page_id": "h6vtsr71bjdg" }, { @@ -2771,7 +2771,7 @@ "description": "All Systems Operational", "open": 1, "error": null, -"checked_at": "2026-09-04T09:07:21Z", +"checked_at": "2026-09-04T10:18:11Z", "page_id": "tgftx4cm9lhk" }, { @@ -2783,7 +2783,7 @@ "description": "unknown", "open": 0, "error": null, -"checked_at": "2026-09-04T09:07:23Z", +"checked_at": "2026-09-04T10:18:07Z", "page_id": "cec99eca0d27350651aff686" }, { @@ -2795,7 +2795,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:07:26Z", +"checked_at": "2026-09-04T10:18:08Z", "page_id": "4xf58j20pv7f" }, { @@ -2807,7 +2807,7 @@ "description": "unknown", "open": 0, "error": null, -"checked_at": "2026-09-04T09:07:26Z", +"checked_at": "2026-09-04T10:18:11Z", "page_id": "cec99eca0d27350651aff686" }, { @@ -2817,9 +2817,9 @@ "status_url": "https://status.exact.com", "state": "degraded", "description": "Partially Degraded Service", -"open": 8, +"open": 9, "error": null, -"checked_at": "2026-09-04T09:07:26Z", +"checked_at": "2026-09-04T10:18:09Z", "page_id": "mr76vvnwb7ph" }, { @@ -2831,7 +2831,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:07:26Z", +"checked_at": "2026-09-04T10:18:07Z", "page_id": "3ztcx2bgmj9s" }, { @@ -2843,7 +2843,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:07:29Z", +"checked_at": "2026-09-04T10:18:09Z", "page_id": "8cps7xt0nkkn" }, { @@ -2855,7 +2855,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:07:22Z", +"checked_at": "2026-09-04T10:18:10Z", "page_id": "15xygypb8423" }, { @@ -2867,7 +2867,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:07:23Z", +"checked_at": "2026-09-04T10:18:08Z", "page_id": "hmtfkmhsb66c" }, { @@ -2879,7 +2879,7 @@ "description": "Partially Degraded Service", "open": 1, "error": null, -"checked_at": "2026-09-04T09:07:26Z", +"checked_at": "2026-09-04T10:18:20Z", "page_id": "pdv1y4ymtslx" }, { @@ -2891,7 +2891,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:07:30Z", +"checked_at": "2026-09-04T10:18:10Z", "page_id": "zgq2s4kxnrh5" }, { @@ -2903,7 +2903,7 @@ "description": "All Systems Operational", "open": 2, "error": null, -"checked_at": "2026-09-04T09:07:26Z", +"checked_at": "2026-09-04T10:18:11Z", "page_id": "h7kz0y1dbjsv" }, { @@ -2915,7 +2915,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:07:33Z", +"checked_at": "2026-09-04T10:18:14Z", "page_id": "z9pq4tnqffhz" }, { @@ -2927,7 +2927,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:07:30Z", +"checked_at": "2026-09-04T10:18:12Z", "page_id": "rxpksf93ynw6" }, { @@ -2939,7 +2939,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:07:31Z", +"checked_at": "2026-09-04T10:18:16Z", "page_id": "9mm3z3f3xbw3" }, { @@ -2951,7 +2951,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:07:31Z", +"checked_at": "2026-09-04T10:18:19Z", "page_id": "z8cjgbr8sqmh" }, { @@ -2963,7 +2963,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:07:31Z", +"checked_at": "2026-09-04T10:18:16Z", "page_id": "qcl58pn3j90b" }, { @@ -2975,7 +2975,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:07:31Z", +"checked_at": "2026-09-04T10:18:12Z", "page_id": "ryqsm6mnh7f9" }, { @@ -2987,7 +2987,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:07:38Z", +"checked_at": "2026-09-04T10:18:12Z", "page_id": "vyj8jx98629z" }, { @@ -2999,7 +2999,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:07:33Z", +"checked_at": "2026-09-04T10:18:20Z", "page_id": "7xswlptgkm8x" }, { @@ -3011,7 +3011,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:07:30Z", +"checked_at": "2026-09-04T10:18:17Z", "page_id": "4d1gcb5lj8s4" }, { @@ -3023,7 +3023,7 @@ "description": "Partial System Outage", "open": 0, "error": null, -"checked_at": "2026-09-04T09:07:33Z", +"checked_at": "2026-09-04T10:18:19Z", "page_id": "6ppcgf6d9w2p" }, { @@ -3035,7 +3035,7 @@ "description": "Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:07:40Z", +"checked_at": "2026-09-04T10:18:17Z", "page_id": "5b5926593c827b422fc89539" }, { @@ -3047,7 +3047,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:07:34Z", +"checked_at": "2026-09-04T10:18:16Z", "page_id": "ccvkj5xvl2zs" }, { @@ -3059,7 +3059,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:07:38Z", +"checked_at": "2026-09-04T10:18:22Z", "page_id": "65rccr4mbblw" }, { @@ -3071,7 +3071,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:07:33Z", +"checked_at": "2026-09-04T10:18:22Z", "page_id": "9dwnwphgswgn" }, { @@ -3083,7 +3083,7 @@ "description": "Partially Degraded Service", "open": 2, "error": null, -"checked_at": "2026-09-04T09:07:36Z", +"checked_at": "2026-09-04T10:18:23Z", "page_id": "78lm3dxlst13" }, { @@ -3095,7 +3095,7 @@ "description": "Service Under Maintenance", "open": 0, "error": null, -"checked_at": "2026-09-04T09:07:36Z", +"checked_at": "2026-09-04T10:18:22Z", "page_id": "s3xxyfbwv8pz" }, { @@ -3107,7 +3107,7 @@ "description": "UP", "open": 0, "error": null, -"checked_at": "2026-09-04T09:07:40Z", +"checked_at": "2026-09-04T10:18:22Z", "page_id": null }, { @@ -3119,7 +3119,7 @@ "description": "unknown", "open": 0, "error": "moved: not a statuspage any more", -"checked_at": "2026-09-04T09:07:49Z", +"checked_at": "2026-09-04T10:18:31Z", "page_id": null }, { @@ -3131,7 +3131,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:07:43Z", +"checked_at": "2026-09-04T10:18:27Z", "page_id": "7m2fxdjqj8mc" }, { @@ -3143,7 +3143,7 @@ "description": "unknown", "open": 0, "error": "http 401", -"checked_at": "2026-09-04T09:07:38Z", +"checked_at": "2026-09-04T10:18:27Z", "page_id": null }, { @@ -3155,7 +3155,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:07:39Z", +"checked_at": "2026-09-04T10:18:20Z", "page_id": "rtl9cj1jksdd" }, { @@ -3167,7 +3167,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:07:35Z", +"checked_at": "2026-09-04T10:18:22Z", "page_id": "dxmlltjndjnf" }, { @@ -3179,7 +3179,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:07:39Z", +"checked_at": "2026-09-04T10:18:20Z", "page_id": "2my3x69h5rtb" }, { @@ -3191,7 +3191,7 @@ "description": "UP", "open": 0, "error": null, -"checked_at": "2026-09-04T09:07:38Z", +"checked_at": "2026-09-04T10:18:21Z", "page_id": null }, { @@ -3203,7 +3203,7 @@ "description": "operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:07:47Z", +"checked_at": "2026-09-04T10:18:22Z", "page_id": null }, { @@ -3215,7 +3215,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:07:41Z", +"checked_at": "2026-09-04T10:18:23Z", "page_id": "0598znb9bjpl" }, { @@ -3227,7 +3227,7 @@ "description": "unknown", "open": 0, "error": null, -"checked_at": "2026-09-04T09:07:44Z", +"checked_at": "2026-09-04T10:18:22Z", "page_id": "c76b042579dd3007af2ad749" }, { @@ -3239,7 +3239,7 @@ "description": "unknown", "open": 0, "error": null, -"checked_at": "2026-09-04T09:07:47Z", +"checked_at": "2026-09-04T10:18:27Z", "page_id": "cec99eca0d27350651aff686" }, { @@ -3251,7 +3251,7 @@ "description": "operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:07:46Z", +"checked_at": "2026-09-04T10:18:26Z", "page_id": null }, { @@ -3263,7 +3263,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:07:43Z", +"checked_at": "2026-09-04T10:18:25Z", "page_id": "sf4fhm665xvy" }, { @@ -3275,7 +3275,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:07:41Z", +"checked_at": "2026-09-04T10:18:26Z", "page_id": "w7dbdrjkdh1g" }, { @@ -3287,7 +3287,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:07:42Z", +"checked_at": "2026-09-04T10:18:25Z", "page_id": "zncldvn59n96" }, { @@ -3299,7 +3299,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:07:40Z", +"checked_at": "2026-09-04T10:18:25Z", "page_id": "xnm08yh10bv5" }, { @@ -3311,7 +3311,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:07:49Z", +"checked_at": "2026-09-04T10:18:26Z", "page_id": "zczy44m7yf16" }, { @@ -3323,7 +3323,7 @@ "description": "Partially Degraded Service", "open": 1, "error": null, -"checked_at": "2026-09-04T09:07:41Z", +"checked_at": "2026-09-04T10:18:29Z", "page_id": "5cm4df530pl6" }, { @@ -3335,7 +3335,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:07:47Z", +"checked_at": "2026-09-04T10:18:30Z", "page_id": "pbh1zz50vzz3" }, { @@ -3347,7 +3347,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:07:50Z", +"checked_at": "2026-09-04T10:18:33Z", "page_id": "vy0yk5ppnbrn" }, { @@ -3359,7 +3359,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:07:52Z", +"checked_at": "2026-09-04T10:18:32Z", "page_id": "41bcy19p7cf6" }, { @@ -3369,9 +3369,9 @@ "status_url": "https://status.gemini.com", "state": "degraded", "description": "Partially Degraded Service", -"open": 2, +"open": 1, "error": null, -"checked_at": "2026-09-04T09:07:46Z", +"checked_at": "2026-09-04T10:18:29Z", "page_id": "39sk4gs2zhsq" }, { @@ -3383,7 +3383,7 @@ "description": "Partial System Outage", "open": 1, "error": null, -"checked_at": "2026-09-04T09:07:50Z", +"checked_at": "2026-09-04T10:18:31Z", "page_id": "mcy41tlb177g" }, { @@ -3395,7 +3395,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:07:47Z", +"checked_at": "2026-09-04T10:18:33Z", "page_id": "01JEC4YCA5CNSV3G4Q2P5G959W" }, { @@ -3407,7 +3407,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:07:53Z", +"checked_at": "2026-09-04T10:18:32Z", "page_id": "ykjdtv1csj3l" }, { @@ -3419,7 +3419,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:07:46Z", +"checked_at": "2026-09-04T10:18:29Z", "page_id": "1ndz6qr465zx" }, { @@ -3431,7 +3431,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:07:47Z", +"checked_at": "2026-09-04T10:18:27Z", "page_id": "k47r8nj90z97" }, { @@ -3443,7 +3443,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:07:51Z", +"checked_at": "2026-09-04T10:18:41Z", "page_id": "01JR7NN9ZBT861HXDGR6REYW1H" }, { @@ -3455,7 +3455,7 @@ "description": "unknown", "open": 0, "error": "http 401", -"checked_at": "2026-09-04T09:07:51Z", +"checked_at": "2026-09-04T10:18:32Z", "page_id": null }, { @@ -3467,7 +3467,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:07:57Z", +"checked_at": "2026-09-04T10:18:29Z", "page_id": "kctbh9vrtdwd" }, { @@ -3479,7 +3479,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:07:51Z", +"checked_at": "2026-09-04T10:18:29Z", "page_id": "w95jm4rbdm2k" }, { @@ -3491,7 +3491,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:07:51Z", +"checked_at": "2026-09-04T10:18:33Z", "page_id": "8yc2g8k4wvrj" }, { @@ -3503,7 +3503,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:07:50Z", +"checked_at": "2026-09-04T10:18:37Z", "page_id": "mnlz85pm9zhx" }, { @@ -3515,7 +3515,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:07:54Z", +"checked_at": "2026-09-04T10:18:31Z", "page_id": "8bfvqps6cdjc" }, { @@ -3527,7 +3527,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:08:04Z", +"checked_at": "2026-09-04T10:18:40Z", "page_id": "s1lvscrk3yp4" }, { @@ -3539,7 +3539,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:07:53Z", +"checked_at": "2026-09-04T10:18:34Z", "page_id": "01KJZQKSXXQC6TJ04E5H309FVX" }, { @@ -3551,7 +3551,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:07:52Z", +"checked_at": "2026-09-04T10:18:37Z", "page_id": "z8s4n2jmrsl0" }, { @@ -3563,7 +3563,7 @@ "description": "Service Under Maintenance", "open": 0, "error": null, -"checked_at": "2026-09-04T09:07:54Z", +"checked_at": "2026-09-04T10:18:36Z", "page_id": "6r99zhljywjf" }, { @@ -3575,7 +3575,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:08:00Z", +"checked_at": "2026-09-04T10:18:40Z", "page_id": "z8tsnsg80b0g" }, { @@ -3587,7 +3587,7 @@ "description": "Minor Service Outage", "open": 1, "error": null, -"checked_at": "2026-09-04T09:07:57Z", +"checked_at": "2026-09-04T10:18:44Z", "page_id": "rkwlwn2f7myd" }, { @@ -3599,7 +3599,7 @@ "description": "unknown", "open": 0, "error": "http 401", -"checked_at": "2026-09-04T09:08:00Z", +"checked_at": "2026-09-04T10:18:40Z", "page_id": null }, { @@ -3611,7 +3611,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:07:54Z", +"checked_at": "2026-09-04T10:18:43Z", "page_id": "wr4yv9f633gw" }, { @@ -3623,7 +3623,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:08:00Z", +"checked_at": "2026-09-04T10:18:37Z", "page_id": "01JQRV4MRGVDN2KPX94HS1BR71" }, { @@ -3635,7 +3635,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:07:57Z", +"checked_at": "2026-09-04T10:18:45Z", "page_id": "73nj5jhb3tk4" }, { @@ -3647,7 +3647,7 @@ "description": "unknown", "open": 0, "error": "http 401", -"checked_at": "2026-09-04T09:07:57Z", +"checked_at": "2026-09-04T10:18:40Z", "page_id": null }, { @@ -3655,11 +3655,11 @@ "vendor": "Guidewire", "platform": "statuspage", "status_url": "https://status.guidewire.com", -"state": "ok", -"description": "All Systems Operational", -"open": 0, +"state": "maintenance", +"description": "All Systems Operational (scheduled maintenance in progress)", +"open": 1, "error": null, -"checked_at": "2026-09-04T09:07:58Z", +"checked_at": "2026-09-04T10:18:40Z", "page_id": "t71b941hl8l1" }, { @@ -3671,7 +3671,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:07:57Z", +"checked_at": "2026-09-04T10:18:40Z", "page_id": "241nygn31605" }, { @@ -3683,7 +3683,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:08:01Z", +"checked_at": "2026-09-04T10:18:40Z", "page_id": "fbhzv4f2nk7b" }, { @@ -3695,7 +3695,7 @@ "description": "Partially Degraded Service", "open": 0, "error": null, -"checked_at": "2026-09-04T09:08:00Z", +"checked_at": "2026-09-04T10:18:38Z", "page_id": "y82ckylcx8js" }, { @@ -3707,7 +3707,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:08:00Z", +"checked_at": "2026-09-04T10:18:45Z", "page_id": "zmnt6tkys0q0" }, { @@ -3719,7 +3719,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:08:00Z", +"checked_at": "2026-09-04T10:18:43Z", "page_id": "01K7FBWXHZPP52EWA3EGJ2SNVA" }, { @@ -3731,7 +3731,7 @@ "description": "operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:08:01Z", +"checked_at": "2026-09-04T10:18:45Z", "page_id": null }, { @@ -3743,7 +3743,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:08:00Z", +"checked_at": "2026-09-04T10:18:45Z", "page_id": "q4f4gt6nwhh0" }, { @@ -3755,7 +3755,7 @@ "description": "unknown", "open": 0, "error": "http 401", -"checked_at": "2026-09-04T09:08:05Z", +"checked_at": "2026-09-04T10:18:48Z", "page_id": null }, { @@ -3767,7 +3767,7 @@ "description": "operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:08:06Z", +"checked_at": "2026-09-04T10:18:53Z", "page_id": null }, { @@ -3779,7 +3779,7 @@ "description": "Minor Service Outage", "open": 0, "error": null, -"checked_at": "2026-09-04T09:08:00Z", +"checked_at": "2026-09-04T10:18:45Z", "page_id": "8ycs5cnqqv4v" }, { @@ -3791,7 +3791,7 @@ "description": "unknown", "open": 0, "error": "http 401", -"checked_at": "2026-09-04T09:08:06Z", +"checked_at": "2026-09-04T10:18:43Z", "page_id": null }, { @@ -3803,7 +3803,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:08:10Z", +"checked_at": "2026-09-04T10:18:50Z", "page_id": "0m1ljfvm0g6j" }, { @@ -3815,7 +3815,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:08:05Z", +"checked_at": "2026-09-04T10:18:45Z", "page_id": "01KD2YFBV44PW1DVCBYXJW3GJT" }, { @@ -3827,7 +3827,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:08:08Z", +"checked_at": "2026-09-04T10:18:45Z", "page_id": "0lqr48ns91hq" }, { @@ -3839,7 +3839,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:08:03Z", +"checked_at": "2026-09-04T10:18:48Z", "page_id": "7wygpzghm26t" }, { @@ -3851,7 +3851,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:08:03Z", +"checked_at": "2026-09-04T10:18:45Z", "page_id": "b2897hlz70j6" }, { @@ -3859,11 +3859,11 @@ "vendor": "HENNGE One", "platform": "statuspage", "status_url": "https://status.hdeone.com", -"state": "ok", -"description": "All Systems Operational", -"open": 0, +"state": "degraded", +"description": "Partially Degraded Service", +"open": 1, "error": null, -"checked_at": "2026-09-04T09:08:08Z", +"checked_at": "2026-09-04T10:18:48Z", "page_id": "lvh61jgflxk7" }, { @@ -3875,7 +3875,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:08:10Z", +"checked_at": "2026-09-04T10:18:49Z", "page_id": "dldtxmmgwzfd" }, { @@ -3887,7 +3887,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:08:08Z", +"checked_at": "2026-09-04T10:18:49Z", "page_id": "rthxyrqsy0m9" }, { @@ -3899,7 +3899,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:08:10Z", +"checked_at": "2026-09-04T10:18:49Z", "page_id": "5hzzb1l3fzyr" }, { @@ -3911,7 +3911,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:08:08Z", +"checked_at": "2026-09-04T10:18:52Z", "page_id": "yv0cybrq3zvh" }, { @@ -3923,7 +3923,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:08:09Z", +"checked_at": "2026-09-04T10:18:50Z", "page_id": "4qtx7fqj0z21" }, { @@ -3935,7 +3935,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:08:11Z", +"checked_at": "2026-09-04T10:18:51Z", "page_id": "mhm7t0098sfk" }, { @@ -3947,7 +3947,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:08:08Z", +"checked_at": "2026-09-04T10:18:54Z", "page_id": "6bqj9q95nrpr" }, { @@ -3959,7 +3959,7 @@ "description": "Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:08:10Z", +"checked_at": "2026-09-04T10:18:54Z", "page_id": "591aaa7fe69f388425000fda" }, { @@ -3971,7 +3971,7 @@ "description": "operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:08:12Z", +"checked_at": "2026-09-04T10:18:56Z", "page_id": null }, { @@ -3983,7 +3983,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:08:08Z", +"checked_at": "2026-09-04T10:18:56Z", "page_id": "kc6vcr54r52g" }, { @@ -3991,11 +3991,11 @@ "vendor": "HubSpot", "platform": "statuspage", "status_url": "https://status.hubspot.com", -"state": "degraded", -"description": "Minor Service Outage", -"open": 1, +"state": "ok", +"description": "All Systems Operational", +"open": 0, "error": null, -"checked_at": "2026-09-04T09:08:11Z", +"checked_at": "2026-09-04T10:18:54Z", "page_id": "8b9w1wwq3g7d" }, { @@ -4007,7 +4007,7 @@ "description": "operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:08:12Z", +"checked_at": "2026-09-04T10:18:56Z", "page_id": null }, { @@ -4019,7 +4019,7 @@ "description": "All Systems Operational", "open": 2, "error": null, -"checked_at": "2026-09-04T09:08:11Z", +"checked_at": "2026-09-04T10:18:56Z", "page_id": "3sxkxkb94xcp" }, { @@ -4031,7 +4031,7 @@ "description": "Partially Degraded Service", "open": 1, "error": null, -"checked_at": "2026-09-04T09:08:14Z", +"checked_at": "2026-09-04T10:18:52Z", "page_id": "4k5l2v70c39y" }, { @@ -4043,7 +4043,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:08:14Z", +"checked_at": "2026-09-04T10:18:53Z", "page_id": "01JXJ1XHQVTP425ZJYE9FDW1GS" }, { @@ -4055,7 +4055,7 @@ "description": "UP", "open": 0, "error": null, -"checked_at": "2026-09-04T09:08:11Z", +"checked_at": "2026-09-04T10:18:56Z", "page_id": null }, { @@ -4067,7 +4067,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:08:12Z", +"checked_at": "2026-09-04T10:18:54Z", "page_id": "qff0tnxzgs0q" }, { @@ -4079,7 +4079,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:08:14Z", +"checked_at": "2026-09-04T10:19:01Z", "page_id": "qhddg0t7xyb0" }, { @@ -4091,7 +4091,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:08:20Z", +"checked_at": "2026-09-04T10:18:55Z", "page_id": "hcfmhvpbqfb6" }, { @@ -4103,7 +4103,7 @@ "description": "Minor Service Outage", "open": 0, "error": null, -"checked_at": "2026-09-04T09:08:14Z", +"checked_at": "2026-09-04T10:19:01Z", "page_id": "fwm7958lkz7t" }, { @@ -4115,7 +4115,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:08:15Z", +"checked_at": "2026-09-04T10:19:01Z", "page_id": "c9yvrgjpyqyj" }, { @@ -4127,7 +4127,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:08:29Z", +"checked_at": "2026-09-04T10:19:00Z", "page_id": "hrvhvbbtk96c" }, { @@ -4139,7 +4139,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:08:14Z", +"checked_at": "2026-09-04T10:19:03Z", "page_id": "032k0f0j3bsz" }, { @@ -4151,7 +4151,7 @@ "description": "Service Under Maintenance", "open": 0, "error": null, -"checked_at": "2026-09-04T09:08:18Z", +"checked_at": "2026-09-04T10:19:00Z", "page_id": "4dbnz6n8nkt2" }, { @@ -4163,7 +4163,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:08:18Z", +"checked_at": "2026-09-04T10:18:56Z", "page_id": "n3wh2xdrss43" }, { @@ -4175,7 +4175,7 @@ "description": "Service Under Maintenance", "open": 1, "error": null, -"checked_at": "2026-09-04T09:08:15Z", +"checked_at": "2026-09-04T10:19:01Z", "page_id": "qwdhlrdy1q07" }, { @@ -4187,7 +4187,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:08:15Z", +"checked_at": "2026-09-04T10:18:58Z", "page_id": "hfq2h9152m63" }, { @@ -4199,7 +4199,7 @@ "description": "unknown", "open": 0, "error": "moved: not a statuspage any more", -"checked_at": "2026-09-04T09:08:19Z", +"checked_at": "2026-09-04T10:19:02Z", "page_id": null }, { @@ -4209,9 +4209,9 @@ "status_url": "https://status.ingage.jp", "state": "ok", "description": "All Systems Operational", -"open": 1, +"open": 0, "error": null, -"checked_at": "2026-09-04T09:08:26Z", +"checked_at": "2026-09-04T10:19:00Z", "page_id": "dzbpdkzhcjqs" }, { @@ -4223,7 +4223,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:08:21Z", +"checked_at": "2026-09-04T10:19:01Z", "page_id": "wd352sdby1b2" }, { @@ -4235,7 +4235,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:08:18Z", +"checked_at": "2026-09-04T10:18:59Z", "page_id": "lcmq278q15vk" }, { @@ -4247,7 +4247,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:08:16Z", +"checked_at": "2026-09-04T10:18:58Z", "page_id": "1j54m0gcstxg" }, { @@ -4259,7 +4259,7 @@ "description": "UP", "open": 0, "error": null, -"checked_at": "2026-09-04T09:08:26Z", +"checked_at": "2026-09-04T10:19:03Z", "page_id": null }, { @@ -4271,7 +4271,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:08:18Z", +"checked_at": "2026-09-04T10:19:03Z", "page_id": "6d2y771xlz01" }, { @@ -4283,7 +4283,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:08:26Z", +"checked_at": "2026-09-04T10:19:02Z", "page_id": "44h9s96v7cnh" }, { @@ -4295,7 +4295,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:08:30Z", +"checked_at": "2026-09-04T10:19:08Z", "page_id": "b4qwtxsh8hth" }, { @@ -4307,7 +4307,7 @@ "description": "All Systems Operational", "open": 1, "error": null, -"checked_at": "2026-09-04T09:08:23Z", +"checked_at": "2026-09-04T10:19:06Z", "page_id": "383ggbd6fsc8" }, { @@ -4319,7 +4319,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:08:22Z", +"checked_at": "2026-09-04T10:19:05Z", "page_id": "6ztkzlvks30f" }, { @@ -4331,7 +4331,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:08:22Z", +"checked_at": "2026-09-04T10:19:06Z", "page_id": "4w97pyfbfmqf" }, { @@ -4343,7 +4343,7 @@ "description": "Service Under Maintenance", "open": 2, "error": null, -"checked_at": "2026-09-04T09:08:22Z", +"checked_at": "2026-09-04T10:19:05Z", "page_id": "4tdc8ll7wtnf" }, { @@ -4355,7 +4355,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:08:24Z", +"checked_at": "2026-09-04T10:19:13Z", "page_id": "l4wxddfpxjw0" }, { @@ -4367,7 +4367,7 @@ "description": "All Systems Operational", "open": 2, "error": null, -"checked_at": "2026-09-04T09:08:25Z", +"checked_at": "2026-09-04T10:19:08Z", "page_id": "xdhr50sc5fkm" }, { @@ -4379,7 +4379,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:08:22Z", +"checked_at": "2026-09-04T10:19:08Z", "page_id": "wb4ljr0q8dfj" }, { @@ -4391,7 +4391,7 @@ "description": "Service Under Maintenance", "open": 1, "error": null, -"checked_at": "2026-09-04T09:08:29Z", +"checked_at": "2026-09-04T10:19:08Z", "page_id": "93ywsp42bpfg" }, { @@ -4403,7 +4403,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:08:27Z", +"checked_at": "2026-09-04T10:19:10Z", "page_id": "l87djxscpklj" }, { @@ -4415,7 +4415,7 @@ "description": "Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:08:28Z", +"checked_at": "2026-09-04T10:19:09Z", "page_id": "6009d1de31d97c052fce18d7" }, { @@ -4427,7 +4427,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:08:23Z", +"checked_at": "2026-09-04T10:19:08Z", "page_id": "lgc8wg9sgd81" }, { @@ -4439,7 +4439,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:08:28Z", +"checked_at": "2026-09-04T10:19:19Z", "page_id": "4hyb9xl50gtg" }, { @@ -4451,7 +4451,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:08:26Z", +"checked_at": "2026-09-04T10:19:08Z", "page_id": "r9ctb80km09x" }, { @@ -4463,7 +4463,7 @@ "description": "unknown", "open": 0, "error": "http 401", -"checked_at": "2026-09-04T09:08:34Z", +"checked_at": "2026-09-04T10:19:18Z", "page_id": null }, { @@ -4475,7 +4475,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:08:29Z", +"checked_at": "2026-09-04T10:19:10Z", "page_id": "1lhk9566yrfp" }, { @@ -4487,7 +4487,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:08:30Z", +"checked_at": "2026-09-04T10:19:17Z", "page_id": "m8mhskh2nzjb" }, { @@ -4499,7 +4499,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:08:31Z", +"checked_at": "2026-09-04T10:19:13Z", "page_id": "5z7bmx2nb2yj" }, { @@ -4511,7 +4511,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:08:31Z", +"checked_at": "2026-09-04T10:19:11Z", "page_id": "qc97d0m42ltj" }, { @@ -4523,7 +4523,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:08:31Z", +"checked_at": "2026-09-04T10:19:14Z", "page_id": "9v2sbrktwycl" }, { @@ -4535,7 +4535,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:08:31Z", +"checked_at": "2026-09-04T10:19:10Z", "page_id": "jrg4crndtsgz" }, { @@ -4547,7 +4547,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:08:31Z", +"checked_at": "2026-09-04T10:19:13Z", "page_id": "qmzzdxyvmbmk" }, { @@ -4559,7 +4559,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:08:31Z", +"checked_at": "2026-09-04T10:19:16Z", "page_id": "pv54g7ltsc24" }, { @@ -4571,7 +4571,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:08:31Z", +"checked_at": "2026-09-04T10:19:13Z", "page_id": "s6f0gm5gcpmy" }, { @@ -4583,7 +4583,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:08:32Z", +"checked_at": "2026-09-04T10:19:16Z", "page_id": "wdh4b96pzcv9" }, { @@ -4595,7 +4595,7 @@ "description": "unknown", "open": 0, "error": "http 401", -"checked_at": "2026-09-04T09:08:40Z", +"checked_at": "2026-09-04T10:19:25Z", "page_id": null }, { @@ -4607,7 +4607,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:08:31Z", +"checked_at": "2026-09-04T10:19:13Z", "page_id": "1sbvq38wp4wf" }, { @@ -4619,7 +4619,7 @@ "description": "operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:08:36Z", +"checked_at": "2026-09-04T10:19:14Z", "page_id": null }, { @@ -4631,7 +4631,7 @@ "description": "Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:08:42Z", +"checked_at": "2026-09-04T10:19:15Z", "page_id": "595c662f0b000d7d48001cb9" }, { @@ -4643,7 +4643,7 @@ "description": "unknown", "open": 0, "error": "moved: not a statuspage any more", -"checked_at": "2026-09-04T09:08:48Z", +"checked_at": "2026-09-04T10:19:18Z", "page_id": null }, { @@ -4654,8 +4654,8 @@ "state": "unknown", "description": "unknown", "open": 0, -"error": "http 0", -"checked_at": "2026-09-04T09:08:58Z", +"error": "moved: not a statuspage any more", +"checked_at": "2026-09-04T10:19:32Z", "page_id": null }, { @@ -4667,7 +4667,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:08:34Z", +"checked_at": "2026-09-04T10:19:20Z", "page_id": "wg5bvczw1rtf" }, { @@ -4679,7 +4679,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:08:35Z", +"checked_at": "2026-09-04T10:19:19Z", "page_id": "4bfd6xnhjgv8" }, { @@ -4691,7 +4691,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:08:42Z", +"checked_at": "2026-09-04T10:19:20Z", "page_id": "16vdh7mgpq08" }, { @@ -4703,7 +4703,7 @@ "description": "unknown", "open": 0, "error": "moved: not a statuspage any more", -"checked_at": "2026-09-04T09:08:40Z", +"checked_at": "2026-09-04T10:19:29Z", "page_id": null }, { @@ -4715,7 +4715,7 @@ "description": "All Systems Operational", "open": 1, "error": null, -"checked_at": "2026-09-04T09:08:40Z", +"checked_at": "2026-09-04T10:19:29Z", "page_id": "z5m1d7k4jblh" }, { @@ -4725,9 +4725,9 @@ "status_url": "https://status.kinsta.com", "state": "maintenance", "description": "Service Under Maintenance", -"open": 3, +"open": 2, "error": null, -"checked_at": "2026-09-04T09:08:40Z", +"checked_at": "2026-09-04T10:19:20Z", "page_id": "xy8sb5hf1p24" }, { @@ -4739,7 +4739,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:08:40Z", +"checked_at": "2026-09-04T10:19:18Z", "page_id": "bgczv594g2wz" }, { @@ -4751,7 +4751,7 @@ "description": "All Systems Operational", "open": 1, "error": null, -"checked_at": "2026-09-04T09:08:40Z", +"checked_at": "2026-09-04T10:19:24Z", "page_id": "bzcwcdz7454v" }, { @@ -4763,7 +4763,7 @@ "description": "unknown", "open": 0, "error": "moved: not a statuspage any more", -"checked_at": "2026-09-04T09:08:47Z", +"checked_at": "2026-09-04T10:19:22Z", "page_id": null }, { @@ -4775,7 +4775,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:08:42Z", +"checked_at": "2026-09-04T10:19:26Z", "page_id": "nmb4rzn4z0jp" }, { @@ -4785,9 +4785,9 @@ "status_url": "https://status.kraken.com", "state": "degraded", "description": "Partially Degraded Service", -"open": 6, +"open": 5, "error": null, -"checked_at": "2026-09-04T09:08:41Z", +"checked_at": "2026-09-04T10:19:20Z", "page_id": "lfz25gyhcpjf" }, { @@ -4799,7 +4799,7 @@ "description": "unknown", "open": 0, "error": "http 401", -"checked_at": "2026-09-04T09:08:49Z", +"checked_at": "2026-09-04T10:19:31Z", "page_id": null }, { @@ -4811,7 +4811,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:08:42Z", +"checked_at": "2026-09-04T10:19:20Z", "page_id": "x0x5dqxxsdwb" }, { @@ -4823,7 +4823,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:08:44Z", +"checked_at": "2026-09-04T10:19:22Z", "page_id": "9404kdk7lkn7" }, { @@ -4835,7 +4835,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:08:43Z", +"checked_at": "2026-09-04T10:19:32Z", "page_id": "01GZKJ3NDY6EN3SYFYEQRDBS2M" }, { @@ -4847,7 +4847,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:08:42Z", +"checked_at": "2026-09-04T10:19:25Z", "page_id": "5r89fgb80dvg" }, { @@ -4859,7 +4859,7 @@ "description": "Partially Degraded Service", "open": 1, "error": null, -"checked_at": "2026-09-04T09:08:42Z", +"checked_at": "2026-09-04T10:19:26Z", "page_id": "767c5rcj7z12" }, { @@ -4871,7 +4871,7 @@ "description": "Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:08:42Z", +"checked_at": "2026-09-04T10:19:29Z", "page_id": "55957a99e800baa4470002da" }, { @@ -4883,7 +4883,7 @@ "description": "Partial System Outage", "open": 0, "error": null, -"checked_at": "2026-09-04T09:08:42Z", +"checked_at": "2026-09-04T10:19:25Z", "page_id": "v6z1p4pf4qzk" }, { @@ -4895,7 +4895,7 @@ "description": "operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:08:45Z", +"checked_at": "2026-09-04T10:19:27Z", "page_id": null }, { @@ -4907,7 +4907,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:09:00Z", +"checked_at": "2026-09-04T10:19:29Z", "page_id": "2fpdbpm5f67c" }, { @@ -4919,7 +4919,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:08:49Z", +"checked_at": "2026-09-04T10:19:26Z", "page_id": "7c66ps9x5g90" }, { @@ -4931,7 +4931,7 @@ "description": "Partially Degraded Service", "open": 0, "error": null, -"checked_at": "2026-09-04T09:08:48Z", +"checked_at": "2026-09-04T10:19:31Z", "page_id": "ykt0n7w31hlt" }, { @@ -4943,7 +4943,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:08:48Z", +"checked_at": "2026-09-04T10:19:29Z", "page_id": "01GYJ3SH6BPHBR7V0GQAW4GTM0" }, { @@ -4955,7 +4955,7 @@ "description": "All Systems Operational", "open": 1, "error": null, -"checked_at": "2026-09-04T09:08:44Z", +"checked_at": "2026-09-04T10:19:29Z", "page_id": "8dn0wstr1chc" }, { @@ -4967,7 +4967,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:08:47Z", +"checked_at": "2026-09-04T10:19:28Z", "page_id": "fs1jftf56rrr" }, { @@ -4979,7 +4979,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:08:44Z", +"checked_at": "2026-09-04T10:19:32Z", "page_id": "01K4DA4AT80YHJ6G0PNDP1XSRG" }, { @@ -4991,7 +4991,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:08:46Z", +"checked_at": "2026-09-04T10:19:29Z", "page_id": "4718t1z3swn2" }, { @@ -5003,7 +5003,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:08:47Z", +"checked_at": "2026-09-04T10:19:34Z", "page_id": "jxq5p24dzglq" }, { @@ -5015,7 +5015,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:08:55Z", +"checked_at": "2026-09-04T10:19:34Z", "page_id": "flbqdmg201t4" }, { @@ -5027,7 +5027,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:08:51Z", +"checked_at": "2026-09-04T10:19:35Z", "page_id": "v7htgzpzxwsh" }, { @@ -5039,7 +5039,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:08:56Z", +"checked_at": "2026-09-04T10:19:32Z", "page_id": "sjdfmj9dd7zz" }, { @@ -5051,7 +5051,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:08:50Z", +"checked_at": "2026-09-04T10:19:34Z", "page_id": "df7fz4dgtpry" }, { @@ -5063,7 +5063,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:08:58Z", +"checked_at": "2026-09-04T10:19:32Z", "page_id": "kcbfcfjjpkdg" }, { @@ -5075,7 +5075,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:08:54Z", +"checked_at": "2026-09-04T10:19:35Z", "page_id": "tbzrhcdrtv38" }, { @@ -5087,7 +5087,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:08:54Z", +"checked_at": "2026-09-04T10:19:35Z", "page_id": "mtt4gs57z0sn" }, { @@ -5099,7 +5099,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:08:51Z", +"checked_at": "2026-09-04T10:19:38Z", "page_id": "01JJPY3HJYMSV1REXAC7D66X0Z" }, { @@ -5111,7 +5111,7 @@ "description": "All Systems Operational (scheduled maintenance in progress)", "open": 4, "error": null, -"checked_at": "2026-09-04T09:08:51Z", +"checked_at": "2026-09-04T10:19:35Z", "page_id": "97nm731spwzy" }, { @@ -5123,7 +5123,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:08:52Z", +"checked_at": "2026-09-04T10:19:38Z", "page_id": "swcqqk7psrfy" }, { @@ -5135,7 +5135,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:08:53Z", +"checked_at": "2026-09-04T10:19:39Z", "page_id": "pfmdf569fnrr" }, { @@ -5147,7 +5147,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:08:59Z", +"checked_at": "2026-09-04T10:19:35Z", "page_id": "zwg5vlmkjfks" }, { @@ -5159,7 +5159,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:08:59Z", +"checked_at": "2026-09-04T10:19:42Z", "page_id": "zcn9991lf6mb" }, { @@ -5171,7 +5171,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:08:59Z", +"checked_at": "2026-09-04T10:19:38Z", "page_id": "b5x9lmxnhtty" }, { @@ -5183,7 +5183,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:09:01Z", +"checked_at": "2026-09-04T10:19:42Z", "page_id": "745h3w950km3" }, { @@ -5195,7 +5195,7 @@ "description": "UP", "open": 0, "error": null, -"checked_at": "2026-09-04T09:08:59Z", +"checked_at": "2026-09-04T10:19:38Z", "page_id": null }, { @@ -5207,7 +5207,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:08:56Z", +"checked_at": "2026-09-04T10:19:38Z", "page_id": "6jp439mdyy0k" }, { @@ -5219,7 +5219,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:08:58Z", +"checked_at": "2026-09-04T10:19:40Z", "page_id": "y62qy4nt734y" }, { @@ -5231,7 +5231,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:08:57Z", +"checked_at": "2026-09-04T10:19:41Z", "page_id": "1qv141kvmryj" }, { @@ -5243,7 +5243,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:09:00Z", +"checked_at": "2026-09-04T10:19:44Z", "page_id": "l7zzgtkbd195" }, { @@ -5255,7 +5255,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:09:00Z", +"checked_at": "2026-09-04T10:19:47Z", "page_id": "bv3pf3wkkxt4" }, { @@ -5267,7 +5267,7 @@ "description": "Minor Service Outage", "open": 0, "error": null, -"checked_at": "2026-09-04T09:08:59Z", +"checked_at": "2026-09-04T10:19:44Z", "page_id": "d429lk1p6zj3" }, { @@ -5279,7 +5279,7 @@ "description": "Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:09:01Z", +"checked_at": "2026-09-04T10:19:46Z", "page_id": "53fcfbb2ac0c957972000235" }, { @@ -5291,7 +5291,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:08:56Z", +"checked_at": "2026-09-04T10:19:44Z", "page_id": "01HXRMEVMGN2DFKXH927VPQBK8" }, { @@ -5303,7 +5303,7 @@ "description": "Partially Degraded Service", "open": 1, "error": null, -"checked_at": "2026-09-04T09:09:01Z", +"checked_at": "2026-09-04T10:19:42Z", "page_id": "4rqwgw8gmq9t" }, { @@ -5315,7 +5315,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:09:03Z", +"checked_at": "2026-09-04T10:19:47Z", "page_id": "5bhglqd14x7q" }, { @@ -5327,7 +5327,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:09:01Z", +"checked_at": "2026-09-04T10:19:42Z", "page_id": "n1pskh7dw1c1" }, { @@ -5339,7 +5339,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:09:08Z", +"checked_at": "2026-09-04T10:19:48Z", "page_id": "cl25nd1s1tdr" }, { @@ -5351,7 +5351,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:09:02Z", +"checked_at": "2026-09-04T10:19:47Z", "page_id": "lwvwwrw7bz5g" }, { @@ -5363,7 +5363,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:09:01Z", +"checked_at": "2026-09-04T10:19:42Z", "page_id": "sd681bblkv85" }, { @@ -5375,7 +5375,7 @@ "description": "Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:09:08Z", +"checked_at": "2026-09-04T10:19:43Z", "page_id": "5d849b1c02e65b3ec45369d4" }, { @@ -5387,7 +5387,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:09:02Z", +"checked_at": "2026-09-04T10:19:47Z", "page_id": "01JGBY6SXZ5B7XAV0K4CFM96F0" }, { @@ -5399,7 +5399,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:09:10Z", +"checked_at": "2026-09-04T10:19:47Z", "page_id": "x4m91ldrf511" }, { @@ -5411,7 +5411,7 @@ "description": "UP", "open": 0, "error": null, -"checked_at": "2026-09-04T09:09:08Z", +"checked_at": "2026-09-04T10:19:50Z", "page_id": null }, { @@ -5423,7 +5423,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:09:06Z", +"checked_at": "2026-09-04T10:19:51Z", "page_id": "th35d4vb90h8" }, { @@ -5435,7 +5435,7 @@ "description": "unknown", "open": 0, "error": "moved: not a statuspage any more", -"checked_at": "2026-09-04T09:09:21Z", +"checked_at": "2026-09-04T10:19:57Z", "page_id": null }, { @@ -5447,7 +5447,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:09:06Z", +"checked_at": "2026-09-04T10:19:51Z", "page_id": "zh081jts88wj" }, { @@ -5459,7 +5459,7 @@ "description": "Minor Service Outage", "open": 1, "error": null, -"checked_at": "2026-09-04T09:09:11Z", +"checked_at": "2026-09-04T10:19:54Z", "page_id": "smhnl3lt74kc" }, { @@ -5471,7 +5471,7 @@ "description": "Partially Degraded Service", "open": 2, "error": null, -"checked_at": "2026-09-04T09:09:07Z", +"checked_at": "2026-09-04T10:19:50Z", "page_id": "43s1wxzggr85" }, { @@ -5483,7 +5483,7 @@ "description": "Partially Degraded Service", "open": 0, "error": null, -"checked_at": "2026-09-04T09:09:08Z", +"checked_at": "2026-09-04T10:19:54Z", "page_id": "zv8vqrk872kx" }, { @@ -5495,7 +5495,7 @@ "description": "operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:09:11Z", +"checked_at": "2026-09-04T10:19:54Z", "page_id": null }, { @@ -5507,7 +5507,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:09:08Z", +"checked_at": "2026-09-04T10:19:54Z", "page_id": "dbk70dpy3n7h" }, { @@ -5519,7 +5519,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:09:11Z", +"checked_at": "2026-09-04T10:19:58Z", "page_id": "gjwsnqwfgt86" }, { @@ -5531,7 +5531,7 @@ "description": "UP", "open": 0, "error": null, -"checked_at": "2026-09-04T09:09:11Z", +"checked_at": "2026-09-04T10:19:51Z", "page_id": null }, { @@ -5543,7 +5543,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:09:11Z", +"checked_at": "2026-09-04T10:19:53Z", "page_id": "3nnwdbs2nsdq" }, { @@ -5555,7 +5555,7 @@ "description": "All Systems Operational", "open": 1, "error": null, -"checked_at": "2026-09-04T09:09:12Z", +"checked_at": "2026-09-04T10:19:55Z", "page_id": "blcknqccsgzp" }, { @@ -5567,7 +5567,7 @@ "description": "Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:09:11Z", +"checked_at": "2026-09-04T10:19:53Z", "page_id": "6878fc85709daa75be6c7e3c" }, { @@ -5579,7 +5579,7 @@ "description": "Service Under Maintenance", "open": 0, "error": null, -"checked_at": "2026-09-04T09:09:17Z", +"checked_at": "2026-09-04T10:19:50Z", "page_id": "y7hbrgx5qqkb" }, { @@ -5591,7 +5591,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:09:11Z", +"checked_at": "2026-09-04T10:19:58Z", "page_id": "pxgmzwrrkxcn" }, { @@ -5603,7 +5603,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:09:17Z", +"checked_at": "2026-09-04T10:20:03Z", "page_id": "87sx0yb3q2f6" }, { @@ -5615,7 +5615,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:09:19Z", +"checked_at": "2026-09-04T10:20:01Z", "page_id": "83dz7syz0j3x" }, { @@ -5627,7 +5627,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:09:19Z", +"checked_at": "2026-09-04T10:19:57Z", "page_id": "ld01ws8wgxvv" }, { @@ -5639,7 +5639,7 @@ "description": "unknown", "open": 0, "error": "moved: not a statuspage any more", -"checked_at": "2026-09-04T09:09:25Z", +"checked_at": "2026-09-04T10:20:03Z", "page_id": null }, { @@ -5651,7 +5651,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:09:14Z", +"checked_at": "2026-09-04T10:19:58Z", "page_id": "bvsg7njflx8d" }, { @@ -5663,7 +5663,7 @@ "description": "UP", "open": 0, "error": null, -"checked_at": "2026-09-04T09:09:15Z", +"checked_at": "2026-09-04T10:19:57Z", "page_id": null }, { @@ -5675,7 +5675,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:09:13Z", +"checked_at": "2026-09-04T10:19:57Z", "page_id": "xc8f093vf5r6" }, { @@ -5687,7 +5687,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:09:13Z", +"checked_at": "2026-09-04T10:20:04Z", "page_id": "bn2lkk4ydhhs" }, { @@ -5699,7 +5699,7 @@ "description": "Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:09:14Z", +"checked_at": "2026-09-04T10:19:56Z", "page_id": "566925105401bb333d000014" }, { @@ -5711,7 +5711,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:09:15Z", +"checked_at": "2026-09-04T10:20:03Z", "page_id": "jx3xhhwkfjhf" }, { @@ -5723,7 +5723,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:09:19Z", +"checked_at": "2026-09-04T10:20:03Z", "page_id": "j5r1mms1453g" }, { @@ -5735,7 +5735,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:09:19Z", +"checked_at": "2026-09-04T10:20:04Z", "page_id": "vss0s7nbybhn" }, { @@ -5747,7 +5747,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:09:19Z", +"checked_at": "2026-09-04T10:19:58Z", "page_id": "j0mnw8rsnc61" }, { @@ -5759,7 +5759,7 @@ "description": "UP", "open": 0, "error": null, -"checked_at": "2026-09-04T09:09:18Z", +"checked_at": "2026-09-04T10:20:03Z", "page_id": null }, { @@ -5771,7 +5771,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:09:17Z", +"checked_at": "2026-09-04T10:20:03Z", "page_id": "16jh5tyrns46" }, { @@ -5783,7 +5783,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:09:20Z", +"checked_at": "2026-09-04T10:20:03Z", "page_id": "wyvgptkd90hm" }, { @@ -5795,7 +5795,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:09:20Z", +"checked_at": "2026-09-04T10:19:59Z", "page_id": "1wjp5zp9tl7z" }, { @@ -5807,7 +5807,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:09:21Z", +"checked_at": "2026-09-04T10:20:05Z", "page_id": "msx9vl24v14h" }, { @@ -5819,7 +5819,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:09:19Z", +"checked_at": "2026-09-04T10:20:00Z", "page_id": "t28j4gy8rckd" }, { @@ -5831,7 +5831,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:09:20Z", +"checked_at": "2026-09-04T10:20:07Z", "page_id": "2qwvjdg4xvkv" }, { @@ -5843,7 +5843,7 @@ "description": "All Systems Operational", "open": 5, "error": null, -"checked_at": "2026-09-04T09:09:23Z", +"checked_at": "2026-09-04T10:20:01Z", "page_id": "2bdwmtrb0hg9" }, { @@ -5855,7 +5855,7 @@ "description": "unknown", "open": 0, "error": "moved: not a statuspage any more", -"checked_at": "2026-09-04T09:09:26Z", +"checked_at": "2026-09-04T10:20:08Z", "page_id": null }, { @@ -5867,7 +5867,7 @@ "description": "Operational", "open": 1, "error": null, -"checked_at": "2026-09-04T09:09:25Z", +"checked_at": "2026-09-04T10:20:08Z", "page_id": "53cd83d756bbe4a329000456" }, { @@ -5879,7 +5879,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:09:21Z", +"checked_at": "2026-09-04T10:20:13Z", "page_id": "0y2rrttfrd4v" }, { @@ -5891,7 +5891,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:09:19Z", +"checked_at": "2026-09-04T10:20:08Z", "page_id": "5lcqn2qgjtrb" }, { @@ -5903,7 +5903,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:09:23Z", +"checked_at": "2026-09-04T10:20:09Z", "page_id": "68h22lsztll6" }, { @@ -5915,7 +5915,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:09:26Z", +"checked_at": "2026-09-04T10:20:10Z", "page_id": "47k0tntjbb95" }, { @@ -5923,11 +5923,11 @@ "vendor": "One", "platform": "statuspage", "status_url": "https://status.one.com", -"state": "degraded", -"description": "Partially Degraded Service", -"open": 1, +"state": "ok", +"description": "All Systems Operational", +"open": 0, "error": null, -"checked_at": "2026-09-04T09:09:23Z", +"checked_at": "2026-09-04T10:20:07Z", "page_id": "cm5sx5y252x4" }, { @@ -5939,7 +5939,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:09:27Z", +"checked_at": "2026-09-04T10:20:14Z", "page_id": "38c70q4r0gw8" }, { @@ -5951,7 +5951,7 @@ "description": "Partial System Degradation", "open": 1, "error": null, -"checked_at": "2026-09-04T09:09:28Z", +"checked_at": "2026-09-04T10:20:08Z", "page_id": "01JMDK9XYNY6RXSED6SDWW50WY" }, { @@ -5963,7 +5963,7 @@ "description": "UP", "open": 0, "error": null, -"checked_at": "2026-09-04T09:09:27Z", +"checked_at": "2026-09-04T10:20:08Z", "page_id": null }, { @@ -5975,7 +5975,7 @@ "description": "operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:09:24Z", +"checked_at": "2026-09-04T10:20:09Z", "page_id": null }, { @@ -5987,7 +5987,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:09:26Z", +"checked_at": "2026-09-04T10:20:07Z", "page_id": "z132vgt74pff" }, { @@ -5999,7 +5999,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:09:28Z", +"checked_at": "2026-09-04T10:20:14Z", "page_id": "jzcq22pjyx7y" }, { @@ -6011,7 +6011,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:09:28Z", +"checked_at": "2026-09-04T10:20:12Z", "page_id": "rcs5256c5q75" }, { @@ -6023,7 +6023,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:09:29Z", +"checked_at": "2026-09-04T10:20:13Z", "page_id": "k3vdpzlnnrz5" }, { @@ -6035,7 +6035,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:09:32Z", +"checked_at": "2026-09-04T10:20:19Z", "page_id": "ysw4wb9sb5z5" }, { @@ -6047,7 +6047,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:09:35Z", +"checked_at": "2026-09-04T10:20:15Z", "page_id": "7mf88krcygn3" }, { @@ -6059,7 +6059,7 @@ "description": "UP", "open": 0, "error": null, -"checked_at": "2026-09-04T09:09:28Z", +"checked_at": "2026-09-04T10:20:13Z", "page_id": null }, { @@ -6071,7 +6071,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:09:35Z", +"checked_at": "2026-09-04T10:20:14Z", "page_id": "4ttgvbm11nl6" }, { @@ -6083,7 +6083,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:09:32Z", +"checked_at": "2026-09-04T10:20:12Z", "page_id": "q31kxsyj3vxj" }, { @@ -6095,7 +6095,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:09:32Z", +"checked_at": "2026-09-04T10:20:14Z", "page_id": "y3w1zdyn47dm" }, { @@ -6107,7 +6107,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:09:27Z", +"checked_at": "2026-09-04T10:20:14Z", "page_id": "vplwwxhc1z3n" }, { @@ -6119,7 +6119,7 @@ "description": "Partial System Outage", "open": 0, "error": null, -"checked_at": "2026-09-04T09:09:32Z", +"checked_at": "2026-09-04T10:20:12Z", "page_id": "w2l85pjbb8m3" }, { @@ -6131,7 +6131,7 @@ "description": "Planned Maintenance", "open": 5, "error": null, -"checked_at": "2026-09-04T09:09:32Z", +"checked_at": "2026-09-04T10:20:12Z", "page_id": "59dd23da8827c804746f1664" }, { @@ -6143,7 +6143,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:09:35Z", +"checked_at": "2026-09-04T10:20:19Z", "page_id": "v1fst6j5n1rw" }, { @@ -6155,7 +6155,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:09:32Z", +"checked_at": "2026-09-04T10:20:19Z", "page_id": "39f8vhy6rw5d" }, { @@ -6167,7 +6167,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:09:32Z", +"checked_at": "2026-09-04T10:20:15Z", "page_id": "b24rsfmxwsvk" }, { @@ -6179,7 +6179,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:09:32Z", +"checked_at": "2026-09-04T10:20:20Z", "page_id": "80f0zgsx80zh" }, { @@ -6187,11 +6187,11 @@ "vendor": "Panther Labs", "platform": "statuspage", "status_url": "https://status.panther.com", -"state": "degraded", -"description": "Minor Service Outage", +"state": "ok", +"description": "All Systems Operational", "open": 1, "error": null, -"checked_at": "2026-09-04T09:09:35Z", +"checked_at": "2026-09-04T10:20:18Z", "page_id": "7l8f9m2hxglm" }, { @@ -6203,7 +6203,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:09:32Z", +"checked_at": "2026-09-04T10:20:20Z", "page_id": "n7bs3zmrqq63" }, { @@ -6215,7 +6215,7 @@ "description": "All Systems Operational", "open": 1, "error": null, -"checked_at": "2026-09-04T09:09:35Z", +"checked_at": "2026-09-04T10:20:16Z", "page_id": "6m96vp32n0mz" }, { @@ -6227,7 +6227,7 @@ "description": "Partial System Outage", "open": 4, "error": null, -"checked_at": "2026-09-04T09:09:37Z", +"checked_at": "2026-09-04T10:20:18Z", "page_id": "zdrhzpgtdr4q" }, { @@ -6239,7 +6239,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:09:32Z", +"checked_at": "2026-09-04T10:20:21Z", "page_id": "8d849mp6fy12" }, { @@ -6251,7 +6251,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:09:35Z", +"checked_at": "2026-09-04T10:20:21Z", "page_id": "2d8szqmjt2tx" }, { @@ -6263,7 +6263,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:09:35Z", +"checked_at": "2026-09-04T10:20:24Z", "page_id": "pz8szngcwjmz" }, { @@ -6275,7 +6275,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:09:35Z", +"checked_at": "2026-09-04T10:20:19Z", "page_id": "y7h9b9dm0msn" }, { @@ -6287,7 +6287,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:09:37Z", +"checked_at": "2026-09-04T10:20:20Z", "page_id": "8gvw26l8kc3d" }, { @@ -6299,7 +6299,7 @@ "description": "Partially Degraded Service", "open": 1, "error": null, -"checked_at": "2026-09-04T09:09:47Z", +"checked_at": "2026-09-04T10:20:17Z", "page_id": "6fgwm4l2w2yb" }, { @@ -6311,7 +6311,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:09:37Z", +"checked_at": "2026-09-04T10:20:24Z", "page_id": "qxvy69hcwh22" }, { @@ -6323,7 +6323,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:09:37Z", +"checked_at": "2026-09-04T10:20:21Z", "page_id": "qm66bvqg0y7j" }, { @@ -6335,7 +6335,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:09:39Z", +"checked_at": "2026-09-04T10:20:24Z", "page_id": "svch3z6qrnbw" }, { @@ -6347,7 +6347,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:09:57Z", +"checked_at": "2026-09-04T10:20:29Z", "page_id": "5rr9295zs9vm" }, { @@ -6359,7 +6359,7 @@ "description": "UP", "open": 0, "error": null, -"checked_at": "2026-09-04T09:09:45Z", +"checked_at": "2026-09-04T10:20:24Z", "page_id": null }, { @@ -6371,7 +6371,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:09:45Z", +"checked_at": "2026-09-04T10:20:25Z", "page_id": "xl1jfdffsz3j" }, { @@ -6383,7 +6383,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:09:44Z", +"checked_at": "2026-09-04T10:20:25Z", "page_id": "619nm1q7y3ql" }, { @@ -6395,7 +6395,7 @@ "description": "UP", "open": 0, "error": null, -"checked_at": "2026-09-04T09:09:39Z", +"checked_at": "2026-09-04T10:20:28Z", "page_id": null }, { @@ -6407,7 +6407,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:09:45Z", +"checked_at": "2026-09-04T10:20:32Z", "page_id": "411rdjf37cvk" }, { @@ -6419,7 +6419,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:09:44Z", +"checked_at": "2026-09-04T10:20:30Z", "page_id": "hbhghxc6klrw" }, { @@ -6431,7 +6431,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:09:39Z", +"checked_at": "2026-09-04T10:20:37Z", "page_id": "01KPXTKZQWD52QY8AMF705E69F" }, { @@ -6443,7 +6443,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:09:45Z", +"checked_at": "2026-09-04T10:20:26Z", "page_id": "01KJ72XDYEXAHDV9SPTMB7YS2Y" }, { @@ -6455,7 +6455,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:09:45Z", +"checked_at": "2026-09-04T10:20:30Z", "page_id": "01GX91T1T0RXR54F1EKBQMAYCJ" }, { @@ -6467,7 +6467,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:09:45Z", +"checked_at": "2026-09-04T10:20:29Z", "page_id": "9303wxq6qx8t" }, { @@ -6479,7 +6479,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:09:45Z", +"checked_at": "2026-09-04T10:20:27Z", "page_id": "hndmlgmdcpdk" }, { @@ -6491,7 +6491,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:09:48Z", +"checked_at": "2026-09-04T10:20:32Z", "page_id": "kph7ld18zxyq" }, { @@ -6503,7 +6503,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:09:48Z", +"checked_at": "2026-09-04T10:20:32Z", "page_id": "n86f23gkzd8k" }, { @@ -6515,7 +6515,7 @@ "description": "UP", "open": 0, "error": null, -"checked_at": "2026-09-04T09:09:48Z", +"checked_at": "2026-09-04T10:20:31Z", "page_id": null }, { @@ -6527,7 +6527,7 @@ "description": "Service Under Maintenance", "open": 1, "error": null, -"checked_at": "2026-09-04T09:09:49Z", +"checked_at": "2026-09-04T10:20:27Z", "page_id": "v86r27v76str" }, { @@ -6539,7 +6539,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:09:48Z", +"checked_at": "2026-09-04T10:20:31Z", "page_id": "p556j9m0x9q8" }, { @@ -6551,7 +6551,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:09:49Z", +"checked_at": "2026-09-04T10:20:31Z", "page_id": "x1td1qgq8p61" }, { @@ -6563,7 +6563,7 @@ "description": "UP", "open": 0, "error": null, -"checked_at": "2026-09-04T09:09:49Z", +"checked_at": "2026-09-04T10:20:36Z", "page_id": null }, { @@ -6575,7 +6575,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:09:54Z", +"checked_at": "2026-09-04T10:20:37Z", "page_id": "ms1frkqnsp7r" }, { @@ -6587,7 +6587,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:09:48Z", +"checked_at": "2026-09-04T10:20:32Z", "page_id": "gk10kfgcdj4t" }, { @@ -6599,7 +6599,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:09:48Z", +"checked_at": "2026-09-04T10:20:38Z", "page_id": "2y5b64jd7fwp" }, { @@ -6611,7 +6611,7 @@ "description": "UP", "open": 0, "error": null, -"checked_at": "2026-09-04T09:09:52Z", +"checked_at": "2026-09-04T10:20:30Z", "page_id": null }, { @@ -6623,7 +6623,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:09:55Z", +"checked_at": "2026-09-04T10:20:38Z", "page_id": "nlccmmpcmbph" }, { @@ -6635,7 +6635,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:09:55Z", +"checked_at": "2026-09-04T10:20:38Z", "page_id": "25ychs3859v7" }, { @@ -6647,7 +6647,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:10:00Z", +"checked_at": "2026-09-04T10:20:32Z", "page_id": "ljtzv6sfzgp0" }, { @@ -6659,7 +6659,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:09:57Z", +"checked_at": "2026-09-04T10:20:35Z", "page_id": "01JKAHZTBWPGKQX5WNNPM7NN8K" }, { @@ -6671,7 +6671,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:09:51Z", +"checked_at": "2026-09-04T10:20:38Z", "page_id": "rkmr7c2kjz4j" }, { @@ -6683,7 +6683,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:09:57Z", +"checked_at": "2026-09-04T10:20:38Z", "page_id": "1z3c23q4m5xn" }, { @@ -6695,7 +6695,7 @@ "description": "operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:10:00Z", +"checked_at": "2026-09-04T10:20:38Z", "page_id": null }, { @@ -6707,7 +6707,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:10:02Z", +"checked_at": "2026-09-04T10:20:43Z", "page_id": "0sz2z4sydwtv" }, { @@ -6719,7 +6719,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:09:57Z", +"checked_at": "2026-09-04T10:20:40Z", "page_id": "7ck354kfq4cy" }, { @@ -6731,7 +6731,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:09:55Z", +"checked_at": "2026-09-04T10:20:42Z", "page_id": "j2pr9thwz01t" }, { @@ -6743,7 +6743,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:09:57Z", +"checked_at": "2026-09-04T10:20:40Z", "page_id": "slbnjzdcwm8y" }, { @@ -6755,7 +6755,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:09:57Z", +"checked_at": "2026-09-04T10:20:44Z", "page_id": "h38my4nh3mpf" }, { @@ -6767,7 +6767,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:09:56Z", +"checked_at": "2026-09-04T10:20:39Z", "page_id": "01KK1ENJVFQD495AVPY9DPEHZY" }, { @@ -6779,7 +6779,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:09:55Z", +"checked_at": "2026-09-04T10:20:40Z", "page_id": "p6t5x7tdq8yq" }, { @@ -6791,7 +6791,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:10:01Z", +"checked_at": "2026-09-04T10:20:40Z", "page_id": "2p66nmmycsj3" }, { @@ -6803,7 +6803,7 @@ "description": "UP", "open": 0, "error": null, -"checked_at": "2026-09-04T09:09:58Z", +"checked_at": "2026-09-04T10:20:38Z", "page_id": null }, { @@ -6815,7 +6815,7 @@ "description": "unknown", "open": 0, "error": "http 401", -"checked_at": "2026-09-04T09:10:04Z", +"checked_at": "2026-09-04T10:20:49Z", "page_id": null }, { @@ -6827,7 +6827,7 @@ "description": "unknown", "open": 0, "error": "http 401", -"checked_at": "2026-09-04T09:10:02Z", +"checked_at": "2026-09-04T10:20:54Z", "page_id": null }, { @@ -6839,7 +6839,7 @@ "description": "Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:10:01Z", +"checked_at": "2026-09-04T10:20:42Z", "page_id": "5a0415d76b7070172cfa776d" }, { @@ -6851,7 +6851,7 @@ "description": "Partially Degraded Service", "open": 0, "error": null, -"checked_at": "2026-09-04T09:10:02Z", +"checked_at": "2026-09-04T10:20:45Z", "page_id": "10ycvtr1341m" }, { @@ -6863,7 +6863,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:10:01Z", +"checked_at": "2026-09-04T10:20:43Z", "page_id": "vm2ll45fyh5j" }, { @@ -6875,7 +6875,7 @@ "description": "All Systems Operational", "open": 2, "error": null, -"checked_at": "2026-09-04T09:10:05Z", +"checked_at": "2026-09-04T10:20:45Z", "page_id": "dn6mqn7xvzz3" }, { @@ -6885,9 +6885,9 @@ "status_url": "https://status.quicknode.com", "state": "maintenance", "description": "Service Under Maintenance", -"open": 4, +"open": 3, "error": null, -"checked_at": "2026-09-04T09:10:05Z", +"checked_at": "2026-09-04T10:20:48Z", "page_id": "ncsv5l77jntf" }, { @@ -6899,7 +6899,7 @@ "description": "downtime", "open": 0, "error": null, -"checked_at": "2026-09-04T09:10:04Z", +"checked_at": "2026-09-04T10:20:41Z", "page_id": null }, { @@ -6911,7 +6911,7 @@ "description": "All Systems Operational (scheduled maintenance in progress)", "open": 1, "error": null, -"checked_at": "2026-09-04T09:10:02Z", +"checked_at": "2026-09-04T10:20:48Z", "page_id": "nl3z7dsfgpd6" }, { @@ -6923,7 +6923,7 @@ "description": "UP", "open": 0, "error": null, -"checked_at": "2026-09-04T09:10:04Z", +"checked_at": "2026-09-04T10:20:46Z", "page_id": null }, { @@ -6935,7 +6935,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:10:04Z", +"checked_at": "2026-09-04T10:20:47Z", "page_id": "xj0q6t5s793q" }, { @@ -6947,7 +6947,7 @@ "description": "operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:10:05Z", +"checked_at": "2026-09-04T10:20:48Z", "page_id": null }, { @@ -6959,7 +6959,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:10:08Z", +"checked_at": "2026-09-04T10:20:53Z", "page_id": "nz3r09cr7dk1" }, { @@ -6971,7 +6971,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:10:07Z", +"checked_at": "2026-09-04T10:20:45Z", "page_id": "zx74cbdtks3x" }, { @@ -6983,7 +6983,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:10:15Z", +"checked_at": "2026-09-04T10:20:50Z", "page_id": "p5c6ktq11259" }, { @@ -6995,7 +6995,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:10:14Z", +"checked_at": "2026-09-04T10:21:00Z", "page_id": "mnlrk0049tgf" }, { @@ -7007,7 +7007,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:10:08Z", +"checked_at": "2026-09-04T10:20:54Z", "page_id": "ys79tr06mmnw" }, { @@ -7019,7 +7019,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:10:09Z", +"checked_at": "2026-09-04T10:20:49Z", "page_id": "2kbc0d48tv3j" }, { @@ -7031,7 +7031,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:10:07Z", +"checked_at": "2026-09-04T10:20:54Z", "page_id": "btfx2lvlsjph" }, { @@ -7043,7 +7043,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:10:09Z", +"checked_at": "2026-09-04T10:20:50Z", "page_id": "9wftkk2wtrd0" }, { @@ -7055,7 +7055,7 @@ "description": "unknown", "open": 0, "error": "http 401", -"checked_at": "2026-09-04T09:10:15Z", +"checked_at": "2026-09-04T10:20:58Z", "page_id": null }, { @@ -7067,7 +7067,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:10:09Z", +"checked_at": "2026-09-04T10:20:48Z", "page_id": "tyfhm2rrt1tl" }, { @@ -7079,7 +7079,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:10:15Z", +"checked_at": "2026-09-04T10:20:54Z", "page_id": "01J5NNAC2GC4E1C5QTHH7TDZAV" }, { @@ -7091,7 +7091,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:10:14Z", +"checked_at": "2026-09-04T10:20:56Z", "page_id": "ysxtsrzt2b4s" }, { @@ -7103,7 +7103,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:10:12Z", +"checked_at": "2026-09-04T10:20:54Z", "page_id": "01JAVQMNY0DQSV4WA26TFYAMWG" }, { @@ -7115,7 +7115,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:10:13Z", +"checked_at": "2026-09-04T10:20:53Z", "page_id": "d7wjfp7kgjkd" }, { @@ -7127,7 +7127,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:10:13Z", +"checked_at": "2026-09-04T10:20:52Z", "page_id": "w5mwz1hzx8c6" }, { @@ -7139,7 +7139,7 @@ "description": "unknown", "open": 0, "error": "moved: not an instatus page any more", -"checked_at": "2026-09-04T09:10:24Z", +"checked_at": "2026-09-04T10:21:00Z", "page_id": null }, { @@ -7151,7 +7151,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:10:14Z", +"checked_at": "2026-09-04T10:20:57Z", "page_id": "01K4DA1HRDN4SR8G0AG5V8JY6P" }, { @@ -7163,7 +7163,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:10:13Z", +"checked_at": "2026-09-04T10:20:58Z", "page_id": "znsf1ymbqr02" }, { @@ -7175,7 +7175,7 @@ "description": "Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:10:13Z", +"checked_at": "2026-09-04T10:20:57Z", "page_id": "59db90dbcdeb2f04dadcf16d" }, { @@ -7187,7 +7187,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:10:15Z", +"checked_at": "2026-09-04T10:21:00Z", "page_id": "01J8TKJKMDM5SN3E52E3BQ1FRA" }, { @@ -7199,7 +7199,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:10:13Z", +"checked_at": "2026-09-04T10:21:00Z", "page_id": "3ylqq5vfnpmf" }, { @@ -7211,7 +7211,7 @@ "description": "Service Under Maintenance", "open": 0, "error": null, -"checked_at": "2026-09-04T09:10:15Z", +"checked_at": "2026-09-04T10:20:58Z", "page_id": "pclby00q90vc" }, { @@ -7223,7 +7223,7 @@ "description": "unknown", "open": 0, "error": "moved: not a statuspage any more", -"checked_at": "2026-09-04T09:10:26Z", +"checked_at": "2026-09-04T10:21:19Z", "page_id": null }, { @@ -7235,7 +7235,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:10:17Z", +"checked_at": "2026-09-04T10:21:03Z", "page_id": "pl2gjrymjzd3" }, { @@ -7247,7 +7247,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:10:21Z", +"checked_at": "2026-09-04T10:21:00Z", "page_id": "ms2cphgypmss" }, { @@ -7259,7 +7259,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:10:24Z", +"checked_at": "2026-09-04T10:21:07Z", "page_id": "qzkkn6cg4njg" }, { @@ -7271,7 +7271,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:10:22Z", +"checked_at": "2026-09-04T10:21:10Z", "page_id": "b4rd0jtyw03s" }, { @@ -7283,7 +7283,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:10:19Z", +"checked_at": "2026-09-04T10:21:01Z", "page_id": "vbn3b28qz1xc" }, { @@ -7295,7 +7295,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:10:17Z", +"checked_at": "2026-09-04T10:21:07Z", "page_id": "4j96cqfplmfq" }, { @@ -7307,7 +7307,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:10:21Z", +"checked_at": "2026-09-04T10:21:04Z", "page_id": "m4yw2hq52zc9" }, { @@ -7319,7 +7319,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:10:18Z", +"checked_at": "2026-09-04T10:21:05Z", "page_id": "71y1d11qjrsv" }, { @@ -7331,7 +7331,7 @@ "description": "UP", "open": 0, "error": null, -"checked_at": "2026-09-04T09:10:24Z", +"checked_at": "2026-09-04T10:21:06Z", "page_id": null }, { @@ -7343,7 +7343,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:10:27Z", +"checked_at": "2026-09-04T10:21:02Z", "page_id": "bzxtxjq8gjrp" }, { @@ -7355,7 +7355,7 @@ "description": "Partially Degraded Service", "open": 6, "error": null, -"checked_at": "2026-09-04T09:10:22Z", +"checked_at": "2026-09-04T10:21:04Z", "page_id": "s2kbtscly3pj" }, { @@ -7367,7 +7367,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:10:27Z", +"checked_at": "2026-09-04T10:21:12Z", "page_id": "nhjhhjmnpgdh" }, { @@ -7379,7 +7379,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:10:25Z", +"checked_at": "2026-09-04T10:21:08Z", "page_id": "3vdwxk1m42gg" }, { @@ -7391,7 +7391,7 @@ "description": "Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:10:22Z", +"checked_at": "2026-09-04T10:21:06Z", "page_id": "5938a0dbef3e6af26b001921" }, { @@ -7403,7 +7403,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:10:25Z", +"checked_at": "2026-09-04T10:21:11Z", "page_id": "p4p34cxtdxqy" }, { @@ -7415,7 +7415,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:10:29Z", +"checked_at": "2026-09-04T10:21:13Z", "page_id": "zblfzbm0zxs4" }, { @@ -7427,7 +7427,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:10:27Z", +"checked_at": "2026-09-04T10:21:09Z", "page_id": "v05h31t8qhkq" }, { @@ -7439,7 +7439,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:10:23Z", +"checked_at": "2026-09-04T10:21:09Z", "page_id": "f9zwqyg9kgyd" }, { @@ -7451,7 +7451,7 @@ "description": "unknown", "open": 0, "error": "http 401", -"checked_at": "2026-09-04T09:10:26Z", +"checked_at": "2026-09-04T10:21:13Z", "page_id": null }, { @@ -7463,7 +7463,7 @@ "description": "Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:10:28Z", +"checked_at": "2026-09-04T10:21:09Z", "page_id": "5721276eb12b2e5843002acb" }, { @@ -7475,7 +7475,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:10:34Z", +"checked_at": "2026-09-04T10:21:14Z", "page_id": "qp2pg8dlrq7m" }, { @@ -7487,7 +7487,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:10:29Z", +"checked_at": "2026-09-04T10:21:11Z", "page_id": "yzw83vcxbysq" }, { @@ -7499,7 +7499,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:10:38Z", +"checked_at": "2026-09-04T10:21:15Z", "page_id": "zq6qk8cct5d8" }, { @@ -7511,7 +7511,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:10:31Z", +"checked_at": "2026-09-04T10:21:14Z", "page_id": "snjdw73vnmhs" }, { @@ -7523,7 +7523,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:10:38Z", +"checked_at": "2026-09-04T10:21:15Z", "page_id": "t687h3m0nh65" }, { @@ -7535,7 +7535,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:10:32Z", +"checked_at": "2026-09-04T10:21:13Z", "page_id": "kttzs2ddgsvp" }, { @@ -7547,7 +7547,7 @@ "description": "operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:10:29Z", +"checked_at": "2026-09-04T10:21:14Z", "page_id": null }, { @@ -7559,7 +7559,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:10:30Z", +"checked_at": "2026-09-04T10:21:18Z", "page_id": "3c9m0jbxly6r" }, { @@ -7571,7 +7571,7 @@ "description": "unknown", "open": 0, "error": "http 401", -"checked_at": "2026-09-04T09:10:40Z", +"checked_at": "2026-09-04T10:21:16Z", "page_id": null }, { @@ -7583,7 +7583,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:10:33Z", +"checked_at": "2026-09-04T10:21:22Z", "page_id": "q2yfb2vglvjl" }, { @@ -7595,7 +7595,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:10:37Z", +"checked_at": "2026-09-04T10:21:18Z", "page_id": "bk952mqg5b82" }, { @@ -7607,7 +7607,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:10:37Z", +"checked_at": "2026-09-04T10:21:19Z", "page_id": "cvhtv7zfhl9z" }, { @@ -7619,7 +7619,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:10:38Z", +"checked_at": "2026-09-04T10:21:24Z", "page_id": "kwkkj5bkypmq" }, { @@ -7631,7 +7631,7 @@ "description": "operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:10:40Z", +"checked_at": "2026-09-04T10:21:18Z", "page_id": null }, { @@ -7643,7 +7643,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:10:32Z", +"checked_at": "2026-09-04T10:21:19Z", "page_id": "6bh1wlk2f65z" }, { @@ -7655,7 +7655,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:10:42Z", +"checked_at": "2026-09-04T10:21:20Z", "page_id": "hhz2ym1wkfqg" }, { @@ -7667,7 +7667,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:10:40Z", +"checked_at": "2026-09-04T10:21:18Z", "page_id": "nn1z6zyf1cnr" }, { @@ -7679,7 +7679,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:10:34Z", +"checked_at": "2026-09-04T10:21:24Z", "page_id": "x4bhgfp1j1x0" }, { @@ -7691,7 +7691,7 @@ "description": "UP", "open": 0, "error": null, -"checked_at": "2026-09-04T09:10:43Z", +"checked_at": "2026-09-04T10:21:32Z", "page_id": null }, { @@ -7703,7 +7703,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:10:46Z", +"checked_at": "2026-09-04T10:21:19Z", "page_id": "01KBQ23MVFBZW41YJT9SSKGR8X" }, { @@ -7715,7 +7715,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:10:37Z", +"checked_at": "2026-09-04T10:21:19Z", "page_id": "d33g96wd23dd" }, { @@ -7727,7 +7727,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:10:37Z", +"checked_at": "2026-09-04T10:21:22Z", "page_id": "27fcn0qntr9w" }, { @@ -7739,7 +7739,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:10:40Z", +"checked_at": "2026-09-04T10:21:23Z", "page_id": "bc6dd7ft0q75" }, { @@ -7751,7 +7751,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:10:53Z", +"checked_at": "2026-09-04T10:21:26Z", "page_id": "g69jsz2l8w55" }, { @@ -7763,7 +7763,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:10:48Z", +"checked_at": "2026-09-04T10:21:32Z", "page_id": "r5v32zmvzdct" }, { @@ -7775,7 +7775,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:10:42Z", +"checked_at": "2026-09-04T10:21:32Z", "page_id": "k3mchng1gxzn" }, { @@ -7787,7 +7787,7 @@ "description": "Service Under Maintenance", "open": 0, "error": null, -"checked_at": "2026-09-04T09:10:44Z", +"checked_at": "2026-09-04T10:21:22Z", "page_id": "bjnhpkmbdnjl" }, { @@ -7799,7 +7799,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:10:49Z", +"checked_at": "2026-09-04T10:21:26Z", "page_id": "rcjwx6zdsyvk" }, { @@ -7811,7 +7811,7 @@ "description": "Service Under Maintenance", "open": 2, "error": null, -"checked_at": "2026-09-04T09:10:47Z", +"checked_at": "2026-09-04T10:21:27Z", "page_id": "zmjhsbqtpgpb" }, { @@ -7823,7 +7823,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:10:46Z", +"checked_at": "2026-09-04T10:21:27Z", "page_id": "0bkycgrmxs9j" }, { @@ -7835,7 +7835,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:10:42Z", +"checked_at": "2026-09-04T10:21:31Z", "page_id": "01K0RCAA622FEHCSZVG2F3Q84Q" }, { @@ -7847,7 +7847,7 @@ "description": "HASISSUES", "open": 0, "error": null, -"checked_at": "2026-09-04T09:10:43Z", +"checked_at": "2026-09-04T10:21:32Z", "page_id": null }, { @@ -7859,7 +7859,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:10:45Z", +"checked_at": "2026-09-04T10:21:27Z", "page_id": "gg90hvtxx5ns" }, { @@ -7871,7 +7871,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:10:47Z", +"checked_at": "2026-09-04T10:21:26Z", "page_id": "4qt1j489p9cl" }, { @@ -7883,7 +7883,7 @@ "description": "UP", "open": 0, "error": null, -"checked_at": "2026-09-04T09:10:54Z", +"checked_at": "2026-09-04T10:21:32Z", "page_id": null }, { @@ -7895,7 +7895,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:10:53Z", +"checked_at": "2026-09-04T10:21:34Z", "page_id": "tvv76p250rdk" }, { @@ -7907,7 +7907,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:10:47Z", +"checked_at": "2026-09-04T10:21:32Z", "page_id": "q1z5r94tnt56" }, { @@ -7919,7 +7919,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:10:49Z", +"checked_at": "2026-09-04T10:21:28Z", "page_id": "724cl4r0f6zw" }, { @@ -7931,7 +7931,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:10:47Z", +"checked_at": "2026-09-04T10:21:26Z", "page_id": "0nd2xw7tms6z" }, { @@ -7943,7 +7943,7 @@ "description": "All Systems Operational (scheduled maintenance in progress)", "open": 2, "error": null, -"checked_at": "2026-09-04T09:10:47Z", +"checked_at": "2026-09-04T10:21:28Z", "page_id": "6jrkb3x939j9" }, { @@ -7955,7 +7955,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:10:50Z", +"checked_at": "2026-09-04T10:21:35Z", "page_id": "bd8gwyshdvsr" }, { @@ -7963,11 +7963,11 @@ "vendor": "Snowflake", "platform": "statuspage", "status_url": "https://status.snowflake.com", -"state": "partial", -"description": "Partial System Outage", -"open": 2, +"state": "degraded", +"description": "Partially Degraded Service", +"open": 1, "error": null, -"checked_at": "2026-09-04T09:10:52Z", +"checked_at": "2026-09-04T10:21:37Z", "page_id": "94s7z8vpy1n8" }, { @@ -7979,7 +7979,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:10:50Z", +"checked_at": "2026-09-04T10:21:35Z", "page_id": "myj6w6kw42c6" }, { @@ -7991,7 +7991,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:10:55Z", +"checked_at": "2026-09-04T10:21:32Z", "page_id": "rm9mn997x8jd" }, { @@ -8003,7 +8003,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:10:57Z", +"checked_at": "2026-09-04T10:21:32Z", "page_id": "701xnxqmhdh3" }, { @@ -8015,7 +8015,7 @@ "description": "unknown", "open": 0, "error": "http 401", -"checked_at": "2026-09-04T09:10:57Z", +"checked_at": "2026-09-04T10:21:33Z", "page_id": null }, { @@ -8027,7 +8027,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:10:49Z", +"checked_at": "2026-09-04T10:21:37Z", "page_id": "r5ljfdhtqdl1" }, { @@ -8039,7 +8039,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:10:53Z", +"checked_at": "2026-09-04T10:21:35Z", "page_id": "8g4j8wt7c8ll" }, { @@ -8051,7 +8051,7 @@ "description": "Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:10:52Z", +"checked_at": "2026-09-04T10:21:42Z", "page_id": "5d7fa0eb31daae1ff9d77abb" }, { @@ -8063,7 +8063,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:10:53Z", +"checked_at": "2026-09-04T10:21:37Z", "page_id": "wcq76r0ckz90" }, { @@ -8075,7 +8075,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:10:58Z", +"checked_at": "2026-09-04T10:21:41Z", "page_id": "146dh2d2pp25" }, { @@ -8087,7 +8087,7 @@ "description": "unknown", "open": 0, "error": "moved: not a statuspage any more", -"checked_at": "2026-09-04T09:11:07Z", +"checked_at": "2026-09-04T10:21:48Z", "page_id": null }, { @@ -8099,7 +8099,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:10:58Z", +"checked_at": "2026-09-04T10:21:37Z", "page_id": "s6cdj41y026n" }, { @@ -8111,7 +8111,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:11:03Z", +"checked_at": "2026-09-04T10:21:42Z", "page_id": "1jkhm1drpysj" }, { @@ -8123,7 +8123,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:10:58Z", +"checked_at": "2026-09-04T10:21:38Z", "page_id": "7yqwq9b392xq" }, { @@ -8135,7 +8135,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:10:55Z", +"checked_at": "2026-09-04T10:21:37Z", "page_id": "2yh9w74268jx" }, { @@ -8147,7 +8147,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:10:57Z", +"checked_at": "2026-09-04T10:21:37Z", "page_id": "vkh74xvly3rk" }, { @@ -8159,7 +8159,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:10:57Z", +"checked_at": "2026-09-04T10:21:42Z", "page_id": "kmmfkblgkhnf" }, { @@ -8171,7 +8171,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:11:02Z", +"checked_at": "2026-09-04T10:21:51Z", "page_id": "zmdk03p7815p" }, { @@ -8183,7 +8183,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:11:03Z", +"checked_at": "2026-09-04T10:21:48Z", "page_id": "hxx56s96zrww" }, { @@ -8195,7 +8195,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:10:59Z", +"checked_at": "2026-09-04T10:21:41Z", "page_id": "cntbxkqh7bl5" }, { @@ -8207,7 +8207,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:10:58Z", +"checked_at": "2026-09-04T10:21:45Z", "page_id": "c8rwn5q0twhh" }, { @@ -8215,11 +8215,11 @@ "vendor": "Sumo Logic US1", "platform": "statuspage", "status_url": "http://status.us1.sumologic.com", -"state": "degraded", -"description": "Partially Degraded Service", -"open": 1, +"state": "ok", +"description": "All Systems Operational", +"open": 0, "error": null, -"checked_at": "2026-09-04T09:11:03Z", +"checked_at": "2026-09-04T10:21:44Z", "page_id": "mch6db66pqjz" }, { @@ -8231,7 +8231,7 @@ "description": "Partially Degraded Service", "open": 2, "error": null, -"checked_at": "2026-09-04T09:11:00Z", +"checked_at": "2026-09-04T10:21:40Z", "page_id": "q7pxfmcf2sbx" }, { @@ -8243,7 +8243,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:11:03Z", +"checked_at": "2026-09-04T10:21:48Z", "page_id": "6kcn25x6k6f2" }, { @@ -8255,7 +8255,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:11:07Z", +"checked_at": "2026-09-04T10:21:54Z", "page_id": "ywtxb3dfdzbf" }, { @@ -8267,7 +8267,7 @@ "description": "Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:11:02Z", +"checked_at": "2026-09-04T10:21:42Z", "page_id": "5578eca31ae0f1de7300016c" }, { @@ -8279,7 +8279,7 @@ "description": "UP", "open": 0, "error": null, -"checked_at": "2026-09-04T09:11:07Z", +"checked_at": "2026-09-04T10:21:43Z", "page_id": null }, { @@ -8291,7 +8291,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:11:04Z", +"checked_at": "2026-09-04T10:21:44Z", "page_id": "01JVZBX1ZXHYQ4Z6ATG7AQDZ6N" }, { @@ -8303,7 +8303,7 @@ "description": "operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:11:07Z", +"checked_at": "2026-09-04T10:21:53Z", "page_id": null }, { @@ -8315,7 +8315,7 @@ "description": "operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:11:07Z", +"checked_at": "2026-09-04T10:21:49Z", "page_id": null }, { @@ -8327,7 +8327,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:11:07Z", +"checked_at": "2026-09-04T10:21:51Z", "page_id": "gkqh4gtqdkdp" }, { @@ -8339,7 +8339,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:11:06Z", +"checked_at": "2026-09-04T10:21:45Z", "page_id": "gfggtctd0kh2" }, { @@ -8351,7 +8351,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:11:05Z", +"checked_at": "2026-09-04T10:21:50Z", "page_id": "gbvg14byz4n5" }, { @@ -8363,7 +8363,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:11:06Z", +"checked_at": "2026-09-04T10:21:50Z", "page_id": "j16wc0h3wc86" }, { @@ -8375,7 +8375,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:11:13Z", +"checked_at": "2026-09-04T10:21:48Z", "page_id": "dnmfkqzkp304" }, { @@ -8387,7 +8387,7 @@ "description": "unknown", "open": 0, "error": "moved: not a statuspage any more", -"checked_at": "2026-09-04T09:11:13Z", +"checked_at": "2026-09-04T10:21:53Z", "page_id": null }, { @@ -8399,7 +8399,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:11:15Z", +"checked_at": "2026-09-04T10:21:54Z", "page_id": "fqhtj8gm9dms" }, { @@ -8411,7 +8411,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:11:13Z", +"checked_at": "2026-09-04T10:21:52Z", "page_id": "h9tsgmpnkvjr" }, { @@ -8423,7 +8423,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:11:12Z", +"checked_at": "2026-09-04T10:21:58Z", "page_id": "sb2jckjrwjgz" }, { @@ -8435,7 +8435,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:11:10Z", +"checked_at": "2026-09-04T10:21:57Z", "page_id": "9cqcx6hfbm7k" }, { @@ -8447,7 +8447,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:11:16Z", +"checked_at": "2026-09-04T10:21:51Z", "page_id": "c6m20my09x6s" }, { @@ -8459,7 +8459,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:11:12Z", +"checked_at": "2026-09-04T10:21:52Z", "page_id": "91qwwq7gpdx1" }, { @@ -8471,7 +8471,7 @@ "description": "Major System Outage", "open": 2, "error": null, -"checked_at": "2026-09-04T09:11:15Z", +"checked_at": "2026-09-04T10:21:54Z", "page_id": "01JXK67PDFD1744143Q9FGJNGQ" }, { @@ -8483,7 +8483,7 @@ "description": "All Systems Operational", "open": 2, "error": null, -"checked_at": "2026-09-04T09:11:09Z", +"checked_at": "2026-09-04T10:21:52Z", "page_id": "4b43brz4r98l" }, { @@ -8495,7 +8495,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:11:09Z", +"checked_at": "2026-09-04T10:21:58Z", "page_id": "0q1s27l4j67l" }, { @@ -8507,7 +8507,7 @@ "description": "All Systems Operational", "open": 1, "error": null, -"checked_at": "2026-09-04T09:11:11Z", +"checked_at": "2026-09-04T10:21:58Z", "page_id": "3d0cmsmv11qh" }, { @@ -8519,7 +8519,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:11:11Z", +"checked_at": "2026-09-04T10:21:55Z", "page_id": "nhclfvpgxsjh" }, { @@ -8531,7 +8531,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:11:15Z", +"checked_at": "2026-09-04T10:21:55Z", "page_id": "gjgh0hrr6n4h" }, { @@ -8543,7 +8543,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:11:19Z", +"checked_at": "2026-09-04T10:21:54Z", "page_id": "2qth4lwzwl5n" }, { @@ -8555,7 +8555,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:11:11Z", +"checked_at": "2026-09-04T10:21:58Z", "page_id": "5bc1y3k2xcvj" }, { @@ -8567,7 +8567,7 @@ "description": "UP", "open": 0, "error": null, -"checked_at": "2026-09-04T09:11:14Z", +"checked_at": "2026-09-04T10:22:02Z", "page_id": null }, { @@ -8579,7 +8579,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:11:13Z", +"checked_at": "2026-09-04T10:21:58Z", "page_id": "xgskwtpk015z" }, { @@ -8591,7 +8591,7 @@ "description": "unknown", "open": 0, "error": "moved: not a statuspage any more", -"checked_at": "2026-09-04T09:11:18Z", +"checked_at": "2026-09-04T10:22:04Z", "page_id": null }, { @@ -8603,7 +8603,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:11:18Z", +"checked_at": "2026-09-04T10:22:00Z", "page_id": "1tp740n418tg" }, { @@ -8615,7 +8615,7 @@ "description": "Partially Degraded Service", "open": 1, "error": null, -"checked_at": "2026-09-04T09:11:21Z", +"checked_at": "2026-09-04T10:22:05Z", "page_id": "msxnbwlx1dh2" }, { @@ -8627,7 +8627,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:11:17Z", +"checked_at": "2026-09-04T10:22:03Z", "page_id": "b68xvwm7hg2w" }, { @@ -8639,7 +8639,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:11:17Z", +"checked_at": "2026-09-04T10:22:04Z", "page_id": "pl042683455j" }, { @@ -8651,7 +8651,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:11:19Z", +"checked_at": "2026-09-04T10:22:06Z", "page_id": "pnpcptp8xh9k" }, { @@ -8663,7 +8663,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:11:25Z", +"checked_at": "2026-09-04T10:22:04Z", "page_id": "ttkjg93cdj8n" }, { @@ -8675,7 +8675,7 @@ "description": "unknown", "open": 0, "error": "http 404", -"checked_at": "2026-09-04T09:11:18Z", +"checked_at": "2026-09-04T10:22:01Z", "page_id": null }, { @@ -8687,7 +8687,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:11:21Z", +"checked_at": "2026-09-04T10:22:02Z", "page_id": "tv65h2hvqdsf" }, { @@ -8699,7 +8699,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:11:29Z", +"checked_at": "2026-09-04T10:22:11Z", "page_id": "n2dxgx19r8gw" }, { @@ -8711,7 +8711,7 @@ "description": "operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:11:20Z", +"checked_at": "2026-09-04T10:22:08Z", "page_id": null }, { @@ -8723,7 +8723,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:11:31Z", +"checked_at": "2026-09-04T10:22:08Z", "page_id": "kfy1tgdmcqyy" }, { @@ -8733,9 +8733,9 @@ "status_url": "https://status.twilio.com", "state": "degraded", "description": "Partially Degraded Service", -"open": 9, +"open": 11, "error": null, -"checked_at": "2026-09-04T09:11:20Z", +"checked_at": "2026-09-04T10:22:04Z", "page_id": "gpkpyklzq55q" }, { @@ -8747,7 +8747,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:11:27Z", +"checked_at": "2026-09-04T10:22:06Z", "page_id": "d3m2m1y4ghc6" }, { @@ -8759,7 +8759,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:11:24Z", +"checked_at": "2026-09-04T10:22:06Z", "page_id": "yfj40zdsk34s" }, { @@ -8771,7 +8771,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:11:24Z", +"checked_at": "2026-09-04T10:22:04Z", "page_id": "wygv0lcrzvq7" }, { @@ -8783,7 +8783,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:11:21Z", +"checked_at": "2026-09-04T10:22:05Z", "page_id": "n814lw2zwmpq" }, { @@ -8795,7 +8795,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:11:23Z", +"checked_at": "2026-09-04T10:22:08Z", "page_id": "r9sjd13s1zsp" }, { @@ -8807,7 +8807,7 @@ "description": "Partially Degraded Service", "open": 1, "error": null, -"checked_at": "2026-09-04T09:11:22Z", +"checked_at": "2026-09-04T10:22:04Z", "page_id": "z74djf7jvp8m" }, { @@ -8819,7 +8819,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:11:25Z", +"checked_at": "2026-09-04T10:22:07Z", "page_id": "l6t26zgc3vff" }, { @@ -8831,7 +8831,7 @@ "description": "unknown", "open": 0, "error": "moved: not a statuspage any more", -"checked_at": "2026-09-04T09:11:32Z", +"checked_at": "2026-09-04T10:22:10Z", "page_id": null }, { @@ -8843,7 +8843,7 @@ "description": "downtime", "open": 0, "error": null, -"checked_at": "2026-09-04T09:11:27Z", +"checked_at": "2026-09-04T10:22:12Z", "page_id": null }, { @@ -8855,7 +8855,7 @@ "description": "Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:11:28Z", +"checked_at": "2026-09-04T10:22:10Z", "page_id": "5f80d63ea1c48e04c1dfa100" }, { @@ -8867,7 +8867,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:11:29Z", +"checked_at": "2026-09-04T10:22:07Z", "page_id": "01K4S8A0KYPG1M6X02T372EZGT" }, { @@ -8879,7 +8879,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:11:33Z", +"checked_at": "2026-09-04T10:22:20Z", "page_id": "01KFYYTMWBB1VXMT7CBFWF4TD5" }, { @@ -8891,7 +8891,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:11:32Z", +"checked_at": "2026-09-04T10:22:11Z", "page_id": "46f7chxnjxpc" }, { @@ -8903,7 +8903,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:11:28Z", +"checked_at": "2026-09-04T10:22:15Z", "page_id": "k11q7x12bmjp" }, { @@ -8915,7 +8915,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:11:25Z", +"checked_at": "2026-09-04T10:22:12Z", "page_id": "cnkhkzccj9xw" }, { @@ -8927,7 +8927,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:11:31Z", +"checked_at": "2026-09-04T10:22:11Z", "page_id": "ltnt1pzqrlmg" }, { @@ -8939,7 +8939,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:11:28Z", +"checked_at": "2026-09-04T10:22:12Z", "page_id": "0mggy4p2v1q4" }, { @@ -8951,7 +8951,7 @@ "description": "Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:11:27Z", +"checked_at": "2026-09-04T10:22:23Z", "page_id": "584315a9bb1263500e0004b6" }, { @@ -8963,7 +8963,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:11:31Z", +"checked_at": "2026-09-04T10:22:16Z", "page_id": "skvm6gb2qw9r" }, { @@ -8975,7 +8975,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:11:26Z", +"checked_at": "2026-09-04T10:22:19Z", "page_id": "lvglq8h0mdyh" }, { @@ -8987,7 +8987,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:11:30Z", +"checked_at": "2026-09-04T10:22:15Z", "page_id": "kglfygl2qppj" }, { @@ -8999,7 +8999,7 @@ "description": "Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:11:35Z", +"checked_at": "2026-09-04T10:22:18Z", "page_id": "5ea188b3144baf049b282591" }, { @@ -9011,7 +9011,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:11:30Z", +"checked_at": "2026-09-04T10:22:20Z", "page_id": "hfm91t9hr5n0" }, { @@ -9023,7 +9023,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:11:42Z", +"checked_at": "2026-09-04T10:22:13Z", "page_id": "zvpknzcr6znl" }, { @@ -9035,7 +9035,7 @@ "description": "Partially Degraded Service", "open": 0, "error": null, -"checked_at": "2026-09-04T09:11:32Z", +"checked_at": "2026-09-04T10:22:19Z", "page_id": "nszc4mr3scyh" }, { @@ -9047,7 +9047,7 @@ "description": "UP", "open": 0, "error": null, -"checked_at": "2026-09-04T09:11:40Z", +"checked_at": "2026-09-04T10:22:19Z", "page_id": null }, { @@ -9055,11 +9055,11 @@ "vendor": "Vonage", "platform": "statuspage", "status_url": "https://vcc.statuspage.io", -"state": "degraded", -"description": "Minor Service Outage", +"state": "partial", +"description": "Partial System Outage", "open": 1, "error": null, -"checked_at": "2026-09-04T09:11:33Z", +"checked_at": "2026-09-04T10:22:15Z", "page_id": "0gccyfw1x442" }, { @@ -9071,7 +9071,7 @@ "description": "Partially Degraded Service", "open": 3, "error": null, -"checked_at": "2026-09-04T09:11:31Z", +"checked_at": "2026-09-04T10:22:19Z", "page_id": "k4cdqxp909c5" }, { @@ -9083,7 +9083,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:11:34Z", +"checked_at": "2026-09-04T10:22:17Z", "page_id": "5d6hknlz0ql6" }, { @@ -9095,7 +9095,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:11:36Z", +"checked_at": "2026-09-04T10:22:19Z", "page_id": "9bk8nskmh6k6" }, { @@ -9107,7 +9107,7 @@ "description": "unknown", "open": 0, "error": "http 404", -"checked_at": "2026-09-04T09:11:39Z", +"checked_at": "2026-09-04T10:22:21Z", "page_id": null }, { @@ -9119,7 +9119,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:11:36Z", +"checked_at": "2026-09-04T10:22:19Z", "page_id": "kkc10kz2t8yc" }, { @@ -9131,7 +9131,7 @@ "description": "All Systems Operational", "open": 1, "error": null, -"checked_at": "2026-09-04T09:11:39Z", +"checked_at": "2026-09-04T10:22:23Z", "page_id": "79dl9by36yp7" }, { @@ -9143,7 +9143,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:11:38Z", +"checked_at": "2026-09-04T10:22:19Z", "page_id": "1000hc1f0mzf" }, { @@ -9155,7 +9155,7 @@ "description": "All Systems Operational (scheduled maintenance in progress)", "open": 1, "error": null, -"checked_at": "2026-09-04T09:11:44Z", +"checked_at": "2026-09-04T10:22:21Z", "page_id": "2r1tdgqr8ld5" }, { @@ -9167,7 +9167,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:11:36Z", +"checked_at": "2026-09-04T10:22:19Z", "page_id": "9wcfjgptk1hk" }, { @@ -9179,7 +9179,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:11:39Z", +"checked_at": "2026-09-04T10:22:29Z", "page_id": "89nybrkfkjng" }, { @@ -9191,7 +9191,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:11:39Z", +"checked_at": "2026-09-04T10:22:25Z", "page_id": "vzmhf3sfgcfm" }, { @@ -9203,7 +9203,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:11:42Z", +"checked_at": "2026-09-04T10:22:25Z", "page_id": "7bp2kqlfyczm" }, { @@ -9215,7 +9215,7 @@ "description": "Partial System Outage", "open": 2, "error": null, -"checked_at": "2026-09-04T09:11:44Z", +"checked_at": "2026-09-04T10:22:32Z", "page_id": "tmd1c09qtjnm" }, { @@ -9227,7 +9227,7 @@ "description": "operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:11:41Z", +"checked_at": "2026-09-04T10:22:27Z", "page_id": null }, { @@ -9239,7 +9239,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:11:42Z", +"checked_at": "2026-09-04T10:22:24Z", "page_id": "01J1SWF0WRNVQ6SYYMPNMQ979H" }, { @@ -9251,7 +9251,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:11:47Z", +"checked_at": "2026-09-04T10:22:23Z", "page_id": "sc26zwwp3c0r" }, { @@ -9263,7 +9263,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:11:48Z", +"checked_at": "2026-09-04T10:22:29Z", "page_id": "f4yx8n41p9cy" }, { @@ -9275,7 +9275,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:11:41Z", +"checked_at": "2026-09-04T10:22:29Z", "page_id": "nnqjzz7cd4tj" }, { @@ -9287,7 +9287,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:11:43Z", +"checked_at": "2026-09-04T10:22:23Z", "page_id": "3x6vjqhj2cpt" }, { @@ -9299,7 +9299,7 @@ "description": "All Systems Operational", "open": 1, "error": null, -"checked_at": "2026-09-04T09:11:46Z", +"checked_at": "2026-09-04T10:22:29Z", "page_id": "bgx79l11xfsj" }, { @@ -9311,7 +9311,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:11:45Z", +"checked_at": "2026-09-04T10:22:25Z", "page_id": "b0rfh915l1lt" }, { @@ -9323,7 +9323,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:11:47Z", +"checked_at": "2026-09-04T10:22:27Z", "page_id": "gp962tfydk6b" }, { @@ -9335,7 +9335,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:11:47Z", +"checked_at": "2026-09-04T10:22:25Z", "page_id": "m8f43n57h83g" }, { @@ -9347,7 +9347,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:11:44Z", +"checked_at": "2026-09-04T10:22:33Z", "page_id": "pxr8fgvd83rm" }, { @@ -9359,7 +9359,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:11:49Z", +"checked_at": "2026-09-04T10:22:25Z", "page_id": "bfxktrnf6xhf" }, { @@ -9371,7 +9371,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:11:42Z", +"checked_at": "2026-09-04T10:22:29Z", "page_id": "3dqfq14ym6xk" }, { @@ -9383,7 +9383,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:11:44Z", +"checked_at": "2026-09-04T10:22:33Z", "page_id": "q0p9gnywng1z" }, { @@ -9395,7 +9395,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:11:47Z", +"checked_at": "2026-09-04T10:22:33Z", "page_id": "d6z5dbqz49lx" }, { @@ -9407,7 +9407,7 @@ "description": "Partially Degraded Service", "open": 1, "error": null, -"checked_at": "2026-09-04T09:11:45Z", +"checked_at": "2026-09-04T10:22:33Z", "page_id": "03psvxc9s68x" }, { @@ -9419,7 +9419,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:11:50Z", +"checked_at": "2026-09-04T10:22:33Z", "page_id": "y3ht7twyx5rc" }, { @@ -9431,7 +9431,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:11:50Z", +"checked_at": "2026-09-04T10:22:34Z", "page_id": "v5t4bqb3nwgs" }, { @@ -9443,7 +9443,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:11:50Z", +"checked_at": "2026-09-04T10:22:34Z", "page_id": "5lv4k6t686g5" }, { @@ -9455,7 +9455,7 @@ "description": "unknown", "open": 0, "error": null, -"checked_at": "2026-09-04T09:11:52Z", +"checked_at": "2026-09-04T10:22:33Z", "page_id": "cec99eca0d27350651aff686" }, { @@ -9467,7 +9467,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:11:47Z", +"checked_at": "2026-09-04T10:22:37Z", "page_id": "m25gn8nx0j3k" }, { @@ -9479,7 +9479,7 @@ "description": "All Systems Operational (scheduled maintenance in progress)", "open": 2, "error": null, -"checked_at": "2026-09-04T09:11:54Z", +"checked_at": "2026-09-04T10:22:37Z", "page_id": "14qjgk812kgk" }, { @@ -9491,7 +9491,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:11:52Z", +"checked_at": "2026-09-04T10:22:35Z", "page_id": "j4k5f923y480" }, { @@ -9503,7 +9503,7 @@ "description": "All Systems Operational", "open": 0, "error": null, -"checked_at": "2026-09-04T09:11:52Z", +"checked_at": "2026-09-04T10:22:37Z", "page_id": "crwrkd1tmy0k" } ] diff --git a/api/v/1password.json b/api/v/1password.json index f2eb6be4179e3bb97da053b0cd3f7a2088c9290b..8102702e717807ba44af9046e2f58c797a57cbaa 100644 --- a/api/v/1password.json +++ b/api/v/1password.json @@ -3,7 +3,7 @@ "slug": "1password", "platform": "statuspage", "status_url": "https://1password.statuspage.io", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "A fix has been deployed and this issue is now resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-22T15:20:54.949-04:00", "resolved_inferred": false, "started_at": "2026-07-22T13:55:18.026-04:00", @@ -25,7 +25,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-17T14:57:38.340-04:00", "resolved_inferred": false, "started_at": "2026-07-17T14:52:15.282-04:00", @@ -38,7 +38,7 @@ "body": "A fix has been deployed and this issue is now resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-13T15:57:14.635-04:00", "resolved_inferred": false, "started_at": "2026-07-13T14:59:33.940-04:00", @@ -51,7 +51,7 @@ "body": "A fix for this issue has been implemented, and our teams are monitoring. During the outage, GitHub Actions might have failed to pull the latest CLI version, causing the pipeline to fail.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-13T10:30:00.000-04:00", "resolved_inferred": false, "started_at": "2026-07-13T10:30:00.000-04:00", @@ -64,7 +64,7 @@ "body": "# Incident Postmortem - Device Trust Authentication Outage\n\n**Date of Incident:** 2026-07-02 \n**Time of Incident \\(UTC\\):** 19:28 - 20:28 \n**Service\\(s\\) Affected:** This incident affected: USA/Global \\(Device Trust Authentication Service, Device Trust Checks Server, Device Trust Portal, Device Trust API\\) and Europe \\(Device Trust Authentication Service, Device Trust Checks Server, Device Trust Portal, Device Trust API\\). \n**Impact Duration:** 1 Hour\n\n## Summary\n\nOn July 2, 2026, 1Password Device Trust experienced an outage lasting approximately one hour, beginning at 19:28 UTC. During this window, all Device Trust services were unavailable and users were unable to authenticate. We have identified the root cause: an internal configuration change to our cloud load balancing infrastructure was applied more broadly than intended which temporarily made a required endpoint unreachable. This was not a security incident and did not involve any third party. The configuration has been corrected, service has been fully restored, and we have implemented additional safeguards to help prevent this type of issue from recurring.\n\n## Impact on Customers\n\n* **All Device Trust services were completely unavailable during the 60-minute outage window. Users were unable to authenticate to any Device Trust service, including the authentication portal \\(**[**auth.kolide.com**](http://auth.kolide.com)**\\), admin console \\(**[**app.kolide.com**](http://app.kolide.com)**\\), API endpoints, and device server.**\n* **Number of Affected Customers \\(approximate\\):** 100% of Device Trust customers\n* **Geographic Regions Affected \\(if applicable\\):** US and EU\n\n## What Happened?\n\nOn July 2, 2026, A configuration change intended to improve the security configuration of an internal service was applied more broadly than intended, affecting a shared network routing component relied on by Device Trust. The change replaced the underlying network infrastructure supporting Device Trust. However, the traffic routing configuration continued to reference the previous infrastructure instead of the newly provisioned resources. As a result, Device Trust authentication endpoints became unreachable. Reverting the change restored connectivity and service.\n\n* **Timeline of Events \\(UTC\\):**\n\n * 19:28: Network configuration change applied; Network Load Balancers responsible for routing traffic for Device Trust services became unreachable\n * 19:30: Automated monitoring detects the outage and triggers alerts\n * 19:33: Incident is declared at [status.1password.com](http://status.1password.com)\n * 20:03: Root cause is identified as a load balancer configuration issue\n * 20:24: Load balancer is recreated with correct configuration\n * 20:26 Recovery is confirmed for [app.kolide.com](http://app.kolide.com)\n * 20:28 Recovery is confirmed for [auth.kolide.com](http://auth.kolide.com)\n \n* **Contributing Factors \\(if any\\):**\n\n * **Shared component scope not visible during review or validation.** The network infrastructure class affected by the change was shared across multiple services, but this dependency was not documented or surfaced in the change review process. As a result, the pre-production validation, while performed in a lower environment before production rollout, did not cover all dependent services, and the impact on Device Trust was not identified before the change reached production.\n * **Concurrent diagnostic signals slowed root cause identification.** At the time the outage began, unrelated certificate renewal errors surfaced alongside the network connectivity failure. Investigating both signals simultaneously delayed identification of the network configuration change as the root cause.\n \n\n## How Was It Resolved?\n\n* **Resolution Steps:** Once the source of the outage was identified, engineers reverted the configuration change. The affected network infrastructure was recreated with its original, publicly accessible configuration, restoring routing to all Device Trust authentication endpoints. Service recovery was confirmed sequentially across affected services before the incident was closed.\n* **Verification of Resolution:** Following the revert, engineers verified that all Device Trust authentication endpoints were reachable and accepting traffic. Customer confirmation of resolution was subsequently received through the support team.\n\n## What We Are Doing to Prevent Future Incidents\n\n* **Require explicit approval for destructive infrastructure changes.** We are implementing safeguards that require manual review and approval before changes that would destroy and recreate critical network infrastructure can be applied. This creates a forcing function to catch unintended scope before changes reach production.\n* **Improve scope visibility for shared infrastructure components.** We are documenting the dependencies between shared infrastructure components and the services that rely on them, and integrating this information into our change review process. Future changes to shared components will require an explicit assessment of downstream impact before deployment.\n* **Strengthen pre-production validation across shared dependencies.** We are updating our change promotion process to require validation against all services that share affected components \u2014 not only the intended target \u2014 before changes are promoted to production.\n* **Reduce single points of failure in traffic routing.** We are evaluating architectural changes to introduce redundancy into Device Trust's traffic routing configuration, so that a failure in any single component results in degraded service rather than a complete outage.\n\n## Next Steps and Communication\n\n* No action is required from our customers at this time.\n\nWe are committed to providing a reliable and stable service, and we are taking the necessary steps to learn from this event and prevent it from happening again. Thank you for your understanding.\n\nSincerely,\n\nThe 1Password Team", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-02T16:30:48.837-04:00", "resolved_inferred": false, "started_at": "2026-07-02T15:44:00.651-04:00", @@ -77,7 +77,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-30T10:09:25.287-04:00", "resolved_inferred": false, "started_at": "2026-06-29T18:08:19.241-04:00", @@ -90,7 +90,7 @@ "body": "The issue is now resolved, and access to 1Password services should be fully restored.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-24T15:01:46.148-04:00", "resolved_inferred": false, "started_at": "2026-06-24T13:15:10.565-04:00", @@ -103,7 +103,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-18T14:50:42.250-04:00", "resolved_inferred": false, "started_at": "2026-06-18T13:54:11.964-04:00", @@ -116,7 +116,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-17T12:00:17.093-04:00", "resolved_inferred": false, "started_at": "2026-06-16T12:24:03.697-04:00", @@ -129,7 +129,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-12T19:18:57.981-04:00", "resolved_inferred": false, "started_at": "2026-06-11T17:49:05.374-04:00", @@ -142,7 +142,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-16T16:36:03.709-04:00", "resolved_inferred": false, "started_at": "2026-05-16T11:51:33.535-04:00", @@ -155,7 +155,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-04T14:34:49.601-04:00", "resolved_inferred": false, "started_at": "2026-05-04T13:59:28.385-04:00", @@ -168,7 +168,7 @@ "body": "# Incident Postmortem - Login and Sync Issues\n\n**Date of Incident:** 2026-04-27 \n**Time of Incident \\(UTC\\):** 14:15 - 15:41 \n**Service\\(s\\) Affected:** All web APIs \n**Impact Duration:** Approximately 86 minutes\n\n## Summary\n\nOn April 27, 2026, [1Password.com](http://1password.com/) experienced a period of elevated error and full service unavailability in our USA/Global region. A defect deployed in application scaling logic caused a cascading failure during peak usage. This resulted in a period of service unavailability for customers in the USA/Global region.\n\nThis was not a security incident, and there was no loss of data.\n\n## Impact on Customers\n\n* **Sign-in and account access:** Customers in the USA/Global region experienced errors or were unable to sign in or access their 1Password accounts between approximately 14:15 and 15:41 UTC on April 27, 2026.\n* **All 1Password clients:** The disruption applied to all client types, including the web app, CLI, browser extensions, and desktop and mobile applications, for customers connecting through the USA/Global region.\n* **Geographic regions affected:** Only customers on the USA/Global region were affected. Other regions were not impacted.\n\n## What Happened?\n\nWe deployed a change to how our services signal their readiness to serve requests, which contained a latent defect.\n\n* **Timeline of events:**\n\n * **2026-04-27 14:15 UTC** - Load increase triggers issues.\n * **2026-04-27 14:29 UTC** - Incident declared; response team mobilized.\n * **2026-04-27 15:41 UTC** - Issue identified and fix deployed.\n * **2026-04-28 18:06 UTC** - Incident formally resolved following monitoring.\n \n\n## How Was It Resolved?\n\nOur on-call engineering team identified the scaling logic as the cause of the cascading failure and disabled it via a configuration change. Once disabled, capacity was restored, and traffic recovered. A subsequent configuration change was made to prevent this logic from being re-enabled in production environments.\n\n## What We Are Doing to Prevent Future Incidents\n\n* **Immediate fix:** We disabled the defective health check logic and locked the configuration to prevent it from being re-enabled in production.\n* **Retrospective:** We are conducting a full retrospective with the incident responders to identify further improvements to our systems and our response processes.\n\n## Next Steps and Communication\n\n* No action is required from our customers at this time.\n\nWe are committed to providing a reliable and stable service, and we are taking the necessary steps to learn from this event and prevent it from happening again. Thank you for your patience and understanding.\n\nSincerely,\n\nThe 1Password Team", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-28T14:00:34.801-04:00", "resolved_inferred": false, "started_at": "2026-04-27T10:54:26.804-04:00", @@ -181,7 +181,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-22T12:06:19.982-04:00", "resolved_inferred": false, "started_at": "2026-04-22T11:18:52.323-04:00", @@ -194,7 +194,7 @@ "body": "# 2026-04-14 SEV1 Incident Postmortem - Hosted Service in the US experiencing high latency and errors\n\n# Incident Postmortem - Elevated Application Error\n\n**Date of Incident:** 2026-04-14 \n**Time of Incident \\(UTC\\):** 17:25 - 18:00 \n**Service\\(s\\) Affected:** Sign in, Admin console \n**Impact Duration:** Approximately 35 minutes\n\n## Summary\n\nOn April 14, 2026, [1Password.com](http://1Password.com) experienced elevated error rates due to an increase in traffic to our USA/Global infrastructure. Requests arrived more quickly than they could be serviced in our USA/global region. Customers experienced errors and high latency.\n\nThis was not a security incident, and there was no loss of data.\n\n## Impact on Customers\n\n* **Sign-in and account access:**\u00a0Some customers in the USA/Global region experienced errors when attempting to sign in or access their 1Password accounts between 17:25 and 18:00 UTC on April 14, 2026.\n* **All 1Password clients:**\u00a0The disruption applied to all client types, including the web app, browser extensions, and desktop and mobile applications, for customers connecting through the USA/Global region.\n* **Number of affected requests:**\u00a0Approximately 2.95% of requests over the incident window to [1Password.com](http://1Password.com) \\(USA/Global\\) during the incident window resulted in errors or timeouts, though for some brief spikes up to 45% of requests failed.\n* **Geographic regions affected:**\u00a0Customers on our USA/Global only, other regions were not affected.\n\n## What Happened?\n\nAn unusually high volume of traffic exceeded the capacity of our controls, and triggered latency and errors in the underlying applications.\n\n* **Timeline of events:**\n\n * **2026-04-14 17:25**\u00a0- Start of incident.\n * **2026-04-14 17:36**\u00a0- Issue identified.\n * **2026-04-14 17:51**\u00a0- Fix implemented.\n * **2026-04-14 18:01** - Recovery complete.\n \n* **Root cause analysis:** An increase in traffic exceeded the capacity of our traffic management layer, causing degraded service for customers in the USA/Global region.\n\n## How Was It Resolved?\n\n* Established runbooks for load shedding and system upgrades mitigated the issue.\n\n## What We Are Doing to Prevent Future Incidents\n\n* **Resolution:** We made two key changes to prevent recurrence:\n\n 1. **Increased capacity of internal systems**\n 2. **Upgraded traffic controls at the network edge**\n \n* **Verification:** Since implementing these changes, we have observed several additional instances of unusually high traffic matching this incident. In each case, the new controls handled the traffic automatically with no impact to customers or our systems.\n\n## Next Steps and Communication\n\n* No action is required from our customers at this time.\n\nWe are committed to providing a reliable and stable service, and we are taking the necessary steps to learn from this event and prevent it from happening again. Thank you for your understanding.\n\nSincerely,\n\nThe 1Password Team", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-14T21:54:58.647-04:00", "resolved_inferred": false, "started_at": "2026-04-14T13:25:14.000-04:00", @@ -207,7 +207,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-22T11:17:50.561-04:00", "resolved_inferred": false, "started_at": "2026-04-13T13:24:27.560-04:00", @@ -220,7 +220,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-02T10:23:16.557-04:00", "resolved_inferred": false, "started_at": "2026-04-01T10:13:38.187-04:00", @@ -233,7 +233,7 @@ "body": "A fix has been deployed and this issue is now resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-31T20:43:02.537-04:00", "resolved_inferred": false, "started_at": "2026-03-31T17:28:13.895-04:00", @@ -246,7 +246,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-16T13:43:02.427-04:00", "resolved_inferred": false, "started_at": "2026-03-16T13:11:54.093-04:00", @@ -259,7 +259,7 @@ "body": "Users were unable to retrieve documents across multiple platforms. This included degraded performance or failures when attempting to access documents via the CLI as well as through other interfaces.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-12T11:00:00.000-04:00", "resolved_inferred": false, "started_at": "2026-03-12T11:00:00.000-04:00", @@ -272,7 +272,7 @@ "body": "The scheduled maintenance is now complete", "first_seen": "2026-09-04T07:06:16Z", "impact": "maintenance", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-11T03:39:58.741-04:00", "resolved_inferred": false, "started_at": "2026-03-10T16:35:10.567-04:00", @@ -285,7 +285,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-30T13:09:06.557-05:00", "resolved_inferred": false, "started_at": "2026-01-30T10:35:45.063-05:00", @@ -298,7 +298,7 @@ "body": "The fix for the identified 2FA issue has been resolved as of version 8.12.4. The Sign-In attempts policy will become available in the coming weeks.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-03T10:52:27.515-05:00", "resolved_inferred": false, "started_at": "2026-01-23T15:33:54.000-05:00", @@ -311,7 +311,7 @@ "body": "# Incident Postmortem - 1Password Browser Extension Code Syntax Rendering Issue\n\n**Customer impact began \\(stable rollout start\\):** 2025-12-09\n\n**Investigation Started:** 2025-12-17\n\n**Incident Declared \\(UTC\\):** 2025-12-30 13:13\n\n**Fixed Release First Available:** 2026-01-01\n\n**Fixed Release Fully Available and Verified:** 2026-01-05\n\n**Incident Marked Resolved \\(UTC\\):** 2026-01-05 02:15\n\n**Service\\(s\\) Affected:** 1Password browser extension\n\n## Summary\n\nThe 1Password browser extension, which works by injecting code into web pages, inadvertently included code from PrismJS, a third party dependency, breaking syntax highlighting on some websites that display code blocks. The issue was reported in beta in early December, escalated after additional customer reports and a report from an external partner, and required releasing a stable update to remove the problematic dependency chain. This issue affected page rendering only and did not expose vault data or credentials.\n\n## Impact on Customers\n\nCustomers experienced broken code-block syntax highlighting on websites with `` HTML elements while using the 1Password browser extension version 8.11.22 across all major browsers.\n\n* **Code snippet rendering issue:** Syntax highlighting for code blocks was broken on sites that display code snippet; impacted sites included developer documentation pages, technical forums, and blogs with code snippets.\n* **Browser scope:** Reported in Chromium-based browsers initially, and confirmed to affect all major browsers.\n* **Customer reports:** Started in beta with a single report on December 3, 2025, with additional reports in stable December 15\u201316, 2025. From December 9, 2025 through January 3, 2026 we received 55 unique customer reports. The issue was later observed in stable and amplified via social media.\n\n## What Happened?\n\nThe injected content script in the 1Password browser extension was able to include UI-related dependencies from other parts of the 1Password codebase in a context where they should not exist. This happened due to a small change that accidentally pulled in additional libraries caused by insufficient restrictions/guardrails on what dependencies could be imported into injected scripts.\n\n* **Detection and Escalation:**\n\n On December 3, 2025, we received a beta report that syntax highlighting was broken when the 1Password extension was enabled. That report was incorrectly tagged and did not reach the owning team for timely triage, so we did not recognize it as a potential release blocker before version 8.11.22 rolled out to stable on December 9, 2025.\n\n\n\n On December 17, 2025, an external partner reported the issue affecting stable. That report was routed correctly, we connected it to the earlier beta issue, and we began investigation and remediation.\n\n\n* **Timeline of Events \\(UTC\\):**\n\n * 2025-12-03: Internal ticket created after beta report of broken syntax highlighting.\n * 2025-12-09: Bug released to stable version 8.11.22.\n * 2025-12-15 to 2025-12-16: Three additional customers reported the issue \\(not yet routed to the owning team\\).\n * 2025-12-17: An external partner reported the issue affecting stable via a shared Slack channel; the Filling & Saving team began investigation.\n * 2025-12-22: Fix merged \\(script pruning applied broadly to remove PrismJS from injected scripts\\).\n * 2025-12-30: Reports surfaced that social media users observed the issue; stable update coordination began.\n * 2025-12-31: Releases published across all browser platforms.\n * 2026-01-01: Release approved by web stores.\n \n* **Root Cause Analysis:** We did not have an enforced dependency boundary for injected content scripts, which allowed unexpected UI and runtime dependencies to be bundled into the page-injected context.\n* **Trigger:** A new import introduced an indirect dependency chain from an injected script to a UI module and ultimately to PrismJS.\n* **Contributing Factors \\(if any\\):**\n\n * Mis-triage of beta report\n * Missing side-effect regression tests\n \n\n## How Was It Resolved?\n\nWe removed PrismJS from the scripts the extension injects into web pages by eliminating the import chain that pulled it into the injected bundle. We then shipped an updated extension across all supported browsers.\n\n* **Mitigation Steps:**\n\n * Coordinated releasing a stable update once stable impact and broader visibility were confirmed.\n \n* **Resolution Steps:**\n\n * Fix merged on 2025-12-22.\n * Fix was applied to the previous stable release.\n * New beta/stable builds created and published across platforms.\n * Fix approved by web stores as of 2026-01-01.\n * Releases published across nightly, beta, and stable.\n * Because extension updates roll out via browser web stores and auto-update schedules, we consider the fix fully available once all stores had approved the release and we verified the issue could no longer be reproduced on known affected sites.\n \n* **Verification of Resolution:**\n\n * We tested the new builds on known affected websites, validating that code block formatting is working as expected.\n * We confirmed that the browser extension build no longer contained the PrismJS library.\n \n\n## What We Are Doing to Prevent Future Incidents\n\n* Added lint rules to block disallowed imports into injected scripts.\n* Added internal documentation describing how to avoid dangerous imports and the potential impacts.\n* Ensure new lint rules to prevent dangerous imports are blocking in CI pipelines.\n* Add an automated test to internal testing sites to ensure injected content scripts don\u2019t introduce side effects.\n* Implement automated rules \\+ a triage SLA so new beta issues are reviewed by the owning team before stable release decisions.\n* Ensure bundle size changes are blocking changes, enforced by our automated build systems as part of the code review process.\n\n## Next Steps and Communication\n\n* Most browsers will auto-update extensions via their web stores. If the issue persists, customers should manually check for updates and verify they are on the fixed extension versions \\(8.11.27 and newer\\). Customers can verify their version in their browser\u2019s extension/add-ons settings \\(1Password extension version **8.11.27** or newer\\).\n* We will continue monitoring for regressions and follow up on guardrails \\(blocking lint rules, bundle-size checks, and automated website-side-effect tests\\).\n\nWe are committed to providing a reliable and stable service, and we are taking the necessary steps to learn from this event and prevent it from happening again. Thank you for your understanding.\n\nSincerely,\n\nThe 1Password Team", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-23T15:04:42.406-05:00", "resolved_inferred": false, "started_at": "2026-01-23T15:04:42.360-05:00", @@ -324,7 +324,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-12T17:58:31.086-05:00", "resolved_inferred": false, "started_at": "2026-01-12T12:24:08.874-05:00", @@ -337,7 +337,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-17T10:08:48.151-05:00", "resolved_inferred": false, "started_at": "2025-12-17T09:35:23.396-05:00", @@ -350,7 +350,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-30T16:52:23.620-05:00", "resolved_inferred": false, "started_at": "2025-11-30T15:35:48.095-05:00", @@ -363,7 +363,7 @@ "body": "# Incident Postmortem - Cloud Services Degraded\n\n**Date of Incident:** 2025-11-18 \n\n**Time of Incident \\(UTC\\):** 5:03pm UTC - 6:05pm UTC \n\n**Service\\(s\\) Affected:** SSO, sign in, sign up, CLI, web interface, access to vault content and other items, admin console, MFA\n\n**Impact Duration:** ~60 mins\n\n## Summary\n\nOn November 18, 2025, at 5:03 PM UTC, 1Password experienced degraded and temporarily unavailable cloud services for customers in the US region. The issue was caused by database resource exhaustion, causing operations to fail and connections to be rejected. This was not a security incident and no customer data was impacted. The issue was resolved by resizing the database to restore normal performance and ensure additional capacity for future growth.\n\n## Impact on Customers\n\n* **Single Sign-on \\(SSO\\), Multi-factor Authentication \\(MFA\\):** Users with SSO or MFA enabled experienced delays, and in some cases failures to log in.\n* **Browser Extension:** Users who needed to authenticate via the web interface were unable to unlock their vaults.\n* **Web Interface, Administration**: Customers were unable to log in, sign-ups failed, syncing between devices was not functioning, access to vault and other items were unavailable and the admin console was not reachable.\n* **API Access:** CLI users and API requests received timeout errors and slow responses.\n* **Number of Affected Customers \\(approximate\\):** All customers utilizing cloud interfaces and APIs in the affected region for the duration of the incident.\n* **Geographic Regions Affected \\(if applicable\\):** US/Global.\n\n## What Happened?\n\n* **Timeline of Events \\(UTC\\):**\n\n * 2025-11-18 4:59pm: Automated monitoring detects increased errors\n * 2025-11-18 5:03pm: Team began investigating\n * 2025-11-18 5:09pm: Servers restarted, service is still degraded\n * 2025-11-18 5:23pm: Public status page updated to Investigating and services Degraded\n * 2025-11-18 5:25pm: Servers scaled down to reduce database load\n * 2025-11-18 5:41pm: Database instance size upgrade started\n * 2025-11-18 5:44pm: Potentially problematic cron job disabled\n * 2025-11-18 5:56pm: Services slowly started to scale up\n * 2025-11-18 5:57pm: Services started to come back as the database instance resize completes\n * 2025-11-18 6:05pm: Incident marked as Identified\n * 2025-11-18 6:05pm: Team continues to monitor, performance has returned to normal levels\n * 2025-11-18 6:23pm: Incident marked as Monitoring and services Operational\n * 2025-11-18 7:16pm: Incident marked as resolved\n \n* **Root Cause Analysis:** The refactor of a feature increased the impact of a poorly performing query that had previously gone undetected. The result was the exponential increase in resource consumption for the main database. Once resources were fully exhausted, the service rejected connections and all requests failed.\n* **Contributing Factors \\(if any\\):**\n\n * Non-performant queries\n * Database under-provisioned\n \n\n## How Was It Resolved?\n\n* **Mitigation Steps:**\n\n * Background services were halted to reduce load on the database.\n * Application servers were scaled down to further reduce load.\n \n* **Resolution Steps:** Increasing the database instance size resolved the issue.\n* **Verification of Resolution:** Monitoring metrics were closely observed to ensure error rates returned to normal and database performance had stabilized.\n\n## What We Are Doing to Prevent Future Incidents\n\n* **Improving monitoring:** We are updating our monitoring systems to better detect database issues like this before impacting customers.\n* **Improve database performance:** We are refactoring the responsible query to improve performance and reduce load, and tuning the background service to prevent resource contention.\n\n## Next Steps and Communication\n\nNo action is required from our customers at this time.\n\nWe are committed to providing a reliable and stable service, and we are taking the necessary steps to learn from this event and prevent it from happening again. Thank you for your understanding.\n\nSincerely,\n\nThe 1Password Team", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-18T14:15:40.905-05:00", "resolved_inferred": false, "started_at": "2025-11-18T12:22:41.032-05:00", @@ -376,7 +376,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-18T10:47:43.501-05:00", "resolved_inferred": false, "started_at": "2025-11-18T07:06:21.480-05:00", @@ -389,7 +389,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-18T10:37:24.918-05:00", "resolved_inferred": false, "started_at": "2025-11-13T10:57:39.653-05:00", @@ -402,7 +402,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-06T17:04:08.478-05:00", "resolved_inferred": false, "started_at": "2025-11-06T15:16:11.532-05:00", @@ -415,7 +415,7 @@ "body": "The upstream provider has reported full service recovery and Trelica is fully operational. This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-30T10:11:06.156-04:00", "resolved_inferred": false, "started_at": "2025-10-29T14:20:52.280-04:00", @@ -428,7 +428,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-28T21:37:45.856-04:00", "resolved_inferred": false, "started_at": "2025-10-28T16:41:50.485-04:00", @@ -441,7 +441,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-24T14:08:14.942-04:00", "resolved_inferred": false, "started_at": "2025-10-24T13:04:32.048-04:00", @@ -454,7 +454,7 @@ "body": "# Incident Postmortem - 1Password Cloud Services Degraded\n\n* **Date of Incident:** 2025-10-20 \n* **Time of Incident \\(UTC\\):** 07:26:00 - 20:55:00 \n* **Service\\(s\\) Affected:** [1Password.com](http://1password.com/) website, Sign in, Access to passwords and other items \n* **Impact Duration:** 13 hours, 29 minutes\n\n## Summary\n\nOn October 20, 2025 at 07:26:00 UTC, [1Password.com](http://1password.com/) faced intermittent latency, authentication failures, and degraded service availability due to a major outage at [AWS in the us-east-1 region](https://aws.amazon.com/message/101925/). This was not a security incident and no customer data was affected.\n\nAs a result, the 1Password server-side application experienced degradation or intermittent failures, affecting up to 50% of traffic in the US region. Complete service restoration occurred in conjunction with AWS\u2019s final mitigations around 18:30 UTC.\n\n## Impact on Customers\n\nAll US customers accessing 1Password cloud services experienced intermittent latency, authentication failures, and degraded availability on [1Password.com](http://1password.com/).\n\n* **File Share:** Sharing of passwords via links could intermittently fail\n* **Login:** Users logging into vaults experienced timeout errors and slow responses\n* **Web Access:** Users accessing their vault through the web interface experienced timeout errors and slow responses\n* **API Access:** CLI users and API requests received timeout errors and slow responses\n\n## What Happened?\n\nAt 07:11:00 UTC, AWS began experiencing DNS resolution failures in the us-east-1 region, initially affecting DynamoDB and rapidly cascading to multiple AWS services.\u00a0 1Password monitoring detected impact at 07:26:00 UTC when monitoring alerts fired for inability to scale up clusters, and an incident was declared.\n\n1Password immediately deployed mitigations inside our infrastructure to ensure there was adequate compute capacity to serve our US-based users, which included pausing deployments and scaling down any services not critical to key functionality for our users.\n\n**Timeline of Events \\(UTC\\):**\n\n* 06:55:05 - 1Password monitoring triggers warning for unavailable Pods in Deployment \\(caused by inability to obtain AWS IAM credentials\\)\n* 07:03:06 - 1Password monitoring alerts for 5xx errors on auth start endpoint \\(caused by inability to obtain AWS IAM credentials\\) - pages authentication team, but alert recovers within minutes\n* 07:26:00 - 1Password monitoring alerts for inability to scale clusters, engineers begin investigating, Incident declared\n* 07:26:41- AWS confirms elevated error rates across multiple services\n* 07:49:06 - 1Password monitoring alerts for 5xx errors on auth start endpoint \\(caused by inability to obtain AWS IAM credentials\\)\n* 07:51:09 - AWS identifies DNS as the root cause, begins mitigation\n* 08:02:13 - 1Password suspends auto-scaling tooling to retain existing capacity\n* 09:27:33 - AWS reports significant recovery signs\n* 10:35:37 - AWS declares DNS issue fully mitigated, services recovering\n* 14:14:00-15:43:00 - AWS announced full recovery across all services; throttles EC2 launches\n* 16:42:49 - 1Password tooling and users start reporting 503s and inability to login due to volume of traffic\n* 16:50:00 - 1Password services restarted to reset and flush connections, prioritizing post-recovery traffic.\n* 20:53:00 - AWS resolves their incident\n* 20:55:00 - 1Password engineers overscale deployments for stability and overnight observation\n* Oct 21, 2025 - Incident resolved after confirmation of complete upstream recovery\n\n## How Was It Resolved?\n\n* **Mitigation Steps:** 1Password paused deployments and auto-management of cluster capacity to ensure enough capacity was available to serve users through peak access times. As demand outstripped available capacity, 1Password engineering reset the circuit breaker to allow additional connections to the service.\n* **Resolution Steps:** AWS announced system restoration and a reduction in throttling of EC2 API calls. To ensure sufficient capacity for peak traffic, 1Password engineers updated the required number of pods for core services the following business day and resumed auto-management of cluster capacity tooling. The following day, 1Password engineers resumed verification of the health of the systems, deployments, and auto-scaling of the services.\n* **Verification of Resolution:** Engineers observed monitoring systems and cluster management tooling logs to ensure system health.\n\n## **Root Cause Analysis**\n\n* **Root Cause Analysis:** The failures in AWS's internal network affected multiple AWS product APIs. This disruption directly impacted 1Password\u2019s ability to scale up infrastructure, deploy applications, and retrieve configuration data.\n* **Contributing Factors \\(if any\\):**\n\n * Third-party incident response services and paging services were affected by the AWS incident, which complicated communications.\n * Upstream customer IDPs were affected by the AWS outage, and returned errors that resulted in authentication failures.\n \n\n## What We Are Doing to Prevent Future Incidents\n\n* **Improve Incident Response:** Create additional backup protocols for when our incident response tooling is unavailable.\n* **Improve multi-service outage response:** Create strong break-glass runbooks in the event of a multi-service cloud provider outage.\n\n## Next Steps and Communication\n\nNo action is required from our customers at this time.\n\nWe are committed to providing a reliable and stable service, and we are taking the necessary steps to learn from this event and prevent it from happening again. Thank you for your understanding.\n\nSincerely,\n\nThe 1Password Team", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-21T09:51:06.701-04:00", "resolved_inferred": false, "started_at": "2025-10-20T05:05:23.290-04:00", @@ -467,7 +467,7 @@ "body": "# Incident Postmortem - Degraded performance when accessing 1Password\n\n**Date of Incident:** 2025-09-26 \n**Time of Incident:** 4:20pm UTC - 5:39pm UTC \n**Service\\(s\\) Affected:** SSO, Web Sign In, Sign Up, Web Interface, CLI \n**Impact Duration:** ~60 minutes\n\n## Summary\n\nOn September 26, 2025 at 4:20 UTC 1Password\u2019s web interface and APIs experienced degraded performance for all customers in the US region. This was not a result of a security incident and customer data was not affected.\n\n## Impact on Customers\n\nDuring the duration of the incident:\n\n* **Web interface, Administration:** Customers experienced delays when accessing the 1Password web interface.\n* **Single Sign-on \\(SSO\\), Multi-factor Authentication \\(MFA\\):** Users with SSO or MFA enabled experienced delays, and in some cases failures to login.\n* **Command Line Interface \\(CLI\\):** CLI users faced increased latency and timeouts when attempting to access our web APIs.\n* **Browser Extension:** Users requiring web interface authentication experienced delays or failures.\n* **Number of Affected Customers \\(approximate\\):** ~30%\n* **Geographic Regions Affected:** [1password.com](http://1password.com) \\(US/Global\\)\n\n## What Happened?\n\nAt 4:20PM UTC and 5 PM UTC There were traffic bursts which caused extra load on one of our caches. This cache was under-provisioned to handle that spike of activity, which resulted in it exhausting available CPU. This caused cascading errors/latency which manifested in slow and failed requests.\n\n* **Timeline of Events \\(UTC\\):**\n\n * 2025-09-26 4:20pm: Spike in customer traffic began\n * 2025-09-26 4:29pm: Automated monitoring detects increased errors and latency\n * 2025-09-26 4:35pm: The team activates our incident protocol and begins investigation\n * 2025-09-26 4:58pm: The team decides to restart application servers\n * 2025-09-26 5:00pm: The servers have been restarted, service is still degraded, as a second traffic burst begins\n * 2025-09-26 5:18pm: Service starts to improve\n * 2025-09-26 5:25pm: The team detects increased load for the second time\n * 2025-09-26 5:33pm: The team restarts application servers again\n * 2025-09-26 5:39pm: Service is back to normal, team continues to investigate\n * 2025-09-26 7:26pm: Team has found the issue, and proceeds to upgrade cache instance size\n * 2025-09-26 7:49pm: Cache upgrade completed successfully\n * 2025-09-26 7:50pm: Team continues to monitor, performance has returned to nominal levels\n * 2025-09-26 8:24pm: Incident is marked as resolved\n \n* **Root Cause Analysis:**\n\n A code library installed in July introduced latency issues for cache connections. Authentication operations weren't properly rate-limited, allowing large traffic influxes. During peak traffic periods, the cache infrastructure was operating near maximum CPU capacity. The incident occurred when a burst of authentication traffic pushed the cache CPU utilization to 100%. The increased latency and CPU usage together directly caused the incident.\n\n\n* **Contributing Factors:**\n\n * Latency increase due to cache library version upgrade\n * Inadequate rate limiting allowed traffic bursts to go unchecked\n * Cache instance size is under-provisioned\n \n\n## How Was It Resolved?\n\n* **Mitigation Steps:** Restarting application servers temporarily mitigated the latency and errors, but the problems returned when traffic spiked again.\n* **Resolution Steps:** Increasing the instance size for the cache resolved the issue.\n* **Verification of Resolution:** The incident team tested the upgrade in a staging deployment before executing it in production. They then monitored metrics to confirm the system returned to normal levels.\n\n## What We Are Doing to Prevent Future Incidents\n\n* **Improve capacity planning for cache:** We will ensure our internal infrastructure is properly sized to handle current traffic volumes and accommodate future growth. We'll implement regular resource evaluations to maintain adequate capacity as our traffic increases. We will also implement proactive alerting systems that notify our teams when resource utilization approaches critical thresholds.\n* **Update library to a more performant version:** We will upgrade our caching library to the latest stable version to eliminate the current latency issues.\n* **Improve rate limiting for operations that triggered the traffic burst:** Enhancing our rate limiting system will significantly improve our ability to handle future traffic bursts.\n* **Timeline for Implementation:** Observability improvements have already been implemented, and we will complete the remaining work by the end of Q1, 2026.\n\n## Next Steps and Communication\n\nNo action is required from our customers at this time.\n\n\u200c\n\nWe are committed to providing a reliable and stable service, and we are taking the necessary steps to learn from this event and prevent it from happening again. Thank you for your understanding.\n\nSincerely,\n\nThe 1Password Team", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-26T16:24:58.720-04:00", "resolved_inferred": false, "started_at": "2025-09-26T12:51:38.625-04:00", @@ -480,7 +480,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-25T13:22:01.362-04:00", "resolved_inferred": false, "started_at": "2025-09-25T11:43:45.006-04:00", @@ -493,7 +493,7 @@ "body": "# Incident Postmortem - Some customers are unable to interact with the admin console\n\n**Date of Incident:** 2025-09-24 \n\n**Time of Incident \\(UTC\\):** 02:27 - 17:16 \n\n**Service\\(s\\) Affected:** Admin console, Sign in \n\n**Impact Duration:** 36:49\n\n## Summary\n\nSome customers with certain account configurations were placed on a blocklist and presented with a 403 error page after accessing the admin console.\n\n## Impact on Customers\n\n* **Admin console:** Affected customers were presented with a 403 error page whenever they tried to interact with any of the admin console pages.\n* **Log in:** Affected customers were also unable to log in to the application.\n* **Number of Affected Customers \\(approximate\\):** 515\n* **Geographic Regions Affected \\(if applicable\\):** All regions\n\n## What Happened?\n\n* **Timeline of Events \\(UTC\\):**\n\n * Sep 24th 2:27am: Spike in application monitoring alerted engineers to increased rates of IP blocking\n * Sep 24th 3:00am: Cause identified as a change to requests in the application, which had been partially rolled out via a feature flag.\n * Sep 24th 4:03am: The feature flag was enabled to all customers which reduced the spike, but IP blocks continued throughout the day.\n * Sep 24th 10:03pm: Merged an application change to revert the change to prevent the issue reoccurring.\n * Sep 25th 5:03pm: The change was deployed with scheduled application release, error rate dropped off shortly after.\n \n* **Root Cause Analysis:** The issue was caused by GET requests to the Users API exceeding the URL length limit due to a recent change to append a list of UUIDs to the request parameters to resolve customer reported performance issues.\n* **Contributing factors:**\n\n * Requests were switched from GET to POST to prevent requests from exceeding the URL limit, however an issue with the feature flag configuration was causing UUIDs to be sent with the GET endpoint.\n * An underlying issue with the feature flag not resolving as expected in the application.\n \n\n## How Was It Resolved?\n\n* **Mitigation Steps:** Customers were manually removed from the blocklist at multiple points in time as we evaluated the root cause and worked to patch the root issue.\n* **Resolution Steps:** The issue was mitigated by removing UUIDs at the API level if a GET request is used. Additional logging has been added to identify the root cause of the feature flag configuration issue.\n* **Verification of Resolution:** We monitored our server logs to ensure that we did not observe any additional GET requests to the affected URL.\n\n## What We Are Doing to Prevent Future Incidents\n\n* **Audit additional admin console API requests:** We\u2019re performing a sweep of admin console API requests to ensure the utilization of POST requests with highly parameterized URLs.\n* **Remove the feature flag misconfiguration:** We\u2019re correcting the way the feature flag is configured to ensure consistent outcomes.\n\n## Next Steps and Communication\n\nNo action is required from our customers at this time.\n\n\u200c\n\nWe are committed to providing a reliable and stable service, and we are taking the necessary steps to learn from this event and prevent it from happening again. Thank you for your understanding.\n\nSincerely,\n\nThe 1Password Team", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-24T00:10:05.235-04:00", "resolved_inferred": false, "started_at": "2025-09-23T23:00:42.664-04:00", @@ -506,7 +506,7 @@ "body": "# **Provisioning Invites could not be accepted**\n\n**Date of Incident:** 2025-09-23 \n**Time of Incident \\(UTC\\):** 17:18 - 00:46 \n**Service\\(s\\) Affected:** Sign Up \n**Impact Duration:** 7h 28m\n\n## **Summary**\n\nFor 7 hours and 28 minutes, 1Password Provisioning invites could not be accepted, presenting to the user as an invite expiry. Invites could not be accepted due to a web browser routing defect that was not caught during development, review, or release. First identified by customer reports approximately two and a half hours after release, the issue was escalated to development teams and an incident was immediately called. The root cause was identified as a defect introduced by a web client modification, and a fix was created, tested, and released. By 00:46 UTC, the fix was deployed to all environments and service was fully restored.\n\n## **Impact on Customers**\n\n* **Sign-up:** Provisioning invites could not be accepted.\n* **Number of Affected Customers \\(approximate\\):** 100% of provisioning invites could not be accepted\n* **Customer-facing impact**: Users clicking their invite links encountered a misleading \u2018Invite Expired\u2019 message.\n* **Geographic Regions Affected:** 1Password USA/Canada/EU/Enterprise\n\n## **What Happened?**\n\nA change to the web client contained a router defect that incorrectly rendered provisioning invites as expired. Users were presented with an error message that erroneously stated the invite was expired. The change responsible for introducing the defect was able to be released because it was not captured under automatic change notification rules, was lacking automated test coverage, and was not included in the set of manual tests.\n\n* **Timeline of Events \\(UTC\\):**\n\n * 17:18: 1Password Release containing defect\n * 19:53 \\(2 hours, 35 minutes later\\) First customer report\n * 20:49 \\(56 minutes later\\) Escalation to developer teams\n * 21:01: \\(12 minutes later\\) Incident called\n * 22:02: \\(1 hour, 1 minute later\\) Root cause identified\n * 22:29: \\(27 minutes later\\) Fix created and testing initiated\n * 23:49: \\(1 hour, 30 minutes later\\) Fix merged\n * 00:46: \\(57 minutes later\\) Fix released and service fully restored\n \n* **Root Cause Analysis:** A change modified the order in which key provisioning web routes were rendered. As a result, the route handling provisioning invitations failed to use the correct query parameters and the invite rendered as expired.\n* **Contributing Factors:** Automated tests on this endpoint do not exist. Manual testing missed testing the Provisioning routes. The modified code was not covered by automatic change notification rules to notify the Provisioning team. An existing bug that can fail the resending of invites was an initial red herring during the investigation.\n\n## **How Was It Resolved?**\n\n* **Resolution Steps:** The defect in the 1Password web client was corrected so provisioning invites would render correctly.\n* **Verification of Resolution:** 1Password engineering tested the changes and validated that the functionality was restored, as well as verifying that requests for the affected endpoints were successful after the fix was deployed.\n\n## **What We Are Doing to Prevent Future Incidents**\n\n* **Improve automated tests:** We are enhancing our automated tests for the Provisioning Invite routes.\n* **Expand automatic change notifications:** Expanding coverage of automatic change notification rules for areas of code owned by the Provisioning team.\n\n## **Next Steps and Communication**\n\n* No action is required from our customers at this time. Existing invites do not need to be resent and may be accepted.\n* If you are still experiencing issues, please contact our support team at [support@1password.com](mailto:support@1password.com). \n\nWe are committed to providing a reliable and stable service, and we are taking the necessary steps to learn from this event and prevent it from happening again. Thank you for your understanding.\n\nSincerely,\n\nThe 1Password Team", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-23T22:07:03.833-04:00", "resolved_inferred": false, "started_at": "2025-09-23T17:24:26.152-04:00", @@ -519,7 +519,7 @@ "body": "We have confirmed resolution of this issue and this incident is now resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-19T14:17:59.181-04:00", "resolved_inferred": false, "started_at": "2025-09-18T16:19:16.670-04:00", @@ -532,7 +532,7 @@ "body": "Our provider has deployed a fix. Error rates have returned to normal. This incident is now resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-18T13:08:47.709-04:00", "resolved_inferred": false, "started_at": "2025-09-18T10:48:41.437-04:00", @@ -545,7 +545,7 @@ "body": "# Performance Degradation\n\n**Date of Incident:** 2025-09-03 \n**Time of Incident \\(UTC\\):** 11:06 - 12:07 \n**Service\\(s\\) Affected:** All APIs \n**Impact Duration:** 61 minutes\n\n## Summary\n\nFor 61 minutes on the morning of September 3rd, 2025, all 1Password APIs in the US/Global environment had degraded performance or returned an error for approximately 20% of requests. 92% of the impact was mitigated within 13 minutes at 11:19 by automation scaling up infrastructure. By 12:06 a manual restart of the remaining infrastructure completed mitigation. A permanent fix was implemented and deployed to prevent the issue from reoccurring.\n\n## Impact on Customers\n\n* **APIs:** High latency, or a 500 Internal Server Error.\n* **Number of Affected Customers:** 20% of all requests returned errors for 13 minutes, 1% thereafter.\n* **Geographic Regions Affected \\(if applicable\\):** 1Password USA/Global\n\n## What Happened?\n\n* **Timeline of Events \\(UTC\\):**\n\n * 11:05: A customer started a stream of an unusually high volume of requests to an API with sub-optimal performance.\n * 11:06: Some servers started consuming abnormally high memory, causing slow response times and high error rates.\n * 11:19: Automation scaled up infrastructure to service additional load\n * 11:30: Increased errors trigger escalation, on-call engineer begins investigation\n * 11:51: Engineers declare an incident and alert response teams\n * 12:02: Response team begins restarting affected servers.\n * 12:07: All servers completed restarts, and error rates returned to normal levels\n \n* **Root Cause Analysis:** A poorly performing cache operation was triggered repeatedly in a short period of time across multiple servers, leading directly to greatly delayed responses.\n\n## How Was It Resolved?\n\n* **Mitigation Steps:** Automatic instance scaling restored over 98% of operational capacity after 13 minutes. Full capacity was restored through manual intervention\n* **Resolution Steps:** We refactored the poorly performing query.\n* **Verification of Resolution:** We tested the affected API to confirm refactoring of query produced the desired performance improvement. We deployed the fix and monitored it for 24 hours to assert the issue was resolved.\n\n## What We Are Doing to Prevent Future Incidents\n\n* We are auditing services for sub-optimal query performance.\n\n## Next Steps and Communication\n\n* No action is required from our customers at this time.\n\n\u200c\n\nWe are committed to providing a reliable and stable service, and we are taking the necessary steps to learn from this event and prevent it from happening again. Thank you for your understanding.\n\nSincerely,\n\nThe 1Password Team", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-03T07:00:00.000-04:00", "resolved_inferred": false, "started_at": "2025-09-03T07:00:00.000-04:00", @@ -558,7 +558,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-18T18:53:58.892-04:00", "resolved_inferred": false, "started_at": "2025-08-18T17:36:12.219-04:00", @@ -571,7 +571,7 @@ "body": "## **Incident Postmortem - Sign-in Service Degradation**\n\n* **Date of Incident:** 2025-08-05\n* **Time of Incident \\(UTC\\):** 20:20 - 21:20\n* **Service\\(s\\) Affected:** Sign-in, Web Application, Command Line Interface \\(CLI\\), Single Sign On \\(SSO\\), API\u2019s\n* **Impact Duration:** 1 hour\n\n### **Summary**\n\nOn August 5, 2025, 1Password experienced a service degradation that impacted customers' ability to sign in and access the web application. The incident was triggered during a planned architectural improvement when a misconfigured rollback attempt caused an overload of traffic and a subsequent database connection bottleneck. The issue was resolved by correcting the misconfiguration and restarting the web application servers, fully restoring service.\n\n### **Impact on Customers**\n\nDuring the service disruption, some customers experienced degraded performance when accessing their 1Password vaults and signing in.\n\n* **Sign-in Issues**: Customers may have experienced sign-in slowness or timeouts.\n* **Error Messages**: Customers may have seen error messages when attempting to sign in, such as \"Can't sign in\", \"Failed to determine sign in methods for email\", or \"Upstream connect error\".\n* **Vault Access**: Some customers experienced degraded performance when accessing their 1Password vaults.\n* **Geographic Regions Affected:** USA/Global\n\n### **What Happened?**\n\nThe incident was part of ongoing improvements to the 1Password infrastructure and was not the result of a security incident. Customer data was not affected.\n\n**Timeline of Events \\(UTC\\):**\n\n* **17:12**: A planned, phased rollout of an architectural improvement to authentication systems begins.\n* **18:20**: Engineers monitoring the rollout begin to observe higher latency during sign-in for a small subset of accounts.\n* **20:17**: A rollback of the change is initiated. An error in the rollback configuration sends a high volume of traffic to the new code path, causing a database connection bottleneck. Engineers observing the deployment immediately observe service impact.\u00a0\n* **20:21**: A corrective action is deployed to revert the system to its previous state before the misconfigured rollback.\n* **20:39**: While impact is still being observed, a failover from the primary database to a secondary database is initiated. This action has no effect.\u00a0\n* **20:58**: A restart of the service that manages incoming traffic to our services is initiated to reset connections.\n* **21:13**: A rolling restart of the web application servers is initiated.\n* **21:20**: Service is fully restored for all customers.\n\n**Root Cause Analysis:** The root cause was an error in the configuration of an attempted rollback. This misconfiguration incorrectly routed a high volume of sign-in traffic through a new, slower code path, which created a bottleneck of connections to our primary database and made the web application unresponsive.\n\n### **How Was It Resolved?**\n\n**Resolution Steps:** The issue was fully resolved through two key actions:\n\n1. The rollback misconfiguration was identified and corrected, which stopped traffic from flowing to the problematic new code.\n2. A rolling restart of the web application servers was performed to clear the backlog of stuck database connections.\n\n**Verification of Resolution:** Monitoring systems were closely observed for 30 minutes to ensure error rates returned to normal.\n\n### **What We Are Doing to Prevent Future Incidents**\n\nWe are working to implement the following improvements:\n\n* **Improve configuration testing**: We will improve testing procedures of configuration updates and their rollbacks prior to being pushed to production.\n* **Improve our deployment tooling**: We will add additional validation to our traffic management tools to prevent similar configuration errors.\n* **Review our incident response procedures**: We have updated the runbook used to respond to this type of incident with guidance that will enable faster recovery.\n* **Enhance our monitors**: We will add more specific alerts that will help us more quickly distinguish between different application tiers, allowing for faster diagnosis and time to resolution.\n\n### **Next Steps and Communication**\n\nNo action is required from our customers. 1Password applications are designed to be resilient, with local copies of vault data always available on customer devices, even without a connection to the 1Password service.\n\nIf you are still experiencing issues, please contact our support team.\n\nWe are committed to providing a reliable and stable service, and we are taking the necessary steps to learn from this event and prevent it from happening again. Thank you for your understanding.\n\nSincerely, The 1Password Team", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-05T17:59:54.829-04:00", "resolved_inferred": false, "started_at": "2025-08-05T16:46:48.030-04:00", diff --git a/api/v/3stepit.json b/api/v/3stepit.json index 4b55870141bb8aa3b08e1a6f7965c0e0eff828d9..61e4b807095a5161e334258bcc9780211c301311 100644 --- a/api/v/3stepit.json +++ b/api/v/3stepit.json @@ -3,7 +3,7 @@ "slug": "3stepit", "platform": "statuspage", "status_url": "https://status.3stepit.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "unknown", "history_backfilled": false, "first_watched": "2026-09-04T07:06:16Z", diff --git a/api/v/ably.json b/api/v/ably.json index a7cd367435d61e17490dfcc3b5a6ea05bc95e123..049fb38a193cbbbb47050c0698bbd44baf915552 100644 --- a/api/v/ably.json +++ b/api/v/ably.json @@ -3,7 +3,7 @@ "slug": "ably", "platform": "statuspage", "status_url": "https://status.ably.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-28T13:33:07.563Z", "resolved_inferred": false, "started_at": "2026-08-28T12:08:59.848Z", @@ -25,7 +25,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-20T20:24:39.725Z", "resolved_inferred": false, "started_at": "2026-08-20T19:29:36.560Z", @@ -38,7 +38,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-20T19:10:12.011Z", "resolved_inferred": false, "started_at": "2026-08-20T19:07:30.168Z", @@ -51,7 +51,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-17T10:32:02.145Z", "resolved_inferred": false, "started_at": "2026-02-17T10:19:49.762Z", @@ -64,7 +64,7 @@ "body": "This incident has now been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-14T06:05:15.720Z", "resolved_inferred": false, "started_at": "2026-02-14T05:57:02.135Z", @@ -77,7 +77,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-21T19:52:33.695Z", "resolved_inferred": false, "started_at": "2026-01-21T18:11:23.300Z", @@ -90,7 +90,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-11T18:59:46.298Z", "resolved_inferred": false, "started_at": "2025-12-11T18:36:15.932Z", @@ -103,7 +103,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-05T09:18:05.254Z", "resolved_inferred": false, "started_at": "2025-12-05T08:59:03.822Z", @@ -116,7 +116,7 @@ "body": "The incident is now resolved. The elevated protocol adaptor error rate affected EU regions for 36 minutes from 11.25am-12.01pm UTC, for 15 minutes in US regions from 11.50am-12.05pm UTC, and for 14 minutes in AP regions from 11.48am-12.02pm UTC.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-25T12:11:34.496Z", "resolved_inferred": false, "started_at": "2025-11-25T11:38:38.898Z", @@ -129,7 +129,7 @@ "body": "# Summary of incident affecting the Ably production service on 28-29 October - investigation and conclusions\n\n## Overview\n\nThere was an incident affecting Ably's service between 28 and 29 October 2025, which affected the delivery of webhooks. The impact of the incident lasted from 1134 on 28 October to 0936 on 29 October \\(all times UTC\\). The incident occurred as a result of the deployment of new webhook functionality that was incompatible with many already-configured webhook rules.\n\nNow we have a good understanding of the underlying problem, the various factors that led to that having customer impact, and the effectiveness of our response in this case.\n\n## Background\n\nAbly operates a number of production clusters for its service around the globe. There is a main production cluster that services the majority of customer accounts, plus a small number of dedicated clusters for specific accounts. Each of the clusters has a presence in multiple regions in a globally federated system.\n\n### Ably integration rules\n\nAbly processes messages that are published on channels, and directs those to realtime subscribers on those channels, and also directs them to other targets as configured by integration rules. Multiple targets are supported for egress integration rules, including message queues \\(Kafka, AMQP\\) and generic HTTP endpoints \\(webhooks\\).\n\nRules are configured via a control plane which supports:\n\n* direct interactive \\(\"click-ops\"\\) configuration in the Ably dashboard;\n* a [Control API](https://ably.com/docs/api/control-api);\n* a [Terraform Provider](https://ably.com/integrations/ably-terraform-provider) which acts through the Control API.\n\nThe source of truth for integration rule definitions is Ably's core \"realtime\" platform, and the other services \\(the website and control API service\\) obtain access to that via an internal provisioning API.\n\nIntegration rule definitions comprise some attributes that are generic \\(such as `channelFilter` that specifies which channels the rule applies to\\), and some that are specific to each type of integration rule target \\(such as the target endpoint, credentials, and any protocol-specific attributes\\). Some generic attributes - ie attributes that are capable of having a meaning for multiple rule types - are not universally supported, since the evolution of rule features is based on adoption and priority. As a result, the schema for integration rule definitions contains multiple optional generic attributes as well as a wide range of type-specific attributes.\n\nOne generic feature is an option that enables a custom set of trust anchors \\(TLS certificates\\) to be configured for a rule; this is to support integrations that target TLS endpoints that have a self-signed certificate rather than certificates issued by a public Certificate Authority \\(CA\\). This feature is used by customers having self-hosted endpoints, either as part of development/CI infrastructure, or as internally-facing production services where the operational effort of maintaining a certificate from a public CA is not justified.\n\nAt the time of the incident custom trust anchors were supported for Apache Pulsar and Kafka rules, and support had just been added for webhooks.\n\n### Ably's service deployment process\n\nAbly adopts a staggered deployment approach whereby each change is deployed gradually, minimising the adverse impact of any regression that might exist in new software versions having escaped all prior test phases. Changes are typically deployed on a weekly basis; usually in the main \\(multi-tenanted\\) cluster this means that changes are deployed to the ap-southeast-2 \\(Sydney\\) region first, and error rates monitored, before deploying to the remaining regions starting the following day. However, if a deploy needs to be expedited for any reason, subsequent regions can be deployed after a change has been in ap-southeast-2 for only a few hours.\n\nMost monitoring is automated; metrics are gathered for a wide range of service health metrics, including the rates of logged error events, and the rate of error API responses. When error metrics exceed a threshold then on-call engineers are paged to investigate.\n\nSince the majority of Ably's infrastructure comprises immutable EC2 instances, any deploy consists of deploying new instances with the new software version in parallel with retirement of superseded instances. For a normal deploy this process happens over the course of several hours so that the number of instances being retired at any given time is small, minimising any impact of the update on existing traffic. If a deploy needs to be accelerated, such as if making an emergency rollback, then deployment would more typically involve deploying a full complement of replacement instances immediately, followed by termination of old instances at a rate that reflects the urgency of the operation. Immediate and abrupt termination of multiple instances simultaneously leads to a greater risk of loss of ephemeral channel state, so even in accelerated rollbacks the preference is for old instances to be terminated gradually so that there is an orderly shedding of load so as to avoid any data loss.\n\n## As it happened\n\nA change to add support for custom trust anchors was implemented, and this change was part of a set of changes deployed in a staggered deployment starting on 28 October. This happened in ap-southeast-2 from 1134 and, since this change set also included a fix for an unrelated problem, it was expedited and started in other regions from around 1500.\n\nStarting at 1940 on 28 October there was a handful of customer reports of a problem with webhook delivery. There were two independent customer reports of issues on 28 October and a handful of reports overnight.\n\nAt 0731 on 29 October Ably's customer support team escalated the problem reports to Ably's engineering team for investigation. At 0745 an incident was declared, on-call engineers were paged and investigation started.\n\nThe problem was determined to be a regression introduced in the previous day's deploy.\n\nAt 0746 a rollback process was initiated to revert the changes. Rollback was initiated first in ap-southeast-2. At 0811 rollback was initiated for all regions and dedicated clusters that had received the changes.\n\nThe rollback completed at 0936 and errors dropped to zero.\n\n## Investigation\n\nThe investigation aimed to understand:\n\n* the cause of failed webhook invocations;\n* how Ably's testing had failed to detect the regression;\n* how Ably's monitoring had failed to detect the regression;\n* the effectiveness of the response, including the time taken to respond following the first customer problem reports.\n\nThe conclusions of the investigation are summarised below.\n\n### The cause of failed webhook invocations\n\nThe new code that caused the problem was adding support for custom trust anchors for webhooks. This code would look in the rule configuration for a configured set of trust anchors and, if present, use those instead of the system set of trust anchors for public CAs. The problem was caused by the fact that a significant number of preexisting rule definitions already had an empty set of trust anchors configured. The new code then used that empty set instead of the default set and failed to verify the certificate chain for any TLS endpoint.\n\nThese failures were logged internally with a severity that classifies the event as a client configuration error rather than a system error.\n\nThe presence of the empty trust anchor set in existing rule definitions was due to a long-standing behaviour in the web \\(dashboard and control API\\) services that create and update rules via the realtime platform's provisioning API. When custom trust anchor support was first added for Pulsar rules \\(in November 2021\\), the set of custom trust anchors became a generic rule attribute; but the web service would configure an empty set instead of a true zero value when custom trust anchors were unset. This meant that any rules that had been created since November 2021, even for types that did not initially support custom trust anchors, would have an empty set configured.\n\nRemedial actions identified in this area are as follows.\n\n**Fix the immediate regression.** As an interim behaviour, interpret an empty custom trust anchor array as if custom trust anchors are unset \\(and so use the default trust anchors\\).\n\n**Correct web service behaviour.** Update the web service so that a true zero value is set instead of an empty array when custom anchors are not set.\n\n**Correct the configuration of existing rules.** Perform a database update for all existing rule definitions that have an empty array configured.\n\n### The failure of tests to detect the regression\n\nThe relevant tests are a combination of unit tests and integration tests within the test suite of the realtime platform.\n\nUnit test coverage includes test coverage of all webhook configuration options \\(and new tests were included with the deployed change\\), plus tests for different endpoint behaviours \\(HTTP 1 vs HTTP/2 for example\\). Unit tests mock different parts of the surrounding code and system in order to have tests that are as targeted as possible.\n\nIntegration tests include full end-to-end tests that create integration rules via the provisioning API that point to a range of endpoints existing as part of the CI system.\n\nThe reason that none of these tests identified the problem is that none used the configuration in the same way as the web service; in particular, any rule that did not have custom trust anchors would be configured with a null entry. There was no expectation in the tests that an empty set should be interpreted as having no custom configuration.\n\nThere was no integration test coverage of the end-to-end behaviour when rules are created via the web service.\n\nRemedial actions identified in this area are as follows.\n\n**Improve web service testing of integrations.** This should at least include:\n\n* create web service unit tests that verify that an unset custom trust anchor configuration results in a zero value being configured.\n* create web service integration tests that verify end-to-end behaviour involving creation of rules via the web service, with and without custom trust anchors set.\n\n### The failure of monitoring to detect the regression\n\nAbly monitors a wide range of service metrics and alerts relevant engineering teams when those metrics indicate a service problem. Monitored metrics include errors logged internally whilst servicing customer traffic, the rate of error responses to customer requests, and the rate of errors or failures in traffic that is generated by Ably specifically for service monitoring. For this last category, Ably operates a series of \"quality of service\", or QoS, traffic generators that exercise a range of service functionality, so certain classes of failure relating to deployment can be identified that would not be identifiable via CI.\n\nErrors - both those logged internally and customer-visible error responses - can be classified broadly into:\n\n* bad requests - that is, operations that fail because the arguments or parameters of the request are invalid. When these errors are associated with an error code, it is typically in the 4xx range - these include general bad requests, plus authentication and authorisation failures;\n* internal errors - that is, errors that arise performing some operation that ought to succeed, but fails because of an issue \\(eg an unexpected exception, a failure to communicate over the network, or an assertion failure\\). When these errors are associated with an error code, it is generally in the 5xx range.\n\nA high rate of internal errors - either in our internal logs, or in customer-visible responses - is an indication of a problem with the service. A high rate of bad requests is more typically a problem on the customer side; an application is attempting operations that cannot succeed.\n\nAll 5xx \\(internal error\\) metrics are monitored and alerts are generated when they exceed a threshold indicating a problem.\n\nMany 4xx \\(bad request\\) metrics are monitored but in most situations these do not generate alerts. This is for several reasons:\n\n* most are not an indication of a system problem; there is simply some invalid operation being attempted by a client;\n* all public endpoints are subject to a very high rate of spurious requests that fail authentication and authorisation checks, so the general rate of 4xx errors is high.\n\nSimilarly, problems with invocation of a webhook \\(or other rule target\\) are usually a result of misconfiguration of the rule, or unavailability of the target endpoint, and these are classified with a 4xx status code. There is a material background level of such errors.\n\nGiven the very high rate of background 4xx errors on external endpoints, it is generally difficult to identify any pattern on those endpoints that is indicative of a system problem.\n\nNotwithstanding this, all Ably Enterprise accounts have alerts set up both for 4xx and 5xx error metrics. 4xx alerts do not generally page an engineer out-of-hours, but both engineering and customer success teams get notified when there is an unexpected elevated rate of 4xx errors for an Enterprise customer. The configuration of those accounts within Ably's monitoring and alerting systems is added when that customer is onboarded as an enterprise customer.\n\nIn this incident the overall increase in rule invocation failures was not significant in comparison with the normal ambient background error rate so, based on those metrics, there was no clear signal of there being a problem, and it was not sufficient to cross the alerting threshold on any existing enterprise accounts. Many customers with the highest usage volumes had rules created before November 2021, which were unaffected by the problem.\n\nAt the time of the incident, QoS monitoring simulated traffic for some integrations but not webhooks.\n\nRemedial actions identified in this area are as follows.\n\n**Improve the ability in metrics and alerts for integration rules to discriminate between Ably problems and end-user problems.** Although most errors are a result of configuration problems, or problems in end-user infrastructure, it is still clearly possible for Ably regressions to also generate errors. We need to have more intelligent metrics and alerts that identify such occasions without creating an unsustainable number of false-positives. One possibility is to create alerts based on individual metrics labelled by rule type, to ensure that an increase in error rate for an individual rule type is alerted, even if that increase is not a material fraction of errors across all rule types. Another possibility is to correlate error levels with deploy events, or with software versions, so if a variation in error rate is correlated with a code change it is more likely to trigger an alert.\n\n**Add webhook tests to QoS monitoring.** Continuous testing in a production setting of simulated traffic should be extended to include webhooks.\n\n### The effectiveness of the response\n\nFrom the first customer impact of this issue to the final resolution was 22 hours. This is far too long.\n\nAbly's response in this incident led to delays at multiple stages:\n\n* from the time of the problematic code being deployed to the first reported issue was around 8 hours;\n* from the first report to raising an incident was around 12 hours;\n* the full rollback, from the time that an incident was declared, was nearly 2 hours.\n\nOf course, had there been suitable alerting for the production problem we would have reacted sooner; but this timeline reflects the fact that even with the information we did have, the response was slow. This was due to a combination of factors:\n\n* the reports received were all received outside of business hours and, given that the customers raising those reports were not enterprise customers, there was no out-of-hours process to review them;\n* there was some delay before the support team correlated multiple reports to conclude that there was a problem with the delivery of webhooks;\n* the rollback process was comparatively slow, deliberately avoiding a more disruptive abrupt rollback since the issue had impact for a relatively small number of customers.\n\nThe remedial actions in this area are as follows.\n\n**Review processes for handling and escalating issue reports out-of-hours.** Customers on lower support tiers can legitimately expect slower response times to deal with any individual issues or questions they have, but when an Ably problem arises that affects them there is no means for the relevant response team to be made aware. We will review our processes with the aim of improving support in these situations.\n\n## Conclusion\n\nThe service issues were the direct result of a regression in the Ably service - specifically, an incompatibility between a new feature \\(custom trust anchors for webhooks\\) and the existing state of rule configurations.\n\nThe cause of the extended duration of the incident was that the classification and rate of failed delivery events resulted in no alert being generated, which meant that Ably was not aware of the ongoing problem until it was reported by customers. Although it is difficult to monitor 4xx error rates effectively, because of the high background level of such errors, there is clearly a need to improve on the current situation where Ably regressions can go undetected. There was significant additional delay in triggering a response because the reports were received on a support channel that was not monitored out of business hours.\n\nOnce alerted to the problem, Ably initiated the response quickly, but the operational nature of the rollback meant that it took nearly two hours until it was completed.\n\nWe take service continuity very seriously, and this incident represents another opportunity to learn and improve the level of service we are committed to providing for our customers. We are sorry for the disruption that was experienced in this instance, and are committed to identifying and implementing remedial actions so that we eliminate the risk of similar failures in the future.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-29T09:42:56.242Z", "resolved_inferred": false, "started_at": "2025-10-29T08:57:58.445Z", @@ -142,7 +142,7 @@ "body": "Customers may be experiencing connectivity issues affecting our website (ably.com), customer dashboards, the Control API (control.ably.net), the Ably blog and documentation.\n\nOur realtime services are not affected by this issue at this time.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-09T14:10:08.000Z", "resolved_inferred": false, "started_at": "2025-10-09T14:10:08.000Z", @@ -155,7 +155,7 @@ "body": "The incident has been resolved", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-13T13:25:12.428Z", "resolved_inferred": false, "started_at": "2025-08-13T12:47:25.642Z", diff --git a/api/v/abnormal-security.json b/api/v/abnormal-security.json index b622c96b5cf32b7681c1c4d0234d53a2ca24f301..db4976844e72fb4e507012d99b64eeb3b6bdb401 100644 --- a/api/v/abnormal-security.json +++ b/api/v/abnormal-security.json @@ -3,7 +3,7 @@ "slug": "abnormal-security", "platform": "statuspage", "status_url": "https://abnormalsecurity.statuspage.io", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "Starting at 08:50 UTC, Abnormal experienced a service disruption affecting AI Security Mailbox notifications for US and EU customers. Throughout the incident, the AI Security Mailbox continued to function as expected and customer security protection was not impacted; however, affected customers did not receive notifications during the incident window. Abnormal worked with its email delivery provider to reinstate the account, and AI Security Mailbox notifications are now being sent as expected. All notifications from the incident window will be processed. If you experience any further issues, please reach out to Abnormal Support at support@abnormalsecurity.com.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-09-01T11:15:08.000-07:00", "resolved_inferred": false, "started_at": "2026-09-01T09:40:09.000-07:00", @@ -25,7 +25,7 @@ "body": "Starting at 13:15 UTC, Abnormal experienced a service disruption affecting Inbound Email Security and Inline detection and remediation for US customers, resulting in elevated processing time. During this window, some messages experienced delayed detection and remediation. Engineers restored the live processing queue and inline remediation error rates recovered as of 14:18 UTC.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-09-01T07:38:06.436-07:00", "resolved_inferred": false, "started_at": "2026-09-01T07:38:06.392-07:00", @@ -38,7 +38,7 @@ "body": "The engineering team has resolved the primary issue affecting Account Takeover case details in the Gov region. Case details and timeline data are now loading as expected. The remaining minor issues will be addressed separately. Abnormal considers this incident resolved. If you have any further questions, please reach out to support at support@abnormalsecurity.com.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-03T18:22:42.380-07:00", "resolved_inferred": false, "started_at": "2026-08-03T11:50:35.634-07:00", @@ -51,7 +51,7 @@ "body": "Between 22:10 UTC and 22:50 UTC on July 27, 2026, Abnormal experienced a service disruption affecting Inbound Email Security, Inline, and Graymail processing for Google Workspace customers in both US and EU regions. During this time, inbound email processing was temporarily interrupted, which may have caused delays in email detection and remediation. The engineering team has resolved the issue, and all services have been fully restored. All emails from the impacted window have been successfully reprocessed. If you experience any further issues, please reach out to the support team at support@abnormalsecurity.com.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-27T16:10:10.640-07:00", "resolved_inferred": false, "started_at": "2026-07-27T16:10:10.597-07:00", @@ -64,7 +64,7 @@ "body": "As of 04:44 UTC on July 8, 2026, all services have fully recovered and are now live processing traffic for US and EU tenant customers. Abnormal will reprocess all messages received during the impact window to ensure full security analysis is applied. If you experience any continued issues, please reach out to the support team at support@abnormalsecurity.com.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-07T21:44:51.664-07:00", "resolved_inferred": false, "started_at": "2026-07-07T15:58:51.315-07:00", @@ -77,7 +77,7 @@ "body": "Between 16:45 UTC and 17:25 UTC on June 5, 2026, Abnormal experienced message remediation delays affecting Inbound Email Security for GOV customers. During this time, some emails may have experienced delayed remediation. The Abnormal engineering team actively worked to address the issue, and service was fully restored as of 17:25 UTC. All emails from the impacted window have since been reprocessed. If you experience any further issues, please reach out to our support team at support@abnormalsecurity.com.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-05T11:03:42.271-07:00", "resolved_inferred": false, "started_at": "2026-06-05T11:03:42.204-07:00", @@ -90,7 +90,7 @@ "body": "Between 20:00 UTC and 21:22 UTC on June 4, 2026, Abnormal experienced a service disruption impacting inbound email ingestion for all inline US customers. During this time, inbound emails sent to customers may not have been ingested or processed. The Abnormal engineering team identified and resolved the root cause, and service was confirmed recovering as of 21:22 UTC. Emails affected during the incident window have been reprocessed. If you experience any further issues, please reach out to our support team at support@abnormalsecurity.com.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-04T15:07:09.115-07:00", "resolved_inferred": false, "started_at": "2026-06-04T15:07:09.071-07:00", @@ -103,7 +103,7 @@ "body": "Starting at 17:45 UTC on June 2, 2026, Abnormal experienced a service disruption affecting email detection and remediation for Inbound Email Security customers in the EU region. Additionally, between 18:00 UTC and 19:00 UTC, US customers experienced degraded AI Security Mailbox functionality. As of 19:20 UTC, all services have been restored and live traffic is processing normally across both regions. Abnormal is continuing to work through retry queues to reprocess any emails from the impacted window. If you experience any further issues, please reach out to our support team at support@abnormalsecurity.com.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-02T11:43:52.927-07:00", "resolved_inferred": false, "started_at": "2026-06-02T11:08:36.794-07:00", @@ -116,7 +116,7 @@ "body": "Microsoft services have fully recovered from the degraded M365 sign-in audit log delivery, and Abnormal services have also recovered as of 09:41 UTC on May 30, 2026. Abnormal engineering has initiated a reprocess to ensure all Account Takeover detections from the impacted time window are properly processed. No sign-in data was lost during this event. If you experience any further issues, please reach out to Abnormal support at support@abnormalsecurity.com.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-30T09:14:27.080-07:00", "resolved_inferred": false, "started_at": "2026-05-29T08:25:25.028-07:00", @@ -129,7 +129,7 @@ "body": "Starting at 22:00 UTC on May 18, 2026, Abnormal identified an increase in legitimate emails being incorrectly flagged as malicious and remediated, impacting Inbound Email Security and AI Security Mailbox. The engineering team identified and disabled the rule responsible for falsely flagging these emails at 01:03 UTC on May 19, 2026. Messages affected during the impact window will be reprocessed.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-18T16:24:46.000-07:00", "resolved_inferred": false, "started_at": "2026-05-18T16:24:46.000-07:00", @@ -142,7 +142,7 @@ "body": "Between 00:19 UTC and 00:49 UTC, Abnormal experienced message remediation delays affecting Inbound Email Security for US customers. During this approximately 30-minute window, email remediation was temporarily delayed due to a backend database issue. The engineering team stopped the contributing process and remediation services recovered. All messages from the impacted window have since been reprocessed.\n\nIf you experience any further issues, please reach out to our support team at support@abnormalsecurity.com", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-14T18:07:36.453-07:00", "resolved_inferred": false, "started_at": "2026-05-14T18:07:36.403-07:00", @@ -155,7 +155,7 @@ "body": "Between approximately May 2, 2026, and May 4, 2026 at 18:45 UTC, Abnormal experienced a service disruption affecting Security Orchestration, Automation and Response (SOAR) API functionality, Portal data retrieval, and Threat Log display for US customers. During this time, customers utilizing SOAR API integrations may have experienced errors when attempting to query messages, attachments, and threat data. The Abnormal engineering team has deployed a fix and confirmed that SOAR API is functioning as expected. All affected services have been restored to normal operation. If you experience any further issues, please reach out to the Abnormal support team at support@abnormalsecurity.com.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-04T11:58:34.927-07:00", "resolved_inferred": false, "started_at": "2026-05-04T10:21:09.205-07:00", @@ -168,7 +168,7 @@ "body": "Between 00:30 UTC and 08:10 UTC on April 28, 2026, Abnormal experienced an issue impacting email detection and scoring accuracy, which may have resulted in some legitimate emails being incorrectly flagged. Abnormal engineering identified the root cause, implemented a fix, and confirmed that all email detection and scoring services have been fully restored. All messages received during the impact window will be replayed to ensure complete email protection coverage. If you experience any further issues, please reach out to the support team at support@abnormalsecurity.com.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-28T00:09:08.000-07:00", "resolved_inferred": false, "started_at": "2026-04-27T22:25:30.609-07:00", @@ -181,7 +181,7 @@ "body": "Starting at approximately 19:00 UTC on April 8, 2026, Abnormal received reports of customers being unable to access the Customer Support Portal. Some customers experienced intermittent or complete inaccessibility when attempting to log in or navigate the Portal. The Abnormal engineering team identified and resolved the underlying cause. As of 16:40 UTC on April 9, 2026, Customer Support Portal access has been fully restored and customers are able to successfully log in.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-09T10:05:10.168-07:00", "resolved_inferred": false, "started_at": "2026-04-09T08:15:45.239-07:00", @@ -194,7 +194,7 @@ "body": "Starting at 13:30 UTC on April 8, 2026, Abnormal experienced an issue with the email-based support case submission process due to a vendor-caused outage. Customers who submitted support requests by emailing support@abnormalsecurity.com or support@abnormal.ai may have experienced failures when attempting to create new cases. The vendor has confirmed that service has been restored, and Abnormal has verified that emails are now flowing as expected. Customers may resume submitting support requests via email.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-08T17:24:12.200-07:00", "resolved_inferred": false, "started_at": "2026-04-08T13:15:50.500-07:00", @@ -207,7 +207,7 @@ "body": "Between 09:53 UTC on April 4, 2026 and 17:38 UTC on April 6, 2026, Abnormal experienced an issue within the Gov Portal affecting the AI Security Mailbox Analyzed tab and remediation information cards on the message details page. During this time, Gov customers may have experienced failures when loading the AI Security Mailbox Analyzed tab, and remediation details may have appeared incomplete or failed to display on the message details page. The Abnormal engineering team identified and resolved the underlying issue, and full functionality has been restored. If you experience any further issues, please reach out to the support team at support@abnormalsecurity.com.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-08T08:56:25.510-07:00", "resolved_inferred": false, "started_at": "2026-04-08T08:56:25.473-07:00", @@ -220,7 +220,7 @@ "body": "Between approximately 16:00 UTC and 23:50 UTC on March 26, 2026, Abnormal experienced a service disruption impacting AI Security Mailbox report processing for US and EU customers. During this time, new reports submitted to AI Security Mailbox may not have been processed as expected. Abnormal engineers deployed a fix at 23:50 UTC and confirmed that services are now processing in real time. Any reports submitted during the impacted window are currently being reprocessed and are expected to be fully completed within the next few hours. If you experience any further issues, please reach out to the Abnormal support team at support@abnormalsecurity.com.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-26T17:14:59.090-07:00", "resolved_inferred": false, "started_at": "2026-03-26T16:03:45.801-07:00", @@ -233,7 +233,7 @@ "body": "Starting around 22:23 UTC on March 16, 2026, Abnormal experienced a service disruption impacting Inbound Email Security detection and remediation for some US customers. During this time, inline email processing was also affected, and some emails may not have been properly detected or remediated. Abnormal's engineering team actively worked to address the issue, and all services were fully restored as of 23:56 UTC. Detection and remediation are now operating as expected for US customers. If you experience any further issues, please reach out to Abnormal's support team at support@abnormalsecurity.com.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-16T17:00:55.004-07:00", "resolved_inferred": false, "started_at": "2026-03-16T16:21:02.350-07:00", @@ -246,7 +246,7 @@ "body": "Starting around 14:40 UTC, Abnormal experienced an issue with the EU Portal being inaccessible and displaying an error to EU customers. Email detection and remediation services were not impacted during this time and continued to operate normally. Access to the Abnormal Portal for EU customers has been restored as of 15:01 UTC. If you experience any further issues, please reach out to the Abnormal support team at support@abnormalsecurity.com.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-16T08:05:00.543-07:00", "resolved_inferred": false, "started_at": "2026-03-16T07:58:04.332-07:00", @@ -259,7 +259,7 @@ "body": "Between 18:00 UTC and 20:40 UTC on March 12, 2026, Abnormal identified an issue where messages flagged as attack, spam, or borderline experienced delays in appearing within the Threat Log for Gov customers. Inbound Email Security detection and remediation remained fully functional throughout the incident, and all threats continued to be identified and acted upon as expected. Abnormal engineers redeployed the affected services and confirmed recovery as of 20:40 UTC. All messages during the incident window were queued and have been processed. If you experience any further issues, please reach out to Abnormal support at support@abnormalsecurity.com.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-12T13:56:23.155-07:00", "resolved_inferred": false, "started_at": "2026-03-12T13:31:20.161-07:00", @@ -272,7 +272,7 @@ "body": "Between February 23, 2026 at 19:55 UTC and February 24, 2026 at 03:30 UTC, Abnormal experienced an issue impacting Threat Log visibility for GovCloud customers. During this time, newly detected threats did not appear in the Threat Log, and the Email Details page displayed \"content unavailable\" for previously flagged messages. Inbound email processing, threat detection, and remediation were not impacted throughout the duration of this incident. Abnormal engineers have confirmed that Threat Log services are now processing in real time and full visibility has been restored. If you have any questions or concerns, please contact support at support@abnormalsecurity.com.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-23T19:38:47.615-08:00", "resolved_inferred": false, "started_at": "2026-02-23T19:23:51.376-08:00", @@ -285,7 +285,7 @@ "body": "Between 14:28 UTC and 15:00 UTC on February 12, Abnormal experienced issues with customers being able to access the Abnormal Portal. During this time, customers may have experienced the inability to log into the Portal. Service has been fully restored as of 15:00 UTC for customers in US and EU regions. If you experience any further issues, please reach out to support@abnormalsecurity.com.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-12T07:04:27.912-08:00", "resolved_inferred": false, "started_at": "2026-02-12T06:57:28.660-08:00", @@ -298,7 +298,7 @@ "body": "Between 16:22 UTC on February 11 and 01:17 UTC on February 12, government customers may have experienced Account Takeover messages not being properly flagged for security threats. Abnormal's engineering team has resolved the issue and service is confirmed as fully functional. If customers experience any further issues, please reach out to support@abnormalsecurity.com", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-11T17:32:24.000-08:00", "resolved_inferred": false, "started_at": "2026-02-11T16:56:10.000-08:00", @@ -311,7 +311,7 @@ "body": "Between 19:28 UTC and 20:15 UTC, Abnormal experienced service degradation with the Portal. US customers might have experienced issues logging in and navigating the Abnormal Portal during this time. EU customers were not impacted. Abnormal mitigated the root cause and services have been confirmed as fully restored. If you experience any further issues please reach out to support@abnormalsecurity.com", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-11T12:26:37.453-08:00", "resolved_inferred": false, "started_at": "2026-02-11T11:56:41.000-08:00", @@ -324,7 +324,7 @@ "body": "Between 00:56 UTC and 16:00 UTC on February 10, 2026, Abnormal experienced a service disruption affecting email threat detection, AI Security Mailbox, and graymail processing for Government customers. During this time, some malicious and spam emails may not have been properly flagged or processed. Abnormal engineers restored service as of 16:00 UTC for email threat detection, AI Security Mailbox, and graymail processing for Government customers. If customers experience any further issues please reach out to support@abnormalsecurity.com for further assistance.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-10T08:07:21.940-08:00", "resolved_inferred": false, "started_at": "2026-02-10T07:21:45.000-08:00", @@ -337,7 +337,7 @@ "body": "As of 03:30 UTC on January 23, Abnormal's Inbound Email Security services have fully recovered from the processing delays due to the widespread Microsoft outage. Microsoft has confirmed that they have fully resolved the infrastructure issue that was impacting multiple services globally. All email processing has returned to normal performance levels. If you experience any further issues or need assistance, please reach out to Abnormal's support team at support@abnormalsecurity.com.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-23T09:54:53.183-08:00", "resolved_inferred": false, "started_at": "2026-01-22T12:32:40.000-08:00", @@ -350,7 +350,7 @@ "body": "As of 18:33 UTC, Abnormal has fully restored all impacted services. Portal performance has returned to normal levels, and customers can now successfully access threat logs and retrieve threat data through Security Orchestration, Automation and Response integrations without errors. All delayed threat log data has been processed and is now available in customer portals. If customers continue to experience any issues, please contact support at support@abnormalsecurity.com.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-21T10:44:39.542-08:00", "resolved_inferred": false, "started_at": "2026-01-21T09:52:52.100-08:00", @@ -363,7 +363,7 @@ "body": "As of 23:40 UTC on January 16, 2026, the Account Takeover event issue affecting FedRAMP customers has been fully resolved. All Account Takeover services are now operating normally. Abnormal's core email protection services remained fully operational throughout this incident and continued to protect against threats. If customers have any questions or concerns, please contact support at support@abnormalsecurity.com.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-15T16:05:08.499-08:00", "resolved_inferred": false, "started_at": "2026-01-15T12:39:05.793-08:00", @@ -376,7 +376,7 @@ "body": "Between 16:40 UTC and 17:00 UTC, Abnormal experienced a service degradation with the Abnormal Portal affecting Fedramp customers. During this time, Fedramp users experienced errors when trying to load and navigate the portal, along with delays with pages loading. Remediation and detection services remained fully operational throughout the incident window.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-15T09:11:05.000-08:00", "resolved_inferred": false, "started_at": "2026-01-15T09:11:05.000-08:00", @@ -389,7 +389,7 @@ "body": "Between 15:35 UTC and 16:37 UTC, customers experienced issues with the Abnormal Portal which caused slowness and failures when trying to load and navigate the portal. Email remediation and detection services remained fully operational during this time. Abnormal Portal services are now fully recovered and all functionality has been restored. If customers experience any further issues, please contact Abnormal support at support@abnormalsecurity.com.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-13T08:41:08.206-08:00", "resolved_inferred": false, "started_at": "2026-01-13T08:18:17.535-08:00", @@ -402,7 +402,7 @@ "body": "Between 20:04 UTC and 20:45 UTC, US customers experienced issues with the Abnormal Portal which caused difficulties loading and navigating the platform. During this time, some users may have encountered errors or delays when accessing portal features. Email detection and remediation services remained fully operational throughout this incident. Portal functionality has been restored and services are now available. If you experience any further issues pertaining to this incident, please contact us at support@abnormalsecurity.com.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-22T12:55:30.971-08:00", "resolved_inferred": false, "started_at": "2025-12-22T12:55:30.914-08:00", @@ -415,7 +415,7 @@ "body": "As of 12:40 UTC, Abnormal has implemented a fix and engineers are observing Security Orchestration, Automation Response traffic as expected. The service disruption affecting automated security workflows and response actions has been fully resolved. Please reach out to support@abnormalsecurity.com if you experience any further issues.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-20T04:48:01.732-08:00", "resolved_inferred": false, "started_at": "2025-11-20T03:44:24.722-08:00", @@ -428,7 +428,7 @@ "body": "Abnormal's engineering team has fully resolved the Portal access issue. All customers can now successfully log in to the Portal, and services are operating normally. Email security protection remained fully operational throughout this incident. No further updates will be provided for this issue. If customers experience any further issues, please reach out to support@abnormalsecurity.com.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-06T16:20:59.764-08:00", "resolved_inferred": false, "started_at": "2025-11-06T12:46:01.871-08:00", @@ -441,7 +441,7 @@ "body": "All email security services remain stable and are operating normally. Engineers have initiated reprocessing of all messages sent during the incident window to ensure complete security coverage. If customers experience any further issues, please reach out to support@abnormalsecurity.com.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-20T17:49:43.608-07:00", "resolved_inferred": false, "started_at": "2025-10-20T00:48:09.407-07:00", @@ -454,7 +454,7 @@ "body": "Abnormal's email security services and portal access have been fully restored as of 16:35 UTC. Our engineering team is currently processing the backlog of messages from the affected timeframe, which is expected to complete within the next hour. If you experience any further issues, please reach out to support@abnormalsecurity.com.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-14T10:15:02.134-07:00", "resolved_inferred": false, "started_at": "2025-10-14T09:13:01.000-07:00", @@ -467,7 +467,7 @@ "body": "Abnormal has successfully resolved the portal access issue that was affecting customers in Europe as of 21:30 UTC. Full portal functionality has been restored for all affected customers. Abnormal apologizes for any inconvenience this may have caused. If you continue to experience any issues accessing the portal, please contact support at support@abnormalsecurity.com.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-19T14:54:45.149-07:00", "resolved_inferred": false, "started_at": "2025-09-19T13:34:46.632-07:00", @@ -480,7 +480,7 @@ "body": "Engineers identified and resolved a configuration issue that was preventing detection and remediation services from functioning properly for FedRamp customers. All services have been fully restored, and engineering teams are performing a replay of all impacted messages from the incident window to ensure complete threat detection and remediation coverage.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-15T11:55:12.447-07:00", "resolved_inferred": false, "started_at": "2025-09-15T11:00:04.255-07:00", @@ -493,7 +493,7 @@ "body": "Portal access has been fully restored for all US customers as of 07:30 pm PT on September 12, 2025. Detection and remediation services were not impacted as part of this issue, and email protection continued to operate normally throughout the incident. If customers experience any further issues with portal access, please reach out to support at support@abnormalsecurity.com.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-12T19:35:24.674-07:00", "resolved_inferred": false, "started_at": "2025-09-12T18:54:40.532-07:00", @@ -506,7 +506,7 @@ "body": "All impacted mailboxes have been fully recovered and email protection services are now fully functional. If customers experience any issues with mailbox protection services, please contact support at support@abnormalsecurity.com.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-09T20:41:19.233-07:00", "resolved_inferred": false, "started_at": "2025-09-09T15:16:16.915-07:00", @@ -519,7 +519,7 @@ "body": "As of 00:17 UTC on August 22nd, Abnormal's engineering team has fully resolved the login issues affecting customers in our Federal Risk and Authorization Management Program environment. All customers should now be able to access the Abnormal Security Portal normally. Email detection and remediation services remained fully operational throughout this incident. Abnormal apologizes for any inconvenience this issue may have caused. If you experience any further issues related to portal logins, please reach out to support@abnormalsecurity.com", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-21T17:46:55.465-07:00", "resolved_inferred": false, "started_at": "2025-08-21T15:31:32.201-07:00", @@ -532,7 +532,7 @@ "body": "On 2025-08-18 at 16:50 UTC, Abnormal experienced a degradation of the Abnormal Portal where some customers experienced intermittent access issues and slow response times on the threat log and search and response features. The issue has been fully resolved as of 17:50 UTC, and all portal functionality is now operating normally. There was no impact on email remediation during this incident. Abnormal apologizes for any inconvenience this issue caused customers. If you continue to experience any portal access issues, please contact Abnormal Support at support@abnormalsecurity.com.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-18T11:00:41.151-07:00", "resolved_inferred": false, "started_at": "2025-08-18T10:41:46.000-07:00", @@ -545,7 +545,7 @@ "body": "This incident has been fully resolved. As of 21:13 UTC, Abnormal has completed reprocessing all emails from the impacted timeframe for European customers using Inbound Email Security. All affected emails have now been properly analyzed and protected. Abnormal's services are fully operational. If you experience any issues, please contact support at support@abnormalsecurity.com.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-14T15:52:28.089-07:00", "resolved_inferred": false, "started_at": "2025-08-14T06:31:07.007-07:00", diff --git a/api/v/acquia.json b/api/v/acquia.json index d7aba061b1dd04f0be3461f6802e7c605d3b1814..9b7604ee4bc75a5365ec41a1c1f81ca80d4ebfda 100644 --- a/api/v/acquia.json +++ b/api/v/acquia.json @@ -3,7 +3,7 @@ "slug": "acquia", "platform": "statuspage", "status_url": "https://status.acquia.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "The service interruption impacting the Acquia Task system has been fully resolved. AWS US-WEST-2 operations have stabilized, and all queued tasks and system functions are operating normally.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-09-04T02:18:51.438Z", "resolved_inferred": false, "started_at": "2026-09-03T23:19:58.731Z", @@ -22,21 +22,23 @@ "url": "https://stspg.io/v80txq618pg9" }, { -"body": "We've resolved the issue addressing customers use of Site Studio.\u00a0 We're continuing to monitor the service to ensure stability", +"body": "The issue impacting Site Studio endpoints has been fully resolved, and all systems are operational now.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", +"resolved_at": "2026-09-04T09:39:11.352Z", +"resolved_inferred": false, "started_at": "2026-09-03T23:04:11.328Z", -"state": "monitoring", +"state": "resolved", "title": "Multiple customers are currently affected by what appears to be an outage impacting the Site Studio endpoint", -"updated_at": "2026-09-04T04:34:56.887Z", +"updated_at": "2026-09-04T09:39:11.369Z", "url": "https://stspg.io/w32x9vnv014z" }, { "body": "This incident has been resolved. Our upstream search infrastructure partner, SearchStax, has successfully implemented the fix, and Pulse Performance Graphs are now displaying as expected. Core search functionality was unaffected throughout this incident. We apologize for any inconvenience caused and thank you for your patience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-09-04T02:04:42.869Z", "resolved_inferred": false, "started_at": "2026-09-03T16:27:23.205Z", @@ -49,7 +51,7 @@ "body": "We've resolve the problem causing an issue with some customers ability to log into DAM. Contact Customer Support for help on Acquia DAM Community if you continue to experience any ongoing issues.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-09-03T16:24:58.769Z", "resolved_inferred": false, "started_at": "2026-09-03T15:05:24.973Z", @@ -62,7 +64,7 @@ "body": "The issue impacting access to the Pipelines UI and Dashboard for MEO customers has been fully resolved.\r\nA fix was deployed and verification was completed to confirm that the Pipelines Dashboard is fully operational and performing normally.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-09-03T00:13:18.597Z", "resolved_inferred": false, "started_at": "2026-09-02T21:39:29.077Z", @@ -75,7 +77,7 @@ "body": "We've resolved the issue causing degraded file processing for customers hosted in the EU and have completed processing work that accumulated during the incident. Contact Customer Support for help on Acquia DAM Community if you continue to experience any ongoing issues.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-31T17:34:08.530Z", "resolved_inferred": false, "started_at": "2026-08-31T16:28:17.484Z", @@ -88,7 +90,7 @@ "body": "The issue affecting Edge Standard customers has been resolved. Akamai has addressed the vendor API issue, and security and performance metrics are now available in the Edge Standard UI", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-24T11:05:27.821Z", "resolved_inferred": false, "started_at": "2026-08-24T09:29:44.425Z", @@ -101,7 +103,7 @@ "body": "We can confirm that the issue was confirmed mitigated at 20:42 UTC on August 18, 2026 and the service has resumed normal operation.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-19T22:13:09.531Z", "resolved_inferred": false, "started_at": "2026-08-17T21:24:57.304Z", @@ -114,7 +116,7 @@ "body": "The log download issue affecting Acquia Cloud Next and MEO customers was resolved on Aug 11 09:38 UTC, and all systems are fully operational.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-12T09:27:30.470Z", "resolved_inferred": false, "started_at": "2026-08-11T07:40:11.926Z", @@ -127,7 +129,7 @@ "body": "The underlying cause of this service interruption has been addressed. All services are operational at this time.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-10T19:44:51.818Z", "resolved_inferred": false, "started_at": "2026-08-10T18:29:13.357Z", @@ -140,7 +142,7 @@ "body": "The underlying cause of this service interruption has been addressed. All services are operational at this time.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-06T22:48:56.050Z", "resolved_inferred": false, "started_at": "2026-08-06T21:54:59.185Z", @@ -153,7 +155,7 @@ "body": "The issue affecting Acquia Cloud Pipelines has been resolved. Pipeline processing has returned to normal operations, and all previously queued jobs have been handled. Please note that if any of your queued jobs failed with a \"system failure\" message during the incident, they can now be safely re-run. We appreciate your patience while we worked to restore service.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-04T16:21:44.669Z", "resolved_inferred": false, "started_at": "2026-08-04T14:45:30.862Z", @@ -166,7 +168,7 @@ "body": "The issue affecting related and popular search functionality and Pulse monitoring has been fully resolved. All systems are operational. We appreciate your patience during this incident.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-23T19:35:11.495Z", "resolved_inferred": false, "started_at": "2026-07-23T16:48:13.177Z", @@ -179,7 +181,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-23T19:38:51.379Z", "resolved_inferred": false, "started_at": "2026-07-23T16:12:54.046Z", @@ -192,7 +194,7 @@ "body": "We've resolved the issue affecting the availability of some sites. Contact Customer Support for help on Acquia DAM Community if you continue to experience any ongoing issues.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-22T01:21:56.231Z", "resolved_inferred": false, "started_at": "2026-07-21T23:08:40.700Z", @@ -205,7 +207,7 @@ "body": "The issue impacting Acquia Pipelines is now completely resolved. Git connectivity and pipeline processing have returned to normal operations, and we do not anticipate any further impact.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-21T12:37:49.198Z", "resolved_inferred": false, "started_at": "2026-07-21T11:39:26.101Z", @@ -218,7 +220,7 @@ "body": "The issue impacting CDN provisioning for Edge Standard has been fully resolved. New domain configurations are now processing successfully, and we have confirmed stability across the environment. No further impact is expected.\r\nWe apologise for any inconvenience caused and appreciate your patience while we worked through this.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-17T20:06:17.592Z", "resolved_inferred": false, "started_at": "2026-07-17T09:41:22.219Z", @@ -231,7 +233,7 @@ "body": "The underlying cause of this interruption has been addressed. All affected services have been restored. All services are operational at this time.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-22T21:54:48.409Z", "resolved_inferred": false, "started_at": "2026-06-22T14:59:09.557Z", @@ -244,7 +246,7 @@ "body": "The underlying cause of this interruption has been addressed. All affected services have been restored. All services are operational at this time.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-12T07:05:21.764Z", "resolved_inferred": false, "started_at": "2026-06-11T14:02:06.405Z", @@ -257,7 +259,7 @@ "body": "The login issues affecting Acquia Campaign Studio and Campaign Factory have been completely resolved, and all systems are fully operational.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-01T08:49:17.252Z", "resolved_inferred": false, "started_at": "2026-06-01T05:21:33.486Z", @@ -270,7 +272,7 @@ "body": "The issue with our upstream provider has been fully resolved, and all affected services have been restored to normal operations. Thank you for your patience while we worked to address this issue.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-09T13:54:11.219Z", "resolved_inferred": false, "started_at": "2026-05-08T00:16:50.607Z", @@ -283,7 +285,7 @@ "body": "We have resolved the issue causing degraded Portals performance for some customers. Contact Customer Support for help on Acquia DAM Community if you continue to experience any ongoing issues.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-06T00:33:29.781Z", "resolved_inferred": false, "started_at": "2026-05-05T19:43:22.102Z", @@ -296,7 +298,7 @@ "body": "We've detected a service interruption affecting the stability for your application. The issue was quickly identified and resolved. Everything is up and running now.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-01T22:11:24.014Z", "resolved_inferred": false, "started_at": "2026-05-01T22:11:23.964Z", @@ -309,7 +311,7 @@ "body": "We've detected a service interruption affecting the shared load balancers for certain customer applications. All services are operational at this time.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-30T22:54:41.000Z", "resolved_inferred": false, "started_at": "2026-04-30T22:54:40.973Z", @@ -322,7 +324,7 @@ "body": "The underlying cause of this issue has been addressed. All affected services have been restored. All services are operational at this time.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-30T00:30:51.717Z", "resolved_inferred": false, "started_at": "2026-04-29T15:33:33.213Z", @@ -335,7 +337,7 @@ "body": "The issue impacting code deployments for a subset of customers on our Cloud Platform has now been resolved. Our engineering team has implemented a fix and all code deployment functionalities are now restored.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-22T06:33:38.288Z", "resolved_inferred": false, "started_at": "2026-04-21T16:41:30.881Z", @@ -348,7 +350,7 @@ "body": "The issue impacting code deployments for a subset of customers on our Cloud Platform has now been resolved. Our engineering team has implemented a fix and all code deployment functionalities are now restored.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-21T10:01:53.889Z", "resolved_inferred": false, "started_at": "2026-04-21T04:08:30.038Z", @@ -361,7 +363,7 @@ "body": "The issue impacting Two-Factor Authentication (TFA) and preventing logins to the Acquia Cloud UI has been fully resolved, and all systems are now fully operational.\r\nIf you continue to experience any lingering issues, please reach out by filing a support ticket. Thank you for your patience during this interruption.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-20T07:12:30.830Z", "resolved_inferred": false, "started_at": "2026-04-20T05:39:45.365Z", @@ -374,7 +376,7 @@ "body": "Acquia has resolved the issue impacting code deployments for a subset of customers on our Cloud Platform. Users should no longer experience rejected git push commands, as full deployment functionality has been completely restored. We sincerely apologize for the inconvenience and appreciate your patience while we worked to fix this.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-17T20:22:32.552Z", "resolved_inferred": false, "started_at": "2026-04-17T17:32:37.000Z", @@ -387,7 +389,7 @@ "body": "Acquia has resolved the performance degradation affecting Log Streaming services on the Acquia Cloud Next platform. Log Streaming functionality has been fully restored, and customers should now see their logs streaming normally. We appreciate your patience and apologize for any inconvenience this may have caused.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-10T20:24:17.406Z", "resolved_inferred": false, "started_at": "2026-04-10T18:32:55.000Z", @@ -400,7 +402,7 @@ "body": "The issue impacting multiple sites has been resolved, and affected sites are now accessible.We will continue to review this incident internally. If you experience any further issues, please reach out via your existing support channels or respond to your open support ticket.Thank you for your patience.open support ticket.We will share further updates as more information becomes available.restore stability as quickly as possible.We will continue to provide updates as more information becomes available.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-10T04:49:52.589Z", "resolved_inferred": false, "started_at": "2026-04-10T02:05:23.515Z", @@ -413,7 +415,7 @@ "body": "We have completed processing the accumulated work. Contact Customer Support for help on Acquia DAM Community if you continue to experience any ongoing issues.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-09T20:47:53.730Z", "resolved_inferred": false, "started_at": "2026-04-09T13:12:50.041Z", @@ -426,7 +428,7 @@ "body": "The issue impacting accessibility across all Campaign Studio instances has been fully resolved. Our internal engineering team has implemented a fix, and all systems are now operating normally.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-25T15:50:04.027Z", "resolved_inferred": false, "started_at": "2026-03-25T13:55:14.654Z", @@ -439,7 +441,7 @@ "body": "The resource contention issue within our GCP US environment has been successfully resolved.\r\n\r\nOur engineering team has proactively rerun the majority of the stopped and failed input connectors and data refresh workflows. We are currently monitoring the final batch of these workflows to ensure they process completely and that all systems return to normal operation.\r\n\r\nThank you for your patience while our team worked to restore service.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-19T16:54:29.352Z", "resolved_inferred": false, "started_at": "2026-03-19T15:18:31.471Z", @@ -452,7 +454,7 @@ "body": "Acquia has successfully addressed the service interruption impacting a specific load balancer pair. Following a period of monitoring, all associated applications are confirmed to be stable and operating normally. Thank you for your patience and understanding while we worked to restore full service.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-14T12:05:01.673Z", "resolved_inferred": false, "started_at": "2026-03-13T01:04:10.797Z", @@ -465,7 +467,7 @@ "body": "Acquia has resolved the issue impacting the performance and accessibility of Acquia CDP in the AWS US region (hub2.agilone.com). Normal operations have been fully restored. We apologize for the inconvenience and appreciate your patience during this time.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-26T18:52:29.632Z", "resolved_inferred": false, "started_at": "2026-02-26T18:18:47.252Z", @@ -478,7 +480,7 @@ "body": "The underlying cause of this service interruption has been addressed. All affected services have been restored. All services are operational at this time.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-26T04:56:48.352Z", "resolved_inferred": false, "started_at": "2026-02-26T02:39:23.715Z", @@ -491,7 +493,7 @@ "body": "The issue affecting metrics reporting within the Cloud Platform user interface is resolved, and all systems are now operating normally. Connectivity with the backend metrics provider has been restored, with metrics ingestion working correctly and performance charts loading as expected in the Cloud UI. Throughout this incident, hosted applications and websites remained fully operational and were not affected.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-29T10:33:15.218Z", "resolved_inferred": false, "started_at": "2026-01-29T04:24:38.939Z", @@ -504,7 +506,7 @@ "body": "Acquia has resolved the recent service interruption affecting some Applications across Acquia Cloud Next & Acquia Source platforms. All services are now operating normally, and we are no longer observing any related issues. Thank you for your patience and understanding while we worked to restore full service.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-15T12:59:41.708Z", "resolved_inferred": false, "started_at": "2026-01-15T11:56:48.370Z", @@ -517,7 +519,7 @@ "body": "We've resolved the issue causing preview generation to be delayed for some customers. Contact Customer Support for help on Acquia DAM Community if you continue to experience any ongoing issues.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-22T17:12:11.813Z", "resolved_inferred": false, "started_at": "2025-12-19T20:55:47.867Z", @@ -530,7 +532,7 @@ "body": "Acquia has addressed the root cause of the interruption to Acquia Search services, restoring full functionality.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-17T21:12:50.600Z", "resolved_inferred": false, "started_at": "2025-12-17T15:07:42.833Z", @@ -543,7 +545,7 @@ "body": "Acquia has addressed the root cause of the interruption to Acquia Search services, restoring full functionality.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-16T23:14:04.762Z", "resolved_inferred": false, "started_at": "2025-12-16T18:26:54.000Z", @@ -556,7 +558,7 @@ "body": "Snowflake partial outage impacting Acquia Customer Data Platform (CDP) tenants hosted on AWS EU Prod has been fully resolved. All services are now operating normally, and we have observed stable performance since mitigation steps were completed at 15:59 UTC. No further issues have been detected, and all impacted processes have fully recovered.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-16T18:39:41.265Z", "resolved_inferred": false, "started_at": "2025-12-16T05:59:13.009Z", @@ -569,7 +571,7 @@ "body": "Earlier today, an outage affecting Cloudflare services (including their status page, dashboard, and API) caused temporary access issues for Acquia-hosted websites and related services. During the disruption, some users were unable to reach their sites.\r\n\r\nCloudflare has since resolved the issue, and normal service has been fully restored. We will continue to monitor for any further impact.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-05T09:25:09.275Z", "resolved_inferred": false, "started_at": "2025-12-05T09:25:09.232Z", @@ -582,7 +584,7 @@ "body": "We've resolved the issue causing increased error rates in the API (v2) and within DAM. Contact Customer Support for help on Acquia DAM Community if you continue to experience any ongoing issues.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-04T14:51:57.810Z", "resolved_inferred": false, "started_at": "2025-12-04T14:44:41.199Z", @@ -595,7 +597,7 @@ "body": "The underlying cause of the service interruption affecting the Acquia Site Studio API endpoints has been addressed. All impacted Acquia services have been restored, and all services are now fully operational.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-01T16:16:50.311Z", "resolved_inferred": false, "started_at": "2025-12-01T11:22:53.921Z", @@ -608,7 +610,7 @@ "body": "The underlying cause of this Acquia Source service interruption has been addressed. All affected Acquia Source services have been restored. All services are operational at this time.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-18T18:11:47.868Z", "resolved_inferred": false, "started_at": "2025-11-18T13:52:04.000Z", @@ -621,7 +623,7 @@ "body": "The underlying cause of this service interruption has been addressed. All affected Services offered by Acquia Edge powered by Cloudflare has been resolved, and according to our upstream partner, Cloudflare services are currently operating normally with no elevated errors or latency being observed across their network.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-18T18:07:31.979Z", "resolved_inferred": false, "started_at": "2025-11-18T12:11:19.528Z", @@ -634,7 +636,7 @@ "body": "The underlying cause of this service interruption has been addressed. All affected services have been restored and operational now.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-13T18:25:45.260Z", "resolved_inferred": false, "started_at": "2025-11-13T15:01:56.000Z", @@ -647,7 +649,7 @@ "body": "Update: The hotfix addressing the image editing issue for Acquia Source customers has been successfully released and tested.\r\nThe issue, which was introduced in version 2.19.0 as part of a canvas update, is now fully resolved.\r\nCustomers can now return to normal operations and no longer need to use the previously suggested workaround. Our team will continue to monitor the platform closely.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-30T08:36:30.732Z", "resolved_inferred": false, "started_at": "2025-10-28T12:06:26.000Z", diff --git a/api/v/actionstep.json b/api/v/actionstep.json index f7077e7aa1d4e8ea8197a5d6adb2678630b7f107..7b31384ad34232d05c15c925314f5b10b60fa6b2 100644 --- a/api/v/actionstep.json +++ b/api/v/actionstep.json @@ -3,7 +3,7 @@ "slug": "actionstep", "platform": "statuspage", "status_url": "https://status.actionstep.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "This issue has now been fixed, and our Engineering team has confirmed that the Actionstep Practice Management platform is now stable and fully operational again.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-28T16:18:51.487+12:00", "resolved_inferred": false, "started_at": "2026-08-28T12:17:47.187+12:00", @@ -25,7 +25,7 @@ "body": "The issues affecting the Actionstep Practice Management platform have now been resolved. Engineering team confirmed that the services are now fully functional.\n\nWe apologise for any inconvenience this may have caused.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-28T11:45:25.920+12:00", "resolved_inferred": false, "started_at": "2026-08-28T11:30:28.050+12:00", @@ -38,7 +38,7 @@ "body": "The issues affecting the Actionstep Practice Management platform have now been resolved, and our technical teams have confirmed that all services are now fully functional.\n\nWe would like to apologise for any inconvenience this may have caused.\n\nRegards,\nThe Actionstep Team", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-27T15:13:13.772+12:00", "resolved_inferred": false, "started_at": "2026-08-27T14:50:48.000+12:00", @@ -51,7 +51,7 @@ "body": "**Resolved** - Between 00:15\u201301:00 NZST, some Actionstep users were unable to log in to the website. The issue affected users on UK servers, particularly eu-west-1.actionstep.com.\n\nImpact: Login access only. No customer data was affected.\n\nCause: Currently investigating\n\nWorking Solution: Clearing cookies and cache or restarting your machine has shown to resolve the issue.\n\nFor further help, log a ticket at [https://support.actionstep.com](https://support.actionstep.com/)", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-11T01:11:30.000+12:00", "resolved_inferred": false, "started_at": "2026-08-11T00:00:41.000+12:00", @@ -64,7 +64,7 @@ "body": "Between 19:39\u201322:00 NZST, some Actionstep users were unable to log in to the website. The issue affected users on certain ISPs, particularly Virgin Media.\n\nImpact: Login access only. No customer data was affected or moved.\n\nCause: Likely network or routing changes on the affected ISPs impacting access to the Actionstep login page. Affected customers should contact their ISP to check for recent changes.\n\nData location clarification: No customer data is stored in AP Southeast 2. That region only serves the login page. Once you select your system tile, you're redirected to the data centre where your system actually resides (UK region for UK customers). Your data has not moved and remains stored in your designated region.\n\nWorkaround: If you're still affected, use a mobile hotspot to reach the login page and sign in, then switch back to your normal Wi-Fi once logged in.\n\nFor further help, log a ticket at https://support.actionstep.com", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-31T06:00:00.000+12:00", "resolved_inferred": false, "started_at": "2026-07-31T02:23:52.367+12:00", @@ -77,7 +77,7 @@ "body": "We are communicating to provide further information on the issues that affected the Actionstep Gmail Add-on platform which started the 1st of June, 2026 and confirm that the issue is now resolved.\n\nWhat happened:\nThe Gmail Add-on was running on the deprecated Google Apps Script Rhino runtime. Google ended support for the Rhino runtime, which caused the add-on to fail before any app logic could execute.\n\nWhat we did:\nOur team migrated the Apps Script project to the V8 runtime, created a new deployment version, and redeployed the Gmail Add-on. The add-on is now fully operational.\n\nWhat we're doing to prevent this:\nWe have reviewed our runtime dependencies to ensure we are not relying on deprecated infrastructure going forward.\n\nWe apologise for any disruption this caused and thank you for your patience.\n\nRegards,\nActionstep Support Team", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-04T12:31:20.408+12:00", "resolved_inferred": false, "started_at": "2026-06-03T13:38:49.308+12:00", @@ -90,7 +90,7 @@ "body": "The root cause of this issue has now been resolved. \n\nIf you are still experiencing performance degradation and seeing 500 errors, please reach out to support@actionstep.com.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-22T18:22:44.539+12:00", "resolved_inferred": false, "started_at": "2026-05-22T13:25:41.017+12:00", @@ -103,7 +103,7 @@ "body": "Xero has resolved the issue impacting customers. Xero is now stable and customers should be able to use the platform normally.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-11T12:50:04.094+12:00", "resolved_inferred": false, "started_at": "2026-05-11T11:53:46.504+12:00", @@ -116,7 +116,7 @@ "body": "We are communicating to provide further information on the outage that affected the Actionstep platform and confirm that the issue is now resolved.\n\nThis outage started from 9:15am NZT, and prevented user access to the system. Some customers who managed to log in experienced error messages and periods of instability and slowness.\n\nIt is important to confirm that no data was lost, and the issue related to access to platform only.\n\nOur team investigated the issue as the sole priority and released an urgent fix at 9:51am NZT which restored platform access and brought system performance back to normal levels.\n\nThe Actionstep team appreciate the impact that this outage may have had on your business, and we want to reiterate our commitment to improving the experience of all customers who use the platform.\n\nWe have identified the root cause of the issue and implemented steps to prevent it from occurring again in future.\n\nRegards,\nActionstep Support Team", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-17T10:00:26.541+13:00", "resolved_inferred": false, "started_at": "2026-03-17T09:42:40.000+13:00", @@ -129,7 +129,7 @@ "body": "This incident has been resolved. Staging systems are now accessible and back online.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-11T21:04:01.000+13:00", "resolved_inferred": false, "started_at": "2026-03-11T18:07:52.558+13:00", @@ -142,7 +142,7 @@ "body": "We are pleased to report that Microsoft have resolved the issues that were impacting users who rely on Microsoft Authenticator for multi-factor authentication (MFA) when signing in to Actionstep Practice Management and Legal Accounting.\n\nThank you for your patience during this Microsoft service outage.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-23T19:41:30.875+13:00", "resolved_inferred": false, "started_at": "2026-01-23T09:26:14.000+13:00", @@ -155,7 +155,7 @@ "body": "**Post-Incident Summary:** United Kingdom \u2013 External Connectivity Issue \u2013 December 4, 2025\n\n**Incident Overview** \nOn December 4, 2025, some customers in the United Kingdom \u2013 primarily those using Sky Broadband \u2013 experienced difficulty accessing the Actionstep login page. This login page \\(also known as the Launchpad\\) is hosted in the ap-southeast-2 region; however, no customer data for UK systems is stored or processed in this region. Once a user selects their system, they are directed to the appropriate UK/region-specific server where their data resides.\n\nOur investigation confirmed that this incident was caused entirely by a Sky ISP routing/connectivity issue preventing requests from reaching a wide variety of services hosted in ap-southeast-2. Actionstep also contacted AWS, who confirmed we were one of hundreds of services affected by the Sky outage. There was no issue with the Actionstep platform, AWS infrastructure, or our regional hosting.\n\nThe issue began at approximately 2:30 pm GMT on December 4, 2025, and normal access was fully restored by December 9, 2025\n\n**Impact** \nCustomers in the UK using Sky Broadband were intermittently or completely unable to reach the Actionstep login page due to Sky\u2019s network routing issue.\n\nCustomers using other ISPs, or those switching to an alternative connection such as mobile data, were able to access Actionstep normally.\n\nAt all times, the Actionstep platform itself remained operational.\n\n**Resolution** \nOnce Sky resolved their connectivity issue, normal access to the Actionstep login page was restored.\n\nThroughout the incident, Actionstep systems continued to perform normally, and users connecting from unaffected networks experienced no disruption.\n\n**Next Steps** \nNo Actionstep changes are required, as the root cause was external to our systems and infrastructure.\n\nIf customers encounter similar symptoms in the future, we recommend testing an alternative connection \\(such as a mobile hotspot\\) and contacting their ISP to confirm whether a localised network issue is occurring.\n\n**Acknowledgement** \nWe recognise that this caused inconvenience for affected customers and appreciate everyone\u2019s patience while Sky resolved their network routing issue. Ensuring reliable access to Actionstep remains our priority.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-06T04:43:53.000+13:00", "resolved_inferred": false, "started_at": "2025-12-05T03:30:01.000+13:00", @@ -168,7 +168,7 @@ "body": "We are communicating to provide further information on the outage that affected the Actionstep system on 11/11/2025 and confirm that the issue is now resolved.\n\nThis outage started at 8:30 am EST and prevented user access to the system. Some customers who managed to log in experienced error messages and periods of instability and slowness.\n\nIt is important to confirm that no data was lost, and the issue is related to platform performance only.\n\nOur team investigated the issue as the sole priority and released an urgent fix at 11:20 am EST, which restored platform access and brought system performance back to normal levels.\n\nThe Actionstep team appreciates the impact that this outage may have had on your business, and we want to reiterate our commitment to improving the experience of all customers who use the platform.\n\nWe have identified the root cause of the issue and implemented steps to prevent it from occurring again in the future.\n\nRegards,\nActionstep Support Team", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-12T05:30:49.414+13:00", "resolved_inferred": false, "started_at": "2025-11-12T05:20:18.064+13:00", @@ -181,7 +181,7 @@ "body": "**Post-Incident Summary: US \u2013 Actionstep Payments Outage \u2013 October 17, 2024**\n\n### Incident Overview\n\nOn October 17, 2024, Actionstep experienced a service outage affecting the Actionstep Payments platform in the US. A configuration update inadvertently restricted access to a required system resource, which caused payment processing and related services to become temporarily unavailable.\n\n### Impact\n\nUS-based customers were unable to process payments or access related payment features for approximately one hour.\n\n### Resolution\n\nThe engineering team identified the configuration issue, restored access to the affected resource, and confirmed that all payment services were operating normally. Service was fully restored once functionality was verified across multiple customer accounts.\n\n### Next Steps\n\nWe are strengthening our change control and rollout processes to ensure configuration updates are thoroughly tested and deployed safely, with improved monitoring and communication to detect and address issues more quickly.\n\n### Acknowledgement\n\nWe sincerely apologize for the disruption this caused to our US customers. Maintaining reliable and uninterrupted access to Actionstep Payments remains a priority.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-07T05:22:39.661+13:00", "resolved_inferred": false, "started_at": "2025-11-07T04:58:03.012+13:00", @@ -194,7 +194,7 @@ "body": "**Post-Incident Summary: EU-West-1 \\(UK\\) \u2013 System Outage \u2013 October 17, 2024**\n\n### Incident Overview\n\nOn October 17, 2024, Actionstep experienced a service outage affecting customers in the UK region \\(EU-West-1\\). A configuration update inadvertently restricted access to a required system resource, which caused login failures and prevented users from accessing the platform.\n\n### Impact\n\nAll UK-based customers were unable to log in or use Actionstep for about one hour. Internal testing environments in the same region were also affected.\n\n### Resolution\n\nThe engineering team identified the configuration issue, restored access to the affected resource, and confirmed that all systems were operating normally. Service was fully restored once access was verified across multiple customer accounts.\n\n### Next Steps\n\nWe are improving our change control and rollout processes to ensure configuration updates are tested and deployed safely, with enhanced communication and monitoring to detect issues earlier.\n\n### Acknowledgement\n\nWe sincerely apologize for the disruption this caused to our UK customers. Ensuring consistent access and reliability remains our highest priority.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-06T22:26:52.620+13:00", "resolved_inferred": false, "started_at": "2025-11-06T21:45:55.000+13:00", @@ -207,7 +207,7 @@ "body": "**Post-Incident Summary:** Microsoft Dependency Disruption \u2013 Global \u2013 October 29, 2025 \n\n**Incident Overview** \nOn October 29, 2025, a widespread outage affecting Microsoft\u2019s Azure Front Door service caused latency, timeouts, and service errors across Microsoft 365 and Azure platforms. This impacted Actionstep features that rely on Microsoft services. \n\n**Impact** \nDuring the incident, some users experienced difficulty accessing Microsoft-related functionality, including the Outlook Add-in, OneDrive integrations, and Office 365 email services. Service availability improved as Microsoft began recovery efforts, though intermittent issues persisted for some users. \n\n**Resolution** \nMicrosoft reloaded configurations and rebalanced traffic across its network to restore full operational capacity. As of 23:20\u202fUTC, Microsoft reported significant progress, and Actionstep services dependent on Microsoft systems have largely returned to normal operation. \n\n**Next Steps** \nActionstep will continue monitoring Microsoft\u2019s recovery and ensure all integrations remain stable. We are also reviewing dependency monitoring to improve early detection of third-party disruptions. \n\n**Acknowledgement** \nWe appreciate your patience during this incident and apologize for the inconvenience. Ensuring reliable access to all integrated services remains a top priority for Actionstep.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-30T11:55:00.221+13:00", "resolved_inferred": false, "started_at": "2025-10-30T05:50:29.191+13:00", @@ -220,7 +220,7 @@ "body": "On November 6, 2025, Actionstep\u2019s main website \\([actionstep.com](http://actionstep.com)\\) became temporarily unavailable during a scheduled maintenance activity. The maintenance affected only the public website and did not impact access to the Actionstep application.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-22T12:40:39.116+13:00", "resolved_inferred": false, "started_at": "2025-10-22T12:05:55.203+13:00", @@ -233,7 +233,7 @@ "body": "**Post-Incident Summary: North America \\(US-East-1\\) \u2013 AWS Outage Impact \u2013 October 20, 2025**\n\n**Incident Overview** \nOn October 20, 2025, Actionstep services in the US-East-1 region were affected by a widespread outage within Amazon Web Services \\(AWS\\). This incident originated from AWS infrastructure and impacted many cloud-based platforms globally, not just Actionstep. As a result, customers experienced degraded performance and intermittent downtime across the Practice Management and Legal Accounting platforms.\n\n**Impact** \nThe outage occurred between approximately **9:39 a.m. and 2:19 p.m. MDT**. During this period, some customers in North America experienced slow performance, timeouts, and temporary unavailability of certain features. The issue was entirely due to an AWS infrastructure failure and was not caused by Actionstep systems or changes.\n\n**Resolution** \nAWS restored functionality in the affected region, after which Actionstep systems automatically recovered. Our engineering team closely monitored the recovery process and validated all environments to confirm full stability and normal operation. \n \nFor more information about this outage, please see the AWS website: [Service health - Oct 20, 2025 | AWS Health Dashboard | Global](https://health.aws.amazon.com/health/status)\n\n**Next Steps** \nWe are reviewing our communication and monitoring processes to ensure faster updates and improved transparency during third-party service disruptions. We are also exploring additional resilience measures to minimize the impact of future upstream provider outages.\n\n**Acknowledgement** \nWe understand the disruption this caused and apologize for the impact on your firm\u2019s operations. While this incident originated outside of Actionstep\u2019s control, we remain committed to maintaining system reliability and ensuring clear, timely communication during any service interruption.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-21T09:19:47.950+13:00", "resolved_inferred": false, "started_at": "2025-10-21T04:39:35.092+13:00", @@ -246,7 +246,7 @@ "body": "**Post-Incident Summary: Global \u2013 Third-Party Communication Outage \u2013 October 20, 2025**\n\n**Incident Overview** \nOn October 20, 2025, a widespread AWS outage in the US-East-1 region affected several third-party platforms, including Freshdesk and Intercom. As a result, Actionstep\u2019s Support and Accounting teams were unable to send or receive tickets, live chats, or email communications during the disruption.\n\n**Impact** \nThe issue occurred between approximately **9:38 a.m. and 10:04 a.m. MDT**. During this time, customers were unable to contact Actionstep Support or Accounting through normal channels. The outage originated from AWS infrastructure supporting Freshdesk and Intercom and did not involve any Actionstep systems.\n\n**Resolution** \nFreshdesk restored services once AWS resolved the underlying issue. Actionstep teams verified full functionality and resumed normal support operations immediately after recovery.\n\n**Next Steps** \nWe are reviewing backup communication options and evaluating redundancy for critical customer communication tools to ensure we can continue providing updates and assistance during future third-party outages.\n\n**Acknowledgement** \nWe understand the inconvenience this caused and apologize for the disruption to your ability to reach our teams. Maintaining reliable communication and support availability is a top priority, and we are taking steps to strengthen our resilience against external service interruptions.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-21T05:04:30.222+13:00", "resolved_inferred": false, "started_at": "2025-10-21T04:38:40.000+13:00", @@ -259,7 +259,7 @@ "body": "### **Post-Incident Summary: Staging Environment Outage \u2013 October 13, 2025**\n\n**Incident Overview** \nOn October 13, 2025, Actionstep\u2019s Staging environment experienced a temporary service interruption following a system update that affected how application services processed requests.\n\n**Impact** \nBetween 11:29 \u2013 12:20 UTC and again 22:16 \u2013 22:33 UTC, users accessing the Staging environment encountered errors and were unable to complete normal testing or pre-release activities.\n\n**Resolution** \nThe engineering team identified the update as the cause and restored service by rolling back to a stable configuration. Functionality was verified and all systems in Staging returned to normal operation.\n\n**Next Steps** \nWe are refining our deployment and testing procedures to ensure updates to non-production environments are validated without impacting users. Additional automated checks and pre-deployment reviews will be implemented.\n\n**Acknowledgement** \nWe apologize for the disruption this caused. Maintaining reliable and predictable environments for testing and validation remains a key priority.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-14T11:50:28.279+13:00", "resolved_inferred": false, "started_at": "2025-10-14T11:40:07.452+13:00", @@ -272,7 +272,7 @@ "body": "### **Post-Incident Summary: Production Environment Outage \u2013 October 13, 2025**\n\n**Incident Overview** \nOn October 13, 2025, Actionstep experienced two brief service interruptions in the Production environment caused by a system update that affected how application services processed requests.\n\n**Impact** \nCustomers across all regions experienced temporary unavailability between 11:29 \u2013 12:20 UTC and 22:16 \u2013 22:33 UTC. During these times, users were unable to access or perform actions within the platform.\n\n**Resolution** \nThe engineering team identified the cause and restored service by rolling back the recent update to a stable version. The corrected configuration was rebuilt, tested, and redeployed to confirm full restoration of normal operations.\n\n**Next Steps** \nWe are enhancing our testing and deployment processes to prevent similar issues. This includes improved validation of system updates, additional automated testing before release, and refined monitoring to detect issues earlier.\n\n**Acknowledgement** \nWe sincerely apologize for the disruption and appreciate your patience. Maintaining a stable and reliable platform remains our highest priority.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-14T01:27:32.210+13:00", "resolved_inferred": false, "started_at": "2025-10-14T00:33:09.000+13:00", @@ -285,7 +285,7 @@ "body": "We are communicating to provide further information on the issue affecting Reports, document generation, email assignment, and invoice finalization on the eu-west-1 platform on October 3, 2025, and confirm that the issue is now resolved.\n\nThis issue impacted the ability to run reports, finalize invoices, and assign emails via Gmail/Outlook add-ins from 09:00 BST to 10:15 BST, and resulted in tasks being stuck in processing without completion.\n\nIt is important to confirm that no data was lost, and the issue is related to platform performance only.\nOur team investigated the issue as the sole priority during the day and released an urgent fix at 10:15 BST, which restored all functionality to normal operations.\n\nThe Actionstep team appreciates the impact that this issue may have had on your business, and we want to reiterate our commitment to improving the experience of all customers who use the platform.\n\nWe have identified the root cause of the issue and implemented steps to prevent it from occurring again in the future.\n\nRegards,\nActionstep Support Team", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-03T22:22:24.069+13:00", "resolved_inferred": false, "started_at": "2025-10-03T21:26:18.672+13:00", @@ -298,7 +298,7 @@ "body": "**Post-Incident Summary: North America Feature Outage \u2013 September 19, 2025**\n\n**Incident Overview** \nOn September 19, 2025, Actionstep experienced an outage affecting several features in North America, including document, contact, and custom data management, as well as integrations such as Outlook, Word, and Zapier. Customers encountered 403 error messages during this time.\n\n**Impact** \nThe issue occurred between 11:45 a.m. MDT and 1:00 p.m. MDT. During this period, customers in North America were unable to reliably use the affected features.\n\n**Resolution** \nOur engineering team identified the root cause and worked with our partners to remediate the issue. Full functionality was restored by 1:00 p.m. MDT.\n\n**Next Steps** \nWe are implementing additional safeguards in our change management and quality assurance processes to ensure this type of disruption does not occur again.\n\n**Acknowledgement** \nWe understand the disruption this caused and apologize for the impact on your firm\u2019s operations. Maintaining system stability and reliability is our top priority, and we are taking steps to strengthen our controls and prevent recurrence.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-20T07:24:42.549+12:00", "resolved_inferred": false, "started_at": "2025-09-20T05:45:51.000+12:00", @@ -311,7 +311,7 @@ "body": "We are providing additional information about the issue affecting Actionstep Practice Management on August 15, 2025, and confirming that the problem has now been resolved.\n\nThe issues began at 11:51AM MDT and were resolved by 12:10PM MDT.\n\nIt is important to confirm that no data was lost and that the issue was related solely to platform performance.\n\nOur team prioritized investigating the problem and restored functionality to normal operations.\n\nThe Actionstep team understands the impact this issue may have had on your business, and we want to reaffirm our commitment to enhancing the experience for all customers using the platform.\n\nRegards,\nActionstep Support Team", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-16T06:16:12.650+12:00", "resolved_inferred": false, "started_at": "2025-08-16T06:03:01.926+12:00", @@ -324,7 +324,7 @@ "body": "We recently experienced a service interruption on our eu-west-1 server on the 5th of August 2025 that caused degraded performance for some customers. The issue was related to unusually high levels of API activity on one of our servers, which impacted system stability.\n\nWe isolated the source of the high traffic and moved it to a separate environment to restore performance. We are also reviewing our current rate-limiting and monitoring systems to help prevent similar issues in the future.\n\nWe apologise for any inconvenience this caused and thank you for your understanding as we continue to improve the reliability of our service.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-06T03:21:48.821+12:00", "resolved_inferred": false, "started_at": "2025-08-06T02:15:26.000+12:00", diff --git a/api/v/activecampaign.json b/api/v/activecampaign.json index be87c382f66439942cf2199c872ab5b68e98c1bc..11b919d47285f5380d91105d1bf86379a6e96487 100644 --- a/api/v/activecampaign.json +++ b/api/v/activecampaign.json @@ -3,7 +3,7 @@ "slug": "activecampaign", "platform": "statuspage", "status_url": "https://status.activecampaign.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-28T14:16:25.097-05:00", "resolved_inferred": false, "started_at": "2026-08-28T13:48:25.278-05:00", @@ -25,7 +25,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-10T11:59:28.519-05:00", "resolved_inferred": false, "started_at": "2026-08-10T09:14:44.666-05:00", @@ -38,7 +38,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-06T06:40:41.073-05:00", "resolved_inferred": false, "started_at": "2026-08-05T05:59:01.092-05:00", @@ -51,7 +51,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-03T16:24:16.195-05:00", "resolved_inferred": false, "started_at": "2026-08-03T14:34:10.486-05:00", @@ -64,7 +64,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-30T18:16:42.747-05:00", "resolved_inferred": false, "started_at": "2026-07-30T17:23:12.776-05:00", @@ -77,7 +77,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-27T16:15:08.095-05:00", "resolved_inferred": false, "started_at": "2026-07-27T14:53:03.779-05:00", @@ -90,7 +90,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-15T11:02:37.487-05:00", "resolved_inferred": false, "started_at": "2026-07-10T01:57:43.982-05:00", @@ -103,7 +103,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-09T21:01:51.711-05:00", "resolved_inferred": false, "started_at": "2026-07-09T19:49:18.228-05:00", @@ -116,7 +116,7 @@ "body": "Engineers have implemented a fix. all regions are now fully operational again.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-26T18:09:12.753-05:00", "resolved_inferred": false, "started_at": "2026-06-26T17:38:13.000-05:00", @@ -129,7 +129,7 @@ "body": "We believe this issue is resolved at this time. If customers are continuing to experience issues loading the pages in question, they should contact support.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-23T08:52:54.356-05:00", "resolved_inferred": false, "started_at": "2026-06-18T18:19:46.000-05:00", @@ -142,7 +142,7 @@ "body": "This incident was resolved about 1:29pm CT. No further impact has been observed.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-01T16:29:10.424-05:00", "resolved_inferred": false, "started_at": "2026-06-01T09:07:18.187-05:00", @@ -155,7 +155,7 @@ "body": "Engineers have successfully deployed the fix across all systems. Testing confirms that the option to edit advanced searches and segmentations within the Contacts section is now fully restored and operating normally.\n\nThis incident is now resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-19T06:44:16.503-05:00", "resolved_inferred": false, "started_at": "2026-05-19T04:15:53.539-05:00", @@ -168,7 +168,7 @@ "body": "Engineers have released a fix to address the issues impacting the platform. Normal service has been restored for all impacted users.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-28T11:24:23.776-05:00", "resolved_inferred": false, "started_at": "2026-04-28T06:04:28.000-05:00", @@ -181,7 +181,7 @@ "body": "this incident is now resolved. customers should see their automations load.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-13T16:12:00.176-05:00", "resolved_inferred": false, "started_at": "2026-04-13T15:07:11.966-05:00", @@ -194,7 +194,7 @@ "body": "Campaign delays in the EU region have been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-26T20:01:16.468-05:00", "resolved_inferred": false, "started_at": "2026-03-26T12:57:51.080-05:00", @@ -207,7 +207,7 @@ "body": "Engineers have verified the fix in our production environment", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-26T10:29:57.094-05:00", "resolved_inferred": false, "started_at": "2026-03-26T06:56:23.115-05:00", @@ -220,7 +220,7 @@ "body": "The issues affecting service connectivity have been resolved. Following a coordinated effort with our infrastructure partners, all systems are now fully operational and performing as expected", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-05T17:28:06.984-06:00", "resolved_inferred": false, "started_at": "2026-03-05T16:43:50.786-06:00", @@ -233,7 +233,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-18T15:55:24.457-06:00", "resolved_inferred": false, "started_at": "2026-02-18T15:00:09.165-06:00", @@ -246,7 +246,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-16T09:29:28.966-06:00", "resolved_inferred": false, "started_at": "2026-02-13T13:02:25.000-06:00", @@ -259,7 +259,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-17T04:47:50.603-06:00", "resolved_inferred": false, "started_at": "2026-02-10T10:40:31.000-06:00", @@ -272,7 +272,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-30T12:10:15.052-06:00", "resolved_inferred": false, "started_at": "2026-01-30T11:48:53.651-06:00", @@ -285,7 +285,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-09T19:01:39.918-06:00", "resolved_inferred": false, "started_at": "2026-01-09T09:59:17.518-06:00", @@ -298,7 +298,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-04T18:51:44.041-06:00", "resolved_inferred": false, "started_at": "2026-01-04T18:19:28.325-06:00", @@ -311,7 +311,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-27T11:28:21.597-06:00", "resolved_inferred": false, "started_at": "2025-12-27T11:00:19.306-06:00", @@ -324,7 +324,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-14T18:56:05.136-06:00", "resolved_inferred": false, "started_at": "2025-12-13T09:42:15.663-06:00", @@ -337,7 +337,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-13T09:39:02.230-06:00", "resolved_inferred": false, "started_at": "2025-12-11T12:59:46.690-06:00", @@ -350,7 +350,7 @@ "body": "All landing pages are loading as expected.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-20T12:06:05.916-06:00", "resolved_inferred": false, "started_at": "2025-11-20T11:28:30.486-06:00", @@ -363,7 +363,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-17T14:24:07.765-06:00", "resolved_inferred": false, "started_at": "2025-11-17T13:54:53.181-06:00", @@ -376,7 +376,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-06T17:50:01.130-06:00", "resolved_inferred": false, "started_at": "2025-11-06T14:47:12.449-06:00", @@ -389,7 +389,7 @@ "body": "Engineering and support has confirmed that the issue is resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-05T07:24:18.453-06:00", "resolved_inferred": false, "started_at": "2025-11-05T04:59:28.578-06:00", @@ -402,7 +402,7 @@ "body": "All services should be functioning normally at this time.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-04T12:04:53.447-06:00", "resolved_inferred": false, "started_at": "2025-11-04T10:41:50.039-06:00", @@ -415,7 +415,7 @@ "body": "Engineers have identified the cause of the login verification email issue and have implemented a solution.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-27T22:39:26.576-05:00", "resolved_inferred": false, "started_at": "2025-10-27T21:56:24.625-05:00", @@ -428,7 +428,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-21T06:38:43.168-05:00", "resolved_inferred": false, "started_at": "2025-10-20T04:52:00.774-05:00", @@ -441,7 +441,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-12T14:44:59.938-05:00", "resolved_inferred": false, "started_at": "2025-09-12T13:09:15.996-05:00", @@ -454,7 +454,7 @@ "body": "The issue has been addressed and there should be no further delays in automations and/or email campaign sending.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-09T17:58:34.850-05:00", "resolved_inferred": false, "started_at": "2025-09-09T17:15:11.942-05:00", @@ -467,7 +467,7 @@ "body": "Our monitoring shows all systems operating normally. The issue has been fully resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-05T12:56:35.263-05:00", "resolved_inferred": false, "started_at": "2025-09-05T11:21:22.594-05:00", @@ -480,7 +480,7 @@ "body": "This incident has been resolved", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-03T20:49:24.458-05:00", "resolved_inferred": false, "started_at": "2025-09-03T19:28:55.794-05:00", @@ -493,7 +493,7 @@ "body": "Engineers have resolved the issue and service to connected emails has been restored.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-12T04:45:27.663-05:00", "resolved_inferred": false, "started_at": "2025-08-12T04:29:48.000-05:00", @@ -506,7 +506,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-04T17:49:37.903-05:00", "resolved_inferred": false, "started_at": "2025-08-04T15:30:01.637-05:00", diff --git a/api/v/ada.json b/api/v/ada.json index 503cf6566f0f1710edd339daf5338c870ec06905..23e63d819c71c6816f91a3affe4a0bea799c0b91 100644 --- a/api/v/ada.json +++ b/api/v/ada.json @@ -3,7 +3,7 @@ "slug": "ada", "platform": "statuspage", "status_url": "https://status.ada.support", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-09-01T14:05:01.353-04:00", "resolved_inferred": false, "started_at": "2026-09-01T12:37:40.797-04:00", @@ -25,7 +25,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-27T11:39:56.280-04:00", "resolved_inferred": false, "started_at": "2026-08-27T10:49:19.000-04:00", @@ -38,7 +38,7 @@ "body": "Query performance in US2 has returned to normal baseline levels and all affected endpoints. Conversation View, transcripts, conversation search, and analytics dashboards are responding at expected speeds.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-25T16:35:47.632-04:00", "resolved_inferred": false, "started_at": "2026-08-25T16:24:50.282-04:00", @@ -51,7 +51,7 @@ "body": "This incident has been resolved. Timing for conversations appearing in the conversations view has returned to normal. Thank you for your patience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-24T12:23:28.018-04:00", "resolved_inferred": false, "started_at": "2026-08-24T11:12:48.515-04:00", @@ -64,7 +64,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-21T11:09:25.710-04:00", "resolved_inferred": false, "started_at": "2026-08-21T09:11:54.778-04:00", @@ -77,7 +77,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-11T10:25:24.029-04:00", "resolved_inferred": false, "started_at": "2026-08-11T09:22:59.181-04:00", @@ -90,7 +90,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-24T15:32:11.423-04:00", "resolved_inferred": false, "started_at": "2026-07-24T06:41:35.187-04:00", @@ -103,7 +103,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-21T11:41:34.074-04:00", "resolved_inferred": false, "started_at": "2026-07-21T10:29:11.672-04:00", @@ -116,7 +116,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-16T21:48:01.885-04:00", "resolved_inferred": false, "started_at": "2026-07-16T20:48:39.897-04:00", @@ -129,7 +129,7 @@ "body": "WorkOS fix is now effective, and we have stopped monitoring the issue.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-16T07:49:39.924-04:00", "resolved_inferred": false, "started_at": "2026-07-16T06:41:35.964-04:00", @@ -142,7 +142,7 @@ "body": "A fix has been deployed, and queued Zendesk Emails are being sent out now.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-14T09:51:42.512-04:00", "resolved_inferred": false, "started_at": "2026-07-14T09:31:45.953-04:00", @@ -155,7 +155,7 @@ "body": "The team was able to identify the root cause and a fix is in place.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-13T15:56:31.244-04:00", "resolved_inferred": false, "started_at": "2026-07-12T07:45:13.809-04:00", @@ -168,7 +168,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-10T15:12:50.051-04:00", "resolved_inferred": false, "started_at": "2026-07-10T12:46:48.261-04:00", @@ -181,7 +181,7 @@ "body": "The incident have been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-09T00:55:10.471-04:00", "resolved_inferred": false, "started_at": "2026-07-09T00:44:49.553-04:00", @@ -194,7 +194,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-07T10:28:05.712-04:00", "resolved_inferred": false, "started_at": "2026-07-07T07:54:58.552-04:00", @@ -207,7 +207,7 @@ "body": "Identified and resolved an issue affecting some internal background data processing. Our team corrected it and confirmed all systems have returned to normal operation.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-06T18:38:43.759-04:00", "resolved_inferred": false, "started_at": "2026-07-06T17:33:00.000-04:00", @@ -220,7 +220,7 @@ "body": "The incident has been resolved", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-26T18:15:53.709-04:00", "resolved_inferred": false, "started_at": "2026-05-26T16:58:29.586-04:00", @@ -233,7 +233,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-25T12:04:16.138-04:00", "resolved_inferred": false, "started_at": "2026-05-25T10:28:50.696-04:00", @@ -246,7 +246,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-21T20:22:51.674-04:00", "resolved_inferred": false, "started_at": "2026-05-21T18:28:09.942-04:00", @@ -259,7 +259,7 @@ "body": "The certificate rotation issue has been fully resolved. Error rates have returned to normal levels and services are operating as expected. No further impact is anticipated", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-11T10:49:49.000-04:00", "resolved_inferred": false, "started_at": "2026-05-10T15:55:10.212-04:00", @@ -272,7 +272,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-05T17:50:48.014-04:00", "resolved_inferred": false, "started_at": "2026-05-05T17:01:49.250-04:00", @@ -285,7 +285,7 @@ "body": "Based on our Engineering Team's investigation, we have determined the scope of this issue is limited to a very small number of clients and affected conversations. We are continuing to work on the issue, but moving forward will be communicating on this issue on an individual basis.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-01T14:37:07.094-04:00", "resolved_inferred": false, "started_at": "2026-05-01T12:32:47.211-04:00", @@ -298,7 +298,7 @@ "body": "We have resolved an issue that caused an increase in emergency handoffs for a subset of customers.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-28T16:30:42.903-04:00", "resolved_inferred": false, "started_at": "2026-04-28T15:57:32.000-04:00", @@ -311,7 +311,7 @@ "body": "We have identified the root cause of the language detection issue affecting non-English responses. Improvements are actively in progress and will be delivered as part of our ongoing engineering work.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-24T13:00:38.433-04:00", "resolved_inferred": false, "started_at": "2026-04-24T11:06:03.532-04:00", @@ -324,7 +324,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-09T18:39:52.778-04:00", "resolved_inferred": false, "started_at": "2026-04-09T18:12:04.000-04:00", @@ -337,7 +337,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-07T15:35:36.933-04:00", "resolved_inferred": false, "started_at": "2026-04-07T11:37:19.445-04:00", @@ -350,7 +350,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-07T18:07:04.000-04:00", "resolved_inferred": false, "started_at": "2026-04-07T11:27:14.000-04:00", @@ -363,7 +363,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-06T21:10:08.968-04:00", "resolved_inferred": false, "started_at": "2026-04-06T19:37:38.348-04:00", @@ -376,7 +376,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-03T13:53:32.449-04:00", "resolved_inferred": false, "started_at": "2026-04-03T12:38:45.037-04:00", @@ -389,7 +389,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-03T14:40:48.735-04:00", "resolved_inferred": false, "started_at": "2026-04-03T12:32:00.864-04:00", @@ -402,7 +402,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-01T10:01:44.660-04:00", "resolved_inferred": false, "started_at": "2026-04-01T09:13:35.470-04:00", @@ -415,7 +415,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-25T16:42:03.244-04:00", "resolved_inferred": false, "started_at": "2026-03-25T13:46:45.694-04:00", @@ -428,7 +428,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-24T17:02:18.394-04:00", "resolved_inferred": false, "started_at": "2026-03-24T11:29:33.852-04:00", @@ -441,7 +441,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-05T19:03:10.249-05:00", "resolved_inferred": false, "started_at": "2026-03-05T18:51:44.922-05:00", @@ -454,7 +454,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-08T17:04:05.545-05:00", "resolved_inferred": false, "started_at": "2026-02-08T12:16:11.479-05:00", @@ -467,7 +467,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-05T15:30:20.766-05:00", "resolved_inferred": false, "started_at": "2026-02-05T11:50:57.264-05:00", @@ -480,7 +480,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-03T10:34:52.065-05:00", "resolved_inferred": false, "started_at": "2026-02-02T16:33:52.000-05:00", @@ -493,7 +493,7 @@ "body": "The issue impacting Salesforce Messaging integration performance has been resolved. Chats should now connect to agents as expected. We will continue to monitor to ensure ongoing stability.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-31T14:24:04.232-05:00", "resolved_inferred": false, "started_at": "2026-01-31T13:45:56.542-05:00", @@ -506,7 +506,7 @@ "body": "Analytics availability has been restored following an upstream provider outage. Clients may notice minor discrepancies in analytics data from approximately 4:00\u20136:00 AM ET, which will be automatically backfilled later today. We will continue to monitor to ensure everything remains stable.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-31T07:10:05.942-05:00", "resolved_inferred": false, "started_at": "2026-01-31T05:00:44.587-05:00", @@ -519,7 +519,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-22T14:54:46.016-05:00", "resolved_inferred": false, "started_at": "2026-01-22T14:03:47.869-05:00", @@ -532,7 +532,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-19T21:11:59.571-05:00", "resolved_inferred": false, "started_at": "2026-01-19T20:01:34.444-05:00", @@ -545,7 +545,7 @@ "body": "This incident has been resolved", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-07T11:30:30.794-05:00", "resolved_inferred": false, "started_at": "2026-01-07T11:20:42.543-05:00", @@ -558,7 +558,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-05T20:25:26.062-05:00", "resolved_inferred": false, "started_at": "2026-01-05T16:01:32.520-05:00", @@ -571,7 +571,7 @@ "body": "The issue with the Ada Dashboard has been resolved and Dashboard users should see things functioning normally again.\nOur team will continue to monitor the fix. We\u2019re sorry for the impact of this issue and appreciate your understanding.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-15T19:50:29.409-05:00", "resolved_inferred": false, "started_at": "2025-12-15T17:48:22.285-05:00", @@ -584,7 +584,7 @@ "body": "The issue with a delay in the knowledge articles updating has been resolved and regular update cadence has been re-instated. Our team will continue to monitor the fix. We\u2019re sorry for the impact of this issue and appreciate your understanding.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-10T19:22:30.431-05:00", "resolved_inferred": false, "started_at": "2025-12-10T16:15:08.802-05:00", @@ -597,7 +597,7 @@ "body": "The issue with Ada Voice has been resolved and chatters should see things functioning normally again.\nOur team will continue to monitor the fix. We\u2019re sorry for the impact of this issue and appreciate your understanding.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-10T16:06:34.404-05:00", "resolved_inferred": false, "started_at": "2025-12-10T15:22:18.909-05:00", @@ -610,7 +610,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-10T01:05:01.286-05:00", "resolved_inferred": false, "started_at": "2025-12-10T00:19:52.197-05:00", @@ -623,7 +623,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-08T20:33:19.575-05:00", "resolved_inferred": false, "started_at": "2025-12-08T19:20:21.899-05:00", @@ -636,7 +636,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-01T23:17:03.587-05:00", "resolved_inferred": false, "started_at": "2025-12-01T11:59:52.508-05:00", @@ -649,7 +649,7 @@ "body": "The incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-21T05:27:05.560-05:00", "resolved_inferred": false, "started_at": "2025-11-21T04:26:10.489-05:00", diff --git a/api/v/adalo.json b/api/v/adalo.json index b7ff39823785de3b177d6d5268dfdf5bd07c2641..bb5e865c5c3987b968f8cce62f46dc648269c13e 100644 --- a/api/v/adalo.json +++ b/api/v/adalo.json @@ -3,7 +3,7 @@ "slug": "adalo", "platform": "instatus", "status_url": "https://status.adalo.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": false, "first_watched": "2026-09-04T07:06:16Z", diff --git a/api/v/adaptavist-cloud-apps.json b/api/v/adaptavist-cloud-apps.json index 46cc3729e5271b5edc9c4dd9b393d2d9cca175fc..af55971b912fa5d91aaf5aa7911bcaa12b7196bc 100644 --- a/api/v/adaptavist-cloud-apps.json +++ b/api/v/adaptavist-cloud-apps.json @@ -3,7 +3,7 @@ "slug": "adaptavist-cloud-apps", "platform": "statuspage", "status_url": "https://status.connect.adaptavist.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "A small number of scripts failed to run between 9:01am UTC and 9:59am UTC on the 27th Aug 2026. \n\nThe issue is now resolved and scripts should be running normally.\n\nThis affected ScriptRunner for Jira and Confluence Cloud.\n\nApologies for any inconvenience caused.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-27T08:00:00.000Z", "resolved_inferred": false, "started_at": "2026-08-27T08:00:00.000Z", @@ -25,7 +25,7 @@ "body": "We\u2019re confident the ScriptRunner Cloud issues are now resolved, so we\u2019re closing this incident. If you experience any further issues, please contact our team.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-30T19:15:24.871Z", "resolved_inferred": false, "started_at": "2026-07-30T12:49:00.000Z", @@ -38,7 +38,7 @@ "body": "Between 10:15 and 10:30 UTC, customers using ScriptRunner for Jira Cloud or Enhanced Search apps may have experienced increased rate limiting when accessing Jira REST APIs from their scripts, other automations or JQL searches. This was caused by a gradual release of Atlassian's new authentication mechanism for requests made as individual users. We rolled back the changes and apologise for any disruption.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-28T09:00:00.000Z", "resolved_inferred": false, "started_at": "2026-07-28T09:00:00.000Z", @@ -51,7 +51,7 @@ "body": "The issue is caused by the deprecation of the legacy workflows page \nhttps://community.atlassian.com/forums/Jira-Cloud-Admins-articles/Final-notice-old-workflow-editor-deprecation-in-July-2026/ba-p/3247499\n\nFor users to edit their conditions and validators they will need to follow the instructions above to use the new workflow editor experience or edit their conditions and validators via the ScriptRunner Workflows Admin Page\n\nThanks!", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-16T08:52:37.219Z", "resolved_inferred": false, "started_at": "2026-07-16T08:37:13.656Z", @@ -64,7 +64,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-15T23:15:47.411Z", "resolved_inferred": false, "started_at": "2026-07-15T10:55:48.366Z", @@ -77,7 +77,7 @@ "body": "ScriptRunner Cloud migrations are operating normally. The underlying issue has been addressed, and we are monitoring the system to ensure continued stability. Thank you for your patience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-03T16:07:41.218Z", "resolved_inferred": false, "started_at": "2026-07-03T09:02:14.177Z", @@ -90,7 +90,7 @@ "body": "Our monitoring has confirmed the fix has worked.\nWe\u2019ll continue reviewing the incident to help prevent recurrence.\nOnce more, we apologise for any inconvenience caused and thank you for your patience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-16T14:55:52.794Z", "resolved_inferred": false, "started_at": "2026-06-16T12:31:11.945Z", @@ -103,7 +103,7 @@ "body": "Our monitoring has now confirmed that the issue with the Forms for Confluence service, causing errors in some forms has been resolved and that all systems and services are operating normally.\n\nWe\u2019ll continue reviewing the incident to help prevent recurrence.\n\nOnce more, we apologise for any inconvenience caused and thank you for your patience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-16T07:38:38.473Z", "resolved_inferred": false, "started_at": "2026-06-15T14:55:41.721Z", @@ -116,7 +116,7 @@ "body": "The issue has been fixed and the fix has been deployed. We are now monitoring the situation.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-04T19:27:44.737Z", "resolved_inferred": false, "started_at": "2026-06-04T18:52:51.082Z", @@ -129,7 +129,7 @@ "body": "At 13:21 28th May 2026 to 07:34 29th May 2026 UTC, there was an issue affecting script executions.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-01T13:43:54.106Z", "resolved_inferred": false, "started_at": "2026-06-01T10:01:56.419Z", @@ -142,7 +142,7 @@ "body": "Script Manager was unaccessible for a few hours between approximately 13:00 UTC and 22:00 UTC on 2026-05-05. Its visibility and accessibility have been restored. Script executions were unaffected.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-06T07:46:27.281Z", "resolved_inferred": false, "started_at": "2026-05-06T07:46:27.211Z", @@ -155,7 +155,7 @@ "body": "Atlassian published an update to their status page that their monitoring confirmed the issue with delays in delivering events is now resolved", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-30T15:00:29.239Z", "resolved_inferred": false, "started_at": "2026-04-30T09:42:14.424Z", @@ -168,7 +168,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-21T11:35:08.496Z", "resolved_inferred": false, "started_at": "2026-04-20T09:51:13.191Z", @@ -181,7 +181,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-20T11:32:13.201Z", "resolved_inferred": false, "started_at": "2026-04-17T07:27:13.703Z", @@ -194,7 +194,7 @@ "body": "We are confident that the issues we were seeing with processing event webhooks are resolved now. Please get in touch with our team if you experience any more issues.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-16T08:56:22.537Z", "resolved_inferred": false, "started_at": "2026-04-16T08:17:42.006Z", @@ -207,7 +207,7 @@ "body": "At 9:59 to 10:02 UTC (10:59 to 11:02 BST), there was an outage for ScriptRunner and EnhancedSearch apps in the US region only.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-13T10:31:25.550Z", "resolved_inferred": false, "started_at": "2026-04-13T10:31:25.489Z", @@ -220,7 +220,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-25T11:45:21.927Z", "resolved_inferred": false, "started_at": "2026-03-25T11:40:23.280Z", @@ -233,7 +233,7 @@ "body": "Our monitoring has now confirmed that the issue affecting macro functionality has been resolved and that services are running normally again.\nWe apologise for any inconvenience caused.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-13T00:47:56.824Z", "resolved_inferred": false, "started_at": "2026-03-12T15:06:11.995Z", @@ -246,7 +246,7 @@ "body": "At 08:25 UTC the execution demand dropped to normal levels and the system resumed normal operation.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-12T10:31:15.858Z", "resolved_inferred": false, "started_at": "2026-03-12T10:30:47.339Z", @@ -259,7 +259,7 @@ "body": "At 17:35 the execution demand dropped to normal levels and the system resumed normal operation.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-25T17:35:50.000Z", "resolved_inferred": false, "started_at": "2026-02-25T17:33:07.000Z", @@ -272,7 +272,7 @@ "body": "The issue has been resolved, after verifying that ES filter syncing is now working as expected. \n\nApologies for the inconvenience, and thank you for your patience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-20T18:42:13.153Z", "resolved_inferred": false, "started_at": "2026-02-20T14:16:22.682Z", @@ -285,7 +285,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-21T13:43:59.814Z", "resolved_inferred": false, "started_at": "2026-01-21T09:30:03.102Z", @@ -298,7 +298,7 @@ "body": "We have rolled back the changes, the incident is resolved now.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-14T16:59:17.149Z", "resolved_inferred": false, "started_at": "2026-01-14T16:21:07.462Z", @@ -311,7 +311,7 @@ "body": "We are confident that the issue we witnessed this morning is resolved and did not impact the vast majority of our users. We will close this incident, but will continue to monitor the status of the relevant systems as necessary.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-09T10:52:24.247Z", "resolved_inferred": false, "started_at": "2026-01-09T09:23:21.061Z", @@ -324,7 +324,7 @@ "body": "We experienced delays in automated filter syncing for ScriptRunner for Jira Enhanced Search customers in the US from 19:57 UTC to 22:00 UTC. Some filter results may have been out of date during this period for some customers. A work around was available at this time by manually syncing the filter from the Enhanced Search page. We apologise for the disruption and are implementing architecture changes to improve the stability of this service.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-08T22:00:00.000Z", "resolved_inferred": false, "started_at": "2026-01-08T22:00:00.000Z", @@ -337,7 +337,7 @@ "body": "We\u2019re confident the ScriptRunner Cloud issues are now resolved, so we\u2019re closing this incident. If you experience any further issues, please contact our team.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-31T13:14:22.914Z", "resolved_inferred": false, "started_at": "2025-12-31T07:56:17.699Z", @@ -350,7 +350,7 @@ "body": "We\u2019re confident the ScriptRunner Cloud issues are now resolved, so we\u2019re closing this incident. If you experience any further issues, please contact our team. Apologies for the inconvenience", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-31T15:10:55.768Z", "resolved_inferred": false, "started_at": "2025-12-29T12:30:17.000Z", @@ -363,7 +363,7 @@ "body": "We experienced delays in automated filter syncing for ScriptRunner for Jira Enhanced Search customers in the US from 11:00AM UTC to 5:00PM UTC. Some filter results may have been out of date during this period for some customers. A work around was available at this time by manually syncing the filter from the Enhanced Search page. We apologise for the disruption and are implementing architecture changes to improve the stability of this service.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-29T17:00:00.000Z", "resolved_inferred": false, "started_at": "2025-12-29T11:00:00.000Z", @@ -376,7 +376,7 @@ "body": "We have identified the issue and released a fix. Apologies for the inconvenience", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-19T15:53:54.643Z", "resolved_inferred": false, "started_at": "2025-12-18T19:00:47.000Z", @@ -389,7 +389,7 @@ "body": "We experienced delays in automated filter syncing for ScriptRunner for Jira Enhanced Search customers in the US from 12:45 UTC to 14:52 UTC. Some filter results may have been out of date during this period for some customers. A work around was available at this time by manually syncing the filter from the Enhanced Search page. We apologise for the disruption and are implementing architecture changes to improve the stability of this service.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-17T15:00:00.000Z", "resolved_inferred": false, "started_at": "2025-12-17T15:00:00.000Z", @@ -402,7 +402,7 @@ "body": "We have confirmed that automated migrations are working properly. We have identified the root cause and putting things in place to prevent a future outage.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-16T14:28:23.930Z", "resolved_inferred": false, "started_at": "2025-12-12T16:55:39.000Z", @@ -415,7 +415,7 @@ "body": "The issues we were seeing have now been resolved and filters are being synced automatically again.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-10T20:27:39.726Z", "resolved_inferred": false, "started_at": "2025-12-10T19:50:58.000Z", @@ -428,7 +428,7 @@ "body": "Scripts appear to have continued to perform at their standard level throughout a period of monitoring, therefore we're marking this incident as resolved.\n\nApologies for any inconvenience caused.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-11T09:52:48.515Z", "resolved_inferred": false, "started_at": "2025-12-10T16:48:40.973Z", @@ -441,7 +441,7 @@ "body": "We deployed a fix on 10 Dec at 19:32 UTC to resolve the issue and can confirm that the incident is now fully resolved.\n\nWe apologise for any inconvenience caused.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-11T07:44:52.283Z", "resolved_inferred": false, "started_at": "2025-12-10T11:29:22.357Z", @@ -454,7 +454,7 @@ "body": "We experienced delays in automated filter syncing for ScriptRunner for Jira Enhanced Search customers in the US from 10:00PM UTC 3rd December 2025 to 3:00AM UTC on 4th December 2025. Some filter results may have been out of date during this period for some customers. A work around was available at this time by manually syncing the filter from the Enhanced Search page. We apologise for the disruption and are implementing architecture changes to improve the stability of this service.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-04T03:00:00.000Z", "resolved_inferred": false, "started_at": "2025-12-03T22:00:00.000Z", @@ -467,7 +467,7 @@ "body": "All script using saved scripts from Script Manager are now working as expected.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-04T17:50:11.000Z", "resolved_inferred": false, "started_at": "2025-12-03T16:08:35.113Z", @@ -480,7 +480,7 @@ "body": "We experienced delays in automated filter syncing for ScriptRunner for Jira Enhanced Search customers in the US from 2:30AM UTC to 4:25AM UTC. Some filter results may have been out of date during this period for some customers. A work around was available at this time by manually syncing the filter from the Enhanced Search page. We apologise for the disruption and are implementing architecture changes to improve the stability of this service.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-26T02:30:00.000Z", "resolved_inferred": false, "started_at": "2025-11-26T02:30:00.000Z", @@ -493,7 +493,7 @@ "body": "We\u2019re confident the ScriptRunner Cloud issues are now resolved, so we\u2019re closing this incident. If you experience any further issues, please contact our team.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-26T03:32:39.728Z", "resolved_inferred": false, "started_at": "2025-11-25T22:03:58.361Z", @@ -506,7 +506,7 @@ "body": "Our monitoring has now confirmed that the incident has been resolved and that all services are running as normal again.\n\nWe apologise for any inconvenience caused.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-21T11:15:33.677Z", "resolved_inferred": false, "started_at": "2025-11-21T08:27:22.289Z", @@ -519,7 +519,7 @@ "body": "We are confident that the issues experienced with using ScriptRunner Cloud apps yesterday are now resolved, so we are closing this incident. If you experience any further issues then please get in touch with our team.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-20T11:15:45.040Z", "resolved_inferred": false, "started_at": "2025-11-19T15:59:49.832Z", @@ -532,7 +532,7 @@ "body": "Our monitoring has now confirmed that the incident has been resolved and that all services are running as normal again.\n\nWe apologise for any inconvenience caused.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-13T08:58:31.573Z", "resolved_inferred": false, "started_at": "2025-11-13T07:29:06.793Z", @@ -545,7 +545,7 @@ "body": "We have reverted the change causing the shorter timeouts. This has been confirmed to fix the issue.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-10T09:03:05.185Z", "resolved_inferred": false, "started_at": "2025-11-10T08:54:27.397Z", @@ -558,7 +558,7 @@ "body": "Atlassian has deployed a fix to mitigate the webhooks problem, and we've verified that the Script Listener service is now operating normally. If your Script Listener did not work between 01:00 and 20:47 UTC on October 22, 2025, it was likely affected by this incident.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-22T22:21:19.219Z", "resolved_inferred": false, "started_at": "2025-10-22T15:33:00.732Z", @@ -571,7 +571,7 @@ "body": "Between 20-21 October, Atlassian Cloud experienced a major service disruption due to an outage in AWS\u2019s US-EAST-1 region that affected DNS resolution and dependent global services (e.g., DynamoDB, IAM).\n\u2028This caused partial or complete unavailability across multiple Atlassian systems, including:\n* Jira Cloud, Confluence Cloud, and Bitbucket Cloud APIs\n* Marketplace (app listings, installations, licensing, and vendor management)\n* Forge developer platform (app deployment, logging, and monitoring)\n* Atlassian Support portal and related service desks\n* Authentication and user management flows\n\nScriptRunner for Jira and Confluence Cloud, Enhanced Search and Behaviours functionality were indirectly affected through Atlassian platform dependencies (e.g., API latency and Marketplace licensing validation), though no internal ScriptRunner infrastructure outage occurred.\n\u2028AWS mitigated the underlying DNS issue in US-EAST-1, after which Atlassian restored full functionality across affected products. Atlassian has confirmed full recovery of core services, with residual monitoring on migrations and JSM virtual service agents still ongoing.\n\nWe apologise for any inconvenience caused.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-21T07:24:18.568Z", "resolved_inferred": false, "started_at": "2025-10-21T07:24:18.516Z", @@ -584,7 +584,7 @@ "body": "Between 2025-09-29 22:24 UTC and 2025-09-30 00:39 UTC in our US hosting region only the following apps were unable to store and process webhooks, postfunctions and JCMA migration events sent to us from Atlassian due to an AWS service outage: ScriptRunner for Jira Cloud, ScriptRunner for Confluence Cloud and Enhanced Search.\nThis problem impacted Script Listeners, Postfunctions, Scripted Fields that depend on issue updates and Enhanced Search queries using keywords.\nApologies for any inconvenience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-29T21:30:00.000Z", "resolved_inferred": false, "started_at": "2025-09-29T21:30:00.000Z", @@ -597,7 +597,7 @@ "body": "We confirmed our earlier changes solved the problem reliably. The incident is closed and all migrations are operational. Customers who experienced the issue over the last weekend should re-attempt their migrations.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-29T13:15:26.000Z", "resolved_inferred": false, "started_at": "2025-09-25T16:00:31.000Z", @@ -610,7 +610,7 @@ "body": "All in app help documentation for ScriptRunner for Jira Cloud is now available again. Therefore this incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-22T14:09:59.480Z", "resolved_inferred": false, "started_at": "2025-09-22T09:02:07.117Z", @@ -623,7 +623,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-27T16:52:10.608Z", "resolved_inferred": false, "started_at": "2025-08-15T08:40:31.388Z", @@ -636,7 +636,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-15T08:34:25.533Z", "resolved_inferred": false, "started_at": "2025-08-13T09:52:12.657Z", @@ -649,7 +649,7 @@ "body": "This incident has been resolved. Script listeners and post functions should be operating normally.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-14T08:55:33.561Z", "resolved_inferred": false, "started_at": "2025-08-12T09:27:51.455Z", diff --git a/api/v/addigy.json b/api/v/addigy.json index 829cdc40f848351ff7a7d14ffd26e858d47be7f6..33517a0e056bf690774578992eb22c81da602eeb 100644 --- a/api/v/addigy.json +++ b/api/v/addigy.json @@ -3,7 +3,7 @@ "slug": "addigy", "platform": "statuspage", "status_url": "https://status.addigy.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-20T15:53:31.533Z", "resolved_inferred": false, "started_at": "2026-08-20T14:04:11.677Z", @@ -25,7 +25,7 @@ "body": "This issue has been resolved. Logging in to Addigy is working as expected. If you continue to see errors, please open a support ticket and we will assist.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-03T16:12:51.277Z", "resolved_inferred": false, "started_at": "2026-08-03T16:08:03.498Z", @@ -38,7 +38,7 @@ "body": "This issue has been resolved. To create or renew your push certificate, first download a fresh AddigyCSR.plist from your Addigy instance, then upload it to Apple\u2019s APNs portal. An older AddigyCSR.plist file will not work. If you still see errors after using a newly downloaded file, please open a support ticket and we will assist.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-03T16:54:24.436Z", "resolved_inferred": false, "started_at": "2026-08-03T16:01:49.990Z", @@ -51,7 +51,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-15T18:53:14.554Z", "resolved_inferred": false, "started_at": "2026-07-09T21:09:51.891Z", @@ -64,7 +64,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-22T18:01:24.359Z", "resolved_inferred": false, "started_at": "2026-06-22T14:15:24.695Z", @@ -77,7 +77,7 @@ "body": "A fix has been applied and the incident is now resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-18T13:00:46.889Z", "resolved_inferred": false, "started_at": "2026-06-18T12:53:46.874Z", @@ -90,7 +90,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-17T23:05:42.149Z", "resolved_inferred": false, "started_at": "2026-03-17T21:11:09.394Z", @@ -103,7 +103,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-22T20:15:17.409Z", "resolved_inferred": false, "started_at": "2026-02-22T18:41:04.312Z", @@ -116,7 +116,7 @@ "body": "This incident has been resolved. A fix has been deployed and monitoring has been verified.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-30T16:58:42.189Z", "resolved_inferred": false, "started_at": "2026-01-30T14:27:02.492Z", @@ -129,7 +129,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-30T18:18:34.051Z", "resolved_inferred": false, "started_at": "2025-09-30T17:34:01.703Z", @@ -142,7 +142,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-09T19:39:31.578Z", "resolved_inferred": false, "started_at": "2025-09-09T18:50:27.266Z", @@ -155,7 +155,7 @@ "body": "This incident has been resolved and correlated to an upstream provider incident: https://www.cloudflarestatus.com/incidents/d9n3g1vnxdd2", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-21T19:46:35.000Z", "resolved_inferred": false, "started_at": "2025-08-21T18:14:09.616Z", diff --git a/api/v/airbrake.json b/api/v/airbrake.json index 46ca2cd29781d62365bc24ac1436b67d8452ebf0..a957958db2ac7a3a932dd7b29d2044ef75f31a72 100644 --- a/api/v/airbrake.json +++ b/api/v/airbrake.json @@ -3,7 +3,7 @@ "slug": "airbrake", "platform": "statuspage", "status_url": "https://status.airbrake.io", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "The incident has been resolved and metrics are back online. There will be a dip in metric count graphs while the incident was experienced. Error event data was recorded normally and was unaffected. We apologize for the inconvenience. If you have any questions please reach us at support@airbrake.io.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-13T20:29:00.352-07:00", "resolved_inferred": false, "started_at": "2026-07-13T08:15:00.000-07:00", @@ -25,7 +25,7 @@ "body": "We've resolved an issue with our email notifications. The issue was caused by email asset delivery which we've resolved. We apologize for any inconvenience. Please email support at support@airbrake.io if you have any questions or concerns.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-01T08:53:12.777-07:00", "resolved_inferred": false, "started_at": "2026-06-01T07:22:17.515-07:00", @@ -38,7 +38,7 @@ "body": "A subset of customers experienced an issue where the error dashboard list was not loading properly. This may have resulted in error filtering being faulty or the errors list being blank. The issue was escalated to our techops team which resolved the issue.\n\nWe apologize for the inconvenience that this has caused. If you have any questions or concerns, please reach us at support@airbrake.io.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-06T04:00:03.000-07:00", "resolved_inferred": false, "started_at": "2026-05-06T04:00:03.000-07:00", diff --git a/api/v/aiven.json b/api/v/aiven.json index bf0b02f806626eebf85029038a9654976e03dd13..d203b47675e6d3839d4e2cea2507ffe1d6537ef2 100644 --- a/api/v/aiven.json +++ b/api/v/aiven.json @@ -3,7 +3,7 @@ "slug": "aiven", "platform": "statuspage", "status_url": "https://status.aiven.io", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "New VM creation has returned to normal across all cloud providers, including DigitalOcean.\n\n* VM provisioning is operating normally across all regions.\n* The upstream DigitalOcean incident has been resolved.\n* We are continuing to monitor the infrastructure to ensure stable provisioning.\n\nThe incident is now resolved. Thank you for your patience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-09T06:28:49Z", "resolved_inferred": false, "started_at": "2026-08-08T21:28:11Z", @@ -24,7 +24,7 @@ "body": "Our team has successfully applied the appropriate mitigation to all impacted nodes, and the fix has been deployed to prevent future occurrences.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-29T17:07:13Z", "resolved_inferred": false, "started_at": "2026-07-29T14:29:15Z", @@ -36,7 +36,7 @@ "body": "We have resolved the underlying cause of this issue.\n\nShould any further issues be encountered, please reach out to support via the Aiven console.\n\nWe apologise for the inconvenience caused by this issue, and commit to analysing and improving our platform to avoid future incidents similar to this one.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-03T05:28:30Z", "resolved_inferred": false, "started_at": "2026-07-02T23:24:59Z", @@ -48,7 +48,7 @@ "body": "The issue has been resolved. Terraform & Kubernetes operator users should no longer experience `400` errors when using `aiven_pg_database`. We apologize for any inconvenience caused.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-25T13:14:31Z", "resolved_inferred": false, "started_at": "2026-06-25T10:16:16Z", @@ -60,7 +60,7 @@ "body": "The issues affecting KRaft migrations during Kafka 3\\.8 to 3\\.9 upgrades have been resolved.\n\nFixes have been deployed, migrations have been re-enabled, and services have remained stable during monitoring. \n\nIf you are experiencing any issues, please contact support.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-25T11:38:25Z", "resolved_inferred": false, "started_at": "2026-06-23T14:18:37Z", @@ -72,7 +72,7 @@ "body": "The issue has been resolved. All affected functionality is operating normally.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-16T11:05:49Z", "resolved_inferred": false, "started_at": "2026-06-11T15:25:40Z", @@ -84,7 +84,7 @@ "body": "The monitoring period has passed without further evidence of the issue occurring. Incident has been declared resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-09T16:57:26Z", "resolved_inferred": false, "started_at": "2026-06-09T15:10:00Z", @@ -96,7 +96,7 @@ "body": "We have resolved the underlying cause of the issue affection service operations in our Azure regions.\n\nShould any further issues be encountered, please reach out to support via the Aiven console.\n\nWe apologise for the inconvenience caused by this issue, and commit to analysing and improving our platform to avoid future incidents similar to this one.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-25T03:54:07Z", "resolved_inferred": false, "started_at": "2026-05-25T02:29:06Z", @@ -108,7 +108,7 @@ "body": "This issue is now resolved.\n\nShould any further issues be encountered, please reach out to support via the Aiven console.\n\nWe apologise for the inconvenience caused by this issue.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-20T02:38:53Z", "resolved_inferred": false, "started_at": "2026-05-20T01:15:06Z", @@ -120,7 +120,7 @@ "body": "We have resolved the underlying cause of the kafka service disruption.\n\nShould any further issues be encountered, please reach out to support via the Aiven console.\n\nWe apologise for the inconvenience caused by this issue, and commit to analysing and improving our platform to avoid future incidents similar to this one.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-15T23:13:23Z", "resolved_inferred": false, "started_at": "2026-05-14T06:55:15Z", @@ -132,7 +132,7 @@ "body": "The underlying issues with Amazon Web Services (AWS) in the **ME-CENTRAL-1** and **ME-SOUTH-1** regions are ongoing, and AWS continues to work on recovery. \n\nWe have disabled the creation of new services and nodes in the affected regions to prevent further impact. We recommend our customers to migrate their services to a stable region as part of their disaster recovery plan. \n\nAs there are no further actions we can take at this time, we are moving this incident to a resolved state on our status page. The recovery of these regions is fully dependent on AWS. We will make **ME-CENTRAL-1** and **ME-SOUTH-1** regions available again for Aiven services once AWS confirms they are fully restored and stable. \n\nWe recommend customers continue to monitor the official AWS Health Status Page for updates.\nhttps://health.aws.amazon.com/health/status", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-02T11:23:09Z", "resolved_inferred": false, "started_at": "2026-03-01T23:12:45Z", @@ -144,7 +144,7 @@ "body": "The issue affecting node creation on the UpCloud cloud platform has been fully resolved. New services and replacement nodes are now provisioning successfully across all UpCloud regions. Our engineering team has completed all remediation steps and confirmed the stability of the platform.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-17T13:58:34Z", "resolved_inferred": false, "started_at": "2025-12-12T11:33:23Z", @@ -156,7 +156,7 @@ "body": "We are confirming that the platfom has remained **stable** following the resolution of the DNS update performance issue, and the system is handling expected load variations well. We are now closing the incident after extended monitoring.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-08T20:41:10Z", "resolved_inferred": false, "started_at": "2025-12-08T03:48:30Z", @@ -168,7 +168,7 @@ "body": "We have confirmed that all the Aiven services running on the Microsoft Azure region are operational. \n\nIf you face any further issues please contact Aiven support. ", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-06T03:35:09Z", "resolved_inferred": false, "started_at": "2025-12-05T07:19:24Z", @@ -180,7 +180,7 @@ "body": "The issue affecting metrics retrieval has been fully resolved. All metrics APIs and the Metrics page in the console should now be functioning normally. If you continue to experience any problems, please reach out to our support team and we\u2019ll be happy to assist.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-04T19:17:24Z", "resolved_inferred": false, "started_at": "2025-12-04T17:12:15Z", @@ -192,7 +192,7 @@ "body": "We have confirmed that the incident has been resolved, and all the PG replicas are operating normally.\n\nWe apologise for the inconvenience caused by this issue.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-24T05:38:38Z", "resolved_inferred": false, "started_at": "2025-11-24T03:39:21Z", @@ -204,7 +204,7 @@ "body": "We have identified a mitigation to resolve the issues causing PostgreSQL services not being able to be powered on after being powered off. \n\nWe are continuing to monitor closely to ensure no further problems.\n\nWe apologise for the inconvenience caused by this issue. ", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-20T00:07:14Z", "resolved_inferred": false, "started_at": "2025-11-19T22:05:11Z", @@ -216,7 +216,7 @@ "body": "Cloudflare has resolved the issues on their side and our platform has returned to normal operation. No impact was observed on any running services.\n\nShould any further issues be encountered, please reach out to support via the Aiven console.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-18T19:06:12Z", "resolved_inferred": false, "started_at": "2025-11-18T12:08:38Z", @@ -228,7 +228,7 @@ "body": "The root cause of this incident has been fixed. All impacted PostgreSQL 18 nodes are operating normally. \n\nWe apologize for any inconvenience this may have caused. If you continue to experience any issues with your PostgreSQL services, please contact our support team for assistance.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-06T07:35:58Z", "resolved_inferred": false, "started_at": "2025-11-06T04:24:09Z", @@ -240,7 +240,7 @@ "body": "**Resolved** -\u00a0 The issue with starting up new nodes has been resolved, and all services are now operating normally. We apologize for any inconvenience this may have caused.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-31T13:36:24Z", "resolved_inferred": false, "started_at": "2025-10-31T11:32:28Z", @@ -252,7 +252,7 @@ "body": "RESOLVED: We have identified and applied a fix for the issue where services in BYOC environments were struggling to spin up new nodes. All affected services should now be able to create and rebalance nodes normally.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-29T21:18:40Z", "resolved_inferred": false, "started_at": "2025-10-29T17:04:42Z", @@ -264,7 +264,7 @@ "body": "AWS has recovered and declared their incident as resolved.\n\nSee the AWS status page for a timeline on the issue: [https://health.aws.amazon.com/health/status](https://health.aws.amazon.com/health/status \"https://health.aws.amazon.com/health/status\")\n\nShould any further issues be encountered, please reach out to support via the Aiven console.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-20T23:57:36Z", "resolved_inferred": false, "started_at": "2025-10-20T09:30:50Z", @@ -276,7 +276,7 @@ "body": "Digital Ocean Engineering team has confirmed that the IPv6 connectivity issue has been fully resolved across all regions. Users should no longer face IPv6 connectivity issues. \n\nIf you continue to experience problems, please open a ticket with support team. Thank you for your patience and we apologize for any inconvenience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-17T05:05:25Z", "resolved_inferred": false, "started_at": "2025-10-17T00:29:08Z", @@ -288,7 +288,7 @@ "body": "We have resolved the underlying cause of issue affecting our customers using legacy MD5 password cannot connect through pgbouncer.\n\nShould any further issues be encountered, please reach out to support via the Aiven console.\n\nWe apologise for the inconvenience caused by this issue, and commit to analysing and improving our platform to avoid future incidents similar to this one.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-01T05:48:41Z", "resolved_inferred": false, "started_at": "2025-09-30T21:47:50Z", @@ -300,7 +300,7 @@ "body": "Service user logging pipelines are now operating as per normal. If you continue to experience delays, please reach out to Aiven Support. ", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-26T06:04:54Z", "resolved_inferred": false, "started_at": "2025-09-26T01:49:29Z", diff --git a/api/v/akamai-edge-dns.json b/api/v/akamai-edge-dns.json index ebb756a24d46dc924ca4f5e280c04775833bcc6e..4ae20e13b137bee4a4e86a5c405f758cc2e6e35c 100644 --- a/api/v/akamai-edge-dns.json +++ b/api/v/akamai-edge-dns.json @@ -3,7 +3,7 @@ "slug": "akamai-edge-dns", "platform": "statuspage", "status_url": "https://edgedns.status.akamai.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "degraded", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "We are continuing to investigate this issue. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a700001S7tYbCAJ. We will provide the next update as we make progress.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "started_at": "2026-09-04T06:14:59.971Z", "state": "investigating", "title": "Application Load Balancer reporting availability issues", @@ -23,7 +23,7 @@ "body": "We can confirm that the issue was mitigated at 03:30 UTC on 28 August 2026, and the service has resumed normal operation. Customers and partners can view additional details about the incident by logging in to: https://community.akamai.com/customers/s/feed/0D5a700001QvOI6CAN or reaching out to Akamai Support. We apologize for the impact and thank you for your patience and continued support. We are committed to making continuous improvements to make our systems better and prevent a recurrence of this issue.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-28T04:52:29.929Z", "resolved_inferred": false, "started_at": "2026-08-28T01:33:18.801Z", @@ -36,7 +36,7 @@ "body": "Customers and partners can find an incident summary report, here: https://community.akamai.com/customers/s/feed/0D5a700001QPRcTCAX", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-26T10:16:18.115Z", "resolved_inferred": false, "started_at": "2026-08-25T16:52:37.293Z", @@ -49,7 +49,7 @@ "body": "We can confirm that the issue was mitigated at 14:25 UTC on August 22, 2026, and the service has resumed normal operation. Customers and partners can view additional details about the incident by logging in to: https://community.akamai.com/customers/s/feed/0D5a700001Psh2gCAB or reaching out to Akamai Support. We apologize for the impact and thank you for your patience and continued support. We are committed to making continuous improvements to make our systems better and prevent a recurrence of this issue.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-24T18:50:49.215Z", "resolved_inferred": false, "started_at": "2026-08-22T11:21:42.123Z", @@ -62,7 +62,7 @@ "body": "We can confirm that the issue was mitigated at 23:50 UTC on August 24, 2026 and the service has resumed normal operation. Customers and partners can view additional details about the incident by logging in to: https://community.akamai.com/customers/s/feed/0D5a700001PVMc9CAH or reaching out to Akamai Support. We apologize for the impact and thank you for your patience and continued support. We are committed to making continuous improvements to make our systems better and prevent a recurrence of this issue.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-28T21:59:26.418Z", "resolved_inferred": false, "started_at": "2026-08-20T16:43:42.326Z", @@ -75,7 +75,7 @@ "body": "We can confirm that the issue was mitigated at 03:34 UTC on 19 August, 2026, and the service has resumed normal operation. Customers and partners can view additional details about the incident by logging in to: https://community.akamai.com/customers/s/feed/0D5a700001PHy9qCAD or reaching out to Akamai Support. We apologize for the impact and thank you for your patience and continued support. We are committed to making continuous improvements to make our systems better and prevent a recurrence of this issue.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-20T14:46:53.877Z", "resolved_inferred": false, "started_at": "2026-08-19T16:10:55.895Z", @@ -88,7 +88,7 @@ "body": "We can confirm that the issue was mitigated at 14:48 UTC on August 14, 2026, and the service has resumed normal operation. Customers and partners can view additional details about the incident by logging in to: https://community.akamai.com/customers/s/feed/0D5a700001NmwELCAZ or reaching out to Akamai Support. We apologize for the impact and thank you for your patience and continued support. We are committed to making continuous improvements to make our systems better and prevent a recurrence of this issue.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-14T19:40:32.855Z", "resolved_inferred": false, "started_at": "2026-08-14T14:53:36.527Z", @@ -101,7 +101,7 @@ "body": "We can confirm that the issue was confirmed mitigated at 20:42 UTC on August 18, 2026 and the service has resumed normal operation. Customers and partners can view additional details about the incident by logging in to: https://community.akamai.com/customers/s/feed/0D5a700001Nh4U3CAJ or reaching out to Akamai Support. We apologize for the impact and thank you for your patience and continued support. We are committed to making continuous improvements to make our systems better and prevent a recurrence of this issue.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-18T21:29:49.005Z", "resolved_inferred": false, "started_at": "2026-08-13T19:31:27.629Z", @@ -114,7 +114,7 @@ "body": "We can confirm that the issue was mitigated at 11:50 UTC on August 12, 2026, and the service has resumed normal operation. Customers and partners can view additional details about the incident by logging in to: https://community.akamai.com/customers/s/feed/0D5a700001NOXC4CAP or reaching out to Akamai Support. We apologize for the impact and thank you for your patience and continued support. We are committed to making continuous improvements to make our systems better and prevent a recurrence of this issue.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-13T13:52:57.111Z", "resolved_inferred": false, "started_at": "2026-08-12T13:02:24.232Z", @@ -127,7 +127,7 @@ "body": "We can confirm that the issue was mitigated at 08:30 UTC on August 14, 2026 and the service has resumed normal operation. Customers and partners can view additional details about the incident by logging in to: https://community.akamai.com/customers/s/feed/0D5a700001NAvXBCA1 or reaching out to Akamai Support. We apologize for the impact and thank you for your patience and continued support. We are committed to making continuous improvements to make our systems better and prevent a recurrence of this issue.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-14T17:08:09.838Z", "resolved_inferred": false, "started_at": "2026-08-11T10:11:57.929Z", @@ -140,7 +140,7 @@ "body": "We became aware of an issue with Web Security Analytics related to Empty HTTP Accept Language and Content Length header values being logged. The issue lasted between 11:30 UTC on August 3, 2026, and 14:00 UTC on August 4, 2026. We can confirm that the issue is now resolved, and the service has resumed normal operation. Customers and partners can view additional details about the incident by logging in to: https://community.akamai.com/customers/s/feed/0D5a700001M5NvWCAV or reaching out to Akamai Support. We apologize for the impact and thank you for your patience and continued support. We are committed to making continuous improvements to make our systems better and prevent a recurrence of this issue.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-04T14:00:00.000Z", "resolved_inferred": false, "started_at": "2026-08-04T14:00:00.000Z", @@ -153,7 +153,7 @@ "body": "We can confirm that the issue was mitigated at 00:20 UTC on August 4, 2026, and the service has resumed normal operation. Customers and partners can view additional details about the incident by logging in to: https://community.akamai.com/customers/s/feed/0D5a700001M2nELCAZ or reaching out to Akamai Support. We apologize for the impact and thank you for your patience and continued support. We are committed to making continuous improvements to make our systems better and prevent a recurrence of this issue.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-05T14:33:05.909Z", "resolved_inferred": false, "started_at": "2026-08-04T07:54:30.387Z", @@ -166,7 +166,7 @@ "body": "We can confirm that the issue was mitigated at 09:05 UTC on August 1, 2026 and the service has resumed normal operation. Customers and partners can view additional details about the incident by logging in to: https://community.akamai.com/customers/s/feed/0D5a700001LizHpCAJ or reaching out to Akamai Support. We apologize for the impact and thank you for your patience and continued support. We are committed to making continuous improvements to make our systems better and prevent a recurrence of this issue.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-01T12:14:33.276Z", "resolved_inferred": false, "started_at": "2026-08-01T10:54:20.448Z", @@ -179,7 +179,7 @@ "body": "We can confirm that the issue was mitigated at 14:21 UTC on 29 July 2026 and the service has resumed normal operation. Customers and partners can view additional details about the incident by logging in to: https://community.akamai.com/customers/s/feed/0D5a700001LBrwDCAT, or reaching out to Akamai Support. We apologize for the impact and thank you for your patience and continued support. We are committed to making continuous improvements to make our systems better and prevent a recurrence of this issue.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-29T17:06:22.854Z", "resolved_inferred": false, "started_at": "2026-07-29T14:48:18.227Z", @@ -192,7 +192,7 @@ "body": "We can confirm that the issue was mitigated at 01:30 UTC on 27 July 2026 and the service has resumed normal operation. Customers and partners can view additional details about the incident by logging in to: https://community.akamai.com/customers/s/feed/0D5a700001Kh1F0CAJ or reaching out to Akamai Support. We apologize for the impact and thank you for your patience and continued support. We are committed to making continuous improvements to make our systems better and prevent a recurrence of this issue.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-27T06:07:31.956Z", "resolved_inferred": false, "started_at": "2026-07-27T01:46:47.329Z", @@ -205,7 +205,7 @@ "body": "We can confirm that the issue was mitigated at 12:00 UTC on July 24, 2026 and the service has resumed normal operation. Customers and partners can view additional details about the incident by logging in to: https://community.akamai.com/customers/s/feed/0D5a700001KQ2QQCA1 or reaching out to Akamai Support. We apologize for the impact and thank you for your patience and continued support. We are committed to making continuous improvements to make our systems better and prevent a recurrence of this issue.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-24T18:45:31.126Z", "resolved_inferred": false, "started_at": "2026-07-24T12:21:37.517Z", @@ -218,7 +218,7 @@ "body": "We can confirm that the issue was mitigated at 04:10 UTC on July 19, 2026, and the service has resumed normal operation. Customers and partners can view additional details about the incident by logging in to: https://community.akamai.com/customers/s/feed/0D5a700001JVmHpCAL or reaching out to Akamai Support. We apologize for the impact and thank you for your patience and continued support. We are committed to making continuous improvements to make our systems better and prevent a recurrence of this issue.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-20T14:46:38.457Z", "resolved_inferred": false, "started_at": "2026-07-19T07:40:27.560Z", @@ -231,7 +231,7 @@ "body": "We can confirm that the issue was mitigated at 04:36 UTC on 16 July 2026 and the service has resumed normal operation. Customers and partners can view additional details about the incident by logging in to: https://community.akamai.com/customers/s/feed/0D5a700001J1h4UCAR or reaching out to Akamai Support. We apologize for the impact and thank you for your patience and continued support. We are committed to making continuous improvements to make our systems better and prevent a recurrence of this issue.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-23T02:06:06.179Z", "resolved_inferred": false, "started_at": "2026-07-16T04:21:58.828Z", @@ -244,7 +244,7 @@ "body": "We can confirm that the issue was mitigated at 4:20 UTC on July 2, 2026 and the service has resumed normal operation. Customers and partners can view additional details about the incident by logging in to: or reaching out to Akamai Support. We apologize for the impact and thank you for your patience and continued support. We are committed to making continuous improvements to make our systems better and prevent a recurrence of this issue.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-06T04:11:26.005Z", "resolved_inferred": false, "started_at": "2026-07-02T14:40:01.861Z", @@ -257,7 +257,7 @@ "body": "We can confirm that the issue was mitigated at 21:14 UTC on June 30, 2026 and the service has resumed normal operation. Customers and partners can view additional details about the incident by logging in to https://community.akamai.com/customers/s/feed/0D5a700001GabcKCAR or reaching out to Akamai Support. We apologize for the impact and thank you for your patience and continued support. We are committed to making continuous improvements to make our systems better and prevent a recurrence of this issue.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-30T22:02:40.317Z", "resolved_inferred": false, "started_at": "2026-06-30T21:15:05.493Z", @@ -270,7 +270,7 @@ "body": "We can confirm that the issue was mitigated at 16:50 UTC on June 28, 2026, and the service has resumed normal operation. Customers and partners can view additional details about the incident by logging in to: https://community.akamai.com/customers/s/feed/0D5a700001GB7HRCA1 or reaching out to Akamai Support. We apologize for the impact and thank you for your patience and continued support. We are committed to making continuous improvements to make our systems better and prevent a recurrence of this issue.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-29T15:42:59.184Z", "resolved_inferred": false, "started_at": "2026-06-28T14:45:34.035Z", @@ -283,7 +283,7 @@ "body": "We can confirm that the issue was mitigated at 20:55 UTC on 25 June 2026 and the service has resumed normal operation. Customers and partners can view additional details about the incident by logging in to: https://community.akamai.com/customers/s/feed/0D5a700001FiyHGCAZ, or reaching out to Akamai Support. We apologize for the impact and thank you for your patience and continued support. We are committed to making continuous improvements to make our systems better and prevent a recurrence of this issue.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-26T23:35:06.212Z", "resolved_inferred": false, "started_at": "2026-06-25T18:14:17.634Z", @@ -296,7 +296,7 @@ "body": "We became aware of an issue with HTTP and HTTPS related to latency and performance degradation while accessing the applications. The issue lasted between 13:37 UTC and 14:20 UTC on June 16, 2026. We can confirm that the issue is now resolved, and the service has resumed normal operation. Customers and partners can view additional details about the incident by logging in to: https://community.akamai.com/customers/s/feed/0D5a700001E6lLpCAJ or reaching out to Akamai Support. We apologize for the impact and thank you for your patience and continued support. We are committed to making continuous improvements to make our systems better and prevent a recurrence of this issue.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-16T15:45:24.635Z", "resolved_inferred": false, "started_at": "2026-06-16T15:45:24.572Z", @@ -309,7 +309,7 @@ "body": "We identified an issue with the Datastream service where between 10:00 UTC and 21:00 UTC on June 11, 2026, customers may have experienced degraded fidelity on CDN observability streams. We can confirm that the issue is now mitigated as of 21:00 UTC on June 11, 2026, and no longer occurring. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a700001DVkdgCAD. We apologize for any impact and thank you for your patience and continued support. We are committed to making continuous improvements to make our systems better and prevent recurrence.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-12T14:58:05.609Z", "resolved_inferred": false, "started_at": "2026-06-12T14:58:05.505Z", @@ -322,7 +322,7 @@ "body": "We can confirm that the issue was mitigated at 18:41 UTC on June 10, 2026 and the service has resumed normal operation. Customers and partners can view additional details about the incident by logging in to: https://community.akamai.com/customers/s/feed/0D5a700001D7uShCAJ or reaching out to Akamai Support. We apologize for the impact and thank you for your patience and continued support. We are committed to making continuous improvements to make our systems better and prevent a recurrence of this issue.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-11T16:41:41.011Z", "resolved_inferred": false, "started_at": "2026-06-10T18:38:27.837Z", @@ -335,7 +335,7 @@ "body": "We can confirm that the issue was mitigated at 1:30 UTC on June 6, 2026 and the service has resumed normal operation. Customers and partners can view additional details about the incident by logging in to: https://community.akamai.com/customers/s/feed/0D5a700001CQ6lqCAD or reaching out to Akamai Support. We apologize for the impact and thank you for your patience and continued support. We are committed to making continuous improvements to make our systems better and prevent a recurrence of this issue.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-06T07:21:13.014Z", "resolved_inferred": false, "started_at": "2026-06-06T04:29:26.000Z", @@ -348,7 +348,7 @@ "body": "We can confirm that the issue was mitigated at 17:30 UTC on June 12, 2026, 2026, and the service has resumed normal operation. Customers and partners can view additional details about the incident by logging in to: https://community.akamai.com/customers/s/feed/0D5a7000015iVQMCA2, or reaching out to Akamai Support. We apologize for the impact and thank you for your patience and continued support. We are committed to making continuous improvements to make our systems better and prevent a recurrence of this issue.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-19T11:07:17.400Z", "resolved_inferred": false, "started_at": "2026-06-05T16:16:27.279Z", @@ -361,7 +361,7 @@ "body": "We became aware of an issue with HTTP and HTTPS related to latency while accessing the applications. The issue lasted between 11:18 UTC and 12:22 UTC on May 27, 2026. We can confirm that the issue is now resolved, and the service has resumed normal operation. Customers and partners can view additional details about the incident by logging in to: https://community.akamai.com/customers/s/feed/0D5a700001ANLNkCAP or reaching out to Akamai Support. We apologize for the impact and thank you for your patience and continued support. We are committed to making continuous improvements to make our systems better and prevent a recurrence of this issue.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-27T13:28:12.247Z", "resolved_inferred": false, "started_at": "2026-05-27T13:28:12.019Z", @@ -374,7 +374,7 @@ "body": "We can confirm that the issue was mitigated at 14:50 UTC on May 21, 2026, and the service has resumed normal operation. Customers and partners can view additional details about the incident by logging in to: https://community.akamai.com/customers/s/feed/0D5a7000019St8yCAC or reaching out to Akamai Support. We apologize for the impact and thank you for your patience and continued support. We are committed to making continuous improvements to make our systems better and prevent a recurrence of this issue.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-21T16:52:10.334Z", "resolved_inferred": false, "started_at": "2026-05-21T13:58:05.340Z", @@ -387,7 +387,7 @@ "body": "Starting around 12:00 UTC on May 20, 2026, users experienced difficulties with configuration deployments for mPulse and EdgeWorkers. During this period, activations within Property Manager were impacted, preventing affected customers from successfully updating or deploying these configurations.\n\nAkamai initiated an investigation and determined that the issue was caused by a tripped circuit breaker, which resulted in multiple racks in the data center losing power. We responded with a series of coordinated actions to address both the immediate power outage and its downstream effects on critical services. At 14:45 UTC on May 20, 2026, a failover was completed, and by 14:55 UTC on May 20, 2026, error rates in the Akamai Control Center began to decrease, and the issue was mitigated.\n\nWe will continue to investigate the root cause and will take appropriate preventive actions. We apologize for the impact. We appreciate your patience as we worked to resolve this issue. If you have further questions, please post them on [https://community.akamai.com/customers/s/feed/0D5a7000019DgxBCAS](https://community.akamai.com/customers/s/feed/0D5a7000019DgxBCAS).\n\nThis summary provides an overview of our current understanding of the incident given the information available. Our investigation is ongoing and any information herein is subject to change.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-21T12:36:41.094Z", "resolved_inferred": false, "started_at": "2026-05-20T14:29:36.858Z", @@ -400,7 +400,7 @@ "body": "We can confirm that the issue was mitigated and the service has resumed normal operation. Customers and partners can view additional details about the incident by logging in to: https://community.akamai.com/customers/s/feed/0D5a7000018q2TuCAI or reaching out to Akamai Support. We apologize for the impact and thank you for your patience and continued support. We are committed to making continuous improvements to make our systems better and prevent a recurrence of this issue.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-01T07:46:02.442Z", "resolved_inferred": false, "started_at": "2026-05-19T10:13:33.000Z", @@ -413,7 +413,7 @@ "body": "We can confirm that the issue was mitigated at 18:21 UTC on May 14th, 2026 and the service has resumed normal operation. Customers and partners can view additional details about the incident by logging in to: https://community.akamai.com/customers/s/feed/0D5a70000189Hk3CAE, or reaching out to Akamai Support. We apologize for the impact and thank you for your patience and continued support. We are committed to making continuous improvements to make our systems better and prevent a recurrence of this issue.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-14T18:45:51.890Z", "resolved_inferred": false, "started_at": "2026-05-14T18:08:25.615Z", @@ -426,7 +426,7 @@ "body": "We can confirm that the issue was mitigated at approximately 09:40 UTC on May 13, 2026, and the service has resumed normal operation. Customers and partners can view additional details about the incident by logging in to: https://community.akamai.com/customers/s/feed/0D5a7000017tokVCAQ or reaching out to Akamai Support. We apologize for the impact and thank you for your patience and continued support. We are committed to making continuous improvements to make our systems better and prevent a recurrence of this issue.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-13T10:25:03.179Z", "resolved_inferred": false, "started_at": "2026-05-13T09:33:04.568Z", @@ -439,7 +439,7 @@ "body": "Customers and partners can find an incident summary report here: https://community.akamai.com/customers/s/feed/0D5a7000017mjDUCAY", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-13T01:08:51.634Z", "resolved_inferred": false, "started_at": "2026-05-12T17:08:25.136Z", @@ -452,7 +452,7 @@ "body": "We can confirm that the issue was mitigated at 23:13 UTC on May 11, 2026 and the service has resumed normal operation. Customers and partners can view additional details about the incident by logging in to: https://community.akamai.com/customers/s/feed/0D5a7000017a38WCAQ or reaching out to Akamai Support. We apologize for the impact and thank you for your patience and continued support. We are committed to making continuous improvements to make our systems better and prevent a recurrence of this issue.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-12T19:18:56.055Z", "resolved_inferred": false, "started_at": "2026-05-11T16:03:03.105Z", @@ -465,7 +465,7 @@ "body": "We can confirm that the issue was mitigated at approximately 11:30 UTC on May 6, 2026, and the service has resumed normal operation. Customers and partners can view additional details about the incident by logging in to: https://community.akamai.com/customers/s/feed/0D5a7000016uVhvCAE or reaching out to Akamai Support. We apologize for the impact and thank you for your patience and continued support. We are committed to making continuous improvements to make our systems better and prevent a recurrence of this issue.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-06T12:01:06.153Z", "resolved_inferred": false, "started_at": "2026-05-06T11:21:27.308Z", @@ -478,7 +478,7 @@ "body": "We can confirm that the issue was mitigated at 19:00 UTC on April 30, 2026, and the service has resumed normal operation. Customers and partners can view additional details about the incident by logging in to: https://community.akamai.com/customers/s/feed/0D5a70000168PJsCAM, or reaching out to Akamai Support. We apologize for the impact and thank you for your patience and continued support. We are committed to making continuous improvements to make our systems better and prevent a recurrence of this issue.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-30T20:00:19.679Z", "resolved_inferred": false, "started_at": "2026-04-30T18:41:53.530Z", @@ -491,7 +491,7 @@ "body": "We can confirm that the issue was mitigated at 06:50 UTC on May 4, 2026 and the service has resumed normal operation. Customers and partners can view additional details about the incident by logging in to: https://community.akamai.com/customers/s/feed/0D5a7000015pThhCAE or reaching out to Akamai Support. We apologize for the impact and thank you for your patience and continued support. We are committed to making continuous improvements to make our systems better and prevent a recurrence of this issue.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-04T12:24:25.340Z", "resolved_inferred": false, "started_at": "2026-04-29T05:19:52.480Z", @@ -504,7 +504,7 @@ "body": "We can confirm that the issue was mitigated at 12:00 UTC on 2 May, 2026 and the service has resumed normal operation. Customers and partners can view additional details about the incident by logging in to: https://community.akamai.com/customers/s/feed/0D5a7000015jW2OCAU or reaching out to Akamai Support. We apologize for the impact and thank you for your patience and continued support. We are committed to making continuous improvements to make our systems better and prevent a recurrence of this issue.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-04T03:05:38.891Z", "resolved_inferred": false, "started_at": "2026-04-28T16:42:43.247Z", @@ -517,7 +517,7 @@ "body": "We can confirm that the issue was mitigated at 16:20 UTC on April 28, 2026, and the service has resumed normal operation. Customers and partners can view additional details about the incident by logging in to: https://community.akamai.com/customers/s/feed/0D5a7000015iVQMCA2, or reaching out to Akamai Support. We apologize for the impact and thank you for your patience and continued support. We are committed to making continuous improvements to make our systems better and prevent a recurrence of this issue.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-28T23:37:50.470Z", "resolved_inferred": false, "started_at": "2026-04-28T15:40:33.808Z", @@ -530,7 +530,7 @@ "body": "We can confirm that the issue was mitigated at 13:30 UTC on April 28, 2026 and the service has resumed normal operation. Customers and partners can view additional details about the incident by logging in to: https://community.akamai.com/customers/s/feed/0D5a7000015dBomCAE or reaching out to Akamai Support. We apologize for the impact and thank you for your patience and continued support. We are committed to making continuous improvements to make our systems better and prevent a recurrence of this issue.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-28T17:02:49.219Z", "resolved_inferred": false, "started_at": "2026-04-28T02:50:21.736Z", @@ -543,7 +543,7 @@ "body": "We can confirm that the issue was mitigated at 05:26 UTC on 27 April, 2026, and the service has resumed normal operation. Customers and partners can view additional details about the incident by logging in to: https://community.akamai.com/customers/s/feed/0D5a7000015Qwi8CAC or reaching out to Akamai Support.\n\nWe apologize for the impact and thank you for your patience and continued support. We are committed to making continuous improvements to make our systems better and prevent a recurrence of this issue.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-27T13:27:25.583Z", "resolved_inferred": false, "started_at": "2026-04-27T03:20:42.690Z", @@ -556,7 +556,7 @@ "body": "We can confirm that the issue was mitigated at 23:36 UTC on April 24, 2026 and the service has resumed normal operation. Customers and partners can view additional details about the incident by logging in to: https://community.akamai.com/customers/s/feed/0D5a7000015H7xxCAC?language=en_US or reaching out to Akamai Support. We apologize for the impact and thank you for your patience and continued support. We are committed to making continuous improvements to make our systems better and prevent a recurrence of this issue.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-24T23:52:45.134Z", "resolved_inferred": false, "started_at": "2026-04-24T20:07:51.874Z", @@ -569,7 +569,7 @@ "body": "We can confirm that the issue was mitigated at 10:45 UTC on April 28, 2026 and the service has resumed normal operation. Customers and partners can view additional details about the incident by logging in to: https://community.akamai.com/customers/s/feed/0D5a70000151eEnCAI or reaching out to Akamai Support. We apologize for the impact and thank you for your patience and continued support. We are committed to making continuous improvements to make our systems better and prevent a recurrence of this issue.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-28T17:39:18.528Z", "resolved_inferred": false, "started_at": "2026-04-23T14:11:12.339Z", @@ -582,7 +582,7 @@ "body": "We became aware of an issue in the Akamai Control Center related to errors when using multiple tools within \"Edge Diagnostics\". The issue lasted between 20:34 UTC on April 22, 2026, and 8:31 UTC on April 23, 2026. We can confirm that the issue is now resolved, and the service has resumed normal operation. Customers and partners can view additional details about the incident by logging in to: https://community.akamai.com/customers/s/feed/0D5a7000014zYTlCAM or reaching out to Akamai Support. We apologize for the impact and thank you for your patience and continued support. We are committed to making continuous improvements to make our systems better and prevent a recurrence of this issue.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-23T09:44:30.000Z", "resolved_inferred": false, "started_at": "2026-04-23T09:44:30.000Z", @@ -595,7 +595,7 @@ "body": "Customers and partners can find an incident summary report, here: https://community.akamai.com/customers/s/feed/0D5a7000014QIlOCAW", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-21T01:07:38.369Z", "resolved_inferred": false, "started_at": "2026-04-20T12:25:21.935Z", @@ -608,7 +608,7 @@ "body": "We can confirm that the issue was mitigated at 04:57 UTC on 16 April 2026 and the service has resumed normal operation. Customers and partners can view additional details about the incident by logging in to: https://community.akamai.com/customers/s/feed/0D5a7000013s3OVCAY or reaching out to Akamai Support. We apologize for the impact and thank you for your patience and continued support. We are committed to making continuous improvements to make our systems better and prevent a recurrence of this issue.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-16T06:44:20.283Z", "resolved_inferred": false, "started_at": "2026-04-16T03:17:27.921Z", @@ -621,7 +621,7 @@ "body": "We can confirm that the issue was mitigated at 11:30 UTC on April 8, 2026, and the service has resumed normal operation. Customers and partners can view additional details about the incident by logging in to: https://community.akamai.com/customers/s/feed/0D5a7000012Uk7TCAS or reaching out to Akamai Support.\n\nWe apologize for the impact and thank you for your patience and continued support. We are committed to making continuous improvements to make our systems better and prevent a recurrence of this issue.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-08T13:02:20.777Z", "resolved_inferred": false, "started_at": "2026-04-07T18:43:51.686Z", @@ -634,7 +634,7 @@ "body": "We can confirm that the issue was mitigated at 11:00 UTC on April 13, 2026 and the service has resumed normal operation. Customers and partners can view additional details about the incident by logging in to: https://community.akamai.com/customers/s/feed/0D5a7000012RCWbCAO or reaching out to Akamai Support. We apologize for the impact and thank you for your patience and continued support. We are committed to making continuous improvements to make our systems better and prevent a recurrence of this issue.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-14T19:47:46.021Z", "resolved_inferred": false, "started_at": "2026-04-07T12:11:07.442Z", @@ -647,7 +647,7 @@ "body": "We can confirm that the issue was mitigated at 23:12 UTC on April 10, 2026 and the service has resumed normal operation. Customers and partners can view additional details about the incident by logging in to: or reaching out to Akamai Support. We apologize for the impact and thank you for your patience and continued support. We are committed to making continuous improvements to make our systems better and prevent a recurrence of this issue.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-15T16:02:59.494Z", "resolved_inferred": false, "started_at": "2026-04-06T18:22:58.211Z", diff --git a/api/v/alchemy.json b/api/v/alchemy.json index ca0d1c00915f106226a7395a1e92134b9e217d93..de8ee43caf5fa382903e8ed812df2dd4be5ff262 100644 --- a/api/v/alchemy.json +++ b/api/v/alchemy.json @@ -3,7 +3,7 @@ "slug": "alchemy", "platform": "statuspage", "status_url": "https://status.alchemy.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "The incident has been resolved. We are continuing to monitor the situation.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-09-03T16:54:10.399Z", "resolved_inferred": false, "started_at": "2026-09-03T15:41:24.397Z", @@ -25,7 +25,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-09-03T03:48:05.000Z", "resolved_inferred": false, "started_at": "2026-09-03T02:58:55.000Z", @@ -38,7 +38,7 @@ "body": "All networks latencies are back to baseline.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-31T15:34:06.077Z", "resolved_inferred": false, "started_at": "2026-08-31T14:39:39.846Z", @@ -51,7 +51,7 @@ "body": "Incident is resolved and blocks are being produced again - confirmed by Cronost team: https://x.com/CronosNetwork/status/2094417832394301499", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-31T13:38:17.909Z", "resolved_inferred": false, "started_at": "2026-08-31T12:15:16.092Z", @@ -64,7 +64,7 @@ "body": "The elevated latencies affecting Ethereum Mainnet Data APIs have been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-29T19:45:42.275Z", "resolved_inferred": false, "started_at": "2026-08-29T18:13:47.000Z", @@ -77,7 +77,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-27T20:47:01.000Z", "resolved_inferred": false, "started_at": "2026-08-27T20:05:55.000Z", @@ -90,7 +90,7 @@ "body": "This incident has been resolved! WebSocket subscription delivery for X Layer Mainnet in our US East region has returned to normal. HTTP requests were not affected at any point during this incident", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-27T23:40:52.297Z", "resolved_inferred": false, "started_at": "2026-08-27T16:18:44.574Z", @@ -103,7 +103,7 @@ "body": "This incident has been resolved. Between approximately 21:58 UTC and 22:12 UTC, some API requests across multiple networks experienced elevated latency, primarily affecting Token API and Portfolio API balance lookups.\n\nAll services are currently operating normally. We will continue to investigate the underlying cause to prevent recurrence!", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-26T22:12:55.000Z", "resolved_inferred": false, "started_at": "2026-08-26T21:58:13.000Z", @@ -116,7 +116,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-26T21:59:28.000Z", "resolved_inferred": false, "started_at": "2026-08-26T12:30:35.000Z", @@ -129,7 +129,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-25T18:30:50.000Z", "resolved_inferred": false, "started_at": "2026-08-25T13:31:17.157Z", @@ -142,7 +142,7 @@ "body": "A subset of nodes serving Unichain Mainnet in our US East (use1) region experienced stalled safe/finalized block tracking, causing delayed safe/finalized block data for requests routed through that region. The latest block head and overall API serving were unaffected throughout and no elevated error rates were observed.\n\nWe performed a rolling restart of the affected nodes, which resolved the issue. Safe/finalized data is now current and within normal lag across the region.\n\nThis incident is resolved!", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-24T18:37:04.751Z", "resolved_inferred": false, "started_at": "2026-08-24T12:23:27.483Z", @@ -155,7 +155,7 @@ "body": "Resolved - Elevated latency on BNB Smart Chain Mainnet JSON-RPC requests has been fully mitigated. All methods are performing within normal latency ranges!", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-25T14:25:45.249Z", "resolved_inferred": false, "started_at": "2026-08-23T14:20:30.217Z", @@ -168,7 +168,7 @@ "body": "Latency has returned to normal for Robinhood Mainnet. We will continue to monitor the service.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-22T22:43:51.868Z", "resolved_inferred": false, "started_at": "2026-08-22T21:33:48.844Z", @@ -181,7 +181,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-20T01:43:19.879Z", "resolved_inferred": false, "started_at": "2026-08-20T00:36:00.000Z", @@ -194,7 +194,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-20T16:02:39.853Z", "resolved_inferred": false, "started_at": "2026-08-19T17:42:17.000Z", @@ -207,7 +207,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-19T06:45:37.051Z", "resolved_inferred": false, "started_at": "2026-08-19T06:00:37.127Z", @@ -220,7 +220,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-17T14:30:58.000Z", "resolved_inferred": false, "started_at": "2026-08-17T14:18:14.530Z", @@ -233,7 +233,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-13T15:41:08.000Z", "resolved_inferred": false, "started_at": "2026-08-13T14:52:31.670Z", @@ -246,7 +246,7 @@ "body": "This incident has been resolved. Injective Mainnet performance has returned to normal.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-14T18:00:57.000Z", "resolved_inferred": false, "started_at": "2026-08-13T11:36:52.594Z", @@ -259,7 +259,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-12T08:03:40.551Z", "resolved_inferred": false, "started_at": "2026-08-12T04:45:15.286Z", @@ -272,7 +272,7 @@ "body": "The issue has been resolved. Solana Mainnet service has recovered in Singapore and Tokyo, and we are monitoring the situation closely.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-12T04:44:30.569Z", "resolved_inferred": false, "started_at": "2026-08-12T04:38:33.206Z", @@ -285,7 +285,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-12T02:33:22.475Z", "resolved_inferred": false, "started_at": "2026-08-12T01:19:45.000Z", @@ -298,7 +298,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-10T17:11:14.299Z", "resolved_inferred": false, "started_at": "2026-08-10T12:29:38.657Z", @@ -311,7 +311,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-06T06:12:09.788Z", "resolved_inferred": false, "started_at": "2026-08-06T06:09:06.830Z", @@ -324,7 +324,7 @@ "body": "Between 17:22 and 17:35 UTC on August 5, a subset of eth_getUserOperationReceipt requests across multiple networks experienced increased latencies. This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-05T17:45:11.000Z", "resolved_inferred": false, "started_at": "2026-08-05T17:45:11.000Z", @@ -337,7 +337,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-31T16:02:32.197Z", "resolved_inferred": false, "started_at": "2026-07-31T15:08:55.000Z", @@ -350,7 +350,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-31T14:23:36.759Z", "resolved_inferred": false, "started_at": "2026-07-31T13:19:33.711Z", @@ -363,7 +363,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-31T02:49:50.531Z", "resolved_inferred": false, "started_at": "2026-07-31T01:07:51.942Z", @@ -376,7 +376,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-30T17:10:12.171Z", "resolved_inferred": false, "started_at": "2026-07-30T16:04:18.285Z", @@ -389,7 +389,7 @@ "body": "Between 22:35 and 22:55 UTC on July 30, a subset of requests on Robinhood Mainnet experienced elevated latency. This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-30T21:30:00.000Z", "resolved_inferred": false, "started_at": "2026-07-30T00:00:00.000Z", @@ -402,7 +402,7 @@ "body": "Between 13:30 UTC on July 28 and 08:00 UTC on July 29, HYPERLIQUID\\_MAINNET requests served from us-east experienced elevated latency, and `eth_sendRawTransaction` returned a high rate of errors. Read methods remained available throughout, with elevated response times.\n\n**Impact**\n\nTransaction submission was the primary failure mode. During the peak period, the large majority of `eth_sendRawTransaction` requests either timed out or returned an error, and clients retrying submissions saw sustained failures. Read traffic on the network was slower than normal but continued to be served successfully. Latency was elevated for all HYPERLIQUID\\_MAINNET request types for the duration of the event.\n\n**Root cause**\n\nA majority of our Hyperliquid full nodes in us-east lost peering with the network. The nodes were unable to complete state synchronization handshakes with upstream peers -- connection attempts were rate limited, timed out, or rejected because peer connection slots were full. Affected nodes fell behind and were removed from the healthy serving pool. Recovery required the upstream peer pool to free capacity; feeding new peers into the configuration and pruning node state did not restore peering.\n\nTwo factors extended the impact:\n\n* With that capacity gone, all us-east traffic concentrated on the remaining archive node pool, which pushed latency up further and made `eth_sendRawTransaction` the first method to fail.\n* On Hyperliquid, transactions are not propagated peer-to-peer. They are relayed to a network-level submission endpoint that can rate limit, which means the transaction submission path is sensitive to network conditions independent of which infrastructure serves the request.\n\n**Resolution**\n\nWe began routing `eth_sendRawTransaction` to secondary infra as soon as the issue was identified, but this did not restore transaction submission. Submissions relayed through secondary infra continued to fail at a comparable rate, since that path depends on the same network-level submission endpoint. \n\nA subset of nodes began to recover from around 01:30 UTC on July 29, when the first `hlnode` in us-east returned to a healthy state as upstream peer capacity freed up. Server-side errors from our serving layer dropped off around the same time, though submissions continued to fail through a mix of remaining unhealthy nodes and rejections at the network's submission endpoint. Peering re-established across the rest of the pool over the following hours. Latency returned to normal levels by approximately 08:00 UTC, request volumes and error rates returned to baseline, and all us-east nodes were confirmed healthy shortly afterward.\n\n**Follow-up**\n\nWe are exploring running our own validator and sentry nodes for Hyperliquid so that peering no longer depends on availability in the shared public peer pool.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-29T08:00:53.000Z", "resolved_inferred": false, "started_at": "2026-07-28T14:06:34.423Z", @@ -415,7 +415,7 @@ "body": "This is resolved. Base Mainnet's Safe head has caught up and data batching to Ethereum L1 is back to normal. Block production was unaffected throughout. See the Base status page for their full update: https://status.base.org/incidents/j6y12tshwkcg", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-28T15:33:18.806Z", "resolved_inferred": false, "started_at": "2026-07-28T13:26:57.168Z", @@ -428,7 +428,7 @@ "body": "Nodes have recovered and services are healthy again.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-27T06:51:48.839Z", "resolved_inferred": false, "started_at": "2026-07-27T03:39:54.079Z", @@ -441,7 +441,7 @@ "body": "Nodes have been rescyned with stable binary and services are back to healthy.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-24T12:49:32.837Z", "resolved_inferred": false, "started_at": "2026-07-24T09:36:40.044Z", @@ -454,7 +454,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-24T11:09:57.252Z", "resolved_inferred": false, "started_at": "2026-07-23T15:12:29.745Z", @@ -467,7 +467,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-24T12:00:48.517Z", "resolved_inferred": false, "started_at": "2026-07-23T09:34:15.165Z", @@ -480,7 +480,7 @@ "body": "Resolved: All impacted networks, including Mode Sepolia (testnet), have fully recovered and caught up. This incident is now resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-22T18:42:07.504Z", "resolved_inferred": false, "started_at": "2026-07-22T18:07:15.813Z", @@ -493,7 +493,7 @@ "body": "Traffic has been fully restored to the US West region. This incident is now resolved!", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-22T21:00:56.000Z", "resolved_inferred": false, "started_at": "2026-07-22T15:51:25.000Z", @@ -506,7 +506,7 @@ "body": "We have confirmed full recovery across our BNB Smart Chain Mainnet infrastructure. All nodes are healthy and serving traffic normally, with response times and error rates back to baseline. This incident is now resolved. Thank you for your patience!", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-22T14:43:21.230Z", "resolved_inferred": false, "started_at": "2026-07-22T07:45:25.000Z", @@ -519,7 +519,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-21T22:42:10.724Z", "resolved_inferred": false, "started_at": "2026-07-21T20:49:23.000Z", @@ -532,7 +532,7 @@ "body": "Between approximately 23:20 UTC on July 17 and 03:30 UTC on July 18, some Polygon Mainnet requests experienced slower than normal response times, mainly for log queries. The issue was limited to the us-east-1 region.\nThe cause was an unusually heavy request load that put pressure on part of our infrastructure in the region. We added extra capacity and rebalanced traffic, after which performance returned to normal.\n\nThe issue is fully resolved. We apologize for the disruption.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-17T20:00:00.000Z", "resolved_inferred": false, "started_at": "2026-07-17T20:00:00.000Z", @@ -545,7 +545,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-16T04:51:26.432Z", "resolved_inferred": false, "started_at": "2026-07-16T04:20:09.652Z", @@ -558,7 +558,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-16T04:02:12.215Z", "resolved_inferred": false, "started_at": "2026-07-15T23:09:24.996Z", @@ -571,7 +571,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-15T16:25:34.000Z", "resolved_inferred": false, "started_at": "2026-07-15T16:00:18.451Z", @@ -584,7 +584,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-15T17:15:14.000Z", "resolved_inferred": false, "started_at": "2026-07-15T14:52:44.687Z", @@ -597,7 +597,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-15T16:50:58.316Z", "resolved_inferred": false, "started_at": "2026-07-15T13:17:30.430Z", @@ -610,7 +610,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-15T00:52:00.446Z", "resolved_inferred": false, "started_at": "2026-07-14T23:48:19.491Z", @@ -623,7 +623,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-13T21:13:22.000Z", "resolved_inferred": false, "started_at": "2026-07-13T21:09:02.003Z", @@ -636,7 +636,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-10T16:01:08.269Z", "resolved_inferred": false, "started_at": "2026-07-10T15:16:20.000Z", @@ -649,7 +649,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-10T10:00:00.000Z", "resolved_inferred": false, "started_at": "2026-07-10T10:00:00.000Z", diff --git a/api/v/alert-logic.json b/api/v/alert-logic.json index 71c39c0122cfe076c9cdb17e158fa2a07c885e53..eb3f6d281b507979563c6eb5667392bd20e4bc03 100644 --- a/api/v/alert-logic.json +++ b/api/v/alert-logic.json @@ -3,7 +3,7 @@ "slug": "alert-logic", "platform": "statuspage", "status_url": "https://status.alertlogic.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", diff --git a/api/v/alloy.json b/api/v/alloy.json index e3e62e22757851a908726028763aa050f74d50d6..43180b44fd68265a189518443328abf87061c049 100644 --- a/api/v/alloy.json +++ b/api/v/alloy.json @@ -3,7 +3,7 @@ "slug": "alloy", "platform": "statuspage", "status_url": "https://status.alloy.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "Between 12:45 PM and 1:20 PM ET on August 27, a third-party data provider Threatmetrix experienced a service disruption that caused intermittent connection errors on device intelligence checks. During this window, some evaluations that use impacted service completed as partial rather than returning a full provider response, and some requests saw elevated latency or connector timeouts.\n\n The provider has confirmed the underlying issue is resolved, and error rates returned to normal by 1:20 PM ET. Evaluations submitted outside this window were not affected.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-27T12:45:00.000-04:00", "resolved_inferred": false, "started_at": "2026-08-27T12:45:00.000-04:00", @@ -25,7 +25,7 @@ "body": "Issue have been fully resolved. \nElevated error rates were observed on August 25th between 14:18 and 14:22 PM ET and between 14:29 and 14:35 PM ET", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-25T16:39:35.164-04:00", "resolved_inferred": false, "started_at": "2026-08-25T14:45:06.409-04:00", @@ -38,7 +38,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-20T16:43:02.408-04:00", "resolved_inferred": false, "started_at": "2026-08-20T11:38:04.913-04:00", @@ -51,7 +51,7 @@ "body": "The issue affecting the Journeys API has been fully resolved, and service has returned to normal. We have completed monitoring and confirmed that related dashboard functionality has also recovered as of July 21, 2026 at 5:11 PM ET.\n\nThank you for your patience while we worked to restore service.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-22T11:44:34.905-04:00", "resolved_inferred": false, "started_at": "2026-07-21T13:56:59.694-04:00", @@ -64,7 +64,7 @@ "body": "We have confirmed that login functionality and Application Queues have returned to normal operation, and no further impact is being observed. Thank you for your patience while we worked to resolve this issue.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-17T10:51:17.535-04:00", "resolved_inferred": false, "started_at": "2026-07-17T10:42:41.291-04:00", @@ -77,7 +77,7 @@ "body": "We have seen recovery across the impacted LexisNexis services and error rates has returned to expected levels. This incident is now considered resolved.\n\nWe will continue to work with the LexisNexis team to obtain a Root Cause Analysis (RCA). If you would like to receive a copy of the RCA when it becomes available, please contact support@alloy.com.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-14T15:09:12.325-04:00", "resolved_inferred": false, "started_at": "2026-07-14T11:31:29.627-04:00", @@ -90,7 +90,7 @@ "body": "After further montioring, we have not observed any new errors. All systems are operating normally.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-18T14:27:52.296-04:00", "resolved_inferred": false, "started_at": "2026-06-18T14:03:29.420-04:00", @@ -103,7 +103,7 @@ "body": "Service has returned to normal operation as of 3:36 PM ET, and our monitoring confirms that API performance is stable. We will continue to monitor closely to ensure ongoing reliability.\n\nWe apologize for any disruption this may have caused and appreciate your patience while we worked to resolve the issue.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-11T15:56:40.841-04:00", "resolved_inferred": false, "started_at": "2026-06-11T15:22:42.273-04:00", @@ -116,7 +116,7 @@ "body": "Starting at 9:17 AM ET, the homepage analytics dashboards were not loading as expected. All other dashboard pages and services remained fully operational. As of 11:47 AM ET, the system has recovered and is fully operational.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-08T09:00:00.000-04:00", "resolved_inferred": false, "started_at": "2026-05-08T09:00:00.000-04:00", @@ -129,7 +129,7 @@ "body": "We believe the cause of the latency is resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-07T23:57:46.253-04:00", "resolved_inferred": false, "started_at": "2026-05-07T23:23:46.224-04:00", @@ -142,7 +142,7 @@ "body": "The issue has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-23T11:33:26.193-04:00", "resolved_inferred": false, "started_at": "2026-04-23T10:25:59.879-04:00", @@ -155,7 +155,7 @@ "body": "We recently identified and resolved an issue affecting some plugins initialized through the Alloy SDK.\n\nFor a subset of SDK Plugins, applications initializing the SDK may have experienced unexpected behavior, which could present as UI instability or premature close events.\n\nWe mitigated the issue by rolling back a recent SDK change. Following the rollback, normal plugin behavior was restored.\n\nIf you continue to experience any issues, please contact Alloy Support.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-05T11:00:00.000-05:00", "resolved_inferred": false, "started_at": "2026-03-05T11:00:00.000-05:00", @@ -168,7 +168,7 @@ "body": "Between March 4 at 11:00 PM ET and March 5 at 10:07 AM ET, we experienced an elevated rate of memory-related errors impacting evaluations running through JQ input attributes. As a result, some evaluations returned a null value for the input attribute instead of the correct value, potentially interrupting decisioning in the Workflow. Impacted applications would need to be re-run.\n\nOnly workflows using input attributes with JQ were impacted; other Workflow logic was not impacted.\n\nThe issue has been identified and resolved, and all systems are now operating normally.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-04T23:00:00.000-05:00", "resolved_inferred": false, "started_at": "2026-03-04T23:00:00.000-05:00", @@ -181,7 +181,7 @@ "body": "API functionality has been fully restored. We are continuing to investigate the impact and look into root causes.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-24T05:00:46.000-05:00", "resolved_inferred": false, "started_at": "2026-02-24T04:30:57.000-05:00", @@ -194,7 +194,7 @@ "body": "Realtime webhook processing has been fully restored, and has maintained stability after monitoring. All new webhook events are now completing in realtime as expected. To further strengthen system stability, the engineering team has deployed an additional mitigation to prevent webhook queue backlogging under similar spike conditions.\n\nA thorough postmortem will be completed a Root Cause Analysis (RCA) can be shared with customers - please email support@alloy.com if you would like to receive the RCA. We are also investing in further improvements to the reliability and resiliency of our webhook queueing mechanism in the future to prevent event loss in the future.\n\nPlease note, action is required to ensure applications process: \n\nDuring the incident, webhook events generated between 2:24 PM - 4:38 PM ET and 5:42 - 5:45 ET were not successfully processed and were permanently lost. Webhooks generated outside of this time window were not impacted.\n\nThis issue affects applications that are stuck at a Journey step dependent on an Alloy webhook response to proceed (for example, action nodes), as well as applications that completed with a Manual Review outcome but are not reflecting back in core after review.\n\nApplications submitted during the affected window that are currently blocked due to a missing webhook dependency will need to be replayed. We recommend resubmitting those applications via API. Re-running an application will leverage cached data by default and will not trigger new calls to external data vendors.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-19T20:03:39.360-05:00", "resolved_inferred": false, "started_at": "2026-02-19T15:49:29.100-05:00", @@ -207,7 +207,7 @@ "body": "The root cause has been identified. Response times for the Dashboard and API have returned to normal levels since 3:46 PM ET.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-17T16:14:54.188-05:00", "resolved_inferred": false, "started_at": "2026-02-17T16:03:36.091-05:00", @@ -220,7 +220,7 @@ "body": "Between 11:20 AM and 12:04 PM ET, some workflows returned a 500 error when attempting to save a new version. Existing workflow versions and decisioning on existing workflow versions were not impacted. Once the root cause was identified as a previous code change, the issue was resolved at 12:04 PM ET when the affected change was rolled back, and all functionality related to workflow version saving was fully restored.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-02T12:27:00.937-05:00", "resolved_inferred": false, "started_at": "2026-02-02T12:27:00.881-05:00", @@ -233,7 +233,7 @@ "body": "A fix has been implemented and all systems are operational.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-08T16:30:45.000-05:00", "resolved_inferred": false, "started_at": "2026-01-08T13:43:22.813-05:00", @@ -246,7 +246,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-02T17:05:14.450-05:00", "resolved_inferred": false, "started_at": "2026-01-02T16:15:10.000-05:00", @@ -259,7 +259,7 @@ "body": "The OpenCorporates team has assisted in resolving the issue, and the OpenCorporates data service is now fully operational. Any applications that previously failed due to this incident can now be re-run.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-03T17:51:47.886-05:00", "resolved_inferred": false, "started_at": "2025-12-03T13:37:29.290-05:00", @@ -272,7 +272,7 @@ "body": "Alloy is observing error rates have decreased across all impacted services as of 9:36 AM ET. \n\nCloudFlare has confirmed a fix has been implemented as of 9:42 AM ET. More information about the CloudFlare outage can be found here: https://www.cloudflarestatus.com/incidents/8gmgl950y3h7", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-18T10:08:01.367-05:00", "resolved_inferred": false, "started_at": "2025-11-18T08:37:50.652-05:00", @@ -285,7 +285,7 @@ "body": "Our monitoring confirms that processing has returned to normal. We have not observed any further errors since 12:20 PM ET. Any applications that failed during this period can now be re-run successfully.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-03T12:20:45.000-05:00", "resolved_inferred": false, "started_at": "2025-11-03T12:06:51.937-05:00", @@ -298,7 +298,7 @@ "body": "As of 11:44 PM ET, the webhook backlog has been fully processed, and real-time webhook processing has been restored.\n\nAll major Alloy services are now fully operational, with performance metrics and latency levels remaining stable.\n\nOur teams continue to work closely with AWS and the third-party vendor to complete a comprehensive post-mortem. We will share a Root Cause Analysis (RCA) once that review is finalized. If you\u2019d like to receive the RCA once it's available, please email support@alloy.com\n.\nWe appreciate your patience and understanding throughout this incident.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-20T23:52:17.301-04:00", "resolved_inferred": false, "started_at": "2025-10-20T03:15:20.691-04:00", @@ -311,7 +311,7 @@ "body": "Our monitoring confirms that processing has returned to normal. We have not observed any timeout errors since 6:02 PM ET. Any applications that failed during this period can now be re-run successfully.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-17T18:19:51.869-04:00", "resolved_inferred": false, "started_at": "2025-10-17T18:07:00.973-04:00", @@ -324,7 +324,7 @@ "body": "Our monitoring confirms that processing has returned to normal. We have not observed any further errors since 7:01 PM ET. Any applications that failed during this period can now be re-run successfully.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-17T19:09:49.153-04:00", "resolved_inferred": false, "started_at": "2025-10-17T15:44:22.446-04:00", @@ -337,7 +337,7 @@ "body": "Our monitoring confirms that processing has returned to normal. We have not observed any timeout errors since 4:46 PM ET. Any applications that failed during this period can now be re-run successfully.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-08T17:40:59.204-04:00", "resolved_inferred": false, "started_at": "2025-10-08T16:12:52.000-04:00", @@ -350,7 +350,7 @@ "body": "Our monitoring confirms that processing has returned to normal. We have not observed any timeout errors since 4:46 PM ET. Any applications that failed during this period can now be re-run successfully.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-08T17:41:07.520-04:00", "resolved_inferred": false, "started_at": "2025-10-08T16:12:33.620-04:00", @@ -363,7 +363,7 @@ "body": "Our monitoring confirms that processing has returned to normal. We have not observed any timeout errors since 4:46 PM ET. Any applications that failed during this period can now be re-run successfully.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-08T17:41:14.619-04:00", "resolved_inferred": false, "started_at": "2025-10-08T16:11:40.907-04:00", @@ -376,7 +376,7 @@ "body": "Our SMS vendor has confirmed that around 11:43 AM ET, there were SMS delivery delays when sending messages To T-mobile Network in the USA. They are now observing recovery when sending SMS messages over T-mobile and we\u2019ve received confirmed reports from customers as well.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-29T14:16:31.846-04:00", "resolved_inferred": false, "started_at": "2025-09-29T13:40:09.133-04:00", @@ -389,7 +389,7 @@ "body": "We have detected that calls to Qualifile were failing from 12:01AM ET due to a Qualifile maintenance window. We are monitoring to determine when their system is back up.\n\nWe have confirmed that Qualifile processing has returned to normal. We have not observed any timeout errors since 2:03 PM ET. Any applications that failed during this period can now be re-run successfully.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-21T00:00:00.000-04:00", "resolved_inferred": false, "started_at": "2025-09-21T00:00:00.000-04:00", @@ -402,7 +402,7 @@ "body": "We are resolving this incident after affected customers confirmed that updating their allowlisted domain .*alloy.com in their security vendor restored dashboard access. The issue was limited to customers who control Alloy dashboard access via Allowlisted IPs and use a security vendor that routes traffic over dedicated IPs based on domain.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-20T12:32:04.184-04:00", "resolved_inferred": false, "started_at": "2025-09-19T14:13:44.640-04:00", @@ -415,7 +415,7 @@ "body": "We\u2019ve resolved the issue that was causing the 403 errors, and our systems have returned to normal operations. Thank you for your patience while we worked to address this.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-10T15:49:56.717-04:00", "resolved_inferred": false, "started_at": "2025-09-10T14:55:42.938-04:00", @@ -428,7 +428,7 @@ "body": "Our monitoring confirms that Iovation processing has returned to normal. We have not observed any timeout errors since 3:46 PM ET. Any applications that failed during this period can now be re-run successfully.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-21T17:08:37.508-04:00", "resolved_inferred": false, "started_at": "2025-08-21T14:36:54.000-04:00", @@ -441,7 +441,7 @@ "body": "Between 10:37 AM ET and 12:12 PM ET, requests to ComplyAdvantage had a 206 error, causing evaluations running this service to fail. We identified the root cause and deployed a fix. The issue has been resolved, and evaluations can now be rerun.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-20T10:37:00.000-04:00", "resolved_inferred": false, "started_at": "2025-08-20T10:37:00.000-04:00", @@ -454,7 +454,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-13T18:17:30.713-04:00", "resolved_inferred": false, "started_at": "2025-08-13T18:02:47.906-04:00", @@ -467,7 +467,7 @@ "body": "Iovation failures resolved at 9:52 AM EDT. Any applications that failed during this time can be re-run.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-08T10:16:49.000-04:00", "resolved_inferred": false, "started_at": "2025-08-08T09:55:22.000-04:00", @@ -480,7 +480,7 @@ "body": "An interprocess communication issue resulted in a period of increased API latency and downtime from 12:28 to 12:44 ET (16 minutes). We have remediated the underlying issue and are working on an RCA of the incident now.\n\nAPI issues during this time will appear as either increased latency and/or HTTP 206 response codes. All API requests are retryable and can be retried now.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-05T12:48:02.000-04:00", "resolved_inferred": false, "started_at": "2025-08-05T12:37:40.946-04:00", diff --git a/api/v/alphavps.json b/api/v/alphavps.json index 2058a21ec3808c18c9a2b78c5588dbf364875be5..32edb62c45d818838b6e0f8ed842c7868fb047ec 100644 --- a/api/v/alphavps.json +++ b/api/v/alphavps.json @@ -3,7 +3,7 @@ "slug": "alphavps", "platform": "statuspage", "status_url": "https://status.alphavps.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-21T14:11:04.516+03:00", "resolved_inferred": false, "started_at": "2026-07-30T15:50:58.316+03:00", @@ -25,7 +25,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-09T06:44:11.606+03:00", "resolved_inferred": false, "started_at": "2026-06-29T21:42:41.066+03:00", @@ -38,7 +38,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-30T03:51:51.404+03:00", "resolved_inferred": false, "started_at": "2026-05-27T15:56:03.738+03:00", @@ -51,7 +51,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-30T03:52:06.994+03:00", "resolved_inferred": false, "started_at": "2026-04-07T12:31:31.976+03:00", @@ -64,7 +64,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-26T22:02:26.000+03:00", "resolved_inferred": false, "started_at": "2025-09-23T01:05:32.423+03:00", @@ -77,7 +77,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-04T08:26:59.471+03:00", "resolved_inferred": false, "started_at": "2025-09-04T08:13:28.541+03:00", @@ -90,7 +90,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-03T10:33:23.988+03:00", "resolved_inferred": false, "started_at": "2025-09-03T08:09:55.024+03:00", diff --git a/api/v/amplitude.json b/api/v/amplitude.json index 9fdeb17ac664904b6084be86eab913a865e15f64..376dbab207d05c32cc2504a666d80ee34c911fad 100644 --- a/api/v/amplitude.json +++ b/api/v/amplitude.json @@ -3,7 +3,7 @@ "slug": "amplitude", "platform": "statuspage", "status_url": "https://status.amplitude.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-26T11:38:27.211-07:00", "resolved_inferred": false, "started_at": "2026-08-26T08:23:56.873-07:00", @@ -25,7 +25,7 @@ "body": "Incident timeline\n\nResolved \u2014 Amplitude is accessible once again, and customers should be able to access the platform as expected.\n\nPosted Aug 25, 2026 - 14:03 PT\n\nInvestigating \u2014 Since approximately 13:48 PT, some customers may have experienced a brief interruption when using Amplitude.\n\nPosted Aug 25, 2026 - 13:48 PT\n\nWe apologize for the disruption.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-25T13:48:00.000-07:00", "resolved_inferred": false, "started_at": "2026-08-25T13:48:00.000-07:00", @@ -38,7 +38,7 @@ "body": "A fix was deployed, and the issue was fully resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-24T20:23:01.519-07:00", "resolved_inferred": false, "started_at": "2026-08-24T19:06:37.620-07:00", @@ -51,7 +51,7 @@ "body": "On 2026-08-19 at 10:41:25 AM PT, some customers who had not explicitly enabled AI through the AI Controls page were placed in \u201cAdmin preview,\u201d and non-admin users could not access AI features. The issue was fully resolved at 12:41 PM PT on 2026-08-19. No data was impacted, and no customer action is required. Following the fix, customers should now be able to access Global Chat and see the Global Chat interface instead of the \u201cNo access\u201d message.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-19T10:41:00.000-07:00", "resolved_inferred": false, "started_at": "2026-08-19T10:41:00.000-07:00", @@ -64,7 +64,7 @@ "body": "On 2026-08-13 at 7:45 PM PT (2:45 AM UTC on 2026-08-14), we experienced a data ingestion latency. The issue was fully resolved at 8:35 PM PT (3:35 AM UTC on 2026-08-14), and all data has since been recovered. There was no data loss, and no customer action is required.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-13T19:30:00.000-07:00", "resolved_inferred": false, "started_at": "2026-08-13T19:30:00.000-07:00", @@ -77,7 +77,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-12T20:45:54.905-07:00", "resolved_inferred": false, "started_at": "2026-08-12T16:39:08.000-07:00", @@ -90,7 +90,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-01T23:12:43.160-07:00", "resolved_inferred": false, "started_at": "2026-08-01T22:45:46.343-07:00", @@ -103,7 +103,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-31T20:51:59.748-07:00", "resolved_inferred": false, "started_at": "2026-07-31T19:07:20.532-07:00", @@ -116,7 +116,7 @@ "body": "Between approximately 2026-07-24 03:39\u201305:00 PT (10:39\u201312:00 UTC), some customers may have experienced intermittent connectivity issues while accessing Amplitude or sending data, including connection timeouts. This was caused by an AWS networking disruption in the us-west-2 region affecting multiple upstream AWS services.\n\nThe issue originated outside of Amplitude's infrastructure and was resolved by AWS.\n\nServices:\n- Our SDKs queue undelivered events on-device and automatically retry sending them, so we expect minimal to no data loss from this incident. No ingested data was lost and no action is required.\n- Experiment/Flag evaluations failed and return 503s due to service unavailability. There is no data loss.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-24T10:05:39.000-07:00", "resolved_inferred": false, "started_at": "2026-07-24T10:05:39.000-07:00", @@ -129,7 +129,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-24T08:59:35.307-07:00", "resolved_inferred": false, "started_at": "2026-07-24T07:45:28.683-07:00", @@ -142,7 +142,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-23T10:03:42.394-07:00", "resolved_inferred": false, "started_at": "2026-07-23T07:35:43.063-07:00", @@ -155,7 +155,7 @@ "body": "We identified the source of the issue and rolled back the responsible change at 12:06 PM PT (19:06 UTC). Error rates have returned to normal, and we are actively monitoring to confirm full stability.\n\nThere is no data loss. No customer action is needed at this time.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-22T13:20:59.156-07:00", "resolved_inferred": false, "started_at": "2026-07-22T13:20:59.109-07:00", @@ -168,7 +168,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-13T16:07:58.791-07:00", "resolved_inferred": false, "started_at": "2026-07-13T14:31:53.771-07:00", @@ -181,7 +181,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-13T16:17:08.997-07:00", "resolved_inferred": false, "started_at": "2026-07-13T11:51:09.422-07:00", @@ -194,7 +194,7 @@ "body": "The incident has been resolved and the Custom Metrics metrics details page displays normally now.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-13T07:59:40.179-07:00", "resolved_inferred": false, "started_at": "2026-07-13T04:41:59.470-07:00", @@ -207,7 +207,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-13T01:39:10.911-07:00", "resolved_inferred": false, "started_at": "2026-07-12T23:15:43.000-07:00", @@ -220,7 +220,7 @@ "body": "This incident is resolved. Shared embeds and public links have been stable since 1:50 AM PT (08:50 UTC), and we have verified affected links render normally. A permanent fix ships later today. No data was lost and no customer action is needed.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-09T02:45:56.400-07:00", "resolved_inferred": false, "started_at": "2026-07-09T02:12:47.316-07:00", @@ -233,7 +233,7 @@ "body": "All systems are caught up and functioning normally.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-05T12:11:06.588-07:00", "resolved_inferred": false, "started_at": "2026-07-05T08:56:16.586-07:00", @@ -246,7 +246,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-18T21:30:56.080-07:00", "resolved_inferred": false, "started_at": "2026-06-18T12:29:15.000-07:00", @@ -259,7 +259,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-04T16:05:35.687-07:00", "resolved_inferred": false, "started_at": "2026-06-04T11:55:08.000-07:00", @@ -272,7 +272,7 @@ "body": "Service has been restored for the Amplitude application, and users should now be able to access the application normally.\n\nWe have implemented a fix and are monitoring the system to ensure continued stability. We do not expect any data loss at this time.\n\nThank you for your patience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-03T06:26:38.443-07:00", "resolved_inferred": false, "started_at": "2026-06-03T06:13:13.489-07:00", @@ -285,7 +285,7 @@ "body": "We have resolved the issue affecting the Amplitude application, and services are operating normally again.\n\nWe do not expect any data loss as a result of this incident. Our team will continue to monitor the system to ensure stability.\n\nThank you for your patience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-03T05:52:37.689-07:00", "resolved_inferred": false, "started_at": "2026-06-03T05:25:01.137-07:00", @@ -298,7 +298,7 @@ "body": "The issue causing elevated application latency has been resolved. We have confirmed that system performance has returned to normal levels and continue to monitor closely to ensure ongoing stability.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-21T23:32:06.945-07:00", "resolved_inferred": false, "started_at": "2026-05-21T19:51:02.241-07:00", @@ -311,7 +311,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-19T06:02:42.792-07:00", "resolved_inferred": false, "started_at": "2026-05-19T05:45:51.777-07:00", @@ -324,7 +324,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-14T19:03:53.426-07:00", "resolved_inferred": false, "started_at": "2026-05-14T14:42:22.022-07:00", @@ -337,7 +337,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-05T12:44:54.338-07:00", "resolved_inferred": false, "started_at": "2026-05-05T12:13:50.213-07:00", @@ -350,7 +350,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-29T07:33:06.509-07:00", "resolved_inferred": false, "started_at": "2026-04-29T01:15:23.000-07:00", @@ -363,7 +363,7 @@ "body": "The Amplitude web application in the US was briefly inaccessible. We identified the issue to be related to a misconfigured feature flag. The issue started at 10:00 AM PST, lasting 10 minutes, and is now resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-28T10:00:00.000-07:00", "resolved_inferred": false, "started_at": "2026-04-28T10:00:00.000-07:00", @@ -376,7 +376,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-23T13:32:07.743-07:00", "resolved_inferred": false, "started_at": "2026-04-23T12:56:18.227-07:00", @@ -389,7 +389,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-15T18:11:53.438-07:00", "resolved_inferred": false, "started_at": "2026-04-15T16:09:27.612-07:00", @@ -402,7 +402,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-13T14:00:56.162-07:00", "resolved_inferred": false, "started_at": "2026-04-13T08:45:16.000-07:00", @@ -415,7 +415,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-12T03:52:44.330-07:00", "resolved_inferred": false, "started_at": "2026-04-12T01:24:36.041-07:00", @@ -428,7 +428,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-06T17:48:17.296-07:00", "resolved_inferred": false, "started_at": "2026-04-06T12:53:19.789-07:00", @@ -441,7 +441,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-03T16:52:18.005-07:00", "resolved_inferred": false, "started_at": "2026-04-03T14:52:01.000-07:00", @@ -454,7 +454,7 @@ "body": "We have fixed the issue", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-27T10:11:41.283-07:00", "resolved_inferred": false, "started_at": "2026-03-27T08:52:20.381-07:00", @@ -467,7 +467,7 @@ "body": "Some Flags and experiments that were targeting cohorts did not evaluate users into control and treatment correctly. This has been fixed", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-26T20:00:00.000-07:00", "resolved_inferred": false, "started_at": "2026-03-26T17:00:00.000-07:00", @@ -480,7 +480,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-25T11:09:09.739-07:00", "resolved_inferred": false, "started_at": "2026-03-25T11:00:50.187-07:00", @@ -493,7 +493,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-20T13:00:11.935-07:00", "resolved_inferred": false, "started_at": "2026-03-20T10:31:36.152-07:00", @@ -506,7 +506,7 @@ "body": "Duration: March 16, 2026, 11:20 AM PT to 1:17 PM PT\n\nBetween 11:20 AM PT and 1:17 PM PT, the Experiment Evaluation Service experienced a partial outage, resulting in elevated 500, 502, and 503 errors for some requests. Our team has successfully resolved the issue, and the service is now operating normally. We apologize for any inconvenience this disruption may have caused.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-16T13:55:39.780-07:00", "resolved_inferred": false, "started_at": "2026-03-16T13:55:39.724-07:00", @@ -519,7 +519,7 @@ "body": "Between 2026-03-16 08:57 AM PT (15:57 UTC) and 09:23 AM PT (16:23 UTC), some Amplitude users experienced intermittent 500 errors when loading charts, dashboards, and reports in Analytics and Experiment.\n\nA second brief interruption occurred at approximately 09:49 AM PT (16:49 UTC), during which some requests again returned 500 errors.\n\nThe issue was caused by a temporary database disruption that has since automatically recovered. Our team has confirmed that services are operating normally. No data loss occurred, and no customer action is needed.\n\nWe are actively investigating the root cause to prevent recurrence and will continue to monitor the system.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-16T09:00:00.000-07:00", "resolved_inferred": false, "started_at": "2026-03-16T09:00:00.000-07:00", @@ -532,7 +532,7 @@ "body": "A migration to transition some Growth orgs to a new permission system, which is activated by a feature flag, did not operate correctly, resulting in the appearance of lost role assignments for users. This affected some Growth orgs that have project-based permissions. Removing the feature flag for these orgs reverted them to the old permission system, restoring all role assignments correctly.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-10T09:00:00.000-07:00", "resolved_inferred": false, "started_at": "2026-03-10T09:00:00.000-07:00", @@ -545,7 +545,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-02T20:46:37.680-08:00", "resolved_inferred": false, "started_at": "2026-03-02T18:53:37.824-08:00", @@ -558,7 +558,7 @@ "body": "As of 3:10 PM PT, we have fully recovered and all systems are operating normally.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-27T15:47:57.347-08:00", "resolved_inferred": false, "started_at": "2026-02-27T14:22:46.000-08:00", @@ -571,7 +571,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-26T14:58:51.003-08:00", "resolved_inferred": false, "started_at": "2026-02-26T12:48:20.886-08:00", @@ -584,7 +584,7 @@ "body": "This incident has been resolved. The bug was isolated to a permissions issue with Amplitude users and did not impact any data ingestion, experiments, or other features. All user permissions should be back to operational.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-12T15:49:32.919-08:00", "resolved_inferred": false, "started_at": "2026-02-12T15:19:05.168-08:00", @@ -597,7 +597,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-20T19:07:13.727-08:00", "resolved_inferred": false, "started_at": "2026-01-20T12:05:34.000-08:00", @@ -610,7 +610,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-08T09:17:41.960-08:00", "resolved_inferred": false, "started_at": "2026-01-08T06:07:32.961-08:00", @@ -623,7 +623,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-10T00:46:00.275-08:00", "resolved_inferred": false, "started_at": "2025-12-09T19:40:30.695-08:00", @@ -636,7 +636,7 @@ "body": "As of Nov 22, 2025 14:00 UTC, this incident is resolved and customers should be able to see all historical data. Please reach out to support if you're still seeing gaps in your historical data.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-22T09:07:04.218-08:00", "resolved_inferred": false, "started_at": "2025-11-21T15:40:16.877-08:00", @@ -649,7 +649,7 @@ "body": "Amplitude's user interface and data ingestion were not impacted by the recent Cloudflare outage. However, your downstream destinations may have been impacted and we recommend checking with your vendor's status page to confirm impact.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-17T03:30:00.000-08:00", "resolved_inferred": false, "started_at": "2025-11-17T03:30:00.000-08:00", diff --git a/api/v/amsoil-inc.json b/api/v/amsoil-inc.json index cab17b7d8ef6635a9ff8a3048e8797fcbed968c5..c22306f63c02c578f6d1c433cf36845aa1b59cb4 100644 --- a/api/v/amsoil-inc.json +++ b/api/v/amsoil-inc.json @@ -3,7 +3,7 @@ "slug": "amsoil-inc", "platform": "statuspage", "status_url": "https://status.amsoil.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-29T11:03:36.517-05:00", "resolved_inferred": false, "started_at": "2026-05-27T15:09:52.416-05:00", @@ -25,7 +25,7 @@ "body": "We have successfully resolved the issue causing degraded performance at AMSOIL.com and AMSOIL.ca. We apologize for any inconvenience this may have caused. \nSincerely, \n\nAMSOIL INC.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-18T09:03:39.127-06:00", "resolved_inferred": false, "started_at": "2025-11-18T08:22:58.379-06:00", diff --git a/api/v/anchor-host.json b/api/v/anchor-host.json index 390187ccea7f06a7c571e44f6cb00a38561092ae..edf6a2c353991c0ce7c2eae107ae07d388489a26 100644 --- a/api/v/anchor-host.json +++ b/api/v/anchor-host.json @@ -3,7 +3,7 @@ "slug": "anchor-host", "platform": "statuspage", "status_url": "https://anchorhost.statuspage.io", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "WP Rocket doesn't have a patch yet so we patched it directly with our v3.23.2.2. All customers affected with the WP Rocket + WordPress 7.1 compatible issue should be restored. Whenever WP Rocket does release an official fix, customers should automatically upgrade to that.\n\nThere were a few other plugins with similar compatible issues with v7.1. Reviewing and fixing as I discover them.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-19T17:54:39.976-04:00", "resolved_inferred": false, "started_at": "2026-08-19T17:31:57.739-04:00", @@ -25,7 +25,7 @@ "body": "The server has been stabilized. All customer websites should be restored.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-01T15:16:58.525-04:00", "resolved_inferred": false, "started_at": "2026-04-01T14:30:24.973-04:00", @@ -38,7 +38,7 @@ "body": "All customer website appears to be restored and healthy. Will continue to monitor the Cloudflare situation: https://www.cloudflarestatus.com/incidents/8gmgl950y3h7.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-18T09:57:00.361-05:00", "resolved_inferred": false, "started_at": "2025-11-18T08:17:48.295-05:00", diff --git a/api/v/anthropic.json b/api/v/anthropic.json index 914e3f8a2c7698dc1ef69854beba538519374224..f92da3538fc4c31e506729a7b7844204f8c9c78f 100644 --- a/api/v/anthropic.json +++ b/api/v/anthropic.json @@ -3,7 +3,7 @@ "slug": "anthropic", "platform": "statuspage", "status_url": "https://status.anthropic.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:16:22Z", @@ -12,7 +12,7 @@ "body": "The issue affecting Claude Mythos 5.1, Claude Fable 5.1, and Claude Opus 5 has been resolved. Impact has ended as of 9:16 PT / 16:16 UTC.", "first_seen": "2026-09-04T07:16:22Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-09-03T16:23:12.052Z", "resolved_inferred": false, "started_at": "2026-09-03T13:26:04.201Z", @@ -25,7 +25,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:16:22Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-09-03T12:56:26.632Z", "resolved_inferred": false, "started_at": "2026-09-03T12:37:31.766Z", @@ -38,7 +38,7 @@ "body": "The issue affecting Claude Sonnet 5 has been resolved. Impact occurred from 2:05pm PT / 21:05 UTC to 2:19pm PT / 21:19 UTC.", "first_seen": "2026-09-04T07:16:22Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-09-02T21:44:28.095Z", "resolved_inferred": false, "started_at": "2026-09-02T21:17:58.704Z", @@ -51,7 +51,7 @@ "body": "This issue has been resolved.", "first_seen": "2026-09-04T07:16:22Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-09-02T01:24:22.251Z", "resolved_inferred": false, "started_at": "2026-09-01T23:26:48.992Z", @@ -64,7 +64,7 @@ "body": "This issue has been resolved.", "first_seen": "2026-09-04T07:16:22Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-09-01T18:07:03.372Z", "resolved_inferred": false, "started_at": "2026-09-01T17:05:11.462Z", @@ -77,7 +77,7 @@ "body": "This issue has been resolved.", "first_seen": "2026-09-04T07:16:22Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-09-01T16:22:19.479Z", "resolved_inferred": false, "started_at": "2026-09-01T16:02:48.681Z", @@ -90,7 +90,7 @@ "body": "The issue affecting Claude Code has been resolved. Impact occurred from 16\u223655 to 19\u223616 UTC.", "first_seen": "2026-09-04T07:16:22Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-31T20:36:00.297Z", "resolved_inferred": false, "started_at": "2026-08-31T19:21:32.139Z", @@ -103,7 +103,7 @@ "body": "This issue has been resolved.", "first_seen": "2026-09-04T07:16:22Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-31T17:52:26.026Z", "resolved_inferred": false, "started_at": "2026-08-31T17:23:06.241Z", @@ -116,7 +116,7 @@ "body": "The issue affecting Claude Cowork and Claude Code on the web has been resolved.", "first_seen": "2026-09-04T07:16:22Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-28T20:21:18.448Z", "resolved_inferred": false, "started_at": "2026-08-28T17:22:02.377Z", @@ -129,7 +129,7 @@ "body": "This issue has been resolved.", "first_seen": "2026-09-04T07:16:22Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-24T20:26:21.577Z", "resolved_inferred": false, "started_at": "2026-08-24T20:11:23.934Z", @@ -142,7 +142,7 @@ "body": "This issue has been resolved.", "first_seen": "2026-09-04T07:16:22Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-24T17:16:02.904Z", "resolved_inferred": false, "started_at": "2026-08-24T17:12:42.200Z", @@ -155,7 +155,7 @@ "body": "This issue has been resolved. From 9:50pm PT / 04:50 UTC through 00:36am PT / 07:36 UTC, users saw elevated errors on requests to Claude models, including Claude Opus 5 and Fable 5.", "first_seen": "2026-09-04T07:16:22Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-24T08:30:47.615Z", "resolved_inferred": false, "started_at": "2026-08-24T05:06:39.493Z", @@ -168,7 +168,7 @@ "body": "This issue has been resolved.", "first_seen": "2026-09-04T07:16:22Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-20T19:42:38.692Z", "resolved_inferred": false, "started_at": "2026-08-20T19:16:24.932Z", @@ -181,7 +181,7 @@ "body": "This issue has been resolved.", "first_seen": "2026-09-04T07:16:22Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-20T19:01:03.844Z", "resolved_inferred": false, "started_at": "2026-08-20T18:32:13.296Z", @@ -194,7 +194,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:16:22Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-19T11:02:18.264Z", "resolved_inferred": false, "started_at": "2026-08-19T09:42:37.414Z", @@ -207,7 +207,7 @@ "body": "The issue affecting Claude Opus 5 has been resolved. Impact occurred from 16:11 to 18:23 UTC.", "first_seen": "2026-09-04T07:16:22Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-18T19:01:45.447Z", "resolved_inferred": false, "started_at": "2026-08-18T16:20:22.240Z", @@ -220,7 +220,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:16:22Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-17T15:29:25.545Z", "resolved_inferred": false, "started_at": "2026-08-17T13:56:41.055Z", @@ -233,7 +233,7 @@ "body": "The issue affecting claude.ai, platform.claude.com, the Claude API, Claude Code, and Claude Cowork has been resolved.", "first_seen": "2026-09-04T07:16:22Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-16T22:34:39.037Z", "resolved_inferred": false, "started_at": "2026-08-16T21:58:56.949Z", @@ -246,7 +246,7 @@ "body": "The issue affecting Claude services has been resolved. Impact occurred from 20:00 Aug 14, 2026 to 00:11 Aug 15 , 2026 UTC.", "first_seen": "2026-09-04T07:16:22Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-15T00:27:36.893Z", "resolved_inferred": false, "started_at": "2026-08-14T23:57:16.567Z", @@ -259,7 +259,7 @@ "body": "The issue affecting the Claude API, Claude Code, and Claude Cowork has been resolved. Impact occurred from 20:14 to 20:38 UTC.", "first_seen": "2026-09-04T07:16:22Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-14T21:58:12.691Z", "resolved_inferred": false, "started_at": "2026-08-14T20:30:36.289Z", @@ -272,7 +272,7 @@ "body": "The issue resulting in users being unable to reach status.claude.com has been resolved.", "first_seen": "2026-09-04T07:16:22Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-14T10:53:22.898Z", "resolved_inferred": false, "started_at": "2026-08-14T07:58:11.620Z", @@ -285,7 +285,7 @@ "body": "The issue affecting Claude services has been resolved. Impact occurred from 23:42 to 00:50 UTC.", "first_seen": "2026-09-04T07:16:22Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-14T00:51:24.100Z", "resolved_inferred": false, "started_at": "2026-08-14T00:36:42.423Z", @@ -298,7 +298,7 @@ "body": "The issue affecting Claude Mythos 5 and Claude Fable 5 has been resolved.", "first_seen": "2026-09-04T07:16:22Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-13T16:08:35.730Z", "resolved_inferred": false, "started_at": "2026-08-13T14:33:45.159Z", @@ -311,7 +311,7 @@ "body": "This issue has been resolved.", "first_seen": "2026-09-04T07:16:22Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-12T18:07:11.547Z", "resolved_inferred": false, "started_at": "2026-08-12T13:50:28.458Z", @@ -324,7 +324,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:16:22Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-05T14:34:15.264Z", "resolved_inferred": false, "started_at": "2026-08-05T13:51:30.287Z", @@ -337,7 +337,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:16:22Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-05T14:14:36.006Z", "resolved_inferred": false, "started_at": "2026-08-05T07:05:54.000Z", @@ -350,7 +350,7 @@ "body": "This issue has been resolved.", "first_seen": "2026-09-04T07:16:22Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-04T21:59:29.385Z", "resolved_inferred": false, "started_at": "2026-08-04T20:48:20.773Z", @@ -363,7 +363,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:16:22Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-04T11:52:10.820Z", "resolved_inferred": false, "started_at": "2026-08-04T11:27:20.691Z", @@ -376,7 +376,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:16:22Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-04T06:55:43.194Z", "resolved_inferred": false, "started_at": "2026-08-04T06:16:33.847Z", @@ -389,7 +389,7 @@ "body": "As of 15:20 UTC (8:20am PT), error rates on Claude Sonnet 5 have returned to baseline. This incident is resolved.", "first_seen": "2026-09-04T07:16:22Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-03T15:29:01.564Z", "resolved_inferred": false, "started_at": "2026-08-03T15:13:45.862Z", @@ -402,7 +402,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:16:22Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-03T14:17:14.797Z", "resolved_inferred": false, "started_at": "2026-08-03T12:52:52.852Z", @@ -415,7 +415,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:16:22Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-31T07:04:49.691Z", "resolved_inferred": false, "started_at": "2026-07-31T06:18:08.068Z", @@ -428,7 +428,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:16:22Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-30T14:24:12.155Z", "resolved_inferred": false, "started_at": "2026-07-30T13:43:19.847Z", @@ -441,7 +441,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:16:22Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-30T10:48:56.631Z", "resolved_inferred": false, "started_at": "2026-07-30T05:57:43.524Z", @@ -454,7 +454,7 @@ "body": "This issue has been resolved.", "first_seen": "2026-09-04T07:16:22Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-29T22:36:20.701Z", "resolved_inferred": false, "started_at": "2026-07-29T19:49:45.388Z", @@ -467,7 +467,7 @@ "body": "As of 7:34 PST / 14:34 UTC the errors have returned to baseline.", "first_seen": "2026-09-04T07:16:22Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-27T14:36:43.730Z", "resolved_inferred": false, "started_at": "2026-07-27T13:39:52.265Z", @@ -480,7 +480,7 @@ "body": "As of 4:47 PST / 11:47 UTC the errors have returned to baseline.", "first_seen": "2026-09-04T07:16:22Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-27T12:30:22.946Z", "resolved_inferred": false, "started_at": "2026-07-27T11:27:38.071Z", @@ -493,7 +493,7 @@ "body": "As of 2:03 PST / 9:03 UTC the errors have returned to baseline.", "first_seen": "2026-09-04T07:16:22Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-27T09:05:24.911Z", "resolved_inferred": false, "started_at": "2026-07-27T08:16:57.590Z", @@ -506,7 +506,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:16:22Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-26T10:44:14.944Z", "resolved_inferred": false, "started_at": "2026-07-26T09:17:12.697Z", @@ -519,7 +519,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:16:22Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-25T22:08:41.677Z", "resolved_inferred": false, "started_at": "2026-07-25T21:34:51.173Z", @@ -532,7 +532,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:16:22Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-25T19:44:32.851Z", "resolved_inferred": false, "started_at": "2026-07-25T18:40:31.869Z", @@ -545,7 +545,7 @@ "body": "For approximately 10 minutes, error rates on Sonnet 4.6 and 5 were elevated. Service returned to normal at approximately 11:07a PDT.", "first_seen": "2026-09-04T07:16:22Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-25T18:13:01.000Z", "resolved_inferred": false, "started_at": "2026-07-25T18:13:01.000Z", @@ -558,7 +558,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:16:22Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-24T10:22:06.541Z", "resolved_inferred": false, "started_at": "2026-07-24T09:09:56.943Z", @@ -571,7 +571,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:16:22Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-23T00:10:17.291Z", "resolved_inferred": false, "started_at": "2026-07-22T23:52:59.578Z", @@ -584,7 +584,7 @@ "body": "This issue has been resolved.", "first_seen": "2026-09-04T07:16:22Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-24T15:36:54.682Z", "resolved_inferred": false, "started_at": "2026-07-22T17:56:10.087Z", @@ -597,7 +597,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:16:22Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-22T17:45:37.482Z", "resolved_inferred": false, "started_at": "2026-07-22T17:27:36.523Z", @@ -610,7 +610,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:16:22Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-22T16:12:32.364Z", "resolved_inferred": false, "started_at": "2026-07-22T15:24:05.453Z", @@ -623,7 +623,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:16:22Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-22T15:23:37.914Z", "resolved_inferred": false, "started_at": "2026-07-22T13:37:28.237Z", @@ -636,7 +636,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:16:22Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-22T09:00:25.206Z", "resolved_inferred": false, "started_at": "2026-07-22T08:34:31.885Z", @@ -649,7 +649,7 @@ "body": "From 8:28am PT / 15:28 UTC through 9:26am PT / 16:26 UTC users experienced elevated errors on requests to multiple Claude models. This issue has been resolved.", "first_seen": "2026-09-04T07:16:22Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-21T18:18:55.036Z", "resolved_inferred": false, "started_at": "2026-07-21T15:35:03.996Z", diff --git a/api/v/apaleo.json b/api/v/apaleo.json index bd1dec698233861c40a12744c4051813bd83d9c8..28b1b571335cd24ca548d1bb2c0def9daae6177a 100644 --- a/api/v/apaleo.json +++ b/api/v/apaleo.json @@ -3,7 +3,7 @@ "slug": "apaleo", "platform": "statuspage", "status_url": "https://status.apaleo.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "Systems have been stable and working correctly for over 1 hour. We continue monitoring.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-27T17:44:44.515Z", "resolved_inferred": false, "started_at": "2026-08-27T13:30:00.392Z", @@ -25,7 +25,7 @@ "body": "Between 11:10 and 11:35 UTC (13:10\u201313:35 CEST), some users may have experienced errors when signing in via SSO. The issue was intermittent and affected only SSO-based authentication. Sign-ins using other authentication methods were not impacted and continued to work normally. The problem has since been resolved, and SSO login is now operating as expected. Users who were affected should now be able to log in without issue. We apologize for any inconvenience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-11T11:00:00.000Z", "resolved_inferred": false, "started_at": "2026-08-11T11:00:00.000Z", @@ -38,7 +38,7 @@ "body": "An update was deployed that has improved the performance.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-20T13:09:08.296Z", "resolved_inferred": false, "started_at": "2026-07-20T11:21:02.635Z", @@ -51,7 +51,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-30T17:59:18.327Z", "resolved_inferred": false, "started_at": "2026-06-30T16:34:06.170Z", @@ -64,7 +64,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-05T10:55:17.567Z", "resolved_inferred": false, "started_at": "2026-05-05T10:16:39.868Z", @@ -77,7 +77,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-10T15:38:24.450Z", "resolved_inferred": false, "started_at": "2026-03-10T08:27:58.427Z", @@ -90,7 +90,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-09T16:52:12.451Z", "resolved_inferred": false, "started_at": "2026-03-09T16:26:10.470Z", @@ -103,7 +103,7 @@ "body": "All pending night audits have now been successfully processed, and systems are operating normally. Our team will continue to monitor to ensure stability.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-06T10:39:41.476Z", "resolved_inferred": false, "started_at": "2026-03-06T08:21:53.631Z", @@ -116,7 +116,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-21T00:53:24.158Z", "resolved_inferred": false, "started_at": "2026-02-21T00:36:07.850Z", @@ -129,7 +129,7 @@ "body": "We experienced an infrastructure failover on a backend system, the issue has been resolved and delayed processing has been caught up.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-20T19:00:00.000Z", "resolved_inferred": false, "started_at": "2026-02-20T19:00:00.000Z", @@ -142,7 +142,7 @@ "body": "All systems are working nominally, any webhook delays cleared.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-17T22:14:40.744Z", "resolved_inferred": false, "started_at": "2026-02-17T21:39:12.069Z", @@ -155,7 +155,7 @@ "body": "A transient issue affecting both the UI and API layers resulted in incorrect permission-related messages being returned. The issue was resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-11T15:50:00.000Z", "resolved_inferred": false, "started_at": "2026-02-11T14:30:00.000Z", @@ -168,7 +168,7 @@ "body": "We experienced a technical issue with GET /finance/v1/folios endpoint that has now been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-29T09:00:00.000Z", "resolved_inferred": false, "started_at": "2026-01-29T09:00:00.000Z", @@ -181,7 +181,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-18T17:53:35.064Z", "resolved_inferred": false, "started_at": "2025-11-18T13:23:45.598Z", @@ -194,7 +194,7 @@ "body": "For approx. 20 minutes", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-05T08:30:00.000Z", "resolved_inferred": false, "started_at": "2025-11-05T08:30:00.000Z", @@ -207,7 +207,7 @@ "body": "We continue to monitor", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-23T14:41:10.691Z", "resolved_inferred": false, "started_at": "2025-10-23T11:30:50.000Z", @@ -220,7 +220,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-01T12:12:51.367Z", "resolved_inferred": false, "started_at": "2025-10-01T09:03:22.776Z", @@ -233,7 +233,7 @@ "body": "Webhook delivery performance has returned to normal, and the vast majority of events are now processing on time. We consider this incident resolved, but our team will continue to monitor the system to ensure sustained stability.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-22T08:51:18.823Z", "resolved_inferred": false, "started_at": "2025-08-20T09:12:25.970Z", @@ -246,7 +246,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-07T12:06:34.168Z", "resolved_inferred": false, "started_at": "2025-08-07T11:24:18.838Z", diff --git a/api/v/api-video.json b/api/v/api-video.json index a2a2542f149d8cc87e73243f6925b958e5c8fcff..703d74b6631318cac3f4eff7003fd98f7550f7cb 100644 --- a/api/v/api-video.json +++ b/api/v/api-video.json @@ -3,7 +3,7 @@ "slug": "api-video", "platform": "statuspage", "status_url": "https://status.api.video", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "The issue affecting the Analytics database has been resolved, and all Analytics services are now fully operational.\nData retrieval through both the dashboard and API has been restored. \nThank you for your patience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-21T07:33:01.055Z", "resolved_inferred": false, "started_at": "2026-07-20T09:32:02.667Z", @@ -25,7 +25,7 @@ "body": "The issue affecting our database has been resolved, and all services are operating normally again.\nThe incident was caused by an issue with our database provider, which has since been resolved. We appreciate your patience while we worked with our provider to restore full service.\nThank you for your understanding. If you continue to experience any issues, please contact our support team.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-20T06:59:38.308Z", "resolved_inferred": false, "started_at": "2026-07-19T17:27:47.137Z", @@ -38,7 +38,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-07T10:37:55.637Z", "resolved_inferred": false, "started_at": "2026-07-07T08:06:28.819Z", @@ -51,7 +51,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-06T15:07:21.121Z", "resolved_inferred": false, "started_at": "2026-07-06T12:35:55.428Z", @@ -64,7 +64,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-09T08:54:27.164Z", "resolved_inferred": false, "started_at": "2026-06-09T07:48:22.189Z", @@ -77,7 +77,7 @@ "body": "The encoding queue has been fully processed and the pipeline is now operating normally. All pending videos have been cleared, and processing times have returned to the standard latency. No further delays are expected at this time.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-27T09:02:13.110Z", "resolved_inferred": false, "started_at": "2026-04-27T08:33:32.257Z", @@ -90,7 +90,7 @@ "body": "A service disruption occurred due to an unexpected underlying infrastructure malfunction.\nWe apologize for any inconvenience caused and appreciate your understanding.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-13T12:03:03.274Z", "resolved_inferred": false, "started_at": "2026-04-13T09:36:26.000Z", @@ -103,7 +103,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-26T13:30:18.993Z", "resolved_inferred": false, "started_at": "2026-03-26T13:07:15.511Z", @@ -116,7 +116,7 @@ "body": "This incident has been resolved.\nHeavy traffic on our database servers caused access issues to our content delivery servers and affected the dashboard.\nWe sincerely apologize for the outage and any inconvenience this may have caused.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-23T12:21:50.590Z", "resolved_inferred": false, "started_at": "2026-03-23T10:13:52.657Z", @@ -129,7 +129,7 @@ "body": "A network-related issue caused DNS resolution failures for some of our internal services, which affected service availability for a significant portion of users during 55 minutes.\nOur team identified the root cause, resolved the network/DNS issue, and services are now fully restored.\nWe apologize for the disruption and appreciate your patience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-11T20:12:45.159Z", "resolved_inferred": false, "started_at": "2026-03-11T19:21:00.437Z", @@ -142,7 +142,7 @@ "body": "Queue has been treated, service is back to normal.\nAn hypervisor failure was identified has the root cause of the slowdown", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-10T10:58:34.666Z", "resolved_inferred": false, "started_at": "2025-12-10T10:09:12.460Z", @@ -155,7 +155,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-02T17:19:06.216Z", "resolved_inferred": false, "started_at": "2025-12-02T07:43:27.336Z", @@ -168,7 +168,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-05T08:54:12.654Z", "resolved_inferred": false, "started_at": "2025-11-05T07:49:37.999Z", @@ -181,7 +181,7 @@ "body": "The service has fully recovered. Performances have been optimal since 18:00 UTC.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-18T19:11:21.532Z", "resolved_inferred": false, "started_at": "2025-10-17T16:35:20.239Z", @@ -194,7 +194,7 @@ "body": "The incident has been resolved.\nPending tasks are being processed.\nWe apologize for any inconvenience caused.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-30T09:32:50.264Z", "resolved_inferred": false, "started_at": "2025-09-30T09:13:00.400Z", @@ -207,7 +207,7 @@ "body": "The storage has fully recover. The VOD ingest and delivery service are operational since 18:09 UTC.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-02T18:21:36.842Z", "resolved_inferred": false, "started_at": "2025-09-02T16:33:32.182Z", diff --git a/api/v/apify.json b/api/v/apify.json index cea7d1a1195c19a933285a1e5588c127a37a0e05..fcf40c1ce373624d5183f2f8502ea15b217800ed 100644 --- a/api/v/apify.json +++ b/api/v/apify.json @@ -3,7 +3,7 @@ "slug": "apify", "platform": "statuspage", "status_url": "https://status.apify.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-20T18:14:23.779+02:00", "resolved_inferred": false, "started_at": "2026-08-20T16:05:26.370+02:00", @@ -25,7 +25,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-14T16:05:05.683+02:00", "resolved_inferred": false, "started_at": "2026-08-13T17:38:56.958+02:00", @@ -38,7 +38,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-08T20:59:11.474+02:00", "resolved_inferred": false, "started_at": "2026-08-07T23:00:02.249+02:00", @@ -51,7 +51,7 @@ "body": "The Google SERP Proxy is stabilized, and we continue to monitor its performance.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-05T15:30:14.000+02:00", "resolved_inferred": false, "started_at": "2026-08-04T01:56:45.122+02:00", @@ -64,7 +64,7 @@ "body": "The problem has been resolved. Impact was an increased error rate at the Actor Standby API, not other component was affected. There was no downtime during the period of the incident.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-26T09:57:43.065+02:00", "resolved_inferred": false, "started_at": "2026-07-26T08:53:28.418+02:00", @@ -77,7 +77,7 @@ "body": "The database is fully recovered, and all systems are operational. We apologize for any inconvenience this might have caused. We are currently implementing new measures to ensure this won't happen again.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-22T04:38:42.765+02:00", "resolved_inferred": false, "started_at": "2026-07-21T16:49:36.548+02:00", @@ -90,7 +90,7 @@ "body": "All systems are operational, and we apologize for any inconvenience this might have caused.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-21T13:53:36.743+02:00", "resolved_inferred": false, "started_at": "2026-07-21T08:52:32.166+02:00", @@ -103,7 +103,7 @@ "body": "The issue has been resolved.\nBoth the response time and success rate have returned to normal levels.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-17T22:08:31.551+02:00", "resolved_inferred": false, "started_at": "2026-07-17T16:04:46.135+02:00", @@ -116,7 +116,7 @@ "body": "Webhooks are operational, and we apologize for any inconvenience this might have caused.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-04T19:07:34.129+02:00", "resolved_inferred": false, "started_at": "2026-06-04T17:07:50.012+02:00", @@ -129,7 +129,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-16T07:28:09.245+02:00", "resolved_inferred": false, "started_at": "2026-05-15T13:48:36.116+02:00", @@ -142,7 +142,7 @@ "body": "We experienced degraded performance on our proxy due to an unexpected increase in load. This caused slower response times for some users.\n\nThe issue lasted approximately 5 minutes and has been fully resolved. All systems are now operating normally.\n\nWe apologize for the inconvenience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-14T09:20:00.000+02:00", "resolved_inferred": false, "started_at": "2026-05-14T07:20:00.000+02:00", @@ -155,7 +155,7 @@ "body": "We have implemented a fix for the OAuth flow, and the connections are now working normally.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-07T10:27:00.250+02:00", "resolved_inferred": false, "started_at": "2026-05-06T22:08:34.494+02:00", @@ -168,7 +168,7 @@ "body": "We've resolved an issue where a key-value store API update caused some Actor runs to time out.\n\nIf your Actor run timed out you can get it back by resurrecting it. There was no data loss.\n\nWe sincerely apologize for any inconvenience this may have caused.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-05T16:34:55.748+02:00", "resolved_inferred": false, "started_at": "2026-05-05T15:50:20.781+02:00", @@ -181,7 +181,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-01T13:57:11.814+02:00", "resolved_inferred": false, "started_at": "2026-05-01T13:23:58.449+02:00", @@ -194,7 +194,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-29T17:13:32.497+02:00", "resolved_inferred": false, "started_at": "2026-04-29T14:35:09.564+02:00", @@ -207,7 +207,7 @@ "body": "All systems are operational, and we apologize for any inconvenience this might have caused. We are currently implementing new measures to make sure that this won't happen again.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-09T11:15:57.630+02:00", "resolved_inferred": false, "started_at": "2026-04-08T12:01:20.919+02:00", @@ -220,7 +220,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-12T10:34:56.026+01:00", "resolved_inferred": false, "started_at": "2026-03-11T13:48:42.994+01:00", @@ -233,7 +233,7 @@ "body": "Datacenter proxy performance has been fully restored.\nWe apologize for any inconvenience this may have caused.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-06T20:05:09.355+01:00", "resolved_inferred": false, "started_at": "2026-03-06T18:27:45.340+01:00", @@ -246,7 +246,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-27T10:37:36.015+01:00", "resolved_inferred": false, "started_at": "2026-01-27T05:10:23.229+01:00", @@ -259,7 +259,7 @@ "body": "All systems are operational, and we apologize for any inconvenience this might have caused. We are currently implementing new measures to make sure that this won't happen again.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-21T16:19:46.721+01:00", "resolved_inferred": false, "started_at": "2026-01-21T16:17:28.000+01:00", @@ -272,7 +272,7 @@ "body": "A fix has been implemented, and Apify Store is back to normal operations.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-12T09:58:12.130+01:00", "resolved_inferred": false, "started_at": "2026-01-12T09:22:09.053+01:00", @@ -285,7 +285,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-09T22:13:37.064+01:00", "resolved_inferred": false, "started_at": "2026-01-09T21:26:39.377+01:00", @@ -298,7 +298,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-31T11:50:03.495+01:00", "resolved_inferred": false, "started_at": "2025-12-31T11:31:49.397+01:00", @@ -311,7 +311,7 @@ "body": "The issue affecting the creation of new Actors from Actor templates has now been fully resolved.\nService is operating normally again.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-11T18:26:25.056+01:00", "resolved_inferred": false, "started_at": "2025-12-11T15:56:27.440+01:00", @@ -324,7 +324,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-29T21:21:34.133+01:00", "resolved_inferred": false, "started_at": "2025-10-29T20:06:38.973+01:00", @@ -337,7 +337,7 @@ "body": "As of 07:30 UTC, the Apify platform is operating normally. Amazon Web Services have also marked their incident as resolved, which gives us confidence that the outage has concluded. We will continue to monitor the situation and apologize for any inconvenience this may have caused.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-21T09:30:06.000+02:00", "resolved_inferred": false, "started_at": "2025-10-20T16:42:47.133+02:00", @@ -350,7 +350,7 @@ "body": "All systems are operational, and we apologize for any inconvenience this might have caused. We are currently implementing new measures to make sure that this won't happen again.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-20T16:40:57.916+02:00", "resolved_inferred": false, "started_at": "2025-10-20T09:00:17.000+02:00", @@ -363,7 +363,7 @@ "body": "Incident has been resolved", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-14T18:37:42.542+02:00", "resolved_inferred": false, "started_at": "2025-10-14T18:35:02.714+02:00", @@ -376,7 +376,7 @@ "body": "Actor build success rate has fully recovered. If your Actor builds failed, please rerun them. We apologize for any inconvenience caused.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-25T03:48:23.006+02:00", "resolved_inferred": false, "started_at": "2025-09-25T01:16:14.887+02:00", @@ -389,7 +389,7 @@ "body": "The latest version of the apify/send-mail Actor failed to email all recipients. The issue lasted from around 13:50 to 14:05 CEST. The root cause was identified, and the service of the Actor was restored.\n\nWe apologize for any inconvenience this might have caused. We take this problem seriously and will take steps to prevent such issues from occurring in the future.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-15T14:38:10.455+02:00", "resolved_inferred": false, "started_at": "2025-09-15T14:38:10.412+02:00", @@ -402,7 +402,7 @@ "body": "All affected Actors have been rebuilt, and all builds are working correctly now.\n\nWe will continue to monitor the situation in case more failed builds appear.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-09T17:06:36.154+02:00", "resolved_inferred": false, "started_at": "2025-09-09T13:17:28.328+02:00", @@ -415,7 +415,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-07T18:15:45.098+02:00", "resolved_inferred": false, "started_at": "2025-08-07T16:44:33.073+02:00", @@ -428,7 +428,7 @@ "body": "The issue with country codes for datacenter proxies has been resolved.\nDatacenter proxies with country codes are now fully operational again.\n\nWe apologize for any inconvenience this may have caused, and thank you for your patience!", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-01T15:21:44.655+02:00", "resolved_inferred": false, "started_at": "2025-08-01T11:03:54.683+02:00", @@ -441,7 +441,7 @@ "body": "This incident has been resolved. We are sorry for the inconvenience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-01T10:13:49.905+02:00", "resolved_inferred": false, "started_at": "2025-08-01T08:30:48.318+02:00", diff --git a/api/v/apigee.json b/api/v/apigee.json index c4c6e191fad51dd3df2a689671de9a461e7a6530..1e6fb5495573a56b62d6f66f8b0f6511f3edd73c 100644 --- a/api/v/apigee.json +++ b/api/v/apigee.json @@ -3,7 +3,7 @@ "slug": "apigee", "platform": "statuspage", "status_url": "https://status.apigee.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", diff --git a/api/v/apollo.json b/api/v/apollo.json index 76b5531cb45232954d837d6e758709c193b94d20..caeab60b8f3393323e021e97079f544bf5140610 100644 --- a/api/v/apollo.json +++ b/api/v/apollo.json @@ -3,7 +3,7 @@ "slug": "apollo", "platform": "statuspage", "status_url": "http://status.apollographql.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "Our third party vendor has confirmed the issue is now resolved, and all Apollo products have recovered.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-09-01T20:18:54Z", "resolved_inferred": false, "started_at": "2026-09-01T15:41:44Z", @@ -24,7 +24,7 @@ "body": "The fix has been deployed. These failed operations would have appeared as rate limit errors, but the rate limit was being incorrectly applied. We have made changes to ensure the rate limit works as expected.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-26T23:36:51Z", "resolved_inferred": false, "started_at": "2026-08-26T22:12:39Z", @@ -36,7 +36,7 @@ "body": "The issue has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-11T23:19:08Z", "resolved_inferred": false, "started_at": "2026-08-11T19:11:37Z", @@ -48,7 +48,7 @@ "body": "The issue has been fixed.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-05T10:08:58Z", "resolved_inferred": false, "started_at": "2026-08-05T09:43:26Z", @@ -60,7 +60,7 @@ "body": "The error rate for Proposals has returned to normal, no further impact expected.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-09T18:09:55Z", "resolved_inferred": false, "started_at": "2026-07-09T15:41:29Z", @@ -72,7 +72,7 @@ "body": "The backlock of schema coordinate (object field, input object field, and enum value) metrics has now cleared and there is no more metric ingestion delay. The metrics for input object fields, enum values, and the operation and client breakdown of object fields is inaccurate for June 27 4-5am and 8-9pm, and missing between 5am to 8pm (all times in UTC). All other metrics were not impacted.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-28T20:16:19Z", "resolved_inferred": false, "started_at": "2026-06-28T03:13:19Z", @@ -84,7 +84,7 @@ "body": "The metric ingestion backlog has been fully processed and all metrics have resumed normal ingestion. We do not believe any data was lost as a result of this incident. All metric types should now be operating as expected. Thank you for your patience throughout this incident.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-15T22:16:12Z", "resolved_inferred": false, "started_at": "2026-06-15T14:38:25Z", @@ -96,7 +96,7 @@ "body": "After extended monitoring, we have confirmed that the issue is resolved. Post-incident action items will continue after the end of the incident. As with all incidents, we will be conducting an internal post-mortem. We appreciate your patience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-01T11:39:54Z", "resolved_inferred": false, "started_at": "2026-06-01T08:35:25Z", @@ -108,7 +108,7 @@ "body": "The issue affecting the visibility of the \u201cSubmit a Request\u201d and \u201cMy Requests\u201d buttons in the Apollo Support Portal has been resolved.\nPortal functionality has been restored, and users should now be able to access these options normally.\nThank you for your patience while we worked to resolve this issue.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-26T12:58:43Z", "resolved_inferred": false, "started_at": "2026-05-25T19:50:43Z", @@ -120,7 +120,7 @@ "body": "We have observed sustained restored functionality in our Studio-initiated support ticket form and are marking this as fully resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-27T10:29:10Z", "resolved_inferred": false, "started_at": "2026-04-27T08:34:51Z", @@ -132,7 +132,7 @@ "body": "We have resolved the issue. Customers should see full functionality.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-24T20:53:27Z", "resolved_inferred": false, "started_at": "2026-04-24T19:27:20Z", @@ -144,7 +144,7 @@ "body": "SSO login is now fixed.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-21T17:47:38Z", "resolved_inferred": false, "started_at": "2026-04-21T17:05:47Z", @@ -156,7 +156,7 @@ "body": "Proposals errors have been clear for ~2 hours since the rollback reached prod. Marking resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-16T15:43:07Z", "resolved_inferred": false, "started_at": "2026-04-16T12:45:07Z", @@ -168,7 +168,7 @@ "body": "Retries of delayed transaction emails have been successful. If you have not received an email you were expecting for account reasons, we suggest retrying the workflow which triggered the email.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-31T07:39:56Z", "resolved_inferred": false, "started_at": "2026-03-31T06:59:02Z", @@ -180,7 +180,7 @@ "body": "We've identified an issue where our metrics ingestion pipeline was falling behind for several hours. Systems have now fully recovered and no data was lost, however some customers may have experienced delays viewing insights data in Studio and / or slower page load times during this event. Apologies for the interruption.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-10T16:00:00Z", "resolved_inferred": false, "started_at": "2026-02-12T06:06:22Z", @@ -192,7 +192,7 @@ "body": "The issue has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-21T21:25:39Z", "resolved_inferred": false, "started_at": "2025-11-21T18:05:32Z", @@ -204,7 +204,7 @@ "body": "There was a period of degraded performance on schema publishing. The root cause has been identified and service restored.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-18T17:30:00Z", "resolved_inferred": false, "started_at": "2025-11-18T19:06:04Z", @@ -216,7 +216,7 @@ "body": "We are marking this incident resolved on the Apollo side.\n\nFor any continuing matters, please consult our support portal: https://support.apollographql.com/", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-18T15:38:24Z", "resolved_inferred": false, "started_at": "2025-11-18T13:05:25Z", @@ -228,7 +228,7 @@ "body": "Cloud Routers are experiencing elevated errors due to an upstream external provider incident.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-18T12:30:00Z", "resolved_inferred": false, "started_at": "2025-11-18T13:05:25Z", @@ -240,7 +240,7 @@ "body": "We've confirmed that the issue with federation versions 2.9, 2.10, and 2.11 is resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-05T15:12:28Z", "resolved_inferred": false, "started_at": "2025-11-05T14:05:49Z", @@ -252,7 +252,7 @@ "body": "No schema publishing or checks issues have been observed for couple of hours now. We are continuing to monitor our services in relation to the AWS outage today on the other open incident.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-21T05:26:55Z", "resolved_inferred": false, "started_at": "2025-10-20T21:06:09Z", @@ -264,7 +264,7 @@ "body": "We will mark this as resolved as issues impacting our service have been resolved either through mitigation or upstream provider resolution. While some of our dependent services have indicated there is on-going stabilization of their own systems (following on the AWS us-east-1 disruptions yesterday) any unresolved items have NO impact to our offerings. In the event that we have new findings or degradations, we will open a new incident.\n\nThank you for your patience while we adapted toward changing circumstances following on yesterday's events, and thank you to teams across the industry who worked (or may still be working) tirelessly toward recovery.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-21T10:00:48Z", "resolved_inferred": false, "started_at": "2025-10-20T16:56:25Z", @@ -276,7 +276,7 @@ "body": "As a result of the AWS us-east-1 system recovery, our own systems have also recovered, including AWS Uplink and AWS-hosted Cloud Routers. At this time we will mark this issue as Resolved, though we will continue to monitor for any possible reoccurrence.\n\nAs noted in a previous update, the default configuration for Apollo Router and Apollo Gateway deployments is to roam between Google Cloud Platform (GCP) and Amazon Web Services (AWS) endpoints in the event that one or the other is available. If you have changed your configuration to rely on merely one provider, we recommend considering a configuration with fallback redundancy. Please contact support if you need assistance with this configuration.\n\nAdditionally, our support systems have recovered and we believe any issues opened during the AWS incident have been received by our support teams. If you believe your issue has not been received, please feel free to reach out to our support team again.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-20T10:39:12Z", "resolved_inferred": false, "started_at": "2025-10-20T08:14:38Z", @@ -288,7 +288,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-17T11:52:11Z", "resolved_inferred": false, "started_at": "2025-09-17T11:05:53Z", @@ -300,7 +300,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-21T21:22:06Z", "resolved_inferred": false, "started_at": "2025-08-21T22:06:05Z", diff --git a/api/v/appen.json b/api/v/appen.json index d80e74b240ecb8853a98915b7d189554eaec9a3a..ebba7af5d828da84dd3088e37c0014a24512d191 100644 --- a/api/v/appen.json +++ b/api/v/appen.json @@ -3,7 +3,7 @@ "slug": "appen", "platform": "statuspage", "status_url": "https://status.appen.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-11T02:58:10.818-07:00", "resolved_inferred": false, "started_at": "2025-09-11T02:54:11.921-07:00", @@ -25,7 +25,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-11T02:34:03.272-07:00", "resolved_inferred": false, "started_at": "2025-09-11T02:30:07.226-07:00", @@ -38,7 +38,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-11T02:04:37.358-07:00", "resolved_inferred": false, "started_at": "2025-09-11T02:03:13.955-07:00", @@ -51,7 +51,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-09T07:28:41.403-07:00", "resolved_inferred": false, "started_at": "2025-09-09T07:16:25.464-07:00", @@ -64,7 +64,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-09T07:11:25.289-07:00", "resolved_inferred": false, "started_at": "2025-09-09T07:10:57.630-07:00", @@ -77,7 +77,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-09T07:07:07.621-07:00", "resolved_inferred": false, "started_at": "2025-09-09T06:54:11.145-07:00", @@ -90,7 +90,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-09T07:29:22.253-07:00", "resolved_inferred": false, "started_at": "2025-09-09T06:47:06.876-07:00", @@ -103,7 +103,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-02T07:06:22.869-07:00", "resolved_inferred": false, "started_at": "2025-09-02T04:20:55.634-07:00", @@ -116,7 +116,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-02T07:06:40.053-07:00", "resolved_inferred": false, "started_at": "2025-09-02T04:17:53.174-07:00", @@ -129,7 +129,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-02T07:07:00.897-07:00", "resolved_inferred": false, "started_at": "2025-09-02T04:04:32.005-07:00", @@ -142,7 +142,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-02T07:07:16.984-07:00", "resolved_inferred": false, "started_at": "2025-09-02T03:54:29.511-07:00", @@ -155,7 +155,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-02T07:07:31.486-07:00", "resolved_inferred": false, "started_at": "2025-09-02T03:53:00.479-07:00", @@ -168,7 +168,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-02T07:07:45.175-07:00", "resolved_inferred": false, "started_at": "2025-09-02T02:48:51.611-07:00", diff --git a/api/v/appriver.json b/api/v/appriver.json index 5b83607d09cd7c3abb7f0bcfc71592a2280aad16..064bb9fc57e2f046f1e6b53037f2197c6a5661f0 100644 --- a/api/v/appriver.json +++ b/api/v/appriver.json @@ -3,7 +3,7 @@ "slug": "appriver", "platform": "statuspage", "status_url": "https://status.appriver.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "unknown", "history_backfilled": false, "first_watched": "2026-09-04T07:06:16Z", diff --git a/api/v/appsflyer.json b/api/v/appsflyer.json index 49bb34821f3ad877921493b12faf4dc40fc49a4e..19df8943a07e593abb924343f0b53c4d73eea565 100644 --- a/api/v/appsflyer.json +++ b/api/v/appsflyer.json @@ -3,7 +3,7 @@ "slug": "appsflyer", "platform": "statuspage", "status_url": "https://status.appsflyer.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "Some of our services were impacted by a DNS issue between 14:35 and 15:35 UTC.\nDuring this time: clicks and impressions processing was delayed, which resulted in a temporary increase in organic attribution; the Onelink API was partially available; and some processed events are missing geo data.\nThe issue has been fully resolved.\nPlease contact our support team with any questions.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-27T16:53:33.075Z", "resolved_inferred": false, "started_at": "2026-07-27T15:08:43.785Z", @@ -25,7 +25,7 @@ "body": "We are seeing significantly fewer reports related to domain mapping and expect the DNS propagation process to complete in the coming hours. \nWe are marking this incident as resolved.\nIf you have any questions or need assistance, our team is available to help.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-12T12:34:39.082Z", "resolved_inferred": false, "started_at": "2026-03-10T04:09:46.425Z", @@ -38,7 +38,7 @@ "body": "Dashboard availability has been fully restored.\nOur teams continue to monitor performance.\nIf you encounter any further issues, please contact Technical Support.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-10T22:46:14.478Z", "resolved_inferred": false, "started_at": "2026-02-10T21:08:17.899Z", @@ -51,7 +51,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-26T21:03:55.639Z", "resolved_inferred": false, "started_at": "2026-01-25T09:35:49.000Z", @@ -64,7 +64,7 @@ "body": "Meta API availability has returned to normal, and we continue to monitor conversion rates closely.\nWe will update this page if any further anomalies occur.\nThank you for your patience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-17T05:57:50.808Z", "resolved_inferred": false, "started_at": "2025-12-16T15:39:58.049Z", @@ -77,7 +77,7 @@ "body": "Our teams reprocessed engagements from approximately 10:25 AM UTC to 11:15 AM UTC, and those engagements are now available for new conversions. \nThank you for your patience, and please contact us for any related questions.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-26T15:02:09.720Z", "resolved_inferred": false, "started_at": "2025-10-26T11:14:46.505Z", @@ -90,7 +90,7 @@ "body": "Meta API availability has returned to normal, and we continue to monitor conversion rates closely.\nWe will update this page if any further anomalies occur.\nThank you for your patience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-20T11:33:56.101Z", "resolved_inferred": false, "started_at": "2025-09-20T07:12:27.000Z", @@ -103,7 +103,7 @@ "body": "The Push API delay issue is resolved. The backlog of events not sent since 01:07 UTC is now being delivered and will clear over the next few hours. We\u2019re monitoring until completion.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-20T14:27:24.072Z", "resolved_inferred": false, "started_at": "2025-08-20T14:14:34.119Z", @@ -116,7 +116,7 @@ "body": "We can confirm that the issue is now resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-05T10:55:05.830Z", "resolved_inferred": false, "started_at": "2025-08-05T10:33:34.882Z", @@ -129,7 +129,7 @@ "body": "The issue has been resolved and the cost, clicks and impressions data is now available in all the reports and dashboards", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-02T13:20:01.265Z", "resolved_inferred": false, "started_at": "2025-08-01T19:05:52.821Z", diff --git a/api/v/appwrite.json b/api/v/appwrite.json index c71f375de30881854ace50ed5dba034425b00f7e..04d6e58879f82f8f2be6765ff8e95e45c6904f7a 100644 --- a/api/v/appwrite.json +++ b/api/v/appwrite.json @@ -3,7 +3,7 @@ "slug": "appwrite", "platform": "betterstack", "status_url": "https://status.appwrite.io", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": false, "first_watched": "2026-09-04T07:06:16Z", diff --git a/api/v/aptible.json b/api/v/aptible.json index dc59fa3e5a63639d57be3aea61f18c5fe8df3625..58b806025672de10a3b3ea88ce3373d04d4d7142 100644 --- a/api/v/aptible.json +++ b/api/v/aptible.json @@ -3,7 +3,7 @@ "slug": "aptible", "platform": "statuspage", "status_url": "https://status.aptible.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-27T11:12:00.684-04:00", "resolved_inferred": false, "started_at": "2026-07-27T06:31:04.452-04:00", @@ -25,7 +25,7 @@ "body": "Following the fixes deployed per the previous update, we have seen stable performance on the LLM Gateway since 7:12 EDT and are resolving the issue.\n\nThe root cause of this issue was a severe performance degradation in 3 specific endpoints:\n\u2022\u00a0`GET /models`\n\u2022\u00a0`GET /v1/models`\n\u2022\u00a0`GET /metadata/models`\n\n...all of which return a list of available models. The performance issue on these endpoints was severe enough to cause significant request queueing and degraded performance for other unaffected endpoints. The fix we deployed added caching on this endpoint to ensure fast responses. Since those fixes have been deployed, we are no longer seeing request queueing or impacts to other LLM Gateway API endpoints.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-17T13:04:04.670-04:00", "resolved_inferred": false, "started_at": "2026-07-16T18:31:08.575-04:00", @@ -38,7 +38,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-23T17:48:13.568-04:00", "resolved_inferred": false, "started_at": "2026-06-08T14:28:46.841-04:00", @@ -51,7 +51,7 @@ "body": "As of 18:42 UTC the upstream provider began to accept log messages again consistently and this issue is now remediated.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-03T15:16:20.104-04:00", "resolved_inferred": false, "started_at": "2026-06-03T12:02:30.705-04:00", @@ -64,7 +64,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-08T11:35:02.686-04:00", "resolved_inferred": false, "started_at": "2026-05-08T01:02:07.845-04:00", @@ -77,7 +77,7 @@ "body": "An upstream AWS issue affected infrastructure in a single Availability Zone in us-east-1. During the event, we blocked provisioning into the affected zone and monitored AWS\u2019s recovery efforts.\n\nAWS has since recovered enough of the affected availability zone for the impacted Aptible infrastructure to recover. We have also completed recovery of any Aptible-managed resources that required follow-up action on our side.\n\nAny customers with directly affected resources have been notified of resolution. We are continuing normal platform monitoring, but we are marking this incident as resolved on our end.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-08T23:35:54.117-04:00", "resolved_inferred": false, "started_at": "2026-05-07T21:05:42.870-04:00", @@ -90,7 +90,7 @@ "body": "Aptible is aware of CVE-2026-31431, also known as \u201cCopy Fail,\u201d a recently disclosed Linux kernel vulnerability that may allow local privilege escalation under certain conditions [0].\n\nWe have taken action across the Aptible platform to protect all customer workloads against this vulnerability. No customer action is required at this time.\n\nWe will continue to monitor upstream kernel, distribution, and security vendor guidance related to this CVE and will take any additional action if needed.\n\n[0] https://copy.fail/", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-29T18:40:43.316-04:00", "resolved_inferred": false, "started_at": "2026-04-29T18:40:43.273-04:00", @@ -103,7 +103,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-18T23:10:17.839-04:00", "resolved_inferred": false, "started_at": "2026-04-18T22:03:58.794-04:00", @@ -116,7 +116,7 @@ "body": "Additional detail about timeline: we observed a relative increase in DNS resolver errors in us-east-1 beginning at approximately 2026-03-17 18:30 UTC. The elevated error rate was intermittent rather than constant, with the most visible clusters occurring from roughly 18:30-18:55 UTC and again from about 20:55-21:40 UTC. Error rates returned to normal shortly after 21:40 UTC.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-17T19:33:35.883-04:00", "resolved_inferred": false, "started_at": "2026-03-17T18:33:47.740-04:00", @@ -129,7 +129,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-31T09:49:00.737-05:00", "resolved_inferred": false, "started_at": "2025-12-31T05:48:35.671-05:00", @@ -142,7 +142,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-30T12:15:34.065-05:00", "resolved_inferred": false, "started_at": "2025-12-29T21:14:23.204-05:00", @@ -155,7 +155,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-08T11:52:22.240-05:00", "resolved_inferred": false, "started_at": "2025-12-05T09:39:55.817-05:00", @@ -168,7 +168,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-05T11:07:49.146-05:00", "resolved_inferred": false, "started_at": "2025-11-05T10:59:59.035-05:00", @@ -181,7 +181,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-29T17:50:27.460-04:00", "resolved_inferred": false, "started_at": "2025-10-29T17:17:17.088-04:00", @@ -194,7 +194,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-28T17:08:52.592-04:00", "resolved_inferred": false, "started_at": "2025-10-28T13:09:06.240-04:00", @@ -207,7 +207,7 @@ "body": "AWS has marked the underlying issue in us-east-1 as resolved, and we\u2019ve confirmed continued stability across all EC2-related operations.\n\nAll Aptible operations are functioning normally, and this incident is now closed.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-20T19:04:19.807-04:00", "resolved_inferred": false, "started_at": "2025-10-20T07:53:09.171-04:00", @@ -220,7 +220,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-20T05:46:00.046-04:00", "resolved_inferred": false, "started_at": "2025-10-20T03:47:14.947-04:00", @@ -233,7 +233,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-11T23:40:31.265-04:00", "resolved_inferred": false, "started_at": "2025-10-11T22:30:16.257-04:00", @@ -246,7 +246,7 @@ "body": "Aptible has reviewed and addressed the Redis vulnerability described in https://redis.io/blog/security-advisory-cve-2025-49844/.\n\nWe have confirmed that all internal Redis instances used in delivering the Aptible platform are secure and have no exploitation path related to this CVE.\n\nFor Aptible customers who do not have their Redis databases publicly exposed, a path to exploitation is similarly unlikely. Additionally, for customers using Redis 6.2 databases on Aptible, a patched version will be available by Oct 10th at 5pm EST, and additional releases (7.2) are upcoming; see aptible.com/changelog for ongoing release updates. To ensure you are running the latest minor version when available, please run the cli command: aptible db:reload for each Redis database.\n\nFor more information on using this command, visit https://www.aptible.com/docs/reference/aptible-cli/cli-commands/cli-db-reload.\n\nIf you have any specific questions or concerns related to this CVE, please contact us.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-10T11:53:25.000-04:00", "resolved_inferred": false, "started_at": "2025-10-10T11:53:25.000-04:00", @@ -259,7 +259,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-07T10:21:32.490-04:00", "resolved_inferred": false, "started_at": "2025-08-07T09:43:14.966-04:00", diff --git a/api/v/apwide.json b/api/v/apwide.json index c0f6ef4541b332b705e850ba5ba8a316a5eb9d24..e3004fc9dd34e06ce5aaedaaa46a9be332756c70 100644 --- a/api/v/apwide.json +++ b/api/v/apwide.json @@ -3,7 +3,7 @@ "slug": "apwide", "platform": "statuspage", "status_url": "https://apwide.statuspage.io", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "We have identified and resolved the root cause of the issue.\nOne of our nodes was unable to perform DNS resolution due to routing errors.\nThe routing issues have now been fixed, and DNS resolution is working correctly.\n\nWe apologize for the inconvenience caused.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-10T21:27:10.497+01:00", "resolved_inferred": false, "started_at": "2026-03-10T20:04:58.869+01:00", @@ -25,7 +25,7 @@ "body": "**07:23 UTC** \u2013 The support team was alerted by monitoring that some database queries were taking longer than expected.\n\n**07:34 UTC** \u2013 Our uptime probes began raising alerts indicating that Golive was no longer accessible to end users.\n\n**07:46 UTC** \u2013 The support team updated the status page to notify users of a Golive outage.\n\n**08:23 UTC** \u2013 The support team identified an abnormal traffic spike originating from Atlassian webhooks. Under normal conditions, traffic peaks reach around 1,000 webhook calls per minute; however, we experienced a sustained spike exceeding 9,000 calls per minute. This caused one of our components to open more database connections than it was designed to handle, forcing it to restart repeatedly. To protect the Golive application, webhook traffic was temporarily disabled. The component stopped restarting and access to Golive was restored.\n\n**11:20 UTC** \u2013 The engineering team implemented an initial performance improvement on the affected component. The fix was deployed to production, and webhook traffic was re-enabled to evaluate performance.\n\n**11:44 UTC** \u2013 Webhook traffic was suspended again as the initial fix proved insufficient. Although database connections were no longer an issue, the component was still receiving excessive request traffic.\n\n**14:01 UTC** \u2013 A second improvement was implemented, this time at the gateway level. The fix was deployed to production and webhook traffic was re-enabled. No further restarts were observed, and Golive appeared to be fully operational.\n\n**14:45 UTC** \u2013 After several traffic peaks reaching up to 5,000 webhook calls per minute, all components continued to operate normally, with sufficient margins in terms of database connections and execution threads. The incident was closed. \n \nWith the additional performance improvements, the infrastructure now appears capable of handling a significantly higher load than originally designed.\n\nFurthermore, traffic should be better segregated to isolate asynchronous workloads \\(webhooks, conflict checking, automation, etc.\\) from transactional traffic \\(UI application usage\\). This separation should help mitigate the risk of asynchronous traffic impacting normal user navigation.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-05T15:56:54.317+01:00", "resolved_inferred": false, "started_at": "2026-02-05T08:46:30.902+01:00", @@ -38,7 +38,7 @@ "body": "**Outage Recap**\n\n* **2025-11-05 at 5:56 AM UTC**, our monitoring system began raising alerts indicating that some of our services were unable to communicate with the database.\n* **6:20 AM UTC:** We reported an outage affecting the **Golive** and **Time Squad** services on our status page.\n* **6:26 AM UTC:** We suspected the issue originated from our hosting provider\u2019s managed database service. We contacted their support team and opened a ticket.\n* **6:57 AM UTC:** The hosting provider confirmed the issue on their side and announced a general outage on their platform. [Incident link](https://public-cloud.status-ovhcloud.com/incidents/9qmxv0gbky43)\n* **7:58 AM UTC:** The hosting provider reported that the issue had been resolved. We restarted our **Golive** and **Time Squad** services.\n* **8:19 AM UTC:** All of our services were fully restored, and we updated our status page accordingly.\n* **8:31 AM UTC:** The hosting provider informed us that the root cause was a **DNS issue** on their end.\n\nWe apologize for the inconvenience caused and appreciate your patience and understanding.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-05T11:07:55.539+01:00", "resolved_inferred": false, "started_at": "2025-11-05T07:20:24.892+01:00", diff --git a/api/v/aqua.json b/api/v/aqua.json index 4aa5d45487a759918c110e6c073596cb86ebbce5..c448eb205e7220daba560ed2f1981318d20f3560 100644 --- a/api/v/aqua.json +++ b/api/v/aqua.json @@ -3,7 +3,7 @@ "slug": "aqua", "platform": "statuspage", "status_url": "https://status.aquasec.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "Aqua Supply Chain Vulnerability Scanning Service Disruption Notice - Resolved\n\nSince approximately 09:00 UTC on August 31, 2025, our Supply Chain Vulnerability Scanning service experienced a degradation, causing CI/CD pipeline timeouts and timeouts on the Supply Chain page.\n\nUpdate: The applied fix has been confirmed effective following a period of active monitoring, and the service has returned to normal operation. The Supply Chain Vulnerability Scanning component status has been updated to Operational.\n\nWe apologize for the inconvenience this incident may have caused and thank you for your patience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-31T19:30:45.477Z", "resolved_inferred": false, "started_at": "2026-08-31T17:18:15.683Z", @@ -25,7 +25,7 @@ "body": "Since approximately 09:00 UTC on August 31, 2025, our Supply Chain Vulnerability Scanning service has been experiencing a degradation. This is currently causing CI/CD pipeline timeouts and timeouts on the Supply Chain page.\n\nOur team is actively investigating and has engaged the relevant internal teams to work toward resolution. We will share updates as they become available. We apologize for any inconvenience this is causing.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-31T13:00:00.000Z", "resolved_inferred": false, "started_at": "2026-08-31T13:00:00.000Z", @@ -38,7 +38,7 @@ "body": "The issues affecting login performance have been mitigated, and services are now operating normally.\nWe continue to monitor the situation to ensure stability.\nThank you for your patience and understanding.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-21T01:52:41.464Z", "resolved_inferred": false, "started_at": "2025-10-20T15:01:36.162Z", @@ -51,7 +51,7 @@ "body": "On October 1st, 2025, at approximately 08:10 AM UTC, our Container Image Scanning service experienced a performance degradation. This caused the resulting in partial impact on scanning requests.\n\nThe Aqua team promptly identified the issue and engaged the India team for resolution. The incident was mitigated at 08:56 AM UTC on October 1st, 2025.\n\nWe apologize for any inconvenience caused by this disruption. To prevent recurrence, we are enhancing our monitoring and alerting systems and implementing automated remediation measures where possible.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-01T08:00:00.000Z", "resolved_inferred": false, "started_at": "2025-10-01T08:00:00.000Z", @@ -64,7 +64,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-08T10:55:52.972Z", "resolved_inferred": false, "started_at": "2025-09-08T08:34:31.108Z", @@ -77,7 +77,7 @@ "body": "The maintenance for the CSPM scanning service has been completed. All systems are fully operational.", "first_seen": "2026-09-04T07:06:16Z", "impact": "maintenance", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-05T03:26:21.907Z", "resolved_inferred": false, "started_at": "2025-09-04T19:30:40.000Z", diff --git a/api/v/arista-cloudvision.json b/api/v/arista-cloudvision.json index bdc135bc7cf693b5778976649092980b6dba795a..ecccd58e7509842a7666e90d8ecb2ebe320faf18 100644 --- a/api/v/arista-cloudvision.json +++ b/api/v/arista-cloudvision.json @@ -3,7 +3,7 @@ "slug": "arista-cloudvision", "platform": "statuspage", "status_url": "https://status.arista.io", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "A mitigation was put in place and the performance is now stabilized. We will continue to monitor the situation. Thank you", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-09-01T04:47:56.942Z", "resolved_inferred": false, "started_at": "2026-09-01T03:22:34.450Z", @@ -25,7 +25,7 @@ "body": "This incident arose from unexpected localized network partitioning due to underlying conditions. Our systems automatically detected the event in <5m of the start of the impact, and began recovery, with minimal manual intervention involved. We are analyzing further hardening against the underlying conditions of this nature.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-28T20:40:36.781Z", "resolved_inferred": false, "started_at": "2026-08-28T17:39:57.230Z", @@ -38,7 +38,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-20T05:09:23.081Z", "resolved_inferred": false, "started_at": "2026-08-20T02:54:03.744Z", @@ -51,7 +51,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-12T19:03:50.725Z", "resolved_inferred": false, "started_at": "2026-08-12T18:51:17.000Z", @@ -64,7 +64,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-13T05:25:27.232Z", "resolved_inferred": false, "started_at": "2026-08-12T16:19:38.427Z", @@ -77,7 +77,7 @@ "body": "The issue has been identified and a mitigation has been put in place. Streaming latencies have returned to their expected level.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-06T11:47:35.502Z", "resolved_inferred": false, "started_at": "2026-08-06T10:45:23.704Z", @@ -90,7 +90,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-15T21:45:15.101Z", "resolved_inferred": false, "started_at": "2026-07-15T21:45:01.991Z", @@ -103,7 +103,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-15T03:27:33.953Z", "resolved_inferred": false, "started_at": "2026-07-15T01:09:33.713Z", @@ -116,7 +116,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-10T18:46:39.905Z", "resolved_inferred": false, "started_at": "2026-07-10T18:25:05.679Z", @@ -129,7 +129,7 @@ "body": "This issue is resolved. Please follow https://status.arista.io/incidents/5vx7cvb07k7d for postmortem update when it becomes available.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-13T23:54:59.538Z", "resolved_inferred": false, "started_at": "2026-07-07T22:58:26.134Z", @@ -142,7 +142,7 @@ "body": "**Incident Report: CVaaS Service Disruption - June 26th, 2026**\n\nOn June 26th, 2026 10:00AM PDT - 12:30PM PDT CVaaS service region cv-prod-us-central1-b experienced significant ingestion delay into NetDL that caused the following incorrect states to be observed by users:\n\n* Devices incorrectly marked as Inactive,\n* Multiple inactionable \u201cDevice Stopped Streaming\u201d events,\n* Multiple inactionable \u201cHigh Streaming Latency\u201d events\n\nDuring this time period, executing device provisioning actions may have been delayed or failed. There was no data loss. However, data ingested from actively streaming devices into CVaaS may have only become accessible after some delay. This may have impacted users accessing the UI, or other services consuming that data from CloudVision via API integrations. \n\nBetween June 26, 2026 12:30PM PDT - June 27th, 12:30PM PDT, some users may have experienced the above behaviors intermittently impact their devices, but not block device provisioning activities.\n\nBy June 27th, 2026, all mitigations were in place, and we transitioned to mitigating intermittent instances of elevated tail latency along the data ingestion path into NetDL. Between June 27th, 2026 and July 6th, 2026 a small subset of users of the cv-prod-us-central1-b service region may have experienced rare, but intermittent instances where CloudVision reported Event \u201cHigh Streaming Latency\u201d, potentially due to brief delays in NetDL ingestion. Users were not blocked from performing device provisioning activities.\n\n\u200c\n\n**Root Cause**\n\nNetwork performance degradation and instabilities in our underlying cloud provider were the ultimate root causes of delays ingesting data into the part of the system responsible for storing, processing, and updating device streaming status and streaming latency. Our mitigation activities between June 26th, 2026 and June 27th, 2026 stabilized the vast majority of the impact, but the changing underlying conditions prolonged the total duration of incident. This incident was not caused by software change\\(s\\), monitoring gaps, or software bugs in CloudVision as-a-Service.\n\n\u200c\n\n**Our Response**\n\nMultiple teams at Arista engaged around the clock from June 26th, 2026 until July 6th, 2026 to ensure we fully resolved this incident, as well as reviewed all details in our internal reviews. We continue to actively monitor this service region, as well as all of our CloudVision as-a-Service service regions.\n\nArista takes full responsibility for the performance and availability of the service regardless of the underlying cloud platform conditions. We are committed to making changes in both the short and long term that will provide greater resilience to underlying provider instabilities and changing real-time conditions.\n\nThank you for using CloudVision as-a-Service.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-07T22:57:18.224Z", "resolved_inferred": false, "started_at": "2026-06-26T17:27:17.754Z", @@ -155,7 +155,7 @@ "body": "We identified the source of the problem and the data ingestion latency has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-10T16:03:13.608Z", "resolved_inferred": false, "started_at": "2026-06-10T11:48:01.850Z", @@ -168,7 +168,7 @@ "body": "**Incident Report: CVaaS Service Disruption - May 29, 2026**\n\nOn May 29th, 2026, CloudVision as-a-Service delivered a software change for a set of services that provide the Network Provisioning workflows in the product. All services regions were impacted by this Network Provisioning feature update.\u00a0\n\nThis update introduced a critical bug across all service regions. As a result, customers utilizing the Network Provisioning workflows \\(see [https://www.arista.io/help/articles/provisioning-network-provisioning#network-provisioning](https://www.arista.io/help/articles/provisioning-network-provisioning#network-provisioning)\\) may have experienced instances where devices were mapped to the incorrect containers in the network provisioning hierarchy, creating a risk that unintended configuration states could be applied if customers then attempted to roll out additional changes to devices. The Network Provisioning workflows were disabled while we recovered from the issue, meaning that customers could not make any changes to their network configuration during this time.\n\nCustomers only defining their network configuration using Studios workflows \\(see [https://www.arista.io/help/articles/provisioning-studios](https://www.arista.io/help/articles/provisioning-studios)\\) were not impacted.\n\nThe software change that caused this issue was rolled back on May 29th, 2026. The delay in mitigation was due to gaps in our automated monitoring systems.\n\nFAQ:\n\n* _Did this bug cause a network outage for customers?_ No.\n* _Was there any data loss?_ No.\n* Was overall CloudVision service availability impacted?No.\n* _Are there any additional steps to recovery?_ No; the vast majority of impacted customers were recovered without requiring customer intervention. At this moment if you have not been directly contacted by us, no further action is required from you.\n\n\u200c\n\n**Root Cause**\n\nThe bug was due to logic applied to an incorrect data state within the Network Provisioning feature. This caused an incorrect device container mapping during the device state reconciliation phase. This was not caught during testing or during the post deployment evaluation phase in various environments prior to being released to production. Additionally, the rollout strategy used in the continuous delivery applicable for this particular set of services allowed the bug to propagate quickly across all CloudVision as-a-Service regions.\n\n\u200c\n\n**Our Response**\n\nOnce the bug was identified on May 29th, 2026, our team rolled back the update responsible within approximately a five hour period on all production regions. In addition, API usage restrictions were established as a protective measure against customers that may inadvertently execute a configuration change on their network without knowledge of this bug and device state change. Between May 29th and June 1st, 2026, our team engaged in continuous efforts to restore services for all affected customers and devices. The majority of these recovery operations were successfully concluded by May 30th, 2026. Throughout this period, we maintained regular updates on Statuspage to keep our customers informed regarding our progress.\n\nWe understand a disruption of this nature is unacceptable for our customers. We are conducting a full review of design, testing, validation, delivery, monitoring, and incident response as part of the postmortem review, and we are committed to ensuring we do not run into incidents of this nature in the future.\u00a0\n\nThank you for using CloudVision as-a-Service.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-04T00:50:38.220Z", "resolved_inferred": false, "started_at": "2026-05-29T20:24:49.338Z", @@ -181,7 +181,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-29T21:02:17.763Z", "resolved_inferred": false, "started_at": "2026-05-29T17:45:17.916Z", @@ -194,7 +194,7 @@ "body": "This incident has been resolved. We will follow up with a postmortem.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-27T01:02:39.759Z", "resolved_inferred": false, "started_at": "2026-05-26T15:38:23.965Z", @@ -207,7 +207,7 @@ "body": "We experienced high device streaming latency on this affected cluster. \n\nSome impact may be user visible, such as:\n- A delay in processing streamed device data. Some events such as \"Device stopped streaming\" or \"Streaming Latency Breached Threshold\" may fire as a result of this. In this case, the device updates are behind schedule and will be processed with some delay during the impact window.\n- There may be some stale data, or sporadic timeouts viewing parts of the UI.\n- Some provisioning features may be delayed or timeout due to the high latency.\n\nThis was due to an internal component upgrade in our cloud environment; we continue to work on decreasing the impact of this upgrade process. Thank you for your patience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-18T13:35:22.839Z", "resolved_inferred": false, "started_at": "2026-05-18T13:35:22.776Z", @@ -220,7 +220,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-15T17:30:14.843Z", "resolved_inferred": false, "started_at": "2026-05-15T17:24:21.000Z", @@ -233,7 +233,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-15T12:34:33.103Z", "resolved_inferred": false, "started_at": "2026-04-15T12:04:42.879Z", @@ -246,7 +246,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-19T00:57:11.179Z", "resolved_inferred": false, "started_at": "2026-03-19T00:38:53.548Z", @@ -259,7 +259,7 @@ "body": "The fix has been successfully deployed to all regions. Customers will have to reload the UI for the changes to take effect.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-12T21:57:50.933Z", "resolved_inferred": false, "started_at": "2026-03-12T15:33:08.562Z", @@ -272,7 +272,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-04T06:43:05.682Z", "resolved_inferred": false, "started_at": "2026-03-04T05:23:36.000Z", @@ -285,7 +285,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-03T04:31:27.923Z", "resolved_inferred": false, "started_at": "2026-03-03T04:15:47.058Z", @@ -298,7 +298,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-17T16:54:04.498Z", "resolved_inferred": false, "started_at": "2026-02-13T01:30:08.000Z", @@ -311,7 +311,7 @@ "body": "**Incident Report: Platform Outage - January 31st, 2026**\n\nOn January 31, 2026, CloudVision as-a-Service experienced a platform-wide incident within the cv-prod-us-central1-a region that lasted a total of 1 hour and 18 minutes. During the first hour of this window, the platform remained operational despite intermittent connectivity disruptions that impacted <1% of total traffic. In the final 18 minutes of the incident, traffic loss increased to approximately 2%. During this period, users likely experienced a gradual loss of connectivity and platform access. This included disruptions to device streaming, where devices may have started to coalesce data to resume streaming once platform stabilized, which is the standard failure-mode behavior designed to preserve data integrity during network instability.\n\nThis incident was not the result of a security breach, unauthorized intrusion, or any malicious activity.\n\n\u200c\n\n**Root Cause**\n\nThe root cause of this disruption was identified as a catastrophic networking loss within our third-party cloud infrastructure provider.\n\n\u200c\n\n**Our Response**\n\nOur team detected the outage within five minutes of the initial failure and remained in constant communication with the provider to manage triage, recovery, and remediation efforts. During the incident, we made the strategic decision not to initiate a full site disaster recovery. Our technical assessment concluded that a full failover would have been significantly more disruptive to the user experience and would have ultimately prolonged the duration of the incident.\n\n\u200c\n\nWe understand that any service interruption is an unacceptable outcome for our users. We are currently working on internal initiatives to make our architecture more resilient to these specific modes of failure while simultaneously partnering with our cloud provider to ensure better stability of the underlying infrastructure.\n\n\u200c\n\nWe appreciate your patience and your continued use of CloudVision as-a-Service.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-31T01:42:31.826Z", "resolved_inferred": false, "started_at": "2026-01-31T00:16:11.984Z", @@ -324,7 +324,7 @@ "body": "**Incident Report: Login By Email Service Outage - January 30th, 2026**\n\nOn January 30, 2026, CloudVision as-a-Service experienced a service outage affecting the \"Login By Email\" functionality lasting 2 hours and 36 minutes. During this window, customers attempting to access their accounts using Login By Email failed to receive the invitation emails. This incident was isolated strictly to the Login By Email service; SSO and SAML based login remained fully operational.\n\nThere was no data loss or compromise of customer information. This outage was not the result of a security breach, unauthorized intrusion, or any malicious activity.\n\n**Root Cause**\n\nOur investigation identified a gap in monitoring for a critical third-party integration. Because this specific telemetry was missing, early warning signals were missed, leading to the eventual service disruption. Additionally, we identified internal process failures that contributed to the duration of the outage.\n\n**Our Response**\n\nInternal escalation protocols successfully engaged subject matter experts within 30 minutes of the first reported case. Initial delays in resolution were primarily due to various process failures including delays in required coordination with third party vendor. We are implementing the missing monitoring triggers for third-party integrations to ensure early detection, as well as reviewing our processes as part of various fixes we are addressing.\n\nWe understand that any service disruption is impactful. We are committed to implementing changes identified during our internal investigation to prevent this type of failure from happening again.\n\nThank you for using CloudVision as-a-Service.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-30T16:05:26.723Z", "resolved_inferred": false, "started_at": "2026-01-30T14:36:34.310Z", @@ -337,7 +337,7 @@ "body": "Telemetry was delayed for up to 30 minutes due to an disruptive infrastructure reconfiguration. The incident has now been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-23T12:13:47.702Z", "resolved_inferred": false, "started_at": "2026-01-23T09:28:30.595Z", @@ -350,7 +350,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-15T23:49:30.238Z", "resolved_inferred": false, "started_at": "2026-01-15T20:53:52.525Z", @@ -363,7 +363,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-13T00:11:03.157Z", "resolved_inferred": false, "started_at": "2026-01-12T21:48:47.442Z", @@ -376,7 +376,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-19T22:17:01.161Z", "resolved_inferred": false, "started_at": "2025-12-19T17:22:14.735Z", @@ -389,7 +389,7 @@ "body": "Closing this courtesy notice.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-09T23:59:34.329Z", "resolved_inferred": false, "started_at": "2025-12-09T17:42:18.000Z", @@ -402,7 +402,7 @@ "body": "Hello CloudVision as a Service customers,\n\nWe have identified an issue impacting a small subset of customers where all EOS devices in a tenant were incorrectly marked as inactive. Importantly, the devices were actively streaming and all data and telemetry were generated and stored correctly.\n\nImpacted customers may have observed this incorrect streaming status displayed for several consecutive hours or days since November 25th, 2025. \n\nWe have identified the root cause and deployed an immediate fix. There is no action required from you as the customer. This is a courtesy notice only.\n\nIf you have any questions about this issue or if your tenant was affected, please reach out to support@arista.com.\n\nThank you for being a valued CloudVision as a Service customer.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-08T23:57:38.551Z", "resolved_inferred": false, "started_at": "2025-12-08T23:57:38.505Z", @@ -415,7 +415,7 @@ "body": "The data processing pipeline has fully recovered, and the service is now operating in a healthy state.\n\nThe ingestion of device telemetry data was not impacted during the incident. There was no data loss.\n\nPostmortem for this incident is still pending. Our team is currently actively working on reviewing this incident, and postmortem update.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-12T14:15:00.312Z", "resolved_inferred": false, "started_at": "2025-10-12T11:05:27.234Z", @@ -428,7 +428,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-16T19:01:13.690Z", "resolved_inferred": false, "started_at": "2025-09-16T18:38:05.616Z", @@ -441,7 +441,7 @@ "body": "This incident is resolved", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-11T23:17:38.156Z", "resolved_inferred": false, "started_at": "2025-09-11T18:00:35.380Z", @@ -454,7 +454,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-11T00:32:19.636Z", "resolved_inferred": false, "started_at": "2025-09-10T23:18:33.114Z", @@ -467,7 +467,7 @@ "body": "**Incident Report: CVaaS Service Disruption - September 8, 2025** \nOn September 8, 2025, CloudVision as-a-Service experienced a service disruption, lasting from 8 minutes in our UK region \\(cv-prod-uk-1\\) to 25 minutes in a US region \\(us-central1-a\\). During this time, users were unable to establish new connections, and transient connection errors occurred for those with existing connections.\n\nWe do not expect any data loss, as device state streaming was coalesced and resumed after the disruption. This incident was not caused by a security breach, intrusion, or other malicious activity.\n\n\u200c\n\n**Root Cause**\n\nAn internal certificate expired within our trust chain, causing a disruption. The certificate was not properly monitored in our system, which notifies and automatically renews certificates, leading to its expiration.\n\n\u200c\n\n**Our Response**\n\nOur team was alerted to similar service disruptions across various global regions, and a status page incident was posted because the issue was not transient and was unrelated to our service provider. The disruption was triaged, the root cause identified, and mitigations implemented within 20 minutes. Corrective actions were taken simultaneously over the next approximately 35 minutes. The incident was closed after an assessment of all regions was completed, and services were restored.\n\nWe understand that an outage of this nature is unacceptable and apologize to all affected CloudVision as-a-Service users impacted by this incident. We are committed to implementing changes identified during our internal investigation to prevent this type of failure from happening again.\n\nThank you for using CloudVision as-a-Service.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-08T15:35:04.842Z", "resolved_inferred": false, "started_at": "2025-09-08T12:56:47.000Z", @@ -480,7 +480,7 @@ "body": "## **Incident Report: CVaaS Service Disruption - September 1, 2025**\n\nOn September 1, 2025, CloudVision as-a-Service region cv-prod-euwest-2 experienced a disruption that lasted 2h. During this time some devices may have experienced state update becoming visible to be delayed up to those 2h. There was no data loss of device state. This incident was not due to a security breach, intrusion, or otherwise malicious activity.\u200c\n\n**Root Cause**\n\nThe root cause of this incident was caused by residual impact that was as described [in this incident](https://status.arista.io/incidents/7bcj2khfpqcy). Please find further details of root cause, and our response as described in this linked post.\n\nThank you for using CloudVision as-a-Service.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-02T05:38:02.043Z", "resolved_inferred": false, "started_at": "2025-09-02T03:38:10.444Z", @@ -493,7 +493,7 @@ "body": "## **Incident Report: CVaaS Service Disruption - September 1, 2025**\n\nOn September 1, 2025, CloudVision as-a-Service region cv-prod-euwest-2 experienced a disruption that lasted 11 hours and 48 minutes. During this time, the service was unable to ingest flow data successfully. As a result, a gap in data might be seen when viewing traffic flow dashboards, flows in Topology views, event-specific details related to traffic flows, or UNO-related product reporting during this period. This incident was not due to a security breach, intrusion, or otherwise malicious activity.\n\n \n**Root cause**\n\nThis outage was caused by a subset of our data becoming unreadable. The particular corner case was a result of a race condition found in a specific part of the system that controls data lifecycle and enforces access control through checking permissions. Successful authz is required for any CRUD operations on any part of our data to be successful. When we reach an inconsistent state as such, our system\u2019s default behavior is to fail close. This design, while protective, led to this incident where we could not successfully ingest and write flow data, and the system remained secure by design.\n\n \n**Our Response**\n\nOur team worked non-stop to resolve the issue. The extended duration of the outage was due to an initial misdiagnosis of the root cause. Once the correct cause was identified, our team was able to resolve the issue and restore full functionality within approximately 30 minutes.\n\nWe understand this broad outage and the impact on your experience is unacceptable. We sincerely apologize to all affected CloudVision as-a-Service users in the affected region. We are committed to implementing changes identified during our internal investigation to prevent this type of failure from happening again. \n\nThank you for using CloudVision as-a-Service.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-02T05:27:01.000Z", "resolved_inferred": false, "started_at": "2025-09-01T17:39:23.067Z", @@ -506,7 +506,7 @@ "body": "The fix has been deployed and this incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-01T14:26:29.658Z", "resolved_inferred": false, "started_at": "2025-09-01T14:09:08.656Z", @@ -519,7 +519,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-26T23:14:51.685Z", "resolved_inferred": false, "started_at": "2025-08-26T20:59:19.277Z", @@ -532,7 +532,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-21T18:36:43.756Z", "resolved_inferred": false, "started_at": "2025-08-21T17:41:34.013Z", @@ -545,7 +545,7 @@ "body": "This is a retroactive post for the event that occurred earlier today on us1b on August 13th, 8:30 UTC that lasted about 10 minutes.\n\nSome impact may have been user visible, such as:\n- Some events, such as \"Device stopped streaming\" or \"Streaming Latency Breached Threshold\" may have fired incorrectly during this period.\n- There may have been sporadic timeouts when viewing parts of the UI.\n- There may have been general slowdown of provisioning activities, potentially resulting in timeouts or errors.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-13T15:27:32.710Z", "resolved_inferred": false, "started_at": "2025-08-13T15:27:32.652Z", @@ -558,7 +558,7 @@ "body": "A fix has been implemented and performance has returned to normal.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-13T13:23:16.832Z", "resolved_inferred": false, "started_at": "2025-08-13T13:04:53.609Z", @@ -571,7 +571,7 @@ "body": "This is a retroactive post for the event that occurred on us1b on August 8th, 2:41 UTC that lasted about 10minutes.\n\nSome impact may have been user visible, such as:\n- There is no data loss, however due to delay in processing streamed device data, some events such as \"Device stopped streaming\" or \"Streaming Latency Breached Threshold\" may fire. Please note that there is no data loss and all data will be processed with some delay during the impact window.\n- There may be some stale data, or sporadic timeouts viewing parts of the UI.\n\nWe are currently investigating the issue and working on mitigation. Thank you for your patience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-08T16:23:41.446Z", "resolved_inferred": false, "started_at": "2025-08-08T16:23:41.400Z", diff --git a/api/v/array.json b/api/v/array.json index 71d02edf47ba2327dd8c078f9d8c3b0c897ac812..ef51666215f32aa24b745e362bc524db84b47eb2 100644 --- a/api/v/array.json +++ b/api/v/array.json @@ -3,7 +3,7 @@ "slug": "array", "platform": "statuspage", "status_url": "https://status.array.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "TransUnion services have remained stable, and we are no longer seeing the service issues impacting enrollments, Score Simulator, and report ordering. This incident is now resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-09-03T14:14:15.486-04:00", "resolved_inferred": false, "started_at": "2026-09-03T10:33:56.917-04:00", @@ -25,7 +25,7 @@ "body": "The issue affecting Financial Calculators has been resolved, and functionality has been fully restored. Our teams have confirmed that the calculators are operating as expected. Thank you for your patience while we worked to resolve this issue.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-31T18:02:15.807-04:00", "resolved_inferred": false, "started_at": "2026-08-31T10:07:07.000-04:00", @@ -38,7 +38,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-30T00:44:55.851-04:00", "resolved_inferred": false, "started_at": "2026-08-30T00:40:32.980-04:00", @@ -51,7 +51,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-30T01:16:01.784-04:00", "resolved_inferred": false, "started_at": "2026-08-29T23:29:04.881-04:00", @@ -64,7 +64,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-29T22:10:22.713-04:00", "resolved_inferred": false, "started_at": "2026-08-29T22:04:24.786-04:00", @@ -77,7 +77,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-21T13:46:43.370-04:00", "resolved_inferred": false, "started_at": "2026-08-21T12:05:29.537-04:00", @@ -90,7 +90,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-15T00:08:17.954-04:00", "resolved_inferred": false, "started_at": "2026-08-14T22:46:59.022-04:00", @@ -103,7 +103,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-12T04:06:42.902-04:00", "resolved_inferred": false, "started_at": "2026-08-12T03:15:44.450-04:00", @@ -116,7 +116,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-10T08:59:46.659-04:00", "resolved_inferred": false, "started_at": "2026-08-10T08:21:47.190-04:00", @@ -129,7 +129,7 @@ "body": "This issue has been resolved", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-06T16:44:34.380-04:00", "resolved_inferred": false, "started_at": "2026-08-05T10:26:21.297-04:00", @@ -142,7 +142,7 @@ "body": "This incident has been resolved", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-06T12:16:12.326-04:00", "resolved_inferred": false, "started_at": "2026-08-04T12:27:05.370-04:00", @@ -155,7 +155,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-30T20:09:40.090-04:00", "resolved_inferred": false, "started_at": "2026-07-30T18:20:18.633-04:00", @@ -168,7 +168,7 @@ "body": "This incident has been resolved and credit reports should now be returning data successfully.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-24T13:26:38.857-04:00", "resolved_inferred": false, "started_at": "2026-07-24T10:54:44.200-04:00", @@ -181,7 +181,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-14T14:01:33.347-04:00", "resolved_inferred": false, "started_at": "2026-07-14T11:54:47.950-04:00", @@ -194,7 +194,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-14T14:01:56.206-04:00", "resolved_inferred": false, "started_at": "2026-07-14T11:13:57.000-04:00", @@ -207,7 +207,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-13T01:55:29.771-04:00", "resolved_inferred": false, "started_at": "2026-07-13T01:18:58.332-04:00", @@ -220,7 +220,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-13T01:07:25.017-04:00", "resolved_inferred": false, "started_at": "2026-07-12T23:22:11.772-04:00", @@ -233,7 +233,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-11T00:06:41.136-04:00", "resolved_inferred": false, "started_at": "2026-07-10T19:16:02.548-04:00", @@ -246,7 +246,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-07T23:23:05.454-04:00", "resolved_inferred": false, "started_at": "2026-07-07T23:06:49.953-04:00", @@ -259,7 +259,7 @@ "body": "Services are restored", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-07T12:38:24.080-04:00", "resolved_inferred": false, "started_at": "2026-07-07T10:24:04.869-04:00", @@ -272,7 +272,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-06T11:40:47.044-04:00", "resolved_inferred": false, "started_at": "2026-07-06T10:31:18.000-04:00", @@ -285,7 +285,7 @@ "body": "We have reached out to TU to confirm if any issues on their end & monitoring.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-02T20:23:57.863-04:00", "resolved_inferred": false, "started_at": "2026-07-02T17:58:23.468-04:00", @@ -298,7 +298,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-01T17:10:13.361-04:00", "resolved_inferred": false, "started_at": "2026-07-01T16:07:49.172-04:00", @@ -311,7 +311,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-01T17:11:28.373-04:00", "resolved_inferred": false, "started_at": "2026-07-01T14:22:49.923-04:00", @@ -324,7 +324,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-01T13:33:08.373-04:00", "resolved_inferred": false, "started_at": "2026-07-01T12:31:34.011-04:00", @@ -337,7 +337,7 @@ "body": "This incident affecting white label websites has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-25T13:54:01.000-04:00", "resolved_inferred": false, "started_at": "2026-06-25T13:06:57.000-04:00", @@ -350,7 +350,7 @@ "body": "This incident in regards to latency in our response time has been resolved", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-15T15:03:29.158-04:00", "resolved_inferred": false, "started_at": "2026-06-15T14:03:36.744-04:00", @@ -363,7 +363,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-10T14:38:10.975-04:00", "resolved_inferred": false, "started_at": "2026-06-10T12:55:51.347-04:00", @@ -376,7 +376,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-04T14:20:10.432-04:00", "resolved_inferred": false, "started_at": "2026-06-04T13:02:15.000-04:00", @@ -389,7 +389,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-02T21:10:17.742-04:00", "resolved_inferred": false, "started_at": "2026-06-02T20:12:58.526-04:00", @@ -402,7 +402,7 @@ "body": "Service performance has remained stable, and we have not observed a recurrence of the previously reported impact to Identity Protection (IDP) and My Credit Manager (MCM) alerts following the mitigation efforts implemented earlier.\n\nAt this time, we are considering the incident resolved. Our teams will continue to monitor the affected services to confirm continued stability. We appreciate your patience and understanding throughout this incident.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-02T12:27:00.541-04:00", "resolved_inferred": false, "started_at": "2026-06-01T10:16:37.000-04:00", @@ -415,7 +415,7 @@ "body": "This incident has been resolved. Report pulls for My Credit Manager were operational as of 11:45 am ET", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-31T13:32:33.216-04:00", "resolved_inferred": false, "started_at": "2026-05-31T07:58:16.921-04:00", @@ -428,7 +428,7 @@ "body": "The issue affecting Privacy Protect has been resolved, and services have returned to normal operation.\n\nAs part of the recovery process, delayed verifications and affected background scans will continue to be processed throughout the afternoon. Clients may receive verification webhooks for records that were impacted during the incident, including some records that may no longer exist in their systems. Any verification webhooks that do not correspond to an active record on your end can be safely ignored.\n\nWe appreciate your patience and understanding throughout this incident.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-03T13:25:30.000-04:00", "resolved_inferred": false, "started_at": "2026-05-28T21:57:09.867-04:00", @@ -441,7 +441,7 @@ "body": "We have implemented a fix for this issue.\nHowever, users may still see duplicate records on their scan results as we clean up these records.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-27T20:17:40.373-04:00", "resolved_inferred": false, "started_at": "2026-05-27T16:41:49.796-04:00", @@ -454,7 +454,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-21T16:19:56.180-04:00", "resolved_inferred": false, "started_at": "2026-05-21T16:16:43.942-04:00", @@ -467,7 +467,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-21T16:15:00.420-04:00", "resolved_inferred": false, "started_at": "2026-05-21T15:47:29.358-04:00", @@ -480,7 +480,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-11T12:02:26.752-04:00", "resolved_inferred": false, "started_at": "2026-05-11T09:50:11.000-04:00", @@ -493,7 +493,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-09T04:20:06.623-04:00", "resolved_inferred": false, "started_at": "2026-05-08T17:49:50.000-04:00", @@ -506,7 +506,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-06T17:00:57.147-04:00", "resolved_inferred": false, "started_at": "2026-05-06T16:04:31.179-04:00", @@ -519,7 +519,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-06T16:22:41.237-04:00", "resolved_inferred": false, "started_at": "2026-05-06T15:49:44.793-04:00", @@ -532,7 +532,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-01T15:36:10.796-04:00", "resolved_inferred": false, "started_at": "2026-05-01T08:47:06.690-04:00", @@ -545,7 +545,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-27T15:29:52.937-04:00", "resolved_inferred": false, "started_at": "2026-04-27T14:45:48.000-04:00", @@ -558,7 +558,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-22T19:53:43.305-04:00", "resolved_inferred": false, "started_at": "2026-04-22T19:27:53.677-04:00", @@ -571,7 +571,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-14T17:53:49.434-04:00", "resolved_inferred": false, "started_at": "2026-04-14T17:48:52.418-04:00", @@ -584,7 +584,7 @@ "body": "This issue has been resolved. We\u2019re continuing to monitor performance to ensure everything remains stable.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-08T16:03:12.558-04:00", "resolved_inferred": false, "started_at": "2026-04-08T15:44:45.289-04:00", @@ -597,7 +597,7 @@ "body": "our monitoring indicated a low-volume occurrence of delayed response times for a small number of report storage / retrieval requests, we investigated and remediated.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-02T11:44:35.074-04:00", "resolved_inferred": false, "started_at": "2026-04-02T11:16:19.800-04:00", @@ -610,7 +610,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-01T18:19:22.857-04:00", "resolved_inferred": false, "started_at": "2026-04-01T17:41:59.000-04:00", @@ -623,7 +623,7 @@ "body": "All systems have stabilized all services to a steady state volume.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-31T16:03:46.723-04:00", "resolved_inferred": false, "started_at": "2026-03-31T15:31:39.980-04:00", @@ -636,7 +636,7 @@ "body": "We observed an issue with the RabbitMQ cluster in shared prod. The cluster was reconnected and services are restored.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-30T12:49:47.464-04:00", "resolved_inferred": false, "started_at": "2026-03-30T12:04:31.000-04:00", @@ -649,7 +649,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-19T07:32:24.970-04:00", "resolved_inferred": false, "started_at": "2026-03-19T03:18:50.406-04:00", diff --git a/api/v/ashby.json b/api/v/ashby.json index 4b1076248a13b9e32c5aa74434a4060d0c5c2a49..b02ce31e04c5223dba4e53ed6a4a2e65c78e7147 100644 --- a/api/v/ashby.json +++ b/api/v/ashby.json @@ -3,7 +3,7 @@ "slug": "ashby", "platform": "statuspage", "status_url": "https://status.ashbyhq.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "Our upstream provider has resolved the issue.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-31T18:11:38.708Z", "resolved_inferred": false, "started_at": "2026-08-31T17:44:26.072Z", @@ -25,7 +25,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-09T13:00:20.391Z", "resolved_inferred": false, "started_at": "2026-08-07T19:11:00.100Z", @@ -38,7 +38,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-27T21:12:55.243Z", "resolved_inferred": false, "started_at": "2026-07-27T14:56:43.923Z", @@ -51,7 +51,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-16T11:00:55.444Z", "resolved_inferred": false, "started_at": "2026-07-16T08:40:00.000Z", @@ -64,7 +64,7 @@ "body": "For approximately 11 minutes from 10:19 AM PDT to 10:30 AM PDT, Ashby users experienced long-running loading screens and, in some cases, errors. This was the result of requests to our servers taking too long to respond. Candidates applying for jobs were unaffected.\n\nOur maintenance this weekend will address the root cause of this issue by increasing our database capacity.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-13T17:19:00.000Z", "resolved_inferred": false, "started_at": "2026-07-13T17:19:00.000Z", @@ -77,7 +77,7 @@ "body": "This incident has been resolved. Resumes that failed to parse during the incident have been backfilled.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-08T04:17:54.867Z", "resolved_inferred": false, "started_at": "2026-07-08T00:40:32.296Z", @@ -90,7 +90,7 @@ "body": "From 11:30am until 1:40pm PDT, candidate PDF exports failed with a generic message. The cause of this issue has already been identified and fixed.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-06T18:30:00.000Z", "resolved_inferred": false, "started_at": "2026-07-06T18:30:00.000Z", @@ -103,7 +103,7 @@ "body": "Our upstream provider, Cloudflare, has implemented a fix and our tests indicate they have resolved the issue.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-02T02:14:47.126Z", "resolved_inferred": false, "started_at": "2026-07-01T20:19:55.143Z", @@ -116,7 +116,7 @@ "body": "We've confirmed Ashby is available again in the Sydney region. We will work with our upstream provider to understand what happened.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-01T19:03:07.080Z", "resolved_inferred": false, "started_at": "2026-07-01T18:49:25.490Z", @@ -129,7 +129,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-24T22:21:00.145Z", "resolved_inferred": false, "started_at": "2026-06-24T21:16:01.044Z", @@ -142,7 +142,7 @@ "body": "We're experiencing an issue sending Slack and email notifications for interview reminders between 4:00PM and 5:00PM (UTC)", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-24T16:00:00.000Z", "resolved_inferred": false, "started_at": "2026-06-24T16:00:00.000Z", @@ -155,7 +155,7 @@ "body": "We're experiencing an issue sending Slack and email notifications for interview reminders between 4:00PM and 7:00PM (UTC)", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-22T16:00:00.000Z", "resolved_inferred": false, "started_at": "2026-06-22T16:00:00.000Z", @@ -168,7 +168,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-19T14:20:28.773Z", "resolved_inferred": false, "started_at": "2026-06-19T13:47:54.028Z", @@ -181,7 +181,7 @@ "body": "Integrations degraded due to an infrastructure issue. Affected services include Google Workspace integration (including sending via Gmail); ATS syncs; autocomplete for candidate resumes/locations; and some AI features.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-19T06:30:00.000Z", "resolved_inferred": false, "started_at": "2026-06-19T06:30:00.000Z", @@ -194,7 +194,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-16T09:22:02.333Z", "resolved_inferred": false, "started_at": "2026-06-16T08:21:44.130Z", @@ -207,7 +207,7 @@ "body": "## **Summary**\n\nOn Monday, June 15, from approximately 4:00 AM PDT to 10:26 AM PDT, Safari and iOS users encountered an error with embedded and Ashby-hosted job boards \\([jobs.ashbyhq.com](http://jobs.ashbyhq.com)\\) and could not view or apply to jobs.\u00a0\n\nWe became aware of the problem at 9:43 AM PDT and recovered at 10:26 AM PDT.\n\n## **Why did this happen?**\n\nAshby's internal code build process processes the code that powers your hosted and embedded job boards. As part of our security practices, each file is published with verification data that browsers use to confirm the file they download is exactly what we intend to serve. We shipped a change to this build process that modified the files after their verification data had been generated, so the files no longer matched the verification data and failed to load in Safari and iOS mobile browsers. The same files did not fail in the same way in other browsers, such as Chrome and Firefox, which is why the failure appeared inconsistent amongst visitors.\n\n## **How did we resolve this situation?**\n\nAfter confirming the failure was tied to a recent deploy, we rolled back to a known-good state to restore service. We confirmed that job boards loaded correctly in Safari, on mobile devices, and in other browsers before resuming normal deployments.\n\n## **How did we get to this point?**\n\nThe change altered our shipped code in a way we did not anticipate, and two gaps let it reach production undetected:\u00a0\n\n1. Our automated job board tests ran only against Chrome.\n2. We didn\u2019t have a check verifying file integrity at the point of publishing, where this particular failure surfaced.\n\n## **What have we put in place to prevent this from happening in the future?**\n\n1. We added an automated check that verifies file integrity immediately before publishing; any mismatch now blocks the deployment of updates to Ashby. We confirmed it catches this exact failure.\n2. We corrected how integrity verification is applied to our job board code, so that all browsers enforce it consistently.\n3. We expanded our automated job board tests to run against Safari and Firefox, not just Chrome.\n4. We have added additional monitoring, including on mobile browsers, to alert us directly when a job board fails to load in this way.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-15T19:15:43.381Z", "resolved_inferred": false, "started_at": "2026-06-15T16:59:16.420Z", @@ -220,7 +220,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-02T21:57:01.078Z", "resolved_inferred": false, "started_at": "2026-06-02T14:55:08.350Z", @@ -233,7 +233,7 @@ "body": "## **Summary**\n\nOn Sunday, May 31st, at 10pm PST, Ashby was slow and had a high error rate for approximately 1 hour, from 10pm to 11:10pm \\(PST\\).\n\nDuring this time, the Ashby main application would have been slow, and approximately 50% of user actions would have resulted in Ashby displaying an error. Some candidates may have noticed a slower response to their job applications, but all applications were successful and none were lost.\n\n## **Why did this happen?**\n\nOn Sunday, May 31st, at 4pm PST, an account with one of our AI providers became unavailable. As a result, calls to that provider started to error. These calls are configured to automatically retry periodically until they succeed, but the retries caused a steady increase in the number of such calls per minute. In turn, this drained the capacity of a shared subsystem that manages many different processes at Ashby.\n\nIn particular, that shared subsystem is used for storing user session data. As the shared subsystem became overwhelmed, user sessions became slower to respond.\n\nThis caused requests to our web servers to take significantly longer to process. Which then caused our web servers to begin running out of capacity.\n\nAt 6am, capacity reached a critical low. At this point, our system began rejecting user actions. This is done to prevent complete system failure.\n\n## **How did we resolve the situation?**\n\nAt 10:04pm PST, our on-call engineers were notified. By 10:16pm PST, our on-call engineers were beginning an investigation.\n\nAt 11:03pm PST, we identified the subsystem that had reached capacity.\n\nAt 11:07pm PST, we stopped processing certain types of automated actions.\n\nAt 11:09pm PST, we identified the issue with the external provider and rectified it immediately.\n\nAt 11:10pm PST, error rates were down to 10%.\n\nAt 11:20pm PST, error rates were down to normal levels \\(~0%\\).\n\nAt 11:54pm PST, normal service was resumed, and no data was lost.\n\n## **What have we put in place to prevent it from happening in the future?**\n\nWe\u2019ve done an internal postmortem on this incident and have implemented or plan to implement a variety of changes that achieve three things:\n\n1. Reduced the likelihood of future failure\n2. Faster incident response times\n3. Lower impact on customers in the event of failure\n\nSpecifically, we have done the following:\n\n* We were already in the process of replacing the subsystem at the center of the outage. We have accelerated that work. The replacement is not vulnerable to this particular kind of failure.\n* We\u2019ve added additional monitoring around our AI providers to alert us to failures like this sooner.\n* We are prioritizing a fix for the retry mechanism that led to this incident.\n* We are migrating our user session storage to a new subsystem that is not vulnerable to this particular kind of failure.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-01T09:04:00.602Z", "resolved_inferred": false, "started_at": "2026-06-01T06:33:08.355Z", @@ -246,7 +246,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-29T15:55:09.399Z", "resolved_inferred": false, "started_at": "2026-05-29T13:41:51.731Z", @@ -259,7 +259,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-28T15:14:38.306Z", "resolved_inferred": false, "started_at": "2026-05-28T13:34:26.412Z", @@ -272,7 +272,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-15T21:59:10.226Z", "resolved_inferred": false, "started_at": "2026-05-15T21:10:11.507Z", @@ -285,7 +285,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-15T00:58:53.849Z", "resolved_inferred": false, "started_at": "2026-05-15T00:19:30.985Z", @@ -298,7 +298,7 @@ "body": "The issue has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-01T00:13:02.842Z", "resolved_inferred": false, "started_at": "2026-03-31T22:43:10.120Z", @@ -311,7 +311,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-24T18:51:04.355Z", "resolved_inferred": false, "started_at": "2026-03-24T15:43:13.025Z", @@ -324,7 +324,7 @@ "body": "### **Summary**\n\nFor a brief period on Monday, March 24, and from Tuesday, March 25 to Thursday, March 27, 2026, Ashby's scheduling features displayed incorrect interviewer availability for a subset of organizations with the\u00a0 Google Workspace integration. This allowed candidates to be scheduled even when an interviewer may already have a meeting. This bug affected the following scheduling features:\n\n* Manual scheduling\n* Direct booking links\n* Advanced scheduling\n\nThe issue only impacted organizations using Google Calendar sync without domain-wide delegation.\n\n### **Why did this happen?**\n\nAshby integrates with Google Calendar to display interviewer availability and power our scheduling features. Because some interviewers aren\u2019t authenticated Ashby users, we occasionally read their calendar data on behalf of a user who is. A code change deployed on March 24 updated the calendar synchronization logic as part of an improvement to our Google Calendar authorization process. A bug in this logic incorrectly conflated the interviewer\u2019s calendar with the authenticated user's, resulting in inaccurate availability being displayed during scheduling.\n\nThe code change was initially deployed on March 24, then briefly reverted, and redeployed on March 25, which is why there were separate windows of impact.\n\n### **How did we resolve the situation?**\n\nThe bug was active during three separate windows:\n\n* Monday, March 24, 8:21 AM - 9:52 AM PDT \\(approximately 1.5 hours\\)\u00a0\n* Tuesday, March 25, 7:05 AM - 7:52 AM PDT \\(approximately 47 minutes\\)\u00a0\n* Tuesday, March 25, 9:52 AM - Thursday, March 27, 5:34 AM PDT \\(approximately 44 hours\\)\u00a0\n\nOn Thursday, March 27, 2026, at 4:31 AM PDT, a customer reported that an interviewer\u2019s availability appeared incorrect. At 5:10 AM PDT, we identified the root cause, and at 5:34 AM PDT, we deployed a fix and triggered calendar resyncs for affected organizations to restore accurate availability data.\n\n### **What have we put in place to prevent it from happening in the future?**\n\n1. **Improved static analysis checks.** We improved static analysis checks to ensure similar code changes are analyzed for correctness before they reach production.\u00a0\n2. **Improved testing for calendar authorization scenarios.** The bug affected a specific authorization configuration that is difficult to replicate in our test environments. We are building improved test tooling to enable automated tests across even more permutations of integration configurations.\n3. **Better monitoring for calendar sync accuracy.** We are adding monitoring that will alert us when calendar data retrieved through this particular authorization path does not match the intended user.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-24T15:00:00.000Z", "resolved_inferred": false, "started_at": "2026-03-24T15:00:00.000Z", @@ -337,7 +337,7 @@ "body": "The incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-12T16:15:13.262Z", "resolved_inferred": false, "started_at": "2026-03-12T15:47:36.617Z", @@ -350,7 +350,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-12T13:07:44.681Z", "resolved_inferred": false, "started_at": "2026-03-12T12:56:30.491Z", @@ -363,7 +363,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-04T20:44:31.122Z", "resolved_inferred": false, "started_at": "2026-03-04T19:59:54.223Z", @@ -376,7 +376,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-24T17:36:46.223Z", "resolved_inferred": false, "started_at": "2026-02-24T16:35:58.809Z", @@ -389,7 +389,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-20T19:45:52.776Z", "resolved_inferred": false, "started_at": "2026-02-20T18:59:07.761Z", @@ -402,7 +402,7 @@ "body": "The issue has been resolved by the upstream provider.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-13T10:15:33.592Z", "resolved_inferred": false, "started_at": "2026-02-13T05:10:17.969Z", @@ -415,7 +415,7 @@ "body": "Resolved: Reporting data is now up to date. Thank you for your patience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-12T18:46:13.008Z", "resolved_inferred": false, "started_at": "2026-02-12T16:30:50.651Z", @@ -428,7 +428,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-04T17:46:31.992Z", "resolved_inferred": false, "started_at": "2026-02-04T16:46:56.128Z", @@ -441,7 +441,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-23T13:16:05.295Z", "resolved_inferred": false, "started_at": "2026-01-22T22:00:22.000Z", @@ -454,7 +454,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-20T22:49:52.884Z", "resolved_inferred": false, "started_at": "2026-01-20T16:30:37.000Z", @@ -467,7 +467,7 @@ "body": "We've implemented a fix and verified offer templates and workflows are working.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-06T18:21:12.059Z", "resolved_inferred": false, "started_at": "2026-01-06T17:52:38.000Z", @@ -480,7 +480,7 @@ "body": "Dropbox Sign has resolved their downtime, and we've verified e-signature works in Ashby.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-02T23:36:38.725Z", "resolved_inferred": false, "started_at": "2026-01-02T21:12:50.120Z", @@ -493,7 +493,7 @@ "body": "We saw elevated errors loading candidate profiles and sending emails starting at 12:08 UTC.\n\nWe resolved this at 12:56 UTC.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-16T12:08:00.000Z", "resolved_inferred": false, "started_at": "2025-12-16T12:08:00.000Z", @@ -506,7 +506,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-05T09:46:46.687Z", "resolved_inferred": false, "started_at": "2025-12-05T09:07:15.618Z", @@ -519,7 +519,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-04T21:18:09.760Z", "resolved_inferred": false, "started_at": "2025-12-04T19:25:56.850Z", @@ -532,7 +532,7 @@ "body": "Cloudflare's scheduled maintenance is finished, and we're no longer seeing any service degradation.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-03T19:03:07.010Z", "resolved_inferred": false, "started_at": "2025-12-03T15:58:33.000Z", @@ -545,7 +545,7 @@ "body": "Ashby-hosted job boards are operational again. We have identified the root cause and are addressing it.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-02T13:44:53.944Z", "resolved_inferred": false, "started_at": "2025-12-02T13:37:41.005Z", @@ -558,7 +558,7 @@ "body": "We have noticed increased errors loading https://app.ashbyhq.com.\nThe issue has been resolved and the app is responsive again.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-20T12:14:35.986Z", "resolved_inferred": false, "started_at": "2025-11-20T12:14:35.939Z", @@ -571,7 +571,7 @@ "body": "We have resolved an issue that caused errors with manually rescheduling candidates between 9:10 AM and 10:30 AM UTC.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-17T10:42:59.642Z", "resolved_inferred": false, "started_at": "2025-11-17T10:42:59.583Z", @@ -584,7 +584,7 @@ "body": "We have deployed changes that mitigate this issue.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-08T02:11:07.655Z", "resolved_inferred": false, "started_at": "2025-11-07T19:42:59.404Z", @@ -597,7 +597,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-29T23:08:49.315Z", "resolved_inferred": false, "started_at": "2025-10-29T22:45:34.890Z", @@ -610,7 +610,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-25T07:08:42.798Z", "resolved_inferred": false, "started_at": "2025-10-24T20:14:16.658Z", @@ -623,7 +623,7 @@ "body": "## **Summary**\n\nOn October 22, 2025, Ashby was unavailable for approximately 20 minutes \\(4:00 PM to 4:19 PM UTC\\). Due to a bug introduced five hours earlier, a critical service in Ashby\u2019s infrastructure began to fail, causing our application to become unavailable. Customer job boards remained functional during this period.\n\nOnce we resolved the availability issue, we disabled the Workday and Analytics syncs and gradually increased their frequency over approximately 1 hour and 45 minutes, from 5:29 PM UTC to 7:15 PM UTC.\n\n## **Why did this happen?**\n\nBefore the incident, a bug was introduced to our application code that ran on an automated schedule. Over the course of five hours, the bug caused an increasing amount of network traffic to a critical service that the application code communicated with. Approximately 10 minutes before the incident, the increased network traffic caused a sudden spike in memory usage on the virtual machine hosting the critical service, resulting in the virtual machine running out of memory and the service failing.\u00a0\n\n## **How did we resolve the situation?**\n\nOn Thursday, October 22, 2025, at 10:48AM UTC, we deployed the application code change containing the bug.\n\nAt 4:00 PM UTC, various automated monitors alerted our team that Ashby was unavailable, and an incident was initiated by our On-call Engineer.\n\nAt 4:09 PM UTC, we determined the service failed due to the virtual machine running out of memory and began the process of failing over the service to a backup virtual machine.\n\nAt 4:19PM UTC, the service was restored, and we confirmed Ashby was available.\n\nAt 4:33PM UTC, we identified the probable cause and began reverting the change that introduced the bug.\n\nAt 6:09PM UTC, we verified the bug we suspected was the root cause. At 6:15PM UTC, the revert was shipped to production.\n\nAt 6:16PM UTC, out of an abundance of caution, we slowly increased the frequency the application code was run while monitoring the critical service it communicated with.\n\nAt 7:15 PM UTC, we felt confident that we had removed any effects introduced by the identified bug and restored the application code to its normal schedule. Because we hadn\u2019t run the normal schedule for several hours, it would take time for the application code to go through the backlog of tasks it needed to perform.\n\nAt 8:07PM UTC, the backlog of tasks was completed, and we resolved the incident.\n\n## **What have we put in place to prevent it from happening in the future?**\n\nOnce we identified the root cause and resolved the incident, we immediately implemented two changes to detect or prevent this issue from recurring:\n\n* **Monitors that detect and alert our team to outliers in network traffic to our critical service.**\n* **We deployed a change that removed the network traffic side effect that caused the incident.** The bug uncovered this side effect.\n\n**Our team has also committed to moving the critical service that failed to virtual machines that auto-scale.** One of the reasons the critical service failed was that we had explicitly allocated a specific amount of memory for the virtual machine, and when that limit was reached, the machine failed. We will be transitioning this service to one that enables our cloud service provider to automatically scale both the size \\(including available memory\\) and the number of machines on which the service runs.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-22T20:07:00.952Z", "resolved_inferred": false, "started_at": "2025-10-22T16:06:36.330Z", @@ -636,7 +636,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-22T17:36:30.745Z", "resolved_inferred": false, "started_at": "2025-10-22T13:53:49.563Z", @@ -649,7 +649,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-21T21:37:30.789Z", "resolved_inferred": false, "started_at": "2025-10-21T18:30:46.000Z", diff --git a/api/v/assembled.json b/api/v/assembled.json index 1ef8ed7bbcf3bb788d3c55f873c0c862a5e12708..1990fe7801c36cb997ace7aaac0269d6d0be8da7 100644 --- a/api/v/assembled.json +++ b/api/v/assembled.json @@ -3,7 +3,7 @@ "slug": "assembled", "platform": "statuspage", "status_url": "https://status.assembled.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-31T19:14:41.481Z", "resolved_inferred": false, "started_at": "2026-08-31T17:30:32.201Z", @@ -25,7 +25,7 @@ "body": "The underlying issue has been resolved. \n\n**Action from your team is required.** A Salesforce admin will need to reauthenticate the connection to restore syncing. In Assembled, go to Configure \u2192 Third-Party Integrations \u2192 Integrations, find Salesforce, disable the connection, then reconnect using an active admin account. Once reauthenticated, our team will help ensure your data syncs properly again. \n\nPlease contact support@assembled.com once you've reauthenticated your Salesforce integration in Assembled.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-21T04:53:03.823Z", "resolved_inferred": false, "started_at": "2026-08-21T01:54:20.002Z", @@ -38,7 +38,7 @@ "body": "We've identified and address the root cause and are now operating normally again.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-22T23:50:45.518Z", "resolved_inferred": false, "started_at": "2026-07-22T23:11:14.000Z", @@ -51,7 +51,7 @@ "body": "Increased load in API requests affected our APIs and Voice services, leading to increased latency. For voice, we temporarily diverted traffic to live agents as we investigated and resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-20T15:00:00.000Z", "resolved_inferred": false, "started_at": "2026-07-20T15:00:00.000Z", @@ -64,7 +64,7 @@ "body": "We've returned to normal levels of latency and error rates across all services.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-15T17:24:12.504Z", "resolved_inferred": false, "started_at": "2026-07-15T00:40:22.912Z", @@ -77,7 +77,7 @@ "body": "All APIs and the Assembled web application are fully functional.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-13T18:53:40.706Z", "resolved_inferred": false, "started_at": "2026-07-13T15:30:47.000Z", @@ -90,7 +90,7 @@ "body": "Data affected during the period has been successfully retried.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-10T17:56:07.389Z", "resolved_inferred": false, "started_at": "2026-07-10T16:52:55.000Z", @@ -103,7 +103,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-09T21:24:53.204Z", "resolved_inferred": false, "started_at": "2026-07-09T21:13:08.362Z", @@ -116,7 +116,7 @@ "body": "Between 2:07pm ET to 2:25pm ET, our retrieval of agent states and tickets was delayed and we were not receiving data during this time. Our engineering team has resolved the issue and is applying agent state exclusions for any affected customers during this time period.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-10T18:07:00.000Z", "resolved_inferred": false, "started_at": "2026-06-10T18:07:00.000Z", @@ -129,7 +129,7 @@ "body": "After continued monitoring, we have confirmed that all systems remain fully restored and reporting data is displaying as expected. This incident is now resolved. Thank you for your patience throughout this process.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-04T15:01:03.370Z", "resolved_inferred": false, "started_at": "2026-06-01T00:02:57.369Z", @@ -142,7 +142,7 @@ "body": "Reporting data is now fully up to date.\n\nAll operations related to the database upgrade are now complete.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-30T08:05:07.310Z", "resolved_inferred": false, "started_at": "2026-05-30T05:38:39.580Z", @@ -155,7 +155,7 @@ "body": "This incident has been resolved. A database operation degraded performance, which caused pages across the product to become unresponsive. We\u2019re reviewing our database operation safeguards and monitoring to reduce the likelihood of similar issues in the future.\n\n[6:53 AM PT ] Our voice agent is still unavailable as the system recovers, but we are successfully able to transfer callers to a live agent upon error.\n\n[7:08 AM PT] The voice agent is healthy and available.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-15T13:53:41.000Z", "resolved_inferred": false, "started_at": "2026-05-15T13:44:57.000Z", @@ -168,7 +168,7 @@ "body": "This incident has been resolved. A database operation degraded performance, which caused pages across the product to become unresponsive. We\u2019re reviewing our database operation safeguards and monitoring to reduce the likelihood of similar issues in the future.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-12T18:23:17.000Z", "resolved_inferred": false, "started_at": "2026-05-12T18:03:02.000Z", @@ -181,7 +181,7 @@ "body": "Between 6:30pm ET on May 6th and 7am ET on May 7th, some customers saw missing or zero values in reporting surfaces (including support volume and queue/exclusion views) for data values that appeared after 6:30pm ET on 5/6/2026 due to delayed replication in one of our data-processing tasks. \n\nData ingestion itself continued normally and no conversation data was lost, the issue was isolated to metric freshness/display. \n\nWe restored the task, backfilled dependent metrics, and service is now operating normally, with additional monitoring improvements underway to prevent recurrence.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-07T11:15:47.000Z", "resolved_inferred": false, "started_at": "2026-05-07T11:15:47.000Z", @@ -194,7 +194,7 @@ "body": "The issue with proxied APIs in workflows has now been resolved and they work as expected.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-29T00:01:40.927Z", "resolved_inferred": false, "started_at": "2026-04-28T23:46:59.488Z", @@ -207,7 +207,7 @@ "body": "Between 10:56 AM and 11:09 AM PT, a subset of sync jobs responsible for retrieving agent states and ticket updates experienced intermittent failures. The underlying issue has been identified and resolved, and we have verified that all affected ticket updates are now backfilling any data.\n\nWe've also added a system-level agent state exclusion to ensure that these failures do not affect adherence and are conducting a postmortem to identify any system improvements that can be made.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-24T18:21:05.027Z", "resolved_inferred": false, "started_at": "2026-04-24T18:21:04.973Z", @@ -220,7 +220,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-30T17:40:28.441Z", "resolved_inferred": false, "started_at": "2026-03-30T17:18:56.700Z", @@ -233,7 +233,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-06T19:27:21.572Z", "resolved_inferred": false, "started_at": "2026-03-06T16:17:59.402Z", @@ -246,7 +246,7 @@ "body": "Upstream provider service outage caused the Assembled voice agent to experience elevated latency and error rates. Once root cause was confirmed, we proactively diverted all traffic to human agents.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-05T00:51:56.000Z", "resolved_inferred": false, "started_at": "2026-03-05T00:51:56.000Z", @@ -259,7 +259,7 @@ "body": "This incident has been resolved, and we will continue to recover past data into Assembled", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-03T17:16:05.080Z", "resolved_inferred": false, "started_at": "2026-03-03T12:57:27.195Z", @@ -272,7 +272,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-26T22:58:52.338Z", "resolved_inferred": false, "started_at": "2026-02-26T22:31:44.735Z", @@ -285,7 +285,7 @@ "body": "We have identified and resolved the issue with Copilot\u2019s Draft reply. The root cause was an upstream model provider intermittently returning responses in an unexpected format that bypassed our existing fallback logic. We're identifying improvements to prevent future impact on customers.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-24T21:35:52.000Z", "resolved_inferred": false, "started_at": "2026-02-24T21:05:15.000Z", @@ -298,7 +298,7 @@ "body": "All forecasts have been regenerated and the incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-21T00:00:56.000Z", "resolved_inferred": false, "started_at": "2025-12-19T19:35:10.553Z", @@ -311,7 +311,7 @@ "body": "We've fixed the bug causing errors on the staffing timeline. We apologize for the inconvenience!", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-17T21:37:47.921Z", "resolved_inferred": false, "started_at": "2025-12-17T21:04:11.332Z", @@ -324,7 +324,7 @@ "body": "Voice agent experiencing increased latency", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-14T11:00:00.000Z", "resolved_inferred": false, "started_at": "2025-11-14T11:00:00.000Z", @@ -337,7 +337,7 @@ "body": "All services are now operational.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-20T22:30:52.588Z", "resolved_inferred": false, "started_at": "2025-10-20T14:57:01.000Z", @@ -350,7 +350,7 @@ "body": "A fix has been implemented from our provider and we've seen almost all of our underlying services recover. We'll be adding agent state exclusions for the affected time period and will continue to monitor other services as they come back online.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-20T10:44:33.876Z", "resolved_inferred": false, "started_at": "2025-10-20T10:23:00.563Z", @@ -363,7 +363,7 @@ "body": "Activities should now be syncing successfully into Google Calendar from Assembled.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-23T07:45:26.000Z", "resolved_inferred": false, "started_at": "2025-09-23T03:00:45.855Z", @@ -376,7 +376,7 @@ "body": "This incident has been resolved. Google has published a report regarding this issue: https://www.google.com/appsstatus/dashboard/incidents/oFcAZTr4EVieF5Fr6Ee9", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-18T16:33:29.746Z", "resolved_inferred": false, "started_at": "2025-09-18T15:13:07.683Z", @@ -389,7 +389,7 @@ "body": "From 12:23 PM PT to 3:02 PM PT, chat handoffs were not functioning correctly. Conversations were not actually being handed off to human agents, and on the QA review page only the first message was visible even though conversations continued.\n\nThe issue has been fully resolved going forward. We are also investigating options for retrieving the missing conversation data from the affected time window.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-10T19:23:00.000Z", "resolved_inferred": false, "started_at": "2025-09-10T19:23:00.000Z", @@ -402,7 +402,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-21T19:37:07.971Z", "resolved_inferred": false, "started_at": "2025-08-21T19:24:31.756Z", @@ -415,7 +415,7 @@ "body": "Our upstream provider has resolved the incident, so our system is once again back in a healthy state to receive calls.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-06T04:30:03.816Z", "resolved_inferred": false, "started_at": "2025-08-06T02:50:31.970Z", @@ -428,7 +428,7 @@ "body": "From 10:15am PT to 12:32 PT, agent messages sent from CRM platforms (Zendesk, Kustomer, etc.) were not appearing in the chat widget to end customers. This would occur for any messages escalated to live chat, but did not affect email handoff messages.\n\nWe've identified and resolved the issue and the full functionality for live chat is restored. We'll be conducting a full postmortem of this incident.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-04T19:46:08.740Z", "resolved_inferred": false, "started_at": "2025-08-04T19:46:08.675Z", diff --git a/api/v/atera.json b/api/v/atera.json index ac97e5164c98cfdcc6cf9d454744ec3cfe73ed51..31fcf4b60388bd9474e8963a852e26e152e1dc3b 100644 --- a/api/v/atera.json +++ b/api/v/atera.json @@ -3,7 +3,7 @@ "slug": "atera", "platform": "statuspage", "status_url": "https://status.atera.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "This incident has been resolved", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-22T03:21:38.197-04:00", "resolved_inferred": false, "started_at": "2026-06-22T00:10:15.920-04:00", @@ -25,7 +25,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-23T09:52:47.148-04:00", "resolved_inferred": false, "started_at": "2026-06-11T15:15:32.000-04:00", @@ -38,7 +38,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-09T08:31:19.381-04:00", "resolved_inferred": false, "started_at": "2026-06-09T03:31:52.790-04:00", @@ -51,7 +51,7 @@ "body": "The issue has been identified and resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-02T18:50:20.591-04:00", "resolved_inferred": false, "started_at": "2026-04-02T15:26:29.475-04:00", @@ -64,7 +64,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-09T13:11:34.294-04:00", "resolved_inferred": false, "started_at": "2026-03-09T11:14:12.039-04:00", @@ -77,7 +77,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-09T11:24:52.342-04:00", "resolved_inferred": false, "started_at": "2026-03-09T10:01:57.047-04:00", @@ -90,7 +90,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-22T14:08:49.676-05:00", "resolved_inferred": false, "started_at": "2026-02-22T11:43:39.540-05:00", @@ -103,7 +103,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-11T20:30:04.721-05:00", "resolved_inferred": false, "started_at": "2026-02-11T18:47:59.356-05:00", @@ -116,7 +116,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-12T10:08:23.557-05:00", "resolved_inferred": false, "started_at": "2026-01-12T06:48:51.009-05:00", @@ -129,7 +129,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-12T06:38:53.881-05:00", "resolved_inferred": false, "started_at": "2026-01-12T05:28:29.564-05:00", @@ -142,7 +142,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-05T02:47:08.128-05:00", "resolved_inferred": false, "started_at": "2026-01-05T02:22:16.905-05:00", @@ -155,7 +155,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-05T05:18:41.637-05:00", "resolved_inferred": false, "started_at": "2025-12-05T04:11:54.789-05:00", @@ -168,7 +168,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-18T11:12:57.623-05:00", "resolved_inferred": false, "started_at": "2025-11-18T07:15:58.000-05:00", @@ -181,7 +181,7 @@ "body": "Fix: This issue has been fully resolved in collaboration with Microsoft.\nAction Required: You can now safely download and install the latest MSI installer", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-11T09:04:40.116-04:00", "resolved_inferred": false, "started_at": "2025-09-11T03:40:15.000-04:00", diff --git a/api/v/athennian.json b/api/v/athennian.json index 4ef04aa2aa6a9fbd027743bc3cc6e3ef6abbc162..fc53b51b02e6b5b8a1b5cc1e2df64e88cffc2e6a 100644 --- a/api/v/athennian.json +++ b/api/v/athennian.json @@ -3,7 +3,7 @@ "slug": "athennian", "platform": "statuspage", "status_url": "https://athennian.statuspage.io", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "degraded", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "This incident has been resolved. The issue causing documents and folders to appear missing in Minute Books for a subset of entities has been fixed, and we've confirmed normal behavior is restored. If you continue to experience any issues, please contact support.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-28T21:51:04.540-06:00", "resolved_inferred": false, "started_at": "2026-08-28T11:30:20.000-06:00", @@ -25,7 +25,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-06T16:47:10.853-07:00", "resolved_inferred": false, "started_at": "2026-03-06T14:30:01.313-07:00", @@ -38,7 +38,7 @@ "body": "The site is currently back online, though some components may still experience intermittent degradation or elevated latency.\n\nAWS continues to work on restoring the affected infrastructure and services within the Middle East region. While our primary services are recovering, we are keeping the incident open as we monitor system stability and wait for final confirmation of full resolution from AWS.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "started_at": "2026-03-02T10:27:22.000-07:00", "state": "monitoring", "title": "AWS Middle East Region Disruption", @@ -49,7 +49,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-18T13:51:25.319-07:00", "resolved_inferred": false, "started_at": "2025-11-18T07:42:48.315-07:00", diff --git a/api/v/atlassian-access.json b/api/v/atlassian-access.json index f6cf46278ee89a0c219f46103bfbc0f1983498c7..90f7517f511c27ffdf9a0e32a7e905c53fb686cf 100644 --- a/api/v/atlassian-access.json +++ b/api/v/atlassian-access.json @@ -3,7 +3,7 @@ "slug": "atlassian-access", "platform": "statuspage", "status_url": "https://access.status.atlassian.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "### Summary\n\nOn May 14, 2026, between 04:30 and 05:26 UTC, Atlassian customers experienced widespread service disruption across multiple Atlassian Cloud products. The issue was caused by a race condition in our internal deployment orchestration platform during a routine rollback operation of a core identity service in the us-east region. This race condition resulted in insufficient capacity for the identity service in the affected region which started returning errors to dependent products. The incident was detected within a minute by automated monitoring systems and mitigated in 56 minutes.\n\n### **IMPACT**\n\nDuring the incident, customers attempting to access Atlassian Cloud products in the us-east region experienced authentication and permission failures and were unable to access services. Customers also experienced errors when accessing the support portal until Atlassian fell back to an alternate support method. This was caused by a core identity service in the us-east region becoming unavailable. Affected products included Atlassian Administration, Atlassian Analytics, Bitbucket, Compass, Confluence, Jira, Jira Product Discovery, Jira Service Management and Trello. Some users outside us-east may have been affected in certain scenarios.\n\n### **ROOT CAUSE**\n\nThe incident was caused by a race condition in our internal deployment orchestration platform during a routine rollback operation of a core identity service in the us-east region. This race condition resulted in insufficient capacity for the identity service in the affected region which started returning errors to dependent products.\n\n### **REMEDIAL ACTIONS PLAN & NEXT STEPS**\n\nWe know that outages impact your productivity. Atlassian is prioritizing the following actions to help prevent similar incidents in future:\n\n* **Refine deployment orchestration safeguards**\n\n * Harden our deployment platform to prevent similar race conditions or resulting capacity loss during a rollback operation.\n * Streamline mitigation steps when a service becomes unavailable in a region.\n \n* **Reduce cross-region impact**\n\n * Improve regional isolation and fallback handling so an issue affecting a single region is less likely to impact customers or product functionality in other regions.\n \n\nWe recognise how critical reliable access to Atlassian products is for our customers' productivity, and we apologize to customers who were impacted by this incident.\n\nThanks,\n\nAtlassian", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-14T06:48:27.867Z", "resolved_inferred": false, "started_at": "2026-05-14T05:11:19.141Z", @@ -25,7 +25,7 @@ "body": "All dates and times below are in UTC unless stated otherwise.\n\n### Summary\n\nOn May 8, 2026 between 00:22 and 06:08, one of our hosting providers suffered a significant incident in a specific availability zone in prod-east which led to Atlassian customers experiencing degraded performance and delays of background operations and automation execution.\n\nThe incident started on May 8, 2026 at 00:22 and was detected within 4 minutes by automated monitoring systems. Our teams worked to restore core access by 06:08. Final cleanup of backlogged processes and minor issues progressed in stages from there was completed iteratively by 19:15.\n\n### **IMPACT**\n\nThe primary infrastructure affected in this incident was the event processing pipeline in the prod-east region, which distributes events between Atlassian services and underpins background operations such as automation execution, search indexing, notifications, permission synchronisation.\n\n* Between 00:22 and 06:08, an infrastructure incident in our hosting provider triggered an ingestion failure in our event processing pipeline.\n* At 02:50, event ingestion was failed over to an unaffected availability zone, progressively restoring live event flows.\n* At 06:08, reliability for new ingestion in prod-east recovered to 100%. The remaining work was to drain the accumulated cross-region backlog of messages, which completed by 17:00.\n* By 18:48, Automation had processed their backlog of events that were created while processing\n\n**Automation**\n\nBetween 00:22 and 02:50, customers with automation rules triggered by events originating from the prod-east region experienced a significant reduction in rule executions. During this window, event-triggered automation rules were not firing because the events that trigger them were not being delivered. Rule authoring, saving, and rules triggered manually, by schedules, or by webhooks were not affected.\n\nAt 02:50, the event processing infrastructure failed over to an unaffected availability zone, restoring delivery of live events to Automation and allowing new event-triggered rules to begin executing normally. However, events generated during the impact window still needed to be replayed before delayed automations could be processed.\n\nBeginning at 08:28, upstream services replayed their queued events in a coordinated sequence, and all replayed events were processed by 18:48. During the replay window, customers may have experienced automation rules executing later than expected, a small number of rules reaching daily processing limits due to compressed replay, and time-sensitive rules not completing as expected if internal timeout thresholds were exceeded.\n\n**Jira and Jira Service Management**\n\nBetween 00:22 and 02:50, customers with tenants hosted in the prod-east region experienced disruption to Jira and Jira Service Management event-driven features like automation, along with a short period of elevated errors during infrastructure failover. Core Jira experiences, including issue view, boards, and project navigation, remained available throughout the incident.\n\nJira event delivery was affected by the primary impact, preventing downstream services from receiving issue lifecycle events. This affected automation rules triggered by Jira events, AI agent orchestration in Jira, notifications for issue updates and transitions, search indexing for newly created or modified issues, and event-driven integrations between Jira and other Atlassian products.\n\nAt 02:50, the event processing infrastructure failed over to an unaffected availability zone, restoring delivery of new events. All events generated during the impact window were retained in a recovery queue and required replaying. This began at 08:28 and completed at 12:00. During the replay window, customers may have experienced automation rules executing later than expected, delayed notifications arriving hours after the triggering action, temporary gaps in search results for content created or modified during the impact window, and AI agent workflows not completing as expected where internal timeout thresholds were exceeded.\n\n**Confluence**\n\nBetween 00:22 and 02:50, customers with tenants hosted in the prod-east region experienced disruptions to event-driven services in Confluence. This resulted in delays to search indexing, notifications, automation rule execution, and permission synchronisation.\n\nThe underlying event processing infrastructure failed over to an unaffected availability zone, after which live Confluence operations resumed normally. However, events generated during the impact window were queued for replay, and some background services remained delayed until that replay and related validation work completed.\n\nBetween 10:14 and 17:00, a bulk replay of all the queued tenant replay tasks was completed to restore data consistency. During and immediately after the replay window, customers may have experienced search results not reflecting content created or modified during the outage, delayed or missing notifications for page and comment activity, automation rules firing later than expected, and brief delays in permission synchronisation for tenants relying on incremental identity sync.\n\n**Bitbucket and Pipelines**\n\nBetween 00:22 and 06:08, customers using Bitbucket and Pipelines experienced failures and degraded functionality across event-driven workflows. Core Git operations, including push, pull, and clone, were not affected and continued to operate normally throughout the incident.\n\nAutomatic pipeline triggers initiated by push or pull request events were unavailable during the impact window. Merge queues, custom merge checks, Forge-based triggers, workspace permission changes, and some workspace provisioning flows were also affected. Customers using merge queues were unable to merge pull requests, and some pipeline steps failed because queued work contributed to elevated concurrency limits.\n\nAt approximately 03:57, Pipelines was reconfigured to consume events through an alternative path, restoring automatic pipeline triggering. Merge queues, custom merge checks, Forge triggers, and other affected workflows were progressively restored as the underlying event processing infrastructure recovered. All Bitbucket and Pipelines services were confirmed fully operational by 06:08. After recovery, queued events were reviewed and replayed where safe to restore data consistency for billing, audit logging, and other background processes.\n\n**Identity Services**\n\nBetween 00:22 and 02:50, customers with tenants hosted in the prod-east region experienced delays in the propagation of identity and group membership changes to downstream Atlassian products. Core identity operations, including authentication, login, and direct group management actions, were not affected and continued to function normally throughout the incident.\n\nThe impact was limited to asynchronous, event-driven operations that depend on the event processing pipeline. This included delays in delivering group membership and user profile changes to products such as Jira and Confluence, which affected downstream permission synchronisation and crowd sync flows. A small number of SCIM-based identity synchronisation and site provisioning workflows also experienced temporary delays.\n\nAfter the event processing infrastructure recovered, backed-up identity and group directory events were replayed where required, restoring downstream consistency for affected products. No identity data was lost. Group membership changes, user profile updates, and provisioning-related events that occurred during the impact window were retained and processed after recovery.\n\n### **REMEDIAL ACTIONS PLAN & NEXT STEPS**\n\nWe know outages impact your productivity. While our monitoring and recovery processes helped us respond quickly, this incident highlighted opportunities to further strengthen resilience for event-driven services.\n\nWe are prioritizing improvements that will:\n\n* **Enhance failover coverage** so critical event processing can recover more smoothly during infrastructure disruptions.\n* **Strengthen recovery handling** so replayed events can be processed more quickly.\n\nWe apologize to customers whose services were impacted during this incident; we are taking immediate steps to improve the platform\u2019s performance and availability.\n\nThanks,\n\nAtlassian Customer Support.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-08T19:45:31.250Z", "resolved_inferred": false, "started_at": "2026-05-08T01:31:38.240Z", @@ -38,7 +38,7 @@ "body": "### Summary\n\nOn April 13, 2026, between 05:49 and 06:29 UTC, customers experienced failures when attempting to log in, sign up, reset passwords, and complete multi-factor authentication flows across Atlassian cloud products. Approximately 90% of authentication requests failed during the peak impact window, affecting users in the US East and EU regions. The incident was mitigated within 40 minutes through manual intervention, and full service was restored by 06:29 UTC.\n\n### **IMPACT**\n\n* **Duration**: ~40 minutes \\(05:49\u201306:29 UTC, April 13, 2026\\)\n* **Affected regions**: US East and EU \\(authentication infrastructure serves EU traffic from US East, with traffic primarily from EU at this time of day\\).\n* **Affected products**: All Atlassian cloud products requiring authentication, including Jira, Confluence, Jira Service Management, and Trello.\n* **Customer experience**: Users attempting to log in, sign up, reset passwords, or complete MFA flows received errors. Users already logged in with active sessions were unaffected.\n\n### **ROOT CAUSE**\n\nThis incident had several contributing factors that combined to produce a failure that the system could not recover from without manual intervention.\n\n**The primary cause** was a recently enabled change that caused our authentication infrastructure to retry requests to a downstream identity service when those requests were slow to respond. This retry behaviour was rolled out to 100% of traffic earlier the same day. Under normal conditions this would be benign, but it meant that any slowness in the downstream service was amplified. Since multiple upstream services were also independently retrying their own failed requests, the amplification compounded further into a retry storm.\n\n**The trigger** was a burst of legitimate user traffic. A pattern of many parallel link preview requests for a single user caused a concentrated load spike on a downstream identity service, pushing its response times above the retry threshold. On its own, this kind of spike had occurred many times before and always recovered. With the retry amplification now in effect, the spike instead created a runaway feedback loop: slow responses caused retries, retries increased load, increased load caused slower responses, preventing recovery.\n\nThe incident was mitigated by manually scaling up the downstream identity service to provide sufficient capacity to absorb the amplified load. Once scaled, the service recovered immediately, bringing authentication error rates to zero within one minute.\n\n**REMEDIAL ACTIONS PLAN & NEXT STEPS**\n\nWe are taking the following actions designed to prevent recurrence and improve our resilience:\n\n1. **Immediate**: The retry-on-timeout change has been disabled.\n2. **Load shedding and self-healing**: We are adding load shedding capabilities to our authentication services so that they can automatically shed excess load and self-recover during traffic spikes, without requiring action before automatic scaling starts.\n3. **Reducing request fan-out**: We are reviewing patterns where a single user action can generate many parallel downstream requests, and will introduce methods where possible to reduce the amplification potential.\n\nWe apologize to customers whose services were interrupted by this incident and we are taking immediate steps to improve the platform\u2019s reliability.\n\nThanks,\n\nAtlassian Customer Support", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-13T10:17:20.783Z", "resolved_inferred": false, "started_at": "2026-04-13T07:29:46.094Z", @@ -51,7 +51,7 @@ "body": "### Summary\n\nOn April 8, 2026, between 04:46 UTC and 12:09 UTC, search functionality was unavailable or degraded across several Atlassian Cloud products, including Jira, Confluence, Jira Service Management, Rovo, Rovo Dev, Loom, Guard Standard, Customer Service Management and Atlassian Administration. \n\nA configuration change increased the resources reserved for a core system component that runs on nodes in our compute platform. On a subset of clusters configured for high\u2011density workloads, the increased reservations exceeded available node capacity interrupting search and related experiences for affected customers.\n\nThe root cause was identified and a rollback was merged at 05:42 UTC with some systems seeing recovery by 07:33 UTC**.** Core search functionality was restored approximately by 08:55 UTC, and full downstream recovery completed by 12:09 UTC.\n\n### **IMPACT**\n\nDuring the impact period, some customers experienced outages or degradation in search across Jira, Confluence, Jira Service Management, Rovo, Rovo Dev, Loom, Guard Standard, Customer Service Management and Atlassian Administration. Other experiences that rely on search such as quick find, navigation, AI assistants, dashboards, were also intermittently affected during this period.\n\nImpacted customers may have been unable to find pages or recordings and experienced degraded performance in finding issues; received empty or delayed search results; or experienced AI assistants and dashboards that could not retrieve relevant context.\n\n**Jira, Jira Service Management and Customer Service Management:** Search and experiences that depend on search like finding issues and agent responses in CSM remained available but with degraded performance in fallback mode. By 12:09 UTC, search indexes and search performance was fully restored from fallback to full capacity across all regions.\n\n**Guard Standard and Atlassian Administration:** Search functionality was unavailable for parts of the incident window. As a result, Domain Claims, usage tracking, and managed accounts were degraded for portions of the window. These services were restored to operational status by 07:33 UTC. Guard Premium was not impacted by this issue.\n\n**Confluence:** Search functionality was unavailable for parts of the incident window. Recovery began at 07:30 UTC as backend search clusters were restored. Full recovery, including search index replay, completed at 11:37 UTC.\n\n**Loom:** Search functionality and some experiences that rely on Confluence Search, such as sharing to spaces\\) was unavailable for portions of the window and fully restored at 11:37 UTC.\n\n**Rovo and Rovo Dev:** Rovo agents remained responsive but experienced degraded functionality due to loss of search capabilities in underlying services. They were unable to reliably return context about work items or pages. Functionality was fully restored at 11:37 UTC.\n\n### **ROOT CAUSE**\n\nAtlassian products rely on OpenSearch clusters to power their search capabilities including issue search, content search, and AI-powered search features. \n\nAn infrastructure configuration change increased resource reservations \\(CPU & Memory\\) for a system component that runs across our compute platform. On a subset of clusters configured for high-density workloads, the increased reservations exceeded available node capacity. This caused search workloads to be evicted and, in some clusters, could not reschedule onto any available nodes impacting search functionality across affected products.\n\nThe change was deployed across multiple production clusters in a short time frame, limiting the opportunity to detect the capacity conflict in a smaller subset of clusters before it reached the wider fleet. Automated scaling systems attempted to recover by provisioning additional capacity but in the worst\u2011affected clusters this led to runaway node scaling and exhaustion of available network resources, prolonging recovery time.\n\n### **REMEDIAL ACTIONS PLAN & NEXT STEPS**\n\nWe understand that service disruptions impact your productivity. In addition to our existing testing and preventative processes, Atlassian is prioritizing the following actions to help reduce the likelihood and impact of similar incidents in the future and to speed up recovery when issues occur:\n\n* **Enforce smaller deployment cohorts and larger soak for critical platform changes for these cluster types** \n Implement smaller deployment cohorts, mandatory soak periods between environments, and automated health gates so that changes are validated on a limited set of clusters before being promoted more broadly.\n* **Strengthen automated pre\u2011deploy validation for resource changes** \n Add validation checks to ensure resource changes for system components are compatible with node capacity and reserved headroom, preventing system workloads from crowding out customer workloads.\n* **Improve post\u2011deploy verification and alerting** \n Enhance monitoring and post\u2011deployment verification to detect patterns such as spikes in pending pods, runaway node scaling, and low pod\u2011IP headroom closely correlated with new configuration being rolled out.\n* **Align autoscaling behavior with capacity and safety limits** \n Align autoscaling capacity calculations with node reservations and introduce safeguards and circuit breakers to prevent runaway scaling and to enforce safe limits on node and pod IP counts.\n* **Enhance recovery automation** \n Improve automation and runbooks so we can safely disable autoscaling, remove empty nodes in bulk, and restore normal operations faster across multiple clusters in parallel.\n\nWe apologize to customers whose services were impacted during this incident; we are taking immediate steps to improve the platform\u2019s performance and availability and to reduce the risk and impact of similar issues in future.\n\nThanks,\n\nAtlassian Customer Support", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-08T11:43:29.733Z", "resolved_inferred": false, "started_at": "2026-04-08T06:01:35.680Z", @@ -64,7 +64,7 @@ "body": "We have implemented the fix and the group page in the Admin Hub is now functioning as expected.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-18T11:30:29.120Z", "resolved_inferred": false, "started_at": "2026-02-18T11:28:09.872Z", @@ -77,7 +77,7 @@ "body": "### Summary\n\nOn **December 27, 2025**, between **02:48 UTC and 05:20 UTC**, some Atlassian cloud customers experienced failures in sending and receiving emails and mobile notifications. Core Jira and Confluence functionality remained available.\n\nThe issue was triggered when **TLS certificates used by Atlassian\u2019s monitoring infrastructure expired**, causing parts of our metrics pipeline to stop accepting traffic. Services responsible for email and mobile notifications had a critical path dependency on monitoring path leading to service disruptions.\n\nAll impacted services were fully restored by **05:20 UTC**, around **2.5 hours** after customer impact began.\n\n### IMPACT\n\nDuring the impact window, customers experienced:\n\n* **Outbound product email failures** \\(notifications and other product emails did not send\\).\n* **Identity and account flow failures** where emails were required \\(e.g. sign\u2011ups, password resets, one\u2011time\u2011password / step\u2011up challenges\\).\n* **Jira and Confluence mobile push notifications**\n* **Customer site activations and some admin policy changes** failing and requiring later reprocessing.\n\n### ROOT CAUSE\n\nThe incident was caused by:\n\n1. **Expired TLS certificates** on domains used by our monitoring and metrics infrastructure caused by **misconfigured DNS authorization record** which prevented automatic renewal.\n2. **Tight coupling of services to metrics publishing**, which caused them to fail when monitoring endpoints became unavailable, instead of degrading gracefully.\n\n### REMEDIAL ACTIONS PLAN & NEXT STEPS\n\nWe recognize that outages like this have a direct impact on customers\u2019 ability to receive important notifications, complete account tasks, and operate their sites.\n\nWe are prioritizing the following actions to improve our existing testing, monitoring and certificate management processes:\n\n* **Hardening monitoring and certificate infrastructure**\n\n * We are refining DNS and certificate configuration across our monitoring domains and strengthening proactive checks to detect and address failed renewals and certificate issues well before expiry.\n * We are also improving alerting on our monitoring and metrics pipeline.\n \n* **Decoupling monitoring from critical customer flows** \n We are updating services such as outbound email, identity, mobile push, provisioning, and admin policy changes so they no longer depend on metrics publishing to operate. If monitoring becomes unavailable, these services will continue to run and degrade gracefully by dropping or buffering metrics instead of failing customer operations.\n\nWe apologize to customers impacted during this incident. We are implementing the improvements above to help ensure that similar issues are avoided.\n\nThanks, \nAtlassian Customer Support", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-27T05:20:20.550Z", "resolved_inferred": false, "started_at": "2025-12-27T04:42:32.884Z", @@ -90,7 +90,7 @@ "body": "On December 15th, 2025, affected Guard users in US Prod East region may have experienced some service disruption. The issue has now been resolved, and the service is operating normally for all affected customers.\n\nNote: All previously failed Guard provisioning and open workflows have been replayed by Atlassian. No actions are needed from customers for these events.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-15T22:07:53.438Z", "resolved_inferred": false, "started_at": "2025-12-15T20:23:41.417Z", @@ -103,7 +103,7 @@ "body": "On December 15th, 2025, Admin Hub, Atlassian Analytics, Confluence Cloud, Ecosystem, Focus, Jira, Jira Product Discovery, Jira Service Management, and Rovo users in the prod-us-east region may have experienced performance degradations and errors on the web page and mobile apps. The issue has now been resolved, and the service is operating normally for all affected customers.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-15T19:02:03.786Z", "resolved_inferred": false, "started_at": "2025-12-15T16:16:25.657Z", @@ -116,7 +116,7 @@ "body": "Impacted customers have now confirmed that they are receiving their emails as expected.\n\nIf you do continue to see these emails being missing or delayed, please check in with your organizations email admin to review and release them.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-17T00:11:36.845Z", "resolved_inferred": false, "started_at": "2025-11-13T18:56:12.844Z", @@ -129,7 +129,7 @@ "body": "### Postmortem publish date: Nov 19th, 2025\n\n### Summary\n\nAll dates and times below are in UTC unless stated otherwise.\n\nCustomers utilizing Atlassian products experienced elevated error rates and degraded performance between Oct 20, 2025 06:48 and Oct 21, 2025 04:05. The service disruptions were triggered due to an [AWS DynamoDB outage](https://aws.amazon.com/message/101925/#:~:text=1%3A50%20PM.-,DynamoDB,-Between%2011%3A48) and further affected by subsequent failures in [AWS EC2](https://aws.amazon.com/message/101925/#:~:text=service%20disruption%20event.-,Amazon%20EC2,-Between%2011%3A48) and [AWS Network Load Balancer](https://aws.amazon.com/message/101925/#:~:text=service%20disruption%20event.-,Amazon%20EC2,-Between%2011%3A48) within the us-east-1 region.\n\nThe incident started at Oct 20, 2025 06:48 and was detected within six minutes by our automated monitoring systems. Our teams worked to restore all core services by Oct 21, 2025 04:05. Final cleanup of backlogged processes and minor issues was completed on Oct 22, 2025.\n\nWe recognize the critical role our products play in your daily operations, and we offer our sincere apologies for any impact this incident had on your teams. We are taking immediate steps to enhance the reliability and performance of our services, so that you continue to receive the standard of service you have come to trust.\n\n### IMPACT\n\nBefore examining product-level impacts, it's helpful to understand Atlassian's service topology and internal dependencies.\n\nProducts such as Jira and Confluence are deployed across multiple AWS regions. The data for each tenant is stored and processed exclusively within its designated host region. This design is intentional and represents the desired operational state, as it limits the impact of any regional outage strictly to tenants in-region, in this case us-east-1.\n\nWhile in-scope application data is pinned to the region selected by the customer, there are times when systems need to call other internal services that may be based in a different region. If a problem occurs in the main region where these services operate, systems are designed to automatically fail over to a backup region, usually within three minutes.\n\nHowever, if unexpected issues arise during this failover, it can take longer to restore services. In rare cases, this could affect customers in more than one region. It\u2019s important to note that all in-scope application data for supported products is pinned according to a customer\u2019s chosen region.\n\n**Jira**\n\nBetween Oct 20, 2025 06:48 and Oct 20, 2025 20:00, customers with tenants hosted in the us-east-1 region experienced increased error rates when accessing core entities such as Issues, Boards, and Backlogs. This disruption was caused by AWS's inability to allocate AWS EC2 instances and elevated errors in AWS Network Load Balancer \\(NLB\\). During this window, users may also have observed intermittent timeouts, slow page loads, and failures when performing operations like creating or updating issues, loading board views, and executing workflow transitions.\n\nBetween Oct 20, 2025 08:36 and Oct 20, 2025 09:23, customers across all regions experienced elevated failure rates when attempting to load Jira pages. This disruption was caused by the regional frontend service entering an unhealthy state during this specific time interval.\n\nNormally, the frontend service connects to the primary AWS DynamoDB instance located in the us-east-1 to retrieve the most recent configuration data necessary for proper operation. Additionally, the service is designed with a fallback mechanism that references static configuration data in the event that the primary database becomes inaccessible. Unfortunately, a latent bug existed in the local fallback path. When the frontend service nodes restarted, they were unable to load critical operational configuration data from primary or fallback sources, leading to the observed failures experienced by customers.\n\nBetween Oct 20, 2025 06:48 and Oct 21, 2025 06:30, customers experienced significant delays and missing Jira in-app notifications across all regions. The notification ingestion service, which is hosted exclusively in us-east-1, exhibited an increased failure rate when processing notification messages due to AWS EC2 and NLB issues. This issue resulted in notifications being delayed - and in some cases, not delivered at all - to users worldwide.\n\n**Jira Service Management \\(JSM\\)**\n\nJSM was impacted similarly to Jira above, with the same timeframes and for the same reasons.\n\nBetween Oct 20, 2025 08:36 and Oct 20, 2025 09:23, customers across all regions experienced significantly elevated failure rates when attempting to load JSM pages. This affected all JSM experiences including the Help Centre, Portal, Queues, Work Items, Operations, and Alerts.\n\n**Confluence**\n\nBetween Oct 20, 2025 06:48 and Oct 21, 2025 02:45, customers using Confluence in the us-east-1 region experienced elevated failure rates when performing common operations such as editing pages or adding comments. The primary cause of this service degradation was the system's inability to auto-scale due to AWS EC2 issues to manage peak traffic load effectively.\n\nThough the AWS outage ended at Oct 20, 21:09, a subset of customers continued to experience failures as some Confluence web server nodes across multiple clusters remained in an unhealthy state. This was ultimately mitigated by recycling the affected nodes.\n\nTo protect our systems while AWS recovered, we made a deliberate decision to enable node termination protection. This action successfully preserved our server capacity but, as a trade-off, it extended the time required for a full recovery once AWS services were restored.\n\n**Automation**\n\nBetween Oct 20, 2025 06:55 and Oct 20, 2025 23:59, automation customers whose rules are processed in us-east-1 experienced delays of up to 23 hours in rule execution.\n\nDuring this window, some events triggering rule executions were processed out of order because they arrived later during backlog processing. This caused potential inconsistencies in workflow executions, as rules were run in the order events were received, not when the action causing the event occurred. Additionally, some rule actions failed because they depend on first-party and third-party systems, which were also affected by the AWS outage. Customers can see most of these failures in their audit logs; however, a few updates were not logged due to the nature of the outage.\n\nBy Oct 21, 2025 5:30, the backlog of rule runs in us-east-1 was cleared. Although most of these delayed rules were successfully handled, there were some additional replays of events to ensure completeness. Our investigation confirmed that a few events may never have triggered their associated rules due to the outage.\n\nBetween Oct 20, 2025 06:55 and Oct 20, 2025 11:20, all non-us-east-1 regional automation services experienced delays of up to 4 hours in rule execution. This was caused by an upstream service that was unable to deliver events as expected. The delivery service encountered a failure due to a cross-region dependency call to a service hosted in the us-east-1 region. Because of this dependency issue, the delivery service was unable to successfully deliver events throughout this time frame, resulting in customer-defined rules not being executed in a timely manner.\n\n**Bitbucket and Pipelines**\n\nBetween Oct 20, 2025 06:48 and Oct 20, 2025 09:33, Bitbucket experienced intermittent unavailability across core services. During this period, users faced increased error rates and latency when signing in, navigating repositories, and performing essential actions such as creating, updating, or approving pull requests. The primary cause was an AWS DynamoDB outage that impacted downstream services.\n\nBetween Oct 20, 2025 06:48 and Oct 20, 2025 22:46, numerous Bitbucket Pipeline steps failed to start, stalled mid-execution, or experienced significant queueing delays. Impact varied, with partial recoveries followed by degradation as downstream components re-synchronized. The primary cause was an AWS DynamoDB outage, compounded by instability in AWS EC2 instance availability and AWS Network Load Balancers.\n\nFurthermore, Bitbucket Pipelines continued to experience a low but persistent rate of step timeouts and scheduling errors due to AWS bare-metal capacity shortages in select availability zones. Atlassian coordinated with AWS to provision additional bare-metal hosts and addressed a significant backlog of pending pods, successfully restoring services by 01:30 on Oct 21, 2025.\n\n**Trello**\n\nBetween Oct 20, 2025 06:48 and Oct 20, 2025 15:25, users of Trello experienced widespread service degradation and intermittent failures due to upstream AWS issues affecting multiple components, including AWS DynamoDB and subsequent AWS EC2 capacity constraints. During this period, customers reported elevated error rates when loading boards, opening cards, adding comments or attachments.\n\n**Login**\n\nBetween Oct 20, 2025 06:48 and Oct 20, 2025 09:30, a small subset of users experienced failures when attempting to initiate new login sessions using SAML tokens. This resulted in an inability for those users to access Atlassian products during that time period. However, users who already had valid active sessions were not affected by this issue and continued to have uninterrupted access.\n\nThe issue impacted all regions globally because regional identity services relied on a write replica located in the us-east-1 region to synchronize profile data. When the primary region became unavailable, the failover to a secondary database in another region failed, which delayed recovery. This failover defect has since been addressed.\n\n**Statuspage**\n\nBetween Oct 20, 2025 06:48 and Oct 20, 2025 09:30, Statuspage customers who were not already logged in to the management portal were unable to log in to create or update incident statuses. This impact was restricted only to users who were not already logged in at the time. The root cause was the same as described in the Login section above, and it was resolved by the same remediation steps.\n\n### REMEDIAL ACTION PLAN & NEXT STEPS\n\nWe have completed the following critical actions designed to help prevent cross-region impact from similar issues:\n\n* Resolved the code defect in the fallback option to ensure that Jira Frontend Services in other regions remain unaffected during a region-wide outage.\n* Fixed the issue that prevented timely failover of the identity service which impacted new login sessions.\n* Resolved the code defect so that delivery services in unaffected regions remain operational during region-wide outages.\n\nAdditionally, we are prioritizing the following improvement actions:\n\n* Implement mitigation strategies to strengthen resilience against region-wide outages in the notification ingestion service.\n\nAlthough disruptions to our cloud services are sometimes unavoidable during outages of the underlying cloud provider, we continuously evaluate and improve test coverage to strengthen resilience of our cloud services against these issues.\n\nWe recognize the critical importance of our products to your daily operations and overall productivity, and we extend our sincere apologies for any disruptions this incident may have caused your teams. If you were impacted and require additional details for internal post-incident reviews, please reach out to your Atlassian support representative with affected timeframes and tenant identifiers so we can correlate logs and provide guidance.\n\nThanks,\n\nAtlassian Customer Support", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-21T05:24:26.990Z", "resolved_inferred": false, "started_at": "2025-10-20T07:56:12.795Z", @@ -142,7 +142,7 @@ "body": "### **SUMMARY**\n\nOn September 22, 2025, between 04:38 and 04:48 UTC, Atlassian customers experienced connection errors preventing access to their [atlassian.net](http://atlassian.net/) sites. Some customers observed intermittent errors as services gradually recovered until 06:17 UTC.\n\nThe event was triggered by a faulty configuration change to our Content Delivery Network \\(CDN\\). The change included an invalid hostname which prevented customers from successfully connecting to [atlassian.net](http://atlassian.net/) domains.\n\nThe incident was detected within 1 minute by our monitoring systems and mitigated by rolling back the change, which put Atlassian systems into a known good state. The acute impact was resolved in 10 minutes and all lingering errors resolved in 1 hour 38 minutes.\n\n### **IMPACT**\n\nThe acute impact occurred on\u00a0September 22, 2025, between 04:38 UTC and 04:48 UTC to Confluence, Compass and Jira, including Jira Service Management. The incident caused service disruption to customers when they attempted to load those products in their browser or interact with APIs. Between 04:48 UTC and 06:17 UTC some customers continued to observe intermittent errors as services gradually recovered.\n\n### **ROOT CAUSE**\n\nThe issue was caused by a change to the hostname configuration of our Content Delivery Network \\(CDN\\). As a result, the products mentioned could not receive connections, and the users received TLS handshake errors, followed by HTTP 503 and 403 errors.\n\nMore specifically a new CDN configuration contained a resource name which conflicted with the existing customer-serving CDN resource, and was able to be deployed, overwriting it. The root cause of the incident was the failure in the detection of the bug by our pre-deployment validations and tests.\n\n### **REMEDIAL ACTIONS PLAN & NEXT STEPS**\n\nWe know that you rely on our products for your daily operations and productivity, and we sincerely apologize for any impact this disruption has had on you, your team or your organisation.\n\nWe are prioritizing the following improvement actions to help avoid repeating this type of incident:\n\n* Improved pre-deployment change controls and testing.\n* Improved validation of target configurations before deployment to ensure customer-serving CDN resources cannot their hostnames changed.\n* Sharding of our CDN configuration to enable progressive changes.\n\nWe sincerely appreciate your understanding and patience as we improve our processes to provide a better customer experience.\n\nThank you,\n\nAtlassian Customer Support", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-22T07:17:23.797Z", "resolved_inferred": false, "started_at": "2025-09-22T05:59:59.234Z", @@ -155,7 +155,7 @@ "body": "Between 2025-08-03T21:34 and 2025-08-05T03:43 UTC some users would not have received the emails for product invitations.\nThe change that caused these emails to stop being sent has been rolled back.\nNew invitation emails should now be sent correctly for all products.\nFor users that were impacted by this issue, re-submitting their invitation will also re-send the email to them if required.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-05T04:19:02.903Z", "resolved_inferred": false, "started_at": "2025-08-04T23:44:47.052Z", diff --git a/api/v/atlassian-compass.json b/api/v/atlassian-compass.json index 8b7493cd579c908f36f8e6b462b28e395f7e7107..b8f11aac62c5ba96ffb5b0b2d5630ca0d0b07ea9 100644 --- a/api/v/atlassian-compass.json +++ b/api/v/atlassian-compass.json @@ -3,7 +3,7 @@ "slug": "atlassian-compass", "platform": "statuspage", "status_url": "https://compass.status.atlassian.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "### Summary\n\nOn May 14, 2026, between 04:30 and 05:26 UTC, Atlassian customers experienced widespread service disruption across multiple Atlassian Cloud products. The issue was caused by a race condition in our internal deployment orchestration platform during a routine rollback operation of a core identity service in the us-east region. This race condition resulted in insufficient capacity for the identity service in the affected region which started returning errors to dependent products. The incident was detected within a minute by automated monitoring systems and mitigated in 56 minutes.\n\n### **IMPACT**\n\nDuring the incident, customers attempting to access Atlassian Cloud products in the us-east region experienced authentication and permission failures and were unable to access services. Customers also experienced errors when accessing the support portal until Atlassian fell back to an alternate support method. This was caused by a core identity service in the us-east region becoming unavailable. Affected products included Atlassian Administration, Atlassian Analytics, Bitbucket, Compass, Confluence, Jira, Jira Product Discovery, Jira Service Management and Trello. Some users outside us-east may have been affected in certain scenarios.\n\n### **ROOT CAUSE**\n\nThe incident was caused by a race condition in our internal deployment orchestration platform during a routine rollback operation of a core identity service in the us-east region. This race condition resulted in insufficient capacity for the identity service in the affected region which started returning errors to dependent products.\n\n### **REMEDIAL ACTIONS PLAN & NEXT STEPS**\n\nWe know that outages impact your productivity. Atlassian is prioritizing the following actions to help prevent similar incidents in future:\n\n* **Refine deployment orchestration safeguards**\n\n * Harden our deployment platform to prevent similar race conditions or resulting capacity loss during a rollback operation.\n * Streamline mitigation steps when a service becomes unavailable in a region.\n \n* **Reduce cross-region impact**\n\n * Improve regional isolation and fallback handling so an issue affecting a single region is less likely to impact customers or product functionality in other regions.\n \n\nWe recognise how critical reliable access to Atlassian products is for our customers' productivity, and we apologize to customers who were impacted by this incident.\n\nThanks,\n\nAtlassian", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-14T06:48:27.600Z", "resolved_inferred": false, "started_at": "2026-05-14T05:24:54.073Z", @@ -25,7 +25,7 @@ "body": "All dates and times below are in UTC unless stated otherwise.\n\n### Summary\n\nOn May 8, 2026 between 00:22 and 06:08, one of our hosting providers suffered a significant incident in a specific availability zone in prod-east which led to Atlassian customers experiencing degraded performance and delays of background operations and automation execution.\n\nThe incident started on May 8, 2026 at 00:22 and was detected within 4 minutes by automated monitoring systems. Our teams worked to restore core access by 06:08. Final cleanup of backlogged processes and minor issues progressed in stages from there was completed iteratively by 19:15.\n\n### **IMPACT**\n\nThe primary infrastructure affected in this incident was the event processing pipeline in the prod-east region, which distributes events between Atlassian services and underpins background operations such as automation execution, search indexing, notifications, permission synchronisation.\n\n* Between 00:22 and 06:08, an infrastructure incident in our hosting provider triggered an ingestion failure in our event processing pipeline.\n* At 02:50, event ingestion was failed over to an unaffected availability zone, progressively restoring live event flows.\n* At 06:08, reliability for new ingestion in prod-east recovered to 100%. The remaining work was to drain the accumulated cross-region backlog of messages, which completed by 17:00.\n* By 18:48, Automation had processed their backlog of events that were created while processing\n\n**Automation**\n\nBetween 00:22 and 02:50, customers with automation rules triggered by events originating from the prod-east region experienced a significant reduction in rule executions. During this window, event-triggered automation rules were not firing because the events that trigger them were not being delivered. Rule authoring, saving, and rules triggered manually, by schedules, or by webhooks were not affected.\n\nAt 02:50, the event processing infrastructure failed over to an unaffected availability zone, restoring delivery of live events to Automation and allowing new event-triggered rules to begin executing normally. However, events generated during the impact window still needed to be replayed before delayed automations could be processed.\n\nBeginning at 08:28, upstream services replayed their queued events in a coordinated sequence, and all replayed events were processed by 18:48. During the replay window, customers may have experienced automation rules executing later than expected, a small number of rules reaching daily processing limits due to compressed replay, and time-sensitive rules not completing as expected if internal timeout thresholds were exceeded.\n\n**Jira and Jira Service Management**\n\nBetween 00:22 and 02:50, customers with tenants hosted in the prod-east region experienced disruption to Jira and Jira Service Management event-driven features like automation, along with a short period of elevated errors during infrastructure failover. Core Jira experiences, including issue view, boards, and project navigation, remained available throughout the incident.\n\nJira event delivery was affected by the primary impact, preventing downstream services from receiving issue lifecycle events. This affected automation rules triggered by Jira events, AI agent orchestration in Jira, notifications for issue updates and transitions, search indexing for newly created or modified issues, and event-driven integrations between Jira and other Atlassian products.\n\nAt 02:50, the event processing infrastructure failed over to an unaffected availability zone, restoring delivery of new events. All events generated during the impact window were retained in a recovery queue and required replaying. This began at 08:28 and completed at 12:00. During the replay window, customers may have experienced automation rules executing later than expected, delayed notifications arriving hours after the triggering action, temporary gaps in search results for content created or modified during the impact window, and AI agent workflows not completing as expected where internal timeout thresholds were exceeded.\n\n**Confluence**\n\nBetween 00:22 and 02:50, customers with tenants hosted in the prod-east region experienced disruptions to event-driven services in Confluence. This resulted in delays to search indexing, notifications, automation rule execution, and permission synchronisation.\n\nThe underlying event processing infrastructure failed over to an unaffected availability zone, after which live Confluence operations resumed normally. However, events generated during the impact window were queued for replay, and some background services remained delayed until that replay and related validation work completed.\n\nBetween 10:14 and 17:00, a bulk replay of all the queued tenant replay tasks was completed to restore data consistency. During and immediately after the replay window, customers may have experienced search results not reflecting content created or modified during the outage, delayed or missing notifications for page and comment activity, automation rules firing later than expected, and brief delays in permission synchronisation for tenants relying on incremental identity sync.\n\n**Bitbucket and Pipelines**\n\nBetween 00:22 and 06:08, customers using Bitbucket and Pipelines experienced failures and degraded functionality across event-driven workflows. Core Git operations, including push, pull, and clone, were not affected and continued to operate normally throughout the incident.\n\nAutomatic pipeline triggers initiated by push or pull request events were unavailable during the impact window. Merge queues, custom merge checks, Forge-based triggers, workspace permission changes, and some workspace provisioning flows were also affected. Customers using merge queues were unable to merge pull requests, and some pipeline steps failed because queued work contributed to elevated concurrency limits.\n\nAt approximately 03:57, Pipelines was reconfigured to consume events through an alternative path, restoring automatic pipeline triggering. Merge queues, custom merge checks, Forge triggers, and other affected workflows were progressively restored as the underlying event processing infrastructure recovered. All Bitbucket and Pipelines services were confirmed fully operational by 06:08. After recovery, queued events were reviewed and replayed where safe to restore data consistency for billing, audit logging, and other background processes.\n\n**Identity Services**\n\nBetween 00:22 and 02:50, customers with tenants hosted in the prod-east region experienced delays in the propagation of identity and group membership changes to downstream Atlassian products. Core identity operations, including authentication, login, and direct group management actions, were not affected and continued to function normally throughout the incident.\n\nThe impact was limited to asynchronous, event-driven operations that depend on the event processing pipeline. This included delays in delivering group membership and user profile changes to products such as Jira and Confluence, which affected downstream permission synchronisation and crowd sync flows. A small number of SCIM-based identity synchronisation and site provisioning workflows also experienced temporary delays.\n\nAfter the event processing infrastructure recovered, backed-up identity and group directory events were replayed where required, restoring downstream consistency for affected products. No identity data was lost. Group membership changes, user profile updates, and provisioning-related events that occurred during the impact window were retained and processed after recovery.\n\n### **REMEDIAL ACTIONS PLAN & NEXT STEPS**\n\nWe know outages impact your productivity. While our monitoring and recovery processes helped us respond quickly, this incident highlighted opportunities to further strengthen resilience for event-driven services.\n\nWe are prioritizing improvements that will:\n\n* **Enhance failover coverage** so critical event processing can recover more smoothly during infrastructure disruptions.\n* **Strengthen recovery handling** so replayed events can be processed more quickly.\n\nWe apologize to customers whose services were impacted during this incident; we are taking immediate steps to improve the platform\u2019s performance and availability.\n\nThanks,\n\nAtlassian Customer Support.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-08T19:45:32.332Z", "resolved_inferred": false, "started_at": "2026-05-08T01:31:38.318Z", @@ -38,7 +38,7 @@ "body": "### Postmortem publish date: Nov 19th, 2025\n\n### Summary\n\nAll dates and times below are in UTC unless stated otherwise.\n\nCustomers utilizing Atlassian products experienced elevated error rates and degraded performance between Oct 20, 2025 06:48 and Oct 21, 2025 04:05. The service disruptions were triggered due to an [AWS DynamoDB outage](https://aws.amazon.com/message/101925/#:~:text=1%3A50%20PM.-,DynamoDB,-Between%2011%3A48) and further affected by subsequent failures in [AWS EC2](https://aws.amazon.com/message/101925/#:~:text=service%20disruption%20event.-,Amazon%20EC2,-Between%2011%3A48) and [AWS Network Load Balancer](https://aws.amazon.com/message/101925/#:~:text=service%20disruption%20event.-,Amazon%20EC2,-Between%2011%3A48) within the us-east-1 region.\n\nThe incident started at Oct 20, 2025 06:48 and was detected within six minutes by our automated monitoring systems. Our teams worked to restore all core services by Oct 21, 2025 04:05. Final cleanup of backlogged processes and minor issues was completed on Oct 22, 2025.\n\nWe recognize the critical role our products play in your daily operations, and we offer our sincere apologies for any impact this incident had on your teams. We are taking immediate steps to enhance the reliability and performance of our services, so that you continue to receive the standard of service you have come to trust.\n\n### IMPACT\n\nBefore examining product-level impacts, it's helpful to understand Atlassian's service topology and internal dependencies.\n\nProducts such as Jira and Confluence are deployed across multiple AWS regions. The data for each tenant is stored and processed exclusively within its designated host region. This design is intentional and represents the desired operational state, as it limits the impact of any regional outage strictly to tenants in-region, in this case us-east-1.\n\nWhile in-scope application data is pinned to the region selected by the customer, there are times when systems need to call other internal services that may be based in a different region. If a problem occurs in the main region where these services operate, systems are designed to automatically fail over to a backup region, usually within three minutes.\n\nHowever, if unexpected issues arise during this failover, it can take longer to restore services. In rare cases, this could affect customers in more than one region. It\u2019s important to note that all in-scope application data for supported products is pinned according to a customer\u2019s chosen region.\n\n**Jira**\n\nBetween Oct 20, 2025 06:48 and Oct 20, 2025 20:00, customers with tenants hosted in the us-east-1 region experienced increased error rates when accessing core entities such as Issues, Boards, and Backlogs. This disruption was caused by AWS's inability to allocate AWS EC2 instances and elevated errors in AWS Network Load Balancer \\(NLB\\). During this window, users may also have observed intermittent timeouts, slow page loads, and failures when performing operations like creating or updating issues, loading board views, and executing workflow transitions.\n\nBetween Oct 20, 2025 08:36 and Oct 20, 2025 09:23, customers across all regions experienced elevated failure rates when attempting to load Jira pages. This disruption was caused by the regional frontend service entering an unhealthy state during this specific time interval.\n\nNormally, the frontend service connects to the primary AWS DynamoDB instance located in the us-east-1 to retrieve the most recent configuration data necessary for proper operation. Additionally, the service is designed with a fallback mechanism that references static configuration data in the event that the primary database becomes inaccessible. Unfortunately, a latent bug existed in the local fallback path. When the frontend service nodes restarted, they were unable to load critical operational configuration data from primary or fallback sources, leading to the observed failures experienced by customers.\n\nBetween Oct 20, 2025 06:48 and Oct 21, 2025 06:30, customers experienced significant delays and missing Jira in-app notifications across all regions. The notification ingestion service, which is hosted exclusively in us-east-1, exhibited an increased failure rate when processing notification messages due to AWS EC2 and NLB issues. This issue resulted in notifications being delayed - and in some cases, not delivered at all - to users worldwide.\n\n**Jira Service Management \\(JSM\\)**\n\nJSM was impacted similarly to Jira above, with the same timeframes and for the same reasons.\n\nBetween Oct 20, 2025 08:36 and Oct 20, 2025 09:23, customers across all regions experienced significantly elevated failure rates when attempting to load JSM pages. This affected all JSM experiences including the Help Centre, Portal, Queues, Work Items, Operations, and Alerts.\n\n**Confluence**\n\nBetween Oct 20, 2025 06:48 and Oct 21, 2025 02:45, customers using Confluence in the us-east-1 region experienced elevated failure rates when performing common operations such as editing pages or adding comments. The primary cause of this service degradation was the system's inability to auto-scale due to AWS EC2 issues to manage peak traffic load effectively.\n\nThough the AWS outage ended at Oct 20, 21:09, a subset of customers continued to experience failures as some Confluence web server nodes across multiple clusters remained in an unhealthy state. This was ultimately mitigated by recycling the affected nodes.\n\nTo protect our systems while AWS recovered, we made a deliberate decision to enable node termination protection. This action successfully preserved our server capacity but, as a trade-off, it extended the time required for a full recovery once AWS services were restored.\n\n**Automation**\n\nBetween Oct 20, 2025 06:55 and Oct 20, 2025 23:59, automation customers whose rules are processed in us-east-1 experienced delays of up to 23 hours in rule execution.\n\nDuring this window, some events triggering rule executions were processed out of order because they arrived later during backlog processing. This caused potential inconsistencies in workflow executions, as rules were run in the order events were received, not when the action causing the event occurred. Additionally, some rule actions failed because they depend on first-party and third-party systems, which were also affected by the AWS outage. Customers can see most of these failures in their audit logs; however, a few updates were not logged due to the nature of the outage.\n\nBy Oct 21, 2025 5:30, the backlog of rule runs in us-east-1 was cleared. Although most of these delayed rules were successfully handled, there were some additional replays of events to ensure completeness. Our investigation confirmed that a few events may never have triggered their associated rules due to the outage.\n\nBetween Oct 20, 2025 06:55 and Oct 20, 2025 11:20, all non-us-east-1 regional automation services experienced delays of up to 4 hours in rule execution. This was caused by an upstream service that was unable to deliver events as expected. The delivery service encountered a failure due to a cross-region dependency call to a service hosted in the us-east-1 region. Because of this dependency issue, the delivery service was unable to successfully deliver events throughout this time frame, resulting in customer-defined rules not being executed in a timely manner.\n\n**Bitbucket and Pipelines**\n\nBetween Oct 20, 2025 06:48 and Oct 20, 2025 09:33, Bitbucket experienced intermittent unavailability across core services. During this period, users faced increased error rates and latency when signing in, navigating repositories, and performing essential actions such as creating, updating, or approving pull requests. The primary cause was an AWS DynamoDB outage that impacted downstream services.\n\nBetween Oct 20, 2025 06:48 and Oct 20, 2025 22:46, numerous Bitbucket Pipeline steps failed to start, stalled mid-execution, or experienced significant queueing delays. Impact varied, with partial recoveries followed by degradation as downstream components re-synchronized. The primary cause was an AWS DynamoDB outage, compounded by instability in AWS EC2 instance availability and AWS Network Load Balancers.\n\nFurthermore, Bitbucket Pipelines continued to experience a low but persistent rate of step timeouts and scheduling errors due to AWS bare-metal capacity shortages in select availability zones. Atlassian coordinated with AWS to provision additional bare-metal hosts and addressed a significant backlog of pending pods, successfully restoring services by 01:30 on Oct 21, 2025.\n\n**Trello**\n\nBetween Oct 20, 2025 06:48 and Oct 20, 2025 15:25, users of Trello experienced widespread service degradation and intermittent failures due to upstream AWS issues affecting multiple components, including AWS DynamoDB and subsequent AWS EC2 capacity constraints. During this period, customers reported elevated error rates when loading boards, opening cards, adding comments or attachments.\n\n**Login**\n\nBetween Oct 20, 2025 06:48 and Oct 20, 2025 09:30, a small subset of users experienced failures when attempting to initiate new login sessions using SAML tokens. This resulted in an inability for those users to access Atlassian products during that time period. However, users who already had valid active sessions were not affected by this issue and continued to have uninterrupted access.\n\nThe issue impacted all regions globally because regional identity services relied on a write replica located in the us-east-1 region to synchronize profile data. When the primary region became unavailable, the failover to a secondary database in another region failed, which delayed recovery. This failover defect has since been addressed.\n\n**Statuspage**\n\nBetween Oct 20, 2025 06:48 and Oct 20, 2025 09:30, Statuspage customers who were not already logged in to the management portal were unable to log in to create or update incident statuses. This impact was restricted only to users who were not already logged in at the time. The root cause was the same as described in the Login section above, and it was resolved by the same remediation steps.\n\n### REMEDIAL ACTION PLAN & NEXT STEPS\n\nWe have completed the following critical actions designed to help prevent cross-region impact from similar issues:\n\n* Resolved the code defect in the fallback option to ensure that Jira Frontend Services in other regions remain unaffected during a region-wide outage.\n* Fixed the issue that prevented timely failover of the identity service which impacted new login sessions.\n* Resolved the code defect so that delivery services in unaffected regions remain operational during region-wide outages.\n\nAdditionally, we are prioritizing the following improvement actions:\n\n* Implement mitigation strategies to strengthen resilience against region-wide outages in the notification ingestion service.\n\nAlthough disruptions to our cloud services are sometimes unavoidable during outages of the underlying cloud provider, we continuously evaluate and improve test coverage to strengthen resilience of our cloud services against these issues.\n\nWe recognize the critical importance of our products to your daily operations and overall productivity, and we extend our sincere apologies for any disruptions this incident may have caused your teams. If you were impacted and require additional details for internal post-incident reviews, please reach out to your Atlassian support representative with affected timeframes and tenant identifiers so we can correlate logs and provide guidance.\n\nThanks,\n\nAtlassian Customer Support", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-21T05:24:27.565Z", "resolved_inferred": false, "started_at": "2025-10-20T07:56:12.959Z", @@ -51,7 +51,7 @@ "body": "Between 13:10 UTC to 14:00 UTC, we experienced notification delay for Jira Service Management, Opsgenie, and Compass in only EU-region. The issue has been resolved and the service is operating normally.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-30T14:32:25.335Z", "resolved_inferred": false, "started_at": "2025-09-30T14:07:08.233Z", @@ -64,7 +64,7 @@ "body": "### **SUMMARY**\n\nOn September 22, 2025, between 04:38 and 04:48 UTC, Atlassian customers experienced connection errors preventing access to their [atlassian.net](http://atlassian.net/) sites. Some customers observed intermittent errors as services gradually recovered until 06:17 UTC.\n\nThe event was triggered by a faulty configuration change to our Content Delivery Network \\(CDN\\). The change included an invalid hostname which prevented customers from successfully connecting to [atlassian.net](http://atlassian.net/) domains.\n\nThe incident was detected within 1 minute by our monitoring systems and mitigated by rolling back the change, which put Atlassian systems into a known good state. The acute impact was resolved in 10 minutes and all lingering errors resolved in 1 hour 38 minutes.\n\n### **IMPACT**\n\nThe acute impact occurred on\u00a0September 22, 2025, between 04:38 UTC and 04:48 UTC to Confluence, Compass and Jira, including Jira Service Management. The incident caused service disruption to customers when they attempted to load those products in their browser or interact with APIs. Between 04:48 UTC and 06:17 UTC some customers continued to observe intermittent errors as services gradually recovered.\n\n### **ROOT CAUSE**\n\nThe issue was caused by a change to the hostname configuration of our Content Delivery Network \\(CDN\\). As a result, the products mentioned could not receive connections, and the users received TLS handshake errors, followed by HTTP 503 and 403 errors.\n\nMore specifically a new CDN configuration contained a resource name which conflicted with the existing customer-serving CDN resource, and was able to be deployed, overwriting it. The root cause of the incident was the failure in the detection of the bug by our pre-deployment validations and tests.\n\n### **REMEDIAL ACTIONS PLAN & NEXT STEPS**\n\nWe know that you rely on our products for your daily operations and productivity, and we sincerely apologize for any impact this disruption has had on you, your team or your organisation.\n\nWe are prioritizing the following improvement actions to help avoid repeating this type of incident:\n\n* Improved pre-deployment change controls and testing.\n* Improved validation of target configurations before deployment to ensure customer-serving CDN resources cannot their hostnames changed.\n* Sharding of our CDN configuration to enable progressive changes.\n\nWe sincerely appreciate your understanding and patience as we improve our processes to provide a better customer experience.\n\nThank you,\n\nAtlassian Customer Support", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-22T07:17:23.768Z", "resolved_inferred": false, "started_at": "2025-09-22T05:59:59.177Z", @@ -77,7 +77,7 @@ "body": "Between September 10, 2025, 3:19 PM UTC and September 11, 2025, 2:44 PM UTC, there was degraded performance in web experiences and the REST APIs for some Jira Service Management, Opsgenie, and Compass Cloud customers in the US region. We have deployed a fix to mitigate the issue and have verified that the services have recovered. The issue has been resolved and the service is operating normally.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-11T18:45:19.750Z", "resolved_inferred": false, "started_at": "2025-09-11T08:53:32.822Z", diff --git a/api/v/atlassian-developer.json b/api/v/atlassian-developer.json index 12f613533f0d0cda2afb413874f0173aa6bebbee..1f7e45e72d6825605603b41f6a497e13a94714b2 100644 --- a/api/v/atlassian-developer.json +++ b/api/v/atlassian-developer.json @@ -3,7 +3,7 @@ "slug": "atlassian-developer", "platform": "statuspage", "status_url": "https://developer.status.atlassian.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "We have identified the cause of the issue impacting installation requests and deployed a fix. The issue is now resolved, and the service is operating normally for all affected customers.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-09-02T03:17:39.246Z", "resolved_inferred": false, "started_at": "2026-09-02T03:09:23.978Z", @@ -25,7 +25,7 @@ "body": "On Aug 25th, 2026, between 08:12 UTC and 11:03 UTC, some Marketplace apps may have experienced scheduled triggers (5-minute intervals) not firing as expected.\n\nThe issue has now been resolved and the 5-minute scheduled triggers are operating normally for all customers.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-25T11:11:04.824Z", "resolved_inferred": false, "started_at": "2026-08-25T10:58:56.965Z", @@ -38,7 +38,7 @@ "body": "We have confirmed that the issues relating to installing, uninstalling and managing Forge and OAuth 2.0 apps should now be fully resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-03T03:37:51.207Z", "resolved_inferred": false, "started_at": "2026-08-03T03:26:36.528Z", @@ -51,7 +51,7 @@ "body": "On Jul 13, 2026, partner operations may have experienced some service disruption. The issue has now been resolved, and the service is operating normally for all affected customers.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-13T17:46:03.265Z", "resolved_inferred": false, "started_at": "2026-07-13T15:48:27.246Z", @@ -64,7 +64,7 @@ "body": "All customers that had previously received the incorrect notifications about the Time Tracker for Jira Cloud and DC app should have received corrective communications at this time.\n\nWe are now resolving this issue.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-02T04:43:17.909Z", "resolved_inferred": false, "started_at": "2026-06-30T02:45:58.000Z", @@ -77,7 +77,7 @@ "body": "On June 26, 2026, some customers may have experienced performance degradation with remote Forge apps facing rate-limiting issues. The issue has now been resolved, and the service is operating normally for all affected customers.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-26T21:39:37.248Z", "resolved_inferred": false, "started_at": "2026-06-26T14:32:39.810Z", @@ -90,7 +90,7 @@ "body": "We are now confident that any of the tasks that were impacted by this incident and were delayed should now be operating as expected.\n\nWe apologize for any inconvenience that this issue may have caused.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-10T06:31:05.820Z", "resolved_inferred": false, "started_at": "2026-06-10T04:55:13.006Z", @@ -103,7 +103,7 @@ "body": "Between 08:30 UTC and 13:51 UTC on 26 May 2026, some users were unable to load or edit certain macros in the Confluence Cloud page editor. Our engineering team identified and resolved the underlying issue, and macro functionality has been fully restored.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-26T13:55:52.263Z", "resolved_inferred": false, "started_at": "2026-05-26T10:40:00.326Z", @@ -116,7 +116,7 @@ "body": "The root cause has been identified and a fix has been applied.\n\nFull service restoration has been completed.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-20T14:14:35.345Z", "resolved_inferred": false, "started_at": "2026-05-20T12:06:23.836Z", @@ -129,7 +129,7 @@ "body": "Due to an incorrect deployment, a banner stating 'This app may stop working soon' was briefly displayed on the Marketplace Apps. This banner was not intended to appear on these apps.\n\nThe feature has since been corrected and the banner is no longer appearing. No action is required, the banner was displayed in error and there is no impact to app functionality or availability.\n\nWe apologise for any confusion this may have caused.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-20T10:16:52.997Z", "resolved_inferred": false, "started_at": "2026-05-20T10:16:52.944Z", @@ -142,7 +142,7 @@ "body": "On May 14, 2026, Developer and Marketplace service desks were inaccessible for affected users. The issue has now been resolved, and the service is operating normally for all affected customers.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-14T21:35:12.921Z", "resolved_inferred": false, "started_at": "2026-05-14T21:04:04.214Z", @@ -155,7 +155,7 @@ "body": "All products and services impacted by this incident should now be fully recovered, and this incident is resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-14T06:49:28.904Z", "resolved_inferred": false, "started_at": "2026-05-14T05:11:20.261Z", @@ -168,7 +168,7 @@ "body": "On May 12, 2026, some users in US East region may have experienced intermittent failures with forge invocations for some applications. The issue has now been resolved, and the service is operating normally for all affected customers.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-12T17:40:43.123Z", "resolved_inferred": false, "started_at": "2026-05-12T15:50:29.317Z", @@ -181,7 +181,7 @@ "body": "On May 12, 2026, some users in EU West region may have experienced delayed or queued webhook events. The issue has now been resolved, and the service is operating normally for all affected customers.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-12T18:11:26.274Z", "resolved_inferred": false, "started_at": "2026-05-12T14:03:20.536Z", @@ -194,7 +194,7 @@ "body": "On May 11, 2026, users in EU West and US East regions may have experienced performance degradation with delayed or queued webhook events. The issue has now been resolved, and the service is operating normally for all affected customers.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-11T18:16:05.697Z", "resolved_inferred": false, "started_at": "2026-05-11T14:24:14.135Z", @@ -207,7 +207,7 @@ "body": "All dates and times below are in UTC unless stated otherwise.\n\n### Summary\n\nOn May 8, 2026 between 00:22 and 06:08, one of our hosting providers suffered a significant incident in a specific availability zone in prod-east which led to Atlassian customers experiencing degraded performance and delays of background operations and automation execution.\n\nThe incident started on May 8, 2026 at 00:22 and was detected within 4 minutes by automated monitoring systems. Our teams worked to restore core access by 06:08. Final cleanup of backlogged processes and minor issues progressed in stages from there was completed iteratively by 19:15.\n\n### **IMPACT**\n\nThe primary infrastructure affected in this incident was the event processing pipeline in the prod-east region, which distributes events between Atlassian services and underpins background operations such as automation execution, search indexing, notifications, permission synchronisation.\n\n* Between 00:22 and 06:08, an infrastructure incident in our hosting provider triggered an ingestion failure in our event processing pipeline.\n* At 02:50, event ingestion was failed over to an unaffected availability zone, progressively restoring live event flows.\n* At 06:08, reliability for new ingestion in prod-east recovered to 100%. The remaining work was to drain the accumulated cross-region backlog of messages, which completed by 17:00.\n* By 18:48, Automation had processed their backlog of events that were created while processing\n\n**Automation**\n\nBetween 00:22 and 02:50, customers with automation rules triggered by events originating from the prod-east region experienced a significant reduction in rule executions. During this window, event-triggered automation rules were not firing because the events that trigger them were not being delivered. Rule authoring, saving, and rules triggered manually, by schedules, or by webhooks were not affected.\n\nAt 02:50, the event processing infrastructure failed over to an unaffected availability zone, restoring delivery of live events to Automation and allowing new event-triggered rules to begin executing normally. However, events generated during the impact window still needed to be replayed before delayed automations could be processed.\n\nBeginning at 08:28, upstream services replayed their queued events in a coordinated sequence, and all replayed events were processed by 18:48. During the replay window, customers may have experienced automation rules executing later than expected, a small number of rules reaching daily processing limits due to compressed replay, and time-sensitive rules not completing as expected if internal timeout thresholds were exceeded.\n\n**Jira and Jira Service Management**\n\nBetween 00:22 and 02:50, customers with tenants hosted in the prod-east region experienced disruption to Jira and Jira Service Management event-driven features like automation, along with a short period of elevated errors during infrastructure failover. Core Jira experiences, including issue view, boards, and project navigation, remained available throughout the incident.\n\nJira event delivery was affected by the primary impact, preventing downstream services from receiving issue lifecycle events. This affected automation rules triggered by Jira events, AI agent orchestration in Jira, notifications for issue updates and transitions, search indexing for newly created or modified issues, and event-driven integrations between Jira and other Atlassian products.\n\nAt 02:50, the event processing infrastructure failed over to an unaffected availability zone, restoring delivery of new events. All events generated during the impact window were retained in a recovery queue and required replaying. This began at 08:28 and completed at 12:00. During the replay window, customers may have experienced automation rules executing later than expected, delayed notifications arriving hours after the triggering action, temporary gaps in search results for content created or modified during the impact window, and AI agent workflows not completing as expected where internal timeout thresholds were exceeded.\n\n**Confluence**\n\nBetween 00:22 and 02:50, customers with tenants hosted in the prod-east region experienced disruptions to event-driven services in Confluence. This resulted in delays to search indexing, notifications, automation rule execution, and permission synchronisation.\n\nThe underlying event processing infrastructure failed over to an unaffected availability zone, after which live Confluence operations resumed normally. However, events generated during the impact window were queued for replay, and some background services remained delayed until that replay and related validation work completed.\n\nBetween 10:14 and 17:00, a bulk replay of all the queued tenant replay tasks was completed to restore data consistency. During and immediately after the replay window, customers may have experienced search results not reflecting content created or modified during the outage, delayed or missing notifications for page and comment activity, automation rules firing later than expected, and brief delays in permission synchronisation for tenants relying on incremental identity sync.\n\n**Bitbucket and Pipelines**\n\nBetween 00:22 and 06:08, customers using Bitbucket and Pipelines experienced failures and degraded functionality across event-driven workflows. Core Git operations, including push, pull, and clone, were not affected and continued to operate normally throughout the incident.\n\nAutomatic pipeline triggers initiated by push or pull request events were unavailable during the impact window. Merge queues, custom merge checks, Forge-based triggers, workspace permission changes, and some workspace provisioning flows were also affected. Customers using merge queues were unable to merge pull requests, and some pipeline steps failed because queued work contributed to elevated concurrency limits.\n\nAt approximately 03:57, Pipelines was reconfigured to consume events through an alternative path, restoring automatic pipeline triggering. Merge queues, custom merge checks, Forge triggers, and other affected workflows were progressively restored as the underlying event processing infrastructure recovered. All Bitbucket and Pipelines services were confirmed fully operational by 06:08. After recovery, queued events were reviewed and replayed where safe to restore data consistency for billing, audit logging, and other background processes.\n\n**Identity Services**\n\nBetween 00:22 and 02:50, customers with tenants hosted in the prod-east region experienced delays in the propagation of identity and group membership changes to downstream Atlassian products. Core identity operations, including authentication, login, and direct group management actions, were not affected and continued to function normally throughout the incident.\n\nThe impact was limited to asynchronous, event-driven operations that depend on the event processing pipeline. This included delays in delivering group membership and user profile changes to products such as Jira and Confluence, which affected downstream permission synchronisation and crowd sync flows. A small number of SCIM-based identity synchronisation and site provisioning workflows also experienced temporary delays.\n\nAfter the event processing infrastructure recovered, backed-up identity and group directory events were replayed where required, restoring downstream consistency for affected products. No identity data was lost. Group membership changes, user profile updates, and provisioning-related events that occurred during the impact window were retained and processed after recovery.\n\n### **REMEDIAL ACTIONS PLAN & NEXT STEPS**\n\nWe know outages impact your productivity. While our monitoring and recovery processes helped us respond quickly, this incident highlighted opportunities to further strengthen resilience for event-driven services.\n\nWe are prioritizing improvements that will:\n\n* **Enhance failover coverage** so critical event processing can recover more smoothly during infrastructure disruptions.\n* **Strengthen recovery handling** so replayed events can be processed more quickly.\n\nWe apologize to customers whose services were impacted during this incident; we are taking immediate steps to improve the platform\u2019s performance and availability.\n\nThanks,\n\nAtlassian Customer Support.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-08T19:45:31.603Z", "resolved_inferred": false, "started_at": "2026-05-08T04:10:28.630Z", @@ -220,7 +220,7 @@ "body": "On Tuesday, May 5, 2026, some Forge users may have experienced performance delays in webhook delivery in the US East region. The issue has now been resolved, and the service is operating normally for all affected customers.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-05T22:34:14.686Z", "resolved_inferred": false, "started_at": "2026-05-05T17:40:11.867Z", @@ -233,7 +233,7 @@ "body": "The issue causing intermittent delays in our webhook delivery has been resolved. A fix was deployed to address a resource constraint in our systems. Our monitoring shows webhook delivery is now operating normally.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-30T14:56:57.972Z", "resolved_inferred": false, "started_at": "2026-04-30T08:59:04.029Z", @@ -246,7 +246,7 @@ "body": "The issue has now been resolved, and the service is operating normally for all affected customers.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-28T21:50:42.758Z", "resolved_inferred": false, "started_at": "2026-04-28T18:28:20.767Z", @@ -259,7 +259,7 @@ "body": "The issue has now been resolved, and the service is operating normally for all affected customers.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-23T16:14:43.771Z", "resolved_inferred": false, "started_at": "2026-04-22T06:57:00.565Z", @@ -272,7 +272,7 @@ "body": "The issue has now been resolved, and the service is operating normally for all affected customers.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-13T15:11:45.243Z", "resolved_inferred": false, "started_at": "2026-04-13T10:58:02.547Z", @@ -285,7 +285,7 @@ "body": "The outage affecting Forge app logs between 05:00 UTC and 07:00 UTC on 8 April 2026 has been resolved, and systems are now stable.\n\nWe are currently working on recovery efforts, including retrieving logs from this downtime window and validating data completeness. During this process, you may temporarily see duplicate log entries; however, this will not result in duplicate usage or additional costs.\n\nWe will continue to monitor the system closely and provide further updates as needed.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-08T07:45:13.000Z", "resolved_inferred": false, "started_at": "2026-04-08T06:55:07.248Z", @@ -298,7 +298,7 @@ "body": "On April 2, 2026, affected users may have experienced some service disruption. The issue has now been resolved, and the service is operating normally for all affected customers.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-02T22:36:41.280Z", "resolved_inferred": false, "started_at": "2026-04-02T20:46:43.730Z", @@ -311,7 +311,7 @@ "body": "On March 24, 2026, between 04:14 AM UTC and 08:40 AM UTC, Connect Apps using connect API's experienced performance degradation. The issue has now been resolved, and the service is operating normally for all affected customers.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-24T08:44:23.346Z", "resolved_inferred": false, "started_at": "2026-03-24T07:59:20.308Z", @@ -324,7 +324,7 @@ "body": "On March 17th, 2026, between 9:05 AM UTC and 11:10 AM UTC, Forge app management and related developer tooling experienced some service disruption. The issue has now been resolved, and the service is operating normally for affected customers.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-17T11:37:37.061Z", "resolved_inferred": false, "started_at": "2026-03-17T10:05:28.000Z", @@ -337,7 +337,7 @@ "body": "On March 12, 2026, affected Confluence Cloud users may have experienced some service disruption. The issue has now been resolved, and the service is operating normally for all affected customers.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-13T00:26:04.153Z", "resolved_inferred": false, "started_at": "2026-03-12T11:42:38.845Z", @@ -350,7 +350,7 @@ "body": "We are providing a further update regarding the install count discrepancy that some partners may have observed for some apps since Feb 27, 2026.\n\n- The Active Installations tab in the Marketplace Partner Portal is now showing accurate install counts for impacted apps from Mar 3, 2026 onward.\n- The install counts displayed on app listings remain accurate for impacted apps.\n- Please note that data from Mar 3, 2026 onward will remain accurate going forward.\n- You may notice a temporary dip in install counts for Mar 2, 2026. We are backfilling the data, and counts for that date will be restored once complete.\n- Actual customer installs were not impacted; only the reported counts displayed in the Partner Portal and on app listings were affected for some apps, and this is now fully functional.\n\nThank you for your patience and understanding.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-04T03:04:15.737Z", "resolved_inferred": false, "started_at": "2026-03-02T16:15:12.562Z", @@ -363,7 +363,7 @@ "body": "We have now reactivated all subscriptions that were previously cancelled. Impacted users may have received email notifications confirming this change. There has been no impact to the functioning of the app, it should continue to work as expected.\nTo help prevent any future interruptions, we kindly request that billing admins ensure a valid billing payment method is added before the next billing cycle.\nWe apologise for any confusion and appreciate your understanding.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-19T17:12:31.473Z", "resolved_inferred": false, "started_at": "2026-02-16T11:24:02.892Z", @@ -376,7 +376,7 @@ "body": "This issue is resolved. In our monitoring no other unexpected issues were seen.\n\nFor customers still experiencing errors, this may indicate a legitimate permission configuration issue on your side and should be investigated as usual.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-19T08:04:57.460Z", "resolved_inferred": false, "started_at": "2026-02-13T07:41:39.717Z", @@ -389,7 +389,7 @@ "body": "Impact\n\nWe are currently experiencing an issue affecting the Forge platform, specifically related to scheduled triggers. Users may encounter instances where these triggers are not executing as anticipated, disrupting the normal operation of their Forge apps. This behavior began approximately at 2 AM UTC.\n\nCurrent Status\n\nOur engineering team identified the root cause and performed a rollback deployment to resolve the issue.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-06T11:32:35.358Z", "resolved_inferred": false, "started_at": "2026-02-06T09:37:35.831Z", @@ -402,7 +402,7 @@ "body": "Team has identified the root cause and the issue has now been resolved, and the impacted services are operating normally. Team will continue to monitor the impacted services.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-03T10:50:35.750Z", "resolved_inferred": false, "started_at": "2026-02-03T10:19:54.355Z", @@ -415,7 +415,7 @@ "body": "On January 28, 2026, some customers may have experienced Forge function invocation availability disruption. The issue has now been resolved, and the service is operating normally for all affected customers.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-28T19:20:20.274Z", "resolved_inferred": false, "started_at": "2026-01-28T17:34:56.308Z", @@ -428,7 +428,7 @@ "body": "The issue is completely resolved and Developer Console is now displaying all the usage metrics correctly. We apologize for any inconvenience this may have caused.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-17T06:07:27.782Z", "resolved_inferred": false, "started_at": "2025-12-16T05:47:29.672Z", @@ -441,7 +441,7 @@ "body": "The rollback required to resolve this issue is now completed, and we have verified across the impacted products that App installation behaviour is now working as expected. We apologize for any inconvenience this may have caused.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-11T04:37:14.124Z", "resolved_inferred": false, "started_at": "2025-12-11T01:08:44.953Z", @@ -454,7 +454,7 @@ "body": "Between Dec 8 05:30 UTC and Dec 9 05:30 UTC, new Forge app versions were not auto-published to Atlassian Marketplace. We\u2019ve implemented a mitigation and auto-publish is operating normally.\n\nAction required: If you deployed during this window, please manually publish those versions in Marketplace (or re-deploy your app with forge deploy). \n\nWe\u2019re sorry for the inconvenience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-09T08:14:04.000Z", "resolved_inferred": false, "started_at": "2025-12-09T08:14:04.000Z", @@ -467,7 +467,7 @@ "body": "The feature flag causing the issue has been reverted, fixing the problem. With that this incident is resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-05T12:09:05.554Z", "resolved_inferred": false, "started_at": "2025-12-05T08:08:53.836Z", @@ -480,7 +480,7 @@ "body": "Impact\n\nCustomers experienced degraded performance in log ingestion services affecting the Ecosystem, particularly the Forge platform. Due to this issue, accessing logs ingested from the morning of the incident (starting 06:00 UTC) was impacted, leading to delays or incomplete data visibility through the Dev Console and related channels.\n\nCurrent Status\n\nThis incident has been resolved, and Forge Logs are back in operational mode.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-10T14:03:18.231Z", "resolved_inferred": false, "started_at": "2025-11-10T10:41:39.876Z", @@ -493,7 +493,7 @@ "body": "Validation is complete. All tables backing Aggregated Sales Reporting, Transaction Reporting, and Export Transaction APIs have been fully repopulated. Data for the impacted window (25 Oct 2025 00:00 IST \u2013 27 Oct 2025 14:00 IST) has been restored and verified. No action is required from vendors. We are closing this incident.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-28T13:42:21.577Z", "resolved_inferred": false, "started_at": "2025-10-27T12:04:05.344Z", @@ -506,7 +506,7 @@ "body": "### Summary\n\nOn October 22, 2025, Confluence Cloud webhook events were not delivered to Connect apps and Forge apps that use webhooks via `connectModules`. This outage began after a backend deployment introduced a code change that prevented Confluence from recognizing registered webhook listeners. As a result, no webhook events were generated for approximately 20 hours, impacting apps that depend on webhooks. The issue was resolved by rolling back to a previous stable deployment. We\u2019re taking steps to improve detection and rollback processes.\n\n### **IMPACT**\n\nBetween 01:12 UTC and 21:46 UTC on October 22, 2025, Confluence was unable to send out webhook events. As a result, none of the apps that rely on these events received them during this time. This includes Connect apps and Forge apps that use webhooks through `connectModules`.\n\nCustomers may have noticed outdated content appearing in their Marketplace apps, or new content not syncing.\n\n### **ROOT CAUSE**\n\nThe issue was caused by a change to Confluence backend systems. As a result, no webhook events were delivered to Connect and Forge apps that use webhooks via `connectModules`. This occurred because a Java class was loaded by 2 different classloaders, causing Confluence to fail to find registered webhook listeners and thus not emit events.\n\n### **REMEDIAL ACTIONS PLAN & NEXT STEPS**\n\nWebhooks are a critical functionality for many apps. On this occasion, our system did not generate any errors because it was inadvertently using an incorrect version of a Java class, which was loaded by a different ClassLoader. As a result, the issue occurred silently and couldn\u2019t be detected via existing automated error monitoring.\n\n\u00a0\n\nWe are prioritizing the following improvement actions to help prevent this issue from reoccurring:\n\n* Additional integration tests to identify problems before merging code to our main branch.\n* Additional detectors and alerts to identify when webhook event volume drops below a certain threshold.\n* Exploring resync / lost event recovery mechanism without overloading Atlassian infrastructure\n\n * We acknowledge that the availability of Connect apps is important for our customers and ecosystem partners, and we will endeavour to provide support for these apps in line with our public roadmap for Connect end of life. You can read our announcement here: [Announcing Connect End of Support: Timeline and Next Steps - Work Life by Atlassian](https://www.atlassian.com/blog/developer/announcing-connect-end-of-support-timeline-and-next-steps)\n \n While this incident primarily impacted Connect, we would like to note that Forge currently includes additional internal capabilities, such as retry [Atlassian app events](https://developer.atlassian.com/platform/forge/events-reference/product_events/#retry-atlassian-app-events) and internal DLQ, that could assist with recovery in these types of incidents..\n\n \n \n We highly encourage partners to migrate to Forge to utilize the latest webhook infrastructure.\n\n \n \n\nWe apologize to customers and ecosystem partners whose services were impacted during this incident; we are taking immediate steps to improve the platform\u2019s performance and availability.\n\nThanks,\n\nAtlassian Customer Support", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-22T22:09:20.000Z", "resolved_inferred": false, "started_at": "2025-10-22T12:15:57.948Z", @@ -519,7 +519,7 @@ "body": "### Postmortem publish date: Nov 19th, 2025\n\n### Summary\n\nAll dates and times below are in UTC unless stated otherwise.\n\nCustomers utilizing Atlassian products experienced elevated error rates and degraded performance between Oct 20, 2025 06:48 and Oct 21, 2025 04:05. The service disruptions were triggered due to an [AWS DynamoDB outage](https://aws.amazon.com/message/101925/#:~:text=1%3A50%20PM.-,DynamoDB,-Between%2011%3A48) and further affected by subsequent failures in [AWS EC2](https://aws.amazon.com/message/101925/#:~:text=service%20disruption%20event.-,Amazon%20EC2,-Between%2011%3A48) and [AWS Network Load Balancer](https://aws.amazon.com/message/101925/#:~:text=service%20disruption%20event.-,Amazon%20EC2,-Between%2011%3A48) within the us-east-1 region.\n\nThe incident started at Oct 20, 2025 06:48 and was detected within six minutes by our automated monitoring systems. Our teams worked to restore all core services by Oct 21, 2025 04:05. Final cleanup of backlogged processes and minor issues was completed on Oct 22, 2025.\n\nWe recognize the critical role our products play in your daily operations, and we offer our sincere apologies for any impact this incident had on your teams. We are taking immediate steps to enhance the reliability and performance of our services, so that you continue to receive the standard of service you have come to trust.\n\n### IMPACT\n\nBefore examining product-level impacts, it's helpful to understand Atlassian's service topology and internal dependencies.\n\nProducts such as Jira and Confluence are deployed across multiple AWS regions. The data for each tenant is stored and processed exclusively within its designated host region. This design is intentional and represents the desired operational state, as it limits the impact of any regional outage strictly to tenants in-region, in this case us-east-1.\n\nWhile in-scope application data is pinned to the region selected by the customer, there are times when systems need to call other internal services that may be based in a different region. If a problem occurs in the main region where these services operate, systems are designed to automatically fail over to a backup region, usually within three minutes.\n\nHowever, if unexpected issues arise during this failover, it can take longer to restore services. In rare cases, this could affect customers in more than one region. It\u2019s important to note that all in-scope application data for supported products is pinned according to a customer\u2019s chosen region.\n\n**Jira**\n\nBetween Oct 20, 2025 06:48 and Oct 20, 2025 20:00, customers with tenants hosted in the us-east-1 region experienced increased error rates when accessing core entities such as Issues, Boards, and Backlogs. This disruption was caused by AWS's inability to allocate AWS EC2 instances and elevated errors in AWS Network Load Balancer \\(NLB\\). During this window, users may also have observed intermittent timeouts, slow page loads, and failures when performing operations like creating or updating issues, loading board views, and executing workflow transitions.\n\nBetween Oct 20, 2025 08:36 and Oct 20, 2025 09:23, customers across all regions experienced elevated failure rates when attempting to load Jira pages. This disruption was caused by the regional frontend service entering an unhealthy state during this specific time interval.\n\nNormally, the frontend service connects to the primary AWS DynamoDB instance located in the us-east-1 to retrieve the most recent configuration data necessary for proper operation. Additionally, the service is designed with a fallback mechanism that references static configuration data in the event that the primary database becomes inaccessible. Unfortunately, a latent bug existed in the local fallback path. When the frontend service nodes restarted, they were unable to load critical operational configuration data from primary or fallback sources, leading to the observed failures experienced by customers.\n\nBetween Oct 20, 2025 06:48 and Oct 21, 2025 06:30, customers experienced significant delays and missing Jira in-app notifications across all regions. The notification ingestion service, which is hosted exclusively in us-east-1, exhibited an increased failure rate when processing notification messages due to AWS EC2 and NLB issues. This issue resulted in notifications being delayed - and in some cases, not delivered at all - to users worldwide.\n\n**Jira Service Management \\(JSM\\)**\n\nJSM was impacted similarly to Jira above, with the same timeframes and for the same reasons.\n\nBetween Oct 20, 2025 08:36 and Oct 20, 2025 09:23, customers across all regions experienced significantly elevated failure rates when attempting to load JSM pages. This affected all JSM experiences including the Help Centre, Portal, Queues, Work Items, Operations, and Alerts.\n\n**Confluence**\n\nBetween Oct 20, 2025 06:48 and Oct 21, 2025 02:45, customers using Confluence in the us-east-1 region experienced elevated failure rates when performing common operations such as editing pages or adding comments. The primary cause of this service degradation was the system's inability to auto-scale due to AWS EC2 issues to manage peak traffic load effectively.\n\nThough the AWS outage ended at Oct 20, 21:09, a subset of customers continued to experience failures as some Confluence web server nodes across multiple clusters remained in an unhealthy state. This was ultimately mitigated by recycling the affected nodes.\n\nTo protect our systems while AWS recovered, we made a deliberate decision to enable node termination protection. This action successfully preserved our server capacity but, as a trade-off, it extended the time required for a full recovery once AWS services were restored.\n\n**Automation**\n\nBetween Oct 20, 2025 06:55 and Oct 20, 2025 23:59, automation customers whose rules are processed in us-east-1 experienced delays of up to 23 hours in rule execution.\n\nDuring this window, some events triggering rule executions were processed out of order because they arrived later during backlog processing. This caused potential inconsistencies in workflow executions, as rules were run in the order events were received, not when the action causing the event occurred. Additionally, some rule actions failed because they depend on first-party and third-party systems, which were also affected by the AWS outage. Customers can see most of these failures in their audit logs; however, a few updates were not logged due to the nature of the outage.\n\nBy Oct 21, 2025 5:30, the backlog of rule runs in us-east-1 was cleared. Although most of these delayed rules were successfully handled, there were some additional replays of events to ensure completeness. Our investigation confirmed that a few events may never have triggered their associated rules due to the outage.\n\nBetween Oct 20, 2025 06:55 and Oct 20, 2025 11:20, all non-us-east-1 regional automation services experienced delays of up to 4 hours in rule execution. This was caused by an upstream service that was unable to deliver events as expected. The delivery service encountered a failure due to a cross-region dependency call to a service hosted in the us-east-1 region. Because of this dependency issue, the delivery service was unable to successfully deliver events throughout this time frame, resulting in customer-defined rules not being executed in a timely manner.\n\n**Bitbucket and Pipelines**\n\nBetween Oct 20, 2025 06:48 and Oct 20, 2025 09:33, Bitbucket experienced intermittent unavailability across core services. During this period, users faced increased error rates and latency when signing in, navigating repositories, and performing essential actions such as creating, updating, or approving pull requests. The primary cause was an AWS DynamoDB outage that impacted downstream services.\n\nBetween Oct 20, 2025 06:48 and Oct 20, 2025 22:46, numerous Bitbucket Pipeline steps failed to start, stalled mid-execution, or experienced significant queueing delays. Impact varied, with partial recoveries followed by degradation as downstream components re-synchronized. The primary cause was an AWS DynamoDB outage, compounded by instability in AWS EC2 instance availability and AWS Network Load Balancers.\n\nFurthermore, Bitbucket Pipelines continued to experience a low but persistent rate of step timeouts and scheduling errors due to AWS bare-metal capacity shortages in select availability zones. Atlassian coordinated with AWS to provision additional bare-metal hosts and addressed a significant backlog of pending pods, successfully restoring services by 01:30 on Oct 21, 2025.\n\n**Trello**\n\nBetween Oct 20, 2025 06:48 and Oct 20, 2025 15:25, users of Trello experienced widespread service degradation and intermittent failures due to upstream AWS issues affecting multiple components, including AWS DynamoDB and subsequent AWS EC2 capacity constraints. During this period, customers reported elevated error rates when loading boards, opening cards, adding comments or attachments.\n\n**Login**\n\nBetween Oct 20, 2025 06:48 and Oct 20, 2025 09:30, a small subset of users experienced failures when attempting to initiate new login sessions using SAML tokens. This resulted in an inability for those users to access Atlassian products during that time period. However, users who already had valid active sessions were not affected by this issue and continued to have uninterrupted access.\n\nThe issue impacted all regions globally because regional identity services relied on a write replica located in the us-east-1 region to synchronize profile data. When the primary region became unavailable, the failover to a secondary database in another region failed, which delayed recovery. This failover defect has since been addressed.\n\n**Statuspage**\n\nBetween Oct 20, 2025 06:48 and Oct 20, 2025 09:30, Statuspage customers who were not already logged in to the management portal were unable to log in to create or update incident statuses. This impact was restricted only to users who were not already logged in at the time. The root cause was the same as described in the Login section above, and it was resolved by the same remediation steps.\n\n### REMEDIAL ACTION PLAN & NEXT STEPS\n\nWe have completed the following critical actions designed to help prevent cross-region impact from similar issues:\n\n* Resolved the code defect in the fallback option to ensure that Jira Frontend Services in other regions remain unaffected during a region-wide outage.\n* Fixed the issue that prevented timely failover of the identity service which impacted new login sessions.\n* Resolved the code defect so that delivery services in unaffected regions remain operational during region-wide outages.\n\nAdditionally, we are prioritizing the following improvement actions:\n\n* Implement mitigation strategies to strengthen resilience against region-wide outages in the notification ingestion service.\n\nAlthough disruptions to our cloud services are sometimes unavoidable during outages of the underlying cloud provider, we continuously evaluate and improve test coverage to strengthen resilience of our cloud services against these issues.\n\nWe recognize the critical importance of our products to your daily operations and overall productivity, and we extend our sincere apologies for any disruptions this incident may have caused your teams. If you were impacted and require additional details for internal post-incident reviews, please reach out to your Atlassian support representative with affected timeframes and tenant identifiers so we can correlate logs and provide guidance.\n\nThanks,\n\nAtlassian Customer Support", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-21T05:24:25.603Z", "resolved_inferred": false, "started_at": "2025-10-20T07:56:11.430Z", @@ -532,7 +532,7 @@ "body": "Between 06:58 12 Oct UTC to 18:30 12 Oct UTC, we experienced calls from a some forge apps to external services (outside of Atlassian) intermittently fail. The issue has been resolved and the service is operating normally.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-12T19:25:16.839Z", "resolved_inferred": false, "started_at": "2025-10-12T15:25:53.472Z", @@ -545,7 +545,7 @@ "body": "Between 06:30 12th Oct, 2025 UTC to 08:33 12th Oct, 2025 UTC, we experienced a degradation in us-east and ca-central regions affecting authenticated egress calls from Forge functions and from Forge bridge. \n\nThe issue has been resolved and the service is operating normally.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-12T09:14:40.272Z", "resolved_inferred": false, "started_at": "2025-10-12T07:29:47.822Z", @@ -558,7 +558,7 @@ "body": "Between 29 Sep 2025 07:10 UTC and 03 Oct 2025 06:00 UTC, some customers experienced unexpected Allow access OAuth consent prompts when using the Forge app UI. The issue has been resolved, and the service is operating normally.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-03T06:24:19.291Z", "resolved_inferred": false, "started_at": "2025-10-03T03:43:27.000Z", @@ -571,7 +571,7 @@ "body": "Between 08:30 AM UTC to 16:30 UTC on September 29, 2025, some developers experienced delays of log delivery for the Dev Console. The root cause was an unexpected spike in volume that required updates to autoscaling configurations to address. We have deployed a fix to mitigate the issue and have verified that the services have recovered. The conditions that cause the bug have been addressed and we\u2019re actively working on a permanent fix. The issue has been resolved and the service is processing logs normally. We are currently processing the delayed logs and anticipate completion by 17:00 UTC today, September 29, 2025.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-29T17:07:09.374Z", "resolved_inferred": false, "started_at": "2025-09-29T15:32:40.124Z", @@ -584,7 +584,7 @@ "body": "Issues affecting Marketplace Reporting APIs and Partner Portal have been resolved. Both services are now back up and running normally. This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-26T10:45:55.450Z", "resolved_inferred": false, "started_at": "2025-09-26T10:09:49.455Z", @@ -597,7 +597,7 @@ "body": "We experienced a disruption affecting all JSM assets APIs using Connect JWT and user impersonation for connect apps, starting on September 13th at 2:05 AM UTC and lasting until September 17th at 3:36 PM UTC. This issue was caused by an internal routing change within Atlassian systems. During this time, all Assets API calls using Connect authentications were disrupted. The issue has now been resolved, and all affected APIs are fully operational again. We sincerely apologise for any inconvenience caused and thank you for your patience and understanding.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-25T08:14:11.708Z", "resolved_inferred": false, "started_at": "2025-09-25T08:14:11.610Z", @@ -610,7 +610,7 @@ "body": "No customer impact has been observed seen since mitigation began. We are now closing this incident.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-19T02:02:51.884Z", "resolved_inferred": false, "started_at": "2025-09-15T02:06:05.594Z", @@ -623,7 +623,7 @@ "body": "Changes have landed in production at 11:40 AM (UTC). The issue is resolved and the endpoint is now operating normally.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-12T11:56:02.700Z", "resolved_inferred": false, "started_at": "2025-09-12T08:14:51.720Z", @@ -636,7 +636,7 @@ "body": "Between 12:50 UTC to 13:20 UTC, we experienced partial failures for deploying forge apps via forge cli for Atlassian Developers. \nThe issue has been resolved and the service is operating normally.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-08T13:46:29.610Z", "resolved_inferred": false, "started_at": "2025-09-08T13:35:23.947Z", @@ -649,7 +649,7 @@ "body": "This incident is resolved now. Between 6:30 AM and 8:35 AM UTC on September 8th, there was an issue with one of the dependent vendor services, due to which invocations were intermittently failing, primarily in the EU-CENTRAL-1 Region. This issue is fixed now.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-08T10:05:53.000Z", "resolved_inferred": false, "started_at": "2025-09-08T07:44:14.089Z", diff --git a/api/v/atlassian-partners.json b/api/v/atlassian-partners.json index 667adc7c9bf7b57f4a26e43150e146c9975f4ffb..49cc3250763b5f0af16f95308634f3d1e935fc27 100644 --- a/api/v/atlassian-partners.json +++ b/api/v/atlassian-partners.json @@ -3,7 +3,7 @@ "slug": "atlassian-partners", "platform": "statuspage", "status_url": "https://partners.status.atlassian.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "### Summary\n\nOn May 14, 2026, between 04:30 and 05:26 UTC, Atlassian customers experienced widespread service disruption across multiple Atlassian Cloud products. The issue was caused by a race condition in our internal deployment orchestration platform during a routine rollback operation of a core identity service in the us-east region. This race condition resulted in insufficient capacity for the identity service in the affected region which started returning errors to dependent products. The incident was detected within a minute by automated monitoring systems and mitigated in 56 minutes.\n\n### **IMPACT**\n\nDuring the incident, customers attempting to access Atlassian Cloud products in the us-east region experienced authentication and permission failures and were unable to access services. Customers also experienced errors when accessing the support portal until Atlassian fell back to an alternate support method. This was caused by a core identity service in the us-east region becoming unavailable. Affected products included Atlassian Administration, Atlassian Analytics, Bitbucket, Compass, Confluence, Jira, Jira Product Discovery, Jira Service Management and Trello. Some users outside us-east may have been affected in certain scenarios.\n\n### **ROOT CAUSE**\n\nThe incident was caused by a race condition in our internal deployment orchestration platform during a routine rollback operation of a core identity service in the us-east region. This race condition resulted in insufficient capacity for the identity service in the affected region which started returning errors to dependent products.\n\n### **REMEDIAL ACTIONS PLAN & NEXT STEPS**\n\nWe know that outages impact your productivity. Atlassian is prioritizing the following actions to help prevent similar incidents in future:\n\n* **Refine deployment orchestration safeguards**\n\n * Harden our deployment platform to prevent similar race conditions or resulting capacity loss during a rollback operation.\n * Streamline mitigation steps when a service becomes unavailable in a region.\n \n* **Reduce cross-region impact**\n\n * Improve regional isolation and fallback handling so an issue affecting a single region is less likely to impact customers or product functionality in other regions.\n \n\nWe recognise how critical reliable access to Atlassian products is for our customers' productivity, and we apologize to customers who were impacted by this incident.\n\nThanks,\n\nAtlassian", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-14T06:48:27.737Z", "resolved_inferred": false, "started_at": "2026-05-14T05:11:20.126Z", @@ -25,7 +25,7 @@ "body": "Users attempting to access the Atlassian shop will now be directed to our Homepage. This will prevent ongoing security related error messages from being presented in the meantime while the shop is able to be restored to its full functionality.\nPlease reach out to Atlassian Support for additional assistance if required.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-07T02:38:02.620Z", "resolved_inferred": false, "started_at": "2026-05-07T02:27:15.303Z", @@ -38,7 +38,7 @@ "body": "### Postmortem publish date: Nov 19th, 2025\n\n### Summary\n\nAll dates and times below are in UTC unless stated otherwise.\n\nCustomers utilizing Atlassian products experienced elevated error rates and degraded performance between Oct 20, 2025 06:48 and Oct 21, 2025 04:05. The service disruptions were triggered due to an [AWS DynamoDB outage](https://aws.amazon.com/message/101925/#:~:text=1%3A50%20PM.-,DynamoDB,-Between%2011%3A48) and further affected by subsequent failures in [AWS EC2](https://aws.amazon.com/message/101925/#:~:text=service%20disruption%20event.-,Amazon%20EC2,-Between%2011%3A48) and [AWS Network Load Balancer](https://aws.amazon.com/message/101925/#:~:text=service%20disruption%20event.-,Amazon%20EC2,-Between%2011%3A48) within the us-east-1 region.\n\nThe incident started at Oct 20, 2025 06:48 and was detected within six minutes by our automated monitoring systems. Our teams worked to restore all core services by Oct 21, 2025 04:05. Final cleanup of backlogged processes and minor issues was completed on Oct 22, 2025.\n\nWe recognize the critical role our products play in your daily operations, and we offer our sincere apologies for any impact this incident had on your teams. We are taking immediate steps to enhance the reliability and performance of our services, so that you continue to receive the standard of service you have come to trust.\n\n### IMPACT\n\nBefore examining product-level impacts, it's helpful to understand Atlassian's service topology and internal dependencies.\n\nProducts such as Jira and Confluence are deployed across multiple AWS regions. The data for each tenant is stored and processed exclusively within its designated host region. This design is intentional and represents the desired operational state, as it limits the impact of any regional outage strictly to tenants in-region, in this case us-east-1.\n\nWhile in-scope application data is pinned to the region selected by the customer, there are times when systems need to call other internal services that may be based in a different region. If a problem occurs in the main region where these services operate, systems are designed to automatically fail over to a backup region, usually within three minutes.\n\nHowever, if unexpected issues arise during this failover, it can take longer to restore services. In rare cases, this could affect customers in more than one region. It\u2019s important to note that all in-scope application data for supported products is pinned according to a customer\u2019s chosen region.\n\n**Jira**\n\nBetween Oct 20, 2025 06:48 and Oct 20, 2025 20:00, customers with tenants hosted in the us-east-1 region experienced increased error rates when accessing core entities such as Issues, Boards, and Backlogs. This disruption was caused by AWS's inability to allocate AWS EC2 instances and elevated errors in AWS Network Load Balancer \\(NLB\\). During this window, users may also have observed intermittent timeouts, slow page loads, and failures when performing operations like creating or updating issues, loading board views, and executing workflow transitions.\n\nBetween Oct 20, 2025 08:36 and Oct 20, 2025 09:23, customers across all regions experienced elevated failure rates when attempting to load Jira pages. This disruption was caused by the regional frontend service entering an unhealthy state during this specific time interval.\n\nNormally, the frontend service connects to the primary AWS DynamoDB instance located in the us-east-1 to retrieve the most recent configuration data necessary for proper operation. Additionally, the service is designed with a fallback mechanism that references static configuration data in the event that the primary database becomes inaccessible. Unfortunately, a latent bug existed in the local fallback path. When the frontend service nodes restarted, they were unable to load critical operational configuration data from primary or fallback sources, leading to the observed failures experienced by customers.\n\nBetween Oct 20, 2025 06:48 and Oct 21, 2025 06:30, customers experienced significant delays and missing Jira in-app notifications across all regions. The notification ingestion service, which is hosted exclusively in us-east-1, exhibited an increased failure rate when processing notification messages due to AWS EC2 and NLB issues. This issue resulted in notifications being delayed - and in some cases, not delivered at all - to users worldwide.\n\n**Jira Service Management \\(JSM\\)**\n\nJSM was impacted similarly to Jira above, with the same timeframes and for the same reasons.\n\nBetween Oct 20, 2025 08:36 and Oct 20, 2025 09:23, customers across all regions experienced significantly elevated failure rates when attempting to load JSM pages. This affected all JSM experiences including the Help Centre, Portal, Queues, Work Items, Operations, and Alerts.\n\n**Confluence**\n\nBetween Oct 20, 2025 06:48 and Oct 21, 2025 02:45, customers using Confluence in the us-east-1 region experienced elevated failure rates when performing common operations such as editing pages or adding comments. The primary cause of this service degradation was the system's inability to auto-scale due to AWS EC2 issues to manage peak traffic load effectively.\n\nThough the AWS outage ended at Oct 20, 21:09, a subset of customers continued to experience failures as some Confluence web server nodes across multiple clusters remained in an unhealthy state. This was ultimately mitigated by recycling the affected nodes.\n\nTo protect our systems while AWS recovered, we made a deliberate decision to enable node termination protection. This action successfully preserved our server capacity but, as a trade-off, it extended the time required for a full recovery once AWS services were restored.\n\n**Automation**\n\nBetween Oct 20, 2025 06:55 and Oct 20, 2025 23:59, automation customers whose rules are processed in us-east-1 experienced delays of up to 23 hours in rule execution.\n\nDuring this window, some events triggering rule executions were processed out of order because they arrived later during backlog processing. This caused potential inconsistencies in workflow executions, as rules were run in the order events were received, not when the action causing the event occurred. Additionally, some rule actions failed because they depend on first-party and third-party systems, which were also affected by the AWS outage. Customers can see most of these failures in their audit logs; however, a few updates were not logged due to the nature of the outage.\n\nBy Oct 21, 2025 5:30, the backlog of rule runs in us-east-1 was cleared. Although most of these delayed rules were successfully handled, there were some additional replays of events to ensure completeness. Our investigation confirmed that a few events may never have triggered their associated rules due to the outage.\n\nBetween Oct 20, 2025 06:55 and Oct 20, 2025 11:20, all non-us-east-1 regional automation services experienced delays of up to 4 hours in rule execution. This was caused by an upstream service that was unable to deliver events as expected. The delivery service encountered a failure due to a cross-region dependency call to a service hosted in the us-east-1 region. Because of this dependency issue, the delivery service was unable to successfully deliver events throughout this time frame, resulting in customer-defined rules not being executed in a timely manner.\n\n**Bitbucket and Pipelines**\n\nBetween Oct 20, 2025 06:48 and Oct 20, 2025 09:33, Bitbucket experienced intermittent unavailability across core services. During this period, users faced increased error rates and latency when signing in, navigating repositories, and performing essential actions such as creating, updating, or approving pull requests. The primary cause was an AWS DynamoDB outage that impacted downstream services.\n\nBetween Oct 20, 2025 06:48 and Oct 20, 2025 22:46, numerous Bitbucket Pipeline steps failed to start, stalled mid-execution, or experienced significant queueing delays. Impact varied, with partial recoveries followed by degradation as downstream components re-synchronized. The primary cause was an AWS DynamoDB outage, compounded by instability in AWS EC2 instance availability and AWS Network Load Balancers.\n\nFurthermore, Bitbucket Pipelines continued to experience a low but persistent rate of step timeouts and scheduling errors due to AWS bare-metal capacity shortages in select availability zones. Atlassian coordinated with AWS to provision additional bare-metal hosts and addressed a significant backlog of pending pods, successfully restoring services by 01:30 on Oct 21, 2025.\n\n**Trello**\n\nBetween Oct 20, 2025 06:48 and Oct 20, 2025 15:25, users of Trello experienced widespread service degradation and intermittent failures due to upstream AWS issues affecting multiple components, including AWS DynamoDB and subsequent AWS EC2 capacity constraints. During this period, customers reported elevated error rates when loading boards, opening cards, adding comments or attachments.\n\n**Login**\n\nBetween Oct 20, 2025 06:48 and Oct 20, 2025 09:30, a small subset of users experienced failures when attempting to initiate new login sessions using SAML tokens. This resulted in an inability for those users to access Atlassian products during that time period. However, users who already had valid active sessions were not affected by this issue and continued to have uninterrupted access.\n\nThe issue impacted all regions globally because regional identity services relied on a write replica located in the us-east-1 region to synchronize profile data. When the primary region became unavailable, the failover to a secondary database in another region failed, which delayed recovery. This failover defect has since been addressed.\n\n**Statuspage**\n\nBetween Oct 20, 2025 06:48 and Oct 20, 2025 09:30, Statuspage customers who were not already logged in to the management portal were unable to log in to create or update incident statuses. This impact was restricted only to users who were not already logged in at the time. The root cause was the same as described in the Login section above, and it was resolved by the same remediation steps.\n\n### REMEDIAL ACTION PLAN & NEXT STEPS\n\nWe have completed the following critical actions designed to help prevent cross-region impact from similar issues:\n\n* Resolved the code defect in the fallback option to ensure that Jira Frontend Services in other regions remain unaffected during a region-wide outage.\n* Fixed the issue that prevented timely failover of the identity service which impacted new login sessions.\n* Resolved the code defect so that delivery services in unaffected regions remain operational during region-wide outages.\n\nAdditionally, we are prioritizing the following improvement actions:\n\n* Implement mitigation strategies to strengthen resilience against region-wide outages in the notification ingestion service.\n\nAlthough disruptions to our cloud services are sometimes unavoidable during outages of the underlying cloud provider, we continuously evaluate and improve test coverage to strengthen resilience of our cloud services against these issues.\n\nWe recognize the critical importance of our products to your daily operations and overall productivity, and we extend our sincere apologies for any disruptions this incident may have caused your teams. If you were impacted and require additional details for internal post-incident reviews, please reach out to your Atlassian support representative with affected timeframes and tenant identifiers so we can correlate logs and provide guidance.\n\nThanks,\n\nAtlassian Customer Support", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-21T05:24:27.089Z", "resolved_inferred": false, "started_at": "2025-10-20T07:56:11.485Z", diff --git a/api/v/atlassian-support.json b/api/v/atlassian-support.json index 2419166cc4ae95910cfb8f669b610ec01bda303e..6092e809817765a7d229f4ead0a1e957a9a50623 100644 --- a/api/v/atlassian-support.json +++ b/api/v/atlassian-support.json @@ -3,7 +3,7 @@ "slug": "atlassian-support", "platform": "statuspage", "status_url": "https://support.status.atlassian.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "### Summary\n\nOn May 14, 2026, between 04:30 and 05:26 UTC, Atlassian customers experienced widespread service disruption across multiple Atlassian Cloud products. The issue was caused by a race condition in our internal deployment orchestration platform during a routine rollback operation of a core identity service in the us-east region. This race condition resulted in insufficient capacity for the identity service in the affected region which started returning errors to dependent products. The incident was detected within a minute by automated monitoring systems and mitigated in 56 minutes.\n\n### **IMPACT**\n\nDuring the incident, customers attempting to access Atlassian Cloud products in the us-east region experienced authentication and permission failures and were unable to access services. Customers also experienced errors when accessing the support portal until Atlassian fell back to an alternate support method. This was caused by a core identity service in the us-east region becoming unavailable. Affected products included Atlassian Administration, Atlassian Analytics, Bitbucket, Compass, Confluence, Jira, Jira Product Discovery, Jira Service Management and Trello. Some users outside us-east may have been affected in certain scenarios.\n\n### **ROOT CAUSE**\n\nThe incident was caused by a race condition in our internal deployment orchestration platform during a routine rollback operation of a core identity service in the us-east region. This race condition resulted in insufficient capacity for the identity service in the affected region which started returning errors to dependent products.\n\n### **REMEDIAL ACTIONS PLAN & NEXT STEPS**\n\nWe know that outages impact your productivity. Atlassian is prioritizing the following actions to help prevent similar incidents in future:\n\n* **Refine deployment orchestration safeguards**\n\n * Harden our deployment platform to prevent similar race conditions or resulting capacity loss during a rollback operation.\n * Streamline mitigation steps when a service becomes unavailable in a region.\n \n* **Reduce cross-region impact**\n\n * Improve regional isolation and fallback handling so an issue affecting a single region is less likely to impact customers or product functionality in other regions.\n \n\nWe recognise how critical reliable access to Atlassian products is for our customers' productivity, and we apologize to customers who were impacted by this incident.\n\nThanks,\n\nAtlassian", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-14T06:48:27.570Z", "resolved_inferred": false, "started_at": "2026-05-14T05:03:32.221Z", @@ -25,7 +25,7 @@ "body": "All dates and times below are in UTC unless stated otherwise.\n\n### Summary\n\nOn May 8, 2026 between 00:22 and 06:08, one of our hosting providers suffered a significant incident in a specific availability zone in prod-east which led to Atlassian customers experiencing degraded performance and delays of background operations and automation execution.\n\nThe incident started on May 8, 2026 at 00:22 and was detected within 4 minutes by automated monitoring systems. Our teams worked to restore core access by 06:08. Final cleanup of backlogged processes and minor issues progressed in stages from there was completed iteratively by 19:15.\n\n### **IMPACT**\n\nThe primary infrastructure affected in this incident was the event processing pipeline in the prod-east region, which distributes events between Atlassian services and underpins background operations such as automation execution, search indexing, notifications, permission synchronisation.\n\n* Between 00:22 and 06:08, an infrastructure incident in our hosting provider triggered an ingestion failure in our event processing pipeline.\n* At 02:50, event ingestion was failed over to an unaffected availability zone, progressively restoring live event flows.\n* At 06:08, reliability for new ingestion in prod-east recovered to 100%. The remaining work was to drain the accumulated cross-region backlog of messages, which completed by 17:00.\n* By 18:48, Automation had processed their backlog of events that were created while processing\n\n**Automation**\n\nBetween 00:22 and 02:50, customers with automation rules triggered by events originating from the prod-east region experienced a significant reduction in rule executions. During this window, event-triggered automation rules were not firing because the events that trigger them were not being delivered. Rule authoring, saving, and rules triggered manually, by schedules, or by webhooks were not affected.\n\nAt 02:50, the event processing infrastructure failed over to an unaffected availability zone, restoring delivery of live events to Automation and allowing new event-triggered rules to begin executing normally. However, events generated during the impact window still needed to be replayed before delayed automations could be processed.\n\nBeginning at 08:28, upstream services replayed their queued events in a coordinated sequence, and all replayed events were processed by 18:48. During the replay window, customers may have experienced automation rules executing later than expected, a small number of rules reaching daily processing limits due to compressed replay, and time-sensitive rules not completing as expected if internal timeout thresholds were exceeded.\n\n**Jira and Jira Service Management**\n\nBetween 00:22 and 02:50, customers with tenants hosted in the prod-east region experienced disruption to Jira and Jira Service Management event-driven features like automation, along with a short period of elevated errors during infrastructure failover. Core Jira experiences, including issue view, boards, and project navigation, remained available throughout the incident.\n\nJira event delivery was affected by the primary impact, preventing downstream services from receiving issue lifecycle events. This affected automation rules triggered by Jira events, AI agent orchestration in Jira, notifications for issue updates and transitions, search indexing for newly created or modified issues, and event-driven integrations between Jira and other Atlassian products.\n\nAt 02:50, the event processing infrastructure failed over to an unaffected availability zone, restoring delivery of new events. All events generated during the impact window were retained in a recovery queue and required replaying. This began at 08:28 and completed at 12:00. During the replay window, customers may have experienced automation rules executing later than expected, delayed notifications arriving hours after the triggering action, temporary gaps in search results for content created or modified during the impact window, and AI agent workflows not completing as expected where internal timeout thresholds were exceeded.\n\n**Confluence**\n\nBetween 00:22 and 02:50, customers with tenants hosted in the prod-east region experienced disruptions to event-driven services in Confluence. This resulted in delays to search indexing, notifications, automation rule execution, and permission synchronisation.\n\nThe underlying event processing infrastructure failed over to an unaffected availability zone, after which live Confluence operations resumed normally. However, events generated during the impact window were queued for replay, and some background services remained delayed until that replay and related validation work completed.\n\nBetween 10:14 and 17:00, a bulk replay of all the queued tenant replay tasks was completed to restore data consistency. During and immediately after the replay window, customers may have experienced search results not reflecting content created or modified during the outage, delayed or missing notifications for page and comment activity, automation rules firing later than expected, and brief delays in permission synchronisation for tenants relying on incremental identity sync.\n\n**Bitbucket and Pipelines**\n\nBetween 00:22 and 06:08, customers using Bitbucket and Pipelines experienced failures and degraded functionality across event-driven workflows. Core Git operations, including push, pull, and clone, were not affected and continued to operate normally throughout the incident.\n\nAutomatic pipeline triggers initiated by push or pull request events were unavailable during the impact window. Merge queues, custom merge checks, Forge-based triggers, workspace permission changes, and some workspace provisioning flows were also affected. Customers using merge queues were unable to merge pull requests, and some pipeline steps failed because queued work contributed to elevated concurrency limits.\n\nAt approximately 03:57, Pipelines was reconfigured to consume events through an alternative path, restoring automatic pipeline triggering. Merge queues, custom merge checks, Forge triggers, and other affected workflows were progressively restored as the underlying event processing infrastructure recovered. All Bitbucket and Pipelines services were confirmed fully operational by 06:08. After recovery, queued events were reviewed and replayed where safe to restore data consistency for billing, audit logging, and other background processes.\n\n**Identity Services**\n\nBetween 00:22 and 02:50, customers with tenants hosted in the prod-east region experienced delays in the propagation of identity and group membership changes to downstream Atlassian products. Core identity operations, including authentication, login, and direct group management actions, were not affected and continued to function normally throughout the incident.\n\nThe impact was limited to asynchronous, event-driven operations that depend on the event processing pipeline. This included delays in delivering group membership and user profile changes to products such as Jira and Confluence, which affected downstream permission synchronisation and crowd sync flows. A small number of SCIM-based identity synchronisation and site provisioning workflows also experienced temporary delays.\n\nAfter the event processing infrastructure recovered, backed-up identity and group directory events were replayed where required, restoring downstream consistency for affected products. No identity data was lost. Group membership changes, user profile updates, and provisioning-related events that occurred during the impact window were retained and processed after recovery.\n\n### **REMEDIAL ACTIONS PLAN & NEXT STEPS**\n\nWe know outages impact your productivity. While our monitoring and recovery processes helped us respond quickly, this incident highlighted opportunities to further strengthen resilience for event-driven services.\n\nWe are prioritizing improvements that will:\n\n* **Enhance failover coverage** so critical event processing can recover more smoothly during infrastructure disruptions.\n* **Strengthen recovery handling** so replayed events can be processed more quickly.\n\nWe apologize to customers whose services were impacted during this incident; we are taking immediate steps to improve the platform\u2019s performance and availability.\n\nThanks,\n\nAtlassian Customer Support", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-08T02:02:13.089Z", "resolved_inferred": false, "started_at": "2026-05-08T01:31:38.263Z", @@ -38,7 +38,7 @@ "body": "### SUMMARY\n\n### \n\nBetween May 1, 2026 at 23:34 UTC and May 2, 2026 at 02:53 UTC Atlassian customers using Jira and Jira Service Management (JSM) across all Cloud tenants received an error page when attempting to open a work item due to a schema incompatibility, and editing work item fields was degraded for both products. Navigating to and interacting with boards were degraded for Jira specifically. On Jira mobile, users were unable to view work items and work item search was degraded. This was caused by a deployment of a schema configuration change that had only been validated against some production environments.\n\n \n\nThe issue also affected Atlassian's customer support operations and temporarily impacted Atlassian\u2019s ability to respond to incoming support requests. Customers were able to raise tickets as usual.\n\n \n\nAtlassian\u2019s automated monitoring systems detected the issue on May 1, 2026 at 23:41 UTC, and engineering teams promptly began investigating.\n\n \n\nThe issue was reported on Statuspage on May 2, 2026 at 00:55 UTC.\n\n \n\nThe issue was resolved after 3 hours and 19 minutes on May 2, 2026 at 02:53 UTC when the previous version of the schema configuration was successfully redeployed to all regions.\n\n \n\n### IMPACT\n\n### \n\n- **Duration**: 3 hours 19 minutes (May 1, 2026 at 23:34 UTC \u2013 May 2, 2026 at 02:53 UTC)\n- **Affected regions**: All regions.\n- **Affected products**: Jira, JSM, Jira Mobile\n- **Customer experience**:\n- Users were unable to view work items using the work item view; consequently updating and creating work items from the work item view was affected.\n- Editing work items was degraded.\n- Boards did not show under Spaces in the Jira navigation.\n- Certain board interactions were affected.\n- Other areas of Jira not dependent on the broken schema configuration continued to operate normally.\n\n### \n\n### ROOT CAUSE\n\n### \n\nThe root cause was a deployment sequencing issue. A schema configuration change was deployed to the API gateway layer before the corresponding application-level change had been deployed across all production environments. This created a mismatch between the schema expected by the gateway and the schema served by the application servers.\n\n### \n\n### MITIGATIONS\n\n### \n\nThe engineering team identified the problematic schema change and initiated a rollback of the deployment. A deployment blocker was put in place to prevent further changes while the rollback was executed. The previous version of the schema configuration was redeployed, and service was restored across all regions.\n\n### \n\n### REMEDIAL ACTION PLAN & NEXT STEPS\n\n### \n\nWe understand that service disruptions impact your productivity. In addition to our existing testing and preventative processes, Atlassian is prioritizing the following actions to help reduce the likelihood and impact of similar incidents in the future and to speed up recovery when issues occur:\n\n- We are adding automated pre-deployment checks to verify that schema configurations are compatible across all production environments before changes are deployed.\n- We will streamline our incident communication processes, incident response training and tooling to reduce the time between incident detection and customer notification.\n- We are working to improve resilience of critical customer-facing support services to ensure SLA continuity during outages.\n\nWe apologize to customers whose services were impacted during this incident. We are taking immediate steps to reduce the risk and impact of similar issues in future.\n\n \n\nThanks,\n\nAtlassian", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-02T02:47:55.357Z", "resolved_inferred": false, "started_at": "2026-05-02T01:38:27.814Z", @@ -51,7 +51,7 @@ "body": "### Summary\n\nOn April 13, 2026, between 05:49 and 06:29 UTC, customers experienced failures when attempting to log in, sign up, reset passwords, and complete multi-factor authentication flows across Atlassian cloud products. Approximately 90% of authentication requests failed during the peak impact window, affecting users in the US East and EU regions. The incident was mitigated within 40 minutes through manual intervention, and full service was restored by 06:29 UTC.\n\n### **IMPACT**\n\n* **Duration**: ~40 minutes \\(05:49\u201306:29 UTC, April 13, 2026\\)\n* **Affected regions**: US East and EU \\(authentication infrastructure serves EU traffic from US East, with traffic primarily from EU at this time of day\\).\n* **Affected products**: All Atlassian cloud products requiring authentication, including Jira, Confluence, Jira Service Management, and Trello.\n* **Customer experience**: Users attempting to log in, sign up, reset passwords, or complete MFA flows received errors. Users already logged in with active sessions were unaffected.\n\n### **ROOT CAUSE**\n\nThis incident had several contributing factors that combined to produce a failure that the system could not recover from without manual intervention.\n\n**The primary cause** was a recently enabled change that caused our authentication infrastructure to retry requests to a downstream identity service when those requests were slow to respond. This retry behaviour was rolled out to 100% of traffic earlier the same day. Under normal conditions this would be benign, but it meant that any slowness in the downstream service was amplified. Since multiple upstream services were also independently retrying their own failed requests, the amplification compounded further into a retry storm.\n\n**The trigger** was a burst of legitimate user traffic. A pattern of many parallel link preview requests for a single user caused a concentrated load spike on a downstream identity service, pushing its response times above the retry threshold. On its own, this kind of spike had occurred many times before and always recovered. With the retry amplification now in effect, the spike instead created a runaway feedback loop: slow responses caused retries, retries increased load, increased load caused slower responses, preventing recovery.\n\nThe incident was mitigated by manually scaling up the downstream identity service to provide sufficient capacity to absorb the amplified load. Once scaled, the service recovered immediately, bringing authentication error rates to zero within one minute.\n\n**REMEDIAL ACTIONS PLAN & NEXT STEPS**\n\nWe are taking the following actions designed to prevent recurrence and improve our resilience:\n\n1. **Immediate**: The retry-on-timeout change has been disabled.\n2. **Load shedding and self-healing**: We are adding load shedding capabilities to our authentication services so that they can automatically shed excess load and self-recover during traffic spikes, without requiring action before automatic scaling starts.\n3. **Reducing request fan-out**: We are reviewing patterns where a single user action can generate many parallel downstream requests, and will introduce methods where possible to reduce the amplification potential.\n\nWe apologize to customers whose services were interrupted by this incident and we are taking immediate steps to improve the platform\u2019s reliability.\n\nThanks,\n\nAtlassian Customer Support", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-13T10:17:20.727Z", "resolved_inferred": false, "started_at": "2026-04-13T07:29:45.882Z", @@ -64,7 +64,7 @@ "body": "Our team has been able to successfully recover all services from confluence.atlassian.com and ja.confluence.atlassian.com and these sites are now performing as expected. This incident is now resolved.\nWe apologize for any inconvenience that this issue may have caused.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-02T02:39:51.742Z", "resolved_inferred": false, "started_at": "2026-04-02T01:49:20.929Z", @@ -77,7 +77,7 @@ "body": "Team has reconfirmed everything is working as expected. This issue is resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-17T14:43:58.021Z", "resolved_inferred": false, "started_at": "2025-12-17T13:48:38.385Z", @@ -90,7 +90,7 @@ "body": "The feature flag causing the issue has been reverted, fixing the problem. With that this incident is resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-05T12:09:05.412Z", "resolved_inferred": false, "started_at": "2025-12-05T08:08:52.709Z", @@ -103,7 +103,7 @@ "body": "The issue has been resolved and there is no performance related slowness on Atlassian Community Forums now.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-10T04:17:13.505Z", "resolved_inferred": false, "started_at": "2025-11-06T19:36:32.503Z", @@ -116,7 +116,7 @@ "body": "### Postmortem publish date: Nov 19th, 2025\n\n### Summary\n\nAll dates and times below are in UTC unless stated otherwise.\n\nCustomers utilizing Atlassian products experienced elevated error rates and degraded performance between Oct 20, 2025 06:48 and Oct 21, 2025 04:05. The service disruptions were triggered due to an [AWS DynamoDB outage](https://aws.amazon.com/message/101925/#:~:text=1%3A50%20PM.-,DynamoDB,-Between%2011%3A48) and further affected by subsequent failures in [AWS EC2](https://aws.amazon.com/message/101925/#:~:text=service%20disruption%20event.-,Amazon%20EC2,-Between%2011%3A48) and [AWS Network Load Balancer](https://aws.amazon.com/message/101925/#:~:text=service%20disruption%20event.-,Amazon%20EC2,-Between%2011%3A48) within the us-east-1 region.\n\nThe incident started at Oct 20, 2025 06:48 and was detected within six minutes by our automated monitoring systems. Our teams worked to restore all core services by Oct 21, 2025 04:05. Final cleanup of backlogged processes and minor issues was completed on Oct 22, 2025.\n\nWe recognize the critical role our products play in your daily operations, and we offer our sincere apologies for any impact this incident had on your teams. We are taking immediate steps to enhance the reliability and performance of our services, so that you continue to receive the standard of service you have come to trust.\n\n### IMPACT\n\nBefore examining product-level impacts, it's helpful to understand Atlassian's service topology and internal dependencies.\n\nProducts such as Jira and Confluence are deployed across multiple AWS regions. The data for each tenant is stored and processed exclusively within its designated host region. This design is intentional and represents the desired operational state, as it limits the impact of any regional outage strictly to tenants in-region, in this case us-east-1.\n\nWhile in-scope application data is pinned to the region selected by the customer, there are times when systems need to call other internal services that may be based in a different region. If a problem occurs in the main region where these services operate, systems are designed to automatically fail over to a backup region, usually within three minutes.\n\nHowever, if unexpected issues arise during this failover, it can take longer to restore services. In rare cases, this could affect customers in more than one region. It\u2019s important to note that all in-scope application data for supported products is pinned according to a customer\u2019s chosen region.\n\n**Jira**\n\nBetween Oct 20, 2025 06:48 and Oct 20, 2025 20:00, customers with tenants hosted in the us-east-1 region experienced increased error rates when accessing core entities such as Issues, Boards, and Backlogs. This disruption was caused by AWS's inability to allocate AWS EC2 instances and elevated errors in AWS Network Load Balancer \\(NLB\\). During this window, users may also have observed intermittent timeouts, slow page loads, and failures when performing operations like creating or updating issues, loading board views, and executing workflow transitions.\n\nBetween Oct 20, 2025 08:36 and Oct 20, 2025 09:23, customers across all regions experienced elevated failure rates when attempting to load Jira pages. This disruption was caused by the regional frontend service entering an unhealthy state during this specific time interval.\n\nNormally, the frontend service connects to the primary AWS DynamoDB instance located in the us-east-1 to retrieve the most recent configuration data necessary for proper operation. Additionally, the service is designed with a fallback mechanism that references static configuration data in the event that the primary database becomes inaccessible. Unfortunately, a latent bug existed in the local fallback path. When the frontend service nodes restarted, they were unable to load critical operational configuration data from primary or fallback sources, leading to the observed failures experienced by customers.\n\nBetween Oct 20, 2025 06:48 and Oct 21, 2025 06:30, customers experienced significant delays and missing Jira in-app notifications across all regions. The notification ingestion service, which is hosted exclusively in us-east-1, exhibited an increased failure rate when processing notification messages due to AWS EC2 and NLB issues. This issue resulted in notifications being delayed - and in some cases, not delivered at all - to users worldwide.\n\n**Jira Service Management \\(JSM\\)**\n\nJSM was impacted similarly to Jira above, with the same timeframes and for the same reasons.\n\nBetween Oct 20, 2025 08:36 and Oct 20, 2025 09:23, customers across all regions experienced significantly elevated failure rates when attempting to load JSM pages. This affected all JSM experiences including the Help Centre, Portal, Queues, Work Items, Operations, and Alerts.\n\n**Confluence**\n\nBetween Oct 20, 2025 06:48 and Oct 21, 2025 02:45, customers using Confluence in the us-east-1 region experienced elevated failure rates when performing common operations such as editing pages or adding comments. The primary cause of this service degradation was the system's inability to auto-scale due to AWS EC2 issues to manage peak traffic load effectively.\n\nThough the AWS outage ended at Oct 20, 21:09, a subset of customers continued to experience failures as some Confluence web server nodes across multiple clusters remained in an unhealthy state. This was ultimately mitigated by recycling the affected nodes.\n\nTo protect our systems while AWS recovered, we made a deliberate decision to enable node termination protection. This action successfully preserved our server capacity but, as a trade-off, it extended the time required for a full recovery once AWS services were restored.\n\n**Automation**\n\nBetween Oct 20, 2025 06:55 and Oct 20, 2025 23:59, automation customers whose rules are processed in us-east-1 experienced delays of up to 23 hours in rule execution.\n\nDuring this window, some events triggering rule executions were processed out of order because they arrived later during backlog processing. This caused potential inconsistencies in workflow executions, as rules were run in the order events were received, not when the action causing the event occurred. Additionally, some rule actions failed because they depend on first-party and third-party systems, which were also affected by the AWS outage. Customers can see most of these failures in their audit logs; however, a few updates were not logged due to the nature of the outage.\n\nBy Oct 21, 2025 5:30, the backlog of rule runs in us-east-1 was cleared. Although most of these delayed rules were successfully handled, there were some additional replays of events to ensure completeness. Our investigation confirmed that a few events may never have triggered their associated rules due to the outage.\n\nBetween Oct 20, 2025 06:55 and Oct 20, 2025 11:20, all non-us-east-1 regional automation services experienced delays of up to 4 hours in rule execution. This was caused by an upstream service that was unable to deliver events as expected. The delivery service encountered a failure due to a cross-region dependency call to a service hosted in the us-east-1 region. Because of this dependency issue, the delivery service was unable to successfully deliver events throughout this time frame, resulting in customer-defined rules not being executed in a timely manner.\n\n**Bitbucket and Pipelines**\n\nBetween Oct 20, 2025 06:48 and Oct 20, 2025 09:33, Bitbucket experienced intermittent unavailability across core services. During this period, users faced increased error rates and latency when signing in, navigating repositories, and performing essential actions such as creating, updating, or approving pull requests. The primary cause was an AWS DynamoDB outage that impacted downstream services.\n\nBetween Oct 20, 2025 06:48 and Oct 20, 2025 22:46, numerous Bitbucket Pipeline steps failed to start, stalled mid-execution, or experienced significant queueing delays. Impact varied, with partial recoveries followed by degradation as downstream components re-synchronized. The primary cause was an AWS DynamoDB outage, compounded by instability in AWS EC2 instance availability and AWS Network Load Balancers.\n\nFurthermore, Bitbucket Pipelines continued to experience a low but persistent rate of step timeouts and scheduling errors due to AWS bare-metal capacity shortages in select availability zones. Atlassian coordinated with AWS to provision additional bare-metal hosts and addressed a significant backlog of pending pods, successfully restoring services by 01:30 on Oct 21, 2025.\n\n**Trello**\n\nBetween Oct 20, 2025 06:48 and Oct 20, 2025 15:25, users of Trello experienced widespread service degradation and intermittent failures due to upstream AWS issues affecting multiple components, including AWS DynamoDB and subsequent AWS EC2 capacity constraints. During this period, customers reported elevated error rates when loading boards, opening cards, adding comments or attachments.\n\n**Login**\n\nBetween Oct 20, 2025 06:48 and Oct 20, 2025 09:30, a small subset of users experienced failures when attempting to initiate new login sessions using SAML tokens. This resulted in an inability for those users to access Atlassian products during that time period. However, users who already had valid active sessions were not affected by this issue and continued to have uninterrupted access.\n\nThe issue impacted all regions globally because regional identity services relied on a write replica located in the us-east-1 region to synchronize profile data. When the primary region became unavailable, the failover to a secondary database in another region failed, which delayed recovery. This failover defect has since been addressed.\n\n**Statuspage**\n\nBetween Oct 20, 2025 06:48 and Oct 20, 2025 09:30, Statuspage customers who were not already logged in to the management portal were unable to log in to create or update incident statuses. This impact was restricted only to users who were not already logged in at the time. The root cause was the same as described in the Login section above, and it was resolved by the same remediation steps.\n\n### REMEDIAL ACTION PLAN & NEXT STEPS\n\nWe have completed the following critical actions designed to help prevent cross-region impact from similar issues:\n\n* Resolved the code defect in the fallback option to ensure that Jira Frontend Services in other regions remain unaffected during a region-wide outage.\n* Fixed the issue that prevented timely failover of the identity service which impacted new login sessions.\n* Resolved the code defect so that delivery services in unaffected regions remain operational during region-wide outages.\n\nAdditionally, we are prioritizing the following improvement actions:\n\n* Implement mitigation strategies to strengthen resilience against region-wide outages in the notification ingestion service.\n\nAlthough disruptions to our cloud services are sometimes unavoidable during outages of the underlying cloud provider, we continuously evaluate and improve test coverage to strengthen resilience of our cloud services against these issues.\n\nWe recognize the critical importance of our products to your daily operations and overall productivity, and we extend our sincere apologies for any disruptions this incident may have caused your teams. If you were impacted and require additional details for internal post-incident reviews, please reach out to your Atlassian support representative with affected timeframes and tenant identifiers so we can correlate logs and provide guidance.\n\nThanks,\n\nAtlassian Customer Support", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-21T05:24:27.129Z", "resolved_inferred": false, "started_at": "2025-10-20T07:56:12.455Z", @@ -129,7 +129,7 @@ "body": "We have resolved the incident. A new version of the Loom chrome extension has been approved and published to the Chrome Extension store. Update to the latest version(v5.5.142) of the extension.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-09T20:00:15.226Z", "resolved_inferred": false, "started_at": "2025-10-08T22:20:37.356Z", @@ -142,7 +142,7 @@ "body": "We are closing this incident on Statuspage as the Atlassian Support portal functionality has been restored. \n\nWe are aware that the ticket attachments panel remains unavailable and that some customers may be receiving a 'Something went wrong!' error message despite successfully uploading ticket attachments. We are working to resolve these UX issues. Atlassian Support is available for customers needing further assistance.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-08T02:18:18.900Z", "resolved_inferred": false, "started_at": "2025-10-06T01:10:49.669Z", diff --git a/api/v/atlassian.json b/api/v/atlassian.json index bdf3aa32b4f1704417be8be3f3a66e7feffe5fc3..b7282856f6a6f459e8c18bf738861e673d775bec 100644 --- a/api/v/atlassian.json +++ b/api/v/atlassian.json @@ -3,7 +3,7 @@ "slug": "atlassian", "platform": "statuspage", "status_url": "https://status.atlassian.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", diff --git a/api/v/authentic8.json b/api/v/authentic8.json index b386331df431fc4d1db496bb0331d3ff1873c594..1ef877d521b82f7987d6e7e1bf244b6538dea92f 100644 --- a/api/v/authentic8.json +++ b/api/v/authentic8.json @@ -3,7 +3,7 @@ "slug": "authentic8", "platform": "status.io", "status_url": "https://status.authentic8.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": false, "first_watched": "2026-09-04T07:06:16Z", diff --git a/api/v/auvik.json b/api/v/auvik.json index 5e22d02aae997ddb212183da8ec372fd41093f8f..ce5f76d064dd5bf712a2676942f70499718f6ed8 100644 --- a/api/v/auvik.json +++ b/api/v/auvik.json @@ -3,7 +3,7 @@ "slug": "auvik", "platform": "statuspage", "status_url": "https://status.auvik.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "The incident has been fully resolved, and all services are operating normally.\n\nCustomers should no longer experience any related issues. If you continue to experience problems, please don't hesitate to contact Auvik Support.\n\nWe will provide a Root Cause Analysis (RCA) once it is available.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-09-03T08:18:52.526-04:00", "resolved_inferred": false, "started_at": "2026-09-03T07:12:53.072-04:00", @@ -25,7 +25,7 @@ "body": "# Service Disruption - Availability Issues on the AU1 Cluster\n\n## Root Cause Analysis\n\n### Duration of the incident\n\nDiscovered: Aug 27, 2026 12:20 - UTC \nResolved: Aug 27, 2026 13:15 - UTC\n\n### Customer impact\n\nClients hosted in the AU1 region experienced a temporary interruption of Auvik services. Depending on the client, monitoring, alerting, collector connectivity, and access to the web interface were unavailable for up to approximately one hour.\n\n### Cause\n\nA cascading failure in core platform services caused multiple service components to restart, including a central coordination component. This resulted in widespread client-environment restarts across the AU1 region.\n\n### Effect\n\nAffected client environments became temporarily unavailable while services restarted. The platform recovered automatically. Post-recovery verification confirmed normal service operation.\n\n### Future consideration\\(s\\)\n\n* Continue evaluating resiliency improvements for core service coordination and recovery behavior following large-scale restarts.\n* Continue using post-recovery validation checks to confirm client services return to expected operation after a broad service restart.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-27T09:30:25.575-04:00", "resolved_inferred": false, "started_at": "2026-08-27T08:46:10.771-04:00", @@ -38,7 +38,7 @@ "body": "# Service Degradation - Legacy Alerts Notification\n\n## Root Cause Analysis\n\n### Duration of the incident\n\nDiscovered: Aug 17, 2026 13:15 - UTC \nResolved: Aug 21, 2026 14:12 - UTC\n\n### Customer impact\n\nSome customers using Legacy Alerts experienced inaccurate alert notifications, including false-positive alerts and unintended email notifications. During remediation, some legacy alert processing was delayed, and alert visibility in the user interface temporarily lagged. V2 Alerts remained operational throughout the incident.\n\n### Cause\n\nA product release intended to retire older default Legacy Alert configurations for new environments also removed supporting alert conditions that were still required by some existing customers with customized Legacy Alerts. Without the complete conditions, certain Legacy Alerts could trigger inaccurately. The remediation required reprocessing affected alerts, which temporarily increased processing load and contributed to delayed alert visibility, alert flapping, and excessive notifications.\n\n### Effect\n\nAffected Legacy Alerts could trigger when the underlying condition was not present, re-trigger after being paused, or send notifications more broadly than intended. The resulting in-service lag also temporarily delayed displaying some alerts. Engineering restored the required alert configuration, removed the unintended broad email association, increased processing capacity, and proactively corrected additional affected customer environments.\n\n### Future consideration\\(s\\)\n\n\u2022 Add monitoring for abnormal volumes of Legacy Alerts so unexpected alert activity can be detected earlier.\n\n\u2022 Expand pre-release and end-to-end testing for existing customized Legacy Alerts, including alert triggering, notification delivery, and post-change recovery behavior.\n\n\u2022 Strengthen canary-release review so alerting anomalies are investigated and understood before wider deployment.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-20T10:11:24.839-04:00", "resolved_inferred": false, "started_at": "2026-08-17T13:53:50.634-04:00", @@ -51,7 +51,7 @@ "body": "The incident has been fully resolved, and all services are operating normally.\n\nCustomers should no longer experience any related issues. If you continue to experience problems, please don't hesitate to contact Auvik Support.\n\nWe will provide a Root Cause Analysis (RCA) once it is available.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-17T12:42:43.026-04:00", "resolved_inferred": false, "started_at": "2026-08-17T11:00:40.735-04:00", @@ -64,7 +64,7 @@ "body": "# Service Disruption - SNMPv3 Monitoring Loss Following Collector Upgrade\n\n## Root Cause Analysis\n\n### Duration of the incident\n\nDiscovered: Apr 13, 2026 20:00 - UTC \nResolved: Apr 13, 2026 22:32 - UTC\n\n### Customer impact\n\nCustomers experienced a loss of monitoring data from only devices using specific SNMPv3 configurations. While devices remained online and reachable, monitoring data was not collected, resulting in reduced visibility across environments.\n\n### Cause\n\nA recent collector upgrade introduced changes to encryption handling that affected support for certain legacy SNMPv3 configurations. This resulted in failures when attempting to collect data from devices configured that way.\n\n### Effect\n\nMonitoring data collection failed for affected devices across multiple clusters. This led to a noticeable drop in available device metrics and visibility, despite no loss of connectivity to the devices themselves.\n\n### Future consideation\\(s\\)\n\n* Expand test coverage to include a broader range of SNMP configurations\n* Improve monitoring to detect drops in data collection more proactively\n* Strengthen validation processes for major upgrades and dependency changes\n* Implement additional safeguards to identify compatibility issues prior to release", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-13T22:33:40.666-04:00", "resolved_inferred": false, "started_at": "2026-04-13T20:32:11.502-04:00", @@ -77,7 +77,7 @@ "body": "# Service Degraded - Some Customers Experiencing Login Issues After Maintenance\n\n## Root Cause Analysis\n\n### Duration of the incident\n\nDiscovered: Mar 7, 2026 18:42 - UTC \nResolved: Mar 9, 2026 21:10 - UTC\n\n### Cause\n\nFollowing a platform upgrade, an internal reconciliation process incorrectly identified a subset of user records as deleted. This occurred due to an error condition in a synchronization component that failed to process all expected user data during reconciliation.\n\n### Effect\n\nAffected users were able to log in to the platform but were unable to access their expected sites or tenants due to missing user authorizations. In some cases, API access using previously generated API keys was also affected.\n\nMonitoring, alerting, and data collection services continued to function normally throughout the incident.\n\n### Action taken\n\nEngineering paused the process that spreads the changes across the platform to prevent further impact.\n\nUser access was then restored using backup data taken prior to the upgrade. This allowed the team to recover user access, permissions, and related access keys.\n\nAfter restoration was completed and access was verified across all environments, the incident was declared resolved.\n\n### Future consideration\\(s\\)\n\n* Implement additional monitoring to detect unexpected changes in user or authorization records.\n* Add safeguards within reconciliation processes to prevent large-scale unintended deletions.\n* Improve post-upgrade validation checks to identify abnormal record changes earlier.\n* Enhance disaster recovery tooling and backup retrieval processes to speed up restoration efforts.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-09T17:26:06.121-04:00", "resolved_inferred": false, "started_at": "2026-03-08T15:10:43.417-04:00", @@ -90,7 +90,7 @@ "body": "# Service Disruption - The EU2 cluster was unavailable \n\n## Root Cause Analysis\n\n### Duration of the incident\n\nDiscovered: Dec 15, 2025 20:00 \u2013 UTC \nResolved: Dec 16, 2025 02:00 \u2013 UTC\n\n### Customer impact\n\nDuring the incident window, customers hosted in the EU2 region experienced intermittent service degradation. This included slower system responsiveness, temporary inconsistencies in monitoring data, and brief periods where alerts may have been delayed or inaccurate. \nMost customers regained access as services were progressively restored, and complete stability was confirmed before the incident was closed.\n\n### Cause\n\nThe incident was caused by an elevated load in the EU2 service environment, resulting in an uneven workload distribution across backend resources. As the load increased, automated recovery mechanisms were unable to stabilize the environment fully, necessitating a controlled restart of the regional service to restore normal operations.\n\n### Effect\n\nThe imbalance led to reduced service performance and temporary unavailability for some customers until recovery actions were completed. Engineering teams were required to intervene to safely restart the affected region and validate service health before returning operations to normal.\n\n### Future consideation\\(s\\)\n\n* Improve automated workload balancing to absorb regional load increases.\n* Strengthen early indicators for backend saturation to enable earlier intervention.\n* Refine operational procedures to further reduce recovery time in similar scenarios.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-15T20:57:36.921-05:00", "resolved_inferred": false, "started_at": "2025-12-15T18:28:18.629-05:00", @@ -103,7 +103,7 @@ "body": "# Service Degraded - Duplicated Devices for Meraki Switch Stacks\n\n## Root Cause Analysis\n\n### Duration of the incident\n\nDiscovered: Dec 15, 2025 08:34 \u2013 UTC \nResolved: Dec 15, 2025 13:20 \u2013 UTC\n\n### Customer impact\n\nCustomers with Meraki switch stacks across all clusters experienced: \nDuplicate Meraki switches are appearing in the device inventory, including entries without management IP addresses. \nInability to manually delete duplicates, as they were automatically recreated. \nConfusing or inaccurate device and stack representations. \nTemporary inflation of billable device counts for some tenants \\(billing data captured and under review\\). \nNo other device types were affected.\n\n### Cause\n\nA configuration update intended to improve how Meraki switch stacks are represented in the platform caused unintended behavior. \nFor tenants already using Meraki stacking, the system was unable to match newly processed stack data to existing switches consistently. This caused already-stacked switches to be incorrectly interpreted as new devices, generating duplicate inventory entries. Because the underlying synchronization logic reinforced these entries, any customer deletion of duplicates did not persist, and duplicates reappeared.\n\n### Effect\n\nThe issue led to inaccurate device inventories and misleading switch-stack views for customers using Meraki stacking, causing confusion in device management and increasing support tickets. Internal teams experienced additional operational overhead as they investigated the duplication patterns and validated safe removal procedures. Complete remediation required coordinated cleanup across all clusters to restore accurate device records and ensure no further duplicates were generated.\n\n### Future consideration\\(s\\)\n\n* Strengthen validation of device and stack metadata before inventory updates.\n* Improve testing coverage using a production-like stacked device configuration.\n* Add monitoring and alerting for abnormal changes in device counts.\n* Use safer rollout controls and feature flags for changes affecting device inventory logic.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-15T13:23:04.412-05:00", "resolved_inferred": false, "started_at": "2025-12-15T09:35:29.220-05:00", @@ -116,7 +116,7 @@ "body": "# Service Degraded - FortiGate firewalls duplicated in the EU2 cluster, causing a flood of alerts.\n\n## Root Cause Analysis\n\n### Duration of the incident\n\nDiscovered: Dec 11, 2025 14:00 \u2013 UTC \nResolved: Dec 17, 2025 06:45 \u2013 UTC\n\n### Customer impact\n\nClients with FortiGate firewalls in the EU2 region experienced:\n\n* A significant increase in \u201cdevice offline\u201d alerts due to status flapping between duplicate and original device entries.\n* Duplicate firewalls appear in inventory views, leading to confusion in device management.\n* Inaccurate device statistics and monitoring gaps.\n* In some cases, customers attempted to delete duplicates, which resulted in the loss of historical data on the original device.\n\nNo other device types or regions were affected.\n\n### Cause\n\nA system change intended to improve how high-availability firewall configurations were processed introduced unexpected behavior. Under certain conditions, the platform was unable to detect when multiple records referenced the same firewall device consistently. As a result, some firewalls were incorrectly detected as new devices, causing duplicate entries and inconsistent operational status reporting.\n\n### Effect\n\nThe issue resulted in elevated alert volumes across impacted tenants and caused instability in device-status reporting for the affected firewalls. Customers experienced increased operational overhead as they reviewed unexpected alerts and duplicate device entries, and engineering teams were required to intervene to restore accurate device associations and remove the duplicated records.fFuture consideration\\(s\\)\n\n* Strengthen validation of device-supplied information before it affects inventory or monitoring.\n* Implement alerting for sudden spikes in offline/online transitions to detect similar issues earlier.\n* Improve observability of device lifecycle behavior to identify anomalies proactively.\n* Use feature-flagged or staged rollouts for changes that affect device processing logic.\n* Incorporate production-like data into pre-deployment testing to better anticipate unexpected device behaviors.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-11T18:46:29.027-05:00", "resolved_inferred": false, "started_at": "2025-12-11T09:30:41.924-05:00", @@ -129,7 +129,7 @@ "body": "The incident has been fully resolved, and all services are operating normally.\n\nCustomers should no longer experience any related issues. If you continue to experience problems, please don't hesitate to contact Auvik Support.\n\nWe appreciate your understanding and patience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-05T08:32:57.269-05:00", "resolved_inferred": false, "started_at": "2025-12-05T07:50:30.000-05:00", @@ -142,7 +142,7 @@ "body": "Latest update from Okta\nIncident Resolved\n\nDecember 3, 2025 at 8:58am PST\n\nAn issue impacting the core authentication service for customers in Okta Cell US7 has been resolved. Additional root cause information will be available within five business days.\n\nWe will close the status page for Auvik's sites.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-03T12:28:00.389-05:00", "resolved_inferred": false, "started_at": "2025-12-03T09:21:09.865-05:00", @@ -155,7 +155,7 @@ "body": "# Service Degraded - Data Not Loading Across All Clusters\n\n## Root Cause Analysis\n\n### Duration of the incident\n\nDiscovered: Nov 21, 2025 17:43 \u2013 UTC \nResolved: Nov 21, 2025 19:18 \u2013 UTC\n\n### Customer impact\n\nCustomers across all regions were able to log in, but many were unable to view key data within the platform. This included features such as:\n\n* Network maps\n* Inventory and site lists\n* Dashboards\n* Other views are dependent on permissions and hierarchical data.\n\nThis resulted in degraded usability and limited visibility into managed environments.\n\n### Cause\n\nDuring a routine maintenance task intended to clean up older data records, an incorrect piece of information was unintentionally added to the system. This faulty data prevented a core component\u2014responsible for organizing how customer information is displayed in the platform\u2014from functioning correctly.\n\nBecause this component could not run as expected, many areas of the product that rely on structured data \\(such as maps, dashboards, and inventory views\\) were unable to load. This led to widespread service degradation across all clusters.\n\n### Effect\n\nBecause the system could not correctly load the information needed to display customer environments, several parts of the platform were unable to show data. As a result, many users could log in but were unable to see maps, inventory details, site lists, dashboards, or other information they usually rely on. \nThis created a degraded experience across all regions, limiting visibility and making it difficult for customers to perform routine monitoring and management tasks until the issue was resolved.\n\n### Future consideation\\(s\\)\n\n* Introduce stronger validation and safeguards to prevent malformed data from being accepted into critical systems.\n* Improve the resilience of backend services so they fail gracefully rather than entering repeated restart cycles.\n* Implement additional monitoring to provide earlier detection of issues affecting data-loading functions.\n* Enhance internal tools used during maintenance and cleanup activities to reduce the risk of unintentional data corruption.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-21T14:26:06.441-05:00", "resolved_inferred": false, "started_at": "2025-11-21T13:29:10.342-05:00", @@ -168,7 +168,7 @@ "body": "The incident has been fully resolved, and all services are operating normally.\n\nCustomers should no longer experience any related issues. If you continue to experience problems, please don't hesitate to contact Auvik Support.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-20T06:57:38.371-04:00", "resolved_inferred": false, "started_at": "2025-10-20T05:51:11.783-04:00", @@ -181,7 +181,7 @@ "body": "# Service Degraded - Sites have lost settings after maintenance\n\n## Root Cause Analysis\n\n### Duration of the incident\n\nDiscovered: Oct 11, 2025 \u2013 12:00 UTC \nResolved: Oct 15, 2025 \u2013 22:00 UTC\n\n### Cause\n\nDuring a scheduled system update, a background maintenance process unintentionally removed reference files used to identify stored site configurations. When affected systems restarted after the update, they were unable to locate those configuration files and temporarily appeared as new, empty sites.\n\nThis occurred because the maintenance process was using outdated information when determining which data to clean up safely. The underlying data remained securely stored, but the missing reference files prevented normal access until they were restored.\n\n### Effect\n\nA subset of tenants across multiple clusters temporarily lost access to their site configurations and appeared as newly created environments. \nCustomers observed missing data and configurations, including previously defined network settings and device details.\n\n### Action taken\n\n_All times are in UTC_\n\n**10/11/2025**\n\n**12:00** \u2013 A scheduled system upgrade began across all clusters.\n\n**15:25** \u2013 The support team received reports from customers that some sites appeared empty or missing data.\n\n**16:00** \u2013 Engineering immediately began investigating and determined this was not related to normal data processing delays.\n\n**10/12/2025**\n\nAdditional reports confirmed that several sites were missing configuration information. The engineering team confirmed that the original data was still securely stored, but was not being correctly loaded by the system.\n\n**10/13/2025**\n\nThe issue was traced to missing metadata files that help identify stored configurations. The engineering team began restoring affected sites using the most recent valid configuration data.\n\nAutomated recovery tools were developed to safely restore additional sites and ensure consistent recovery across all clusters.\n\n**10/14/2025**\n\nEngineering verified that configuration data was fully restored and synchronized across supporting services.\n\nThe recovery process was extended to all remaining sites, with validation steps confirming successful restoration.\n\n**10/15/2025**\n\nFinal recovery efforts for the remaining affected clusters were completed..\n\n**22:00** \u2013 All affected sites were confirmed operational with their configurations restored and verified.\n\n### Future consideration\\(s\\)\n\n* Remove dependency of cleanup processes on outdated cluster data sources.\n* Validate all automated cleanup jobs to ensure they do not operate on production clusters.\n* Implement monitoring for missing or corrupted metadata files before deployments.\n* Enhance post-deployment validation to verify the integrity of configuration data across all clusters.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-15T13:33:51.847-04:00", "resolved_inferred": false, "started_at": "2025-10-15T11:22:07.158-04:00", @@ -194,7 +194,7 @@ "body": "# Service Disruption - Platform Availability and Login Access \n\n## Root Cause Analysis\n\n### Duration of the incident\n\nDiscovered: Sep 23, 2025 \u2013 17:45- UTC \nResolved: Sep 26, 2025 \u2013 13:58 - UTC\n\n### Customer impact\n\nTenants on the CA1 cluster lost their settings, and Auvik was inaccessible for a time.\n\nIntermittent platform errors and degraded performance for some customers.\n\nA temporary issue prevented certain users from logging in via Okta.\n\nDelays in data synchronization in the EU1 region necessitate restarting the cluster.\n\n### Cause\n\nA configuration update intended for specific tenants was applied globally due to a missing query constraint.\n\nThis caused the deletion of tenant and user records in one cluster, leading to cascading synchronization and workload impacts across other clusters.\n\nAs a result, user data was propagated as deletions to the identity provider, temporarily removing affected user accounts.\n\n### Effect\n\nThe CA1 cluster required restoration from a backup, resulting in the temporary unavailability of some tenant data.\n\n43 tenants and 22 user accounts required manual recreation and verification.\n\nAuthentication failures occurred for affected users due to the removal of identity records.\n\nThe EU1 cluster experienced performance degradation as it processed a large data synchronization backlog.\n\nIncreased load briefly impacted the responsiveness of other clusters\u2019 regional services.\n\n### Future consideration\\(s\\)\n\n* Implement a dry-run and confirmation step in internal tooling to validate production commands before execution.\n* Reinforce the change-management process for improved peer visibility and validation.\n* Expand resource and capacity monitoring to identify anomalies earlier and respond proactively.\n* Revisit release control lifecycle practices to remove obsolete configurations after rollout completion.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-26T09:58:35.912-04:00", "resolved_inferred": false, "started_at": "2025-09-23T13:45:56.147-04:00", @@ -207,7 +207,7 @@ "body": "# Service Degraded - Clients experienced login issues to their site because the URL redirect was not working.\n\n## Root Cause Analysis\n\n \nA recent update led to more traffic than expected, resulting in simultaneous overload of the same systems. This overloaded them, leading to delays and occasional failures when customers tried to log in. Some customers also experienced issues when trying to start new trials.\n\n### Duration of the incident\n\nDiscovered: Sep 17, 2025 13:50 - UTC \nResolved: Sep 18, 2025 21:00 - UTC\n\n### Cause\n\nThe update unintentionally created extra demand on shared systems. As a result, the login process and new trial creation sometimes failed or responded slowly.\n\n### Effect\n\n* Some customers could not log in after entering their password or completing MFA.\n* Occasional slow responses and error messages \\(404/500/502/504\\).\n* New trial sign-ups sometimes failed or were delayed.\n* Internal tools that rely on the same login process also saw intermittent issues.\n\n### Action taken \n\n* Adjusted system settings to reduce pressure on overloaded services.\n* Closely monitored traffic while making changes to keep the service stable.\n* Applied a temporary workaround to allow new trials to be created reliably.\n* Released a fix to stabilize the login redirect process.\n* Made further tuning changes to spread out demand and reduce load.\n* Continued monitoring until the login and sign-up flows were confirmed to be stable.\n\n### Future consideration\\(s\\)\n\n* Reduce reliance on a single system for login and trial flows by distributing the workload across multiple systems..\n* Enhance monitoring to identify login errors and trial creation issues more promptly.\n* Add safeguards to prevent overload, including traffic limits and fallback options.\n* Test updates under heavier load conditions to catch these issues earlier.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-18T17:00:23.307-04:00", "resolved_inferred": false, "started_at": "2025-09-17T09:53:56.227-04:00", @@ -220,7 +220,7 @@ "body": "# Service Degraded - Login and Collector Installation Issues on US3 Cluster\n\n## Root Cause Analysis\n\n### Duration of the incident\n\nDiscovered: Sep 10, 2025 13:17 UTC \nResolved: Sep 12, 2025 15:08 UTC\n\n### Cause\n\nTwo separate but overlapping issues contributed to this incident:\n\n* Collector Installation Failures \u2013 Windows collectors were unable to install due to missing service principal credentials on the backend agent server, which prevented successful API calls for subscription data.\n* Login and Redirect Failures \u2013 Following a restart of the US3 frontend, requests for user and tenant data from secondary clusters intermittently failed. This caused login attempts through Okta to hang and product redirects to fail.\n\n### Effect\n\n* Users attempting to log in via Okta were unable to complete authentication and access tenants.\n* Some sites experienced 500 errors when attempting to access dashboards.\n* Windows collector installations via GUI and CLI failed, preventing the deployment of new collectors.\n\n### Action taken\n\n_All times are in UTC_\n\n \n**09/10/2025**\n\n**13:17** \u2013 Users report inability to log in to Auvik Production through Okta.\n\n**13:28** \u2013 Errors in US3 frontend logs identified relating to user/tenant data queries.\n\n**13:37** \u2013 Engineering suspends frontend deployment in the US3 cluster.\n\n**13:39** \u2013 Issues confirmed across secondary clusters; logs analyzed for root cause.\n\n**14:54** \u2013 Identified that the frontend redirect service could not fetch required tenant data; feature flag disabled to restore functionality.\n\n**15:01** \u2013 Engineering confirms that the workaround restores login functionality while monitoring tenant recovery. The incident is resolved on the status page.\n\n**09/12/2025**\n\n**15:08** \u2013 Feature flag re-enabled after system recovery; frontend services reconciled successfully. Incident fully resolved.\n\n### Future consideration\\(s\\)\n\n* Improve validation of service principal credentials to prevent collector installation failures.\n* Enhance monitoring and alerting around login and redirect workflows to detect tenant query failures earlier.\n* Review and refine feature flag rollout procedures to minimize dependency risks and ensure optimal deployment.\n* Continue improving how customer data is distributed across clusters so that queries run more efficiently and reliably, even during high system load or maintenance events.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-10T13:26:51.000-04:00", "resolved_inferred": false, "started_at": "2025-09-10T12:43:33.677-04:00", @@ -233,7 +233,7 @@ "body": "The access issues for clients on the US4 cluster have been fully resolved, and services are operating as expected.\n\nImpact: \nCustomers should no longer experience any related issues. If you continue to experience issues, please report them to Auvik Support.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-27T19:06:55.799-04:00", "resolved_inferred": false, "started_at": "2025-08-27T17:30:17.548-04:00", @@ -246,7 +246,7 @@ "body": "# Service Disruption - Intermittent Availability & Performance Issues Across Multiple Clusters\n\n## Root Cause Analysis\n\n### Duration of the incident\n\nDiscovered: Aug 25, 2025 18:00 - UTC \nResolved: Aug 29, 2025 14:00 - UTC\n\n### Cause\n\nA configuration rollout unexpectedly generated a large number of configuration entries, which propagated across tenants. This resulted in excessive background processing and memory pressure in core services. The strain led to degraded performance, instability, and in some cases, brief service crashes across clusters.\n\n### Effect\n\nCustomers experienced:\n\n* Intermittent access and sign-in issues in several regions\n* Slow page loads and missing/delayed alert notifications\n* Errors or gaps in specific dashboard and visualization views\n* Temporary unavailability for a small number of tenants\n\n### Action taken\n\n_All times are in UTC_\n\n**08/25/2025** \n**18:00** \u2014 Rollout halted after error rates increased. \n**19:00** \u2014 Targeted service restarts restored partial availability. \n**22:00** \u2014 Added backend capacity and began controlled rollouts.\n\n**08/26\u201308/28/2025**\n\nContinued staged rollouts with adjusted capacity. \nCleaned up configuration entries for affected tenants. \nTuned resource allocations for read/permissioning services\n\n**08/29/2025**\n\n**14:00** \u2014 All clusters stabilized; monitoring confirmed normal performance.\n\n### Future consideration\\(s\\)\n\n* Enhance autoscaling and resource thresholds for services under heavy background processing.\n* Add scale-aware pre-deployment validation for configuration rollouts.\n* Refine monitoring to surface customer-visible issues earlier.\n* Expand operational runbooks for rollback and tenant recovery.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-27T10:13:51.026-04:00", "resolved_inferred": false, "started_at": "2025-08-25T14:32:03.498-04:00", @@ -259,7 +259,7 @@ "body": "# Performance Degraded - Site dropdown not working for several clusters\n\n## Root Cause Analysis\n\n### Duration of the incident\n\nDiscovered: Aug 25, 2025 \u2013 15:40 UTC \nResolved: Aug 25, 2025 \u2013 16:45 UTC\n\n### Cause\n\nA recent system update introduced a change that depended on data not yet available in our production environment. As a result, the site selector \\(drop-down\\) was unable to load correctly, which prevented users from switching between sites until the update was rolled back.\n\n### Effect\n\nCustomers were unable to switch sites in the platform, which limited access to some account information and historical data.\n\n### Action taken\n\n_All times are in UTC_\n\n**08/25/2025**\n\n**15:40** \u2013 Update deployed across production clusters.\n\n**16:17** \u2013 Customer reports received that the site drop-down was not loading.\n\n**16:26** \u2013 Engineering identified the change that introduced the issue.\n\n16**:27** \u2013 Incident declared; response team assembled.\n\n**16:40** \u2013 Deployment was rolled back.\n\n**16:45** \u2013 Service restored; site drop-down working as expected. Incident resolved.\n\n### \nFuture consideration\\(s\\)\n\n* Add extra checks before updates to ensure all required data is available in production.\n* Improve safeguards so that unrelated changes are not deployed together.\n* Build fallback mechanisms to ensure that new features do not impact existing functionality.\n* Strengthen monitoring to detect and alert on similar issues in the future quickly.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-25T12:58:53.882-04:00", "resolved_inferred": false, "started_at": "2025-08-25T12:58:53.838-04:00", @@ -272,7 +272,7 @@ "body": "# Service Degraded - Clients on the EU1 cluster using V2 alerting are not reviewing device alerts.\n\n## Root Cause Analysis\n\n### Duration of the incident\n\nDiscovered: Aug 21, 2025 23:47 - UTC \nResolved: Aug 22, 2025 12:00 - UTC\n\n### Cause\n\nA change to the alert-processing timing logic introduced a defect where time windows did not close properly. This prevented events from being processed promptly, causing alerts to queue up and delaying their delivery to the user interface.\n\n### Effect\n\nCustomers on the EU1 cluster using V2 alerting experienced delays in reviewing device alerts, with some alerts being delayed by up to 12 hours.\n\n### Action taken\n\n_All times are in UTC_\n\n**08/21/2025**\n\n**23:47** \u2013 Alert processing began lagging; backlog started building.\n\n**08/22/2025**\n\n**06:00** \u2013 Incident declared; engineers engaged to investigate.\n\n**12:00** \u2013 Adjustments made to processing pipeline; backlog cleared; all delayed alerts reprocessed; service restored.\n\n### Future consideration\\(s\\)\n\n* Add monitoring for time-window stalls and backlog growth.\n* Expand testing to cover out-of-order and skewed event scenarios.\n* Strengthen rollback plans for all future alert-processing changes.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-22T06:36:49.497-04:00", "resolved_inferred": false, "started_at": "2025-08-22T05:32:22.637-04:00", @@ -285,7 +285,7 @@ "body": "# Performance Degraded - Sites on the EU2 cluster are slow to load\n\n## Root Cause Analysis\n\n### Duration of the incident\n\nDiscovered: Aug 20, 2025 09:27 \u2013 UTC \nResolved: Aug 20, 2025 10:05 \u2013 UTC\n\n### Cause\n\nOne application component handling user requests on EU2 became unhealthy and stopped responding normally.\n\n### Effect\n\nSome EU2 customers experienced slow page loads and intermittent timeouts in the web experience during the incident window. \nAction taken\n\n_All times are in UTC_\n\n**08/20/2025**\n\n**09:27** \u2013 Potential slowness on EU2 reported; investigation initiated.\n\n**09:35** \u2013 Elevated errors observed; incident declared; response team engaged.\n\n**09:45** \u2013 Application components restarted to restore service.\n\n**10:05** \u2013 Service performance restored.\n\n**10:07** \u2013 Validation confirmed recovery; incident closed.\n\n### Future consideration\\(s\\)\n\n* Complete an investigation into the component crash and address any defects found.\n* Enhance monitoring/alerting for rising request latency and timeout errors to detect earlier.\n* Review deployment and health-check safeguards to auto-recover unresponsive components safely.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-20T10:09:21.589-04:00", "resolved_inferred": false, "started_at": "2025-08-20T09:50:24.176-04:00", @@ -298,7 +298,7 @@ "body": "# Performance Degraded - Clients on the US2 cluster are slow to load\n\n## Root Cause Analysis\n\n### Duration of the incident\n\nDiscovered: Aug 19, 2025 \u2013 13:10 UTC \nResolved: Aug 19, 2025 \u2013 15:30 UTC\n\n### Cause\n\nRecent configuration changes to backend data replication caused a surge in database writes. This increased CPU utilization across all clusters, but while other clusters recovered, the US2 database instance did not. The elevated CPU load persisted for over 24 hours, which led to customer-facing slowness when loading sites on the US2 cluster.\n\n### Effect\n\nCustomers on the US2 cluster experienced significantly slower site load times in the Auvik UI. This impacted demos, trials, and production users, resulting in degraded user experience until resolution.\n\n### Action taken\n\n_All times are in UTC_\n\n**08/19/2025**\n\n**13:10** \u2013 Sales reported demo site loading issues on US2.\n\n**13:22** \u2013 Engineering identified elevated CPU usage on the US2 database.\n\n**13:27** \u2013 Investigation into DB performance began.\n\n**13:57** \u2013 Confirmed that US2 had remained at 100% CPU since Aug 18.\n\n**14:25** \u2013 Troubleshooting efforts to recover performance begin.\n\n**14:36** \u2013 Proposal made to scale up resources for the DB.\n\n**15:00** \u2013 Decision made to upgrade the US2 database instance type.\n\n**15:09** \u2013 Database instance size increased.\n\n**15:22** \u2013 Read/write latency returned to normal.\n\n**15:30** \u2013 US2 UI performance confirmed as fully recovered.\n\n### Future consideration\\(s\\)\n\n* Enhance database CPU monitoring alerts to ensure visibility into leading indicators.\n* Improve alerting for customer-impacting issues such as UI slowness.\n* Conduct proactive reviews of cluster resource utilization to identify potential bottlenecks.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-19T11:30:00.000-04:00", "resolved_inferred": false, "started_at": "2025-08-19T11:30:00.000-04:00", diff --git a/api/v/avanan.json b/api/v/avanan.json index e404a6e1da38aa539b80aabbe20bb7c24ade3c47..65db642e4f8871a800858a71953918edde2c2a14 100644 --- a/api/v/avanan.json +++ b/api/v/avanan.json @@ -3,7 +3,7 @@ "slug": "avanan", "platform": "statuspage", "status_url": "https://status.avanan.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "unknown", "history_backfilled": false, "first_watched": "2026-09-04T07:06:16Z", diff --git a/api/v/avaya-cloud.json b/api/v/avaya-cloud.json index feb0dd9d6d1980ff51898656dbb011276db6f86b..fa3f5395d031cf4dcf268301fa017b58e27e0f9e 100644 --- a/api/v/avaya-cloud.json +++ b/api/v/avaya-cloud.json @@ -3,7 +3,7 @@ "slug": "avaya-cloud", "platform": "statuspage", "status_url": "https://status.avayacloud.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-23T19:25:14.537-04:00", "resolved_inferred": false, "started_at": "2026-04-23T15:36:07.356-04:00", @@ -25,7 +25,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-27T04:06:18.692-04:00", "resolved_inferred": false, "started_at": "2026-03-26T06:06:03.634-04:00", @@ -38,7 +38,7 @@ "body": "The incident has been resolved", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-20T09:27:47.224-04:00", "resolved_inferred": false, "started_at": "2026-03-19T18:59:00.398-04:00", @@ -51,7 +51,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-18T08:17:25.377-04:00", "resolved_inferred": false, "started_at": "2026-03-17T20:39:47.917-04:00", @@ -64,7 +64,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-17T20:28:48.700-04:00", "resolved_inferred": false, "started_at": "2026-02-26T19:07:07.642-05:00", @@ -77,7 +77,7 @@ "body": "Issue has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-20T13:47:59.135-05:00", "resolved_inferred": false, "started_at": "2026-02-19T12:28:41.317-05:00", @@ -90,7 +90,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-03T15:25:24.959-05:00", "resolved_inferred": false, "started_at": "2026-02-03T14:02:58.255-05:00", @@ -103,7 +103,7 @@ "body": "Incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-03T07:13:47.248-05:00", "resolved_inferred": false, "started_at": "2026-02-03T03:53:24.039-05:00", @@ -116,7 +116,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-30T03:21:37.965-05:00", "resolved_inferred": false, "started_at": "2026-01-29T07:03:08.679-05:00", @@ -129,7 +129,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-26T11:31:36.810-05:00", "resolved_inferred": false, "started_at": "2026-01-26T07:04:01.078-05:00", @@ -142,7 +142,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-23T13:24:32.471-05:00", "resolved_inferred": false, "started_at": "2026-01-17T09:23:43.704-05:00", @@ -155,7 +155,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-17T03:03:25.279-05:00", "resolved_inferred": false, "started_at": "2025-12-16T16:43:23.361-05:00", @@ -168,7 +168,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-16T03:39:07.708-05:00", "resolved_inferred": false, "started_at": "2025-12-16T03:28:33.521-05:00", @@ -181,7 +181,7 @@ "body": "Issue has been resolved already.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-15T01:22:51.632-05:00", "resolved_inferred": false, "started_at": "2025-12-15T01:22:51.578-05:00", @@ -194,7 +194,7 @@ "body": "The incident has been resolved and services are operating normally. Avaya will continue to monitor the situatio.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-08T11:30:06.091-05:00", "resolved_inferred": false, "started_at": "2025-12-07T16:36:46.000-05:00", @@ -207,7 +207,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-06T02:56:02.229-05:00", "resolved_inferred": false, "started_at": "2025-12-05T12:51:54.354-05:00", @@ -220,7 +220,7 @@ "body": "If a new user has been created in the last two weeks and the user was unable to login, it is recommended to follow the KB article today again.\nhttps://kb.avaya.com/kb/index?page=content&id=SOLN385689", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-28T04:23:30.322-05:00", "resolved_inferred": false, "started_at": "2025-11-27T12:39:17.240-05:00", @@ -233,7 +233,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-02T13:32:04.400-05:00", "resolved_inferred": false, "started_at": "2025-11-26T15:39:13.089-05:00", @@ -246,7 +246,7 @@ "body": "We have identified and resolved the issue", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-26T02:37:16.256-05:00", "resolved_inferred": false, "started_at": "2025-11-25T08:46:37.299-05:00", @@ -259,7 +259,7 @@ "body": "The incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-19T08:46:12.565-05:00", "resolved_inferred": false, "started_at": "2025-11-18T07:01:56.940-05:00", @@ -272,7 +272,7 @@ "body": "All services are fully operational, and normal functionality has been restored.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-03T16:54:10.197-05:00", "resolved_inferred": false, "started_at": "2025-11-03T14:16:58.510-05:00", @@ -285,7 +285,7 @@ "body": "We observed the recording issue post Verint maintenance update on Prod-ASE.\nProblem was resolved post Certificate update.\nThere was no Data loss in this process.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-09T01:53:30.875-04:00", "resolved_inferred": false, "started_at": "2025-10-09T01:53:30.825-04:00", @@ -298,7 +298,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-26T16:23:39.867-04:00", "resolved_inferred": false, "started_at": "2025-09-26T15:21:53.699-04:00", @@ -311,7 +311,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-12T08:38:51.803-04:00", "resolved_inferred": false, "started_at": "2025-09-12T08:01:44.780-04:00", @@ -324,7 +324,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-09T14:13:55.744-04:00", "resolved_inferred": false, "started_at": "2025-09-09T13:28:16.094-04:00", @@ -337,7 +337,7 @@ "body": "We recently identified an intermittent issue that caused errors during the saving of Agents. This issue has now been fully resolved, and no further action is required.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-08T09:05:53.506-04:00", "resolved_inferred": false, "started_at": "2025-09-08T09:05:53.452-04:00", @@ -350,7 +350,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-05T14:20:18.698-04:00", "resolved_inferred": false, "started_at": "2025-09-05T13:30:53.309-04:00", @@ -363,7 +363,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-01T08:50:16.854-04:00", "resolved_inferred": false, "started_at": "2025-09-01T06:04:00.895-04:00", @@ -376,7 +376,7 @@ "body": "The issue impacting Journey Store services in the APAC region has been fully resolved. All services are now operating normally. We will continue to monitor to ensure stability.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-18T02:53:33.696-04:00", "resolved_inferred": false, "started_at": "2025-08-18T02:32:03.783-04:00", @@ -389,7 +389,7 @@ "body": "Issue has been identified with automation test for voice call and until resolved manual tests will be conducted. There are no impact to production tenants.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-16T08:26:23.183-04:00", "resolved_inferred": false, "started_at": "2025-08-16T06:51:21.491-04:00", @@ -402,7 +402,7 @@ "body": "The incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-14T06:44:45.457-04:00", "resolved_inferred": false, "started_at": "2025-08-13T17:43:32.453-04:00", @@ -415,7 +415,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-12T10:30:26.814-04:00", "resolved_inferred": false, "started_at": "2025-08-11T14:35:52.585-04:00", @@ -428,7 +428,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-10T04:38:48.748-04:00", "resolved_inferred": false, "started_at": "2025-08-10T01:29:07.278-04:00", diff --git a/api/v/aviator.json b/api/v/aviator.json index f596957988f38501330405c60c8fe13e9be1bcc7..f26e4973daaba3e7ec78267564f1782f0d8925d6 100644 --- a/api/v/aviator.json +++ b/api/v/aviator.json @@ -3,7 +3,7 @@ "slug": "aviator", "platform": "statuspage", "status_url": "https://status.aviator.co", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "The incident is resolved.\n\nRoot cause: A large bulk team-reorganization in one customer's GitHub organization triggered database lock contention in our team-sync handler, which consumed the shared worker pool that processes all the background tasks.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-11T21:49:12.726Z", "resolved_inferred": false, "started_at": "2026-08-11T20:43:05.494Z", @@ -25,7 +25,7 @@ "body": "We deployed a fix to improve the queue page load performance that has resolved the performance issues.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-15T02:17:49.910Z", "resolved_inferred": false, "started_at": "2026-07-14T18:26:33.913Z", @@ -38,7 +38,7 @@ "body": "User reported queues slow in merging PRs. This was reported at 8.38am PT, we investigated and noticed that each task was talking longer to process. Found the actual slow behavior started after the last deploy at 9.06pm PT on Apr 30. Initiated a rollback, completed the rollback at 9.23am PT.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-01T15:30:00.000Z", "resolved_inferred": false, "started_at": "2026-05-01T15:30:00.000Z", diff --git a/api/v/axcient.json b/api/v/axcient.json index 50735b1485d89213b28d7d4aac15ba8631bbb39e..3562053ece9daa0d7f28383e43589d78844cfc06 100644 --- a/api/v/axcient.json +++ b/api/v/axcient.json @@ -3,7 +3,7 @@ "slug": "axcient", "platform": "statuspage", "status_url": "https://status.axcient.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "unknown", "history_backfilled": false, "first_watched": "2026-09-04T07:06:16Z", diff --git a/api/v/axiom.json b/api/v/axiom.json index f191dc8ad5b6579b943563bd888f6ab495fb815b..02be8d26bbbc7fe0a36f6fb04ac5190a9b9db433 100644 --- a/api/v/axiom.json +++ b/api/v/axiom.json @@ -3,7 +3,7 @@ "slug": "axiom", "platform": "statuspage", "status_url": "https://status.axiom.co", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "Access to the Axiom Console through Github is available as well as all other authentication methods.\n\nUsers might experience a one-time email verification step for their Primary Github email. The Primary email address should be configured as the email used with an Axiom account. Additional verified emails can be used to access separate Axiom accounts.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-12T20:08:07Z", "resolved_inferred": false, "started_at": "2026-08-10T17:08:16Z", @@ -24,7 +24,7 @@ "body": "A revert has happened, the query service is now operating normally.\n\nThe root cause has also been identified and we are actively working on it so queries are not affected again.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-15T10:26:22Z", "resolved_inferred": false, "started_at": "2026-07-15T10:17:16Z", @@ -36,7 +36,7 @@ "body": "We have rolled back the changes we have made in our infrastructure to fix the firehose ingestion.\nFirehose ingestion should be back now.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-30T21:39:51Z", "resolved_inferred": false, "started_at": "2026-06-30T18:30:27Z", @@ -48,7 +48,7 @@ "body": "Underlying infrastructure issues have been resolved, metrics queries on EU Edge Deployment should now be fully operational.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-19T14:45:44Z", "resolved_inferred": false, "started_at": "2026-06-19T10:24:31Z", @@ -60,7 +60,7 @@ "body": "This incident is fully resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-15T21:27:15Z", "resolved_inferred": false, "started_at": "2026-05-15T17:17:36Z", @@ -72,7 +72,7 @@ "body": "We see full recovery of the query subsystem.\n\nFor a small number of metrics datasets, there might be data missing between 00:15 and 01:24 UTC. We're working on recovery with our infrastructure provider.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-08T00:50:00Z", "resolved_inferred": false, "started_at": "2026-05-08T00:16:02Z", @@ -84,7 +84,7 @@ "body": "All systems are operating normally. The issue has been fully resolved and we are continuing to monitor to ensure stability.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-28T15:09:01Z", "resolved_inferred": false, "started_at": "2026-04-28T14:27:28Z", @@ -96,7 +96,7 @@ "body": "This incident is now resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-18T05:12:00Z", "resolved_inferred": false, "started_at": "2026-04-17T15:00:58Z", @@ -108,7 +108,7 @@ "body": "Between March 30 and April 13, a configuration issue prevented email notifications from firing for monitors on our Legacy EU infrastructure (not EU edge deployment). Monitor evaluation was functioning correctly during this period \u2014 monitors were being evaluated and other notification channels were unaffected \u2014 but email delivery through our email provider was misconfigured for the EU region.\n\nThe issue has been resolved. Email notifications are now firing correctly for all EU monitors. If you believe you missed critical email alerts during this window, we recommend reviewing your monitor history in the Axiom dashboard.\n\nWe apologize for the disruption and are putting safeguards in place to prevent similar issues in the future.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-30T09:40:00Z", "resolved_inferred": false, "started_at": "2026-04-14T09:43:06Z", @@ -120,7 +120,7 @@ "body": "This incident is resolved", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-12T15:13:48Z", "resolved_inferred": false, "started_at": "2026-04-12T13:21:48Z", @@ -132,7 +132,7 @@ "body": "This incident is resolved", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-06T02:02:44Z", "resolved_inferred": false, "started_at": "2026-03-06T01:29:48Z", @@ -144,7 +144,7 @@ "body": "Just before 3pm on 26th of Feb '26, an incorrect configuration was accidentally deployed to our EU environment which impacted query performance. We quickly identified the issue and released a fix. ", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-26T15:00:00Z", "resolved_inferred": false, "started_at": "2026-02-26T17:46:29Z", @@ -156,7 +156,7 @@ "body": "All services have returned to normal operation. Queries are executing successfully, and internal traffic between services has been fully restored. We are continuing to monitor the system to ensure stability.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-26T15:55:00Z", "resolved_inferred": false, "started_at": "2026-02-26T16:13:13Z", @@ -168,7 +168,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-27T19:40:00Z", "resolved_inferred": false, "started_at": "2026-01-27T17:16:00Z", @@ -180,7 +180,7 @@ "body": "All services are operating nominally.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-17T13:01:14Z", "resolved_inferred": false, "started_at": "2026-01-17T01:06:39Z", @@ -192,7 +192,7 @@ "body": "We have identified and solved the issue at hand. Optimal query performance should not be restored.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-13T22:31:36Z", "resolved_inferred": false, "started_at": "2026-01-13T22:08:57Z", @@ -204,7 +204,7 @@ "body": "All error rates are back to nominal levels.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-09T23:41:27Z", "resolved_inferred": false, "started_at": "2026-01-09T21:03:53Z", @@ -216,7 +216,7 @@ "body": "This incident is now fully resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-15T15:01:21Z", "resolved_inferred": false, "started_at": "2025-12-15T14:51:19Z", @@ -228,7 +228,7 @@ "body": "Access to Axiom Console was temporary disrupted. Users were unable to access Axiom and were shown a Vercel sign-in screen.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-05T14:45:00Z", "resolved_inferred": false, "started_at": "2025-12-05T15:28:11Z", @@ -240,7 +240,7 @@ "body": "We have identified and resolved issues with monitor processing in the EU region\n\nSome of our EU customers could have experienced monitor processing issues.\n\nDuring this period, gaps in alerting were a possibility due to instability issues caused by underlying scaling issues. Monitoring systems in other regions remained operational. \n\nThe issue was identified and resolved on Sunday evening, and all monitoring services in the EU region have since been fully restored.\n\nTo prevent similar issues in the future, we have added automated configuration validation, expanded deployment checks for regional dependencies, and introduced enhanced monitoring of our monitoring layer itself.\n\nWe apologise for the disruption this caused. The issue is now fully resolved, and monitoring and alerting in the EU region are operating normally.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-02T20:10:00Z", "resolved_inferred": false, "started_at": "2025-11-03T18:10:44Z", @@ -252,7 +252,7 @@ "body": "This incident is now fully resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-20T11:31:28Z", "resolved_inferred": false, "started_at": "2025-10-20T07:55:02Z", @@ -264,7 +264,7 @@ "body": "Full connectivity with Vercel has been re-established.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-06T11:14:37Z", "resolved_inferred": false, "started_at": "2025-10-06T08:03:56Z", @@ -276,7 +276,7 @@ "body": "This incident is now fully resolved", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-15T22:29:22Z", "resolved_inferred": false, "started_at": "2025-09-15T17:39:34Z", @@ -288,7 +288,7 @@ "body": "This incident is resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-28T17:09:46Z", "resolved_inferred": false, "started_at": "2025-08-28T14:41:23Z", diff --git a/api/v/axios.json b/api/v/axios.json index 7787cf502039caea531f03e89f1cfc60f60ffb52..958c40a83613aff7deccf8d5082a3650ade98bc3 100644 --- a/api/v/axios.json +++ b/api/v/axios.json @@ -3,7 +3,7 @@ "slug": "axios", "platform": "statuspage", "status_url": "https://status.axioshq.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "The issue has been resolved. We apologize for any inconvenience the disruption may have caused.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-16T22:11:49Z", "resolved_inferred": false, "started_at": "2026-03-16T21:51:27Z", @@ -24,7 +24,7 @@ "body": "Cloudflare has resolved the issue. Everything has been functional for the past few hours but we were extra cautious in case additional errors would appear. Thank you for your patience. ", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-18T19:42:59Z", "resolved_inferred": false, "started_at": "2025-11-18T12:05:24Z", @@ -36,7 +36,7 @@ "body": "The issue has been resolved. We apologize for any inconvenience the disruption may have caused.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-21T00:53:36Z", "resolved_inferred": false, "started_at": "2025-10-20T14:20:28Z", @@ -48,7 +48,7 @@ "body": "The issue has been resolved. We apologize for any inconvenience the disruption may have caused.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-19T13:13:59Z", "resolved_inferred": false, "started_at": "2025-09-19T12:38:49Z", @@ -60,7 +60,7 @@ "body": "The issue has been resolved. We apologize for any inconvenience the disruption may have caused.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-29T19:57:20Z", "resolved_inferred": false, "started_at": "2025-08-29T19:13:41Z", diff --git a/api/v/axis-communications.json b/api/v/axis-communications.json index b3dd22c8c7e3b0b7a403608614763edeabe17409..e14203e13db30057782d1ef8a0bdf310413396b9 100644 --- a/api/v/axis-communications.json +++ b/api/v/axis-communications.json @@ -3,7 +3,7 @@ "slug": "axis-communications", "platform": "statuspage", "status_url": "https://status.axis.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-28T15:44:08.252+02:00", "resolved_inferred": false, "started_at": "2026-08-28T15:39:32.795+02:00", @@ -25,7 +25,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-04T10:09:14.388+02:00", "resolved_inferred": false, "started_at": "2026-08-04T10:06:11.796+02:00", @@ -38,7 +38,7 @@ "body": "Problematic service was identified and fixed", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-11T20:10:30.509+02:00", "resolved_inferred": false, "started_at": "2026-07-11T20:01:11.209+02:00", @@ -51,7 +51,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-23T18:00:46.316+02:00", "resolved_inferred": false, "started_at": "2026-06-23T17:04:00.245+02:00", @@ -64,7 +64,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-28T14:40:02.685+02:00", "resolved_inferred": false, "started_at": "2026-04-28T14:28:15.551+02:00", @@ -77,7 +77,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-28T20:25:04.575+01:00", "resolved_inferred": false, "started_at": "2026-03-28T18:58:31.796+01:00", @@ -90,7 +90,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-25T20:50:00.325+01:00", "resolved_inferred": false, "started_at": "2026-02-25T19:06:47.724+01:00", @@ -103,7 +103,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-20T06:59:09.671+01:00", "resolved_inferred": false, "started_at": "2026-02-20T06:39:36.717+01:00", @@ -116,7 +116,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-12T11:40:49.554+01:00", "resolved_inferred": false, "started_at": "2026-02-12T07:24:16.806+01:00", @@ -129,7 +129,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-28T20:01:27.394+01:00", "resolved_inferred": false, "started_at": "2026-01-28T18:39:48.411+01:00", @@ -142,7 +142,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-18T14:48:03.729+01:00", "resolved_inferred": false, "started_at": "2025-12-18T12:29:53.027+01:00", @@ -155,7 +155,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-16T16:16:19.402+01:00", "resolved_inferred": false, "started_at": "2025-12-15T15:44:45.962+01:00", @@ -168,7 +168,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-30T04:36:18.705+01:00", "resolved_inferred": false, "started_at": "2025-10-29T17:34:37.209+01:00", @@ -181,7 +181,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-28T16:54:18.410+01:00", "resolved_inferred": false, "started_at": "2025-10-28T16:12:52.911+01:00", @@ -194,7 +194,7 @@ "body": "All services are now operating normally.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-21T00:58:20.119+02:00", "resolved_inferred": false, "started_at": "2025-10-20T18:37:34.921+02:00", @@ -207,7 +207,7 @@ "body": "The outage at AWS US-EAST-1 has caused onboarding and streaming services to become unavailable in the Americas region.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-20T09:00:00.000+02:00", "resolved_inferred": false, "started_at": "2025-10-20T09:00:00.000+02:00", @@ -220,7 +220,7 @@ "body": "This incident was due to issues in Microsoft Azure. Microsoft has confirmed that their services has now almost fully recovered. We no longer see any signs of our services being affected, but we will continue to monitor the situation.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-09T15:24:00.800+02:00", "resolved_inferred": false, "started_at": "2025-10-09T11:18:06.325+02:00", @@ -233,7 +233,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-01T07:57:50.763+02:00", "resolved_inferred": false, "started_at": "2025-09-30T19:54:55.940+02:00", @@ -246,7 +246,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-25T08:45:39.693+02:00", "resolved_inferred": false, "started_at": "2025-09-25T02:47:49.183+02:00", @@ -259,7 +259,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-24T15:51:37.338+02:00", "resolved_inferred": false, "started_at": "2025-09-24T15:12:14.605+02:00", @@ -272,7 +272,7 @@ "body": "Problem is fixed now.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-05T15:16:35.430+02:00", "resolved_inferred": false, "started_at": "2025-09-05T04:48:49.737+02:00", @@ -285,7 +285,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-03T19:16:56.484+02:00", "resolved_inferred": false, "started_at": "2025-09-03T15:32:29.571+02:00", @@ -298,7 +298,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-01T15:42:43.253+02:00", "resolved_inferred": false, "started_at": "2025-09-01T08:28:34.616+02:00", @@ -311,7 +311,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-19T08:30:34.395+02:00", "resolved_inferred": false, "started_at": "2025-08-18T13:55:58.394+02:00", diff --git a/api/v/axway.json b/api/v/axway.json index 360d1164b82be78f3d752efa1f0624e64339b3dd..65b89e39e6fb55070dee56977eed7bde4c9a9c6f 100644 --- a/api/v/axway.json +++ b/api/v/axway.json @@ -3,7 +3,7 @@ "slug": "axway", "platform": "statuspage", "status_url": "https://status.axway.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-18T20:05:39.000Z", "resolved_inferred": false, "started_at": "2026-08-18T19:40:42.000Z", @@ -25,7 +25,7 @@ "body": "We observed a brief period of degraded authentication service between 05:50 UTC and 06:50 UTC on 11 August 2026, during which a small number of users may have experienced login failures.\n\nThe issue has been fully resolved, and services are operating normally. Additional monitoring and preventive measures have been put in place to help maintain service reliability.\n\nWe regret any disruption this may have caused and appreciate your continued trust.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-11T06:50:00.000Z", "resolved_inferred": false, "started_at": "2026-08-11T05:50:00.000Z", @@ -38,7 +38,7 @@ "body": "Unbounded queries overwhelmed the analytics systems in use by Engage and Platform, causing delays in processing between 2PM-3PM UTC today.\n\nWe will be working to improve query size and performance as well as introduce further restrictions to prevent this from causing issues in the future.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-11T14:00:00.000Z", "resolved_inferred": false, "started_at": "2026-05-11T14:00:00.000Z", @@ -51,7 +51,7 @@ "body": "We\u2019re sorry \u2014 between 13:00 UTC and 14:00 UTC today some customers experienced partial interruptions to Axway Platform, Axway Analytics, Amplify Marketplace, and Amplify Engage. During that window an internal service error caused elevated failures and automated retries, which temporarily prevented normal access for some users.\n\nWe restored access by allowing queued requests to proceed while we validated and deployed a tested fix; normal service was confirmed at 14:00 UTC. No customer data was exposed.\n\nWe\u2019re taking steps to reduce the chance of this happening again, including additional safeguards, improved test coverage, and broader alerting so production issues are surfaced to our public status page and support teams more quickly.\n\nIf you\u2019re still seeing problems or need help, please contact support through your usual channels.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-19T13:00:00.000Z", "resolved_inferred": false, "started_at": "2026-02-19T13:00:00.000Z", @@ -64,7 +64,7 @@ "body": "Description: During the detected outage on Amplify Studio, users experienced instability in activating integrations. Additionally, the receipt of monitoring data from Fusion was affected.\n\nRoot Cause: The introduction of additional monitoring checks in the environments led to a permissions error on the clusters. This error disrupted connectivity between the Studio and Fusion instances. The standard validation routines prior to being deployed in production didn\u2019t catch this permission mismatch. \n\nCorrective Action: The permissions were promptly reverted, and impacted services were verified. To prevent recurrence, we have implemented additional checks to ensure such changes do not affect production without being detected in lower environments first.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-09T06:30:00.000Z", "resolved_inferred": false, "started_at": "2025-12-09T06:30:00.000Z", diff --git a/api/v/b2c2.json b/api/v/b2c2.json index af02f5c3a70e52ec233bbc784c4b4fa014837251..8de42b5dff8bcae610b7f1e964e8df375ec3de02 100644 --- a/api/v/b2c2.json +++ b/api/v/b2c2.json @@ -3,7 +3,7 @@ "slug": "b2c2", "platform": "statuspage", "status_url": "https://status.b2c2.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-31T09:46:06.970Z", "resolved_inferred": false, "started_at": "2026-08-31T09:18:19.289Z", @@ -25,7 +25,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-31T08:50:44.797Z", "resolved_inferred": false, "started_at": "2026-08-31T05:17:44.882Z", @@ -38,7 +38,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-24T17:44:21.945Z", "resolved_inferred": false, "started_at": "2026-06-24T17:38:20.405Z", @@ -51,7 +51,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-03T21:04:43.801Z", "resolved_inferred": false, "started_at": "2026-06-03T18:02:19.016Z", @@ -64,7 +64,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-11T13:30:44.343Z", "resolved_inferred": false, "started_at": "2026-05-11T13:02:11.570Z", @@ -77,7 +77,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-11T10:57:08.559Z", "resolved_inferred": false, "started_at": "2026-05-11T09:59:55.029Z", @@ -90,7 +90,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-16T16:02:45.730Z", "resolved_inferred": false, "started_at": "2026-03-16T03:22:59.387Z", @@ -103,7 +103,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-20T17:30:11.140Z", "resolved_inferred": false, "started_at": "2026-02-20T16:56:09.406Z", @@ -116,7 +116,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-13T11:04:54.733Z", "resolved_inferred": false, "started_at": "2026-02-13T10:59:51.138Z", @@ -129,7 +129,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-28T19:14:56.902Z", "resolved_inferred": false, "started_at": "2026-01-28T18:27:21.601Z", @@ -142,7 +142,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-20T20:42:56.038Z", "resolved_inferred": false, "started_at": "2026-01-20T20:22:25.686Z", @@ -155,7 +155,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-04T13:18:36.263Z", "resolved_inferred": false, "started_at": "2025-11-04T11:29:27.258Z", @@ -168,7 +168,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-10T21:58:56.306Z", "resolved_inferred": false, "started_at": "2025-10-10T21:20:13.726Z", @@ -181,7 +181,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-10T14:17:43.756Z", "resolved_inferred": false, "started_at": "2025-10-10T13:53:29.667Z", @@ -194,7 +194,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-09T16:34:21.319Z", "resolved_inferred": false, "started_at": "2025-10-09T15:48:47.347Z", diff --git a/api/v/balena.json b/api/v/balena.json index 10b6fe1d07fc3c092c2499b0385bdc7794475a87..435df9258648cb1b7b620eca854556503a4c9cfb 100644 --- a/api/v/balena.json +++ b/api/v/balena.json @@ -3,7 +3,7 @@ "slug": "balena", "platform": "statuspage", "status_url": "https://status.balena.io", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "Unusual load on the proxy, caused some degraded performances on the device URL. \nEverything is now working properly.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-27T18:41:36.497Z", "resolved_inferred": false, "started_at": "2026-07-27T16:49:05.052Z", @@ -25,7 +25,7 @@ "body": "A routine version upgrade to a backend cache changed how the API handled its request queues. Under unusually heavy request load, those queues filled up and the API started dropping traffic, returning timeouts and errors.\n\nOver the course of the incident, affected users saw elevated API error rates that intermittently disrupted dashboard logins, API access, and device connectivity.\n\nWe mitigated it by rate-limiting the abnormal traffic at our edge and rolling the cache back to the previous version, which restored normal queue behaviour and recovered the platform.\n\nTo avoid a repeat, we're improving rate limiting so a single heavy consumer can't degrade service for others, and exploring autoscaling and load testing so infrastructure changes are validated under realistic load before they reach production.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-06T14:37:47.181Z", "resolved_inferred": false, "started_at": "2026-07-06T13:47:23.022Z", @@ -38,7 +38,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-09T18:24:27.299Z", "resolved_inferred": false, "started_at": "2026-07-02T14:03:50.645Z", @@ -51,7 +51,7 @@ "body": "A vulnerability mitigation update required replacing compute cluster nodes, which, when applied, rolled back due to a timeout. This caused some workloads \\(API, delta, builder\\) to become temporarily unavailable and triggering some undesired secondary effects, including ungracefully terminating a few long lived instances servicing VPN connections. While the rest of the services came back reasonably quickly within a minute or so, it too around one and a quarter hours to re-establish VPN tunnels.\n\nA scheduled maintenance will be posted later to perform this update during a planned outage window.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-05T21:03:33.607Z", "resolved_inferred": false, "started_at": "2026-05-05T18:12:25.509Z", @@ -64,7 +64,7 @@ "body": "Starting around March 11, some cloud builds began failing intermittently with no such image errors. The failures were non-deterministic and affected all architectures. At peak, some users saw around 50% failure rates.\n\nWe identified and fixed several bugs in the builder's image garbage collector that caused it to over-count freed disk space and run too aggressively, eventually deleting images that in-progress builds still needed. Fixes were deployed between March 19 and April 14, with build failure rates dropping to near-zero after the final deploy.\n\nWe're continuing to monitor and working on additional safeguards to prevent the garbage collector from targeting images that active builds depend on.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-21T16:30:32.566Z", "resolved_inferred": false, "started_at": "2026-03-31T12:55:25.446Z", @@ -77,7 +77,7 @@ "body": "We experienced degraded API performance due to an internal configuration change that unintentionally increased system load, resulting in slower response times and reduced request capacity. Our team identified the issue and rolled back the change to restore stability. A root cause fix has been implemented and deployed aswell. The system has now fully recovered, and services are operating normally.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-25T14:07:04.631Z", "resolved_inferred": false, "started_at": "2026-03-24T12:43:08.142Z", @@ -90,7 +90,7 @@ "body": "Between March 11 and March 25, some cloud builds experienced intermittent failures with \"no such image\" errors. The issue was non-deterministic and did not affect all builds.\n\nWe've identified a likely contributing factor and deployed mitigations that have stabilized build reliability. We're continuing to investigate the underlying cause to prevent recurrence.\n\nIf you experienced build failures during this window, re-running your build should succeed. We appreciate your patience while we worked through this, and we apologize for the disruption.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-25T13:18:51.711Z", "resolved_inferred": false, "started_at": "2026-03-23T16:57:53.653Z", @@ -103,7 +103,7 @@ "body": "We identified an issue in Dashboard v32.2.0, released on March 2, 2026, where opening the dashboard via a direct link to certain pages \\(such as billing or other account management pages\\) could result in being unexpectedly redirected to the fleets overview. This was caused by a race condition in our access control logic that made a routing decision before all authorization data had finished loading.\n\nThe issue was resolved on March 3, 2026 with a fix that ensures the dashboard waits for all access information to be available before determining whether a user can view a page.\n\nWe understand this was frustrating, particularly for users trying to manage billing or account settings via bookmarked or shared links. We apologize for the disruption and are adding test coverage for direct-link navigation to prevent similar regressions in the future.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-03T20:17:41.098Z", "resolved_inferred": false, "started_at": "2026-03-03T17:44:25.283Z", @@ -116,7 +116,7 @@ "body": "On February 26, 2026 at approximately 19:00 UTC, users began experiencing failures when connecting to their devices via balena device ssh. The command returned a generic \"host error\" with no further detail. The issue affected all CLI-based SSH access through the balena proxy.\n\nWeb terminal access and balena device tunnel remained functional throughout the incident and were available as workarounds. Devices themselves were online and healthy; the failure occurred at the authentication stage between the proxy and the device.\n\n**Root cause**\n\nThe balena proxy runs several internal processes. As a resource-saving measure, the service that handles web terminal connections had been disabled in the proxy pods dedicated to CLI SSH, since those pods do not serve web terminal sessions. What was not recognized at the time was that this service also carried the responsibility for loading SSH identity keys into the shared SSH agent used by the proxy. With it disabled, the proxy pods had no keys loaded and could not authenticate with devices, causing every SSH connection attempt to fail at the authentication stage.\n\n**Resolution**\n\nThe service that handles web terminal connections was temporarily re-enabled in the SSH proxy pods while a permanent fix was being developed, restoring SSH key availability and resolving the authentication failures. A permanent fix has since been deployed.\n\n**Follow-up**\n\nWe have decoupled the SSH key loading from the service that handles web terminal connections so that it is an independent initialization process in the proxy. We also added additional monitoring to ensure that SSH access through the proxy is adequately checked.\n\nWe sincerely apologize for the impact this caused. We are committed to improving our processes to prevent issues like these.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-27T03:39:08.670Z", "resolved_inferred": false, "started_at": "2026-02-26T19:20:35.588Z", @@ -129,7 +129,7 @@ "body": "On Feb 24, 2026 around ~17:20 UTC, a routine infrastructure deployment caused intermittent availability issues with Device URLs and web terminal access. Devices remained online and functional throughout, and CLI-based SSH access was unaffected.\n\nThe issue was caused by a configuration change that intentionally disabled several internal services no longer required by our proxy infrastructure. However, these services were still associated with pod health checks. A misconfigured override mechanism applied this change to production before it had passed through all required release gate checks, which would have caught the failing health checks.\n\nThe issue was identified quickly through automated monitoring and service was restored manually while a permanent fix was deployed. We have since corrected the underlying configuration override mechanism and are adding additional monitoring coverage to catch similar issues before they reach production.\n\nWe apologize for the disruption and thank you for your patience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-24T20:54:26.375Z", "resolved_inferred": false, "started_at": "2026-02-24T17:27:22.514Z", @@ -142,7 +142,7 @@ "body": "v2 delta generation service experienced failures from ~21:15 UTC Feb 9 to ~10:00 UTC Feb 10, 2026, due to a missing configuration dependency during a logic change.\n\n**Impact:**\n\n* v2 delta generation requests failed to complete\n* No data loss or security impact\n\n**Root Cause:** Recent logic changes were deployed without the required accompanying configuration update, preventing the service from completing v2 delta requests.\n\n**Resolution:** The logic changes were rolled back, restoring the service to its previous stable state.\n\n**Follow-up Actions:**\n\n* Prepare and deploy the permanent fix\n\nWe apologize for the disruption and any inconvenience this caused. We are committed to improving our processes to prevent similar issues in the future.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-11T00:02:30.160Z", "resolved_inferred": false, "started_at": "2026-02-10T09:33:42.929Z", @@ -155,7 +155,7 @@ "body": "Balena devices were unable to connect to Cloudlink on February 10, 2026, from approximately 02:26 GMT to 07:11 GMT due to an expired server certificate. Devices that were already connected to Cloudlink were unaffected unless the connection was terminated.\n\n**Root Cause:** The Cloudlink servers were using an expired certificate that was due for replacement. Consequently, incoming Cloudlink connections failed with a certificate verification error.\n\n**Resolution:** The certificate has been replaced, and Cloudlink servers were restarted to use the new certificate. Balena devices are expected to reconnect to Cloudlink within a few minutes after being disconnected due to the restart.\n\n**Follow-up Actions:**\n\n* Expand certificate expiry monitoring coverage to include all active certificates\n* Automate the certificate renewal process for Cloudlink\n\nWe apologize for any disruption this caused and appreciate your patience as we continue improving our processes and operations.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-10T07:56:34.794Z", "resolved_inferred": false, "started_at": "2026-02-10T04:05:10.780Z", @@ -168,7 +168,7 @@ "body": "Delta generation service experienced degraded performance from ~0900 UTC Feb 4 to ~1700 UTC Feb 5, 2026, due to 32-bit address space limitations affecting large image delta processing.\n\n**Impact:**\n\n* Delta generation timeout rate increased significantly for large container images\n* Users experienced slower image deployments and potential timeouts\n* No data loss or security impact\n\n**Root Cause:** Worker auto-discovery began routing some large delta generation tasks to 32-bit Docker sockets, causing memory constraint failures.\n\n**Resolution:** Corrected worker selection routing to only use 64-bit sockets for delta generation.\n\n**Follow-up Actions:**\n\n* Improve monitoring of delta generation performance and failure rates\n* Add alerting for threshold violations to detect similar issues faster\n\nWe apologize for the service interruption and any inconvenience this caused to your deployments. We are committed to improving our monitoring and alerting to prevent similar issues in the future.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-06T13:53:02.752Z", "resolved_inferred": false, "started_at": "2026-02-04T20:43:19.771Z", @@ -181,7 +181,7 @@ "body": "### What Happened\n\nOn January 28, our API experienced degraded performance due to a cascading pod failure triggered by infrastructure inconsistency.\n\n### Root Cause\n\nWe unexpectedly had one node running on an older generation CPU, which caused uneven load distribution. When that node's pod failed a health check under normal traffic spikes, it triggered a cascading failure across other pods \\(a \"thundering herd\" effect\\).\n\n### Resolution\n\nWe resolved the incident by:\n\n* Scaling up the number of API pods to restore capacity during recovery\n* Removing the infrastructure inconsistency that caused the initial failure\n* Adjusting health check configurations to prevent similar cascading failures\n\nWe apologize for any disruption this caused and appreciate your patience as we continue improving our platform's resilience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-28T22:06:19.336Z", "resolved_inferred": false, "started_at": "2026-01-28T18:54:18.743Z", @@ -194,7 +194,7 @@ "body": "Between 00:35 GMT and 01:00 GMT on January 28, 2026, users may have experienced intermittent connectivity issues with the balenaCloud API. Consequently, users may have had difficulty using the balenaCloud dashboard, and some devices also faced delays in reporting their current state to the backend.\n\n**Root Cause:** The incident was triggered during a planned configuration update to our environment. This update caused a brief, simultaneous restart of several core service components. As these services resumed, a high volume of concurrent device Cloudlink reconnections created a temporary surge in traffic. This surge exceeded the immediate processing capacity of our API backend, leading to increased latency and a temporary reduction in available service instances as they struggled to clear the request queue.\n\n**Resolution:** Our engineering team monitored the API as it processed the initial backlog. Service stabilized as the surge of reconnection requests subsided and API instances returned to healthy operating levels. Normal service was fully restored by 01:00 GMT.\n\n**Follow-up Actions:** We are reviewing the API deployment configuration and performance thresholds to better handle rapid spikes in traffic.\n\nWe sincerely apologize for the disruption to your workflow and appreciate your continued patience as we improve the resilience of our platform.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-28T01:00:00.000Z", "resolved_inferred": false, "started_at": "2026-01-28T01:00:00.000Z", @@ -207,7 +207,7 @@ "body": "Insufficient AWS compute capacity overloaded the remaining nodes. This high load caused readiness probes to fail, triggering API restarts that created a feedback loop of increasing pressure.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-24T09:38:25.418Z", "resolved_inferred": false, "started_at": "2025-12-23T16:32:02.019Z", @@ -220,7 +220,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-05T09:37:17.743Z", "resolved_inferred": false, "started_at": "2025-12-05T09:05:53.807Z", @@ -233,7 +233,7 @@ "body": "### Summary\n\nOn November 12, 2025, we experienced an incident causing increased build failures. This was traced to a significant network issue upstream of our hosting provider, which was outside their direct control. Build success rates returned to normal as of 17:15 UTC, and we formally closed the incident at 20:00 UTC after a period of extended monitoring.\n\n### What Happened\n\nA network issue between upstream service providers resulted in severe packet loss. This network degradation disrupted connections to our remote builder workers, causing an increase in builds failing with connection timeout errors \\(e.g., `ETIMEDOUT`\\).\n\n### Our Response & Mitigation\n\n* While the upstream network issue was being addressed, we brought additional builder workers online in unaffected regions to successfully route and process builds.\n* We were in communication with our hosting provider, who was monitoring the external network problem.\n\n### Resolution\n\n* **Recovery \\(17:15 UTC\\):** The upstream network provider resolved the issue, and we observed build failure rates and connection quality return to normal levels.\n* **Incident Closed \\(20:00 UTC\\):** After an extended period of monitoring to ensure all systems remained stable, we formally closed the incident.\n\nWe apologize for the disruption this caused.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-12T19:58:15.735Z", "resolved_inferred": false, "started_at": "2025-11-12T09:13:13.927Z", @@ -246,7 +246,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-20T23:03:43.933Z", "resolved_inferred": false, "started_at": "2025-10-20T08:45:35.303Z", @@ -259,7 +259,7 @@ "body": "An update to our kube-system infrastructure resulted in a disruptive pod rollout that left some devices disconnected from Cloudlink for up to 10 minutes. We apologize for the interruption and future updates to this component will be handled within planned maintenance windows.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-01T13:30:00.000Z", "resolved_inferred": false, "started_at": "2025-10-01T13:30:00.000Z", @@ -272,7 +272,7 @@ "body": "On **September 30th**, following a production deployment of a core component, a critical authorization failure affected the `balena device tunnel` command, preventing users from establishing port tunnel connections.\n\n### Summary of the Incident\n\nA subtle bug was introduced several weeks ago in a **small database query change** within a component. This change passed our standard review process and all pre-deployment testing, including unit tests utilizing mocked API endpoints.\n\nBecause of other pending changes, this component update was not immediately deployed. When it was finally released to production on September 30th, the query exhibited an unexpected incompatibility with the **live production API environment**.\n\nThe failure was not immediately apparent through our primary monitoring, but once the authorization issue was identified, our team quickly found the flawed query, deployed a patched component, and restored full functionality.\n\n### Root Cause and Timeline\n\n* **Change Introduction:** A small change to a database query was merged several weeks ago.\n* **Failed Validation:** The change passed unit tests and code review but failed to correctly interact with the real-world production API due to a subtle environmental or data-specific condition.\n* **Deployment & Failure:** On **September 30th**, the component was deployed. The authorization failure for `balena device tunnel` was subsequently observed.\n* **Resolution:** The bug was quickly diagnosed, the query was patched, and a fixed component was deployed to production, resolving the incident.\n\n### Corrective Actions\n\nWe are taking immediate steps to prevent this type of failure from recurring:\n\n1. **Unit Test Realism:** We have **updated our unit test mocks** to more accurately reflect invalid or non-standard production responses, ensuring future query changes are validated against real-world failure modes.\n2. **End-to-End Test Scheduling:** We are prioritizing the development and scheduling of a new **end-to-end test** specifically dedicated to validating the full functionality of the `device tunnel` command in a production-like environment. This will catch integration errors sooner.\n\nWe apologize for the interruption this caused to your workflow. We are committed to using this incident to improve the robustness and reliability of our continuous deployment process.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-30T21:56:45.703Z", "resolved_inferred": false, "started_at": "2025-09-30T19:47:47.495Z", @@ -285,7 +285,7 @@ "body": "#### Impact\n\nUsers were unable to access their devices via SSH through the web-terminal or the CLI. The CLI would return an error:\n\n`user does not have permission to access device`\n\nAn error in our Renovate configuration allowed our automation system to merge and deploy an unintended backend component to production. \n\n#### Resolution\n\nOur team quickly identified the issue and:\n\n1. Immediately rolled back the component to the previous verified version\n2. Restored remote SSH access for all affected devices\n3. Corrected the Renovate bot configuration to prevent similar automatic deployments\n\n#### Response\n\n* **Enhanced deployment controls:** We've restored our automation configuration to ensure all components must pass manual review before production deployment\n* **Improved monitoring:** We're considering implementing additional alerts to catch similar issues faster\n* **Process review:** We're reviewing our automated deployment processes to identify other potential gaps\n\nWe apologize for the disruption and appreciate your patience as we resolved this issue. If you continue to experience any problems, please contact our support team.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-17T22:01:28.892Z", "resolved_inferred": false, "started_at": "2025-09-17T20:10:15.971Z", @@ -298,7 +298,7 @@ "body": "The core problem stemmed from processing large files in the build context, which led to increased memory usage and, at times, network latency between regions.\n\n### Summary of Events\n\n* **Investigation and Identification \\(September 16, 2025\\):** We initially identified the issue as excessive memory consumption on our builder services.\n* **Temporary Mitigation \\(September 23, 2025\\):** We detected that network latency, particularly with larger build contexts, was contributing to the problem. We deployed temporary servers to mitigate this regional impact.\n* **Resolution \\(September 25, 2025\\):** The issue was resolved by implementing higher memory allocations on the builder services to handle the larger build context files and buffer memory issues.\n\n### Permanent Fixes and Structural Changes\n\nTo ensure long-term stability and prevent recurrence, our team implemented a series of comprehensive structural improvements focused on reducing memory usage, improving stream handling, and modernizing our codebase:\n\n* **Improved Build Stream Handling:** The most significant fix involved updating the system to buffer individual task build streams via the filesystem rather than memory. This leverages disk space, which scales much better and more cheaply than memory, to massively reduce the RSS memory usage.\n* **Streamlining and Modernization:** We undertook a broad effort to update and optimize how data streams are processed, including switching to native Node.js stream implementations \\(`stream.promises.pipeline`, `Transform`, `Passthrough`\\) to replace older, archived dependencies, which reduces the likelihood of memory leaks and edge cases.\n* **Other Enhancements:** We introduced various performance tweaks, such as avoiding reprocessing contract headers, improving error forwarding for stream failures \\(fixing a memory leak\\), and using model info to improve typings across the system.\n\nWe realize the recent incidents can be very disruptive and understand your frustration. Each of these incidents as well as their cause and steps to resolution have been documented on our status page. You can view the recent ones here on the history page with links to the details about each event: [**https://status.balena.io/history**](https://status.balena.io/history).\n\nAs you may know, the recent frequency of incidents is historically unusual for us. Our DevOps team worked overtime to resolve the issues as they arose. Our general process is not only to resolve, but also involve the broader team to make careful structural changes as preventative measures. For instance, we are reducing our reliance on hosting partners that may suffer from regional network network issues.\n\nThank you for your patience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-25T08:57:27.000Z", "resolved_inferred": false, "started_at": "2025-09-16T02:33:40.760Z", @@ -311,7 +311,7 @@ "body": "On Sept. 10th, around 13:30pm UTC, our alerting system reported intermittent elevated API errors. We quickly determined the cause of the incident to be an overly aggressive liveness probe rotating our API pods. A fix was deployed immediately.\n\nWhile the API was recovering, an automatic update of the Cloudlink pods occurred. As the API was slower to respond, device reconnections and SSH authentication were slower than usual, but steadily improving.\n\nThis apparent recovery was masking a different issue in the Cloudlink update itself\u2014an issue that was severely impacting container performance under high concurrency. This problem was only apparent at the scale of the production environment and was completely invisible at the lower scale of our development and testing environments.\n\nOnce the concurrency issue had been properly identified, we quickly reverted the update and Cloudlink returned to its expected performance level.\n\nIn the aftermath of this incident, we're making a few important changes in our Cloudlink testing, validation, and deployment protocols to better detect and automatically revert issues that would only happen in production.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-10T22:08:34.223Z", "resolved_inferred": false, "started_at": "2025-09-10T13:47:40.754Z", @@ -324,7 +324,7 @@ "body": "We experienced a temporary outage affecting ESR image downloads due to a recent system update. The issue was quickly identified and resolved by rolling back to a previous stable version while we address the underlying compatibility issue.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-27T20:45:04.280Z", "resolved_inferred": false, "started_at": "2025-08-27T16:48:35.907Z", @@ -337,7 +337,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-19T11:29:10.026Z", "resolved_inferred": false, "started_at": "2025-08-19T11:20:51.617Z", @@ -350,7 +350,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-14T15:01:04.397Z", "resolved_inferred": false, "started_at": "2025-08-14T13:52:15.670Z", diff --git a/api/v/bandwidth.json b/api/v/bandwidth.json index a22bc15a215b2ad7f49605896ff467b3d9292448..325ca6750d8e2bfbf02580a936fd10995c11178b 100644 --- a/api/v/bandwidth.json +++ b/api/v/bandwidth.json @@ -3,7 +3,7 @@ "slug": "bandwidth", "platform": "statuspage", "status_url": "http://status.bandwidth.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "partial", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "For a short period of time calls were not being signed with regards to STIR/SHAKEN. No call failure were observed with this incident. Proper call signing has been restored.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-09-03T21:09:57.707-04:00", "resolved_inferred": false, "started_at": "2026-09-03T21:09:57.645-04:00", @@ -25,7 +25,7 @@ "body": "Bandwidth can confirm all services are restored. This incident is resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-09-03T18:18:39.806-04:00", "resolved_inferred": false, "started_at": "2026-09-03T14:21:11.361-04:00", @@ -38,18 +38,18 @@ "body": "Our carrier has identified the cause of this incident and is working to complete repairs.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "started_at": "2026-09-03T11:06:19.491-04:00", "state": "identified", "title": "Bandwidth Local Market Impairment - 330 - Evansville, IN", -"updated_at": "2026-09-04T01:35:10.698-04:00", +"updated_at": "2026-09-04T05:15:12.474-04:00", "url": "https://stspg.io/17dwhqdjmnb6" }, { "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-09-03T07:55:13.185-04:00", "resolved_inferred": false, "started_at": "2026-09-03T05:53:29.579-04:00", @@ -62,7 +62,7 @@ "body": "Our carrier has completed all necessary repairs and Bandwidth can confirm all services are restored. This incident is resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-09-03T22:14:57.690-04:00", "resolved_inferred": false, "started_at": "2026-09-03T02:44:26.094-04:00", @@ -75,7 +75,7 @@ "body": "Market recovered, but carrier still working.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "started_at": "2026-09-02T22:50:11.821-04:00", "state": "monitoring", "title": "Bandwidth Local Market Impairment - 136 - Syracuse, NY", @@ -86,7 +86,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-09-03T13:54:53.582-04:00", "resolved_inferred": false, "started_at": "2026-09-02T13:33:28.046-04:00", @@ -99,7 +99,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-09-02T07:56:19.356-04:00", "resolved_inferred": false, "started_at": "2026-09-02T05:16:23.071-04:00", @@ -112,7 +112,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-09-02T06:50:47.754-04:00", "resolved_inferred": false, "started_at": "2026-09-02T01:44:45.397-04:00", @@ -125,7 +125,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-09-01T13:29:23.000-04:00", "resolved_inferred": false, "started_at": "2026-09-01T12:15:34.670-04:00", @@ -138,7 +138,7 @@ "body": "Final: Our carrier has completed all necessary repairs (SSL certificate update) and Bandwidth can confirm all services are restored. This incident is being resolved.\n\nStart Time: 2026-09-01 07:11:00 UTC\n\nEnd Time: 2026-09-01 08:55:00 UTC", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-09-01T07:11:00.484-04:00", "resolved_inferred": false, "started_at": "2026-09-01T04:40:03.683-04:00", @@ -151,7 +151,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-09-01T00:29:39.070-04:00", "resolved_inferred": false, "started_at": "2026-08-31T22:28:20.586-04:00", @@ -164,7 +164,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-31T17:13:57.259-04:00", "resolved_inferred": false, "started_at": "2026-08-31T13:05:07.077-04:00", @@ -177,7 +177,7 @@ "body": "For a brief period of time, some Toll Free port orders were delayed in provisioning due to network condition with a industry partner. At this time provisioning activities are processing as expected.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-31T11:46:14.000-04:00", "resolved_inferred": false, "started_at": "2026-08-31T11:46:14.000-04:00", @@ -190,7 +190,7 @@ "body": "For a brief period of time, a sub-set of Toll Free Origination voice traffic was unable to complete due to an off-network incident. This incident has been resolved and we are observing expected network behavior.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-28T11:54:56.000-04:00", "resolved_inferred": false, "started_at": "2026-08-28T11:54:56.000-04:00", @@ -203,7 +203,7 @@ "body": "For a brief period of time a subset of customer traffic, with a specific account settings were until not route traffic as expected. Teams have resolved this incident and are observing expected traffic behaviors.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-26T14:23:25.000-04:00", "resolved_inferred": false, "started_at": "2026-08-26T14:23:25.000-04:00", @@ -216,7 +216,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-25T11:01:40.495-04:00", "resolved_inferred": false, "started_at": "2026-08-25T09:01:27.027-04:00", @@ -229,7 +229,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-24T16:32:57.664-04:00", "resolved_inferred": false, "started_at": "2026-08-24T12:21:00.298-04:00", @@ -242,7 +242,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-21T11:09:44.745-04:00", "resolved_inferred": false, "started_at": "2026-08-21T09:57:40.884-04:00", @@ -255,7 +255,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-20T17:39:44.560-04:00", "resolved_inferred": false, "started_at": "2026-08-20T10:05:04.140-04:00", @@ -268,7 +268,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-20T09:13:23.376-04:00", "resolved_inferred": false, "started_at": "2026-08-20T08:17:33.631-04:00", @@ -281,7 +281,7 @@ "body": "For a brief period of time, number orders in the Bandwidth App were delayed or failed to complete. This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-19T07:16:30.000-04:00", "resolved_inferred": false, "started_at": "2026-08-19T07:16:30.000-04:00", @@ -294,7 +294,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-18T10:08:34.525-04:00", "resolved_inferred": false, "started_at": "2026-08-18T03:57:56.000-04:00", @@ -307,7 +307,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-17T19:24:26.684-04:00", "resolved_inferred": false, "started_at": "2026-08-17T12:50:45.739-04:00", @@ -320,7 +320,7 @@ "body": "Bandwidth teams resolved an incident where RCS Agents were deployed to the incorrect region resulting in potential traffic issues.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-17T06:04:38.000-04:00", "resolved_inferred": false, "started_at": "2026-08-17T06:04:38.000-04:00", @@ -333,7 +333,7 @@ "body": "For a brief period of time new telephone number orders were delayed in processing. At this time, orders are processing as expected, and we consider this incident resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-16T06:59:48.000-04:00", "resolved_inferred": false, "started_at": "2026-08-16T06:59:48.000-04:00", @@ -346,7 +346,7 @@ "body": "For a brief period of time, a sub-set of traffic transiting over porting of our ATL datacenter may have unexpectedly failed to complete as intended. At this time this portion of traffic has restored and our network is operating as expected.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-14T10:21:00.000-04:00", "resolved_inferred": false, "started_at": "2026-08-14T10:21:00.000-04:00", @@ -359,7 +359,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-14T14:15:33.674-04:00", "resolved_inferred": false, "started_at": "2026-08-14T09:30:06.396-04:00", @@ -372,7 +372,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-14T08:09:03.369-04:00", "resolved_inferred": false, "started_at": "2026-08-14T06:54:56.335-04:00", @@ -385,7 +385,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-11T16:10:20.071-04:00", "resolved_inferred": false, "started_at": "2026-08-11T12:39:22.296-04:00", @@ -398,7 +398,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-11T14:39:00.569-04:00", "resolved_inferred": false, "started_at": "2026-08-11T11:43:56.426-04:00", @@ -411,7 +411,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-12T00:30:39.000-04:00", "resolved_inferred": false, "started_at": "2026-08-10T23:38:03.093-04:00", @@ -424,7 +424,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-07T12:20:17.212-04:00", "resolved_inferred": false, "started_at": "2026-08-07T03:56:58.363-04:00", @@ -437,7 +437,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-05T02:50:07.665-04:00", "resolved_inferred": false, "started_at": "2026-08-04T10:15:00.988-04:00", @@ -450,7 +450,7 @@ "body": "For a brief period of a time, a small subset of voice traffic transversing our DFW datacenter experienced unexpected call failures. This incident is now resolved and we are observing expected network behavior.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-03T17:48:47.744-04:00", "resolved_inferred": false, "started_at": "2026-08-03T17:48:47.682-04:00", @@ -463,7 +463,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-03T08:39:36.022-04:00", "resolved_inferred": false, "started_at": "2026-08-03T07:40:28.773-04:00", @@ -476,7 +476,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-03T06:50:18.376-04:00", "resolved_inferred": false, "started_at": "2026-08-03T05:07:15.732-04:00", @@ -489,7 +489,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-31T19:02:15.948-04:00", "resolved_inferred": false, "started_at": "2026-07-30T13:51:12.043-04:00", @@ -502,7 +502,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-31T11:05:21.691-04:00", "resolved_inferred": false, "started_at": "2026-07-30T12:28:07.555-04:00", @@ -515,7 +515,7 @@ "body": "Customers experienced delays in receiving Delivery Receipts (DLRs) for messaging traffic. This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-30T10:00:00.000-04:00", "resolved_inferred": false, "started_at": "2026-07-30T10:00:00.000-04:00", @@ -528,7 +528,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-28T01:27:54.000-04:00", "resolved_inferred": false, "started_at": "2026-07-28T01:00:11.517-04:00", @@ -541,7 +541,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-27T11:40:12.867-04:00", "resolved_inferred": false, "started_at": "2026-07-27T11:30:18.570-04:00", @@ -554,7 +554,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-27T12:52:26.293-04:00", "resolved_inferred": false, "started_at": "2026-07-27T08:33:07.526-04:00", @@ -567,7 +567,7 @@ "body": "For a brief period of time, the Bandwidth App may have been unresponsive to users. At this time the App is stable and we consider this incident resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-23T04:30:00.000-04:00", "resolved_inferred": false, "started_at": "2026-07-23T04:30:00.000-04:00", @@ -580,7 +580,7 @@ "body": "For a brief period of time, a small subset of Programable Voice traffic experienced traffic disruption. Traffic has since stabilized and we consider this incident resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-22T19:23:00.000-04:00", "resolved_inferred": false, "started_at": "2026-07-22T19:23:00.000-04:00", @@ -593,7 +593,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-21T22:36:35.988-04:00", "resolved_inferred": false, "started_at": "2026-07-21T17:52:55.810-04:00", @@ -606,7 +606,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-21T20:07:15.550-04:00", "resolved_inferred": false, "started_at": "2026-07-21T13:35:41.893-04:00", @@ -619,7 +619,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-21T14:10:41.906-04:00", "resolved_inferred": false, "started_at": "2026-07-21T08:37:23.158-04:00", @@ -632,7 +632,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-20T08:53:07.874-04:00", "resolved_inferred": false, "started_at": "2026-07-20T06:07:10.215-04:00", @@ -645,7 +645,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-17T15:49:32.213-04:00", "resolved_inferred": false, "started_at": "2026-07-17T12:27:57.937-04:00", diff --git a/api/v/barracuda-msp.json b/api/v/barracuda-msp.json index cade49c193d88a31894c46ca1ad8465bf6c69422..899962b20d2cbb6dab6f3849da09701764d655fa 100644 --- a/api/v/barracuda-msp.json +++ b/api/v/barracuda-msp.json @@ -3,7 +3,7 @@ "slug": "barracuda-msp", "platform": "statuspage", "status_url": "https://mwrmm.statuspage.io", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-09T08:45:30.137-04:00", "resolved_inferred": false, "started_at": "2026-05-08T08:26:10.906-04:00", @@ -25,7 +25,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-09T14:04:32.898-04:00", "resolved_inferred": false, "started_at": "2026-03-02T09:25:24.878-05:00", @@ -38,7 +38,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-06T08:48:04.597-05:00", "resolved_inferred": false, "started_at": "2026-01-05T09:18:52.835-05:00", diff --git a/api/v/barracuda.json b/api/v/barracuda.json index d71c146e7ac37e6873fe1ff7673758fbd9642fd6..f7cee8aca41913984547109d01e4846ba4978a9a 100644 --- a/api/v/barracuda.json +++ b/api/v/barracuda.json @@ -3,7 +3,7 @@ "slug": "barracuda", "platform": "statuspage", "status_url": "https://status.barracuda.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "This incident is resolved", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-09-02T20:54:56.069Z", "resolved_inferred": false, "started_at": "2026-09-02T17:31:29.195Z", @@ -25,7 +25,7 @@ "body": "Incident resolved", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-09-01T11:23:44.219Z", "resolved_inferred": false, "started_at": "2026-09-01T01:08:58.234Z", @@ -38,7 +38,7 @@ "body": "The incident has been resolved and root cause investigation is proceeding.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-09-01T00:48:47.752Z", "resolved_inferred": false, "started_at": "2026-08-31T23:25:59.219Z", @@ -51,7 +51,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-25T13:39:14.011Z", "resolved_inferred": false, "started_at": "2026-08-24T14:17:14.177Z", @@ -64,7 +64,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-10T17:00:25.189Z", "resolved_inferred": false, "started_at": "2026-08-10T16:57:01.536Z", @@ -77,7 +77,7 @@ "body": "This incident has been resolved, and the impacted threat detection is now fully operational", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-05T17:37:00.979Z", "resolved_inferred": false, "started_at": "2026-08-05T15:47:36.134Z", @@ -90,7 +90,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-04T13:56:38.227Z", "resolved_inferred": false, "started_at": "2026-08-03T20:56:58.275Z", @@ -103,7 +103,7 @@ "body": "We have resolved an issue that was affecting some Authentication Services customers.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-31T18:02:46.445Z", "resolved_inferred": false, "started_at": "2026-07-31T17:36:49.345Z", @@ -116,7 +116,7 @@ "body": "This incident has been resolved, and the threat detection is now fully operational", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-29T17:55:09.963Z", "resolved_inferred": false, "started_at": "2026-07-29T16:16:47.564Z", @@ -129,7 +129,7 @@ "body": "We have resolved an issue that was affecting some Authentication Services customers.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-23T20:37:21.130Z", "resolved_inferred": false, "started_at": "2026-07-23T19:02:15.028Z", @@ -142,7 +142,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-07T13:21:36.666Z", "resolved_inferred": false, "started_at": "2026-07-07T12:22:34.759Z", @@ -155,7 +155,7 @@ "body": "This incident has been resolved, and the visibility of impacted data sources within the XDR dashboard (CSD) is now fully operational", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-07T17:40:50.641Z", "resolved_inferred": false, "started_at": "2026-07-06T15:15:33.350Z", @@ -168,7 +168,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-02T09:06:00.754Z", "resolved_inferred": false, "started_at": "2026-07-02T03:25:14.619Z", @@ -181,7 +181,7 @@ "body": "The engineering investigation is complete.\u00a0 The incident was caused by a datacenter device failure which has been addressed.\u00a0 Mail items which were deferred during the incident are now processed and available for search.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-02T15:11:30.338Z", "resolved_inferred": false, "started_at": "2026-07-01T23:40:56.492Z", @@ -194,7 +194,7 @@ "body": "We have successfully completed the scheduled system upgrade for the Email Security Events ingestion service in the US region. During the upgrade window, there was a temporary disruption in event ingestion from 06/22/2026 22:48:50 UTC to 06/23/2026 00:06:00 UTC.\u00a0\n\nWe acknowledge the potential impact this interruption may have had on your business operations and would like to assure you that the service has now been fully restored and is operating normally.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-23T00:24:54.728Z", "resolved_inferred": false, "started_at": "2026-06-22T21:07:59.500Z", @@ -207,7 +207,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-11T15:22:06.048Z", "resolved_inferred": false, "started_at": "2026-06-11T10:02:43.520Z", @@ -220,7 +220,7 @@ "body": "This incident has been resolved, and the events ingestion is now fully operational", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-03T22:12:23.687Z", "resolved_inferred": false, "started_at": "2026-06-03T20:44:40.644Z", @@ -233,7 +233,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-16T01:39:14.647Z", "resolved_inferred": false, "started_at": "2026-05-15T10:12:14.761Z", @@ -246,7 +246,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-12T13:59:30.158Z", "resolved_inferred": false, "started_at": "2026-05-12T15:39:11.140Z", @@ -259,7 +259,7 @@ "body": "This issue has been resolved for all customers and mail processing has been restored to full capacity. All items are now available for search results.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-01T20:03:46.552Z", "resolved_inferred": false, "started_at": "2026-04-30T07:54:34.155Z", @@ -272,7 +272,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-28T18:27:27.414Z", "resolved_inferred": false, "started_at": "2026-04-28T14:14:46.648Z", @@ -285,7 +285,7 @@ "body": "Our Datalake vendor has restored the Compute service, however there is no impact to our logs ingestion service in XDR. Hence, closing this incident", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-27T20:53:09.350Z", "resolved_inferred": false, "started_at": "2026-04-27T20:07:37.372Z", @@ -298,7 +298,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-11T10:01:59.329Z", "resolved_inferred": false, "started_at": "2026-04-23T09:15:44.500Z", @@ -311,7 +311,7 @@ "body": "This incident has been resolved by the datalake vendor, and the impacted service is fully operational", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-22T01:20:34.984Z", "resolved_inferred": false, "started_at": "2026-04-21T20:56:43.611Z", @@ -324,7 +324,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-16T06:37:35.031Z", "resolved_inferred": false, "started_at": "2026-04-15T16:48:15.300Z", @@ -337,7 +337,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-09T23:26:20.062Z", "resolved_inferred": false, "started_at": "2026-04-09T19:29:18.198Z", @@ -350,7 +350,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-03T19:37:57.475Z", "resolved_inferred": false, "started_at": "2026-04-02T00:29:24.282Z", @@ -363,7 +363,7 @@ "body": "This incident has been resolved, and the visibility of data sources within the XDR dashboard (CSD) is now fully operational", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-30T14:48:39.004Z", "resolved_inferred": false, "started_at": "2026-03-30T11:49:27.876Z", @@ -376,7 +376,7 @@ "body": "All customer impact has been resolved and mail processing is fully restored for all customers in the region.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-29T15:18:34.682Z", "resolved_inferred": false, "started_at": "2026-03-28T10:53:20.000Z", @@ -389,7 +389,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-27T17:57:12.513Z", "resolved_inferred": false, "started_at": "2026-03-27T13:18:13.044Z", @@ -402,7 +402,7 @@ "body": "We are currently experience ingestion delays with incident response.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-27T13:14:35.000Z", "resolved_inferred": false, "started_at": "2026-03-27T13:14:35.000Z", @@ -415,7 +415,7 @@ "body": "This incident has been resolved, and the Barracuda Email events ingestion in US is fully operational", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-30T16:31:38.139Z", "resolved_inferred": false, "started_at": "2026-03-27T08:25:33.334Z", @@ -428,7 +428,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-20T18:10:46.695Z", "resolved_inferred": false, "started_at": "2026-03-20T12:39:40.978Z", @@ -441,7 +441,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-27T18:07:44.668Z", "resolved_inferred": false, "started_at": "2026-02-27T12:24:00.949Z", @@ -454,7 +454,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-13T13:18:45.460Z", "resolved_inferred": false, "started_at": "2026-02-25T22:05:37.376Z", @@ -467,7 +467,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-25T09:10:01.494Z", "resolved_inferred": false, "started_at": "2026-02-24T10:15:05.327Z", @@ -480,7 +480,7 @@ "body": "This incident has been resolved, and o365 events ingestion in the US is now fully operational.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-03T22:29:21.143Z", "resolved_inferred": false, "started_at": "2026-02-24T04:02:20.831Z", @@ -493,7 +493,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-18T19:12:40.180Z", "resolved_inferred": false, "started_at": "2026-02-18T14:04:49.776Z", @@ -506,7 +506,7 @@ "body": "This incident is now resolved", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-17T17:20:38.067Z", "resolved_inferred": false, "started_at": "2026-02-16T04:01:12.000Z", @@ -519,7 +519,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-10T23:10:34.289Z", "resolved_inferred": false, "started_at": "2026-02-10T22:30:38.773Z", @@ -532,7 +532,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-11T15:06:50.095Z", "resolved_inferred": false, "started_at": "2026-02-10T17:27:43.000Z", @@ -545,7 +545,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-13T16:08:35.752Z", "resolved_inferred": false, "started_at": "2026-02-09T16:21:24.333Z", @@ -558,7 +558,7 @@ "body": "This incident has been resolved", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-18T18:24:39.679Z", "resolved_inferred": false, "started_at": "2026-02-09T15:50:00.312Z", @@ -571,7 +571,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-10T13:34:32.206Z", "resolved_inferred": false, "started_at": "2026-02-09T14:38:31.426Z", @@ -584,7 +584,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-04T14:36:00.047Z", "resolved_inferred": false, "started_at": "2026-02-03T18:30:38.770Z", @@ -597,7 +597,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-31T15:35:29.572Z", "resolved_inferred": false, "started_at": "2026-01-31T08:57:02.449Z", @@ -610,7 +610,7 @@ "body": "This incident has been resolved", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-06T16:54:04.127Z", "resolved_inferred": false, "started_at": "2026-01-29T14:32:46.965Z", @@ -623,7 +623,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-02T10:09:36.490Z", "resolved_inferred": false, "started_at": "2026-01-29T12:08:51.558Z", @@ -636,7 +636,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-23T11:01:10.979Z", "resolved_inferred": false, "started_at": "2026-01-22T22:02:18.445Z", @@ -649,7 +649,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-23T14:14:17.933Z", "resolved_inferred": false, "started_at": "2026-01-22T19:49:00.051Z", diff --git a/api/v/basedash.json b/api/v/basedash.json index f02bca2ce6db3a48ec915a3ea0624daa9217c5d5..cd6625457930251bba7f21c22d1d6bb04a2a5535 100644 --- a/api/v/basedash.json +++ b/api/v/basedash.json @@ -3,7 +3,7 @@ "slug": "basedash", "platform": "instatus", "status_url": "https://status.basedash.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": false, "first_watched": "2026-09-04T07:06:16Z", diff --git a/api/v/bentley-systems.json b/api/v/bentley-systems.json index dbf917cbb53d96a98688e6b8339452fa983cad00..c522836056c77d4f829f7213c51444a21a00de6f 100644 --- a/api/v/bentley-systems.json +++ b/api/v/bentley-systems.json @@ -3,7 +3,7 @@ "slug": "bentley-systems", "platform": "statuspage", "status_url": "https://statuspage.openground.bentley.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "Bentley has resolved the issues with the Identity Management Service.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-10T15:14:37.133Z", "resolved_inferred": false, "started_at": "2026-08-10T14:51:26.460Z", @@ -25,7 +25,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-18T14:37:20.315Z", "resolved_inferred": false, "started_at": "2026-03-18T09:40:51.365Z", @@ -38,7 +38,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-02T20:30:07.971Z", "resolved_inferred": false, "started_at": "2025-12-02T12:28:17.770Z", @@ -51,7 +51,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-01T16:47:57.984Z", "resolved_inferred": false, "started_at": "2025-12-01T10:13:31.299Z", @@ -64,7 +64,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-21T16:28:21.796Z", "resolved_inferred": false, "started_at": "2025-11-21T12:58:20.654Z", @@ -77,7 +77,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-29T23:42:10.013Z", "resolved_inferred": false, "started_at": "2025-10-29T17:12:56.481Z", @@ -90,7 +90,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-26T10:28:07.020Z", "resolved_inferred": false, "started_at": "2025-09-26T09:59:28.707Z", @@ -103,7 +103,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-09T09:53:20.853Z", "resolved_inferred": false, "started_at": "2025-09-09T09:14:29.438Z", @@ -116,7 +116,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-04T08:24:04.112Z", "resolved_inferred": false, "started_at": "2025-09-03T09:18:22.141Z", @@ -129,7 +129,7 @@ "body": "Investigating user access issues to OpenGround Admin Portal (no other services impacted)", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-28T05:00:00.000Z", "resolved_inferred": false, "started_at": "2025-08-27T23:00:00.000Z", @@ -142,7 +142,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-07-31T18:57:16.524Z", "resolved_inferred": false, "started_at": "2025-07-31T14:23:04.841Z", @@ -155,7 +155,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-07-31T13:59:41.922Z", "resolved_inferred": false, "started_at": "2025-07-31T11:33:06.973Z", diff --git a/api/v/bettercloud.json b/api/v/bettercloud.json index 385fc764bbeaa40fba4cbedc942cd3195479ee53..5aca75edcd452c6bcf0bda67dd0b1bb232f34847 100644 --- a/api/v/bettercloud.json +++ b/api/v/bettercloud.json @@ -3,7 +3,7 @@ "slug": "bettercloud", "platform": "statuspage", "status_url": "https://status.bettercloud.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "We have remediated the issue that resulted in the suspension of a limited number of Bamboo HR integrations.\n\nWe advise any customer utilizing the Bamboo HR Integration within BetterCloud User Automation to check the Integration Center and manually reconnect as needed using the directions in our help center article.\n\nWe apologize for any inconvenience this issue may have caused. If you have any questions, please reach out to our Support team by emailing support@bettercloud.com.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-09-02T18:36:36.911-04:00", "resolved_inferred": false, "started_at": "2026-09-01T17:30:40.501-04:00", @@ -25,7 +25,7 @@ "body": "The issue with our Chat service has been restored. We appreciate your patience! If you have any questions, please contact Support: support@bettercloud.com", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-05T18:28:00.351-04:00", "resolved_inferred": false, "started_at": "2026-08-05T16:14:20.375-04:00", @@ -38,7 +38,7 @@ "body": "We have remediated the issue that resulted in the suspension of a limited number of Office 365 integrations.\n\nBetterCloud was able to automatically reconnect a subset of customer affected Integrations. However, we advise any customer utilizing the Office 365 Integration within BetterCloud User Automation to check the Integration Center and manually reconnect as needed using the directions in our help center article.\n\nWe apologize for any inconvenience this issue may have caused. If you have any questions, please reach out to our Support team by emailing support@bettercloud.com.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-19T18:30:15.861-04:00", "resolved_inferred": false, "started_at": "2026-05-19T10:51:32.553-04:00", @@ -51,7 +51,7 @@ "body": "We have monitored for stability and concluded this issue is resolved. \n\nThis incident prevented the Workflow's UI and the Action menu from loading correctly. Further analysis showed this incident caused a delay for Workflows executed manually/scheduled to execute via the UI (ie: On Demand). All impacted Workflows have since processed as expected. \n\nWe apologize for any inconvenience this issue may have caused. If you have any questions, please contact our support team by emailing support@bettercloud.com.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-04T14:47:26.076-04:00", "resolved_inferred": false, "started_at": "2026-05-04T09:14:02.930-04:00", @@ -64,7 +64,7 @@ "body": "We have resolved the issue preventing certain Workflows from triggering. All Workflows that were expected to trigger during the outage have been reprocessed. Thank you for your patience and understanding. If you have any questions or concerns, please reach out to support@bettercloud.com", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-01T23:42:44.333-04:00", "resolved_inferred": false, "started_at": "2026-05-01T15:14:59.962-04:00", @@ -77,7 +77,7 @@ "body": "We have implemented a fix for the issue causing delays in action execution for a subset of customers. We apologize for any inconvenience this issue may have caused. If you have any questions, please contact our Support Team at support@bettercloud.com.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-30T19:11:24.373-04:00", "resolved_inferred": false, "started_at": "2026-04-30T17:32:34.359-04:00", @@ -90,7 +90,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-28T09:25:09.831-04:00", "resolved_inferred": false, "started_at": "2026-04-24T17:11:07.126-04:00", @@ -103,7 +103,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-22T16:34:19.378-04:00", "resolved_inferred": false, "started_at": "2026-04-22T10:30:01.892-04:00", @@ -116,7 +116,7 @@ "body": "We have resolved the issue affecting certain customers that was resulting in a File Governance insights data issue. We apologize for any inconvenience this issue may have caused. If you have any questions, please contact our Support Team at support@bettercloud.com.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-16T12:29:57.461-04:00", "resolved_inferred": false, "started_at": "2026-04-14T13:44:21.191-04:00", @@ -129,7 +129,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-19T13:55:46.802-05:00", "resolved_inferred": false, "started_at": "2026-02-19T10:49:53.893-05:00", @@ -142,7 +142,7 @@ "body": "We have implemented a fix that was causing Workflow Action delays for a subset of customers. We apologize for any inconvenience this issue may have caused. If you have any questions, please contact our Support Team at support@bettercloud.com.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-05T17:27:33.723-05:00", "resolved_inferred": false, "started_at": "2026-01-05T16:54:33.407-05:00", @@ -155,7 +155,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-19T17:52:43.954-05:00", "resolved_inferred": false, "started_at": "2025-12-19T14:47:25.897-05:00", @@ -168,7 +168,7 @@ "body": "Some users experienced errors when when attempting to access BetterCloud Google Administration (g.bettercloud.com) between approximately 6pm ET on 12/3 and 1am ET on 12/4. The issue has been corrected and access has been restored.\n\nA related issue causing certain tasks including signature policies, sheet imports/exports, and reports to take longer than expected was fixed today. If you have any questions, please contact our Support Team.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-03T18:00:00.000-05:00", "resolved_inferred": false, "started_at": "2025-12-03T18:00:00.000-05:00", @@ -181,7 +181,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-04T17:04:57.853-05:00", "resolved_inferred": false, "started_at": "2025-11-03T13:40:52.061-05:00", @@ -194,7 +194,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-26T14:32:41.317-04:00", "resolved_inferred": false, "started_at": "2025-09-26T12:29:58.043-04:00", @@ -207,7 +207,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-10T09:16:32.884-04:00", "resolved_inferred": false, "started_at": "2025-09-04T10:06:19.000-04:00", diff --git a/api/v/bexio.json b/api/v/bexio.json index 1845fb81134e26ebd91b829a05c3bbf880283032..5e15afab80b93269142ce38e6c8667f2d1fee0b0 100644 --- a/api/v/bexio.json +++ b/api/v/bexio.json @@ -3,27 +3,27 @@ "slug": "bexio", "platform": "statuspage", "status_url": "https://www.bexio-status.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "degraded", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", "incidents": [ { -"body": "Our email partner's server is currently experiencing limited availability, causing intermittent delays in sending authentication emails. Our technical team is working at full speed to resolve the issue.", +"body": "Currently, system emails from bexio (e.g., forgot password, 2FA codes, company invitations, sending of your invoices, etc.) are experiencing delivery delays due to technical issues with our email provider. We are already working on a solution.", "first_seen": "2026-09-04T09:06:33Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "started_at": "2026-09-04T10:55:27.393+02:00", "state": "investigating", "title": "2FA: emails are not being sent", -"updated_at": "2026-09-04T10:55:27.544+02:00", +"updated_at": "2026-09-04T11:33:35.842+02:00", "url": "https://stspg.io/27sbjs3lxjv3" }, { "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-09T14:44:27.674+02:00", "resolved_inferred": false, "started_at": "2026-07-09T14:32:29.794+02:00", @@ -36,7 +36,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-08T11:09:03.076+02:00", "resolved_inferred": false, "started_at": "2026-07-08T10:24:07.170+02:00", @@ -49,7 +49,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-26T13:13:06.800+02:00", "resolved_inferred": false, "started_at": "2026-06-25T17:02:58.960+02:00", @@ -62,7 +62,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-02T17:40:17.171+02:00", "resolved_inferred": false, "started_at": "2026-06-02T17:30:52.979+02:00", @@ -75,7 +75,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-21T15:48:48.750+02:00", "resolved_inferred": false, "started_at": "2026-04-21T10:58:27.436+02:00", @@ -88,7 +88,7 @@ "body": "You can now send emails again without any restrictions. \nThank you very much for your patience and your trust in bexio", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-24T17:29:47.427+01:00", "resolved_inferred": false, "started_at": "2026-03-24T08:40:50.877+01:00", @@ -101,7 +101,7 @@ "body": "The logo in your bexio profile will now be displayed as usual. Thank you for your patience and understanding.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-23T13:14:43.008+01:00", "resolved_inferred": false, "started_at": "2026-03-23T09:32:50.352+01:00", @@ -114,7 +114,7 @@ "body": "Emails are now being sent reliably again. The limit of 20 documents per hour and a maximum of 5 recipients remains in place for the time being.\nThe delay in email delivery has also been resolved.\n\nWe apologise for any inconvenience caused and thank you for your understanding.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-23T13:15:40.701+01:00", "resolved_inferred": false, "started_at": "2026-03-20T08:24:26.820+01:00", @@ -127,7 +127,7 @@ "body": "developer.bexio.com is available again. We apologise for any inconvenience caused.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-19T16:59:41.840+01:00", "resolved_inferred": false, "started_at": "2026-03-19T16:20:29.279+01:00", @@ -140,7 +140,7 @@ "body": "Bank transactions have been successfully processed and imported. Contact imports are also available again. You can now use bexio as usual. Thank you for your patience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-17T13:02:26.098+01:00", "resolved_inferred": false, "started_at": "2026-03-17T10:12:41.753+01:00", @@ -153,7 +153,7 @@ "body": "Bills are being processed as usual again. However, we are still working on the final data migration and kindly ask for a little more patience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-16T16:59:16.030+01:00", "resolved_inferred": false, "started_at": "2026-03-16T15:30:23.458+01:00", @@ -166,7 +166,7 @@ "body": "The error has been fixed. The purchase module is now fully available again. Thank you for your understanding.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-03T14:47:16.000+01:00", "resolved_inferred": false, "started_at": "2026-03-03T11:05:07.117+01:00", @@ -179,7 +179,7 @@ "body": "The error has been fixed. The purchase module is now fully available again. Thank you for your understanding.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-02T16:45:27.455+01:00", "resolved_inferred": false, "started_at": "2026-03-02T13:59:35.890+01:00", @@ -192,7 +192,7 @@ "body": "The error has been fixed: All bills and expenses will now be posted immediately and reliably again. The entire purchase area is now available to you again as usual. We apologize for any inconvenience caused and thank you for your patience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-17T15:36:37.826+01:00", "resolved_inferred": false, "started_at": "2026-02-17T14:06:43.745+01:00", @@ -205,7 +205,7 @@ "body": "We were able to resolve the issue. The banking interface is available again as expected. We apologise for any inconvenience caused.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-27T13:39:25.338+01:00", "resolved_inferred": false, "started_at": "2026-01-27T12:02:57.161+01:00", @@ -218,7 +218,7 @@ "body": "Issue resolved", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-19T10:33:01.585+01:00", "resolved_inferred": false, "started_at": "2026-01-19T08:55:31.949+01:00", @@ -231,7 +231,7 @@ "body": "bexio is fully operational again. We apologize for the inconvenience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-18T16:09:14.062+01:00", "resolved_inferred": false, "started_at": "2025-12-18T15:40:07.113+01:00", @@ -244,7 +244,7 @@ "body": "We were able to resolve the issue. A fix has been implemented and we are monitoring the results.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-14T18:04:50.491+01:00", "resolved_inferred": false, "started_at": "2025-12-14T17:04:30.984+01:00", @@ -257,7 +257,7 @@ "body": "We were able to resolve the issue. The unexpected unavailability of bexio was caused by a problem with our partner Cloudflare.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-05T11:20:33.427+01:00", "resolved_inferred": false, "started_at": "2025-12-05T10:01:56.625+01:00", @@ -270,7 +270,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-25T10:10:47.851+01:00", "resolved_inferred": false, "started_at": "2025-11-25T08:51:53.196+01:00", @@ -283,7 +283,7 @@ "body": "We were able to resolve the issue with one of our network providers.\nbexio is now available again with its usual reliability and speed.\nWe thank you for your understanding and apologise for any inconvenience caused.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-20T21:03:55.229+01:00", "resolved_inferred": false, "started_at": "2025-11-20T08:34:08.214+01:00", @@ -296,7 +296,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-13T09:17:01.351+01:00", "resolved_inferred": false, "started_at": "2025-11-12T15:49:39.229+01:00", @@ -309,7 +309,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-22T15:02:09.559+02:00", "resolved_inferred": false, "started_at": "2025-10-22T12:00:21.000+02:00", @@ -322,7 +322,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-22T09:47:06.393+02:00", "resolved_inferred": false, "started_at": "2025-10-22T09:21:38.721+02:00", @@ -335,7 +335,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-10T13:24:11.484+02:00", "resolved_inferred": false, "started_at": "2025-09-10T09:18:00.756+02:00", diff --git a/api/v/bigleaf.json b/api/v/bigleaf.json index 39c93c723ab3155b067ab1c39b115a177ef077d6..453072127373b31b3f038e4d200a390b2dab83e3 100644 --- a/api/v/bigleaf.json +++ b/api/v/bigleaf.json @@ -3,7 +3,7 @@ "slug": "bigleaf", "platform": "statuspage", "status_url": "https://status.bigleaf.net", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-08T11:11:46.329-07:00", "resolved_inferred": false, "started_at": "2026-07-08T09:55:25.499-07:00", @@ -25,7 +25,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-18T11:46:46.220-07:00", "resolved_inferred": false, "started_at": "2026-06-18T07:39:23.519-07:00", @@ -38,7 +38,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-30T13:00:26.073-07:00", "resolved_inferred": false, "started_at": "2026-04-30T10:53:48.316-07:00", @@ -51,7 +51,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-20T13:30:27.173-08:00", "resolved_inferred": false, "started_at": "2026-02-20T11:00:43.150-08:00", @@ -64,7 +64,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-04T15:08:12.286-08:00", "resolved_inferred": false, "started_at": "2025-12-04T11:31:50.952-08:00", @@ -77,7 +77,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-02T14:57:32.506-07:00", "resolved_inferred": false, "started_at": "2025-10-02T12:54:23.372-07:00", @@ -90,7 +90,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-26T13:30:31.829-07:00", "resolved_inferred": false, "started_at": "2025-09-26T10:01:59.408-07:00", @@ -103,7 +103,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-18T10:28:19.293-07:00", "resolved_inferred": false, "started_at": "2025-09-18T09:19:53.031-07:00", @@ -116,7 +116,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-12T07:30:30.912-07:00", "resolved_inferred": false, "started_at": "2025-09-12T05:41:56.112-07:00", @@ -129,7 +129,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-11T14:41:40.451-07:00", "resolved_inferred": false, "started_at": "2025-09-11T13:07:52.316-07:00", @@ -142,7 +142,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-22T11:39:50.721-07:00", "resolved_inferred": false, "started_at": "2025-08-22T10:31:44.978-07:00", @@ -155,7 +155,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-08T11:34:38.011-07:00", "resolved_inferred": false, "started_at": "2025-08-08T10:58:28.312-07:00", diff --git a/api/v/binary-lane.json b/api/v/binary-lane.json index 8c3a408ee99f7f956983b3ed30b16940caf73866..f15cff263d9fd46e279b7b93c614875f5fce55d2 100644 --- a/api/v/binary-lane.json +++ b/api/v/binary-lane.json @@ -3,7 +3,7 @@ "slug": "binary-lane", "platform": "statuspage", "status_url": "http://status.binarylane.com.au", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "This update formally closes the incident of Friday 15 May.\n\nTo summarise the event: from 12:30 PM AEST our network was targeted by a large-scale volumetric denial-of-service attack directed evenly across our entire public IP space \u2014 the largest we have observed. The volume exceeded the international transit capacity of our primary upstream, who dropped our connectivity several times to protect their wider network. Services were kept reachable via alternate paths through the afternoon, with general availability restored by 7:12 PM that evening and all city POPs returned to their normal direct-service configuration by Monday 18 May.\n\nAs stated throughout: this was a network-level attack on reachability. It was not a breach or intrusion, no customer systems were accessed, and no customer data was involved. Our engagement with the Australian Signals Directorate on this incident has concluded from our side, with all requested material provided or accounted for. We again thank our customers for their patience and the constructive feedback we received. This incident is now resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-08T11:11:36.582+10:00", "resolved_inferred": false, "started_at": "2026-05-15T13:19:51.436+10:00", @@ -25,7 +25,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-10T16:07:01.091+10:00", "resolved_inferred": false, "started_at": "2026-05-10T14:26:19.520+10:00", @@ -38,7 +38,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-25T12:24:12.185+10:00", "resolved_inferred": false, "started_at": "2026-04-24T20:57:50.547+10:00", @@ -51,7 +51,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-09T18:03:08.531+11:00", "resolved_inferred": false, "started_at": "2026-03-09T15:51:11.650+11:00", @@ -64,7 +64,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-04T11:16:15.620+10:00", "resolved_inferred": false, "started_at": "2025-08-01T10:51:23.369+10:00", diff --git a/api/v/bitbucket.json b/api/v/bitbucket.json index 3b5fa7a4d7d4e46938f3eb9a142734bcdae7bc7b..498bb99b6ae1d713f553c0400111a1874c984538 100644 --- a/api/v/bitbucket.json +++ b/api/v/bitbucket.json @@ -3,7 +3,7 @@ "slug": "bitbucket", "platform": "statuspage", "status_url": "https://bitbucket.status.atlassian.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "On July 31, 2026, affected Bitbucket Cloud users for some customers may have experienced failures loading the site and impacts to associated pipelines. The issue has now been resolved, and the service is operating normally for all affected customers.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-31T15:38:29.093Z", "resolved_inferred": false, "started_at": "2026-07-31T13:09:55.121Z", @@ -25,7 +25,7 @@ "body": "On June 11, 2026, Bitbucket users may have experienced performance degradation affecting Bitbucket OAuth login. The issue has now been resolved, and the service is operating normally for all affected customers.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-12T00:14:47.526Z", "resolved_inferred": false, "started_at": "2026-06-11T22:48:40.863Z", @@ -38,7 +38,7 @@ "body": "### Summary\n\nOn May 14, 2026, between 04:30 and 05:26 UTC, Atlassian customers experienced widespread service disruption across multiple Atlassian Cloud products. The issue was caused by a race condition in our internal deployment orchestration platform during a routine rollback operation of a core identity service in the us-east region. This race condition resulted in insufficient capacity for the identity service in the affected region which started returning errors to dependent products. The incident was detected within a minute by automated monitoring systems and mitigated in 56 minutes.\n\n### **IMPACT**\n\nDuring the incident, customers attempting to access Atlassian Cloud products in the us-east region experienced authentication and permission failures and were unable to access services. Customers also experienced errors when accessing the support portal until Atlassian fell back to an alternate support method. This was caused by a core identity service in the us-east region becoming unavailable. Affected products included Atlassian Administration, Atlassian Analytics, Bitbucket, Compass, Confluence, Jira, Jira Product Discovery, Jira Service Management and Trello. Some users outside us-east may have been affected in certain scenarios.\n\n### **ROOT CAUSE**\n\nThe incident was caused by a race condition in our internal deployment orchestration platform during a routine rollback operation of a core identity service in the us-east region. This race condition resulted in insufficient capacity for the identity service in the affected region which started returning errors to dependent products.\n\n### **REMEDIAL ACTIONS PLAN & NEXT STEPS**\n\nWe know that outages impact your productivity. Atlassian is prioritizing the following actions to help prevent similar incidents in future:\n\n* **Refine deployment orchestration safeguards**\n\n * Harden our deployment platform to prevent similar race conditions or resulting capacity loss during a rollback operation.\n * Streamline mitigation steps when a service becomes unavailable in a region.\n \n* **Reduce cross-region impact**\n\n * Improve regional isolation and fallback handling so an issue affecting a single region is less likely to impact customers or product functionality in other regions.\n \n\nWe recognise how critical reliable access to Atlassian products is for our customers' productivity, and we apologize to customers who were impacted by this incident.\n\nThanks,\n\nAtlassian", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-14T06:48:26.114Z", "resolved_inferred": false, "started_at": "2026-05-14T05:03:33.069Z", @@ -51,7 +51,7 @@ "body": "All dates and times below are in UTC unless stated otherwise.\n\n### Summary\n\nOn May 8, 2026 between 00:22 and 06:08, one of our hosting providers suffered a significant incident in a specific availability zone in prod-east which led to Atlassian customers experiencing degraded performance and delays of background operations and automation execution.\n\nThe incident started on May 8, 2026 at 00:22 and was detected within 4 minutes by automated monitoring systems. Our teams worked to restore core access by 06:08. Final cleanup of backlogged processes and minor issues progressed in stages from there was completed iteratively by 19:15.\n\n### **IMPACT**\n\nThe primary infrastructure affected in this incident was the event processing pipeline in the prod-east region, which distributes events between Atlassian services and underpins background operations such as automation execution, search indexing, notifications, permission synchronisation.\n\n* Between 00:22 and 06:08, an infrastructure incident in our hosting provider triggered an ingestion failure in our event processing pipeline.\n* At 02:50, event ingestion was failed over to an unaffected availability zone, progressively restoring live event flows.\n* At 06:08, reliability for new ingestion in prod-east recovered to 100%. The remaining work was to drain the accumulated cross-region backlog of messages, which completed by 17:00.\n* By 18:48, Automation had processed their backlog of events that were created while processing\n\n**Automation**\n\nBetween 00:22 and 02:50, customers with automation rules triggered by events originating from the prod-east region experienced a significant reduction in rule executions. During this window, event-triggered automation rules were not firing because the events that trigger them were not being delivered. Rule authoring, saving, and rules triggered manually, by schedules, or by webhooks were not affected.\n\nAt 02:50, the event processing infrastructure failed over to an unaffected availability zone, restoring delivery of live events to Automation and allowing new event-triggered rules to begin executing normally. However, events generated during the impact window still needed to be replayed before delayed automations could be processed.\n\nBeginning at 08:28, upstream services replayed their queued events in a coordinated sequence, and all replayed events were processed by 18:48. During the replay window, customers may have experienced automation rules executing later than expected, a small number of rules reaching daily processing limits due to compressed replay, and time-sensitive rules not completing as expected if internal timeout thresholds were exceeded.\n\n**Jira and Jira Service Management**\n\nBetween 00:22 and 02:50, customers with tenants hosted in the prod-east region experienced disruption to Jira and Jira Service Management event-driven features like automation, along with a short period of elevated errors during infrastructure failover. Core Jira experiences, including issue view, boards, and project navigation, remained available throughout the incident.\n\nJira event delivery was affected by the primary impact, preventing downstream services from receiving issue lifecycle events. This affected automation rules triggered by Jira events, AI agent orchestration in Jira, notifications for issue updates and transitions, search indexing for newly created or modified issues, and event-driven integrations between Jira and other Atlassian products.\n\nAt 02:50, the event processing infrastructure failed over to an unaffected availability zone, restoring delivery of new events. All events generated during the impact window were retained in a recovery queue and required replaying. This began at 08:28 and completed at 12:00. During the replay window, customers may have experienced automation rules executing later than expected, delayed notifications arriving hours after the triggering action, temporary gaps in search results for content created or modified during the impact window, and AI agent workflows not completing as expected where internal timeout thresholds were exceeded.\n\n**Confluence**\n\nBetween 00:22 and 02:50, customers with tenants hosted in the prod-east region experienced disruptions to event-driven services in Confluence. This resulted in delays to search indexing, notifications, automation rule execution, and permission synchronisation.\n\nThe underlying event processing infrastructure failed over to an unaffected availability zone, after which live Confluence operations resumed normally. However, events generated during the impact window were queued for replay, and some background services remained delayed until that replay and related validation work completed.\n\nBetween 10:14 and 17:00, a bulk replay of all the queued tenant replay tasks was completed to restore data consistency. During and immediately after the replay window, customers may have experienced search results not reflecting content created or modified during the outage, delayed or missing notifications for page and comment activity, automation rules firing later than expected, and brief delays in permission synchronisation for tenants relying on incremental identity sync.\n\n**Bitbucket and Pipelines**\n\nBetween 00:22 and 06:08, customers using Bitbucket and Pipelines experienced failures and degraded functionality across event-driven workflows. Core Git operations, including push, pull, and clone, were not affected and continued to operate normally throughout the incident.\n\nAutomatic pipeline triggers initiated by push or pull request events were unavailable during the impact window. Merge queues, custom merge checks, Forge-based triggers, workspace permission changes, and some workspace provisioning flows were also affected. Customers using merge queues were unable to merge pull requests, and some pipeline steps failed because queued work contributed to elevated concurrency limits.\n\nAt approximately 03:57, Pipelines was reconfigured to consume events through an alternative path, restoring automatic pipeline triggering. Merge queues, custom merge checks, Forge triggers, and other affected workflows were progressively restored as the underlying event processing infrastructure recovered. All Bitbucket and Pipelines services were confirmed fully operational by 06:08. After recovery, queued events were reviewed and replayed where safe to restore data consistency for billing, audit logging, and other background processes.\n\n**Identity Services**\n\nBetween 00:22 and 02:50, customers with tenants hosted in the prod-east region experienced delays in the propagation of identity and group membership changes to downstream Atlassian products. Core identity operations, including authentication, login, and direct group management actions, were not affected and continued to function normally throughout the incident.\n\nThe impact was limited to asynchronous, event-driven operations that depend on the event processing pipeline. This included delays in delivering group membership and user profile changes to products such as Jira and Confluence, which affected downstream permission synchronisation and crowd sync flows. A small number of SCIM-based identity synchronisation and site provisioning workflows also experienced temporary delays.\n\nAfter the event processing infrastructure recovered, backed-up identity and group directory events were replayed where required, restoring downstream consistency for affected products. No identity data was lost. Group membership changes, user profile updates, and provisioning-related events that occurred during the impact window were retained and processed after recovery.\n\n### **REMEDIAL ACTIONS PLAN & NEXT STEPS**\n\nWe know outages impact your productivity. While our monitoring and recovery processes helped us respond quickly, this incident highlighted opportunities to further strengthen resilience for event-driven services.\n\nWe are prioritizing improvements that will:\n\n* **Enhance failover coverage** so critical event processing can recover more smoothly during infrastructure disruptions.\n* **Strengthen recovery handling** so replayed events can be processed more quickly.\n\nWe apologize to customers whose services were impacted during this incident; we are taking immediate steps to improve the platform\u2019s performance and availability.\n\nThanks,\n\nAtlassian Customer Support.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-08T19:45:31.415Z", "resolved_inferred": false, "started_at": "2026-05-08T01:31:38.240Z", @@ -64,7 +64,7 @@ "body": "On April 16 at 8:00PM UTC Bitbucket Pipelines users may have experienced performance degradation running new pipelines. The issue has now been resolved, and the service is operating normally for all affected customers.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-16T20:44:41.288Z", "resolved_inferred": false, "started_at": "2026-04-16T20:23:10.857Z", @@ -77,7 +77,7 @@ "body": "### Summary\n\nOn April 13, 2026, between 05:49 and 06:29 UTC, customers experienced failures when attempting to log in, sign up, reset passwords, and complete multi-factor authentication flows across Atlassian cloud products. Approximately 90% of authentication requests failed during the peak impact window, affecting users in the US East and EU regions. The incident was mitigated within 40 minutes through manual intervention, and full service was restored by 06:29 UTC.\n\n### **IMPACT**\n\n* **Duration**: ~40 minutes \\(05:49\u201306:29 UTC, April 13, 2026\\)\n* **Affected regions**: US East and EU \\(authentication infrastructure serves EU traffic from US East, with traffic primarily from EU at this time of day\\).\n* **Affected products**: All Atlassian cloud products requiring authentication, including Jira, Confluence, Jira Service Management, and Trello.\n* **Customer experience**: Users attempting to log in, sign up, reset passwords, or complete MFA flows received errors. Users already logged in with active sessions were unaffected.\n\n### **ROOT CAUSE**\n\nThis incident had several contributing factors that combined to produce a failure that the system could not recover from without manual intervention.\n\n**The primary cause** was a recently enabled change that caused our authentication infrastructure to retry requests to a downstream identity service when those requests were slow to respond. This retry behaviour was rolled out to 100% of traffic earlier the same day. Under normal conditions this would be benign, but it meant that any slowness in the downstream service was amplified. Since multiple upstream services were also independently retrying their own failed requests, the amplification compounded further into a retry storm.\n\n**The trigger** was a burst of legitimate user traffic. A pattern of many parallel link preview requests for a single user caused a concentrated load spike on a downstream identity service, pushing its response times above the retry threshold. On its own, this kind of spike had occurred many times before and always recovered. With the retry amplification now in effect, the spike instead created a runaway feedback loop: slow responses caused retries, retries increased load, increased load caused slower responses, preventing recovery.\n\nThe incident was mitigated by manually scaling up the downstream identity service to provide sufficient capacity to absorb the amplified load. Once scaled, the service recovered immediately, bringing authentication error rates to zero within one minute.\n\n**REMEDIAL ACTIONS PLAN & NEXT STEPS**\n\nWe are taking the following actions designed to prevent recurrence and improve our resilience:\n\n1. **Immediate**: The retry-on-timeout change has been disabled.\n2. **Load shedding and self-healing**: We are adding load shedding capabilities to our authentication services so that they can automatically shed excess load and self-recover during traffic spikes, without requiring action before automatic scaling starts.\n3. **Reducing request fan-out**: We are reviewing patterns where a single user action can generate many parallel downstream requests, and will introduce methods where possible to reduce the amplification potential.\n\nWe apologize to customers whose services were interrupted by this incident and we are taking immediate steps to improve the platform\u2019s reliability.\n\nThanks,\n\nAtlassian Customer Support", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-13T10:17:20.730Z", "resolved_inferred": false, "started_at": "2026-04-13T07:29:45.600Z", @@ -90,7 +90,7 @@ "body": "We have successfully mitigated the incident, and the affected service is now fully operational. Our teams have verified that normal functionality has been restored and the service is performing as expected.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-12T12:33:39.767Z", "resolved_inferred": false, "started_at": "2026-03-12T08:48:06.230Z", @@ -103,7 +103,7 @@ "body": "### Summary\n\nOn March 6, 2026, between 02:19 UTC and 04:00 UTC, Bitbucket Cloud experienced an incident impacting the web app, API, CLI, and Pipelines operations. This was caused by the Bitbucket application hitting a regional provisioning API rate limit with our hosting provider, preventing application workers from handling website traffic. The incident was detected within 1 minute by automated monitoring and mitigated by scaling systems down and then back up to full capacity which put Atlassian systems into a known good state.\n\n### **IMPACT**\n\nThe incident resulted in a Bitbucket Cloud services being unavailable for 1 hour and 6 minutes on March 6, 2026 between 02:19 UTC and 03:25 UTC, followed by degraded website performance until 04:00 UTC. During this time, customers were unable to access Bitbucket services including the web app, Git operations \\(clone, push, pull over HTTPS and SSH\\), API, and running builds in Pipelines.\n\n### **ROOT CAUSE**\n\nThe issue stemmed from a change to an internal deployment system that increased use of a platform credential service, hitting a quota with our hosting provider. This blocked Bitbucket services from deploying additional capacity because new application nodes request the credential service on startup and were rate limited. This caused degradation of Bitbucket experiences and more failed requests to Bitbucket Cloud\u2019s website and public APIs.\n\n### **REMEDIAL ACTIONS PLAN & NEXT STEPS**\n\nThe incident response team manually scaled down Bitbucket services, then gradually scaled them back up while closely monitoring our quota. We simultaneously engaged with our hosting provider to temporarily increasing this limit to unblock bringing more Bitbucket service capacity online.\n\nWe know that outages impact your productivity. While we have a number of testing and preventative processes in place, Bitbucket services lacked necessary boundaries to be resilient to upstream platform system changes. To help minimise the impact of breaking changes to our environments, we will implement additional preventative measures such as:\n\n* Improve monitoring of shared Atlassian platform resources.\n* Update Bitbucket application bootstrapping to prevent new capacity from failing during resource contention of shared platform services.\n* Reduce Bitbucket\u2019s dependency on shared hosting provider services.\n* Deploy Bitbucket services across multiple regions to reduce single-region failure risk.\n\nWe apologize to customers whose services were impacted during this incident; we are taking immediate steps to improve the platform\u2019s performance and availability.\n\nThanks,\n\nAtlassian Customer Support", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-06T05:11:40.845Z", "resolved_inferred": false, "started_at": "2026-03-06T02:44:40.605Z", @@ -116,7 +116,7 @@ "body": "On January 28, 2026, affected Bitbucket Cloud users in eu-west-1 may have experienced some service disruption. The issue has now been resolved, and the service is operating normally for all affected customers.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-28T20:00:05.256Z", "resolved_inferred": false, "started_at": "2026-01-28T16:49:04.000Z", @@ -129,7 +129,7 @@ "body": "### Summary\n\nOn Jan 7, 2026, between 15:28 UTC and 17:04 UTC, Atlassian customers using Bitbucket Cloud could not load the dashboard landing page. Users also faced degraded performance and intermittent failures navigating other parts of the application or using public REST APIs.\n\nThe event was caused by an unexpected load on a public API, causing long-running queries on a database which resulted in failed web and api requests. The incident was detected within three minutes by automated monitoring systems and mitigated by introducing stricter limits on the API for certain traffic, while taking manual actions on the impacted database, restoring Bitbucket to a healthy state.\n\n### **IMPACT**\n\nOccurring on Bitbucket Cloud on Jan 7, 2026, between 15:28 UTC and 17:04 UTC, the incident caused degraded performance and intermittent failures to a subset of customers interacting with the Bitbucket web application and public APIs. Git operations over SSH and HTTPS were not impacted.\n\n### **ROOT CAUSE**\n\nThe event was caused by an unexpected load on a public API. The request volume during this period resulted in high resource utilization our central database\u2019s read replicas, impacting website and our API performance and reliability. \n\n### **REMEDIAL ACTIONS PLAN & NEXT STEPS**\n\nWe know outages reduce your productivity. Although we have several testing and prevention processes, this issue went undetected because a specific request pattern on a public API was not tested against the traffic volume seen during the incident.\n\nWe prioritized the following actions to prevent repeating this type of incident:\n\n* Improve rate limiting and caching capabilities at multiple points in our networking and application layers.\n* Apply stricter rate limits for specific public APIs to protect infrastructure health and shared application resources.\n* Optimize performance of specific queries and codepaths on these APIs to handle high request loads.\n\nWe apologize to customers whose services were impacted during this incident; we are taking immediate steps to improve the platform\u2019s performance and availability.\n\nThanks,\n\nAtlassian Customer Support", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-07T18:53:23.637Z", "resolved_inferred": false, "started_at": "2026-01-07T16:23:29.492Z", @@ -142,7 +142,7 @@ "body": "We have successfully mitigated the incident and the affected service is now fully operational. Our teams have verified that normal functionality has been restored. Thank you for your patience and understanding while we worked to resolve this issue.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-07T06:40:31.787Z", "resolved_inferred": false, "started_at": "2026-01-07T06:05:13.882Z", @@ -155,7 +155,7 @@ "body": "### Summary\n\nOn **December 27, 2025**, between **02:48 UTC and 05:20 UTC**, some Atlassian cloud customers experienced failures in sending and receiving emails and mobile notifications. Core Jira and Confluence functionality remained available.\n\nThe issue was triggered when **TLS certificates used by Atlassian\u2019s monitoring infrastructure expired**, causing parts of our metrics pipeline to stop accepting traffic. Services responsible for email and mobile notifications had a critical path dependency on monitoring path leading to service disruptions.\n\nAll impacted services were fully restored by **05:20 UTC**, around **2.5 hours** after customer impact began.\n\n### IMPACT\n\nDuring the impact window, customers experienced:\n\n* **Outbound product email failures** \\(notifications and other product emails did not send\\).\n* **Identity and account flow failures** where emails were required \\(e.g. sign\u2011ups, password resets, one\u2011time\u2011password / step\u2011up challenges\\).\n* **Jira and Confluence mobile push notifications**\n* **Customer site activations and some admin policy changes** failing and requiring later reprocessing.\n\n### ROOT CAUSE\n\nThe incident was caused by:\n\n1. **Expired TLS certificates** on domains used by our monitoring and metrics infrastructure caused by **misconfigured DNS authorization record** which prevented automatic renewal.\n2. **Tight coupling of services to metrics publishing**, which caused them to fail when monitoring endpoints became unavailable, instead of degrading gracefully.\n\n### REMEDIAL ACTIONS PLAN & NEXT STEPS\n\nWe recognize that outages like this have a direct impact on customers\u2019 ability to receive important notifications, complete account tasks, and operate their sites.\n\nWe are prioritizing the following actions to improve our existing testing, monitoring and certificate management processes:\n\n* **Hardening monitoring and certificate infrastructure**\n\n * We are refining DNS and certificate configuration across our monitoring domains and strengthening proactive checks to detect and address failed renewals and certificate issues well before expiry.\n * We are also improving alerting on our monitoring and metrics pipeline.\n \n* **Decoupling monitoring from critical customer flows** \n We are updating services such as outbound email, identity, mobile push, provisioning, and admin policy changes so they no longer depend on metrics publishing to operate. If monitoring becomes unavailable, these services will continue to run and degrade gracefully by dropping or buffering metrics instead of failing customer operations.\n\nWe apologize to customers impacted during this incident. We are implementing the improvements above to help ensure that similar issues are avoided.\n\nThanks, \nAtlassian Customer Support", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-27T05:20:21.718Z", "resolved_inferred": false, "started_at": "2025-12-27T04:42:31.916Z", @@ -168,7 +168,7 @@ "body": "## Summary\n\nOn November 11, 2025, between 16:25 and 19:13 UTC, Atlassian customers were unable to access Bitbucket Cloud services. Customers experienced a period of 1 hour and 16 minutes where performance was degraded and a period of 1 hour and 32 minutes where the Bitbucket Cloud website, APIs, and Git hosting were unavailable. The event was triggered by a code change that unintentionally impacted how we evaluate feature flags, impacting all customers. The incident was detected within 5 minutes by automated monitoring systems and mitigated by scaling multiple services and deploying a fix which put Atlassian systems into a known good state. The total time to full resolution was about 2 hours and 48 minutes.\n\n### **IMPACT**\n\nThe overall impact was between\u00a0November 11, 2025, 16:25 UTC and\u00a0November 11, 2025, 19:13 UTC on Bitbucket Cloud. Between 16:25 UTC and 16:50 UTC, users were seeing degraded experiences with both Git services and pull request experiences within the Bitbucket Cloud site. Starting at 16:50 UTC, users were unable to access Bitbucket Cloud and associated services entirely.\n\n### **ROOT CAUSE**\n\nDuring a routine deployment, a code change had a negative impact on a component used for feature flag evaluation. To mitigate this issue the Bitbucket engineering team manually scaled up Git services. This inadvertently resulted in hitting a regional limit with our hosting provider, causing new Git service instances to fail. This ultimately led to degradation of multiple dependent services and an increased number of failed requests via Bitbucket Cloud\u2019s website and public APIs.\n\n### **ACTIONS TAKEN**\n\nOur team immediately began investigating the issue and testing various mitigations, including scaling the impacted services, in an effort to reduce the effects of the change. However, these efforts were unsuccessful due to an unexpected scaling limit imposed by our underlying hosting platform. Attempts to roll back the code change were also unsuccessful, as the platform\u2019s scaling limit prevented new infrastructure from being provisioned during the rollback process. In particular, any attempts to provision new infrastructure caused a high volume of calls to occur in a short period, leading to failures, retries, and a feedback loop that worsened the situation.\n\nTo address this, the team scaled down certain services to reduce load on the platform, which allowed for the successful deployment of a fix and restoration of service. Once the fix was in place, healthy services were scaled back up to meet customer demand.\n\n### **REMEDIATION AND NEXT STEPS**\n\nWe recognize the significant impact outages have on our customers\u2019 productivity. Despite our robust testing and preventative measures, this particular issue related to feature flag evaluation was not detected in other environments and only became apparent under high load conditions that had not previously occurred. The incident has provided valuable information about our hosting platform\u2019s scaling limits, and we are actively applying these learnings to enhance our resilience and response times.\n\nTo help prevent similar incidents in the future, we have taken the following actions:\n\n* Enhanced the resiliency of the affected feature gate component to to prevent future changes from resulting in widespread service impact.\n* Updated application logic to prevent services from hitting these platform scaling limits.\n* Implemented additional safeguards to detect and handle platform-imposed limits proactively during deployment and rollback scenarios.\n\nWe apologize to customers whose services were impacted during this incident; we are taking immediate steps to improve the platform\u2019s performance and availability.\n\nThanks,\n\nAtlassian Customer Support", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-11T21:10:26.250Z", "resolved_inferred": false, "started_at": "2025-11-11T16:59:13.466Z", @@ -181,7 +181,7 @@ "body": "### Postmortem publish date: Nov 19th, 2025\n\n### Summary\n\nAll dates and times below are in UTC unless stated otherwise.\n\nCustomers utilizing Atlassian products experienced elevated error rates and degraded performance between Oct 20, 2025 06:48 and Oct 21, 2025 04:05. The service disruptions were triggered due to an [AWS DynamoDB outage](https://aws.amazon.com/message/101925/#:~:text=1%3A50%20PM.-,DynamoDB,-Between%2011%3A48) and further affected by subsequent failures in [AWS EC2](https://aws.amazon.com/message/101925/#:~:text=service%20disruption%20event.-,Amazon%20EC2,-Between%2011%3A48) and [AWS Network Load Balancer](https://aws.amazon.com/message/101925/#:~:text=service%20disruption%20event.-,Amazon%20EC2,-Between%2011%3A48) within the us-east-1 region.\n\nThe incident started at Oct 20, 2025 06:48 and was detected within six minutes by our automated monitoring systems. Our teams worked to restore all core services by Oct 21, 2025 04:05. Final cleanup of backlogged processes and minor issues was completed on Oct 22, 2025.\n\nWe recognize the critical role our products play in your daily operations, and we offer our sincere apologies for any impact this incident had on your teams. We are taking immediate steps to enhance the reliability and performance of our services, so that you continue to receive the standard of service you have come to trust.\n\n### IMPACT\n\nBefore examining product-level impacts, it's helpful to understand Atlassian's service topology and internal dependencies.\n\nProducts such as Jira and Confluence are deployed across multiple AWS regions. The data for each tenant is stored and processed exclusively within its designated host region. This design is intentional and represents the desired operational state, as it limits the impact of any regional outage strictly to tenants in-region, in this case us-east-1.\n\nWhile in-scope application data is pinned to the region selected by the customer, there are times when systems need to call other internal services that may be based in a different region. If a problem occurs in the main region where these services operate, systems are designed to automatically fail over to a backup region, usually within three minutes.\n\nHowever, if unexpected issues arise during this failover, it can take longer to restore services. In rare cases, this could affect customers in more than one region. It\u2019s important to note that all in-scope application data for supported products is pinned according to a customer\u2019s chosen region.\n\n**Jira**\n\nBetween Oct 20, 2025 06:48 and Oct 20, 2025 20:00, customers with tenants hosted in the us-east-1 region experienced increased error rates when accessing core entities such as Issues, Boards, and Backlogs. This disruption was caused by AWS's inability to allocate AWS EC2 instances and elevated errors in AWS Network Load Balancer \\(NLB\\). During this window, users may also have observed intermittent timeouts, slow page loads, and failures when performing operations like creating or updating issues, loading board views, and executing workflow transitions.\n\nBetween Oct 20, 2025 08:36 and Oct 20, 2025 09:23, customers across all regions experienced elevated failure rates when attempting to load Jira pages. This disruption was caused by the regional frontend service entering an unhealthy state during this specific time interval.\n\nNormally, the frontend service connects to the primary AWS DynamoDB instance located in the us-east-1 to retrieve the most recent configuration data necessary for proper operation. Additionally, the service is designed with a fallback mechanism that references static configuration data in the event that the primary database becomes inaccessible. Unfortunately, a latent bug existed in the local fallback path. When the frontend service nodes restarted, they were unable to load critical operational configuration data from primary or fallback sources, leading to the observed failures experienced by customers.\n\nBetween Oct 20, 2025 06:48 and Oct 21, 2025 06:30, customers experienced significant delays and missing Jira in-app notifications across all regions. The notification ingestion service, which is hosted exclusively in us-east-1, exhibited an increased failure rate when processing notification messages due to AWS EC2 and NLB issues. This issue resulted in notifications being delayed - and in some cases, not delivered at all - to users worldwide.\n\n**Jira Service Management \\(JSM\\)**\n\nJSM was impacted similarly to Jira above, with the same timeframes and for the same reasons.\n\nBetween Oct 20, 2025 08:36 and Oct 20, 2025 09:23, customers across all regions experienced significantly elevated failure rates when attempting to load JSM pages. This affected all JSM experiences including the Help Centre, Portal, Queues, Work Items, Operations, and Alerts.\n\n**Confluence**\n\nBetween Oct 20, 2025 06:48 and Oct 21, 2025 02:45, customers using Confluence in the us-east-1 region experienced elevated failure rates when performing common operations such as editing pages or adding comments. The primary cause of this service degradation was the system's inability to auto-scale due to AWS EC2 issues to manage peak traffic load effectively.\n\nThough the AWS outage ended at Oct 20, 21:09, a subset of customers continued to experience failures as some Confluence web server nodes across multiple clusters remained in an unhealthy state. This was ultimately mitigated by recycling the affected nodes.\n\nTo protect our systems while AWS recovered, we made a deliberate decision to enable node termination protection. This action successfully preserved our server capacity but, as a trade-off, it extended the time required for a full recovery once AWS services were restored.\n\n**Automation**\n\nBetween Oct 20, 2025 06:55 and Oct 20, 2025 23:59, automation customers whose rules are processed in us-east-1 experienced delays of up to 23 hours in rule execution.\n\nDuring this window, some events triggering rule executions were processed out of order because they arrived later during backlog processing. This caused potential inconsistencies in workflow executions, as rules were run in the order events were received, not when the action causing the event occurred. Additionally, some rule actions failed because they depend on first-party and third-party systems, which were also affected by the AWS outage. Customers can see most of these failures in their audit logs; however, a few updates were not logged due to the nature of the outage.\n\nBy Oct 21, 2025 5:30, the backlog of rule runs in us-east-1 was cleared. Although most of these delayed rules were successfully handled, there were some additional replays of events to ensure completeness. Our investigation confirmed that a few events may never have triggered their associated rules due to the outage.\n\nBetween Oct 20, 2025 06:55 and Oct 20, 2025 11:20, all non-us-east-1 regional automation services experienced delays of up to 4 hours in rule execution. This was caused by an upstream service that was unable to deliver events as expected. The delivery service encountered a failure due to a cross-region dependency call to a service hosted in the us-east-1 region. Because of this dependency issue, the delivery service was unable to successfully deliver events throughout this time frame, resulting in customer-defined rules not being executed in a timely manner.\n\n**Bitbucket and Pipelines**\n\nBetween Oct 20, 2025 06:48 and Oct 20, 2025 09:33, Bitbucket experienced intermittent unavailability across core services. During this period, users faced increased error rates and latency when signing in, navigating repositories, and performing essential actions such as creating, updating, or approving pull requests. The primary cause was an AWS DynamoDB outage that impacted downstream services.\n\nBetween Oct 20, 2025 06:48 and Oct 20, 2025 22:46, numerous Bitbucket Pipeline steps failed to start, stalled mid-execution, or experienced significant queueing delays. Impact varied, with partial recoveries followed by degradation as downstream components re-synchronized. The primary cause was an AWS DynamoDB outage, compounded by instability in AWS EC2 instance availability and AWS Network Load Balancers.\n\nFurthermore, Bitbucket Pipelines continued to experience a low but persistent rate of step timeouts and scheduling errors due to AWS bare-metal capacity shortages in select availability zones. Atlassian coordinated with AWS to provision additional bare-metal hosts and addressed a significant backlog of pending pods, successfully restoring services by 01:30 on Oct 21, 2025.\n\n**Trello**\n\nBetween Oct 20, 2025 06:48 and Oct 20, 2025 15:25, users of Trello experienced widespread service degradation and intermittent failures due to upstream AWS issues affecting multiple components, including AWS DynamoDB and subsequent AWS EC2 capacity constraints. During this period, customers reported elevated error rates when loading boards, opening cards, adding comments or attachments.\n\n**Login**\n\nBetween Oct 20, 2025 06:48 and Oct 20, 2025 09:30, a small subset of users experienced failures when attempting to initiate new login sessions using SAML tokens. This resulted in an inability for those users to access Atlassian products during that time period. However, users who already had valid active sessions were not affected by this issue and continued to have uninterrupted access.\n\nThe issue impacted all regions globally because regional identity services relied on a write replica located in the us-east-1 region to synchronize profile data. When the primary region became unavailable, the failover to a secondary database in another region failed, which delayed recovery. This failover defect has since been addressed.\n\n**Statuspage**\n\nBetween Oct 20, 2025 06:48 and Oct 20, 2025 09:30, Statuspage customers who were not already logged in to the management portal were unable to log in to create or update incident statuses. This impact was restricted only to users who were not already logged in at the time. The root cause was the same as described in the Login section above, and it was resolved by the same remediation steps.\n\n### REMEDIAL ACTION PLAN & NEXT STEPS\n\nWe have completed the following critical actions designed to help prevent cross-region impact from similar issues:\n\n* Resolved the code defect in the fallback option to ensure that Jira Frontend Services in other regions remain unaffected during a region-wide outage.\n* Fixed the issue that prevented timely failover of the identity service which impacted new login sessions.\n* Resolved the code defect so that delivery services in unaffected regions remain operational during region-wide outages.\n\nAdditionally, we are prioritizing the following improvement actions:\n\n* Implement mitigation strategies to strengthen resilience against region-wide outages in the notification ingestion service.\n\nAlthough disruptions to our cloud services are sometimes unavoidable during outages of the underlying cloud provider, we continuously evaluate and improve test coverage to strengthen resilience of our cloud services against these issues.\n\nWe recognize the critical importance of our products to your daily operations and overall productivity, and we extend our sincere apologies for any disruptions this incident may have caused your teams. If you were impacted and require additional details for internal post-incident reviews, please reach out to your Atlassian support representative with affected timeframes and tenant identifiers so we can correlate logs and provide guidance.\n\nThanks,\n\nAtlassian Customer Support", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-21T05:24:27.288Z", "resolved_inferred": false, "started_at": "2025-10-20T07:56:11.412Z", @@ -194,7 +194,7 @@ "body": "Between 03:30 UTC to 03:50 UTC, we experienced delyas in running pipelines for Atlassian Bitbucket. The issue has been resolved and the service is operating normally.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-16T04:30:49.504Z", "resolved_inferred": false, "started_at": "2025-09-16T04:00:45.092Z", @@ -207,7 +207,7 @@ "body": "issue resloved pipeline is completed.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-27T15:25:44.417Z", "resolved_inferred": false, "started_at": "2025-08-26T15:06:05.969Z", @@ -220,7 +220,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-20T15:16:23.263Z", "resolved_inferred": false, "started_at": "2025-08-20T07:30:28.000Z", @@ -233,7 +233,7 @@ "body": "Bitbucket Cloud is fully recovered.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-19T15:22:30.168Z", "resolved_inferred": false, "started_at": "2025-08-19T14:27:32.331Z", @@ -246,7 +246,7 @@ "body": "Today, between 13:55 and 14:35 UTC, we experienced a degradation on Bitbucket cloud, which impacted access to the website.\nThis issue has been resolved, and services are now operating normally for all affected customers.\nWe will monitor it closely to ensure stability", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-05T15:03:36.789Z", "resolved_inferred": false, "started_at": "2025-08-05T15:03:36.737Z", @@ -259,7 +259,7 @@ "body": "Between 08:00UTC to 09:00UTC, we experienced degraded performance with push and clone operations for Atlassian Bitbucket. The issue has been resolved and the service is operating normally.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-01T09:22:28.748Z", "resolved_inferred": false, "started_at": "2025-08-01T08:16:29.491Z", diff --git a/api/v/bitfinex.json b/api/v/bitfinex.json index a6b1fecad2c4308dba3500f99b2d1b26c7bf62b3..cb4319e205deed145137a039dbdec5e5ce0673e4 100644 --- a/api/v/bitfinex.json +++ b/api/v/bitfinex.json @@ -3,7 +3,7 @@ "slug": "bitfinex", "platform": "statuspage", "status_url": "https://bitfinex.statuspage.io", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "maintenance", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-14T02:23:29.750Z", "resolved_inferred": false, "started_at": "2025-08-13T23:29:37.522Z", diff --git a/api/v/bitgo.json b/api/v/bitgo.json index e73d8c692655f7746a2515cf8fb115fccacc40fd..e23cc9764d1b3b20a50e509b2fb22ed5d63f5898 100644 --- a/api/v/bitgo.json +++ b/api/v/bitgo.json @@ -3,7 +3,7 @@ "slug": "bitgo", "platform": "statuspage", "status_url": "https://status.bitgo.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-27T12:12:54.237-07:00", "resolved_inferred": false, "started_at": "2026-08-27T11:20:29.380-07:00", @@ -25,7 +25,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-26T00:04:55.593-07:00", "resolved_inferred": false, "started_at": "2026-08-25T23:23:31.022-07:00", @@ -38,7 +38,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-24T16:25:33.783-07:00", "resolved_inferred": false, "started_at": "2026-08-24T13:07:17.000-07:00", @@ -51,7 +51,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-21T07:11:09.032-07:00", "resolved_inferred": false, "started_at": "2026-08-21T04:07:24.223-07:00", @@ -64,7 +64,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-18T22:58:22.241-07:00", "resolved_inferred": false, "started_at": "2026-08-18T20:43:47.305-07:00", @@ -77,7 +77,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-17T10:49:50.347-07:00", "resolved_inferred": false, "started_at": "2026-08-17T09:08:58.252-07:00", @@ -90,7 +90,7 @@ "body": "The change causing this issue has been reverted, and new whitelist addresses are no longer affected.\n\nWe are currently identifying whitelist entries impacted during the affected period and working to correct them.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-10T12:45:22.600-07:00", "resolved_inferred": false, "started_at": "2026-08-10T12:32:45.000-07:00", @@ -103,7 +103,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-06T12:37:31.944-07:00", "resolved_inferred": false, "started_at": "2026-08-06T11:38:50.965-07:00", @@ -116,7 +116,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-29T16:26:15.672-07:00", "resolved_inferred": false, "started_at": "2026-07-29T08:51:57.734-07:00", @@ -129,7 +129,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-22T17:51:44.333-07:00", "resolved_inferred": false, "started_at": "2026-07-22T16:33:21.388-07:00", @@ -142,7 +142,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-16T21:14:02.678-07:00", "resolved_inferred": false, "started_at": "2026-07-16T18:18:59.986-07:00", @@ -155,7 +155,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-13T06:58:52.739-07:00", "resolved_inferred": false, "started_at": "2026-07-13T05:58:10.825-07:00", @@ -168,7 +168,7 @@ "body": "Investigating \u2014 10:27 AM UTC\nWe are investigating reports of delays in transaction confirmation processing. Some deposits and withdrawals may take longer than usual to appear as confirmed.\n\nIdentified \u2014 11:54 AM UTC\nWe have identified the cause of the delay and are actively mitigating. Transactions continue to be processed, though confirmations may lag for some networks.\n\nResolved \u2014 1:06 PM UTC\nThis incident has been resolved. Confirmation processing has returned to normal levels. Any transactions delayed during this window have since confirmed.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-02T03:27:00.000-07:00", "resolved_inferred": false, "started_at": "2026-07-02T03:27:00.000-07:00", @@ -181,7 +181,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-01T10:52:44.241-07:00", "resolved_inferred": false, "started_at": "2026-07-01T09:50:00.040-07:00", @@ -194,7 +194,7 @@ "body": "We experienced a network degradation between 1:30am and 3:30am UTC, which impacted some client requests during that window.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-30T21:02:00.792-07:00", "resolved_inferred": false, "started_at": "2026-06-30T20:19:57.928-07:00", @@ -207,7 +207,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-24T02:57:09.542-07:00", "resolved_inferred": false, "started_at": "2026-06-24T02:21:00.248-07:00", @@ -220,7 +220,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-22T10:21:30.098-07:00", "resolved_inferred": false, "started_at": "2026-06-22T07:05:33.371-07:00", @@ -233,7 +233,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-19T04:42:00.944-07:00", "resolved_inferred": false, "started_at": "2026-06-19T03:02:00.148-07:00", @@ -246,7 +246,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-16T03:30:32.134-07:00", "resolved_inferred": false, "started_at": "2026-06-16T01:28:47.970-07:00", @@ -259,7 +259,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-11T01:59:20.072-07:00", "resolved_inferred": false, "started_at": "2026-06-11T01:35:32.693-07:00", @@ -272,7 +272,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-09T02:54:03.571-07:00", "resolved_inferred": false, "started_at": "2026-06-09T02:23:36.623-07:00", @@ -285,7 +285,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-05T08:22:28.289-07:00", "resolved_inferred": false, "started_at": "2026-06-05T07:05:01.190-07:00", @@ -298,7 +298,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-05T02:39:37.029-07:00", "resolved_inferred": false, "started_at": "2026-06-05T00:44:26.390-07:00", @@ -311,7 +311,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-03T17:17:01.224-07:00", "resolved_inferred": false, "started_at": "2026-06-03T12:37:48.000-07:00", @@ -324,7 +324,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-01T07:27:14.109-07:00", "resolved_inferred": false, "started_at": "2026-06-01T06:30:05.560-07:00", @@ -337,7 +337,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-29T20:14:38.074-07:00", "resolved_inferred": false, "started_at": "2026-05-29T18:30:16.686-07:00", @@ -350,7 +350,7 @@ "body": "We have resumed processing SUI transactions successfully. If you encounter any failed or delayed transactions, please contact us at support@bitgo.com and our team will be happy to assist.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-29T11:43:20.232-07:00", "resolved_inferred": false, "started_at": "2026-05-29T06:17:14.756-07:00", @@ -363,7 +363,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-29T04:45:15.766-07:00", "resolved_inferred": false, "started_at": "2026-05-29T03:06:12.341-07:00", @@ -376,7 +376,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-28T20:06:25.693-07:00", "resolved_inferred": false, "started_at": "2026-05-28T09:16:23.504-07:00", @@ -389,7 +389,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-12T02:00:27.409-07:00", "resolved_inferred": false, "started_at": "2026-05-12T01:55:50.765-07:00", @@ -402,7 +402,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-06T07:58:38.678-07:00", "resolved_inferred": false, "started_at": "2026-05-06T07:12:27.590-07:00", @@ -415,7 +415,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-05T06:48:29.791-07:00", "resolved_inferred": false, "started_at": "2026-05-05T02:34:32.133-07:00", @@ -428,7 +428,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-02T11:13:39.194-07:00", "resolved_inferred": false, "started_at": "2026-05-02T09:24:08.795-07:00", @@ -441,7 +441,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-30T15:11:10.575-07:00", "resolved_inferred": false, "started_at": "2026-04-30T13:47:56.034-07:00", @@ -454,7 +454,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-30T07:45:51.884-07:00", "resolved_inferred": false, "started_at": "2026-04-30T06:47:23.956-07:00", @@ -467,7 +467,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-28T10:02:00.941-07:00", "resolved_inferred": false, "started_at": "2026-04-28T09:22:01.797-07:00", @@ -480,7 +480,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-25T11:06:34.899-07:00", "resolved_inferred": false, "started_at": "2026-04-25T07:04:05.628-07:00", @@ -493,7 +493,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-22T04:18:05.502-07:00", "resolved_inferred": false, "started_at": "2026-04-21T11:34:52.962-07:00", @@ -506,7 +506,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-21T06:13:16.800-07:00", "resolved_inferred": false, "started_at": "2026-04-21T02:42:41.572-07:00", @@ -519,7 +519,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-20T16:41:22.988-07:00", "resolved_inferred": false, "started_at": "2026-04-20T12:38:06.594-07:00", @@ -532,7 +532,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-20T08:02:17.670-07:00", "resolved_inferred": false, "started_at": "2026-04-20T06:13:12.981-07:00", @@ -545,7 +545,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-17T00:32:04.734-07:00", "resolved_inferred": false, "started_at": "2026-04-16T22:42:04.753-07:00", @@ -558,7 +558,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-14T09:38:06.903-07:00", "resolved_inferred": false, "started_at": "2026-04-14T08:28:36.858-07:00", @@ -571,7 +571,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-14T07:52:07.744-07:00", "resolved_inferred": false, "started_at": "2026-04-14T07:31:30.441-07:00", @@ -584,7 +584,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-14T01:10:45.775-07:00", "resolved_inferred": false, "started_at": "2026-04-14T01:07:36.998-07:00", @@ -597,7 +597,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-09T09:49:32.524-07:00", "resolved_inferred": false, "started_at": "2026-04-09T01:39:21.432-07:00", @@ -610,7 +610,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-08T18:18:51.923-07:00", "resolved_inferred": false, "started_at": "2026-04-08T17:36:38.695-07:00", @@ -623,7 +623,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-08T13:44:07.280-07:00", "resolved_inferred": false, "started_at": "2026-04-08T12:05:12.828-07:00", @@ -636,7 +636,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-08T07:42:42.765-07:00", "resolved_inferred": false, "started_at": "2026-04-08T07:34:26.902-07:00", @@ -649,7 +649,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-08T08:34:17.244-07:00", "resolved_inferred": false, "started_at": "2026-04-08T06:54:07.138-07:00", diff --git a/api/v/bitly.json b/api/v/bitly.json index 1c83cad7c3416a50f7683d27bd1f3bae6d3e741a..e045ec6ec477a76095d3d6eb3c0cb1f0bb9bc632 100644 --- a/api/v/bitly.json +++ b/api/v/bitly.json @@ -3,7 +3,7 @@ "slug": "bitly", "platform": "statuspage", "status_url": "https://status.bitly.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "The incident affecting availability of bitly.com has been resolved and the website is fully operational.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-25T19:10:32.815-04:00", "resolved_inferred": false, "started_at": "2026-04-25T19:04:19.776-04:00", @@ -25,7 +25,7 @@ "body": "The issue has been identified and resolved. We will continue to monitor.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-16T16:20:51.503-04:00", "resolved_inferred": false, "started_at": "2026-03-16T15:42:56.737-04:00", @@ -38,7 +38,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-19T21:21:33.805-05:00", "resolved_inferred": false, "started_at": "2026-02-12T12:49:44.394-05:00", @@ -51,7 +51,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-05T18:04:11.960-05:00", "resolved_inferred": false, "started_at": "2026-01-05T16:42:41.087-05:00", @@ -64,7 +64,7 @@ "body": "The incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-12T10:11:05.402-04:00", "resolved_inferred": false, "started_at": "2025-09-12T08:38:44.610-04:00", @@ -77,7 +77,7 @@ "body": "The 3rd party outage causing issues with transactional email sends has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-12T06:24:39.507-04:00", "resolved_inferred": false, "started_at": "2025-09-12T04:46:42.709-04:00", @@ -90,7 +90,7 @@ "body": "The outage of our 3rd party provider that was blocking new user sign ups has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-11T20:21:46.878-04:00", "resolved_inferred": false, "started_at": "2025-09-11T19:21:55.911-04:00", @@ -103,7 +103,7 @@ "body": "The 3rd party provider incident involving checkout with PayPal has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-01T11:37:43.672-04:00", "resolved_inferred": false, "started_at": "2025-08-01T09:02:34.838-04:00", diff --git a/api/v/bitmex.json b/api/v/bitmex.json index bb88ff17f2b67e0369fde0026cc2504c1dbf7cea..f441d924d284d8f0a677d7a05df27b0613f77729 100644 --- a/api/v/bitmex.json +++ b/api/v/bitmex.json @@ -3,7 +3,7 @@ "slug": "bitmex", "platform": "statuspage", "status_url": "https://status.bitmex.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "The withdrawal backlog has been cleared and systems are operating as expected. ", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-13T14:52:35Z", "resolved_inferred": false, "started_at": "2026-07-13T14:08:03Z", @@ -24,7 +24,7 @@ "body": "The incident is now resolved", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-16T07:31:58Z", "resolved_inferred": false, "started_at": "2026-06-13T07:36:25Z", @@ -36,7 +36,7 @@ "body": "Connections are restored. Monitoring complete", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-14T12:18:00Z", "resolved_inferred": false, "started_at": "2026-05-14T09:28:24Z", @@ -48,7 +48,7 @@ "body": "The issue has been resolved, all systems are operating normally", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-12T07:39:00Z", "resolved_inferred": false, "started_at": "2026-05-12T07:59:34Z", @@ -60,7 +60,7 @@ "body": "The fix has been implemented and withdrawals are now flowing as expected. ", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-15T16:23:40Z", "resolved_inferred": false, "started_at": "2026-04-15T12:48:52Z", @@ -72,7 +72,7 @@ "body": "The issue is now resolved", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-28T12:25:00Z", "resolved_inferred": false, "started_at": "2026-03-28T13:38:51Z", @@ -84,7 +84,7 @@ "body": "This issue is now resolved", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-24T06:09:37Z", "resolved_inferred": false, "started_at": "2026-03-24T05:43:14Z", @@ -96,7 +96,7 @@ "body": "REST API queries for trading related data (read-only HTTP GET requests, not order management requests) took longer to return than usual over a period of 23 minutes from 18:13 UTC to 18:36 UTC.\n\nThe root causes of both issues have been identified and we are working on permanent fixes to prevent a recurrence. We apologise for any inconvenience this may be causing. If you have any further questions, please contact us via https://www.bitmex.com/app/support/contact.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2018-12-27T18:36:00Z", "resolved_inferred": false, "started_at": "2026-02-26T07:58:00Z", @@ -108,7 +108,7 @@ "body": "From 06:53 to 07:03 UTC today, September 3rd, 2018, the service of our websocket API was impaired, which impacted the live data updates on the [bitmex.com](http://bitmex.com) website as well as clients connected directly to our websocket API. \n\nAs part of a scheduled software release on the trading engine, our market data distribution component became saturated with a cascade of updates during the restart process which temporarily prevented downstream data distribution on the websocket API. \n\nWe apologise for the disruption. The root cause has been identified and mitigated in the production environment. BitMEX engineers have already deployed a fix for the underlying issue to prevent a re-occurrence. We are also improving a number of alerting mechanisms to enable us to recover from potential issues in a more timely manner.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2018-09-03T06:03:00Z", "resolved_inferred": false, "started_at": "2026-02-26T07:58:00Z", @@ -120,7 +120,7 @@ "body": "From 14:29 to 15:26 UTC today, August 4, 2018, access to [BitMEX.com](http://BitMEX.com) and the BitMEX API was severely impaired. \n\nA large spike in load caused an overload in a critical internal system used for rate limiting and sessions, creating a feedback loop in that system where data was recalculated more often than usual, exacerbating the load. \n\nThe feedback loop has been fixed and systems have returned back to normal. BitMEX engineers are working to separate these systems entirely, so that these particular non-critical operations cannot affect processing time of critical trade requests and logins. \n\nWe apologise for the disruption. BitMEX engineers have disabled the cause of the feedback loop and are working the weekend to separate these critical systems so that such an event cannot occur again.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2018-08-04T14:26:00Z", "resolved_inferred": false, "started_at": "2026-02-26T07:58:00Z", @@ -132,7 +132,7 @@ "body": "Today, May 17, 2018, the BitMEX trading engine encountered several separate and heretofore unpredictable problems, causing feed latency and downtime in spurts throughout the day. \n \nDisks mounted to the main trading engine hardware degraded sharply in performance at roughly 10:00 UTC. This degradation caused feed latency during scheduled archive and reindex jobs, which caused significant backpressure. Disk I/O operations were running at roughly 1/20 of their expected rate. \n \nBitMEX runs redundant drives, but in this case, both drives were simultaneously exhibiting this degraded behavior. We had no choice but to schedule a maintenance downtime to replace them. Unfortunately, backpressure reached critical levels faster than we expected and we moved up our timetable. \n \nAt no point was data integrity compromised by this problem, but restoring the machine to a functional state with nominal disk performance took longer than expected to execute and verify. \n \nAfter this action was complete, we restarted trading. Unfortunately, another problem was uncovered during the next archive, where a reindex job combined with a previously rare request pattern led to unexpected index regeneration and symbol revalidation on specific tables. This led to another backpressure scenario, with similar symptoms. \n \nWe have identified and fixed multiple contributing factors to the above behavior. The trading engine team will be closely monitoring engine performance throughout the day while continuing root cause analysis for the slowdowns.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2018-05-17T15:00:00Z", "resolved_inferred": false, "started_at": "2026-02-26T07:58:00Z", @@ -144,7 +144,7 @@ "body": "Between 05:40 and 07:11 UTC today, a subset of the requests to the BitMEX REST API experienced slow API responses and eventual API timeouts due to resource contention at the API layer. Upon detection via our internal alerting mechanisms we identified the cause and mitigated the immediate impact within a few minutes. There is currently no ongoing issue and there was no impact to the trading engine or user data during this time. \n\nFixes for the underlying root cause of the issue have been identified and are being worked on as a priority. We will follow up with another announcement once these are live. We have also increased the sensitivity of our system monitoring to detect and resolve potential similar issues much sooner. We apologise for any inconvenience this may have caused.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2019-02-08T07:11:08Z", "resolved_inferred": false, "started_at": "2026-02-26T07:57:59Z", @@ -156,7 +156,7 @@ "body": "Earlier today, the [testnet.bitmex.com](http://testnet.bitmex.com) website and the API were not available for approximately 16 minutes from 19:42 to 19:57 UTC. We identified the cause, made adjustments and service has resumed immediately. We apologise for any inconvenience this may have caused", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2019-01-23T19:57:48Z", "resolved_inferred": false, "started_at": "2026-02-26T07:57:59Z", @@ -168,7 +168,7 @@ "body": "At 05:48:10 UTC and 06:10:10 UTC, BitMEX experienced minor outages for approximately 30 seconds whereby requests to the trading engine were load-shed as the engine was busy. During these times, clients would have observed a lack of updates over the WebSocket API for the same reason. The outages were due to data replay complications during a regularly scheduled market data distribution component restart. \n\nThere was no data loss during these events and an additional safety mechanism to prevent a similar situation from impacting the trading engine has already been deployed. The root causes have also been identified and we are currently working on permanent fixes to prevent a recurrence. Updates will follow in the future. \n\nOn 15 Jan 2019, we successfully released an enhancement to our internal market data distribution component's re-subscription logic. This addresses the root cause of the previous week's issue and along with the additional safety mechanism to prevent impact to the trading engine deployed at the time, we don't anticipate a reoccurrence of last week's issue.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2019-01-09T06:10:31Z", "resolved_inferred": false, "started_at": "2026-02-26T07:57:59Z", @@ -180,7 +180,7 @@ "body": "At 02:44:10 UTC the WebSocket API saw a degradation in performance for a minute where 7% of commands sent by clients failed. Connections continued undergoing a 1% failure rate of commands until servers recovered at 02:47:00 UTC. \n\nClients may have also seen an increase in response times for some market data REST endpoints up during this period. This was due to a rolling restart of the API servers that occurred in too tight of a timeframe.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2019-01-09T02:47:06Z", "resolved_inferred": false, "started_at": "2026-02-26T07:57:59Z", @@ -192,7 +192,7 @@ "body": "On 27 December at 18:38 UTC, BitMEX experienced a minor outage for approximately 1 minute whereby the trading engine was unavailable. During this time, market data updates were not published over the Websocket API. \n\nThe root causes of both issues have been identified and we are working on permanent fixes to prevent a recurrence. Updates will follow in the future.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2018-12-27T18:39:00Z", "resolved_inferred": false, "started_at": "2026-02-26T07:57:59Z", @@ -204,7 +204,7 @@ "body": "On 2 April 2019 between 04:44:34 UTC and 05:22:08 UTC, less than 200 positions were auto-deleveraged due to the sharp price movements of the underlying mark price on XBTU19 and ETHM19.\n\nAt the time of these auto-deleveraging events, the Insurance Fund allocated to these contracts was minimal. The Insurance Fund is allocated individually to each contract according to how many liquidations contribute to that specific contract \\(System Gains and Losses\\). In the case of expired contracts, BitMEX has a process in place to roll over the Insurance Fund allocated to these contracts into the next front month contract. With the recent expiry on the 29th March 2019, this process failed and front month contracts did not receive their reallocation, and the funds remained unallocated. As a result, a handful of users were auto-deleveraged upon large liquidations within these affected contracts. \n\nBitMEX receives auto-deleveraging reports and was made aware of the unusually high rate of auto-deleveraging events, at which point we investigated the matter. We identified the root cause, corrected the allocation and put further controls in place to ensure that reallocation failures are automatically flagged internally. \n\nFor users that were affected, BitMEX will be reaching out to you personally to explain the situation and document your compensation. We compensated users based on the maximum potential profit that they would have made over the timeframe of these auto-deleveraging events. We exited these users at the best price of each contract: longs at 5,079.5 on XBTU19 and shorts at 0.03103 on ETHM19. BitMEX did not profit from these auto-deleveraged positions.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2019-04-02T04:22:44Z", "resolved_inferred": false, "started_at": "2026-02-26T07:57:58Z", @@ -216,7 +216,7 @@ "body": "On 29 March at 12:00 UTC, BitMEX experienced a minor outage for approximately 15 seconds whereby all requests would have been load shed as the engine was blocked during settlement operations. The platform was back to normal after the 15 second outage.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2019-03-29T23:00:29Z", "resolved_inferred": false, "started_at": "2026-02-26T07:57:58Z", @@ -228,7 +228,7 @@ "body": "The issue has been resolved. We apologise for any inconvenience this may be causing. If you have any further questions, please contact us via https://www.bitmex.com/app/support/contact.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2019-03-29T20:08:15Z", "resolved_inferred": false, "started_at": "2026-02-26T07:57:58Z", @@ -240,7 +240,7 @@ "body": "On 19 February at 05:31 UTC, BitMEX experienced a minor outage for approximately 1 minute whereby all trading engine operations were suspended. \n\nThis issue occurred due to a sustained period of data transfers between the internal market data distribution components. This was part of a regularly scheduled update to improve the overall resiliency of the platform. The root cause has been identified and a fix via internal processes has been put in place to prevent a recurrence. Additionally, we are continuing to re-work our market data distribution architecture to eliminate any potential impact to the trading engine in such a scenario.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2019-02-19T05:32:14Z", "resolved_inferred": false, "started_at": "2026-02-26T07:57:58Z", @@ -252,7 +252,7 @@ "body": "Between 21:30 UTC 25 November 2019 and 07:05 UTC 26 November 2019 the Websocket API was running with degraded capacity. This resulted in slightly more latent feeds during this time and some isolated occurrences of substantial lag during traffic spikes correlated with large market moves. \n\nThe issue was identified when latency thresholds were breached in our automated monitoring systems around 06:55 UTC. From 07:05 the issue was resolved and full capacity was restored. We continue to monitor the impacted services closely. \n\nThe issue was caused by incorrect CPU pinning following a release of a market data distribution component at 21:30 UTC 25 November 2019. The impact of this was only observed during large traffic spikes which occurred several hours later and so was not identified during the post release checks at the time. The configuration of this service has been corrected and the deployment tested to prevent this from happening again.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2019-11-26T07:05:08Z", "resolved_inferred": false, "started_at": "2026-02-26T07:57:57Z", @@ -264,7 +264,7 @@ "body": "Between 10:44:13 and 10:52:29 UTC on 24 July 2019, the realtime data on the following websocket API feeds was interrupted: \n\naccount, affiliate, execution, funds, instrument, margin, order, position, trade, transact, wallet \n\nUsers of the BitMEX website may have noticed that some data was not updating during this period; e.g. in the Recent Trades panel, Open Orders panel, Fills panel, and Position panel. \n\nThe following public feeds were unaffected during this period: \n\nfunding, insurance, liquidation, settlement, impactQuote, impactQuoteBin1m, quote, quoteBin1m, quoteBin5m, quoteBin1h, quoteBin1d, tradeBin1m, tradeBin5m, tradeBin1h, tradeBin1d, orderBookL2\\_25, orderBook10, orderBookL2 The REST API was also unaffected and client-side data loss due to missed feed updates during this period can be resolved using the REST API. \n\nDuring this period we continued to process all order instructions and the trading engine was unaffected. The outage was due to a slow consuming internal market data service which became degraded, putting pressure on our market data infrastructure. This internal market data service has been suspended whilst the root cause is being investigated. Additionally, several safety mechanisms are currently being deployed to prevent a potential recurrence from impacting user-facing feeds.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2019-07-27T19:13:22Z", "resolved_inferred": false, "started_at": "2026-02-26T07:57:57Z", @@ -276,7 +276,7 @@ "body": "Between 07:50 and 07:58 UTC on 27 June 2019, the following websocket API feeds were interrupted due to a complication during a planned upgrade of our market data distribution services:\n\nAccount, affiliate, execution, funds, instrument, margin, order, position, trade, transact, wallet Users of the BitMEX website may have noticed some data not updating during this period e.g. in the Recent Trades panel, Open Orders panel, Fills panel, and Position panel.\n\nThe following public feeds were unaffected during this period:\n\nFunding, insurance, liquidation, settlement, impactQuote, impactQuoteBin1m, quote, quoteBin1m, quoteBin5m, quoteBin1h, quoteBin1d, tradeBin1m, tradeBin5m, tradeBin1h, tradeBin1d, orderBookL2\\_25, orderBook10, orderBookL2 During this period we continued to process order instructions and the trading engine was unaffected.\n\nDue to this issue, data in a subset of data mirrors which service user REST API requests was left in an incomplete state. A side-effect of this was that some users observed stale open orders on the BitMEX website for orders which were already cancelled for a period of 90 minutes whilst data was being restored. Any API users that may be missing updates for this period can now backfill data via the REST API.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2019-06-27T06:58:24Z", "resolved_inferred": false, "started_at": "2026-02-26T07:57:57Z", @@ -288,7 +288,7 @@ "body": "At 21:09:00 UTC 25 June, we released an update to our API layer that inadvertently started to count WebSocket subscriptions to certain tables against the request rate limit that had otherwise been exempt. This update may have impacted customers who heavily utilise the WebSocket API. Once the issue was identified at 00:19 UTC 26 June, we immediately rolled back the update to bring systems back to normal. \n\nWe apologise for any inconvenience this may have caused. To read more about which subscriptions are exempt from the request rate limiter, see our previous blog post \\[[https://blog.bitmex.com/update-to-our-realtime-apis-image-delivery/](https://blog.bitmex.com/update-to-our-realtime-apis-image-delivery/)\\] for details.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2019-06-26T00:19:23Z", "resolved_inferred": false, "started_at": "2026-02-26T07:57:57Z", @@ -300,7 +300,7 @@ "body": "Between 09:25:54 UTC and 09:44:30 UTC 24 June 2019 the orderBookL2, orderBookL2\\_25, orderBook10, and quote realtime websocket feeds for ETHUSD were in a degraded state. During this period, the state of the ETHUSD orderbook on these feeds was incorrect. \n\nWe were able to identify and resolve the root cause of the issue within a minute of detection. The issue was caused by a rare sequence of order events that triggered a bug in an optimisation of the orderBookL2 calculation which had been deployed to the production environment several hours earlier. This change has since been reverted. \n\nThere was no impact to orders in the trading engine itself \u2013 just the presentation of the calculated orderbook for ETHUSD downstream of the trading engine. \n\nWe have deployed additional automated feed validators to detect potential similar issues in the future and to alert us earlier.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2019-06-24T19:36:17Z", "resolved_inferred": false, "started_at": "2026-02-26T07:57:57Z", diff --git a/api/v/bitpanda.json b/api/v/bitpanda.json index a292173544b1a29e9fc0be445437a6160289bc73..edcfafc8e17a06117c23518c97b5fd612120d060 100644 --- a/api/v/bitpanda.json +++ b/api/v/bitpanda.json @@ -3,7 +3,7 @@ "slug": "bitpanda", "platform": "statuspage", "status_url": "https://status.bitpanda.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "partial", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-19T18:31:43.727+02:00", "resolved_inferred": false, "started_at": "2026-08-19T17:58:48.165+02:00", @@ -25,7 +25,7 @@ "body": "The incident has been resolved and Digistocks are available for trading again.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-14T08:37:33.211+02:00", "resolved_inferred": false, "started_at": "2026-08-13T10:15:18.077+02:00", @@ -38,7 +38,7 @@ "body": "The issue has been resolved and real-stock trading is available.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-14T08:38:40.267+02:00", "resolved_inferred": false, "started_at": "2026-08-13T08:15:53.843+02:00", @@ -51,7 +51,7 @@ "body": "This incident has been resolved. All fiat withdrawal, deposit, and account verification services are operating normally.\nWithdrawals that were rejected during the disruption were automatically refunded. Deposits that were delayed have now been processed.\nWe apologize for the inconvenience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-22T13:04:41.507+02:00", "resolved_inferred": false, "started_at": "2026-07-21T13:38:20.038+02:00", @@ -64,7 +64,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-23T16:37:08.225+02:00", "resolved_inferred": false, "started_at": "2026-06-23T14:55:48.000+02:00", @@ -77,7 +77,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-21T16:15:10.919+02:00", "resolved_inferred": false, "started_at": "2026-06-21T15:57:36.290+02:00", @@ -90,7 +90,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-04T15:49:53.693+02:00", "resolved_inferred": false, "started_at": "2026-06-04T09:43:24.668+02:00", @@ -103,7 +103,7 @@ "body": "A fix has been implemented.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-05T10:57:28.231+02:00", "resolved_inferred": false, "started_at": "2026-06-02T19:18:14.810+02:00", @@ -116,7 +116,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-02T15:15:30.617+02:00", "resolved_inferred": false, "started_at": "2026-06-02T13:15:59.013+02:00", @@ -129,7 +129,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-21T08:19:44.573+02:00", "resolved_inferred": false, "started_at": "2026-05-21T08:03:53.025+02:00", @@ -142,7 +142,7 @@ "body": "The issue has been resolved", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-04T20:19:57.676+02:00", "resolved_inferred": false, "started_at": "2026-05-04T19:22:02.058+02:00", @@ -155,7 +155,7 @@ "body": "The issue had been solved by our card payment provider.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-29T22:22:47.000+02:00", "resolved_inferred": false, "started_at": "2026-04-29T21:10:02.522+02:00", @@ -168,7 +168,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-17T09:02:38.866+02:00", "resolved_inferred": false, "started_at": "2026-04-16T14:56:59.000+02:00", @@ -181,7 +181,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-16T13:46:00.809+02:00", "resolved_inferred": false, "started_at": "2026-04-15T16:27:08.183+02:00", @@ -194,7 +194,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-08T13:23:23.979+02:00", "resolved_inferred": false, "started_at": "2026-04-08T10:34:42.000+02:00", @@ -207,7 +207,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-27T17:59:19.649+01:00", "resolved_inferred": false, "started_at": "2026-03-27T17:25:07.154+01:00", @@ -220,7 +220,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-24T19:42:09.308+01:00", "resolved_inferred": false, "started_at": "2026-03-24T18:52:43.551+01:00", @@ -233,7 +233,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-25T14:24:38.089+01:00", "resolved_inferred": false, "started_at": "2026-03-24T12:55:22.223+01:00", @@ -246,7 +246,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-21T22:20:38.219+01:00", "resolved_inferred": false, "started_at": "2026-03-21T19:39:58.682+01:00", @@ -259,7 +259,7 @@ "body": "All pending transactions have been processed.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-09T19:28:26.778+01:00", "resolved_inferred": false, "started_at": "2026-03-09T14:52:15.446+01:00", @@ -272,7 +272,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-25T17:39:09.587+01:00", "resolved_inferred": false, "started_at": "2026-02-24T17:30:21.198+01:00", @@ -285,7 +285,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-02T19:59:55.351+01:00", "resolved_inferred": false, "started_at": "2026-02-02T18:44:02.790+01:00", @@ -298,7 +298,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-27T19:47:49.810+01:00", "resolved_inferred": false, "started_at": "2026-01-27T18:35:47.997+01:00", @@ -311,7 +311,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-05T10:21:10.939+01:00", "resolved_inferred": false, "started_at": "2025-12-05T10:02:10.706+01:00", @@ -324,7 +324,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-27T22:49:06.074+01:00", "resolved_inferred": false, "started_at": "2025-11-27T22:02:10.225+01:00", @@ -337,7 +337,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-22T18:27:35.084+01:00", "resolved_inferred": false, "started_at": "2025-11-22T17:31:41.000+01:00", @@ -350,7 +350,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-01T09:33:11.791+01:00", "resolved_inferred": false, "started_at": "2025-11-21T16:15:13.588+01:00", @@ -363,7 +363,7 @@ "body": "Trading has been resumed for the affected assets and normal service has been restored.\nWe\u2019ll continue to monitor performance to ensure everything remains stable. Thank you for your patience and understanding.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-13T14:30:35.693+01:00", "resolved_inferred": false, "started_at": "2025-11-13T13:16:59.757+01:00", @@ -376,7 +376,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-13T16:40:37.190+01:00", "resolved_inferred": false, "started_at": "2025-11-11T13:55:14.179+01:00", @@ -389,7 +389,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-11T13:41:13.658+01:00", "resolved_inferred": false, "started_at": "2025-11-11T10:30:47.783+01:00", @@ -402,7 +402,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-06T18:49:35.697+01:00", "resolved_inferred": false, "started_at": "2025-11-06T17:38:33.540+01:00", @@ -415,7 +415,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-01T19:13:12.322+01:00", "resolved_inferred": false, "started_at": "2025-11-01T17:23:07.665+01:00", @@ -428,7 +428,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-01T21:34:09.891+01:00", "resolved_inferred": false, "started_at": "2025-11-01T14:03:44.273+01:00", @@ -441,7 +441,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-20T15:05:25.232+02:00", "resolved_inferred": false, "started_at": "2025-10-20T10:36:53.286+02:00", @@ -454,7 +454,7 @@ "body": "The issue has been resolved and deposits through Paypal are available again.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-16T19:32:23.873+02:00", "resolved_inferred": false, "started_at": "2025-10-16T18:33:53.960+02:00", @@ -467,7 +467,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-12T01:42:32.188+02:00", "resolved_inferred": false, "started_at": "2025-10-11T20:23:23.367+02:00", @@ -480,7 +480,7 @@ "body": "The incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-11T14:27:55.510+02:00", "resolved_inferred": false, "started_at": "2025-10-11T13:05:25.817+02:00", @@ -493,7 +493,7 @@ "body": "Bitpanda has experienced a platform-wide outage due to the recent news in the market that triggered a liquidation chain affecting most exchanges and brokers.\n\nWe apologise for the inconvenience this incident has caused.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-10T23:20:00.000+02:00", "resolved_inferred": false, "started_at": "2025-10-10T23:20:00.000+02:00", @@ -506,7 +506,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-03T14:23:28.314+02:00", "resolved_inferred": false, "started_at": "2025-09-29T19:43:50.981+02:00", @@ -519,7 +519,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-23T09:57:39.896+02:00", "resolved_inferred": false, "started_at": "2025-09-23T09:13:50.751+02:00", @@ -532,7 +532,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-06T12:00:49.391+02:00", "resolved_inferred": false, "started_at": "2025-08-21T19:34:55.000+02:00", @@ -545,7 +545,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-01T17:25:33.021+02:00", "resolved_inferred": false, "started_at": "2025-08-01T15:01:45.844+02:00", diff --git a/api/v/bitrise.json b/api/v/bitrise.json index cdf579d7e7a1fd6970546b35aed5b0a137145646..de2ff21b888cc111ce7278c69ffb1d02a60ce9d6 100644 --- a/api/v/bitrise.json +++ b/api/v/bitrise.json @@ -3,7 +3,7 @@ "slug": "bitrise", "platform": "statuspage", "status_url": "https://status.bitrise.io", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-28T13:33:53.393Z", "resolved_inferred": false, "started_at": "2026-08-28T13:01:48.494Z", @@ -25,7 +25,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-07T14:00:20.258Z", "resolved_inferred": false, "started_at": "2026-08-07T13:02:32.556Z", @@ -38,7 +38,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-31T13:29:23.365Z", "resolved_inferred": false, "started_at": "2026-07-30T15:40:35.000Z", @@ -51,7 +51,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-17T00:13:44.047Z", "resolved_inferred": false, "started_at": "2026-07-16T23:04:35.878Z", @@ -64,7 +64,7 @@ "body": "We experienced a brief period of high error rates on our website. The issue was resolved after a rollback.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-16T14:51:45.000Z", "resolved_inferred": false, "started_at": "2026-07-16T14:51:45.000Z", @@ -77,7 +77,7 @@ "body": "This incident has been resolved. We experienced a network outage in our ORD data center caused by dropped packets between nodes, which led to failed health checks and a cluster-wide disruption. The outage was mitigated on July 14, and we've since applied network configuration changes across all our data centers to address the underlying cause and prevent recurrence. We apologize for the disruption it caused.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-15T18:13:58.227Z", "resolved_inferred": false, "started_at": "2026-07-14T16:40:23.438Z", @@ -90,7 +90,7 @@ "body": "This incident has been resolved. Some builds may still experience slower clone operations from GitHub due to performance degradation affecting Git operations in some of our datacenters. As a workaround, use Bitrise key-based caching for SPM dependencies so builds do not re-resolve them over the slow path. Add Restore SPM Cache (restore-spm-cache@3) before your dependency-resolution/build step and Save SPM Cache (save-spm-cache@1) after your dependency resolution and build steps \u2014 no extra configuration needed. Please note that Bitrise does not cache your source code; your repository must still be cloned to fetch the latest changes. If a build fails or hangs during code fetch, retry the build to attempt the clone operation again.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-15T18:10:43.920Z", "resolved_inferred": false, "started_at": "2026-07-14T15:35:30.930Z", @@ -103,7 +103,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-13T10:49:58.866Z", "resolved_inferred": false, "started_at": "2026-07-13T09:08:01.878Z", @@ -116,7 +116,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-10T19:50:54.955Z", "resolved_inferred": false, "started_at": "2026-07-10T17:49:26.673Z", @@ -129,7 +129,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-09T12:12:13.430Z", "resolved_inferred": false, "started_at": "2026-07-09T09:05:31.576Z", @@ -142,7 +142,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-08T21:30:49.017Z", "resolved_inferred": false, "started_at": "2026-07-08T20:19:59.000Z", @@ -155,7 +155,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-09T07:57:08.094Z", "resolved_inferred": false, "started_at": "2026-07-08T13:54:44.165Z", @@ -168,7 +168,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-07T15:09:45.725Z", "resolved_inferred": false, "started_at": "2026-07-07T15:06:07.241Z", @@ -181,7 +181,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-27T08:25:10.745Z", "resolved_inferred": false, "started_at": "2026-06-26T19:40:42.398Z", @@ -194,7 +194,7 @@ "body": "We improved the handling of transient Firebase errors, Virtual Device Steps are back to normal.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-26T06:14:29.232Z", "resolved_inferred": false, "started_at": "2026-06-25T10:28:18.995Z", @@ -207,7 +207,7 @@ "body": "We have observed some malformed data appearing in build logs, we have quickly issues a fix and this has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-23T09:00:00.000Z", "resolved_inferred": false, "started_at": "2026-06-23T09:00:00.000Z", @@ -220,7 +220,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-17T16:29:54.624Z", "resolved_inferred": false, "started_at": "2026-06-17T15:34:34.000Z", @@ -233,7 +233,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-11T20:39:21.435Z", "resolved_inferred": false, "started_at": "2026-06-11T20:26:52.342Z", @@ -246,7 +246,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-11T18:46:39.662Z", "resolved_inferred": false, "started_at": "2026-06-11T16:50:18.688Z", @@ -259,7 +259,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-03T08:52:22.866Z", "resolved_inferred": false, "started_at": "2026-05-28T15:00:11.930Z", @@ -272,7 +272,7 @@ "body": "This incident is now resolved, and impacted services are now operating.\n\nOur teams identified the root cause, released a fix, and were monitoring our systems continuously to ensure the mitigation is safe. We'll conduct an internal post-mortem to understand what happened and learn how to avoid a similar outage in the future.\n\nThank you for your patience and understanding. If you encounter any issues, please reach out to our Support team:\n\nhttps://support.bitrise.io/en/", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-01T21:50:36.633Z", "resolved_inferred": false, "started_at": "2026-04-30T11:34:31.683Z", @@ -285,7 +285,7 @@ "body": "On April 28, 2026, rate limiting by Maven Central began causing 429 errors for Bitrise-hosted CI jobs attempting to download dependencies. We responded by enabling a proxy layer to mirror Maven packages within Bitrise in order to reduce load on Maven Central. The proxy service is working as intended, and the vast majority of dependency downloads over the previous 1.5 days have been served by Bitrise. There was, however, a subset of Bitrise CI jobs that were in the long tail and still experiencing 429 errors, even when following our recommended steps for using the mirror. Over the past several hours, we have evenly distributed traffic flow and have addressed the edge cases in customer Gradle configurations that bypassed the mirror.\n\nIf you are still experiencing 429 rate-limiting errors when installing dependencies, and you have already followed the recommended steps for using the mirror, please reach out to us at support@bitrise.io.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-29T20:24:42.577Z", "resolved_inferred": false, "started_at": "2026-04-29T10:36:21.002Z", @@ -298,7 +298,7 @@ "body": "This incident is now resolved and impacted services are now operating without issues.\n\nOur teams identified the root cause, released a fix and were monitoring our systems continuously to ensure the mitigation is safe. We'll conduct an internal post-mortem to understand what happened and learn how to avoid a similar outage in the future.\n\nThank you for your patience and understanding. If you encounter any issues, please reach out to our Support team:\n\nhttps://support.bitrise.io/en/", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-28T22:14:25.691Z", "resolved_inferred": false, "started_at": "2026-04-28T13:38:13.813Z", @@ -311,7 +311,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-28T17:27:49.756Z", "resolved_inferred": false, "started_at": "2026-04-28T12:29:05.881Z", @@ -324,7 +324,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-20T19:45:26.257Z", "resolved_inferred": false, "started_at": "2026-04-20T16:37:06.000Z", @@ -337,7 +337,7 @@ "body": "This incident is now resolved, and impacted services are now operating without issues.\n\nOur teams identified the root cause, released a fix, and were monitoring our systems continuously to ensure the mitigation is safe. We'll conduct an internal post-mortem to understand what happened and learn how to avoid a similar outage in the future.\n\nThank you for your patience and understanding. If you encounter any issues, please reach out to our Support team:\n\nhttps://support.bitrise.io/en/", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-15T20:54:58.338Z", "resolved_inferred": false, "started_at": "2026-04-15T20:23:40.000Z", @@ -350,7 +350,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-19T22:43:12.101Z", "resolved_inferred": false, "started_at": "2026-03-19T16:52:15.069Z", @@ -363,7 +363,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-09T15:41:49.583Z", "resolved_inferred": false, "started_at": "2026-03-09T12:21:24.983Z", @@ -376,7 +376,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-05T12:14:26.679Z", "resolved_inferred": false, "started_at": "2026-03-05T11:43:38.675Z", @@ -389,7 +389,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-02T17:32:38.187Z", "resolved_inferred": false, "started_at": "2026-03-02T15:59:11.417Z", @@ -402,7 +402,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-02T15:57:29.821Z", "resolved_inferred": false, "started_at": "2026-03-02T13:27:48.420Z", @@ -415,7 +415,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-02T11:46:16.254Z", "resolved_inferred": false, "started_at": "2026-03-02T11:37:17.797Z", @@ -428,7 +428,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-11T17:48:43.310Z", "resolved_inferred": false, "started_at": "2026-02-11T14:59:48.000Z", @@ -441,7 +441,7 @@ "body": "We observed high error rates affecting our static site (bitrise.io) due to Cloudflare\u2019s incident between 8:56 - 9:12 UTC \n\napp.bitrise.io was unaffected", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-05T09:00:00.000Z", "resolved_inferred": false, "started_at": "2025-12-05T09:00:00.000Z", @@ -454,7 +454,7 @@ "body": "This incident is now resolved and impacted services are now operating without issues.\n\nOur teams identified the root cause, released a fix and were monitoring our systems continuously to ensure the mitigation is safe. We'll conduct an internal post-mortem to understand what happened and learn how to avoid a similar outage in the future.\n\nThank you for your patience and understanding. If you encounter any issues, please reach out to our Support team:\n\nhttps://support.bitrise.io/en/", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-03T10:59:19.746Z", "resolved_inferred": false, "started_at": "2025-12-03T10:18:18.546Z", @@ -467,7 +467,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-27T14:28:04.516Z", "resolved_inferred": false, "started_at": "2025-11-26T16:09:25.000Z", @@ -480,7 +480,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-25T17:20:32.971Z", "resolved_inferred": false, "started_at": "2025-11-25T16:55:49.000Z", @@ -493,7 +493,7 @@ "body": "Wait times have now dropped to approximately 30 seconds across most queues. This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-18T20:38:41.101Z", "resolved_inferred": false, "started_at": "2025-11-18T17:20:34.279Z", @@ -506,7 +506,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-18T20:36:25.848Z", "resolved_inferred": false, "started_at": "2025-11-18T11:53:13.462Z", @@ -519,7 +519,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-10T11:14:04.510Z", "resolved_inferred": false, "started_at": "2025-11-10T11:10:39.000Z", @@ -532,7 +532,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-30T17:55:53.854Z", "resolved_inferred": false, "started_at": "2025-10-30T16:18:34.000Z", @@ -545,7 +545,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-28T19:04:49.514Z", "resolved_inferred": false, "started_at": "2025-10-28T16:21:52.804Z", @@ -558,7 +558,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-24T12:23:26.641Z", "resolved_inferred": false, "started_at": "2025-10-24T09:48:02.680Z", @@ -571,7 +571,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-20T23:37:19.994Z", "resolved_inferred": false, "started_at": "2025-10-20T16:27:29.891Z", @@ -584,7 +584,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-20T14:24:00.072Z", "resolved_inferred": false, "started_at": "2025-10-20T10:10:25.765Z", @@ -597,7 +597,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-14T17:16:13.220Z", "resolved_inferred": false, "started_at": "2025-10-14T16:52:03.023Z", @@ -610,7 +610,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-02T12:43:38.797Z", "resolved_inferred": false, "started_at": "2025-10-02T12:31:45.230Z", @@ -623,7 +623,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-08T18:55:53.491Z", "resolved_inferred": false, "started_at": "2025-09-08T17:08:26.874Z", @@ -636,7 +636,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-06T15:17:53.938Z", "resolved_inferred": false, "started_at": "2025-09-06T14:41:36.526Z", diff --git a/api/v/bitso.json b/api/v/bitso.json index ea9ed998dd3dd7dea3051579b57c10562b1a717a..d8de7c4921120c24de4531f13511860138ea9d71 100644 --- a/api/v/bitso.json +++ b/api/v/bitso.json @@ -3,7 +3,7 @@ "slug": "bitso", "platform": "statuspage", "status_url": "https://status.bitso.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "maintenance", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-09-03T17:04:39.500Z", "resolved_inferred": false, "started_at": "2026-09-03T13:04:10.000Z", @@ -25,7 +25,7 @@ "body": "Scheduled maintenance is currently in progress. We will provide updates as necessary.", "first_seen": "2026-09-04T07:06:16Z", "impact": "maintenance", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "started_at": "2026-09-02T15:18:00.000Z", "state": "maintenance", "title": "Important update: ACX (Across Protocol) will be delisted", @@ -36,7 +36,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-09-01T20:15:27.000Z", "resolved_inferred": false, "started_at": "2026-09-01T19:37:09.179Z", @@ -49,7 +49,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-31T16:12:13.451Z", "resolved_inferred": false, "started_at": "2026-08-31T14:02:02.523Z", @@ -62,7 +62,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-29T19:13:50.911Z", "resolved_inferred": false, "started_at": "2026-08-28T23:53:26.928Z", @@ -75,7 +75,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-28T21:23:26.026Z", "resolved_inferred": false, "started_at": "2026-08-28T19:10:19.525Z", @@ -88,7 +88,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-21T14:39:54.156Z", "resolved_inferred": false, "started_at": "2026-08-21T13:35:25.326Z", @@ -101,7 +101,7 @@ "body": "Resolved: Our payment processing provider has resolved the issue and BRL withdrawals via PIX are operating normally again. Any withdrawal requests that previously failed or were delayed should now be processing as expected. If you continue to experience problems, please contact our support team. Thank you for your patience.\n\n---\n\nResuelto: Nuestro proveedor de procesamiento de pagos resolvi\u00f3 el problema y los retiros de reales brasile\u00f1os (BRL) mediante PIX ya operan con normalidad. Las solicitudes de retiro que anteriormente fallaron o se demoraron deber\u00edan procesarse con normalidad. Si contin\u00faas experimentando problemas, comun\u00edcate con nuestro equipo de soporte. Gracias por tu paciencia.\n\n---\n\nResolvido: Nosso provedor de processamento de pagamentos resolveu o problema e os saques em reais (BRL) via PIX voltaram a operar normalmente. As solicita\u00e7\u00f5es de saque que falharam ou sofreram atrasos anteriormente devem ser processadas normalmente. Se voc\u00ea continuar enfrentando problemas, entre em contato com nossa equipe de suporte. Obrigado pela sua paci\u00eancia.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-20T03:42:35.478Z", "resolved_inferred": false, "started_at": "2026-08-19T22:26:02.965Z", @@ -114,7 +114,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-19T15:01:41.699Z", "resolved_inferred": false, "started_at": "2026-08-19T14:33:14.984Z", @@ -127,7 +127,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-12T22:14:42.706Z", "resolved_inferred": false, "started_at": "2026-08-12T21:01:31.253Z", @@ -140,7 +140,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-04T13:37:29.508Z", "resolved_inferred": false, "started_at": "2026-08-03T16:48:27.567Z", @@ -153,7 +153,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-13T12:56:07.465Z", "resolved_inferred": false, "started_at": "2026-07-13T11:37:03.395Z", @@ -166,7 +166,7 @@ "body": "All pending rewards have been successfully processed and disbursed to affected accounts. Balances should now accurately reflect these distributions. We appreciate your patience while we resolved this issue.\n\nIf you need further assistance, please contact our Customer Support team at https://support.bitso.com/.\n\n-----------------------\n\nLos rendimientos pendientes han sido procesados y distribuidos con \u00e9xito a las cuentas afectadas. Los saldos ya deber\u00edan reflejar con precisi\u00f3n estas distribuciones. Agradecemos su paciencia mientras resolv\u00edamos este problema.\n\nSi necesita ayuda, comun\u00edquese con nuestro equipo de Atenci\u00f3n al Cliente en https://support.bitso.com/.\n\n-----------------------\n\nTodas as recompensas pendentes foram processadas e distribu\u00eddas com sucesso para as contas afetadas. Os saldos j\u00e1 devem refletir com precis\u00e3o essas distribui\u00e7\u00f5es. Agradecemos a sua paci\u00eancia enquanto corr\u00edamos atr\u00e1s para resolver este problema.\n\nSe voc\u00ea tiver alguma d\u00favida ou precisar de assist\u00eancia, por favor, entre em contato com a nossa equipe de Suporte ao Cliente em https://support.bitso.com/.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-07T18:36:11.690Z", "resolved_inferred": false, "started_at": "2026-07-07T12:18:31.806Z", @@ -179,7 +179,7 @@ "body": "SPEI deposits and withdrawals have been fully restored following the completion of Banxico's daily operative day change. All queued transactions are being processed.\n\nWe have identified that this disruption lasted longer than expected due to a secondary database issue on our payment infrastructure. We are taking steps to prevent recurrence.\n\nThank you for your patience.\n---\nLos dep\u00f3sitos y retiros v\u00eda SPEI han sido completamente restaurados tras la finalizaci\u00f3n del cambio de d\u00eda operativo de Banxico. Las transacciones en cola est\u00e1n siendo procesadas.\n\nIdentificamos que la interrupci\u00f3n dur\u00f3 m\u00e1s de lo esperado debido a un problema secundario en la base de datos de nuestra infraestructura de pagos. Estamos tomando medidas para prevenir que se repita.\n\nGracias por su paciencia.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-07T00:57:11.428Z", "resolved_inferred": false, "started_at": "2026-07-07T00:25:57.006Z", @@ -192,7 +192,7 @@ "body": "This incident has been resolved.\n\n------------------\n\nEste incidente ha sido resuelto.\n\n------------------\n\nEste incidente foi resolvido.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-30T19:40:39.010Z", "resolved_inferred": false, "started_at": "2026-06-30T17:59:51.000Z", @@ -205,7 +205,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-25T20:27:53.423Z", "resolved_inferred": false, "started_at": "2026-06-25T16:57:19.640Z", @@ -218,7 +218,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-13T01:49:38.720Z", "resolved_inferred": false, "started_at": "2026-06-13T00:10:48.000Z", @@ -231,7 +231,7 @@ "body": "All queued ARS withdrawals have been successfully processed and services are operating normally.\n\nWe apologize for the inconvenience caused earlier today and thank you for your patience.\n\n---------------\n\nTodos los retiros en ARS que se encontraban pendientes han sido procesados exitosamente y los servicios est\u00e1n operando con normalidad.\n\nLamentamos los inconvenientes ocasionados el d\u00eda de hoy y agradecemos su paciencia.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-12T20:44:36.152Z", "resolved_inferred": false, "started_at": "2026-06-12T19:57:53.766Z", @@ -244,7 +244,7 @@ "body": "Resolved. The sell window and liquidation process for H (Humanity Protocol) have concluded.\nAs previously announced, Bitso discontinued H following a confirmed security incident that affected the original H token contract in June 2026. Selling ended on August 6, 2026 at 18:00 UTC, and any remaining H balances have since been automatically converted to Digital Dollars at market price and credited to holders' accounts.\nDeposits, withdrawals, buying, and selling for H remain permanently disabled. This discontinuation is final: there is no migration, airdrop, or replacement token for H, and Bitso does not list or support the new HUMANITY token.\nIf you held H and haven't seen your balance reflecting a Digital Dollars credit in your account, please contact Support.\n\n-----------------------------------------------------\n\nResuelto. La ventana de venta y el proceso de liquidaci\u00f3n de H (Humanity Protocol) han concluido.\nComo se anunci\u00f3 previamente, Bitso descontinu\u00f3 H tras un incidente de seguridad confirmado que afect\u00f3 al contrato original del token H en junio de 2026. La venta finaliz\u00f3 el 6 de agosto de 2026 a las 18:00 UTC, y cualquier saldo restante de H ha sido convertido autom\u00e1ticamente a D\u00f3lares Digitales a precio de mercado y acreditado en las cuentas de los usuarios.\nLos dep\u00f3sitos, retiros, compra y venta de H permanecen deshabilitados de forma permanente. Esta descontinuaci\u00f3n es definitiva: no habr\u00e1 migraci\u00f3n, airdrop ni token de reemplazo para H, y Bitso no lista ni da soporte al nuevo token HUMANITY.\nSi ten\u00edas H y no ves reflejado el dep\u00f3sito de D\u00f3lares Digitales en tu cuenta, por favor contacta a Soporte.\n\n-----------------------------------------------------\n\nResolvido. A janela de venda e o processo de liquida\u00e7\u00e3o do H (Humanity Protocol) foram conclu\u00eddos.\nComo anunciado anteriormente, a Bitso descontinuou o H ap\u00f3s um incidente de seguran\u00e7a confirmado que afetou o contrato original do token H em junho de 2026. A venda foi encerrada em 6 de agosto de 2026, \u00e0s 18h00 UTC, e qualquer saldo restante de H foi convertido automaticamente para D\u00f3lares Digitais ao pre\u00e7o de mercado e creditado nas contas dos usu\u00e1rios.\nDep\u00f3sitos, saques, compra e venda de H permanecem desativados permanentemente. Essa descontinua\u00e7\u00e3o \u00e9 definitiva: n\u00e3o haver\u00e1 migra\u00e7\u00e3o, airdrop ou token de substitui\u00e7\u00e3o para o H, e a Bitso n\u00e3o lista nem oferece suporte ao novo token HUMANITY.\nSe voc\u00ea possu\u00eda H e n\u00e3o v\u00ea seu saldo refletido como um cr\u00e9dito em D\u00f3lares Digitais em sua conta, entre em contato com o Suporte.\nTodos os sistemas est\u00e3o operando normalmente.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-06T19:25:07.078Z", "resolved_inferred": false, "started_at": "2026-06-09T14:45:35.000Z", @@ -257,7 +257,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-07T12:13:55.786Z", "resolved_inferred": false, "started_at": "2026-06-07T11:41:33.205Z", @@ -270,7 +270,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-03T00:35:09.985Z", "resolved_inferred": false, "started_at": "2026-06-02T21:35:45.698Z", @@ -283,7 +283,7 @@ "body": "Following a period of close monitoring, we can confirm that deposit performance is completely stable and processing times have returned to normal. Consequently, this incident has been resolved.\n\nThank you once again for your patience and support throughout this process!\n\n----------------\n\nTras el per\u00edodo de monitoreo, podemos confirmar que el rendimiento de los dep\u00f3sitos es completamente estable y los tiempos de procesamiento han vuelto a la normalidad. En consecuencia, este incidente ha sido resuelto.\n\n\u00a1Agradecemos una vez m\u00e1s su paciencia y apoyo a lo largo de este proceso!", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-02T20:04:42.692Z", "resolved_inferred": false, "started_at": "2026-06-02T13:51:46.613Z", @@ -296,7 +296,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-02T12:07:41.132Z", "resolved_inferred": false, "started_at": "2026-06-02T09:48:09.752Z", @@ -309,7 +309,7 @@ "body": "This incident has been resolved.\n\n------------------------------------------------\n\nEste incidente ha sido resuelto.\n\n------------------------------------------------\n\nEste incidente foi resolvido.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-27T17:21:56.895Z", "resolved_inferred": false, "started_at": "2026-05-27T14:59:17.200Z", @@ -322,7 +322,7 @@ "body": "We are pleased to inform you that the Hedera Mainnet has stabilized. Consequently, HBAR deposits and withdrawals have been fully re-enabled on our platform.\n\nThank you for your patience and understanding while our team monitored the situation. As a reminder, your funds remained completely safe throughout this brief disruption.\n\nIf you have any remaining questions or need assistance with a transaction, please reach out to our Customer Support team at https://support.bitso.com/.\n\n----------------------------------------------\n\nNos complace informar que la red principal de Hedera (Hedera Mainnet) se ha estabilizado. Por lo tanto, los dep\u00f3sitos y retiros de HBAR han sido completamente rehabilitados en nuestra plataforma.\n\nAgradecemos tu paciencia y comprensi\u00f3n mientras nuestro equipo monitoreaba la situaci\u00f3n. Te recordamos que tus fondos permanecieron completamente seguros durante esta breve interrupci\u00f3n.\n\nSi tienes alguna duda o necesitas asistencia con una transacci\u00f3n, por favor ponte en contacto con nuestro equipo de Soporte al Cliente en https://support.bitso.com/.\n\n----------------------------------------------\n\nTemos o prazer de informar que a rede principal da Hedera (Hedera Mainnet) j\u00e1 se estabilizou. Consequentemente, os dep\u00f3sitos e saques de HBAR foram totalmente reativados em nossa plataforma.\n\nAgradecemos a sua paci\u00eancia e compreens\u00e3o enquanto a nossa equipe monitorava a situa\u00e7\u00e3o. Lembramos que os seus fundos permaneceram totalmente seguros durante esta breve interrup\u00e7\u00e3o.\n\nSe voc\u00ea tiver alguma d\u00favida ou precisar de assist\u00eancia com alguma transa\u00e7\u00e3o, por favor, entre em contato com a nossa equipe de Suporte ao Cliente em https://support.bitso.com/.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-20T18:49:18.424Z", "resolved_inferred": false, "started_at": "2026-05-20T18:30:03.260Z", @@ -335,7 +335,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-08T09:04:36.332Z", "resolved_inferred": false, "started_at": "2026-05-08T04:44:32.749Z", @@ -348,7 +348,7 @@ "body": "We have resolved an incident that affected COP withdrawals between 9:08 and 10:14 AM COT. Withdrawals are now processing normally.\n\nYour balance and assets remain completely safe and unaffected.\n\nWe apologize for any inconvenience this may have caused. If you require further assistance, do not hesitate to contact our Customer Support team at https://support.bitso.com.\n\n--------------\n\nHemos resuelto un incidente que afect\u00f3 los retiros en COP entre las 9:08 y las 10:14 AM COT. Los retiros ya se est\u00e1n procesando con normalidad.\n\nTu saldo y activos permanecen completamente seguros y no se han visto afectados.\n\nLamentamos las molestias que esto pudo haber causado. Si necesitas ayuda adicional, no dudes en contactar a nuestro equipo de Soporte al Cliente en https://support.bitso.com.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-28T15:54:06.991Z", "resolved_inferred": false, "started_at": "2026-04-28T15:54:06.955Z", @@ -361,7 +361,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-27T14:14:13.445Z", "resolved_inferred": false, "started_at": "2026-04-26T18:39:26.830Z", @@ -374,7 +374,7 @@ "body": "This incident has been resolved.\n\n---------------------------\n\nEste incidente ha sido resuelto.\n\n---------------------------\n\nEste incidente foi resolvido.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-28T20:08:27.570Z", "resolved_inferred": false, "started_at": "2026-04-25T21:11:29.872Z", @@ -387,7 +387,7 @@ "body": "This incident has been resolved.\n\n--------------------\n\nEste incidente ha sido resuelto.\n\n--------------------\n\nEste incidente foi resolvido.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-20T18:07:10.271Z", "resolved_inferred": false, "started_at": "2026-04-20T17:39:27.000Z", @@ -400,7 +400,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-16T11:54:05.239Z", "resolved_inferred": false, "started_at": "2026-04-16T11:05:54.911Z", @@ -413,7 +413,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-14T00:36:13.087Z", "resolved_inferred": false, "started_at": "2026-04-14T00:24:01.168Z", @@ -426,7 +426,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-10T05:34:15.000Z", "resolved_inferred": false, "started_at": "2026-04-10T00:47:09.859Z", @@ -439,7 +439,7 @@ "body": "The issue affecting our withdrawal service has been fully resolved, all withdrawal routes\u2014including MXN, PIX, ARS, have been re-enabled and are now fully operational. Our team has verified end-to-end transactions across all platforms, and monitoring shows that service levels have returned to normal. \n\nWe apologize for the inconvenience and appreciate your patience.\n\n-----------------------------------\n\nEl problema que afectaba nuestro servicio de retiros ha sido completamente resuelto. Tras la estabilizaci\u00f3n de nuestros sistemas de bases de datos, todas las rutas de retiro \u2014incluyendo MXN, PIX, ARS y Lightning Network\u2014 han sido reactivadas progresivamente y operan con normalidad. Nuestro equipo ha verificado transacciones de extremo a extremo en todas las plataformas y el monitoreo confirma que los niveles de servicio se han normalizado. \n\nLamentamos los inconvenientes y agradecemos su paciencia.\n\n-----------------------------------\n\nO problema que afetava nosso servi\u00e7o de saques foi totalmente resolvido. Ap\u00f3s a estabiliza\u00e7\u00e3o de nossos sistemas de banco de dados, todas as rotas de saque \u2014 incluindo MXN, PIX, ARS e Lightning Network \u2014 foram reativadas progressivamente e agora est\u00e3o totalmente operacionais. Nossa equipe verificou as transa\u00e7\u00f5es de ponta a ponta em todas as plataformas e o monitoramento mostra que os n\u00edveis de servi\u00e7o retornaram ao normal. \n\nLamentamos o inconveniente e agradecemos a sua paci\u00eancia.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-08T22:19:12.104Z", "resolved_inferred": false, "started_at": "2026-04-08T20:06:34.804Z", @@ -452,7 +452,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-07T06:43:02.755Z", "resolved_inferred": false, "started_at": "2026-04-07T04:06:29.744Z", @@ -465,7 +465,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-07T02:14:08.523Z", "resolved_inferred": false, "started_at": "2026-04-07T00:44:13.735Z", @@ -478,7 +478,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-07T00:35:51.565Z", "resolved_inferred": false, "started_at": "2026-04-06T20:43:43.611Z", @@ -491,7 +491,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-06T18:32:35.347Z", "resolved_inferred": false, "started_at": "2026-04-06T16:26:20.088Z", @@ -504,7 +504,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-01T22:58:02.895Z", "resolved_inferred": false, "started_at": "2026-04-01T19:36:52.176Z", @@ -517,7 +517,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-31T06:12:53.784Z", "resolved_inferred": false, "started_at": "2026-03-31T03:03:36.432Z", @@ -530,7 +530,7 @@ "body": "This incident has been resolved.\n\n------------------------------\n\nEste incidente ha sido resuelto.\n\n------------------------------\n\nEste incidente foi resolvido.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-24T19:13:14.395Z", "resolved_inferred": false, "started_at": "2026-03-24T17:17:24.155Z", @@ -543,7 +543,7 @@ "body": "This incident has been resolved.\n\n----------------------------------------------------------------------\n\nEste incidente ha sido resuelto.\n\n----------------------------------------------------------------------\n\nEste incidente foi resolvido.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-18T18:03:34.663Z", "resolved_inferred": false, "started_at": "2026-03-18T13:44:19.466Z", @@ -556,7 +556,7 @@ "body": "This incident has been resolved.\n\n---------------------------------\n\nEste incidente ha sido resuelto.\n\n---------------------------------\n\nEste incidente foi resolvido.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-17T20:19:03.657Z", "resolved_inferred": false, "started_at": "2026-03-17T19:21:23.000Z", @@ -569,7 +569,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-16T10:38:22.447Z", "resolved_inferred": false, "started_at": "2026-03-16T10:17:12.000Z", @@ -582,7 +582,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-13T05:07:57.271Z", "resolved_inferred": false, "started_at": "2026-03-13T02:31:21.000Z", @@ -595,7 +595,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-03T02:59:08.564Z", "resolved_inferred": false, "started_at": "2026-03-03T01:31:54.753Z", @@ -608,7 +608,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-02T15:40:34.192Z", "resolved_inferred": false, "started_at": "2026-03-02T14:52:15.541Z", @@ -621,7 +621,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-28T16:59:48.441Z", "resolved_inferred": false, "started_at": "2026-02-28T13:02:33.000Z", @@ -634,7 +634,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-26T20:15:40.098Z", "resolved_inferred": false, "started_at": "2026-02-26T13:45:03.054Z", @@ -647,7 +647,7 @@ "body": "This incident has been resolved.\n\n-------------------\n\nEste incidente ha sido resuelto.\n\n-------------------\n\nEste incidente foi resolvido.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-12T18:56:08.496Z", "resolved_inferred": false, "started_at": "2026-02-12T17:26:55.000Z", @@ -660,7 +660,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-05T22:24:14.760Z", "resolved_inferred": false, "started_at": "2026-02-05T20:17:23.981Z", diff --git a/api/v/bittitan.json b/api/v/bittitan.json index 6e405a5dded53cf0ee2917fe15a7aa964a745a8c..f65d1894c82f6c73340d084c1392722430a91e4a 100644 --- a/api/v/bittitan.json +++ b/api/v/bittitan.json @@ -3,7 +3,7 @@ "slug": "bittitan", "platform": "statuspage", "status_url": "https://status.bittitan.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "MigrationWiz Document Migration Errors\n\nFollowing a system upgrade on August 19, 2026 that improved overall document migration speed and throughput, we have identified an issue affecting a small subset of customers. Some users may encounter one of the following errors during document migrations:\n\n\"Collection was modified; enumeration operation may not execute.\"\n\"Offset and length were out of bounds\"\n\"Did not read all bytes from file.\"\n\nThese errors are not indicative of data loss. They are the result of a DLL upgrade included in the August 19 release, which causes logs generated prior to the upgrade to be unreadable by the updated code. We are aware of the issue and actively working on a broader resolution.\n \nRecommended Steps\nIf you are experiencing one of the errors above, please perform a Reset Items and resubmit the migration pass. This resolves the issue in most cases. \n\nFor instructions, see How to Reset Items in MigrationWiz. \nhttps://help.bittitan.com/hc/en-us/articles/360042167494-MigrationWiz-Statistics-Statistics-Lookup#01H8HEMGW00PCG8XHWPM7QHWJD\n\nIf the error persists after performing a Reset Items, please open a Support Case so our team can assist you directly while we work on a broader fix.\n \nWe will provide updates here as our investigation continues.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "started_at": "2026-09-03T06:58:32.359-07:00", "state": "investigating", "title": "MigrationWiz Document Migration Errors", @@ -23,7 +23,7 @@ "body": "We have resolved the issue affecting OneDrive to OneDrive migrations using Delegate Application authentication. Customers who previously encountered the error message \"Your migration failed while checking destination credentials\" should now be able to run migrations successfully.\nIf you continue to experience issues, please resubmit your migration. If problems persist, contact our support team.\nWe apologize for any inconvenience this may have caused.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-08T11:04:11.780-07:00", "resolved_inferred": false, "started_at": "2026-07-08T07:43:58.150-07:00", @@ -36,7 +36,7 @@ "body": "This incident is resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-25T13:31:37.867-08:00", "resolved_inferred": false, "started_at": "2026-02-25T09:10:08.190-08:00", @@ -49,7 +49,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-24T05:40:21.236-08:00", "resolved_inferred": false, "started_at": "2026-02-23T14:11:49.815-08:00", @@ -62,7 +62,7 @@ "body": "This incident is now resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-29T06:27:27.769-07:00", "resolved_inferred": false, "started_at": "2026-02-13T13:09:54.000-08:00", @@ -75,7 +75,7 @@ "body": "With the release of our Microsoft modern identity platform (v2) upgrade, designed to enhance security, reliability, and the overall configuration experience, the majority of the initial issues identified following launch have now been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-13T13:08:32.897-08:00", "resolved_inferred": false, "started_at": "2026-01-08T12:33:18.000-08:00", @@ -88,7 +88,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-09T14:03:44.437-08:00", "resolved_inferred": false, "started_at": "2025-12-08T09:49:54.089-08:00", @@ -101,7 +101,7 @@ "body": "Migration jobs continue to process, but stopping them from the MigrationWiz UI is working inconsistently. Please contact Support if you require any migration lines to be stopped", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-08T09:45:21.000-08:00", "resolved_inferred": false, "started_at": "2025-12-08T09:45:21.000-08:00", @@ -114,7 +114,7 @@ "body": "Migration jobs continue to process, but stopping them from the MigrationWiz UI is working inconsistently. Please contact Support if you require any migration lines to be stopped.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-08T09:41:50.562-08:00", "resolved_inferred": false, "started_at": "2025-12-07T06:34:23.000-08:00", @@ -127,7 +127,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-08T09:42:12.777-08:00", "resolved_inferred": false, "started_at": "2025-12-05T09:53:48.945-08:00", @@ -140,7 +140,7 @@ "body": "All previously identified issues have been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-05T08:33:26.001-08:00", "resolved_inferred": false, "started_at": "2025-12-05T06:26:44.000-08:00", diff --git a/api/v/bizzabo.json b/api/v/bizzabo.json index 9af276f2996e586b6d344d0c8a979b270af6eb10..d626ab30bc870ab6cbf289260073e2994e6a85ea 100644 --- a/api/v/bizzabo.json +++ b/api/v/bizzabo.json @@ -3,7 +3,7 @@ "slug": "bizzabo", "platform": "statuspage", "status_url": "https://status.bizzabo.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "We're happy to report that the issue has been resolved, and everything is back to normal. We apologize for any inconvenience this may have caused and appreciate your patience while we worked to resolve the issue. Please let us know if you have any further questions or concerns.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-09-01T14:05:22.206-04:00", "resolved_inferred": false, "started_at": "2026-09-01T11:56:50.980-04:00", @@ -25,7 +25,7 @@ "body": "We're happy to report that the Cloudflare incident has been resolved, and everything is back to normal. We apologize for any inconvenience this may have caused and appreciate your patience. Please let us know if you have any further questions or concerns.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-18T12:46:05.271-05:00", "resolved_inferred": false, "started_at": "2025-11-18T07:02:55.300-05:00", @@ -38,7 +38,7 @@ "body": "We're happy to report that the issue has been resolved, and everything is back to normal. We apologize for any inconvenience this may have caused and appreciate your patience while we worked to resolve the issue. Please let us know if you have any further questions or concerns.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-11T09:01:30.370-05:00", "resolved_inferred": false, "started_at": "2025-11-11T04:02:37.330-05:00", @@ -51,7 +51,7 @@ "body": "Service has returned to normal and all components are operational. The AWS disruption has been resolved. Thank you for your patience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-21T04:19:06.815-04:00", "resolved_inferred": false, "started_at": "2025-10-20T03:39:29.545-04:00", @@ -64,7 +64,7 @@ "body": "We're happy to report that the issue has been resolved, and everything is back to normal. We apologize for any inconvenience this may have caused and appreciate your patience while we worked to resolve the issue. Please let us know if you have any further questions or concerns.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-17T04:06:20.654-04:00", "resolved_inferred": false, "started_at": "2025-10-16T10:03:22.373-04:00", @@ -77,7 +77,7 @@ "body": "We're happy to report that the issue has been resolved, and everything is back to normal. We apologize for any inconvenience this may have caused and appreciate your patience while we worked to resolve the issue. Please let us know if you have any further questions or concerns.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-21T16:41:33.848-04:00", "resolved_inferred": false, "started_at": "2025-08-21T13:39:56.320-04:00", @@ -90,7 +90,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-19T10:31:05.397-04:00", "resolved_inferred": false, "started_at": "2025-08-19T09:15:11.249-04:00", diff --git a/api/v/blazemeter.json b/api/v/blazemeter.json index 34915e13956b284772848fa967a30b842f8a2400..9932ce0c4dd8b480402ab3c0886ec03c27b406cb 100644 --- a/api/v/blazemeter.json +++ b/api/v/blazemeter.json @@ -3,7 +3,7 @@ "slug": "blazemeter", "platform": "statuspage", "status_url": "https://status.blazemeter.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-01T09:27:49.777-07:00", "resolved_inferred": false, "started_at": "2026-05-26T08:52:58.401-07:00", @@ -25,7 +25,7 @@ "body": "The incident with new user registration has been resolved", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-08T03:42:55.436-07:00", "resolved_inferred": false, "started_at": "2026-05-07T14:05:00.659-07:00", @@ -38,7 +38,7 @@ "body": "Our tests are continuing to run as expected and we have received confirmation from other sources as well. At this time, we are resolving the incident.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-30T11:29:40.245-07:00", "resolved_inferred": false, "started_at": "2026-03-30T07:51:30.356-07:00", @@ -51,7 +51,7 @@ "body": "The fixes that have been applied are working as expected and teams should be able to use their Dedicated IPs again without issue. We are resolving the incident at this time", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-21T07:50:41.341-08:00", "resolved_inferred": false, "started_at": "2026-01-21T06:36:17.106-08:00", @@ -64,7 +64,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "maintenance", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-15T01:53:42.786-07:00", "resolved_inferred": false, "started_at": "2025-10-15T00:22:54.505-07:00", @@ -77,7 +77,7 @@ "body": "We are resolving the incident now as the issue has been fixed for some time and we have given time for users to see the message. As a reminder, if you Services are in Failed state then you just need to restart them and they should again be functioning as expected.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-07T09:33:15.971-07:00", "resolved_inferred": false, "started_at": "2025-10-07T08:17:02.115-07:00", @@ -90,7 +90,7 @@ "body": "Our tests have continued to run successfully from the US Illinois location. At this time you may resume utilizing the US Illinois location in your tests if you would like. We are closing the incident now.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-03T15:52:07.225-07:00", "resolved_inferred": false, "started_at": "2025-10-03T14:17:01.544-07:00", @@ -103,7 +103,7 @@ "body": "We are no longer seeing the data processing delays with our tests at this time. We are resolving the incident now, but will continue to monitor for any potentially lingering issues.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-24T09:27:54.647-07:00", "resolved_inferred": false, "started_at": "2025-09-24T04:29:30.532-07:00", @@ -116,7 +116,7 @@ "body": "The fix for the data processing issue has been deployed now and we are seeing improvement in our tests as well. At this time we are resolving the incident.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-11T16:56:16.412-07:00", "resolved_inferred": false, "started_at": "2025-09-11T15:10:10.222-07:00", diff --git a/api/v/blend.json b/api/v/blend.json index 134467de57cc267e547a8ff2bb73b2de302d16a9..f6d75ce72c33f009aed91dd6dc19e29732c63ad1 100644 --- a/api/v/blend.json +++ b/api/v/blend.json @@ -3,7 +3,7 @@ "slug": "blend", "platform": "statuspage", "status_url": "https://status.blend.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-13T12:55:36.529-07:00", "resolved_inferred": false, "started_at": "2026-08-13T07:05:52.764-07:00", @@ -25,7 +25,7 @@ "body": "Per ICE Mortgage Technology's status page, a client-side fix for the Send Disclosures error has been released via critical patch 26.2.0.4, and has been deployed to both UAT and Production Encompass environments.\n\nAction required: To receive the patch, users will need to log out of the Encompass Smart Client and log back in.\n\nSeveral clients have confirmed service is restored after applying the patch. If you continue to experience issues sending Disclosures after logging back in, please reach out to the ICE/Encompass Support Team.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-11T07:50:37.742-07:00", "resolved_inferred": false, "started_at": "2026-08-10T13:28:42.899-07:00", @@ -38,7 +38,7 @@ "body": "We scaled up processing capacity on our end to work through the backlog of signature and package completion events between DocuSign and Blend. This backlog has now fully processed, and document e-sign tasks are reflecting completion status successfully. RON, Hybrid Closings, Disclosures, and Follow Up flows using eSign functionality are operating normally.\n\nThank you for your patience while we worked through this issue.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-31T12:45:46.027-07:00", "resolved_inferred": false, "started_at": "2026-07-31T07:19:36.899-07:00", @@ -51,7 +51,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-29T12:00:59.808-07:00", "resolved_inferred": false, "started_at": "2026-07-28T20:09:15.506-07:00", @@ -64,7 +64,7 @@ "body": "The Blend Engineering Team has\u00a0identified the cause of the intermittent delays affecting our Encompass Partner Document Delivery (PDD) integration, and service has returned to normal.\n\nOur Engineering team has implemented mitigations to restore stability and will continue to monitor the environment closely to ensure the issue does not recur.\n\nWe are also continuing work on additional improvements to further strengthen the resiliency of the integration.\n\nThank you for your patience while we worked to resolve this issue.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-23T15:02:22.700-07:00", "resolved_inferred": false, "started_at": "2026-07-23T09:47:12.381-07:00", @@ -77,7 +77,7 @@ "body": "The fix for this issue has now been deployed, and we believe the matter is fully resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-22T14:09:03.789-07:00", "resolved_inferred": false, "started_at": "2026-07-22T09:38:45.645-07:00", @@ -90,7 +90,7 @@ "body": "The issue affecting delivery of multi-factor authentication codes sent via SMS short code appears to be resolved. Service has recovered, and users should now be able to receive MFA codes as expected.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-22T12:57:11.065-07:00", "resolved_inferred": false, "started_at": "2026-06-22T09:37:15.142-07:00", @@ -103,7 +103,7 @@ "body": "Cloudflare has reported that traffic engineering efforts have successfully mitigated the majority of congestion and packet drops. Please refer to the linked Cloudflare status page for the latest provider updates.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-22T11:52:04.823-07:00", "resolved_inferred": false, "started_at": "2026-06-22T08:00:17.381-07:00", @@ -116,7 +116,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-10T15:02:04.138-07:00", "resolved_inferred": false, "started_at": "2026-06-10T10:06:03.956-07:00", @@ -129,7 +129,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-08T07:04:18.528-07:00", "resolved_inferred": false, "started_at": "2026-06-05T12:11:51.250-07:00", @@ -142,7 +142,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-13T08:55:18.116-07:00", "resolved_inferred": false, "started_at": "2026-05-13T08:21:09.336-07:00", @@ -155,7 +155,7 @@ "body": "Encompass confirmed the issue on their end has been resolved and all services remain in a stable state.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-25T06:49:11.945-07:00", "resolved_inferred": false, "started_at": "2026-04-24T09:21:26.207-07:00", @@ -168,7 +168,7 @@ "body": "The issue impacting Blend Beta environments has been resolved, and the beta environments are now functioning normally.\n\nWe will continue to monitor closely to ensure ongoing stability. Please feel free to reach out to us if you encounter any issues.\n\nThank you for your patience while we worked through this issue.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-09T13:07:00.333-07:00", "resolved_inferred": false, "started_at": "2026-04-09T09:26:22.693-07:00", @@ -181,7 +181,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-09T07:11:01.557-07:00", "resolved_inferred": false, "started_at": "2026-04-08T09:54:41.000-07:00", @@ -194,7 +194,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-05T20:22:04.011-08:00", "resolved_inferred": false, "started_at": "2026-03-05T14:00:06.308-08:00", @@ -207,7 +207,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-02T14:55:57.801-08:00", "resolved_inferred": false, "started_at": "2026-03-02T11:48:35.415-08:00", @@ -220,7 +220,7 @@ "body": "Resolved but still monitoring. Continue to send Hybrid Closing packages.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-11T09:05:25.781-08:00", "resolved_inferred": false, "started_at": "2026-02-11T07:50:41.763-08:00", @@ -233,7 +233,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-20T16:59:07.226-08:00", "resolved_inferred": false, "started_at": "2026-01-20T10:35:53.826-08:00", @@ -246,7 +246,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-20T16:59:35.138-08:00", "resolved_inferred": false, "started_at": "2026-01-20T07:13:01.208-08:00", @@ -259,7 +259,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-16T16:17:03.548-08:00", "resolved_inferred": false, "started_at": "2026-01-14T05:38:34.878-08:00", @@ -272,7 +272,7 @@ "body": "All affected services including Blend Signing Room (RONs) and Public API have been recovered.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-13T13:52:30.132-08:00", "resolved_inferred": false, "started_at": "2026-01-13T12:23:48.000-08:00", @@ -285,7 +285,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-01T08:30:08.085-08:00", "resolved_inferred": false, "started_at": "2025-11-25T20:14:56.634-08:00", @@ -298,7 +298,7 @@ "body": "We have identified the impacted applications and re-exported applications stuck \"in progress.\" We have started sending out impact lists individually to any impacted clients.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-25T13:02:16.015-08:00", "resolved_inferred": false, "started_at": "2025-11-25T08:40:34.805-08:00", @@ -311,7 +311,7 @@ "body": "AUS Functionality Fully Restored\n\nWe have successfully resolved and confirmed the full restoration of AUS functionality. You can now run AUS as expected.\nPlease note that this incident was strictly confined to AUS; there were no other known or expected impacts to any other Blend features or user data.\n\nThank you for your patience as our team worked to deploy this fix quickly. We appreciate your partnership.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-19T08:59:53.450-08:00", "resolved_inferred": false, "started_at": "2025-11-19T07:44:45.000-08:00", @@ -324,7 +324,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-03T09:54:57.563-08:00", "resolved_inferred": false, "started_at": "2025-11-03T08:37:28.254-08:00", @@ -337,7 +337,7 @@ "body": "Our application export queues have returned to normal levels. At this time, we believe that this incident is resolved, although some of Blend's integration partners may continue to experience issues as they recover.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-20T14:37:24.878-07:00", "resolved_inferred": false, "started_at": "2025-10-20T02:27:13.212-07:00", @@ -350,7 +350,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-22T07:28:21.240-07:00", "resolved_inferred": false, "started_at": "2025-08-21T11:35:33.000-07:00", diff --git a/api/v/blip.json b/api/v/blip.json index 0014f90a1146bed48cadfb892269fb0b8bb30acc..623c9427781a34d746da78b415c0cc6758ee0d83 100644 --- a/api/v/blip.json +++ b/api/v/blip.json @@ -3,7 +3,7 @@ "slug": "blip", "platform": "statuspage", "status_url": "https://status.blip.ai", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "This incident has been resolved. The underlying configuration mapping errors, connection saturation, and TLS handshake failures have been fully addressed. All system services, messaging traffic, and affected clusters have been restored to full operation. Continuous monitoring remains active to ensure system stability.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-24T10:34:54.225-03:00", "resolved_inferred": false, "started_at": "2026-08-24T08:50:11.624-03:00", @@ -25,7 +25,7 @@ "body": "The email provider's corporate account experienced a temporary access block, affecting the delivery of login emails, reports, and system notifications. We have implemented the changes requested by the provider and are configuring additional safeguards for other platform features, as well as setting up preventive alerts to ensure a rapid response should the issue recur. We are implementing a new configuration to restructure workflows, ensuring that any email delivery inconsistencies do not impact or compromise other system functions. Preventive alert rules have been established to immediately notify the technical team if this behavior recurs with the provider. Communication channels and technical investigations involving both the provider and internal teams remain active to ensure the situation is fully and permanently stabilized. To resolve the incident, we carried out the adjustments and configurations required to unblock and restore the corporate account. This included unblocking and validating essential system emails, reports, and portal emails, as well as reconfiguring email integration routes passing through the gateway to ensure smooth traffic flow without affecting other platform features. We also monitored environment testing and confirmed that email receipt had returned to normal for affected customers. Next steps: An internal meeting will be held tomorrow among the responsible teams to evaluate and define the next steps for resuming email services, ensuring a safe and controlled reactivation.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-20T19:38:04.244-03:00", "resolved_inferred": false, "started_at": "2026-08-20T09:50:40.000-03:00", @@ -38,7 +38,7 @@ "body": "We identified that customers were experiencing slow bot response times, with delays ranging from 10 seconds to a full minute. The technical team mobilized to validate the issue and investigate the environment's logs. We performed a rollback of the application update that had been intended to improve the platform. We appreciate everyone's patience and cooperation while we addressed this situation.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-06T18:01:28.023-03:00", "resolved_inferred": false, "started_at": "2026-08-06T17:47:35.614-03:00", @@ -51,7 +51,7 @@ "body": "The environment has been fully restored to normal and is stable, with message flow and history back to normal. Our technical teams increased the processing capacity of the messaging queues to eliminate bottlenecks and resolved discrepancies regarding message history persistence. Normal operations were restored at 9:50 PM yesterday, and the system remained under continuous monitoring until 9:30 AM today to fully validate performance. The emergency response has concluded, and the platform remains under standard preventive monitoring.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-06T13:48:35.717-03:00", "resolved_inferred": false, "started_at": "2026-08-05T12:58:45.000-03:00", @@ -64,7 +64,7 @@ "body": "Informamos que o incidente foi conclu\u00eddo. O envio de mensagens via BSUID atrav\u00e9s da API foi totalmente restabelecido", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-12T16:40:10.332-03:00", "resolved_inferred": false, "started_at": "2026-07-24T18:00:27.000-03:00", @@ -77,7 +77,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-23T21:40:16.416-03:00", "resolved_inferred": false, "started_at": "2026-06-23T20:09:56.293-03:00", @@ -90,7 +90,7 @@ "body": "The incident affecting media message delivery through the WhatsApp channel has been resolved.\nWe observed a significant reduction in errors starting at approximately 13:50 (GMT-3), and subsequent validation tests were completed successfully without further issues.\nAfter further investigation, Meta informed us that an internal issue related to its Forward Proxy service had been identified and resolved.\nThe service has remained stable since then, and no new impacts have been observed. This incident is now considered resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-16T16:03:12.827-03:00", "resolved_inferred": false, "started_at": "2026-06-16T11:40:11.000-03:00", @@ -103,7 +103,7 @@ "body": "The Meta API has been restored: https://metastatus.com/whatsapp-business-api", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-12T15:15:31.000-03:00", "resolved_inferred": false, "started_at": "2026-06-12T10:30:04.000-03:00", @@ -116,7 +116,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-01T23:10:14.779-03:00", "resolved_inferred": false, "started_at": "2026-06-01T22:50:12.223-03:00", @@ -129,7 +129,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-05T16:05:34.000-03:00", "resolved_inferred": false, "started_at": "2026-05-05T15:51:44.031-03:00", @@ -142,7 +142,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-05T14:10:12.452-03:00", "resolved_inferred": false, "started_at": "2026-05-05T13:54:44.037-03:00", @@ -155,7 +155,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-05T11:56:16.000-03:00", "resolved_inferred": false, "started_at": "2026-05-05T11:52:43.995-03:00", @@ -168,7 +168,7 @@ "body": "The issue affecting AI agents has been resolved after reverting recent changes, restoring normal functionality.\nThe root cause is still under investigation, and we are continuing internal analysis to fully understand the scenario.\nNo further impact is expected.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-23T08:24:19.000-03:00", "resolved_inferred": false, "started_at": "2026-04-22T10:37:00.000-03:00", @@ -181,7 +181,7 @@ "body": "The issue affecting ticket distribution and performance on Blip Desk has been resolved. Customers experienced difficulties handling tickets and slowness when accessing the platform. The root cause was identified and corrected, and the service is now fully operational.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-08T11:06:46.501-03:00", "resolved_inferred": false, "started_at": "2026-04-08T09:26:46.833-03:00", @@ -194,7 +194,7 @@ "body": "The issue affecting AI-powered bots has been resolved. During the incident, users may have experienced missing responses from bots. The service is now fully restored and operating normally.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-02T10:40:32.745-03:00", "resolved_inferred": false, "started_at": "2026-04-02T08:19:58.383-03:00", @@ -207,7 +207,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-01T22:19:14.604-03:00", "resolved_inferred": false, "started_at": "2026-03-01T21:56:14.445-03:00", @@ -220,7 +220,7 @@ "body": "The incident affecting contact search functionality in bots has been resolved.\nThe root cause was identified as high resource consumption in the search component.\n\nAfter technical adjustments, performance indicators have remained within expected levels.\n\nWe will continue monitoring the platform to ensure ongoing stability.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-23T17:01:32.885-03:00", "resolved_inferred": false, "started_at": "2026-02-23T10:19:06.000-03:00", @@ -233,7 +233,7 @@ "body": "The incident has been resolved. We observed that the environment remained stable and we did not find any other errors.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-03T16:59:51.702-03:00", "resolved_inferred": false, "started_at": "2026-02-03T16:21:00.000-03:00", @@ -246,7 +246,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-22T14:16:57.000-03:00", "resolved_inferred": false, "started_at": "2026-01-20T10:31:06.997-03:00", @@ -259,7 +259,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-19T22:00:19.000-03:00", "resolved_inferred": false, "started_at": "2026-01-19T08:40:20.000-03:00", @@ -272,7 +272,7 @@ "body": "The incident has been removed from the vendor's Status Page. The environment remains stable.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-19T11:14:25.673-03:00", "resolved_inferred": false, "started_at": "2025-12-19T09:33:24.640-03:00", @@ -285,7 +285,7 @@ "body": "What happened and what was the impact on customers:\nWe identified a failure in the AI application. As a result, customers experienced a failure in the messages from the AI-powered bots.\n\nActions taken:\nUpdate of the expired token\nRestart Rollout in all pods\nMonitoring of metrics after restarts\n\nFailure occurrences:\nStart of failure: 11/12/2025 8:10 AM (GMT-3)\nFault resolution: 11/12/2025 10:10 AM (GMT-3)\n\nRoot cause\nThe failure was caused by instabilities resulting from expired credentials on an external service, which temporarily impacted the bot's operation.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-11T11:26:13.000-03:00", "resolved_inferred": false, "started_at": "2025-12-11T11:26:13.000-03:00", @@ -298,7 +298,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-10T13:00:24.000-03:00", "resolved_inferred": false, "started_at": "2025-12-10T10:46:13.000-03:00", @@ -311,7 +311,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-10T10:05:19.000-03:00", "resolved_inferred": false, "started_at": "2025-12-10T09:15:51.000-03:00", @@ -324,7 +324,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-05T08:01:35.414-03:00", "resolved_inferred": false, "started_at": "2025-12-05T06:24:54.571-03:00", @@ -337,7 +337,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-04T11:10:54.000-03:00", "resolved_inferred": false, "started_at": "2025-12-04T08:30:00.000-03:00", @@ -350,7 +350,7 @@ "body": "O cen\u00e1rio foi normalizado e uma solu\u00e7\u00e3o para mitigar problemas futuros est\u00e1 sendo desenvolvida.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-24T16:27:46.661-03:00", "resolved_inferred": false, "started_at": "2025-11-24T10:12:00.000-03:00", @@ -363,7 +363,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-06T12:27:47.130-03:00", "resolved_inferred": false, "started_at": "2025-11-06T08:00:10.000-03:00", @@ -376,7 +376,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-29T21:05:33.000-03:00", "resolved_inferred": false, "started_at": "2025-10-29T13:18:54.341-03:00", @@ -389,7 +389,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-30T20:26:48.842-03:00", "resolved_inferred": false, "started_at": "2025-08-30T18:30:05.000-03:00", @@ -402,7 +402,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-22T12:55:36.131-03:00", "resolved_inferred": false, "started_at": "2025-08-22T08:30:19.000-03:00", @@ -415,7 +415,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-11T15:27:34.885-03:00", "resolved_inferred": false, "started_at": "2025-08-11T09:05:50.000-03:00", diff --git a/api/v/blockchain.json b/api/v/blockchain.json index d715e0ee657cac5605f707e4ae57d592c0c84d8c..babfd7c2e966fb510f3bd7384bc4ad7bf40545e6 100644 --- a/api/v/blockchain.json +++ b/api/v/blockchain.json @@ -3,7 +3,7 @@ "slug": "blockchain", "platform": "statuspage", "status_url": "https://www.blockchain-status.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "All systems are working. We are actively monitoring the current status.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-09T09:43:24Z", "resolved_inferred": false, "started_at": "2026-08-08T09:06:23Z", @@ -24,7 +24,7 @@ "body": "All systems are working. We are actively monitoring the current status.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-20T16:58:02Z", "resolved_inferred": false, "started_at": "2026-05-20T02:54:20Z", @@ -36,7 +36,7 @@ "body": "All systems are working. We are actively monitoring the current status.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-15T12:15:36Z", "resolved_inferred": false, "started_at": "2026-01-14T15:41:07Z", @@ -48,7 +48,7 @@ "body": "All systems are working. We are actively monitoring the current status.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-26T14:28:42Z", "resolved_inferred": false, "started_at": "2026-01-12T14:31:36Z", @@ -60,7 +60,7 @@ "body": "All systems are working. We are actively monitoring the current status.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-23T15:28:35Z", "resolved_inferred": false, "started_at": "2025-11-21T10:59:24Z", @@ -72,7 +72,7 @@ "body": "All systems are working. We are actively monitoring the current status.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-11T18:31:48Z", "resolved_inferred": false, "started_at": "2025-11-10T15:25:31Z", diff --git a/api/v/bluefin.json b/api/v/bluefin.json index 9c8136bce12fd825c22156955215b23abef65933..c7684c8e6421c3ba362ec71f9eadc978f39b11d2 100644 --- a/api/v/bluefin.json +++ b/api/v/bluefin.json @@ -3,7 +3,7 @@ "slug": "bluefin", "platform": "statuspage", "status_url": "https://status.bluefin.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-09-02T15:07:39.140-04:00", "resolved_inferred": false, "started_at": "2026-09-02T11:49:46.612-04:00", @@ -25,7 +25,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-25T12:00:10.728-04:00", "resolved_inferred": false, "started_at": "2026-08-25T10:51:26.846-04:00", @@ -38,7 +38,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-25T10:35:23.006-04:00", "resolved_inferred": false, "started_at": "2026-08-25T10:06:37.000-04:00", @@ -51,7 +51,7 @@ "body": "The issue affecting SaaSConex has been resolved, and normal service has been restored.\n\nOur team has verified that the fix has been successfully implemented and that systems are operating as expected. We will continue to monitor the service to ensure ongoing stability.\n\nWe apologize for any inconvenience caused and thank you for your patience and understanding throughout this incident.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-07T13:55:47.000-04:00", "resolved_inferred": false, "started_at": "2026-08-07T13:00:00.752-04:00", @@ -64,7 +64,7 @@ "body": "This incident has been resolved. We thank you for your patience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-28T10:15:07.734-04:00", "resolved_inferred": false, "started_at": "2026-07-28T09:31:47.180-04:00", @@ -77,7 +77,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-09T10:55:21.890-04:00", "resolved_inferred": false, "started_at": "2026-07-09T10:24:13.704-04:00", @@ -90,7 +90,7 @@ "body": "The issue affecting intermittent processing has been resolved. Our third-party service provider has confirmed that services are operating normally, and we have not observed any further impact. We will continue to monitor the environment, but this incident is now considered resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-29T08:16:06.812-04:00", "resolved_inferred": false, "started_at": "2026-05-28T14:23:16.495-04:00", @@ -103,7 +103,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-16T14:23:49.878-04:00", "resolved_inferred": false, "started_at": "2026-03-16T12:38:00.771-04:00", @@ -116,7 +116,7 @@ "body": "We are pleased to inform you that the issues causing delays in ACH settlement activity have been resolved. The Federal Reserve has addressed the problem, and Bluefin\u2019s processing systems continue to operate normally. We appreciate your understanding.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-03T14:58:53.624-05:00", "resolved_inferred": false, "started_at": "2026-03-03T10:28:18.459-05:00", @@ -129,7 +129,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-08T04:38:48.238-05:00", "resolved_inferred": false, "started_at": "2026-02-08T03:18:13.578-05:00", @@ -142,7 +142,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-03T05:17:32.509-05:00", "resolved_inferred": false, "started_at": "2026-02-02T17:33:34.146-05:00", @@ -155,7 +155,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-28T07:40:00.245-05:00", "resolved_inferred": false, "started_at": "2026-01-26T12:09:22.691-05:00", @@ -168,7 +168,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-21T14:04:37.535-05:00", "resolved_inferred": false, "started_at": "2026-01-21T12:59:12.262-05:00", @@ -181,7 +181,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-30T00:35:30.544-05:00", "resolved_inferred": false, "started_at": "2025-12-29T12:25:21.091-05:00", @@ -194,7 +194,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-12T18:35:58.967-05:00", "resolved_inferred": false, "started_at": "2025-12-12T13:17:41.178-05:00", @@ -207,7 +207,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-01T07:07:02.512-04:00", "resolved_inferred": false, "started_at": "2025-10-31T23:23:39.668-04:00", @@ -220,7 +220,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-20T18:29:53.333-04:00", "resolved_inferred": false, "started_at": "2025-10-20T10:14:08.935-04:00", @@ -233,7 +233,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-19T07:34:01.363-04:00", "resolved_inferred": false, "started_at": "2025-10-19T07:33:38.049-04:00", @@ -246,7 +246,7 @@ "body": "Update - All Systems Operational", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-15T18:58:27.775-04:00", "resolved_inferred": false, "started_at": "2025-10-15T13:10:43.235-04:00", @@ -259,7 +259,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-12T16:38:00.285-04:00", "resolved_inferred": false, "started_at": "2025-09-12T10:16:37.084-04:00", @@ -272,7 +272,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-05T15:21:03.354-04:00", "resolved_inferred": false, "started_at": "2025-09-05T11:45:15.726-04:00", @@ -285,7 +285,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-25T09:01:16.853-04:00", "resolved_inferred": false, "started_at": "2025-08-25T08:48:08.863-04:00", @@ -298,7 +298,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-21T07:39:50.720-04:00", "resolved_inferred": false, "started_at": "2025-08-21T07:07:16.954-04:00", @@ -311,7 +311,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-07T03:40:45.952-04:00", "resolved_inferred": false, "started_at": "2025-08-07T01:18:00.883-04:00", @@ -324,7 +324,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-05T21:15:40.095-04:00", "resolved_inferred": false, "started_at": "2025-08-05T17:32:13.490-04:00", diff --git a/api/v/bolt.json b/api/v/bolt.json index deacb22040d9adfbd8ba584a437c5fc9fedf362d..f7e8c21bab1327d255c36a28b7feecc6cbe504b0 100644 --- a/api/v/bolt.json +++ b/api/v/bolt.json @@ -3,7 +3,7 @@ "slug": "bolt", "platform": "statuspage", "status_url": "https://status.bolt.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", diff --git a/api/v/booksy.json b/api/v/booksy.json index fc450e74a21c9ff5fa3085c0c760909995ac6dd1..b73e16a29ec2971d9a3a67136bccde7e8a80e007 100644 --- a/api/v/booksy.json +++ b/api/v/booksy.json @@ -3,7 +3,7 @@ "slug": "booksy", "platform": "statuspage", "status_url": "https://status.booksy.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", diff --git a/api/v/box.json b/api/v/box.json index 0f4a5989ea43cd78584665b5560fb3b8e2982324..50109c0b341a84adb8444fe47a6463ff6e73021b 100644 --- a/api/v/box.json +++ b/api/v/box.json @@ -3,7 +3,7 @@ "slug": "box", "platform": "statuspage", "status_url": "https://status.box.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "This incident is now resolved and Box services have been restored to full functionality. If you generated reports during the impacted period, please re-run those reports. Please contact Box Support at https://support.box.com/ if you continue to experience any issues.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-09-03T20:03:26.934-07:00", "resolved_inferred": false, "started_at": "2026-09-03T19:10:06.402-07:00", @@ -25,7 +25,7 @@ "body": "After further monitoring, this incident is now considered resolved. Box services have been restored to full functionality. Please contact Box Support at https://support.box.com/ if you continue to experience any issues.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-28T03:00:41.109-07:00", "resolved_inferred": false, "started_at": "2026-08-28T01:20:35.272-07:00", @@ -38,7 +38,7 @@ "body": "After further monitoring, this incident is now considered resolved. If you continue to experience any issues, please contact Box Support at https://support.box.com.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-25T00:37:39.283-07:00", "resolved_inferred": false, "started_at": "2026-08-24T23:53:37.438-07:00", @@ -51,7 +51,7 @@ "body": "_Notice and disclaimer: Box is providing this preliminary information subject to further review and analysis. To the best of our knowledge, this is the current state and we may update as more information is confirmed._\n\nOn August 24, 2026 between 2:03 PM PDT and 2:24 PM PDT, some customers experienced degraded upload performance, elevated errors, and reduced availability for certain user operations.\n\nThe issue was caused by an internal background clean-up process that generated an unexpectedly high volume of requests and overloaded part of our back-end system. We applied an immediate mitigation to stop the offending traffic, and service levels returned to normal within minutes. We are reviewing the recent changes and retry behavior that contributed to this event and are working to prevent recurrence.\n\nWe are conducting a full engineering postmortem and our overview is subject to change with further analysis and findings. In the event our continuing investigation yields further substantive findings, we may publish additional analysis after the conclusion of the full engineering postmortem.\n\nWe are continuously working to improve Box and want to make sure we are delivering the best product and user experience we can. We hope we have provided some clarity here and we would be happy to answer any questions you may still have regarding this matter.\n\nSincerely,\n\nThe Box Team", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-24T15:03:07.119-07:00", "resolved_inferred": false, "started_at": "2026-08-24T14:21:52.400-07:00", @@ -64,7 +64,7 @@ "body": "_Notice and disclaimer: Box is providing this preliminary information subject to further review and analysis. To the best of our knowledge, this is the current state and we may update as more information is confirmed._\n\nOn August 24, 2026 between 10:28 AM PDT and 10:35 AM PDT, some customers may have experienced failures signing in and intermittent inability to access files and other core Box features.\n\nThe disruption was caused by a traffic increase at our edge load-balancers that delayed requests to back-end services. Error rates returned to normal after the traffic spike subsided and services recovered. We are reviewing our load-balancing and client-connection practices and working with our cloud provider to reduce the likelihood of recurrence.\n\nWe are conducting a full engineering postmortem and our overview is subject to change with further analysis and findings. In the event our continuing investigation yields further substantive findings, we may publish additional analysis after the conclusion of the full engineering postmortem.\n\nWe are continuously working to improve Box and want to make sure we are delivering the best product and user experience we can. We hope we have provided some clarity here and we would be happy to answer any questions you may still have regarding this matter.\n\nSincerely,\n\nThe Box Team", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-24T10:30:00.000-07:00", "resolved_inferred": false, "started_at": "2026-08-24T08:30:00.000-07:00", @@ -77,7 +77,7 @@ "body": "From approximately 2:42 AM to 2:45 AM PDT (US Pacific Time), we observed an issue impacting Box Notes. Our systems automatically detected and corrected the underlying issue. There is no current impact and no further updates will be provided here. If you continue to experience any issues, please contact Box Support at https://support.box.com.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-21T02:45:00.000-07:00", "resolved_inferred": false, "started_at": "2026-08-20T15:00:00.000-07:00", @@ -90,7 +90,7 @@ "body": "_Notice and disclaimer: Box is providing this preliminary information subject to further review and analysis. To the best of our knowledge, this is the current state and we may update as more information is confirmed._\n\nOn August 19, 2026 between 4:17 PM and 6:19 PM PT, some customers experienced errors or delays when opening files using Microsoft Office Online and when using related integrations such as Open With, Box Edit, and iWork. A limited subset of folder views in All Files that rely on those integrations may also have been affected.\n\nThe issue occurred because of a recent release that led to elevated errors and latency for some users. When we reverted the change, service metrics returned to normal. Customer testing showed restoration by 6:19 PM PT.\n\nWe are reviewing our deployment and release processes to help prevent recurrence.\n\nAdditionally, we are conducting a full engineering postmortem and our overview is subject to change with further analysis and findings. In the event our continuing investigation yields further substantive findings, we may publish additional analysis after the conclusion of the full engineering postmortem.\n\nWe are continuously working to improve Box and want to make sure we are delivering the best product and user experience we can. We hope we have provided some clarity here and we would be happy to answer any questions you may still have regarding this matter.\n\nSincerely,\n\nThe Box Team", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-19T18:44:28.049-07:00", "resolved_inferred": false, "started_at": "2026-08-19T17:31:23.000-07:00", @@ -103,7 +103,7 @@ "body": "_Notice and disclaimer: Box is providing this preliminary information subject to further review and analysis. To the best of our knowledge, this is the current state and we may update as more information is confirmed._\n\nOn August 19, 2026 between 3:44pm PDT to 3:49pm PDT, some users may have experienced difficulties while working in Box. When attempting to access Box during this time, some users may have seen an error message. Preview, and Box Notes functionalities were impacted. This occurred because of an issue affecting Box\u2019s critical third party cloud ingress services.\n\nWe are conducting a full engineering postmortem in conjunction with our cloud provider, and our overview is subject to change with further analysis and findings. In the event our continuing investigation yields further substantive findings, we may publish additional analysis after the conclusion of the full engineering postmortem.\n\nWe are continuously working to improve Box and want to make sure we are delivering the best product and user experience we can. We hope we have provided some clarity here and we would be happy to answer any questions you may still have regarding this matter.\n\nSincerely, \nThe Box Team", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-19T15:00:00.000-07:00", "resolved_inferred": false, "started_at": "2026-08-19T15:00:00.000-07:00", @@ -116,7 +116,7 @@ "body": "After further monitoring, this incident is now considered resolved. All Files Page Service has been restored to full functionality. If you continue to experience any issues, please contact Box Support at https://support.box.com.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-19T05:03:02.576-07:00", "resolved_inferred": false, "started_at": "2026-08-19T04:38:19.903-07:00", @@ -129,7 +129,7 @@ "body": "_Notice and disclaimer: Box is providing this preliminary information subject to further review and analysis. To the best of our knowledge, this is the current state and we may update as more information is confirmed._\n\nOn Aug 6, 2026 between 6:42 PM PDT and 6:48 PM PDT and again between 7:27 PM to 7:33 PM PDT, some customers may have experienced intermittent failures affecting login, uploads/downloads, Notes, Box AI, and API access in Box. The disruptions were caused by a temporary resource exhaustion on our front\u2011end infrastructure. \n\nWe are conducting a full engineering postmortem and our overview is subject to change with further analysis and findings. In the event our continuing investigation yields further substantive findings, we may publish additional analysis after the conclusion of the full engineering postmortem.\n\nWe are continuously working to improve Box and want to make sure we are delivering the best product and user experience we can. We hope we have provided some clarity here and we would be happy to answer any questions you may still have regarding this matter.\n\nSincerely,\n\nThe Box Team", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-06T22:16:57.766-07:00", "resolved_inferred": false, "started_at": "2026-08-06T19:37:34.595-07:00", @@ -142,7 +142,7 @@ "body": "On August 4, 2026 between 12:10 PM PDT and 1:20 PM PDT, some customers experienced failures and delays when uploading files to Box. The problem was caused by a routing issue on our frontend load balancers. We restored service by rerouting upload traffic and provisioning additional capacity.\n\n# Analysis\n\nA temporary network connectivity disruption impacted a small part of our load balancing fleet, causing a spike of TCP retransmit errors. Our engineering team mitigated the impact by redirecting traffic away from the affected region, which restored normal upload operations and resolved the errors. This incident highlighted opportunities to improve observable signals and alerting for TCP retransmit errors.\n\n# Corrective Actions\n\nBox has initiated the following corrective actions:\n\n* Improve monitoring and alerting for the isolated TCP retransmit issues. \n* Review and update operational runbooks for isolating problematic instances and for capacity management to shorten time to mitigation.\n\n\u200c\n\nWe are continuously working to improve Box and want to make sure we are delivering the best product and user experience we can. We hope we have provided some clarity here and we would be happy to answer any questions you may still have regarding this matter.\n\nSincerely, \nThe Box Team", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-04T13:44:52.273-07:00", "resolved_inferred": false, "started_at": "2026-08-04T13:23:03.393-07:00", @@ -155,7 +155,7 @@ "body": "We recently addressed issues affecting Shuttle standalone jobs. We would like to take the opportunity to further explain these issues and the steps we have taken to keep them from happening in the future.\n\nBetween 3:41 AM and 3:57 AM PDT on July 31, 2026, some customers using Shuttle Standalone could sign in to their Shuttle Standalone accounts and view their dashboards, but could not view job details, change job settings, or create new standalone jobs. The Shuttle native experience was not affected. After we restored service, we confirmed that customers could access existing jobs and create new ones. \n\n# Analysis\n\nA misconfiguration in Shuttle resulted in depleted resources that accessed job history. This caused Shuttle pages that load job history to time out. We restored access by restarting the affected services at 3:57 AM PDT. Job management returned to normal, with no recurrence. This briefly blocked the standalone experience for affected customers, even though sign-in and the Shuttle native experience continued to work.\n\n# Corrective Actions\n\nBox has initiated the following corrective actions:\n\n* Updating the capacity allocation to avoid the recurrence of this issue\n* Adding monitoring to better preempt the issue from occurring \n\nWe are continuously working to improve Box and want to make sure we are delivering the best product and user experience we can. We hope we have provided some clarity here and we would be happy to answer any questions you may still have regarding this matter.\n\nSincerely,\n\nThe Box Team", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-31T04:30:17.820-07:00", "resolved_inferred": false, "started_at": "2026-07-31T04:09:34.000-07:00", @@ -168,7 +168,7 @@ "body": "We recently addressed issues affecting file uploads and edits that create new file versions. We want to explain what happened and what we have done to prevent it from happening again. \n\nBetween Jul 26, 2026 4:38 PM PDT and Jul 28, 2026 10:34 AM PDT, some users may have experienced delays or failures when uploading files or saving edits that create new file versions. The impact was limited to cases with a high number of concurrent uploads or edits on the same file.\n\nDuring this period, concurrent upload and edit traffic contended on shared database locks while creating new file versions. Under load, an overly conservative insert locking strategy acquired locks, creating a bottleneck in the database. The contention was amplified by background processes that post-process the uploaded file and attach additional information to every new version, competing for the same locks.\n\n# Analysis\n\nThis incident highlighted several opportunities for improvement:\n\n* Lock-wait failures do not appear in our usual change-stream / mutation telemetry, which delayed our investigation. \n* Background processes can contend with upload and edit paths that create new versions. Our development environments did not fully test this particular interaction under load.\n\nRemediation combined an immediate reduction in non-essential background scan load with a code change that relaxed the overly conservative locking behavior, while preserving the intended isolation guarantees.\n\n# Corrective Actions\n\nBox has initiated the following corrective actions:\n\n* Deploy and validate the insert-behavior fix across all live clusters \\(completed and confirmed\\).\n* Improve observability for lock-wait and timeout-driven load so contention sources are visible.\n\nWe are continuously working to improve Box and want to make sure we are delivering the best product and user experience we can. We hope we have provided some clarity here and we would be happy to answer any questions you may still have regarding this matter.\n\nSincerely,\n\nThe Box Team", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-27T21:57:55.766-07:00", "resolved_inferred": false, "started_at": "2026-07-27T19:58:26.496-07:00", @@ -181,7 +181,7 @@ "body": "We recently addressed an issue affecting Box Hubs. We\u2019d like to take this opportunity to explain what happened and the steps we\u2019ve taken to prevent it from happening again. \n\nBetween 06:50 AM PDT to 07:26 AM PDT on July 23, 2026, some users may have experienced difficulties while working in Box. During this time, users attempting to access Box Hubs were unable to load the Hubs gallery and instead encountered a \"Not Found\" page. The issue occurred as a result of a recent frontend dependency update, which introduced a package version conflict that prevented the Hubs module from loading correctly. We were able to resolve the issue by rolling back the frontend application to the previous stable version, which fully restored access to Box Hubs. In addition, we are working to improve our automated pre-release testing processes to ensure that dependency updates are validated across all affected modules before reaching production, and we are enhancing our monitoring and alerting capabilities to detect and surface similar issues more quickly, to prevent similar issues from occurring in the future.\n\n# **Analysis** \n\nAt the technical level, a shared package used by the core web application and the Hubs page module fell out of version alignment when the core application upgraded the dependency without a corresponding update in the Hubs module. This caused the Hubs page to crash at load time. The regression was not caught before reaching production because pre-release automated tests were scoped to core application features and did not cover dependent page modules. Once in production, detection was slowed by monitoring gaps, meaning the incident was ultimately surfaced by synthetic monitoring rather than production observability tooling.\n\n# **Corrective Actions**\n\nBox has initiated the following corrective actions:\n\n* Improving frontend error monitoring to clearly attribute client-side errors to specific pages, enabling faster detection of page-level failures in production.\n\n* Enhancing module-level observability and alerting to detect load-time failures for modules. This will ensure we are fully aware of any issues in the integration of sub-modules \\(such as Hubs\\) with the core web app as early as possible.\n* Expanding pre-release automated smoke tests to cover all page modules dependent on the core web application, ensuring that package version conflicts are caught in the release pipeline before reaching production.\n* Improving staging environment alerting to surface potential regressions earlier in the release process, before changes are promoted to production.\n\nWe are continuously working to improve Box and want to make sure we are delivering the best product and user experience we can. We hope we have provided some clarity here and we would be happy to answer any questions you may still have regarding this matter.\u00a0\n\nSincerely,\n\nThe Box Team", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-23T07:30:22.894-07:00", "resolved_inferred": false, "started_at": "2026-07-23T07:14:47.603-07:00", @@ -194,7 +194,7 @@ "body": "We recently addressed an issue affecting metadata updates using File Request in Box. We would like to take the opportunity to further explain the issue and the steps we have taken to keep similar issues from happening in the future.\n\nBetween 09:10 AM PDT on July 22, 2026 and 03:36 PM PDT on July 23, 2026, some users may have experienced delays in metadata updates while uploading files using File Request. The issue occurred when repeated attempts to process a subset of unsuccessful metadata events reduced available processing capacity and delayed other events. We restored the metadata functionality of File Requests by limiting unnecessary retries, reducing processing idle time, and improving the handling of failures that would not succeed when retried. In addition, we are improving retry behavior, monitoring, and response procedures for similar asynchronous processes.\n\n# Analysis\n\nAt the time of the issue, the system automatically retried failed file processing. During an extended period of failures, these retries consumed most of the system's capacity, causing files to pile up in a queue. As processing slowed, more files encountered issues that retries could not resolve, further increasing the delay.\n\nWe restored normal processing by temporarily reducing retry attempts, removing redundant retries, and allowing permanent failures to fail without being repeatedly processed. We continued monitoring the service before confirming that full functionality had been restored.\n\n# Corrective Actions\n\nThe following corrective actions have been completed or are planned:\n\n* Completed changes to limit retries and stop repeatedly processing failures that cannot be resolved through retries.\n* Applying the same, improved retry handling to other asynchronous processes, preventing similar occurrences from happening to other File Request features.\n* Improving alerting and response procedures for processing backlogs and retained unsuccessful events to ensure that temporary issues can later be retried safely.\n\nWe are continuously working to improve Box and want to make sure we are delivering the best product and user experience we can. We hope we have provided some clarity here and we would be happy to answer any questions you may still have regarding this matter.\n\nSincerely,\n\nThe Box Team", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-23T04:42:10.645-07:00", "resolved_inferred": false, "started_at": "2026-07-23T02:45:51.100-07:00", @@ -207,7 +207,7 @@ "body": "We recently addressed issues affecting Open With integrations within Box. We would like to take this opportunity to further explain these issues and the steps we have taken to prevent them from reoccurring.\n\nBetween 1:00 PM PDT and 2:40 PM PDT on July 16, 2026, some customers may have been unable to open or edit files using any Open With integration in the Box web application. During this period, affected files may have appeared unavailable or grayed out, and users may have encountered permission-related errors when launching an integration. Microsoft Office workflows, including Office Online in the browser and desktop editing through Box Edit, were among those impacted.\n\nThe issue occurred after a recent service update unintentionally changed how integration workflows were handled, causing the product to return an empty set of available integration actions for affected files. We resolved the issue by reverting the service to the previously deployed version, after which service metrics and customer confirmations recovered. In addition, we are taking steps to reduce reoccurrence by improving testing, monitoring, and release practices for integration paths.\n\n# Analysis\n\nThis incident highlighted opportunities to improve end-to-end testing for integration workflows and our automated detection process.\n\nThe failure mode returned an empty action list rather than hard errors, which kept broad service-level signals near baseline and made the impact visible primarily through customer reports.\n\n# Corrective Actions\n\nBox has initiated the following corrective actions:\n\n* Expanded lower-environment end-to-end tests to validate Open With / Office Online behaviors after changes to integration-related code.\n* Added targeted monitoring and alerting for integration action and permission-check failures so regressions surface automatically.\n* Documented and formalized release and rollback runbooks for integration-related changes, including clear validation and rollback steps to reduce time-to-recovery.\n\nWe are continuously working to improve Box and want to make sure we are delivering the best product and user experience we can. We hope we have provided some clarity here and we would be happy to answer any questions you may still have regarding this matter.\n\nSincerely,\n\nThe Box Team", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-16T14:48:30.000-07:00", "resolved_inferred": false, "started_at": "2026-07-16T14:30:27.000-07:00", @@ -220,7 +220,7 @@ "body": "We recently addressed issues affecting Box Relay. We would like to take the opportunity to further explain these issues and the steps we have taken to keep them from happening in the future.\n\nBetween 1:10 AM and 11:33 PM PT on July 14, 2026, some users may have experienced difficulties while working in Box. During this time, some users may have experienced degradation of Box Relay workflows that include a task outcome. The issue occurred as a result of a recent code change intended to improve how task assignments are handled in workflows. We were able to resolve the issue by reverting that change and restoring the previous behavior. In addition, we are improving our automated testing, monitoring, and deployment safeguards to prevent similar issues from occurring in the future.\u00a0\n\n\u200c\n\n**Analysis** \n\nA Box Relay workflow can include a task outcome, which assigns a task to one or more people. As part of that outcome, the workflow also attempts to give each assignee access to the relevant file. A recent change caused the entire task outcome to fail whenever that access-granting operation was rejected. Such a rejection is an expected condition in some configurations \\(_e.g._, when the person who owns the workflow does not have sufficient permission to share the file, or when sharing restrictions are in place\\) and it can occur even when the assignee already has access to the file. Previously these rejections were tolerated and the task was still created. After the change, they caused the task outcome to fail, so affected workflows stopped completing.\n\n\u200c\n\n**Corrective Actions**\n\nBox has initiated the following corrective actions:\n\n* Adding automated test coverage for this scenario to prevent similar regressions.\n* Adding monitoring and alerting for workflow-processing failures, so this class of issue is detected proactively rather than through customer reports.\n* Refining the task-assignment logic to avoid unnecessary access-granting operations when an assignee already has access to the file.\n\n\u200c\n\nWe are continuously working to improve Box and want to make sure we are delivering the best product and user experience we can. We hope we have provided some clarity here and we would be happy to answer any questions you may still have regarding this matter.\u00a0\n\nSincerely, \nThe Box Team", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-14T23:43:22.021-07:00", "resolved_inferred": false, "started_at": "2026-07-14T21:14:09.557-07:00", @@ -233,7 +233,7 @@ "body": "We recently addressed an issue that affected Box Search and related Query functionality, including the Public APIs and Box Apps features that rely on them. We would like to take the opportunity to explain what happened and the steps we have taken to prevent it from happening again.\n\nOn July 7, 2026 between 06:22 AM and 08:53 AM PT, some customers may have experienced elevated latencies and intermittent errors when using the Box Search and Query functionality. Public APIs for these features, Box Apps, Web App Search, and other functionalities that depends on Search and Query APIs were also impacted. This incident was caused by a sudden surge in indexing traffic that overwhelmed services in one of our subsystems, before they could be scaled up or rate limiting could kick in. We were able to remediate the issue by isolating the offending traffic and allowing the surge of indexing work to finish processing and drain. Regular traffic routing was restored once the affected infrastructure was healthy again.\n\n# **Analysis**\n\nThis incident revealed an opportunity to improve how we protect our search indexing subsystem from sudden~~,~~ and concentrated surges of load. While our stateless services can quickly autoscale horizontally, our stateful systems cannot be scaled as quickly to handle sudden surges in load. We\u2019ve historically focused on query traffic driven load and over-provisioned to handle any increases in internally generated indexing load. This incident revealed that sudden and large indexing surges can impact stability more than we anticipated. Our safeguards did not sufficiently slow or throttle a large burst of re-indexing traffic, and a temporary configuration change in place at the time of this incident caused files to be re-indexed in full even when only non-content attributes had changed, amplifying the load. \n\n# **Corrective Actions**\n\nBox has initiated the following corrective actions:\n\n* Add per source rate limiting to the indexing pipeline so a large burst of work cannot overwhelm the subsystem.\n* Optimize indexing load, so files are only re-indexed when their content has actually changed.\n* Set safer limits on how much work the pipeline will accept at once.\n* Improve monitoring and alerting to detect unusual spikes in processing earlier and respond before customers are impacted.\n\n\u200c\n\nWe are continuously working to improve Box and want to make sure we are delivering the best product and user experience we can. We hope this provides clarity on what occurred and the steps we are taking. We would be happy to answer any questions you may still have regarding this matter.\n\nSincerely, \nThe Box Team", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-07T09:19:34.145-07:00", "resolved_inferred": false, "started_at": "2026-07-07T07:11:14.153-07:00", @@ -246,7 +246,7 @@ "body": "Between 10:40 AM PDT and 12:33 PM PDT on June 25, 2026, some users may have experienced difficulties while working in Box. During this time, users routed through one particular US region may have seen failures or delays when attempting to download folders as ZIP files.\n\nThe issue occurred after a recent network component update impacted a backend service in that region. We restored the feature availability by reverting the change. In addition, we are updating configuration and monitoring practices for such changes to reduce the likelihood of recurrence.\n\n# Analysis\n\nAs part of our continuous and ongoing service improvement efforts, we recently rolled out a change to our internal compute platform. In one of our US regions, this change resulted in a resource problem within our service mesh layers. This incident highlighted opportunities to improve how platform updates and service configuration changes are propogated across Box compute regions.\n\n# Corrective Actions\n\nBox has initiated the following corrective actions:\n\n* Improved our multi-region roll out monitoring and alerting\n* Audited resource configurations for multi-region services\n* Improved ongoing monitoring and alerting of multi-region services\n\n\u200c\n\nWe are continuously working to improve Box and want to make sure we are delivering the best product and user experience we can. We hope we have provided some clarity here and we would be happy to answer any questions you may still have regarding this matter.\n\nSincerely, \nThe Box Team", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-25T14:47:38.161-07:00", "resolved_inferred": false, "started_at": "2026-06-25T12:29:04.063-07:00", @@ -259,7 +259,7 @@ "body": "We recently addressed issues affecting file uploads in Box. We would like to take the opportunity to further explain these issues and the steps we have taken to keep them from happening in the future.\n\nBetween 4:47 AM PDT and 5:28 AM PDT on June 24, 2026, some users may have experienced difficulties uploading larger files to Box. During this time, chunked uploads of large files may have failed or timed out, while smaller file uploads continued to work normally. The issue occurred when an internal system that temporarily tracks the progress of large, chunked uploads experienced an unexpected failover and lost the in-progress upload information it was holding. The issue resolved once those connections were reset. In addition, we are hardening how our upload service detects and recovers from this kind of interruption to prevent similar issues in the future.\n\n# Analysis\n\nLarge file uploads in Box are split into multiple parts and rely on a shared internal caching system to track the progress of each upload while it is in flight. During this incident, that caching system underwent an unexpected failover, and the newly promoted instance did not contain all of the in-progress upload state. As a result, affected sessions could not continue and returned errors. Recovery was further delayed because the upload service continued to use a connection that was no longer valid. Standard file uploads do not depend on this system and were not affected.\n\n## Corrective Actions\n\nBox has initiated the following corrective actions:\n\n* Adding dedicated monitoring and alerting for this caching system so that similar failures are detected and corrected more quickly.\n* Improving how the upload service detects a lost connection and reconnects automatically, so that recovery is faster and does not require manual intervention.\n* Strengthening the resilience of large-upload session storage so that a failure of this caching system has reduced impact on in-progress uploads.\n\nWe are continuously working to improve Box and want to make sure we are delivering the best product and user experience we can. We hope we have provided some clarity here and we would be happy to answer any questions you may still have regarding this matter.\n\nSincerely, \n\nThe Box Team", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-24T05:33:15.191-07:00", "resolved_inferred": false, "started_at": "2026-06-24T05:18:40.053-07:00", @@ -272,7 +272,7 @@ "body": "We recently addressed issues affecting the Box API, All Files, and Box AI. We would like to take the opportunity to further explain what happened and the steps we have taken to prevent reoccurrence.\n\nBetween 12:06 PM PDT and 12:39 PM PDT on June 17, 2026, some users may have experienced difficulties while working in Box. During this time, some customers were unable to access content, browse folders, or complete uploads and other file operations, and error rates for affected features were elevated.\n\n**What Happened**\n\nThe issue occurred after a recent rollout of a new traffic-routing change for the All Files experience reached full traffic volume. This routing change directed file-browsing requests through a newer service path that, under full production load, generated a significantly higher volume of calls to an underlying data-access component than had been observed during earlier, partial rollouts. The increased call volume saturated a capacity-limited thread pool within our file service. Once that threshold was crossed, automated health checks detected the degraded state and began restarting affected service instances \u2014 which, combined with retry traffic from dependent services, amplified the load and caused a cascading degradation affecting the API, All Files browsing, and Box AI.\n\n**How We Restored Service**\n\nWe restored service by:\n\n* Disabling the recent traffic-routing rollout, returning file-browsing requests to the prior service path\n* Increasing the capacity of the affected file service to absorb the load\n* Reverting a separate, unrelated deployment as a precautionary measure\n\nMonitoring confirmed that availability and error rates returned to normal by 12:39 PM PDT, approximately 33 minutes after impact began.\n\n**Analysis**\n\nThis incident highlighted opportunities to evaluate how a new traffic-routing change is validated at production scale and how dependent components behave when exposed to that traffic pattern for the first time. Specifically, the new routing path generated a more resource-intensive class of data queries than the partial rollout had revealed, and the affected service lacked sufficient capacity headroom to absorb the full traffic volume. It also showed the value of rapid rollback capability and coordinated monitoring across feature rollouts and service capacity limits.\n\n**Corrective Actions**\n\nBox has initiated the following corrective actions:\n\n* **Increase and harden service capacity and autoscaling:** We have increased the capacity of the affected file service and are improving autoscaling thresholds so the service can respond dynamically to traffic spikes.\n* **Improve pre-rollout validation:** We are strengthening load testing and validation of traffic-routing changes under realistic, production-like conditions before full deployment.\n* **Tighten rollout safeguards and monitoring:** We are improving rollout gates, alerting, and automated rollback capabilities to enable faster detection and response when changes cause elevated error rates.\n* **Decouple health probes from capacity saturation:** We are updating how service health checks interact with capacity limits to avoid crash-loop scenarios that can amplify failures during high-load events.\n\nWe are continuously working to improve Box and want to make sure we are delivering the best product and user experience we can. We hope this provides clarity on what occurred and the steps we are taking. We would be happy to answer any questions you may still have regarding this matter.\n\nSincerely, The Box Team", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-17T13:28:10.568-07:00", "resolved_inferred": false, "started_at": "2026-06-17T12:34:08.934-07:00", @@ -285,7 +285,7 @@ "body": "We recently addressed issues affecting Box Public API. We would like to take the opportunity to further explain these issues and the steps we have taken to keep them from happening in the future. \n\nBetween 5:10 PM PDT and 6:40 PM PDT on June 10, 2026, some users may have experienced difficulties accessing or working within Box. During this period, there was a noticeable degradation affecting Public API request processing. This issue occurred as a result of a recent software change to our authentication infrastructure in our ongoing effort to improve performance and stability of Public API service. We were able to resolve the issue by scaling up the service, correcting its resource allocation, and rolling back the change. In addition, we are working to improve our resource provisioning to prevent similar issues from occurring in the future. \n\n**Analysis** \n\nWe recently began rolling out an update to our authentication infrastructure designed to improve performance and stability of Public API service. Following the gradual rollout, an increase in resource utilization during peak traffic led to unexpected resource utilization on our authentication infrastructure. As a result, those servers became unresponsive, preventing them from processing Public API requests. We were able to resolve the issue by temporarily scaling up and adjusting the resource allocations of the authentication service. \n\n**Corrective Actions**\n\nBox has initiated the following corrective actions:\n\n* Rebalancing the resource allocations of the authentication service to accommodate higher traffic volumes\n* Tuning server timeouts across Public API components to ensure consistent, predictable API response times\n* Establishing processes and automation to reduce time to mitigation \n\nWe are continuously working to improve Box and want to make sure we are delivering the best product and user experience we can. We hope we have provided some clarity here and we would be happy to answer any questions you may still have regarding this matter.\u00a0\n\nSincerely, \nThe Box Team", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-10T19:01:00.142-07:00", "resolved_inferred": false, "started_at": "2026-06-10T17:34:13.920-07:00", @@ -298,7 +298,7 @@ "body": "We recently addressed issues affecting Authentication, File Access, Notes, Uploads, and Public API. We would like to take the opportunity to further explain these issues and the steps we have taken to keep them from happening in the future.\n\nOn June 3, 2026 between 10:53 PM and 10:58 PM PDT, some customers may have experienced issues when attempting to sign in to Box and when accessing files, notes, uploads, and our public API. The issue was caused by a temporary fluctuation in a database shard due to elevated disk activity, which led to connection saturation and service errors for a subset of users. Service returned to normal by 10:58 PM PDT and monitoring remains in place to watch for recurrence. \n\n# Analysis\n\nAs part of our routine system maintenance, we deployed standard software updates to our infrastructure. Following these updates, a scheduled background system scan processed a larger-than-normal volume of files. This background activity led to temporary resource contention on the database tier, resulting in brief latency and connection saturation for a subset of users.\n\nWhile Box utilizes redundant database replicas to ensure high availability, our automated monitoring and failover systems did not immediately redirect traffic because the database remained partially responsive. \n\n# Corrective Actions\n\nBox has initiated the following corrective actions:\n\n* Implemented strict I/O resource limits on background maintenance processes to ensure they cannot impact active user traffic.\n* Upgraded our database monitoring and health checks to immediately detect and alert on localized resource contention, ensuring faster automated failover response.\n\n\u200c\n\nWe are continuously working to improve Box and want to make sure we are delivering the best product and user experience we can. We hope we have provided some clarity here and we would be happy to answer any questions you may still have regarding this matter.\n\nSincerely, \nThe Box Team", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-03T10:53:00.000-07:00", "resolved_inferred": false, "started_at": "2026-06-03T10:30:00.000-07:00", @@ -311,7 +311,7 @@ "body": "_Notice and disclaimer: Box is providing this preliminary information subject to further review and analysis. To the best of our knowledge, this is the current state and we may update as more information is confirmed._\n\nOn May 31, 2026 between 5:00pm PDT and 6:41pm PDT, some customers may have experienced errors or degraded performance when using Box AI features, including failures to generate AI responses or slower-than-expected behavior. The issue affected only AI-related capabilities and did not impact general file access.\n\nThe disruption was caused by an outage with a third-party AI provider that led to failed AI requests. Service was restored once the provider issue was resolved and normal AI request processing resumed.\n\nWe are reviewing our third-party dependencies and operational practices to reduce the risk of similar interruptions in the future.\n\nWe are conducting a full engineering postmortem and our overview is subject to change with further analysis and findings. In the event our continuing investigation yields further substantive findings, we may publish additional analysis after the conclusion of the full engineering postmortem.\n\nWe are continuously working to improve Box and want to make sure we are delivering the best product and user experience we can. We hope we have provided some clarity here and we would be happy to answer any questions you may still have regarding this matter.\n\nSincerely,\n\nThe Box Team", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-31T19:25:47.434-07:00", "resolved_inferred": false, "started_at": "2026-05-31T17:58:40.111-07:00", @@ -324,7 +324,7 @@ "body": "We recently addressed issues affecting Box Drive login and Single Sign-On \\(SSO\\) configuration. We would like to take the opportunity to further explain these issues and the steps we have taken to keep them from happening in the future.\n\nBetween 10:56 PM PDT on May 21, 2026 and 2:07 AM PDT on May 22, 2026, some users may have experienced difficulties while working in Box. During this time, enterprise customers with Intune Mobile Application Management \\(MAM\\) enabled experienced SSO login failures when attempting to access Box Drive, and administrators were unable to view, update, or manage SSO configurations in the Admin Console. The issue occurred as a result of an unintended configuration change where our primary, active identity provider administration console region was inadvertently flipped to passive mode. We were able to resolve the issue by restoring the primary administration console region back to active status, which immediately restored normal API and login flows. In addition, we are making updates to improve monitoring and alerting for related operational workflows to prevent similar issues from occurring in the future.\u00a0\n\n**Analysis** \n\nThe active and standby regions were unintentionally reversed, causing the live production region to be switched into standby mode. As a result, the administrative API, which was used in for Intune MAM login flow, began rejecting requests for customers using Intune MAM-protected accounts and temporarily blocked certain SSO management actions in the Admin Console. End users affected by this saw login errors until the regions were restored to their correct state. We have since added safeguards to prevent unintended region switches and improved how our login flow handles this type of upstream failure.\n\n**Corrective Actions**\n\nBox has initiated the following corrective actions:\n\n* Add monitoring to catch certain configuration mismatches that could lead to unintended changes in service routing\n* Implement additional restrictions for administrative console region-flip\n\nWe are continuously working to improve Box and want to make sure we are delivering the best product and user experience we can. We hope we have provided some clarity here and we would be happy to answer any questions you may still have regarding this matter.\u00a0 \n\nSincerely,\n\nThe Box Team", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-22T02:18:22.378-07:00", "resolved_inferred": false, "started_at": "2026-05-22T01:46:15.327-07:00", @@ -337,7 +337,7 @@ "body": "We recently addressed issues affecting **Enterprise Events API**. We would like to take the opportunity to further explain these issues and the steps we have taken to keep them from happening in the future.\n\n\u200c\n\nBetween 2:31am and 4:45pm PDT on May 14, 2026, some users may have experienced difficulties while working in Box. During this time, customers using the streaming Enterprise Events API experienced delivery delays of up to 6.5 hours. The issue occurred when an internal indexing service unexpectedly generated events at an unconstrained rate, which caused a significant concentrated spike in the total events volume. We were able to resolve the issue by redirecting those events from our streaming enterprise events pipeline for later processing. In addition, we will exclude events originating from internal services from our enterprise events processing pipelines and proactively deprioritize unexpected surges in events to prevent similar issues from occurring in the future.\n\n\u200c\n\n**Analysis** \n\n\u200c\n\nThere were a number of contributing factors leading to this incident and a reoccurrence on May 18, 2026 between 11:52am and 2:03pm PDT with delivery delays of up to 1.1 hours:\n\n\u200c\n\nOur internal search indexing service produced events, which should not have been created, at a rate significantly exceeding enterprise usage. These events were published to a queue to be written to the persistent datastore. Also, these events were concentrated in certain access patterns causing hot spotting in some database partitions. The significantly reduced throughput of these partitions caused the subscriber to fall behind. Once these access patterns were identified and the corresponding events removed, service was resolved promptly. Moving forward, these events will not be published.\n\n\u200c\n\n**Corrective Actions**\n\n\u200c\n\nThe following corrective actions have been completed or are planned:\n\n\u200c\n\n* **Disable Event Publishing for Search Services** - We are disabling enterprise events from being produced and processed from Box internal services.\n* **Deprioritize Surge Workloads** - We will monitor for workloads generating significant volumes of event data and deprioritize those events from the primary pipeline.\n* **Update Incident Response Procedures** - We are updating our runbooks to account for these conditions and related actions.\n\n\u200c\n\nWe are continuously working to improve Box and want to make sure we are delivering the best product and user experience we can. We hope we have provided some clarity here and we would be happy to answer any questions you may still have regarding this matter.\u00a0\n\n \n\nSincerely,\n\nThe Box Team", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-14T12:30:00.000-07:00", "resolved_inferred": false, "started_at": "2026-05-14T12:30:00.000-07:00", @@ -350,7 +350,7 @@ "body": "We recently addressed issues affecting folder and collection browsing, and related APIs. We would like to take the opportunity to further explain these issues and the steps we have taken to keep them from happening in the future.\n\nBetween 05:22 PM PDT and 07:04 PM PDT on May 6, 2026, some users may have experienced difficulties while working in Box. During this time, users reported failures and elevated errors when loading folders and collections, intermittent service errors, and degraded AI-related functionality.\n\nThe issue was caused by runtime saturation in a backend API service that had been gradually approaching its capacity limits over several weeks. During peak traffic hours, multiple service instances simultaneously became unable to respond to internal health checks within the configured timeout. As those instances were restarted, traffic shifted to the remaining instances, increasing load on them and creating a cascading failure. We mitigated the issue by stopping the restart cycle, routing traffic to alternate paths, and increasing service capacity.\n\n\u200c\n\n**Analysis**\n\nThis incident revealed several contributing causes:\n\n* Insufficient scaling signals \u2014 autoscaling was primarily configured around CPU utilization. For this service, CPU utilization did not accurately reflect runtime saturation, so the fleet did not scale early enough in response to the actual bottleneck.\n* Health check sensitivity under load \u2014 health checks were configured with timeouts that did not account for the service\u2019s behavior under sustained runtime saturation. Once instances became slow to respond, restarts amplified the problem by shifting more traffic to the remaining instances.\n* Gradual capacity erosion without alerting \u2014 the service had shown intermittent health check failures during prior peak traffic periods. Those earlier events were narrow enough to self-recover, but they were not surfaced as a clear trend requiring action.\n* Retry amplification \u2014 as service instances became unavailable, upstream retry behavior added additional load to the remaining healthy instances, accelerating the cascade.\n\nThis incident highlighted opportunities for improvement in how we detect and respond to runtime saturation that is not always visible from CPU metrics alone. It also reinforced the need for stronger end-to-end observability, clearer health-check visibility, and validated mitigation paths for service instability.\n\n\u200c\n\n**Corrective Actions**\n\nBox has initiated the following corrective actions:\n\n* Improved runtime monitoring and alerting \u2014 we added alerts for runtime saturation metrics that detect this class of failure independently of CPU utilization, providing earlier warning before customer impact occurs.\n* Revised autoscaling strategy \u2014 we reconfigured autoscaling to trigger on signals that reflect actual service capacity and validate that the fleet scales correctly under realistic load conditions.\n* Health check and resilience tuning \u2014 we are reviewing health check configurations and retry behavior to reduce the risk that transient runtime saturation can turn into cascading restarts.\n* Capacity validation and load testing \u2014 we are establishing load testing against production-representative traffic patterns and maintaining capacity headroom until the service's efficiency improvements are validated.\n* Runtime performance improvements \u2014 we identified and are implementing changes to the service framework that significantly reduce per-request overhead, providing more headroom against future saturation.\n\n\u200c\n\nWe are continuously working to improve Box and want to make sure we are delivering the best product and user experience we can. We hope we have provided some clarity here and we would be happy to answer any questions you may still have regarding this matter.\n\nSincerely, \nThe Box Team", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-06T20:07:43.297-07:00", "resolved_inferred": false, "started_at": "2026-05-06T18:20:15.000-07:00", @@ -363,7 +363,7 @@ "body": "After further monitoring, this incident is now considered resolved. Search with metadata has been restored to full functionality. If you continue to experience any issues, please contact Box Support at https://support.box.com.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-27T12:11:39.555-07:00", "resolved_inferred": false, "started_at": "2026-04-27T10:36:40.630-07:00", @@ -376,7 +376,7 @@ "body": "On April 2, 2026 between 8:19 PM PDT and 11:56 PM PDT, some users may have experienced difficulties while working in Box. During this time, Box Sign users might have experienced errors while creating new signature requests, accessing existing signature requests, or attempting ~~been unable~~ to access the service. The issue occurred as a result of an erroneous change made by a third-party infrastructure provider. We were able to resolve the issue by escalating it to the provider. In addition, we are working to improve the reliability of the Box Sign service by enhancing our disaster recovery processes to prevent similar issues from occurring in the future.\u00a0\n\n\u200c\n\nWe are conducting a full engineering postmortem and our overview is subject to change with further analysis and findings. In the event our continuing investigation yields further substantive findings, we may publish additional analysis after the conclusion of the full engineering postmortem.\n\n \n\nWe are continuously working to improve Box and want to make sure we are delivering the best product and user experience we can. We hope we have provided some clarity here and we would be happy to answer any questions you may still have regarding this matter.\u00a0\n\n \n\nSincerely,\n\nThe Box Team", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-03T01:09:36.925-07:00", "resolved_inferred": false, "started_at": "2026-04-02T21:04:31.122-07:00", @@ -389,7 +389,7 @@ "body": "After further monitoring, this incident is now considered resolved. The Admin console service has been restored to full functionality. If you continue to experience any issues, please contact Box Support at https://support.box.com.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-25T07:03:53.516-07:00", "resolved_inferred": false, "started_at": "2026-03-25T04:44:45.799-07:00", @@ -402,7 +402,7 @@ "body": "We recently addressed issues affecting Shuttle \\(migration service\\). We would like to take the opportunity to further explain these issues and the steps we have taken to keep them from happening in the future.\n\n\u200c\n\nBetween 03/24/2026 08:00 PM PDT and 03/25/2026 11:40 AM PDT on Mar 24\u201325, 2026 \u2014 some users may have experienced difficulties while working in Box. During this time, users reported blank pages, timeouts, and failures when configuring or running migration jobs in the Shuttle interface.\n\n\u200c\n\nThe issue occurred after a vendor-managed database maintenance update that included an operating system and security library change, which caused the affected database clusters to enter a read-only or degraded state and prevented normal job configuration and history access. We were able to resolve the issue after the vendor reverted the change on the affected clusters and our teams restarted the dependent services, after which we verified normal operation. In addition, we will take steps to reduce the likelihood of recurrence by improving coordination and testing for vendor-managed upgrades and strengthening our operational safeguards.\n\n\u200c\n\n# Analysis\n\n\u200c\n\nThis incident highlighted risks in relying on vendor-managed platform updates without staged validation across environments, and showed gaps in how quickly we could detect and isolate read-only database states. Response required close vendor collaboration to identify and revert the change; internal mitigations \\(service restarts and connection management\\) were insufficient until the vendor rollback completed. We will improve pre-upgrade controls, monitoring for early signs of degraded database state, and runbook guidance for faster mitigation.\n\n\u200c\n\n# Corrective Actions\n\nBox has initiated the following corrective actions:\n\n\u200c\n\n* Require staged validation of vendor-managed platform upgrades \\(dev \u2192 staging \u2192 production\\) before production rollout.\n* Establish a coordinated upgrade/runbook with the vendor that defines pre-checks, rollback steps, and escalation pathways.\n* Enhance monitoring and alerts for read-only database states, failed elections, and connection saturation to detect similar issues earlier.\n\n\u200c\n\nWe are continuously working to improve Box and want to make sure we are delivering the best product and user experience we can. We hope we have provided some clarity here and we would be happy to answer any questions you may still have regarding this matter.\n\n\u200c\n\nSincerely,\n\n\u200c\n\nThe Box Team", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-25T10:00:26.223-07:00", "resolved_inferred": false, "started_at": "2026-03-24T22:52:05.462-07:00", @@ -415,7 +415,7 @@ "body": "We recently addressed issues affecting the \u201cAll Files\u201d page in Box. We would like to take the opportunity to further explain these issues and the steps we have taken to keep them from happening in the future.\n\nBetween **3:00 PM PDT** and **9:34 PM PDT** on **March 19, 2026**, some users may have experienced difficulties while working in Box. During this time, users accessing Box through the web application may have encountered blank pages when navigating into folders on the \u201cAll Files\u201d page or when opening certain shared links. The issue occurred as a result of a recent code change, made in our ongoing effort to improve performance and stability. We were able to resolve the issue by reverting the web application to the previous stable version. In addition, we are strengthening safeguards in our deployment and rollback processes to prevent similar issues from occurring in the future.\u00a0\n\n**Analysis** \n\nThe incident revealed areas for improvement in automation reliability, validation controls, and the consistency of rollout and rollback mechanisms, which contributed to an unintended artifact version being promoted to the production environment. \n\n**Corrective Actions**\n\nBox has initiated the following corrective actions:\n\n* **Strengthen deployment validation and gating mechanisms**: We are implementing stricter automated checks to verify artifact integrity, version correctness, and configuration alignment at each stage of the pipeline, ensuring only validated and approved builds can be promoted to production.\n* **Standardize and reinforce rollout and rollback procedures**: We are establishing consistent, well-documented deployment and rollback workflows with automated safeguards and audit trails to ensure reliable reversibility and prevent incorrect artifact promotion during release operations.\n\nWe are continuously working to improve Box and want to make sure we are delivering the best product and user experience we can. We hope we have provided some clarity here and we would be happy to answer any questions you may still have regarding this matter.\u00a0\n\nSincerely,\n\nThe Box Team", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-19T22:08:54.099-07:00", "resolved_inferred": false, "started_at": "2026-03-19T20:37:48.892-07:00", @@ -428,7 +428,7 @@ "body": "Between 10:56am PST to 11:42am PST on March 18th, 2026 some users may have experienced difficulties previewing files. No further impact has been observed and we are considering this issue to be resolved. If you are still experiencing any issues, please let us know at https://support.box.com.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-18T11:00:00.000-07:00", "resolved_inferred": false, "started_at": "2026-03-18T09:00:00.000-07:00", @@ -441,7 +441,7 @@ "body": "We recently addressed an issue affecting logins to Box. We would like to take the opportunity to further explain this issue and the steps we have taken to keep it from happening in the future.\n\nBetween **4:46 PM PDT** and **5:32 PM PDT** on **March 9, 2026**, some users may have experienced difficulties logging in to Box leading to disruptions when using some Box features. This issue occurred when a service involved in the login process did not have sufficient resources to handle an uneven spike in traffic, which caused a portion of login-related requests to time out. We resolved this by increasing resources for the affected service and expanding its capacity. We also took additional steps to reduce the likelihood that this type of issue could affect the login experience in the future.\n\n## **Analysis**\n\nThe incident surfaced opportunities to further refine how we size and distribute capacity across services that support login-related traffic. It also underscored the value of strengthening earlier detection of traffic imbalances and simplifying dependencies within critical login flows.\n\n## **Corrective Actions**\n\nBox has initiated the following corrective actions:\n\n* **Strengthen resource allocation and scaling:** We are tuning resource allocation and scaling behavior so services can better absorb unusual traffic patterns without degradation.\n* **Improve traffic distribution and monitoring:** We are refining how traffic is distributed across service instances and strengthening monitoring so we can identify and address unhealthy capacity patterns sooner.\n* **Reduce login path dependencies:** We are simplifying the login flow so fewer background checks are required for most users, reducing the potential impact of issues in supporting services.\n\n\u200c\n\nWe are continuously working to improve Box and want to make sure we are delivering the best product and user experience we can. We hope we have provided some clarity here and we would be happy to answer any questions you may still have regarding this matter.\n\nSincerely, \nThe Box Team", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-09T18:14:03.518-07:00", "resolved_inferred": false, "started_at": "2026-03-09T17:30:24.333-07:00", @@ -454,7 +454,7 @@ "body": "We recently addressed issues affecting Box FTP and SFTP services. We would like to take the opportunity to further explain these issues and the steps we have taken to keep them from happening in the future.\n\n \n\nFrom February 25th, 2026 at 9:20 AM PST to February 27th at 4:10 PM PST, some users may have experienced difficulties while working in Box. During this time, Box FTP and SFTP users may have seen CAPTCHA messages while logging in through FTP. The issue occurred due to a change in internal traffic routing which affected the Box FTP and SFTP services. We were able to resolve the issue by reverting the internal routing change and clearing CAPTCHAs for affected users. We are now working to harden the system against internal rate limiting going forward to prevent similar issues from occurring in the future.\u00a0\n\n\u200c\n\n**Analysis** \n\nOn February 23rd at 8:20 AM PST, a change was made to send a subset of login traffic through a new route. After this change, no issues were observed and no customer issues were reported. On February 25th at 8:20 AM PST, a subsequent change was made to send more of the same login traffic through the new route. Roughly one hour after this change was completed, the Box FTP service started to receive an increased rate of CAPTCHA failures, blocking users from logging in. The second routing change was identified as the root cause and reverted on February 27th at 12:49 PM PST. After revert, a number of Box FTP users needed to clear an additional CAPTCHA. Box Support assisted in clearing the CAPTCHAs manually and by 4:10 PM PST, all Box FTP and SFTP login errors were resolved.\n\n\u200c\n\nOur analysis determined that the root cause of this issue was a service that was added to the call stack in the new route. The service in question did not properly communicate rate limiting information sent by the Box FTP service. This led to Box FTP being internally rate limited, which prompted users to improperly complete a CAPTCHA when logging in to Box FTP. \n\n\u200c\n\n**Corrective Actions**\n\nBox has initiated the following corrective actions:\n\n* The service in question has been fixed to properly forward required rate limiting information.\n* We are implementing enhanced monitoring to enable faster responses in the case of similar occurrences.\n* A comprehensive review is being performed to find any instances of missing rate limiting information within the stack.\n\n\u200c\n\nWe are continuously working to improve Box and want to make sure we are delivering the best product and user experience we can. We hope we have provided some clarity here and we would be happy to answer any questions you may still have regarding this matter.\u00a0\n\n \n\nSincerely,\n\nThe Box Team", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-27T15:51:54.322-08:00", "resolved_inferred": false, "started_at": "2026-02-27T12:02:45.000-08:00", @@ -467,7 +467,7 @@ "body": "_Notice and disclaimer: Box is providing this preliminary information subject to further review and analysis. To the best of our knowledge, this is the current state and we may update as more information is confirmed._\n\n \n\nOn February 25, 2026 between 4:45 am PST and 5:40 am PST, some users may have experienced difficulties while working in Box. During this time, customers of Box Zones UK may have had issues with uploading, downloading, and previewing files.\n\n\u200c\n\nThe issue occurred when some instances of a backend service in the impacted region ran into memory pressure. We resolved the issue by temporarily redirecting certain compute processes from the impacted region to the US region. Of note, even during the period of temporary traffic redirection, all Box Zones customer content continued to be stored in the correct Box Zones region. \n\n\u200c\n\nWe are conducting a full engineering postmortem and our overview is subject to change with further analysis. In the event our continuing investigation yields further substantive findings, we may publish additional analysis after the conclusion of the full engineering postmortem.\n\n \n\nWe are continuously working to improve Box and want to make sure we are delivering the best product and user experience we can. We hope we have provided some clarity here and we would be happy to answer any questions you may still have regarding this matter.\u00a0\n\n \n\nSincerely,\n\nThe Box Team", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-25T06:16:45.788-08:00", "resolved_inferred": false, "started_at": "2026-02-25T05:00:14.000-08:00", @@ -480,7 +480,7 @@ "body": "_Notice and disclaimer: Box is providing this preliminary information subject to further review and analysis. To the best of our knowledge, this is the current state and we may update as more information is confirmed._\n\n \n\nOn February 24, 2026 between 1:15 PM PST and 3:59 PM PST, some users may have experienced difficulties while working in Box. The most significant impact occurred from 1:42 PM PST to 1:59 PM PST, when Uploads, Downloads, Logins, APIs, and Notes saw elevated latency and errors. A small subset of functionality continued to experience some degradation through 3:59 PM PST. The issue occurred due to our cache cluster becoming temporarily overloaded due to a traffic spike concentrated on a single hot key. We were able to resolve the majority of the impact by rate limiting peripheral workloads and fully resolve the issue by stopping the offending traffic source. We are now implementing automated hot key detection and introducing dynamic rate limiting at the caching layer to prevent similar issues from occurring in the future.\n\n\u200c\n\nWe are conducting a full engineering postmortem and our overview is subject to change with further analysis and findings. In the event our continuing investigation yields further substantive findings, we may publish additional analysis after the conclusion of the full engineering postmortem.\n\n \n\nWe are continuously working to improve Box and want to make sure we are delivering the best product and user experience we can. We hope we have provided some clarity here and we would be happy to answer any questions you may still have regarding this matter.\n\n \n\nSincerely,\n\nThe Box Team", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-24T16:15:38.617-08:00", "resolved_inferred": false, "started_at": "2026-02-24T15:32:12.938-08:00", @@ -493,7 +493,7 @@ "body": "_Notice and disclaimer: Box is providing this preliminary information subject to further review and analysis. To the best of our knowledge, this is the current state and we may update as more information is confirmed._ \n\n\u200c\n\nOn February 24th, 2026 between 6:11 AM PST and 6:40 AM PST, some users may have experienced difficulties while while attempting to log into Box. Users already logged into Box were not impacted by this issue. The issue occurred due to a recent configuration change related to device security that prevented users from logging in to Box. We were able to resolve the issue by quickly reverting the change. We are also working to improve our release strategy and testing processes to prevent similar issues from occurring in the future.\n\n\u200c\n\nWe are conducting a full engineering postmortem and our overview is subject to change with further analysis and findings. In the event our continuing investigation yields further substantive findings, we may publish additional analysis after the conclusion of the full engineering postmortem.\n\n \n\nWe are continuously working to improve Box and want to make sure we are delivering the best product and user experience we can. We hope we have provided some clarity here and we would be happy to answer any questions you may still have regarding this matter.\u00a0\n\n \n\nSincerely,\n\nThe Box Team", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-24T08:07:33.718-08:00", "resolved_inferred": false, "started_at": "2026-02-24T06:59:00.418-08:00", @@ -506,7 +506,7 @@ "body": "We recently addressed issues affecting Box web access. We would like to take the opportunity to further explain these issues and the steps we have taken to keep them from happening in the future.\n\nBetween 10:50 AM PST and 11:25 AM PST on February 20, 2026, some users may have experienced difficulties accessing Box via web browser, including failed page loads and intermittent connectivity. During this time, requests to our site that relied on a third-party network service did not route reliably for affected networks, causing DNS resolution and connectivity failures for that hostname. We were able to restore service after the third-party re-advertised the affected network prefixes, at which point we safely re-enabled the dependent routing configuration, restoring normal service behavior. In addition, we are working with the third-party provider and updating our procedures and monitoring to reduce the risk of recurrence and improve detection and recovery.\n\n# Analysis\n\nThis incident highlighted a dependency risk on third-party network prefix advertisement and revealed opportunities to improve early detection and customer-facing communication. It also reinforced the importance of clear playbooks for safely changing routing configurations during third-party outages and ensuring monitoring captures customer-impacting DNS and connectivity failures quickly.\n\n# Corrective Actions\n\nBox has initiated the following corrective actions:\n\n* Work with the third-party provider to complete follow-up and incorporate their post-incident findings\n* Update our routing and operational runbooks to clarify safe, pre-approved steps for toggling routing configurations during third-party network incidents\n* Enhance external-facing monitoring and alert thresholds for DNS and site availability to detect and communicate customer impact more quickly\n\n\u200c\n\nWe are continuously working to improve Box and want to make sure we are delivering the best product and user experience we can. We hope we have provided some clarity here and we would be happy to answer any questions you may still have regarding this matter.\n\nSincerely, \nThe Box Team", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-20T12:37:30.000-08:00", "resolved_inferred": false, "started_at": "2026-02-20T11:11:55.000-08:00", @@ -519,7 +519,7 @@ "body": "From approximately 9:52 PM to 10:00 PM US Pacific time, we observed an issue impacting Logins, Notes and API. There is no current impact and no further updates will be provided here. If you continue to experience any issues, please contact Box Support at https://support.box.com.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-08T22:00:00.000-08:00", "resolved_inferred": false, "started_at": "2026-01-08T22:00:00.000-08:00", @@ -532,7 +532,7 @@ "body": "We recently addressed issues affecting Box. We would like to take the opportunity to further explain these issues and the steps we have taken to keep them from happening in the future.\n\n\u200c\n\nOn January 7th, 2026 between 5:10 PM and 5:50 PM PST, some customers experienced elevated errors and timeouts across multiple Box experiences, including Login, Uploads/Downloads, Box Notes, and the Public API. These issues were caused by a series of changes that triggered a request storm that overloaded our caching fleet. We resolved this by initially rate limiting background traffic and then rolling back the changes.\n\n\u200c\n\n**Analysis** \n\nOn January 6th, a new feature was deployed that increased the utilization of one of our cache backends. That feature, in isolation, did not cause any problem. On January 7th, at 3:30 PM PST, another application change was rolled out that increased the traffic on the same system. Combined, these two changes significantly decreased our capacity buffer on some of our cache systems.\n\n\u200c\n\nOn January 7th at 5:00 PM PT, another unrelated application change was released which created a short traffic spike in the cache system. This spike would have been handled without problems in a normal situation, but the reduced capacity buffer in our cache system created some temporary slowness and retries. Unfortunately, one critical code path that had been migrated to a newer infrastructure had a more aggressive retry policy than the old one. As a result, a retry storm increased the traffic progressively to our caching infrastructure. This traffic increase was not evenly balanced, as it was mostly targeting the few servers that were suffering under the load. The peak impact window was felt between 5:30PM and 5:50PM.\n\n\u200c\n\nTo resume normal operations, we deprioritized some background traffic to increase the capacity of our cache system, and rolled back the changes that were causing the elevated traffic.\n\n\u200c\n\n**Corrective Actions**\n\nBox has initiated the following corrective actions:\n\n* Implemented a more conservative retry control policy \\(to prevent retry amplification during partial failures\\)\n* Improved handling of cache-related failures to reduce cascading effects\n* Enhanced monitoring and alerting of our capacity buffers to identify the impact of sudden traffic spikes on our cache systems\n\n\u200c\n\nWe are continuously working to improve Box and want to make sure we are delivering the best product and user experience we can. We hope we have provided some clarity here and we would be happy to answer any questions you may still have regarding this matter.\u00a0\n\n\u200c\n\nSincerely, \nThe Box Team", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-07T18:37:45.040-08:00", "resolved_inferred": false, "started_at": "2026-01-07T17:39:31.724-08:00", @@ -545,7 +545,7 @@ "body": "We recently addressed issues affecting the Enterprise Report feature. We would like to take the opportunity to further explain these issues and the steps we have taken to keep them from happening in the future.\n\n \n\nOn January 2, 2026 between 5:30 AM and 2:33 PM PST, some users may have experienced difficulties while working in Box. During this time, users were unable to generate some types of Enterprise Reports, and Enterprise Reports scheduled during this time interval may have failed. We were able to resolve the issue by rolling back a configuration change that caused the issues for the reporting engine.\n\n\u200c\n\n**Analysis** \n\nBox Enterprise Reports relies on a definition of the schemas that describe the underlying database tables that the engine will consume to generate the reports. As we deliver new products, these schemas may occasionally need to be updated, and we have a standard process and pipeline to deploy these schema. As part of a project to upgrade our pipeline infrastructure, the schema deployment pipeline migrated to a new infrastructure. During the migration process, an external library version upgrade introduced a new default behavior that was not compatible with the existing pipeline. As a result, the Enterprise Reports service could not access the underlying tables in some cases, resulting in a temporary degradation of the service. Additionally, the migration process exposed some observability and guardrails gaps in the pipeline that would have prevented this issue from happening and that extended the impact for a longer period of time.\n\n\u200c\n\nOnce identified, the incompatible library was reverted to the previous version and the system went back to normal.\n\n\u200c\n\n**Corrective Actions**\n\nBox has initiated the following corrective actions:\n\n* Introduce a schema validation step in the deployment pipeline so that incompatible schemas cannot be deployed\n* Enforce the environment promotion process as part of the schema deployment pipeline\n* Uplift the observability of the pipeline to enable more visibility around the different phases of the deployment process\n\n\u200c\n\nWe are continuously working to improve Box and want to make sure we are delivering the best product and user experience we can. We hope we have provided some clarity here and we would be happy to answer any questions you may still have regarding this matter.\u00a0\n\n \n\nSincerely,\n\nThe Box Team", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-02T05:30:00.000-08:00", "resolved_inferred": false, "started_at": "2026-01-02T05:30:00.000-08:00", @@ -558,7 +558,7 @@ "body": "We recently addressed issues affecting several features of Box. We would like to take the opportunity to further explain these issues and the steps we have taken to keep them from happening in the future.\n\n\u200c\n\nOn December 17, 2025, from 11:15 AM PST to 4:46 PM PST, some users may have experienced difficulties while working in Box Sign, Box AI, and Box Doc Gen. During this time, users may have noticed service degradation and delayed email delivery. The issue was caused by a missing schema, which was itself caused by a corrupted schema deployment. We were able to resolve the issue by rolling back the change that temporarily created issues.\n\n\u200c\n\n**Analysis** \n\nBox Sign, Box AI, and Box Doc Gen rely on a definition of the schemas that describe the events that they need to process. As we deliver new products, these schemas may occasionally need to be updated, and we have a standard process and pipeline to deploy these schema. As part of a project to upgrade our pipeline infrastructure, the schema deployment pipeline migrated to a new infrastructure. During the migration process, an external library version upgrade introduced a new default behavior that was not compatible with the existing pipeline. This resulted in a temporary degradation of the service. Additionally, the migration process exposed some observability and guardrail gaps in the pipeline that would have prevented this issue from happening and that extended the impact for a longer period of time.\n\nOnce identified, the incompatible library was reverted to the previous version and the system resumed to normal.\n\n\u200c\n\n**Corrective Actions**\n\nBox has initiated the following corrective actions:\n\n* Introduce a schema validation step in the deployment pipeline so that incompatible schemas cannot be deployed\n* Enforce the environment promotion process as part of the schema deployment pipeline\n* Uplift the observability of the pipeline to enable more visibility around the different phases of the deployment process\n\n\u200c\n\nWe are continuously working to improve Box and want to make sure we are delivering the best product and user experience we can. We hope we have provided some clarity here and we would be happy to answer any questions you may still have regarding this matter.\u00a0\n\n\u200c\n\nSincerely, \nThe Box Team", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-17T16:45:12.213-08:00", "resolved_inferred": false, "started_at": "2025-12-17T16:21:38.894-08:00", @@ -571,7 +571,7 @@ "body": "We recently addressed issues affecting Box services**.** We would like to take the opportunity to further explain these issues and the steps we have taken to prevent them from happening in the future.\n\nOn December 16, 2025 between 4:25 PM PST and 7:23 PM PST, some users may have experienced slowness and temporary unavailability while working in Box. The issue occurred when we attempted to roll back a diagnostic change that was suspected of causing a minor degradation. The rollback unintentionally resulted in decreased capacity in our middleware service, leading to a degraded site experience. It also introduced a distributed deadlock condition that prolonged our incident response and mitigation efforts. Ultimately, we were able to resolve the deadlock and return to normal operations by temporarily throttling inbound traffic.\n\nWe have implemented measures to increase system capacity and minimize the possibility of a similar deadlock occurring in the future. We are also working on adding safeguards to avoid the rollback failure that served as the proximate cause of this incident.\n\n**Analysis**\n\nBetween 11:11 AM PST and 1:38 PM PST, there was a production deployment of code that was aimed at gathering diagnostic information from our middleware service, in our ongoing efforts to improve system performance and resilience.\n\nAt 3:30 PM PST, we observed a brief, mostly imperceptible degradation and decided to roll back the change as a precaution. Due to failure in the rollback procedure, we observed a significantly reduced capacity in our middleware service that eventually led to a distributed deadlock condition between critical databases.\n\nBox has made significant investments in reliability and mitigation measures. In this case, the issue was regional in scope and cross-region recovery capabilities are still in development. We therefore completed recovery by remediating the impacted region directly rather than executing a regional failover.\n\nWe restored middleware service capacity by 5:21 PM PST, but the deadlock condition persisted. After several lower-impact attempts to dislodge the deadlock were unsuccessful, we took a broader mitigation step and throttled all traffic at 6:54 PM PST. This resulted in a 26-minute full outage, after which systems stabilized and gradually recovered, with the site returning to full functionality at 7:23 PM PST.\n\n**Corrective Actions**\n\nBox has initiated the following corrective actions:\n\n* Complete the planned capacity increase to reduce the chance of similar deadlocks and shorten recovery time if they occur\n* Strengthen rollback safeguards so changes can be safely and reliably reverted, preventing a repeat of the rollback failure that triggered this incident\n\nThank you again for being a valued Box customer. We are continuously working to improve Box and want to make sure we are delivering the best in class product and user experience. Should you have any additional questions please do not hesitate to contact us.\n\nSincerely,\n\nThe Box Team", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-16T20:31:45.457-08:00", "resolved_inferred": false, "started_at": "2025-12-16T16:57:51.000-08:00", @@ -584,7 +584,7 @@ "body": "Notice and disclaimer: Box is providing this preliminary information subject to further review and analysis. To the best of our knowledge, this is the current state and we may update as more information is confirmed.\n\nOn November 10, 2025 between 5:00 pm PST and 5:26 pm PST, some users may have experienced slowness or temporary unavailability while working in Box. The issue occurred due to a sudden, large traffic spike on one database, which caused connection saturation on other databases, making them temporarily inaccessible. The issue was automatically resolved as our middleware service detected the problem and backed off. We are working on ways to prevent sudden traffic spikes from cascading to other systems and accelerating our middleware service\u2019s auto-remediation process to prevent similar issues from occurring in the future.\n\nWe are conducting a full engineering postmortem and our overview is subject to change with further analysis and findings. In the event our continuing investigation yields further substantive findings, we may publish additional analysis after the conclusion of the full engineering postmortem.\n\nWe are continuously working to improve Box and want to make sure we are delivering the best product and user experience we can. We hope we have provided some clarity here and we would be happy to answer any questions you may still have regarding this matter.\n\nSincerely,\n\nThe Box Team", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-10T17:00:00.000-08:00", "resolved_inferred": false, "started_at": "2025-11-10T17:00:00.000-08:00", @@ -597,7 +597,7 @@ "body": "We recently addressed issues affecting downloads, preview, and Box Notes. We would like to take the opportunity to further explain these issues and the steps we have taken to keep them from happening in the future.\n\nBetween 10:07 PM PDT and 11:16 PM PDT on October 29, 2025, some users may have experienced difficulties while working in Box. During this time, users may have encountered problems downloading or previewing files and using Box Notes. The issue was caused by a disruption with one of our third-party cloud partners. We resolved the issue by restarting and scaling up the impacted backend services. In addition, we are examining how to improve our resiliency in these scenarios to prevent similar issues from occurring in the future.\n\n\u200c\n\n**Analysis** \n\nThis issue was triggered by a maintenance operation at one of our third-party cloud providers. During this operation, we encountered increased latency between several components in our US cloud regions. Because impact during this issue was limited to US cloud regions, Box Zones customers were not impacted. With the corrective actions outlined below, we strive to prevent or greatly minimize impact to customers from future similar incidents.\n\n\u200c\n\n**Corrective Actions**\n\nBox has initiated the following corrective actions:\n\n* Updated our client timeouts to be more fault-tolerant in the face of third party disruptions\n* Improved our regional resiliency through increased geo-redundancy for external dependencies\n* Updated our internal incident response processes to improve our response time\n\n\u200c\n\nWe are continuously working to improve Box and want to make sure we are delivering the best product and user experience we can. We hope we have provided some clarity here and we would be happy to answer any questions you may still have regarding this matter.\u00a0\n\nSincerely, \nThe Box Team", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-29T23:51:21.357-07:00", "resolved_inferred": false, "started_at": "2025-10-29T22:29:42.000-07:00", @@ -610,7 +610,7 @@ "body": "After further monitoring, this incident is now considered resolved. The SMS Service has been restored to full functionality. If you continue to experience any issues, please contact Box Support at https://support.box.com.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-20T03:08:40.965-07:00", "resolved_inferred": false, "started_at": "2025-10-20T02:01:18.247-07:00", @@ -623,7 +623,7 @@ "body": "We recently addressed issues affecting availability of the Box All Files page. We would like to take the opportunity to further explain these issues and the steps we have taken to keep them from happening in the future.\n\nBetween 5:42 AM PDT and 6:30 AM PDT on October 17th, some users may have experienced difficulties while working in Box. During this time, there was a degradation in availability of the All Files page. The issue occurred due to a bug in our code promotion pipeline, which promoted a disruptive change beyond the canary stage, causing wider impact. We were able to resolve the issue by rolling back the change. In addition, we are working to improve our release strategy and testing processes to prevent similar issues from occurring in the future.\u00a0\n\n\u200c\n\n**Analysis** \n\nThe code that was promoted beyond the canary stage introduced an unintended change in the behavior of our feature flagging mechanism. The code change was intended to improve application performance by implementing a filtering-based approach. However, the feature flagging system was not yet fully compatible with this implementation, which resulted in a malfunction on the All Files page.\n\n\u200c\n\n**Corrective Actions**\n\nBox has initiated the following corrective actions:\n\n* Strengthened the canary deployment validation criteria in our release strategy.\n* Updated internal documentation to reflect feature-flag system dependencies and operational constraints.\n* Provided engineers clear guidance for safely integrating changes with the feature-flag system.\n\n\u200c\n\nWe are continuously working to improve Box and want to make sure we are delivering the best product and user experience we can. We hope we have provided some clarity here and we would be happy to answer any questions you may still have regarding this matter.\u00a0\n\nSincerely, \nThe Box Team", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-17T08:07:53.740-07:00", "resolved_inferred": false, "started_at": "2025-10-17T06:36:15.736-07:00", @@ -636,7 +636,7 @@ "body": "From approximately 2:25 PM to 03:01 PM US Pacific time, we observed an issue impacting Box Preview and Shared Links. Our systems automatically detected and corrected the underlying issue. There is no current impact and no further updates will be provided here. If you continue to experience any issues, please contact Box Support at https://support.box.com.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-01T12:00:00.000-07:00", "resolved_inferred": false, "started_at": "2025-10-01T12:00:00.000-07:00", @@ -649,7 +649,7 @@ "body": "We recently addressed issues affecting Box. We would like to take the opportunity to further explain these issues and the steps we have taken to keep them from happening in the future.\n\nBetween 2:14 PM PDT and 10:12 PM PDT on September 22nd, 2025, some users may have experienced difficulties while working in Box. During this time, users may have encountered intermittent errors while using Box AI in Box Hubs. The issue occurred as a result of a code change aimed at improving the reliability of our Box AI service. We were able to resolve the issue by reverting the problematic code change. In addition, we are improving our internal testing and validation procedures to prevent similar issues from occurring in the future. \n\n**Analysis**\n\nThe code change that led to this incident unintentionally switched the underlying LLM that provides vector embeddings for Box AI in Hubs to a different model. That model did not have sufficient capacity to take production traffic and as a result, users experienced errors while interacting with Box AI in Box Hubs during this time.\n\n**Corrective Actions**\n\nBox has initiated the following corrective actions:\n\n* Improve internal testing and validation procedures for changes going to production\n* Improve observability processes for changes being deployed to production\n* Increase traffic in pre-production environments to exercise high traffic loads\n\nWe are continuously working to improve Box and want to make sure we are delivering the best product and user experience we can. We hope we have provided some clarity here and we would be happy to answer any questions you may still have regarding this matter.\u00a0\n\nSincerely, \nThe Box Team", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-22T22:31:50.409-07:00", "resolved_inferred": false, "started_at": "2025-09-22T21:41:54.231-07:00", diff --git a/api/v/brandfetch.json b/api/v/brandfetch.json index d1a3cf77290432a20a2510d25a02921d790c201f..fbc053d8ef90ff64020aee5a3b5d56fb7f2ffe65 100644 --- a/api/v/brandfetch.json +++ b/api/v/brandfetch.json @@ -3,7 +3,7 @@ "slug": "brandfetch", "platform": "betterstack", "status_url": "https://status.brandfetch.io", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": false, "first_watched": "2026-09-04T07:06:16Z", diff --git a/api/v/brave.json b/api/v/brave.json index 7650e8900d808955acc3e4a0ef237ef842ab714a..45d7a9ea05c119d89d631fa6e2c2f7551d4684d4 100644 --- a/api/v/brave.json +++ b/api/v/brave.json @@ -3,7 +3,7 @@ "slug": "brave", "platform": "betterstack", "status_url": "https://status.brave.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "major", "history_backfilled": false, "first_watched": "2026-09-04T07:06:16Z", diff --git a/api/v/breach-secure-now.json b/api/v/breach-secure-now.json index 1d800ea4ba95b4dd645a53e3ae65dcaf511544d0..94fedcf26835c9884b3d77a3c769b550414846d0 100644 --- a/api/v/breach-secure-now.json +++ b/api/v/breach-secure-now.json @@ -3,7 +3,7 @@ "slug": "breach-secure-now", "platform": "statuspage", "status_url": "https://status.breachsecurenow.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "maintenance", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-19T09:38:27.509-04:00", "resolved_inferred": false, "started_at": "2026-06-18T09:45:10.554-04:00", @@ -25,7 +25,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-16T22:35:35.842-04:00", "resolved_inferred": false, "started_at": "2026-06-16T15:47:36.323-04:00", @@ -38,7 +38,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-08T21:24:28.923-04:00", "resolved_inferred": false, "started_at": "2026-04-08T12:22:43.847-04:00", @@ -51,7 +51,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-24T18:38:23.992-04:00", "resolved_inferred": false, "started_at": "2026-03-17T13:17:40.244-04:00", @@ -64,7 +64,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-06T12:54:52.185-05:00", "resolved_inferred": false, "started_at": "2026-01-29T21:23:47.731-05:00", @@ -77,7 +77,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-08T12:20:57.415-04:00", "resolved_inferred": false, "started_at": "2026-01-22T09:55:01.000-05:00", @@ -90,7 +90,7 @@ "body": "Update: A fix has been developed and deployed to both the Microsoft Teams Application and Catch Phish. \n \nNotes: An error occurred when decoding certain security tokens from Microsoft. \n \nThank you for your patience and understanding as we resolved the issue.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-06T16:01:43.072-05:00", "resolved_inferred": false, "started_at": "2025-11-04T12:38:59.396-05:00", @@ -103,7 +103,7 @@ "body": "The outage affecting several Microsoft services has been resolved. There should be no further impact to the Breach Secure Now portal. Thank you for your patience while we monitored this issue.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-31T11:00:18.386-04:00", "resolved_inferred": false, "started_at": "2025-10-29T17:13:45.471-04:00", @@ -116,7 +116,7 @@ "body": "The AWS outage that affected the BSN portal and related services has been resolved. Thank you for your patience during this incident.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-27T09:54:26.580-04:00", "resolved_inferred": false, "started_at": "2025-10-20T10:58:17.166-04:00", @@ -129,7 +129,7 @@ "body": "The issue affecting Active Directory sync has been resolved. Thank you for your patience while we addressed this issue.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-27T13:31:49.182-04:00", "resolved_inferred": false, "started_at": "2025-10-15T14:26:27.717-04:00", @@ -142,7 +142,7 @@ "body": "The issue preventing the deletion or archiving of inactive clients has been resolved. Thank you for your patience as we addressed this matter.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-15T14:41:56.088-04:00", "resolved_inferred": false, "started_at": "2025-09-29T17:02:28.965-04:00", @@ -155,7 +155,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-20T09:25:24.808-05:00", "resolved_inferred": false, "started_at": "2025-09-25T10:09:47.280-04:00", @@ -168,7 +168,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-27T09:57:00.816-04:00", "resolved_inferred": false, "started_at": "2025-09-22T17:33:34.910-04:00", @@ -181,7 +181,7 @@ "body": "We have implemented a permanent fix that addresses the phishing campaign scheduling issue. Our Support team is following up with partners who have open tickets related to this matter and will continue monitoring phishing campaign performance to ensure stability.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-03T13:51:21.865-04:00", "resolved_inferred": false, "started_at": "2025-09-19T11:40:41.023-04:00", @@ -194,7 +194,7 @@ "body": "The issue causing simulated phishing emails to remain in queue status has been resolved. Following the deployment of a fix earlier this month, our team has confirmed that phishing emails are now being sent out as expected.\n\nSome residual configuration-related issues may still occur. If you continue to experience any problems, please open a support ticket, and our team will assist on a case-by-case basis.\n\nThank you for your patience and understanding as we resolved this matter.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-27T16:53:25.827-04:00", "resolved_inferred": false, "started_at": "2025-09-15T11:51:02.379-04:00", @@ -207,7 +207,7 @@ "body": "The issue affecting the downloading of reports and certificates has been resolved. Thank you for your patience as we addressed this matter.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-05T13:55:32.289-04:00", "resolved_inferred": false, "started_at": "2025-09-02T10:02:59.097-04:00", diff --git a/api/v/brex.json b/api/v/brex.json index decc2a22a886cdf5500b2bd51d97c192f577ce2a..60ca17a8ff0a8f1f1035378e640b039f6ffe92c8 100644 --- a/api/v/brex.json +++ b/api/v/brex.json @@ -3,7 +3,7 @@ "slug": "brex", "platform": "statuspage", "status_url": "https://status.brex.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "The Brex Trust Portal has been up and running again since 12:00pm PT.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-09-02T01:56:47.877Z", "resolved_inferred": false, "started_at": "2026-09-01T17:48:49.964Z", @@ -25,7 +25,7 @@ "body": "Mastercard Network Outage has been resolved, and transactions should now be correctly processed.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-15T05:53:45.680Z", "resolved_inferred": false, "started_at": "2026-08-15T04:49:16.691Z", @@ -38,7 +38,7 @@ "body": "We have resolved the issue.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-11T19:12:47.130Z", "resolved_inferred": false, "started_at": "2026-08-11T17:16:12.312Z", @@ -51,7 +51,7 @@ "body": "We have resolved the issue.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-04T20:34:17.807Z", "resolved_inferred": false, "started_at": "2026-08-04T16:01:35.084Z", @@ -64,7 +64,7 @@ "body": "We\u2019ve resolved the issue affecting notifications and the Tasks page. All services are operating normally.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-30T18:11:56.392Z", "resolved_inferred": false, "started_at": "2026-07-30T17:04:03.000Z", @@ -77,7 +77,7 @@ "body": "Scheduled Maintenance has been completed.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-19T07:45:48.630Z", "resolved_inferred": false, "started_at": "2026-07-19T06:32:16.184Z", @@ -90,7 +90,7 @@ "body": "Scheduled Maintenance has been completed", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-18T09:32:36.549Z", "resolved_inferred": false, "started_at": "2026-07-18T07:01:02.187Z", @@ -103,7 +103,7 @@ "body": "We have identified the root cause and resolved the issue.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-17T15:32:10.044Z", "resolved_inferred": false, "started_at": "2026-07-17T14:51:49.310Z", @@ -116,7 +116,7 @@ "body": "Maintenance is complete, Dashboard and External APIs are available.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-12T07:17:43.281Z", "resolved_inferred": false, "started_at": "2026-07-12T07:08:08.013Z", @@ -129,7 +129,7 @@ "body": "We have resolved the issue.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-03T17:02:05.548Z", "resolved_inferred": false, "started_at": "2026-07-03T16:28:28.796Z", @@ -142,7 +142,7 @@ "body": "We have resolved the issue.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-03T05:03:30.573Z", "resolved_inferred": false, "started_at": "2026-07-03T00:25:46.863Z", @@ -155,7 +155,7 @@ "body": "We have resolved the issue and transactions are now being synced correctly. In the vast majority of cases, previously missing transactions will show up automatically in the next 24 hours.\n\nIn a few rare cases, additional action may be required and we will reach out directly. If you do not see expected transactions please monitor your inbox, or reach out to our support team for further assistance.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-26T03:28:04.863Z", "resolved_inferred": false, "started_at": "2026-06-25T18:59:36.592Z", @@ -168,7 +168,7 @@ "body": "The maintenance has been confirmed to be complete. Any failed API calls can be successfully retried and users should now be able to transact and see their cards and transactions.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-14T05:29:53.745Z", "resolved_inferred": false, "started_at": "2026-06-14T05:11:33.417Z", @@ -181,7 +181,7 @@ "body": "The maintenance has been confirmed to be complete. Any failed API calls can be successfully retried and users should now be able to load the Brex Dashboard successfully.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-13T15:17:40.078Z", "resolved_inferred": false, "started_at": "2026-06-13T15:10:03.000Z", @@ -194,7 +194,7 @@ "body": "We have resolved the issue affecting the ability to book and manage trips. Users can now continue using Brex Travel.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-13T07:53:58.000Z", "resolved_inferred": false, "started_at": "2026-06-13T05:21:54.745Z", @@ -207,7 +207,7 @@ "body": "We have resolved the issue.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-04T22:01:48.327Z", "resolved_inferred": false, "started_at": "2026-06-04T21:23:41.156Z", @@ -220,7 +220,7 @@ "body": "Some Dashboard requests were blocked with a misleading error message, the issue is resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-19T00:15:16.514Z", "resolved_inferred": false, "started_at": "2026-05-19T00:15:16.458Z", @@ -233,7 +233,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-14T17:14:42.466Z", "resolved_inferred": false, "started_at": "2026-05-14T15:00:04.717Z", @@ -246,7 +246,7 @@ "body": "We see Quickbooks successfully syncing bank feeds initiated by Pro Access firms for their client's accounts.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-02T04:09:09.280Z", "resolved_inferred": false, "started_at": "2026-05-02T02:02:08.172Z", @@ -259,7 +259,7 @@ "body": "Activity logs and audit trail pages are stable.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-21T14:22:21.067Z", "resolved_inferred": false, "started_at": "2026-04-21T04:24:45.717Z", @@ -272,7 +272,7 @@ "body": "We have resolved the issue.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-03T11:20:34.363Z", "resolved_inferred": false, "started_at": "2026-04-03T10:50:07.371Z", @@ -285,7 +285,7 @@ "body": "We have seen latency stabilize.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-02T18:24:49.320Z", "resolved_inferred": false, "started_at": "2026-04-02T17:43:37.899Z", @@ -298,7 +298,7 @@ "body": "We have resolved the issue.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-02T16:02:38.936Z", "resolved_inferred": false, "started_at": "2026-04-02T15:17:48.664Z", @@ -311,7 +311,7 @@ "body": "We have resolved the issue.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-27T14:32:53.251Z", "resolved_inferred": false, "started_at": "2026-03-26T14:45:43.122Z", @@ -324,7 +324,7 @@ "body": "The issue was resolved", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-18T13:40:02.294Z", "resolved_inferred": false, "started_at": "2026-03-18T12:24:25.086Z", @@ -337,7 +337,7 @@ "body": "We have resolved the issue.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-12T03:09:03.426Z", "resolved_inferred": false, "started_at": "2026-03-12T02:42:14.773Z", @@ -350,7 +350,7 @@ "body": "We have resolved the issue.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-08T15:42:33.515Z", "resolved_inferred": false, "started_at": "2026-03-08T14:48:57.042Z", @@ -363,7 +363,7 @@ "body": "This is now resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-04T19:48:45.327Z", "resolved_inferred": false, "started_at": "2026-03-04T19:38:59.595Z", @@ -376,7 +376,7 @@ "body": "We have resolved the issue.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-04T00:35:18.069Z", "resolved_inferred": false, "started_at": "2026-03-03T22:14:59.404Z", @@ -389,7 +389,7 @@ "body": "We have resolved the issue.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-24T21:16:24.121Z", "resolved_inferred": false, "started_at": "2026-02-24T20:21:41.753Z", @@ -402,7 +402,7 @@ "body": "We have resolved the issue.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-27T17:18:09.635Z", "resolved_inferred": false, "started_at": "2026-01-27T17:10:18.559Z", @@ -415,7 +415,7 @@ "body": "Emails going to Microsoft-based addresses should now be received in a timely mannner", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-23T16:13:41.115Z", "resolved_inferred": false, "started_at": "2026-01-22T22:36:13.818Z", @@ -428,7 +428,7 @@ "body": "We have resolved the issue.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-09T20:48:07.049Z", "resolved_inferred": false, "started_at": "2026-01-09T19:43:45.598Z", @@ -441,7 +441,7 @@ "body": "Maintenance is now complete, and all systems are back online.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-23T10:18:10.000Z", "resolved_inferred": false, "started_at": "2025-11-23T09:35:43.000Z", @@ -454,7 +454,7 @@ "body": "We experienced an outage affecting chat support, receipt processing and address verification due to an outage by one of our partners, Cloudflare. This has now been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-18T17:53:56.818Z", "resolved_inferred": false, "started_at": "2025-11-18T16:17:47.777Z", @@ -467,7 +467,7 @@ "body": "We experienced an outage affecting chat support, receipt processing and address verification due to an outage by one of our partners, Cloudflare. This is now resolved, and our team is monitoring to ensure normal operations.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-18T16:30:26.000Z", "resolved_inferred": false, "started_at": "2025-11-18T13:17:55.659Z", @@ -480,7 +480,7 @@ "body": "The issue when sending money or paying a bill via international wire in non-USD currencies has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-01T22:03:27.177Z", "resolved_inferred": false, "started_at": "2025-11-01T20:06:31.542Z", @@ -493,7 +493,7 @@ "body": "We have resolved the issue.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-07T23:39:50.040Z", "resolved_inferred": false, "started_at": "2025-10-07T23:12:54.609Z", @@ -506,7 +506,7 @@ "body": "This issue is now fully resolved", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-03T20:38:32.259Z", "resolved_inferred": false, "started_at": "2025-10-03T14:52:12.599Z", @@ -519,7 +519,7 @@ "body": "We have resolved the issue.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-29T11:55:34.112Z", "resolved_inferred": false, "started_at": "2025-09-29T11:47:24.831Z", @@ -532,7 +532,7 @@ "body": "We have resolved the issue. We will continue monitoring for stability.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-26T14:23:06.814Z", "resolved_inferred": false, "started_at": "2025-09-26T13:48:12.743Z", @@ -545,7 +545,7 @@ "body": "Transactions retrieved by calling the list expenses API endpoint (https://developer.brex.com/openapi/expenses_api/#operation/listExpenses) between 1:30pm PT on September 18 and 5:30pm PT on September 22 may have contained incorrect expense data. This issue caused certain transactions to be assigned to the wrong users or to have incorrect merchant information.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-18T20:30:00.000Z", "resolved_inferred": false, "started_at": "2025-09-18T20:30:00.000Z", @@ -558,7 +558,7 @@ "body": "Google has resolved the issue: https://www.google.com/appsstatus/dashboard/incidents/7Bgq1PUK83NuVZHMZXWd", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-18T16:08:03.839Z", "resolved_inferred": false, "started_at": "2025-09-18T15:55:15.141Z", @@ -571,7 +571,7 @@ "body": "We have resolved the issue.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-16T23:20:29.497Z", "resolved_inferred": false, "started_at": "2025-09-16T17:03:28.333Z", @@ -584,7 +584,7 @@ "body": "We have resolved the issue.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-04T06:08:34.806Z", "resolved_inferred": false, "started_at": "2025-09-03T22:36:15.325Z", @@ -597,7 +597,7 @@ "body": "We have resolved the issue.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-03T15:54:37.402Z", "resolved_inferred": false, "started_at": "2025-09-03T15:25:45.629Z", @@ -610,7 +610,7 @@ "body": "We've resolved the issue and all affected functionality has been restored.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-27T16:04:23.303Z", "resolved_inferred": false, "started_at": "2025-08-27T14:39:27.045Z", @@ -623,7 +623,7 @@ "body": "This issue is now resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-27T02:26:47.338Z", "resolved_inferred": false, "started_at": "2025-08-27T02:23:52.744Z", @@ -636,7 +636,7 @@ "body": "Functionality has been restored.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-26T00:59:15.780Z", "resolved_inferred": false, "started_at": "2025-08-25T22:53:00.807Z", @@ -649,7 +649,7 @@ "body": "We are seeing the Dashboard and API latency go back to normal now.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-07T01:42:35.928Z", "resolved_inferred": false, "started_at": "2025-08-07T01:12:22.087Z", diff --git a/api/v/brightly-software.json b/api/v/brightly-software.json index b2eb065204fcffbd8b85b1dc0903148661fbad2c..d849edc79c295c3ee4d43b3ebf6e6902c4d8a6d4 100644 --- a/api/v/brightly-software.json +++ b/api/v/brightly-software.json @@ -3,7 +3,7 @@ "slug": "brightly-software", "platform": "statuspage", "status_url": "https://status.brightlysoftware.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "This issue has been resolved. Thank you for your patience. Please contact ams-assetessentials-support.si@siemens.com if you have any questions.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-28T17:09:01.181-04:00", "resolved_inferred": false, "started_at": "2026-08-28T10:23:35.314-04:00", @@ -25,7 +25,7 @@ "body": "This issue has been resolved. Thank you for your patience. Please contact ams-confirm-support.si@siemens.com if you have any questions.\n\nThis update was posted at 17:53 BST on 26 August 2026.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-26T12:53:33.000-04:00", "resolved_inferred": false, "started_at": "2026-08-26T08:52:57.216-04:00", @@ -38,7 +38,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-20T09:52:53.214-04:00", "resolved_inferred": false, "started_at": "2026-08-20T08:12:43.198-04:00", @@ -51,7 +51,7 @@ "body": "Our team has implemented a fix for this issue. The services are restored and working properly. We will continue to monitor all systems. Thank you for your patience! Please contact ams-events-support.si@siemens.com if you have any questions.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "started_at": "2026-08-11T09:58:31.569-04:00", "state": "monitoring", "title": "Event Manager \u2013 Intermittent Latency During Navigation", @@ -62,7 +62,7 @@ "body": "This issue has been resolved. Thank you for your patience. Please contact ams-assetessentials-support.si@siemens.com if you have any questions.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-20T12:58:44.985-04:00", "resolved_inferred": false, "started_at": "2026-07-20T11:55:55.000-04:00", @@ -75,7 +75,7 @@ "body": "We are continuing to investigate an issue that is preventing Canadian clients from accessing TheWorxHub using 'clientname.theworxhub.ca' URLs. \n \nAt this time, we cannot confirm whether the previous URL will be restored, so users should use the currently supported URL going forward to ensure uninterrupted access: 'clientname.theworxhub.com'\n \nWe recommend updating any bookmarks, shortcuts, or saved links to the supported URL above. We sincerely apologize for the inconvenience and understand how important consistent access is for your teams. We are taking this seriously and are strengthening our internal domain management processes to help prevent similar issues going forward.\nWe will share additional updates as we have more information. Please contact ams-support.si@siemens.com if you have any questions\"", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "started_at": "2026-07-06T16:09:21.706-04:00", "state": "investigating", "title": "TheWorxHub - Access Issue for Canadian clients", @@ -86,7 +86,7 @@ "body": "We have resolved the issue that was causing users to receive a certificate-based authentication error when logging in to Confirm Enterprise. The resolution has been validated with affected clients, and services are now operating as expected.\n\nWe apologise for any inconvenience or disruption this issue may have caused and thank you for your patience while we worked to restore normal service.\n\nUpdate: 3 Jul 2026 17:34 BST", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-03T12:35:44.225-04:00", "resolved_inferred": false, "started_at": "2026-07-03T10:17:10.000-04:00", @@ -99,7 +99,7 @@ "body": "This issue has been resolved and support channels are operational. Thank you for your patience. Please contact support@brightlysoftware.com if you have any questions.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-26T20:51:53.248-04:00", "resolved_inferred": false, "started_at": "2026-06-26T17:16:14.495-04:00", @@ -112,7 +112,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-06T16:29:43.963-04:00", "resolved_inferred": false, "started_at": "2026-06-19T11:34:54.772-04:00", @@ -125,7 +125,7 @@ "body": "This issue has been resolved. Thank you for your patience. Please contact events.support@brightlysoftware.com if you have any questions.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-17T12:29:50.752-04:00", "resolved_inferred": false, "started_at": "2026-06-17T09:10:18.525-04:00", @@ -138,7 +138,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-25T12:12:08.537-04:00", "resolved_inferred": false, "started_at": "2026-06-16T10:55:25.630-04:00", @@ -151,7 +151,7 @@ "body": "The data syncing issue has been resolved, and syncing is now in progress. Please note it may take up to two hours for all data to be fully updated in Data Share and Analytics. Please contact assetessentialshelp@brightlysoftware.com if you have any questions.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-15T16:32:55.890-04:00", "resolved_inferred": false, "started_at": "2026-06-15T14:29:48.125-04:00", @@ -164,7 +164,7 @@ "body": "This issue has been resolved. Thank you for your patience. Please contact assetessentialshelp@brightlysoftware.com if you have any questions.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-09T09:30:40.124-04:00", "resolved_inferred": false, "started_at": "2026-06-08T07:31:46.563-04:00", @@ -177,7 +177,7 @@ "body": "Our engineers have been monitoring the application. The issue is now resolved. Thank you for your patience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-07T14:25:07.501-04:00", "resolved_inferred": false, "started_at": "2026-05-07T08:29:18.289-04:00", @@ -190,7 +190,7 @@ "body": "This issue has been resolved. Thank you for your patience. Please contact support@brightlysoftware.com if you have any questions.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-14T09:37:11.606-04:00", "resolved_inferred": false, "started_at": "2026-04-10T09:16:08.593-04:00", @@ -203,7 +203,7 @@ "body": "This issue has been resolved. Thank you for your patience. Please contact support@brightlysoftware.com if you have any questions.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-13T11:33:59.502-04:00", "resolved_inferred": false, "started_at": "2026-04-09T09:52:37.968-04:00", @@ -216,7 +216,7 @@ "body": "This issue has been resolved. Thank you for your patience. Please contact events.support@brightlysoftware.com if you have any questions.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-02T18:12:36.783-04:00", "resolved_inferred": false, "started_at": "2026-04-01T17:05:25.356-04:00", @@ -229,7 +229,7 @@ "body": "This issue has been resolved. Thank you for your patience. Please contact events.support@brightlysoftware.com if you have any questions.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-27T08:51:45.719-04:00", "resolved_inferred": false, "started_at": "2026-03-26T10:29:46.483-04:00", @@ -242,7 +242,7 @@ "body": "We have resolved the problem where users get a certificate-based authentication error when logging in to Confirm Enterprise. \nWe apologise for the disruption it caused. Please contact confirm.support@brightlysoftware.com if you have any questions.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-25T12:43:08.313-04:00", "resolved_inferred": false, "started_at": "2026-03-25T10:28:14.548-04:00", @@ -255,7 +255,7 @@ "body": "Our team has implemented a fix for this issue. The services are restored and working properly. We will continue to monitor all systems. Thank you for your patience!", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-25T09:33:35.162-04:00", "resolved_inferred": false, "started_at": "2026-03-24T10:50:49.122-04:00", @@ -268,7 +268,7 @@ "body": "This issue has been resolved. Thank you for your patience. Please contact support@brightlysoftware.com if you have any questions.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-23T14:26:36.421-04:00", "resolved_inferred": false, "started_at": "2026-03-23T11:16:44.390-04:00", @@ -281,7 +281,7 @@ "body": "This issue has been resolved. Thank you for your patience. Please contact our Support Team at support@brightlysoftware.com with any questions.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-17T12:42:47.516-04:00", "resolved_inferred": false, "started_at": "2026-03-17T10:58:13.349-04:00", @@ -294,7 +294,7 @@ "body": "This issue has been resolved. Thank you for your patience. Please contact our Support Team at assetessentialshelp@brightlysoftware.com with any questions.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-17T12:43:27.182-04:00", "resolved_inferred": false, "started_at": "2026-03-17T09:48:04.600-04:00", @@ -307,7 +307,7 @@ "body": "This issue has been resolved. Thank you for your patience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-17T12:44:17.581-04:00", "resolved_inferred": false, "started_at": "2026-03-09T08:42:39.568-04:00", @@ -320,7 +320,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-11T12:52:58.236-04:00", "resolved_inferred": false, "started_at": "2026-03-05T09:16:14.293-05:00", @@ -333,7 +333,7 @@ "body": "This issue has been resolved. Thank you for your patience!", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-16T10:41:41.644-05:00", "resolved_inferred": false, "started_at": "2026-02-11T14:08:14.160-05:00", @@ -346,7 +346,7 @@ "body": "We have resolved the issue with users not being able to access MySchoolBuilding. If you are still experiencing this issue, please clear your browser's cache and try again by going to https://login.myschoolbuilding.com/msb or https://www.myschoolbuilding.com/msb. While the change is in place, DNS updates can take some time to fully propagate. Because of this, you may continue to see the issue for a short period. If you need further assistance please contact support@brightlysoftware.com. Thank you for your patience while we worked to resolve this issue.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-11T12:19:36.816-05:00", "resolved_inferred": false, "started_at": "2026-02-11T08:32:53.000-05:00", @@ -359,7 +359,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-03T13:31:09.808-05:00", "resolved_inferred": false, "started_at": "2026-02-03T12:44:12.449-05:00", @@ -372,7 +372,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-20T16:14:59.265-05:00", "resolved_inferred": false, "started_at": "2026-01-20T14:28:47.510-05:00", @@ -385,7 +385,7 @@ "body": "Our engineers have been monitoring the application. The latency issue has been resolved. Thank you for your patience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-08T15:05:04.632-05:00", "resolved_inferred": false, "started_at": "2026-01-08T08:29:15.155-05:00", @@ -398,7 +398,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-21T09:32:43.679-05:00", "resolved_inferred": false, "started_at": "2025-11-20T11:15:14.497-05:00", @@ -411,7 +411,7 @@ "body": "This issue has been resolved. If further assistance is needed please reach out to Brightly Support: support@brightlysoftware.com", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-21T08:15:57.952-04:00", "resolved_inferred": false, "started_at": "2025-10-20T08:12:48.000-04:00", @@ -424,7 +424,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-07T08:26:20.360-04:00", "resolved_inferred": false, "started_at": "2025-10-03T13:59:16.283-04:00", @@ -437,7 +437,7 @@ "body": "This issue has been resolved. If further assistance is needed please reach out to Brightly Support: support@brightlysoftware.com", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-02T14:48:07.496-04:00", "resolved_inferred": false, "started_at": "2025-10-01T08:33:24.889-04:00", @@ -450,7 +450,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-24T17:01:06.980-04:00", "resolved_inferred": false, "started_at": "2025-09-24T14:59:42.708-04:00", @@ -463,7 +463,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-20T13:18:04.303-04:00", "resolved_inferred": false, "started_at": "2025-09-19T17:09:54.665-04:00", @@ -476,7 +476,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-16T16:30:12.037-04:00", "resolved_inferred": false, "started_at": "2025-09-16T16:11:31.452-04:00", @@ -489,7 +489,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-15T09:08:05.086-04:00", "resolved_inferred": false, "started_at": "2025-08-14T11:37:24.420-04:00", @@ -502,7 +502,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-11T09:59:33.893-04:00", "resolved_inferred": false, "started_at": "2025-08-01T12:19:41.320-04:00", @@ -515,7 +515,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-11T10:00:00.854-04:00", "resolved_inferred": false, "started_at": "2025-08-01T12:04:56.228-04:00", @@ -528,7 +528,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-11T09:59:06.509-04:00", "resolved_inferred": false, "started_at": "2025-08-01T09:15:09.760-04:00", diff --git a/api/v/brivo.json b/api/v/brivo.json index 1aba741ff640f44930b4f89b7a9ed3429ead9a3d..03bbb6dfd7d55ed1038c3674f21748a26a4c3434 100644 --- a/api/v/brivo.json +++ b/api/v/brivo.json @@ -3,7 +3,7 @@ "slug": "brivo", "platform": "statuspage", "status_url": "https://status.brivo.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "This was a brief interruption that has since recovered. Service is operating normally.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-24T19:10:46.134-04:00", "resolved_inferred": false, "started_at": "2026-08-24T18:52:38.360-04:00", @@ -25,7 +25,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-24T12:28:36.784-04:00", "resolved_inferred": false, "started_at": "2026-08-24T11:44:38.365-04:00", @@ -38,7 +38,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-22T12:03:30.000-04:00", "resolved_inferred": false, "started_at": "2026-08-22T09:56:39.206-04:00", @@ -51,7 +51,7 @@ "body": "Normal operations have been restored for the Brivo API. Recently, an update was made that caused the API to return 400 Bad Request errors for requests containing extra, unsupported query parameters. We have rolled back to ensure your previously successful requests continue to work as expected. Incident occurred from 3:30AM ET to 5:20PM ET.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-15T03:30:00.000-04:00", "resolved_inferred": false, "started_at": "2026-07-15T03:30:00.000-04:00", @@ -64,7 +64,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-01T15:41:46.653-04:00", "resolved_inferred": false, "started_at": "2026-06-01T14:24:02.981-04:00", @@ -77,7 +77,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-29T19:17:56.522-04:00", "resolved_inferred": false, "started_at": "2026-05-29T11:37:23.122-04:00", @@ -90,7 +90,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-21T11:25:49.478-04:00", "resolved_inferred": false, "started_at": "2026-05-20T16:30:21.000-04:00", @@ -103,7 +103,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-14T14:03:39.800-04:00", "resolved_inferred": false, "started_at": "2026-05-14T12:38:33.229-04:00", @@ -116,7 +116,7 @@ "body": "This is a configuration issue", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-13T17:08:28.820-04:00", "resolved_inferred": false, "started_at": "2026-05-13T16:54:00.659-04:00", @@ -129,7 +129,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-01T18:40:43.431-04:00", "resolved_inferred": false, "started_at": "2026-05-01T13:28:18.198-04:00", @@ -142,7 +142,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-23T20:25:12.151-04:00", "resolved_inferred": false, "started_at": "2026-04-23T20:04:53.512-04:00", @@ -155,7 +155,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-17T02:11:16.912-04:00", "resolved_inferred": false, "started_at": "2026-04-17T01:35:55.545-04:00", @@ -168,7 +168,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-14T14:37:27.721-04:00", "resolved_inferred": false, "started_at": "2026-04-14T13:42:18.306-04:00", @@ -181,7 +181,7 @@ "body": "This incident has been resolved", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-23T10:47:09.158-04:00", "resolved_inferred": false, "started_at": "2026-03-23T09:24:42.171-04:00", @@ -194,7 +194,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-11T07:18:14.964-04:00", "resolved_inferred": false, "started_at": "2026-03-11T05:29:12.720-04:00", @@ -207,7 +207,7 @@ "body": "This incident has been resolved", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-09T19:26:50.554-04:00", "resolved_inferred": false, "started_at": "2026-03-09T14:09:55.179-04:00", @@ -220,7 +220,7 @@ "body": "From 11:03AM to 12:57PM, Administrators with custom roles were unable to use Brivo Access.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-04T11:00:00.000-05:00", "resolved_inferred": false, "started_at": "2026-03-04T11:00:00.000-05:00", @@ -233,7 +233,7 @@ "body": "All toll-free numbers have been restored and are once again available to customers and resellers. Thank you for your patience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-03T17:22:36.727-05:00", "resolved_inferred": false, "started_at": "2026-03-03T14:39:53.613-05:00", @@ -246,7 +246,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-18T09:26:51.037-05:00", "resolved_inferred": false, "started_at": "2026-02-18T06:30:20.000-05:00", @@ -259,7 +259,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-21T09:06:03.170-05:00", "resolved_inferred": false, "started_at": "2026-01-21T02:44:26.158-05:00", @@ -272,7 +272,7 @@ "body": "The Brivo API, Integrations, and Mobile Applications are currently performing normally.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-12T18:35:17.038-05:00", "resolved_inferred": false, "started_at": "2026-01-12T12:28:19.495-05:00", @@ -285,7 +285,7 @@ "body": "We resolved an issue with being able to add Brivo Wallet Passes.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-13T08:22:00.000-05:00", "resolved_inferred": false, "started_at": "2026-01-12T08:30:00.000-05:00", @@ -298,7 +298,7 @@ "body": "Events and panel commands are processing normally.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-05T14:30:02.895-05:00", "resolved_inferred": false, "started_at": "2026-01-05T12:57:50.613-05:00", @@ -311,7 +311,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-20T09:09:15.990-05:00", "resolved_inferred": false, "started_at": "2025-11-20T08:27:17.803-05:00", @@ -324,7 +324,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-04T21:12:47.403-05:00", "resolved_inferred": false, "started_at": "2025-11-04T08:49:06.382-05:00", @@ -337,7 +337,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-29T12:30:59.058-04:00", "resolved_inferred": false, "started_at": "2025-10-29T10:25:14.934-04:00", @@ -350,7 +350,7 @@ "body": "All systems are fully operational and latencies are back to normal.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-21T05:22:26.248-04:00", "resolved_inferred": false, "started_at": "2025-10-20T05:53:50.000-04:00", @@ -363,7 +363,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-20T00:55:29.572-04:00", "resolved_inferred": false, "started_at": "2025-10-20T00:14:18.074-04:00", @@ -376,7 +376,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-23T14:13:42.029-04:00", "resolved_inferred": false, "started_at": "2025-09-23T09:20:29.076-04:00", @@ -389,7 +389,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-06T08:10:05.545-04:00", "resolved_inferred": false, "started_at": "2025-08-06T06:36:33.908-04:00", @@ -402,7 +402,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-04T20:22:18.521-04:00", "resolved_inferred": false, "started_at": "2025-08-04T15:27:11.860-04:00", diff --git a/api/v/bugcrowd.json b/api/v/bugcrowd.json index 7ef9d16d3132b8a62e3f67c91bf98a9b33aec48e..215c2607d1dd432c8901edc3b0966f0412dc88c1 100644 --- a/api/v/bugcrowd.json +++ b/api/v/bugcrowd.json @@ -3,7 +3,7 @@ "slug": "bugcrowd", "platform": "statuspage", "status_url": "https://www.bugcrowdstatus.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-25T21:33:14.766-08:00", "resolved_inferred": false, "started_at": "2026-02-25T21:08:26.660-08:00", @@ -25,7 +25,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-21T17:50:48.753-07:00", "resolved_inferred": false, "started_at": "2025-10-21T17:14:38.322-07:00", diff --git a/api/v/bugsnag.json b/api/v/bugsnag.json index aa25918fbc623ada0fb5de284cff6c9ba5011624..15d58c9f1fc887085665f037de88810b4af69297 100644 --- a/api/v/bugsnag.json +++ b/api/v/bugsnag.json @@ -3,7 +3,7 @@ "slug": "bugsnag", "platform": "statuspage", "status_url": "https://status.bugsnag.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-20T19:57:07.320Z", "resolved_inferred": false, "started_at": "2026-08-20T17:36:30.110Z", @@ -25,7 +25,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-22T18:10:21.872Z", "resolved_inferred": false, "started_at": "2026-01-22T16:54:36.724Z", @@ -38,7 +38,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-18T17:43:39.568Z", "resolved_inferred": false, "started_at": "2025-11-18T14:40:48.000Z", @@ -51,7 +51,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-11T09:26:36.524Z", "resolved_inferred": false, "started_at": "2025-11-11T08:49:56.754Z", @@ -64,7 +64,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-10T11:39:56.064Z", "resolved_inferred": false, "started_at": "2025-11-10T11:33:56.830Z", @@ -77,7 +77,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-07T09:33:09.972Z", "resolved_inferred": false, "started_at": "2025-11-07T02:59:11.650Z", @@ -90,7 +90,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-20T10:59:40.928Z", "resolved_inferred": false, "started_at": "2025-10-20T10:11:12.994Z", diff --git a/api/v/bunny.json b/api/v/bunny.json index 43801722e3828d7057c71682d9295d0f9592197e..4eae3c5bdbcabcd36b5d45cd0d8b81ce28ee3a94 100644 --- a/api/v/bunny.json +++ b/api/v/bunny.json @@ -3,7 +3,7 @@ "slug": "bunny", "platform": "statuspage", "status_url": "https://status.bunny.net", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "This issue is now fully resolved. Our Engineering team have identified additional guardrails to prevent this specific issue from happening in future.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-09-03T15:38:59.098Z", "resolved_inferred": false, "started_at": "2026-09-03T13:47:32.763Z", @@ -25,7 +25,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-09-03T13:11:17.317Z", "resolved_inferred": false, "started_at": "2026-09-03T08:53:40.424Z", @@ -38,7 +38,7 @@ "body": "A wider network incident in Los Angeles impacted Bunny Services hosted in the region. Affected network providers have mitigated the incident and all impacted services have remained stable since then.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-09-02T15:51:16.785Z", "resolved_inferred": false, "started_at": "2026-09-02T14:38:50.966Z", @@ -51,7 +51,7 @@ "body": "After monitoring the affected services, we have confirmed that Database management and idle Database activation are operating normally.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-25T22:31:25.673Z", "resolved_inferred": false, "started_at": "2026-08-25T14:06:59.791Z", @@ -64,7 +64,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-18T04:29:22.430Z", "resolved_inferred": false, "started_at": "2026-08-18T02:28:30.685Z", @@ -77,7 +77,7 @@ "body": "We have identified a process on a single server causing Basic DRM transformation failures, and was the cause of intermittent video freezes/500s. This has been rectified by the Engineering team.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-23T09:02:02.784Z", "resolved_inferred": false, "started_at": "2026-07-23T08:33:33.296Z", @@ -90,7 +90,7 @@ "body": "The login issue has now been resolved following a fix deployed by our Frontend team.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-17T11:11:48.625Z", "resolved_inferred": false, "started_at": "2026-07-17T10:57:20.256Z", @@ -103,7 +103,7 @@ "body": "We identified an failing database process on the Storage layer, which has now been resolved by our Engineering team.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-01T09:53:06.030Z", "resolved_inferred": false, "started_at": "2026-07-01T09:45:49.834Z", @@ -116,7 +116,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-27T20:11:46.172Z", "resolved_inferred": false, "started_at": "2026-06-27T18:57:37.020Z", @@ -129,7 +129,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-26T14:57:20.577Z", "resolved_inferred": false, "started_at": "2026-06-26T14:21:45.549Z", @@ -142,7 +142,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-24T03:11:23.808Z", "resolved_inferred": false, "started_at": "2026-06-23T13:22:21.323Z", @@ -155,7 +155,7 @@ "body": "As per Lets Encrypt status page, this has been resolved - we similarly have observed no degradation/failures on certificate renewals since their update went out.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-19T09:37:04.033Z", "resolved_inferred": false, "started_at": "2026-06-18T20:57:55.439Z", @@ -168,7 +168,7 @@ "body": "All pending configuration changes have propagated across the CDN.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-15T21:24:25.923Z", "resolved_inferred": false, "started_at": "2026-06-15T20:25:15.761Z", @@ -181,7 +181,7 @@ "body": "We no longer see delays stemming from Lets Encrypt and the issue is considered resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-03T12:38:39.861Z", "resolved_inferred": false, "started_at": "2026-06-03T09:02:51.635Z", @@ -194,7 +194,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-01T20:17:27.804Z", "resolved_inferred": false, "started_at": "2026-06-01T16:19:11.647Z", @@ -207,7 +207,7 @@ "body": "Processing Delays and Intermittent Timeouts for Magic Containers\n\nOn June 1, Magic Containers experienced degraded service for approximately one hour due to a network connectivity issue in our hosting provider's environment. Customers running workloads may have seen increased processing delays, intermittent timeouts, temporary disruption, or reduced availability as some workloads were automatically rescheduled. The issue was resolved after the underlying network conditions stabilized, allowing scheduling activity to resume normally.\n\nWe are improving the resilience of Magic Containers so degraded connectivity can be detected and handled more effectively, not only complete outages. We are also adding safeguards to reduce unnecessary or duplicate workload rescheduling during degraded conditions, helping limit customer impact if similar infrastructure issues occur again.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-01T20:18:45.367Z", "resolved_inferred": false, "started_at": "2026-06-01T16:02:40.911Z", @@ -220,7 +220,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-01T10:38:30.234Z", "resolved_inferred": false, "started_at": "2026-06-01T07:24:16.088Z", @@ -233,7 +233,7 @@ "body": "The fix has been deployed to all nodes. We will be readding the missing nodes to the pool today.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-27T11:15:42.030Z", "resolved_inferred": false, "started_at": "2026-05-26T06:47:26.330Z", @@ -246,7 +246,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-23T13:52:51.428Z", "resolved_inferred": false, "started_at": "2026-05-22T11:19:46.636Z", @@ -259,7 +259,7 @@ "body": "An internal process failure related to the management of our bunny.net domain with one of our domain registrars led to the temporary suspension of the domain, causing multiple services under bunny.net to become unavailable.\n\nAfter identifying and confirming the issue, we worked with the registrar to restore the domain and all affected services are now recovering as DNS changes propagate globally. We have identified the root cause internally and are implementing additional safeguards and escalation procedures to ensure this cannot happen again.\n\nDuring the outage, products and services under bunny.net experienced varying levels of disruption depending on DNS propagation and their dependency on bunny.net infrastructure and Bunny DNS.\n\nServices including the Website, Dashboard, API, DNS, and related tools experienced widespread availability issues. Other products such as Stream and Magic Containers saw limited disruption and remained largely operational for most users, though some functionality was impacted depending on DNS resolution and service dependencies. Core services such as CDN delivery and Storage remained operational throughout the incident.\n\nWe will publish a full public RCA once the incident is fully resolved, including additional details around the timeline, service impact, root cause, and the preventative measures being implemented.\n\nWe're deeply sorry for the disruption and inconvenience caused. We expect the situation to fully resolve over the next few hours as DNS propagation completes worldwide. If you have any questions, please contact support@bunny.net.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-21T18:21:00.494Z", "resolved_inferred": false, "started_at": "2026-05-21T16:39:41.814Z", @@ -272,7 +272,7 @@ "body": "This incident has now been cleared.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-14T15:41:18.237Z", "resolved_inferred": false, "started_at": "2026-05-14T14:23:38.613Z", @@ -285,7 +285,7 @@ "body": "The configuration delay has now been resolved. At around 00:15, we observed a large scale domain sync that caused configuration delays. This was resolved at 06:00 UTC, before the backlog of configuration changes were cleared by 09:30 UTC. Our Engineering team have identified the core issue and will take action to prevent future recurrence of the problem.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-01T11:12:13.562Z", "resolved_inferred": false, "started_at": "2026-05-01T03:51:45.518Z", @@ -298,7 +298,7 @@ "body": "We identified and resolved an issue that could cause endpoint updates to experience delayed propagation after CDN services had been running for an extended period of time. The issue was related to endpoint synchronization between Magic Containers and the CDN routing component, where slower processing connected to sticky session invalidation could result in stale endpoint data remaining in use longer than expected.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-26T08:23:56.155Z", "resolved_inferred": false, "started_at": "2026-04-30T10:12:55.000Z", @@ -311,7 +311,7 @@ "body": "Our Engineering team identified an overloaded process with on our statistics endpoint. This was rectified and monitored, and the issue has now been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-30T21:51:32.891Z", "resolved_inferred": false, "started_at": "2026-03-30T09:05:20.000Z", @@ -324,7 +324,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-26T19:21:59.164Z", "resolved_inferred": false, "started_at": "2026-03-26T16:16:01.196Z", @@ -337,7 +337,7 @@ "body": "We have expanded our transcoding capacity, transcoding delays have now cleared, and processing has normalized.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-27T09:00:31.746Z", "resolved_inferred": false, "started_at": "2026-03-23T19:50:09.000Z", @@ -350,7 +350,7 @@ "body": "Our Containers team found that a recent deployment had resulted in an unintended CPU throttling on new pod or app deployments. This has now been resolved, and the team has made mitigating changes to ensure this does not resurface.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-19T15:05:44.585Z", "resolved_inferred": false, "started_at": "2026-03-19T11:41:22.160Z", @@ -363,7 +363,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-06T04:43:15.087Z", "resolved_inferred": false, "started_at": "2026-03-05T15:29:42.887Z", @@ -376,7 +376,7 @@ "body": "Migration to our new Logging Platform is now complete, and near real-time logs should be visible again.\n\nUnfortunately, we had to accelerate the migration timeline as our legacy platform began struggling much sooner than expected. Because of this, we made the difficult decision to complete the migration before fully backfilling the expected 3 days of retained logging history.\n\nAt the moment, approximately 1.5 days of logs are available on the new platform. This will gradually increase and return to the full 3-day retention by Friday.\n\nThe raw, unprocessed logs remain stored on the legacy logging platform. If you require access to these logs and have a valid justification, please submit a support ticket, and we will do our best to recover them on a case-by-case basis.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-04T14:32:33.754Z", "resolved_inferred": false, "started_at": "2026-03-03T10:12:06.774Z", @@ -389,7 +389,7 @@ "body": "This issue is now resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-02T11:21:42.137Z", "resolved_inferred": false, "started_at": "2026-03-02T09:18:07.443Z", @@ -402,7 +402,7 @@ "body": "The issue affecting one server in our German storage array has been fully resolved. All services are now operating normally. We will continue monitoring to ensure stability.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-22T19:11:00.950Z", "resolved_inferred": false, "started_at": "2026-02-20T16:13:29.902Z", @@ -415,7 +415,7 @@ "body": "This is now fully resolved and the zone updates are publishing as normal.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-11T22:32:07.351Z", "resolved_inferred": false, "started_at": "2026-02-11T13:53:57.794Z", @@ -428,7 +428,7 @@ "body": "Our API team identified root cause and performed a deployment change on our network to resolve the issue.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-06T14:10:43.436Z", "resolved_inferred": false, "started_at": "2026-02-06T14:02:35.354Z", @@ -441,7 +441,7 @@ "body": "The configuration delay has now been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-06T14:01:38.343Z", "resolved_inferred": false, "started_at": "2026-02-06T09:56:23.917Z", @@ -454,7 +454,7 @@ "body": "A fix has now been applied and near real-time log delivery has now been restored. There is separately a backlog of requests that is being processed (but does not affect current real-time logs delivered).", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-04T12:37:52.901Z", "resolved_inferred": false, "started_at": "2026-02-04T10:58:30.226Z", @@ -467,7 +467,7 @@ "body": "This was caused by an upstream network provider experiencing a network outage. While CDN traffic was not affected, supporting services such as Stream, Storage and our Core API may have been intermittently returning timeout errors. This has now been rectified and plans are in motion to further build redundancy into these products.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-29T00:35:04.641Z", "resolved_inferred": false, "started_at": "2026-01-28T23:39:47.000Z", @@ -480,7 +480,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-15T22:58:44.556Z", "resolved_inferred": false, "started_at": "2026-01-15T22:28:10.277Z", @@ -493,7 +493,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-06T07:51:52.562Z", "resolved_inferred": false, "started_at": "2026-01-05T12:00:30.698Z", @@ -506,7 +506,7 @@ "body": "A transient networking issue was addressed, and the issue is now resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-11T09:02:51.920Z", "resolved_inferred": false, "started_at": "2025-12-11T08:56:10.057Z", @@ -519,7 +519,7 @@ "body": "The incident appears to be resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-05T09:29:20.000Z", "resolved_inferred": false, "started_at": "2025-12-05T09:01:07.000Z", @@ -532,7 +532,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-02T08:45:50.114Z", "resolved_inferred": false, "started_at": "2025-12-01T14:56:45.000Z", @@ -545,7 +545,7 @@ "body": "This incident has now been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-28T17:24:17.618Z", "resolved_inferred": false, "started_at": "2025-11-28T13:31:48.167Z", @@ -558,7 +558,7 @@ "body": "This issue has now been fully resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-27T10:01:01.147Z", "resolved_inferred": false, "started_at": "2025-11-23T22:23:06.000Z", @@ -571,7 +571,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-18T14:46:02.634Z", "resolved_inferred": false, "started_at": "2025-11-18T12:12:48.310Z", @@ -584,7 +584,7 @@ "body": "This incident has now been resolved", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-07T15:21:25.097Z", "resolved_inferred": false, "started_at": "2025-11-07T12:02:26.295Z", @@ -597,7 +597,7 @@ "body": "This incident has now been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-02T18:26:37.188Z", "resolved_inferred": false, "started_at": "2025-10-02T15:48:48.077Z", @@ -610,7 +610,7 @@ "body": "This issue is now resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-24T13:19:58.251Z", "resolved_inferred": false, "started_at": "2025-09-24T11:49:18.532Z", @@ -623,7 +623,7 @@ "body": "The issue has been identified and a fix has been implemented.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-23T17:34:21.349Z", "resolved_inferred": false, "started_at": "2025-09-23T14:18:42.236Z", @@ -636,7 +636,7 @@ "body": "This issue is now resolved. A transient network issue caused performance degradation on our API processes, which was addressed.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-19T09:28:22.158Z", "resolved_inferred": false, "started_at": "2025-09-19T08:27:32.159Z", @@ -649,7 +649,7 @@ "body": "The logging backlog has fully cleared and delivery is optimal again.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-11T09:29:24.991Z", "resolved_inferred": false, "started_at": "2025-09-09T10:01:02.517Z", diff --git a/api/v/calendly.json b/api/v/calendly.json index 1a832c18d123ab34e4a83852089a30b82c30fd10..efdd5d799bc26e9f9eff7e044f2f48ed6af26fbc 100644 --- a/api/v/calendly.json +++ b/api/v/calendly.json @@ -3,7 +3,7 @@ "slug": "calendly", "platform": "statuspage", "status_url": "https://www.calendlystatus.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "We have resolved the issue that prevented users from logging into Calendly.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-23T21:47:55Z", "resolved_inferred": false, "started_at": "2026-07-23T21:21:17Z", @@ -24,7 +24,7 @@ "body": "We are continuing to monitor the system to ensure everything remains stable.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-09T16:37:01Z", "resolved_inferred": false, "started_at": "2026-07-08T17:25:40Z", @@ -36,7 +36,7 @@ "body": "The issue has been resolved, and we are closely monitoring the situation to ensure continued stability.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-22T17:55:15Z", "resolved_inferred": false, "started_at": "2026-05-22T17:01:21Z", @@ -48,7 +48,7 @@ "body": "GoToMeeting APIs experienced issues that caused GoToMeeting events to not be created. The issue has now been resolved by GoToMeeting.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2018-02-01T17:00:00Z", "resolved_inferred": false, "started_at": "2026-04-15T15:21:43Z", @@ -60,7 +60,7 @@ "body": "The team has resolved issues that were preventing users from loading calendly.com", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2018-10-01T20:22:55Z", "resolved_inferred": false, "started_at": "2026-04-15T15:21:42Z", @@ -72,7 +72,7 @@ "body": "This morning our engineers identified an issue that may have caused users using IE11 to experience problems with the login and booking flows. All issues have been resolved and we are continuing to monitor to ensure stability.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2018-09-14T18:09:36Z", "resolved_inferred": false, "started_at": "2026-04-15T15:21:42Z", @@ -84,7 +84,7 @@ "body": "Outlook Desktop functionality has been restored for all users.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2018-06-26T22:44:16Z", "resolved_inferred": false, "started_at": "2026-04-15T15:21:42Z", @@ -96,7 +96,7 @@ "body": "Google has resolved their API issues and all Calendly functionality is now restored.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2018-06-20T20:37:08Z", "resolved_inferred": false, "started_at": "2026-04-15T15:21:42Z", @@ -108,7 +108,7 @@ "body": "Zoom has returned to full functionality and links should resume automatically generating. If you require any additional assistance please reach out to support@calendly.com.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2019-01-09T21:27:33Z", "resolved_inferred": false, "started_at": "2026-04-15T15:21:41Z", @@ -120,7 +120,7 @@ "body": "All login services have returned to stable at this time.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2018-12-05T00:06:38Z", "resolved_inferred": false, "started_at": "2026-04-15T15:21:41Z", @@ -132,7 +132,7 @@ "body": "Zoom has deployed a patch that resolves an issue with OAuth authorizations that affected a small segment of users. We believe that this issue has been resolved. If you continue to experience any issues, please reach out to support@calendly.com.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2018-12-03T19:23:18Z", "resolved_inferred": false, "started_at": "2026-04-15T15:21:41Z", @@ -144,7 +144,7 @@ "body": "Service has been fully restored.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2018-10-02T19:25:54Z", "resolved_inferred": false, "started_at": "2026-04-15T15:21:41Z", @@ -156,7 +156,7 @@ "body": "Apple has resolved the issue. iCloud users should no longer be impacted.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2019-03-19T22:57:32Z", "resolved_inferred": false, "started_at": "2026-04-15T15:21:40Z", @@ -168,7 +168,7 @@ "body": "Fix has been confirmed. Thank you for your patience!", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2019-03-11T19:39:42Z", "resolved_inferred": false, "started_at": "2026-04-15T15:21:40Z", @@ -180,7 +180,7 @@ "body": "This incident has been resolved for all users", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2019-02-12T21:41:54Z", "resolved_inferred": false, "started_at": "2026-04-15T15:21:40Z", @@ -192,7 +192,7 @@ "body": "DNS issues affecting logins using the Outlook 365 service appear to have been resolved. If you experience any further issues, please reach out to support@calendly.com", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2019-01-29T23:06:27Z", "resolved_inferred": false, "started_at": "2026-04-15T15:21:40Z", @@ -204,7 +204,7 @@ "body": "Issue has been resolved. All calendar events and correspondence should be fully operational.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2019-05-22T21:43:17Z", "resolved_inferred": false, "started_at": "2026-04-15T15:21:39Z", @@ -216,7 +216,7 @@ "body": "Calendly site is back up and fully functioning.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2019-04-24T11:41:08Z", "resolved_inferred": false, "started_at": "2026-04-15T15:21:39Z", @@ -228,7 +228,7 @@ "body": "Issue has been resolved and we are continuing to monitor.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2019-04-18T14:42:25Z", "resolved_inferred": false, "started_at": "2026-04-15T15:21:39Z", @@ -240,7 +240,7 @@ "body": "Google reports that its services have been fully restored and the issues are now resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2019-06-03T00:16:24Z", "resolved_inferred": false, "started_at": "2026-04-15T15:21:38Z", @@ -252,7 +252,7 @@ "body": "The issue has been resolved and we are continuing to monitor performance.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2019-05-31T20:20:09Z", "resolved_inferred": false, "started_at": "2026-04-15T15:21:38Z", @@ -264,7 +264,7 @@ "body": "Stripe has resolved the issue and their billing functionality has been restored within the Calendly system.\nhttps://status.stripe.com/", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2019-07-10T17:12:07Z", "resolved_inferred": false, "started_at": "2026-04-15T15:21:37Z", @@ -276,7 +276,7 @@ "body": "Cloudflare systems have recovered and access to Calendly and Zendesk has been restored. Our developers will continue to monitor going forward.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2019-07-02T14:14:13Z", "resolved_inferred": false, "started_at": "2026-04-15T15:21:37Z", @@ -288,7 +288,7 @@ "body": "Google reports that its services have been fully restored and the issues are now resolved.\n\nMore information on the status of the Google Calendar service can be found at https://www.google.com/appsstatus#hl=en&v=issue&sid=2&iid=cc21ebe3962430b2e4ae2b52e3dde98f", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2019-06-18T17:33:33Z", "resolved_inferred": false, "started_at": "2026-04-15T15:21:37Z", @@ -300,7 +300,7 @@ "body": "Stripe billing and account upgrade/downgrade functionality have been fully restored.\n\nOn 2019-07-10, the Stripe API was unavailable from 16:36\u201317:02 UTC, and again from 21:14\u201322:47 UTC. Stripe has confirmed that systems are restored and fully operational.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2019-07-11T13:41:48Z", "resolved_inferred": false, "started_at": "2026-04-15T15:21:36Z", diff --git a/api/v/calix.json b/api/v/calix.json index e66a5e5926ac5216e1942cbbe81d521e99f3bb7b..a758e3adb4d57dfcc07c53c0eb50170558e3367a 100644 --- a/api/v/calix.json +++ b/api/v/calix.json @@ -3,7 +3,7 @@ "slug": "calix", "platform": "statuspage", "status_url": "https://trust.calix.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "Customer Advisory \u2013 Cloud Service Outage\nIncident Start Time: 9:30 AM ET, July 24, 2026\nCurrent Status: Resolved\n \nLatest Update\n \nOperations Cloud services have been successfully restored, and all core functionalities are now operating normally. The Health pipeline is fully operational, including customer-configured threshold processing.\nRecovery activities are complete at this stage. Any remaining data gaps or residual issues will be evaluated and addressed on a case-by-case basis to ensure minimal customer impact.\n \nCommunity post link; https://community.calix.com/s/feed/0D5Pm00002aJM42KAG\n \nWhat We\u2019re Doing: The identified issue has been addressed through corrective actions, and systems have now recovered. This will be the final post for this incident.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-25T09:45:58.762-07:00", "resolved_inferred": false, "started_at": "2026-07-24T07:30:06.577-07:00", diff --git a/api/v/calm.json b/api/v/calm.json index c515f479ba6fccf2ab15c00810f2b7976ad529aa..33e1735b32dd2fd90b93a861e7cea334b487da09 100644 --- a/api/v/calm.json +++ b/api/v/calm.json @@ -3,7 +3,7 @@ "slug": "calm", "platform": "statuspage", "status_url": "https://status.calm.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-16T14:07:09.493Z", "resolved_inferred": false, "started_at": "2026-06-16T14:07:07.164Z", @@ -25,7 +25,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-16T14:06:15.158Z", "resolved_inferred": false, "started_at": "2026-06-16T14:05:25.685Z", @@ -38,7 +38,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-16T12:29:57.301Z", "resolved_inferred": false, "started_at": "2026-06-16T12:28:51.206Z", @@ -51,7 +51,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-12T18:07:35.255Z", "resolved_inferred": false, "started_at": "2026-06-12T18:07:30.704Z", @@ -64,7 +64,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-17T05:42:12.163Z", "resolved_inferred": false, "started_at": "2026-05-17T05:40:35.574Z", @@ -77,7 +77,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-16T22:15:13.927Z", "resolved_inferred": false, "started_at": "2026-05-16T22:15:03.599Z", @@ -90,7 +90,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-29T21:42:37.588Z", "resolved_inferred": false, "started_at": "2026-04-29T21:40:52.927Z", @@ -103,7 +103,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-29T21:40:51.802Z", "resolved_inferred": false, "started_at": "2026-04-29T21:39:34.313Z", @@ -116,7 +116,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-29T21:39:06.097Z", "resolved_inferred": false, "started_at": "2026-04-29T21:38:46.379Z", @@ -129,7 +129,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-20T00:30:51.667Z", "resolved_inferred": false, "started_at": "2026-02-20T00:29:54.839Z", @@ -142,7 +142,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-22T16:50:15.960Z", "resolved_inferred": false, "started_at": "2026-01-22T16:50:02.788Z", @@ -155,7 +155,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-03T22:33:12.046Z", "resolved_inferred": false, "started_at": "2025-11-03T22:32:55.092Z", @@ -168,7 +168,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-09T21:25:07.452Z", "resolved_inferred": false, "started_at": "2025-10-09T21:23:57.352Z", @@ -181,7 +181,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-29T17:00:08.492Z", "resolved_inferred": false, "started_at": "2025-09-29T16:59:53.633Z", @@ -194,7 +194,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-29T13:12:07.162Z", "resolved_inferred": false, "started_at": "2025-09-29T13:11:54.598Z", @@ -207,7 +207,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-22T16:33:35.000Z", "resolved_inferred": false, "started_at": "2025-09-22T16:33:32.645Z", @@ -220,7 +220,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-18T15:42:31.000Z", "resolved_inferred": false, "started_at": "2025-09-18T15:42:16.813Z", diff --git a/api/v/canary.json b/api/v/canary.json index 1bf1d9b9b50e135aea568f47750981c02cd541bb..233fd67e3f26730401d9b6207ca979d528f44e34 100644 --- a/api/v/canary.json +++ b/api/v/canary.json @@ -3,7 +3,7 @@ "slug": "canary", "platform": "statuspage", "status_url": "https://canary.statuspage.io", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "All Canary services that were being impacted by the Amazon Web Services incident have now been restored. If you are continuing to experience any issues, please contact our support team via support@canary.is", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-20T18:10:10.551-04:00", "resolved_inferred": false, "started_at": "2025-10-20T15:08:32.805-04:00", diff --git a/api/v/carrot-quest.json b/api/v/carrot-quest.json index 51897b9096f3b286ac1568dc02cfc51d6cf798f2..76493536e9bd159fa14a782ae94aa07af195c882 100644 --- a/api/v/carrot-quest.json +++ b/api/v/carrot-quest.json @@ -3,7 +3,7 @@ "slug": "carrot-quest", "platform": "statuspage", "status_url": "https://status.carrotquest.io", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-27T17:54:46.913+05:00", "resolved_inferred": false, "started_at": "2026-02-27T16:30:38.752+05:00", diff --git a/api/v/carta.json b/api/v/carta.json index e9342386dca926138cd745be1568d9bad356a60d..000d3000f1f592e7a3d4076857f47017653e3f6c 100644 --- a/api/v/carta.json +++ b/api/v/carta.json @@ -3,7 +3,7 @@ "slug": "carta", "platform": "statuspage", "status_url": "https://status.carta.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-09-01T13:28:49.669-07:00", "resolved_inferred": false, "started_at": "2026-09-01T08:45:14.803-07:00", @@ -25,7 +25,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-16T03:31:58.323-07:00", "resolved_inferred": false, "started_at": "2026-07-16T02:45:48.898-07:00", @@ -38,7 +38,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-06T11:30:30.150-07:00", "resolved_inferred": false, "started_at": "2026-07-06T09:38:45.112-07:00", @@ -51,7 +51,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-27T16:45:42.800-07:00", "resolved_inferred": false, "started_at": "2026-05-27T14:50:58.946-07:00", @@ -64,7 +64,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-31T13:27:14.267-07:00", "resolved_inferred": false, "started_at": "2026-03-31T08:43:37.534-07:00", @@ -77,7 +77,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-19T11:26:10.741-07:00", "resolved_inferred": false, "started_at": "2026-03-19T08:36:36.998-07:00", @@ -90,7 +90,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-24T13:57:54.537-08:00", "resolved_inferred": false, "started_at": "2025-11-24T13:52:31.153-08:00", @@ -103,7 +103,7 @@ "body": "Upstream issues have been resolved, no further user issues are expected on Carta applications", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-18T12:00:50.818-08:00", "resolved_inferred": false, "started_at": "2025-11-18T06:25:26.497-08:00", @@ -116,7 +116,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-20T14:01:58.906-07:00", "resolved_inferred": false, "started_at": "2025-10-20T09:07:03.483-07:00", @@ -129,7 +129,7 @@ "body": "Site performance continues to be normal. The issue has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-20T03:36:28.107-07:00", "resolved_inferred": false, "started_at": "2025-10-20T02:35:19.779-07:00", @@ -142,7 +142,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-21T13:22:23.167-07:00", "resolved_inferred": false, "started_at": "2025-08-21T12:06:09.723-07:00", @@ -155,7 +155,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-15T11:00:10.936-07:00", "resolved_inferred": false, "started_at": "2025-08-15T08:23:08.321-07:00", diff --git a/api/v/caseware-cloud.json b/api/v/caseware-cloud.json index 03bc1c8fddebc1dfeb5fab9f385e9a8d896761b2..293f54b77da1342152baf54dc29f4e55e6e54a69 100644 --- a/api/v/caseware-cloud.json +++ b/api/v/caseware-cloud.json @@ -3,7 +3,7 @@ "slug": "caseware-cloud", "platform": "statuspage", "status_url": "https://status.casewarecloud.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "The Cloud Financials application has resumed successfully - Incident Resolved.\nWe apologize for any inconvenience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-09-01T23:44:09.287Z", "resolved_inferred": false, "started_at": "2026-09-01T22:58:30.175Z", @@ -25,7 +25,7 @@ "body": "SmartSync Cloud Service monitoring has resumed successfully - Incident Resolved.\nWe apologize for any inconvenience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-31T19:31:22.714Z", "resolved_inferred": false, "started_at": "2026-08-31T18:55:35.320Z", @@ -38,7 +38,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-15T03:45:37.020Z", "resolved_inferred": false, "started_at": "2026-08-14T19:12:56.970Z", @@ -51,7 +51,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-12T13:18:18.366Z", "resolved_inferred": false, "started_at": "2026-08-12T12:42:47.129Z", @@ -64,7 +64,7 @@ "body": "SmartSync Cloud Service monitoring has resumed successfully - Incident Resolved.\nWe apologize for any inconvenience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-11T00:23:32.069Z", "resolved_inferred": false, "started_at": "2026-08-10T23:44:50.527Z", @@ -77,7 +77,7 @@ "body": "SmartSync Cloud Service monitoring has resumed successfully - Incident Resolved.\nWe apologize for any inconvenience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-10T19:26:21.452Z", "resolved_inferred": false, "started_at": "2026-08-10T18:58:26.837Z", @@ -90,7 +90,7 @@ "body": "SmartSync Cloud Service monitoring has resumed successfully - Incident Resolved.\nWe apologize for any inconvenience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-10T18:27:06.000Z", "resolved_inferred": false, "started_at": "2026-08-10T17:49:27.339Z", @@ -103,7 +103,7 @@ "body": "Caseware Cloud Service monitoring has resumed successfully - Incident Resolved.\nWe apologize for any inconvenience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-04T16:11:15.181Z", "resolved_inferred": false, "started_at": "2026-08-04T15:30:46.790Z", @@ -116,7 +116,7 @@ "body": "Caseware Cloud Service monitoring has resumed successfully - Incident Resolved.\nWe apologize for any inconvenience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-03T16:00:10.000Z", "resolved_inferred": false, "started_at": "2026-08-03T15:32:53.475Z", @@ -129,7 +129,7 @@ "body": "The issue affecting Verity Service in the Canada, Europe, and United States regions has been resolved. \n\n The root cause was identified, and corrective actions were successfully implemented. Service has returned to normal operation, and our teams have confirmed stability across the affected regions. \n\n We will continue to monitor the environment to ensure service remains healthy. \n\n We apologize for any inconvenience and appreciate your patience throughout this incident.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-30T15:40:09.000Z", "resolved_inferred": false, "started_at": "2026-07-30T14:04:27.418Z", @@ -142,7 +142,7 @@ "body": "SmartSync Cloud Service monitoring has resumed successfully - Incident Resolved.\nWe apologize for any inconvenience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-18T07:31:31.000Z", "resolved_inferred": false, "started_at": "2026-07-18T06:59:58.000Z", @@ -155,7 +155,7 @@ "body": "Caseware Cloud Service monitoring has resumed successfully - Incident Resolved.\nWe apologize for any inconvenience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-16T16:23:07.000Z", "resolved_inferred": false, "started_at": "2026-07-16T14:20:19.000Z", @@ -168,7 +168,7 @@ "body": "SmartSync Cloud Service monitoring has resumed successfully - Incident Resolved.\nWe apologize for any inconvenience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-14T21:14:42.258Z", "resolved_inferred": false, "started_at": "2026-07-14T19:50:45.852Z", @@ -181,7 +181,7 @@ "body": "Cloud-based Engagement Solutions monitoring has resumed successfully - Incident Resolved.\nWe apologize for any inconvenience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-14T06:42:14.719Z", "resolved_inferred": false, "started_at": "2026-07-14T04:30:12.290Z", @@ -194,7 +194,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-13T22:31:51.338Z", "resolved_inferred": false, "started_at": "2026-07-13T21:39:13.000Z", @@ -207,7 +207,7 @@ "body": "SmartSync Cloud Service monitoring has resumed successfully - Incident Resolved.\nWe apologize for any inconvenience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-13T16:08:08.000Z", "resolved_inferred": false, "started_at": "2026-07-13T15:01:35.953Z", @@ -220,7 +220,7 @@ "body": "Cloud-based Engagement Solutions monitoring has resumed successfully - Incident Resolved.\nWe apologize for any inconvenience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-10T21:39:44.644Z", "resolved_inferred": false, "started_at": "2026-07-10T20:28:55.845Z", @@ -233,7 +233,7 @@ "body": "Cloud-based Engagement Solutions monitoring has resumed successfully - Incident Resolved.\nWe apologize for any inconvenience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-10T15:48:11.171Z", "resolved_inferred": false, "started_at": "2026-07-10T13:18:32.767Z", @@ -246,7 +246,7 @@ "body": "Cloud-based Engagement Solutions monitoring has resumed successfully - Incident Resolved.\nWe apologize for any inconvenience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-10T08:04:57.988Z", "resolved_inferred": false, "started_at": "2026-07-10T02:51:14.261Z", @@ -259,7 +259,7 @@ "body": "We are experiencing a Partial Outage impacting Verity Service in Canada and United States region(s).\n\nOur teams are actively investigating the issue, identifying the root cause, and implementing the necessary corrective actions.\n\nAn update will be provided within the hour.\n\nWe apologize for any inconvenience and appreciate your patience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-08T15:17:35.838Z", "resolved_inferred": false, "started_at": "2026-07-08T14:07:32.000Z", @@ -272,7 +272,7 @@ "body": "SmartSync Cloud Service monitoring has resumed successfully - Incident Resolved.\nWe apologize for any inconvenience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-04T01:59:33.274Z", "resolved_inferred": false, "started_at": "2026-07-03T21:09:29.898Z", @@ -285,7 +285,7 @@ "body": "This incident has been resolved.\n\nWe apologize for any inconvenience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-01T19:13:24.698Z", "resolved_inferred": false, "started_at": "2026-07-01T18:37:14.404Z", @@ -298,7 +298,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-25T09:08:33.000Z", "resolved_inferred": false, "started_at": "2026-06-24T13:27:52.635Z", @@ -311,7 +311,7 @@ "body": "Caseware Cloud Service monitoring has resumed successfully - Incident Resolved.\nWe apologize for any inconvenience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-19T09:55:13.273Z", "resolved_inferred": false, "started_at": "2026-06-19T08:39:09.000Z", @@ -324,7 +324,7 @@ "body": "SmartSync Cloud Service monitoring has resumed successfully - Incident Resolved.\nWe apologize for any inconvenience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-17T21:59:48.000Z", "resolved_inferred": false, "started_at": "2026-06-17T20:47:33.521Z", @@ -337,7 +337,7 @@ "body": "SmartSync Cloud Service monitoring has resumed successfully - Incident Resolved.\nWe apologize for any inconvenience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-08T13:51:59.000Z", "resolved_inferred": false, "started_at": "2026-06-08T13:24:15.553Z", @@ -350,7 +350,7 @@ "body": "The template authoring flow issue monitoring has resumed successfully - Incident Resolved.\nWe apologize for any inconvenience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-08T23:45:22.000Z", "resolved_inferred": false, "started_at": "2026-06-06T07:45:00.000Z", @@ -363,7 +363,7 @@ "body": "SmartSync Cloud Service monitoring has resumed successfully - Incident Resolved.\nWe apologize for any inconvenience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-03T17:40:18.000Z", "resolved_inferred": false, "started_at": "2026-06-03T12:20:24.618Z", @@ -376,7 +376,7 @@ "body": "SmartSync Cloud Service monitoring has resumed successfully - Incident Resolved.\nWe apologize for any inconvenience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-03T11:05:22.162Z", "resolved_inferred": false, "started_at": "2026-06-03T08:45:07.000Z", @@ -389,7 +389,7 @@ "body": "Caseware Cloud Service monitoring has resumed successfully - Incident Resolved.\nWe apologize for any inconvenience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-01T14:49:44.000Z", "resolved_inferred": false, "started_at": "2026-06-01T14:13:48.000Z", @@ -402,7 +402,7 @@ "body": "Cloud-based Engagement Solutions monitoring has resumed successfully - Incident Resolved.\nWe apologize for any inconvenience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-29T20:04:45.784Z", "resolved_inferred": false, "started_at": "2026-05-29T17:28:23.709Z", @@ -415,7 +415,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-28T02:53:20.402Z", "resolved_inferred": false, "started_at": "2026-05-28T01:20:08.580Z", @@ -428,7 +428,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-27T17:43:43.966Z", "resolved_inferred": false, "started_at": "2026-05-27T13:50:09.000Z", @@ -441,7 +441,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-18T14:19:07.734Z", "resolved_inferred": false, "started_at": "2026-05-18T13:57:58.915Z", @@ -454,7 +454,7 @@ "body": "Caseware Cloud Service monitoring has resumed successfully - Incident Resolved.\nWe apologize for any inconvenience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-13T08:30:16.000Z", "resolved_inferred": false, "started_at": "2026-05-12T22:00:46.000Z", @@ -467,7 +467,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-09T08:00:56.000Z", "resolved_inferred": false, "started_at": "2026-05-07T07:14:42.000Z", @@ -480,7 +480,7 @@ "body": "SmartSync Cloud Service monitoring has resumed successfully - Incident Resolved.\nWe apologize for any inconvenience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-16T18:43:34.473Z", "resolved_inferred": false, "started_at": "2026-04-16T17:55:54.000Z", @@ -493,7 +493,7 @@ "body": "Cloud Connectors in Cloud-based Engagement Solutions monitoring has resumed successfully - Incident Resolved.\nWe apologize for any inconvenience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-13T18:13:33.274Z", "resolved_inferred": false, "started_at": "2026-04-13T18:13:33.177Z", @@ -506,7 +506,7 @@ "body": "Cloud Connectors in Cloud-based Engagement Solutions monitoring has resumed successfully - Incident Resolved.\nWe apologize for any inconvenience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-13T18:11:33.860Z", "resolved_inferred": false, "started_at": "2026-04-13T14:49:44.000Z", @@ -519,7 +519,7 @@ "body": "Cloud-based Engagement Solutions monitoring has resumed successfully - Incident Resolved.\nWe apologize for any inconvenience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-26T16:30:28.000Z", "resolved_inferred": false, "started_at": "2026-03-26T01:05:31.000Z", @@ -532,7 +532,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-20T09:32:55.000Z", "resolved_inferred": false, "started_at": "2026-03-20T08:30:44.000Z", @@ -545,7 +545,7 @@ "body": "SmartSync Cloud Service monitoring has resumed successfully - Incident Resolved.\nWe apologize for any inconvenience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-16T17:01:49.000Z", "resolved_inferred": false, "started_at": "2026-03-16T10:10:09.000Z", @@ -558,7 +558,7 @@ "body": "Caseware Cloud Service monitoring has resumed successfully - Incident Resolved.\nWe apologize for any inconvenience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-11T23:00:59.000Z", "resolved_inferred": false, "started_at": "2026-03-11T21:45:15.000Z", @@ -571,7 +571,7 @@ "body": "Sherlock monitoring has resumed successfully - Incident Resolved.\nWe apologize for any inconvenience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-25T17:16:14.710Z", "resolved_inferred": false, "started_at": "2026-02-25T15:37:19.871Z", @@ -584,7 +584,7 @@ "body": "Caseware Cloud Service, Cloud-based Engagement Solutions monitoring has resumed successfully - Incident Resolved.\nWe apologize for any inconvenience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-23T14:26:08.888Z", "resolved_inferred": false, "started_at": "2026-02-23T13:18:03.000Z", @@ -597,7 +597,7 @@ "body": "Caseware Cloud Service monitoring has resumed successfully - Incident Resolved.\nWe apologize for any inconvenience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-10T23:56:17.000Z", "resolved_inferred": false, "started_at": "2026-02-10T14:53:49.000Z", @@ -610,7 +610,7 @@ "body": "Caseware Cloud Service monitoring has resumed successfully - Incident Resolved.\nWe apologize for any inconvenience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-30T15:20:27.000Z", "resolved_inferred": false, "started_at": "2026-01-29T13:25:41.000Z", @@ -623,7 +623,7 @@ "body": "The Issuev2 Sherlock API and the Issuev2 dataset within the Sherlock Reader/Builder are operating normally. Post-resolution monitoring has completed successfully.\n\nAt this time, the incident is considered fully resolved. We apologize for any inconvenience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-29T18:46:13.667Z", "resolved_inferred": false, "started_at": "2026-01-28T17:12:14.068Z", @@ -636,7 +636,7 @@ "body": "Caseware Cloud Service monitoring has resumed successfully - Incident Resolved.\nWe apologize for any inconvenience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-28T12:00:00.000Z", "resolved_inferred": false, "started_at": "2026-01-28T11:20:53.000Z", @@ -649,7 +649,7 @@ "body": "Cloud-based Engagement Solutions monitoring has resumed successfully - Incident Resolved.\nWe apologize for any inconvenience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-22T21:46:28.519Z", "resolved_inferred": false, "started_at": "2026-01-22T21:14:01.996Z", diff --git a/api/v/castle.json b/api/v/castle.json index beb4a8f75b0e8aa2a115b5fe3e1495ec01c4c697..6d8f3fb7b4096acb02f787e922057f6cea4979ca 100644 --- a/api/v/castle.json +++ b/api/v/castle.json @@ -3,7 +3,7 @@ "slug": "castle", "platform": "statuspage", "status_url": "https://status.castle.io", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "We experienced an elevated number of errors returned by our API. Our team resolved the issue, and the API is operating normally. We apologize for any inconvenience caused.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-31T17:04:00.000Z", "resolved_inferred": false, "started_at": "2026-07-31T16:55:00.000Z", @@ -25,7 +25,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-08T16:41:00.831Z", "resolved_inferred": false, "started_at": "2026-05-08T04:31:52.717Z", @@ -38,7 +38,7 @@ "body": "We experienced an issue with downsizing one of our underlying nodes that affected the 25% of our traffic.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-17T09:56:21.150Z", "resolved_inferred": false, "started_at": "2026-03-17T09:56:21.098Z", @@ -51,7 +51,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-22T23:01:59.706Z", "resolved_inferred": false, "started_at": "2026-01-22T23:01:59.652Z", diff --git a/api/v/catalyst-cloud.json b/api/v/catalyst-cloud.json index 3da9b7e73694954b9e7d1e9deae64679d7beee4e..b0f6c2d6b52a13597bb32a227b5a1cca15c790c0 100644 --- a/api/v/catalyst-cloud.json +++ b/api/v/catalyst-cloud.json @@ -3,7 +3,7 @@ "slug": "catalyst-cloud", "platform": "statuspage", "status_url": "https://status.catalystcloud.nz", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-19T14:45:16.140+12:00", "resolved_inferred": false, "started_at": "2026-08-19T14:37:55.000+12:00", @@ -25,7 +25,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-17T18:25:06.690+12:00", "resolved_inferred": false, "started_at": "2026-08-17T15:16:38.443+12:00", @@ -38,7 +38,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-13T08:23:29.047+12:00", "resolved_inferred": false, "started_at": "2026-08-13T07:53:23.993+12:00", @@ -51,7 +51,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-31T08:16:38.888+12:00", "resolved_inferred": false, "started_at": "2026-07-30T12:21:57.535+12:00", @@ -64,7 +64,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-28T17:18:18.743+12:00", "resolved_inferred": false, "started_at": "2026-07-28T09:57:01.948+12:00", @@ -77,7 +77,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-23T12:23:48.975+12:00", "resolved_inferred": false, "started_at": "2026-06-23T12:02:07.185+12:00", @@ -90,7 +90,7 @@ "body": "The emergency maintenance is complete.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-03T17:41:51.684+12:00", "resolved_inferred": false, "started_at": "2026-06-03T17:01:43.071+12:00", @@ -103,7 +103,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-09T21:20:47.997+12:00", "resolved_inferred": false, "started_at": "2026-05-09T06:05:03.051+12:00", @@ -116,7 +116,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-07T16:56:54.883+12:00", "resolved_inferred": false, "started_at": "2026-05-07T16:03:25.446+12:00", @@ -129,7 +129,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-15T17:24:48.981+12:00", "resolved_inferred": false, "started_at": "2026-04-15T16:12:16.239+12:00", @@ -142,7 +142,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-13T22:51:48.106+13:00", "resolved_inferred": false, "started_at": "2026-03-13T17:40:57.020+13:00", @@ -155,7 +155,7 @@ "body": "Some of our APIs in the nz-por-1 region were suffering from degraded performance and, occasionally, failed creation requests.\n\nThis issue has now been resolved, and all APIs are now available again.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-04T23:30:00.000+13:00", "resolved_inferred": false, "started_at": "2026-03-04T21:00:00.000+13:00", @@ -168,7 +168,7 @@ "body": "One of our compute hypervisors in the nz-hlz-1 region suffered from a networking issue causing higher than usual latency for block storage access for instances hosted on that hypervisor.\n\nThe issue has now been fixed, and all affected instances should now have performance restored.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-26T11:00:00.000+13:00", "resolved_inferred": false, "started_at": "2026-02-26T11:00:00.000+13:00", @@ -181,7 +181,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-21T09:50:02.108+13:00", "resolved_inferred": false, "started_at": "2026-02-21T08:59:06.986+13:00", @@ -194,7 +194,7 @@ "body": "New database instances can now be created in the nz-hlz-1 region.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-21T09:47:06.104+13:00", "resolved_inferred": false, "started_at": "2026-02-21T08:50:11.872+13:00", @@ -207,7 +207,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-05T18:04:48.220+13:00", "resolved_inferred": false, "started_at": "2026-02-05T15:00:12.872+13:00", @@ -220,7 +220,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-04T06:07:38.825+13:00", "resolved_inferred": false, "started_at": "2026-02-04T05:26:00.109+13:00", @@ -233,7 +233,7 @@ "body": "This issue has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-02T13:11:43.252+13:00", "resolved_inferred": false, "started_at": "2026-01-29T14:06:02.843+13:00", @@ -246,7 +246,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-28T09:49:15.470+13:00", "resolved_inferred": false, "started_at": "2026-01-28T09:32:34.880+13:00", @@ -259,7 +259,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "maintenance", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-17T20:29:42.816+13:00", "resolved_inferred": false, "started_at": "2025-11-17T18:18:48.435+13:00", @@ -272,7 +272,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-17T10:21:55.872+12:00", "resolved_inferred": false, "started_at": "2025-09-17T09:52:39.580+12:00", diff --git a/api/v/cdc-service.json b/api/v/cdc-service.json index 437ec73aba60a19b053e6678978cdfb876652d05..0f424b5087dc314edaf2aeb7fedc246812d6daeb 100644 --- a/api/v/cdc-service.json +++ b/api/v/cdc-service.json @@ -3,7 +3,7 @@ "slug": "cdc-service", "platform": "status.io", "status_url": "http://status.cdc.systems", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": false, "first_watched": "2026-09-04T07:06:16Z", diff --git a/api/v/cdnjs.json b/api/v/cdnjs.json index 6d8ceccb9e86186e9ccaa44346e43d5a37cd1395..f46d4b611789c97ea7eb2a9167944eeba1a7bb16 100644 --- a/api/v/cdnjs.json +++ b/api/v/cdnjs.json @@ -3,7 +3,7 @@ "slug": "cdnjs", "platform": "statuspage", "status_url": "https://status.cdnjs.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "We have confirmed that searching libraries on cdnjs continues to be available. Our upstream search provider has also confirmed resolution on their end.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-30T16:57:18.702Z", "resolved_inferred": false, "started_at": "2026-07-30T11:50:20.268Z", diff --git a/api/v/ceros.json b/api/v/ceros.json index 62ead50de47e4d154fcc1f53ff051d3e054fb309..89035dffdcc0f309f44d127f525384284009af4a 100644 --- a/api/v/ceros.json +++ b/api/v/ceros.json @@ -3,7 +3,7 @@ "slug": "ceros", "platform": "statuspage", "status_url": "https://status.ceros.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-14T11:54:21.286-04:00", "resolved_inferred": false, "started_at": "2026-04-14T08:56:03.897-04:00", @@ -25,7 +25,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-03T12:38:02.898-05:00", "resolved_inferred": false, "started_at": "2025-12-03T08:49:39.445-05:00", @@ -38,7 +38,7 @@ "body": "We are continuing to monitor one issue affecting video uploads, however all other functionality is now back online.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-20T11:07:18.534-04:00", "resolved_inferred": false, "started_at": "2025-10-20T05:50:16.877-04:00", @@ -51,7 +51,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-21T18:05:28.028-04:00", "resolved_inferred": false, "started_at": "2025-08-21T14:53:46.961-04:00", diff --git a/api/v/cex-io.json b/api/v/cex-io.json index ab86577a1b7c9e2ea809bf00cbc5538c03ff8810..473746776a0da189f503079a02dcf91bfa4479da 100644 --- a/api/v/cex-io.json +++ b/api/v/cex-io.json @@ -3,7 +3,7 @@ "slug": "cex-io", "platform": "statuspage", "status_url": "https://status.cex.io", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "maintenance", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-16T08:47:58.232Z", "resolved_inferred": false, "started_at": "2026-08-16T06:30:12.522Z", @@ -25,7 +25,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "maintenance", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-16T08:48:12.780Z", "resolved_inferred": false, "started_at": "2026-08-16T06:10:39.108Z", @@ -38,7 +38,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "maintenance", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-16T08:48:25.188Z", "resolved_inferred": false, "started_at": "2026-08-16T06:07:13.660Z", @@ -51,7 +51,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "maintenance", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-10T08:17:35.597Z", "resolved_inferred": false, "started_at": "2026-08-04T09:41:16.060Z", @@ -64,7 +64,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "maintenance", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-05T12:24:48.905Z", "resolved_inferred": false, "started_at": "2026-07-20T12:36:15.971Z", @@ -77,7 +77,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "maintenance", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-12T08:19:27.305Z", "resolved_inferred": false, "started_at": "2026-07-20T10:10:38.359Z", @@ -90,7 +90,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "maintenance", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-22T12:06:48.131Z", "resolved_inferred": false, "started_at": "2026-07-20T09:12:59.806Z", @@ -103,7 +103,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "maintenance", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-26T12:02:57.455Z", "resolved_inferred": false, "started_at": "2026-06-26T11:03:30.805Z", @@ -116,7 +116,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "maintenance", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-26T06:45:08.437Z", "resolved_inferred": false, "started_at": "2026-06-25T17:20:54.263Z", @@ -129,7 +129,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "maintenance", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-13T10:57:37.071Z", "resolved_inferred": false, "started_at": "2026-06-25T13:04:31.590Z", @@ -142,7 +142,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "maintenance", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-24T11:16:02.960Z", "resolved_inferred": false, "started_at": "2026-06-24T08:42:28.615Z", @@ -155,7 +155,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "maintenance", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-10T08:28:16.218Z", "resolved_inferred": false, "started_at": "2026-06-09T09:35:26.146Z", @@ -168,7 +168,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "maintenance", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-14T13:22:31.554Z", "resolved_inferred": false, "started_at": "2026-06-01T08:02:53.756Z", @@ -181,7 +181,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "maintenance", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-23T08:50:17.091Z", "resolved_inferred": false, "started_at": "2026-05-28T11:16:12.835Z", @@ -194,7 +194,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "maintenance", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-25T16:51:11.957Z", "resolved_inferred": false, "started_at": "2026-05-25T13:41:29.906Z", @@ -207,7 +207,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "maintenance", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-01T10:24:58.485Z", "resolved_inferred": false, "started_at": "2026-05-01T08:57:15.493Z", @@ -220,7 +220,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "maintenance", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-04T08:19:09.202Z", "resolved_inferred": false, "started_at": "2026-04-29T08:40:32.195Z", @@ -233,7 +233,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "maintenance", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-24T09:22:25.515Z", "resolved_inferred": false, "started_at": "2026-04-24T09:00:57.556Z", @@ -246,7 +246,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "maintenance", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-22T14:33:03.082Z", "resolved_inferred": false, "started_at": "2026-04-09T14:05:11.134Z", @@ -259,7 +259,7 @@ "body": "Swift transfers have been retired.", "first_seen": "2026-09-04T07:06:16Z", "impact": "maintenance", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-01T16:36:41.588Z", "resolved_inferred": false, "started_at": "2026-03-05T17:37:29.254Z", @@ -272,7 +272,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "maintenance", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-20T14:32:28.506Z", "resolved_inferred": false, "started_at": "2026-03-04T07:59:15.797Z", @@ -285,7 +285,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "maintenance", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-25T18:30:07.359Z", "resolved_inferred": false, "started_at": "2026-02-25T15:30:58.063Z", @@ -298,7 +298,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "maintenance", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-23T12:35:24.679Z", "resolved_inferred": false, "started_at": "2026-02-23T11:58:53.223Z", @@ -311,7 +311,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "maintenance", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-18T14:55:03.838Z", "resolved_inferred": false, "started_at": "2026-02-18T14:42:17.148Z", @@ -324,7 +324,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "maintenance", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-04T13:03:13.487Z", "resolved_inferred": false, "started_at": "2026-02-16T12:49:27.097Z", @@ -337,7 +337,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "maintenance", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-16T07:44:35.518Z", "resolved_inferred": false, "started_at": "2026-02-15T13:00:42.934Z", @@ -350,7 +350,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "maintenance", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-17T08:30:43.100Z", "resolved_inferred": false, "started_at": "2026-02-12T10:16:04.190Z", @@ -363,7 +363,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "maintenance", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-11T08:19:16.935Z", "resolved_inferred": false, "started_at": "2026-02-11T08:08:02.808Z", @@ -376,7 +376,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "maintenance", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-06T14:43:27.974Z", "resolved_inferred": false, "started_at": "2026-02-06T13:51:18.615Z", @@ -389,7 +389,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "maintenance", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-06T11:01:52.756Z", "resolved_inferred": false, "started_at": "2026-02-06T06:04:29.436Z", @@ -402,7 +402,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "maintenance", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-04T13:30:05.360Z", "resolved_inferred": false, "started_at": "2026-01-28T08:33:22.682Z", @@ -415,7 +415,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "maintenance", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-22T12:34:41.166Z", "resolved_inferred": false, "started_at": "2026-01-22T11:44:46.275Z", @@ -428,7 +428,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "maintenance", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-22T09:50:22.372Z", "resolved_inferred": false, "started_at": "2026-01-21T16:53:42.056Z", @@ -441,7 +441,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "maintenance", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-19T09:49:06.848Z", "resolved_inferred": false, "started_at": "2026-01-19T06:39:10.578Z", @@ -454,7 +454,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-09T20:51:59.066Z", "resolved_inferred": false, "started_at": "2026-01-09T20:13:24.747Z", @@ -467,7 +467,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "maintenance", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-07T12:20:21.478Z", "resolved_inferred": false, "started_at": "2026-01-06T10:16:41.036Z", @@ -480,7 +480,7 @@ "body": "Skrill/Neteller/Epay payments have been retired.", "first_seen": "2026-09-04T07:06:16Z", "impact": "maintenance", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-01T16:33:06.456Z", "resolved_inferred": false, "started_at": "2025-12-30T16:33:11.134Z", @@ -493,7 +493,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "maintenance", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-30T08:52:17.348Z", "resolved_inferred": false, "started_at": "2025-12-29T13:59:56.002Z", @@ -506,7 +506,7 @@ "body": "METIS will be available in a \u201ctrade only\u201d option due to the liquidity provider\u2019s possibilities. The transfer process will take several working days.", "first_seen": "2026-09-04T07:06:16Z", "impact": "maintenance", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-07T10:43:02.654Z", "resolved_inferred": false, "started_at": "2025-12-26T09:52:33.084Z", @@ -519,7 +519,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "maintenance", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-24T09:02:20.210Z", "resolved_inferred": false, "started_at": "2025-12-23T08:30:12.088Z", @@ -532,7 +532,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-18T11:15:47.802Z", "resolved_inferred": false, "started_at": "2025-12-17T13:04:52.204Z", @@ -545,7 +545,7 @@ "body": "Faster payments are now available for withdrawals-only.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-01T15:33:34.229Z", "resolved_inferred": false, "started_at": "2025-12-17T10:32:59.422Z", @@ -558,7 +558,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-07T16:39:27.931Z", "resolved_inferred": false, "started_at": "2025-12-07T16:15:45.308Z", @@ -571,7 +571,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "maintenance", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-08T15:13:48.569Z", "resolved_inferred": false, "started_at": "2025-12-04T09:40:23.848Z", @@ -584,7 +584,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "maintenance", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-02T08:29:54.585Z", "resolved_inferred": false, "started_at": "2025-12-01T21:03:42.440Z", @@ -597,7 +597,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-01T09:35:54.226Z", "resolved_inferred": false, "started_at": "2025-11-30T11:29:22.271Z", @@ -610,7 +610,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "maintenance", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-08T15:14:54.170Z", "resolved_inferred": false, "started_at": "2025-11-21T09:17:03.443Z", @@ -623,7 +623,7 @@ "body": "We are proceeding to the \u201ctrade only\u201d option due to the liquidity provider\u2019s possibilities. The transfer process will take several working days.", "first_seen": "2026-09-04T07:06:16Z", "impact": "maintenance", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-26T16:45:54.446Z", "resolved_inferred": false, "started_at": "2025-10-14T15:34:50.994Z", @@ -636,7 +636,7 @@ "body": "Wire transfers have been retired. This component has been removed from our status page.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-20T13:54:29.628Z", "resolved_inferred": false, "started_at": "2025-09-22T10:49:15.797Z", @@ -649,7 +649,7 @@ "body": "ENJ will be available in a \u201ctrade only\u201d option due to the liquidity provider\u2019s possibilities. The transfer process will take several working days.", "first_seen": "2026-09-04T07:06:16Z", "impact": "maintenance", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-26T16:47:52.939Z", "resolved_inferred": false, "started_at": "2025-08-01T11:52:26.569Z", diff --git a/api/v/chainalysis.json b/api/v/chainalysis.json index 147b66a65c82da5a2f60ba5212c5cecada272515..09667235e46af893600160f2a53bbb7dc4caf254 100644 --- a/api/v/chainalysis.json +++ b/api/v/chainalysis.json @@ -3,7 +3,7 @@ "slug": "chainalysis", "platform": "statuspage", "status_url": "https://status.chainalysis.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "This incident has been resolved. Please reach out to support@chainalysis.com if you have any questions or require further assistance.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-09-03T05:15:54.414Z", "resolved_inferred": false, "started_at": "2026-09-01T20:09:34.352Z", @@ -25,7 +25,7 @@ "body": "This incident has been resolved. Please reach out to support@chainalysis.com if you have any questions or require further assistance.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-24T17:54:45.205Z", "resolved_inferred": false, "started_at": "2026-08-24T14:53:07.379Z", @@ -38,7 +38,7 @@ "body": "This incident has been resolved. Please reach out to support@chainalysis.com if you have any questions or require further assistance.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-07T18:12:10.119Z", "resolved_inferred": false, "started_at": "2026-08-07T16:59:52.951Z", @@ -51,7 +51,7 @@ "body": "This incident has been resolved. Please reach out to support@chainalysis.com if you have any questions or require further assistance.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-30T16:52:11.784Z", "resolved_inferred": false, "started_at": "2026-07-30T16:38:25.369Z", @@ -64,7 +64,7 @@ "body": "This incident has been resolved. \n\nPlease reach out to support@chainalysis.com if you have any questions or require further assistance.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-17T15:02:29.769Z", "resolved_inferred": false, "started_at": "2026-07-17T14:57:21.545Z", @@ -77,7 +77,7 @@ "body": "Between 22:00 UTC and 23:30 UTC, KYT experienced an error in processing some Solana transfers. The issue is now resolved, and we are checking the number of affected transfers. No action is required from customers as the transfers will be reprocessed from our end.\n\nIf you experience any further issues or have any questions, please reach out to support@chainalysis.com.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-16T00:12:41.000Z", "resolved_inferred": false, "started_at": "2026-07-16T00:12:40.987Z", @@ -90,7 +90,7 @@ "body": "This incident has been resolved. \n\nPlease reach out to support@chainalysis.com if you have any questions or require further assistance.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-14T13:31:00.826Z", "resolved_inferred": false, "started_at": "2026-07-13T23:44:21.007Z", @@ -103,7 +103,7 @@ "body": "This incident has been resolved. Please reach out to support@chainalysis.com if you have any questions or require further assistance.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-02T21:15:48.842Z", "resolved_inferred": false, "started_at": "2026-07-02T16:46:28.071Z", @@ -116,7 +116,7 @@ "body": "This incident has been resolved.\n\n If you have any questions, please contact support@chainalysis.com.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-02T13:30:02.969Z", "resolved_inferred": false, "started_at": "2026-07-02T01:02:51.534Z", @@ -129,7 +129,7 @@ "body": "At 9:43AM UTC, all users were prevented from opening (or changing if already open) Next-Gen graphs. Users would have experienced between 10-17 minutes of downtime. \n\nThis incident has been resolved.\n\nIf you experience any further issues, please reach out to support@chainalysis.com.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-23T08:30:00.000Z", "resolved_inferred": false, "started_at": "2026-06-23T08:30:00.000Z", @@ -142,7 +142,7 @@ "body": "This incident has been resolved.\n\nIf you experience any continued issues, please reach out to support@chainalysis.com", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-24T14:15:21.956Z", "resolved_inferred": false, "started_at": "2026-06-22T19:57:38.000Z", @@ -155,7 +155,7 @@ "body": "This incident has been resolved.\n\nIf you experience any continued issues, please reach out to support@chainalysis.com.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-22T15:13:45.976Z", "resolved_inferred": false, "started_at": "2026-06-20T19:58:13.751Z", @@ -168,7 +168,7 @@ "body": "This incident has been resolved and no further issues are expected. \n\nIf you experience any problems at all, reach out to support@chainalysis.com", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-12T09:05:54.673Z", "resolved_inferred": false, "started_at": "2026-06-12T07:53:03.779Z", @@ -181,7 +181,7 @@ "body": "We experienced a partial degradation of service affecting some Reactor users between 06:35 UTC and 06:38 UTC. \n\nService has recovered and we consider this resolved. However, we will continue to monitoring to ensure platform stability.\n\nIf you experience any further issues, please reach out to support@chainalysis.com", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-08T12:26:42.405Z", "resolved_inferred": false, "started_at": "2026-06-08T12:26:42.362Z", @@ -194,7 +194,7 @@ "body": "Between 17:44 and 18:18 UTC, users may have experienced errors when attempting to load the KYT UI. This issue is now resolved.\n\nPlease reach out to support@chainalysis.com if you have any questions or require further assistance.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-05T18:35:39.885Z", "resolved_inferred": false, "started_at": "2026-06-05T18:35:39.837Z", @@ -207,7 +207,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-25T10:20:37.061Z", "resolved_inferred": false, "started_at": "2026-05-21T00:11:24.620Z", @@ -220,7 +220,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-20T22:43:13.381Z", "resolved_inferred": false, "started_at": "2026-05-20T18:31:03.000Z", @@ -233,7 +233,7 @@ "body": "This incident has been resolved.\n\nIf you experience any further issues, please contact us at support@chainalysis.com.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-15T13:57:09.023Z", "resolved_inferred": false, "started_at": "2026-05-13T11:39:55.901Z", @@ -246,7 +246,7 @@ "body": "This incident has been resolved. \n\nReactor data is current, and transfers are processed without delays in KYT. \n\nIf you encounter further delays with BCH, please reach out to support@chainalysis.com", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-12T11:50:24.113Z", "resolved_inferred": false, "started_at": "2026-05-12T10:06:00.594Z", @@ -259,7 +259,7 @@ "body": "All affected alerts have been backfilled. \nPlease reach out to support@chainalysis.com if you have any questions.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-13T19:32:23.110Z", "resolved_inferred": false, "started_at": "2026-05-08T19:14:55.330Z", @@ -272,7 +272,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-06T02:46:02.380Z", "resolved_inferred": false, "started_at": "2026-05-06T01:23:44.708Z", @@ -285,7 +285,7 @@ "body": "Reactor data for Plasma is now up to date and stable. \n\nPlease contact support@chainalysis.com if you have any questions.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-15T17:31:54.675Z", "resolved_inferred": false, "started_at": "2026-04-23T09:29:14.397Z", @@ -298,7 +298,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-22T20:02:45.459Z", "resolved_inferred": false, "started_at": "2026-04-22T05:06:09.858Z", @@ -311,7 +311,7 @@ "body": "This issue has now been fully resolved and all Plasma data is currently up to date within Reactor \n\nIf you have any issues going forward, please reach out to support@chainalysis.co", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-20T15:30:56.721Z", "resolved_inferred": false, "started_at": "2026-04-20T07:51:18.650Z", @@ -324,7 +324,7 @@ "body": "This incident has been resolved. Please reach out to support@chainalysis.com if you have any questions.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-16T08:55:54.312Z", "resolved_inferred": false, "started_at": "2026-04-15T14:44:56.761Z", @@ -337,7 +337,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-27T20:30:21.581Z", "resolved_inferred": false, "started_at": "2026-03-27T04:47:20.545Z", @@ -350,7 +350,7 @@ "body": "Reactor experienced an outage between 15:05 UTC and 15:22 UTC. During this time, some customers may have been unable to access graphs. The issue has since been resolved.\n\nPlease contact support@chainalysis.com if you have any questions or need further assistance.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-24T17:18:47.262Z", "resolved_inferred": false, "started_at": "2026-03-24T17:18:47.171Z", @@ -363,7 +363,7 @@ "body": "This incident has been resolved. Any failed KYT transfers have now been reprocessed.\n\nPlease reach out to support@chainalysis.com if you have any questions or require further assistance.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-24T23:00:18.695Z", "resolved_inferred": false, "started_at": "2026-03-24T17:02:52.467Z", @@ -376,7 +376,7 @@ "body": "We can confirm this has now been fully resolved. \n\nIf you experience any issues at all, please reach out support@chainalysis.com", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-11T11:35:06.288Z", "resolved_inferred": false, "started_at": "2026-03-11T09:23:35.315Z", @@ -389,7 +389,7 @@ "body": "Between 4:53 UTC and 6:33 UTC, some KYT transfer processing experienced delays of up to 20 minutes.\n\nThe issue has been fully resolved, and transfer processing is operating normally.\n\nIf you continue to experience any issues, please contact support@chainalysis.com.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-10T06:56:02.696Z", "resolved_inferred": false, "started_at": "2026-03-10T06:56:02.637Z", @@ -402,7 +402,7 @@ "body": "This incident has been resolved. \n\nIf you experience any further issues, please reach out to support@chainalysis.com", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-06T03:13:59.843Z", "resolved_inferred": false, "started_at": "2026-03-06T01:30:12.247Z", @@ -415,7 +415,7 @@ "body": "Between 13:52 and 14:42 UTC, KYT transfer processing experienced delays of up to 40 minutes.\n\nThe issue has been fully resolved, and transfer processing is operating normally.\n\nIf you continue to experience any issues, please contact support@chainalysis.com.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-03T15:23:04.841Z", "resolved_inferred": false, "started_at": "2026-03-03T15:23:04.780Z", @@ -428,7 +428,7 @@ "body": "This incident has been resolved. \n\nIf you experience any further issues, please reach out to support@chainalysis.com", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-25T15:02:23.596Z", "resolved_inferred": false, "started_at": "2026-02-24T13:45:43.062Z", @@ -441,7 +441,7 @@ "body": "Due to data refreshes, we experienced delays on transfers for the Plasma Blockchain in Reactor between 14:00 UTC on February 20th and 10:00 AM on February 23rd. The team has mitigated the observed impact, and all products have up-to-date data.\n\nIf you experience any issues, please reach out to support@chainalysis.com.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-23T11:06:58.941Z", "resolved_inferred": false, "started_at": "2026-02-23T11:06:58.893Z", @@ -454,7 +454,7 @@ "body": "This incident has been resolved.\n\nIf you experience any further issues, please reach out to support@chainalysis.com", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-09T19:56:43.770Z", "resolved_inferred": false, "started_at": "2026-02-02T15:00:56.847Z", @@ -467,7 +467,7 @@ "body": "This issue has now been resolved. \n\nIf you have any issues, reach out to support@chainalysis.com", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-15T10:29:07.249Z", "resolved_inferred": false, "started_at": "2026-01-14T10:04:06.193Z", @@ -480,7 +480,7 @@ "body": "From an Engineering side this incident has been resolved and all services are operating as expected.\n\nWe have identified a final list of customers whose alerts may have been impacted and are finalising customer communications with appropriate internal stakeholders. \n\nWe will proactively reach out to any customers we believe were affected to discuss next steps.\n\nIf you experience any issues at all, please reach out to support@chainalysis.com", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-24T13:41:26.458Z", "resolved_inferred": false, "started_at": "2025-12-19T15:37:35.293Z", @@ -493,7 +493,7 @@ "body": "This incident has been resolved. Any previously failed transfers have been successfully reprocessed. If you experience any further issues, please contact support@chainalysis.com.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-19T00:41:53.209Z", "resolved_inferred": false, "started_at": "2025-12-18T21:05:59.777Z", @@ -506,7 +506,7 @@ "body": "This incident has been resolved. Any previously failed transfers have been successfully reprocessed. If you experience any further issues, please contact support@chainalysis.com.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-15T15:10:06.722Z", "resolved_inferred": false, "started_at": "2025-12-15T11:07:40.000Z", @@ -519,7 +519,7 @@ "body": "After extensive monitoring over the past few hours, we are confident that the incident has now been resolved and all our systems are operating as expected. \n\nIf you experience any issues, please reach out to support@chainalysis.com.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-05T13:17:44.547Z", "resolved_inferred": false, "started_at": "2025-12-05T09:08:48.319Z", @@ -532,7 +532,7 @@ "body": "This incident has now been resolved. If you experience any issues, please reach out to support@chainalysis.com.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-02T16:51:15.738Z", "resolved_inferred": false, "started_at": "2025-12-02T11:42:25.297Z", @@ -545,7 +545,7 @@ "body": "This incident has been resolved. Please reach out to support@chainalysis.com if you require assistance or have any questions.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-13T22:54:14.231Z", "resolved_inferred": false, "started_at": "2025-11-13T22:12:34.841Z", @@ -558,7 +558,7 @@ "body": "This incident has been resolved and all services are fully operational. \n\nCustomers may have experienced KYT API interruptions during UTC 09:09 and UTC 09:20. Please resubmit any transfers or withdrawals that did not go through during this time.\n\nIf you require further assistance, please reach out to support@chainalysis.com.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-05T11:22:28.352Z", "resolved_inferred": false, "started_at": "2025-11-05T09:22:49.574Z", @@ -571,7 +571,7 @@ "body": "This incident has been resolved. We have confirmed that all services are fully operational. \n\nShould you continue to experience any issues, please contact the Support Team at support@chainalysis.com.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-31T16:27:13.461Z", "resolved_inferred": false, "started_at": "2025-10-31T14:29:38.506Z", @@ -584,7 +584,7 @@ "body": "Polygon is now back to tip and customers should see no further delays in Polygon data in Reactor. \n\nIf you experience any further issues please reach out to support@chainalysis.com", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-05T12:48:16.436Z", "resolved_inferred": false, "started_at": "2025-10-05T11:38:28.031Z", @@ -597,7 +597,7 @@ "body": "This incident is now classed as resolved. If you see any further issues please reach out to support@chainalysis.com", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-30T15:19:08.548Z", "resolved_inferred": false, "started_at": "2025-09-30T10:28:48.369Z", @@ -610,7 +610,7 @@ "body": "The incident has been resolved. If you continue experiencing any issues, please reach out to support@chainalysis.com", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-24T02:47:55.540Z", "resolved_inferred": false, "started_at": "2025-09-24T02:24:42.321Z", @@ -623,7 +623,7 @@ "body": "This incident has been resolved.\n\nPlease reach out to support@chainalysis.com if you require any further assistance.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-19T22:49:10.932Z", "resolved_inferred": false, "started_at": "2025-09-19T18:18:20.152Z", @@ -636,7 +636,7 @@ "body": "API latencies have remained at normal levels since the earlier spike. We will continue working with our cloud providers to understand the root cause, but no further impact is expected.\n\nPlease contact support@chainalysis.com if you have any questions or need further assistance.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-17T19:00:17.095Z", "resolved_inferred": false, "started_at": "2025-09-16T09:43:55.109Z", @@ -649,7 +649,7 @@ "body": "Between 14:58 UTC and 15:14 UTC, some requests to the KYT API returned 502 errors. The issue has since been resolved.\n\nPlease contact support@chainalysis.com if you have any questions or need further assistance.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-11T16:00:23.219Z", "resolved_inferred": false, "started_at": "2025-09-11T16:00:23.170Z", diff --git a/api/v/check-point.json b/api/v/check-point.json index 579658f549fd5eb20d0b39e6b010694248524e98..2e1571a6713408ba69272f2f71add5ebb5b26d30 100644 --- a/api/v/check-point.json +++ b/api/v/check-point.json @@ -3,7 +3,7 @@ "slug": "check-point", "platform": "statuspage", "status_url": "https://status.checkpoint.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "partial", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-26T08:31:15.601Z", "resolved_inferred": false, "started_at": "2026-08-26T05:56:47.000Z", @@ -25,7 +25,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-25T18:52:38.164Z", "resolved_inferred": false, "started_at": "2026-08-25T17:34:23.544Z", @@ -38,7 +38,7 @@ "body": "This incident has been resolved.\nThe IL-1 Data Center is now fully operational, and all affected gateways have been restored to normal function.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-25T10:46:14.664Z", "resolved_inferred": false, "started_at": "2026-08-25T08:19:58.362Z", @@ -51,7 +51,7 @@ "body": "Devices wrongly appeared disconnected during this time.\nErrors appeared when attempting to create or save settings - plan / gateway.\nNo impact on existing gateways connectivity.\n\nIncident time 7:00-10:00 AM UTC.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-03T07:00:00.000Z", "resolved_inferred": false, "started_at": "2026-08-03T07:00:00.000Z", @@ -64,7 +64,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-29T15:05:07.743Z", "resolved_inferred": false, "started_at": "2026-07-29T13:43:37.720Z", @@ -77,7 +77,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-12T06:33:24.801Z", "resolved_inferred": false, "started_at": "2026-07-12T05:47:31.414Z", @@ -90,7 +90,7 @@ "body": "Root cause seem to derive from global Cellcom ISP routing issues, also reported in downdetector.co.il\nZTA were recovered when ISP on Israel-1 was switched from Cellcom.\nSome local users that uses Cellcom\\Golan Tel may still face signing in or connecting issues. Until the issue is resolved *by the ISP*, users are encouraged to use a different ISP", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-06T11:15:17.863Z", "resolved_inferred": false, "started_at": "2026-07-06T09:04:43.482Z", @@ -103,7 +103,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-05T13:10:29.056Z", "resolved_inferred": false, "started_at": "2026-07-05T12:27:22.347Z", @@ -116,7 +116,7 @@ "body": "This incident is resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-05T11:27:22.145Z", "resolved_inferred": false, "started_at": "2026-07-05T10:24:12.000Z", @@ -129,7 +129,7 @@ "body": "Incident Duration: June 29, 08:00 UTC \u2013 June 30, 09:30 UTC (~26 hours)\nAffected Services: Datatube EU Production - West Europe region\nAffected Products: CloudGuard WAF, Playblocks, XDR\n \n\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\n \nOverview\n \nOn June 29\u201330, 2026, EU production Datatube services experienced a partial degradation affecting data ingestion in the West Europe region, a small portion of events experienced delayed processing during this window. \n \n\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\n \nCustomer Impact\n \nDuring the incident window, approximately ~0.2% of total EU ingestion events were affected across products.\n \nCustomers using CloudGuard WAF, Playblocks, or XDR in the West Europe region may have experienced:\n- Delayed visibility of security events in dashboards and reports\n- Delayed data in queries covering the June 29\u201330 window\n \n\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\n \nIncident Timeline (UTC)\n \nJun 29 \u2013 08:00 First customer reports received; investigation initiated immediately, cross-team investigation mobilized across infrastructure, networking, and product teams.\n \nJun 29 \u2013 10:00 First mitigation applied - provided temporary partial relief.\n \nJun 29 \u2013 13:30 Second mitigation applied, narrowing the root cause scope further, also provided temporary partial relief.\n \nJun 29 \u2013 18:00 Issue confirmed as affecting multiple products; joint investigation continued.\n \nJun 29 \u2013 21:15 Capacity expanded to stabilize the environment and protect against further degradation.\n \nJun 30 \u2013 05:00 Final diagnostic steps executed to isolate root cause precisely.\n \nJun 30 \u2013 09:30 Root cause confirmed and resolved; all services fully restored.\n \nThe investigation required coordinated effort across multiple teams because early symptoms were consistent with several possible root causes. Each mitigation step both provided partial relief and helped narrow the diagnosis - this is standard practice to avoid introducing new risk while a production system is under stress.\n \n\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\n \nRoot Cause\n \nA misconfiguration in the EU gateway's communication protocols, which was dormant under normal operating conditions, was triggered by load introduced during routine maintenance. Once identified, the fix was straightforward and immediately effective.\n \n\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\n \nNext Steps & Action Items\n \n1. Audit and align protocol configurations across all regional gateways - to prevent recurrence in other regions.\n2. Add capacity alerting on all regional gateways - to detect such anomalies before they cause customer impact.\n3. Improve client-side monitoring to surface connection-level failures and latencies earlier.\n4. Introduce stress testing for sensitive network components as part of the change process - validating configurations in an isolated, production-like environment before and after any change to catch hidden issues before they reach production.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-29T08:00:00.000Z", "resolved_inferred": false, "started_at": "2026-06-29T08:00:00.000Z", @@ -142,7 +142,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-27T07:50:14.516Z", "resolved_inferred": false, "started_at": "2026-06-27T06:35:46.174Z", @@ -155,7 +155,7 @@ "body": "The Web SmartConsole on the Portal was unavailable for few hours, customers could work regularly with Installed SmartConsole or Streamed SmartConsole", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-21T23:00:00.000Z", "resolved_inferred": false, "started_at": "2026-06-21T23:00:00.000Z", @@ -168,7 +168,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-10T03:37:32.995Z", "resolved_inferred": false, "started_at": "2026-06-10T02:52:32.305Z", @@ -181,7 +181,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-08T16:26:06.605Z", "resolved_inferred": false, "started_at": "2026-06-08T15:27:45.939Z", @@ -194,7 +194,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-08T14:28:35.999Z", "resolved_inferred": false, "started_at": "2026-06-08T14:04:12.129Z", @@ -207,7 +207,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-08T12:46:14.801Z", "resolved_inferred": false, "started_at": "2026-06-08T12:10:22.940Z", @@ -220,7 +220,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-07T18:59:57.919Z", "resolved_inferred": false, "started_at": "2026-06-07T16:50:41.953Z", @@ -233,7 +233,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-07T14:08:18.935Z", "resolved_inferred": false, "started_at": "2026-06-07T12:40:42.931Z", @@ -246,7 +246,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-03T10:44:36.501Z", "resolved_inferred": false, "started_at": "2026-06-02T09:28:05.226Z", @@ -259,7 +259,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-01T15:06:39.878Z", "resolved_inferred": false, "started_at": "2026-06-01T13:36:23.107Z", @@ -272,7 +272,7 @@ "body": "Some customers may experience delay in logs arrival time", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-01T05:00:00.000Z", "resolved_inferred": false, "started_at": "2026-06-01T05:00:00.000Z", @@ -285,7 +285,7 @@ "body": "Users were unable to access Spark gateways through the service.\n\nThe issue was caused by recent infrastructure changes that unintentionally impacted RMD access, resulting in valid access requests being rejected.\n\nThe issue was resolved at 04:25 AM UTC.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-01T01:00:00.000Z", "resolved_inferred": false, "started_at": "2026-06-01T01:00:00.000Z", @@ -298,7 +298,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-31T12:05:41.588Z", "resolved_inferred": false, "started_at": "2026-05-31T11:48:09.616Z", @@ -311,7 +311,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-13T17:32:54.503Z", "resolved_inferred": false, "started_at": "2026-05-13T15:40:25.664Z", @@ -324,7 +324,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-27T15:52:15.790Z", "resolved_inferred": false, "started_at": "2026-04-27T14:12:42.261Z", @@ -337,7 +337,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-26T10:16:51.322Z", "resolved_inferred": false, "started_at": "2026-04-26T09:59:34.057Z", @@ -350,7 +350,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-20T11:49:32.014Z", "resolved_inferred": false, "started_at": "2026-04-20T09:40:30.282Z", @@ -363,7 +363,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-18T19:29:47.819Z", "resolved_inferred": false, "started_at": "2026-04-18T18:54:53.526Z", @@ -376,7 +376,7 @@ "body": "This incident has been resolved", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-15T15:36:37.238Z", "resolved_inferred": false, "started_at": "2026-04-15T14:11:27.551Z", @@ -389,7 +389,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-09T14:19:08.150Z", "resolved_inferred": false, "started_at": "2026-04-09T13:59:44.351Z", @@ -402,7 +402,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-07T11:33:29.467Z", "resolved_inferred": false, "started_at": "2026-04-07T06:42:51.000Z", @@ -415,7 +415,7 @@ "body": "Incident has been resolved.\n\nTimeframe: The issue started at 6:45 AM UTC and was resolved at 12:20 PM UTC.\n\nImpact: During this time, gateways failed to communicate with Spark Management and appeared disconnected in the Spark Management application.\n\nRoot Cause: An internal error caused failures in the gateway heartbeat flow due to a shared file exceeding its size limit.\n\nResolution: Proper handling and rotation mechanisms were added for this file to prevent recurrence.\n\nThe fix has been applied to all Spark Management instances across all supported regions, although the impact was limited to the EU data residency.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-27T11:59:59.395Z", "resolved_inferred": false, "started_at": "2026-03-27T10:21:40.804Z", @@ -428,7 +428,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-25T18:42:59.065Z", "resolved_inferred": false, "started_at": "2026-03-25T18:00:31.000Z", @@ -441,7 +441,7 @@ "body": "This issue has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-19T22:51:19.712Z", "resolved_inferred": false, "started_at": "2026-03-19T18:52:27.211Z", @@ -454,7 +454,7 @@ "body": "Earlier today, customers in the India region experienced connectivity issues when accessing the Harmony Endpoint Management Portal.\nDuring the incident, customers whose services were hosted in this region may have experienced:\nDifficulty accessing the Harmony Endpoint Management Portal\nConnectivity issues between Endpoint clients and the server\nThe issue started approximately 3 hours ago and has now been fully resolved.\nOur team worked with MIS to identify and address the issue, and services have returned to normal operation.\nWe apologize for the inconvenience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-16T06:49:21.867Z", "resolved_inferred": false, "started_at": "2026-03-16T06:49:21.803Z", @@ -467,7 +467,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-16T13:04:15.181Z", "resolved_inferred": false, "started_at": "2026-03-16T06:30:43.000Z", @@ -480,7 +480,7 @@ "body": "XDR detection services are operational.\nWe are still waiting for the cloud services to become operational in UAE for the portal access.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "started_at": "2026-03-03T14:31:19.102Z", "state": "identified", "title": "Infinity XDR is unavailable in UAE region", @@ -491,7 +491,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-02T17:18:24.478Z", "resolved_inferred": false, "started_at": "2026-03-02T11:01:19.609Z", @@ -504,7 +504,7 @@ "body": "We are continuing to monitor the situation as it develops.\nAWS team expects to see improvements to core services in the coming hours.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "started_at": "2026-03-02T08:07:43.426Z", "state": "identified", "title": "UAE Infinity Portal Outage", @@ -515,7 +515,7 @@ "body": "ThreatCloud AI Traffic is routed to other regions. Impacted services:\nWeb Security, URL and File Reputation services.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "started_at": "2026-03-02T07:00:48.000Z", "state": "monitoring", "title": "ThreatCloud AI services in UAE region", @@ -526,7 +526,7 @@ "body": "We are continuing to work on a fix for this issue.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "started_at": "2026-03-02T06:42:37.410Z", "state": "identified", "title": "Smart-1 Cloud is not available in UAE region", @@ -537,7 +537,7 @@ "body": "Threat Emulation and Threat Extraction experience service disruptions in the UAE due to an issue of AWS (https://health.aws.amazon.com/health/status).\nTraffic is routed to other regions.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "started_at": "2026-03-01T20:30:47.000Z", "state": "monitoring", "title": "SandBlast Threat Emulation & Threat Extraction services - UAE region", @@ -548,7 +548,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-01T20:41:25.193Z", "resolved_inferred": false, "started_at": "2026-03-01T19:04:13.039Z", @@ -561,7 +561,7 @@ "body": "We are continuing to monitor for any further issues.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "started_at": "2026-03-01T17:13:28.090Z", "state": "monitoring", "title": "Harmony Endpoint \u2013 Temporary Service Disruption in UAE (United Arab Emirates) Region", @@ -572,7 +572,7 @@ "body": "Harmony Mobile UAE - Operational Issues\nIssue with infrastructure of unknown origin at this point - being investigated", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "started_at": "2026-03-01T13:05:44.326Z", "state": "investigating", "title": "Harmony Mobile UAE - Operational Issues", @@ -583,7 +583,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-01T11:04:26.454Z", "resolved_inferred": false, "started_at": "2026-03-01T08:57:49.278Z", @@ -596,7 +596,7 @@ "body": "We are currently investigating this issue.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "started_at": "2026-03-01T08:52:26.650Z", "state": "investigating", "title": "Customers may experience logs delay", @@ -607,7 +607,7 @@ "body": "Final Update: macOS Tahoe 26.3 Compatibility Issue\nWe have completed our investigation into the macOS Tahoe 26.3 compatibility issue affecting a limited subset of devices running Harmony Endpoint Threat Prevention blades.\n\nThe root cause has been identified, and recovery and mitigation steps are now available.\n\nCustomers who upgraded to macOS Tahoe 26.3 and are experiencing boot issues should follow the guidance in SecureKnowledge article SK184676:\nhttps://supportcenter.checkpoint.com/supportcenter/portal?solutionid=sk184676\n\nDevices that have not yet upgraded to macOS Tahoe 26.3 should wait for a forthcoming Harmony Endpoint update before proceeding with the OS upgrade.\n\nOur engineering teams are preparing an updated client version to fully address the compatibility change introduced in macOS Tahoe 26.3.\n\nThis incident is now considered mitigated. For additional assistance, please contact Check Point Support and reference SK184676.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-12T23:19:08.494Z", "resolved_inferred": false, "started_at": "2026-02-12T14:54:50.024Z", @@ -620,7 +620,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-10T22:37:27.204Z", "resolved_inferred": false, "started_at": "2026-02-10T21:55:42.737Z", @@ -633,7 +633,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-10T15:54:59.935Z", "resolved_inferred": false, "started_at": "2026-02-10T15:39:26.241Z", diff --git a/api/v/chromatic.json b/api/v/chromatic.json index ef568ccde79c2665942e835dbd9e5da1f87e60f6..08467eeced375a17679350315e72348bb4a0f5b9 100644 --- a/api/v/chromatic.json +++ b/api/v/chromatic.json @@ -3,7 +3,7 @@ "slug": "chromatic", "platform": "betterstack", "status_url": "https://status.chromatic.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": false, "first_watched": "2026-09-04T07:06:16Z", diff --git a/api/v/cint.json b/api/v/cint.json index 6e9a99a0149a484d5ee78e3cc047097c5c9a1047..4ae7a85ab420faa53f00507b0a7e2d0ee1d9d474 100644 --- a/api/v/cint.json +++ b/api/v/cint.json @@ -3,7 +3,7 @@ "slug": "cint", "platform": "statuspage", "status_url": "https://status.cint.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "After monitoring system stability over the last few hours, we can confirm the issue is resolved. Report generation and email delivery are functioning normally. If you continue to experience any problems, please contact our Support team.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-25T21:24:09.318Z", "resolved_inferred": false, "started_at": "2026-08-25T09:41:12.541Z", @@ -25,7 +25,7 @@ "body": "We experienced a period of degraded performance affecting the respondent experience. Respondents may encounter errors or longer load times when attempting surveys, and Marketplace/Cint Exchange users may encounter errors when testing the respondent flow. This issue occurred between 2026/08/18 09:01 UTC and 09:12 UTC and is now resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-18T09:52:28.319Z", "resolved_inferred": false, "started_at": "2026-08-18T09:52:28.280Z", @@ -38,7 +38,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-02T19:30:02.104Z", "resolved_inferred": false, "started_at": "2026-07-02T09:52:23.688Z", @@ -51,7 +51,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-28T18:43:08.194Z", "resolved_inferred": false, "started_at": "2026-04-28T18:20:48.802Z", @@ -64,7 +64,7 @@ "body": "This issue has been resolved. Please reach out to our Support team if you're still experiencing any issues.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-19T17:41:26.211Z", "resolved_inferred": false, "started_at": "2026-02-19T15:12:07.250Z", @@ -77,7 +77,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-11T19:33:15.695Z", "resolved_inferred": false, "started_at": "2026-02-11T17:20:01.164Z", @@ -90,7 +90,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-22T00:36:47.880Z", "resolved_inferred": false, "started_at": "2026-01-21T21:06:05.546Z", @@ -103,7 +103,7 @@ "body": "This issue has been resolved. To ensure the integrity of our services, we are monitoring the state of the Lucid Measurement Dashboard and the Lucid Measurement API. Please reach out to our Support team if you're still experiencing any issues.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-13T16:04:12.650Z", "resolved_inferred": false, "started_at": "2025-11-13T15:19:37.579Z", @@ -116,7 +116,7 @@ "body": "This issue has been resolved. Please reach out to our Support team if you're still experiencing any issues. ( if any, specify actions users need to take as a result of the issue to resume normal activity )", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-30T05:15:03.187Z", "resolved_inferred": false, "started_at": "2025-10-29T17:16:05.918Z", @@ -129,7 +129,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-28T11:19:37.606Z", "resolved_inferred": false, "started_at": "2025-10-28T09:17:42.617Z", @@ -142,7 +142,7 @@ "body": "This issue has been resolved. All impacted Lucid Measurement study results have now been reprocessed and should be visualizing.\nWe have identified the root cause and are working to ensure this does not happen again going forward. Thank you for your patience! Please reach out to our Support team if you're still experiencing any issues.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-28T20:25:06.922Z", "resolved_inferred": false, "started_at": "2025-10-27T19:23:08.701Z", @@ -155,7 +155,7 @@ "body": "This issue has been resolved. Please reach out to our Support team if you're still experiencing any issues.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-21T02:31:33.000Z", "resolved_inferred": false, "started_at": "2025-10-20T18:02:54.534Z", @@ -168,7 +168,7 @@ "body": "The incident has been resolved. We will continue to monitor stability across all systems. If you encounter any issues, please contact our Support team immediately.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-20T10:52:12.902Z", "resolved_inferred": false, "started_at": "2025-10-20T10:13:58.000Z", @@ -181,7 +181,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-28T15:13:51.471Z", "resolved_inferred": false, "started_at": "2025-08-28T13:18:35.915Z", diff --git a/api/v/circle-ci.json b/api/v/circle-ci.json index 38a94f1753e7dd2da6db5581c7c8782a6cdab291..7b92ae5530e5ade23330cce6b3de4a17c3047912 100644 --- a/api/v/circle-ci.json +++ b/api/v/circle-ci.json @@ -3,7 +3,7 @@ "slug": "circle-ci", "platform": "statuspage", "status_url": "https://status.circleci.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-26T16:10:23.938Z", "resolved_inferred": false, "started_at": "2026-08-26T15:43:38.082Z", @@ -25,7 +25,7 @@ "body": "Between 19:49 UTC and 21:07 UTC on August 25, 2026, customers attempting to log in to CircleCI using GitHub were unable to sign in, and received an error from GitHub stating the callback URL was invalid. Customers who were already logged in were not affected. The issue has been resolved and GitHub login is functioning normally. We thank you for your patience while our team worked on implementing a fix.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-25T20:00:00.000Z", "resolved_inferred": false, "started_at": "2026-08-25T20:00:00.000Z", @@ -38,7 +38,7 @@ "body": "Insights data is good once more. Thank you for your patience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-17T21:37:03.148Z", "resolved_inferred": false, "started_at": "2026-08-17T21:06:09.742Z", @@ -51,7 +51,7 @@ "body": "GitHub's APIs appear to be operating normally.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-17T19:05:30.477Z", "resolved_inferred": false, "started_at": "2026-08-17T14:04:21.229Z", @@ -64,7 +64,7 @@ "body": "Following planned maintenance that ended at 13:00 UTC on August 15, some impact to job processing continued for approximately 30 minutes beyond the window we announced.\n\nSome customers continued to see delays in jobs starting, along with a small number of jobs failing with infrastructure errors, until approximately 13:30 UTC.\n\nThis has been resolved and job processing has returned to normal. Customers whose jobs failed during this window may rerun affected jobs. We thank you for your patience while our team worked on implementing a fix and apologize for any inconvenience the extended impact may have caused.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-15T17:00:00.000Z", "resolved_inferred": false, "started_at": "2026-08-15T13:58:54.814Z", @@ -77,7 +77,7 @@ "body": "The issue impacting customers who use GitHub as their VCS while GitHub was undergoing a service degradation (https://www.githubstatus.com/incidents/76t89hbfb09h) has now been resolved. GitHub has resolved the underlying issue and the affected functionality has returned to normal. \n\nWe thank you for your patience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-12T16:43:37.854Z", "resolved_inferred": false, "started_at": "2026-08-12T16:33:41.163Z", @@ -90,7 +90,7 @@ "body": "Between 13:50 UTC and approximately 17:30 UTC on August 11, 2026, some customers experienced delays of up to an hour in pipeline status updates and in notification delivery. \n\nBetween 16:40 UTC and 17:00 UTC within that same window, a small number of customers also saw newly created pipelines fail to process, appearing in an errored state in the UI and API. \n\nThe issue has been resolved and all affected functionality has returned to normal. Customers whose pipelines errored during that window can retrigger them. \n\nWe thank you for your patience while our team worked on implementing a fix.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-11T18:00:00.000Z", "resolved_inferred": false, "started_at": "2026-08-11T17:42:47.509Z", @@ -103,7 +103,7 @@ "body": "The Usage API issue has been resolved. Data has been loaded for yesterday, 8/5/2026. We appreciate your patience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-06T19:54:25.375Z", "resolved_inferred": false, "started_at": "2026-08-06T13:06:17.519Z", @@ -116,7 +116,7 @@ "body": "The upstream issue has been resolved, and the insights data from the last 24 hours has caught up. Thank you for your patience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-05T21:01:12.564Z", "resolved_inferred": false, "started_at": "2026-08-05T16:58:27.652Z", @@ -129,7 +129,7 @@ "body": "Queue times for Android and Windows jobs have reduced significantly over the last hour. You may still notice brief, isolated queuing at times, but this is no longer at incident-level impact. This was related to capacity constraints with a third-party infrastructure provider. We thank you for your patience while we monitored the situation. If you have any issues, please reach out to our Support team.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-04T23:40:23.795Z", "resolved_inferred": false, "started_at": "2026-08-04T19:27:28.000Z", @@ -142,7 +142,7 @@ "body": "The issue impacting customers who use GitHub as their VCS while GitHub was undergoing a service degradation (https://www.githubstatus.com/incidents/yjysg0xrl67m) has now been resolved. GitHub has resolved the underlying issue and the affected functionality has returned to normal. \n\nWe thank you for your patience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-24T17:41:31.000Z", "resolved_inferred": false, "started_at": "2026-07-24T16:35:44.272Z", @@ -155,7 +155,7 @@ "body": "Between 19:24 UTC on 22 July and 01:50 UTC on 23 July, customers using the gen3 preview machine (Linux VM) resource classes experienced delays and, in some cases, jobs failing to start. We have removed the gen3 resource classes while we address stability issues affecting them. Unfortunately, workflows that we were unable to provision compute capacity for during this period were cancelled. Affected customers should change their resource class from gen3 to gen2 and rerun those workflows. \n\nWe thank you for your patience while our team worked to resolve this.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-23T02:05:30.377Z", "resolved_inferred": false, "started_at": "2026-07-22T19:57:15.421Z", @@ -168,7 +168,7 @@ "body": "Between 03:18 UTC and 06:04 UTC on July 22, 2026, a subset of customers were unable to access app.circleci.com. The issue has been resolved and access has returned to normal. \n\nWe thank you for your patience while our team worked on implementing a fix.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-22T06:27:34.150Z", "resolved_inferred": false, "started_at": "2026-07-22T06:13:48.941Z", @@ -181,7 +181,7 @@ "body": "## Summary\n\nOn July 20, 2026 from 00:22 to 01:45 UTC, CircleCI customers using our GitHub integrations experienced failures running pipelines and experienced workflows getting stuck. During this incident, some pipelines triggered by users using GitHub failed to start or ran as error pipelines. Customers whose pipelines failed or ran as error pipelines during this window should re-run them.\n\nThis was caused by an [upstream API degradation at GitHub](https://www.githubstatus.com/incidents/ph5nns5y4gxj), which impacted many GitHub APIs that CircleCI uses to trigger and run pipelines.\n\nBy 01:45 UTC, GitHub APIs recovered, and customer pipelines ran normally.\n\nThe original CircleCI status page can be found [here](https://status.circleci.com/incidents/9lvbbbs9l87b).\u00a0\n\n## What Happened\n\n\\(all times UTC\\)\n\nBeginning\u00a000:22\u00a0on July 20, 2026, GitHub began returning elevated errors for the following API requests:\n\n* `applications/*/token`\n* `repos/*/commits`\n* `repos/*/*/contents/*`\n* `repos/*/*/hooks`\n* `repos/*/*/hooks/*`\n* `repos/*/*/keys`\n* `repos/*/*/pulls`\n* `repos/*/*/statuses/*`\n\nCircleCI relies on these requests to correctly trigger and run pipelines.\n\nAt 00:22, our internal monitoring alerted us to the problem. Our team began investigating, and found that a small number of pipelines belonging to GitHub projects either failed to start or ran as error pipelines. This included scheduled pipelines and workflows. In addition, a small number of customer workflows experienced stuck jobs and required a re-run of the workflow to fix.\n\nAt\u00a001:45, GitHub recovered and pipeline processing returned to normal operating levels. Only pipelines triggered during the incident window were affected, and customers should re-run those pipelines.\n\n## Future Prevention and Process Improvement\n\nWe are actively working to improve the resilience of pipeline processing during GitHub service disruptions to reduce the customer impact of similar incidents in the future. We are scoping features that will help customers recover with reduced manual steps after incidents resolve.\n\nCustomer experience is our top priority, and we commit to continually improving the reliability of our systems to match the trust that our customers place in us. Please reach out to our support team with any questions or concerns.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-20T01:45:35.921Z", "resolved_inferred": false, "started_at": "2026-07-20T00:35:59.020Z", @@ -194,7 +194,7 @@ "body": "An incident affecting GitHub's API caused CircleCI customers to experience errors loading the web app and signing in, along with pipelines and scheduled workflows failing to start or running late. GitHub has resolved the underlying incident (https://www.githubstatus.com/) and all affected functionality has returned to normal.\n\nCustomers whose jobs or pipelines failed may rerun them. Scheduled pipelines and workflows that were missed during the incident will not run automatically and will need to be re-triggered.\n\nWe thank you for your patience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-17T00:26:36.776Z", "resolved_inferred": false, "started_at": "2026-07-16T23:04:18.952Z", @@ -207,7 +207,7 @@ "body": "On July 13 between 15:30 UTC and 22:40 UTC, we experienced delays starting jobs on Docker (Gen 2) resource classes due to capacity constraints from our cloud provider. The same issue recurred on July 14 between 15:45 UTC and 22:50 UTC.\n\nDelays reached up to 25 minutes on July 13 and up to 24 minutes on July 14. The medium+ and 2 X-large+ resource classes saw the longest waits. Earlier updates in this incident reported figures based on average wait times, which didn't reflect the maximum impact some customers may have experienced.\n\nWait times have now returned to normal. We are continuing to work with our cloud provider to add capacity ahead of the next peak period. Thank you for your patience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-15T00:32:55.545Z", "resolved_inferred": false, "started_at": "2026-07-14T22:54:42.726Z", @@ -220,7 +220,7 @@ "body": "## Summary\n\nFrom 01:33 UTC to 05:18 UTC on July 14, 2026, customers with a Bitbucket-linked identity were unable to log in to CircleCI, and some customers experienced workflows that failed to start or update, due to a change in how Bitbucket's OAuth service reports account permissions. At 05:07 UTC, we deployed a fix that corrected how our systems read the updated permissions field. Some customers needed to log out and re-authenticate their Bitbucket integration after we deployed the fix. Our systems continued processing the backlog of affected jobs until 08:39 UTC.\n\nWe thank our customers for their patience as we resolved this incident. Please reach out to our support team with any questions or concerns.\n\nThe status page for this incident can be found [here](https://status.circleci.com/incidents/gsyjwybg477g).\n\n## Background\n\nCircleCI supports logging in with a GitHub account, a Bitbucket account, or an email and password. When a customer logs in with a Bitbucket-linked identity, or when CircleCI needs to refresh the customer's access on their behalf, we exchange an authorization token with Bitbucket's OAuth service. This exchange includes a list of the permissions, or \"scopes,\" the customer has granted us, which Bitbucket and CircleCI use to confirm what CircleCI is authorized to do on the customer\u2019s behalf.\n\n## What Happened\n\n\\(All times UTC\\)\n\nOn April 8, 2026, [Bitbucket announced a change to its OAuth service](https://developer.atlassian.com/cloud/bitbucket/changelog/#CHANGE-3139): it would be renaming the field used to report a customer's granted permissions. Bitbucket ran a transition period during which both the old and new field names were available, then fully removed the old field name on May 4, 2026. Our systems had not been updated to recognize the new field name, so once Bitbucket fully phased out the old one, requests that depended on it began to fail.\n\nAt 01:33 on July 14, 2026, our systems began failing to process permissions information returned for Bitbucket-linked accounts, because our systems still expected the old permissions structure. This caused login attempts for all Bitbucket-linked accounts to fail, including for customers who log in with GitHub but have a Bitbucket identity linked to their account.\n\nAt 01:59, automated monitoring alerted our engineering team to a spike in errors on the affected systems. The team began investigating immediately, confirmed customer impact at 02:38, and alerted customers via our status page at 02:51. By 03:00, the team had isolated the failures to the renamed Bitbucket field.\n\nBeginning at 03:17, workflow status updates for Bitbucket pipelines belonging to customers with an expired access token began to be dropped. The Bitbucket permissions check is used broadly across our platform, and these permissions failures also affected some of our internal job-processing systems. This caused a subset of workflows to become stuck without a final status, and caused some pull requests to show missing or stuck status checks.\n\nAt 04:21, the team deployed an initial fix that resolved the underlying issue, restoring the login flow and returning our internal permissions system to normal operation. Some affected customers needed to log out and log back in to pick up the fix. By 05:07, the team deployed two additional fixes so our systems would begin accepting Bitbucket's new permissions field format going forward. We resolved the incident at 05:18.\n\nSome customers did need to log out and re-authenticate their Bitbucket integration before their account fully recovered. Our systems continued processing a backlog of affected jobs, returning to normal levels by approximately 08:39.\n\n## Future Prevention and Process Improvement\n\nWe are taking the following steps to prevent a recurrence and improve our response time:\n\n**We are hardening our authorization code against upstream API changes.** This incident happened because our system did not gracefully handle a renamed field in a response from a third-party identity provider. We will be immediately updating our authorization code so that unexpected or missing fields from GitHub, Bitbucket, and GitLab are handled safely.\n\n**We are improving how we track upstream provider changes.** We currently already monitor changelogs from our identity providers for exactly this kind of breaking change, but we didn't add this particular provider change to our monitoring in time to catch it before it shipped. We are auditing and expanding this monitoring so provider announcements reach our team before they affect customers.\n\n**We are improving how we classify and communicate incidents in their earliest minutes.** This incident's initial classification did not immediately reflect its customer-facing severity. We are refining our incident tooling and guidance to help engineers identify and communicate customer impact more quickly.\n\n**We are improving the resilience of our workflow-processing pipeline.** A downstream failure in this incident caused some workflow status updates to be dropped rather than retried or clearly surfaced. We are reviewing this system's retry and error-handling behavior so similar downstream failures are more visible and easier to recover from.\n\nCustomer experience is our top priority, and we commit to continually improving the reliability of our systems to match the trust that our customers place in us. Please reach out to our support team with any questions or concerns.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-14T05:15:18.525Z", "resolved_inferred": false, "started_at": "2026-07-14T02:49:37.834Z", @@ -233,7 +233,7 @@ "body": "## Summary\n\nFrom 18:00 UTC on July 13, 2026 to 23:18 UTC on July 14, 2026, some customers running jobs on CircleCI's macOS fleet experienced jobs that hung or failed to progress during GitHub fetch steps. For these customers, GitHub fetch steps which would ordinarily take 1-2 minutes took 20-30 minutes, and timed out. The issue was caused by a capacity and routing problem on the network path between our Mac infrastructure provider and GitHub, and the associated intermittent networking issues slowed down fetches from GitHub. During the entire incident, our team worked directly with our Mac infrastructure provider to identify and reroute traffic away from the affected network paths. We resolved an initial occurrence at 19:40 UTC on July 13. The issue recurred at 21:52 UTC that same day, we reopened the incident, and it was fully resolved by 23:18 UTC on July 14.\n\nOur macOS fleet had a similar issue several weeks ago. From 20:18 UTC on June 24, 2026 to 03:09 UTC on June 25, 2026, customers experienced a [similar incident](https://status.circleci.com/incidents/gvysjmkf4ct9) affecting the ability of macOS jobs to reach GitHub. That incident was also caused by a network routing problem in our Mac infrastructure provider.\n\nWe thank our customers for their patience while we worked through this incident. Please see below for specific actions which CircleCI and our Mac infrastructure provider will be taking. Please reach out to our support team with any questions or concerns.\n\nThe status pages for this incident can be found [here](https://status.circleci.com/incidents/n1tc2lw9q7l0) and [here](https://status.circleci.com/incidents/7cnl777wp9qz).\n\n## Background\n\nCircleCI's macOS jobs are hosted on a third-party Mac infrastructure provider. That provider connects to the broader internet, including services like GitHub, over multiple redundant upstream network paths. When one of those paths is experiencing reduced capacity or a routing problem, jobs that are fetching code or dependencies from a destination along that network path can slow down or hang intermittently, even when CircleCI's own platform, the third-party infrastructure provider, and the destination service are all operating normally.\n\n## What Happened\n\n_\\(All times UTC\\)_\n\nAt 18:00 on July 13, some customers running macOS jobs began experiencing intermittent failures and delays fetching code and dependencies from GitHub. We opened an investigation and alerted our customers via our status page at 18:55. By 19:04, our Mac infrastructure provider identified increased latency on one of its network paths and rerouted traffic around it. Fetch times recovered, and we moved the incident to `Monitoring` at 19:29, and to `Resolved` at 19:40.\n\nAt 20:44 UTC, customers reported that the issue had returned. We reopened the incident and updated our status page to `Investigating` at 21:52. Over the following two hours, we worked closely with our infrastructure provider to gather diagnostic data in an effort to isolate the affected network path. In the meantime, we published guidance recommending that customers increase their `no_output_timeout` setting to 15\u201320 minutes, to allow more time for GitHub fetches to complete during the intermittent slowdowns, and moved the status page to `Monitoring` at 23:35.\n\nAfter publishing the workaround guidance at 23:35 UTC on July 13, we expected the underlying network issue to improve overnight. It did not. At 13:59 UTC on July 14, we confirmed that customers were still experiencing intermittent failures and moved the status page back to `Investigating`. Our engineering team reproduced the failure directly using our own testing tools, which helped confirm this was a general `git-fetch` issue rather than something specific to any particular build tool, container image, or software update. At 15:35, we updated the status page to share that our infrastructure provider was testing changes to its network configuration to isolate the source of the issue. At 16:31, we updated the status page again to share that we'd identified the cause as reduced inbound bandwidth on a specific route, and that we were working with our provider to shift traffic to a different route. At 16:36, our infrastructure provider identified the affected network paths and shifted traffic away from them, fetch times recovered, and at 16:58, we updated the status page to `Monitoring`.\n\nBy early afternoon, some customers were again seeing slow fetch times, and we moved the status page back to `Investigating` at 20:18. Our infrastructure provider identified two additional network paths with degraded performance and shifted traffic away from them by 22:07. Fetch times stabilized over the following hour, and we marked the incident `Resolved` at 23:18.\n\nIn total, customers running Mac jobs may have experienced intermittent job slowdowns or failures for portions of the window between 18:00 UTC on July 13 and 23:18 UTC on July 14. Our infrastructure provider has since reported clean test results across its network and believes the underlying capacity issue originated further upstream, closer to GitHub, rather than within its own network. We are continuing to monitor this closely.\n\n## Future Prevention and Process Improvement\n\nWe are taking the following steps to prevent a recurrence and improve our response time:\n\n**We are building additional automated monitoring for macOS fleet GitHub-fetch performance.** Our extensive automated monitoring did not catch this incident. We are now adding end-to-end monitoring for GitHub fetches in particular, in order to detect similar issues proactively.\n\n**We are working directly with our Mac infrastructure provider on faster, more proactive detection.** We are asking our provider to build monitoring that can detect a degraded network path and reroute around it automatically, rather than relying on CircleCI to identify and request a reroute during an active incident.\n\n**We are turning the diagnostic tooling we built during this incident into a standing capability.** This will let us detect and reproduce this class of network failure on demand going forward, rather than assembling test infrastructure during an active incident.\n\n**We are reviewing our incident response process for a sufficient confirmation window before marking a network-related incident Resolved.** This incident briefly recurred after an early, premature resolution; we are formalizing a minimum period of confirmed-clean monitoring before closing incidents of this type. We will continue to provide regular updates along the way as investigation and remediation continues.\n\n**We are actively moving from a single provider for Mac infrastructure** **to multiple providers.** This will allow CircleCI to route incoming customer workloads to the most available and best-performing provider.\n\nCustomer experience is our top priority, and we commit to continually improving the reliability of our systems to match the trust that our customers place in us. Please reach out to our support team with any questions or concerns.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-14T23:18:34.925Z", "resolved_inferred": false, "started_at": "2026-07-13T21:52:02.888Z", @@ -246,7 +246,7 @@ "body": "We've confirmed the fix with our infrastructure provider and successful tests on our end. If customers continue to see any failed runs, please run again for a successful connection and reach out to Support if any further issues.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-13T19:40:22.542Z", "resolved_inferred": false, "started_at": "2026-07-13T18:55:54.301Z", @@ -259,7 +259,7 @@ "body": "## Summary\n\nOn July 2, 2026, from 15:12 UTC to 16:44 UTC, some CircleCI customers experienced failures starting pipelines and difficulty accessing the CircleCI UI, including an inability to log in. Customers triggering pipelines via the API may also have had pipelines fail to run.\n\nThe incident originated from a combination of internal maintenance and customer-initiated project deletions running concurrently, which caused elevated load on a data service. The connection layer between our API and that data service was not configured to time out slow responses under the elevated load conditions seen during this incident. This eventually exhausted available threads and prevented the request routing layer from handling any other requests, resulting in customer-facing errors.\n\nThe affected services were scaled up and the internal maintenance job was canceled to reduce pressure, allowing all affected functionality to return to normal. Customers whose jobs failed during this window may rerun affected jobs. A small number of customers may still see workflows that appear to be running; this is actively being corrected and does not impact billing.\n\nWe thank you for your patience while our team worked on implementing a fix.\n\n## What Happened\n\n\\(all times UTC\\)\n\nAt 13:30 on July 2, 2026, as part of normal platform maintenance, our engineering team began a data deletion job, divided into several hundred individual maintenance tasks. At 14:40, unrelated to our platform maintenance, a significant number of customer project deletion requests were received and began executing.\n\nAt 15:12, the combined load from the maintenance tasks and the customer-driven projection deletions caused an internal data service to slow down, and this began cascading into our API layer. Because connections between the API layer and the workflows data service were not configured to time out slow responses under elevated load conditions, the API-handling components became overwhelmed, went unresponsive, and began failing their health checks. This caused our request routing layer to lose available upstream requests, resulting in customers seeing errors when attempting to access the UI, to log in via GitHub or Bitbucket OAuth, or to start pipelines.\n\nAt 15:16, our monitoring systems alerted and engineers were paged. The team investigated and confirmed the source of the elevated load. At 15:30 Engineers began to scale up the affected services and cancelled a long-running maintenance task to drain the load. The team noted signs of that the system was recovering around 16:12 and adjusted the status to monitoring at 16:24.\n\nAt 16:44, the team confirmed that all customer-facing services had recovered to normal operating levels. Background load from the deletion job drained by approximately 17:00. Following the incident, we discovered a small number of workflows continued to inaccurately report that they were in a running state. This should be corrected within the next few days. In all cases, customers will only be billed for actual compute time used.\n\n## Future Prevention and Process Improvement\n\nOur team is implementing the following improvements as a result of this incident:\n\n* After the incident was resolved we added timeout protections on connections between our API layer and internal data services, so that slow responses from a downstream service cannot exhaust API worker capacity.\n* We are actively investigating ways to enforce resource limits on background data tasks to prevent them from impacting customer-facing services.\n* We are improving observability and alerting on the affected data service so that resource pressure is detected earlier, before it reaches a level that impacts customers.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-02T16:44:04.676Z", "resolved_inferred": false, "started_at": "2026-07-02T15:25:28.360Z", @@ -272,7 +272,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-29T16:58:09.761Z", "resolved_inferred": false, "started_at": "2026-06-29T10:23:34.607Z", @@ -285,7 +285,7 @@ "body": "We observed a surge in demand for Xcode 26.6 and have since mitigated the incident by increasing the available capacity for that Xcode version. Customers may have seen jobs queueing for ~10-15 mins.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-26T15:00:00.000Z", "resolved_inferred": false, "started_at": "2026-06-26T15:00:00.000Z", @@ -298,7 +298,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-25T23:03:58.327Z", "resolved_inferred": false, "started_at": "2026-06-25T22:44:15.737Z", @@ -311,7 +311,7 @@ "body": "We are concluding this incident based on a confirmed fix with our infrastructure provider and successful tests. For any customers seeing failed runs, please run again for a successful connection.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-25T03:06:41.792Z", "resolved_inferred": false, "started_at": "2026-06-24T23:13:45.020Z", @@ -324,7 +324,7 @@ "body": "## Summary\n\nOn Tuesday, June 23, 2026, our engineering team identified that a single Docker job cluster was operating below expected performance levels. Our infrastructure is organized into routing groups, each responsible for handling a specific segment of traffic, and this cluster was the sole member of its group. To address the performance issue, they initiated a standard two-step procedure to safely take it out of rotation: first, update the routing configuration to stop directing traffic to the cluster, then take it offline.\n\nWhen the team moved to take the cluster offline, the first step of the procedure was skipped. The cluster was removed from the available pool, but the routing configuration was not updated, meaning traffic continued to be directed to the routing group even though it had no capacity to process work. With no other clusters in the routing group to absorb the traffic, affected jobs had nowhere to go and began queuing rather than starting. This is a routine and safe operation when the two-step procedure is followed correctly, this incident exposed a gap in our tooling that allowed the procedure to be completed out of order.\n\nThe issue began at approximately 17:25 UTC and was fully resolved by 19:46 UTC, for a total impact window of roughly 2 hours and 20 minutes. Only Docker jobs were affected; other job types, including machine and macOS jobs, continued to operate normally.\n\nBeyond the missed step, several factors extended the impact window. An automated alert fired within a minute of the change deploying, but was dismissed as expected behavior. This delayed detection by nearly an hour. When engineers attempted to accelerate recovery by restoring a prior known-good version, they encountered unexpected issues with the rollback process, adding further delay before the fix could be deployed.\n\nThe original status page for this incident can be found [here](https://status.circleci.com/incidents/rp9y8kszn25j).\n\n## How Job Routing Works\n\nCircleCI uses Nomad as its job scheduling system for Docker-based jobs. When a job is triggered, it is routed to one of several Nomad clusters, organized into routing groups each responsible for handling a specific segment of traffic. This multi-cluster architecture is intentional: clusters are isolated from one another so that an issue in one does not impact the others, limiting blast radius and improving overall resiliency. Under normal circumstances, if a cluster becomes unavailable, traffic is automatically rerouted to the remaining operational clusters in its routing group, allowing jobs to continue without interruption.\n\n## What Happened\n\n\\(All times UTC\\)\n\nPrior to the incident, our engineering team identified that a single Docker job cluster was operating below expected performance levels. Our infrastructure is organized into routing groups, each responsible for handling a specific segment of traffic, and this cluster was the sole member of its group. To address the performance issue, they initiated a standard two-step procedure to safely take it out of rotation.\n\nAt 16:58, our engineering team applied a configuration change to remove the affected cluster from service. The first step of the two-step procedure was missed. The cluster was removed from the available pool, but the routing configuration was not updated, leaving traffic still being directed to a routing group with no capacity to process it.\n\nWhen the configuration change was fully deployed at 17:25, the affected jobs began to queue.\n\nAt 17:26, our monitoring alerted us to reduced job throughput on the affected cluster. Because throughput on that cluster was expected to drop as part of the cluster rotation procedure, the alert was interpreted as expected behavior and no action was taken.\n\nBy 18:19, a series of customer support tickets made clear that something beyond expected behavior was occurring. A formal incident was declared at 18:28 and engineers began investigating.\n\nBy 18:33, the team confirmed the impact was isolated to a subset of Docker jobs and identified a large backlog of queued jobs. At 18:41, a fix was merged to restore the affected cluster back into the available pool. Deployment of that fix was delayed because the CI smoke tests assume functioning clusters, leading to some rework of the pipeline itself. In parallel, the team attempted to accelerate recovery at 18:54 by restoring a prior known-good configuration directly, but encountered a conflict that left multiple active versions running simultaneously, preventing a clean rollback. The fix was fully deployed at 19:20 and Docker jobs began processing again.\n\nBy 19:28, the team confirmed the backlog was actively clearing and newly submitted jobs were starting at normal times.\n\nCustomers who had accumulated queued jobs during the incident period may have experienced a surge in concurrent job starts upon recovery, potentially hitting plan concurrency limits, which would have resulted in jobs still queueing while we processed the backlog.\n\nIn total, the period during which Docker jobs were unable to start lasted from approximately 17:25 to 19:20, roughly 1 hour and 55 minutes. The additional time from 19:20 to 19:46 was spent processing the accumulated backlog, during which some previously queued jobs completed with elevated wait times.\n\n## Future Prevention and Process Improvement\n\nWe are taking the following steps to prevent a recurrence and improve our response time:\n\n**We are strengthening our failover architecture.** Our multi-cluster design is built for resiliency, and while automatic failover mechanisms are already in place, this incident exposed a gap in our safeguards. We are closing that gap to ensure traffic is rerouted to healthy clusters across routing groups regardless of whether a cluster goes down unexpectedly or is intentionally taken offline.\n\n**We are enhancing our cluster rotation procedure.** This incident was possible because our tooling allowed an invalid state to exist, a cluster removed from the available pool while the routing configuration still directed traffic to it. We are updating this tooling to enforce that routing configuration and cluster availability are always updated together, and that the procedure cannot be completed out of order.\n\n**We are improving our monitoring and alerting.** The automated alert that fired during this incident was dismissed because it appeared consistent with the operation being performed. We are improving our monitoring so that unexpected side effects are surfaced clearly and are not confused with expected behavior.\n\n**We are improving our rollback capabilities.** During the incident, our team encountered delays when attempting to deploy the fix. We are auditing our deployment configurations to ensure that rollbacks can be executed more quickly and reliably during incidents.\n\nReliability is our top priority, and we are committed to ensuring that infrastructure upgrades like this one are executed with the appropriate safeguards in place.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-23T19:58:24.368Z", "resolved_inferred": false, "started_at": "2026-06-23T18:34:35.096Z", @@ -337,7 +337,7 @@ "body": "Customers using Bitbucket as their VCS provider or as their login provider experienced errors when interacting with Bitbucket repositories and authenticating to CircleCI. This was caused by an incident with Atlassian Bitbucket's OAuth service, which has now been resolved and all affected functionality has returned to normal.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-12T00:18:31.301Z", "resolved_inferred": false, "started_at": "2026-06-11T21:31:49.306Z", @@ -350,7 +350,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-10T23:07:35.612Z", "resolved_inferred": false, "started_at": "2026-06-10T22:39:15.430Z", @@ -363,7 +363,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-10T16:41:14.512Z", "resolved_inferred": false, "started_at": "2026-06-10T16:30:49.849Z", @@ -376,7 +376,7 @@ "body": "Between 13:29 UTC and 18:20 UTC on June 9, 2026, some customers experienced 500 errors when making requests to the pipeline values and workflow API endpoints, as well as errors in the UI. Jobs running were not impacted during this window. The issue has been resolved and all affected functionality has returned to normal. We thank you for your patience while our team worked on implementing a fix.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-09T18:43:23.042Z", "resolved_inferred": false, "started_at": "2026-06-09T17:45:04.136Z", @@ -389,7 +389,7 @@ "body": "This issue has been resolved and macOS jobs across all resource classes are starting normally again. Customers whose jobs failed to start during this window may rerun them. We thank you for your patience while our team worked on implementing a fix.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-07T04:44:29.255Z", "resolved_inferred": false, "started_at": "2026-06-07T04:20:18.650Z", @@ -402,7 +402,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-02T13:11:15.415Z", "resolved_inferred": false, "started_at": "2026-06-02T12:52:06.923Z", @@ -415,7 +415,7 @@ "body": "All Mac jobs are running successfully.\n\nOur infrastructure provider has confirmed that the DDoS attack has been mitigated and that services have been restored.\n\nThank you for your patience during this incident.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-01T03:26:10.499Z", "resolved_inferred": false, "started_at": "2026-06-01T01:04:39.220Z", @@ -428,7 +428,7 @@ "body": "Mac jobs have now fully recovered.\n\nThank you for your patience during this incident.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-01T00:45:07.993Z", "resolved_inferred": false, "started_at": "2026-05-31T18:15:41.770Z", @@ -441,7 +441,7 @@ "body": "The Usage API incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-29T18:10:15.886Z", "resolved_inferred": false, "started_at": "2026-05-29T14:51:42.399Z", @@ -454,7 +454,7 @@ "body": "Customers running jobs that pulled dependencies from Maven Central experienced elevated 429 (rate limit) errors. We have worked with Sonatype to allow list CircleCI's dedicated IP ranges. Customers using our IP ranges feature should no longer see Maven Central rate limits affect their jobs while we continue work to fully address the issue for all customers.\n\nCustomers whose jobs failed during this window may rerun affected jobs. We thank you for your patience while our team worked on implementing a fix.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-14T19:38:54.325Z", "resolved_inferred": false, "started_at": "2026-05-14T16:49:02.701Z", @@ -467,7 +467,7 @@ "body": "This incident is resolved. Thank you for your patience, and we apologize for any inconvenience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-06T20:13:46.165Z", "resolved_inferred": false, "started_at": "2026-05-06T19:42:48.226Z", @@ -480,7 +480,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-06T21:26:23.566Z", "resolved_inferred": false, "started_at": "2026-05-06T17:54:34.393Z", @@ -493,7 +493,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-01T11:08:22.351Z", "resolved_inferred": false, "started_at": "2026-05-01T10:51:24.148Z", @@ -506,7 +506,7 @@ "body": "This issue has been resolved. All data is up to date through yesterday.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-01T14:02:02.849Z", "resolved_inferred": false, "started_at": "2026-05-01T10:04:37.280Z", @@ -519,7 +519,7 @@ "body": "Customers running macOS jobs on m4pro.medium and m4pro.large with the xcode:26.4.0 image experienced job rejections with the error: \"Job was rejected because resource class , image xcode:26.4.0 is not a valid resource class\". The issue has been resolved and affected jobs should now run normally. \n\nCustomers whose jobs failed may rerun affected jobs. \n\nWe thank you for your patience while our team worked on implementing a fix.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-24T18:36:22.290Z", "resolved_inferred": false, "started_at": "2026-04-24T17:25:16.042Z", @@ -532,7 +532,7 @@ "body": "The Usage API issue has been resolved. All data is now current. Appreciate your patience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-18T15:05:36.562Z", "resolved_inferred": false, "started_at": "2026-04-18T12:07:48.663Z", @@ -545,7 +545,7 @@ "body": "The Usage API incident is resolved on an ongoing basis. There was a 4-hour period yesterday 4/7 for which we did not capture RAM and CPU utilization in our logs. We will not be backfilling the data for that period. Appreciate your patience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-08T20:33:29.716Z", "resolved_inferred": false, "started_at": "2026-04-08T13:20:12.689Z", @@ -558,7 +558,7 @@ "body": "**What happened** \nAll modals and dialogs across the CircleCI application became invisible. They were being rendered correctly in the background, but were not visible to users. This affected approval jobs, SSH key management, and other settings pages across the app. \n \n**Root cause** \nThe issue was introduced by an upgrade to our internal design system library. The new version added animation support to modal components using a library called Framer Motion. These animations are designed to fade modals in from invisible \\(`opacity: 0`\\) to visible \\(`opacity: 1`\\) when opened. \n \nHowever, the animation logic reads open/close state from a specific React context that is only available when modals are opened via a particular component \\(`DialogTrigger`\\). Our application manages modal state differently, passing open/close state directly via props, so that context was never populated. As a result, every modal in the app was permanently stuck in the \"hidden\" animation state and never transitioned to visible. \n \n**Resolution** \nWe reverted the design system upgrade to restore the previous working version, which resolved the issue immediately. We are now working on a follow-up fix that will upgrade Framer Motion properly, by ensuring all modal components receive the required context. \n \n**Impact** \nThe issue affected all modal dialogs across project settings, org settings, user settings, plans & payments, and other areas of the app for the duration of the incident. No data was lost or corrupted. The underlying functionality was intact, just inaccessible via the UI.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-06T21:12:35.372Z", "resolved_inferred": false, "started_at": "2026-04-06T20:33:28.468Z", @@ -571,7 +571,7 @@ "body": "The Usage API issue affecting 4/1 data has been resolved. Updated data will be available on 4/3. Thank you for your patience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-03T02:18:05.030Z", "resolved_inferred": false, "started_at": "2026-04-02T19:19:48.929Z", @@ -584,7 +584,7 @@ "body": "It appears that GitHub's `GET /repos/{owner}/{repo}/commits` API is now stable and responsive.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-01T12:23:57.585Z", "resolved_inferred": false, "started_at": "2026-04-01T11:55:06.957Z", @@ -597,7 +597,7 @@ "body": "On March 18, 2026, customers using workflows configured with serial groups or terminal job dependencies experienced two brief periods of disruption due to a code change.\n\nBetween approximately 12:08 and 12:35 UTC, affected pipelines encountered errors when creating workflows. For pipelines created in a second window from approximately 14:23 to 14:35 UTC, GitHub status updates were not delivered for some completed jobs. Long-running workflows triggered during this window may encounter these errors after the resolution time. The underlying change was reverted in both cases.\n\nAll systems have been operating normally since 14:35 UTC.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-18T16:00:00.000Z", "resolved_inferred": false, "started_at": "2026-03-18T16:00:00.000Z", @@ -610,7 +610,7 @@ "body": "Our engineering team has identified the root cause and has fixes prepared. Due to the nature of the data refresh process, the fix will require a deployment followed by a full refresh cycle before data is fully up to date. We expect that the data should be available within 24-36 hours. The last-24-hours reporting window continues to work normally, and all pipeline pages and job runs remain unaffected.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-16T03:52:47.915Z", "resolved_inferred": false, "started_at": "2026-03-16T03:02:28.023Z", @@ -623,7 +623,7 @@ "body": "The issue affecting the orb list on the Organization Settings page has been resolved. Our engineers have deployed a fix and users should now be able to view their orb list as expected.\u00a0 Orb usage in pipelines and builds was not impacted during this incident. If you continue to experience issues, please contact CircleCI support.\n\nThank you for your patience while we worked on resolving this issue.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-11T02:24:16.348Z", "resolved_inferred": false, "started_at": "2026-03-11T01:58:22.909Z", @@ -636,7 +636,7 @@ "body": "Looks like everything is good. Thank you for your patience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-02T18:21:06.106Z", "resolved_inferred": false, "started_at": "2026-03-02T17:59:14.000Z", @@ -649,7 +649,7 @@ "body": "GitHub have acknowledged and resolved an incident affecting their platform.\nhttps://www.githubstatus.com/incidents/vd3xqfq36rgm\nUsers should no longer experience intermittent checkout failures.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-27T00:17:31.594Z", "resolved_inferred": false, "started_at": "2026-02-26T22:50:46.222Z", diff --git a/api/v/circle.json b/api/v/circle.json index a002f7960e1e46c3f3fddad1263d41caf4068d6d..d8e35f964531792d2bd44fd24942bca2aa3acbb5 100644 --- a/api/v/circle.json +++ b/api/v/circle.json @@ -3,7 +3,7 @@ "slug": "circle", "platform": "statuspage", "status_url": "https://status.circle.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "degraded", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "The issue has been identified. Circle Mint deposits on Linea can be initiated but will not finalize or complete, and outbound Cross-Chain Transfer Protocol (CCTP) attestations are paused while the Linea network team works to restore finalization. Restoration may take several days. Circle Mint transfers and inbound CCTP mints to Linea are unaffected.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "started_at": "2026-09-02T18:21:18.896Z", "state": "identified", "title": "Circle Mint deposits and outbound CCTP attestations on Linea delayed", @@ -23,7 +23,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-09-02T15:02:47.785Z", "resolved_inferred": false, "started_at": "2026-09-02T14:59:17.511Z", @@ -36,7 +36,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-09-01T19:12:13.587Z", "resolved_inferred": false, "started_at": "2026-08-31T16:16:26.651Z", @@ -49,7 +49,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-09-02T21:09:56.719Z", "resolved_inferred": false, "started_at": "2026-08-30T14:58:53.907Z", @@ -62,7 +62,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-31T18:59:05.251Z", "resolved_inferred": false, "started_at": "2026-08-30T14:07:02.181Z", @@ -75,7 +75,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-09-02T01:00:56.223Z", "resolved_inferred": false, "started_at": "2026-08-28T22:07:00.922Z", @@ -88,7 +88,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-24T13:35:28.638Z", "resolved_inferred": false, "started_at": "2026-08-24T13:11:23.064Z", @@ -101,7 +101,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-24T07:35:59.865Z", "resolved_inferred": false, "started_at": "2026-08-24T06:14:26.070Z", @@ -114,7 +114,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-22T18:24:04.361Z", "resolved_inferred": false, "started_at": "2026-08-22T17:26:15.044Z", @@ -127,7 +127,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-22T10:28:29.871Z", "resolved_inferred": false, "started_at": "2026-08-22T02:48:48.985Z", @@ -140,7 +140,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-16T20:40:30.501Z", "resolved_inferred": false, "started_at": "2026-08-16T20:11:16.489Z", @@ -153,7 +153,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-14T23:08:41.613Z", "resolved_inferred": false, "started_at": "2026-08-14T21:30:34.133Z", @@ -166,7 +166,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-16T11:20:11.556Z", "resolved_inferred": false, "started_at": "2026-08-13T21:56:23.026Z", @@ -179,7 +179,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-12T14:08:05.362Z", "resolved_inferred": false, "started_at": "2026-08-12T13:56:08.774Z", @@ -192,7 +192,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-12T09:05:34.821Z", "resolved_inferred": false, "started_at": "2026-08-12T08:23:42.585Z", @@ -205,7 +205,7 @@ "body": "CCTP attestations on Polygon are experiencing technical difficulties and temporary delays. We are currently investigating the cause and working to resolve the issue.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-10T13:02:26.898Z", "resolved_inferred": false, "started_at": "2026-08-10T11:04:40.829Z", @@ -218,7 +218,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-07T05:48:17.844Z", "resolved_inferred": false, "started_at": "2026-08-07T05:16:41.365Z", @@ -231,7 +231,7 @@ "body": "The issue has been resolved", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-03T02:03:57.292Z", "resolved_inferred": false, "started_at": "2026-08-02T23:41:06.078Z", @@ -244,7 +244,7 @@ "body": "We have resolved the issue", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-01T07:40:59.029Z", "resolved_inferred": false, "started_at": "2026-08-01T03:03:12.640Z", @@ -257,7 +257,7 @@ "body": "The issue has been resolved", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-31T17:11:34.921Z", "resolved_inferred": false, "started_at": "2026-07-31T16:43:27.728Z", @@ -270,7 +270,7 @@ "body": "This incident has been resolved", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-30T12:40:44.755Z", "resolved_inferred": false, "started_at": "2026-07-30T10:37:44.284Z", @@ -283,7 +283,7 @@ "body": "The issue has been resolved, and the service is operating normally.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-30T09:14:39.418Z", "resolved_inferred": false, "started_at": "2026-07-29T14:54:17.369Z", @@ -296,7 +296,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-28T19:54:39.187Z", "resolved_inferred": false, "started_at": "2026-07-28T13:17:28.546Z", @@ -309,7 +309,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-24T17:25:35.115Z", "resolved_inferred": false, "started_at": "2026-07-24T16:57:53.745Z", @@ -322,7 +322,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-23T09:56:04.295Z", "resolved_inferred": false, "started_at": "2026-07-23T09:11:16.711Z", @@ -335,7 +335,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-23T03:45:27.308Z", "resolved_inferred": false, "started_at": "2026-07-23T03:07:10.851Z", @@ -348,7 +348,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-22T15:20:08.930Z", "resolved_inferred": false, "started_at": "2026-07-22T14:47:26.369Z", @@ -361,7 +361,7 @@ "body": "USDCx burns on Cardano are experiencing delays. We are currently investigating the cause.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-20T23:47:26.840Z", "resolved_inferred": false, "started_at": "2026-07-20T19:49:59.586Z", @@ -374,7 +374,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-20T16:56:50.584Z", "resolved_inferred": false, "started_at": "2026-07-20T15:50:15.168Z", @@ -387,7 +387,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-15T10:14:33.607Z", "resolved_inferred": false, "started_at": "2026-07-15T09:14:44.973Z", @@ -400,7 +400,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-10T12:54:45.821Z", "resolved_inferred": false, "started_at": "2026-07-10T11:11:46.956Z", @@ -413,7 +413,7 @@ "body": "We have identified an issue causing delays or degraded performance on CCTP Starknet. Some customers may experience slower transaction confirmations or partial unavailability. Our team is investigating the root cause and working to restore normal operation as soon as possible.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-09T07:39:58.927Z", "resolved_inferred": false, "started_at": "2026-07-09T06:39:56.353Z", @@ -426,7 +426,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-08T19:16:46.448Z", "resolved_inferred": false, "started_at": "2026-07-08T19:04:43.167Z", @@ -439,7 +439,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-08T00:43:28.465Z", "resolved_inferred": false, "started_at": "2026-07-07T21:49:57.509Z", @@ -452,7 +452,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-06T18:32:24.598Z", "resolved_inferred": false, "started_at": "2026-07-06T15:09:46.461Z", @@ -465,7 +465,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-07T14:12:20.493Z", "resolved_inferred": false, "started_at": "2026-07-03T21:38:45.918Z", @@ -478,7 +478,7 @@ "body": "This incident has been resolved", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-02T17:15:11.919Z", "resolved_inferred": false, "started_at": "2026-07-02T13:48:41.156Z", @@ -491,7 +491,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-03T01:15:15.995Z", "resolved_inferred": false, "started_at": "2026-06-29T17:16:28.435Z", @@ -504,7 +504,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-02T17:26:20.117Z", "resolved_inferred": false, "started_at": "2026-06-29T15:42:15.409Z", @@ -517,7 +517,7 @@ "body": "The Base Mainnet is currently experiencing a network outage affecting all Base operations. Operations will be possible once the Base network has been restored.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-25T19:37:33.349Z", "resolved_inferred": false, "started_at": "2026-06-25T16:20:36.936Z", @@ -530,7 +530,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-25T11:07:45.373Z", "resolved_inferred": false, "started_at": "2026-06-25T10:02:50.000Z", @@ -543,7 +543,7 @@ "body": "Degradation has recovered", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-24T16:30:09.254Z", "resolved_inferred": false, "started_at": "2026-06-23T17:54:46.093Z", @@ -556,7 +556,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-26T03:17:22.676Z", "resolved_inferred": false, "started_at": "2026-06-22T23:14:16.353Z", @@ -569,7 +569,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-20T20:00:00.000Z", "resolved_inferred": false, "started_at": "2026-06-19T18:12:16.882Z", @@ -582,7 +582,7 @@ "body": "The Solana Devnet restart has completed successfully. Network operations have stabilized, and Circle services are operating normally. This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-20T19:12:06.036Z", "resolved_inferred": false, "started_at": "2026-06-19T17:32:36.892Z", @@ -595,7 +595,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-16T15:26:49.433Z", "resolved_inferred": false, "started_at": "2026-06-15T21:51:50.415Z", @@ -608,7 +608,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-12T02:15:36.000Z", "resolved_inferred": false, "started_at": "2026-06-11T14:45:26.000Z", @@ -621,7 +621,7 @@ "body": "Circle has temporarily paused attestations for USDC burns on Solana via Circle's Cross-Chain Transfer Protocol (CCTP) as part of maintenance to CCTP on Solana", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-09T04:42:41.089Z", "resolved_inferred": false, "started_at": "2026-06-09T04:02:28.802Z", @@ -634,7 +634,7 @@ "body": "This incident is resolved", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-08T17:15:16.273Z", "resolved_inferred": false, "started_at": "2026-06-08T16:52:22.393Z", @@ -647,7 +647,7 @@ "body": "Circle has temporarily paused attestations for USDC burns on Polygon via Circle's Cross-Chain Transfer Protocol (CCTP) as part of maintenance to CCTP on Polygon", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-08T05:58:59.002Z", "resolved_inferred": false, "started_at": "2026-06-08T05:09:20.442Z", diff --git a/api/v/cisco-iot.json b/api/v/cisco-iot.json index c6e21f6e76fd820725c06ec2ff0faa2afcf5cb46..f864b05f6fe5d20bb2bb102c0a9f5467120de25e 100644 --- a/api/v/cisco-iot.json +++ b/api/v/cisco-iot.json @@ -3,7 +3,7 @@ "slug": "cisco-iot", "platform": "statuspage", "status_url": "https://status.ciscoiot.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "Org Hierarchy component has been decommissioned, closing this incident.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-13T09:11:06.842Z", "resolved_inferred": false, "started_at": "2026-07-13T08:29:20.979Z", diff --git a/api/v/cisco-meraki.json b/api/v/cisco-meraki.json index 640e0987597be6a645ab1a0f7bc5e154c7a75b2e..3f879cbe16d0ad87a16f055a97ed4d953a006e25 100644 --- a/api/v/cisco-meraki.json +++ b/api/v/cisco-meraki.json @@ -3,7 +3,7 @@ "slug": "cisco-meraki", "platform": "statuspage", "status_url": "https://status.meraki.net", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-06T01:48:18.291Z", "resolved_inferred": false, "started_at": "2026-08-05T23:44:16.514Z", @@ -25,7 +25,7 @@ "body": "Our teams have successfully mitigated the issue that was affecting customers.\u00a0 It has been confirmed that the the generateSnapshot Camera API endpoint is responding as expected.\u00a0 If you continue to have issues, please contact Customer Support.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-15T19:11:15.010Z", "resolved_inferred": false, "started_at": "2026-07-15T17:43:51.259Z", @@ -38,7 +38,7 @@ "body": "The issue with API responses has been Resolved.\u00a0 If you continue to see issues with failed API calls, please reach out to Customer Support.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-24T00:39:09.420Z", "resolved_inferred": false, "started_at": "2026-06-23T23:44:35.716Z", @@ -51,7 +51,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-12T06:01:48.076Z", "resolved_inferred": false, "started_at": "2026-06-12T03:20:32.254Z", @@ -64,7 +64,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-21T14:10:21.139Z", "resolved_inferred": false, "started_at": "2026-05-21T11:42:52.283Z", @@ -77,7 +77,7 @@ "body": "Our teams have confirmed that the prior issues regarding Live Tools and/or viewing live data for network devices have been resolved.\u00a0 All systems are now operating normally.\u00a0 If you continue to see issues, please contact Meraki Customer Support.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-01T23:14:15.719Z", "resolved_inferred": false, "started_at": "2026-05-01T18:15:20.882Z", @@ -90,7 +90,7 @@ "body": "Our teams have confirmed that the prior issues regarding Live Tools and/or viewing live data for network devices have been resolved.\u00a0 All systems are now operating normally.\u00a0 If you continue to see issues, please contact Meraki Customer Support.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-28T19:19:42.980Z", "resolved_inferred": false, "started_at": "2026-04-28T16:10:51.255Z", @@ -103,7 +103,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-14T19:28:55.490Z", "resolved_inferred": false, "started_at": "2026-04-14T19:11:06.000Z", @@ -116,7 +116,7 @@ "body": "This incident is now resolved. All systems should be operating normally at this time. If you continue to experience issues, please feel free to contact Customer Support.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-15T21:15:27.347Z", "resolved_inferred": false, "started_at": "2025-12-15T18:09:29.859Z", @@ -129,7 +129,7 @@ "body": "The issues connecting to the Support team via phone are now resolved. Thank you for your patience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-21T01:07:42.777Z", "resolved_inferred": false, "started_at": "2025-10-20T15:08:27.000Z", @@ -142,7 +142,7 @@ "body": "The issue involving customers being unable to reach our support team via phone has been resolved. If you continue to experience issues attempting to contact us via our Support Hotline please follow these steps. For new cases please open a case and choose the \"Call In\" option, for existing cases please provide a case comment with the phrase \"10-15-Outage\" and we will reach out to you as soon as possible.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-15T22:31:09.891Z", "resolved_inferred": false, "started_at": "2025-10-15T19:46:26.130Z", @@ -155,7 +155,7 @@ "body": "The mitigation for the earlier MX (firewall) DDNS issues has been fully propagated and verified. Normal DDNS functionality has been restored to all MX (firewall) devices. If you continue to have issues, please contact Meraki Customer Support.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-08T20:17:41.000Z", "resolved_inferred": false, "started_at": "2025-10-08T18:57:57.883Z", @@ -168,7 +168,7 @@ "body": "The recent issue causing slow load times and intermittent timeouts for dashboard pages in subscription-based organizations has been resolved. System performance has returned to normal, and all affected services are operating as expected. If you continue to experience any issues, please contact our support team for further assistance.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-01T22:41:41.869Z", "resolved_inferred": false, "started_at": "2025-10-01T20:52:53.653Z", diff --git a/api/v/cisco-systems.json b/api/v/cisco-systems.json index f08b0f4d7d2cbf76722ac7187bada66f7768316b..e3793247adaf60a1f905bcb1808fc0e6cf3700bd 100644 --- a/api/v/cisco-systems.json +++ b/api/v/cisco-systems.json @@ -3,7 +3,7 @@ "slug": "cisco-systems", "platform": "statuspage", "status_url": "https://status.sse.cisco.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "degraded", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "Between approximately 14:15 and 15:40 UTC, customers using the Investigate dashboard and associated data retrieval APIs may have experienced 503 errors, unavailable graphs or data, and errors when retrieving logs or graph information. The issue has been resolved, and service has returned to normal.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-09-01T18:01:59.000Z", "resolved_inferred": false, "started_at": "2026-09-01T18:01:59.000Z", @@ -25,7 +25,7 @@ "body": "The issue affecting Cisco Secure Access services in the US East (Miami) DCv2 region has been resolved as of 18:21 UTC.\n\nAll services are now operating normally.\n\nWe apologize for any inconvenience caused and thank you for your patience.\n\nWe\u2019re Here to Help If you have any questions, please contact our support team. Thank you for your understanding as we improve your Cisco Secure Access experience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-31T18:22:51.000Z", "resolved_inferred": false, "started_at": "2026-08-31T15:08:45.000Z", @@ -38,7 +38,7 @@ "body": "The issue affecting Cisco Secure Access Remote Access VPN service in the US West (Oregon) region was resolved as of 18:11 UTC.\n\nAll services are now operating normally.\n\nWe apologize for any inconvenience caused and thank you for your patience.\n\nWe\u2019re Here to Help\nIf you have any questions, please contact our support team. Thank you for your understanding as we improve your Cisco Secure Access experience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-28T19:51:10.876Z", "resolved_inferred": false, "started_at": "2026-08-28T19:25:11.934Z", @@ -51,7 +51,7 @@ "body": "The issue affecting Firewall as a Service has been resolved. Service has returned to normal operation. \n\nWe\u2019re Here to Help\nIf you have any questions or need assistance, please contact our support team.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-28T15:36:21.000Z", "resolved_inferred": false, "started_at": "2026-08-28T11:57:44.394Z", @@ -64,7 +64,7 @@ "body": "The incident has been resolved at 13:25 UTC", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-25T14:04:47.000Z", "resolved_inferred": false, "started_at": "2026-08-25T12:24:02.237Z", @@ -77,7 +77,7 @@ "body": "The issue affecting the Policy Enforcement service for some customers connecting through the London data center has been resolved as of 22:46 UTC on August 24, 2026.\nBetween 22:37 UTC and 22:46 UTC, affected customers may have experienced intermittent traffic disruption through the firewall service. The impacted workload was moved to a healthy infrastructure node, and all services are now operating normally.\n\nWe apologize for any inconvenience caused and thank you for your patience.\n\nWe\u2019re Here to Help If you have any questions, please contact our support team. Thank you for your understanding as we improve your Cisco Secure Access experience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-25T03:40:09.787Z", "resolved_inferred": false, "started_at": "2026-08-25T03:40:09.712Z", @@ -90,7 +90,7 @@ "body": "The issue has been resolved. \n\nCustomers in US Virginia DC may have experienced traffic degradation due to a service health-check failure that caused traffic handling to move to a healthy node between 9:52 UTC to 9:58 UTC, when the issue got resolved.\n\nNo customer action is required.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-24T12:55:59.266Z", "resolved_inferred": false, "started_at": "2026-08-24T12:55:59.196Z", @@ -103,7 +103,7 @@ "body": "The network issue affecting Cisco Secure Access policy update processing in Johannesburg, South Africa has been resolved. New and updated policy changes are now applying as expected. \n\nWe\u2019re Here to Help\nIf you have any questions or need assistance, please contact our support team.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-21T18:59:55.867Z", "resolved_inferred": false, "started_at": "2026-08-21T17:09:28.979Z", @@ -116,7 +116,7 @@ "body": "Between 12:12 UTC and 13:15 UTC, customers may have experienced default document classification values for some files in the DSPM dashboard. All other DSPM functions remained fully operational throughout this period. The issue affecting document classification within the Data Security Posture Management (DSPM) service is now resolved.\n\n Affected files will be updated automatically as soon as any activity on the file happens. No customer action is required.\n\nWe sincerely appreciate your patience and understanding.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-21T13:27:18.000Z", "resolved_inferred": false, "started_at": "2026-08-21T13:27:18.000Z", @@ -129,7 +129,7 @@ "body": "The issue affecting Dashboard service with web proxy log in China data Center has been resolved.\n\nAll services are now operating normally.\n\nWe apologize for any inconvenience caused and thank you for your patience.\n\nWe\u2019re Here to Help If you have any questions, please contact our support team. Thank you for your understanding as we improve your Cisco Secure Access experience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-17T06:30:52.771Z", "resolved_inferred": false, "started_at": "2026-08-17T06:13:00.290Z", @@ -142,7 +142,7 @@ "body": "The issue affecting Website Access Issue in Tokyo region has been resolved.\n\nAll services are now operating normally.\n\nWe apologize for any inconvenience caused and thank you for your patience.\n\nWe\u2019re Here to Help If you have any questions, please contact our support team. Thank you for your understanding as we improve your Cisco Secure Access experience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-17T02:38:36.702Z", "resolved_inferred": false, "started_at": "2026-08-17T01:20:17.413Z", @@ -155,7 +155,7 @@ "body": "All services in Frankfurt and previously affected sites are now fully restored. Connectivity and reporting are back to normal.\n\nWe sincerely appreciate your patience and understanding.\n\nWe're Here to Help\nIf you have any questions, please contact our support team. Thank you for your understanding as we improve your Cisco Secure Access experience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-19T09:06:22.727Z", "resolved_inferred": false, "started_at": "2026-08-15T09:30:09.639Z", @@ -168,7 +168,7 @@ "body": "Traffic has been successfully redirected away from the affected data center, and all services have been stabilized as of 05:01 UTC. Customers should now experience normal service performance. \n\nReporting services may take a few hours to fully catch up. During this time, some log and report data may appear delayed. \n\nWe sincerely appreciate your patience and understanding.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-15T05:12:10.000Z", "resolved_inferred": false, "started_at": "2026-08-15T03:18:04.521Z", @@ -181,7 +181,7 @@ "body": "The issue affecting Remote Access VPN connectivity in the Miami, Reston, Dallas, and Jeddah data centers was resolved.\n\nServices are now operating normally.\n\nWe apologize for any inconvenience caused and thank you for your patience.\n\nWe\u2019re Here to Help\nIf you have any questions, please contact our support team. Thank you for your understanding as we continue to improve your Cisco Secure Access experience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-09T06:13:35.676Z", "resolved_inferred": false, "started_at": "2026-08-09T01:37:02.000Z", @@ -194,7 +194,7 @@ "body": "The impact has been mitigated and this incident has been resolved.\n\nAffected customers may have experienced intermittent failures when starting new Clientless Access or Enterprise Browser sessions, including some step-up login workflows, in the US East and Canada regions. Some onboarding-related workflows may also have experienced intermittent failures.\n\nServices have returned to normal operation.\n\nThank you for your patience. If you continue to experience issues, please contact Cisco Customer Support.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-05T18:34:31.251Z", "resolved_inferred": false, "started_at": "2026-08-05T16:50:23.080Z", @@ -207,7 +207,7 @@ "body": "The issue affecting traffic performance in the Japan (Osaka) region has been resolved as of 09:18 UTC. All services are now operating normally, with response times and throughput fully restored.\n\nWe apologize for any inconvenience caused and thank you for your patience.\n\nWe're Here to Help\nIf you have any questions, please contact our support team. Thank you for your understanding as we improve your Cisco Secure Access experience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-05T09:25:40.466Z", "resolved_inferred": false, "started_at": "2026-08-05T06:47:03.187Z", @@ -220,7 +220,7 @@ "body": "We have mitigated the issue affecting Cisco Secure Access Firewall and VPN services in specific India and Tokyo locations.\n\nAffected customers may have experienced intermittent connectivity issues, including packet loss or temporary connection drops, for services associated with the csc_ap-south-1_1_0 location in India and the csc-apne1-1-0-0 location in Tokyo. This issue did not affect all Cisco Secure Access services or all customers in these regions.\n\nRemote Access VPN service has recovered in both affected locations, and services are currently stable. Our teams are continuing to monitor service health and have paused related maintenance activity while the incident is reviewed.\n\nWe appreciate your patience and understanding during this time.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-04T20:35:27.000Z", "resolved_inferred": false, "started_at": "2026-08-04T20:35:27.000Z", @@ -233,7 +233,7 @@ "body": "Impact has been resolved as of 12:18 UTC, Aug 4, 2026. Affected services have been successfully brought back into rotation as of 13:02 UTC, Aug 5, 2026. All services are healthy, and the environment is operating normally.\n\nWe\u2019re Here to Help If you continue to experience issues, please contact Cisco Support.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-04T15:05:21.000Z", "resolved_inferred": false, "started_at": "2026-08-04T06:11:38.923Z", @@ -246,7 +246,7 @@ "body": "This issue has been resolved.\n\nCertificate issuance for Cisco Secure Access Remote Access VPN provisioning has returned to normal, and the certificate provisioning backlog has cleared. New Remote Access VPN region provisioning and first-time VPN setup workflows should now complete as expected.\n\nExisting VPN regions and active access were not expected to be impacted.\n\nThank you for your patience. If you continue to experience issues, please contact Cisco Customer Support.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-31T23:26:08.711Z", "resolved_inferred": false, "started_at": "2026-07-31T18:41:40.254Z", @@ -259,7 +259,7 @@ "body": "This emergency maintenance activity was completed on July 30, 2026. We are publishing this notice retrospectively to provide customers with a complete record of the activity.\n\nMaintenance Details\nCisco performed emergency maintenance on the load-balancing infrastructure supporting internet traffic in the US East region. The activity addressed a known issue with the existing load balancer and involved removing the affected load-balancing component to restore service stability.\n\nDate and Time\nJuly 30, 2026, from 18:34 UTC to 19:21 UTC.\n\nImpact\nDuring the maintenance window, customers using the affected Secure Web Gateway data center may have experienced intermittent issues reaching internet destinations. Service has been restored, and no further customer action is required.\n\nAffected Region\nUS East (Miami) : csc_us-east-1_1_0\n\nWe're Here to Help\nIf you have questions or need assistance, please contact Cisco Support or your Cisco representative.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-30T20:00:15.000Z", "resolved_inferred": false, "started_at": "2026-07-30T20:00:15.000Z", @@ -272,7 +272,7 @@ "body": "This issue has been resolved.\n\nCisco Secure Access customers with policies configured to block the \"M365 Copilot\" or \"Microsoft Copilot\" application categories should no longer experience related access issues with Microsoft 365 services.\n\nCustomers who applied the previously provided workaround can review and restore their policy settings as appropriate for their organization\u2019s security requirements.\n\nThank you for your patience. If you continue to experience issues, please contact Cisco Customer Support.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-25T21:10:55.299Z", "resolved_inferred": false, "started_at": "2026-07-25T17:07:45.919Z", @@ -285,7 +285,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-24T13:06:11.866Z", "resolved_inferred": false, "started_at": "2026-07-24T11:34:15.114Z", @@ -298,7 +298,7 @@ "body": "Mitigation actions have been completed, and Cisco Secure Access services are operating normally.\n\nWe're Here to Help\nIf you have any questions or need assistance, please contact our support team.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-15T18:08:57.412Z", "resolved_inferred": false, "started_at": "2026-07-15T15:27:22.909Z", @@ -311,7 +311,7 @@ "body": "The mitigation has been successfully completed across all regions, and the affected Identity service is operating normally.\n\nPolicy processing for ZTA traffic, ZTNA enrollment, new policy creation, and new user connections have been restored. Existing configurations and ongoing data traffic remain unaffected.\n\nWe appreciate your patience while we worked to resolve this issue.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-15T14:38:00.041Z", "resolved_inferred": false, "started_at": "2026-07-15T09:11:01.000Z", @@ -324,7 +324,7 @@ "body": "The issue affecting the Cisco Secure Access Dashboard in the China data centers has been resolved.\n\nServices are now operating normally.\n\nWe apologize for any inconvenience caused and thank you for your patience.\n\nWe\u2019re Here to Help If you have any questions, please contact our support team. Thank you for your understanding as we improve your Cisco Secure Access experience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-15T08:07:15.892Z", "resolved_inferred": false, "started_at": "2026-07-15T06:27:30.900Z", @@ -337,7 +337,7 @@ "body": "Between 01:40 and 02:05 UTC, we experienced intermittent policy evaluation failures in Tokyo region, resulting in fail-open conditions. During this period, some security policies may not have been applied for affected users, potentially impacting policy enforcement.\n\nServices is now operating normally.\n\nWe apologize for any inconvenience caused and thank you for your patience.\n\nWe\u2019re Here to Help If you have any questions, please contact our support team. Thank you for your understanding as we improve your Cisco Secure Access experience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-15T03:22:49.054Z", "resolved_inferred": false, "started_at": "2026-07-15T03:22:48.991Z", @@ -350,7 +350,7 @@ "body": "Between 01:40 and 02:05 UTC, we experienced intermittent policy evaluation failures in Tokyo region, resulting in fail-open conditions. During this period, some security policies may not have been applied for affected users, potentially impacting policy enforcement.\n\nServices is now operating normally.\n\nWe apologize for any inconvenience caused and thank you for your patience.\n\nWe\u2019re Here to Help If you have any questions, please contact our support team. Thank you for your understanding as we improve your Cisco Secure Access experience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-14T02:59:48.941Z", "resolved_inferred": false, "started_at": "2026-07-14T02:59:48.879Z", @@ -363,7 +363,7 @@ "body": "The issue affecting dashboard component has been resolved.\n\nAll services are now operating normally.\n\nWe apologize for any inconvenience caused and thank you for your patience.\n\nWe\u2019re Here to Help If you have any questions, please contact our support team. Thank you for your understanding as we improve your Cisco Secure Access experience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-09T02:14:39.343Z", "resolved_inferred": false, "started_at": "2026-07-08T19:08:32.000Z", @@ -376,7 +376,7 @@ "body": "The single sign-on issue affecting Cisco Security Cloud access to the Secure Access UI has been resolved. Customers should now be able to log in successfully.\n\nThank you for your patience and understanding.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-08T17:02:32.218Z", "resolved_inferred": false, "started_at": "2026-07-08T16:30:49.505Z", @@ -389,7 +389,7 @@ "body": "The issue affecting Cisco Secure Access in Australia (Sydney) has been resolved.\n\nAll services are now operating normally.\n\nWe\u2019re Here to Help If you have any questions, please contact our support team. Thank you for your understanding as we improve your Cisco Secure Access experience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-04T07:57:20.204Z", "resolved_inferred": false, "started_at": "2026-07-04T03:05:03.000Z", @@ -402,7 +402,7 @@ "body": "The issue affecting Cisco Secure Access platform performance in the US-East region has been resolved as of 07:50 UTC.\n\nAll services are now operating normally, and security policies are being applied as expected.\n\nWe apologize for any inconvenience caused and thank you for your patience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-02T07:52:58.030Z", "resolved_inferred": false, "started_at": "2026-07-02T06:15:30.000Z", @@ -415,7 +415,7 @@ "body": "We are providing a retroactive update for an issue that affected URL filtering policy enforcement for SWG customers in the China region.\n\nBetween 20:26 UTC and 22:10 UTC on June 30, 2026, customers using URL filtering policies in China may have experienced policy enforcement issues. During this time, attempts to access sites that should have been blocked or warned may not have triggered the expected policy action, including block or warn pages.\n\nThe issue affected both China data centers and has been mitigated. URL filtering policy enforcement has been restored, and our engineering teams continue to monitor service stability and investigate the underlying cause.\n\nThank you for your patience and understanding during this incident. If you continue to experience issues, please contact Cisco Customer Support.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-30T23:02:09.797Z", "resolved_inferred": false, "started_at": "2026-06-30T23:02:09.740Z", @@ -428,7 +428,7 @@ "body": "The issue has been mitigated.\n\nWe\u2019re Here to Help\nIf you have any questions or need assistance, please contact our support team.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-30T19:00:52.608Z", "resolved_inferred": false, "started_at": "2026-06-30T18:37:29.869Z", @@ -441,7 +441,7 @@ "body": "The issue affecting Secure Web Gateway (SWG) service for customers connecting to the Virginia data center has been resolved.\n\nService performance has been restored, and no further impact is expected.\n\nWe appreciate your patience and understanding during this incident.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-30T16:32:52.563Z", "resolved_inferred": false, "started_at": "2026-06-30T15:40:40.989Z", @@ -454,7 +454,7 @@ "body": "This maintenance activity was completed on June 26, 2026. At the time, an update was posted through the Cisco Secure Access portal instead of a maintenance notification on the status page. We are now publishing this notice retrospectively to ensure that customers have a complete record of the activity. \n\nMaintenance Details\nRemote Access VPN IP pools were rebalanced across the two data centers in the US East region. This proactive activity was executed to improve IP capacity distribution and help accommodate future growth in VPN connections.\n\nDate and Time\nJune 26, 2026, from 09:04 UTC to 10:28 UTC.\n\nImpact\nDuring the maintenance window, active VPN sessions in the US East (Virginia) region could have experience a brief connection interruption.\nUsers with Auto Reconnect enabled should have had their VPN connections automatically re-established. Users without Auto Reconnect enabled would have need to manually reconnect using Cisco Secure Client.\n\nAffected Region\nUS East (Virginia)\n\nComponents\nRemote Access VPN\n\nWe're Here to Help\nIf you have questions or need assistance, please contact Cisco Support or your Cisco representative.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-26T09:00:00.000Z", "resolved_inferred": false, "started_at": "2026-06-26T09:00:00.000Z", @@ -467,7 +467,7 @@ "body": "The increased DNS response latency affecting DNS resolution services in Amsterdam has been resolved.\n\nCustomers using DNS resolution services through Amsterdam should no longer experience delayed DNS responses related to this issue.Service has been restored to normal operation.\n\nWe\u2019re Here to Help\nIf you have any questions or need assistance, please contact our support team.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-23T16:08:01.618Z", "resolved_inferred": false, "started_at": "2026-06-23T15:34:30.660Z", @@ -480,7 +480,7 @@ "body": "The issue affecting Cisco Secure Access customers in the Asia Pacific (Tokyo) region has been fully resolved. The ap-northeast-1_1_1 vEDC has been restored to rotation, and all services are operating normally.\n\nWe\u2019re Here to Help\nIf you have any questions or need assistance, please contact our support team.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-23T17:11:58.045Z", "resolved_inferred": false, "started_at": "2026-06-23T01:48:16.316Z", @@ -493,7 +493,7 @@ "body": "We are pleased to confirm that the restoration process has been successfully completed for all previously impacted regions. The following region has now been brought back in rotation and fully operational.\n\nUS (Virginia) - us-east-1_1_0\n\nOur engineering team have verified service stability across all affected regions and all impacted regions are now operating normally.\n\nWe apologize for any inconvenience this may have caused and appreciate your patience.\n\nWe\u2019re Here to Help\n If you have any questions, please contact our support team. Thank you for your understanding as we improve your Cisco Secure Access experience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-18T09:03:31.615Z", "resolved_inferred": false, "started_at": "2026-06-17T15:34:22.000Z", @@ -506,7 +506,7 @@ "body": "Between 01:37 UTC and 07:50 UTC, the RAVPN service in the APSE2-1-1-1 cluster at the Australia (Sydney) data center experienced degradation. During this time, customers may have encountered traffic interruption through RAVPN service.\n\nAll services are now operating normally.\n\nWe apologize for any inconvenience this may have caused and appreciate your patience.\n\nWe\u2019re Here to Help If you have any questions, please contact our support team. Thank you for your understanding as we improve your Cisco Secure Access experience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-17T08:36:21.754Z", "resolved_inferred": false, "started_at": "2026-06-17T08:36:21.689Z", @@ -519,7 +519,7 @@ "body": "Following a thorough investigation into the potential connectivity issues reported for Remote Browser Isolation in the Tokyo region, we have confirmed that the service was never impacted. The service remained fully operational throughout the period.\n\nWe\u2019re Here to Help If you have any questions, please contact our support team. Thank you for your understanding as we improve your Cisco Secure Access experience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-17T04:02:39.000Z", "resolved_inferred": false, "started_at": "2026-06-16T21:52:42.000Z", @@ -532,7 +532,7 @@ "body": "An issue affecting Web Security service traffic in the Singapore region was identified and resolved. Service was restored at 23:43 UTC on June 15, 2026.\n\nService has been restored, and no further impact is expected.\n\nWe appreciate your patience and understanding during this incident.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-16T21:53:33.891Z", "resolved_inferred": false, "started_at": "2026-06-15T23:05:08.232Z", @@ -545,7 +545,7 @@ "body": "The issue affecting Web Security service traffic in the Tokyo region has been resolved.\n\nCustomers whose traffic was routed through this region may have experienced intermittent traffic degradation, where some TCP connection attempts may have failed or timed out.\n\nService has been restored, and no further impact is expected.\n\nWe appreciate your patience and understanding during this incident.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-15T23:03:41.331Z", "resolved_inferred": false, "started_at": "2026-06-15T23:00:07.082Z", @@ -558,7 +558,7 @@ "body": "The issue affecting SWG security inspection services in China has been resolved.\n\nCustomers using SWG in this region should no longer experience fail-open scenarios for the affected DLP or file inspection workflows. Normal inspection behavior has been restored.\n\nWe appreciate your patience and understanding during this incident.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-14T19:55:28.481Z", "resolved_inferred": false, "started_at": "2026-06-14T19:02:11.103Z", @@ -571,7 +571,7 @@ "body": "Between 18:06 and 18:46 UTC on June 12, 2026, some customers using the Umbrella/Cisco SSE DNS resolver service with DNSCrypt may have experienced DNS resolution issues when traffic was served through Atlanta.\n\nThe issue has been resolved, and DNS resolution has been restored. No further impact is expected.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-12T21:02:32.000Z", "resolved_inferred": false, "started_at": "2026-06-12T21:02:32.000Z", @@ -584,7 +584,7 @@ "body": "Customers using DNS Steering Destinations with Resource Connector Groups in ZTA Profiles may experience issues with the related DNS steering after changes are made to the associated Resource Connector Group.\n\nWhen private resources are added to or removed from a Resource Connector Group, the DNS Steering Destination may no longer remain properly associated with that group. If this occurs, the defined DNS resolution through the Resource Connector Group may fail.\n\nAs a mitigation step, customers can re-attach the Resource Connector Group to the affected DNS Steering Destination and save the DNS Steering Destination.\n\nOur engineering team is actively investigating. Updates and additional details will be provided as new information becomes available.\n\nWe appreciate your patience and understanding during this time.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-10T01:26:12.974Z", "resolved_inferred": false, "started_at": "2026-06-10T01:26:12.910Z", @@ -597,7 +597,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-05T12:31:46.389Z", "resolved_inferred": false, "started_at": "2026-06-05T08:55:28.483Z", @@ -610,7 +610,7 @@ "body": "On June 4th, 2026, between 17:09 UTC and 18:18 UTC, users experienced intermittent unavailability within specific components of the Cisco Umbrella and Cisco Secure Access dashboards.\n\nAll services are now operating normally.\n\nWe apologize for any inconvenience caused and thank you for your patience.\n\nWe\u2019re Here to Help If you have any questions, please contact our support team. Thank you for your understanding as we improve your Cisco Secure Access experience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-04T19:13:32.693Z", "resolved_inferred": false, "started_at": "2026-06-04T19:13:32.626Z", @@ -623,7 +623,7 @@ "body": "This incident has been resolved. Engineering has restored Cisco Umbrella and Cisco Secure Access dashboard functionality, including impacted policy and administrative workflows.\n\nWe will continue monitoring service health and completing follow-up analysis. No further customer impact is expected at this time.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-04T00:46:45.188Z", "resolved_inferred": false, "started_at": "2026-06-03T20:02:03.708Z", @@ -636,7 +636,7 @@ "body": "The issue has now been resolved, and normal service has been restored. We apologize for any inconvenience caused and appreciate your patience while we addressed the problem.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-02T20:54:40.847Z", "resolved_inferred": false, "started_at": "2026-06-02T20:49:58.000Z", @@ -649,7 +649,7 @@ "body": "The issue affecting the block page service for customers connecting to the LAX data center has been mitigated.\n\nCustomers should no longer experience intermittent timeouts when accessing websites blocked by policy, and block pages should now load as expected.\n\nOur engineering team will continue to monitor the service to ensure stability. We appreciate your patience and understanding during this incident.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-29T21:36:31.623Z", "resolved_inferred": false, "started_at": "2026-05-29T21:32:21.410Z", @@ -662,7 +662,7 @@ "body": "We have implemented a mitigation to redirect UAE traffic to an alternate data center (Mumbai) to address the ongoing service impact. Traffic is being steered to the Mumbai region, and we are actively monitoring system stability and performance. This mitigation primarily applies to automatically steered (roaming) UAE traffic.\n\nCustomers in the affected region are advised to ensure their configurations align with previously shared guidance for alternate region routing, including any required updates to Network Tunnel Groups or Connector Groups. Customers already configured to alternate regions will continue using their configured region.\n\nOur engineering teams continue to investigate the underlying cause and are working closely with partners to ensure full service restoration.\n\nIf you require any assistance, please contact us. We will provide guidance on the necessary actions.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "started_at": "2026-03-02T05:55:48.917Z", "state": "identified", "title": "[Cisco Secure Access] - Connectivity Issue \u2013 Dubai", diff --git a/api/v/cisco-umbrella.json b/api/v/cisco-umbrella.json index 96e622d238fd97a31dbe702eb261e9ce9cd45db0..6120daa67f7036b414a533275c3b4ca05c737e52 100644 --- a/api/v/cisco-umbrella.json +++ b/api/v/cisco-umbrella.json @@ -3,7 +3,7 @@ "slug": "cisco-umbrella", "platform": "statuspage", "status_url": "https://status.umbrella.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "Between approximately 14:15 and 15:40 UTC, customers using the Investigate dashboard and associated data retrieval APIs may have experienced 503 errors, unavailable graphs or data, and errors when retrieving logs or graph information. The issue has been resolved, and service has returned to normal.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-09-01T18:00:25.000Z", "resolved_inferred": false, "started_at": "2026-09-01T18:00:25.000Z", @@ -25,7 +25,7 @@ "body": "The network issue affecting Cisco Umbrella policy update processing in Johannesburg, South Africa has been resolved. New and updated policy changes are now applying as expected.\n\n\nWe\u2019re Here to Help\nIf you have any questions or need assistance, please contact our support team.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-21T19:00:23.629Z", "resolved_inferred": false, "started_at": "2026-08-21T17:07:14.941Z", @@ -38,7 +38,7 @@ "body": "The issue affecting incorrectly categorized DNS Tunneling VPN issue for some domains has been resolved.\n\nAll services are now operating normally.\n\nWe apologize for any inconvenience caused and thank you for your patience.\n\nWe\u2019re Here to Help If you have any questions, please contact our support team. Thank you for your understanding as we improve your Cisco Secure Access experience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-20T07:26:20.302Z", "resolved_inferred": false, "started_at": "2026-08-20T03:18:07.245Z", @@ -51,7 +51,7 @@ "body": "The capacity condition affecting Europe (France) has been resolved. Cisco Secure Connect Remote Access client connections are operating normally.\n\nWe\u2019re Here to Help\nIf you have any questions or need assistance, please contact our support team.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-19T16:20:25.285Z", "resolved_inferred": false, "started_at": "2026-08-19T07:49:41.000Z", @@ -64,7 +64,7 @@ "body": "The connectivity issue in the Palo Alto data center is now resolved. All services are restored and the site is back in rotation. We have confirmed that traffic flow is stable. Thank you for your patience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-20T07:51:54.989Z", "resolved_inferred": false, "started_at": "2026-08-17T15:56:20.048Z", @@ -77,7 +77,7 @@ "body": "All services in Frankfurt and previously affected sites are now fully restored. Connectivity and reporting are back to normal.\n\nWe sincerely appreciate your patience and understanding.\n\nWe're Here to Help\nIf you have any questions, please contact our support team. Thank you for your understanding as we improve your Cisco Secure Access experience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-19T09:04:57.695Z", "resolved_inferred": false, "started_at": "2026-08-15T09:52:06.893Z", @@ -90,7 +90,7 @@ "body": "Traffic has been successfully redirected away from the affected data center, and all services have been stabilized as of 05:01 UTC.\n\nCustomers should now experience normal service performance. If your connection has not restored automatically, we kindly ask that you reconnect manually using Cisco Secure Client to be routed to a healthy location. Reporting services may take a few hours to fully catch up. During this time, some log and report data may appear delayed. \n\nWe sincerely appreciate your patience and understanding.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-15T05:12:25.000Z", "resolved_inferred": false, "started_at": "2026-08-15T03:23:03.841Z", @@ -103,7 +103,7 @@ "body": "This issue has been resolved. Cisco Umbrella customers are now able to download Cisco Secure Client from the dashboard.\n\nWe're Here to Help\nIf you have any questions or need assistance, please contact our support team.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-14T17:26:04.086Z", "resolved_inferred": false, "started_at": "2026-08-14T17:16:23.868Z", @@ -116,7 +116,7 @@ "body": "Between approximately 11:52 UTC and 12:12 UTC on August 12, 2026, customers connecting through the India (Mumbai) data center may have experienced a brief network disruption. During this period, some customers may have experienced disconnections, reduced traffic throughput, or difficulty establishing new connections. \nService was restored as of 12:12 UTC, and all services are now operating normally.\n\nWe apologize for any inconvenience caused and thank you for your patience.\n\nWe're Here to Help\nIf you continue to experience issues, please contact Cisco Support.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-12T12:33:01.299Z", "resolved_inferred": false, "started_at": "2026-08-12T12:33:01.236Z", @@ -129,7 +129,7 @@ "body": "This issue has been resolved.\n\nCisco Secure Connect resiliency region provisioning has returned to normal, and customers should no longer experience issues provisioning new resiliency regions. Current connectivity was not expected to be impacted during this incident.\n\nThank you for your patience. If you continue to experience issues, please contact Cisco Customer Support.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-05T16:53:42.513Z", "resolved_inferred": false, "started_at": "2026-08-05T11:59:12.687Z", @@ -142,7 +142,7 @@ "body": "The issue affecting Cisco Umbrella Cloud Delivered Firewall policy enforcement in Singapore has been resolved. Services have returned to normal operation.\n\nWe\u2019re Here to Help\nIf you have any questions or need assistance, please contact our support team.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-04T20:17:45.504Z", "resolved_inferred": false, "started_at": "2026-08-04T19:50:02.000Z", @@ -155,7 +155,7 @@ "body": "This issue has been resolved.\n\nCisco Secure Connect Remote Access Client connectivity through the Mumbai and Chennai locations has been restored, and the affected services have returned to normal operation.\n\nThank you for your patience. If you continue to experience issues, please contact Cisco Customer Support.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-31T19:51:11.971Z", "resolved_inferred": false, "started_at": "2026-07-31T18:08:16.069Z", @@ -168,7 +168,7 @@ "body": "Certificate provisioning has returned to normal processing, and new connection provisioning and onboarding requests are completing successfully.\n\nWe\u2019re Here to Help\nIf you have any questions or need assistance, please contact our support team.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-31T21:23:01.834Z", "resolved_inferred": false, "started_at": "2026-07-31T15:21:53.407Z", @@ -181,7 +181,7 @@ "body": "This issue has been resolved.\n\nCisco Umbrella customers with DNS policies configured to block the \"M365 Copilot\" or \"Microsoft Copilot\" application categories should no longer experience related access issues with Microsoft 365 services.\n\nCustomers who applied the previously provided workaround can review and restore their DNS policy settings as appropriate for their organization\u2019s security requirements.\n\nThank you for your patience. If you continue to experience issues, please contact Cisco Customer Support.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-25T21:09:43.726Z", "resolved_inferred": false, "started_at": "2026-07-25T14:54:46.851Z", @@ -194,7 +194,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-24T13:06:04.338Z", "resolved_inferred": false, "started_at": "2026-07-24T11:39:33.332Z", @@ -207,7 +207,7 @@ "body": "This issue has been resolved.\n\nCisco Umbrella customers using HTTPS inspection in the Los Angeles and Miami regions should no longer experience certificate warnings or errors when accessing websites or applications inspected by Cisco Umbrella.\n\nThank you for your patience. If you continue to experience issues, please contact Cisco Customer Support.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-21T23:04:00.875Z", "resolved_inferred": false, "started_at": "2026-07-21T22:08:36.512Z", @@ -220,7 +220,7 @@ "body": "This issue has been resolved.\n\nMetric links on the Umbrella Overview dashboard page are now directing customers to the expected Activity page.\n\nThank you for your patience. If you continue to experience issues, please contact Cisco Customer Support.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-21T00:37:00.241Z", "resolved_inferred": false, "started_at": "2026-07-20T23:41:47.310Z", @@ -233,7 +233,7 @@ "body": "Mitigation actions have been completed, and Umbrella services are operating normally.\n\nWe're Here to Help\nIf you have any questions or need assistance, please contact our support team.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-15T18:09:24.286Z", "resolved_inferred": false, "started_at": "2026-07-15T15:32:29.000Z", @@ -246,7 +246,7 @@ "body": "The mitigation has been successfully completed across all regions, and the affected Identity service is operating normally.\n\nPolicy processing for ZTA traffic, ZTNA enrollment, new policy creation, and new user connections have been restored. Existing configurations and ongoing data traffic remain unaffected.\n\nWe appreciate your patience while we worked to resolve this issue.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-15T14:37:15.798Z", "resolved_inferred": false, "started_at": "2026-07-15T09:11:19.000Z", @@ -259,7 +259,7 @@ "body": "The connectivity issues affecting the Mexico region have been resolved. The data center was brought back into rotation at 10:20 UTC, and all services are now operating normally.\n\nWe apologize for any inconvenience caused and thank you for your patience.\n\nWe're Here to Help\nIf you have any questions or need assistance, please contact our support team. Thank you for your understanding and support as we work to improve your Cisco Umbrella experience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-11T10:32:00.735Z", "resolved_inferred": false, "started_at": "2026-07-10T23:21:19.000Z", @@ -272,7 +272,7 @@ "body": "The issue affecting dashboard component has been resolved.\n\nAll services are now operating normally.\n\nWe apologize for any inconvenience caused and thank you for your patience.\n\nWe\u2019re Here to Help If you have any questions, please contact our support team. Thank you for your understanding as we improve your Cisco Secure Access experience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-09T02:13:50.724Z", "resolved_inferred": false, "started_at": "2026-07-08T19:09:43.139Z", @@ -285,7 +285,7 @@ "body": "The single sign-on issue affecting Cisco Security Cloud access to the Umbrella UI has been resolved. Customers should now be able to log in successfully.\n\nThank you for your patience and understanding.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-08T16:55:46.000Z", "resolved_inferred": false, "started_at": "2026-07-08T16:32:21.961Z", @@ -298,7 +298,7 @@ "body": "The issue affecting certificate issuance and renewal for the Cisco Secure Connect platform globally between 12:16 UTC and 13:00 UTC on July 07, 2026 has been resolved. All services are now operating normally, and customers can resume onboarding and provisioning new sites.\n\nWe apologize for any inconvenience caused and thank you for your patience.\n\nWe're Here to Help\nIf you have any questions, please contact our support team. Thank you for your understanding as we improve your Cisco Secure onnect experience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-07T13:14:58.173Z", "resolved_inferred": false, "started_at": "2026-07-07T13:14:58.102Z", @@ -311,7 +311,7 @@ "body": "The increased DNS response latency affecting DNS resolution services in Amsterdam has been resolved.\n\nCustomers using DNS resolution services through Amsterdam should no longer experience delayed DNS responses related to this issue.Service has been restored to normal operation.\n\nWe\u2019re Here to Help\nIf you have any questions or need assistance, please contact our support team.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-23T16:08:11.131Z", "resolved_inferred": false, "started_at": "2026-06-23T15:29:38.160Z", @@ -324,7 +324,7 @@ "body": "Between 13:33 UTC and 14:13 UTC on 18 June 2026, customers connected through the London location experienced disruption to traffic processing. The issue has been resolved, and services are operating normally.\n\nWe\u2019re Here to Help\nIf you have any questions or need assistance, please contact our support team.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-18T14:24:34.847Z", "resolved_inferred": false, "started_at": "2026-06-18T14:24:34.795Z", @@ -337,7 +337,7 @@ "body": "The issue affecting the SL VPN service has been resolved.\n\nCustomers connecting to the Ashburn, Miami, and France DCs should no longer experience SL VPN traffic interruptions. Service has been restored, and no further impact is expected.\n\nWe appreciate your patience and understanding during this incident.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-18T00:13:29.063Z", "resolved_inferred": false, "started_at": "2026-06-17T20:34:37.987Z", @@ -350,7 +350,7 @@ "body": "The issue affecting the Umbrella Networks page has been resolved as of 18:55 UTC.\n\nAll services are now operating normally.\n\nWe apologize for any inconvenience caused and thank you for your patience.\n\nWe\u2019re Here to Help If you have any questions, please contact our support team. Thank you for your understanding as we improve your Cisco Secure Access experience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-16T19:06:42.000Z", "resolved_inferred": false, "started_at": "2026-06-16T18:07:02.158Z", @@ -363,7 +363,7 @@ "body": "The connectivity issues affecting Cisco Umbrella services in the Rio de Janeiro region have been resolved. All services are now operating normally and performance has returned to expected levels.\n\nWe apologize for any inconvenience caused and thank you for your patience.\n\nWe\u2019re Here to Help\nIf you have any questions or need assistance, please contact our support team. Thank you for your understanding and support as we work to improve your Cisco Umbrella experience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-14T03:20:41.000Z", "resolved_inferred": false, "started_at": "2026-06-13T23:24:17.348Z", @@ -376,7 +376,7 @@ "body": "Between 18:06 and 18:46 UTC on June 12, 2026, some customers using the Umbrella/Cisco SSE DNS resolver service with DNSCrypt may have experienced DNS resolution issues when traffic was served through Atlanta.\n\nThe issue has been resolved, and DNS resolution has been restored. No further impact is expected.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-12T20:59:37.000Z", "resolved_inferred": false, "started_at": "2026-06-12T20:59:37.000Z", @@ -389,7 +389,7 @@ "body": "On June 4th, 2026, between 17:09 UTC and 18:18 UTC, users experienced intermittent unavailability within specific components of the Cisco Umbrella and Cisco Secure Access dashboards.\n\nAll services are now operating normally.\n\nWe apologize for any inconvenience caused and thank you for your patience.\n\nWe\u2019re Here to Help If you have any questions, please contact our support team. Thank you for your understanding as we improve your Cisco Secure Access experience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-04T19:14:25.903Z", "resolved_inferred": false, "started_at": "2026-06-04T19:14:25.847Z", @@ -402,7 +402,7 @@ "body": "This incident has been resolved. Engineering has restored Cisco Umbrella and Cisco Secure Access dashboard functionality, including impacted policy and administrative workflows.\n\nWe will continue monitoring service health and completing follow-up analysis. No further customer impact is expected at this time.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-04T00:46:55.779Z", "resolved_inferred": false, "started_at": "2026-06-03T20:08:24.312Z", @@ -415,7 +415,7 @@ "body": "The issue affecting services in the Rio de Janeiro region has been resolved. The affected infrastructure has been restored and returned to service, and traffic is now routing normally. Thank you for your patience.\n\nWe\u2019re Here to Help\nIf you have any questions or need assistance, please contact our support team.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-01T17:27:05.000Z", "resolved_inferred": false, "started_at": "2026-06-01T15:07:05.484Z", @@ -428,7 +428,7 @@ "body": "The issues affecting Cisco Umbrella services in the Johannesburg (South Africa) datacenter regions have been resolved. All services are now operating normally.\n\nWe\u2019re Here to Help \nIf you have any questions, please contact our support team. Thank you for your understanding as we improve your Cisco Umbrella experience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-01T11:02:14.000Z", "resolved_inferred": false, "started_at": "2026-06-01T07:12:52.000Z", @@ -441,7 +441,7 @@ "body": "The issue affecting the block page service for customers connecting to the LAX data center has been mitigated.\n\nCustomers should no longer experience intermittent timeouts when accessing websites blocked by policy, and block pages should now load as expected.\n\nOur engineering team will continue to monitor the service to ensure stability. We appreciate your patience and understanding during this incident.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-29T21:36:24.064Z", "resolved_inferred": false, "started_at": "2026-05-29T21:31:10.690Z", @@ -454,7 +454,7 @@ "body": "The issue affecting the download of new Virtual Appliance (VA) images for Cisco Umbrella has been resolved.\n\nCustomers should now be able to successfully download and deploy new virtual appliance instances. Existing virtual appliance upgrades and already deployed instances were not impacted during this issue.\n\nOur engineering teams have implemented the necessary fixes and confirmed that download functionality has been restored.\n\nWe\u2019re Here to Help\nIf you have any questions or need assistance, please contact our support team.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-25T01:24:24.270Z", "resolved_inferred": false, "started_at": "2026-05-25T00:59:34.979Z", @@ -467,7 +467,7 @@ "body": "The issue affecting SRV record resolution for LDAP and Kerberos services has been resolved.\n\nCustomers should no longer experience authentication issues, including intermittent login failures or problems accessing domain resources that rely on LDAP or Kerberos. All services are operating normally.\n\nWe\u2019re Here to Help\nIf you have any questions or need assistance, please contact our support team.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-14T17:45:49.032Z", "resolved_inferred": false, "started_at": "2026-05-13T23:32:25.959Z", @@ -480,7 +480,7 @@ "body": "All network tunnel functionality is now operating normally. Customers can create new tunnels, and existing tunnels and their configurations remain fully functional. Thank you for your patience during this issue.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-11T12:16:04.421Z", "resolved_inferred": false, "started_at": "2026-05-11T10:39:43.435Z", @@ -493,7 +493,7 @@ "body": "The recent network tunnel connectivity issue has been resolved. All services are operating normally, and customers can now create and manage network tunnels as expected. We will continue to monitor for stability.\n\nThank you for your patience and understanding.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-11T13:37:48.448Z", "resolved_inferred": false, "started_at": "2026-05-11T07:12:17.164Z", @@ -506,7 +506,7 @@ "body": "The issue affecting Cisco Umbrella and Secure Connect in Europe Germany Data Center has been resolved.\n\nAll services are now operating normally.\n\nWe apologize for any inconvenience caused and thank you for your patience.\n\nWe\u2019re Here to Help If you have any questions, please contact our support team. Thank you for your understanding as we improve your experience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-11T04:55:08.458Z", "resolved_inferred": false, "started_at": "2026-05-09T07:03:02.397Z", @@ -519,7 +519,7 @@ "body": "The third-party vendor has resolved the certificate provisioning issue, and onboarding processes are now working as expected.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-29T21:54:50.753Z", "resolved_inferred": false, "started_at": "2026-04-29T19:11:05.351Z", @@ -532,7 +532,7 @@ "body": "The issue affecting Zero Trust Access enrollment for some users is resolved.\n\nWe\u2019re Here to Help \nIf you have any questions or need assistance, please contact our support team. Thank you for your understanding and support as we work to enhance your Cisco Secure Connect experience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-08T12:46:05.822Z", "resolved_inferred": false, "started_at": "2026-04-08T10:31:46.453Z", @@ -545,7 +545,7 @@ "body": "The service performance issues affecting our Umbrella/Secure Connect platform in the Chennai and Mumbai regions have been resolved. Our engineering team has stabilized the environment, and all services are now operating as expected.\n\nWe\u2019re Here to Help \nThank you for your patience and understanding while we worked to restore full service. If you have any questions or need assistance, please contact our support team.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-07T06:14:41.916Z", "resolved_inferred": false, "started_at": "2026-04-07T05:00:25.000Z", @@ -558,7 +558,7 @@ "body": "We are pleased to confirm that the issue affecting the Remote Browser Isolation (RBI) service in the Middle East (UAE) data center has been resolved. All services are now operating normally, and customers should no longer experience \"fail open\" errors or unexpected behavior when accessing the RBI service.\n\nThank you for your patience and understanding while we worked to restore full service. If you have any questions or need assistance, please contact our support team.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-01T11:17:22.772Z", "resolved_inferred": false, "started_at": "2026-04-01T04:26:03.933Z", @@ -571,7 +571,7 @@ "body": "We are pleased to confirm that the timeout and slow connection issue affecting services in the Manchester (man1) data center has been fully resolved. All services are now operating normally.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-26T13:08:39.796Z", "resolved_inferred": false, "started_at": "2026-03-26T12:53:37.122Z", @@ -584,7 +584,7 @@ "body": "The issue affecting Cisco Umbrella customers in the Vancouver (YVR) region has been resolved.All services are now operating normally. \n\nWe\u2019re Here to Help\n If you have any questions or need assistance, please contact our support team.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-24T21:07:03.744Z", "resolved_inferred": false, "started_at": "2026-03-24T19:17:55.989Z", @@ -597,7 +597,7 @@ "body": "The issue has been resolved. Services are operating normally, and functionality has been restored.\n\nWe\u2019re Here to Help\nIf you have any questions or need assistance, please contact our support team.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-20T17:19:33.700Z", "resolved_inferred": false, "started_at": "2026-03-20T16:26:07.803Z", @@ -610,7 +610,7 @@ "body": "We are pleased to confirm that the FRA1 data center has been successfully brought Back Into Rotation (BIR). All services are fully operational, and new connections for Cisco+ Secure Connect VPN are now being directed to FRA1 as usual.\n\nThank you for your patience and understanding. If you have any questions or need assistance, please contact our support team.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-20T13:43:13.207Z", "resolved_inferred": false, "started_at": "2026-03-20T11:50:27.000Z", @@ -623,7 +623,7 @@ "body": "Earlier today at approximately 17:20 UTC, users connected to Cisco Secure Connect in the nyc1 data center may have experienced an administrative disconnect.Users were able to manually reconnect to the service, and no further impact was observed.The issue has been resolved, and services are operating normally.\n\nWe\u2019re Here to Help\n If you have any questions or need assistance, please contact our support team.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-18T18:06:32.000Z", "resolved_inferred": false, "started_at": "2026-03-18T18:06:32.000Z", @@ -636,7 +636,7 @@ "body": "The issue affecting the DNS Resolvers service in the Middle East data center has been resolved.\n\nThe service is now operating normally.\n\nWe apologize for any inconvenience caused and thank you for your patience.\n\nWe\u2019re Here to Help:\nIf you have any questions or need assistance, please contact our support team. Thank you for your understanding and support as we work to enhance your Cisco Secure Access experience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-10T05:52:00.000Z", "resolved_inferred": false, "started_at": "2026-03-10T05:14:24.967Z", @@ -649,7 +649,7 @@ "body": "We are pleased to confirm that the display issue impacting the Investigate dashboard has been fully resolved. All dashboard functions are now operating as expected.\n\nThank you for your patience and understanding while we worked to restore full service.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-12T15:23:21.412Z", "resolved_inferred": false, "started_at": "2026-02-27T17:23:18.000Z", diff --git a/api/v/clearlyip.json b/api/v/clearlyip.json index 1d4cc97350d44d12425e76f6aca4ebea25fcf5ee..925801ba13a959d8d87d6dc16b91c4cf22973040 100644 --- a/api/v/clearlyip.json +++ b/api/v/clearlyip.json @@ -3,7 +3,7 @@ "slug": "clearlyip", "platform": "statuspage", "status_url": "https://status.clearlyip.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-09-03T06:54:31.987-05:00", "resolved_inferred": false, "started_at": "2026-09-01T18:00:42.000-05:00", @@ -25,7 +25,7 @@ "body": "Mail continues to flow normally and at expected deliverability rates without delays.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-27T09:18:14.123-05:00", "resolved_inferred": false, "started_at": "2026-08-25T15:51:54.961-05:00", @@ -38,7 +38,7 @@ "body": "Upstream carrier has resolved the issues at approximately 9:13am CST", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-21T10:07:05.755-05:00", "resolved_inferred": false, "started_at": "2026-08-21T08:46:35.941-05:00", @@ -51,7 +51,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-22T14:38:57.086-05:00", "resolved_inferred": false, "started_at": "2026-06-22T11:59:52.200-05:00", @@ -64,7 +64,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-15T12:48:29.140-05:00", "resolved_inferred": false, "started_at": "2026-06-15T07:53:33.039-05:00", @@ -77,7 +77,7 @@ "body": "All services remain stable and operational, free from the previously experienced issues.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-09T20:16:23.023-05:00", "resolved_inferred": false, "started_at": "2026-06-09T14:22:22.652-05:00", @@ -90,7 +90,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-09T12:24:42.991-05:00", "resolved_inferred": false, "started_at": "2026-06-09T09:27:35.678-05:00", @@ -103,7 +103,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-01T15:13:55.737-05:00", "resolved_inferred": false, "started_at": "2026-06-01T08:54:10.040-05:00", @@ -116,7 +116,7 @@ "body": "**Summary / Impact**\n\nOn the afternoon of May 31st, 2026, 14IP's network operations group began to observe connectivity issues with resources located at its US-Central \\(MKE\\) data center.\u00a0 The team began working with their counterparts at the data center facility to understand the nature of the problem.\u00a0 It was quickly determined that a distributed denial of service \\(DDoS\\) attack targeted upstream was affecting all tenants of the data center.\n\nSignificant malicious traffic \\(exceeding 450gbps\\) was measured upstream during the peak of the attack which overwhelmed equipment as well as primary, secondary, and tertiary links.\u00a0 This traffic was mitigated through coordinated, escalating filtering with upstream transit providers, as well as internal engineering to stabilize routing.\n\nDuring the incident, connectivity to systems and services primarily located in this data center were impacted significantly for periods of time between approximately 2 PM ET and 9:30 PM ET.\u00a0 This included Clearly Cloud, ComXchange hosted, Xivea, Business Connect, EPlatform, and several other systems.\u00a0 \\(US-East trunking services continued to operate during the US-Central incident.\\)\n\n**Follow-Up**\n\nSeveral facility-level network and system improvements have been implemented following the incident which should reduce the risk of future occurrences.\u00a0 This includes the deployment of additional DDoS scrubbing capacity, improved granularity for detecting attacks, additional fiber capacity upstream, as well as core network enhancements.\n\n14IP plans additional improvements to its systems and operations to improve platform resilience and flexibility when responding to future incidents.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-01T06:54:41.806-05:00", "resolved_inferred": false, "started_at": "2026-05-31T13:03:07.711-05:00", @@ -129,7 +129,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-28T13:50:44.687-05:00", "resolved_inferred": false, "started_at": "2026-05-28T12:16:37.000-05:00", @@ -142,7 +142,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-27T13:51:31.249-05:00", "resolved_inferred": false, "started_at": "2026-04-27T13:26:07.040-05:00", @@ -155,7 +155,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-08T14:22:04.831-05:00", "resolved_inferred": false, "started_at": "2026-04-03T15:32:25.076-05:00", @@ -168,7 +168,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-19T10:38:19.292-05:00", "resolved_inferred": false, "started_at": "2026-03-19T09:00:51.000-05:00", @@ -181,7 +181,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-13T20:19:37.705-05:00", "resolved_inferred": false, "started_at": "2026-03-13T18:52:01.952-05:00", @@ -194,7 +194,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-19T11:03:38.602-06:00", "resolved_inferred": false, "started_at": "2026-02-19T08:54:55.585-06:00", @@ -207,7 +207,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-15T13:00:57.440-06:00", "resolved_inferred": false, "started_at": "2025-12-15T12:41:17.843-06:00", @@ -220,7 +220,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-04T13:24:07.672-06:00", "resolved_inferred": false, "started_at": "2025-12-04T12:57:22.233-06:00", @@ -233,7 +233,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-02T13:46:11.981-06:00", "resolved_inferred": false, "started_at": "2025-12-02T10:45:56.217-06:00", @@ -246,7 +246,7 @@ "body": "SIP2 and Proxy55 are not responding. Calls routing to failover trunks", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-11T05:15:37.000-06:00", "resolved_inferred": false, "started_at": "2025-11-11T05:15:37.000-06:00", @@ -259,7 +259,7 @@ "body": "At approximately 11:27AM ET on November 3, ClearlyIP's NOC team began to receive system alerts indicating excess session activity within its US-East trunking systems. The team's investigation identified unauthenticated INVITE messages being received from unknown IPs as the source of the excess traffic, as well as a customer generating unexpected levels of outbound calls. Steps were taken to mitigate the traffic's impact, including restarting affected services to clear sessions and restore normal status. By approximately 11:55AM ET, the US-East situation was stabilized and session traffic had returned to normal levels.\n\nThe team has identified a number of improvements and traffic management strategies to help avoid similar incidents which will be implemented in future maintenance events.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-03T12:10:27.375-06:00", "resolved_inferred": false, "started_at": "2025-11-03T10:49:07.359-06:00", @@ -272,7 +272,7 @@ "body": "At approximately 4:10 PM ET, ClearlyIP's monitoring systems detected registration issues within US-Central trunking. Within a few minutes, it was determined that one of the two primary trunking servers was maintaining its active calls \\(2.us-central\\) and that its counterpart \\(1.us-central\\) had stalled and was not accepting traffic.\n\nIt was quickly determined that the issue stemmed from a database cluster deadlock within the US-Central footprint. Upon analysis, the deadlock's cause was identified to be related to unsuccessful credential change activity. A series of actions were taken during the next 30 minutes which restored 2.us-central to service. Following that, maintenance was performed to resolve version differences on the database node not currently in production before restoring it \\(and 1.us-central\\) to normal service shortly after 6PM ET.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-30T16:13:01.287-05:00", "resolved_inferred": false, "started_at": "2025-10-30T15:21:04.448-05:00", @@ -285,7 +285,7 @@ "body": "A scheduled data center facility network maintenance event occurred during the evening of 10/29, which caused a variety of anticipated monitoring alarms during its completion. The data center facility provided expected updates on the maintenance activity and no issues were immediately noted following its conclusion.\n\nAt approximately 8AM ET on 10/30, a customer reported that trunk registrations to the ClearlyIP US-East trunking servers were failing, while US-Central trunks were operating normally. The issue was escalated by support to engineering, as it indicated potential issues with inbound calling mapped to the US-East region and would also affect customers who hadn't configured redundancy with ClearlyIP US-Central trunking. After analysis, some database connectivity issues within the affected data center were identified as likely to be responsible.\n\nThe engineering team conducted a full review of the affected equipment and began work to restore access to the unresponsive database servers. This required a careful review of replication and synchronization states before steps to re-activate each of the affected servers were taken. By approximately 8:45 AM ET, the team had determined data integrity was intact and started operations to restore synchronization between the US-East database notes. At approximately 9 AM ET, US-East trunking servers were reopened to customer traffic. \n\nSystems monitoring and review occurred immediately following US-East reactivation, and support teams were advised to monitor customer equipment for proper re-registration with US-East servers. During final analysis, several process and monitoring improvements were identified for implementation which should help avoid similar monitoring ambiguity \\(and potential disruption\\) during service provider maintenance events.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-30T09:15:28.971-05:00", "resolved_inferred": false, "started_at": "2025-10-30T06:05:53.000-05:00", @@ -298,7 +298,7 @@ "body": "At approximately 2:30 PM ET on October 29, alerts began to be received by ClearlyIP's Network Operations team indicating problems accessing the database cluster used by Clearly Cloud for most US-based customers. This was interfering with call routing for a portion of customers and prevented access to Call Panel and other system components. The team immediately began investigating and observed the problem related to a protective mechanism which had detected large amounts of database request traffic and proactively restarted services to prevent data loss or corruption. The source of the requests was quickly identified, stopped, and determined to be legitimate. The team then checked each server in the cluster before determining it was safe to restore normal service by approximately 2:45 PM ET.\n\nA postmortem analysis on the source of the database traffic identified it to be related to delivering an unusual backlog of SMS and email messages from the platform. Temporary measures were taken to prevent a recurrence of the same issue while long-term improvements are scheduled.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-29T14:17:59.711-05:00", "resolved_inferred": false, "started_at": "2025-10-29T13:37:07.868-05:00", @@ -311,7 +311,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-29T13:37:40.331-05:00", "resolved_inferred": false, "started_at": "2025-10-29T11:51:46.952-05:00", @@ -324,7 +324,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-20T14:12:11.558-05:00", "resolved_inferred": false, "started_at": "2025-10-20T11:45:17.000-05:00", @@ -337,7 +337,7 @@ "body": "Upstream vendor issue has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-19T15:17:53.712-05:00", "resolved_inferred": false, "started_at": "2025-09-19T14:55:11.938-05:00", @@ -350,7 +350,7 @@ "body": "On 9/16 at approximately 1:50 PM CDT, ClearlyIP began to receive indications of connectivity problems affecting the Pulsar360 Denver data center. Infrastructure and network teams were immediately notified and began troubleshooting. The team quickly ruled out internal infrastructure issues, confirming that links to all Pulsar360 equipment were working normally. Within 15 minutes, the team had identified the source of the issue as a regional Internet routing problem caused by actions of an unrelated third-party fiber provider.\n\nThe issue originated within a route \\(BGP\\) advertisement that erroneously included large sections of IP addresses--among them addresses used by Pulsar360's Denver location. That bad route information caused many ISPs to misdirect traffic away from the Denver data center location.\n\nClearlyIP's engineering team pursued parallel efforts to resolve the underlying issue and explore workarounds that could be executed more rapidly. While contact was still being made with the third-party company through upstream contacts, a solution involving forced advertisement of smaller network segments \\(counteracting the large mis-advertisement\\) was tested successfully. The approach was approved quickly and the team immediately began executing it for all of the Pulsar360 Denver network segments during the next 30 minutes, restoring connectivity.\n\nStable connectivity had been achieved across the entire Denver network approximately one hour after the incident had been reported.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-17T15:11:08.507-05:00", "resolved_inferred": false, "started_at": "2025-09-17T14:44:13.225-05:00", @@ -363,7 +363,7 @@ "body": "At approximately 6:18 PM ET, an internal alarm detected a component restart within the Clearly Cloud US platform. The engineering team quickly determined that the component successfully failed over to a redundant system while restarting, but this resulted in a few moments of disruption for dialing and status notifications \\(BLF, MWI, etc.\\) The issue was immediately escalated to key members of the infrastructure and software groups who were conferenced in to analyze the situation. Approximately ten minutes later, another restart \\(and failover\\) occurred, causing another brief disruption to new calls and status updates. \n\nThe team identified the issue to be triggered by data integrity problems with several contact records. Research confirmed that this issue had never been encountered before, occurring while a routine system task purges expired contact records every 10 minutes. Several solutions were explored, and ultimately a repair of the affected data table was performed at approximately 7:40 PM ET, resolving the underlying problem. Additional cleanup tasks were implemented at approximately 8:00 PM as the escalation team monitored the platform. After recording several task cycles without further incident, the team reviewed potential improvements and documented the incident before marking it resolved at approximately 8:15 PM ET.\n\nWhile every part of Clearly Cloud has redundancies and most of these fail over gracefully without impacting operations, the component in question requires a few moments for backup systems to take over. During this timeframe--between a few seconds and a minute--established calls would be unaffected, but new calls may fail to complete and status messages for BLF, MWI, parking, and other notifications may fail to be sent. Although the issue's impact was limited due to the time of day, multiple brief failovers in a short timeframe caused disruption, which was noticed by several users\n\nClearlyIP's engineering team will incorporate what was learned about this incident within upcoming platform improvements.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-13T20:51:30.522-05:00", "resolved_inferred": false, "started_at": "2025-08-13T17:20:58.000-05:00", diff --git a/api/v/clerk.json b/api/v/clerk.json index 476d88e0bc200a1e1b8c94e38422aba6d8632c0c..0fedd44c15caef5def2e46048599adfacf49be8c 100644 --- a/api/v/clerk.json +++ b/api/v/clerk.json @@ -3,16 +3,26 @@ "slug": "clerk", "platform": "statuspage", "status_url": "https://status.clerk.com", -"last_checked": "2026-09-04T09:06:33Z", -"last_state": "ok", +"last_checked": "2026-09-04T10:17:20Z", +"last_state": "degraded", "history_backfilled": true, "first_watched": "2026-09-04T07:16:22Z", "incidents": [ { +"body": "We are seeing delays in email delivery for recipients on Microsoft-hosted mailboxes (Outlook.com, Hotmail, Microsoft 365). Affected emails, including one-time passcodes and verification links, may arrive late or require re-sending. Emails to other providers are delivering normally. We are working with our email provider to restore normal delivery.", +"first_seen": "2026-09-04T10:17:20Z", +"impact": "minor", +"last_seen": "2026-09-04T10:17:20Z", +"started_at": "2026-09-04T10:06:09Z", +"state": "investigating", +"title": "Delayed email delivery to Microsoft (Outlook / Microsoft 365) recipients", +"updated_at": "2026-09-04T10:06:09Z" +}, +{ "body": "Latency and error rates have held steady since the last update. We will re-open if there is a resurgence in errors or latency.", "first_seen": "2026-09-04T07:16:22Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-09-01T19:13:49Z", "resolved_inferred": false, "started_at": "2026-09-01T15:48:03Z", @@ -24,7 +34,7 @@ "body": "API performance has remained stable following mitigation. This incident has been resolved.", "first_seen": "2026-09-04T07:16:22Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-31T15:40:21Z", "resolved_inferred": false, "started_at": "2026-08-31T13:55:24Z", @@ -36,7 +46,7 @@ "body": "We've resolved the issue with our upstream provider.", "first_seen": "2026-09-04T07:16:22Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-04T23:40:50Z", "resolved_inferred": false, "started_at": "2026-08-04T23:03:58Z", @@ -48,7 +58,7 @@ "body": "All systems are operational", "first_seen": "2026-09-04T07:16:22Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-01T10:04:57Z", "resolved_inferred": false, "started_at": "2026-08-01T10:00:01Z", @@ -60,7 +70,7 @@ "body": "Custom domain provisioning is fully operational again", "first_seen": "2026-09-04T07:16:22Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-31T13:00:49Z", "resolved_inferred": false, "started_at": "2026-07-31T12:23:58Z", @@ -72,7 +82,7 @@ "body": "We have confirmed that error rates have returned to baseline.", "first_seen": "2026-09-04T07:16:22Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-16T14:01:08Z", "resolved_inferred": false, "started_at": "2026-07-16T13:04:44Z", @@ -84,7 +94,7 @@ "body": "There was a service degradation on our caching layer that affected the latency of our APIs. The caching layer is back to normal and latency dropped to normal levels.", "first_seen": "2026-09-04T07:16:22Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-16T07:58:00Z", "resolved_inferred": false, "started_at": "2026-07-16T07:56:30Z", @@ -96,7 +106,7 @@ "body": "All domains have been processed from this incident.", "first_seen": "2026-09-04T07:16:22Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-13T01:37:28Z", "resolved_inferred": false, "started_at": "2026-07-12T22:05:48Z", @@ -108,7 +118,7 @@ "body": "The underlying issue has been identified and the Account Portal is now fully functioning again.", "first_seen": "2026-09-04T07:16:22Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-09T20:43:32Z", "resolved_inferred": false, "started_at": "2026-07-09T20:38:10Z", @@ -120,7 +130,7 @@ "body": "We have identified the cause of the delays and our mitigations have been successful. We are continuing to monitor webhook delivery.", "first_seen": "2026-09-04T07:16:22Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-01T17:26:41Z", "resolved_inferred": false, "started_at": "2026-07-01T17:12:21Z", @@ -132,7 +142,7 @@ "body": "A fix has been published and confirmed it's now resolving SVGs correctly", "first_seen": "2026-09-04T07:16:22Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-18T20:23:37Z", "resolved_inferred": false, "started_at": "2026-06-18T20:21:29Z", @@ -144,7 +154,7 @@ "body": "Services are up and running.", "first_seen": "2026-09-04T07:16:22Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-18T16:18:29Z", "resolved_inferred": false, "started_at": "2026-06-18T15:43:35Z", @@ -156,7 +166,7 @@ "body": "Systems are fully operational", "first_seen": "2026-09-04T07:16:22Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-15T15:26:00Z", "resolved_inferred": false, "started_at": "2026-06-15T15:44:49Z", @@ -168,7 +178,7 @@ "body": "All systems are operational", "first_seen": "2026-09-04T07:16:22Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-12T15:29:11Z", "resolved_inferred": false, "started_at": "2026-06-12T14:48:30Z", @@ -180,7 +190,7 @@ "body": "Between 21:21 and 21:56 UTC on June 9, 2026, a portion of requests to our Analytics service failed and Dashboard charts may have failed to load. The cause was a database connection that had been silently closed upstream but was still being reused by our connection pool. We resolved the issue at 21:56 UTC. No data was lost. To prevent recurrence, we are rolling out a change to detect and self-heal from such failures. We apologize for the disruption", "first_seen": "2026-09-04T07:16:22Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-09T22:37:33Z", "resolved_inferred": false, "started_at": "2026-06-09T21:56:49Z", @@ -192,7 +202,7 @@ "body": "APIs have returned to normal operation.", "first_seen": "2026-09-04T07:16:22Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-28T20:32:13Z", "resolved_inferred": false, "started_at": "2026-05-28T19:16:05Z", @@ -204,7 +214,7 @@ "body": "The root cause has been identified and addressed. We will continue to monitor going forward.", "first_seen": "2026-09-04T07:16:22Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-26T22:26:10Z", "resolved_inferred": false, "started_at": "2026-05-26T21:19:09Z", @@ -216,7 +226,7 @@ "body": "Systems are back to normal.", "first_seen": "2026-09-04T07:16:22Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-22T21:43:13Z", "resolved_inferred": false, "started_at": "2026-05-22T15:48:01Z", @@ -228,7 +238,7 @@ "body": "The upstream provider marked the issue as resolved, we're continuing to monitor the database, but no error was observed.", "first_seen": "2026-09-04T07:16:22Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-14T21:05:59Z", "resolved_inferred": false, "started_at": "2026-05-14T20:37:28Z", @@ -240,7 +250,7 @@ "body": "The issue has been resolved.", "first_seen": "2026-09-04T07:16:22Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-11T17:19:37Z", "resolved_inferred": false, "started_at": "2026-05-11T15:00:40Z", @@ -252,7 +262,7 @@ "body": "We continue to work with our DNS provider to discover the source of the issue. We currently believe approximately 0.37% of traffic was impacted by being unable to resolve DNS of the CDN that provides ClerkJS.", "first_seen": "2026-09-04T07:16:22Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-08T14:40:58Z", "resolved_inferred": false, "started_at": "2026-05-08T11:02:35Z", @@ -264,7 +274,7 @@ "body": "We have identified the root cause and are putting in place mitigations to ensure this does not happen in the future.", "first_seen": "2026-09-04T07:16:22Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-08T02:17:02Z", "resolved_inferred": false, "started_at": "2026-05-08T01:39:36Z", @@ -276,7 +286,7 @@ "body": "The issue has been resolved", "first_seen": "2026-09-04T07:16:22Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-27T21:19:00Z", "resolved_inferred": false, "started_at": "2026-04-27T18:43:49Z", @@ -288,7 +298,7 @@ "body": "The issue has been resolved", "first_seen": "2026-09-04T07:16:22Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-26T07:26:00Z", "resolved_inferred": false, "started_at": "2026-04-26T07:39:28Z", diff --git a/api/v/clickup.json b/api/v/clickup.json index f873f505125e61e5c732e48a6b2564f91d85b302..c8ee5e8ee4847a4880fad4011ea8357b6a7b69b2 100644 --- a/api/v/clickup.json +++ b/api/v/clickup.json @@ -3,7 +3,7 @@ "slug": "clickup", "platform": "status.io", "status_url": "http://status.clickup.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": false, "first_watched": "2026-09-04T07:06:16Z", diff --git a/api/v/clojars.json b/api/v/clojars.json index f9cbaabe4c1e7b0446a3532b2b8f70e8d037a83a..5accc0a6bb18c27bc8d730244486caa8f7b46581 100644 --- a/api/v/clojars.json +++ b/api/v/clojars.json @@ -3,7 +3,7 @@ "slug": "clojars", "platform": "statuspage", "status_url": "http://status.clojars.org", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", diff --git a/api/v/cloud-66.json b/api/v/cloud-66.json index b9ad6ca7817e6c83a8c60cd9362efe24cdbc4476..82216988cbb5e8802b353ce304e643e6fa3e3be9 100644 --- a/api/v/cloud-66.json +++ b/api/v/cloud-66.json @@ -3,7 +3,7 @@ "slug": "cloud-66", "platform": "statuspage", "status_url": "http://status.cloud66.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-09-02T11:56:01.991Z", "resolved_inferred": false, "started_at": "2026-08-24T19:08:46.699Z", diff --git a/api/v/cloudampq.json b/api/v/cloudampq.json index 83b6459d56c5ed5b11378e575981159f5b5c9aaf..db2dbbdf1970126e048ac782df2b531db41c9d2e 100644 --- a/api/v/cloudampq.json +++ b/api/v/cloudampq.json @@ -3,7 +3,7 @@ "slug": "cloudampq", "platform": "statuspage", "status_url": "http://status.cloudamqp.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-26T13:57:03.993Z", "resolved_inferred": false, "started_at": "2026-08-26T13:27:48.443Z", @@ -25,7 +25,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-25T23:58:37.121Z", "resolved_inferred": false, "started_at": "2026-08-24T23:52:56.879Z", @@ -38,7 +38,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-23T21:48:36.927Z", "resolved_inferred": false, "started_at": "2026-07-23T15:33:09.000Z", @@ -51,7 +51,7 @@ "body": "**Summary**\n\nBetween June 25 and June 26, our monitoring system incorrectly reported some dedicated servers as unreachable and sent \"server down\" notifications for servers that were in fact operating normally. This was a monitoring-side issue only \u2014 no customer servers or services were actually down, and no data or message delivery was affected.\n\n**Impact**\n\nAffected customers received one or more alerts indicating their dedicated server was down. These alerts were false positives. The servers themselves remained healthy and fully available throughout the incident.\n\n**Root cause**\n\nBefore connecting to a server, our monitoring system performs a network authorization step. A defect in how one component handled a transient network hiccup could leave a monitoring process unable to complete that step, after which it failed to connect to the servers it was responsible for checking. The servers themselves stayed healthy and available throughout \u2014 the monitoring process had simply lost its ability to reach them, and reported them as down.\n\n**Resolution**\n\nWe identified the affected monitoring processes, confirmed the root cause in production, and deployed a fix that makes this authorization step resilient to such transient failures and able to recover automatically. After deploying, we monitored the system to confirm that notifications returned to normal.\n\nWe apologize for the confusion these false notifications may have caused.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-26T14:44:05.273Z", "resolved_inferred": false, "started_at": "2026-06-25T14:10:56.046Z", @@ -64,7 +64,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-31T11:29:59.115Z", "resolved_inferred": false, "started_at": "2026-05-30T22:25:31.999Z", @@ -77,7 +77,7 @@ "body": "Resolved \u2014 Microsoft has confirmed that the Azure West Europe Virtual Machines incident is resolved. The impact window was 14:09\u201314:13 UTC on 23 May 2026, during which a limited number of customers may have experienced connection failures or unexpected Virtual Machine restarts. The Azure environment self-healed and the service has been confirmed restored.\n\nAffected CloudAMQP instances should now be operating normally.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-23T17:23:02.348Z", "resolved_inferred": false, "started_at": "2026-05-23T16:21:47.428Z", @@ -90,7 +90,7 @@ "body": "# Legacy host metrics integrations degraded\n\nIncident window: 2026-05-21 18:37 UTC \u2013 2026-05-22 04:05 UTC \\(9h 28m\\) \nAffected service: Legacy metric integrations \\(CloudWatch, Datadog, Librato, New Relic, Splunk, Stackdriver\\). Host metrics affected, not broker metrics, nor was internal monitoring or console graphs.\n\n## Summary\n\nFor ~9.5 hours, the service that collects host-level metrics \\(CPU, memory, disk, network\\) for legacy third-party integrations entered a crash loop and stopped shipping data.\n\n## Root Cause\n\nAn internal credential-signing service was migrated to a new container runtime the afternoon before. Due to a bug with environment variables the collector could not renew it's credentials. The collector's existing credential remained valid for several hours, so the failure only surfaced when it tried to renew.\n\n## Resolution\n\nOn-call staff detected the failure early morning, developers helped restore the service and collector recovered at 04:05 UTC.\n\n## Prevention\n\n* All services, both signing and collector report failed authentication attempts earlier and with higher severity\n* Metrics pipeline alarm thresholds was tightened so a similar drop in data triggers alarms faster.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-22T04:50:18.054Z", "resolved_inferred": false, "started_at": "2026-05-22T03:16:44.000Z", @@ -103,7 +103,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-19T13:50:23.819Z", "resolved_inferred": false, "started_at": "2026-05-19T13:21:59.259Z", @@ -116,7 +116,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-05T13:23:45.200Z", "resolved_inferred": false, "started_at": "2026-05-05T10:23:31.681Z", @@ -129,7 +129,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-04T01:44:56.079Z", "resolved_inferred": false, "started_at": "2026-05-03T19:11:24.214Z", @@ -142,7 +142,7 @@ "body": "We had an abnormal increase in traffic causing timeouts and slow responses for customer.cloudamqp.com, we increased capacity and are back to normal. This did not affect any running clusters, just provisioning and configuration updates.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-28T11:05:08.000Z", "resolved_inferred": false, "started_at": "2026-04-28T10:27:23.381Z", @@ -155,7 +155,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-24T10:05:50.000Z", "resolved_inferred": false, "started_at": "2026-04-24T09:36:54.658Z", @@ -168,7 +168,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-23T10:56:07.811Z", "resolved_inferred": false, "started_at": "2026-04-23T10:10:49.006Z", @@ -181,7 +181,7 @@ "body": "Broker metrics and metrics integrations degradation\n\nWindow: 2026-04-23 03:25 \u2013 05:35 UTC \\(2h 10m\\)\n\n## Impact\n\nBroker metrics \\(connections, channels, queues, consumers, message rates, node and netsplit state\\) were degraded, progressively dropping until recovery at 05:35 UTC. Downstream effects:\n\n* Queue, Consumer, Connection, Channel, Connection flow, and Netsplit alarms: threshold breaches during the window may not have triggered, or triggered late. Alarms already tripped before 03:25 UTC kept \n their state.\n* Metrics Integrations \\(Datadog, CloudWatch, New Relic, Splunk, Dynatrace, etc.\\): delivery of broker metrics was reduced for the duration of the window. Alarms configured on the receiving side may \n likewise have missed or lagged.\n\nNot affected: server metrics \\(CPU, memory, disk\\) and their corresponding alarms, Notice alarms, broker availability, and the metric graphs shown in the CloudAMQP console \\(these use a separate data path \nand continued to update normally\\).\n\n## Timeline \\(UTC\\)\n\n* 03:25 \u2014 broker-metrics collection begins degrading\n* 03:35 \u2014 ~30% of broker-metric samples missing\n* 03:50 \u2014 ~50% plateau\n* 05:25 \u2014 collector workers cycled and re-initialised\n* 05:35 \u2014 full throughput restored\n\n## Root cause\n\nBroker metrics are polled from each cluster's management HTTP API by a pool of collector workers and published to an internal message bus that both the Alarms service and Metrics Integrations consume \nfrom. At 03:25 UTC this service became unresponsive without raising an error. Affected workers silently stopped polling while remaining alive to the platform, so automatic restart did not trigger. On-call \n staff began investigating around 05:00 UTC; force-restarting the service restored metric flow.\n\nThe exact trigger has not been identified. Our focus is on ensuring the condition is detected and handled promptly if it recurs.\n\n## What we are changing\n\n* Added metrics and alarms specific to this service, with high-urgency paging for on-call.\n* Reliability improvements in the service itself to detect and restart stalled work.\n\n## What you can do\n\nCloudAMQP offers a new generation of metrics integrations based on Prometheus, with a re-engineered pipeline that does not rely on these centralised services \u2014 each server forwards data directly to your \nendpoint. These have been running in production for some time and have proved very reliable.\n\n* [https://www.cloudamqp.com/blog/prometheus-metrics-integrations.html](https://www.cloudamqp.com/blog/prometheus-metrics-integrations.html)\n* [https://www.cloudamqp.com/docs/monitoring\\_metrics\\_datadog\\_v3.html](https://www.cloudamqp.com/docs/monitoring_metrics_datadog_v3.html)\n* Background: [https://www.cloudamqp.com/blog/decentralized-observability-with-open-telemetry-part-1.html](https://www.cloudamqp.com/blog/decentralized-observability-with-open-telemetry-part-1.html)", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-23T06:00:29.000Z", "resolved_inferred": false, "started_at": "2026-04-23T03:30:55.000Z", @@ -194,7 +194,7 @@ "body": "One of our backend components suffered a small outage due to an unexpected full services restart. Connectivity with the servers were broken and service triggered alarms for many clusters.\n\nWe apologize for the inconvenience. All clusters were operational and healthy within the incident/alarms timespan.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-15T14:00:00.000Z", "resolved_inferred": false, "started_at": "2026-04-15T14:00:00.000Z", @@ -207,7 +207,7 @@ "body": "The Management UI SSO shortcut is back to service.\n\nImpacted Clusters:\nAll customers with clusters created more than 6 months ago\n\nCause:\nSome code changes unexpectedly changed the communication schema between our backend services and the SSO component on the clusters. The proxy configuration conflicted with those changes causing the 502 Bad Gateway error to show up.\n\nImpact:\nOnly the SSO via CloudAMQP Console was impacted given it required communication with our backend components. The AMQP Clusters were healthy and servicing traffic via both AMQP and HTTP on Management UI and API.\nLogging into the Management UI via Credentials and all Authentications Backends was functioning normally.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-02T15:12:18.451Z", "resolved_inferred": false, "started_at": "2026-04-02T14:41:09.826Z", @@ -220,7 +220,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-25T18:03:19.554Z", "resolved_inferred": false, "started_at": "2026-03-25T17:45:56.264Z", @@ -233,7 +233,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-19T03:50:08.680Z", "resolved_inferred": false, "started_at": "2026-03-18T21:25:45.743Z", @@ -246,7 +246,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-04T14:14:42.242Z", "resolved_inferred": false, "started_at": "2026-03-03T21:11:20.327Z", @@ -259,7 +259,7 @@ "body": "### Summary\n\nOn March 3, an internal monitoring metric stopped being reported for approximately 14 hours. No customer metrics delivery was affected, all integrations continued operating normally. The missing metric caused our dashboards to display false failure rates, which was \nincorrectly reported as a metrics delivery outage.\n\n### Impact\n\nNone. Metrics continued to be delivered to all customer endpoints throughout the incident.\n\n### Resolution\n\nThe monitoring metric was restored and we have updated our alerting queries to be resilient to missing data, preventing false positives in the future.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-03T20:51:22.342Z", "resolved_inferred": false, "started_at": "2026-03-03T18:28:21.809Z", @@ -272,7 +272,7 @@ "body": "We are suspending active updates on this status page regarding the AWS Middle East (Bahrain/UAE) outages. We will start supporting those regions again when they have been fully recovered. Reach out to support@cloudamqp.com if you have any questions.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-05T06:55:34.744Z", "resolved_inferred": false, "started_at": "2026-03-02T05:35:34.912Z", @@ -285,7 +285,7 @@ "body": "We are suspending active updates on this status page regarding the AWS Middle East (Bahrain/UAE) outages. We will start supporting those regions again when they have been fully recovered. Reach out to support@cloudamqp.com if you have any questions.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-05T06:55:12.078Z", "resolved_inferred": false, "started_at": "2026-03-01T13:20:55.739Z", @@ -298,7 +298,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-18T15:30:42.913Z", "resolved_inferred": false, "started_at": "2026-02-17T19:31:27.408Z", @@ -311,7 +311,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-03T15:28:16.791Z", "resolved_inferred": false, "started_at": "2026-02-03T14:47:54.350Z", @@ -324,7 +324,7 @@ "body": "This incident has been resolved by Azure, https://azure.status.microsoft/en-us/status", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-03T08:17:09.288Z", "resolved_inferred": false, "started_at": "2026-02-03T02:53:23.770Z", @@ -337,7 +337,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-14T16:58:44.133Z", "resolved_inferred": false, "started_at": "2026-01-14T15:54:03.856Z", @@ -350,7 +350,7 @@ "body": "This incident has been resolved by third party.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-11T13:12:21.112Z", "resolved_inferred": false, "started_at": "2025-12-11T12:16:32.974Z", @@ -363,7 +363,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-10T13:13:15.626Z", "resolved_inferred": false, "started_at": "2025-12-10T10:13:57.543Z", @@ -376,7 +376,7 @@ "body": "This incident has been resolved", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-19T16:03:03.706Z", "resolved_inferred": false, "started_at": "2025-11-19T15:07:48.123Z", @@ -389,7 +389,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-18T02:03:55.681Z", "resolved_inferred": false, "started_at": "2025-11-17T22:52:38.569Z", @@ -402,7 +402,7 @@ "body": "We have observed that impacted clusters has restored services, and are working to ensure everything is back to normal.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-06T01:50:25.906Z", "resolved_inferred": false, "started_at": "2025-11-05T17:47:22.705Z", @@ -415,7 +415,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-30T15:30:22.043Z", "resolved_inferred": false, "started_at": "2025-10-30T03:31:44.499Z", @@ -428,7 +428,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-29T17:58:56.801Z", "resolved_inferred": false, "started_at": "2025-10-29T17:24:45.379Z", @@ -441,7 +441,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-24T05:38:11.869Z", "resolved_inferred": false, "started_at": "2025-10-24T02:21:57.940Z", @@ -454,7 +454,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-20T20:39:27.573Z", "resolved_inferred": false, "started_at": "2025-10-20T17:14:41.000Z", @@ -467,7 +467,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-13T20:27:02.626Z", "resolved_inferred": false, "started_at": "2025-10-13T17:01:10.452Z", @@ -480,7 +480,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-13T17:00:18.885Z", "resolved_inferred": false, "started_at": "2025-10-13T16:44:20.263Z", @@ -493,7 +493,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-27T05:37:20.615Z", "resolved_inferred": false, "started_at": "2025-09-27T01:02:34.390Z", @@ -506,7 +506,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-15T17:40:05.947Z", "resolved_inferred": false, "started_at": "2025-09-15T13:41:19.293Z", diff --git a/api/v/cloudbees.json b/api/v/cloudbees.json index 2b47b1bb7ed02044925acb6b0e142aeff73036d1..d4edf3369089af6b8d692b8a82d9fbcbabca048f 100644 --- a/api/v/cloudbees.json +++ b/api/v/cloudbees.json @@ -3,7 +3,7 @@ "slug": "cloudbees", "platform": "statuspage", "status_url": "https://www.cloudbeesstatus.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-23T08:56:02.362Z", "resolved_inferred": false, "started_at": "2026-06-23T07:17:31.627Z", @@ -25,7 +25,7 @@ "body": "The incident has been fixed and the Unify AI assistant available to the customers.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-08T11:04:04.847Z", "resolved_inferred": false, "started_at": "2026-05-08T10:57:06.531Z", @@ -38,7 +38,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-20T10:52:36.752Z", "resolved_inferred": false, "started_at": "2025-10-20T10:19:35.933Z", @@ -51,7 +51,7 @@ "body": "Customer(s) could not login to the https://app.rollout.io/cloudbees/login due to an FM outage", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-05T08:30:00.000Z", "resolved_inferred": false, "started_at": "2025-10-05T08:30:00.000Z", diff --git a/api/v/cloudcheckr.json b/api/v/cloudcheckr.json index 660a8251771c9adb0e3385d22e72e1f4b9a225d6..bcf0ce69002560cb5dba1fa27021acaee8ec7a2e 100644 --- a/api/v/cloudcheckr.json +++ b/api/v/cloudcheckr.json @@ -3,7 +3,7 @@ "slug": "cloudcheckr", "platform": "statuspage", "status_url": "https://trust.cloudcheckr.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "unknown", "history_backfilled": false, "first_watched": "2026-09-04T07:06:16Z", diff --git a/api/v/cloudera.json b/api/v/cloudera.json index cd6ce30ed8b8aa5906985c072a877c4d29b083da..6699bbbfb33e2b039dd3cd4ef529aebe656c3749 100644 --- a/api/v/cloudera.json +++ b/api/v/cloudera.json @@ -3,7 +3,7 @@ "slug": "cloudera", "platform": "statuspage", "status_url": "https://status.cloudera.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "Current Status: Our teams have successfully implemented a solution to resolve the issue. Our teams are currently monitoring the solution and will provide another update once confirmed.\n\nCustomer Experience: Customer may have observed an Error message: \"no healthy upstream\" while accessing Cloudera Management Console.\nIf you are still experiencing issues or have any questions, please raise a support case with us. A Root Cause Analysis (RCA) will be published within seven business days.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-09-04T02:47:17.907Z", "resolved_inferred": false, "started_at": "2026-09-03T23:18:07.714Z", @@ -25,7 +25,7 @@ "body": "On March 10, 2026, between 15:23 UTC to 17:09 UTC, users may have experienced intermittent connectivity issues accessing the workloads in the Cloudera Management Console of the US region.\n\nThis disruption was traced to the termination of jumpgate-proxy pods, which entered an OOMKilled status after memory utilization exceeded configured limits. This, in turn, impacted connectivity between the control plane and the workloads within the Cloudera Management Console.\n\nService consistency was restored by increasing the memory limits and replica counts for the jumpgate-proxy deployment.\n\nTo prevent recurrence, we will implement alerting mechanisms for jumpgate pod memory utilization and pod states \\(such as CrashLoopBackoff or OOMKilled events\\). This will enable us to proactively detect and mitigate memory pressure before it impacts service availability. We will implement autoscaling to autoheal and respond to increased load.\n\nWe sincerely apologise for any inconvenience this service disruption may have caused. We appreciate your patience as we worked to restore service functionality.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-11T10:00:00.000Z", "resolved_inferred": false, "started_at": "2026-05-11T10:00:00.000Z", @@ -38,7 +38,7 @@ "body": "On March 10, 2026, around 19:56 UTC users may have started experiencing intermittent timeouts accessing the Cloudera Management Console across the US, EU, and AP regions.\u00a0\n\nThis disruption was traced to an internal service certificate expiration where, despite a successful renewal initiation, a misalignment in the deployment sequence prevented the updated credentials from propagating to the active service mesh. The impact was strictly limited to administrative console and API access; all existing data workloads and running environments continued to operate without interruption.\u00a0\n\nService consistency was restored by regenerating and manually applying the certificates across all affected clusters. To prevent recurrence, we have audited all regional clusters and are transitioning to an automated lifecycle for mesh-level certificates.\u00a0\n\nWe sincerely apologize for any inconvenience this service disruption may have caused. We are addressing monitoring gaps to detect these issues before they impact you, our customers. We appreciate your patience as we worked to restore service functionality.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-10T20:00:00.000Z", "resolved_inferred": false, "started_at": "2026-03-10T20:00:00.000Z", @@ -51,7 +51,7 @@ "body": "The intermittent performance and access issues with the Cloudera Management Console and FreeIPA were triggered by a scheduled service upgrade intended to improve platform stability.\n\nOur investigation determined that a change in a core component introduced a latent configuration issue. This specific condition was not exposed in our testing environments, preventing dependent services from applying dynamic configuration updates in production and leading to the outage.\n\nWe've taken immediate action to prevent this issue from recurring: \nSystem Fix: The problematic component change was rolled back, and a permanent patch was deployed to restore proper dynamic configuration functionality. \nProcess Overhaul: We've implemented a more rigorous upgrade process with mandatory, near-production scale validation steps that specifically test for these types of configuration failures. \nEnhanced Monitoring: We significantly improved our monitoring and alerting capabilities to detect these abnormal service behaviours much earlier, ensuring a faster response time.\n\nWe are dedicated to providing a reliable platform and will continue to invest in our infrastructure and processes. Thank you again for your patience and understanding", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-25T17:02:03.359Z", "resolved_inferred": false, "started_at": "2025-09-25T10:23:34.323Z", @@ -64,7 +64,7 @@ "body": "The intermittent performance and access issues with the Cloudera Management Console and FreeIPA were triggered by a scheduled service upgrade intended to improve platform stability.\n\nOur investigation determined that a change in a core component introduced a latent configuration issue. This specific condition was not exposed in our testing environments, preventing dependent services from applying dynamic configuration updates in production and leading to the outage.\n\nWe've taken immediate action to prevent this issue from recurring: \nSystem Fix: The problematic component change was rolled back, and a permanent patch was deployed to restore proper dynamic configuration functionality. \nProcess Overhaul: We've implemented a more rigorous upgrade process with mandatory, near-production scale validation steps that specifically test for these types of configuration failures. \nEnhanced Monitoring: We significantly improved our monitoring and alerting capabilities to detect these abnormal service behaviours much earlier, ensuring a faster response time.\n\nWe are dedicated to providing a reliable platform and will continue to invest in our infrastructure and processes. Thank you again for your patience and understanding", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-25T17:01:35.247Z", "resolved_inferred": false, "started_at": "2025-09-24T19:42:22.945Z", @@ -77,7 +77,7 @@ "body": "A recent system update, intended to enhance stability of our platform, inadvertently led to an unforeseen memory issue affecting a critical internal service responsible for platform access management.\n\n\u200c\n\nA subsequent incoming request spike caused the memory limits exhaustion, which resulted in the service to become intermittently unavailable.\n\n\u200c\n\nThe memory allocation for the service was manually increased, which restored normal operations. This change was then made permanent to circumvent any recurrence.\n\n\u200c\n\nWe have implemented more robust monitoring and alerting to detect similar issues in the future before they can impact our customers. This includes updating the existing alerts for resource exhaustion and adding new alerts based on the incident, to ensure that the right teams are notified immediately.\n\n\u200c\n\nWe are dedicated to providing a reliable and performant platform. We will continue to invest in improving our infrastructure and processes to prevent future disruptions. We appreciate your patience and understanding as we worked to resolve this issue.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-13T15:18:43.292Z", "resolved_inferred": false, "started_at": "2025-08-13T14:33:47.920Z", diff --git a/api/v/cloudfanatic.json b/api/v/cloudfanatic.json index bed851cc641a78120ec610657dd9f723bc5f13a8..b1c1c0bd47342454da69613ea036f2effe6943b1 100644 --- a/api/v/cloudfanatic.json +++ b/api/v/cloudfanatic.json @@ -3,7 +3,7 @@ "slug": "cloudfanatic", "platform": "instatus", "status_url": "https://status.cloudfanatic.net", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": false, "first_watched": "2026-09-04T07:06:16Z", diff --git a/api/v/cloudflare.json b/api/v/cloudflare.json index a33509e0f11d835742cd6066e557925afaac956a..a71e307aaf2400d9fa064a2f4607e6259b07e119 100644 --- a/api/v/cloudflare.json +++ b/api/v/cloudflare.json @@ -3,7 +3,7 @@ "slug": "cloudflare", "platform": "statuspage", "status_url": "https://www.cloudflarestatus.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "degraded", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "Scheduled maintenance is currently in progress. We will provide updates as necessary.", "first_seen": "2026-09-04T09:06:33Z", "impact": "maintenance", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "started_at": "2026-09-04T09:00:00.000Z", "state": "maintenance", "title": "SEA (Seattle) on 2026-09-04", @@ -23,7 +23,7 @@ "body": "Scheduled maintenance is currently in progress. We will provide updates as necessary.", "first_seen": "2026-09-04T07:06:16Z", "impact": "maintenance", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "started_at": "2026-09-04T06:00:00.000Z", "state": "maintenance", "title": "YUL (Montr\u00e9al) on 2026-09-04", @@ -34,7 +34,7 @@ "body": "Between 2:48-3:04 UTC customers reaching Tokyo, JP may have experienced elevated connection resets and latency due to a hardware failure.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-09-04T02:48:37.000Z", "resolved_inferred": false, "started_at": "2026-09-04T04:58:37.879Z", @@ -47,7 +47,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-09-04T03:28:06.967Z", "resolved_inferred": false, "started_at": "2026-09-04T02:58:25.000Z", @@ -60,7 +60,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-09-04T04:09:34.228Z", "resolved_inferred": false, "started_at": "2026-09-03T23:35:48.000Z", @@ -73,7 +73,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-09-03T09:36:02.061Z", "resolved_inferred": false, "started_at": "2026-09-03T09:21:19.000Z", @@ -99,7 +99,7 @@ "body": "Some customers may have observed 522s from 06:30UTC to 07:38 UTC for traffic landing in Seattle (SEA). Impact windows may vary by customer. The issue has been resolved", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-09-03T06:30:00.000Z", "resolved_inferred": false, "started_at": "2026-09-03T05:30:00.000Z", @@ -112,7 +112,7 @@ "body": "Between 1:04-1:28 UTC customers reaching Western North America region R2 buckets may have experienced an elevated number of 503 errors.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-09-03T01:49:18.347Z", "resolved_inferred": false, "started_at": "2026-09-03T01:49:18.259Z", @@ -125,7 +125,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-09-02T15:51:23.581Z", "resolved_inferred": false, "started_at": "2026-09-02T14:47:26.000Z", @@ -138,7 +138,7 @@ "body": "Cloudflare is aware of, and has resolved, increased latency and packet loss in Taipei. \nThis lasted between 08:42 and 0915 UTC on the 2nd September.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-09-02T08:42:00.000Z", "resolved_inferred": false, "started_at": "2026-09-02T08:42:00.000Z", @@ -151,7 +151,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-09-02T02:24:25.688Z", "resolved_inferred": false, "started_at": "2026-09-02T01:02:41.000Z", @@ -164,7 +164,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-09-02T07:58:55.912Z", "resolved_inferred": false, "started_at": "2026-09-01T21:51:16.000Z", @@ -177,7 +177,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-09-01T22:05:44.265Z", "resolved_inferred": false, "started_at": "2026-09-01T21:47:09.000Z", @@ -190,7 +190,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-09-02T07:16:16.890Z", "resolved_inferred": false, "started_at": "2026-09-01T20:06:47.000Z", @@ -203,7 +203,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-09-01T12:05:52.779Z", "resolved_inferred": false, "started_at": "2026-09-01T08:38:51.000Z", @@ -216,7 +216,7 @@ "body": "This incident has been resolved and the developer documentation has also been updated to reflect the same information: https://developers.cloudflare.com/cloudflare-one/integrations/identity-providers/one-time-pin/#allow-otp-emails-through-your-email-gateway", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-31T22:02:59.000Z", "resolved_inferred": false, "started_at": "2026-08-31T20:16:29.000Z", @@ -229,7 +229,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-09-03T19:32:54.106Z", "resolved_inferred": false, "started_at": "2026-08-31T18:47:05.000Z", @@ -242,7 +242,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-31T14:50:56.052Z", "resolved_inferred": false, "started_at": "2026-08-31T11:40:21.000Z", @@ -255,7 +255,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-31T15:04:13.055Z", "resolved_inferred": false, "started_at": "2026-08-31T11:01:59.000Z", @@ -268,7 +268,7 @@ "body": "Customers may have observed issues for traffic handled by our Montr\u00e9al facility between approximately 16:00 and 16:10 UTC today, 2026-08-29.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-29T17:33:44.816Z", "resolved_inferred": false, "started_at": "2026-08-29T17:33:44.756Z", @@ -281,7 +281,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-29T00:43:53.498Z", "resolved_inferred": false, "started_at": "2026-08-28T17:36:54.000Z", @@ -294,7 +294,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-27T22:58:12.068Z", "resolved_inferred": false, "started_at": "2026-08-27T21:19:40.000Z", @@ -307,7 +307,7 @@ "body": "We are continuing to work on a fix for this issue.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "started_at": "2026-08-27T18:46:19.000Z", "state": "identified", "title": "Incorrect geo location for some Cloudflare WARP users", @@ -318,7 +318,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-27T19:29:35.227Z", "resolved_inferred": false, "started_at": "2026-08-27T14:40:38.000Z", @@ -331,7 +331,7 @@ "body": "APIs for Meeting creation/ Participant creation were all failing between UTC 08:42 to UTC 08:50. Running meetings/ Recordings and session participants not impacted.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-27T08:42:00.000Z", "resolved_inferred": false, "started_at": "2026-08-27T07:42:00.000Z", @@ -344,7 +344,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-26T21:30:32.000Z", "resolved_inferred": false, "started_at": "2026-08-26T20:08:32.000Z", @@ -357,7 +357,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-26T15:38:03.408Z", "resolved_inferred": false, "started_at": "2026-08-26T14:59:16.000Z", @@ -370,7 +370,7 @@ "body": "Cloudflare investigated issues with network performance in Los Angeles from 21:33 - 21:45 UTC.\nThe issue is currently resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-25T21:30:00.000Z", "resolved_inferred": false, "started_at": "2026-08-25T21:30:00.000Z", @@ -383,7 +383,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-25T14:52:41.475Z", "resolved_inferred": false, "started_at": "2026-08-24T20:38:27.000Z", @@ -396,7 +396,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-24T06:53:37.780Z", "resolved_inferred": false, "started_at": "2026-08-24T05:47:34.000Z", @@ -409,7 +409,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-24T08:28:22.387Z", "resolved_inferred": false, "started_at": "2026-08-24T03:53:58.000Z", @@ -422,7 +422,7 @@ "body": "Between 23rd August 2026, 01:06 UTC - 01:54 UTC, some customers may have experienced elevated 5xx errors and timeouts for traffic between North American origins and our Singapore data centre.\n\nThis issue is now resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-23T02:00:00.000Z", "resolved_inferred": false, "started_at": "2026-08-23T02:00:00.000Z", @@ -435,7 +435,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-22T02:57:56.480Z", "resolved_inferred": false, "started_at": "2026-08-22T02:31:34.000Z", @@ -448,7 +448,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-21T21:33:58.790Z", "resolved_inferred": false, "started_at": "2026-08-21T20:43:30.000Z", @@ -461,7 +461,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-21T19:39:57.951Z", "resolved_inferred": false, "started_at": "2026-08-21T17:39:20.000Z", @@ -474,7 +474,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-21T15:19:56.036Z", "resolved_inferred": false, "started_at": "2026-08-21T14:59:50.000Z", @@ -487,7 +487,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-21T07:45:56.214Z", "resolved_inferred": false, "started_at": "2026-08-21T07:31:30.000Z", @@ -500,7 +500,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-21T08:22:29.569Z", "resolved_inferred": false, "started_at": "2026-08-21T06:40:44.000Z", @@ -513,7 +513,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-21T00:13:54.635Z", "resolved_inferred": false, "started_at": "2026-08-21T00:05:23.000Z", @@ -526,7 +526,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-20T22:59:33.508Z", "resolved_inferred": false, "started_at": "2026-08-20T19:19:19.000Z", @@ -539,7 +539,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-20T19:32:37.615Z", "resolved_inferred": false, "started_at": "2026-08-20T18:51:08.000Z", @@ -552,7 +552,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-20T17:48:08.512Z", "resolved_inferred": false, "started_at": "2026-08-20T16:48:25.000Z", @@ -565,7 +565,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-20T14:00:10.932Z", "resolved_inferred": false, "started_at": "2026-08-20T13:10:35.000Z", @@ -578,7 +578,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-20T15:14:12.519Z", "resolved_inferred": false, "started_at": "2026-08-20T11:38:10.000Z", @@ -591,7 +591,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-20T05:58:05.134Z", "resolved_inferred": false, "started_at": "2026-08-20T05:41:51.000Z", @@ -604,7 +604,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-19T23:23:29.961Z", "resolved_inferred": false, "started_at": "2026-08-19T21:19:49.000Z", @@ -617,7 +617,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-19T17:24:19.550Z", "resolved_inferred": false, "started_at": "2026-08-19T16:15:29.000Z", @@ -630,7 +630,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-19T07:20:23.527Z", "resolved_inferred": false, "started_at": "2026-08-19T06:59:19.000Z", @@ -643,7 +643,7 @@ "body": "This incident is now resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-18T16:34:54.405Z", "resolved_inferred": false, "started_at": "2026-08-18T16:16:42.000Z", @@ -656,7 +656,7 @@ "body": "This incident is now resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-17T22:41:47.937Z", "resolved_inferred": false, "started_at": "2026-08-17T19:56:52.000Z", @@ -669,7 +669,7 @@ "body": "This incident is now resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-17T20:44:32.240Z", "resolved_inferred": false, "started_at": "2026-08-17T19:34:15.000Z", @@ -682,7 +682,7 @@ "body": "This incident is now resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-17T19:25:39.299Z", "resolved_inferred": false, "started_at": "2026-08-17T17:26:26.000Z", diff --git a/api/v/cloudrepo.json b/api/v/cloudrepo.json index 9995feaa367bae4f6797466abdcc4a60952094ee..142b7f5b328b6228a8b9e8f1345745349f850afe 100644 --- a/api/v/cloudrepo.json +++ b/api/v/cloudrepo.json @@ -3,7 +3,7 @@ "slug": "cloudrepo", "platform": "statuspage", "status_url": "https://status.cloudrepo.io", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", diff --git a/api/v/cloudsigma.json b/api/v/cloudsigma.json index 77795de3fe1f06d20277e3235a86097eee90dcc3..7879afadb94500694cbd4aa09dbbf27bc7925604 100644 --- a/api/v/cloudsigma.json +++ b/api/v/cloudsigma.json @@ -3,7 +3,7 @@ "slug": "cloudsigma", "platform": "statuspage", "status_url": "https://status.cloudsigma.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "degraded", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -25,7 +25,7 @@ "body": "CloudSigma would like to inform you that we are currently experiencing connectivity issues with one of our upstream ISPs.\n\nThe issue appears to be related to routing, with the majority of the packet loss observed on traffic originating from Europe. The affected locations are Clark and Manila2.\n\nOur team is working with the ISP to investigate and resolve the issue. We will provide further updates as soon as more information becomes available.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "started_at": "2026-09-03T09:12:29.547Z", "state": "investigating", "title": "[MNL2][CRK] Connectivity Issues", @@ -36,7 +36,7 @@ "body": "CloudSigma would like to inform you that the PaaS platform is now fully functional in our Clark cloud location. \n\nPlease accept our sincere apologies for any inconvenience caused, and thank you for your patience and understanding.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-31T15:08:28.797Z", "resolved_inferred": false, "started_at": "2026-08-31T12:38:26.000Z", @@ -49,7 +49,7 @@ "body": "CloudSigma would like to inform you that the issue affecting our CAI location has been fully resolved. The issue has been identified as related to an upstream ISP connectivity problem, which was affecting access to the CAI location and the services hosted within it.\n\nWe apologize for any inconvenience and appreciate your patience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-06T22:44:41.718Z", "resolved_inferred": false, "started_at": "2026-08-06T19:48:05.819Z", @@ -62,7 +62,7 @@ "body": "Cloudsigma would like to inform you that the network connectivity issues affecting the Manila location have been resolved. All services are operating normally.\n\nWe appreciate your patience during this incident.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-30T20:45:54.293Z", "resolved_inferred": false, "started_at": "2026-07-30T20:12:12.588Z", @@ -75,7 +75,7 @@ "body": "Cloudsigma would like to inform you that the network connectivity issues affecting the Manila location have been resolved. All services are operating normally.\n\nWe appreciate your patience during this incident.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-30T20:45:53.109Z", "resolved_inferred": false, "started_at": "2026-07-30T20:12:11.112Z", @@ -88,7 +88,7 @@ "body": "CloudSigma would like to inform you that the issue affecting our CAI location has been fully resolved. The issue has been identified as related to an upstream ISP connectivity problem, which was affecting access to the CAI location and the services hosted within it.\n\nWe apologize for any inconvenience and appreciate your patience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-21T03:10:35.654Z", "resolved_inferred": false, "started_at": "2026-07-21T02:28:54.857Z", @@ -101,7 +101,7 @@ "body": "CloudSigma would like to inform you that the issue affecting the availability of our compute hosts on the Dublin cloud has been resolved.\n\nThank you for your patience and understanding.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-19T00:28:08.513Z", "resolved_inferred": false, "started_at": "2026-07-18T18:14:11.696Z", @@ -114,7 +114,7 @@ "body": "CloudSigma would like to inform you that the issue with the degraded performance on our network infrastructure in the Manila 2 and Clark clouds has been fixed. \n\nPlease accept our apologies for the inconvenience caused!", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-09T21:16:12.894Z", "resolved_inferred": false, "started_at": "2026-07-09T19:56:51.181Z", @@ -127,7 +127,7 @@ "body": "CloudSigma would like to inform you that the WebVNC feature for the WebApp in our Manila cloud location has been restored.\n\nOur administrators have resolved the issue, and the service is now operating normally.\n\nWe apologize for any inconvenience caused and thank you for your patience and understanding.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-15T19:07:09.480Z", "resolved_inferred": false, "started_at": "2026-06-14T12:41:38.850Z", @@ -140,7 +140,7 @@ "body": "CloudSigma would like to inform you that the platform's degraded performance in the Monterrey cloud location has been resolved, and it is now operational and stable.\n\nWe apologize for any inconvenience caused.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-05T02:25:23.171Z", "resolved_inferred": false, "started_at": "2026-06-05T00:25:09.185Z", @@ -153,7 +153,7 @@ "body": "CloudSigma would like to inform you that the issue affecting some of our compute hosts in the Frankfurt cloud location has been resolved.\n\nThank you for your patience and understanding.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-02T23:06:36.390Z", "resolved_inferred": false, "started_at": "2026-06-02T20:46:18.926Z", @@ -166,7 +166,7 @@ "body": "CloudSigma would like to inform you that the issues affecting our PaaS infrastructure in Frankfurt have been resolved. \n\nThank you for your patience and understanding.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-27T16:44:16.353Z", "resolved_inferred": false, "started_at": "2026-05-27T16:28:41.789Z", @@ -179,7 +179,7 @@ "body": "CloudSigma would like to inform you that the network issue affecting our Riyadh cloud location has been resolved.\n\nOur team will continue to monitor the environment to ensure ongoing stability. We sincerely apologise for the inconvenience caused and thank you for your patience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-24T17:19:19.178Z", "resolved_inferred": false, "started_at": "2026-05-24T12:44:48.631Z", @@ -192,7 +192,7 @@ "body": "CloudSigma would like to inform you that experienced packet loss on the Riyhad cloud has subsided. \n\nThank you for your patience, & we apologise for any inconvenience caused. We will investigate further the cause of the network issues experienced.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-24T10:49:55.163Z", "resolved_inferred": false, "started_at": "2026-05-24T09:57:15.694Z", @@ -205,7 +205,7 @@ "body": "CloudSigma would like to inform you that the affected vhosts in the Monterrey cloud location are operational and stable.\n\nWe apologize for any inconvenience caused.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-17T21:01:29.525Z", "resolved_inferred": false, "started_at": "2026-05-17T17:28:58.618Z", @@ -218,7 +218,7 @@ "body": "CloudSigma would like to inform you that the issue affecting the login of our Riyadh cloud has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-29T12:10:36.454Z", "resolved_inferred": false, "started_at": "2026-04-29T06:14:26.963Z", @@ -231,7 +231,7 @@ "body": "CloudSigma would like to inform you that the API performance issues in the Riyadh cloud locations have now been resolved. During the incident, users may have experienced issues with WebApp going in and out of availability.\n\nIf you continue to experience any issues, please do not hesitate to report them to our support team. We apologize for any inconvenience caused.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-28T15:53:58.520Z", "resolved_inferred": false, "started_at": "2026-04-28T05:27:20.224Z", @@ -244,7 +244,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-27T11:55:49.865Z", "resolved_inferred": false, "started_at": "2026-04-27T09:35:51.000Z", @@ -257,7 +257,7 @@ "body": "CloudSigma would like to inform you that the API performance issues in the Zurich cloud locations have now been resolved. During the incident, users may have experienced issues with API operations, as well as virtual machines getting stuck in stopping or starting states, and instances appearing as unavailable.\n\nIf you continue to experience any issues, please do not hesitate to report them to our support team. We apologize for any inconvenience caused.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-27T09:52:07.950Z", "resolved_inferred": false, "started_at": "2026-04-27T09:27:36.674Z", @@ -270,7 +270,7 @@ "body": "CloudSigma would like to inform you that the API performance issues in the Zurich and Geneva cloud locations have now been resolved. During the incident, users may have experienced issues with API operations, as well as virtual machines getting stuck in stopping or starting states, and instances appearing as unavailable.\n\nIf you continue to experience any issues, please do not hesitate to report them to our support team. We apologize for any inconvenience caused.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-15T13:56:59.129Z", "resolved_inferred": false, "started_at": "2026-04-15T06:28:27.364Z", @@ -283,7 +283,7 @@ "body": "Cloudsigma would like to inform you that the network connectivity issues affecting the Manila location have been resolved. All services are operating normally.\n\nWe appreciate your patience during this incident.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-13T19:14:04.605Z", "resolved_inferred": false, "started_at": "2026-04-13T16:04:18.066Z", @@ -296,7 +296,7 @@ "body": "This notification was sent by mistake to all of our customers. Please accept our apologies for the inconvenience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-09T23:34:37.150Z", "resolved_inferred": false, "started_at": "2026-04-09T23:32:30.848Z", @@ -309,7 +309,7 @@ "body": "CloudSigma would like to inform you that the issue affecting the CAI location has been fully resolved and network connectivity has been restored.\n\nWe apologize for any inconvenience and appreciate your patience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-10T00:57:37.441Z", "resolved_inferred": false, "started_at": "2026-04-09T23:32:29.340Z", @@ -322,7 +322,7 @@ "body": "CloudSigma would like to inform you that the issue affecting our CAI location has been fully resolved. \n\nWe apologize for any inconvenience and appreciate your patience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-02T00:26:44.110Z", "resolved_inferred": false, "started_at": "2026-04-01T23:27:29.139Z", @@ -335,7 +335,7 @@ "body": "CloudSigma would like to inform you that the issue affecting our CAI location has been fully resolved. \n\nWe apologize for any inconvenience and appreciate your patience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-01T21:17:10.216Z", "resolved_inferred": false, "started_at": "2026-04-01T17:17:43.081Z", @@ -348,7 +348,7 @@ "body": "CloudSigma would like to inform you that the issue with the reachability of our compute hosts in the Riyadh DC location has been fixed. \n\nPlease accept our apologies for the inconvenience caused!", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-20T17:49:52.072Z", "resolved_inferred": false, "started_at": "2026-03-20T13:02:17.667Z", @@ -361,7 +361,7 @@ "body": "CloudSigma would like to inform you that the issue affecting our Monterey location has been fully resolved. Network redundancy has been restored. \n\nWe apologize for any inconvenience and appreciate your patience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-17T11:27:21.264Z", "resolved_inferred": false, "started_at": "2026-03-16T23:34:39.771Z", @@ -374,7 +374,7 @@ "body": "CloudSigma would like to inform you that the issue affecting the PaaS User Panel in our Monterrey cloud has been resolved. The PaaS infrastructure is now operating normally and the panel should be accessible as expected.\n\nOur team monitored the situation after applying the fix and no further issues were observed. If you continue to experience any problems, please let us know.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-16T16:18:43.621Z", "resolved_inferred": false, "started_at": "2026-03-16T11:51:53.768Z", @@ -387,7 +387,7 @@ "body": "CloudSigma would like to inform you that all issues related to the API have been addressed, and the WebApp should now be functioning as expected. We have been monitoring the situation and the issue has not reappeared.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-13T21:06:59.415Z", "resolved_inferred": false, "started_at": "2026-03-07T12:41:07.171Z", @@ -400,7 +400,7 @@ "body": "CloudSigma would like to inform you that the WebApp has been successfully restored and is now operating as expected.\n\nWe would like to assure you that there was no impact on customer virtual machines, network connectivity, or other cloud infrastructure components during the incident.\n\nWe sincerely apologize for any inconvenience this may have caused and appreciate your understanding.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-19T17:08:16.267Z", "resolved_inferred": false, "started_at": "2026-02-19T16:45:29.785Z", @@ -413,7 +413,7 @@ "body": "We would like to inform you that the emergency maintenance to resolve the underlying issue causing the API degraded performance has been completed successfully. After performing the relevant tests in the platform, we can confirm that the degraded performance we reported has been resolved.\n\nThank you very much for your patience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-23T21:53:18.289Z", "resolved_inferred": false, "started_at": "2026-02-17T09:28:45.629Z", @@ -426,7 +426,7 @@ "body": "CloudSigmas would like to inform issue affecting the availability of our compute hosts on the Zurich cloud has been resolved.\n\nThank you for your patience and understanding.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-17T06:40:20.992Z", "resolved_inferred": false, "started_at": "2026-02-17T00:28:28.421Z", @@ -439,7 +439,7 @@ "body": "Cloudsigma would like to inform you that the network connectivity issues affecting the Izmir location have been resolved. All services are operating normally.\n\nWe appreciate your patience during this incident.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-30T17:11:23.834Z", "resolved_inferred": false, "started_at": "2026-01-30T15:17:20.273Z", @@ -452,7 +452,7 @@ "body": "The network connectivity issue affecting our Izmir Cloud location has been resolved.\n\nAll services, including WebApp access and virtual machines, are now operating normally. We will continue to monitor the situation closely.\n\nThank you for your patience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-30T13:05:36.370Z", "resolved_inferred": false, "started_at": "2026-01-30T09:37:53.764Z", @@ -465,7 +465,7 @@ "body": "CloudSigma would like to inform you that the Izmir cloud location is reachable again. \n\nThank you for your understanding on this matter.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-27T20:56:32.838Z", "resolved_inferred": false, "started_at": "2026-01-27T20:08:21.820Z", @@ -478,7 +478,7 @@ "body": "CloudSigma would like to inform you that the WebApp has been successfully restored and is now operating as expected.\n\nWe would like to assure you that there was no impact on customer virtual machines, network connectivity, or other cloud infrastructure components during the incident.\n\nWe sincerely apologize for any inconvenience this may have caused and appreciate your understanding.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-04T10:45:44.953Z", "resolved_inferred": false, "started_at": "2026-01-04T10:28:55.543Z", @@ -491,7 +491,7 @@ "body": "CloudSigma would like to inform you that the WebApp has been successfully restored and is now operating as expected.\n\nWe would like to assure you that there was no impact on customer virtual machines, network connectivity, or other cloud infrastructure components during the incident.\n\nWe sincerely apologize for any inconvenience this may have caused and appreciate your understanding.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-08T11:23:54.490Z", "resolved_inferred": false, "started_at": "2025-12-08T11:09:11.697Z", @@ -504,7 +504,7 @@ "body": "CloudSigma would like to inform you that the experienced degraded network performance in our Monterrey Cloud has been resolved. \n\nPlease accept our apologies for the inconvenience caused!", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-26T04:24:04.664Z", "resolved_inferred": false, "started_at": "2025-11-26T00:08:12.205Z", @@ -517,7 +517,7 @@ "body": "CloudSigma would like to inform you that the WebApp has been successfully restored and is now operating as expected.\n\nWe would like to assure you that there was no impact on customer virtual machines, network connectivity, or other cloud infrastructure components during the incident.\n\nWe sincerely apologize for any inconvenience this may have caused and appreciate your understanding.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-20T18:12:47.484Z", "resolved_inferred": false, "started_at": "2025-11-20T17:46:16.036Z", @@ -530,7 +530,7 @@ "body": "CloudSigma is happy to inform you that Cloudflare's network incident has been resolved and that our WebApp is available in all cloud locations.\n\nThere was no impact on any of the existing servers, drives, or networking. Only the WebPanels are affected by this incident.\n\nFor more information about the issue from Cloudflare's side, kindly review their status page at: https://www.cloudflarestatus.com/incidents/8gmgl950y3h7", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-18T18:12:19.031Z", "resolved_inferred": false, "started_at": "2025-11-18T12:06:54.656Z", @@ -543,7 +543,7 @@ "body": "Alpha3cloud would like to inform you that the experienced degraded network performance in our Washington Cloud has been resolved. \n\nPlease accept our apologies for the inconvenience caused!", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-31T07:18:50.797Z", "resolved_inferred": false, "started_at": "2025-10-31T06:31:19.124Z", @@ -556,7 +556,7 @@ "body": "CloudSigma would like to inform you that the networking issue in our Manila cloud location has been rectified, and all network services are now in proper operation.\n\nOnce again we apologize for any inconvenience caused.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-27T11:01:49.780Z", "resolved_inferred": false, "started_at": "2025-10-27T09:24:17.793Z", @@ -569,7 +569,7 @@ "body": "CloudSigma would like to inform you that the issue in our Cairo Cloud is now resolved. You can once again access the WebApp. There was no impact on already existing servers or services during the interruption.\n\nThank you for your understanding.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-19T13:22:10.981Z", "resolved_inferred": false, "started_at": "2025-10-19T11:59:02.239Z", @@ -582,7 +582,7 @@ "body": "CloudSigma would like to inform you that the web application in the Monterrey cloud location is now accessible. There was no interruption of the already running machines.\n\nPlease accept our sincere apologies for any inconvenience caused.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-16T02:41:44.800Z", "resolved_inferred": false, "started_at": "2025-10-16T00:11:19.429Z", @@ -595,7 +595,7 @@ "body": "CloudSigma is happy to inform you that the availability issue that we have experienced is now resolved.\n\nNo customer data was affected during the incident and normal operations are restored.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-06T03:00:57.837Z", "resolved_inferred": false, "started_at": "2025-10-06T01:53:51.595Z", @@ -608,7 +608,7 @@ "body": "CloudSigma is happy to inform you that the availability issue that we have experienced is now resolved.\n\nNo customer data was affected during the incident and normal operations are restored.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-30T01:42:31.664Z", "resolved_inferred": false, "started_at": "2025-09-30T00:46:47.817Z", @@ -621,7 +621,7 @@ "body": "CloudSigma would like to inform you that the issue regarding the availability of the drives has been rectified.\n\nServices are now operating as expected. Thank you for your patience and understanding. CloudSigma is actively working to reduce such occurrences.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-17T21:16:21.601Z", "resolved_inferred": false, "started_at": "2025-09-17T20:09:12.416Z", @@ -634,7 +634,7 @@ "body": "CloudSigma would like to inform you that the ongoing issue with saving new payment information is being worked on by our Development team. \n\nWe apologize for the inconvenience caused. We will connect with you on a later date to inform you of the implementation of the fix.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-29T10:09:45.460Z", "resolved_inferred": false, "started_at": "2025-09-16T07:08:38.783Z", @@ -647,7 +647,7 @@ "body": "CloudSigma would like to inform you that the WebApp is reachable, and everything is working as expected. \n\nPlease accept our sincere apologies for any inconvenience caused.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-13T06:50:37.047Z", "resolved_inferred": false, "started_at": "2025-09-13T05:22:19.864Z", @@ -660,7 +660,7 @@ "body": "CloudSigma would like to inform you that the accessibility of the drives in the Geneva region is fully restored.", "first_seen": "2026-09-04T08:14:10Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-12T13:01:19.818Z", "resolved_inferred": false, "started_at": "2025-09-12T09:57:34.449Z", diff --git a/api/v/cloudways.json b/api/v/cloudways.json index 1f707e89f11d7e7b2f0e2f0e0a16e62d4dc52c8e..561cbf1d8334e2e886bb9e624332e5dbc4686f7b 100644 --- a/api/v/cloudways.json +++ b/api/v/cloudways.json @@ -3,7 +3,7 @@ "slug": "cloudways", "platform": "statuspage", "status_url": "http://status.cloudways.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-09-02T01:20:20.556Z", "resolved_inferred": false, "started_at": "2026-09-01T07:42:21.958Z", @@ -25,7 +25,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-09-03T09:15:55.551Z", "resolved_inferred": false, "started_at": "2026-08-30T10:52:04.372Z", @@ -38,7 +38,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-25T08:30:15.313Z", "resolved_inferred": false, "started_at": "2026-08-24T18:36:59.000Z", @@ -51,7 +51,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-20T12:25:36.721Z", "resolved_inferred": false, "started_at": "2026-08-20T10:24:37.786Z", @@ -64,7 +64,7 @@ "body": "The issue has been fully resolved and all services are now back to normal operation. We apologize for any inconvenience caused and thank you for your patience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-11T23:46:05.000Z", "resolved_inferred": false, "started_at": "2026-08-11T18:18:59.000Z", @@ -77,7 +77,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-09T07:11:49.058Z", "resolved_inferred": false, "started_at": "2026-08-08T21:33:57.000Z", @@ -90,7 +90,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-08T14:54:19.484Z", "resolved_inferred": false, "started_at": "2026-08-08T07:18:31.000Z", @@ -103,7 +103,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-04T06:56:43.123Z", "resolved_inferred": false, "started_at": "2026-08-03T14:41:34.063Z", @@ -116,7 +116,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-03T22:29:42.698Z", "resolved_inferred": false, "started_at": "2026-08-03T14:23:59.774Z", @@ -129,7 +129,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-24T06:36:28.178Z", "resolved_inferred": false, "started_at": "2026-07-23T17:34:09.963Z", @@ -142,7 +142,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-19T10:21:00.140Z", "resolved_inferred": false, "started_at": "2026-07-19T08:24:53.833Z", @@ -155,7 +155,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-17T13:33:19.660Z", "resolved_inferred": false, "started_at": "2026-07-16T20:57:10.310Z", @@ -168,7 +168,7 @@ "body": "The issue has been resolved. Please contact our support if you continue to experience any related issues.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-15T08:18:14.627Z", "resolved_inferred": false, "started_at": "2026-07-14T10:08:51.413Z", @@ -181,7 +181,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-13T15:49:28.536Z", "resolved_inferred": false, "started_at": "2026-07-13T12:26:12.763Z", @@ -194,7 +194,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-01T14:52:37.594Z", "resolved_inferred": false, "started_at": "2026-07-01T09:38:15.759Z", @@ -207,7 +207,7 @@ "body": "The issue has been resolved. Please contact our support if you continue to experience any related issues.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-01T09:35:40.358Z", "resolved_inferred": false, "started_at": "2026-06-30T12:36:45.840Z", @@ -220,7 +220,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-23T02:41:14.077Z", "resolved_inferred": false, "started_at": "2026-06-22T09:56:48.675Z", @@ -233,7 +233,7 @@ "body": "Our upstream provider, Vultr, has resolved the network connectivity issue affecting their Chicago location.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-06T05:04:08.224Z", "resolved_inferred": false, "started_at": "2026-06-06T00:37:47.411Z", @@ -246,7 +246,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-03T06:50:22.475Z", "resolved_inferred": false, "started_at": "2026-06-01T15:21:48.648Z", @@ -259,7 +259,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-28T12:26:36.767Z", "resolved_inferred": false, "started_at": "2026-05-25T13:04:30.385Z", @@ -272,7 +272,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-20T12:40:03.700Z", "resolved_inferred": false, "started_at": "2026-05-20T01:31:14.749Z", @@ -285,7 +285,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-19T17:58:55.151Z", "resolved_inferred": false, "started_at": "2026-05-19T14:21:28.615Z", @@ -298,7 +298,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-27T12:10:24.217Z", "resolved_inferred": false, "started_at": "2026-05-16T09:47:28.840Z", @@ -311,7 +311,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-09T01:15:12.364Z", "resolved_inferred": false, "started_at": "2026-05-08T20:08:02.522Z", @@ -324,7 +324,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-08T11:54:39.413Z", "resolved_inferred": false, "started_at": "2026-05-08T05:45:21.374Z", @@ -337,7 +337,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-30T08:32:28.852Z", "resolved_inferred": false, "started_at": "2026-04-29T21:58:55.445Z", @@ -350,7 +350,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-29T23:27:26.455Z", "resolved_inferred": false, "started_at": "2026-04-29T19:37:20.000Z", @@ -363,7 +363,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-21T02:15:06.552Z", "resolved_inferred": false, "started_at": "2026-04-20T12:33:05.734Z", @@ -376,7 +376,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-14T15:00:40.263Z", "resolved_inferred": false, "started_at": "2026-04-14T12:33:16.046Z", @@ -389,7 +389,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-04T08:01:34.083Z", "resolved_inferred": false, "started_at": "2026-04-04T06:00:22.585Z", @@ -402,7 +402,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-06T18:35:29.235Z", "resolved_inferred": false, "started_at": "2026-04-02T13:58:45.186Z", @@ -415,7 +415,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-25T15:30:46.483Z", "resolved_inferred": false, "started_at": "2026-03-20T11:42:30.218Z", @@ -428,7 +428,7 @@ "body": "The issue has been resolved. Please contact our support if you continue to experience any related issues.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-17T09:20:13.345Z", "resolved_inferred": false, "started_at": "2026-03-16T21:06:16.026Z", @@ -441,7 +441,7 @@ "body": "Following the ongoing AWS outage in the ME-SOUTH-1 (Bahrain) region, we have disabled server provisioning in this region. If you currently have active workloads in ME-SOUTH-1, please migrate them to an alternative region of your choice. Our support team is available if you need guidance or assistance during the migration process.\nWe apologize for the inconvenience and appreciate your cooperation as we take steps to ensure your service reliability.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-28T19:25:43.018Z", "resolved_inferred": false, "started_at": "2026-03-02T08:05:15.087Z", @@ -454,7 +454,7 @@ "body": "Following the ongoing AWS outage in the ME-Central-1 (UAE) region, we have disabled server provisioning in this region. If you currently have active workloads in ME-Central-1, please migrate them to an alternative region of your choice. Our support team is available if you need guidance or assistance during the migration process.\nWe apologize for the inconvenience and appreciate your cooperation as we take steps to ensure your service reliability.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-28T19:26:40.195Z", "resolved_inferred": false, "started_at": "2026-03-01T13:53:41.918Z", @@ -467,7 +467,7 @@ "body": "The issue has been resolved. Please contact our support if you continue to experience any related issues.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-13T07:16:10.513Z", "resolved_inferred": false, "started_at": "2026-02-12T14:43:07.946Z", @@ -480,7 +480,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-28T15:34:57.945Z", "resolved_inferred": false, "started_at": "2026-01-28T13:04:59.092Z", @@ -493,7 +493,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-21T08:20:27.502Z", "resolved_inferred": false, "started_at": "2026-01-19T10:07:00.881Z", @@ -506,7 +506,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-19T10:01:45.799Z", "resolved_inferred": false, "started_at": "2026-01-19T09:12:43.668Z", @@ -519,7 +519,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-09T20:54:04.268Z", "resolved_inferred": false, "started_at": "2026-01-09T19:48:21.748Z", @@ -532,7 +532,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-05T15:50:23.836Z", "resolved_inferred": false, "started_at": "2026-01-05T14:24:20.889Z", @@ -545,7 +545,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-30T15:09:32.042Z", "resolved_inferred": false, "started_at": "2025-12-30T12:01:21.367Z", @@ -558,7 +558,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-30T06:20:25.123Z", "resolved_inferred": false, "started_at": "2025-12-29T17:34:17.599Z", @@ -571,7 +571,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-21T19:03:29.749Z", "resolved_inferred": false, "started_at": "2025-12-19T12:14:49.543Z", @@ -584,7 +584,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-05T17:18:32.819Z", "resolved_inferred": false, "started_at": "2025-12-05T09:05:21.075Z", @@ -597,7 +597,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-02T12:26:13.938Z", "resolved_inferred": false, "started_at": "2025-12-01T14:10:29.409Z", @@ -610,7 +610,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-27T18:23:28.981Z", "resolved_inferred": false, "started_at": "2025-11-27T14:47:31.681Z", @@ -623,7 +623,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-05T02:40:09.244Z", "resolved_inferred": false, "started_at": "2025-11-24T13:44:16.130Z", @@ -636,7 +636,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-28T02:42:06.832Z", "resolved_inferred": false, "started_at": "2025-11-23T20:42:32.853Z", @@ -649,7 +649,7 @@ "body": "We have received confirmation from Cloudflare that their services have returned to normal and no further errors or latency are being observed across their network. As a result, the issue affecting access to the Cloudways platform has been resolved.\nWe sincerely appreciate your patience and understanding during this disruption.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-18T17:57:16.000Z", "resolved_inferred": false, "started_at": "2025-11-18T12:03:28.000Z", diff --git a/api/v/cockroach-labs.json b/api/v/cockroach-labs.json index 05c6d6ebedec9097c5c2e87af99de20004209fa7..f8e3a1d78f8c5e3a7eb6460fda0cb3a1440f1e6a 100644 --- a/api/v/cockroach-labs.json +++ b/api/v/cockroach-labs.json @@ -3,7 +3,7 @@ "slug": "cockroach-labs", "platform": "statuspage", "status_url": "https://status.cockroachlabs.cloud", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "Google impacts are now reported as fully resolved. Internal teams have confirmed this report. All services are restored.\n\nShould you need further help, please reach out and file a ticket with Support.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-09-01T19:45:19.278Z", "resolved_inferred": false, "started_at": "2026-09-01T15:36:20.466Z", @@ -25,7 +25,7 @@ "body": "Following an extended period of monitoring, the team has confirmed that the cluster remains healthy and stable.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-05T19:50:18.560Z", "resolved_inferred": false, "started_at": "2026-08-04T23:46:23.132Z", @@ -38,7 +38,7 @@ "body": "The cluster creation issue has been restored. Issue is resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-12T21:24:59.100Z", "resolved_inferred": false, "started_at": "2026-07-12T20:08:27.748Z", @@ -51,7 +51,7 @@ "body": "Fix deployment is complete, tested and verified.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-09T22:02:54.461Z", "resolved_inferred": false, "started_at": "2026-06-09T21:26:27.146Z", @@ -64,7 +64,7 @@ "body": "All CockroachDB clusters in the affected AWS availability zone have been restored to a fully operational state. We will continue to monitor the upstream incident from AWS, but do not expect any impact to CockroachDB clusters.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-08T21:53:58.430Z", "resolved_inferred": false, "started_at": "2026-05-08T02:13:34.809Z", @@ -77,7 +77,7 @@ "body": "Social login for Microsoft accounts is now available. Please reach out to support if you continue to experience issues.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-18T16:02:54.560Z", "resolved_inferred": false, "started_at": "2026-03-18T15:23:37.257Z", @@ -90,7 +90,7 @@ "body": "Beginning March 1, 2026, a power outage caused by physical damage to AWS infrastructure affected multiple Availability Zones in the AWS me-central-1 (UAE) region, resulting in the unavailability of CockroachDB Cloud clusters in that region. A single Availability Zone in me-south-1 was also impacted, \ncausing degraded performance for clusters in that region.\n\nWhile AWS has not yet fully restored power to all affected Availability Zones, Cockroach Labs has directly engaged all customers impacted by this incident, providing resolution guidance and hands-on remediation assistance, including cross-region data restoration where applicable.\n\nAs remediation steps have been completed or provided to all directly impacted customers, we are resolving this incident from Cockroach Labs' perspective. Cluster creation in the affected regions remains restricted pending full AWS recovery.\n\nCustomers with outstanding questions or concerns are encouraged to contact Cockroach Labs Support.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-11T19:51:23.812Z", "resolved_inferred": false, "started_at": "2026-03-01T15:11:57.131Z", @@ -103,7 +103,7 @@ "body": "Standard and Basic clusters continue to function normally.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-09T15:20:12.479Z", "resolved_inferred": false, "started_at": "2026-02-09T03:04:06.062Z", @@ -116,7 +116,7 @@ "body": "We have deployed and verified a fix. Advanced clusters should now create within normal time frames.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-02T19:46:51.561Z", "resolved_inferred": false, "started_at": "2026-02-02T16:56:59.707Z", @@ -129,7 +129,7 @@ "body": "All cluster operations are working normally.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-31T22:09:50.952Z", "resolved_inferred": false, "started_at": "2025-10-31T15:54:20.959Z", @@ -142,7 +142,7 @@ "body": "Cluster creation is operating normally, and all delayed clusters have finished creation.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-30T16:05:53.176Z", "resolved_inferred": false, "started_at": "2025-10-30T14:50:14.525Z", @@ -155,7 +155,7 @@ "body": "The earlier AWS outage in the us-east-1 region has been fully resolved. All CockroachDB Cloud operations, including cluster creation, scaling, and backups, are functioning normally again.\nWe\u2019ve verified recovery across affected systems and customer clusters, and normal operations have resumed.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-21T14:56:21.238Z", "resolved_inferred": false, "started_at": "2025-10-20T13:28:46.852Z", @@ -168,7 +168,7 @@ "body": "Google has reported the issue has been resolved and we've verified cluster operations are functional.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-24T16:00:39.299Z", "resolved_inferred": false, "started_at": "2025-09-24T12:31:56.303Z", diff --git a/api/v/cocoapods.json b/api/v/cocoapods.json index 901bb86bbd3d714e16053d71549f4a65419a7ac1..90e7afd60546bd2cbfb384242f0c96e837c798fb 100644 --- a/api/v/cocoapods.json +++ b/api/v/cocoapods.json @@ -3,7 +3,7 @@ "slug": "cocoapods", "platform": "statuspage", "status_url": "https://status.cocoapods.org", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", diff --git a/api/v/code-42.json b/api/v/code-42.json index 21b7c397ca683f920849173fda756a4e2b66b923..0c4a43714282a4f7ceecbe5e6f0e9589114aef65 100644 --- a/api/v/code-42.json +++ b/api/v/code-42.json @@ -3,7 +3,7 @@ "slug": "code-42", "platform": "statuspage", "status_url": "https://status.code42.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-25T12:34:10.052-05:00", "resolved_inferred": false, "started_at": "2026-08-25T08:26:53.916-05:00", @@ -25,7 +25,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-11T22:07:52.245-05:00", "resolved_inferred": false, "started_at": "2026-08-11T07:46:38.685-05:00", @@ -38,7 +38,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-30T08:10:05.764-05:00", "resolved_inferred": false, "started_at": "2026-07-29T21:40:46.062-05:00", @@ -51,7 +51,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-30T10:51:47.559-05:00", "resolved_inferred": false, "started_at": "2026-07-28T11:22:32.497-05:00", @@ -64,7 +64,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-20T19:28:38.852-05:00", "resolved_inferred": false, "started_at": "2026-07-20T16:08:22.502-05:00", @@ -77,7 +77,7 @@ "body": "## Incydr Gov Only\n\nOn July 8 2026 21:00UTC, the service cluster responsible for managing exfiltrated files in our Incydr Gov environment experienced an outage. During the outage, users were unable to download previously captured exfiltrated files from the Incydr console, and the Incydr agent was unable to upload newly captured files to the service. Alerts that rely on file content based risk indicators for exfiltrated file activity would not have been generated during this period.\n\nMimecast Engineering identified and resolved the underlying issue on July 13, 2026, and confirmed the service was fully restored as of 15:00UTC\n\nWe are reviewing Incydr agent behavior during extended service interruptions to ensure captured files are reliably retained and delivered once service is restored, and we are adding additional monitoring to detect this class of issue more quickly going forward.\n\nPlease reach out to your Mimecast representative with any questions.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-13T15:00:00.000-05:00", "resolved_inferred": false, "started_at": "2026-07-13T15:00:00.000-05:00", @@ -90,7 +90,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-06T14:24:07.612-05:00", "resolved_inferred": false, "started_at": "2026-07-06T09:06:46.224-05:00", @@ -103,7 +103,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-25T06:46:01.753-05:00", "resolved_inferred": false, "started_at": "2026-06-24T14:34:39.371-05:00", @@ -116,7 +116,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-24T14:34:05.407-05:00", "resolved_inferred": false, "started_at": "2026-06-24T09:20:23.084-05:00", @@ -129,7 +129,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-23T06:18:59.006-05:00", "resolved_inferred": false, "started_at": "2026-06-22T17:46:50.781-05:00", @@ -142,7 +142,7 @@ "body": "There was a delay in processing of events for the IE, ZA, and DE regions. This was resolved on 6/20/2026.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-22T10:57:41.785-05:00", "resolved_inferred": false, "started_at": "2026-06-22T10:57:41.749-05:00", @@ -155,7 +155,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-13T09:36:23.647-05:00", "resolved_inferred": false, "started_at": "2026-06-13T07:39:38.588-05:00", @@ -168,7 +168,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-11T18:13:21.581-05:00", "resolved_inferred": false, "started_at": "2026-06-11T08:19:04.669-05:00", @@ -181,7 +181,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-01T08:39:10.274-05:00", "resolved_inferred": false, "started_at": "2026-05-29T07:59:21.986-05:00", @@ -194,7 +194,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-27T06:45:10.462-05:00", "resolved_inferred": false, "started_at": "2026-05-26T20:32:50.395-05:00", @@ -207,7 +207,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-21T21:42:03.541-05:00", "resolved_inferred": false, "started_at": "2026-05-21T17:12:18.238-05:00", @@ -220,7 +220,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-14T13:02:42.200-05:00", "resolved_inferred": false, "started_at": "2026-05-11T17:05:57.391-05:00", @@ -233,7 +233,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-02T09:00:17.975-05:00", "resolved_inferred": false, "started_at": "2026-04-29T20:49:05.288-05:00", @@ -246,7 +246,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-30T07:10:51.555-05:00", "resolved_inferred": false, "started_at": "2026-04-29T15:42:00.569-05:00", @@ -259,7 +259,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-28T18:25:11.115-05:00", "resolved_inferred": false, "started_at": "2026-04-28T17:24:43.340-05:00", @@ -272,7 +272,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-23T16:27:04.530-05:00", "resolved_inferred": false, "started_at": "2026-04-23T12:31:12.128-05:00", @@ -285,7 +285,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-31T05:09:04.182-05:00", "resolved_inferred": false, "started_at": "2026-03-30T08:29:40.406-05:00", @@ -298,7 +298,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-25T17:10:19.565-05:00", "resolved_inferred": false, "started_at": "2026-03-25T08:31:41.651-05:00", @@ -311,7 +311,7 @@ "body": "At 21:35 UTC on March 23, 2026, an engineering change was released to all Incydr production environments. This change caused a temporary outage of Incydr services. During the service outage, users were able to authenticate to the Incydr console, but all features and functionality were unavailable. \u00a0\n\nIncydr agents that had already established communication with the Incydr cloud prior to the outage were not affected. A subset of agents that established a connection during the outage may have experienced a monitoring gap of up to six hours.\u00a0\n\nMimecast Engineering teams identified the issue and worked to restore services. All Incydr services were verified to be functioning normally as of 01:30 UTC on March 24, 2026.\u00a0\n\nPlease reach out to your Mimecast representative with any questions.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-24T07:40:25.183-05:00", "resolved_inferred": false, "started_at": "2026-03-23T16:56:45.535-05:00", @@ -324,7 +324,7 @@ "body": "This incident has been resolved all services are back and running.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-19T22:10:06.964-05:00", "resolved_inferred": false, "started_at": "2026-03-19T21:50:49.753-05:00", @@ -337,7 +337,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-11T05:26:24.085-05:00", "resolved_inferred": false, "started_at": "2026-03-10T18:27:54.358-05:00", @@ -350,7 +350,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-05T14:38:00.488-06:00", "resolved_inferred": false, "started_at": "2026-03-05T07:21:59.320-06:00", @@ -363,7 +363,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-19T11:53:32.141-06:00", "resolved_inferred": false, "started_at": "2026-02-18T14:37:08.997-06:00", @@ -376,7 +376,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-04T20:38:03.645-06:00", "resolved_inferred": false, "started_at": "2026-02-04T15:16:07.252-06:00", @@ -389,7 +389,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-03T22:15:13.619-06:00", "resolved_inferred": false, "started_at": "2026-02-03T20:07:48.124-06:00", @@ -402,7 +402,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-04T06:47:10.025-06:00", "resolved_inferred": false, "started_at": "2026-02-03T20:00:15.791-06:00", @@ -415,7 +415,7 @@ "body": "There was a delay in processing Alerts. This has now been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-12T16:20:29.639-06:00", "resolved_inferred": false, "started_at": "2026-01-12T16:20:29.583-06:00", @@ -428,7 +428,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-24T17:58:40.370-06:00", "resolved_inferred": false, "started_at": "2025-11-14T08:34:03.347-06:00", @@ -441,7 +441,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-09T06:03:06.068-06:00", "resolved_inferred": false, "started_at": "2025-11-07T11:36:06.024-06:00", @@ -454,7 +454,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-29T06:59:05.314-05:00", "resolved_inferred": false, "started_at": "2025-10-29T00:14:32.664-05:00", @@ -467,7 +467,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-28T20:57:51.502-05:00", "resolved_inferred": false, "started_at": "2025-10-28T13:27:13.824-05:00", @@ -480,7 +480,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-27T14:14:37.139-05:00", "resolved_inferred": false, "started_at": "2025-10-27T11:17:39.120-05:00", @@ -493,7 +493,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-27T15:51:43.518-05:00", "resolved_inferred": false, "started_at": "2025-10-27T11:01:58.859-05:00", @@ -506,7 +506,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-24T21:51:14.298-05:00", "resolved_inferred": false, "started_at": "2025-10-24T15:19:57.028-05:00", @@ -519,7 +519,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-24T14:58:55.993-05:00", "resolved_inferred": false, "started_at": "2025-10-24T11:07:01.893-05:00", @@ -532,7 +532,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-21T17:33:15.042-05:00", "resolved_inferred": false, "started_at": "2025-10-21T11:26:22.393-05:00", @@ -545,7 +545,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-21T06:40:05.514-05:00", "resolved_inferred": false, "started_at": "2025-10-20T07:59:42.978-05:00", @@ -558,7 +558,7 @@ "body": "We observed a delay in processing watchlist memberships.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-25T11:30:00.000-05:00", "resolved_inferred": false, "started_at": "2025-09-25T11:30:00.000-05:00", @@ -571,7 +571,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-25T09:25:44.374-05:00", "resolved_inferred": false, "started_at": "2025-09-24T12:50:53.224-05:00", @@ -584,7 +584,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-19T13:08:48.244-05:00", "resolved_inferred": false, "started_at": "2025-09-19T11:11:13.534-05:00", @@ -597,7 +597,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-09T19:58:37.079-05:00", "resolved_inferred": false, "started_at": "2025-09-09T16:01:46.906-05:00", @@ -610,7 +610,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-03T06:55:53.726-05:00", "resolved_inferred": false, "started_at": "2025-09-02T20:08:33.171-05:00", @@ -623,7 +623,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-01T17:29:38.507-05:00", "resolved_inferred": false, "started_at": "2025-09-01T16:05:53.625-05:00", @@ -636,7 +636,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-27T16:35:49.140-05:00", "resolved_inferred": false, "started_at": "2025-08-27T10:53:10.541-05:00", @@ -649,7 +649,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-27T07:29:03.554-05:00", "resolved_inferred": false, "started_at": "2025-08-26T15:46:40.949-05:00", diff --git a/api/v/codefresh.json b/api/v/codefresh.json index 9909fb88bdb59b39c5dd4f55bfdbd1a542f4c28c..3bb2cdc5ffbe50eba734ed6173c1137aaf8e4ba4 100644 --- a/api/v/codefresh.json +++ b/api/v/codefresh.json @@ -3,7 +3,7 @@ "slug": "codefresh", "platform": "statuspage", "status_url": "http://status.codefresh.io", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-24T18:21:18.537Z", "resolved_inferred": false, "started_at": "2026-08-24T15:31:01.383Z", @@ -25,7 +25,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-06T16:33:57.301Z", "resolved_inferred": false, "started_at": "2026-07-06T13:22:39.242Z", @@ -38,7 +38,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-06T16:32:59.652Z", "resolved_inferred": false, "started_at": "2026-07-06T12:32:44.939Z", @@ -51,7 +51,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-05T08:49:32.704Z", "resolved_inferred": false, "started_at": "2026-06-05T08:16:10.451Z", @@ -64,7 +64,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-12T20:19:52.225Z", "resolved_inferred": false, "started_at": "2026-05-12T17:34:00.336Z", @@ -77,7 +77,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-07T17:55:55.902Z", "resolved_inferred": false, "started_at": "2026-04-21T14:48:00.719Z", @@ -90,7 +90,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-03T19:02:43.000Z", "resolved_inferred": false, "started_at": "2026-04-03T16:19:57.257Z", @@ -103,7 +103,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-31T07:20:01.017Z", "resolved_inferred": false, "started_at": "2026-03-30T21:13:05.000Z", @@ -116,7 +116,7 @@ "body": "This incident has now been resolved. We will conduct further investigations into the load experienced by our backend for specific operations from a small number of customers, and provide details of our findings.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-16T01:44:27.559Z", "resolved_inferred": false, "started_at": "2026-02-16T00:29:02.453Z", @@ -129,7 +129,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-29T14:05:36.865Z", "resolved_inferred": false, "started_at": "2025-12-29T10:25:22.537Z", @@ -142,7 +142,7 @@ "body": "Github Git Operations is operating normally as of Nov 18, 2025 - 21:56 UTC", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-18T21:58:12.000Z", "resolved_inferred": false, "started_at": "2025-11-18T21:17:31.948Z", @@ -155,7 +155,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-19T00:42:47.240Z", "resolved_inferred": false, "started_at": "2025-11-18T12:07:33.496Z", @@ -168,7 +168,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-05T21:00:09.000Z", "resolved_inferred": false, "started_at": "2025-11-05T20:00:24.196Z", @@ -181,7 +181,7 @@ "body": "This incident has been resolved", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-26T11:15:04.840Z", "resolved_inferred": false, "started_at": "2025-10-26T10:38:12.052Z", @@ -194,7 +194,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-20T19:49:48.422Z", "resolved_inferred": false, "started_at": "2025-10-20T10:12:58.000Z", @@ -207,7 +207,7 @@ "body": "The issue has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-13T18:20:59.444Z", "resolved_inferred": false, "started_at": "2025-10-13T14:10:30.000Z", diff --git a/api/v/codeship.json b/api/v/codeship.json index 014de427c4025425a0239c9465dcaf446453b195..914025cc9abff769b7e07190c240eb7b8c89da5e 100644 --- a/api/v/codeship.json +++ b/api/v/codeship.json @@ -3,7 +3,7 @@ "slug": "codeship", "platform": "statuspage", "status_url": "http://codeship.statuspage.io", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "unknown", "history_backfilled": false, "first_watched": "2026-09-04T07:06:16Z", diff --git a/api/v/codetwo.json b/api/v/codetwo.json index e47e43676cf929b6a237a10a437fa9b46c324d1b..ed79c9b1463505cf2a5d36a5a20b691008b727ce 100644 --- a/api/v/codetwo.json +++ b/api/v/codetwo.json @@ -3,7 +3,7 @@ "slug": "codetwo", "platform": "statuspage", "status_url": "https://status.codetwo.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "Microsoft reports in EX1331830 that their configuration changes have reached approximately 50% of the affected infrastructure and message queues are steadily improving. This is also confirmed by our telemetry. More information can be found in the Microsoft 365 Admin Center under EX1331830 (https://admin.cloud.microsoft/#/servicehealth/:/alerts/EX1331830), if accessible.\n\nCodeTwo is and has been operating normally throughout this incident. All emails were delivered with signatures attached.\n\nAs the issue is no longer affecting our mail flow and is not related to CodeTwo infrastructure, we are resolving it. Our teams will continue to monitor the situation 24/7/365.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-02T22:20:01.109Z", "resolved_inferred": false, "started_at": "2026-06-02T12:39:33.471Z", @@ -25,7 +25,7 @@ "body": "# Summary\n\nOn March 18, 2026, a small subset of CodeTwo customers experienced temporary issues with email delivery. The incident was caused by a Microsoft networking and DNS\u2011related issue within Microsoft 365 infrastructure and was not the result of a failure in the CodeTwo service.\n\n# Impact\n\n* Only a\u00a0limited number of customers\u00a0were affected.\n\n* The issue occurred intermittently.\n* The impact was limited to customers whose mail flow depended on Microsoft 365 services affected by the incident.\n\n# Root cause\n\nMicrosoft confirmed that the incident \\(ID\u00a0MO1255228\\) was caused by a temporary issue with their networking infrastructure, where part of the infrastructure intended to handle production traffic was only partially reinstated. This led to DNS and load\u2011balancing issues, affecting services such as Exchange Online.\n\nThe incident originated entirely within\u00a0Microsoft\u2019s infrastructure\u00a0and was outside of CodeTwo\u2019s control.\n\n# Resolution\n\nMicrosoft manually reinstated the full networking infrastructure and confirmed service health recovery. Following this action, telemetry indicated stable and healthy service operation.\n\n# Why CodeTwo was affected\n\nCodeTwo services integrate directly with Microsoft 365 and Azure and rely on Microsoft\u2011managed DNS and networking components. DNS failures at the Microsoft platform level affect all services integrated with Microsoft 365, including third\u2011party solutions.\n\nThere is no technically viable way for any Microsoft 365-integrated service to be fully immune to platform\u2011level DNS or networking failures on Microsoft\u2019s side.\n\n# Preventive measures\n\n* CodeTwo services are\u00a0monitored 24/7/365.\n\n* We operate\u00a0redundant and failover\u2011capable infrastructure.\n* In case of Microsoft\u2011side incidents, we take all actions\u00a0within our control\u00a0to minimize customer impact, including traffic rerouting where technically possible.\n\nMicrosoft stated that this type of incident has been\u00a0extremely rare\u00a0and committed to improving safeguards to prevent similar events in the future.\n\n# Current status\n\nMicrosoft has confirmed that the affected services were fully restored and operating normally. No further issues related to this incident have been observed.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-18T18:32:22.579Z", "resolved_inferred": false, "started_at": "2026-03-18T15:41:44.952Z", @@ -38,7 +38,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-07T10:44:03.237Z", "resolved_inferred": false, "started_at": "2026-02-07T08:56:21.991Z", @@ -51,7 +51,7 @@ "body": "The fix implemented by the MS Exchange Online team worked and our service is fully operational again.\nThe most recent update from Microsoft: \"We\u2019re continuing to see steady improvements in service availability for Exchange Online and Microsoft Teams and our broader recovery efforts remain actively underway. Engineers are further refining load balancing measures to accelerate recovery and are methodically addressing the remaining impacted services.\"", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-23T03:50:23.275Z", "resolved_inferred": false, "started_at": "2026-01-22T19:37:29.383Z", @@ -64,7 +64,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-12T13:03:01.523Z", "resolved_inferred": false, "started_at": "2026-01-12T12:17:56.421Z", @@ -77,7 +77,7 @@ "body": "Microsoft has published official information about this incident on the Service Health Dashboard (SHD) under ID: EX1183800. Please refer to the SHD for more details.\n\nSince this officially confirms that the issue was not related to CodeTwo, we are resolving this incident on our end. If you have any questions, please raise a service request with Microsoft. You are also welcome to contact our Support Team at: https://www.codetwo.com/company/contact.\n\nAll CodeTwo services have been operational during the incident. Thank you for your understanding and cooperation.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-07T22:20:34.193Z", "resolved_inferred": false, "started_at": "2025-11-06T09:26:06.194Z", @@ -90,7 +90,7 @@ "body": "The issue appears to be resolved now. A bunch of guys were about to turn blue (when we realized Microsoft has messed up the DNS configuration) - we're breathing again. Thank you for your patience and understanding!\n \nThis was a widespread incident affecting multiple Microsoft resources worldwide. Some of the performance issues we experienced as a result were unavoidable. Nevertheless, we\u2019ll continue to enhance our high availability capabilities to make our are services more resilient to similar problems in the future. Please stay tuned, and thank you for your continued trust and business.\n \nIf you have any questions or need assistance, please reach out to our Customer Success Team - we\u2019re online 24 hours a day. And yes, our SOC Team also works around the clock, continuously monitoring our services both reactively and proactively. These teams, along with our Product Team, will remain on \u201cDEFCON 1\u201d until we\u2019re certain the issue has been fully mitigated.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-30T00:07:22.236Z", "resolved_inferred": false, "started_at": "2025-10-29T16:14:43.799Z", @@ -103,7 +103,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-09T17:37:36.503Z", "resolved_inferred": false, "started_at": "2025-10-09T10:29:20.588Z", @@ -116,7 +116,7 @@ "body": "It looks like the incident affected only a handful of tenants in Australia East, and the overall impact was very limited and not related to CodeTwo. We\u2019re not seeing any issues with our services, so we\u2019re closing this incident. Our 24/7/365 Proactive Monitoring Team will continue to actively monitor the service. If you are experiencing any problems, please feel free to reach out to our Support Team - we\u2019re available around the clock.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-16T02:17:37.796Z", "resolved_inferred": false, "started_at": "2025-09-15T23:08:10.073Z", @@ -129,7 +129,7 @@ "body": "The problem has been resolved by Microsoft. For further information, please check Service health in the Microsoft 365 Admin Center (Incident ID: EX1144276).\n\nCodeTwo is operating and has been operating normally. All emails were delivered with signatures attached.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-29T14:54:38.324Z", "resolved_inferred": false, "started_at": "2025-08-29T13:01:45.195Z", @@ -142,7 +142,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-25T06:01:09.136Z", "resolved_inferred": false, "started_at": "2025-08-25T05:32:25.391Z", diff --git a/api/v/codewars.json b/api/v/codewars.json index 8bf0dd73ceb68189f3622c53c55ada1842164407..d418e2c747458acc0956f81207a0d8c8c6762bb1 100644 --- a/api/v/codewars.json +++ b/api/v/codewars.json @@ -3,7 +3,7 @@ "slug": "codewars", "platform": "statuspage", "status_url": "http://status.codewars.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "unknown", "history_backfilled": false, "first_watched": "2026-09-04T07:06:16Z", diff --git a/api/v/cohere.json b/api/v/cohere.json index 57ae872cb3906d900f7590af5d1dca3d687ba80d..4bdfd5020f173e2db0bf6292754e8cf5175db0a7 100644 --- a/api/v/cohere.json +++ b/api/v/cohere.json @@ -3,7 +3,7 @@ "slug": "cohere", "platform": "statuspage", "status_url": "https://status.cohere.ai", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "\ud83c\udf89 The issue has been resolved and we are back to normal.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-09-01T20:03:17Z", "resolved_inferred": false, "started_at": "2026-09-01T15:41:03Z", @@ -24,7 +24,7 @@ "body": "\ud83c\udf89 The issue has been resolved and we are back to normal.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-05T20:33:38Z", "resolved_inferred": false, "started_at": "2026-08-05T19:36:11Z", @@ -36,7 +36,7 @@ "body": "\ud83c\udf89 The issue affecting Dashboard login has been resolved. All Cohere services are operating normally. Thank you for your patience while we worked through this.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-23T23:46:56Z", "resolved_inferred": false, "started_at": "2026-07-23T22:56:25Z", @@ -48,7 +48,7 @@ "body": "\ud83c\udf89 The issue has been resolved and we are back to normal.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-01T16:46:21Z", "resolved_inferred": false, "started_at": "2026-06-01T13:51:54Z", @@ -60,7 +60,7 @@ "body": "Docs are back up!", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-20T22:28:56Z", "resolved_inferred": false, "started_at": "2026-04-20T22:16:13Z", @@ -72,7 +72,7 @@ "body": "\ud83c\udf89 The issue has been resolved and we are back to normal.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-13T21:00:44Z", "resolved_inferred": false, "started_at": "2026-04-13T19:36:12Z", @@ -84,7 +84,7 @@ "body": "\ud83c\udf89 The issue has been resolved and we are back to normal.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-11T15:39:51Z", "resolved_inferred": false, "started_at": "2026-04-11T15:31:05Z", @@ -96,7 +96,7 @@ "body": "The issue has been resolved and all models are back to normal operation", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-13T05:51:37Z", "resolved_inferred": false, "started_at": "2026-02-13T04:34:04Z", @@ -108,7 +108,7 @@ "body": "\ud83c\udf89 The issue has been resolved and we are back to normal.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-18T22:23:24Z", "resolved_inferred": false, "started_at": "2025-10-18T21:46:40Z", @@ -120,7 +120,7 @@ "body": "`logprobs` feature has been correctly marked as unavailable for the specified models.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-01T19:46:40Z", "resolved_inferred": false, "started_at": "2025-10-01T15:56:55Z", @@ -132,7 +132,7 @@ "body": "\ud83c\udf89 The issue has been resolved and we are back to normal.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-07T20:56:17Z", "resolved_inferred": false, "started_at": "2025-08-07T20:46:16Z", diff --git a/api/v/cohesity.json b/api/v/cohesity.json index 41a413f8320455c3ea6c3acd9460e325514f9da2..e3c362d5dc970d1517c29f4ca75f31d3635c399a 100644 --- a/api/v/cohesity.json +++ b/api/v/cohesity.json @@ -3,7 +3,7 @@ "slug": "cohesity", "platform": "statuspage", "status_url": "https://status.cohesity.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "We have been made aware of an issue on the Microsoft side of degradation of services which are impacting CCS workloads.\nOur understanding is that they have remediated the issue and things should be corrected.\nIf you continue to experience problems, please contact Cohesity Support.\n\nMore information can be found at: https://status.cloud.microsoft/m365/referrer=serviceStatusRedirect", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-09-01T17:34:08.779Z", "resolved_inferred": false, "started_at": "2026-09-01T17:34:08.711Z", @@ -25,7 +25,7 @@ "body": "We are currently investigating an intermittent issue impacting certain Microsoft 365 backup jobs (OneDrive and mailbox workloads). Some objects may temporarily be reported as Unprotected, and new backup jobs may be temporarily unable to run. Please be assured this is not attributable to any action on your part; our team has identified the root cause and is implementing a fix. We will provide further updates as they become available.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "started_at": "2026-08-24T20:47:17.738Z", "state": "identified", "title": "Intermittent issue impacting OneDrive and Mailbox workloads in CCS.", @@ -36,7 +36,7 @@ "body": "The Activity Page and Reports on the Helios platform should be fully functional with no lag now.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-25T15:39:28.632Z", "resolved_inferred": false, "started_at": "2026-08-24T17:16:45.381Z", @@ -49,7 +49,7 @@ "body": "We are reissuing this incident statement as Microsoft has recently made the change and we have seen many tenants that have not migrated. Below is the original incident language that was sent in February 2026.\n\nCohesity is issuing this advisory to inform our Cloud Protection Service (CPS) customers of an important change regarding authentication for Microsoft 365 workflows. Microsoft is retiring Azure Access Control Service (ACS), effective April 2, 2026. Currently, ACS is utilized for authentication in certain Microsoft 365 workflows, including backups for SharePoint, OneDrive, Teams, and Groups.\n\nAfter April 2, 2026, backups for these protection jobs will fail unless customers migrate to Certificate-Based Authentication (CBA). To ensure uninterrupted service and data protection, we strongly recommend that all customers review the provided Knowledge Base (KB) article and follow the migration instructions.\n\nThis impacts all regions and all CCS customers.\n\nRecommended Action:\n\nAll recipients of this Field Notice are advised to review the KB article from the additional Resources section for detailed information and recommended preventive actions.\n\nKB article: https://support.cohesity.com/s/article/Steps-to-enable-CBA-Migration-for-CPS\nMicrosoft change announcement: https://learn.microsoft.com/en-us/sharepoint/dev/sp-add-ins/retirement-announcement-for-azure-acs", "first_seen": "2026-09-04T07:06:16Z", "impact": "maintenance", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "started_at": "2026-07-16T19:32:34.666Z", "state": "investigating", "title": "Customer Action Needed - Migrate to Certificate Based Authentication (CBA)", @@ -60,7 +60,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-04T20:20:04.662Z", "resolved_inferred": false, "started_at": "2026-06-03T18:35:58.712Z", @@ -73,7 +73,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-14T09:26:50.956Z", "resolved_inferred": false, "started_at": "2026-05-13T15:22:23.457Z", @@ -86,7 +86,7 @@ "body": "AWS has resolved the issue. Everything seems to be back on line.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-09T15:31:29.090Z", "resolved_inferred": false, "started_at": "2026-05-08T18:04:56.391Z", @@ -99,7 +99,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-06T13:24:36.355Z", "resolved_inferred": false, "started_at": "2026-05-06T11:30:11.682Z", @@ -112,7 +112,7 @@ "body": "A fix has been rolled out for this issue, and our internal monitoring indicates that all login issues have been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-01T16:20:46.645Z", "resolved_inferred": false, "started_at": "2026-04-30T18:32:45.088Z", @@ -125,7 +125,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-05T15:52:24.621Z", "resolved_inferred": false, "started_at": "2026-03-05T12:29:06.955Z", @@ -138,7 +138,7 @@ "body": "This issue should be resolved. If you continue to experience issues with adding resources or source refresh, please work with our support team.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-18T16:24:40.598Z", "resolved_inferred": false, "started_at": "2026-03-04T03:20:58.473Z", @@ -151,7 +151,7 @@ "body": "We are continuing to investigate this issue.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "started_at": "2026-03-02T10:26:51.694Z", "state": "investigating", "title": "CCS impacted in AWS UAE region", @@ -162,7 +162,7 @@ "body": "This issue has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-06T23:20:21.709Z", "resolved_inferred": false, "started_at": "2026-02-06T16:51:42.170Z", @@ -175,7 +175,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-08T01:27:05.059Z", "resolved_inferred": false, "started_at": "2026-01-07T21:40:22.410Z", @@ -188,7 +188,7 @@ "body": "Microsoft has rolled out a fix and all should be resolved. If you are still experiencing issues, please reach out to our support team.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-26T22:51:44.147Z", "resolved_inferred": false, "started_at": "2025-11-26T16:41:14.565Z", @@ -201,7 +201,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-19T05:03:48.509Z", "resolved_inferred": false, "started_at": "2025-11-18T22:20:35.000Z", @@ -214,7 +214,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-05T17:43:21.455Z", "resolved_inferred": false, "started_at": "2025-11-04T12:50:17.337Z", @@ -227,7 +227,7 @@ "body": "AWS has reported that most of its services have recovered at this time. We have also communicated with our impacted customers due to this outage through emails and support bot cases. Our current metrics indicate that all backups are functioning normally. We are closing this incident at this time. If you have any questions, please contact Cohesity Support.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-20T22:43:52.223Z", "resolved_inferred": false, "started_at": "2025-10-20T14:32:37.278Z", @@ -240,7 +240,7 @@ "body": "This was a maintenance announcement, but was opened as an incident. Resolving incident, and scheduling the maintenance accordingly.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-12T18:16:56.935Z", "resolved_inferred": false, "started_at": "2025-08-12T18:13:26.435Z", @@ -253,7 +253,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-11T23:24:59.001Z", "resolved_inferred": false, "started_at": "2025-08-11T19:52:06.027Z", diff --git a/api/v/coinbase-commerce.json b/api/v/coinbase-commerce.json index 69c176efba3549b60cb0b8a9757d11d9015a4bcb..a5795c3a2d6696d151abbbcdc0d8f9ed658d2951 100644 --- a/api/v/coinbase-commerce.json +++ b/api/v/coinbase-commerce.json @@ -3,7 +3,7 @@ "slug": "coinbase-commerce", "platform": "statuspage", "status_url": "https://status.commerce.coinbase.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-28T14:18:24.078-07:00", "resolved_inferred": false, "started_at": "2026-03-20T17:25:07.992-07:00", @@ -25,7 +25,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-09T07:23:51.644-08:00", "resolved_inferred": false, "started_at": "2026-02-07T13:37:38.725-08:00", @@ -38,7 +38,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-09T09:21:52.605-08:00", "resolved_inferred": false, "started_at": "2025-11-09T08:16:19.719-08:00", @@ -51,7 +51,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-20T17:58:56.368-07:00", "resolved_inferred": false, "started_at": "2025-10-20T00:33:19.512-07:00", @@ -64,7 +64,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-16T06:35:30.164-07:00", "resolved_inferred": false, "started_at": "2025-10-15T07:07:45.233-07:00", @@ -77,7 +77,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-27T14:15:07.397-07:00", "resolved_inferred": false, "started_at": "2025-09-26T00:23:12.567-07:00", @@ -90,7 +90,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-17T19:52:05.796-07:00", "resolved_inferred": false, "started_at": "2025-09-17T18:12:44.019-07:00", @@ -103,7 +103,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-21T13:06:47.628-07:00", "resolved_inferred": false, "started_at": "2025-08-21T12:11:43.000-07:00", diff --git a/api/v/coinbase-prime.json b/api/v/coinbase-prime.json index 672e8f9e865da172cd13fc04c9b98021501a0bdc..efa4b22f2cd343211bfb074fa1868febe18db3bb 100644 --- a/api/v/coinbase-prime.json +++ b/api/v/coinbase-prime.json @@ -3,7 +3,7 @@ "slug": "coinbase-prime", "platform": "statuspage", "status_url": "https://status.prime.coinbase.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "We regularly monitor the assets on our exchange to ensure they meet our listing standards. Based on recent reviews, we will suspend trading for IoTeX (IOTX) on 23 September 2026 on or around 2 PM ET. https://x.com/CoinbaseMarkets/status/2091951376490180737", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "started_at": "2026-09-03T10:35:33.959-07:00", "state": "monitoring", "title": "Asset Update: IoTeX (IOTX)", @@ -23,7 +23,7 @@ "body": "We regularly monitor the assets on our exchange to ensure they meet our listing standards. Based on recent reviews, we will suspend trading for Badger DAO (BADGER) & Storj (STORJ) on 28 September 2026 on or around 2 PM ET. https://x.com/CoinbaseMarkets/status/2093400472694526450", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "started_at": "2026-09-03T10:30:19.500-07:00", "state": "monitoring", "title": "Asset Update: Badger DAO (BADGER) & Storj (STORJ)", @@ -34,7 +34,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-09-03T21:00:45.062-07:00", "resolved_inferred": false, "started_at": "2026-09-03T09:40:59.586-07:00", @@ -47,7 +47,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-09-02T19:39:17.555-07:00", "resolved_inferred": false, "started_at": "2026-09-02T19:16:32.882-07:00", @@ -60,7 +60,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-09-02T07:16:34.134-07:00", "resolved_inferred": false, "started_at": "2026-09-02T03:57:55.886-07:00", @@ -73,7 +73,7 @@ "body": "Core DAO sends and receives are temporarily paused. Buys, sells, converts, and fiat transactions are not affected. Our team is aware of this and will provide updates as soon as possible.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "started_at": "2026-08-30T21:48:07.426-07:00", "state": "investigating", "title": "Paused Sends/Receives - Core DAO Network", @@ -84,7 +84,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-29T14:51:20.014-07:00", "resolved_inferred": false, "started_at": "2026-08-28T22:05:32.323-07:00", @@ -97,7 +97,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-21T17:58:25.305-07:00", "resolved_inferred": false, "started_at": "2026-08-21T16:28:21.000-07:00", @@ -110,7 +110,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-14T19:33:40.129-07:00", "resolved_inferred": false, "started_at": "2026-08-14T18:33:23.193-07:00", @@ -123,7 +123,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-12T01:33:49.203-07:00", "resolved_inferred": false, "started_at": "2026-08-12T01:30:02.012-07:00", @@ -136,7 +136,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-12T01:43:25.091-07:00", "resolved_inferred": false, "started_at": "2026-08-11T21:12:12.599-07:00", @@ -149,7 +149,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-10T15:11:21.014-07:00", "resolved_inferred": false, "started_at": "2026-08-10T09:14:57.331-07:00", @@ -162,7 +162,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-27T16:22:46.193-07:00", "resolved_inferred": false, "started_at": "2026-08-06T14:45:12.640-07:00", @@ -175,7 +175,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-03T13:17:14.131-07:00", "resolved_inferred": false, "started_at": "2026-08-03T13:08:39.108-07:00", @@ -188,7 +188,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-31T15:48:18.405-07:00", "resolved_inferred": false, "started_at": "2026-07-31T14:53:16.318-07:00", @@ -201,7 +201,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-31T13:11:33.670-07:00", "resolved_inferred": false, "started_at": "2026-07-31T12:23:50.804-07:00", @@ -214,7 +214,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-28T15:49:31.874-07:00", "resolved_inferred": false, "started_at": "2026-07-28T08:00:03.806-07:00", @@ -227,7 +227,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-21T09:43:03.633-07:00", "resolved_inferred": false, "started_at": "2026-07-21T07:58:39.131-07:00", @@ -240,7 +240,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-18T11:46:12.047-07:00", "resolved_inferred": false, "started_at": "2026-07-18T09:38:10.925-07:00", @@ -253,7 +253,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-17T21:00:05.229-07:00", "resolved_inferred": false, "started_at": "2026-07-17T17:51:00.800-07:00", @@ -266,7 +266,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-16T18:56:42.354-07:00", "resolved_inferred": false, "started_at": "2026-07-16T15:59:37.256-07:00", @@ -279,7 +279,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-16T11:49:36.122-07:00", "resolved_inferred": false, "started_at": "2026-07-16T10:12:25.896-07:00", @@ -292,7 +292,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-15T12:00:59.090-07:00", "resolved_inferred": false, "started_at": "2026-07-15T09:04:03.369-07:00", @@ -305,7 +305,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-14T11:01:48.072-07:00", "resolved_inferred": false, "started_at": "2026-07-14T10:15:05.615-07:00", @@ -318,7 +318,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-14T09:26:12.970-07:00", "resolved_inferred": false, "started_at": "2026-07-14T06:34:12.479-07:00", @@ -331,7 +331,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-12T06:34:47.238-07:00", "resolved_inferred": false, "started_at": "2026-07-12T05:56:59.051-07:00", @@ -344,7 +344,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-10T18:47:34.538-07:00", "resolved_inferred": false, "started_at": "2026-07-10T17:00:09.887-07:00", @@ -357,7 +357,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-10T17:04:51.537-07:00", "resolved_inferred": false, "started_at": "2026-07-10T16:43:39.031-07:00", @@ -370,7 +370,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-10T04:08:08.968-07:00", "resolved_inferred": false, "started_at": "2026-07-10T03:13:18.000-07:00", @@ -383,7 +383,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-10T16:04:20.158-07:00", "resolved_inferred": false, "started_at": "2026-07-08T05:54:53.496-07:00", @@ -396,7 +396,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-08T14:42:06.886-07:00", "resolved_inferred": false, "started_at": "2026-07-08T03:45:23.209-07:00", @@ -409,7 +409,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-11T08:56:36.685-07:00", "resolved_inferred": false, "started_at": "2026-07-07T15:29:48.873-07:00", @@ -422,7 +422,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-04T20:43:11.636-07:00", "resolved_inferred": false, "started_at": "2026-07-04T09:07:11.270-07:00", @@ -435,7 +435,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-25T13:46:53.335-07:00", "resolved_inferred": false, "started_at": "2026-06-25T09:25:42.000-07:00", @@ -448,7 +448,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-24T21:52:52.498-07:00", "resolved_inferred": false, "started_at": "2026-06-24T15:03:33.104-07:00", @@ -461,7 +461,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-24T11:15:50.543-07:00", "resolved_inferred": false, "started_at": "2026-06-24T10:49:25.590-07:00", @@ -474,7 +474,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-16T13:15:35.723-07:00", "resolved_inferred": false, "started_at": "2026-06-16T13:01:14.560-07:00", @@ -487,7 +487,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-17T09:28:20.566-07:00", "resolved_inferred": false, "started_at": "2026-06-16T09:13:52.741-07:00", @@ -500,7 +500,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-16T11:49:50.727-07:00", "resolved_inferred": false, "started_at": "2026-06-16T08:02:27.962-07:00", @@ -513,7 +513,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-15T12:13:45.883-07:00", "resolved_inferred": false, "started_at": "2026-06-15T11:36:39.759-07:00", @@ -526,7 +526,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-13T13:10:47.669-07:00", "resolved_inferred": false, "started_at": "2026-06-13T09:40:12.000-07:00", @@ -539,7 +539,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-10T10:42:49.130-07:00", "resolved_inferred": false, "started_at": "2026-06-09T19:23:01.000-07:00", @@ -552,7 +552,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-09T11:41:36.810-07:00", "resolved_inferred": false, "started_at": "2026-06-09T11:06:52.754-07:00", @@ -565,7 +565,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-05T14:50:14.031-07:00", "resolved_inferred": false, "started_at": "2026-06-05T11:47:09.048-07:00", @@ -578,7 +578,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-04T11:30:52.872-07:00", "resolved_inferred": false, "started_at": "2026-06-04T10:31:13.313-07:00", @@ -591,7 +591,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-04T14:54:56.390-07:00", "resolved_inferred": false, "started_at": "2026-06-03T11:43:44.238-07:00", @@ -604,7 +604,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-01T16:31:05.619-07:00", "resolved_inferred": false, "started_at": "2026-06-01T13:16:13.849-07:00", @@ -617,7 +617,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-29T20:41:31.197-07:00", "resolved_inferred": false, "started_at": "2026-05-29T16:25:00.059-07:00", @@ -630,7 +630,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-28T00:01:47.155-07:00", "resolved_inferred": false, "started_at": "2026-05-27T23:13:49.173-07:00", @@ -643,7 +643,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-27T16:11:25.475-07:00", "resolved_inferred": false, "started_at": "2026-05-27T00:24:37.280-07:00", diff --git a/api/v/coinbase-pro.json b/api/v/coinbase-pro.json index d3304f6fc5e7eb1f0e00c0b3f278252eefd15371..4f56ccd3432cf867d7d6d14f5620d70e905e19c3 100644 --- a/api/v/coinbase-pro.json +++ b/api/v/coinbase-pro.json @@ -3,7 +3,7 @@ "slug": "coinbase-pro", "platform": "statuspage", "status_url": "https://status.pro.coinbase.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "unknown", "history_backfilled": false, "first_watched": "2026-09-04T07:06:16Z", diff --git a/api/v/coinbase.json b/api/v/coinbase.json index 6ba0e219e3d761d37f1a223a59060872b616d363..29ef04a0d068912aeb27384befc6371cf0c827fe 100644 --- a/api/v/coinbase.json +++ b/api/v/coinbase.json @@ -3,7 +3,7 @@ "slug": "coinbase", "platform": "statuspage", "status_url": "https://coinbase.statuspage.io", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "degraded", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "Some customers may experience degraded performance when viewing derivative positions. Our team is investigating and will provide updates as soon as possible. Your funds are safe.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "started_at": "2026-09-03T19:34:19.322-07:00", "state": "investigating", "title": "Degraded Performance - Derivatives Positions", @@ -23,7 +23,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-09-03T21:00:03.398-07:00", "resolved_inferred": false, "started_at": "2026-09-03T09:40:09.642-07:00", @@ -36,7 +36,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-09-03T05:25:52.139-07:00", "resolved_inferred": false, "started_at": "2026-09-03T04:07:44.098-07:00", @@ -49,7 +49,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-09-03T01:16:30.706-07:00", "resolved_inferred": false, "started_at": "2026-09-03T00:37:10.734-07:00", @@ -62,7 +62,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-09-02T22:56:42.809-07:00", "resolved_inferred": false, "started_at": "2026-09-02T20:23:25.268-07:00", @@ -75,7 +75,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-09-02T19:38:33.617-07:00", "resolved_inferred": false, "started_at": "2026-09-02T19:16:03.575-07:00", @@ -88,7 +88,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-09-02T17:08:50.366-07:00", "resolved_inferred": false, "started_at": "2026-09-02T14:57:01.969-07:00", @@ -101,7 +101,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-09-02T07:15:48.608-07:00", "resolved_inferred": false, "started_at": "2026-09-02T03:51:12.853-07:00", @@ -114,7 +114,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-09-01T19:17:11.440-07:00", "resolved_inferred": false, "started_at": "2026-09-01T17:55:36.690-07:00", @@ -127,7 +127,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-09-01T15:37:24.458-07:00", "resolved_inferred": false, "started_at": "2026-09-01T15:32:32.520-07:00", @@ -140,7 +140,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-09-01T08:35:57.546-07:00", "resolved_inferred": false, "started_at": "2026-08-31T17:42:37.077-07:00", @@ -153,7 +153,7 @@ "body": "Core DAO sends and receives are temporarily paused. Buys, sells, converts, and fiat transactions are not affected. Our team is aware of this and will provide updates as soon as possible.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "started_at": "2026-08-30T21:41:13.162-07:00", "state": "investigating", "title": "Paused Sends/Receives - Core DAO Network", @@ -164,7 +164,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-29T14:50:50.360-07:00", "resolved_inferred": false, "started_at": "2026-08-28T22:04:48.148-07:00", @@ -177,7 +177,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-28T01:07:13.983-07:00", "resolved_inferred": false, "started_at": "2026-08-28T00:00:45.240-07:00", @@ -190,7 +190,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-24T11:35:15.627-07:00", "resolved_inferred": false, "started_at": "2026-08-24T11:19:44.449-07:00", @@ -203,7 +203,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-24T10:56:32.532-07:00", "resolved_inferred": false, "started_at": "2026-08-22T04:31:29.239-07:00", @@ -216,7 +216,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-21T17:57:42.140-07:00", "resolved_inferred": false, "started_at": "2026-08-21T16:26:41.000-07:00", @@ -229,7 +229,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-21T18:00:50.785-07:00", "resolved_inferred": false, "started_at": "2026-08-21T14:31:06.985-07:00", @@ -242,7 +242,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-20T16:13:29.973-07:00", "resolved_inferred": false, "started_at": "2026-08-20T15:57:47.489-07:00", @@ -255,7 +255,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-19T09:58:51.332-07:00", "resolved_inferred": false, "started_at": "2026-08-19T09:05:43.956-07:00", @@ -268,7 +268,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-17T19:54:06.677-07:00", "resolved_inferred": false, "started_at": "2026-08-17T16:55:04.826-07:00", @@ -281,7 +281,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-14T22:57:57.795-07:00", "resolved_inferred": false, "started_at": "2026-08-14T22:35:04.401-07:00", @@ -294,7 +294,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-14T19:32:33.979-07:00", "resolved_inferred": false, "started_at": "2026-08-14T18:32:35.285-07:00", @@ -307,7 +307,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-14T06:41:22.740-07:00", "resolved_inferred": false, "started_at": "2026-08-14T06:37:26.222-07:00", @@ -320,7 +320,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-13T17:43:00.159-07:00", "resolved_inferred": false, "started_at": "2026-08-13T17:30:55.174-07:00", @@ -333,7 +333,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-19T17:15:44.425-07:00", "resolved_inferred": false, "started_at": "2026-08-12T14:38:38.389-07:00", @@ -346,7 +346,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-19T17:16:07.385-07:00", "resolved_inferred": false, "started_at": "2026-08-12T14:36:59.088-07:00", @@ -359,7 +359,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-19T17:16:20.587-07:00", "resolved_inferred": false, "started_at": "2026-08-12T14:34:33.266-07:00", @@ -372,7 +372,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-12T01:34:28.584-07:00", "resolved_inferred": false, "started_at": "2026-08-12T01:27:29.295-07:00", @@ -385,7 +385,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-12T01:42:01.008-07:00", "resolved_inferred": false, "started_at": "2026-08-11T21:11:19.292-07:00", @@ -398,7 +398,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-10T15:10:48.177-07:00", "resolved_inferred": false, "started_at": "2026-08-10T09:13:50.118-07:00", @@ -411,7 +411,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-09T01:42:50.200-07:00", "resolved_inferred": false, "started_at": "2026-08-09T00:42:39.529-07:00", @@ -424,7 +424,7 @@ "body": "Some users may have experienced degraded performance when completing transactions through the CDP x402 facilitator between 6:00 AM \u2013 9:00 AM ET on August 7, 2026. This issue has been resolved and normal performance has been restored. Your funds are safe.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-07T03:00:00.000-07:00", "resolved_inferred": false, "started_at": "2026-08-07T03:00:00.000-07:00", @@ -437,7 +437,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-06T03:14:54.313-07:00", "resolved_inferred": false, "started_at": "2026-08-06T01:16:47.047-07:00", @@ -450,7 +450,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-05T08:53:29.733-07:00", "resolved_inferred": false, "started_at": "2026-08-04T18:38:41.605-07:00", @@ -463,7 +463,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-03T13:16:38.432-07:00", "resolved_inferred": false, "started_at": "2026-08-03T13:07:04.104-07:00", @@ -476,7 +476,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-31T15:47:43.562-07:00", "resolved_inferred": false, "started_at": "2026-07-31T14:52:50.853-07:00", @@ -489,7 +489,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-31T13:11:03.939-07:00", "resolved_inferred": false, "started_at": "2026-07-31T12:22:28.578-07:00", @@ -502,7 +502,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-30T03:57:26.604-07:00", "resolved_inferred": false, "started_at": "2026-07-30T02:50:34.308-07:00", @@ -515,7 +515,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-28T14:10:11.489-07:00", "resolved_inferred": false, "started_at": "2026-07-28T13:40:37.102-07:00", @@ -528,7 +528,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-29T16:06:06.689-07:00", "resolved_inferred": false, "started_at": "2026-07-28T13:00:35.000-07:00", @@ -541,7 +541,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-28T11:15:38.547-07:00", "resolved_inferred": false, "started_at": "2026-07-28T09:21:30.293-07:00", @@ -554,7 +554,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-28T15:48:33.596-07:00", "resolved_inferred": false, "started_at": "2026-07-28T07:59:15.916-07:00", @@ -567,7 +567,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-27T18:21:25.953-07:00", "resolved_inferred": false, "started_at": "2026-07-27T18:12:36.493-07:00", @@ -580,7 +580,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-21T23:07:33.661-07:00", "resolved_inferred": false, "started_at": "2026-07-21T20:48:28.586-07:00", @@ -593,7 +593,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-21T09:42:40.302-07:00", "resolved_inferred": false, "started_at": "2026-07-21T07:54:21.780-07:00", @@ -606,7 +606,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-20T07:51:41.862-07:00", "resolved_inferred": false, "started_at": "2026-07-20T06:45:05.118-07:00", @@ -619,7 +619,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-18T11:45:48.158-07:00", "resolved_inferred": false, "started_at": "2026-07-18T09:36:55.966-07:00", @@ -632,7 +632,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-18T23:48:04.742-07:00", "resolved_inferred": false, "started_at": "2026-07-18T06:59:20.134-07:00", @@ -645,7 +645,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-18T00:48:14.582-07:00", "resolved_inferred": false, "started_at": "2026-07-17T19:50:12.455-07:00", diff --git a/api/v/coingate.json b/api/v/coingate.json index 3c191e9e8b147d56b8bd2b3ed0430e9ad943f4d2..4f333293cbc6ee9d6ec7f30ccacd7c4669238c1a 100644 --- a/api/v/coingate.json +++ b/api/v/coingate.json @@ -3,7 +3,7 @@ "slug": "coingate", "platform": "betterstack", "status_url": "https://status.coingate.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": false, "first_watched": "2026-09-04T07:06:16Z", diff --git a/api/v/coinjar.json b/api/v/coinjar.json index 5623e57187ebdcde0ed8e6f0fe127665b99e3170..06b8dbaf9fbd08b9488d1832dd175106723a0d38 100644 --- a/api/v/coinjar.json +++ b/api/v/coinjar.json @@ -3,7 +3,7 @@ "slug": "coinjar", "platform": "statuspage", "status_url": "https://status.coinjar.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-23T18:29:27.111+10:00", "resolved_inferred": false, "started_at": "2026-06-23T17:16:34.309+10:00", @@ -25,7 +25,7 @@ "body": "This incident has been resolved. Please contact support@coinjar.com if you need assistance with an impacted transaction.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-04T13:56:10.169+10:00", "resolved_inferred": false, "started_at": "2026-06-04T11:58:40.773+10:00", @@ -38,7 +38,7 @@ "body": "This incident has been resolved. Please contact support@coinjar.com if you experience any other issues.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-24T10:52:37.871+11:00", "resolved_inferred": false, "started_at": "2025-12-24T09:55:46.000+11:00", @@ -51,7 +51,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-26T18:56:59.954+10:00", "resolved_inferred": false, "started_at": "2025-08-26T17:01:31.023+10:00", @@ -64,7 +64,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-07T15:04:36.690+10:00", "resolved_inferred": false, "started_at": "2025-08-07T10:47:30.136+10:00", diff --git a/api/v/coinlist.json b/api/v/coinlist.json index 457f1087726233a8b9af402037a85bd3687495ca..4698ceead970832544c0150ddfe964f64ed8b277 100644 --- a/api/v/coinlist.json +++ b/api/v/coinlist.json @@ -3,7 +3,7 @@ "slug": "coinlist", "platform": "statuspage", "status_url": "https://status.coinlist.co", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "NIL Withdrawals were re-enabled.", "first_seen": "2026-09-04T07:06:16Z", "impact": "maintenance", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-20T08:38:28.616Z", "resolved_inferred": false, "started_at": "2026-02-18T17:34:00.226Z", @@ -25,7 +25,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-06T23:27:03.422Z", "resolved_inferred": false, "started_at": "2026-01-05T09:00:26.063Z", @@ -38,7 +38,7 @@ "body": "The CoinList non-custodial wallet currently supports deposits for the following assets on the Ethereum mainnet only:\n\t\u2022\tUSDC\n\t\u2022\tUSDT\n\t\u2022\tETH (used for gas fees)\n\nDeposits of unsupported assets, or deposits sent on unsupported networks or chains, will not appear in the wallet interface.", "first_seen": "2026-09-04T07:06:16Z", "impact": "maintenance", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-05T14:24:05.740Z", "resolved_inferred": false, "started_at": "2025-12-08T11:54:43.769Z", @@ -51,7 +51,7 @@ "body": "All trading ended November 30, 2025.", "first_seen": "2026-09-04T07:06:16Z", "impact": "maintenance", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-06T23:28:10.697Z", "resolved_inferred": false, "started_at": "2025-11-19T17:26:59.739Z", @@ -64,7 +64,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-17T19:12:39.268Z", "resolved_inferred": false, "started_at": "2025-11-17T14:07:57.346Z", @@ -77,7 +77,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-03T18:50:56.031Z", "resolved_inferred": false, "started_at": "2025-10-27T16:43:07.269Z", @@ -90,7 +90,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-05T20:28:56.164Z", "resolved_inferred": false, "started_at": "2025-10-24T21:41:06.679Z", @@ -103,7 +103,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-03T20:16:18.780Z", "resolved_inferred": false, "started_at": "2025-10-23T15:51:13.290Z", @@ -116,7 +116,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-21T12:44:03.961Z", "resolved_inferred": false, "started_at": "2025-10-21T11:34:17.078Z", @@ -129,7 +129,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-21T07:08:48.413Z", "resolved_inferred": false, "started_at": "2025-10-20T11:54:18.412Z", @@ -142,7 +142,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-06T17:02:15.012Z", "resolved_inferred": false, "started_at": "2025-10-06T11:21:33.997Z", @@ -155,7 +155,7 @@ "body": "Unscheduled maintenance for FIL has been completed. Deposits, Withdrawals, and Trading have all been enabled.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-10T03:00:56.146Z", "resolved_inferred": false, "started_at": "2025-10-04T04:52:04.845Z", @@ -168,7 +168,7 @@ "body": "AXL withdrawals will not be re-enabled, as we are migrating all AXL to wAXL.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-02T19:03:14.128Z", "resolved_inferred": false, "started_at": "2025-10-02T16:52:21.699Z", @@ -181,7 +181,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-11T08:59:08.371Z", "resolved_inferred": false, "started_at": "2025-09-09T16:40:36.000Z", @@ -194,7 +194,7 @@ "body": "The syncing issue is impacting both Deposits and Withdrawals for all three assets. To simplify status updates, we are resolving this deposit status and merging it with the active withdrawal status. Please note that the issue is still ongoing.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-17T18:48:47.381Z", "resolved_inferred": false, "started_at": "2025-09-05T18:46:34.678Z", @@ -207,7 +207,7 @@ "body": "ICP withdrawals are now enabled.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-20T15:01:30.510Z", "resolved_inferred": false, "started_at": "2025-09-03T17:48:42.208Z", @@ -220,7 +220,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-20T08:58:37.598Z", "resolved_inferred": false, "started_at": "2025-08-14T14:24:15.741Z", diff --git a/api/v/coinmarketcap.json b/api/v/coinmarketcap.json index aaa9549e27d3b268b1c83b6e221ac3e1ec3271d1..2318b898575d1a99ed3376cbcb81a160215d890f 100644 --- a/api/v/coinmarketcap.json +++ b/api/v/coinmarketcap.json @@ -3,7 +3,7 @@ "slug": "coinmarketcap", "platform": "statuspage", "status_url": "https://status.coinmarketcap.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", diff --git a/api/v/commercetools-gmbh.json b/api/v/commercetools-gmbh.json index 42b0e03f23b5cc5173a63c3add5cbdb0886d07c2..be1757638cb16c98d7e86e2a228d9a08cfe4ef5e 100644 --- a/api/v/commercetools-gmbh.json +++ b/api/v/commercetools-gmbh.json @@ -3,7 +3,7 @@ "slug": "commercetools-gmbh", "platform": "status.io", "status_url": "https://status.commercetools.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": false, "first_watched": "2026-09-04T07:06:16Z", diff --git a/api/v/compliancealpha.json b/api/v/compliancealpha.json index 5ac05e8d3c4026a6562d8437139b5afc5a9ddd45..0112d8bc85c67f38c4f5901e92a96684cd494298 100644 --- a/api/v/compliancealpha.json +++ b/api/v/compliancealpha.json @@ -3,7 +3,7 @@ "slug": "compliancealpha", "platform": "statuspage", "status_url": "https://status.acats.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-04T17:05:24.809-04:00", "resolved_inferred": false, "started_at": "2026-08-04T15:51:43.694-04:00", @@ -25,7 +25,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-22T15:14:56.198-04:00", "resolved_inferred": false, "started_at": "2026-07-22T13:28:11.893-04:00", @@ -38,7 +38,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-27T13:59:31.064-04:00", "resolved_inferred": false, "started_at": "2026-05-27T11:48:56.025-04:00", @@ -51,7 +51,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-05T14:48:00.432-04:00", "resolved_inferred": false, "started_at": "2026-05-05T12:36:39.764-04:00", @@ -64,7 +64,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-01T17:01:49.895-04:00", "resolved_inferred": false, "started_at": "2026-05-01T14:02:08.410-04:00", @@ -77,7 +77,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-30T17:13:49.564-04:00", "resolved_inferred": false, "started_at": "2026-04-30T14:23:00.599-04:00", @@ -90,7 +90,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-27T16:40:05.631-04:00", "resolved_inferred": false, "started_at": "2026-04-27T15:54:04.938-04:00", @@ -103,7 +103,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-31T09:40:08.097-04:00", "resolved_inferred": false, "started_at": "2026-03-30T08:19:22.749-04:00", @@ -116,7 +116,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-18T13:32:27.004-05:00", "resolved_inferred": false, "started_at": "2026-02-18T10:20:46.000-05:00", @@ -129,7 +129,7 @@ "body": "The issue affecting ETF selection and security list ordering has been resolved. ETF securities are now selectable, and the security list is displaying in the correct order.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-21T12:26:03.951-05:00", "resolved_inferred": false, "started_at": "2026-01-21T10:18:02.594-05:00", @@ -142,7 +142,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-21T10:02:27.842-05:00", "resolved_inferred": false, "started_at": "2026-01-16T13:36:22.000-05:00", @@ -155,7 +155,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-12T17:40:23.589-05:00", "resolved_inferred": false, "started_at": "2026-01-12T04:45:54.246-05:00", @@ -168,7 +168,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-17T14:42:01.368-05:00", "resolved_inferred": false, "started_at": "2025-12-17T10:43:57.497-05:00", @@ -181,7 +181,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-24T16:08:52.182-05:00", "resolved_inferred": false, "started_at": "2025-11-24T13:40:12.546-05:00", @@ -194,7 +194,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-29T17:55:22.177-04:00", "resolved_inferred": false, "started_at": "2025-10-29T05:26:32.990-04:00", @@ -207,7 +207,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-09T11:17:30.395-04:00", "resolved_inferred": false, "started_at": "2025-10-06T11:51:31.499-04:00", @@ -220,7 +220,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-01T12:26:06.733-04:00", "resolved_inferred": false, "started_at": "2025-10-01T10:42:20.183-04:00", @@ -233,7 +233,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-05T13:27:47.840-04:00", "resolved_inferred": false, "started_at": "2025-09-05T09:50:48.000-04:00", diff --git a/api/v/confluence.json b/api/v/confluence.json index fb09532ed601ec6adf9610ae1431c14dfbb28593..6b1958d7fe905c56a3bca6cd64a070975dabf8a9 100644 --- a/api/v/confluence.json +++ b/api/v/confluence.json @@ -3,7 +3,7 @@ "slug": "confluence", "platform": "statuspage", "status_url": "https://confluence.status.atlassian.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "On 27 August 2026 UTC, Atlassian products including Jira Cloud, Jira Service Management and Confluence experienced a disruption, and services were unavailable to affected users. \n\nThe issue has now been resolved, and the service is operating normally for all affected customers.\n\nA public postmortem for this incident will be made available on this page when our full investigation of the incident has been completed.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-27T05:16:07.474Z", "resolved_inferred": false, "started_at": "2026-08-27T04:22:09.127Z", @@ -25,7 +25,7 @@ "body": "On 25th Aug 2026, some users may have experienced increased latency in email, mobile and slack notifications.\n\nThe issue has now been resolved, and the service is operating normally for all customers.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-25T14:33:57.169Z", "resolved_inferred": false, "started_at": "2026-08-25T08:42:48.035Z", @@ -38,7 +38,7 @@ "body": "On August 24, 2026, some JIRA, JSM, and Confluence users may have experienced performance degradation resulting in increased latency in email, mobile, and Slack notifications. The issue has been resolved for newly created notifications, and service is operating normally.\n\nThere may be older notifications that are being processed, and we expect them to be completed in next few hours.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-24T23:15:20.518Z", "resolved_inferred": false, "started_at": "2026-08-24T19:22:47.308Z", @@ -51,7 +51,7 @@ "body": "On 21st Aug 2026, between 04:26 UTC and 09:33 UTC, some users may have experienced issues with macros not rendering correctly in Confluence. \n\nThe issue has now been resolved and the service is operating normally for all customers.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-21T10:10:30.571Z", "resolved_inferred": false, "started_at": "2026-08-21T07:16:32.123Z", @@ -64,7 +64,7 @@ "body": "On August 12, 2026 some Confluence users utilizing anonymous access via public links, may have experienced a 'Something went wrong' error message. The issue has now been resolved, and the service is operating normally for all affected customers.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-12T22:13:28.260Z", "resolved_inferred": false, "started_at": "2026-08-12T20:11:34.000Z", @@ -77,7 +77,7 @@ "body": "## Summary\n\nOn Jul 6, 2026, between 06:51 and 20:17 UTC, Atlassian customers using cloud products in European (EU) regions experienced service disruptions affecting automation rule execution, user search, user picker, and related workflows. The incident began when a core identity service experienced database saturation in EU regions, increasing latency and error rates. While responders worked to restore capacity, an emergency mitigation was applied which blocked automation rules from accessing the identity endpoint. In parallel, the elevated identity latency contributed to a cascading failure in a downstream user search service, degrading user search and user picker experiences across multiple products. Service was progressively restored after additional database read capacity was added, the emergency block was removed, and the user search service was manually scaled up.\n\n \n\n## Impact\n\nThe incident affected customers across multiple Atlassian products in EU regions on Jul 6, 2026 between 06:51 and 20:17 UTC.\n\n- **Core Identity service degradation:** elevated intermittent access denied rates were observed across products in EU regions.\n- **Automation rule execution failures:** automation rules using the default user (Automation for Jira) in Jira, Jira Service Management, and Jira Product Discovery in EU regions failed with a permissions error.\n- **User search and user picker failures:** user search success rates dropped significantly in EU regions, with user picker capability largely unavailable across products.\n\n \n\n## Root Cause\n\nThe incident originated from a recent configuration change that reduced the cache lifetime for a core identity service. As EU workday traffic ramped up on July 6, 2026, a larger share of requests began reaching the backing database directly rather than being served from cache. The EU databases did not have sufficient regional capacity to absorb the increased load, and database CPU reached saturation, causing elevated intermittent access denied rates.\n\nAs part of the mitigation, an emergency block was applied to reduce load on the saturated identity service database and prioritize restoring the core identity service. This inadvertently prevented automation rules from passing their pre-execution permission checks, causing them to fail. The extended duration was primarily due to a secondary wave of automation rule failures caused by the processing limit throttling.\n\nIn parallel, the sustained degradation caused increased latency and intermittent failures across products that depend on these checks, and contributed to a cascading failure in a downstream user search service. As a result, user search and user picker experiences became largely unavailable in EU regions until the permissions service recovered and the user search service was scaled up to restore capacity.\n\n \n\n## Remedial Actions Plan & Next Steps\n\nWe know outages impact customers' productivity. Atlassian is prioritizing the following actions to help prevent similar incidents in future:\n\n- **Improve safeguards for high-impact emergency mitigations:** Harden operational tooling so mitigation steps that could disable customer-facing workflows require additional review.\n- **Strengthen identity infrastructure capacity and change safety:** Review regional database sizing and capacity headroom to reduce the risk of saturation during peak traffic periods, and refine the assessment process for configuration changes so downstream load impact is evaluated before production rollout.\n- **Strengthen resilience against cascading failures from upstream degradation:** Audit backpressure handling, circuit breaker configuration, and autoscaling behavior in services, so that upstream degradation does not cause broader product impact across user search, user picker, and related experiences.\n- **Harden replay mechanisms for Automation rule failures:** Increase resilience of automation rules to reduce impact associated with incidents occurring in dependencies..\n\nWe recognize how critical reliable product workflows are for our customers, and we apologize to customers who were impacted by this incident.\n\n \n\nThanks,\n\nAtlassian Customer Support", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-06T13:04:02.024Z", "resolved_inferred": false, "started_at": "2026-07-06T09:23:39.471Z", @@ -90,7 +90,7 @@ "body": "### Summary\n\n### \n\nOn Jun 12, 2026, between 07:04 and 12:10 UTC and on Jun 16, 2026, between 12:56 and 14:35 UTC, a subset of Atlassian customers using Confluence Cloud experienced errors and degraded performance when attempting to view or edit pages. The event was triggered when a database cluster within our infrastructure stopped responding to connection close requests. This caused idle connections to accumulate rather than be released \u2014 resulting in increased memory pressure and cascading errors for users. The incident was detected by our automated monitoring within 18 minutes and mitigated by scaling database resources and redeploying, which recycled the idle connections. A permanent fix has since been developed and deployed.\n\n \n\n### IMPACT\n\n### \n\nThe overall impact was between Jun 12, 2026 07:04 and 12:10 UTC and Jun 16, 2026 12:56 and 14:35 UTC on Confluence Cloud. The June 12 incident caused service disruption to a subset of customers in the EU region while the June 16 incident caused service disruption to a subset of customers in the US region. Impacted users experienced errors or degraded performance when attempting to view, edit, or access Confluence content and spaces.\n\n \n\n### ROOT CAUSE\n\n### \n\n1. A database cluster within our infrastructure stopped responding to connection close requests.\n2. Idle connections accumulated across clusters rather than being closed, creating a connection leak and increasing memory pressure on the database layer.\n3. Hitting max connections on the cluster degraded query performance.\n4. Users attempting to view or edit Confluence content experienced errors and slow load times as a result.\n\n \n\n### REMEDIAL ACTIONS PLAN & NEXT STEPS\n\n### \n\nWe know that outages impact your productivity. While we have a number of testing and preventative processes in place, this specific design limitation in our connection cleanup process was not identified until it was triggered by an adverse infrastructure condition in production.\n\n \n\nWe have already deployed the following fix:\n\n- Redesigned the database connection cleanup process to prevent unresponsive connections from impacting the closure of others.\n\nTo minimize the impact of similar incidents in the future, we will implement additional preventative measures such as:\n\n- Monitoring and alerting for connection cleanup latency and failure rates, so that slowdowns in connection closure are detected early.\n- Enhanced safeguards on database connection creation to limit the blast radius of any future connection accumulation events.\n\nWe apologize to customers whose services were impacted during this incident. We are taking immediate steps to improve the resilience of our platform_._\n\n \n\nThanks,\n\nAtlassian Customer Support", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-16T15:56:40.613Z", "resolved_inferred": false, "started_at": "2026-06-16T13:46:41.998Z", @@ -103,7 +103,7 @@ "body": "### Summary\n\nOn Jun 12, 2026, between 07:04 and 12:10 UTC and on Jun 16, 2026, between 12:56 and 14:35 UTC, a subset of Atlassian customers using Confluence Cloud experienced errors and degraded performance when attempting to view or edit pages. The event was triggered when a database cluster within our infrastructure stopped responding to connection close requests. This caused idle connections to accumulate rather than be released \u2014 resulting in increased memory pressure and cascading errors for users. The incident was detected by our automated monitoring within 18 minutes and mitigated by scaling database resources and redeploying, which recycled the idle connections. A permanent fix has since been developed and deployed.\n\n### IMPACT\n\nThe overall impact was between Jun 12, 2026 07:04 and 12:10 UTC and Jun 16, 2026 12:56 and 14:35 UTC on Confluence Cloud. The June 12 incident caused service disruption to a subset of customers in the EU region while the June 16 incident caused service disruption to a subset of customers in the US region. Impacted users experienced errors or degraded performance when attempting to view, edit, or access Confluence content and spaces.\n\n\u200c\n\n### ROOT CAUSE\n\n\u200c\n\n1. A database cluster within our infrastructure stopped responding to connection close requests.\n2. Idle connections accumulated across clusters rather than being closed, creating a connection leak and increasing memory pressure on the database layer.\n3. Hitting max connections on the cluster degraded query performance.\n4. Users attempting to view or edit Confluence content experienced errors and slow load times as a result.\n\n\u200c\n\n### REMEDIAL ACTIONS PLAN & NEXT STEPS\n\n\u200c\n\nWe know that outages impact your productivity. While we have a number of testing and preventative processes in place, this specific design limitation in our connection cleanup process was not identified until it was triggered by an adverse infrastructure condition in production.\n\n\u200c\n\nWe have already deployed the following fix:\n\n* Redesigned the database connection cleanup process to prevent unresponsive connections from impacting the closure of others.\n\nTo minimize the impact of similar incidents in the future, we will implement additional preventative measures such as:\n\n* Monitoring and alerting for connection cleanup latency and failure rates, so that slowdowns in connection closure are detected early.\n* Enhanced safeguards on database connection creation to limit the blast radius of any future connection accumulation events.\n\nWe apologize to customers whose services were impacted during this incident. We are taking immediate steps to improve the resilience of our platform_._\n\n\u200c\n\nThanks,\n\nAtlassian Customer Support", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-12T11:15:09.000Z", "resolved_inferred": false, "started_at": "2026-06-12T07:39:11.109Z", @@ -116,7 +116,7 @@ "body": "We are now confident that any of the tasks that were impacted by this incident and were delayed should now be operating as expected.\n\nWe apologize for any inconvenience that this issue may have caused.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-10T06:31:04.920Z", "resolved_inferred": false, "started_at": "2026-06-10T06:14:02.096Z", @@ -129,7 +129,7 @@ "body": "Between 00:50 UTC and 07:30 UTC on 27 May 2026, some users were facing errors when attempting to view Calendars in Confluence. Our engineering team identified and resolved the underlying issue, and this incident has been fully restored.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-27T07:48:49.273Z", "resolved_inferred": false, "started_at": "2026-05-27T06:03:31.792Z", @@ -142,7 +142,7 @@ "body": "Between 08:30 UTC and 13:51 UTC on 26 May 2026, some users were unable to load or edit certain macros in the Confluence Cloud page editor. Our engineering team identified and resolved the underlying issue, and macro functionality has been fully restored.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-26T13:55:52.365Z", "resolved_inferred": false, "started_at": "2026-05-26T10:40:00.024Z", @@ -155,7 +155,7 @@ "body": "### Summary\n\nOn May 14, 2026, between 04:30 and 05:26 UTC, Atlassian customers experienced widespread service disruption across multiple Atlassian Cloud products. The issue was caused by a race condition in our internal deployment orchestration platform during a routine rollback operation of a core identity service in the us-east region. This race condition resulted in insufficient capacity for the identity service in the affected region which started returning errors to dependent products. The incident was detected within a minute by automated monitoring systems and mitigated in 56 minutes.\n\n### **IMPACT**\n\nDuring the incident, customers attempting to access Atlassian Cloud products in the us-east region experienced authentication and permission failures and were unable to access services. Customers also experienced errors when accessing the support portal until Atlassian fell back to an alternate support method. This was caused by a core identity service in the us-east region becoming unavailable. Affected products included Atlassian Administration, Atlassian Analytics, Bitbucket, Compass, Confluence, Jira, Jira Product Discovery, Jira Service Management and Trello. Some users outside us-east may have been affected in certain scenarios.\n\n### **ROOT CAUSE**\n\nThe incident was caused by a race condition in our internal deployment orchestration platform during a routine rollback operation of a core identity service in the us-east region. This race condition resulted in insufficient capacity for the identity service in the affected region which started returning errors to dependent products.\n\n### **REMEDIAL ACTIONS PLAN & NEXT STEPS**\n\nWe know that outages impact your productivity. Atlassian is prioritizing the following actions to help prevent similar incidents in future:\n\n* **Refine deployment orchestration safeguards**\n\n * Harden our deployment platform to prevent similar race conditions or resulting capacity loss during a rollback operation.\n * Streamline mitigation steps when a service becomes unavailable in a region.\n \n* **Reduce cross-region impact**\n\n * Improve regional isolation and fallback handling so an issue affecting a single region is less likely to impact customers or product functionality in other regions.\n \n\nWe recognise how critical reliable access to Atlassian products is for our customers' productivity, and we apologize to customers who were impacted by this incident.\n\nThanks,\n\nAtlassian", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-14T06:48:27.957Z", "resolved_inferred": false, "started_at": "2026-05-14T04:54:57.984Z", @@ -168,7 +168,7 @@ "body": "All dates and times below are in UTC unless stated otherwise.\n\n### Summary\n\nOn May 8, 2026 between 00:22 and 06:08, one of our hosting providers suffered a significant incident in a specific availability zone in prod-east which led to Atlassian customers experiencing degraded performance and delays of background operations and automation execution.\n\nThe incident started on May 8, 2026 at 00:22 and was detected within 4 minutes by automated monitoring systems. Our teams worked to restore core access by 06:08. Final cleanup of backlogged processes and minor issues progressed in stages from there was completed iteratively by 19:15.\n\n### **IMPACT**\n\nThe primary infrastructure affected in this incident was the event processing pipeline in the prod-east region, which distributes events between Atlassian services and underpins background operations such as automation execution, search indexing, notifications, permission synchronisation.\n\n* Between 00:22 and 06:08, an infrastructure incident in our hosting provider triggered an ingestion failure in our event processing pipeline.\n* At 02:50, event ingestion was failed over to an unaffected availability zone, progressively restoring live event flows.\n* At 06:08, reliability for new ingestion in prod-east recovered to 100%. The remaining work was to drain the accumulated cross-region backlog of messages, which completed by 17:00.\n* By 18:48, Automation had processed their backlog of events that were created while processing\n\n**Automation**\n\nBetween 00:22 and 02:50, customers with automation rules triggered by events originating from the prod-east region experienced a significant reduction in rule executions. During this window, event-triggered automation rules were not firing because the events that trigger them were not being delivered. Rule authoring, saving, and rules triggered manually, by schedules, or by webhooks were not affected.\n\nAt 02:50, the event processing infrastructure failed over to an unaffected availability zone, restoring delivery of live events to Automation and allowing new event-triggered rules to begin executing normally. However, events generated during the impact window still needed to be replayed before delayed automations could be processed.\n\nBeginning at 08:28, upstream services replayed their queued events in a coordinated sequence, and all replayed events were processed by 18:48. During the replay window, customers may have experienced automation rules executing later than expected, a small number of rules reaching daily processing limits due to compressed replay, and time-sensitive rules not completing as expected if internal timeout thresholds were exceeded.\n\n**Jira and Jira Service Management**\n\nBetween 00:22 and 02:50, customers with tenants hosted in the prod-east region experienced disruption to Jira and Jira Service Management event-driven features like automation, along with a short period of elevated errors during infrastructure failover. Core Jira experiences, including issue view, boards, and project navigation, remained available throughout the incident.\n\nJira event delivery was affected by the primary impact, preventing downstream services from receiving issue lifecycle events. This affected automation rules triggered by Jira events, AI agent orchestration in Jira, notifications for issue updates and transitions, search indexing for newly created or modified issues, and event-driven integrations between Jira and other Atlassian products.\n\nAt 02:50, the event processing infrastructure failed over to an unaffected availability zone, restoring delivery of new events. All events generated during the impact window were retained in a recovery queue and required replaying. This began at 08:28 and completed at 12:00. During the replay window, customers may have experienced automation rules executing later than expected, delayed notifications arriving hours after the triggering action, temporary gaps in search results for content created or modified during the impact window, and AI agent workflows not completing as expected where internal timeout thresholds were exceeded.\n\n**Confluence**\n\nBetween 00:22 and 02:50, customers with tenants hosted in the prod-east region experienced disruptions to event-driven services in Confluence. This resulted in delays to search indexing, notifications, automation rule execution, and permission synchronisation.\n\nThe underlying event processing infrastructure failed over to an unaffected availability zone, after which live Confluence operations resumed normally. However, events generated during the impact window were queued for replay, and some background services remained delayed until that replay and related validation work completed.\n\nBetween 10:14 and 17:00, a bulk replay of all the queued tenant replay tasks was completed to restore data consistency. During and immediately after the replay window, customers may have experienced search results not reflecting content created or modified during the outage, delayed or missing notifications for page and comment activity, automation rules firing later than expected, and brief delays in permission synchronisation for tenants relying on incremental identity sync.\n\n**Bitbucket and Pipelines**\n\nBetween 00:22 and 06:08, customers using Bitbucket and Pipelines experienced failures and degraded functionality across event-driven workflows. Core Git operations, including push, pull, and clone, were not affected and continued to operate normally throughout the incident.\n\nAutomatic pipeline triggers initiated by push or pull request events were unavailable during the impact window. Merge queues, custom merge checks, Forge-based triggers, workspace permission changes, and some workspace provisioning flows were also affected. Customers using merge queues were unable to merge pull requests, and some pipeline steps failed because queued work contributed to elevated concurrency limits.\n\nAt approximately 03:57, Pipelines was reconfigured to consume events through an alternative path, restoring automatic pipeline triggering. Merge queues, custom merge checks, Forge triggers, and other affected workflows were progressively restored as the underlying event processing infrastructure recovered. All Bitbucket and Pipelines services were confirmed fully operational by 06:08. After recovery, queued events were reviewed and replayed where safe to restore data consistency for billing, audit logging, and other background processes.\n\n**Identity Services**\n\nBetween 00:22 and 02:50, customers with tenants hosted in the prod-east region experienced delays in the propagation of identity and group membership changes to downstream Atlassian products. Core identity operations, including authentication, login, and direct group management actions, were not affected and continued to function normally throughout the incident.\n\nThe impact was limited to asynchronous, event-driven operations that depend on the event processing pipeline. This included delays in delivering group membership and user profile changes to products such as Jira and Confluence, which affected downstream permission synchronisation and crowd sync flows. A small number of SCIM-based identity synchronisation and site provisioning workflows also experienced temporary delays.\n\nAfter the event processing infrastructure recovered, backed-up identity and group directory events were replayed where required, restoring downstream consistency for affected products. No identity data was lost. Group membership changes, user profile updates, and provisioning-related events that occurred during the impact window were retained and processed after recovery.\n\n### **REMEDIAL ACTIONS PLAN & NEXT STEPS**\n\nWe know outages impact your productivity. While our monitoring and recovery processes helped us respond quickly, this incident highlighted opportunities to further strengthen resilience for event-driven services.\n\nWe are prioritizing improvements that will:\n\n* **Enhance failover coverage** so critical event processing can recover more smoothly during infrastructure disruptions.\n* **Strengthen recovery handling** so replayed events can be processed more quickly.\n\nWe apologize to customers whose services were impacted during this incident; we are taking immediate steps to improve the platform\u2019s performance and availability.\n\nThanks,\n\nAtlassian Customer Support.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-08T19:45:31.411Z", "resolved_inferred": false, "started_at": "2026-05-08T01:31:38.293Z", @@ -181,7 +181,7 @@ "body": "On April 14, 2026, affected users may have experienced some service disruption with automation rules that use Rovo agents. The issue has now been resolved, and the service is operating normally for all affected customers.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-14T16:11:31.593Z", "resolved_inferred": false, "started_at": "2026-04-14T12:25:17.081Z", @@ -194,7 +194,7 @@ "body": "### Summary\n\nOn April 13, 2026, between 05:49 and 06:29 UTC, customers experienced failures when attempting to log in, sign up, reset passwords, and complete multi-factor authentication flows across Atlassian cloud products. Approximately 90% of authentication requests failed during the peak impact window, affecting users in the US East and EU regions. The incident was mitigated within 40 minutes through manual intervention, and full service was restored by 06:29 UTC.\n\n### **IMPACT**\n\n* **Duration**: ~40 minutes \\(05:49\u201306:29 UTC, April 13, 2026\\)\n* **Affected regions**: US East and EU \\(authentication infrastructure serves EU traffic from US East, with traffic primarily from EU at this time of day\\).\n* **Affected products**: All Atlassian cloud products requiring authentication, including Jira, Confluence, Jira Service Management, and Trello.\n* **Customer experience**: Users attempting to log in, sign up, reset passwords, or complete MFA flows received errors. Users already logged in with active sessions were unaffected.\n\n### **ROOT CAUSE**\n\nThis incident had several contributing factors that combined to produce a failure that the system could not recover from without manual intervention.\n\n**The primary cause** was a recently enabled change that caused our authentication infrastructure to retry requests to a downstream identity service when those requests were slow to respond. This retry behaviour was rolled out to 100% of traffic earlier the same day. Under normal conditions this would be benign, but it meant that any slowness in the downstream service was amplified. Since multiple upstream services were also independently retrying their own failed requests, the amplification compounded further into a retry storm.\n\n**The trigger** was a burst of legitimate user traffic. A pattern of many parallel link preview requests for a single user caused a concentrated load spike on a downstream identity service, pushing its response times above the retry threshold. On its own, this kind of spike had occurred many times before and always recovered. With the retry amplification now in effect, the spike instead created a runaway feedback loop: slow responses caused retries, retries increased load, increased load caused slower responses, preventing recovery.\n\nThe incident was mitigated by manually scaling up the downstream identity service to provide sufficient capacity to absorb the amplified load. Once scaled, the service recovered immediately, bringing authentication error rates to zero within one minute.\n\n**REMEDIAL ACTIONS PLAN & NEXT STEPS**\n\nWe are taking the following actions designed to prevent recurrence and improve our resilience:\n\n1. **Immediate**: The retry-on-timeout change has been disabled.\n2. **Load shedding and self-healing**: We are adding load shedding capabilities to our authentication services so that they can automatically shed excess load and self-recover during traffic spikes, without requiring action before automatic scaling starts.\n3. **Reducing request fan-out**: We are reviewing patterns where a single user action can generate many parallel downstream requests, and will introduce methods where possible to reduce the amplification potential.\n\nWe apologize to customers whose services were interrupted by this incident and we are taking immediate steps to improve the platform\u2019s reliability.\n\nThanks,\n\nAtlassian Customer Support", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-13T10:17:20.784Z", "resolved_inferred": false, "started_at": "2026-04-13T07:29:45.536Z", @@ -207,7 +207,7 @@ "body": "### Summary\n\nOn April 8, 2026, between 04:46 UTC and 12:09 UTC, search functionality was unavailable or degraded across several Atlassian Cloud products, including Jira, Confluence, Jira Service Management, Rovo, Rovo Dev, Loom, Guard Standard, Customer Service Management and Atlassian Administration. \n\nA configuration change increased the resources reserved for a core system component that runs on nodes in our compute platform. On a subset of clusters configured for high\u2011density workloads, the increased reservations exceeded available node capacity interrupting search and related experiences for affected customers.\n\nThe root cause was identified and a rollback was merged at 05:42 UTC with some systems seeing recovery by 07:33 UTC**.** Core search functionality was restored approximately by 08:55 UTC, and full downstream recovery completed by 12:09 UTC.\n\n### **IMPACT**\n\nDuring the impact period, some customers experienced outages or degradation in search across Jira, Confluence, Jira Service Management, Rovo, Rovo Dev, Loom, Guard Standard, Customer Service Management and Atlassian Administration. Other experiences that rely on search such as quick find, navigation, AI assistants, dashboards, were also intermittently affected during this period.\n\nImpacted customers may have been unable to find pages or recordings and experienced degraded performance in finding issues; received empty or delayed search results; or experienced AI assistants and dashboards that could not retrieve relevant context.\n\n**Jira, Jira Service Management and Customer Service Management:** Search and experiences that depend on search like finding issues and agent responses in CSM remained available but with degraded performance in fallback mode. By 12:09 UTC, search indexes and search performance was fully restored from fallback to full capacity across all regions.\n\n**Guard Standard and Atlassian Administration:** Search functionality was unavailable for parts of the incident window. As a result, Domain Claims, usage tracking, and managed accounts were degraded for portions of the window. These services were restored to operational status by 07:33 UTC. Guard Premium was not impacted by this issue.\n\n**Confluence:** Search functionality was unavailable for parts of the incident window. Recovery began at 07:30 UTC as backend search clusters were restored. Full recovery, including search index replay, completed at 11:37 UTC.\n\n**Loom:** Search functionality and some experiences that rely on Confluence Search, such as sharing to spaces\\) was unavailable for portions of the window and fully restored at 11:37 UTC.\n\n**Rovo and Rovo Dev:** Rovo agents remained responsive but experienced degraded functionality due to loss of search capabilities in underlying services. They were unable to reliably return context about work items or pages. Functionality was fully restored at 11:37 UTC.\n\n### **ROOT CAUSE**\n\nAtlassian products rely on OpenSearch clusters to power their search capabilities including issue search, content search, and AI-powered search features. \n\nAn infrastructure configuration change increased resource reservations \\(CPU & Memory\\) for a system component that runs across our compute platform. On a subset of clusters configured for high-density workloads, the increased reservations exceeded available node capacity. This caused search workloads to be evicted and, in some clusters, could not reschedule onto any available nodes impacting search functionality across affected products.\n\nThe change was deployed across multiple production clusters in a short time frame, limiting the opportunity to detect the capacity conflict in a smaller subset of clusters before it reached the wider fleet. Automated scaling systems attempted to recover by provisioning additional capacity but in the worst\u2011affected clusters this led to runaway node scaling and exhaustion of available network resources, prolonging recovery time.\n\n### **REMEDIAL ACTIONS PLAN & NEXT STEPS**\n\nWe understand that service disruptions impact your productivity. In addition to our existing testing and preventative processes, Atlassian is prioritizing the following actions to help reduce the likelihood and impact of similar incidents in the future and to speed up recovery when issues occur:\n\n* **Enforce smaller deployment cohorts and larger soak for critical platform changes for these cluster types** \n Implement smaller deployment cohorts, mandatory soak periods between environments, and automated health gates so that changes are validated on a limited set of clusters before being promoted more broadly.\n* **Strengthen automated pre\u2011deploy validation for resource changes** \n Add validation checks to ensure resource changes for system components are compatible with node capacity and reserved headroom, preventing system workloads from crowding out customer workloads.\n* **Improve post\u2011deploy verification and alerting** \n Enhance monitoring and post\u2011deployment verification to detect patterns such as spikes in pending pods, runaway node scaling, and low pod\u2011IP headroom closely correlated with new configuration being rolled out.\n* **Align autoscaling behavior with capacity and safety limits** \n Align autoscaling capacity calculations with node reservations and introduce safeguards and circuit breakers to prevent runaway scaling and to enforce safe limits on node and pod IP counts.\n* **Enhance recovery automation** \n Improve automation and runbooks so we can safely disable autoscaling, remove empty nodes in bulk, and restore normal operations faster across multiple clusters in parallel.\n\nWe apologize to customers whose services were impacted during this incident; we are taking immediate steps to improve the platform\u2019s performance and availability and to reduce the risk and impact of similar issues in future.\n\nThanks,\n\nAtlassian Customer Support", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-08T11:43:29.727Z", "resolved_inferred": false, "started_at": "2026-04-08T05:41:18.009Z", @@ -220,7 +220,7 @@ "body": "On March 12, 2026, affected Confluence Cloud users may have experienced some service disruption. The issue has now been resolved, and the service is operating normally for all affected customers.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-13T00:26:04.596Z", "resolved_inferred": false, "started_at": "2026-03-12T11:42:39.659Z", @@ -233,7 +233,7 @@ "body": "On 9 March UTC, Automation users in the APAC region may have experienced performance degradation within Jira, Jira Product Discovery, Jira Service Management, Jira Work Management, Confluence. The issue has now been resolved, and the service is operating normally for all affected customers.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-10T00:59:03.202Z", "resolved_inferred": false, "started_at": "2026-03-10T00:15:49.969Z", @@ -246,7 +246,7 @@ "body": "This issue has been resolved and all services are functional.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-20T12:26:08.268Z", "resolved_inferred": false, "started_at": "2026-02-20T04:14:19.453Z", @@ -259,7 +259,7 @@ "body": "On February 19 2026, affected Confluence Cloud users may have experienced some service disruption in AP South, APSE, APSE2, East, and Central regions. The issue has now been resolved, and the service is operating normally for all affected customers.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-19T17:47:01.331Z", "resolved_inferred": false, "started_at": "2026-02-19T15:44:25.955Z", @@ -272,7 +272,7 @@ "body": "We have implemented the fix and the group page in the Admin Hub is now functioning as expected.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-18T11:30:29.538Z", "resolved_inferred": false, "started_at": "2026-02-18T10:57:38.385Z", @@ -285,7 +285,7 @@ "body": "Team has identified the root cause and the issue has now been resolved, and the impacted services are operating normally. Team will continue to monitor the impacted services.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-03T10:50:35.599Z", "resolved_inferred": false, "started_at": "2026-02-03T10:19:54.340Z", @@ -298,7 +298,7 @@ "body": "### Summary\n\nOn Jan 08, 2026 between 14:54 UTC and 16:30 UTC, Atlassian customers using Confluence Cloud product\\(s\\) experienced degraded service with view/edit page experiences. The event was triggered by database overload due to an unexpected large burst of traffic. The database overload was the result of a configuration change, which led to a sudden spike in database connections, which impacted a subset of customers in a single partition in the us-east region. The incident was detected within 1 minute by by automated monitoring systems and mitigated by reducing the number of web server hosts connecting to the database layer, which put Atlassian systems into a known good state. The total time to resolution was about 1 hour and 26 minutes.\n\n### **IMPACT**\n\nThe overall impact was between\u00a0Jan 08, 2026, 14:54 UTC and 16:30 UTC on Confluence Cloud products. The incident caused service disruption to customers in a single partition in the us-east region impacting the ability to view and edit pages. We observed partition-wide database saturation due to an unexpected large burst of traffic. Confluence Cloud components impacted during this window were: Login, View / Edit Page, Publish Page, Add Page, Comment.\n\n### **ROOT CAUSE**\n\nA change was introduced that caused cross-region traffic routing for customers instead of routing to the same region. Some caches processing customer data were stale, which heavily loaded the databases and caused them to restart. As a result, the users of the product above could not login, view or edit pages, and the users received HTTP 500 and 504 errors.\n\n### **REMEDIAL ACTIONS PLAN & NEXT STEPS**\n\nWe know that outages impact your productivity. While we have a number of testing and preventative processes in place, this specific issue wasn\u2019t identified due to a specific set of factors which resulted in this condition.\n\nWe are prioritizing the following improvement actions to help avoid repeating this type of incident:\n\n* Fix the routing issue that resulted in cross-regional traffic\n* Decrease maximum number of connections per database instance, to allow for sufficient memory capacity to handle a surge in connections\n\nFurthermore, we deploy our changes progressively \\(by cloud region\\) to avoid broad impact but in this case, the impact was larger than desired. To minimize the impact of breaking changes to our environments, we will implement additional preventative measures such as enabling automatic vertical scaling when database clusters are running low on memory.\n\nWe apologize to customers whose services were impacted during this incident; we are taking steps to help improve the platform\u2019s performance and availability.\n\nThanks,\n\nAtlassian Customer Support", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-08T19:09:42.448Z", "resolved_inferred": false, "started_at": "2026-01-08T15:27:17.401Z", @@ -311,7 +311,7 @@ "body": "### Summary\n\nOn **December 27, 2025**, between **02:48 UTC and 05:20 UTC**, some Atlassian cloud customers experienced failures in sending and receiving emails and mobile notifications. Core Jira and Confluence functionality remained available.\n\nThe issue was triggered when **TLS certificates used by Atlassian\u2019s monitoring infrastructure expired**, causing parts of our metrics pipeline to stop accepting traffic. Services responsible for email and mobile notifications had a critical path dependency on monitoring path leading to service disruptions.\n\nAll impacted services were fully restored by **05:20 UTC**, around **2.5 hours** after customer impact began.\n\n### IMPACT\n\nDuring the impact window, customers experienced:\n\n* **Outbound product email failures** \\(notifications and other product emails did not send\\).\n* **Identity and account flow failures** where emails were required \\(e.g. sign\u2011ups, password resets, one\u2011time\u2011password / step\u2011up challenges\\).\n* **Jira and Confluence mobile push notifications**\n* **Customer site activations and some admin policy changes** failing and requiring later reprocessing.\n\n### ROOT CAUSE\n\nThe incident was caused by:\n\n1. **Expired TLS certificates** on domains used by our monitoring and metrics infrastructure caused by **misconfigured DNS authorization record** which prevented automatic renewal.\n2. **Tight coupling of services to metrics publishing**, which caused them to fail when monitoring endpoints became unavailable, instead of degrading gracefully.\n\n### REMEDIAL ACTIONS PLAN & NEXT STEPS\n\nWe recognize that outages like this have a direct impact on customers\u2019 ability to receive important notifications, complete account tasks, and operate their sites.\n\nWe are prioritizing the following actions to improve our existing testing, monitoring and certificate management processes:\n\n* **Hardening monitoring and certificate infrastructure**\n\n * We are refining DNS and certificate configuration across our monitoring domains and strengthening proactive checks to detect and address failed renewals and certificate issues well before expiry.\n * We are also improving alerting on our monitoring and metrics pipeline.\n \n* **Decoupling monitoring from critical customer flows** \n We are updating services such as outbound email, identity, mobile push, provisioning, and admin policy changes so they no longer depend on metrics publishing to operate. If monitoring becomes unavailable, these services will continue to run and degrade gracefully by dropping or buffering metrics instead of failing customer operations.\n\nWe apologize to customers impacted during this incident. We are implementing the improvements above to help ensure that similar issues are avoided.\n\nThanks, \nAtlassian Customer Support", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-27T05:20:21.496Z", "resolved_inferred": false, "started_at": "2025-12-27T02:48:17.950Z", @@ -324,7 +324,7 @@ "body": "On December 15th, 2025, Admin Hub, Atlassian Analytics, Confluence Cloud, Ecosystem, Focus, Jira, Jira Product Discovery, Jira Service Management, and Rovo users in the prod-us-east region may have experienced performance degradations and errors on the web page and mobile apps. The issue has now been resolved, and the service is operating normally for all affected customers.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-15T19:01:49.869Z", "resolved_inferred": false, "started_at": "2025-12-15T16:26:38.964Z", @@ -337,7 +337,7 @@ "body": "The rollback required to resolve this issue is now completed, and we have verified across the impacted products that App installation behaviour is now working as expected. We apologize for any inconvenience this may have caused.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-11T04:37:14.163Z", "resolved_inferred": false, "started_at": "2025-12-11T01:08:43.933Z", @@ -350,7 +350,7 @@ "body": "### Summary\n\nOn November 21, 2025, between 13:44 and 15:16 UTC, Trello customers were intermittently unable to view and update data on their boards. Customers also may have experienced issues authenticating with Atlassian products, and creating new GitHub and Slack integrations.\n\nThe event was triggered by a bug encountered in the software running our edge proxy fleet, which proxies customer traffic to Atlassian cloud services. The changes included the migration of our edge proxy fleet to hosts running an ARM CPU architecture, rather than the AMD64 CPU architecture they had previously been running, which impacted US East customers.\n\nThe incident was detected within 1 minute by our automated monitoring systems, and mitigated by a scale up of of fleet size, which put Atlassian systems into a known good state. This was followed by a global migration of edge proxy fleet hosts back to AMD64 CPU architecture the following day.\n\n### **IMPACT**\n\nDuring the impact window, US East customers intermittently could not view or update data in Trello.\n\nThe same underlying issue also impacted our Identity services and integrations with GitHub and Slack, meaning some customers had trouble signing in to Atlassian products or creating new integrations. At the incident\u2019s peak, the incident impacted up to:\n\n* 52% of new Trello network connections.\n* 9% of new GitHub and Slack integrations.\n* 8% of new Identity network connections.\n\n### **ROOT CAUSE**\n\nThe issue was caused by a change to CPU architecture from AMD64 to ARM on our edge proxy fleet. This led to a bug that caused these instances to stall under high load, and refuse up to 52% of new connections. As a result, some customers of the products above could not make new connections to Atlassian services, and customers received CloudFront 504 gateway timeout error responses.\n\n### **REMEDIAL ACTIONS PLAN & NEXT STEPS**\n\nWe know that outages impact your productivity. While we deploy our changes progressively by cloud region to avoid broad impact, on this occasion, our pre-change load testing had not accurately reflected production loads.\n\nAs part of our response to this incident, and to help prevent recurrence, we rolled back all edge proxy fleets from ARM to AMD64 CPU architecture globally.\n\nTo minimise the impact of breaking changes to our environments, we plan to implement additional preventative measures such as:\n\n* Adding improved load tests into edge proxy fleet deployment pipelines to catch load-related bugs before deployment to production.\n* Adding alerts to our edge proxy fleet to catch rises in TCP connect times before customer impact.\n\nWe apologize to customers whose services were impacted during this incident; we are taking steps to help improve the platform\u2019s performance and availability.\n\nThanks,\n\nAtlassian Customer Support", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-21T16:49:34.172Z", "resolved_inferred": false, "started_at": "2025-11-21T14:55:09.138Z", @@ -363,7 +363,7 @@ "body": "Elevated Errors in Confluence Whiteboards and Databases Due to Cloudflare Outage\n\nCloudflare successfully deployed a fix for the issue that was impacting Confluence. We are no longer seeing Confluence system performance degradation and Confluence systems have been fully restored. We will continue monitoring", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-18T16:57:12.921Z", "resolved_inferred": false, "started_at": "2025-11-18T13:32:36.448Z", @@ -376,7 +376,7 @@ "body": "Our team has been able to confirm that customers should no longer be experiencing the error while attempting to edit using Confluence.\nWe apologize for any inconvenience this may have caused.\nThis issue is now resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-18T03:35:12.480Z", "resolved_inferred": false, "started_at": "2025-11-18T02:55:17.386Z", @@ -389,7 +389,7 @@ "body": "On November 3, 2025, some Confluence, Jira Service Management, and Jira Cloud users may have experienced performance degradation and errors in the Global Automation UI page. Automation executions were not impacted by this incident. The issue has now been resolved, and the service is operating normally for all affected customers.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-03T18:08:53.292Z", "resolved_inferred": false, "started_at": "2025-11-03T16:11:55.000Z", @@ -402,7 +402,7 @@ "body": "Incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-30T02:09:45.000Z", "resolved_inferred": false, "started_at": "2025-10-29T06:47:04.679Z", @@ -415,7 +415,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-24T09:18:48.667Z", "resolved_inferred": false, "started_at": "2025-10-24T06:31:38.000Z", @@ -428,7 +428,7 @@ "body": "Our teams have identified and fixed the root cause of the issue that caused delay in executing Automation rules. This was caused due to scaling issues following on from the recent AWS outage.\nThis issue is marked as resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-22T06:47:26.041Z", "resolved_inferred": false, "started_at": "2025-10-22T06:20:54.646Z", @@ -441,7 +441,7 @@ "body": "### Postmortem publish date: Nov 19th, 2025\n\n### Summary\n\nAll dates and times below are in UTC unless stated otherwise.\n\nCustomers utilizing Atlassian products experienced elevated error rates and degraded performance between Oct 20, 2025 06:48 and Oct 21, 2025 04:05. The service disruptions were triggered due to an [AWS DynamoDB outage](https://aws.amazon.com/message/101925/#:~:text=1%3A50%20PM.-,DynamoDB,-Between%2011%3A48) and further affected by subsequent failures in [AWS EC2](https://aws.amazon.com/message/101925/#:~:text=service%20disruption%20event.-,Amazon%20EC2,-Between%2011%3A48) and [AWS Network Load Balancer](https://aws.amazon.com/message/101925/#:~:text=service%20disruption%20event.-,Amazon%20EC2,-Between%2011%3A48) within the us-east-1 region.\n\nThe incident started at Oct 20, 2025 06:48 and was detected within six minutes by our automated monitoring systems. Our teams worked to restore all core services by Oct 21, 2025 04:05. Final cleanup of backlogged processes and minor issues was completed on Oct 22, 2025.\n\nWe recognize the critical role our products play in your daily operations, and we offer our sincere apologies for any impact this incident had on your teams. We are taking immediate steps to enhance the reliability and performance of our services, so that you continue to receive the standard of service you have come to trust.\n\n### IMPACT\n\nBefore examining product-level impacts, it's helpful to understand Atlassian's service topology and internal dependencies.\n\nProducts such as Jira and Confluence are deployed across multiple AWS regions. The data for each tenant is stored and processed exclusively within its designated host region. This design is intentional and represents the desired operational state, as it limits the impact of any regional outage strictly to tenants in-region, in this case us-east-1.\n\nWhile in-scope application data is pinned to the region selected by the customer, there are times when systems need to call other internal services that may be based in a different region. If a problem occurs in the main region where these services operate, systems are designed to automatically fail over to a backup region, usually within three minutes.\n\nHowever, if unexpected issues arise during this failover, it can take longer to restore services. In rare cases, this could affect customers in more than one region. It\u2019s important to note that all in-scope application data for supported products is pinned according to a customer\u2019s chosen region.\n\n**Jira**\n\nBetween Oct 20, 2025 06:48 and Oct 20, 2025 20:00, customers with tenants hosted in the us-east-1 region experienced increased error rates when accessing core entities such as Issues, Boards, and Backlogs. This disruption was caused by AWS's inability to allocate AWS EC2 instances and elevated errors in AWS Network Load Balancer \\(NLB\\). During this window, users may also have observed intermittent timeouts, slow page loads, and failures when performing operations like creating or updating issues, loading board views, and executing workflow transitions.\n\nBetween Oct 20, 2025 08:36 and Oct 20, 2025 09:23, customers across all regions experienced elevated failure rates when attempting to load Jira pages. This disruption was caused by the regional frontend service entering an unhealthy state during this specific time interval.\n\nNormally, the frontend service connects to the primary AWS DynamoDB instance located in the us-east-1 to retrieve the most recent configuration data necessary for proper operation. Additionally, the service is designed with a fallback mechanism that references static configuration data in the event that the primary database becomes inaccessible. Unfortunately, a latent bug existed in the local fallback path. When the frontend service nodes restarted, they were unable to load critical operational configuration data from primary or fallback sources, leading to the observed failures experienced by customers.\n\nBetween Oct 20, 2025 06:48 and Oct 21, 2025 06:30, customers experienced significant delays and missing Jira in-app notifications across all regions. The notification ingestion service, which is hosted exclusively in us-east-1, exhibited an increased failure rate when processing notification messages due to AWS EC2 and NLB issues. This issue resulted in notifications being delayed - and in some cases, not delivered at all - to users worldwide.\n\n**Jira Service Management \\(JSM\\)**\n\nJSM was impacted similarly to Jira above, with the same timeframes and for the same reasons.\n\nBetween Oct 20, 2025 08:36 and Oct 20, 2025 09:23, customers across all regions experienced significantly elevated failure rates when attempting to load JSM pages. This affected all JSM experiences including the Help Centre, Portal, Queues, Work Items, Operations, and Alerts.\n\n**Confluence**\n\nBetween Oct 20, 2025 06:48 and Oct 21, 2025 02:45, customers using Confluence in the us-east-1 region experienced elevated failure rates when performing common operations such as editing pages or adding comments. The primary cause of this service degradation was the system's inability to auto-scale due to AWS EC2 issues to manage peak traffic load effectively.\n\nThough the AWS outage ended at Oct 20, 21:09, a subset of customers continued to experience failures as some Confluence web server nodes across multiple clusters remained in an unhealthy state. This was ultimately mitigated by recycling the affected nodes.\n\nTo protect our systems while AWS recovered, we made a deliberate decision to enable node termination protection. This action successfully preserved our server capacity but, as a trade-off, it extended the time required for a full recovery once AWS services were restored.\n\n**Automation**\n\nBetween Oct 20, 2025 06:55 and Oct 20, 2025 23:59, automation customers whose rules are processed in us-east-1 experienced delays of up to 23 hours in rule execution.\n\nDuring this window, some events triggering rule executions were processed out of order because they arrived later during backlog processing. This caused potential inconsistencies in workflow executions, as rules were run in the order events were received, not when the action causing the event occurred. Additionally, some rule actions failed because they depend on first-party and third-party systems, which were also affected by the AWS outage. Customers can see most of these failures in their audit logs; however, a few updates were not logged due to the nature of the outage.\n\nBy Oct 21, 2025 5:30, the backlog of rule runs in us-east-1 was cleared. Although most of these delayed rules were successfully handled, there were some additional replays of events to ensure completeness. Our investigation confirmed that a few events may never have triggered their associated rules due to the outage.\n\nBetween Oct 20, 2025 06:55 and Oct 20, 2025 11:20, all non-us-east-1 regional automation services experienced delays of up to 4 hours in rule execution. This was caused by an upstream service that was unable to deliver events as expected. The delivery service encountered a failure due to a cross-region dependency call to a service hosted in the us-east-1 region. Because of this dependency issue, the delivery service was unable to successfully deliver events throughout this time frame, resulting in customer-defined rules not being executed in a timely manner.\n\n**Bitbucket and Pipelines**\n\nBetween Oct 20, 2025 06:48 and Oct 20, 2025 09:33, Bitbucket experienced intermittent unavailability across core services. During this period, users faced increased error rates and latency when signing in, navigating repositories, and performing essential actions such as creating, updating, or approving pull requests. The primary cause was an AWS DynamoDB outage that impacted downstream services.\n\nBetween Oct 20, 2025 06:48 and Oct 20, 2025 22:46, numerous Bitbucket Pipeline steps failed to start, stalled mid-execution, or experienced significant queueing delays. Impact varied, with partial recoveries followed by degradation as downstream components re-synchronized. The primary cause was an AWS DynamoDB outage, compounded by instability in AWS EC2 instance availability and AWS Network Load Balancers.\n\nFurthermore, Bitbucket Pipelines continued to experience a low but persistent rate of step timeouts and scheduling errors due to AWS bare-metal capacity shortages in select availability zones. Atlassian coordinated with AWS to provision additional bare-metal hosts and addressed a significant backlog of pending pods, successfully restoring services by 01:30 on Oct 21, 2025.\n\n**Trello**\n\nBetween Oct 20, 2025 06:48 and Oct 20, 2025 15:25, users of Trello experienced widespread service degradation and intermittent failures due to upstream AWS issues affecting multiple components, including AWS DynamoDB and subsequent AWS EC2 capacity constraints. During this period, customers reported elevated error rates when loading boards, opening cards, adding comments or attachments.\n\n**Login**\n\nBetween Oct 20, 2025 06:48 and Oct 20, 2025 09:30, a small subset of users experienced failures when attempting to initiate new login sessions using SAML tokens. This resulted in an inability for those users to access Atlassian products during that time period. However, users who already had valid active sessions were not affected by this issue and continued to have uninterrupted access.\n\nThe issue impacted all regions globally because regional identity services relied on a write replica located in the us-east-1 region to synchronize profile data. When the primary region became unavailable, the failover to a secondary database in another region failed, which delayed recovery. This failover defect has since been addressed.\n\n**Statuspage**\n\nBetween Oct 20, 2025 06:48 and Oct 20, 2025 09:30, Statuspage customers who were not already logged in to the management portal were unable to log in to create or update incident statuses. This impact was restricted only to users who were not already logged in at the time. The root cause was the same as described in the Login section above, and it was resolved by the same remediation steps.\n\n### REMEDIAL ACTION PLAN & NEXT STEPS\n\nWe have completed the following critical actions designed to help prevent cross-region impact from similar issues:\n\n* Resolved the code defect in the fallback option to ensure that Jira Frontend Services in other regions remain unaffected during a region-wide outage.\n* Fixed the issue that prevented timely failover of the identity service which impacted new login sessions.\n* Resolved the code defect so that delivery services in unaffected regions remain operational during region-wide outages.\n\nAdditionally, we are prioritizing the following improvement actions:\n\n* Implement mitigation strategies to strengthen resilience against region-wide outages in the notification ingestion service.\n\nAlthough disruptions to our cloud services are sometimes unavoidable during outages of the underlying cloud provider, we continuously evaluate and improve test coverage to strengthen resilience of our cloud services against these issues.\n\nWe recognize the critical importance of our products to your daily operations and overall productivity, and we extend our sincere apologies for any disruptions this incident may have caused your teams. If you were impacted and require additional details for internal post-incident reviews, please reach out to your Atlassian support representative with affected timeframes and tenant identifiers so we can correlate logs and provide guidance.\n\nThanks,\n\nAtlassian Customer Support", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-21T05:24:25.798Z", "resolved_inferred": false, "started_at": "2025-10-20T07:56:11.696Z", @@ -454,7 +454,7 @@ "body": "Between 14:00 UTC to 16:00 UTC, we experienced automation rule functionality degradation for Confluence, Jira Work Management, Jira Service Management, and Jira. \n\nImpact\n\nSome customers using Jira, Confluence, and Jira Service Management were not able to create or update Automation rules, and some Automation rules which triggered webhooks might have been throttled and require re-running. Approximately 50 percent of Automation API calls were affected in the us-east-1 region with customers receiving 429 status codes.\n\nCurrent Status\n\nThe incident has been mitigated by increasing the API Gateway rate limit service quota and disabling the internal service that was causing high traffic volume. \n\nNext Steps\n\nWe are conducting a root cause analysis of the internal service. A post incident review will be conducted.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-15T16:16:07.105Z", "resolved_inferred": false, "started_at": "2025-10-15T13:43:56.097Z", @@ -467,7 +467,7 @@ "body": "On September 29-30 2025, for about 24 hours, Confluence Cloud experienced an incident due to the unintended deprecation of ACJS methods (https://developer.atlassian.com/cloud/confluence/about-the-connect-javascript-api/#connect-javascript-api) linked to retired V1 APIs (https://developer.atlassian.com/cloud/confluence/rest/v1/), resulting in 410 errors affecting partners reliant on these APIs. \n\nThis issue is resolved, we will be working on a longer-term solution to prevent a similar incident from occurring again.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-30T17:15:49.000Z", "resolved_inferred": false, "started_at": "2025-09-30T17:15:49.000Z", @@ -480,7 +480,7 @@ "body": "### **SUMMARY**\n\nOn September 22, 2025, between 04:38 and 04:48 UTC, Atlassian customers experienced connection errors preventing access to their [atlassian.net](http://atlassian.net/) sites. Some customers observed intermittent errors as services gradually recovered until 06:17 UTC.\n\nThe event was triggered by a faulty configuration change to our Content Delivery Network \\(CDN\\). The change included an invalid hostname which prevented customers from successfully connecting to [atlassian.net](http://atlassian.net/) domains.\n\nThe incident was detected within 1 minute by our monitoring systems and mitigated by rolling back the change, which put Atlassian systems into a known good state. The acute impact was resolved in 10 minutes and all lingering errors resolved in 1 hour 38 minutes.\n\n### **IMPACT**\n\nThe acute impact occurred on\u00a0September 22, 2025, between 04:38 UTC and 04:48 UTC to Confluence, Compass and Jira, including Jira Service Management. The incident caused service disruption to customers when they attempted to load those products in their browser or interact with APIs. Between 04:48 UTC and 06:17 UTC some customers continued to observe intermittent errors as services gradually recovered.\n\n### **ROOT CAUSE**\n\nThe issue was caused by a change to the hostname configuration of our Content Delivery Network \\(CDN\\). As a result, the products mentioned could not receive connections, and the users received TLS handshake errors, followed by HTTP 503 and 403 errors.\n\nMore specifically a new CDN configuration contained a resource name which conflicted with the existing customer-serving CDN resource, and was able to be deployed, overwriting it. The root cause of the incident was the failure in the detection of the bug by our pre-deployment validations and tests.\n\n### **REMEDIAL ACTIONS PLAN & NEXT STEPS**\n\nWe know that you rely on our products for your daily operations and productivity, and we sincerely apologize for any impact this disruption has had on you, your team or your organisation.\n\nWe are prioritizing the following improvement actions to help avoid repeating this type of incident:\n\n* Improved pre-deployment change controls and testing.\n* Improved validation of target configurations before deployment to ensure customer-serving CDN resources cannot their hostnames changed.\n* Sharding of our CDN configuration to enable progressive changes.\n\nWe sincerely appreciate your understanding and patience as we improve our processes to provide a better customer experience.\n\nThank you,\n\nAtlassian Customer Support", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-22T07:17:23.603Z", "resolved_inferred": false, "started_at": "2025-09-22T05:09:32.247Z", @@ -493,7 +493,7 @@ "body": "An update has been released by Microsoft to resolve this issue for users of the Edge browser. To verify that you are running the required version of Edge, you can navigate to edge://components/ in the address bar, click the 'Check for update' button for the 'Trust Protections List', ensuring that you are on version 1.0.0.31 or higher to ensure you are running the version that contains the fixed release.\nAll Edge browsers should otherwise receive this update within 10 hours without user intervention.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-15T06:40:39.763Z", "resolved_inferred": false, "started_at": "2025-09-09T10:23:55.779Z", @@ -506,7 +506,7 @@ "body": "Between 2025-08-03T21:34 and 2025-08-05T03:43 UTC some users would not have received the emails for product invitations.\nThe change that caused these emails to stop being sent has been rolled back.\nNew invitation emails should now be sent correctly for all products.\nFor users that were impacted by this issue, re-submitting their invitation will also re-send the email to them if required.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-05T04:19:02.807Z", "resolved_inferred": false, "started_at": "2025-08-04T23:44:47.033Z", diff --git a/api/v/confluent.json b/api/v/confluent.json index 3cbf60a85ff5ed48500915f75145f74ec1fe1b5e..417cebf598fd15252767aea891fd49c207c98f4c 100644 --- a/api/v/confluent.json +++ b/api/v/confluent.json @@ -3,7 +3,7 @@ "slug": "confluent", "platform": "statuspage", "status_url": "https://status.confluent.cloud", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "The GCP issue affecting the us-central1 region has been mitigated and all Confluent Cloud services in the region have returned to normal operation. Provisioning capability, error rates and latency have recovered to expected levels.\n\nCustomers should no longer experience impact. If you continue to see any issues, please contact Confluent Support.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-09-01T17:14:55.269Z", "resolved_inferred": false, "started_at": "2026-09-01T16:27:06.981Z", @@ -25,7 +25,7 @@ "body": "Confluent services in the Azure Southeast Asia region are now healthy and operating normally.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-25T07:29:25.385Z", "resolved_inferred": false, "started_at": "2026-08-25T04:17:43.970Z", @@ -38,7 +38,7 @@ "body": "Between 21:15 \u2013 22:30 UTC and 00:05 \u2013 01:15 UTC on Aug 23\u201324, 2026, Confluent Cloud logging service was degraded. Customers may notice missing Connect and Flink logs in the Confluent Cloud UI, the Confluent CLI, and configured logging integration destinations during these windows. Other log types and the Connect / Flink workloads themselves were unaffected. The issue has been mitigated.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-23T21:00:00.000Z", "resolved_inferred": false, "started_at": "2026-08-23T21:00:00.000Z", @@ -51,7 +51,7 @@ "body": "The GCP issues in us-west1 region have been mitigated. Confluent services are no longer seeing any impact based on our monitoring.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-20T20:18:07.395Z", "resolved_inferred": false, "started_at": "2026-08-20T17:10:10.282Z", @@ -64,7 +64,7 @@ "body": "All the statements should be running now.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-18T00:59:22.002Z", "resolved_inferred": false, "started_at": "2026-07-17T22:01:05.506Z", @@ -77,7 +77,7 @@ "body": "The issue impacting the AWS eu-central-1 region has now been resolved. All clusters are fully operational and healthy.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-16T13:14:46.342Z", "resolved_inferred": false, "started_at": "2026-07-15T23:33:34.173Z", @@ -90,7 +90,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-13T16:04:36.556Z", "resolved_inferred": false, "started_at": "2026-07-13T14:25:44.138Z", @@ -103,7 +103,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-29T20:36:42.494Z", "resolved_inferred": false, "started_at": "2026-06-29T17:44:47.262Z", @@ -116,7 +116,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-29T12:50:24.523Z", "resolved_inferred": false, "started_at": "2026-06-29T11:40:42.000Z", @@ -129,7 +129,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-25T17:53:53.152Z", "resolved_inferred": false, "started_at": "2026-06-25T15:59:11.533Z", @@ -142,7 +142,7 @@ "body": "On June 23rd, between 7:00 to 7:16 UTC the Confluent Cloud Metrics API was unavailable. Confluent has identified the issue and restored functionality.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-23T07:00:00.000Z", "resolved_inferred": false, "started_at": "2026-06-23T04:30:00.000Z", @@ -155,7 +155,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-21T09:19:54.758Z", "resolved_inferred": false, "started_at": "2026-06-21T07:14:59.000Z", @@ -168,7 +168,7 @@ "body": "No further issues have been observed. The incident is now resolved as of 2026-06-16 17:58 UTC.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-16T17:58:57.410Z", "resolved_inferred": false, "started_at": "2026-06-16T16:02:07.000Z", @@ -181,7 +181,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-12T11:55:12.313Z", "resolved_inferred": false, "started_at": "2026-06-12T07:42:15.393Z", @@ -194,7 +194,7 @@ "body": "The Multi Service degradation on Azure has been mitigated. Confluent Cloud is operating normally.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-29T21:47:52.470Z", "resolved_inferred": false, "started_at": "2026-05-29T05:57:51.720Z", @@ -207,7 +207,7 @@ "body": "The incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-22T00:22:54.136Z", "resolved_inferred": false, "started_at": "2026-05-22T00:21:51.280Z", @@ -220,7 +220,7 @@ "body": "The incident has been resolved and us-east-1 (use1-az4) is fully operational.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-04T16:47:47.360Z", "resolved_inferred": false, "started_at": "2026-05-08T01:14:00.584Z", @@ -233,7 +233,7 @@ "body": "The maintenance is complete.", "first_seen": "2026-09-04T07:06:16Z", "impact": "maintenance", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-07T03:08:32.222Z", "resolved_inferred": false, "started_at": "2026-05-06T22:12:13.716Z", @@ -246,7 +246,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-25T00:14:31.028Z", "resolved_inferred": false, "started_at": "2026-04-24T17:18:15.361Z", @@ -259,7 +259,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-21T09:49:19.357Z", "resolved_inferred": false, "started_at": "2026-04-21T09:34:28.929Z", @@ -272,7 +272,7 @@ "body": "Resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-16T03:21:48.867Z", "resolved_inferred": false, "started_at": "2026-03-20T13:58:18.753Z", @@ -285,7 +285,7 @@ "body": "Confluent Cloud Metrics API are now fully functional. The incident has been resolved and systems are functioning as normal.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-05T07:22:20.412Z", "resolved_inferred": false, "started_at": "2026-03-05T04:40:11.173Z", @@ -298,7 +298,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-20T00:55:03.025Z", "resolved_inferred": false, "started_at": "2026-03-02T07:19:27.054Z", @@ -311,7 +311,7 @@ "body": "This incident has been resolved. All Confluent Cloud services are now healthy in me-central-1 region.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-01T22:05:48.229Z", "resolved_inferred": false, "started_at": "2026-03-01T18:08:42.883Z", @@ -324,7 +324,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-27T01:57:43.586Z", "resolved_inferred": false, "started_at": "2026-02-26T19:56:30.188Z", @@ -337,7 +337,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-26T22:24:15.169Z", "resolved_inferred": false, "started_at": "2026-02-26T13:59:54.118Z", @@ -350,7 +350,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-27T18:16:17.173Z", "resolved_inferred": false, "started_at": "2026-02-25T05:01:53.981Z", @@ -363,7 +363,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-25T01:07:09.180Z", "resolved_inferred": false, "started_at": "2026-02-24T21:15:06.000Z", @@ -376,7 +376,7 @@ "body": "The issue was resolved successfully. All systems working as expected.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-24T09:58:28.809Z", "resolved_inferred": false, "started_at": "2026-02-23T22:12:37.346Z", @@ -389,7 +389,7 @@ "body": "The incident has been resolved. New cluster creation in the Azure westus3, southcentralus, and eastus2 regions have been fixed.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-12T02:45:00.524Z", "resolved_inferred": false, "started_at": "2026-02-11T22:14:17.258Z", @@ -402,7 +402,7 @@ "body": "The issue has been resolved and services are operating normally. The root cause was a networking configuration change in the us-west-2 region that caused client connection issues starting at approximately 21:33 UTC, resulting in intermittent service disruption across several Confluent Cloud services, including Kafka, Flink, Metrics API, Logging, Provisioning, and Authentication. The change was reverted, and as of 00:20 UTC, services have been fully restored.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-04T00:48:09.000Z", "resolved_inferred": false, "started_at": "2026-02-03T21:33:23.000Z", @@ -415,7 +415,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-08T16:25:46.630Z", "resolved_inferred": false, "started_at": "2026-01-08T12:30:20.366Z", @@ -428,7 +428,7 @@ "body": "Metrics API /export endpoint was emitting 400 errors from 06:02 UTC to 10:20 UTC", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-16T06:00:00.000Z", "resolved_inferred": false, "started_at": "2025-12-16T06:00:00.000Z", @@ -441,7 +441,7 @@ "body": "This issue has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-10T04:48:01.259Z", "resolved_inferred": false, "started_at": "2025-12-08T17:48:34.000Z", @@ -454,7 +454,7 @@ "body": "No further issues have been observed. The incident is now resolved as of 2025-1203 02:03 UTC.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-03T02:04:05.072Z", "resolved_inferred": false, "started_at": "2025-12-02T21:37:14.799Z", @@ -467,7 +467,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-28T18:33:51.826Z", "resolved_inferred": false, "started_at": "2025-11-28T13:25:32.469Z", @@ -480,7 +480,7 @@ "body": "Some of the Freight customers in AWS us-east-1 could have experienced latency spikes intermittently", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-21T01:00:00.000Z", "resolved_inferred": false, "started_at": "2025-11-20T17:30:00.000Z", @@ -493,7 +493,7 @@ "body": "This issue has been resolved, and there should be no further log loss. All subsequent connector log events are now accessible.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-17T21:07:30.570Z", "resolved_inferred": false, "started_at": "2025-11-17T14:28:11.784Z", @@ -506,7 +506,7 @@ "body": "All affected clusters are now fully operational.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-06T21:39:53.111Z", "resolved_inferred": false, "started_at": "2025-11-05T18:19:57.000Z", @@ -519,7 +519,7 @@ "body": "Some customers in AWS us-east-1 may have experienced unavailability of produce requests for Enterprise SKU clusters from 3:40 to 4:05 PM UTC.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-29T17:00:00.000Z", "resolved_inferred": false, "started_at": "2025-10-29T17:00:00.000Z", @@ -532,7 +532,7 @@ "body": "Microsoft reports Azure status as fully operational. The incident is now resolved as of 0:40 UTC on Oct 29th, 2025.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-30T00:42:28.684Z", "resolved_inferred": false, "started_at": "2025-10-29T16:55:23.000Z", @@ -545,7 +545,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-27T18:13:38.503Z", "resolved_inferred": false, "started_at": "2025-10-27T17:48:27.100Z", @@ -558,7 +558,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-25T05:14:23.432Z", "resolved_inferred": false, "started_at": "2025-10-22T22:38:32.397Z", @@ -571,7 +571,7 @@ "body": "All impacted Flink compute pools have been fixed and degraded statements have recovered.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-22T22:45:42.936Z", "resolved_inferred": false, "started_at": "2025-10-22T16:21:38.191Z", @@ -584,7 +584,7 @@ "body": "The incident has been fully resolved, and all services are operating as expected.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-21T12:05:03.147Z", "resolved_inferred": false, "started_at": "2025-10-20T09:53:21.000Z", @@ -597,7 +597,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-18T05:21:35.689Z", "resolved_inferred": false, "started_at": "2025-10-17T22:44:48.041Z", @@ -610,7 +610,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-08T07:59:33.852Z", "resolved_inferred": false, "started_at": "2025-10-06T19:24:42.741Z", @@ -623,7 +623,7 @@ "body": "This incident has been fully resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-04T15:46:41.505Z", "resolved_inferred": false, "started_at": "2025-10-03T04:43:49.597Z", @@ -636,7 +636,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-01T17:29:49.075Z", "resolved_inferred": false, "started_at": "2025-09-30T16:58:28.442Z", @@ -649,7 +649,7 @@ "body": "All services in the Azure Switzerland North region have now been fully recovered.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-27T23:24:34.496Z", "resolved_inferred": false, "started_at": "2025-09-27T01:00:34.000Z", diff --git a/api/v/connectwise.json b/api/v/connectwise.json index 50b4f92310d6c9b42561f9fc532f37ec9d56a939..140be9ec05be80ae0acd19b4e94e5eb4fa3852cc 100644 --- a/api/v/connectwise.json +++ b/api/v/connectwise.json @@ -3,7 +3,7 @@ "slug": "connectwise", "platform": "status.io", "status_url": "https://status.connectwise.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "degraded", "history_backfilled": false, "first_watched": "2026-09-04T07:06:16Z", @@ -11,7 +11,7 @@ { "body": "We are aware of an issue that is impacting backups for NAS devices. We understand the importance of reliable backup protection and are actively investigating the cause. We will share updates as soon as additional information is available.", "first_seen": "2026-09-04T07:06:16Z", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "started_at": "2026-09-03T18:45:28.250Z", "state": "investigating", "title": "NAS Backups", @@ -21,7 +21,7 @@ { "body": "The backend performance issue affecting support case submissions in the Axcient portal has been fully resolved. Partners can now submit new product support cases through the portal without interruption. Support response times have returned to normal, and all services are operating as expected.", "first_seen": "2026-09-04T07:06:16Z", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "started_at": "2026-03-03T08:54:00.000Z", "state": "investigating", "title": "Support Case Submissions Currently Unavailable in Axcient Portal", diff --git a/api/v/constant-contact.json b/api/v/constant-contact.json index 18cc63fc4888950b2d0277ecf7a7ad9392336647..a66063dfb4d514877aeb629becb1d91d428b5641 100644 --- a/api/v/constant-contact.json +++ b/api/v/constant-contact.json @@ -3,7 +3,7 @@ "slug": "constant-contact", "platform": "statuspage", "status_url": "https://status.constantcontact.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "The login issues and a navigation slowness have been resolved, and all systems are operating normally. Thank you for your patience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-09-02T15:25:33.000-04:00", "resolved_inferred": false, "started_at": "2026-09-02T13:40:17.000-04:00", @@ -25,7 +25,7 @@ "body": "These delays have been resolved and both Segments and APB paths are working as expected.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-25T16:30:04.000-04:00", "resolved_inferred": false, "started_at": "2026-07-23T19:50:20.000-04:00", @@ -38,7 +38,7 @@ "body": "The login issues have been resolved, and all systems are operating normally. Thank you for your patience while we worked through this!", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-17T22:06:23.000-04:00", "resolved_inferred": false, "started_at": "2026-07-17T21:17:34.000-04:00", @@ -51,7 +51,7 @@ "body": "The login issues have been resolved, and all systems are operating normally. Thank you for your patience while we worked through this!", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-15T07:09:27.000-04:00", "resolved_inferred": false, "started_at": "2026-07-15T06:27:13.000-04:00", @@ -64,7 +64,7 @@ "body": "This issue has been resolved, and all scheduled email has been sent.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-07T16:32:48.134-04:00", "resolved_inferred": false, "started_at": "2026-07-07T11:23:28.031-04:00", @@ -77,7 +77,7 @@ "body": "This issue has been resolved and editor functionality has been restored to campaigns", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-01T17:14:23.952-04:00", "resolved_inferred": false, "started_at": "2026-07-01T16:30:49.584-04:00", @@ -90,7 +90,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-23T15:25:12.763-04:00", "resolved_inferred": false, "started_at": "2026-06-23T14:37:22.947-04:00", @@ -103,7 +103,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-21T17:19:28.223-04:00", "resolved_inferred": false, "started_at": "2026-04-21T16:49:15.461-04:00", @@ -116,7 +116,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-20T10:46:45.717-04:00", "resolved_inferred": false, "started_at": "2026-04-20T09:07:38.477-04:00", @@ -129,7 +129,7 @@ "body": "The issue has been resolved", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-06T14:52:33.000-04:00", "resolved_inferred": false, "started_at": "2026-04-06T14:52:33.000-04:00", @@ -142,7 +142,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-26T15:57:32.911-04:00", "resolved_inferred": false, "started_at": "2026-03-26T12:18:58.946-04:00", @@ -155,7 +155,7 @@ "body": "This incident has been resolved. Customers experienced unexpected behavior specifically impacting email tracking functionality. Please note that email delivery was not impacted; your messages were successfully sent and received as intended. Our team identified the tracking issue and immediately restored the system to its full, stable state. All tracking data is now flowing as expected.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-12T08:37:20.000-04:00", "resolved_inferred": false, "started_at": "2026-03-11T21:00:20.000-04:00", @@ -168,7 +168,7 @@ "body": "This incident has been resolved and all delayed mail has been sent.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-25T15:22:43.032-05:00", "resolved_inferred": false, "started_at": "2026-02-25T14:51:39.041-05:00", @@ -181,7 +181,7 @@ "body": "Campaigns are now sending normally.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-06T14:46:26.000-05:00", "resolved_inferred": false, "started_at": "2026-02-06T13:39:23.000-05:00", @@ -194,7 +194,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-23T03:30:49.000-05:00", "resolved_inferred": false, "started_at": "2026-01-22T14:30:37.000-05:00", @@ -207,7 +207,7 @@ "body": "Test mail delivery has resumed and there should be no further delays.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-19T17:05:32.448-05:00", "resolved_inferred": false, "started_at": "2025-11-19T13:49:24.000-05:00", @@ -220,7 +220,7 @@ "body": "The incident has been resolved. Teams will continue to monitor our system.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-18T09:39:38.317-05:00", "resolved_inferred": false, "started_at": "2025-11-18T07:35:38.763-05:00", @@ -233,7 +233,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-12T16:17:44.000-05:00", "resolved_inferred": false, "started_at": "2025-11-12T14:45:33.000-05:00", @@ -246,7 +246,7 @@ "body": "This incident has been resolved", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-27T16:18:46.881-04:00", "resolved_inferred": false, "started_at": "2025-10-27T16:05:28.711-04:00", @@ -259,7 +259,7 @@ "body": "This incident has been resolved and we will continue to monitor the issue.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-20T12:48:43.247-04:00", "resolved_inferred": false, "started_at": "2025-10-20T11:43:50.232-04:00", @@ -272,7 +272,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-16T16:04:16.270-04:00", "resolved_inferred": false, "started_at": "2025-10-16T14:15:32.441-04:00", @@ -285,7 +285,7 @@ "body": "The issues accessing campaign reporting have been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-02T11:00:36.000-04:00", "resolved_inferred": false, "started_at": "2025-10-02T09:30:12.000-04:00", @@ -298,7 +298,7 @@ "body": "The issue has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-01T08:36:35.000-04:00", "resolved_inferred": false, "started_at": "2025-10-01T08:14:57.531-04:00", @@ -311,7 +311,7 @@ "body": "Issues loading Social pages and Landing pages has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-24T14:45:05.000-04:00", "resolved_inferred": false, "started_at": "2025-09-24T13:15:00.000-04:00", @@ -324,7 +324,7 @@ "body": "We have resolved the issue with billing, and payments are processing normally.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-04T21:13:33.000-04:00", "resolved_inferred": false, "started_at": "2025-08-04T18:06:43.000-04:00", diff --git a/api/v/contentful.json b/api/v/contentful.json index 5920f6abfc28cfe6afcd5baebeeb189d3d057ca3..01d9fe8488fb3a68d43a4f008bb90bfc49922c20 100644 --- a/api/v/contentful.json +++ b/api/v/contentful.json @@ -3,7 +3,7 @@ "slug": "contentful", "platform": "statuspage", "status_url": "https://www.contentfulstatus.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "We identified the source of the issue which caused some items which were purged to get stuck in cache. We have complete a full cache purge in the EU and the issue is now resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-09-03T13:25:55.530Z", "resolved_inferred": false, "started_at": "2026-09-03T07:45:28.073Z", @@ -25,7 +25,7 @@ "body": "The issue is resolved and audit logs are delivered as expected again.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-28T05:50:16.714Z", "resolved_inferred": false, "started_at": "2026-08-27T16:26:08.695Z", @@ -38,7 +38,7 @@ "body": "We have implemented a fix and the issue has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-24T21:37:36.316Z", "resolved_inferred": false, "started_at": "2026-08-24T12:12:51.226Z", @@ -51,7 +51,7 @@ "body": "The incident is resolved", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-17T11:56:54.743Z", "resolved_inferred": false, "started_at": "2026-08-17T09:05:21.924Z", @@ -64,7 +64,7 @@ "body": "The issue has been addressed.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-13T11:38:57.320Z", "resolved_inferred": false, "started_at": "2026-08-13T09:34:46.075Z", @@ -77,7 +77,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-10T14:14:44.088Z", "resolved_inferred": false, "started_at": "2026-08-10T11:08:17.249Z", @@ -90,7 +90,7 @@ "body": "We have taken action and error rates have returned to normal.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-03T17:26:30.372Z", "resolved_inferred": false, "started_at": "2026-07-03T09:32:51.827Z", @@ -103,7 +103,7 @@ "body": "This issue has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-02T14:27:40.671Z", "resolved_inferred": false, "started_at": "2026-07-02T07:53:37.675Z", @@ -116,7 +116,7 @@ "body": "This issue has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-30T12:21:45.746Z", "resolved_inferred": false, "started_at": "2026-06-30T10:53:29.142Z", @@ -129,7 +129,7 @@ "body": "Due to an issue identified with an external provider a small portion of customer traffic may have experienced periodic spells of higher latency or timeouts / errors when making requests to the Contentful Management and Contentful Preview APIs in the past few days (26th to 29th June) - the issue has been resolved", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-28T22:00:00.000Z", "resolved_inferred": false, "started_at": "2026-06-28T22:00:00.000Z", @@ -142,7 +142,7 @@ "body": "This issue is now resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-18T20:58:19.497Z", "resolved_inferred": false, "started_at": "2026-06-18T16:11:55.534Z", @@ -155,7 +155,7 @@ "body": "The asset picker in the Cloudinary Marketplace app was not working. The issue is resolved. Customers may need to do a hard refresh to clear their browser cache.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-18T08:24:08.706Z", "resolved_inferred": false, "started_at": "2026-06-18T07:57:30.878Z", @@ -168,7 +168,7 @@ "body": "We have resolved the issue.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-12T20:40:23.190Z", "resolved_inferred": false, "started_at": "2026-06-12T07:53:08.107Z", @@ -181,7 +181,7 @@ "body": "We have resolved the issue.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-11T21:00:47.747Z", "resolved_inferred": false, "started_at": "2026-06-11T12:29:17.146Z", @@ -194,7 +194,7 @@ "body": "We have resolved the underlying issue, the Optimization Hub is available again.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-09T14:18:13.203Z", "resolved_inferred": false, "started_at": "2026-06-09T13:57:29.248Z", @@ -207,7 +207,7 @@ "body": "We think the impact from the issue is over, however, uploads using 3rd cloud providers (Google Drive, Instagram, Box, Dropbox etc) are temporarily disabled.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-02T14:51:15.235Z", "resolved_inferred": false, "started_at": "2026-06-02T13:02:17.433Z", @@ -220,7 +220,7 @@ "body": "The issue has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-26T17:17:39.621Z", "resolved_inferred": false, "started_at": "2026-05-26T17:02:36.857Z", @@ -233,7 +233,7 @@ "body": "We've spotted that something has gone wrong. We're currently investigating the issue, and will provide an update soon.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-19T20:17:59.013Z", "resolved_inferred": false, "started_at": "2026-05-19T16:57:54.749Z", @@ -246,7 +246,7 @@ "body": "We've spotted that something has gone wrong. We're currently investigating the issue, and will provide an update soon.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-19T16:29:17.387Z", "resolved_inferred": false, "started_at": "2026-05-19T16:28:26.169Z", @@ -259,7 +259,7 @@ "body": "The issue has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-13T13:57:27.723Z", "resolved_inferred": false, "started_at": "2026-05-13T13:47:28.755Z", @@ -272,7 +272,7 @@ "body": "We've recovered the logs for all customers for the affected dates and these have been sent through to customer storage.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-05T14:41:24.456Z", "resolved_inferred": false, "started_at": "2026-05-05T13:13:45.656Z", @@ -285,7 +285,7 @@ "body": "The issue has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-04T16:30:44.007Z", "resolved_inferred": false, "started_at": "2026-05-04T13:20:23.479Z", @@ -298,7 +298,7 @@ "body": "The issue has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-28T12:22:43.578Z", "resolved_inferred": false, "started_at": "2026-04-28T11:59:01.131Z", @@ -311,7 +311,7 @@ "body": "The issue has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-23T14:18:06.959Z", "resolved_inferred": false, "started_at": "2026-04-23T13:39:15.430Z", @@ -324,7 +324,7 @@ "body": "The issue has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-23T11:57:59.268Z", "resolved_inferred": false, "started_at": "2026-04-23T11:38:14.058Z", @@ -337,7 +337,7 @@ "body": "The issue has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-13T14:03:59.236Z", "resolved_inferred": false, "started_at": "2026-04-13T13:02:05.649Z", @@ -350,7 +350,7 @@ "body": "We have completed the rollout of the fix and believe all organizations should have restored functionality.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-07T20:31:09.645Z", "resolved_inferred": false, "started_at": "2026-04-07T19:33:22.759Z", @@ -363,7 +363,7 @@ "body": "We have validated that the fix resolved the issue and customers are no longer seeing errors when accessing the org settings page in the Contentful WebApp.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-31T15:03:47.329Z", "resolved_inferred": false, "started_at": "2026-03-31T14:58:06.325Z", @@ -376,7 +376,7 @@ "body": "The issue is fully resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-19T18:54:24.339Z", "resolved_inferred": false, "started_at": "2026-03-19T18:36:12.495Z", @@ -389,7 +389,7 @@ "body": "The issue has been resolved", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-13T13:13:13.000Z", "resolved_inferred": false, "started_at": "2026-03-13T12:41:10.000Z", @@ -402,7 +402,7 @@ "body": "This issue is fully resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-12T18:29:04.690Z", "resolved_inferred": false, "started_at": "2026-03-12T17:48:53.504Z", @@ -415,7 +415,7 @@ "body": "This issue should now be resolved for all customers.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-03T13:47:36.873Z", "resolved_inferred": false, "started_at": "2026-03-03T12:25:44.755Z", @@ -428,7 +428,7 @@ "body": "The issue has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-17T22:16:17.602Z", "resolved_inferred": false, "started_at": "2026-02-17T20:55:45.576Z", @@ -441,7 +441,7 @@ "body": "This issue has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-09T20:54:13.401Z", "resolved_inferred": false, "started_at": "2026-02-09T12:31:53.370Z", @@ -454,7 +454,7 @@ "body": "The issue is now resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-06T17:19:46.788Z", "resolved_inferred": false, "started_at": "2026-02-06T11:03:51.245Z", @@ -467,7 +467,7 @@ "body": "The issue is now resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-06T10:44:05.201Z", "resolved_inferred": false, "started_at": "2026-02-06T09:34:58.147Z", @@ -480,7 +480,7 @@ "body": "This issue has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-27T16:28:21.684Z", "resolved_inferred": false, "started_at": "2026-01-27T15:41:57.072Z", @@ -493,7 +493,7 @@ "body": "The issue was resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-22T21:00:23.217Z", "resolved_inferred": false, "started_at": "2026-01-22T19:59:35.163Z", @@ -506,7 +506,7 @@ "body": "This issue is now resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-22T13:21:42.760Z", "resolved_inferred": false, "started_at": "2026-01-22T12:41:37.000Z", @@ -519,7 +519,7 @@ "body": "This issue has been resolved", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-21T10:59:24.518Z", "resolved_inferred": false, "started_at": "2026-01-21T10:05:20.478Z", @@ -532,7 +532,7 @@ "body": "The problem with assets being stuck in processing has been addressed all back to operational", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-16T14:34:01.101Z", "resolved_inferred": false, "started_at": "2026-01-16T13:14:42.749Z", @@ -545,7 +545,7 @@ "body": "The issue has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-14T23:00:29.818Z", "resolved_inferred": false, "started_at": "2026-01-14T21:32:15.369Z", @@ -558,7 +558,7 @@ "body": "Issue resolved. Customers can now upload assets through the web app as usual.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-14T18:03:00.347Z", "resolved_inferred": false, "started_at": "2026-01-14T16:56:43.634Z", @@ -571,7 +571,7 @@ "body": "Between 08:40 and 09:20 UTC customers experienced errors when trying to log in to Contentful (\"Something went wrong\"). This was due to a change we made to our bot protection logic. Once we saw the impact of the change, we reverted and the issue was resolved. If any customers continue to see the error after that time period, a refresh will resolve the issue.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-15T10:55:24.351Z", "resolved_inferred": false, "started_at": "2025-12-15T10:55:24.298Z", @@ -584,7 +584,7 @@ "body": "The issue is resolved now", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-10T14:01:16.844Z", "resolved_inferred": false, "started_at": "2025-12-10T13:12:10.546Z", @@ -597,7 +597,7 @@ "body": "This issue is now resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-04T11:40:15.456Z", "resolved_inferred": false, "started_at": "2025-12-04T10:33:38.477Z", @@ -610,7 +610,7 @@ "body": "Audit Logs have returned to their normal state and are fully operational again.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-03T09:03:04.360Z", "resolved_inferred": false, "started_at": "2025-12-02T15:12:41.608Z", @@ -623,7 +623,7 @@ "body": "The issue is resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-02T14:16:35.304Z", "resolved_inferred": false, "started_at": "2025-12-02T13:06:28.628Z", @@ -636,7 +636,7 @@ "body": "After monitoring the fix, we can confirm the issue is now fixed for all users.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-21T13:18:22.813Z", "resolved_inferred": false, "started_at": "2025-11-21T12:04:40.472Z", @@ -649,7 +649,7 @@ "body": "We've spotted that something has gone wrong. We're currently investigating the issue, and will provide an update soon.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-19T16:58:37.668Z", "resolved_inferred": false, "started_at": "2025-11-19T16:58:08.154Z", diff --git a/api/v/coreweave.json b/api/v/coreweave.json index 4b9eb99b55c62b148957e83bc7c5f3db507e460a..062c959c529ccf4a265a36c1ae1f7e6dbec49bab 100644 --- a/api/v/coreweave.json +++ b/api/v/coreweave.json @@ -3,7 +3,7 @@ "slug": "coreweave", "platform": "status.io", "status_url": "https://status.coreweave.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "maintenance", "history_backfilled": false, "first_watched": "2026-09-04T07:06:16Z", @@ -11,7 +11,7 @@ { "first_seen": "2026-09-04T07:06:16Z", "impact": "maintenance", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "started_at": "2026-08-28T18:15:46.923Z", "state": "maintenance", "title": "Scheduled CoreWeave Electrical Maintenance - US-EAST-04A", @@ -20,7 +20,7 @@ { "first_seen": "2026-09-04T07:06:16Z", "impact": "maintenance", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "started_at": "2026-08-19T14:44:13.100Z", "state": "maintenance", "title": "Scheduled CoreWeave Maintenance - US-EAST-08A ", diff --git a/api/v/courier.json b/api/v/courier.json index b1eb01fd0a1f8608c2610027eb6041449aff061a..3c369b6fde96972e1103eeeca26dc371808d402e 100644 --- a/api/v/courier.json +++ b/api/v/courier.json @@ -3,7 +3,7 @@ "slug": "courier", "platform": "statuspage", "status_url": "https://status.courier.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "Send pipeline has resolved and enqueued messages are now sending properly.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-18T15:09:09.632-07:00", "resolved_inferred": false, "started_at": "2026-06-18T13:11:52.004-07:00", @@ -25,7 +25,7 @@ "body": "Please continue to monitor Slack's statuspage for any updates related to message deliverability: https://slack-status.com/", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-27T16:16:34.216-07:00", "resolved_inferred": false, "started_at": "2026-05-27T16:06:26.000-07:00", @@ -38,7 +38,7 @@ "body": "# RFO: February 2, 2026 \u2014 Service Interruption\n\n## Executive Summary\n\nOn February 2, 2026, a deployment introduced a configuration change that referenced a file not present in our production build artifacts, causing backend services to become unavailable. API endpoints, automations, and tracking functionality were impacted for 2 hours and 17 minutes in the US region and 2 hours and 42 minutes in the Ireland region. Recovery was prolonged by a concurrent outage at GitHub Actions, our CI/CD provider, which prevented our standard automated rollback. Our team identified the root cause, executed a manual rollback independent of the affected provider, and restored full service across all regions. We have defined targeted action items to prevent recurrence.\n\n## Incident Overview\n\n* **Affected services:** API endpoints \\(including message sending\\), automations, webhooks, tracking links, and authentication\n* **Impact:** Requests to backend services returned errors for the duration of the incident. Users were unable to send messages, trigger automations, or access tracking data. No data was lost \u2014 requests were rejected before ingestion, so no messages were partially processed or left in an inconsistent state.\n* **Detection:** Our monitoring systems flagged elevated error rates within minutes of the issue beginning.\n* **Contributing factor:** GitHub Actions, our CI/CD provider, experienced a complete outage from 10:35 to 16:30 PST. This overlapped with our incident window and prevented our standard automated rollback from executing, extending the time to resolution.\n\n## Timeline of Events\n\nAll times in PST.\n\n| **Time** | **Event** |\n| --- | --- |\n| 10:59 | Deployment of latest release initiated through standard CI/CD pipeline |\n| 11:44 | Deployment completed and went live; services immediately began experiencing errors due to a missing configuration dependency |\n| 11:49 | GitHub Actions, our CI/CD provider, experienced a complete outage, preventing standard rollback procedures |\n| 11:52 | Monitoring alerts triggered; engineering team engaged |\n| 12:00 | Incident declared; rollback initiated; engineering team assembled |\n| 12:07 | Status page updated \u2014 issue identified and rollback in progress. Rollback ends up being blocked by GitHub actions outage. |\n| 12:39 | Team pivoted to an alternative manual rollback approach. This required testing and validating the new approach. |\n| 13:50 | Team executed the alternative manual rollback independent of GitHub Actions after they were fully satisfied that the new approach was safe.\u00a0 |\n| 14:01 | Manual rollback completed in US region; services confirmed operational |\n| 14:26 | Ireland region deployment completed; services confirmed operational |\n| 15:13 | All services verified stable across all regions; incident resolved |\n\n## Root Cause Analysis\n\nThe disruption was traced to a configuration change included in the latest release. The change introduced a startup dependency on a utility file that was intended to be bundled with the deployment package. However, the file was not included in the production build artifacts. When backend services attempted to initialize, they were unable to locate the required file and could not start, resulting in all incoming requests being rejected.\n\nThis discrepancy was not caught prior to production deployment because the file was present and functioning correctly in the development environment. The difference in how build artifacts are assembled between development and production environments meant the issue only manifested in production.\n\n## Mitigation and Resolution\n\n1. Upon identifying the root cause, the team immediately initiated a rollback to the prior known-good release through our standard CI/CD pipeline.\n2. A complete outage at GitHub Actions, our CI/CD provider, prevented the automated rollback from completing. The team identified this external dependency and pivoted to an alternative approach.\n3. The team executed a manual rollback by retrieving prior deployment artifacts from our backup storage and deploying them directly, bypassing the affected CI/CD pipeline entirely.\n4. Services were restored region by region, with the US region confirmed operational at 14:01 PST and the Ireland region at 14:26 PST.\n5. Extended monitoring was conducted across all services before declaring the incident fully resolved at 15:13 PST after we were satisfied everything had been stable for over 45 minutes.\u00a0\n\n## Action Items\n\n| **#** | **Action Item** | **Owner** | **Priority** | **Status** |\n| --- | --- | --- | --- | --- |\n| 1 | Require successful staging deployment and smoke tests before any production deployment | Engineering | P1 | In Progress |\n| 2 | Improve the reliability of automated smoke tests | Engineering | P1 | In Progress |\n| 3 | Add build-time validation to confirm all referenced startup dependencies are present in deployment packages | Engineering | P2 | Open |\n| 4 | Adopt an expedited rollback process as the standard emergency procedure, independent of CI/CD provider availability, reducing recovery time by approximately 35 minutes | Engineering | P2 | In Progress |", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-02T15:13:46.580-08:00", "resolved_inferred": false, "started_at": "2026-02-02T12:07:08.817-08:00", @@ -51,7 +51,7 @@ "body": "The Courier team identified an issue affecting observability metrics between 21:38 UTC and 22:13 UTC, during which metrics briefly experienced an outage. A fix was released and metrics are stabilized through observability channels. Metrics received during the outage window will not be accounted for in observability dashboards.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-29T02:00:00.000-08:00", "resolved_inferred": false, "started_at": "2026-01-29T02:00:00.000-08:00", @@ -64,7 +64,7 @@ "body": "Fix is out and application is stable", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-14T16:56:21.489-08:00", "resolved_inferred": false, "started_at": "2026-01-14T13:47:10.871-08:00", @@ -77,7 +77,7 @@ "body": "The incident has been resolved", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-20T03:11:54.758-07:00", "resolved_inferred": false, "started_at": "2025-10-20T02:19:57.000-07:00", @@ -90,7 +90,7 @@ "body": "Release is in production and Microsoft Teams messages are passing successfully.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-16T23:01:48.017-07:00", "resolved_inferred": false, "started_at": "2025-10-16T22:33:05.648-07:00", @@ -103,7 +103,7 @@ "body": "Courier experienced a slowdown in message delivery with Mailgun providers around 2AM PST. Our monitoring systems caught the spike in the bottleneck, which eventually stabilized. Our infrastructure team is actively monitoring.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-13T09:19:58.000-07:00", "resolved_inferred": false, "started_at": "2025-10-13T09:19:58.000-07:00", @@ -116,7 +116,7 @@ "body": "Courier's delivery platform experienced significant latency around 1am PST. Our platform team managed to resolve the issue and is actively monitoring for any potential issues.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-08T02:00:00.000-07:00", "resolved_inferred": false, "started_at": "2025-10-08T02:00:00.000-07:00", diff --git a/api/v/coveo-cloud.json b/api/v/coveo-cloud.json index 4f50d70dceee80280e24896301d71a548378f263..11ae4d083064ee3506d43f5918661e44ae432cbd 100644 --- a/api/v/coveo-cloud.json +++ b/api/v/coveo-cloud.json @@ -3,7 +3,7 @@ "slug": "coveo-cloud", "platform": "statuspage", "status_url": "https://status.cloud.coveo.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-26T16:17:24.853-04:00", "resolved_inferred": false, "started_at": "2026-08-26T15:12:18.214-04:00", @@ -25,7 +25,7 @@ "body": "The service has remained fully operational since the last update. This incident is resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-18T13:10:08.270-04:00", "resolved_inferred": false, "started_at": "2026-08-18T12:34:24.593-04:00", @@ -38,7 +38,7 @@ "body": "Between 2:30 PM ET and 4:30 PM ET, a temporary degradation on one of our service providers occurred which caused intermittent errors when interacting with Generative Answering in the US during that time window. The issue has been resolved.\n\nIf you need help or to get in touch with us, please visit our Help Portal", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-04T20:48:44.131-04:00", "resolved_inferred": false, "started_at": "2026-08-04T16:16:35.486-04:00", @@ -51,7 +51,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-17T09:55:59.347-04:00", "resolved_inferred": false, "started_at": "2026-07-17T08:05:17.269-04:00", @@ -64,7 +64,7 @@ "body": "The issue is now fully mitigated and this incident is resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-16T21:48:05.337-04:00", "resolved_inferred": false, "started_at": "2026-07-16T06:56:47.222-04:00", @@ -77,7 +77,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-10T17:40:17.987-04:00", "resolved_inferred": false, "started_at": "2026-07-10T14:12:01.653-04:00", @@ -90,7 +90,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-21T13:52:01.878-04:00", "resolved_inferred": false, "started_at": "2026-05-21T12:16:37.848-04:00", @@ -103,7 +103,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-08T15:51:25.662-04:00", "resolved_inferred": false, "started_at": "2026-05-08T07:39:40.771-04:00", @@ -116,7 +116,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-29T17:31:23.061-04:00", "resolved_inferred": false, "started_at": "2026-04-29T11:01:58.974-04:00", @@ -129,7 +129,7 @@ "body": "Between 1:46PM EDT and 2:47PM EDT, a temporary degradation of the Commerce API occurred which affected response time latency in the US region during that time window. The issue has been fixed and we are closely monitoring the service.\n\nIf you need help or to get in touch with us, please visit our Help Portal", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-27T13:46:00.000-04:00", "resolved_inferred": false, "started_at": "2026-04-27T13:46:00.000-04:00", @@ -142,7 +142,7 @@ "body": "The service has remained fully operational since the last update. This incident is resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-08T15:56:01.615-04:00", "resolved_inferred": false, "started_at": "2026-04-08T15:14:13.742-04:00", @@ -155,7 +155,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-03T22:33:42.122-04:00", "resolved_inferred": false, "started_at": "2026-04-03T17:53:46.683-04:00", @@ -168,7 +168,7 @@ "body": "This incident has been resolved. Thank you for your patience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-27T00:16:18.354-04:00", "resolved_inferred": false, "started_at": "2026-03-26T22:33:24.558-04:00", @@ -181,7 +181,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-04T01:26:48.451-05:00", "resolved_inferred": false, "started_at": "2026-03-04T01:22:53.000-05:00", @@ -194,7 +194,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-06T21:42:17.660-05:00", "resolved_inferred": false, "started_at": "2026-02-06T17:24:28.976-05:00", @@ -207,7 +207,7 @@ "body": "The service has remained fully operational since the last update. This incident is resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-13T18:31:48.754-05:00", "resolved_inferred": false, "started_at": "2026-01-13T17:53:52.876-05:00", @@ -220,7 +220,7 @@ "body": "The data received during the third-party outage has been processed.\nReporting in EU and Data Share in US West (Oregon) should be back to normal.\n\nIf you need help or to get in touch with us, please visit our Help Portal", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-16T21:20:55.240-05:00", "resolved_inferred": false, "started_at": "2025-12-16T04:37:50.184-05:00", @@ -233,7 +233,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-10T10:28:16.730-05:00", "resolved_inferred": false, "started_at": "2025-12-10T00:34:38.541-05:00", @@ -246,7 +246,7 @@ "body": "This incident has been resolved. Zscaler has reclassified coveo.com to \"Other Information Technologies\", resolving the access issues some customers were experiencing.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-24T11:14:33.636-05:00", "resolved_inferred": false, "started_at": "2025-11-21T16:15:02.103-05:00", @@ -259,7 +259,7 @@ "body": "This incident has been resolved. All services have remained fully operational since the last update.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-21T07:29:04.680-04:00", "resolved_inferred": false, "started_at": "2025-10-20T05:50:54.975-04:00", @@ -272,7 +272,7 @@ "body": "This incident has been resolved. All sources that were paused due to errors have now been restarted while sources that were stopped will resume normally on their next schedule. Thank you for your patience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-08T16:40:05.427-04:00", "resolved_inferred": false, "started_at": "2025-10-08T15:01:17.763-04:00", @@ -285,7 +285,7 @@ "body": "The service has remained fully operational since the last update. This incident is resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-07T11:26:42.743-04:00", "resolved_inferred": false, "started_at": "2025-10-07T10:45:16.144-04:00", @@ -298,7 +298,7 @@ "body": "The service has remained fully operational since the last update. This incident is resolved.\n\nPlease report any issues through our Help Portal.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-06T19:09:18.000-04:00", "resolved_inferred": false, "started_at": "2025-10-06T17:08:33.000-04:00", @@ -311,7 +311,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-02T00:00:28.648-04:00", "resolved_inferred": false, "started_at": "2025-10-01T23:06:21.000-04:00", @@ -324,7 +324,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-18T07:44:20.280-04:00", "resolved_inferred": false, "started_at": "2025-09-18T05:48:33.782-04:00", @@ -337,7 +337,7 @@ "body": "This incident has been resolved. The service has remained fully operational since the last update.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-12T13:18:59.018-04:00", "resolved_inferred": false, "started_at": "2025-08-12T12:07:36.818-04:00", @@ -350,7 +350,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-05T17:40:05.218-04:00", "resolved_inferred": false, "started_at": "2025-08-05T13:15:43.443-04:00", diff --git a/api/v/coveralls.json b/api/v/coveralls.json index 209222c991bc42f1aef337e099bc293f1175d356..a0d90174abba44a395fff61633c2779a0979a7bc 100644 --- a/api/v/coveralls.json +++ b/api/v/coveralls.json @@ -3,7 +3,7 @@ "slug": "coveralls", "platform": "statuspage", "status_url": "https://status.coveralls.io", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-11T14:09:44.458-07:00", "resolved_inferred": false, "started_at": "2026-08-11T12:02:12.967-07:00", @@ -25,7 +25,7 @@ "body": "This issue was resolved over the weekend. We will continue to monitor for elevated latency in the modified queues.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-20T10:32:17.056-07:00", "resolved_inferred": false, "started_at": "2026-07-15T10:28:59.136-07:00", @@ -38,7 +38,7 @@ "body": "This incident has been resolved but we believe it triggered a worsened incident overnight Sun night/Mon morning (US PDT) which has just been resolved. To be confirmed by full RCA, we believe a deluge of large repo uploads tied up individual web servers that handle frontline requests. Each web server is able to recover on its own, and did, but as volume increased all servers were eventually affected, only allowing short windows where requests could get through\u2014rejecting most requests with 504 errors.\n\nWe'll post a post-mortem when we understand more about what happened and how to prevent it going forward.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-13T07:56:35.290-07:00", "resolved_inferred": false, "started_at": "2026-07-10T08:00:47.000-07:00", @@ -51,7 +51,7 @@ "body": "Increased latency for large repos has been resolved for the general public. We will be clearing three outlier repos overnight, which should be fully cleared by tomorrow AM.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-07T21:39:37.170-07:00", "resolved_inferred": false, "started_at": "2026-07-07T09:43:22.969-07:00", @@ -64,7 +64,7 @@ "body": "We are closing this incident. Our main background processing queue for larger repos has had no backups in 48 hrs. We will continue monitoring for recurrence.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-28T08:53:52.401-07:00", "resolved_inferred": false, "started_at": "2026-05-18T09:41:15.110-07:00", @@ -77,7 +77,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-10T08:11:41.374-07:00", "resolved_inferred": false, "started_at": "2026-05-10T07:44:16.282-07:00", @@ -90,7 +90,7 @@ "body": "# Suspended for Not Paying\u2014While Paying\n\n_Latest update: Tuesday, Mar 24_\n\n[This post-mortem is also available as a PDF](https://s3.amazonaws.com/assets.coveralls.io/statuspage/incidents/20260224/postmortem/Coveralls-Post-Mortem-Service-Outage-Feb-2026.pdf).\n\n## Overview\n\nOn February 24, our hosting provider suspended our account. Our service was down for 68 hours. The stated reason was past-due charges. When we reached our account manager on the day of suspension, he reviewed our account and told us what he saw: an \"account restriction\" that, in his words, \"shouldn't have happened.\"\n\nBizarrely, his review turned up an internal note claiming we'd made _no payments in six months_. That was demonstrably false and we provided immediate evidence to prove it.\n\nWe did have an outstanding balance\u2014the product of a billing dispute that took nearly a full year to reach a decision in our favor. But finalizing what we owed required tracking down two credits we couldn't locate. We asked AR one specific question: _where did those two credits go?_ We asked it _six times_. For some reason we still don't understand, they simply stopped responding. We escalated to our account manager, who promised to intervene. Then we heard nothing from anyone. Until we were suspended.\n\nDespite providing evidence of our payments, open billing cases, and relentless communication, we waited three days for our service to be restored. When someone finally acted, we were back online within minutes. Three days, and then minutes. Our provider has not explained that gap, or responded to the formal request for answers we submitted more than two weeks ago.\n\nWithout those answers, what follows is our account. We're sharing everything and letting you judge for yourself.\n\n_If what you need most right now is assurance that this won't happen again, and to know what we're doing for affected customers, you can jump ahead to **What We're Doing** and **Making It Right**._\n\nBut we'd ask you to read through. On the surface, this looks like a company that didn't pay its bills and got suspended. The full picture tells a different story, and the evidence speaks for itself.\n\n## About Coveralls\n\nCoveralls has been providing code coverage analytics for 15 years. We're bootstrapped: no outside funding. Over 225,000 developers use [Coveralls.io](http://Coveralls.io) every day, and roughly 90% of them are open-source contributors who use the service for free. \\[1\\]\n\nWe have never experienced an outage like this in our 15-year history.\n\n## The Incident\n\n### What We Were Told About Suspension\n\nMore than once, over the past year, we asked our account manager directly whether we were at risk of suspension.\n\nEach time, the answer was no. He told us suspension was designed to be rare, that it was reserved for accounts that had gone _delinquent_\u2014stopped _paying_, and stopped _communicating_\u2014and that it required his sign-off, _and_ his manager's.\n\nHe told us he received a regular list of at-risk accounts among those he managed, so he could review them and give feedback before any action was taken. He told us we had _never_ appeared on that list.\n\nHe said our provider _knew_ we were paying, and _knew_ we were actively communicating, with AR and with him. Based on everything he told us, suspension wasn't just unlikely, it wasn't supposed to be possible. At least not without warning.\n\n### Timeline\n\n**Tuesday, Feb 24 \u2014 Day 1**\n\n1:45 PM PST: We suddenly lose access to our hosting provider's console. The service is still up, so we assume it's a technical issue. Multiple team members try their credentials. None work.\n\n2:42 PM: We receive our first support request saying, \"posting coverage data stopped working\", but we don't see it until 2:51 PM due to the next event.\n\n2:45 PM: A team member gets past a login screen and sees a message: \"Your account was suspended because of past due charges.\" We don't believe it. We reach out to our account manager by email, then text, then phone. He confirms an \"account restriction\" that, based on his review of our account, \"shouldn't have happened\", and shares that an internal note on our account says, \"_Customer has made no payments for 6 months_.\"\n\n2:51 PM: We see the first support request.\n\n2:52 PM: We open an incident on our status page. At this point, we are still expecting this to be reversed quickly and do not yet disclose the suspension publicly. In hindsight, we should have.\n\n~3:00 PM: While we're on the phone with our account manager, one of us discovers the official suspension notification in our inbox, timestamped 2:03 PM, about 15 minutes after we were first locked out. Our AM asks us to create a new support ticket and promises to escalate. Two hours fly by while we feverishly collect and send evidence of improper suspension. We expect our AM to get this reversed as soon as he gets through to\u2014_someone_.\n\n5:36 PM: No definitive update. Our AM is \"still working on it.\" He tells us the AR team involved is on Eastern time and may be gone for the day. We post that the issue has been identified and a fix is being implemented. We believe this. We are wrong.\n\n7:28 PM: No resolution. Our account manager tells us he continues to escalate but that under the current circumstances, he himself has \"limited access\" to our account. Still\u2014_should_ be fixed by morning. We update our incident, extend the outage window, and recommend fail-on-error: false for CI workflows.\n\n~9:30 PM: Still no resolution. We check status throughout the night.\n\n**Wednesday, Feb 25 \u2014 Day 2**\n\n6:45 AM: We text our account manager, surprised service has not been restored.\n\n9:48 AM: First public disclosure \u2014 outage originated at our infrastructure provider. We are unable to access our account.\n\n5:56 PM: After a full day working with our provider's account team, we learn more about the restriction. Not a technical failure\u2014infrastructure and data intact. Their team indicates they are working to reverse it, and we expect resolution by morning.\n\n**Thursday, Feb 26 \u2014 Day 3**\n\n6:53 AM: Still waiting. \"We thought this would be resolved by this morning.\"\n\n5:13 PM: After a full second day of trying to get answers as to why this is happening, and why it hasn't been resolved yet, the picture remains unclear. No ETA. \"What appears to have been an automated action, one that no one on their side has taken ownership of causing or fixing.\" We commit to evaluating backup infrastructure and promise a full post-mortem.\n\n**Friday, Feb 27 \u2014 Day 4**\n\n7:41 AM: \"As we pass milestones in this outage that we never imagined we would see \\(and haven't in 15 years of operation\\)...\" We announce that if not restored by EOD, we will stand up new infrastructure over the weekend.\n\n11:02 AM: Systems begin coming back online. We have not been told what changed.\n\n11:11 AM: Service partially restored.\n\n12:23 PM: After one hour of monitoring, cautiously optimistic that service is fully restored in all regions.\n\n**2:30 PM: After two more hours of monitoring, the incident is officially marked resolved. Total outage: approximately three days \\(68 hours\\) across 4 calendar days.**\n\n\u200c\n\n## What We Think Happened\n\nHere's what we found when we started looking for answers:\n\n### The Note That Wasn't True\n\nThe first thing we learned about why our account had been suspended was what our account manager told us: there was an internal note from AR that read:\n\n> _Customer has made no payments for 6 months._\n\nThis was demonstrably false. Here is our payment history for that exact period\u2014September 1, 2025 through February 24, 2026 \\(the date of our suspension\\):\n\n![](https://s3.amazonaws.com/assets.coveralls.io/statuspage/incidents/20260224/postmortem/image2.png)\n\nWe shared this evidence with our provider immediately, backed by bank statements:\n\n![](https://s3.amazonaws.com/assets.coveralls.io/statuspage/incidents/20260224/postmortem/image1.png)\n\n\u200c\n\nBut it raises the question: if we were paying, why would our provider think we _weren't_?\n\n### Why The Note Existed\n\nWhen we look at our billing console we can see why someone might _think_ we hadn't paid: **it shows none of our payments**.\n\nInvoices we know to have been fully paid show none of our payments against them.\n\nMost notably, the **Transactions Tab** of the **Payments** section of our billing console contains _**no payment records**_ **for last 6 months**\u2014resonating with that internal note:\n\n\u200c\n\n\u200c\n\n![](https://s3.amazonaws.com/assets.coveralls.io/statuspage/incidents/20260224/postmortem/image4.png)\n\u200c\n\nIf an automated system relied on this same data to determine whether a customer had made payments, and that data showed six months of silence, it _might_ trigger exactly the kind of suspension we experienced: an automated action with no advance warning, with no one on their side able to explain it or willing to take ownership of it.\n\nThis is our strongest piece of evidence that the suspension was triggered by bad data, and not our actual account status.\n\n\u2014\n\nTo put this in context: over the six months during which the internal note claimed we'd paid _nothing_, our provider billed us $127,186. Our verified payments for the same period totaled $120,312\u2014a gap of roughly $6,900, which is less than a third of the amount we were actively disputing in our second open billing case.\n\n![](https://s3.amazonaws.com/assets.coveralls.io/statuspage/incidents/20260224/postmortem/image3.png)\n\n\n![](https://s3.amazonaws.com/assets.coveralls.io/statuspage/incidents/20260224/postmortem/image5.png)\n\n\\(By March 5, our payments even exceeded our total invoiced charges for the period: we were not delinquent.\\)\n\nOur payments were in line with our usage. We weren't _up-to-date_\u2014but the portion of the balance we still carried traced directly back to a single incident that triggered a billing dispute, which took ten months to resolve and still hadn't fully landed by the time we were suspended.\n\n\u2014\n\nBut the note, and the billing console, only explain so much. They might explain how the suspension was _triggered_. They don't explain why it took _three days_ to reverse, even after providing evidence of our payments and open billing cases. If there's an answer for that, it lives in the rest of the story. We've looked. We don't see a justification for either. Draw your own conclusions.\n\n### How The Balance Happened\n\nIn 2025, we faced a critical infrastructure challenge. Our production PostgreSQL database, approaching a 65TB ceiling due to failing maintenance operations, also needed a major version upgrade before end-of-life. We started the upgrade a month early. It took four-and-a-half months to complete.\n\nDuring three-and-a-half of those months, our provider levied Extended Support Fees on us that roughly _quadrupled_ our database hosting costs for that period. \\[2\\] We asked our provider to pause or waive them\u2014the fees were simply beyond what we could absorb. They told us that wasn't possible, but that we could open a billing dispute and make our case. We did that, and our provider eventually approved credits for the full amount. But that process took ten months. \\[3\\]\n\nDuring those ten months, those fees accumulated into a past due balance, so we asked AR for a repayment plan, and their answer was: wait. The credit outcome would affect what we owed, and they needed the case to resolve before we could finalize any repayment agreement.\n\nIn response to an email titled \"Seeking repayment plan for past due balance,\" an AR representative told us:\n\n> _Upon checking, the support case related to billing adjustment review via case ID remains active. Please continue to monitor the support case for any update and provide the required information for faster resolution. Once the billing adjustment review for re-appeal was completed, we can discuss for possible payment plan._\n\nIn the meantime, we paid what we could and waited for resolution. Our balance stayed on the books for ten months\u2014and with it came past-due notices with threats of suspension we were told were automated and couldn't be stopped. Those are what prompted us to ask our account manager, more than once, whether we were truly at risk of suspension, and his answers gave us confidence that, difficult as the situation was, we were managing it the right way.\n\nWhen those warnings arrived, we did the same thing: made a payment and notified AR. That pattern\u2014always paying, always communicating\u2014put us squarely in the playbook our account manager described, and it seemed to work because we never appeared on his at-risk list.\n\n### A Balance We Couldn't Pin Down\n\nWhen the billing case finally resolved in January 2026, we expected to finalize a repayment plan, but we were blocked _again_\u2014and explaining why requires a brief note on how the approved credits worked:\n\nThe credits didn't arrive as a direct reduction to our outstanding balance. They came in eight different amounts, apparently as cash refunds\u2014separate transactions that made their way back to us through different payment methods. This meant our balance didn't shrink by the amount of the credits as we expected it would; and, more importantly, some of the credits remained outstanding due to two transactions we couldn't locate. Whether and how _those_ had been applied\u2014_unclear_.\n\nThose two missing refunds had no payment method attached in our billing console, and we couldn't find matching deposits in any of our bank or card accounts. They were material to calculating our actual outstanding balance, and any repayment plan, and without AR's help, we couldn't track them down.\n\nSo we submitted our first request for help on February 12:\n\n> _We are having trouble balancing our remaining amount due \\($\\[redacted\\]\\) against our credits awarded Jan8 \\($\\[redacted\\]\\). Can you help us track down these two \\(2\\) refund transactions? \\[...\\] We can't find a payment method associated with those two refunds \\[...\\] And we can't find matching transactions anywhere in any of our card or bank account statements. Do you know how / where those refunds were applied?_\n\nThree days later, on Feb 15, we received a response that simply restated the information in our billing console. It didn't answer our question.\n\nWithin an hour of receiving it, we responded and made the stakes explicit:\n\n> _Sorry if I wasn't clear: We have not been able to find these two refunds: \\[...\\] We cannot find the money. We believe we did not actually receive it. We have a general repayment plan in mind that we hope to present, but first we need to resolve this question of these two missing refunds. Without being able to account for that $\\[redacted\\], we believe our current outstanding balance could be off by that much. Your input on this is crucial for us._\n\nWe received no response.\n\nGrowing concerned about a possible disconnect with AR, that Friday, February 20, we cc'd our account manager on another follow-up to AR and, separately, forwarded the full thread to him directly, asking him to intervene:\n\n> _Is there any way you can help us get a response from \\[Redacted\\] or someone else in Billing regarding the missing refund payments? We want to implement a repayment plan, but need to be clear on our numbers._\n\nHe replied the same day:\n\n> _Yes \u2014 I'll reach out to her. \\[...\\] Let me pop into the ticket to see if I can escalate._\n\nThat was the last we heard from anyone.\n\nOn February 19, we received a past-due notice with a suspension warning dated the following day. This wasn't unusual\u2014we'd received them throughout the entire ten-month period and had always responded the same way: we made a payment and notified AR. We made a $10,000 payment on February 20 and let AR know. We interpreted the passing of February 20 the way we always had: as confirmation that our payment had been received and the threat had passed.\n\nFour days later, we were suspended.\n\n### Six Weeks Before Suspension\n\nSix weeks before our suspension, on January 14, we filed a second billing dispute. We had been trying to _reduce_ our hosting costs by shrinking our production database; instead, a mandatory storage configuration upgrade blocked us for 27 days and roughly _doubled_ our costs during that period. We disputed the incremental charges.\n\nAfter working through all required questions, our request was formally submitted to Billing's specialist team:\n\n> _Since these charges are not yet present on your account we here at Billing team cannot promise a refund or credits to offset these charges. However, we can connect with your AWS Account Manager for getting an exception approved for you by our specialist internal team. Please contact your Account Manager so they can work with the team for the required approval._\n\nWe formally looped in our AM as directed\u2014he was already cc'd on the case, but we followed the process\u2014and he confirmed he was actively monitoring and advocating for our credit request.\n\nOn January 22, we experienced a temporary account restriction\u2014we were unable to add certain services needed for our workaround. We reached out to our AM and sent a parallel update to our AR contact, informing her of the open billing case and our AM's involvement. The restriction was lifted.\n\nOur AR contact replied with direction nearly identical to what we'd received throughout our first billing dispute:\n\n> _Kindly continue to monitor the support case for billing adjustment review._\n\nThe technical workaround we selected took 20 days\u2014January 22 through February 10\u2014spanning our two most recent billing periods.\n\nWhen the effort was complete, we updated Billing, and our account manager, with the final timeline, cost, and the amount of our credit request. By February 12, everyone had the same information: the work was done, the dispute was submitted, and our last two invoices were under active dispute.\n\nBased on prior experience and similar direction from AR, we believed charges under active dispute would not be counted toward our outstanding balance\u2014let alone any balance used to justify suspension.\n\nWe don't know whether our disputed billing charges _were_ part of the outstanding balance that triggered suspension, or not. All we know is that AR knew about this open case, and so did our AM, who had told us more than once that he reviewed at-risk accounts before any suspension action was taken.\n\nNeither warned us that suspension was imminent.\n\n\u2014\n\nTo recap: we were paying\u2014over $100K during the same six months the internal note claimed we'd paid nothing. We were communicating\u2014multiple messages to AR in the twelve days before suspension, plus a direct escalation to our account manager after AR went silent. We had an open billing dispute, and a repayment plan in progress with a specific blocker we had been asking AR to help us resolve for nearly two weeks.\n\nNone of the criteria our account manager described for suspension applied to us. We hadn't stopped paying. We hadn't stopped communicating. We had never appeared on his at-risk list. The suspension hadn't had his sign-off or his manager's.\n\nOn the day of our suspension, our account manager reviewed our account and told us it \"shouldn't have happened.\"\n\nThree days later, when someone finally acted, service was restored within minutes.\n\nTo this day, we still don't know exactly why the suspension happened, or why it took three days to reverse.\n\n## Open Questions \\(Our Formal Request for Answers\\)\n\nOn March 4, three business days after our service was restored, we sent a formal request for answers to our hosting provider. As of this writing\u2014fourteen days later\u2014we have not received a response.\n\nWe're not publishing those questions verbatim here because we don't want to frame them as a public ultimatum. But our questions cover four areas:\n\nWe want to understand what triggered the suspension and who authorized it\u2014whether it was automated or a human decision, and why we were suspended when we had never appeared on our account manager's at-risk list.\n\nWe want to know why our billing console showed no payment records for a period in which we had paid over $104K in verified bank transactions, and what prompted the internal note.\n\nWe want to know why our missing refund issue\u2014raised six times between February 12 and February 24\u2014was never substantively addressed before we were suspended.\n\nAnd we want to understand why reinstatement took three days after we provided evidence of our payments, our open billing cases, and our multiple attempts to resolve the blocker to our repayment agreement\u2014especially when service was restored in _minutes_ once someone finally acted.\n\nWe're committed to updating this post-mortem when we have those answers.\n\n## What We've Learned\n\nTwo things we should have done differently, and one assumption we should never have made.\n\nThe process guidance our account manager provided was verbal. We relied on it in good faith\u2014it was specific, consistent, and came from someone with direct knowledge of our account. But we never sought written confirmation. We should have.\n\nWe noticed discrepancies in our billing console earlier in this process. We flagged them but didn't fully understand their significance, or their potential connection to how our account might be evaluated\u2014until it was too late to escalate effectively. That's a failure we must own.\n\nAnd finally: we assumed we were safe. We were doing everything we'd been told to do. The most recent suspension warning had passed without incident\u2014as others had. We interpreted that silence as confirmation. It wasn't. We should have insisted on written confirmation of our account status; and when we couldn't get AR to respond, we should have escalated beyond email and beyond our account manager.\n\n\u2014\n\nThat's our account of what happened. What follows is what we're doing about it.\n\n## What We're Doing\n\nThe most significant thing we've done to prevent a recurrence is reduce our monthly database hosting costs by approximately 50% from their peak. We accomplished this by completing a major database project we'd been working toward for over a year\u2014the same project that was blocked twice, producing the unplanned cost spikes at the center of both billing disputes. That pressure is gone. We can easily meet our regular charges going forward.\n\nWe have nearly paid off our outstanding balance\u2014by 50% if disputed charges are included, by more if not\u2014and we've already begun implementing our repayment plan. We met with our provider this week to formalize that, but we're not waiting to execute. If we prevail in our open billing dispute, the remaining balance shrinks further, making repayment that much easier and faster.\n\nWe are standing up failover infrastructure on a second provider, expected to be operational within 60 days. No single vendor should ever again have the ability to take our service offline with no recourse.\n\n### Going Forward\n\nGoing forward, we will not rely on verbal guidance or implicit signals to determine our account standing. We will seek explicit, written confirmation of our status from both our account manager and a dedicated AR contact\u2014someone we hope will commit, in writing, to direct communication \\(not system warnings\\) that gives us at least one opportunity to resolve any issue before adverse action is taken. We will also get in writing the exact steps our provider follows before suspending an account.\n\nFinally, we owe you a commitment about how we communicate during incidents. During this outage, there were moments\u2014particularly on Day 1\u2014where we knew more than we shared publicly. We held back because we didn't fully believe what was happening, and because we kept expecting it to be reversed at any moment. That was the wrong call. Going forward, we will share what we know as soon as we know it, even when it's embarrassing, scary, and we don't yet have the full picture. You deserve that transparency in real time, not just in a post-mortem.\n\n## Making it Right\n\nEvery paying customer affected by this outage will receive a credit equal to four days of their current subscription\u2014one day for each day of interrupted service. This credit will be applied automatically to your next bill.\n\nWe understand that's not enough\u2014it's an attempt to be equitable while not harming ourselves more than we've already been harmed by this outage. We want you to know that if anyone feels it doesn't properly compensate for how the outage affected you, just reach out and we will refund the whole month. No questions asked.\n\nTo our open-source users: the best we can offer is this post-mortem. We know some of you have been through similar things. If it's helpful for you to discuss further, please reach out. We'd also be grateful to hear from anyone who's been through something similar and what you did about it from a hosting perspective. And thanks for the HugOps. We're ready to share some back now.\n\nIf you have questions about anything in this post-mortem, we're at [ops@coveralls.io](mailto:ops@coveralls.io).\n\n## Acknowledgments\n\nFinally: thank you.\n\nDuring the worst week in our 15-year history, our community showed up. Customers offered server rack space. An SRE director offered to apply pressure through his own provider relationships. People we'd never met sent messages of support and solidarity.\n\nIn the DevOps community, the term is: HugOps. We received a lot of it that week, and it made a real difference.\n\nFor those who've stayed with us through this\u2014thank you. We know you have other options. We appreciate the opportunity to make this right.\n\n\u2014\n\n## Notes\n\n\\[1\\] _That ratio matters for this case. Our revenue doesn't scale proportionately to our infrastructure costs. Unexpected cost spikes hit us harder than they would a company whose hosting bill is covered by proportional revenue, which is part of why the billing situation at the center of this story developed the way it did._\n\n\\[2\\] _AWS RDS Extended Support Fees \\(ESF\\) are charged per vCPU per hour on any RDS instance running a PostgreSQL major version past its end of standard support date \u2014 on top of normal instance costs. Our production instance was a db.r6g.16xlarge: 64 vCPUs, 512 GB RAM, at the 65TB maximum RDS storage allocation. At 64 vCPUs and the Year 1 ESF rate, the surcharge approached the cost of the instance itself. Our Major Version Upgrade \u2014 which took four and a half months, three and a half of which fell within the Extended Support window \u2014 required a Blue/Green Deployment, meaning we ran two db.r6g.16xlarge instances simultaneously for that entire period, each accumulating ESF charges around the clock. Two instances at normal cost plus ESF on both: that is what nearly quadrupled our database hosting costs for the period._\n\n\\[3\\] _Note: In connection with the credit award, we signed an agreement that restricts us from disclosing specific amounts or characterizing our provider's position on the dispute._\n\n\u2014\n\n[Download a PDF version of this post-mortem](https://s3.amazonaws.com/assets.coveralls.io/statuspage/incidents/20260224/postmortem/Coveralls-Post-Mortem-Service-Outage-Feb-2026.pdf).", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-27T14:30:00.000-08:00", "resolved_inferred": false, "started_at": "2026-02-24T14:52:29.054-08:00", @@ -103,7 +103,7 @@ "body": "Just a note to address the gap in our Coverage Calculation Background Job Dequeue Time Graph today, MON, FEB 2 from 00:15:00 PST to 07:35:00 PST:\n\nCoveralls experienced no disruption in service at this time. Instead, a deployment issue cause the cron job that reports the metric to fail until it was resolved at 07:35:00 PST.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-02T09:33:52.000-08:00", "resolved_inferred": false, "started_at": "2026-02-02T09:33:51.977-08:00", @@ -116,7 +116,7 @@ "body": "We had to pause some queues to recover performance for new jobs, but will clear those as soon as we've recovered normal build times for new jobs (ETA: 15-min).\n\nIf you are a user in APAC or EU, you may have had your jobs paused. One repo in particular has represented 90% overnight workload. We will reach out to that user.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-19T07:24:16.835-08:00", "resolved_inferred": false, "started_at": "2025-12-19T06:34:44.392-08:00", @@ -129,7 +129,7 @@ "body": "Build times are normal for all new builds. Background queues have been cleared of 99% of backlogged jobs; the only ones that remain are for large repos (>5K source files), which should clear in the next 30-45 minutes depending on size.\n\nNo further effects on latency expected. \n\nClosing this incident.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-18T08:58:27.156-08:00", "resolved_inferred": false, "started_at": "2025-12-18T06:51:18.919-08:00", @@ -142,7 +142,7 @@ "body": "This incident has been resolved. Build times for all new builds is normal across the board.\n\nWe are still clearing a backlog of background jobs, which should be clear in the next 15-20-min.\n\nIf you are having issues with a slow or stuck build, feel free to reach out to us at support@coveralls.io. These steps will save time:\n\n1) Mention this incident:\nhttps://status.coveralls.io/incidents/hkqt790213m5\n\n2) Share your Coveralls Build URL (from your CI build log), or your CI build number.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-17T11:43:38.674-08:00", "resolved_inferred": false, "started_at": "2025-11-17T08:35:03.565-08:00", @@ -155,7 +155,7 @@ "body": "We have attempted to improve latency this morning for new jobs from users in EU and US time zones, which has meant offloading older jobs to specialized queues with scaled up resources, which, at this point, have already drained.\n\nSystem-wide, latency continues improving for all users and should reach normal in 15-30 minutes for most users.\n\nIf you are still experiencing elevated latency after that, or have any jobs from CI builds run in the last 24 hrs that have not completed, please reach out to us at support@coveralls.io and we'll investigate to determine whether your builds were caught up in this incident, or if they have a different cause.\n\nNOTE: Missing data points in the \"DEQUEUE\" Graph on our main Status Page does not indicate that processing stopped during that period, just that the server that reports our stats lost comms during that period. As stated elsewhere, to avoid this confusion in the future it's one of our goals to spread stats collection across all servers.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-10T10:55:54.000-08:00", "resolved_inferred": false, "started_at": "2025-11-10T08:14:00.004-08:00", @@ -168,7 +168,7 @@ "body": "We are closing this incident having received no further reports of 504 errors today. We will continue to monitor for them.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-24T14:54:04.600-07:00", "resolved_inferred": false, "started_at": "2025-10-24T11:35:11.000-07:00", @@ -181,7 +181,7 @@ "body": "We have received no further reports of 504 timeout errors on coverage report uploads today, but we continue to monitor and will continue trying to improve our mitigations.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-13T16:15:42.403-07:00", "resolved_inferred": false, "started_at": "2025-10-13T11:02:40.474-07:00", @@ -194,7 +194,7 @@ "body": "This incident is resolved. \n\nWe have applied an additional layer of monitoring that should help us catch these cases earlier.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-10T12:00:40.425-07:00", "resolved_inferred": false, "started_at": "2025-10-10T08:23:27.445-07:00", @@ -207,7 +207,7 @@ "body": "We are closing this incident after recent mitigations and a weekend without any reports.\n\nWe continue to implement mitigations and infrastructure changes we believe will further reduce incidents of this error type.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-29T08:56:14.000-07:00", "resolved_inferred": false, "started_at": "2025-09-26T08:28:03.000-07:00", @@ -220,7 +220,7 @@ "body": "**This is a postmortem on this specific issue:** Intermittent 500 Errors on Coverage Uploads\n\n**Summary** \nBetween September 20\u201324, some customers experienced intermittent `500 Internal Server Error` responses during coverage uploads \\(`POST /api/v1/jobs`\\). The issue was initially hard to diagnose because:\n\n* Failures did not surface reliably in our error tracker \\(BugSnag\\).\n* They appeared to affect only some requests, some customers.\n\n**Impact**\n\n* Some coverage uploads failed to process, causing build reporting delays or gaps.\n* Frequency was low enough to appear intermittent, which delayed detection and resolution.\n\n**Timeline**\n\n* **Sep 20\u201323**: First customer reports of intermittent 500s. Initial theories involved a regression in a recent release of our coverage-reporter integration \\(client-side\\).\n* **Sep 23\u201324**: Deep log analysis across ELB and application logs revealed errors concentrated on a single web server.\n* **Sep 24**: Confirmed that server alone was responsible for thousands of SSL-related failures \\(`Faraday::SSLError`, `OpenSSL::SSL::SSLError`, `Seahorse::Client::NetworkingError`\\). Other servers were clean.\n* **Sep 24**: Mitigation: that server was destroyed. Errors ceased immediately.\n\n**Root Cause** \nIn terms of possible cause, we believe this additional Web server was provisioned during autoscaling with a different Ubuntu version than the rest of the fleet. This seemed to result in a broken or outdated CA certificate store, causing outbound SSL connections \\(GitHub, Travis, etc.\\) to fail intermittently\u2014but then bubble up to a `500` error for the original request \\(`POST` to `/api.v1/jobs`\\).\n\n**Resolution**\n\n* Problematic server removed from service.\n* Future mitigation: verify baseline OS/version and CA store when adding new servers, especially via automation.\n* Next step: document the correct procedure to disable a single server in Cloud66 load balancers, instead of outright destroying, so we can retain the server for forensic investigations.\n\n**Lessons Learned**\n\n* Errors can hide if they don\u2019t surface in the bug tracker. Direct log analysis is essential.\n* Even one misconfigured server can cause significant customer impact.\n* Consistency in OS/base image, and CA, is critical.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-24T17:53:00.000-07:00", "resolved_inferred": false, "started_at": "2025-09-03T11:00:31.000-07:00", @@ -233,7 +233,7 @@ "body": "We believe this issue has been resolved for now.\n\nThe underlying cause still appears to be large spikes in incoming Web traffic from other outlier repositories that we have not yet identified or not yet paused.\n\n**Interim Solution**:\n\nTo reduce the risk of recurrence, we have applied _temporary load balancer adjustments_ that change how requests are distributed, which should _lower_\u2014if not _eliminate_\u2014the frequency of **503** \u201c**This website is under heavy load**\u201d **errors**.\n\n**Permanent Solution**:\n\nWe are also designing a permanent solution to _rate-limit abnormal request patterns_. This will require coordination at the policy/SLA level before it can be fully implemented.\n\nIn the meantime, we will continue to closely monitor traffic and use targeted load balancer and web server configurations to mitigate the impact of outlier traffic spikes.\n\n**More details**:\n\nFor a more detailed assessment / RCA of this incident and its recent, related incidents, see [this postmortem](https://status.coveralls.io/incidents/wqbsxnzv0jsf).\n\n**Update \\(Thu, Aug 21\\)**:\n\nWe have identified a **different permanent solution**, which does not entail changes to SLA-level details for \u201coutlier repos.\u201d We may still implement such a solution, but our alternative solution should avoid further 503 errors and be implemented in the next 48-72 hrs.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-20T15:21:47.849-07:00", "resolved_inferred": false, "started_at": "2025-08-20T08:48:22.100-07:00", @@ -246,7 +246,7 @@ "body": "### Postmortem: Reports of \u201cWebsite under heavy load\u201d errors\n\nWe experienced multiple intermittent errors over the past several days before we were able to identify the true root cause and resolve the issue.\n\n**Root Cause** \nThe errors were caused by a single outlier repository generating extremely high-volume requests \\(750\u20131,800\\+ coverage report uploads per build\\). Combined with the default \u201csticky request\u201d behavior in Passenger Enterprise \\(which routes repeat requests from the same IP to the same HTTP server\\), this overwhelmed individual servers. Once a server\u2019s request queue was exhausted, subsequent requests returned a `503` error with the message: _\u201cThis website is under heavy load.\u201d_\n\nAlthough each server was able to process individual requests within normal timeframes, the concentrated traffic volume from a single repo and source IP could not be evenly distributed across servers. This led to repeated saturation of request queues and customer-visible errors.\n\n**Solutions Implemented**\n\n1. We are testing new settings to override Passenger\u2019s default \u201csticky request\u201d behavior to allow requests to be distributed more evenly across servers.\n2. We have paused processing for the outlier repository while we validate that the configuration changes are sufficient to prevent future incidents.\n\n**Next Steps**\n\n* Continue monitoring system performance to confirm stability.\n* Reintroduce the paused repository once we are confident the mitigations are effective.\n\n**Closing** \nWe appreciate your patience as we worked through this issue. These changes are intended to permanently guard against similar incidents going forward. If you encounter unexpected errors, please contact us at [support@coveralls.io](mailto:support@coveralls.io).\n\n**Related incidents**\n\n1. **Aug 13**: [Intermittent request rejections](https://status.coveralls.io/incidents/1n7plxrj8j44)\n2. **Aug 14**: [Service unavailable with HTML error page or 500 errors](https://status.coveralls.io/incidents/v5mcbrsbhgt4)\n3. **Aug 18**: [Reports of \"Website under heavy load\" errors](https://status.coveralls.io/incidents/fr6sp5kyn128)\n4. **Aug 19 \\(Today\\)**: [Reports of \"Website under heavy load\" errors](https://status.coveralls.io/incidents/wqbsxnzv0jsf)", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-19T10:26:33.373-07:00", "resolved_inferred": false, "started_at": "2025-08-19T08:21:44.595-07:00", @@ -259,7 +259,7 @@ "body": "A postmortem for this incident and its related incidents has been posted [here](https://status.coveralls.io/incidents/wqbsxnzv0jsf):\n\n* [**Postmortem: Reports of \u201cWebsite under heavy load\u201d errors**](https://status.coveralls.io/incidents/wqbsxnzv0jsf)\n\n**Related incidents**\n\n1. **Aug 13**: [Intermittent request rejections](https://status.coveralls.io/incidents/1n7plxrj8j44)\n2. **Aug 14**: [Service unavailable with HTML error page or 500 errors](https://status.coveralls.io/incidents/v5mcbrsbhgt4)\n3. **Aug 18**: [Reports of \"Website under heavy load\" errors](https://status.coveralls.io/incidents/fr6sp5kyn128)\n4. **Aug 19 \\(Today\\)**: [Reports of \"Website under heavy load\" errors](https://status.coveralls.io/incidents/wqbsxnzv0jsf)", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-19T01:10:17.588-07:00", "resolved_inferred": false, "started_at": "2025-08-18T12:25:56.000-07:00", @@ -272,7 +272,7 @@ "body": "A postmortem for this incident and its related incidents has been posted [here](https://status.coveralls.io/incidents/wqbsxnzv0jsf):\n\n* [**Postmortem: Reports of \u201cWebsite under heavy load\u201d errors**](https://status.coveralls.io/incidents/wqbsxnzv0jsf)\n\n**Related incidents**\n\n1. **Aug 13**: [Intermittent request rejections](https://status.coveralls.io/incidents/1n7plxrj8j44)\n2. **Aug 14**: [Service unavailable with HTML error page or 500 errors](https://status.coveralls.io/incidents/v5mcbrsbhgt4)\n3. **Aug 18**: [Reports of \"Website under heavy load\" errors](https://status.coveralls.io/incidents/fr6sp5kyn128)\n4. **Aug 19 \\(Today\\)**: [Reports of \"Website under heavy load\" errors](https://status.coveralls.io/incidents/wqbsxnzv0jsf)\n\n\u200c\n\n**Previous postmortem, prior to final resolution:**\n\nWe received customer reports early this morning PDT, Thu, Aug 14, indicating that the [Coveralls.io](http://Coveralls.io) service was unavailable for a substantial period overnight.\n\nWhile our Dequeue Graph appears unresponsive since 18:00 UTC yesterday Aug 13 / 11:00 PDT yesterday, Aug 13, this does not seem to be related to the unavailable period, which appears to have started around 02:00 UTC Aug 14 / 22:00 PDT Aug 13, because we were in service all day and afternoon yesterday, Wed, Aug 13, through EOD PDT.\n\nOur uptime ping did not catch this because Phusion Passenger was returning an HTML error page. Some customers report receiving a 500 error in that message; others report simply receiving HTML as their API response instead of JSON.\n\nWhile we have not seen production bugs specific to the issue, we suspect it\u2019s because the issue occurred at the Passenger/Nginx layer, which simply prevented new traffic since occurring. As far as previously received coverage report uploads, we see successful background processing of jobs in queue all through the evening into this morning.\n\nWe suspect as root cause a regression from a deploy around 5pm yesterday, due mainly to the fact that rolling back to a previous deploy has, so far, resolved the issue.\n\nWe will investigate further to obtain a full understanding of the root cause, but in the meantime, we\u2019ll continue monitoring.\n\nPlease reach out if you are still experiencing any form of error page in Web requests, or any non-200 API response from C[overalls.io.](http://Coveralls.io)\n\nOur apologies for the inconvenience.\n\n**Note**: **Recommended** **Best Practice**: `continue-on-error: true`\n\nAs a general best practice, we recommend adding the **input option** `continue-on-error: true` \\(for [Coveralls GitHub Action](https://github.com/marketplace/actions/coveralls-github-action#inputs)\\), or `continue_on_error: true` \\(for [Coveralls Orb for CircleCI](https://circleci.com/developer/orbs/orb/coveralls/coveralls#commands-upload)\\); or the `--no-fail` **flag** \\(for [Coveralls Universal Coverage Reporter](https://github.com/coverallsapp/coverage-reporter?tab=readme-ov-file#usage)\\), which will keep Coveralls errors from breaking your CI workflows in the future.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-14T07:45:56.622-07:00", "resolved_inferred": false, "started_at": "2025-08-14T07:35:14.384-07:00", @@ -285,7 +285,7 @@ "body": "A postmortem for this incident and its related incidents has been posted [here](https://status.coveralls.io/incidents/wqbsxnzv0jsf):\n\n* [**Postmortem: Reports of \u201cWebsite under heavy load\u201d errors**](https://status.coveralls.io/incidents/wqbsxnzv0jsf)\n\n**Related incidents**\n\n1. **Aug 13**: [Intermittent request rejections](https://status.coveralls.io/incidents/1n7plxrj8j44)\n2. **Aug 14**: [Service unavailable with HTML error page or 500 errors](https://status.coveralls.io/incidents/v5mcbrsbhgt4)\n3. **Aug 18**: [Reports of \"Website under heavy load\" errors](https://status.coveralls.io/incidents/fr6sp5kyn128)\n4. **Aug 19 \\(Today\\)**: [Reports of \"Website under heavy load\" errors](https://status.coveralls.io/incidents/wqbsxnzv0jsf)", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-13T12:24:03.000-07:00", "resolved_inferred": false, "started_at": "2025-08-13T10:14:07.058-07:00", @@ -298,7 +298,7 @@ "body": "We experienced a period of elevated latency due to overnight traffic for about 6 hours today, Fri, Aug 8, from about 1am-7am PDT. We paused a couple of outlier repos, scaled servers to clear a backlog, and resolved ongoing latency. It took approximately 30-min to clear our remaining backlog of background jobs.\n\nWe'd also like to take this opportunity to address a question we get, which is: \n\nQ: \"If the Dequeue Time Graph is missing from the Status Page, does that mean processing has stopped?\"\n\nA: No. While a missing graph can indicate a problem, it\u2019s often isolated to the sampling process itself\u2014either the cron job that collects the data or the single server we currently use for sampling. This \u201cflagship\u201d server runs additional packages and handles control and reporting tasks beyond normal app serving. At times, those extra duties can overload it, causing sampling failures without affecting overall build processing. We plan to broaden our sampling to multiple servers in the future.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-08T08:00:00.000-07:00", "resolved_inferred": false, "started_at": "2025-08-08T01:00:00.000-07:00", @@ -311,7 +311,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-01T06:59:26.279-07:00", "resolved_inferred": false, "started_at": "2025-08-01T06:58:25.914-07:00", diff --git a/api/v/cradlepoint.json b/api/v/cradlepoint.json index f0f1847e55d641be5337494fd47d63cd4135e514..af0a8a9cc4d26e4b7525caf7460c7e8fa5a55d61 100644 --- a/api/v/cradlepoint.json +++ b/api/v/cradlepoint.json @@ -3,7 +3,7 @@ "slug": "cradlepoint", "platform": "statuspage", "status_url": "https://status.cradlepoint.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "maintenance", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-26T09:57:56.780-06:00", "resolved_inferred": false, "started_at": "2026-08-26T07:40:35.170-06:00", @@ -25,7 +25,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-21T22:25:40.895-06:00", "resolved_inferred": false, "started_at": "2026-08-21T14:58:38.095-06:00", @@ -38,7 +38,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-24T06:48:02.683-06:00", "resolved_inferred": false, "started_at": "2026-07-24T05:28:27.505-06:00", @@ -51,7 +51,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-08T18:30:58.000-06:00", "resolved_inferred": false, "started_at": "2026-07-08T16:49:06.278-06:00", @@ -64,7 +64,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-16T09:37:15.921-06:00", "resolved_inferred": false, "started_at": "2026-06-16T09:15:29.731-06:00", @@ -77,7 +77,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-27T14:33:46.322-06:00", "resolved_inferred": false, "started_at": "2026-05-27T13:40:42.779-06:00", @@ -90,7 +90,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-26T19:00:11.916-06:00", "resolved_inferred": false, "started_at": "2026-03-26T15:06:29.044-06:00", @@ -103,7 +103,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-13T16:45:06.398-06:00", "resolved_inferred": false, "started_at": "2026-03-13T16:13:07.706-06:00", @@ -116,7 +116,7 @@ "body": "Oracle has confirmed that issue has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-05T09:32:50.762-07:00", "resolved_inferred": false, "started_at": "2026-03-02T17:34:14.495-07:00", @@ -129,7 +129,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-01T20:23:33.928-07:00", "resolved_inferred": false, "started_at": "2026-03-01T18:46:37.596-07:00", @@ -142,7 +142,7 @@ "body": "This issue has been resolved, and access to Ericsson Enterprise Wireless University is now accessible via NetCloud Manager.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-18T10:26:33.306-07:00", "resolved_inferred": false, "started_at": "2026-02-13T10:58:23.980-07:00", @@ -155,7 +155,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-26T21:38:16.234-07:00", "resolved_inferred": false, "started_at": "2026-01-25T15:08:17.511-07:00", @@ -168,7 +168,7 @@ "body": "The incident with our third party service provider has been resolved and the NetCloud Manager service is operational. We will continue to monitor in case further issues arise.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-18T10:30:25.034-07:00", "resolved_inferred": false, "started_at": "2025-11-18T04:53:04.350-07:00", @@ -181,7 +181,7 @@ "body": "Docker hub issue has been resolved. We have validated SASE network creation and everything looks good.", "first_seen": "2026-09-04T07:06:16Z", "impact": "maintenance", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-24T19:46:22.843-06:00", "resolved_inferred": false, "started_at": "2025-09-24T18:10:32.417-06:00", @@ -194,7 +194,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-02T16:57:50.821-06:00", "resolved_inferred": false, "started_at": "2025-09-02T14:02:38.272-06:00", @@ -207,7 +207,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-21T19:02:14.815-06:00", "resolved_inferred": false, "started_at": "2025-08-21T12:34:39.722-06:00", diff --git a/api/v/crates-io.json b/api/v/crates-io.json index be38e77645c700e1927ae1cfc81b031579c5e0f6..eef76ef7f5469ffeda14fc97aa990b873a293fb9 100644 --- a/api/v/crates-io.json +++ b/api/v/crates-io.json @@ -3,7 +3,7 @@ "slug": "crates-io", "platform": "statuspage", "status_url": "https://status.crates.io", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "This incident has been resolved. Big thanks to Fastly for providing their CDN services and their fast response time!", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-11T15:42:01.184Z", "resolved_inferred": false, "started_at": "2026-07-11T14:22:04.000Z", @@ -25,7 +25,7 @@ "body": "The primary source of the load appears to have been a scraper abusing our API. We have blocked the scraper and the replica database has returned to its normal heavily loaded state instead of being overloaded.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-14T01:53:50.246Z", "resolved_inferred": false, "started_at": "2026-06-14T01:20:20.834Z", @@ -38,7 +38,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-26T17:00:27.438Z", "resolved_inferred": false, "started_at": "2026-05-23T18:47:52.749Z", @@ -51,7 +51,7 @@ "body": "All endpoints are now operational and available again.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-20T16:57:19.107Z", "resolved_inferred": false, "started_at": "2026-05-20T15:52:07.000Z", @@ -64,7 +64,7 @@ "body": "The indexes are now back to normal operations.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-14T23:44:57.045Z", "resolved_inferred": false, "started_at": "2026-04-14T20:48:45.092Z", @@ -77,7 +77,7 @@ "body": "The background worker has caught up, and crate publishes are now updating normally in both indexes.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-12T19:46:22.818Z", "resolved_inferred": false, "started_at": "2026-02-12T19:36:46.793Z", @@ -90,7 +90,7 @@ "body": "Everything continues to look stable, so we can consider this resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-11T01:14:02.937Z", "resolved_inferred": false, "started_at": "2025-11-10T23:56:32.471Z", @@ -103,7 +103,7 @@ "body": "All published crates have been synced to the Git index, and there is now no backlog.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-01T06:38:20.353Z", "resolved_inferred": false, "started_at": "2025-11-01T03:15:57.511Z", @@ -116,7 +116,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-02T23:33:15.769Z", "resolved_inferred": false, "started_at": "2025-09-02T22:48:33.280Z", @@ -129,7 +129,7 @@ "body": "The Git index has caught up and is now up to date.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-13T01:55:33.688Z", "resolved_inferred": false, "started_at": "2025-08-12T21:47:31.000Z", diff --git a/api/v/criteo.json b/api/v/criteo.json index 66c4da1bca0dc79077b2cc09b73da9cfa6185272..de73d5958fcc4ea43f2bb37dfd68284d7b16df66 100644 --- a/api/v/criteo.json +++ b/api/v/criteo.json @@ -3,7 +3,7 @@ "slug": "criteo", "platform": "statuspage", "status_url": "https://status.criteo.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-27T16:37:41.042+02:00", "resolved_inferred": false, "started_at": "2026-08-27T12:57:58.547+02:00", @@ -25,7 +25,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-12T11:24:35.080+02:00", "resolved_inferred": false, "started_at": "2026-08-12T03:15:43.410+02:00", @@ -38,7 +38,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-29T17:15:09.419+02:00", "resolved_inferred": false, "started_at": "2026-07-29T16:50:56.456+02:00", @@ -51,7 +51,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-22T15:14:38.892+02:00", "resolved_inferred": false, "started_at": "2026-07-22T05:10:00.690+02:00", @@ -64,7 +64,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-17T06:51:21.875+02:00", "resolved_inferred": false, "started_at": "2026-07-17T06:19:31.766+02:00", @@ -77,7 +77,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-16T01:53:15.575+02:00", "resolved_inferred": false, "started_at": "2026-07-15T03:08:48.142+02:00", @@ -90,7 +90,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-13T17:30:43.980+02:00", "resolved_inferred": false, "started_at": "2026-07-13T12:22:04.338+02:00", @@ -103,7 +103,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-10T12:35:13.000+02:00", "resolved_inferred": false, "started_at": "2026-07-10T12:21:01.000+02:00", @@ -116,7 +116,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-10T12:37:27.634+02:00", "resolved_inferred": false, "started_at": "2026-07-10T08:11:00.314+02:00", @@ -129,7 +129,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-08T05:35:09.956+02:00", "resolved_inferred": false, "started_at": "2026-07-08T05:01:57.663+02:00", @@ -142,7 +142,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-03T12:17:45.420+02:00", "resolved_inferred": false, "started_at": "2026-07-03T11:18:40.972+02:00", @@ -155,7 +155,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-01T17:05:27.437+02:00", "resolved_inferred": false, "started_at": "2026-06-30T21:02:05.254+02:00", @@ -168,7 +168,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-30T02:33:30.653+02:00", "resolved_inferred": false, "started_at": "2026-06-29T13:08:31.841+02:00", @@ -181,7 +181,7 @@ "body": "Data is now up to date. This incident is resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-29T13:07:00.300+02:00", "resolved_inferred": false, "started_at": "2026-06-29T03:22:02.726+02:00", @@ -194,7 +194,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-18T07:31:32.806+02:00", "resolved_inferred": false, "started_at": "2026-06-18T06:26:20.339+02:00", @@ -207,7 +207,7 @@ "body": "Dear customers, we are pleased to report that the issue has been resolved. All services are functioning normally. Thank you for your patience. If you continue to experience issues, please contact your Criteo representative.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-21T18:22:52.669+02:00", "resolved_inferred": false, "started_at": "2026-05-21T11:35:03.580+02:00", @@ -220,7 +220,7 @@ "body": "Incident has been resolved", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-25T16:51:36.454+02:00", "resolved_inferred": false, "started_at": "2026-04-25T16:21:58.961+02:00", @@ -233,7 +233,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-31T15:55:02.590+02:00", "resolved_inferred": false, "started_at": "2026-03-31T12:43:01.294+02:00", @@ -246,7 +246,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-30T11:21:43.857+02:00", "resolved_inferred": false, "started_at": "2026-03-30T10:56:28.541+02:00", @@ -259,7 +259,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-31T12:41:55.696+02:00", "resolved_inferred": false, "started_at": "2026-03-26T16:58:58.000+01:00", @@ -272,7 +272,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-24T13:42:00.892+01:00", "resolved_inferred": false, "started_at": "2026-03-24T12:41:18.497+01:00", @@ -285,7 +285,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-17T14:16:48.341+01:00", "resolved_inferred": false, "started_at": "2026-03-17T09:15:15.648+01:00", @@ -298,7 +298,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-10T14:53:02.841+01:00", "resolved_inferred": false, "started_at": "2026-03-10T09:52:17.038+01:00", @@ -311,7 +311,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-09T22:36:48.687+01:00", "resolved_inferred": false, "started_at": "2026-03-09T22:22:01.689+01:00", @@ -324,7 +324,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-05T18:15:19.526+01:00", "resolved_inferred": false, "started_at": "2026-03-05T15:54:25.589+01:00", @@ -337,7 +337,7 @@ "body": "Issue has been addressed and is no longer occurring.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-27T18:19:09.032+01:00", "resolved_inferred": false, "started_at": "2026-02-27T00:15:11.528+01:00", @@ -350,7 +350,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-26T15:40:17.495+01:00", "resolved_inferred": false, "started_at": "2026-01-23T22:59:40.116+01:00", @@ -363,7 +363,7 @@ "body": "This issue has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-15T16:31:43.728+01:00", "resolved_inferred": false, "started_at": "2026-01-15T15:59:59.017+01:00", @@ -376,7 +376,7 @@ "body": "Incident is resolved. Any additional lag will be catching up over the next few hours.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-08T20:40:57.720+01:00", "resolved_inferred": false, "started_at": "2026-01-08T17:57:48.192+01:00", @@ -389,7 +389,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-07T01:33:54.339+01:00", "resolved_inferred": false, "started_at": "2026-01-05T22:49:32.129+01:00", @@ -402,7 +402,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-26T14:05:05.273+01:00", "resolved_inferred": false, "started_at": "2025-12-26T07:55:42.201+01:00", @@ -415,7 +415,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-11T23:59:54.385+01:00", "resolved_inferred": false, "started_at": "2025-12-11T17:30:24.000+01:00", @@ -428,7 +428,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-12T15:16:49.500+01:00", "resolved_inferred": false, "started_at": "2025-12-11T11:37:07.000+01:00", @@ -441,7 +441,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-25T19:31:17.623+01:00", "resolved_inferred": false, "started_at": "2025-11-25T19:19:42.800+01:00", @@ -454,7 +454,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-11T14:37:50.638+01:00", "resolved_inferred": false, "started_at": "2025-11-11T10:06:32.200+01:00", @@ -467,7 +467,7 @@ "body": "The fix for the issue affecting Offsite campaign reporting in markets using currencies other than EUR has been successfully deployed to production today.\nFrom now on, newly calculated values for Sales and ROAS will display correctly for all CMax Offsite clients.\n\nPlease note that this was a UI display issue only \u2014 campaign performance, data collection, and delivery were not affected at any point.\n\nThank you for your patience and understanding while we worked to resolve this issue.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-12T18:02:58.483+01:00", "resolved_inferred": false, "started_at": "2025-11-05T18:22:12.000+01:00", @@ -480,7 +480,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-20T12:08:00.946+02:00", "resolved_inferred": false, "started_at": "2025-10-20T11:38:21.959+02:00", @@ -493,7 +493,7 @@ "body": "Resolved \u2013 The issue preventing Admin users from having campaigns and line items auto-approved in Commerce Max and/or Commerce Yield has been fixed.\n\nAll campaign and line item creation should now work as expected.\n\nWe apologize for the disruption and appreciate your patience while we resolved this issue.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-07T20:09:54.383+02:00", "resolved_inferred": false, "started_at": "2025-10-07T12:17:55.689+02:00", @@ -506,7 +506,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-23T17:06:50.630+02:00", "resolved_inferred": false, "started_at": "2025-09-23T12:16:00.077+02:00", @@ -519,7 +519,7 @@ "body": "Our data processing infrastructure was running behind which is causing inaccuracies in the reporting API for Commerce Max and Commerce Yield.\n\nThe issue was resolved and the data is catching up to expected values.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-18T22:59:51.975+02:00", "resolved_inferred": false, "started_at": "2025-09-18T12:22:17.097+02:00", @@ -532,7 +532,7 @@ "body": "Users may have trouble using Commerce Max and/or Commerce Yield component: Analytics Module.\n\nWe have confirmed that the incident is over and that the service is operating normally.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-18T11:59:53.710+02:00", "resolved_inferred": false, "started_at": "2025-09-18T11:05:45.000+02:00", @@ -545,7 +545,7 @@ "body": "This incident has been resolved. There should be no more delays with the RM API.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-15T15:55:33.808+02:00", "resolved_inferred": false, "started_at": "2025-09-11T15:55:50.759+02:00", @@ -558,7 +558,7 @@ "body": "Users may have trouble using Commerce Max and/or Commerce Yield component.\n\nWe have confirmed that the incident is over and that the service is operating normally.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-09T14:31:04.687+02:00", "resolved_inferred": false, "started_at": "2025-09-09T14:16:17.701+02:00", @@ -571,7 +571,7 @@ "body": "Dear customers, The issue impacting Commerce Growth Event Tracking has now been resolved \u2705. The Event Timeline is displaying correctly again. We apologize for the inconvenience this may have caused and thank you for your patience while our team worked on a fix.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-22T14:17:46.426+02:00", "resolved_inferred": false, "started_at": "2025-08-22T14:10:21.851+02:00", @@ -584,7 +584,7 @@ "body": "Users can access the Creative Library again", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-15T23:41:54.688+02:00", "resolved_inferred": false, "started_at": "2025-08-15T13:36:48.624+02:00", @@ -597,7 +597,7 @@ "body": "Users may have trouble using Criteo Retail Media API component (and endpoint if available).\n\nWe have confirmed that the incident is over and that the service is operating normally.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-13T06:04:34.582+02:00", "resolved_inferred": false, "started_at": "2025-08-13T04:39:21.842+02:00", diff --git a/api/v/crucial-hosting.json b/api/v/crucial-hosting.json index 37ab19208306386e71cfce50ee14e850f87a14e3..86494428e5b8e4441d502e5b8e28622a37126cd5 100644 --- a/api/v/crucial-hosting.json +++ b/api/v/crucial-hosting.json @@ -3,7 +3,7 @@ "slug": "crucial-hosting", "platform": "statuspage", "status_url": "https://status.crucial.com.au", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "The issue affecting email delivery and website availability has now been resolved.\n \nOur Engineering Team has confirmed that websites and email services are operating normally.\n \nWe will continue to monitor the services to ensure stability.\n \nWe appreciate your patience and understanding while we worked to address this issue.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "started_at": "2026-09-01T21:30:19.757+10:00", "state": "monitoring", "title": "Service Disruption \u2013 Email Delivery and Website Availability", @@ -23,7 +23,7 @@ "body": "Our phone support lines have now been restored and are fully operational.\n\nOur engineers have completed the necessary work to resolve the issue and are taking steps to help prevent it from happening again.\n\nWe apologize for the inconvenience and appreciate your patience and understanding.\n\nLive Chat Support: Our live chat support remains available 24/7 if you need further assistance.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-14T12:00:06.168+10:00", "resolved_inferred": false, "started_at": "2026-08-14T11:12:51.507+10:00", @@ -36,7 +36,7 @@ "body": "Dear Customers,\n\ncPanel has released a security update to address CVE-2026-58048, a database privilege escalation vulnerability affecting supported cPanel & WHM versions. We strongly recommend that all customers update their servers to the patched versions available.\n\nPlease refer to the official advisories below for more details:\n\nhttps://support.cpanel.net/hc/en-us/articles/42285745783703-Security-CVE-2026-58048-Database-Privilege-Escalation\n\nAction Required \n\nPlease log in to your server via SSH as the root user and run the following command:\n\n/scripts/upcp\n\nThis command will download and install the latest available cPanel & WHM updates, including the security fixes released by cPanel.\n\nAfter the update completes, verify your cPanel version:\n\n/usr/local/cpanel/cpanel -V\n\nWhy This Update required \n\nThis security release addresses a vulnerability that could allow privilege escalation within the database environment. Applying the latest cPanel update is the recommended mitigation from cPanel and helps protect your server from potential exploitation.\n\nIf you are unable to perform the update or experience any issues during the upgrade process, please contact our support team. We will be happy to assist you.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "started_at": "2026-08-03T20:30:59.778+10:00", "state": "monitoring", "title": "Security Advisory: Immediate cPanel Update Recommended for VPS & Dedicated Servers", @@ -47,7 +47,7 @@ "body": "The issue affecting the email services, along with webmail access, has now been resolved. Our Engineering Team will continue to closely monitor the situation to ensure ongoing stability.\nWe appreciate your patience and understanding while we worked to address this matter. Please be assured that we will continue to provide updates should any new developments arise.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-03T20:22:30.900+10:00", "resolved_inferred": false, "started_at": "2026-07-31T11:50:55.439+10:00", @@ -60,7 +60,7 @@ "body": "The issue affecting email delivery to Hotmail domains has been resolved, and email delivery has returned to normal.\n\nOur Engineering Team has completed the necessary work, and we are no longer observing the reported delivery issue.\n\nThank you for your patience and understanding while we worked to resolve this issue.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-12T21:38:43.095+10:00", "resolved_inferred": false, "started_at": "2026-07-29T22:13:08.588+10:00", @@ -73,7 +73,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-29T22:20:44.215+10:00", "resolved_inferred": false, "started_at": "2026-07-21T14:09:38.319+10:00", @@ -86,7 +86,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-29T22:58:53.822+10:00", "resolved_inferred": false, "started_at": "2026-06-15T08:39:52.310+10:00", @@ -99,7 +99,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-29T22:59:13.925+10:00", "resolved_inferred": false, "started_at": "2026-06-05T14:00:48.568+10:00", @@ -112,7 +112,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-29T22:59:36.387+10:00", "resolved_inferred": false, "started_at": "2026-05-18T14:06:24.155+10:00", @@ -125,7 +125,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-29T22:59:55.390+10:00", "resolved_inferred": false, "started_at": "2026-05-09T03:44:16.155+10:00", @@ -138,7 +138,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-29T22:58:24.704+10:00", "resolved_inferred": false, "started_at": "2026-05-08T16:59:05.298+10:00", @@ -151,7 +151,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-29T22:21:11.537+10:00", "resolved_inferred": false, "started_at": "2026-04-29T16:34:42.022+10:00", @@ -164,7 +164,7 @@ "body": "Restore for vmsh02.performance-hosting.com.au has been completed successfully\nAll the affected servers are now up and running", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-24T23:28:51.512+10:00", "resolved_inferred": false, "started_at": "2025-09-22T11:22:40.007+10:00", diff --git a/api/v/crypto-com.json b/api/v/crypto-com.json index 5056ee26f99a634f9b67780d477959a575ca0c73..6cdd18033b4bded16d197f0999bcda4d2c3b4504 100644 --- a/api/v/crypto-com.json +++ b/api/v/crypto-com.json @@ -3,7 +3,7 @@ "slug": "crypto-com", "platform": "statuspage", "status_url": "https://status.crypto.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-27T08:11:54.615+08:00", "resolved_inferred": false, "started_at": "2026-08-27T08:03:22.955+08:00", @@ -25,7 +25,7 @@ "body": "New TON staking requests are temporarily unavailable. Existing staked positions are unaffected and continue to earn rewards. Unstaking remains available but may take longer than usual to process. We apologise for any inconvenience this may cause.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "started_at": "2026-08-26T14:55:45.194+08:00", "state": "investigating", "title": "TON Staking Temporary Service Disruption", @@ -36,7 +36,7 @@ "body": "EGLD staking operations and reward distributions are resumed", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-26T17:52:23.104+08:00", "resolved_inferred": false, "started_at": "2026-08-13T15:22:30.000+08:00", @@ -49,7 +49,7 @@ "body": "Deposits and Withdrawals of ONE, ORAI, RAVEN have been paused due to ongoing security concern", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "started_at": "2026-08-12T16:06:31.213+08:00", "state": "investigating", "title": "ONE, ORAI, RAVEN Deposits/Withdrawals Temporarily Suspended", @@ -60,7 +60,7 @@ "body": "Crypto deposit & withdrawal services are resumed", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-02T16:03:23.998+08:00", "resolved_inferred": false, "started_at": "2026-08-02T12:49:08.101+08:00", @@ -73,7 +73,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-31T15:03:18.716+08:00", "resolved_inferred": false, "started_at": "2026-07-31T13:32:36.000+08:00", @@ -86,7 +86,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-24T13:20:09.145+08:00", "resolved_inferred": false, "started_at": "2026-07-23T15:41:54.668+08:00", @@ -99,7 +99,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-08T11:28:23.869+08:00", "resolved_inferred": false, "started_at": "2026-07-07T23:33:14.000+08:00", @@ -112,7 +112,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-26T09:37:11.845+08:00", "resolved_inferred": false, "started_at": "2026-06-26T02:37:23.703+08:00", @@ -125,7 +125,7 @@ "body": "The Crypto.com Pay on-ramp service is currently unavailable due to ongoing maintenance. We will provide an update as soon as service is restored. We apologize for any inconvenience this may cause.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "started_at": "2026-06-09T19:36:38.002+08:00", "state": "investigating", "title": "Crypto.com Pay-on-ramp service maintenance", @@ -136,7 +136,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-29T15:10:30.754+08:00", "resolved_inferred": false, "started_at": "2026-05-28T23:20:25.150+08:00", @@ -149,7 +149,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-11T15:44:36.741+08:00", "resolved_inferred": false, "started_at": "2026-05-27T15:11:19.783+08:00", @@ -162,7 +162,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-22T21:12:19.001+08:00", "resolved_inferred": false, "started_at": "2026-05-22T15:59:03.000+08:00", @@ -175,7 +175,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-17T15:36:16.826+08:00", "resolved_inferred": false, "started_at": "2026-05-19T00:09:48.276+08:00", @@ -188,7 +188,7 @@ "body": "Deposits and Withdrawals of RUNE have been resumed.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-27T12:31:10.876+08:00", "resolved_inferred": false, "started_at": "2026-05-15T22:07:00.207+08:00", @@ -201,7 +201,7 @@ "body": "FLR Staking has been resumed.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-02T18:08:06.908+08:00", "resolved_inferred": false, "started_at": "2026-05-14T16:15:33.675+08:00", @@ -214,7 +214,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-01T21:40:06.947+08:00", "resolved_inferred": false, "started_at": "2026-05-01T20:35:04.000+08:00", @@ -227,7 +227,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-30T18:35:37.297+08:00", "resolved_inferred": false, "started_at": "2026-04-30T00:34:39.426+08:00", @@ -240,7 +240,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-29T16:33:29.300+08:00", "resolved_inferred": false, "started_at": "2026-04-29T14:11:55.242+08:00", @@ -253,7 +253,7 @@ "body": "This incident has been resolved and LTC deposit features have been reestablished.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-26T09:51:47.998+08:00", "resolved_inferred": false, "started_at": "2026-04-26T09:05:30.078+08:00", @@ -266,7 +266,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-18T19:46:04.959+08:00", "resolved_inferred": false, "started_at": "2026-04-18T00:59:03.895+08:00", @@ -279,7 +279,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-18T01:04:55.067+08:00", "resolved_inferred": false, "started_at": "2026-04-17T02:26:44.987+08:00", @@ -292,7 +292,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-07T00:40:53.482+08:00", "resolved_inferred": false, "started_at": "2026-04-06T18:01:53.000+08:00", @@ -305,7 +305,7 @@ "body": "This incident has beer resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-02T11:44:46.751+08:00", "resolved_inferred": false, "started_at": "2026-04-02T10:30:46.115+08:00", @@ -318,7 +318,7 @@ "body": "The wait can be up to 70 days. For more information on latest ETH Validator queue backlog, please check here: https://www.validatorqueue.com/", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "started_at": "2026-03-21T16:49:18.000+08:00", "state": "identified", "title": "ETH staking process delayed", @@ -329,7 +329,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-21T01:15:15.017+08:00", "resolved_inferred": false, "started_at": "2026-03-21T00:11:56.000+08:00", @@ -342,7 +342,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-18T13:41:21.866+08:00", "resolved_inferred": false, "started_at": "2026-03-18T13:40:55.579+08:00", @@ -355,7 +355,7 @@ "body": "The incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-15T16:35:54.000+08:00", "resolved_inferred": false, "started_at": "2026-03-15T12:04:37.305+08:00", @@ -368,7 +368,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-13T14:29:41.263+08:00", "resolved_inferred": false, "started_at": "2026-03-12T21:04:07.390+08:00", @@ -381,7 +381,7 @@ "body": "Issue has been resolved and FLR staking has been resumed.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-27T18:12:14.034+08:00", "resolved_inferred": false, "started_at": "2026-03-03T11:36:21.586+08:00", @@ -394,7 +394,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-25T06:12:41.741+08:00", "resolved_inferred": false, "started_at": "2026-02-25T02:52:42.616+08:00", @@ -407,7 +407,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-20T05:42:43.315+08:00", "resolved_inferred": false, "started_at": "2026-02-20T03:29:15.472+08:00", @@ -420,7 +420,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-05T18:58:51.885+08:00", "resolved_inferred": false, "started_at": "2026-02-02T18:43:31.106+08:00", @@ -433,7 +433,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-31T22:33:56.032+08:00", "resolved_inferred": false, "started_at": "2026-01-31T21:03:05.629+08:00", @@ -446,7 +446,7 @@ "body": "All FLR staking services are recovered", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-12T14:32:14.234+08:00", "resolved_inferred": false, "started_at": "2026-01-27T18:43:28.964+08:00", @@ -459,7 +459,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-25T05:55:03.320+08:00", "resolved_inferred": false, "started_at": "2026-01-25T03:21:47.679+08:00", @@ -472,7 +472,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-17T00:04:52.463+08:00", "resolved_inferred": false, "started_at": "2026-01-17T00:01:15.256+08:00", @@ -485,7 +485,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-16T02:07:19.433+08:00", "resolved_inferred": false, "started_at": "2025-12-16T00:59:04.738+08:00", @@ -498,7 +498,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-19T12:30:01.989+08:00", "resolved_inferred": false, "started_at": "2025-12-15T14:01:31.776+08:00", @@ -511,7 +511,7 @@ "body": "Cloudflare team confirm the issue is resolved\nOur services are resumed", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-05T17:20:40.553+08:00", "resolved_inferred": false, "started_at": "2025-12-05T17:07:24.717+08:00", @@ -524,7 +524,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-30T05:43:02.064+08:00", "resolved_inferred": false, "started_at": "2025-11-30T04:21:42.433+08:00", @@ -537,7 +537,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-27T16:47:18.663+08:00", "resolved_inferred": false, "started_at": "2025-11-27T01:11:46.000+08:00", @@ -550,7 +550,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-18T22:35:40.844+08:00", "resolved_inferred": false, "started_at": "2025-11-18T21:58:09.000+08:00", @@ -563,7 +563,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-18T22:35:53.714+08:00", "resolved_inferred": false, "started_at": "2025-11-18T20:01:35.000+08:00", @@ -576,7 +576,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-09T15:22:07.545+08:00", "resolved_inferred": false, "started_at": "2025-11-09T13:21:01.862+08:00", @@ -589,7 +589,7 @@ "body": "Sign up via exchange app is resumed", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-04T13:27:22.000+08:00", "resolved_inferred": false, "started_at": "2025-11-04T12:04:32.583+08:00", @@ -602,7 +602,7 @@ "body": "KSM Staking has been resumed.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-10T10:04:33.741+08:00", "resolved_inferred": false, "started_at": "2025-10-09T17:39:46.795+08:00", @@ -615,7 +615,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-07T17:28:53.360+08:00", "resolved_inferred": false, "started_at": "2025-09-17T19:58:43.814+08:00", @@ -628,7 +628,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-06T22:33:08.975+08:00", "resolved_inferred": false, "started_at": "2025-09-10T22:55:59.613+08:00", @@ -641,7 +641,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-06T22:33:19.887+08:00", "resolved_inferred": false, "started_at": "2025-09-09T13:30:40.000+08:00", diff --git a/api/v/cumulocity.json b/api/v/cumulocity.json index 971df47e90b17dfbf898b758cd57323e34505a56..cbfcec6a644a8158a4b0982d6f81576adee5e274 100644 --- a/api/v/cumulocity.json +++ b/api/v/cumulocity.json @@ -3,7 +3,7 @@ "slug": "cumulocity", "platform": "instatus", "status_url": "http://status.cumulocity.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": false, "first_watched": "2026-09-04T07:06:16Z", @@ -11,7 +11,7 @@ { "first_seen": "2026-09-04T07:06:16Z", "impact": "MAJOROUTAGE", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "started_at": "2026-08-31T08:11:00.000Z", "state": "monitoring", "title": "Platform Issue | CUMULOCITY.COM", diff --git a/api/v/currents.json b/api/v/currents.json index 6628788b8567650be38938446bd8c86f1337af64..37c792e8fe22029fe1882bff89ba933a697e0563 100644 --- a/api/v/currents.json +++ b/api/v/currents.json @@ -3,7 +3,7 @@ "slug": "currents", "platform": "instatus", "status_url": "https://currents.instatus.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": false, "first_watched": "2026-09-04T07:06:16Z", diff --git a/api/v/cybersmart.json b/api/v/cybersmart.json index 1d30879ad1bf7e31d4ecf4acd68820962a15b7d3..34ec1bd69f9c1a8c8a47aa93efa485d83967e445 100644 --- a/api/v/cybersmart.json +++ b/api/v/cybersmart.json @@ -3,7 +3,7 @@ "slug": "cybersmart", "platform": "statuspage", "status_url": "https://status.cybersmart.co.uk", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-18T15:43:06.324+00:00", "resolved_inferred": false, "started_at": "2025-11-18T12:27:20.667+00:00", diff --git a/api/v/cycode.json b/api/v/cycode.json index 29efa8fdc860554074ed4fca46e21bda15a3c611..293549e5bf958e831c867499060b36e0cb4d77f0 100644 --- a/api/v/cycode.json +++ b/api/v/cycode.json @@ -3,7 +3,7 @@ "slug": "cycode", "platform": "statuspage", "status_url": "https://status.cycode.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "GitHub component: Pull Requests\nOriginal GitHub incident: https://stspg.io/0xbhhq84v4mt", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-09-01T16:05:06Z", "resolved_inferred": false, "started_at": "2026-09-01T15:10:38Z", @@ -24,7 +24,7 @@ "body": "GitHub component: Pull Requests\nOriginal GitHub incident: https://stspg.io/nrbwjftcz72d", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-27T00:30:26Z", "resolved_inferred": false, "started_at": "2026-08-26T23:04:59Z", @@ -36,7 +36,7 @@ "body": "The system is back to being fully operational.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-20T16:36:59Z", "resolved_inferred": false, "started_at": "2026-08-20T14:52:37Z", @@ -48,7 +48,7 @@ "body": "**1. Summary**\n\nOn August 19, 2026, some customers experienced slower page loading and data display, as well as delays when starting or completing pull request scans. \n\nThe disruption was caused by a managed memory database entering a repeated restart cycle and not recovering automatically. This created a temporary slowdown in processing. Expected service behavior was restored after corrective actions, including replacement and increased capacity for the affected service. The provider is continuing to investigate why the service was unable to return to normal operation automatically.\n\n**2. Key Timeline (IDT)**\n\n\u2022 August 19, 2026, 16:10 IDT: We identified performance degradation affecting parts of the platform and pull request scanning.\n\n\u2022 August 19, 2026, 16:30 IDT: An initial corrective change was applied and service behavior was monitored.\n\n\u2022 August 19, 2026, 16:46 IDT: We confirmed that some delays were continuing and expanded the investigation.\n\n\u2022 August 19, 2026, 17:14 IDT: We began working with our service provider to investigate instability in the managed memory database.\n\n\u2022 August 19, 2026, 18:46 IDT: Recovery actions were in progress, with temporary mitigations in place to reduce customer impact.\n\n\u2022 August 19, 2026, 19:06 IDT: The managed memory database capacity update completed, and platform responsiveness and pull request scanning returned to expected behavior.\n\n**3. Root Cause**\n\nThe managed memory database entered a repeated restart cycle and was unable to recover automatically. This caused delays in the processing systems that support platform responsiveness and pull request scans.\n\nThe affected service underwent a routine replacement process, followed by a capacity increase during the recovery effort. While the capacity increase completed successfully and restored expected behavior, AWS is still researching why the service did not come back up normally after the restart cycle. Their detailed root-cause analysis is pending.\n\n**4. Actions Taken**\n\n\u2022 Applied corrective updates to reduce immediate processing demand.\n\n\u2022 Temporarily adjusted the status update process to reduce reliance on the affected service.\n\n\u2022 Restarted affected processing components to restore responsiveness.\n\n\u2022 Worked with the service provider to replace affected capacity and complete a capacity increase.\n\n\u2022 Monitored platform performance and scan processing until expected behavior was confirmed.\n\n**4b. Action Items**\n\n\u2022 Review the service provider\u2019s detailed root-cause analysis when available.\n\n\u2022 Improve monitoring to detect similar recovery delays earlier.\n\n\u2022 Add safeguards to reduce the impact of temporary processing slowdowns.\n\n\u2022 Introduce separate Redis capacity for each service to isolate workloads and reduce the impact of an issue in one service on others.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-19T18:06:00Z", "resolved_inferred": false, "started_at": "2026-08-19T13:18:38Z", @@ -60,7 +60,7 @@ "body": " \n\nSome GitHub pull request status checks in the EU region were delayed by up to 30 minutes before completing. \n\nNo checks were lost and no action is needed - delayed checks completed automatically. We identified the cause, and fixed it. We're monitoring closely.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-18T08:31:00Z", "resolved_inferred": false, "started_at": "2026-08-18T14:34:21Z", @@ -72,7 +72,7 @@ "body": "GitHub component: Git Operations, Webhooks, API Requests, Pull Requests\nOriginal GitHub incident: https://stspg.io/y1fl26l6wpzr", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-17T21:21:14Z", "resolved_inferred": false, "started_at": "2026-08-17T13:44:06Z", @@ -84,7 +84,7 @@ "body": "**Summary**\n\nPR secret scans experienced processing lag, causing delays in processing pull requests.\n\nThe issue was caused by timeouts when calling the model validation service. The model validation service was experiencing elevated latency and errors because compute nodes were scheduled on a subnet that had exhausted its available IPs.\n\nThis slowed PR secret scan processing and caused consumer lag to build up.\n\nTo resolve the issue, we temporarily disabled the feature that produces new PR secret scans so the queue could drain. We also resolved the underlying infrastructure issue by moving nodes to subnets with available free IPs.\n\n**Customer Impact**\n\nCustomers experienced delayed PR secret scans.\n\nOther scan types remained operational.\n\n**Root Cause**\n\nThe secret scanner calls the AI model validation service to classify detections during PR scans.\n\nThe model validation call had a 30-second timeout configured. When the model validation service became slow or unresponsive, each failed request could block a scan consumer for the full 30 seconds before timing out.\n\nThe underlying issue was in the model-serving infrastructure. One of the private subnets had run out of available IPs, and new nodes were created in that exhausted subnet, leaving model-serving pods in a pending state.\n\nThis resulted in elevated latency and errors in the model validation service and reduced the processing capacity of PR secret scans.\n\n**Contributing Factors**\n\n\u2022 **Model validation timeouts.** The model validation service timeout was 30 seconds. When the service was degraded, scan consumers waited for the full timeout before the request failed, which created a processing bottleneck.\n\n\u2022 **No fallback to bypass AI validation for PR scans.** There was no mechanism to skip AI model validation specifically for PR secret scans while allowing the rest of the scan to continue. The available kill switch stopped producing PR secret scans entirely. This meant the mitigation required a tradeoff between allowing processing lag to continue or temporarily stopping PR secret scans.\n\n\u2022 **Customer communication gap.** Internal alerts for PR scan lag did fire, but the status page was not updated promptly to reflect the degradation. As a result, there was a period in which we had internal visibility into the issue while customers did not have the same visibility through the status page.\n\n**Mitigation and Recovery**\n\nA pre-existing feature flag was used to stop new PR secret scans from being produced.\n\nThis stopped new messages from being added to the PR secret scan queue and allowed the existing backlog to drain.\n\nThe backlog was cleared shortly after the mitigation was enabled.\n\nIn parallel, the underlying model-serving infrastructure issue was resolved by moving nodes to subnets with available free IPs, restoring model-serving capacity.\n\nOnce the infrastructure issue was resolved and the backlog had drained, PR secret scanning was restored.\n\n**Learnings and Corrective Actions**\n\n\u2022 **Review the AI model validation timeout.** The 30-second model validation timeout meant that when the model-serving layer degraded, each scan consumer could remain blocked for the full timeout before failing. We are reviewing the timeout and retry behavior. This work must also account for the risk that shorter timeouts and faster retries could increase request volume against an already degraded model-serving service.\n\n\u2022 **Add a graceful degradation path for AI validation.** The system currently has a kill switch for PR secret scanning, but does not have a graceful degradation mechanism for the AI validation step. We are working on a mechanism that can disable AI model calls specifically for PR scans, allowing scans to continue while avoiding the dependency on a degraded model-serving layer. The goal is to allow scans to continue with reduced functionality rather than stopping PR secret scanning entirely.\n\n\u2022 **Improve alerting and incident communication.** The alerting infrastructure detected PR scan lag, but the status page was not updated promptly. We are improving the process for escalating service degradation and communicating customer-facing impact through the status page.\n\n\u2022 **Improve model-serving infrastructure resilience.** The underlying infrastructure issue occurred because nodes were scheduled on a subnet with no available IPs. The immediate issue was resolved by moving nodes to subnets with free IPs. We are continuing to improve the resilience of the model-serving infrastructure to reduce the likelihood that infrastructure capacity issues can affect PR scan processing.\n\n**Conclusion**\n\nThe incident was caused by degradation in the AI model validation service due to an infrastructure issue where nodes were scheduled on a subnet with exhausted IP capacity.\n\nThe resulting model validation timeouts slowed PR secret scan processing and caused consumer lag to build.\n\nWe mitigated the incident by temporarily stopping new PR secret scans, allowing the backlog to drain, and restoring model-serving capacity by moving nodes to subnets with available free IPs.\n\nWe are following up with improvements to model-serving resilience, timeout and retry behavior, runtime configuration, graceful degradation, alerting, and customer communication.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-14T16:14:19Z", "resolved_inferred": false, "started_at": "2026-08-14T13:41:27Z", @@ -96,7 +96,7 @@ "body": "GitHub component: Git Operations, Webhooks, Pull Requests\nOriginal GitHub incident: https://stspg.io/f0cgtdc0kqxg", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-13T15:39:18Z", "resolved_inferred": false, "started_at": "2026-08-13T14:53:48Z", @@ -108,7 +108,7 @@ "body": "GitHub component: Pull Requests\nOriginal GitHub incident: https://stspg.io/ssd9z8l2g46v", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-12T16:42:12Z", "resolved_inferred": false, "started_at": "2026-08-12T16:25:59Z", @@ -120,7 +120,7 @@ "body": "GitHub component: API Requests\nOriginal GitHub incident: https://stspg.io/3xn46bst0bjh", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-11T20:10:19Z", "resolved_inferred": false, "started_at": "2026-08-11T14:55:27Z", @@ -132,7 +132,7 @@ "body": "**Root Cause**\n\nThe incident was caused by a deployment of one service that ran a database index creation. The team has identified an issue with the way we perform index creations as database migrations. \n\nDuring a deployment the pods with newest image of the service attempted to create an index on a big table. The team has identified that the index creation took 7 minutes. However, during index creation pods were not responsive, and as a result, Kubernetes deemed them as unhealthy pods and attempted to retry those pods after 5 minutes.\n\nAs a result, because the pod got killed before the index creation was fully completed, the database transaction was rolled back. Then, subsequent pods attempted to create the index again, dying after 5 minutes.\n\nThis lead to the database being in unhealthy state, and the service was down. \n\nThe team has rolled back the deployment, and killed all replicas that attempted to create the index. Thanks to that, the service and the database was in healthy state again.\n\n \n\n**Why safety measures did not help**\n\nCycode provides a safety mechanism that unblocks all Pull Request scans after a specific period of time, giving each scan a maximum duration before the Pull Request is unblocked. However, because the service that is responsible for triggering and completing scans, as well as this safety net, was down, the process couldn't behave as expected. We acknowledge this gap and are working on strengthening this area of our system.\n\n \n\n**Action items**\n\n\u2022 The team is actively investigating enhancements and new safety protocols that can be put in place in order to have another safety net preventing Pull Request scans being stuck in case of any incident.\n\n\u2022 The team is investigating changes to the index creation process.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-10T15:45:54Z", "resolved_inferred": false, "started_at": "2026-08-10T14:06:34Z", @@ -144,7 +144,7 @@ "body": "The platform is now fully operational and processing normally", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-04T06:08:42Z", "resolved_inferred": false, "started_at": "2026-08-02T14:08:56Z", @@ -156,7 +156,7 @@ "body": "**Root Cause**\n\nThe incident was caused by a deployment of one service that ran a database migration. The team has identified that this migration contained faulty code and as a result lead to database overload when attempting to deploy the service. As a result, the service was partially down until the deployment was reverted. During this time, all scans were processed with lower than expected performance.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-27T11:57:22Z", "resolved_inferred": false, "started_at": "2026-07-27T10:31:15Z", @@ -168,7 +168,7 @@ "body": "GitHub component: API Requests\nOriginal GitHub incident: https://stspg.io/vr201n49yl53", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-27T04:12:43Z", "resolved_inferred": false, "started_at": "2026-07-27T03:56:45Z", @@ -180,7 +180,7 @@ "body": "GitHub component: Pull Requests\nOriginal GitHub incident: https://stspg.io/sm1tp7kfm4vj", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-24T20:26:37Z", "resolved_inferred": false, "started_at": "2026-07-24T19:40:50Z", @@ -192,7 +192,7 @@ "body": "The issue has been resolved, and we are continuing to monitor the situation.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-24T21:58:42Z", "resolved_inferred": false, "started_at": "2026-07-24T17:45:35Z", @@ -204,7 +204,7 @@ "body": "GitHub component: API Requests, Pull Requests\nOriginal GitHub incident: https://stspg.io/j5c80shxqm53", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-24T17:40:25Z", "resolved_inferred": false, "started_at": "2026-07-24T16:21:08Z", @@ -216,7 +216,7 @@ "body": "GitHub component: Webhooks, Pull Requests\nOriginal GitHub incident: https://stspg.io/syhr80rth84z", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-23T09:39:23Z", "resolved_inferred": false, "started_at": "2026-07-23T07:58:43Z", @@ -228,7 +228,7 @@ "body": "The incident has been resolved, and the platform is operating normally.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-16T20:05:34Z", "resolved_inferred": false, "started_at": "2026-07-16T18:56:47Z", @@ -240,7 +240,7 @@ "body": "A fix has been applied and functionality is fully restored; we are continuing to monitor to ensure everything remains stable.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-15T19:07:05Z", "resolved_inferred": false, "started_at": "2026-07-15T17:22:05Z", @@ -252,7 +252,7 @@ "body": "We\u2019re continuing to monitor detection processing and the associated delays in violation status updates (including auto-resolution)", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-14T21:23:08Z", "resolved_inferred": false, "started_at": "2026-07-14T16:12:50Z", @@ -264,7 +264,7 @@ "body": "The system is now fully operational. There should be no more degraded performance.\n\n \n\n**Summary**\nWe observed a period of slowness and intermittent timeouts affecting various system functions in the EU region, including the application interface and pull request (PR) scans. The issue was primarily caused by a processing system reaching its network and memory capacity limits, exacerbated by a high volume of automated activity from a single source. We have since upgraded the underlying infrastructure and implemented safeguards to prevent similar high-volume activity from impacting the system. The issue is now fully resolved, and all services have returned to expected performance levels.\n\n**Key Timeline (IDT)**\n\n\u2022 **July 13, 2026, 11:44 IDT**: Incident detected following reports of UI slowness and PR scan delays.\n\n\u2022 **July 13, 2026, 12:19 IDT**: Infrastructure bottleneck identified; decision made to upgrade the processing cluster.\n\n\u2022 **July 13, 2026, 12:26 IDT**: A high-volume automated process was identified and disabled to reduce immediate load.\n\n\u2022 **July 13, 2026, 13:09 IDT**: Infrastructure upgrade completed; network throughput returned to normal levels.\n\n\u2022 **July 13, 2026, 15:35 IDT**: All backlogs cleared, and the incident was officially resolved.\n\n**Root Cause**\nThe incident was triggered by a combination of factors: a processing cluster reached its maximum network bandwidth and memory capacity due to an undersized configuration for the current workload. This was further strained by a specific automated workflow that generated an unusually high volume of update requests. Additionally, a configuration difference in the message processing pipeline in the EU region prevented the system from effectively handling the resulting backlog.\n\n**Actions Taken**\n\n\u2022 **Upgraded Infrastructure**: The processing cluster was upgraded to a higher-capacity instance type to provide more network bandwidth and memory.\n\n\u2022 **Disabled High-Volume Source**: A specific client identifier responsible for excessive traffic was temporarily disabled to restore system stability.\n\n\u2022 **Restored Connectivity**: Affected service components were restarted to ensure they re-established clean connections to the upgraded infrastructure.\n\n\u2022 **Increased Processing Parallelism**: The number of partitions in the affected message queue was increased to allow the system to process the backlog more quickly.\n\n**Action Items**\n\n\u2022 **Enhance Monitoring**: Implement new alerts for network and memory utilization to detect capacity issues before they impact customers.\n\n\u2022 **Optimize Update Workflow**: Refactor the status update process to batch requests, significantly reducing the load on the processing system.\n\n\u2022 **Implement Rate Limiting**: Introduce safeguards to prevent any single source from consuming disproportionate system resources.\n\n\u2022 **Standardize Regional Configurations**: Conduct an audit to ensure infrastructure and message queue settings are consistent across all regions.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-13T12:36:21Z", "resolved_inferred": false, "started_at": "2026-07-13T08:47:48Z", @@ -276,7 +276,7 @@ "body": "Functionality is fully restored; we are continuing to monitor to ensure everything remains stable.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-17T16:58:39Z", "resolved_inferred": false, "started_at": "2026-07-09T10:54:26Z", @@ -288,7 +288,7 @@ "body": "The issue affecting Maestro AI services has been resolved. Maestro Risk Explorability, Risk AI Remediation, Maestro Remediation, and Graph AI are now available and operating normally.\n\n \n\n**Summary**\n\nOn July 9, 2026, customers using the Maestro service in the European production environment experienced a period of service unavailability. The issue began following a configuration update that inadvertently changed the service's regional routing. This caused the system to attempt connections through a network path that lacked the necessary permissions and to a region where specific processing models were unavailable. The issue has been fully resolved, and service has been restored to all affected customers.\n\n**Key Timeline (IDT)**\n\n\u2022 **July 9, 2026, 12:02 IDT:** The incident was identified and an investigation was initiated.\n\n\u2022 **July 9, 2026, 12:07 IDT:** Public notification was issued regarding the service interruption.\n\n\u2022 **July 9, 2026, 13:00 IDT:** A network configuration fix was applied, restoring primary connectivity.\n\n\u2022 **July 9, 2026, 13:39 IDT:** Service was fully restored after implementing model fallbacks, and the incident was marked as resolved.\n\n**Root Cause**\n\nThe service interruption was triggered by a recent update to the authentication and configuration process. This update introduced a conflict in how the system identified its operating region. Specifically, an automated update process overrode manual settings, routing traffic to a different regional endpoint. This new path was blocked by a missing network security rule and attempted to use a processing model that was not supported in that specific region, leading to service failure.\n\n**Actions Taken**\n\n\u2022 **Restored Network Connectivity:** Manually updated network security rules to allow secure traffic through the new regional endpoint.\n\n\u2022 **Implemented Model Fallbacks:** Configured the system to use alternative processing models to ensure immediate service availability while long-term regional configurations were adjusted.\n\n\u2022 **Updated Status Communications:** Maintained real-time updates for stakeholders and customers throughout the recovery process.\n\n**Action Items**\n\n\u2022 **Standardize Configuration Precedence:** Update the deployment workflow to prevent automated processes from silently overriding critical environment settings.\n\n\u2022 **Infrastructure Audit:** Conduct a comprehensive review of network security rules across all regions to ensure consistency and prevent similar connectivity gaps.\n\n\u2022 **Enhance Automated Monitoring:** Implement end-to-end health checks and synthetic probes to detect regional connectivity issues automatically before they impact users.\n\n\u2022 **Improve Deployment Policies:** Establish new guidelines to ensure that configuration changes are deployed and validated in production-like environments more frequently to reduce the risk of \"stale\" updates.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-09T10:39:50Z", "resolved_inferred": false, "started_at": "2026-07-09T09:07:18Z", @@ -300,7 +300,7 @@ "body": "AWS has confirmed that the issue has been fully mitigated and we are currently not observing any related issues.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-06T15:08:14Z", "resolved_inferred": false, "started_at": "2026-07-06T12:52:03Z", diff --git a/api/v/cypress.json b/api/v/cypress.json index d9435975dcab72e7a31d43c177e57a4028460cd5..60d875f8dd682b3f92765d40fcc460b987860a17 100644 --- a/api/v/cypress.json +++ b/api/v/cypress.json @@ -3,7 +3,7 @@ "slug": "cypress", "platform": "statuspage", "status_url": "https://status.cypress.io", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "unknown", "history_backfilled": false, "first_watched": "2026-09-04T07:06:16Z", diff --git a/api/v/dashlane.json b/api/v/dashlane.json index d21e97cc08c93cdaf64fc5444d3aa51a6bc01be3..8def9c54d08f43e54b717f89b04ddb8b2cc47b12 100644 --- a/api/v/dashlane.json +++ b/api/v/dashlane.json @@ -3,7 +3,7 @@ "slug": "dashlane", "platform": "status.io", "status_url": "https://status.dashlane.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": false, "first_watched": "2026-09-04T07:06:16Z", @@ -11,7 +11,7 @@ { "body": "We have received reports from several users having received an email that their account has been suspended. We have also received reports that some users are experiencing difficulties in logging in to Dashlane after resetting their master password.\r\n\r\nWe are investigating this situation, and we will provide further updates as soon as we have more information. Thank you for your understanding.", "first_seen": "2026-09-04T07:06:16Z", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "started_at": "2026-05-31T15:19:56.948Z", "state": "investigating", "title": "Investigating Unexpected Account Notifications and Login Issues", diff --git a/api/v/databox.json b/api/v/databox.json index 01ed11f6112af38b3fd5027efee84e8cc5ffe697..3e4fe608a71de3ae872c5d6a88597ef8e7fda04a 100644 --- a/api/v/databox.json +++ b/api/v/databox.json @@ -3,7 +3,7 @@ "slug": "databox", "platform": "statuspage", "status_url": "https://status.databox.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "The GitHub integration is fully available again.\n\nAs part of restoring the integration, we also introduced security improvements that give customers more control over which repositories Databox can access.\n\nExisting connections can be reconnected, and historical metric data remains available. Data from the period while the integration was unavailable may be incomplete.\n\nThank you for your patience.\n\nIf you have any questions, please reach out to our Support team via chat or help@databox.com.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-19T10:07:59.369-04:00", "resolved_inferred": false, "started_at": "2026-08-16T09:27:42.000-04:00", @@ -25,7 +25,7 @@ "body": "The application was unreachable due to a global Amazon Web Services outage. The issue is now resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-16T06:28:01.103-04:00", "resolved_inferred": false, "started_at": "2026-07-16T04:18:44.000-04:00", @@ -38,7 +38,7 @@ "body": "We experienced an issue affecting the delivery of scheduled Scorecards. During this incident, some Scorecards were delayed and were not sent as expected between Friday, 16:00 CEST (09:00 EST) and Monday, 17:00 CEST (10:00 EST).\n\nThe issue has been resolved, and all delayed Scorecards have now been successfully delivered. We will continue monitoring to ensure normal operation.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-22T12:39:50.534-04:00", "resolved_inferred": false, "started_at": "2026-06-22T12:39:50.493-04:00", @@ -51,7 +51,7 @@ "body": "We experienced a service disruption affecting the Databox app. Due to technical issues, our web app was unavailable on Wednesday, May 13, from 02:00 to 06:38 CET (Tuesday, May 12, from 8:00 PM to 12:38 AM EST).\n\nAll services have since been restored and are operating normally.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-15T06:46:29.525-04:00", "resolved_inferred": false, "started_at": "2026-05-15T06:46:29.485-04:00", @@ -64,7 +64,7 @@ "body": "We experienced a service disruption affecting the Databox app. During this incident, the application was unavailable, resulting in an outage across all services.\n\nThe Databox app was inaccessible during the following period:\nTuesday, 13:58\u201314:06 CET (08:58\u201309:06 EST)\n\nAll services have since been restored and are operating normally.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-10T09:34:37.108-04:00", "resolved_inferred": false, "started_at": "2026-03-10T09:34:37.057-04:00", @@ -77,7 +77,7 @@ "body": "The issue affecting outgoing emails has been resolved. Scheduled notifications, password reset emails, and user invitation emails are sending normally. We will continue monitoring.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-06T12:10:14.631-05:00", "resolved_inferred": false, "started_at": "2026-03-06T06:14:00.253-05:00", @@ -90,7 +90,7 @@ "body": "We experienced a service disruption affecting the Databox app. During this incident, the application was unavailable, resulting in an outage across all services.\n\nThe Databox app was inaccessible during the following periods:\nFriday, 00:37\u201301:12 CET (Thursday, 6:37\u20137:12 PM EST)\nFriday, 04:35\u201304:50 CET (Thursday, 10:35\u201310:50 PM EST)\n\nAll users attempting to access the Databox app during these periods were impacted. As a result, regular data syncing may have been delayed, the first scheduled sync of the day may have been missed, and some notifications may have been delayed or not delivered.\n\nAll services have since been restored and are operating normally.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-06T04:48:35.627-05:00", "resolved_inferred": false, "started_at": "2026-02-06T04:48:35.561-05:00", @@ -103,7 +103,7 @@ "body": "Metric syncing is fully operational. The earlier Google Analytics 4 rate limit errors have been mitigated, and the issue is now resolved.\n\nThank you for your patience and understanding on the matter. If you have any questions, please reach out to our Support services via chat or help@databox.com.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-04T04:53:32.896-05:00", "resolved_inferred": false, "started_at": "2026-02-03T07:13:01.164-05:00", @@ -116,7 +116,7 @@ "body": "The issue has been resolved. Scheduled syncs are now being performed as expected again.\n\nThank you for your patience and understanding. If you have any questions, please reach out to our Support services via chat or help@databox.com.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-06T09:05:26.824-05:00", "resolved_inferred": false, "started_at": "2025-11-06T07:35:52.724-05:00", @@ -129,7 +129,7 @@ "body": "The issue has been resolved. The Reddit Ads metrics are now syncing normally again.\n\nIf you have any questions for us, please reach out to our Support services via chat or help@databox.com.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-05T09:18:40.022-05:00", "resolved_inferred": false, "started_at": "2025-11-05T08:24:00.309-05:00", @@ -142,7 +142,7 @@ "body": "AWS has resolved the reported outage. Our monitoring confirms that all systems are stable and operating normally.\n\nWe\u2019ll continue to keep an eye on performance, but no further impact is expected at this time.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-21T05:45:43.660-04:00", "resolved_inferred": false, "started_at": "2025-10-20T05:49:07.145-04:00", @@ -155,7 +155,7 @@ "body": "On Saturday, October 18, an issue occurred that prevented new data from being written to the warehouse. This caused dataset metric preparation processes to stop temporarily.\n\nIssues occurred between 2.30 AM EDT and 11:15 AM EDT (8.30 AM CET and 5.15 PM CET).\n\nThank you for your patience and understanding. If you have any questions, please reach out to our Support services via chat or help@databox.com.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-19T14:49:11.302-04:00", "resolved_inferred": false, "started_at": "2025-10-19T14:49:11.248-04:00", @@ -168,7 +168,7 @@ "body": "Issue has been resolved. The app can now be accessed normally.\n\nThank you for your patience and understanding on the matter. If you have any questions, please reach out to our Support services via chat or help@databox.com.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-07T10:32:16.049-04:00", "resolved_inferred": false, "started_at": "2025-10-07T09:09:20.784-04:00", @@ -181,7 +181,7 @@ "body": "After monitoring the Xero integrations for a while, we can confirm that the issue is resolved.\n\nThe Xero data sources are now connected, new Xero connections can be added and data is syncing normally for Xero metrics.\n\nThank you for your patience and understanding on the matter. If you have any questions, please reach out to our Support services via chat or help@databox.com.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-06T04:48:05.871-04:00", "resolved_inferred": false, "started_at": "2025-10-02T09:59:57.528-04:00", @@ -194,7 +194,7 @@ "body": "Our Security team, together with an external cybersecurity service provider, has concluded an investigation connected to suspicious activity involving a limited number of Databox customer connections with Salesforce.\n\nWe have not identified any evidence that any customer\u2019s Databox account or personal data was compromised.\n\nThat makes this incident resolved, the Salesforce integration has been removed as a precaution measurement and will not be available until further notice. This means existing Salesforce connections are disabled in Databox and new connections cannot be established.\n\nWe are working on re-enabling the Salesforce integration and will keep you updated once it\u2019s available again.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-08T07:29:21.000-04:00", "resolved_inferred": false, "started_at": "2025-09-25T03:35:13.870-04:00", @@ -207,7 +207,7 @@ "body": "The release and migration are now complete. All related issues have been resolved and should no longer occur.\n\nIf you have any questions for us, please reach out to our Support services via chat or help@databox.com.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-10T11:12:44.929-04:00", "resolved_inferred": false, "started_at": "2025-09-10T07:57:52.977-04:00", @@ -220,7 +220,7 @@ "body": "The issue has been resolved. The datasets feature now works as expected. \n\nThank you for your patience and understanding on the matter. If you have any questions, please reach out to our Support services via chat or help@databox.com.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-29T17:02:28.081-04:00", "resolved_inferred": false, "started_at": "2025-08-29T15:01:54.268-04:00", diff --git a/api/v/databricks.json b/api/v/databricks.json index ea1d84f6462450f832df2b9f6b3d2bee1aa0f667..3d46f35910842573cc0b837801c5765b5a796c8f 100644 --- a/api/v/databricks.json +++ b/api/v/databricks.json @@ -3,7 +3,7 @@ "slug": "databricks", "platform": "status.io", "status_url": "https://status.databricks.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": false, "first_watched": "2026-09-04T07:06:16Z", diff --git a/api/v/datacake.json b/api/v/datacake.json index 65c6cebc985ff250253e839a6fc9c97abc57b6ca..92e7b3c0b2c0c1bd4b9c6817e1fca9420a0c332d 100644 --- a/api/v/datacake.json +++ b/api/v/datacake.json @@ -3,7 +3,7 @@ "slug": "datacake", "platform": "instatus", "status_url": "https://datacake-status.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": false, "first_watched": "2026-09-04T07:06:16Z", diff --git a/api/v/datadog.json b/api/v/datadog.json index 2e96c8e92e00118fc2e389378a16a31323f358a4..214332f0847ce17c21b2fb352c3cc82890733e59 100644 --- a/api/v/datadog.json +++ b/api/v/datadog.json @@ -3,7 +3,7 @@ "slug": "datadog", "platform": "statuspage", "status_url": "https://status.datadoghq.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "The issue is now resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-09-03T19:01:22.899-04:00", "resolved_inferred": false, "started_at": "2026-09-03T13:20:26.220-04:00", @@ -25,7 +25,7 @@ "body": "The issue is now resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-09-01T21:24:48.880-04:00", "resolved_inferred": false, "started_at": "2026-09-01T21:07:32.534-04:00", @@ -38,7 +38,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-06T15:37:32.874-04:00", "resolved_inferred": false, "started_at": "2026-08-06T14:51:32.514-04:00", @@ -51,7 +51,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-30T04:27:01.231-04:00", "resolved_inferred": false, "started_at": "2026-07-30T03:44:26.428-04:00", @@ -64,7 +64,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-29T13:28:08.443-04:00", "resolved_inferred": false, "started_at": "2026-07-29T11:41:51.915-04:00", @@ -77,7 +77,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-27T15:52:05.822-04:00", "resolved_inferred": false, "started_at": "2026-07-27T15:05:38.062-04:00", @@ -90,7 +90,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-23T14:13:36.888-04:00", "resolved_inferred": false, "started_at": "2026-07-23T13:08:39.793-04:00", @@ -103,7 +103,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-10T11:59:28.762-04:00", "resolved_inferred": false, "started_at": "2026-07-10T10:09:23.744-04:00", @@ -116,7 +116,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-02T21:29:11.981-04:00", "resolved_inferred": false, "started_at": "2026-07-02T20:25:57.077-04:00", @@ -129,7 +129,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-01T16:37:08.245-04:00", "resolved_inferred": false, "started_at": "2026-07-01T14:31:20.464-04:00", @@ -142,7 +142,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-30T16:32:44.628-04:00", "resolved_inferred": false, "started_at": "2026-06-30T13:51:54.596-04:00", @@ -155,7 +155,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-30T07:18:50.339-04:00", "resolved_inferred": false, "started_at": "2026-06-30T06:35:02.766-04:00", @@ -168,7 +168,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-26T09:45:37.493-04:00", "resolved_inferred": false, "started_at": "2026-06-26T09:38:59.132-04:00", @@ -181,7 +181,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-25T19:32:26.545-04:00", "resolved_inferred": false, "started_at": "2026-06-25T19:23:01.642-04:00", @@ -194,7 +194,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-22T18:41:36.494-04:00", "resolved_inferred": false, "started_at": "2026-06-22T17:27:41.508-04:00", @@ -207,7 +207,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-18T12:33:28.910-04:00", "resolved_inferred": false, "started_at": "2026-06-18T12:13:18.539-04:00", @@ -220,7 +220,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-12T15:39:44.126-04:00", "resolved_inferred": false, "started_at": "2026-06-12T13:12:28.442-04:00", @@ -233,7 +233,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-08T08:59:27.139-04:00", "resolved_inferred": false, "started_at": "2026-06-08T07:05:03.193-04:00", @@ -246,7 +246,7 @@ "body": "This incident has been resolved and Azure metrics are reporting as expected.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-15T23:43:01.802-04:00", "resolved_inferred": false, "started_at": "2026-05-15T22:17:24.976-04:00", @@ -259,7 +259,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-14T15:48:24.589-04:00", "resolved_inferred": false, "started_at": "2026-05-14T14:24:38.680-04:00", @@ -272,7 +272,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-13T11:53:19.730-04:00", "resolved_inferred": false, "started_at": "2026-05-13T11:16:27.132-04:00", @@ -285,7 +285,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-08T10:07:35.466-04:00", "resolved_inferred": false, "started_at": "2026-05-07T20:06:53.061-04:00", @@ -298,7 +298,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-05T15:52:31.844-04:00", "resolved_inferred": false, "started_at": "2026-05-05T14:14:03.754-04:00", @@ -311,7 +311,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-30T21:19:56.916-04:00", "resolved_inferred": false, "started_at": "2026-04-30T20:45:48.677-04:00", @@ -324,7 +324,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-24T12:50:36.003-04:00", "resolved_inferred": false, "started_at": "2026-04-24T12:27:19.942-04:00", @@ -337,7 +337,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-15T20:37:38.862-04:00", "resolved_inferred": false, "started_at": "2026-04-15T18:38:22.912-04:00", @@ -350,7 +350,7 @@ "body": "Between approximately 9:42 AM and 10:38 AM ET on April 10, we observed delivery failures for customers in the US1, AP1, and AP2 regions. During this window, notifications to the following integrations were delayed or temporarily undelivered:\n\n\u2022 PagerDuty\n\u2022 Slack\n\u2022 Microsoft Teams\n\u2022 Webhooks\n\u2022 Jira\n\u2022 ServiceNow\n\u2022 OpsGenie\n\u2022 VictorOps\n\u2022 BigPanda\n\u2022 Zendesk\n\u2022 Sumologic\n\nAll delayed notifications have been replayed with the following exceptions: PagerDuty pages and Slack notifications queued during the outage window were not replayed, as they were no longer actionable at the time of recovery. Webhook notifications will be reprocessed and delivered at a later date.\n\nNo monitoring data was lost during this incident. Monitor evaluations continued normally \u2014 only the delivery of triggered notifications was affected.\n\nThank you for your patience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-10T16:59:49.000-04:00", "resolved_inferred": false, "started_at": "2026-04-10T10:54:11.000-04:00", @@ -363,7 +363,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-27T15:30:04.932-04:00", "resolved_inferred": false, "started_at": "2026-03-27T14:57:08.423-04:00", @@ -376,7 +376,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-26T15:56:35.378-04:00", "resolved_inferred": false, "started_at": "2026-03-26T10:24:24.753-04:00", @@ -389,7 +389,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-18T22:53:46.258-04:00", "resolved_inferred": false, "started_at": "2026-03-18T20:54:23.191-04:00", @@ -402,7 +402,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-13T06:30:25.499-04:00", "resolved_inferred": false, "started_at": "2026-03-13T05:26:35.665-04:00", @@ -415,7 +415,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-24T02:08:31.512-05:00", "resolved_inferred": false, "started_at": "2026-02-23T23:31:54.191-05:00", @@ -428,7 +428,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-18T15:37:18.980-05:00", "resolved_inferred": false, "started_at": "2026-02-18T14:30:23.632-05:00", @@ -441,7 +441,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-11T21:08:46.715-05:00", "resolved_inferred": false, "started_at": "2026-02-11T19:57:47.013-05:00", @@ -454,7 +454,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-11T18:44:55.420-05:00", "resolved_inferred": false, "started_at": "2026-02-11T15:56:50.834-05:00", @@ -467,7 +467,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-05T12:43:22.857-05:00", "resolved_inferred": false, "started_at": "2026-02-05T10:24:58.173-05:00", @@ -480,7 +480,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-29T14:55:05.164-05:00", "resolved_inferred": false, "started_at": "2026-01-29T12:35:31.807-05:00", @@ -493,7 +493,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-28T18:36:23.179-05:00", "resolved_inferred": false, "started_at": "2026-01-28T15:30:31.000-05:00", @@ -506,7 +506,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-22T14:27:45.914-05:00", "resolved_inferred": false, "started_at": "2026-01-22T13:51:22.114-05:00", @@ -519,7 +519,7 @@ "body": "This incident is resolved. There's no more delay for the processing of Events, nor impact on the event stream, event based widgets and event based monitors.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-18T09:24:41.174-05:00", "resolved_inferred": false, "started_at": "2026-01-18T07:33:26.505-05:00", @@ -532,7 +532,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-12T18:43:52.417-05:00", "resolved_inferred": false, "started_at": "2025-12-12T16:49:44.306-05:00", @@ -545,7 +545,7 @@ "body": "All impact related to APM metrics has been resolved. A separate incident has been created to track the remaining impact in live process data.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-12T16:52:51.132-05:00", "resolved_inferred": false, "started_at": "2025-12-12T13:37:34.103-05:00", @@ -558,7 +558,7 @@ "body": "This incident has been resolved. Live data is being processed normally and gaps in distribution metrics on graphs will be backfilled within the next hour.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-09T16:08:28.161-05:00", "resolved_inferred": false, "started_at": "2025-12-09T15:16:17.223-05:00", @@ -571,7 +571,7 @@ "body": "This incident has been resolved as of 2:32PM ET.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-19T14:44:17.410-05:00", "resolved_inferred": false, "started_at": "2025-11-19T14:08:07.752-05:00", @@ -584,7 +584,7 @@ "body": "This incident has been resolved. Notification delays were only affecting our internal monitoring and were due to the ongoing Cloudflare incident: https://www.cloudflarestatus.com/incidents/8gmgl950y3h7/.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-18T08:53:58.019-05:00", "resolved_inferred": false, "started_at": "2025-11-18T08:17:44.575-05:00", @@ -597,7 +597,7 @@ "body": "All errors stopped as of 12:02ET. This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-17T12:20:10.000-05:00", "resolved_inferred": false, "started_at": "2025-11-17T11:23:14.226-05:00", @@ -610,7 +610,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-13T14:07:51.517-05:00", "resolved_inferred": false, "started_at": "2025-11-13T13:58:01.396-05:00", @@ -623,7 +623,7 @@ "body": "APM metrics are now processing live.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-05T12:57:12.658-05:00", "resolved_inferred": false, "started_at": "2025-11-05T10:42:35.000-05:00", @@ -636,7 +636,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-28T18:01:26.977-04:00", "resolved_inferred": false, "started_at": "2025-10-28T14:32:04.041-04:00", @@ -649,7 +649,7 @@ "body": "Backfills for Metrics and Log Management data have completed. All systems are back to normal.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-22T10:40:11.620-04:00", "resolved_inferred": false, "started_at": "2025-10-20T08:45:48.000-04:00", diff --git a/api/v/datagrail.json b/api/v/datagrail.json index 3d5d643131c36b7ec45e23ba34cc2e08f70b92e4..17f7ce96125529f3f5bb28f5f492974918483a20 100644 --- a/api/v/datagrail.json +++ b/api/v/datagrail.json @@ -3,7 +3,7 @@ "slug": "datagrail", "platform": "statuspage", "status_url": "https://status.datagrail.io", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-22T15:31:11.942-07:00", "resolved_inferred": false, "started_at": "2026-08-22T14:42:45.400-07:00", @@ -25,7 +25,7 @@ "body": "This degradation has been resolved. All Privacy Request intake forms are loading at normal speed.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-08T14:15:17.000-08:00", "resolved_inferred": false, "started_at": "2026-01-08T12:20:01.047-08:00", @@ -38,7 +38,7 @@ "body": "This issue has been resolved!", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-26T13:39:13.252-07:00", "resolved_inferred": false, "started_at": "2025-08-26T09:58:16.406-07:00", diff --git a/api/v/datarobot.json b/api/v/datarobot.json index 9a026266af56b6c87fc20036bb03a77d4d16d533..e7d3fae441125b9b2d1721b51604ded5d67dcb0b 100644 --- a/api/v/datarobot.json +++ b/api/v/datarobot.json @@ -3,7 +3,7 @@ "slug": "datarobot", "platform": "statuspage", "status_url": "https://status.datarobot.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "The fix is now deployed to all the Prod environments and Generative AI Playground is now working as expected.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-18T14:44:25.107Z", "resolved_inferred": false, "started_at": "2026-08-18T12:20:14.880Z", @@ -25,7 +25,7 @@ "body": "Engineering team observed that the Vector Database creation is operational across all DataRobot MTS environments. The incident is Resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-24T18:42:58.671Z", "resolved_inferred": false, "started_at": "2026-07-24T17:32:57.073Z", @@ -38,7 +38,7 @@ "body": "The issue is contained and the team has verified that predictions against Custom Models in all MTSaaS environments are healthy.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-02T13:37:45.506Z", "resolved_inferred": false, "started_at": "2026-07-02T13:03:34.408Z", @@ -51,7 +51,7 @@ "body": "A fix has been deployed to production and the issue is now resolved. All systems are operating normally.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-03T09:29:45.131Z", "resolved_inferred": false, "started_at": "2026-05-29T08:37:18.478Z", @@ -64,7 +64,7 @@ "body": "Feature drift statistics processing has been restored to normal. All metrics are now up to date. No data was lost.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-28T09:47:58.768Z", "resolved_inferred": false, "started_at": "2026-05-28T08:30:39.000Z", @@ -77,7 +77,7 @@ "body": "Custom Models, Custom Applications & Data upload services are back to Operational state in US SAAS Environment. Issue is Resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-26T06:18:22.735Z", "resolved_inferred": false, "started_at": "2026-05-26T05:09:20.918Z", @@ -90,7 +90,7 @@ "body": "Engineering confirmed the issue is resolved and all services are restored.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-08T20:21:03.258Z", "resolved_inferred": false, "started_at": "2026-05-08T00:15:33.000Z", @@ -103,7 +103,7 @@ "body": "Engineering has applied the required infrastructure configuration changes. The service is operating normally and no further user impact is observed. Engineering will continue monitoring cluster health to ensure stability. The incident is now marked as Contained.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-10T11:01:03.112Z", "resolved_inferred": false, "started_at": "2026-04-10T10:24:56.497Z", @@ -116,7 +116,7 @@ "body": "Engineering has implemented the required fixes to resolve the elevated error rates. Services are now operating normally, and no further user impact has been observed. The team will continue to monitor the system to ensure stability. The incident is now considered contained.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-10T13:04:16.406Z", "resolved_inferred": false, "started_at": "2026-04-09T21:56:26.788Z", @@ -129,7 +129,7 @@ "body": "Quay.io functionality has been restored and DataRobot environments are fully stabilized.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-31T08:53:43.875Z", "resolved_inferred": false, "started_at": "2026-03-30T20:43:10.339Z", @@ -142,7 +142,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-13T18:43:49.655Z", "resolved_inferred": false, "started_at": "2026-03-13T17:49:32.920Z", @@ -155,7 +155,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-17T18:32:10.260Z", "resolved_inferred": false, "started_at": "2026-03-11T20:05:24.109Z", @@ -168,7 +168,7 @@ "body": "The mitigation implemented by Engineering has resolved the Kubernetes network issue, and the incident is now contained.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-11T16:41:02.998Z", "resolved_inferred": false, "started_at": "2026-03-11T14:36:01.774Z", @@ -181,7 +181,7 @@ "body": "This incident is now resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-18T21:19:56.452Z", "resolved_inferred": false, "started_at": "2026-02-18T21:04:04.986Z", @@ -194,7 +194,7 @@ "body": "Rollback of the JP cluster to the previous version is complete and the problem has been mitigated.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-17T15:55:34.727Z", "resolved_inferred": false, "started_at": "2026-02-17T15:48:09.528Z", @@ -207,7 +207,7 @@ "body": "New version of Agentic application template is released, the issue is resolved", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-16T12:49:28.601Z", "resolved_inferred": false, "started_at": "2026-02-16T11:35:49.535Z", @@ -220,7 +220,7 @@ "body": "The incident has now been resolved. All services are now operational.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-13T21:31:51.661Z", "resolved_inferred": false, "started_at": "2026-02-13T20:39:05.459Z", @@ -233,7 +233,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-22T14:19:49.188Z", "resolved_inferred": false, "started_at": "2026-01-08T18:15:54.385Z", @@ -246,7 +246,7 @@ "body": "Between 16:50 UTC and 17:09 UTC, one of external providers(DockerHub) had an outage that might have caused temporary delays in starting platform workloads. The issue has been resolved and normal operations have resumed. Engineering is continuing to monitor the system.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-17T17:00:00.000Z", "resolved_inferred": false, "started_at": "2025-12-17T17:00:00.000Z", @@ -259,7 +259,7 @@ "body": "The engineering team has confirmed recovery across all MTS and STS environments.\nNo further updates are expected.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-05T11:35:07.183Z", "resolved_inferred": false, "started_at": "2025-12-05T11:09:18.502Z", @@ -272,7 +272,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-27T08:26:20.820Z", "resolved_inferred": false, "started_at": "2025-11-26T07:17:34.566Z", @@ -285,7 +285,7 @@ "body": "The issue is fixed. Access to the US, EU, and JP clusters is restored.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-20T07:23:23.632Z", "resolved_inferred": false, "started_at": "2025-11-20T06:52:37.069Z", @@ -298,7 +298,7 @@ "body": "The issue has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-07T11:50:35.096Z", "resolved_inferred": false, "started_at": "2025-11-07T07:14:47.015Z", @@ -311,7 +311,7 @@ "body": "The Engineering team hasn't observed any new occurrences during monitoring.\n\nAll services remain fully operational.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-07T12:37:32.917Z", "resolved_inferred": false, "started_at": "2025-11-06T12:38:10.614Z", @@ -324,7 +324,7 @@ "body": "The Engineering team has successfully resolved the connection and processing timeouts affecting data operations in MTS Production.\n\nServices are now running stable.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-04T14:32:44.134Z", "resolved_inferred": false, "started_at": "2025-11-04T13:57:12.261Z", @@ -337,7 +337,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-22T14:40:56.784Z", "resolved_inferred": false, "started_at": "2025-10-22T13:16:11.363Z", @@ -350,7 +350,7 @@ "body": "This incident has been resolved. AWS is reporting systems as operational. Engineering will continue to monitor the situation.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-20T22:11:11.971Z", "resolved_inferred": false, "started_at": "2025-10-20T09:49:08.000Z", @@ -363,7 +363,7 @@ "body": "Engineering team has applied the fix to address UI issue affecting Model Visibility and Project Management. This problem has now been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-01T18:04:44.689Z", "resolved_inferred": false, "started_at": "2025-10-01T09:40:26.879Z", @@ -376,7 +376,7 @@ "body": "Issue is resolved and DataRobot MTS & STS services are back to normal.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-25T01:56:34.603Z", "resolved_inferred": false, "started_at": "2025-09-25T01:19:06.390Z", @@ -389,7 +389,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-10T18:03:34.236Z", "resolved_inferred": false, "started_at": "2025-09-09T05:39:06.574Z", @@ -402,7 +402,7 @@ "body": "Engineering has applied the fix to mitigate the issue impacting serverless deployments when a new deployment is created or an existing deployment is modified.\n\nThe problem has now been contained.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-02T18:07:55.819Z", "resolved_inferred": false, "started_at": "2025-09-02T15:37:45.009Z", diff --git a/api/v/datastax.json b/api/v/datastax.json index f09a0ed37a120b9be96a4fc75cf1f375474631f0..ab40533574d0c47d105dd21588f1a5f88c43e346 100644 --- a/api/v/datastax.json +++ b/api/v/datastax.json @@ -3,7 +3,7 @@ "slug": "datastax", "platform": "statuspage", "status_url": "https://status.astra.datastax.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "GCP has resolved their incident (see below) and we have not seen further impact while we monitored independently.\n\nRelated GCP incident: https://status.cloud.google.com/incidents/J5ia5t9p3g9Q5Wi7r8Ev", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-09-01T19:22:48.425Z", "resolved_inferred": false, "started_at": "2026-09-01T17:39:11.850Z", @@ -25,7 +25,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-14T16:17:40.497Z", "resolved_inferred": false, "started_at": "2026-08-14T13:55:33.200Z", @@ -38,7 +38,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-30T19:19:59.534Z", "resolved_inferred": false, "started_at": "2026-07-30T11:30:55.000Z", @@ -51,7 +51,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-22T20:18:00.333Z", "resolved_inferred": false, "started_at": "2026-07-22T18:24:08.000Z", @@ -64,7 +64,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-16T12:59:53.874Z", "resolved_inferred": false, "started_at": "2026-06-16T10:47:30.517Z", @@ -77,7 +77,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-05T20:11:39.041Z", "resolved_inferred": false, "started_at": "2026-06-05T18:33:32.126Z", @@ -90,7 +90,7 @@ "body": "Azure has confirmed that services have recovered, and we have also observed system recovery.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-29T23:19:06.000Z", "resolved_inferred": false, "started_at": "2026-05-29T05:55:22.000Z", @@ -103,7 +103,7 @@ "body": "Resolved", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-09T07:10:30.108Z", "resolved_inferred": false, "started_at": "2026-05-08T07:27:53.245Z", @@ -116,7 +116,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-16T05:35:55.140Z", "resolved_inferred": false, "started_at": "2026-04-16T04:30:49.734Z", @@ -129,7 +129,7 @@ "body": "The issue is resolved, but in case you still have trouble connecting, we recommend restarting the apps.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-16T05:34:59.481Z", "resolved_inferred": false, "started_at": "2026-04-16T03:44:06.974Z", @@ -142,7 +142,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-07T20:28:57.615Z", "resolved_inferred": false, "started_at": "2026-04-07T17:29:36.195Z", @@ -155,7 +155,7 @@ "body": "A fix has been rolled out. The Health Dashboard is now accessible again.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-23T20:14:33.028Z", "resolved_inferred": false, "started_at": "2026-03-23T17:17:24.844Z", @@ -168,7 +168,7 @@ "body": "This incident has been fully resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-25T06:05:10.899Z", "resolved_inferred": false, "started_at": "2026-02-25T05:38:55.703Z", @@ -181,7 +181,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-19T01:42:12.135Z", "resolved_inferred": false, "started_at": "2026-02-18T12:33:46.431Z", @@ -194,7 +194,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-27T21:49:24.412Z", "resolved_inferred": false, "started_at": "2026-01-24T00:47:44.779Z", @@ -207,7 +207,7 @@ "body": "AWS has rolled back changes to their EKS API servers which introduced some incompatibility causing our client API calls to fail. This incident is now resolved and database creation for AWS Astra Managed Clusters is working in all available regions.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-14T20:28:37.489Z", "resolved_inferred": false, "started_at": "2026-01-14T17:47:20.618Z", @@ -220,7 +220,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-13T02:11:18.574Z", "resolved_inferred": false, "started_at": "2026-01-12T23:14:05.161Z", @@ -233,7 +233,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-14T15:43:20.571Z", "resolved_inferred": false, "started_at": "2025-11-14T03:30:24.130Z", @@ -246,7 +246,7 @@ "body": "Issues with API error rates in AWS eu-west-1 has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-13T16:10:45.023Z", "resolved_inferred": false, "started_at": "2025-11-13T11:23:25.463Z", @@ -259,7 +259,7 @@ "body": "Database creation issues have been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-12T05:57:54.157Z", "resolved_inferred": false, "started_at": "2025-11-12T05:13:07.127Z", @@ -272,7 +272,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "maintenance", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-13T06:10:10.279Z", "resolved_inferred": false, "started_at": "2025-11-12T03:36:02.406Z", @@ -285,7 +285,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-04T15:03:49.083Z", "resolved_inferred": false, "started_at": "2025-11-04T08:50:31.185Z", @@ -298,7 +298,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-21T02:30:07.549Z", "resolved_inferred": false, "started_at": "2025-10-20T09:56:55.408Z", @@ -311,7 +311,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-14T23:29:06.636Z", "resolved_inferred": false, "started_at": "2025-10-14T19:51:26.507Z", @@ -324,7 +324,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-09T01:14:48.770Z", "resolved_inferred": false, "started_at": "2025-10-08T18:21:01.528Z", @@ -337,7 +337,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-26T19:12:11.042Z", "resolved_inferred": false, "started_at": "2025-09-26T09:14:46.758Z", @@ -350,7 +350,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-25T20:23:21.368Z", "resolved_inferred": false, "started_at": "2025-09-25T13:48:24.477Z", @@ -363,7 +363,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-25T13:13:33.409Z", "resolved_inferred": false, "started_at": "2025-09-25T13:11:00.296Z", @@ -376,7 +376,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-11T01:46:02.995Z", "resolved_inferred": false, "started_at": "2025-08-11T00:32:10.851Z", @@ -389,7 +389,7 @@ "body": "This issue has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-09T02:29:22.464Z", "resolved_inferred": false, "started_at": "2025-08-09T01:46:35.772Z", @@ -402,7 +402,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "maintenance", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-08T20:38:32.145Z", "resolved_inferred": false, "started_at": "2025-08-08T14:55:36.536Z", diff --git a/api/v/datavant.json b/api/v/datavant.json index 7a5346886851767edf2235ffbfc42602b35c39cb..ed3694ef0787700db8d9c7b1fa605737b277cea3 100644 --- a/api/v/datavant.json +++ b/api/v/datavant.json @@ -3,7 +3,7 @@ "slug": "datavant", "platform": "statuspage", "status_url": "https://status.datavant.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", diff --git a/api/v/datto.json b/api/v/datto.json index c7941eb510bae248d8ea0ceb56b8ba58e32e9bba..78a5b64df4320685a5e236061acf265ee4da240c 100644 --- a/api/v/datto.json +++ b/api/v/datto.json @@ -3,7 +3,7 @@ "slug": "datto", "platform": "statuspage", "status_url": "https://status.datto.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "degraded", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -13,6 +13,8 @@ "first_seen": "2026-09-04T07:06:16Z", "impact": "maintenance", "last_seen": "2026-09-04T09:06:33Z", +"resolved_at": "2026-09-04T10:17:20Z", +"resolved_inferred": true, "started_at": "2026-09-04T03:00:00.000-04:00", "state": "maintenance", "title": "VSA9 - VSA Patch Release v9.5.27 - Revan/Leo", @@ -23,7 +25,7 @@ "body": "We are aware of a problem where Datto Endpoint Backup for PC users hosted on Cloud Siris 299242 may experience degraded backup and recovery performance..\n\nThe Kaseya Engineering Team is investigating the issue and working towards a resolution.\n\nShould you need any additional questions or require assistance, please contact our support team at https://helpdesk.kaseya.com/hc/en-gb#/contact \n\nSubscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "started_at": "2026-09-03T15:20:05.573-04:00", "state": "investigating", "title": "Datto Endpoint Backup for PC - Backup and Restore - Service Disruption for Customers Hosted on Cloud Siris 299242", @@ -34,7 +36,7 @@ "body": "The issue preventing Secure Edge administrators from viewing recent usage information within Datto Network Manager has been resolved.\n\nQueued data has finished processing, and usage metrics are now available as expected. We appreciate your patience while we worked through this issue.\n\nSubscribe to the Kaseya Status Page for up to date information at https://status.kaseya.com/", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-09-02T19:17:22.893-04:00", "resolved_inferred": false, "started_at": "2026-09-02T17:11:29.033-04:00", @@ -47,7 +49,7 @@ "body": "Following the recent changes deployed by our R&D team, we are seeing improvements in Exchange backup success rates for customers hosted on pod 'aue1-saas-p0'. Our team remains actively engaged and continues to work on further improvements while closely monitoring the environment.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "started_at": "2026-09-02T16:33:44.152-04:00", "state": "identified", "title": "Datto SaaS Protection - Backup performance degradation for Exchange services on pod 'aue1-saas-p0'", @@ -58,7 +60,7 @@ "body": "The remediation has been identified and is currently being deployed to the affected nodes in a phased rollout to ensure a controlled and efficient resolution.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "started_at": "2026-09-02T06:10:45.329-04:00", "state": "identified", "title": "Datto BCDR - Cloud Recovery - Cloud Operations Service Impact", @@ -69,7 +71,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-09-02T06:11:31.414-04:00", "resolved_inferred": false, "started_at": "2026-09-02T02:00:34.000-04:00", @@ -82,7 +84,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-09-02T12:51:47.422-04:00", "resolved_inferred": false, "started_at": "2026-09-01T17:49:24.000-04:00", @@ -95,7 +97,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-09-01T09:27:53.578-04:00", "resolved_inferred": false, "started_at": "2026-09-01T08:13:23.834-04:00", @@ -108,7 +110,7 @@ "body": "The issue affecting access to the Datto RMM Vidal platform has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-09-01T11:56:49.484-04:00", "resolved_inferred": false, "started_at": "2026-09-01T07:37:56.194-04:00", @@ -121,7 +123,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-31T13:34:14.106-04:00", "resolved_inferred": false, "started_at": "2026-08-31T12:01:10.696-04:00", @@ -134,7 +136,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-28T14:23:12.837-04:00", "resolved_inferred": false, "started_at": "2026-08-28T13:13:41.132-04:00", @@ -147,7 +149,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-31T09:40:38.705-04:00", "resolved_inferred": false, "started_at": "2026-08-28T06:30:39.388-04:00", @@ -160,7 +162,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-31T16:11:25.460-04:00", "resolved_inferred": false, "started_at": "2026-08-27T10:52:42.789-04:00", @@ -173,7 +175,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-09-03T11:28:16.779-04:00", "resolved_inferred": false, "started_at": "2026-08-27T08:39:45.700-04:00", @@ -186,7 +188,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-28T14:18:27.869-04:00", "resolved_inferred": false, "started_at": "2026-08-26T10:40:14.950-04:00", @@ -199,7 +201,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-31T09:43:12.659-04:00", "resolved_inferred": false, "started_at": "2026-08-25T16:39:37.000-04:00", @@ -212,7 +214,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-09-03T12:44:14.081-04:00", "resolved_inferred": false, "started_at": "2026-08-25T12:09:00.000-04:00", @@ -225,7 +227,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-25T12:34:13.021-04:00", "resolved_inferred": false, "started_at": "2026-08-24T11:46:07.193-04:00", @@ -238,7 +240,7 @@ "body": "Scheduled maintenance is currently in progress. We will provide updates as necessary.", "first_seen": "2026-09-04T07:06:16Z", "impact": "maintenance", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "started_at": "2026-08-24T08:00:00.000-04:00", "state": "maintenance", "title": "Kaseya - Scheduled Server Infrastructure Maintenance", @@ -249,7 +251,7 @@ "body": "Changes made by the Kaseya R&D team have proven successful and full functionality has been restored. \n\nThe issue is now considered resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-22T10:50:09.323-04:00", "resolved_inferred": false, "started_at": "2026-08-21T14:22:34.803-04:00", @@ -262,7 +264,7 @@ "body": "The issue affecting Activity Log performance on the Vidal Platform following the 15.1 release has been resolved.\n\nThe Kaseya Engineering Team implemented a fix and has confirmed that Activity Logs are loading as expected after monitoring the platform to ensure ongoing stability and performance.\n\nShould you have any additional questions or require assistance, please contact our support team at https://helpdesk.kaseya.com/hc/en-gb#/contact\n\nSubscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-28T14:43:01.281-04:00", "resolved_inferred": false, "started_at": "2026-08-21T13:17:03.617-04:00", @@ -275,7 +277,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-19T16:08:09.519-04:00", "resolved_inferred": false, "started_at": "2026-08-19T07:25:27.359-04:00", @@ -288,7 +290,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-20T08:38:40.555-04:00", "resolved_inferred": false, "started_at": "2026-08-18T10:15:05.998-04:00", @@ -301,7 +303,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-18T10:13:49.607-04:00", "resolved_inferred": false, "started_at": "2026-08-17T23:46:29.225-04:00", @@ -314,7 +316,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-18T00:26:24.733-04:00", "resolved_inferred": false, "started_at": "2026-08-17T21:53:27.913-04:00", @@ -327,7 +329,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-14T15:32:50.224-04:00", "resolved_inferred": false, "started_at": "2026-08-13T05:24:48.841-04:00", @@ -340,7 +342,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-14T08:14:53.308-04:00", "resolved_inferred": false, "started_at": "2026-08-12T17:56:16.380-04:00", @@ -353,7 +355,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-12T07:55:24.738-04:00", "resolved_inferred": false, "started_at": "2026-08-11T21:48:45.450-04:00", @@ -366,7 +368,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-12T15:33:16.373-04:00", "resolved_inferred": false, "started_at": "2026-08-11T13:35:45.116-04:00", @@ -379,7 +381,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-10T09:23:00.169-04:00", "resolved_inferred": false, "started_at": "2026-08-08T13:15:07.741-04:00", @@ -392,7 +394,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-07T19:48:58.436-04:00", "resolved_inferred": false, "started_at": "2026-08-07T18:59:36.960-04:00", @@ -405,7 +407,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-24T14:02:27.790-04:00", "resolved_inferred": false, "started_at": "2026-08-06T13:51:58.612-04:00", @@ -418,7 +420,7 @@ "body": "# Summary: \n\nBetween 2026-08-06 05:41 UTC and 2026-08-06 18:03 UTC, ConnectBooster customers were unable to login to ConnectBooster using KaseyaOne Single-Sign-On \\(SSO\\). \n\n# Root Cause: \n\nAn unexpected failure in a dependency used by the SSO login process caused login attempts to fail. \n\n## Incident Timeline: \n\n\u2022 Identified: 2026-08-06 13:30 UTC \n\n\u2022 Public Notification: 2026-08-06 14:15 UTC \n\n\u2022 Resolved: 2026-08-06 18:03 UTC \n\n# Preventative Measures: \n\nTo reduce the likelihood and impact of similar incidents in the future, we are taking the following steps. \n\n## Enhancements to Monitoring and Alerting: \n\n* Enhance login workflow logging to provide improved visibility into authentication performance and failures across all login methods. \n* Implement monitoring and alerting for login workflows using request, error, and performance metrics, enabling the team to quickly identify and respond to authentication issues.\n\n## Enhancements to Infrastructure Resiliency: \n\n* Streamline services within the SSO login workflow so that authentication can continue successfully even if related supporting services are unavailable.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-06T17:28:20.472-04:00", "resolved_inferred": false, "started_at": "2026-08-06T10:15:11.000-04:00", @@ -431,7 +433,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-06T12:56:47.953-04:00", "resolved_inferred": false, "started_at": "2026-08-06T09:41:57.629-04:00", @@ -444,7 +446,7 @@ "body": "SaaS Protection backup performance remains strong across all regions and supported services. Backups for Google services, OneDrive, and SharePoint continue to run on the standard three-times-daily schedule. To support consistently high success rates during the ongoing transition from Exchange Web Services (EWS) to Microsoft Graph APIs, Exchange and Teams backups continue to operate on a temporary twice-daily cadence.\n\nOur R&D teams remain focused on the migration effort, making and refining configuration changes as needed while closely monitoring backup health and performance. Although overall system stability remains strong, some customers may continue to experience occasional backup delays or missed backup cycles due to API call throttling as migration and optimization activities progress.\n\nThe migration from EWS to Microsoft Graph APIs is ongoing and is still projected for completion between late August and early September 2026.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "started_at": "2026-08-05T15:40:45.206-04:00", "state": "monitoring", "title": "Datto SaaS Protection - Backup performance degradation for M365 services affecting multiple pods/regions", @@ -455,7 +457,7 @@ "body": "**\\[Datto Endpoint Backup for PC\\]** \u00a0\n\n**A performance degradation event affected the Datto Endpoint Backup for PC Server service, impacting service responsiveness and availability\u00a0\u2013\u00a02026-07-31**\u00a0\n\n\u200c\n\n**Summary:** Between **2026-07-31 05:30 PM UTC** and **2026-08-05 07:30 PM UTC**, Datto Endpoint Backup for PC customers\u00a0hosted on Cloud Siris 215069 encountered reduced performance and intermittent issues with offsite capabilities.\u00a0\n\n\u00a0\u00a0\n\n**Root Cause:**\u00a0\u00a0\n\nThe service interruption resulted from a hardware failure. Recovery activities were conducted with a focus on maintaining service integrity and minimizing potential impact. Following restoration of service, a review was completed and improvement actions have been identified to further enhance recovery processes.\u00a0\n\n\u00a0\n\n**Incident Timeline:**\u00a0\u00a0\n\n* Identified: **2026-07-31 05:30 PM UTC**\u00a0\u00a0\n\n* Public Notification: **2026-07-31 05:34 PM UTC**\u00a0\u00a0\n\n* Resolved: **2026-08-05\u00a007:30 PM UTC**\u00a0\u00a0\n\n\u00a0\u00a0\n\n**Preventative Measures:** To reduce the likelihood and impact of similar incidents in the future, we are taking the following steps.\u00a0\u00a0\n\n* Create standardized documentation for system restoration workflows and conduct process reviews with key technical and operational teams to ensure effective execution, knowledge sharing, and continuous improvement.\u00a0\n\n* Establish a centralized and well-documented catalog of monitoring alerts and designated response teams to improve operational visibility, accountability, and incident management.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-05T14:06:40.979-04:00", "resolved_inferred": false, "started_at": "2026-07-31T13:44:45.787-04:00", @@ -468,7 +470,7 @@ "body": "**Root Cause Analysis \u2013 DRMM Agent Services Incorrectly Flagged by Endpoint Security Software**\u00a0\n\n**Summary**\u00a0\n\nBetween **2026-07-30 17:00 UTC and 2026-07-31 18:43 UTC**, some Datto RMM customers on the Syrah platform experienced issues following the deployment of agent version **15.1.0**. The issue affected endpoints utilizing **Sophos**, where certain DRMM agent services were identified as malicious. In affected environments, agent files were quarantined or removed, causing the Datto RMM agent to become non-functional until remediation actions were completed.\u00a0\n\nThe issue affected a subset of customers and was resolved after coordination with the security vendor.\u00a0\n\n**Root Cause**\u00a0\n\nFollowing the deployment of DRMM agent version 15.1.0, certain agent components were incorrectly identified as malicious by a third-party endpoint security vendor. The detection was a false positive and was not the result of malware or unauthorized code within the DRMM agent. Investigation determined that the detection was likely related to changes in the digital signing reputation of the agent files, which caused the security tool to classify legitimate agent activity as suspicious.\u00a0\n\n**Incident Timeline**\u00a0\n\n* **Identified:** 2026-07-30 21:00 UTC\u00a0\n\n* **Public Notification:** 2026-07-31 02:27 UTC\u00a0\n\n* **Resolved:** 2026-07-31 18:43 UTC\u00a0\n\n**Preventative Measures**\u00a0\n\nTo reduce the likelihood and impact of similar incidents in the future, we are implementing the following improvements:\u00a0\n\n**Enhancements to Release Validation**\u00a0\n\n* Further strengthen our pre-release validation by incorporating a broader set of security and threat-intelligence platforms before agent updates are broadly deployed.\u00a0\n\n* Broaden third-party endpoint security testing to further improve early detection of potential false-positive classifications before release.\u00a0\n\n**Enhancements to Vendor Coordination**\u00a0\n\n* Expand the existing file reputation submission process to include additional security providers to further improve coordination and response options, reducing reliance on a single vendor path.\u00a0\n\n* Establish more formalized engagement processes with security vendors to facilitate faster review and resolution of false-positive detections.\u00a0\n\n**Enhancements to Agent Deployment Practices**\u00a0\n\n* Evaluate staged agent rollout capabilities that would allow updates to be gradually deployed to a subset of endpoints before broader distribution limiting the scope of impact when issues are detected.\u00a0\n\n* Use phased deployments to identify unexpected environmental interactions earlier and further reduce potential customer impact.\u00a0\n\n**Enhancements to Agent Update Architecture**\u00a0\n\n* Review and improve elements of the agent update mechanism to reduce the likelihood that normal update activities are misinterpreted by security software.\u00a0\n\n* Continue refining update workflows to improve compatibility with modern endpoint protection technologies to further reduce the risk of false positive classifications", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-03T12:04:18.574-04:00", "resolved_inferred": false, "started_at": "2026-07-30T22:27:33.000-04:00", @@ -481,7 +483,7 @@ "body": "**Datto RMM - Global Filters Using Site Criteria Returned Incorrect Results \u2013 2026-07-30**\u00a0\n\n**Summary**\u00a0\n\nBetween **2026-07-30 18:10 UTC** and **2026-07-31 02:30 UTC**, some **Datto RMM** customers experienced an issue where **Global Filters using Site specific criteria, including Site Name**, **Site Description**, or **Site is On-Demand,** and **excluding \u201cdoes not contain\u201d** criteria, returned broader-than-expected device results. \u00a0\n\nAs a result, customers using the affected filter configurations may have seen devices incorrectly included in filter results, creating a risk of inaccurate device targeting for downstream automation, policies, or jobs that ran during the exposure window.\u00a0\n\nThe time required to fully restore service was extended because a rollback path for the release was not available. As a result, mitigation required the issue to be diagnosed, a software fix to be developed, tested, and deployed before the incident could be resolved.\u00a0\n\nEngineering isolated the regression, developed a corrective code change, validated the fix, and deployed it to restore expected filter behavior.\u00a0\n\n\u200c\n\n**Root Cause**\u00a0\n\nA software defect introduced during a performance optimization of site-based filtering logic caused certain filter criteria to be processed incorrectly. Under specific filter configurations, portions of the filtering logic were not applied as intended, resulting in broader device selection results than expected.\u00a0\n\nA corrective code change was validated and deployed to restore expected filter behavior.\u00a0\n\n\u200c\n\n**Incident Timeline**\u00a0\n\n**Identified:** 2026-07-31 00:30 UTC\u00a0\n\n**Public Notification:** 2026-07-31 01:48 UTC\u00a0\n\n**Resolved:** 2026-07-31 02:30 UTC\u00a0\n\n\u200c\n\n**Preventative Measures**\u00a0\n\nTo reduce the likelihood and impact of similar incidents in the future, we are taking the following steps:\u00a0\n\n**Enhancements to Release Management Practices**\u00a0\n\n* Expand unit test coverage for code changes to improve validation of functionality affected by application changes.\u00a0\n\n* Expand automated regression test coverage across filter functionality, including historical defect scenarios and previously identified filter-related use cases.\u00a0\n\n* Increase automated test coverage for critical customer workflows and core platform functionality to improve release readiness validation.\u00a0\n\n* Execute automated regression testing as part of both development and release validation processes.\u00a0\n\n* Evaluate additional release strategies such as customer beta testing, canary deployments, and blue/green deployments to enhance existing release strategies and further reduce risk, improve early issue detection, and minimize customer impact during software releases.\u00a0\n\n**Enhancements to Quality Assurance and Detection**\u00a0\n\n* Implement additional automated regression testing for filter functionality and related workflows.\u00a0\n\n* Additional scope will be added to automated Regression testing that covers functional completeness and accuracy to cover critical customer workflow validation\u00a0\u00a0\n\n* Expand monitoring and alerting around post-deployment validation activities to accelerate identification of release-related issues.\u00a0\n\n* Establish automated validation of key customer workflows following deployment to improve early detection of functional regressions during QA testing.\u00a0\n\n**Enhancements to Incident Recovery Capabilities**\u00a0\n\n* Implement automated post-deployment validation of critical workflows and use resulting signals to accelerate mitigation decisions when issues are detected post-release.\u00a0\n\n* Develop rollback capabilities to enable restoration to a known good release version when appropriate.\u00a0\n\n* Assess rollback mechanisms that align with future deployment strategy improvements, including staged deployment and service-based release models.\u00a0\n\n\u00a0\n\nThese improvements are intended to strengthen release validation, improve early detection of functional regressions, reduce restoration time during incidents, and limit the potential impact of future release-related issues.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-30T23:26:19.199-04:00", "resolved_inferred": false, "started_at": "2026-07-30T20:48:34.000-04:00", @@ -494,7 +496,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-30T16:04:38.927-04:00", "resolved_inferred": false, "started_at": "2026-07-30T09:44:43.793-04:00", @@ -507,7 +509,7 @@ "body": "Backups continue to process and all customer accounts hosted on pod 'gbe2-saas-p0' are accessible and functioning normally.\n\nThis incident is resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-29T16:15:06.271-04:00", "resolved_inferred": false, "started_at": "2026-07-29T06:55:57.907-04:00", @@ -520,7 +522,7 @@ "body": "# Summary: \n\nBetween 2026-07-28 14:53 UTC and 2026-07-29 14:38 UTC, Autotask customers hosted on zones AE01, AE02, AE03, AE04, AW01, AW02, AW03, AW04, PR01, LR01, ES01, AU01, and AU02 experienced a delay in inbound email ticket creation. \n\n# Root Cause: \n\nA configuration issue introduced during the deployment of a new environment resulted in unintended mailbox access conflicts, which unexpectedly interfered with normal email processing and delayed ticket creation from inbound emails. \n\n## Incident Timeline: \n\n* Identified: 2026-07-28 15:12 UTC \n* Public Notification: 2026-07-28 18:01 UTC \n* Mitigated: 2026-07-28 18:06 UTC \n* Resolved: 2026-07-29 14:38 UTC \n\n# Preventative Measures: \n\nTo reduce the likelihood and impact of similar incidents in the future, we are taking the following steps. \n\n* **Enhancements to Release and Configuration Management**: We are strengthening our environment deployment process by introducing additional validation and review checkpoints for configuration settings before new environments are brought into service. \n* **Enhancements to Monitoring and Alerting**: We are implementing additional monitoring and alerting for email processing workflows to enable faster detection and response when abnormal error rates occur. \n* **Enhancements to Service Resiliency**: We are improving email processing workflow to ensure messages are easier to reprocess if processing failures occur, reducing the amount of time required to remediate mail processing problems in the future. \n* **Enhancements to Diagnostics and Troubleshooting**: We are expanding operational logging and diagnostic capabilities to provide greater visibility into processing failures and accelerate root cause identification and recovery efforts. \n* **Enhancements to Incident Response**: We have reviewed and refined our operational procedures and recovery processes to reduce restoration times and minimize customer impact during future incidents.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-29T03:04:25.682-04:00", "resolved_inferred": false, "started_at": "2026-07-28T14:01:32.762-04:00", @@ -533,7 +535,7 @@ "body": "**Endpoint Backup v2\u00a0-\u00a0Assets in UniView may inaccurately report backup failures despite successful backup completion\u00a0\u2013 2026-07-27**\u00a0\n\n\u00a0\n\n**Summary:** Between **2026-07-27 20:00 UTC and 2026-07-28 23:30 UTC**, Endpoint Backup v2 customers experienced an issue in which assets within UniView incorrectly reported backup failures, despite backups completing successfully.\u00a0\n\n\u00a0\u00a0\n\n**Root Cause:**\u00a0\u00a0\n\nThe incident was caused by a processing capacity constraint that delayed the synchronization of backup status information. As a result, recently completed backups were not reflected in the user interface in a timely manner, creating visibility issues for customers. Backup operations continued to complete successfully, and no backup data was impacted.\u00a0\n\n\u00a0\n\n**Incident Timeline:**\u00a0\u00a0\n\n* Identified: **2026-07-27 20:00\u00a0UTC**\u00a0\u00a0\n\n* Public Notification: **2026-07-28 13:52 UTC**\u00a0\u00a0\n\n* Resolved: **2026-07-28 23:30\u00a0UTC**\u00a0\u00a0\n\n\u00a0\u00a0\n\n**Preventative Measures:** To reduce the likelihood and impact of similar incidents in the future, we are taking the following steps.\u00a0 \u00a0\n\n* Implemented a more efficient data synchronization mechanism to reduce processing overhead, improve system performance, and accelerate the delivery of updated information across the platform.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-29T19:59:44.369-04:00", "resolved_inferred": false, "started_at": "2026-07-28T08:52:54.364-04:00", @@ -546,7 +548,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-27T16:00:56.213-04:00", "resolved_inferred": false, "started_at": "2026-07-27T13:35:33.590-04:00", @@ -559,7 +561,7 @@ "body": "**Root Cause Analysis \u2013 VSA10 Intermittent Service Degradation Following 10.28 Release**\u00a0\n\n**Summary**\u00a0\n\nBetween **2026-07-24 02:00 UTC** and **2026-07-24 20:25 UTC**, some customers using VSA10 experienced intermittent service degradation, including temporary agent connectivity issues, delayed agent check-ins, and HTTP 503 errors. During periods of elevated automation activity, affected agents could appear to repeatedly transition between online and offline states before reconnecting automatically. The issue was fully resolved on July 24, 2026.\u00a0\u00a0\n\n**Root Cause**\u00a0\n\nA software change introduced in the 10.28 release altered how certain automation-related database operations were processed. Under high levels of concurrent automation activity, this change resulted in resource contention within the application environment, leading to intermittent service interruptions and delayed responses for agent communications. A hotfix was developed, tested, and deployed the same day to restore the previous transaction handling behavior and eliminate the contention condition.\u00a0\n\n**Incident Timeline**\u00a0\n\n* **Identified:** 2026-07-24 02:00 UTC\u00a0\n\n* **Public Notification:** 2026-07-24 13:27 UTC\u00a0\n\n* **Resolved:** 2026-07-24 20:25 UTC\u00a0\n\n**Preventative Measures**\u00a0\n\nTo reduce the likelihood and impact of similar incidents in the future, we are implementing the following improvements:\u00a0\n\n**Enhancements to Monitoring and Alerting**\u00a0\n\n* Introduce additional monitoring and alerting for database contention and long-running transactions to further accelerate detection of similar conditions.\u00a0\n\n* Expand service health dashboards to further improve visibility into application response performance.\u00a0\n\n**Enhancements to Release Management Practices**\u00a0\n\n* Implement expanded canary deployment procedures for higher-risk platform changes, allowing updates to be validated on a limited subset of infrastructure before broader rollout, further reducing the risk for these deployments.\u00a0\n\n* Add additional review requirements for changes affecting high-volume agent communication paths, further reducing risk for these deployments.\u00a0\n\n**Enhancements to Validation and Testing**\u00a0\n\n* Strengthen load and concurrency testing for components that support large-scale automation activity, further increasing scalability at the time of deployment.\u00a0\n\n* Increase validation coverage for scenarios that simulate production-scale agent workloads to catch scalability issues prior to deployment, further reducing risk.\u00a0\n\n**Enhancements to Platform Resiliency**\u00a0\n\n* Continue development of automation workload distribution improvements designed to reduce concentrated processing spikes during large-scale task execution, further increasing scalability at the time of deployment.\u00a0\n\n* Review additional service isolation and capacity improvements to further reduce the impact of localized workload surges.\u00a0\n\n**Completed Corrective Action**\u00a0\n\n* The software change responsible for the contention condition was reverted through a hotfix deployed on July 24, 2026. Following deployment, monitoring confirmed that error rates returned to normal levels and no recurrence of the issue was observed.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-24T17:23:58.368-04:00", "resolved_inferred": false, "started_at": "2026-07-24T09:27:23.650-04:00", @@ -572,7 +574,7 @@ "body": "**Datto Partner Portal - Intermittent HTTP 500 errors encountered when accessing the Portal and Recovery Launchpad \u2013 2026-07-24**\u00a0\n\n\u00a0\n\n**Summary:** Between **2026-07-24 03:00 AM UTC** and **2026-07-24 11:29 AM UTC**, Datto BCDR customers experienced login issues when attempting to access the Datto Partner Portal and Recovery Launchpad.\u00a0\n\n\u00a0\u00a0\n\n**Root Cause:**\u00a0\u00a0\n\nDuring the onboarding of a firewall environment into centralized management, an unexpected configuration synchronization event created an inconsistent configuration state. This resulted in the removal of critical routing information, loss of some VPN authentication settings, and the creation of duplicate configuration entries, causing an internet outage, delaying VPN recovery for affected sites, and preventing a standard rollback. Manual remediation and restoration to the last known stable configuration were required to fully recover services.\u00a0\u00a0\n\n\u00a0\n\n**Incident Timeline:**\u00a0\u00a0\n\n* Identified: 2026-07-24 03:00 AM UTC\u00a0\u00a0\n\n* Public Notification: 2026-07-24 08:47 AM UTC\u00a0\u00a0\n\n* Resolved: 2026-07-24 11:29 AM UTC\u00a0\u00a0\n\n\u00a0\u00a0\n\n**Preventative Measures:** To reduce the likelihood and impact of similar incidents in the future, we are taking the following steps.\u00a0\u00a0\u00a0\n\n* Implement VPN traffic baseline monitoring and alerting to detect abnormal activity and enable faster issue identification.\u00a0\n\n* Define a rollback SOP with clear decision criteria and timelines for outages caused by software defects during planned maintenance.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-24T06:29:46.905-04:00", "resolved_inferred": false, "started_at": "2026-07-24T04:47:27.144-04:00", @@ -585,7 +587,7 @@ "body": "# Summary: \n\nBetween 2026-07-23 14:44 UTC and 2026-07-23 19:41 UTC, KaseyaOne customers were unable to access the KaseyaOne Portal, and authentication into integrated applications that relied on KaseyaOne SSO was also impacted. \n\n# Root Cause: \n\nA network connectivity issue affecting the Microsoft Azure West US region caused service disruption for infrastructure supporting KaseyaOne. This resulted in loss of portal accessibility and SSO functionality until Microsoft restored regional connectivity. \n\n## Incident Timeline: \n\n* Identified: 2026-07-23 14:45 UTC \n* Public Notification: 2026-07-23 15:15 UTC \n* Resolved: 2026-07-23 19:41 UTC \n\n# Preventative Measures: \n\nTo reduce the likelihood and impact of similar incidents in the future, we are making Enhancements to Infrastructure Resiliency. Specifically: \n\n* Implementing a multi-region deployment architecture with designated primary and disaster recovery regions. This enhancement will reduce reliance on a single Azure region and improve service availability during regional infrastructure failures.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-23T17:19:29.116-04:00", "resolved_inferred": false, "started_at": "2026-07-23T11:15:08.000-04:00", @@ -598,7 +600,7 @@ "body": "**Datto Networking-\u00a0Web filtering policy changes fail to deploy to DNA and D200 appliances\u00a0\u2013 2026-07-17**\u00a0\n\n\u00a0\n\n**Summary:** Between **2026-07-17 10:37 PM UTC** and **2026-07-27\u00a002:45 PM UTC**, **Datto Networking** customers experienced an issue where web filtering configuration changes were not being successfully applied on the DNA and D200 appliances.\u00a0\n\n\u00a0\u00a0\n\n**Root Cause:**\u00a0\u00a0\n\nThe issue was traced to an application integration change that resulted in processing errors and prevented certain configuration updates from being applied successfully. An additional issue affecting the application of category-based configuration changes was also identified. Remediation for both issues was developed promptly.\u00a0\u00a0\n\n\u00a0\n\n**Incident Timeline:**\u00a0\u00a0\n\n* Identified: **2026-07-17 10:37 PM UTC**\u00a0\u00a0\n\n* Public Notification: **2026-07-23 02:37 PM UTC**\u00a0\u00a0\n\n* Resolved: **2026-07-27 02:45 PM UTC**\u00a0\u00a0\n\n\u00a0\u00a0\n\n**Preventative Measures:** To reduce the likelihood and impact of similar incidents in the future, we are taking the following steps.\u00a0 \u00a0\u00a0\n\n* Improve monitoring and alerting effectiveness to accelerate issue identification, streamline triage activities, and support service reliability.\u00a0\n\n* Complete the transition away from legacy infrastructure dependencies to improve platform resilience, reduce operational risk, and prevent similar issues from recurring.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-27T10:45:18.495-04:00", "resolved_inferred": false, "started_at": "2026-07-23T09:37:48.578-04:00", @@ -611,7 +613,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-23T05:24:53.284-04:00", "resolved_inferred": false, "started_at": "2026-07-23T04:22:22.298-04:00", @@ -624,7 +626,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-23T02:26:15.220-04:00", "resolved_inferred": false, "started_at": "2026-07-23T00:17:46.133-04:00", @@ -637,7 +639,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-21T14:42:03.874-04:00", "resolved_inferred": false, "started_at": "2026-07-21T14:05:46.256-04:00", @@ -650,7 +652,7 @@ "body": "**Root Cause Analysis \u2013 Datto RMM Merlot Intermittent User Interface Degradation**\n\n**Summary**\n\nBetween **2026-07-21 07:55 UTC** and **2026-07-21 17:00 UTC**, some customers on the Merlot platform experienced intermittent performance degradation within Datto RMM. During this period, users may have encountered slow-loading or failing pages, missing Global Search results, delayed or incomplete device summary information, and intermittent issues accessing certain functionality within the web interface. Service stability was restored following a series of remediation activities targeting the affected messaging and application services.\u00a0\n\n**Root Cause**\n\nOur investigation determined that the incident was caused by instability within a core messaging service dependency path used by several Datto RMM components. This instability impacted communication between application services, resulting in elevated backend resource utilization and intermittent failures of customer-facing workflows. The issue was further compounded by the persistence of unhealthy service connections from the recent incident the day prior, which contributed to message processing delays and reduced application responsiveness. Recovery required restarting the affected messaging infrastructure and dependent services, along with infrastructure adjustments to restore normal operation.\n\n**Incident Timeline**\n\n* Identified: 2026-07-21 07:55 UTC\n* Public Notification: 2026-07-21 08:55 UTC\n* Incident Monitoring: 2026-07-21 10:06 UTC\n* Additional Investigation: 2026-07-21 15:09 UTC\n* Resolved: 2026-07-21 17:14 UTC\n\n**Preventative Measures**\n\nTo reduce the likelihood and impact of similar incidents in the future, we are taking the following actions:\n\n* **Enhancing infrastructure resiliency** by improving service recovery mechanisms so dependent services can recover automatically when messaging infrastructure is restored, reducing the risk of cascading failures across connected services.\n\n* **Enhancing monitoring and alerting** by implementing additional monitoring for messaging service health, queue backlog growth, and end-to-end workflow execution so potential issues can be identified and resolved before customer impact occurs.\n\n* **Enhancing customer experience monitoring** by introducing workflow-based monitoring and dashboards focused on key customer journeys, allowing earlier identification of degraded user experiences within the platform.\n\n* **Enhancing incident management and response** by developing and documenting recovery procedures for messaging-path degradation scenarios, including validation steps to ensure all related services are operating normally before an incident is considered resolved.\n\n* **Enhancing post-incident validation** by adding additional dependency-aware validation checks following major recovery activities to confirm the health of interconnected services and reduce the likelihood of follow-on incidents.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-22T07:51:32.274-04:00", "resolved_inferred": false, "started_at": "2026-07-21T04:55:34.259-04:00", @@ -663,7 +665,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-22T10:18:49.018-04:00", "resolved_inferred": false, "started_at": "2026-07-08T08:37:14.386-04:00", diff --git a/api/v/dbt-cloud.json b/api/v/dbt-cloud.json index 8fef8e976a754b075c037725f32ad410e9bbf48e..40b3ab5cdbda9d28d8ad552b0c5c9d913356ef82 100644 --- a/api/v/dbt-cloud.json +++ b/api/v/dbt-cloud.json @@ -3,7 +3,7 @@ "slug": "dbt-cloud", "platform": "statuspage", "status_url": "https://status.getdbt.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "A configuration change affecting new account onboarding caused some customers signing up for a dbt State or dbt Wizard trial to be unable to create a project or proceed past the billing setup step. This impacted new trial sign-ups between 2026-09-03 11:48 UTC and 2026-09-03 12:53 UTC. The issue was resolved and all affected systems are functioning normally. Please contact Support at [support@getdbt.com](mailto:support@getdbt.com \"support@getdbt.com\") if you continue to experience issues or have any follow-up questions.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-09-03T13:25:48Z", "resolved_inferred": false, "started_at": "2026-09-03T13:24:41Z", @@ -24,7 +24,7 @@ "body": "The issue has been resolved, and all affected systems are now functioning normally as of 1:45 PM Eastern. Between 7:05 AM Eastern and 1:45 PM Eastern an issue with delayed metadata impacted the Discovery (Metadata) API in our EU2 region. We have put measures in place to prevent a recurrence and metadata ingestion has returned to normal. Please contact Support via email [support@getdbt.com](http://support@getdbt.com \"support@getdbt.com\") if you continue to experience delays and are unsure of the root cause.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-09-02T17:57:35Z", "resolved_inferred": false, "started_at": "2026-09-02T15:00:59Z", @@ -36,7 +36,7 @@ "body": "The issue has been resolved, and all affected systems are now functioning normally. Between 11 AM Eastern, August 25th, and 12 PM Eastern, August 26th, an issue with the [support@getdbt.com](mailto:support@getdbt.com \"support@getdbt.com\") email resulted in customers receiving \"address not found\" errors or unable to reach this email for support. We have put measures in place to prevent a recurrence and the [support@getdbt.com](mailto:support@getdbt.com \"support@getdbt.com\") email has returned to normal.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-26T21:49:19Z", "resolved_inferred": false, "started_at": "2026-08-26T15:58:36Z", @@ -48,7 +48,7 @@ "body": "This incident is resolved. Connections to Databricks warehouses in our AU region returned to normal operation at approximately August 25, 04:07 UTC, and we have seen no further errors since.\n\n \n\nDevelopment sessions in the IDE and job runs that rely on Databricks credentials are operating normally.\n\nPlease contact Support at [support@getdbt.com](mailto:support@getdbt.com) if you continue to experience issues or have any follow-up questions.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-25T04:59:59Z", "resolved_inferred": false, "started_at": "2026-08-25T04:23:49Z", @@ -60,7 +60,7 @@ "body": "The issue has been resolved, and all affected systems are now functioning normally as of 3:00PM UTC.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-24T15:00:00Z", "resolved_inferred": false, "started_at": "2026-08-24T15:44:38Z", @@ -72,7 +72,7 @@ "body": "A recent deployment to the Studio AI assistant (Wizard) caused it to lose required parameters when using its tools, resulting in failures for file reads and edits, git actions, and dbt commands run through the assistant. This impacted the Studio AI assistant across multiple multi-tenant instances between 2026-08-18 08:47 UTC and 2026-08-18 10:18 UTC. A fix has been released and all affected systems are functioning normally. Please contact Support at [support@getdbt.com](mailto:support@getdbt.com) if you continue to experience issues or have any follow-up questions.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-18T11:19:42Z", "resolved_inferred": false, "started_at": "2026-08-18T09:15:44Z", @@ -84,7 +84,7 @@ "body": "The issue has been resolved, and all affected systems are now functioning normally as of 5 PM Eastern. Between 9:30 AM Eastern and 5 PM Eastern a widespread GitHub outage resulted in multiple failures across git services within dbt Platform. [https://www.githubstatus.com/incidents/zkxwbgr0cnmx](https://www.githubstatus.com/incidents/zkxwbgr0cnmx \"https://www.githubstatus.com/incidents/zkxwbgr0cnmx\")\n\nPlease contact Support via email [support@getdbt.com](http://support@getdbt.com \"support@getdbt.com\") if you continue to experience issues and are unsure of the root cause.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-17T21:21:51Z", "resolved_inferred": false, "started_at": "2026-08-17T15:02:37Z", @@ -96,7 +96,7 @@ "body": "This issue has been resolved. AI agent functionality in dbt Copilot and dbt Studio is fully restored.\n\nPlease contact Support via email [support@getdbt.com](http://support@getdbt.com \"support@getdbt.com\") if you continue to experience delays and are unsure of the root cause.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-13T23:33:22Z", "resolved_inferred": false, "started_at": "2026-08-13T20:18:44Z", @@ -108,7 +108,7 @@ "body": "The issue has been resolved, and all affected systems are now functioning normally. \n\nBetween 10 Aug 22:16 - 23:33 UTC an issue with our platform's memory resulted in intermittent 500 or 502 errors with admin APIs requests.\n\n\nWe have put measures in place to prevent a recurrence and the admin API requests have returned to normal.\n\nPlease contact Support via email [support@getdbt.com](mailto:support@getdbt.com) if you continue to experience delays and are unsure of the root cause.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-11T01:30:12Z", "resolved_inferred": false, "started_at": "2026-08-10T23:26:19Z", @@ -120,7 +120,7 @@ "body": "A regression in a recent Fusion build affecting the BigQuery adapter led to incremental models being rebuilt from empty instead of updating incrementally. This impacted some customers using BigQuery as their connected data warehouse with cross-project execution/target configurations between August 4, 2026 at 20:00 UTC and August 9, 2026 at 17:15 UTC. The affected Fusion build was rolled back to the last known-good version, and all affected systems are functioning normally. Please contact Support at [support@getdbt.com](mailto:support@getdbt.com \"support@getdbt.com\") if you continue to experience issues or have any follow-up questions", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-09T17:43:41Z", "resolved_inferred": false, "started_at": "2026-08-09T16:25:44Z", @@ -132,7 +132,7 @@ "body": "Since our last update, we've continued to monitor AI Codegen (Wizard) in EMEA and error rates have remained normal. As of 09:16 UTC, 29 July 2026, this incident is resolved. ", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-29T09:18:19Z", "resolved_inferred": false, "started_at": "2026-07-29T09:12:59Z", @@ -144,7 +144,7 @@ "body": "A certificate configuration change affecting our multi-tenant AWS instances caused browsers to show certificate or \"insecure connection\" warnings when accessing the dbt platform. This impacted the US, AU, and EU/EMEA multi-tenant instances between approximately 2026-07-27 16:54 UTC and 2026-07-27 18:43 UTC. The issue has been resolved and all affected systems are functioning normally. Please contact Support at [support@getdbt.com](mailto:support@getdbt.com) if you continue to experience issues or have any follow-up questions.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-27T18:50:42Z", "resolved_inferred": false, "started_at": "2026-07-27T18:25:19Z", @@ -156,7 +156,7 @@ "body": "Intermittent job run failures during the git repository clone step affected our EMEA infrastructure. This impacted job runs between 2026-07-24 00:00 UTC and 2026-07-24 11:08 UTC. The issue has not recurred for over 3.5 hours and all affected systems are functioning normally. Please contact Support at [support@getdbt.com](mailto:support@getdbt.com) if you continue to experience issues or have any follow-up questions.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-24T14:58:03Z", "resolved_inferred": false, "started_at": "2026-07-24T07:58:08Z", @@ -168,7 +168,7 @@ "body": "The issue has been resolved and affected system is now functioning normally as of 5:25 AM UTC. \n\nEarlier, we had an issue that impacted editing and creating environment variables. We have put measures in place to prevent a recurrence and the user interface is now back to normal. \n\nPlease contact Support via email [support@getdbt.com](http://support@getdbt.com \"support@getdbt.com\") if you continue to experience issues and are unsure of the root cause.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-22T07:29:49Z", "resolved_inferred": false, "started_at": "2026-07-22T01:52:14Z", @@ -180,7 +180,7 @@ "body": "This incident is resolved. Scheduled, CI, and API-triggered job runs that clone from GitHub were failing at the \"Clone git repository\" step due to an upstream GitHub incident affecting SSH deploy key authentication.\n\nGitHub has resolved the underlying issue. Git clone error rates on the dbt platform have returned to normal and remained stable. Job runs are operating as expected, and any runs that failed during the incident can be safely retried.\n\nWe apologize for the disruption and thank you for your patience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-21T12:52:00Z", "resolved_inferred": false, "started_at": "2026-07-21T10:23:29Z", @@ -192,7 +192,7 @@ "body": "**Update \u2014 13:52 UTC**\n\nGit clone errors on prod-emea have not recurred and success rates have remained normal. We have not identified a definitive root cause on our side and are continuing to investigate internally. We are resolving this incident, but will follow up if new information becomes available.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-19T13:55:00Z", "resolved_inferred": false, "started_at": "2026-07-19T07:33:02Z", @@ -204,7 +204,7 @@ "body": "The issue has been resolved, and all affected systems are now functioning normally. We have confirmed that the impact was as a result of a GitHub outage: \nPlease contact Support via email [support@getdbt.com](mailto:support@getdbt.com) if you continue to experience delays and are unsure of the root cause.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-17T01:00:58Z", "resolved_inferred": false, "started_at": "2026-07-16T23:48:09Z", @@ -216,7 +216,7 @@ "body": "The issue has been resolved, and all affected systems are now functioning normally as of 10:50 UTC. Between 09:40 UTC and 10:50 UTC, an issue affecting [login.dbt.com](http://login.dbt.com) and account discovery resulted in intermittent slowness when signing in and loading account information. We have put measures in place to prevent a recurrence and the affected services have returned to normal. Please contact Support via email at [support@getdbt.com](mailto:support@getdbt.com) if you continue to experience delays and are unsure of the root cause.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-10T14:46:53Z", "resolved_inferred": false, "started_at": "2026-07-10T12:19:55Z", @@ -228,7 +228,7 @@ "body": "The issue has been resolved, and all affected systems are now functioning normally. Please contact Support via email [support@getdbt.com](http://support@getdbt.com \"support@getdbt.com\") if you continue to experience delays and are unsure of the root cause.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-07T01:30:57Z", "resolved_inferred": false, "started_at": "2026-07-07T00:55:07Z", @@ -240,7 +240,7 @@ "body": "The issue has been resolved, and all affected systems are now functioning normally as of 5:12PM Eastern. Please contact Support via email [support@getdbt.com](http://support@getdbt.com \"support@getdbt.com\") if you continue to experience delays and are unsure of the root cause.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-30T21:30:00Z", "resolved_inferred": false, "started_at": "2026-06-30T21:57:06Z", @@ -252,7 +252,7 @@ "body": "From 24 June 2:00 PM UTC to 25 June 2:00 PM UTC, users may have experienced latency or brief unavailability in API requests. These may have resulted in failed API requests, or job runs statuses not updating correctly. The issue has since been resolved and there should be no further impact. Please contact us at support@getdbt.com with any questions or concerns. We thank you for your patience and understanding.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-24T14:00:00Z", "resolved_inferred": false, "started_at": "2026-06-29T04:47:31Z", @@ -264,7 +264,7 @@ "body": "The issue has been resolved, and all affected systems are now functioning normally as of 20:18 UTC. \n Please contact Support via email [support@getdbt.com](http://support@getdbt.com \"support@getdbt.com\") if you continue to experience delays and are unsure of the root cause.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-25T15:41:32Z", "resolved_inferred": false, "started_at": "2026-06-24T16:14:34Z", @@ -276,7 +276,7 @@ "body": "The issue has been resolved, and all affected systems are now functioning normally. Please contact Support via email [support@getdbt.com](http://support@getdbt.com \"support@getdbt.com\") if you continue to experience delays and are unsure of the root cause.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-19T18:36:00Z", "resolved_inferred": false, "started_at": "2026-06-19T17:19:42Z", @@ -288,7 +288,7 @@ "body": "The issue has been resolved, and all affected systems are functioning normally . Between 04:00 EST and 04:53 EST an issue with the Global Login Service resulted in customers unable to login. Please contact Support via email [support@getdbt.com](http://support@getdbt.com \"support@getdbt.com\") if you continue to experience any issues regarding this.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-19T12:25:02Z", "resolved_inferred": false, "started_at": "2026-06-19T08:52:14Z", @@ -300,7 +300,7 @@ "body": "The issue has been resolved, and all affected systems are now functioning normally. Between 19 Jun 00:00 - 06:50 UTC, an issue with login resulted in users receiving \"Access denied\" error at authentication. \n\nWe have put measures in place to prevent a recurrence and all system has returned to normal. \n\nPlease contact Support via email [support@getdbt.com](http://support@getdbt.com \"support@getdbt.com\") if you continue to experience delays and are unsure of the root cause.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-19T07:55:20Z", "resolved_inferred": false, "started_at": "2026-06-19T06:16:14Z", diff --git a/api/v/dead-man-s-snitch.json b/api/v/dead-man-s-snitch.json index 8cdd8705f02c1dd749fb0825d6e7ca326f23df40..6d2f05b759b98dcbd666ae7258819312d1d08f8e 100644 --- a/api/v/dead-man-s-snitch.json +++ b/api/v/dead-man-s-snitch.json @@ -3,7 +3,7 @@ "slug": "dead-man-s-snitch", "platform": "statuspage", "status_url": "https://status.deadmanssnitch.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "Maintenance on our primary message bus is done and all systems are back to normal. This kind of maintenance shouldn't be causing timeouts or delayed processing and we will be digging into it to ensure it doesn't occur again.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-22T19:03:45.184-05:00", "resolved_inferred": false, "started_at": "2025-11-22T12:12:00.630-05:00", @@ -25,7 +25,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-20T15:18:39.589-04:00", "resolved_inferred": false, "started_at": "2025-10-20T13:19:17.364-04:00", diff --git a/api/v/deepsource.json b/api/v/deepsource.json index ba25bae48a11828bee88077c42e7bd3b0b3ddad6..31ebd05ffb3d654be99a07d1b15608253edc8dd5 100644 --- a/api/v/deepsource.json +++ b/api/v/deepsource.json @@ -3,7 +3,7 @@ "slug": "deepsource", "platform": "betterstack", "status_url": "https://status.deepsource.io", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "unknown", "history_backfilled": false, "first_watched": "2026-09-04T07:06:16Z", diff --git a/api/v/degreed.json b/api/v/degreed.json index 110541dbd50e286e124bcd4bb87131a5bc7985d9..9191b9b05772a1828894780b3555ba6ec53f93cc 100644 --- a/api/v/degreed.json +++ b/api/v/degreed.json @@ -3,7 +3,7 @@ "slug": "degreed", "platform": "statuspage", "status_url": "https://degreed.statuspage.io", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "This incident has been resolved, and site performance has returned to normal.\n\nA Root Cause Analysis is currently in progress and will be published in the Knowledge Center by the end of the week. Customers with open support tickets related to this incident will be notified once it is available.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-31T18:11:15.567Z", "resolved_inferred": false, "started_at": "2026-08-31T15:25:03.989Z", @@ -25,7 +25,7 @@ "body": "The US Degreed platform has been fully restored. Our engineering team implemented a fix to our underlying infrastructure, and we will continue to closely monitor the systems to ensure ongoing stability.\nA full root cause analysis will be shared in the coming days. We are grateful for your patience and apologize for the inconvenience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-23T17:44:28.000Z", "resolved_inferred": false, "started_at": "2026-06-23T14:29:33.632Z", @@ -38,7 +38,7 @@ "body": "Search has been restored to full performance. Our team has completed the necessary mitigation steps and the system is stable. We will continue to monitor closely to ensure everything remains healthy. Thank you for your patience throughout this incident.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-08T19:49:48.688Z", "resolved_inferred": false, "started_at": "2026-04-08T16:04:16.411Z", @@ -51,7 +51,7 @@ "body": "Search Performance and Integration Data Sync\n\nWe\u2019re pleased to share that Degreed Search services have been fully restored, and Search functionality is now operating at normal performance levels. Our engineering teams will continue to actively monitor service health to ensure ongoing stability.\n\nAlso, all remaining integration data that was queued in our database has now been successfully synced therefore all content, user, and learning information is fully up to date.\n\nThis will be our final message on this issue, and we sincerely appreciate your continued patience and understanding throughout the resolution process. For any related questions, please reach out to our Support team or your Account Director.\n\nA full root cause analysis will be shared in the coming days. Thank you again for your patience and partnership.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-01T02:25:15.075Z", "resolved_inferred": false, "started_at": "2026-02-26T09:02:13.477Z", @@ -64,7 +64,7 @@ "body": "The Zendesk issue caused by the Cloudflare outage has now been resolved and all services are operating normally.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-05T11:03:54.454Z", "resolved_inferred": false, "started_at": "2025-12-05T10:14:55.959Z", @@ -77,7 +77,7 @@ "body": "We have resolved the issue affecting search performance. Response times and result consistency have returned to normal. We continue to monitor closely for any anomalies to ensure full stability.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-25T19:19:49.701Z", "resolved_inferred": false, "started_at": "2025-11-25T14:27:38.032Z", @@ -90,7 +90,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-18T17:06:39.977Z", "resolved_inferred": false, "started_at": "2025-11-18T13:27:42.479Z", @@ -103,7 +103,7 @@ "body": "Resolved: The issue has been fully resolved, and all systems are now operating normally.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-03T17:56:29.422Z", "resolved_inferred": false, "started_at": "2025-11-03T15:08:52.597Z", @@ -116,7 +116,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-29T22:31:04.717Z", "resolved_inferred": false, "started_at": "2025-10-29T16:19:46.901Z", @@ -129,7 +129,7 @@ "body": "This incident has been resolved. \nUsers in all regions should now be able to log in successfully via SSO.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-27T16:43:30.408Z", "resolved_inferred": false, "started_at": "2025-08-27T16:01:01.000Z", @@ -142,7 +142,7 @@ "body": "The issue has been resolved. Please note that pending reports are still processing and may take 12\u201324 hours to fully complete. We appreciate your patience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-06T21:40:45.852Z", "resolved_inferred": false, "started_at": "2025-08-06T20:39:00.497Z", diff --git a/api/v/dell-boomi.json b/api/v/dell-boomi.json index d5ddcd9853a9a8f4145250f28bd452c4061913b2..690d0ad298cb486fccdab204f86b7ac1d703d621 100644 --- a/api/v/dell-boomi.json +++ b/api/v/dell-boomi.json @@ -3,7 +3,7 @@ "slug": "dell-boomi", "platform": "statuspage", "status_url": "https://status.boomi.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "Our engineering team has corrected the issue and Boomi Data Integration API and Data Integration Console is operating as expected.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-06T12:21:17.673Z", "resolved_inferred": false, "started_at": "2026-08-06T10:15:01.205Z", @@ -25,7 +25,7 @@ "body": "Our engineering team has corrected the issue and Boomi Platform UI and Public API is operating as expected.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-29T20:23:16.280Z", "resolved_inferred": false, "started_at": "2026-07-29T18:05:29.944Z", @@ -38,7 +38,7 @@ "body": "Our engineering team has corrected the issue, and the Boomi Platform UI and Public API on Statuspage are operating as expected.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-29T17:00:57.428Z", "resolved_inferred": false, "started_at": "2026-07-29T15:33:44.365Z", @@ -51,7 +51,7 @@ "body": "Our engineering team has corrected the issue and Boomi Platform UI, Public API and Process Reporting Document Metadata is operating as expected.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-20T12:11:04.597Z", "resolved_inferred": false, "started_at": "2026-07-20T08:43:53.965Z", @@ -64,7 +64,7 @@ "body": "Our engineering team has corrected the issue and Boomi USA East Data Integration API Degraded is operating as expected.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-12T08:06:48.981Z", "resolved_inferred": false, "started_at": "2026-06-12T04:17:38.016Z", @@ -77,7 +77,7 @@ "body": "Our engineering team has corrected the issue and Boomi Process Reporting Document Metadata is operating as expected.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-25T12:56:18.182Z", "resolved_inferred": false, "started_at": "2026-04-25T10:35:31.975Z", @@ -90,7 +90,7 @@ "body": "Our engineering team has corrected the issue and Boomi MFT Automated File Transfer is operating as expected.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-31T03:40:59.229Z", "resolved_inferred": false, "started_at": "2026-03-31T01:26:22.105Z", @@ -103,7 +103,7 @@ "body": "Our engineering team has corrected the issue and Boomi USA North Central File Sharing Cloud is operating as expected.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-09T16:32:47.889Z", "resolved_inferred": false, "started_at": "2026-03-09T15:33:31.649Z", @@ -116,7 +116,7 @@ "body": "Our engineering team has corrected the issue and Boomi Process Reporting Document Metadata is operating as expected.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-04T20:04:35.700Z", "resolved_inferred": false, "started_at": "2026-03-04T13:25:46.198Z", @@ -129,7 +129,7 @@ "body": "Our engineering team has corrected the issue and Boomi Platform UI and Public API is operating as expected.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-23T08:52:15.895Z", "resolved_inferred": false, "started_at": "2026-01-23T07:04:32.579Z", @@ -142,7 +142,7 @@ "body": "Our engineering team has corrected the issue and Boomi USA Central Automated File Transfer Cloud is operating as expected.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-22T17:55:55.223Z", "resolved_inferred": false, "started_at": "2026-01-22T15:42:40.603Z", @@ -155,7 +155,7 @@ "body": "Our engineering team has corrected the issue and Boomi West Integration Cloud is operating as expected.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-12T21:14:30.858Z", "resolved_inferred": false, "started_at": "2026-01-12T20:23:20.453Z", @@ -168,7 +168,7 @@ "body": "Our engineering team has corrected the issue and Boomi Data Integration (API and Console) is operating as expected.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-03T15:03:37.442Z", "resolved_inferred": false, "started_at": "2026-01-03T11:23:51.180Z", @@ -181,7 +181,7 @@ "body": "Our engineering team has corrected the issue and Boomi Process Reporting Document Metadata is operating as expected.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-15T17:07:17.217Z", "resolved_inferred": false, "started_at": "2025-12-14T17:23:28.588Z", @@ -194,7 +194,7 @@ "body": "Our engineering team has corrected the issue and Boomi Data Integration Service is operating as expected.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-11T20:47:29.091Z", "resolved_inferred": false, "started_at": "2025-12-11T20:33:03.018Z", @@ -207,7 +207,7 @@ "body": "The Boomi Cloud API Management service is now back in good health and the issue that caused degradation has been resolved.\n\nThis is the final update from us on this issue.\n\nPlease contact us via Boomi Support Center (https://community.boomi.com/s/support) for any questions or concerns.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-06T23:38:05.284Z", "resolved_inferred": false, "started_at": "2025-12-06T22:27:18.767Z", @@ -220,7 +220,7 @@ "body": "The Boomi Cloud API Management service is now back in good health and the issue that caused degradation has been resolved.\n\nThis is the final update from us on this issue.\n\nPlease contact us via Boomi Support Center (https://community.boomi.com/s/support) for any questions or concerns.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-05T05:21:26.674Z", "resolved_inferred": false, "started_at": "2025-12-05T04:38:04.153Z", @@ -233,7 +233,7 @@ "body": "Our engineering team has corrected the issue and Boomi DEU Hub Cloud is operating as expected. \n\nWe will conduct an internal review of this issue and make appropriate improvements to our system to help prevent or minimize future recurrence.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-03T23:56:33.923Z", "resolved_inferred": false, "started_at": "2025-11-29T15:17:00.000Z", @@ -246,7 +246,7 @@ "body": "Our engineering team has corrected the issue and Boomi USA East Data Integration is operating as expected.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-21T08:00:30.000Z", "resolved_inferred": false, "started_at": "2025-11-21T07:30:10.000Z", @@ -259,7 +259,7 @@ "body": "Our engineering team has corrected the issue and Boomi GBR Automated File Transfer Cloud is operating as expected.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-18T17:40:24.182Z", "resolved_inferred": false, "started_at": "2025-11-18T13:18:37.000Z", @@ -272,7 +272,7 @@ "body": "Our engineering team has corrected the issue and Boomi USA East Data Integration API and Console is operating as expected.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-12T20:16:32.000Z", "resolved_inferred": false, "started_at": "2025-11-12T19:37:29.000Z", @@ -285,7 +285,7 @@ "body": "Our engineering team has corrected the issue and Boomi USA East Data Integration API and Console is operating as expected.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-12T19:34:10.000Z", "resolved_inferred": false, "started_at": "2025-11-12T14:04:50.636Z", @@ -298,7 +298,7 @@ "body": "Our engineering team has corrected the issue and Boomi DEU Integration Cloud 01 Status is operating as expected.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-03T17:05:57.056Z", "resolved_inferred": false, "started_at": "2025-11-03T12:07:57.653Z", @@ -311,7 +311,7 @@ "body": "Our engineering team has corrected the issue and Boomi Process Reporting Document Metadata is operating as expected for all new executions. Please note that users may still experience delays in updates to Process Reporting for the affected period as we work through the backlog of messages.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-25T18:40:08.329Z", "resolved_inferred": false, "started_at": "2025-10-25T11:46:52.000Z", @@ -324,7 +324,7 @@ "body": "Our engineering team has corrected the issue and Boomi Process Reporting Document Metadata is operating as expected.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-20T12:35:09.877Z", "resolved_inferred": false, "started_at": "2025-10-20T11:06:57.428Z", @@ -337,7 +337,7 @@ "body": "Our engineering team has corrected the issue and Boomi Cloud API Management platform is operating as expected.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-20T12:19:42.102Z", "resolved_inferred": false, "started_at": "2025-10-20T09:29:51.076Z", @@ -350,7 +350,7 @@ "body": "Our engineering team has corrected the issue and Boomi ANZ File Sharing Cloud is operating as expected.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-25T22:52:52.469Z", "resolved_inferred": false, "started_at": "2025-09-25T22:17:25.673Z", @@ -363,7 +363,7 @@ "body": "Our engineering team has corrected the issue and Boomi Enterprise Platform is operating as expected.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-22T17:15:08.170Z", "resolved_inferred": false, "started_at": "2025-09-22T16:33:59.408Z", @@ -376,7 +376,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-04T22:34:14.678Z", "resolved_inferred": false, "started_at": "2025-08-04T18:47:53.334Z", diff --git a/api/v/deno-deploy.json b/api/v/deno-deploy.json index 5376aaf9d624f1708ddb90f4db451b92cc93ca05..919214251bd70508a8aac801f89835d8c3931a5e 100644 --- a/api/v/deno-deploy.json +++ b/api/v/deno-deploy.json @@ -3,7 +3,7 @@ "slug": "deno-deploy", "platform": "instatus", "status_url": "https://denostatus.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": false, "first_watched": "2026-09-04T07:06:16Z", diff --git a/api/v/deskpro.json b/api/v/deskpro.json index 4f3e11eaffe12028ed828c0717cbcfca18a0d41f..a1ca2c7981529c05e513f637eaed8d69e849fe8f 100644 --- a/api/v/deskpro.json +++ b/api/v/deskpro.json @@ -3,7 +3,7 @@ "slug": "deskpro", "platform": "statuspage", "status_url": "https://www.deskprostatus.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "The issue has been fixed, and AI functionality is now working normally.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-20T18:20:19.713+01:00", "resolved_inferred": false, "started_at": "2026-08-20T16:13:17.037+01:00", @@ -25,7 +25,7 @@ "body": "This issue has been resolved. The cause was an internal change to how our systems renew their access credentials, which left file storage temporarily unreachable. Access was restored automatically at 07:00 UTC and the change has been corrected. Only the EU region was affected. We are sorry for the disruption.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-19T11:36:01.680+01:00", "resolved_inferred": false, "started_at": "2026-08-19T08:42:03.379+01:00", @@ -38,7 +38,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-27T14:42:33.761+01:00", "resolved_inferred": false, "started_at": "2026-07-24T10:27:48.065+01:00", @@ -51,7 +51,7 @@ "body": "Between 7:30am and 7:44am BST this morning, access to Deskpro was degraded for approximately 14 minutes. The disruption occurred during scheduled infrastructure maintenance, part of our ongoing hardening work following the recent service incident. The maintenance took longer to apply than anticipated. Service was fully restored at 7:44am and all systems are operating normally. No data was lost or affected.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-15T07:30:00.000+01:00", "resolved_inferred": false, "started_at": "2026-07-15T07:30:00.000+01:00", @@ -64,7 +64,7 @@ "body": "Between approximately 13:36 and 14:15 BST, some customers experienced errors and slow performance when using Deskpro. This was caused by an issue with one of our database servers. Our team identified the affected server and rerouted traffic away from it, restoring normal performance. We've opened an investigation with our infrastructure provider to determine the root cause.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-13T13:30:00.000+01:00", "resolved_inferred": false, "started_at": "2026-07-13T13:30:00.000+01:00", @@ -77,7 +77,7 @@ "body": "This issue is now resolved. We have removed the mitigations that were put in place and confirmed normal operation. We'll continue to monitor closely to ensure stability and will provide a further update if anything changes.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-26T14:54:42.379+01:00", "resolved_inferred": false, "started_at": "2026-06-15T16:39:19.146+01:00", @@ -90,7 +90,7 @@ "body": "The issue has now been resolved.\n\nAgent replies on WhatsApp and Meta social channels are sending as expected.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-26T10:07:58.595+01:00", "resolved_inferred": false, "started_at": "2026-05-20T13:03:23.825+01:00", @@ -103,7 +103,7 @@ "body": "Inbound call alerting has been restored for all affected customers.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-07T16:22:23.435+01:00", "resolved_inferred": false, "started_at": "2026-05-07T10:13:25.534+01:00", @@ -116,7 +116,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-23T23:32:25.211+01:00", "resolved_inferred": false, "started_at": "2026-04-23T18:40:23.837+01:00", @@ -129,7 +129,7 @@ "body": "After monitoring over the weekend, this incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-30T11:49:34.250+01:00", "resolved_inferred": false, "started_at": "2026-03-27T12:38:05.269+00:00", @@ -142,7 +142,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-06T15:50:09.211+00:00", "resolved_inferred": false, "started_at": "2026-02-06T13:54:20.646+00:00", @@ -155,7 +155,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-08T09:54:10.993+00:00", "resolved_inferred": false, "started_at": "2026-01-08T08:52:44.882+00:00", @@ -168,7 +168,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-10T11:10:56.104+00:00", "resolved_inferred": false, "started_at": "2025-12-10T08:39:50.271+00:00", @@ -181,7 +181,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-24T20:25:15.231+00:00", "resolved_inferred": false, "started_at": "2025-11-24T11:50:05.000+00:00", @@ -194,7 +194,7 @@ "body": "Cloudflare report that the issue has been resolved.\n\nNormal service should be fully restored. If you continue to experience any issues, please reach out to support@deskpro.com.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-18T15:04:07.281+00:00", "resolved_inferred": false, "started_at": "2025-11-18T12:46:30.000+00:00", @@ -207,7 +207,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-02T18:44:47.578+01:00", "resolved_inferred": false, "started_at": "2025-10-01T11:00:13.000+01:00", diff --git a/api/v/devolutions.json b/api/v/devolutions.json index 5c51d5e981db50e1967cbcab8faccda596fa0e32..58fa124cccd323bb3f491012a093c54f0c493139 100644 --- a/api/v/devolutions.json +++ b/api/v/devolutions.json @@ -3,7 +3,7 @@ "slug": "devolutions", "platform": "statuspage", "status_url": "http://status.devolutions.net", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-19T14:29:29.113-04:00", "resolved_inferred": false, "started_at": "2026-08-19T11:52:28.568-04:00", @@ -25,7 +25,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-22T13:20:22.619-04:00", "resolved_inferred": false, "started_at": "2026-07-22T08:29:02.661-04:00", @@ -38,7 +38,7 @@ "body": "The incident has been resolved. If you are using the encryption service, you may need to restart it if you still encounter errors.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-14T11:06:54.061-04:00", "resolved_inferred": false, "started_at": "2026-07-14T03:55:20.608-04:00", @@ -51,7 +51,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-30T14:21:24.909-04:00", "resolved_inferred": false, "started_at": "2026-06-29T10:17:57.441-04:00", @@ -64,7 +64,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-28T10:58:40.366-04:00", "resolved_inferred": false, "started_at": "2026-06-28T10:03:23.407-04:00", @@ -77,7 +77,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-17T16:19:16.912-04:00", "resolved_inferred": false, "started_at": "2026-04-17T13:14:41.236-04:00", @@ -90,7 +90,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-31T11:16:19.967-04:00", "resolved_inferred": false, "started_at": "2026-03-31T08:06:44.499-04:00", @@ -103,7 +103,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-11T11:03:33.231-04:00", "resolved_inferred": false, "started_at": "2026-03-11T10:44:24.109-04:00", @@ -116,7 +116,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-01T10:57:20.156-05:00", "resolved_inferred": false, "started_at": "2026-03-01T09:45:24.145-05:00", @@ -129,7 +129,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-04T13:47:27.842-05:00", "resolved_inferred": false, "started_at": "2026-02-04T13:28:08.687-05:00", @@ -142,7 +142,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-03T15:24:05.800-05:00", "resolved_inferred": false, "started_at": "2026-02-03T14:15:08.955-05:00", @@ -155,7 +155,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-03T12:17:02.412-05:00", "resolved_inferred": false, "started_at": "2026-02-03T10:30:11.728-05:00", @@ -168,7 +168,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-07T11:51:40.037-05:00", "resolved_inferred": false, "started_at": "2026-01-07T11:20:31.405-05:00", @@ -181,7 +181,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-09T16:20:25.617-05:00", "resolved_inferred": false, "started_at": "2025-12-09T15:03:28.371-05:00", @@ -194,7 +194,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-18T15:32:10.804-05:00", "resolved_inferred": false, "started_at": "2025-11-18T14:32:47.315-05:00", @@ -207,7 +207,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-18T12:00:05.445-05:00", "resolved_inferred": false, "started_at": "2025-11-18T07:47:38.138-05:00", @@ -220,7 +220,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-29T08:56:11.084-04:00", "resolved_inferred": false, "started_at": "2025-10-29T08:27:32.464-04:00", @@ -233,7 +233,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-08T12:31:58.423-04:00", "resolved_inferred": false, "started_at": "2025-10-08T12:08:43.212-04:00", @@ -246,7 +246,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-07T13:44:29.167-04:00", "resolved_inferred": false, "started_at": "2025-10-07T09:54:04.853-04:00", @@ -259,7 +259,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-04T23:43:32.211-04:00", "resolved_inferred": false, "started_at": "2025-10-04T23:03:53.053-04:00", diff --git a/api/v/digicert.json b/api/v/digicert.json index e1e5249bbcbcf4de8a7d81830910e0b1c590dc86..fac15d64a83947c50ac58d5881d979aebd0b841d 100644 --- a/api/v/digicert.json +++ b/api/v/digicert.json @@ -3,16 +3,27 @@ "slug": "digicert", "platform": "statuspage", "status_url": "https://status.digicert.com", -"last_checked": "2026-09-04T09:06:33Z", -"last_state": "ok", +"last_checked": "2026-09-04T10:17:20Z", +"last_state": "partial", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", "incidents": [ { +"body": "We are currently experiencing a technical problem with our DigiCert Support Email System and are working to resolve the issue as quickly as possible.\n\nWe are tracking this issue under Case# 05116620\n\nWhile we work to restore access to our DigiCert Support Email System , you can contact us through:\nTelephone: Call us\n\nChat: Chat with us\n\nEmail: Message us\n\nWe apologize for any inconvenience this may cause you.\n \nDigiCert Support\n\nWe apologize for any inconvenience this may cause you.\n\n\nDigiCert Support\n\n\u30c7\u30b8\u30b5\u30fc\u30c8 \u30a6\u30a7\u30d6\u30b5\u30a4\u30c8\u30bb\u30ad\u30e5\u30ea\u30c6\u30a3\u30a2\u30e9\u30fc\u30c8\u60c5\u5831 \u2013 DigiCert Alert\n\n\u73fe\u5728\u3001 DigiCert Support Email System \u306f\u30c6\u30af\u30cb\u30ab\u30eb\u9762\u306b\u304a\u3051\u308b\u554f\u984c\u304c\u78ba\u8a8d\u3055\u308c\u3066\u304a\u308a\u3001\u5fa9\u65e7\u306b\u3080\u3051\u3066\u8abf\u67fb\u3092\u9032\u3081\u3066\u3044\u307e\u3059\u3002\n\n\u30b1\u30fc\u30b9\u756a\u53f7 05116620\n\n\u4f55\u304b\u3054\u4e0d\u660e\u306a\u70b9\u3001\u3054\u8cea\u554f\u7b49\u304c\u3054\u3056\u3044\u307e\u3057\u305f\u3089\u3053\u3061\u3089\u304b\u3089\u304a\u9858\u3044\u3044\u305f\u3057\u307e\u3059\u3002\nTelephone: Call us\n\nChat: Chat with us\n\nEmail: Message us\n\n\u3054\u4e0d\u4fbf\u3092\u304a\u639b\u3051\u3057\u3066\u7533\u3057\u8a33\u3054\u3056\u3044\u307e\u305b\u3093\u304c\u3001\u4f55\u5352\u3054\u7406\u89e3\u306e\u307b\u3069\u3088\u308d\u3057\u304f\u304a\u9858\u3044\u3044\u305f\u3057\u307e\u3059\u3002\n\n\u30c7\u30b8\u30b5\u30fc\u30c8\u30a6\u30a7\u30d6\u30b5\u30a4\u30c8\u30bb\u30ad\u30e5\u30ea\u30c6\u30a3\u30b5\u30dd\u30fc\u30c8", +"first_seen": "2026-09-04T10:17:20Z", +"impact": "major", +"last_seen": "2026-09-04T10:17:20Z", +"started_at": "2026-09-04T10:03:50.640Z", +"state": "investigating", +"title": "DigiCert Support Email System Alert", +"updated_at": "2026-09-04T10:03:50.759Z", +"url": "https://stspg.io/3k64t6nf77zm" +}, +{ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-19T17:30:32.685Z", "resolved_inferred": false, "started_at": "2026-08-19T17:10:54.280Z", @@ -25,7 +36,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-13T17:47:06.390Z", "resolved_inferred": false, "started_at": "2026-08-13T16:37:31.886Z", @@ -38,7 +49,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-11T19:32:20.908Z", "resolved_inferred": false, "started_at": "2026-08-11T18:45:30.000Z", @@ -51,7 +62,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-03T14:30:43.181Z", "resolved_inferred": false, "started_at": "2026-08-03T12:35:35.000Z", @@ -64,7 +75,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-01T06:58:12.908Z", "resolved_inferred": false, "started_at": "2026-08-01T06:22:10.672Z", @@ -77,7 +88,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-24T11:40:36.526Z", "resolved_inferred": false, "started_at": "2026-07-24T09:52:43.000Z", @@ -90,7 +101,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-17T21:04:58.402Z", "resolved_inferred": false, "started_at": "2026-07-17T20:23:55.045Z", @@ -103,7 +114,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-01T20:11:08.644Z", "resolved_inferred": false, "started_at": "2026-07-01T18:11:57.000Z", @@ -116,7 +127,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-08T11:20:58.100Z", "resolved_inferred": false, "started_at": "2026-06-08T09:47:47.425Z", @@ -129,7 +140,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-01T11:12:28.267Z", "resolved_inferred": false, "started_at": "2026-06-01T10:17:23.816Z", @@ -142,7 +153,7 @@ "body": "The issue has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-19T18:13:17.094Z", "resolved_inferred": false, "started_at": "2026-05-19T12:46:01.645Z", @@ -155,7 +166,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-15T16:47:13.431Z", "resolved_inferred": false, "started_at": "2026-05-15T16:28:56.978Z", @@ -168,7 +179,7 @@ "body": "This issue has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-11T11:04:02.546Z", "resolved_inferred": false, "started_at": "2026-05-11T08:47:44.222Z", @@ -181,7 +192,7 @@ "body": "The incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-11T14:52:36.890Z", "resolved_inferred": false, "started_at": "2026-05-11T07:44:22.273Z", @@ -194,7 +205,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-28T16:10:16.304Z", "resolved_inferred": false, "started_at": "2026-04-28T10:02:04.570Z", @@ -207,7 +218,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-23T14:26:06.150Z", "resolved_inferred": false, "started_at": "2026-04-23T08:14:00.735Z", @@ -220,7 +231,7 @@ "body": "The incident has been resolved and response time has been consistently good in the DC1 US Prod instance for all the managers.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-23T11:59:41.186Z", "resolved_inferred": false, "started_at": "2026-04-23T06:52:37.185Z", @@ -233,7 +244,7 @@ "body": "The response time has improved and customers confirmed recovery.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-15T14:08:31.690Z", "resolved_inferred": false, "started_at": "2026-04-15T09:34:02.986Z", @@ -246,7 +257,7 @@ "body": "The incident has been resolved and signings are going through fine.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-18T16:35:03.422Z", "resolved_inferred": false, "started_at": "2026-03-18T15:00:00.807Z", @@ -259,7 +270,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-12T05:30:16.681Z", "resolved_inferred": false, "started_at": "2026-03-12T04:42:19.267Z", @@ -272,7 +283,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-05T16:28:27.837Z", "resolved_inferred": false, "started_at": "2026-03-05T13:27:53.615Z", @@ -285,7 +296,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-19T19:47:01.688Z", "resolved_inferred": false, "started_at": "2026-02-19T11:28:18.740Z", @@ -298,7 +309,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-12T06:11:48.851Z", "resolved_inferred": false, "started_at": "2026-02-12T05:41:02.000Z", @@ -311,7 +322,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "maintenance", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-10T20:28:20.388Z", "resolved_inferred": false, "started_at": "2026-02-10T15:33:35.066Z", @@ -324,7 +335,7 @@ "body": "The incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-02T15:16:52.007Z", "resolved_inferred": false, "started_at": "2026-02-02T13:03:45.358Z", @@ -337,7 +348,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-22T08:44:22.223Z", "resolved_inferred": false, "started_at": "2026-01-22T08:01:01.021Z", @@ -350,7 +361,7 @@ "body": "We are continuing to investigate this issue.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-21T17:17:15.414Z", "resolved_inferred": false, "started_at": "2026-01-21T16:55:48.573Z", @@ -363,7 +374,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-19T11:43:46.061Z", "resolved_inferred": false, "started_at": "2026-01-19T11:21:26.019Z", @@ -376,7 +387,7 @@ "body": "The incident has been resolved", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-09T12:18:29.332Z", "resolved_inferred": false, "started_at": "2026-01-09T11:10:32.894Z", @@ -389,7 +400,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-18T09:52:09.343Z", "resolved_inferred": false, "started_at": "2025-12-18T06:46:30.460Z", @@ -402,7 +413,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-19T14:48:54.824Z", "resolved_inferred": false, "started_at": "2025-11-19T11:08:37.539Z", @@ -415,7 +426,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-12T15:20:55.946Z", "resolved_inferred": false, "started_at": "2025-11-12T14:30:40.393Z", @@ -428,7 +439,7 @@ "body": "All the affected customers confirmed that they are no more seeing timeouts during signing", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-13T14:29:31.381Z", "resolved_inferred": false, "started_at": "2025-11-12T07:58:56.213Z", @@ -441,7 +452,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-11T14:35:59.839Z", "resolved_inferred": false, "started_at": "2025-11-11T11:46:26.271Z", @@ -454,7 +465,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-12T01:02:33.332Z", "resolved_inferred": false, "started_at": "2025-11-11T10:08:21.514Z", @@ -467,7 +478,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-11T21:57:18.975Z", "resolved_inferred": false, "started_at": "2025-11-11T08:50:47.000Z", @@ -480,7 +491,7 @@ "body": "Incident has been resolved", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-10T16:24:32.018Z", "resolved_inferred": false, "started_at": "2025-11-10T09:35:13.255Z", @@ -493,7 +504,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-29T20:34:06.513Z", "resolved_inferred": false, "started_at": "2025-10-29T16:37:06.544Z", @@ -506,7 +517,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-14T21:21:39.469Z", "resolved_inferred": false, "started_at": "2025-10-14T20:48:38.095Z", @@ -519,7 +530,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-03T15:19:40.636Z", "resolved_inferred": false, "started_at": "2025-10-03T14:58:33.000Z", @@ -532,7 +543,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-28T17:07:25.115Z", "resolved_inferred": false, "started_at": "2025-09-28T13:38:32.657Z", @@ -545,7 +556,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-25T15:29:25.560Z", "resolved_inferred": false, "started_at": "2025-09-25T11:48:24.549Z", @@ -558,7 +569,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-23T12:54:28.473Z", "resolved_inferred": false, "started_at": "2025-09-23T07:57:14.326Z", @@ -571,7 +582,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-11T18:55:26.255Z", "resolved_inferred": false, "started_at": "2025-09-11T18:44:43.352Z", @@ -584,7 +595,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-07T09:42:09.888Z", "resolved_inferred": false, "started_at": "2025-09-07T08:01:18.000Z", @@ -597,7 +608,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-04T00:54:00.228Z", "resolved_inferred": false, "started_at": "2025-09-04T00:29:31.368Z", @@ -610,7 +621,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-26T17:12:33.227Z", "resolved_inferred": false, "started_at": "2025-08-26T16:02:26.000Z", @@ -623,7 +634,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-21T23:10:37.291Z", "resolved_inferred": false, "started_at": "2025-08-21T22:52:30.364Z", @@ -636,7 +647,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-20T18:02:47.118Z", "resolved_inferred": false, "started_at": "2025-08-20T17:40:48.207Z", diff --git a/api/v/digital-pacific.json b/api/v/digital-pacific.json index 068141762797d581bbd6cee8824a0d3ea57be3a3..ad129b7989e7187e56828c3dfaad263b12f34467 100644 --- a/api/v/digital-pacific.json +++ b/api/v/digital-pacific.json @@ -3,7 +3,7 @@ "slug": "digital-pacific", "platform": "statuspage", "status_url": "https://www.dpstatus.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "The issue affecting email delivery and website availability has now been resolved.\n \nOur Engineering Team has confirmed that websites and email services are operating normally.\n \nWe will continue to monitor the services to ensure stability.\n \nWe appreciate your patience and understanding while we worked to address this issue.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "started_at": "2026-09-01T21:29:49.085+10:00", "state": "monitoring", "title": "Service Disruption \u2013 Email Delivery and Website Availability", @@ -23,7 +23,7 @@ "body": "Our phone support lines have now been restored and are fully operational.\n\nOur engineers have completed the necessary work to resolve the issue and are taking steps to help prevent it from happening again.\n\nWe apologize for the inconvenience and appreciate your patience and understanding.\n\nLive Chat Support: Our live chat support remains available 24/7 if you need further assistance.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-14T11:59:17.571+10:00", "resolved_inferred": false, "started_at": "2026-08-14T11:12:19.729+10:00", @@ -36,7 +36,7 @@ "body": "Dear Customers,\n\ncPanel has released a security update to address CVE-2026-58048, a database privilege escalation vulnerability affecting supported cPanel & WHM versions. We strongly recommend that all customers update their servers to the patched versions available.\n\nPlease refer to the official advisories below for more details:\n\nhttps://support.cpanel.net/hc/en-us/articles/42285745783703-Security-CVE-2026-58048-Database-Privilege-Escalation\n\nAction Required \n\nPlease log in to your server via SSH as the root user and run the following command:\n\n/scripts/upcp\n\nThis command will download and install the latest available cPanel & WHM updates, including the security fixes released by cPanel.\n\nAfter the update completes, verify your cPanel version:\n\n/usr/local/cpanel/cpanel -V\n\nWhy This Update required \n\nThis security release addresses a vulnerability that could allow privilege escalation within the database environment. Applying the latest cPanel update is the recommended mitigation from cPanel and helps protect your server from potential exploitation.\n\nIf you are unable to perform the update or experience any issues during the upgrade process, please contact our support team. We will be happy to assist you.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "started_at": "2026-08-03T20:29:38.055+10:00", "state": "monitoring", "title": "Security Advisory: Immediate cPanel Update Recommended for VPS & Dedicated Servers", @@ -47,7 +47,7 @@ "body": "The issue affecting the email services, along with webmail access, has now been resolved. Our Engineering Team will continue to closely monitor the situation to ensure ongoing stability.\nWe appreciate your patience and understanding while we worked to address this matter. Please be assured that we will continue to provide updates should any new developments arise.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-03T20:20:49.543+10:00", "resolved_inferred": false, "started_at": "2026-07-31T11:49:29.979+10:00", @@ -60,7 +60,7 @@ "body": "The issue affecting email delivery to Hotmail domains has been resolved, and email delivery has returned to normal.\n\nOur Engineering Team has completed the necessary work, and we are no longer observing the reported delivery issue.\n\nThank you for your patience and understanding while we worked to resolve this issue.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-12T21:38:20.480+10:00", "resolved_inferred": false, "started_at": "2026-07-29T22:12:03.667+10:00", @@ -73,7 +73,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-29T22:05:51.356+10:00", "resolved_inferred": false, "started_at": "2026-07-21T14:08:54.713+10:00", @@ -86,7 +86,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-12T20:09:57.220+10:00", "resolved_inferred": false, "started_at": "2026-07-03T19:57:49.794+10:00", @@ -99,7 +99,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-29T22:14:44.753+10:00", "resolved_inferred": false, "started_at": "2026-06-15T08:38:15.415+10:00", @@ -112,7 +112,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-29T22:17:44.197+10:00", "resolved_inferred": false, "started_at": "2026-06-05T13:59:06.308+10:00", @@ -125,7 +125,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-29T22:19:12.853+10:00", "resolved_inferred": false, "started_at": "2026-05-18T14:05:06.655+10:00", @@ -138,7 +138,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-29T22:19:38.383+10:00", "resolved_inferred": false, "started_at": "2026-05-09T03:44:31.704+10:00", @@ -151,7 +151,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-29T22:19:59.378+10:00", "resolved_inferred": false, "started_at": "2026-05-08T16:59:02.883+10:00", @@ -164,7 +164,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-29T22:20:19.264+10:00", "resolved_inferred": false, "started_at": "2026-04-29T16:29:09.772+10:00", @@ -177,7 +177,7 @@ "body": "Our engineering team has completed the necessary corrective actions, and services have now been restored. All impacted servers are back online and operating normally.\n\nWe sincerely apologise for the disruption and thank you for your patience while we worked to resolve this matter.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-30T10:59:17.279+10:00", "resolved_inferred": false, "started_at": "2025-09-22T11:18:05.000+10:00", diff --git a/api/v/digital-pigeon.json b/api/v/digital-pigeon.json index 87195b6b153a87e5ece5191a9975fad05f00eb88..65c70ce7019d8ee41ede0b508f5acdf5a4182834 100644 --- a/api/v/digital-pigeon.json +++ b/api/v/digital-pigeon.json @@ -3,7 +3,7 @@ "slug": "digital-pigeon", "platform": "statuspage", "status_url": "https://status.digitalpigeon.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", diff --git a/api/v/digitalocean.json b/api/v/digitalocean.json index c125b1628a7d171cd6a0ee9ab05dbeaab9de8e05..6f3c3eafcdc06d84c2a6f1bdf7ac0c5fbe5ef86d 100644 --- a/api/v/digitalocean.json +++ b/api/v/digitalocean.json @@ -3,7 +3,7 @@ "slug": "digitalocean", "platform": "statuspage", "status_url": "https://status.digitalocean.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "Our Engineering team has confirmed all services remain stable and we will now resolve this incident. Further details on root cause and mitigation will be provided in a postmortem via this status page for users interested in learning more. \n\nThank you for your patience throughout this incident. If you continue to experience any issues, please reach out to Support from within your account", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-25T19:04:33.091Z", "resolved_inferred": false, "started_at": "2026-08-24T17:14:43.701Z", @@ -25,7 +25,7 @@ "body": "Our Engineering team has resolved the issue preventing cluster creation on Managed Databases in the NYC3 and NYC1 regions. Customers can now create new Managed Databases Clusters normally.\n\nOur Engineering team has monitored the environment to ensure stability. We sincerely apologize for any inconvenience this disruption may have caused to your operations. If you continue to experience issues, please open a ticket with our Support team: https://cloudsupport.digitalocean.com/s/", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-23T14:33:31.719Z", "resolved_inferred": false, "started_at": "2026-08-23T05:11:37.000Z", @@ -38,7 +38,7 @@ "body": "Our Engineering team has confirmed that the issue impacting Container Registry and Spaces accessibility has been resolved. \n\nSpaces accessibility via the Cloud Control Panel is now restored, and pushing and pulling container images is succeeding as expected. Customers who previously encountered these issues should now be able to access Spaces and deploy their container images without further issues.\n\nIf you continue to experience any problems, please open a ticket with our support team. Thank you for your patience, and we apologize for any inconvenience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-21T14:52:40.373Z", "resolved_inferred": false, "started_at": "2026-08-21T12:59:42.692Z", @@ -51,7 +51,7 @@ "body": "Our Engineering team has confirmed the regional control plane is healthy and CPU Droplets, Managed databases, Load balancers, Block storage, Kubernetes (DOKS) and Spaces are operating normally.\n\nGPU Droplets continue to be impacted and our teams are working to restore all nodes. We will communicate with GPU Droplet customers separately via Slack and email with more information and regular updates.\n\nThank you for your patience throughout this incident. If you continue to experience any issues, please open a support ticket from within your account.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-19T19:34:54.136Z", "resolved_inferred": false, "started_at": "2026-08-19T11:10:06.329Z", @@ -64,7 +64,7 @@ "body": "Between Aug 13, 09:50 UTC and 14:30 UTC, customers in the FRA1 region experienced an issue affecting Block Storage Volumes attachment and detachment operations on Droplets and Managed Kubernetes clusters.\n\nDuring this window, customers may have encountered delays or been unable to attach and detach Block Storage Volumes from their resources.\n\nBlock Storage Volumes attachment and detachment operations now appear to be functioning normally, and customers should no longer experience issues with these operations. For Managed Kubernetes clusters specifically, some residual cleanup of affected volume attachments may still be needed, and our team is actively working through this.\n\nWe apologize for any inconvenience this may have caused. If you continue to experience issues with Block Storage Volumes operations, please don't hesitate to open a support ticket for further investigation. Our team will be happy to assist you.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-13T14:59:44.895Z", "resolved_inferred": false, "started_at": "2026-08-13T14:59:44.847Z", @@ -77,7 +77,7 @@ "body": "Our Engineering team confirms the full resolution of the issue affecting all impacted services, including new account registration, Droplet Creation, Reserved IPs, Automated Backups and Snapshots, Droplet Autoscale, DOKS clusters, GenAI services, the Droplet Console, and Database cluster creation.\n\nWe apologize for the inconvenience. If you continue to experience any issues, please open a support ticket from within your account.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-09T01:01:02.727Z", "resolved_inferred": false, "started_at": "2026-08-08T18:57:49.228Z", @@ -90,7 +90,7 @@ "body": "Our Engineering team has confirmed that the issue affecting Functions on App Platform has been fully resolved. Functions builds, deploys, and requests to Functions endpoints are all working as expected. The fix implemented earlier was successful, and we are no longer seeing any problems affecting Functions.\n\nHowever, if you continue to experience any issues, please don't hesitate to raise a support ticket for further investigation.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-06T21:05:05.672Z", "resolved_inferred": false, "started_at": "2026-08-06T19:01:27.576Z", @@ -103,7 +103,7 @@ "body": "Between Aug 6, 06:42 UTC and 09:08 UTC, customers experienced failures with write operations across multiple DigitalOcean services, including Managed Databases, DOKS, Cloud Firewalls, DNS, Spaces, Block Storage Volumes, and event processing.\n\nCustomers attempting to update Cloud Firewall rules, modify DNS records, manage object storage operations, provision or scale DOKS clusters and node pools, and make other infrastructure configuration changes experienced failures. These operations returned errors, preventing customers from managing their resources. Additionally, event processing was delayed or failed during this window, which may have impacted the timeliness of resource status updates and notifications.\n\nThe services have recovered and are now operating normally. Customers should no longer experience issues with write operations, configuration changes, or event processing.\n\nWe apologize for any inconvenience this may have caused. If you continue to experience issues with any of these services, please don't hesitate to open a support ticket. Our team will be happy to assist you.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-06T16:33:14.860Z", "resolved_inferred": false, "started_at": "2026-08-06T16:33:14.787Z", @@ -116,7 +116,7 @@ "body": "As of 21:06 UTC, our Engineering team has resolved the issue affecting Spaces Cold Storage billing. An error in our billing processing system caused incorrect values to be reflected in daily usage and current invoices for customers with cold storage buckets.\n\nOur team identified and corrected an issue with the billing data sync, ensuring accurate usage reporting. If you continue to experience any issues, please open a ticket with our Support team. We apologize for any inconvenience this may have caused.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-04T21:42:43.197Z", "resolved_inferred": false, "started_at": "2026-08-04T16:13:35.593Z", @@ -129,7 +129,7 @@ "body": "Between 09:36 and 13:30 UTC on August 3, some customers experienced intermittent errors while accessing the DigitalOcean Cloud Control Panel. We renewed the affected internal certificates and restored access. The issue is resolved, and the Cloud Control Panel is operating normally. We apologize for the disruption.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-03T17:59:42.943Z", "resolved_inferred": false, "started_at": "2026-08-03T13:58:04.872Z", @@ -142,7 +142,7 @@ "body": "Our Engineering team has resolved the issue causing empty or broken responses from Kimi-K3. If you continue to experience any problems, please open a ticket with our Support team. We apologize for any inconvenience this may have caused.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-30T06:15:55.395Z", "resolved_inferred": false, "started_at": "2026-07-29T17:56:51.011Z", @@ -155,7 +155,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-28T15:24:28.800Z", "resolved_inferred": false, "started_at": "2026-07-27T18:31:40.584Z", @@ -168,7 +168,7 @@ "body": "Between 07:46\u00a0 UTC & 10:24 UTC today, some users in India accessing resources in the NYC region may have experienced connectivity issues. The impact was limited to users using Airtel as their ISP.\n\nOur investigation determined that the issue was caused by an internal network issue within Airtel and was not related to DigitalOcean network. The connectivity issue now appears to be resolved, and users should no longer experience problems accessing their resources.\n\nWe apologize for any inconvenience this may have caused. However, if you continue to experience any connectivity issues, please don't hesitate to open a support ticket for further investigation; we'll be happy to assist you further.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-24T12:42:25.955Z", "resolved_inferred": false, "started_at": "2026-07-24T10:36:52.252Z", @@ -181,7 +181,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-23T12:37:00.025Z", "resolved_inferred": false, "started_at": "2026-07-23T11:16:59.123Z", @@ -194,7 +194,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-22T19:42:17.085Z", "resolved_inferred": false, "started_at": "2026-07-22T16:50:42.474Z", @@ -207,7 +207,7 @@ "body": "Our Engineering team has confirmed that the issue regarding volume attachment to Droplets in the NYC1, NYC3, SGP1, SYD1, and BLR1 regions has been fully resolved, and all services are now operating normally.\n\nIf you continue to experience any issues, please contact our Support team by opening a ticket. We apologize for any inconvenience caused.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-19T15:32:39.578Z", "resolved_inferred": false, "started_at": "2026-07-19T09:51:19.000Z", @@ -220,7 +220,7 @@ "body": "Our engineering team has resolved the outbound network connectivity issue in the BLR1 region. If you continue to experience problems, please open a ticket with our support team. We apologize for any inconvenience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-19T09:52:00.733Z", "resolved_inferred": false, "started_at": "2026-07-19T06:57:41.458Z", @@ -233,7 +233,7 @@ "body": "Our Engineering team has confirmed that the underlying issue affecting Reserved IP routing in the TOR1 region has been fully resolved, and services are now operating normally.\n\nIf you continue to experience any issues, please contact our Support team by opening a ticket. We apologize for any inconvenience caused.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-16T17:24:35.996Z", "resolved_inferred": false, "started_at": "2026-07-16T13:39:47.134Z", @@ -246,7 +246,7 @@ "body": "The deployed fix has successfully restored full functionality, and our monitoring shows that system performance has completely stabilized. Response times for all Gemma 4 inference workflows have returned to normal baseline levels.\nWe will continue to track platform stability moving forward to ensure long-term reliability. We apologize for any disruption this may have caused to your workflows and appreciate your patience throughout the recovery process.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-15T21:46:35.616Z", "resolved_inferred": false, "started_at": "2026-07-13T19:04:10.240Z", @@ -259,7 +259,7 @@ "body": "The issue affecting Kubernetes deployments in the NYC1 region has been resolved. Our investigation found intermittent DNS timeouts affecting a small number of DOKS clusters, with affected worker nodes running on shared-CPU Droplets. This is a documented limitation for latency-sensitive cluster DNS workloads such as CoreDNS.\n\nThe affected clusters are currently functional. To reduce the risk of recurrence, we recommend running CoreDNS on non-shared/dedicated CPU node pools and using sufficient CoreDNS replicas. \n\nIf you continue to see DNS failures or NodeNotReady events, please open a support ticket so we can investigate that cluster specifically.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-11T01:27:56.795Z", "resolved_inferred": false, "started_at": "2026-07-09T20:31:52.156Z", @@ -272,7 +272,7 @@ "body": "Our Engineering team has confirmed that the issue with the Deepseek V4 Pro model in Serverless Inference and Agent Platform has been fully resolved. The model is now operational, and users should be able to use it without experiencing any errors.\n\nIf you continue to experience any problems, please open a ticket with our Support team. We apologize for any inconvenience this may have caused and appreciate your patience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-05T00:53:19.389Z", "resolved_inferred": false, "started_at": "2026-07-04T22:13:45.293Z", @@ -285,7 +285,7 @@ "body": "Our Engineering team has confirmed that the issue impacting Droplets in the NYC3 region has been fully resolved. Users can now perform actions on their Droplets or create new Droplets in this region without any issues.\n\nWe appreciate your patience while we worked to resolve this issue. If you continue to experience any problems, please open a support ticket from your account so our team can investigate further.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-04T15:10:06.071Z", "resolved_inferred": false, "started_at": "2026-07-04T14:42:47.881Z", @@ -298,7 +298,7 @@ "body": "Our engineering team has resolved the issue with Managed Database Clusters. All database systems should now be operating normally. If you continue to experience problems, please open a ticket with our support team. We apologize for any inconvenience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-03T08:20:23.462Z", "resolved_inferred": false, "started_at": "2026-07-02T22:04:53.265Z", @@ -311,7 +311,7 @@ "body": "The intermittent DNS lookup failures between Managed Kubernetes and Managed Database hostnames in the FRA1 region have been resolved for now but please let us know if you see the issue again. Connectivity has remained stable, and all systems are operating normally. If you continue to experience any problems, please open a ticket with our support team. Thank you for your patience, and we apologize for any inconvenience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-01T16:28:25.933Z", "resolved_inferred": false, "started_at": "2026-07-01T11:35:28.934Z", @@ -324,7 +324,7 @@ "body": "Our Engineering team has confirmed that the issue impacting Droplet resizes using the \"Downscale Anytime\" option has been fully resolved. Users can now resize their Droplets using the \"Downscale Anytime\" option without any issues.\n\nWe appreciate your patience while we worked to resolve this issue. If you continue to experience any problems, please open a support ticket from your account so our team can investigate further.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-01T13:28:10.841Z", "resolved_inferred": false, "started_at": "2026-07-01T11:13:21.135Z", @@ -337,7 +337,7 @@ "body": "This incident has been resolved, and our teams continue to monitor the results. If you experience any further issues, please contact support.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-02T03:38:53.338Z", "resolved_inferred": false, "started_at": "2026-07-01T06:25:23.501Z", @@ -350,7 +350,7 @@ "body": "Between 00:00 UTC & 16:00 UTC today, our Engineering team identified an issue affecting backup operations on Droplets. During this period, backups scheduled within this window may not have been created and may appear as missing.\n\nOur team has taken necessary measures to resolve the issue, and we can confirm that the backup service has been restored and is now functioning normally. Upcoming scheduled backups should be performed as expected.\n\nWe sincerely apologize for any inconvenience this may have caused and appreciate your understanding. However, if you have any further questions or concerns, please create a support ticket for further analysis.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-27T18:24:25.102Z", "resolved_inferred": false, "started_at": "2026-06-27T18:24:25.041Z", @@ -363,7 +363,7 @@ "body": "Our Engineering team has resolved the issue that was causing HTTP 400 errors for requests to Anthropic models. Users should now be able to access Anthropic models without any issues.\nIf you continue to experience problems, please open a ticket with our Support team so we can investigate further.\nWe apologize for any inconvenience this may have caused.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-27T05:15:38.421Z", "resolved_inferred": false, "started_at": "2026-06-27T04:43:29.854Z", @@ -376,7 +376,7 @@ "body": "Between 13:22 & 14:26 UTC today, users have experienced missing monitoring graphs for Droplets (with DO agent installed), Load Balancers, Databases, and other services within the Cloud Control Panel.\n\nOur engineering team has identified the root cause of the issue and has taken appropriate steps to restore functionality. We can confirm that services have been restored and are functioning as expected.\n\nWe apologize for any inconvenience this may have caused. If you continue to experience issues viewing monitoring graphs, please create a support ticket for further analysis. Thank you for your patience and understanding", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-19T16:37:38.303Z", "resolved_inferred": false, "started_at": "2026-06-19T14:00:32.960Z", @@ -389,7 +389,7 @@ "body": "The connectivity issues affecting our Serverless/GenAI Inference API have been fully resolved.\nOur engineering teams successfully completed the connectivity restoration. All systems should be functioning normally, and the endpoint should be fully operational.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-17T00:29:42.280Z", "resolved_inferred": false, "started_at": "2026-06-16T22:00:52.000Z", @@ -402,7 +402,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-11T17:42:05.051Z", "resolved_inferred": false, "started_at": "2026-06-11T14:24:20.851Z", @@ -415,7 +415,7 @@ "body": "Between 09:41 and 11:24 UTC, our Engineering team identified an issue impacting the DNS API service. During this period, users may have experienced issues performing domain and DNS record management operations through the Control Panel and API. Services dependent on DNS API operations, including Let's Encrypt certificate provisioning, MongoDB cluster creation, App Platform deployments, and DigitalOcean Kubernetes (DOKS) cluster create and delete operations, were also impacted.\n\nOur Engineering team has confirmed that the underlying issue affecting the DNS API service has been fully resolved, and all affected services are now operating normally.\n\nIf you continue to experience any issues, please contact our Support team by opening a ticket. We apologize for any inconvenience caused.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-04T11:47:05.272Z", "resolved_inferred": false, "started_at": "2026-06-04T10:12:10.120Z", @@ -428,7 +428,7 @@ "body": "Our Engineering team has confirmed that the issue impacting build failures on App Platform has been resolved at 07:00 am UTC. All App Platform builds are now succeeding as expected. Customers who previously encountered build failures should now be able to deploy their applications without further issues.\n\nIf you continue to experience any problems, please open a ticket with our support team. Thank you for your patience, and we apologize for any inconvenience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-29T07:58:23.373Z", "resolved_inferred": false, "started_at": "2026-05-29T00:14:19.240Z", @@ -441,7 +441,7 @@ "body": "Between 06:35 UTC & 12:36 UTC today, our engineering team identified an issue impacting the Cloud Firewall. During this period, users might have encountered issues while updating their firewall rules.\n\nOur team has taken appropriate measures to address the issue. We can confirm that service has been restored and is now functioning normally.\n\nWe regret the inconvenience caused and appreciate your patience and understanding. However, if you continue to experience any issues, please create a support ticket for further analysis.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-20T13:03:09.605Z", "resolved_inferred": false, "started_at": "2026-05-20T12:08:27.021Z", @@ -454,7 +454,7 @@ "body": "Our Engineering team has verified that the issue causing incorrect Cloud Firewall rules to display on the cloud panel is fully resolved. The user interface continues to function as expected, and all systems have returned to normal operating conditions.\n\nIf you continue to experience problems, please open a ticket with our support team. Thank you for your patience throughout this incident.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-20T07:48:14.980Z", "resolved_inferred": false, "started_at": "2026-05-20T05:35:48.457Z", @@ -467,7 +467,7 @@ "body": "From 00:00 UTC to 01:40 UTC, users may have experienced degraded write performance and intermittent impacts to workloads dependent on Block Storage Volumes in the NYC3 region.\n\nOur Engineering team has confirmed that the underlying infrastructure issue affecting Block Storage Volumes at the storage layer has been fully resolved, and services are now operating normally.\n\nIf you continue to experience any issues, please contact our Support team by opening a ticket. We apologize for any inconvenience caused.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-20T05:13:50.000Z", "resolved_inferred": false, "started_at": "2026-05-20T01:05:16.154Z", @@ -480,7 +480,7 @@ "body": "As of the current time, our Engineering team has confirmed that the issue with Serverless Inference has been resolved. The root cause of the issue was an outage with our provider, Anthropic, which affected users of Sonnet 4.6 and Opus 4.7 models. According to Anthropic's status page (https://status.claude.com/incidents/8z7l5zcy0v3b), they have resolved the outage. If you continue to experience problems, please open a ticket with our Support team. We apologize for any inconvenience this may have caused.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-15T02:00:39.064Z", "resolved_inferred": false, "started_at": "2026-05-15T01:21:51.685Z", @@ -493,7 +493,7 @@ "body": "As of 19:50 UTC, the issue affecting the DNS service has been fully resolved, and all related services, including Let's Encrypt certificate issuance and Managed MongoDB provisioning, are now operating normally.\n\nThe backlog of delayed requests has been successfully processed, and all DNS record updates, pending certificate, and MongoDB operations should now be complete. \n\nWe apologize for the disruption this caused and appreciate your patience while our team worked to restore full functionality.\n\nHowever, if you continue to experience any issues, please don't hesitate to raise a support ticket for further investigation. We'll be happy to assist you.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-14T20:46:40.334Z", "resolved_inferred": false, "started_at": "2026-05-14T13:57:38.574Z", @@ -506,7 +506,7 @@ "body": "The remediation for the issue affecting the GradientAI Agent Platform Playground has been fully implemented, and the service is operating normally. We are no longer observing customer impact related to this issue, and the incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-12T11:37:12.000Z", "resolved_inferred": false, "started_at": "2026-05-12T10:24:07.025Z", @@ -519,7 +519,7 @@ "body": "Between 5:35 and 14:25 UTC today, our Engineering team identified an issue that prevents enabling Two-Factor Authentication (2FA) and Google/GitHub authentication through the Control Panel. During this period, users might have encountered issues while enabling authentication methods and accessing teams with secure sign-in enabled.\n\nOur team has taken appropriate measures to address the issue. We can confirm that service has been restored and is now functioning normally.\n\nWe regret the inconvenience caused. However, if you continue to experience any issues, please create a support ticket for further analysis.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-09T14:42:15.691Z", "resolved_inferred": false, "started_at": "2026-05-09T11:15:11.260Z", @@ -532,7 +532,7 @@ "body": "The upstream outage with Let's Encrypt has been resolved. Customers should now be able to issue Let's Encrypt certificates for Spaces, Load Balancers, and App Platform Custom Domains. Our Engineering team has also confirmed that stuck or delayed actions with Mongo, Advanced PG, and Advanced MySQL databases should complete normally now. \n\nWe appreciate your patience. If you continue to experience any issues, please open a support ticket from within your account.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-08T21:54:44.593Z", "resolved_inferred": false, "started_at": "2026-05-08T20:46:22.108Z", @@ -545,7 +545,7 @@ "body": "Our engineering team has resolved the issue with multiple services in NYC2 region, and all services should now be operating normally. If you continue to experience problems, please open a ticket with our support team. We apologize for any inconvenience and thank you for your patience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-08T19:59:48.942Z", "resolved_inferred": false, "started_at": "2026-05-08T18:01:42.481Z", @@ -558,7 +558,7 @@ "body": "All services are operating normally. We will continue to monitor the system to ensure ongoing reliability.\n\nThank you for your patience while we worked to resolve this issue.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-28T19:33:38.769Z", "resolved_inferred": false, "started_at": "2026-04-28T13:45:20.299Z", @@ -571,7 +571,7 @@ "body": "The issue is resolved, and service is operating normally.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-27T11:37:36.467Z", "resolved_inferred": false, "started_at": "2026-04-27T10:38:30.000Z", @@ -584,7 +584,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-23T23:51:58.178Z", "resolved_inferred": false, "started_at": "2026-04-23T22:26:34.000Z", @@ -597,7 +597,7 @@ "body": "Our Engineering team has confirmed that the issue impacting App Platform deployments and Kubernetes (DOKS) nodes has been fully resolved at 09:22 UTC. Users may already notice improvements while deploying apps and DOKS nodes.\n\nAll App Platform deployments are now succeeding as expected. Customers who previously encountered build failures should now be able to deploy their applications without further issues.\n\nIf you continue to experience any problems, please open a ticket with our support team. Thank you for your patience, and we apologize for any inconvenience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-23T10:09:54.770Z", "resolved_inferred": false, "started_at": "2026-04-23T08:08:37.488Z", @@ -610,7 +610,7 @@ "body": "Our Engineering team has confirmed full resolution of the issue with Cloud UI for Managed Kubernetes at 09:19 UTC.\n\nAll the services should be functioning as expected.\n\nIf you continue to experience problems, please open a ticket with our support team. Thank you for your patience throughout this incident!", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-23T08:46:39.799Z", "resolved_inferred": false, "started_at": "2026-04-23T07:01:46.702Z", @@ -623,7 +623,7 @@ "body": "Our Engineering team has resolved the issue that was impacting the DigitalOcean API and the Cloud Control Panel. The system is now operating normally.\n\nDuring the incident, users may have experienced difficulties accessing droplets, viewing the Droplets page, or performing CRUD (Create, Read, Update, Delete) operations via the API. We have verified that the issue has been fully resolved.\n\nWe apologize for the inconvenience this may have caused. If you continue to experience any issues, please submit a support ticket through the Cloud Control Panel so our team can assist you further.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-22T11:47:38.128Z", "resolved_inferred": false, "started_at": "2026-04-22T11:06:49.867Z", @@ -636,7 +636,7 @@ "body": "Our Engineering team has confirmed that the issue affecting the DNS resolution of .co top-level domain (TLD) has been resolved. The DNS resolution for .co domains is now working as expected.\n\nWe apologize for the inconvenience. If you continue to face any issues, please open a support ticket from within your account.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-18T14:10:35.084Z", "resolved_inferred": false, "started_at": "2026-04-17T21:22:52.396Z", @@ -649,7 +649,7 @@ "body": "From 17:22 to 17:46 UTC, our Engineering team observed an issue impacting Spaces availability in the NYC3 region. During this time, customers may have encountered 500 errors and degraded performance while accessing Spaces buckets. The issue has now been fully resolved. If you continue to experience problems, please open a ticket with our support team from within your Cloud Control Panel. We apologize for any inconvenience caused.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-17T18:27:09.864Z", "resolved_inferred": false, "started_at": "2026-04-17T18:27:09.813Z", diff --git a/api/v/discord.json b/api/v/discord.json index d445dfccde9b450a94b59596b0bcbd33ac9df096..1fb93ca20f87a8c1ae9df1e02ea15017a3480f6a 100644 --- a/api/v/discord.json +++ b/api/v/discord.json @@ -3,7 +3,7 @@ "slug": "discord", "platform": "statuspage", "status_url": "https://discordstatus.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-09-03T15:27:33.274-07:00", "resolved_inferred": false, "started_at": "2026-09-03T14:31:27.760-07:00", @@ -25,7 +25,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-09-03T08:37:47.454-07:00", "resolved_inferred": false, "started_at": "2026-09-03T07:35:27.281-07:00", @@ -38,7 +38,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-09-02T16:42:44.301-07:00", "resolved_inferred": false, "started_at": "2026-09-02T16:26:42.223-07:00", @@ -51,7 +51,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-09-02T11:26:50.199-07:00", "resolved_inferred": false, "started_at": "2026-09-02T09:12:20.853-07:00", @@ -64,7 +64,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-31T17:49:17.176-07:00", "resolved_inferred": false, "started_at": "2026-08-31T15:54:05.942-07:00", @@ -77,7 +77,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-13T23:24:04.508-07:00", "resolved_inferred": false, "started_at": "2026-08-13T23:09:38.232-07:00", @@ -90,7 +90,7 @@ "body": "This issue has been fully resolved", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-07T16:02:18.715-07:00", "resolved_inferred": false, "started_at": "2026-08-07T15:21:42.000-07:00", @@ -103,7 +103,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-04T13:17:15.330-07:00", "resolved_inferred": false, "started_at": "2026-08-04T11:49:50.000-07:00", @@ -116,7 +116,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-27T11:05:48.565-07:00", "resolved_inferred": false, "started_at": "2026-07-27T10:48:46.407-07:00", @@ -129,7 +129,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-22T16:57:46.890-07:00", "resolved_inferred": false, "started_at": "2026-07-22T16:32:44.340-07:00", @@ -142,7 +142,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-16T20:48:44.191-07:00", "resolved_inferred": false, "started_at": "2026-07-16T17:49:10.632-07:00", @@ -155,7 +155,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-10T12:33:31.569-07:00", "resolved_inferred": false, "started_at": "2026-07-10T09:49:33.987-07:00", @@ -168,7 +168,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-29T13:24:21.260-07:00", "resolved_inferred": false, "started_at": "2026-06-29T11:46:22.622-07:00", @@ -181,7 +181,7 @@ "body": "This incident has been resolved", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-10T11:35:12.294-07:00", "resolved_inferred": false, "started_at": "2026-06-10T10:15:38.349-07:00", @@ -194,7 +194,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-09T14:44:14.070-07:00", "resolved_inferred": false, "started_at": "2026-06-09T14:24:31.040-07:00", @@ -207,7 +207,7 @@ "body": "We have applied a fix and are seeing recovery across our systems", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-21T20:39:59.372-07:00", "resolved_inferred": false, "started_at": "2026-05-21T18:55:43.997-07:00", @@ -220,7 +220,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-09T00:01:44.236-07:00", "resolved_inferred": false, "started_at": "2026-05-08T23:25:52.281-07:00", @@ -233,7 +233,7 @@ "body": "All critical functionalities have recovered for all users.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-08T15:38:17.335-07:00", "resolved_inferred": false, "started_at": "2026-05-08T12:08:32.005-07:00", @@ -246,7 +246,7 @@ "body": "We've resolved the issue and messaging should be functional", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-02T10:29:17.660-07:00", "resolved_inferred": false, "started_at": "2026-05-02T10:03:31.594-07:00", @@ -259,7 +259,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-28T14:12:03.026-07:00", "resolved_inferred": false, "started_at": "2026-04-28T12:20:14.879-07:00", @@ -272,7 +272,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-18T20:52:20.329-07:00", "resolved_inferred": false, "started_at": "2026-04-18T19:37:27.045-07:00", @@ -285,7 +285,7 @@ "body": "The issue has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-16T13:30:06.453-07:00", "resolved_inferred": false, "started_at": "2026-04-16T12:47:09.573-07:00", @@ -298,7 +298,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-06T19:52:03.247-07:00", "resolved_inferred": false, "started_at": "2026-04-06T18:48:05.433-07:00", @@ -311,7 +311,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-30T22:36:51.800-07:00", "resolved_inferred": false, "started_at": "2026-03-30T22:11:48.484-07:00", @@ -324,7 +324,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-28T14:44:16.991-07:00", "resolved_inferred": false, "started_at": "2026-03-28T14:23:50.319-07:00", @@ -337,7 +337,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-25T15:38:17.907-07:00", "resolved_inferred": false, "started_at": "2026-03-25T12:21:47.075-07:00", @@ -350,7 +350,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-25T08:51:12.759-07:00", "resolved_inferred": false, "started_at": "2026-03-25T08:18:46.585-07:00", @@ -363,7 +363,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-19T22:56:47.669-07:00", "resolved_inferred": false, "started_at": "2026-03-19T19:47:07.528-07:00", @@ -376,7 +376,7 @@ "body": "We believe that the 503s have been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-12T14:04:13.386-07:00", "resolved_inferred": false, "started_at": "2026-03-12T14:04:13.338-07:00", @@ -389,7 +389,7 @@ "body": "We believe the 503s have been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-12T14:06:00.560-07:00", "resolved_inferred": false, "started_at": "2026-03-12T13:50:26.853-07:00", @@ -402,7 +402,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-11T16:33:11.258-07:00", "resolved_inferred": false, "started_at": "2026-03-11T16:07:07.963-07:00", @@ -415,7 +415,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-09T10:58:48.107-07:00", "resolved_inferred": false, "started_at": "2026-03-09T10:08:03.357-07:00", @@ -428,7 +428,7 @@ "body": "k-ID age verification is operating normally again in the UK and Australia. Previously age verified users were not impacted.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-05T19:49:19.990-08:00", "resolved_inferred": false, "started_at": "2026-03-05T19:26:36.000-08:00", @@ -441,7 +441,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-04T17:58:07.567-08:00", "resolved_inferred": false, "started_at": "2026-03-04T17:37:11.746-08:00", @@ -454,7 +454,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-11T10:25:06.008-07:00", "resolved_inferred": false, "started_at": "2026-03-02T12:02:15.000-08:00", @@ -467,7 +467,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-28T14:54:27.900-08:00", "resolved_inferred": false, "started_at": "2026-02-28T13:54:29.000-08:00", @@ -480,7 +480,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-28T08:37:54.888-08:00", "resolved_inferred": false, "started_at": "2026-02-28T06:39:39.835-08:00", @@ -493,7 +493,7 @@ "body": "We are currently investigating this issue.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-28T06:00:00.000-08:00", "resolved_inferred": false, "started_at": "2026-02-28T06:00:00.000-08:00", @@ -506,7 +506,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-27T14:26:41.734-08:00", "resolved_inferred": false, "started_at": "2026-02-27T13:52:42.622-08:00", @@ -519,7 +519,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-27T15:03:12.620-08:00", "resolved_inferred": false, "started_at": "2026-01-27T13:23:55.995-08:00", @@ -532,7 +532,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-24T22:04:31.034-08:00", "resolved_inferred": false, "started_at": "2026-01-24T16:35:07.937-08:00", @@ -545,7 +545,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-19T15:23:14.719-08:00", "resolved_inferred": false, "started_at": "2025-12-19T14:55:38.534-08:00", @@ -558,7 +558,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-17T10:09:27.981-08:00", "resolved_inferred": false, "started_at": "2025-12-17T09:49:43.930-08:00", @@ -571,7 +571,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-05T01:22:58.738-08:00", "resolved_inferred": false, "started_at": "2025-12-05T01:14:18.956-08:00", @@ -584,7 +584,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-03T10:29:26.880-08:00", "resolved_inferred": false, "started_at": "2025-12-03T07:53:12.702-08:00", @@ -597,7 +597,7 @@ "body": "The upstream provider has resolved the issue on their side, and all Discord components are operating normally.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-18T11:29:55.840-08:00", "resolved_inferred": false, "started_at": "2025-11-18T04:58:36.874-08:00", @@ -610,7 +610,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-17T14:33:45.551-08:00", "resolved_inferred": false, "started_at": "2025-11-17T13:57:19.152-08:00", @@ -623,7 +623,7 @@ "body": "A fix has been implemented and we are monitoring the results.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-15T10:38:02.480-08:00", "resolved_inferred": false, "started_at": "2025-11-15T05:42:50.917-08:00", @@ -636,7 +636,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-12T14:11:15.508-08:00", "resolved_inferred": false, "started_at": "2025-11-12T12:55:21.858-08:00", @@ -649,7 +649,7 @@ "body": "test over", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-23T12:51:52.650-07:00", "resolved_inferred": false, "started_at": "2025-10-23T12:51:22.474-07:00", diff --git a/api/v/divio.json b/api/v/divio.json index 21f05757ab1fb8152c54c0461e756b958995b6d8..34ebe1098334a6f9c5707aa78694c5a84709ec36 100644 --- a/api/v/divio.json +++ b/api/v/divio.json @@ -3,7 +3,7 @@ "slug": "divio", "platform": "statuspage", "status_url": "https://status.divio.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-18T11:04:11.668Z", "resolved_inferred": false, "started_at": "2026-03-18T10:30:58.992Z", @@ -25,7 +25,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-05T10:56:01.775Z", "resolved_inferred": false, "started_at": "2026-03-05T10:20:11.658Z", @@ -38,7 +38,7 @@ "body": "DNSimple has confirmed that all systems are operational and we can confirm from our side that domain resolution is working normally for all customers.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-10T21:15:02.240Z", "resolved_inferred": false, "started_at": "2026-02-10T17:25:07.374Z", @@ -51,7 +51,7 @@ "body": "Service Impact Restored: We have confirmed that the intermittent issues affecting the Divio Control Panel and Media/Asset Delivery are restored.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-18T19:35:57.158Z", "resolved_inferred": false, "started_at": "2025-11-18T12:43:12.104Z", @@ -64,7 +64,7 @@ "body": "The fix has been successfully deployed across all regions and we can now report that all systems are back to normal.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-20T18:17:21.653Z", "resolved_inferred": false, "started_at": "2025-10-20T16:31:12.099Z", diff --git a/api/v/dixa.json b/api/v/dixa.json index 3f0cab9c91f5ebbb5dfe6db98b1a9823963fd3e1..6ad67beb0512a918a269bd8c224b2ebb2f63c5f3 100644 --- a/api/v/dixa.json +++ b/api/v/dixa.json @@ -3,7 +3,7 @@ "slug": "dixa", "platform": "statuspage", "status_url": "https://status.dixa.io", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "### **Post-Mortem: Advanced Insight & Miuros Degraded Performance**\n\n**Date of Incident:** July 28, 2026\n\n**Duration:** 12:47 PM \u2013 1:15 PM CEST \\(28 minutes\\)\n\n**Severity:** Medium \u2014 degraded performance, partial access issues\n\n#### **Summary**\n\nOn July 28, 2026, at 12:47 PM CEST, users began experiencing degraded performance and intermittent difficulty accessing Advanced Insight & Miuros. Our team identified the issue and began investigating shortly after it was detected. A fix was implemented, and full service was confirmed restored by 1:15 PM CEST.\n\n#### **Impact**\n\nBetween 12:47 PM and 1:15 PM CEST, some users experienced slow load times or were unable to reliably access Advanced Insight & Miuros. No data loss occurred, and access was fully restored once the fix was deployed.\n\n#### **Root Cause**\n\nThe degraded performance was traced to a change introduced during a recent deployment to the Advanced Insight & Miuros environment, which had an unintended impact on service performance. Once flagged, our engineering team investigated the affected components and implemented a corrective fix to restore normal performance.\n\n#### **Resolution**\n\nUpon detecting the issue at 12:47 PM CEST, our team began investigating the affected services. The root cause was traced to the recent deployment, and a fix was rolled out, resolving the degraded performance. Full functionality was confirmed at 1:15 PM CEST.\n\n#### **Preventive Measures**\n\nTo help prevent similar incidents going forward, we are:\n\n* Strengthening pre-deployment validation and performance testing for Advanced Insight & Miuros\n* Improving monitoring and alerting thresholds to detect performance degradation earlier\n* Refining our rollback process to reduce time-to-resolution for similar issues\n\n#### **Closing Note**\n\nWe understand how important reliable access to Advanced Insight & Miuros is to your workflows. We apologize for any inconvenience caused during this period and are committed to strengthening the resilience of this service.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-28T13:15:37.739+02:00", "resolved_inferred": false, "started_at": "2026-07-28T12:47:20.793+02:00", @@ -25,7 +25,7 @@ "body": "### **Post-Mortem: Conversation Handling & Login Service Disruption**\n\n**Date of Incident:** July 28, 2026\n\n**Duration:** 8:53 AM \u2013 9:03 AM CEST \\(10 minutes\\)\n\n**Severity:** High \u2014 partial service disruption\n\n#### **Summary**\n\nOn July 28, 2026, at 8:53 AM CEST, Dixa experienced a service disruption affecting conversation handling and user login functionality. The issue was identified quickly by our engineering team, a fix was deployed at 9:03 AM CEST, and full functionality was restored within 10 minutes of the initial impact.\n\n#### **Impact**\n\nUsers may have experienced difficulty logging into Dixa or handling conversations during the affected window. No data loss occurred, and all systems returned to normal operation by 9:03 AM CEST.\n\n#### **Root Cause**\n\nThe disruption was traced to a change introduced during a routine deployment to our production environment, which had an unintended effect on the services responsible for conversation handling and authentication. Our monitoring systems flagged the anomaly shortly after it occurred, allowing our engineering team to identify and roll back the change quickly.\n\n#### **Resolution**\n\nEngineers on-call were alerted immediately once the anomaly was detected. The team traced the issue to the recent deployment and deployed a corrective fix at 9:03 AM CEST, which resolved the disruption.\n\n#### **Preventive Measures**\n\nTo reduce the likelihood of similar incidents going forward, we are:\n\n* Strengthening our pre-deployment validation checks to catch this class of issue before it reaches production\n* Improving automated rollback triggers so similar anomalies are reverted even faster\n* Enhancing monitoring coverage on conversation handling and authentication services specifically\n\n#### **Closing Note**\n\nWe know reliability is critical to how you run your business, and we take incidents like this seriously. We apologize for any inconvenience this may have caused and remain committed to continuously improving the resilience of our platform.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-28T09:00:00.000+02:00", "resolved_inferred": false, "started_at": "2026-07-28T09:00:00.000+02:00", @@ -38,7 +38,7 @@ "body": "All data is now re-deployed and we're completely up to date for everyone.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-29T17:11:23.915+02:00", "resolved_inferred": false, "started_at": "2026-06-29T11:04:35.000+02:00", @@ -51,7 +51,7 @@ "body": "Data ingestion has fully caught up and the Real-Time Dashboard, Search and Conversations pages are showing live data again.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-23T13:51:38.603+02:00", "resolved_inferred": false, "started_at": "2026-04-23T13:42:51.123+02:00", @@ -64,7 +64,7 @@ "body": "## **Summary**\n\nOn April 8, 2026, Dixa experienced a partial outage lasting approximately 58 minutes. New WebSocket connections were unable to be established, which meant that new logins failed, and any agents who refreshed their browser or lost their connection could not reconnect. Agents who remained on an existing session were unaffected during the incident.\n\nThe root cause was a TLS certificate misconfiguration introduced during a planned migration of our ingress controller infrastructure. The issue was identified, fixed, and fully resolved within the hour.\n\n## **Impact**\n\nBetween 18:26 and 19:24 CEST, customers attempting to log in to Dixa or re-establish a WebSocket connection \\(e.g., after a page reload\\) were unable to do so. Browsers rejected the connection due to an invalid TLS certificate being served.\n\nAgents who were already logged in with an active WebSocket session continued to operate normally throughout the incident. The impact was limited to new or reconnecting sessions.\n\nA small number of customers were affected and reported the issue to our support team.\n\nNo conversations or data have been lost during the incident.\n\n## **Timeline \\(CEST\\)**\n\n* 18:26 - Internal reports that Dixa is not loading for some users\n* 18:30 - Issue escalated to engineering via our critical support channel\n* 18:32 - Status page updated to **Investigating**\n* 18:40 - Engineering identifies a TLS certificate error \\(`ERR_CERT_AUTHORITY_INVALID`\\)\n* 18:52 - Root cause identified, a self-signed default certificate was being served instead of the correct one\n* 19:00 - Status page updated to **Identified**\n* 19:11 - Fix deployed; WebSocket connections begin recovering\n* 19:12 - Status page updated to **Monitoring**\n* 19:24 - Full recovery confirmed; status page updated to **Resolved**\n\n## **Root Cause**\n\nAs part of our ongoing WebSocket resilience work to ensure a more stable platform, we migrated our ingress controller \\(the component that routes incoming traffic to internal services\\) from an end-of-support solution to a new one. This migration was tested in our staging environment before being applied to production.\n\nHowever, there was a configuration discrepancy between staging and production for the ingress class that handles WebSocket traffic. When DNS was switched to the new ingress controller on the morning of April 8, existing connections continued to work through cached DNS entries still pointing to the old controller. Hours later, as DNS caches expired across the internet, clients began resolving to the new controller, which, due to the misconfiguration, did not recognize the WebSocket routes. This caused it to serve a default self-signed TLS certificate instead of the valid one, leading browsers to reject the connection.\n\nThe length of the partial outage per customer varies depending on when the DNS cache expired, and if WebSocket connections started to connect to the new load balancer.\n\n## **Resolution**\n\nOnce the root cause was identified, a configuration update was deployed to the new ingress controller so that it could correctly handle WebSocket traffic. Connections began recovering immediately after the fix was applied.\n\n## **Preventive Measures**\n\nWe have taken the following steps to reduce the likelihood and impact of similar issues in the future:\n\n* **Environment parity:** All non-production environments have been aligned with production configuration conventions, eliminating the discrepancy that caused this incident.\n* **Endpoint monitoring:** We have added external monitoring checks that validate both the availability and TLS certificate validity of our WebSocket endpoints. This will enable faster detection if a similar issue occurs.\n* **WebSocket isolation**: We will isolate the platform's WebSocket requirement to be optional, so if a similar issue should happen in the future, the disruption will be less intrusive for users.\n\n\u200c\n\n\u200c\n\nWe sincerely apologize for the disruption this caused. Reliability is a top priority for us, and we are committed to learning from every incident to make Dixa more resilient. If you have any questions, please don't hesitate to reach out to your account team or our support at [friends@dixa.com](mailto:friends@dixa.com).", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-08T19:24:01.536+02:00", "resolved_inferred": false, "started_at": "2026-04-08T18:32:27.000+02:00", @@ -77,7 +77,7 @@ "body": "_Dixa experienced issues with the Smart Reply feature in AI CoPilot on 18 March 2026._ \n \n_**Summary**_ \n_18 March 2026 at 14:37 CET - 20:20 CET, customers experienced issues with the Smart Reply feature in AI CoPilot. Agents were unable to use Smart Reply._\n\n \n_**Root cause**_ \n_A code change introduced a regression that caused agents' browsers to block completing the request to load Smart Reply suggestions._ \n \n_**Timeline**_ \n_At 14:37 CET on 18 March 2026: Issue flagged internally after several customers reported the issue_ \n_At 15:33 CET: Engineering investigates and attempts an initial rollback, which does not resolve the issue._ \n_At 16:02 CET: Status page updated to \"Investigating\" \u2014 customers notified of difficulties with AiCoPilot Smart Replies._ \n_At 16:48 CET: Status page updated \u2014 engineering continues to investigate._ \n_At 18:17 CET: Status page updated \u2014 root cause investigation ongoing_ \n_At 20:20 CET: The knowledge-backend service is successfully rolled back to a stable version, restoring Smart Reply._ \n_At 20:52 CET: Status page updated to \"Resolved\" \u2014 all known issues confirmed resolved._ \n \n_**Solution**_ \n_The immediate solution was to roll back to a stable version from prior to the breaking change, restoring Smart Reply for all affected customers._ \n_Long term, the team will review the offending commit before re-deploying to prevent similar regressions from reaching production undetected._ \n_We sincerely apologise for the inconvenience caused by this issue._", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-18T20:52:32.662+01:00", "resolved_inferred": false, "started_at": "2026-03-18T16:02:38.364+01:00", @@ -90,7 +90,7 @@ "body": "**Summary:** On March 11, 2026, Dixa experienced platform-wide degraded performance lasting approximately 3 hours \\(08:30 - 12:35 CET\\). Customers experienced slow or failed conversation loading, timeouts on email sending, conversation transfers, assignments, and flow processing. No data was lost, and there were no security issues at any point.\n\n**Impact:**\n\n* _Availability_: Platform-wide slowness and partial inaccessibility for ~3 hours.\n* _Affected functionality_: Conversation loading, email sending, conversation transfers, conversation assignments, and flow processing - all experienced significant slowness and intermittent failures.\n* _Data integrity:_ All emails were fully processed after the fix. No data was lost, and no security issues occurred at any point.\n\n**Root Cause:** The incident was caused by an atypical traffic pattern in inbound email processing that resulted in repeated internal retries - retries are a normal part of email distribution, accounting for factors such as sending delays and server availability, but this expanded exponentially. The sustained retry volume placed excessive load on a central platform component, causing cascading timeouts across dependent services and resulting in platform-wide degradation.\n\n**Timeline \\(CET\\):**\n\n* Mar 11, 06:00 - First signs of email processing errors detected\n* Mar 11, 08:30 - Platform degradation begins; customer impact starts\n* Mar 11, 10:50 - First mitigation deployed; partial improvement\n* Mar 11, 12:30 - Root cause fully identified; final fix applied\n* Mar 11, 12:35 - Platform stability confirmed\n\n**Resolution:** We identified and addressed the source of the abnormal email volume, which resulted in an immediate reduction in error rates, and the platform to recover.\n\n**What We Have Done Since This Incident:** Following this incident, we have already implemented the following improvements:\n\n1. Added validation to reject invalid email addresses early in the pipeline, preventing them from entering retry loops.\n2. Optimised internal lookups to fetch only necessary data instead of the full conversation history, significantly reducing load during email processing.\n3. Added deduplication logic to prevent redundant data fetches during email processing.\n4. Enforced concurrency limits: platform components now shed excess traffic when saturated, allowing requests to be redistributed rather than queued indefinitely.\n5. Added deadline checking: expired requests are now discarded immediately instead of consuming resources on work that is no longer needed.\n6. Reduced internal timeout thresholds to fail fast under contention rather than blocking for extended periods.\n\n**What We're Continuing to Work On:**\n\n1. Loop detection and interruption - Introduce mechanisms to detect and automatically halt email processing anomalies before they can accumulate significant load.\n2. Improved alerting and escalation - Ensure processing anomalies are detected and escalated with appropriate urgency.\n\n**Closing Note:** We sincerely apologize for the disruption this caused. These improvements are our highest priority. If you have any questions, please reach out to [friends@dixa.com](mailto:friends@dixa.com).", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-11T12:31:08.544+01:00", "resolved_inferred": false, "started_at": "2026-03-11T09:18:20.141+01:00", @@ -103,7 +103,7 @@ "body": "**Summary**: On March 10, 2026, all public Dixa Knowledge Help Centers were unavailable following a production deployment performed during scheduled maintenance. \n\n**Impact**\n\n* Dixa Knowledge Public Help Centers remained inaccessible for 6 hours \\(approximately\\) \n* Customers with advanced custom CSS styling were contacted directly with instructions on how to update their selectors to prevent recurrence.\n\n**Root Cause:** After the production deployment performed during a scheduled maintenance, all public Help Centers became unavailable. Visitors saw an error page \\(500\\) instead of help content.\n\n**Timeline \\(CET\\)**\n\nMar 10, 08:00 - Maintenance completed. No anomalies detected.\n\nMar 10, 11:52 - Initial customer reports received. Considered isolated cases at the time.\n\nMar 10, 13:38 - Incident process triggered. Reported on Status page.\n\nMar 10, 13:57 - Root cause fully identified.\n\nMar 10, 14:13 - Fix deployed. Public Help Centers restored; some styling issues persisted.\n\nMar 10, 14:48 - Root cause for styling anomalies identified as linked to build-time generated class names. Affected customers notified with instructions.\n\nMar 10, 18:03 - Incident resolved. \n\n**Resolution**: We identified a misconfiguration in the deployment that caused Help Centers to attempt to load from a test environment rather than production. A fix was deployed, and an immediate reduction in error rates confirmed it was effective.\n\n**What We Have Done Since This Incident:** Following this incident, we have already implemented the following improvements:\n\n1. Proactively contacted all affected customers with clear instructions on how to update their custom CSS styling.\n2. Documented additional validations for future migrations and action plans to address similar errors. \n3. External documentation updated to offer alternatives to the use of auto-generated classes for styling Help Centers.\n\n**What We're Continuing to Work On**\n\n* Improve monitoring and alerting, ensure availability issues are detected and escalated promptly, independent of customer reports.\n* Investigating a solution to expose stable, named elements for Help Center customization, reducing dependency on build-generated class names.\n\n**Closing Note:** We sincerely apologize for the disruption this caused. We appreciate your patience throughout this disruption. If you have any questions, please reach out to friends@dixa.com.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-10T18:03:48.756+01:00", "resolved_inferred": false, "started_at": "2026-03-10T13:38:16.571+01:00", @@ -116,7 +116,7 @@ "body": "**Summary** \nOn March 2, 2026, Dixa experienced platform-wide degraded performance lasting approximately 3 hours and 45 minutes. Customers experienced slow or failed conversation loading, timeouts on email sending, conversation transfers, assignments, and flow processing. No data was lost, and there were no security issues at any point.\n\n**Impact**\n\n* **Availability:** Platform-wide slowness and partial inaccessibility for ~3 hours 45 minutes.\n* **Affected functionality:** Inbound email processing, conversation loading, conversation transfers, conversation assignments, and flow processing \u2014 all experienced significant slowness and intermittent failures.\n* **Side effect:** Some inbound emails resulted in empty, queue-less conversations being created. These are safe to close or merge with the correctly processed follow-up conversation.\n* **Data integrity:** All emails were fully processed after the fix. No data was lost and no security issues occurred at any point.\n\n**Root Cause** \nThe incident was caused by a significant and atypical spike in inbound conversations that fell well outside expected operational parameters. This unexpected volume put pressure on a central database component, which began throttling requests. The throttling then cascaded to other parts of the system, resulting in platform-wide slowness and temporary inaccessibility.\n\n**Timeline \\(CET\\)** \nMar 1, 02:14 Significant and atypical spike in inbound conversations begins \nMar 2, ~17:45 Database throttling begins; connection pools saturate \nMar 2, 19:08 Incident declared; investigation begins \nMar 2, 20:06Mitigation measures applied; investigation ongoing \nMar 2, 20:18 Root cause identified \nMar 2, 21:09 Fix deployed; error rates drop \nMar 2, 21:17 Resolution confirmed \nMar 2, 21:21Incident resolved\n\n**Resolution** \nWe identified and addressed the source of the abnormal conversation volume, which immediately caused error rates to drop and the platform to recover.\n\n**What We're Doing to Prevent Recurrence** \nWe have identified several systemic improvements and are actively working on them:\n\n1. **Detect and suppress atypical inbound volume patterns** \u2014 Introduce early filtering to prevent abnormal spikes from reaching core platform components.\n2. **Improve retry and backoff behaviour** \u2014 Reduce the risk of compounding load during high-traffic failure scenarios.\n3. **Reduce inter-service dependencies** \u2014 Limit the blast radius of a single overloaded component affecting other parts of the platform.\n4. **Improve database resilience** \u2014 Add circuit breakers and timeouts to prevent database pressure from cascading across services.\n5. **Atomic conversation creation** \u2014 Ensure conversations are never persisted without their initial message, eliminating orphaned empty conversations as a failure side effect.\n\n**Closing Note** \nWe sincerely apologize for the disruption this caused. We take platform reliability seriously and are committed to the systemic improvements outlined above. If you have any questions, please reach out to [friends@dixa.com](mailto:friends@dixa.com).", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-02T21:21:46.989+01:00", "resolved_inferred": false, "started_at": "2026-03-02T19:08:07.114+01:00", @@ -129,7 +129,7 @@ "body": "**Incident Summary** \nOn Feb 20, 2026 - 15:24 CET, we experienced a brief period of degraded performance across the platform. Some customers may have noticed slower response times and intermittent timeouts while using the interface.\n\n**Impact** \nDuring the incident window, a subset of requests were delayed or failed, which may have affected normal usage for some customers.\n\n**Root Cause** \nThe issue was caused by an internal service experiencing elevated load, which temporarily impacted request processing across the platform.\n\n**Resolution** \nOur engineering team identified the issue quickly and restored normal performance. The platform has been operating normally since the fix was applied.\n\n**Prevention** \nWe are reviewing monitoring and scaling controls for the affected service to reduce the likelihood of similar incidents in the future.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-20T15:35:23.000+01:00", "resolved_inferred": false, "started_at": "2026-02-20T15:24:47.000+01:00", @@ -142,7 +142,7 @@ "body": "Dixa experienced issues with transcription on Tuesday 27th January 2026 between 11:27 and 13:15 CET\n\n \n**Timeline**\n\n* At 10:22 CET / 4:22 EST Azure reports issues on the Azure OpenAI Service \n* At 11:27 CET / 5:27 EST the first issues with transcriptions start to happen at Dixa. At 11:46 CET / 5:46 EST Dixa investigates unrelated issues with live chats and calls. \n* At 12:16 CET / 6:16 EST While investigating the unrelated issues, Dixa noticed the issues with transcriptions. \n* At 13:15 CET / 7:15 EST Transcription issues disappear.\n\n**Impact** \nTranscriptions were not available or delayed in the specified timeframe. \n \n**Root cause** \nOur provider for AI voice transcriptions, Azure, reported issues. According to their [status](https://azure.status.microsoft/en-us/status/history/): \n_Between 09:22 UTC and 16:12 UTC on 27 January 2026, and again between 11:14 UTC and 13:35 UTC on 29 January 2026, a platform issue resulted in an impact to the Azure OpenAI Service in the Sweden Central region. Impacted customers may have experienced HTTP 500/503 errors, failed inference requests, and/or issues with model deployment metadata. This issue also affected the Agent Service and other downstream AI Services dependent on Azure OpenAI in this region._ \n \n**Immediate solution** \nWe monitored the situation until it was fixed. \n \n**Long-term solution \\(where applicable\\)** \nWe could consider changing region for our service if the issues become more frequent. Otherwise, Azure has been reliable enough to keep the current infrastructure. Furthermore, Azure made improvements on their side to prevent this situation from happening again.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-27T13:36:22.295+01:00", "resolved_inferred": false, "started_at": "2026-01-27T12:41:10.851+01:00", @@ -155,7 +155,7 @@ "body": "All known issues to this incident have been resolved. We thank you for your patience and cooperation.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-06T16:40:16.746+01:00", "resolved_inferred": false, "started_at": "2026-01-06T16:24:58.794+01:00", @@ -168,7 +168,7 @@ "body": "# **Degraded performance - AI Voice Transcription and webhooks**\n\n## **Summary**\n\nOn 22 December 2025, Dixa experienced an issue with the AI Voice Transcription feature. Transcriptions were not being generated for phone calls. Once the issue was resolved, a temporary period of degraded performance on Webhooks occurred as the system processed a backlog of pending transcriptions.\n\n## **Root cause**\n\nFollowing a scheduled release, a component responsible for processing voice transcription requests stopped functioning correctly. When the issue was resolved, the system began processing all pending transcription requests. The high volume of these requests temporarily affected Webhook delivery times, causing delays in notifications to third-party integrations.\n\n## **Timeline**\n\n**Monday 22 December at 11:30 CET:** Issue reported and investigation started.\n\n**Monday 22 December at 12:00 CET:** The issue was identified and a fix was deployed. AI Voice Transcription began processing again.\n\n**Monday 22 December at 12:26 CET:** Degraded Webhook performance identified, affecting some third-party integrations, including chatbots.\n\n**Monday 22 December at 12:54 CET:** AI Voice Transcription fully restored.\n\n**Monday 22 December at 14:35 CET:** All services fully recovered. Incident closed.\n\n## **Preventive measures**\n\nDixa will implement the following measures to prevent similar issues in the future:\n\n* Enhanced monitoring for the AI voice transcription feature.\n\n* Improved handling of backlog processing to minimise impact on dependent services.\n\nWe sincerely apologise for the inconvenience this has caused.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-22T14:41:38.098+01:00", "resolved_inferred": false, "started_at": "2025-12-22T11:30:19.148+01:00", @@ -181,7 +181,7 @@ "body": "**Summary**\n\nOn the 16th of December 2025 between 8:49 PM CET and 9:34 PM CET we experienced intermittent issues with AI features such as Co-pilot and intent detection automation on some of the Dixa instances.\n\n**Root cause**\n\nThe incident was caused by the increased usage of the above mentioned features which caused hitting the set usage limit. \n\n**Timeline**\n\nAt 8:49 PM CET: We started observing usage spikes which resulted in errors that started occurring around AI related features. \n\nAt 8:55 PM CET: Status page was updated with the areas that were impacted by the issue.\n\nAt 9:03 PM CET: We found the root cause and moved the incident status to Identified. \n\nAt 9:12 PM CET: The fix was deployed and the incident status changed to Monitoring.\n\nAt 9:34 PM CET: After a period of monitoring we did not observed any more errors and the incident status was moved to Resolved. \n\n**Solution**\n\nThe immediate solution was to increase the usage limits as well as implement the separation of the limits per each AI feature in the backend. \n\nLong term we are planning to implement proactive alerting and monitoring around AI features usage and set limits to prevent the errors that occurred when the usage spiked. \u200c\n\nWe sincerely apologise for the inconvenience caused by the above issue.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-16T21:34:11.069+01:00", "resolved_inferred": false, "started_at": "2025-12-16T20:49:59.000+01:00", @@ -194,7 +194,7 @@ "body": "Summary\nParts of Dixa\u2019s search functionality malfunctioned during a 30-minute window, following a deployment including some deficient code, affecting, amongst others, the search feature within the Email and Phone composer features, respectively. \n\nRoot Cause\nStarting at 2.28 PM (CET) on 8 Dec, the faulty application started serving requests, some of which it was unable to handle. This was due to an insufficiently tested code path that got invoked under certain feature flag configurations, resulting in the search request not being handled correctly.\n\nAction Items\nOn-call engineers were alerted about elevated error levels within 15 minutes of the first failing requests, and shortly after, were able to identify the impaired deployment, rolling it back to a previous version while investigations continued. At 3.07 PM (CET), error rates related to failing search requests had completely levelled off.\n\nA fix to the root issue has been released since, further improving the overall safety and handling of code dictated by feature flag configurations. This includes more thorough runtime parameter checks as well as adding several regression tests to ensure the issue won\u2019t be reintroduced.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-08T14:30:00.000+01:00", "resolved_inferred": false, "started_at": "2025-12-08T14:30:00.000+01:00", @@ -207,7 +207,7 @@ "body": "**Summary** \n\nOn the 18th of November 2025 at 12:55 PM CET we received reports of Dixa Knowledge help centers not being available due to a Cloudflare error. At roughly the same time, we were made aware internally that we were receiving a lot of errors on AI-related functionality from one of our upstream sub-processors handling AI requests.\u200c\n\n**Root cause** \n\nThe incident originated from a major Cloudflare service disruption \\([https://www.cloudflarestatus.com/incidents/8gmgl950y3h7\\)](https://www.cloudflarestatus.com/incidents/8gmgl950y3h7)) caused by a configuration file used for Cloudflare\u2019s Bot Management system. The file was auto-generated and due to a bug became too large, subsequently crashing Cloudflare services and causing major disruption across the globe. \n\nDixa is using Cloudflare solely for the purpose of serving Dixa Knowledge's Knowledge Bases. Cloudflare helps us handle verification of custom host names and generating certificates for these custom host names, as well as protect the knowledge bases from malicious third parties.\n\nWe quickly learned that one of our upstream sub-processors for AI-related features also uses Cloudflare for similar reasons, therefore also breaking AI Co-Pilot, Mim, Intent Detection and other AI-powered features inside Dixa.\n\n**Timeline**\n\nAt 12:55 pm CET: We started observing increased errors on services handling AI-related features inside Dixa and received the first report about Dixa Knowledge KBs being inaccessible. We triggered our internal incident process and communicated here at 12:59 PM CET.\n\nAt 1:06 pm CET: The full impact on Dixa services started to become clear, and we were confident only AI-related features and Knowledge Bases were affected. \n\nFor the next hour and a half, we monitored the situation closely and saw alternating service recovery and disruption on the before-mentioned services while Cloudflare was recovering.\n\nAt 2:49 pm CET: We were made aware by our AI sub-processor that they saw slight improvements in connectivity.\n\nAt 3:46 pm CET: The impacted systems have fully recovered. The incident status was moved to Monitoring. \n\nAt 5.43 pm CET: We changed the incident on our status page from 'Monitoring' to 'Resolved' as no further problems have been reported nor detected.\n\nAt 6:44 pm CET: Cloudflare confirmed that the incident is fully resolved on their end.\n\n\u200c\n\nWe sincerely apologize for the inconvenience this has caused.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-18T16:43:10.576+01:00", "resolved_inferred": false, "started_at": "2025-11-18T12:59:22.233+01:00", @@ -220,7 +220,7 @@ "body": "**Summary**\u00a0\n\nOn the 20th of October 2025 at 6:55 PM CEST due to the ongoing AWS incident Dixa experienced intermittent issues with Telephony Inbound and Outbound connectivity. On some Dixa instances the calls were not being placed or the connection between agents and users was not established.\u00a0\n\n\u200c\n\n**Root cause**\u00a0\n\nThe incident originated from a **major AWS service disruption in the us-east-1 region** caused by a **DNS race condition within Amazon DynamoDB\u2019s endpoint management system**. The fault temporarily removed valid DNS records for several AWS services, resulting in widespread API resolution failures across multiple dependent systems.\n\nDixa is using Twilio\u2019s APIs for **telephony services.** When DynamoDB\u2019s DNS records were invalidated, Twilio\u2019s **regional load balancers lost access to key internal routing data**, which caused inbound and outbound voice requests to fail.\u00a0\n\nBecause Twilio\u2019s APIs are globally routed through Twilio\u2019s us-east-1 infrastructure, Dixa\u2019s platform became unable to establish or maintain voice sessions.\u00a0\n\n\u200c\n\n**Timeline**\n\nAt 06:55 pm CEST: We started observing intermittent interruptions with Telephony Inbound and Outbound service. Only some Dixa instances and phone numbers were affected. The incident was reported with the Identified status.\u00a0\n\nAt 07:52 pm CEST: The update is posted stating that some of the services are still impacted.\u00a0\n\nAt 08:51 pm CEST: There are no signs of issues on Dixa services anymore, however the third party services are still recovering and minimal interruptions could be expected.\u00a0\n\nAt 09:46 pm CEST: The impacted systems have fully recovered. The incident status was moved to Monitoring.\u00a0\n\nAt 00:56 am CEST on the 21st of October: AWS confirmed that the incident is fully resolved on their end. Dixa\u2019s incident status was changed to Resolved.\u00a0\n\n\u200c\n\n**Preventive measures**\u00a0\n\nDixa will evaluate implementing the following measures to mitigate the risk of similar issues in the future:\u00a0\n\n* evaluate the feasibility of enabling outbound and inbound routing via multi-regional providers in case the us-east-1 Twilio region fails.\n* Independent external health check monitoring outside of AWS and Twilio.\n* Service dependency mapping and redundancy revisit.\n* Incident communication redundancy\u00a0\n\n\u200c\n\nWe sincerely apologise for the inconvenience this has caused.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-21T00:56:58.770+02:00", "resolved_inferred": false, "started_at": "2025-10-20T18:55:44.806+02:00", @@ -233,7 +233,7 @@ "body": "**Summary**\u00a0\n\nOn the 20th of October 2025, starting from 08:58 am CEST, Dixa experienced widespread disruptions caused by the issues coming from third-party services.\u00a0\n\n**Impacted services**\n\n* Telephony Inbound and Outbound traffic - Calls were not being placed for the most part of the incident, and for a period of time, calls were placed, but the connection between agents and end users was not established.\u00a0\n* WhatsApp channel - conversations were queued but not sent during the incident. All queued messages were sent as soon as the issue was resolved.\n* SMS channel - conversations were queued but not sent during the incident. All queued messages were sent as soon as the issue was resolved.\n* Login to Elevio - login to Elevio was impacted. Help Centers were fully operational.\u00a0\n* Login to the Status page was impacted, which caused challenges with communicating incident updates once the incident was raised.\u00a0\n* Access to Dixa\u2019s Public API documentation[ docs.dixa.io](http://docs.dixa.io) was also affected by the incident; Dixa\u2019s API was fully operational.\n\n**Root cause**\u00a0\n\nThe incident originated from a **major AWS service disruption in the us-east-1 region** caused by a **DNS race condition within Amazon DynamoDB\u2019s endpoint management system**. The fault temporarily removed valid DNS records for several AWS services, resulting in widespread API resolution failures across multiple dependent systems.\n\nDixa is using Twilio\u2019s APIs for **telephony, WhatsApp, and SMS channels**. When DynamoDB\u2019s DNS records were invalidated, Twilio\u2019s **regional load balancers lost access to key internal routing data**, which caused inbound and outbound voice requests to fail. This also impacted dependent APIs for SMS and WhatsApp delivery.\n\nBecause Twilio\u2019s APIs are globally routed through Twilio\u2019s us-east-1 infrastructure, Dixa\u2019s platform became unable to establish or maintain voice sessions, send or receive SMS messages, or process WhatsApp traffic. Other parts of the Dixa platform \\(login, chat, email\\) remained operational, but all Twilio-dependent communication channels were impacted for the most part of the duration of the AWS event.\u00a0\n\n### **Timeline**\n\nAt 08:58 am CEST: We started observing errors in the logs coming from 3rd party systems, and shortly after, we started getting reports from customers about issues.\n\nAt 09:16 am CEST: The Incident was reported on the status page with status: Investigating. The system we use for the status page was also impacted due to the same root cause at AWS, and we were unable to add further details regarding the incident.\n\nBetween 9:00 and 10:00 am CEST: We kept updating the users who reached out to our support team about the status of the issue, while adding more details to the status page was not possible.\n\nAt 10:00 am CEST: An updated incident message was posted in the Agent interface to notify users about the status of the incident\u00a0\n\nAt 10:07 am CEST: We regained access to the status page and updated the status of the incident to: Identified and added the information about impacted services.\u00a0\n\nAt 10:20 am CEST: The incident status update is posted as well, with the notification being sent to all status page subscribers.\u00a0\n\nAt 10:55 am CEST: The next status page update is posted with reference to the incidents at AWS and Twilio, which were the root cause of the issues with Dixa services. We also reported issues with logging in to Elevio caused by the same incident.\u00a0\n\nAt 11:52 am CEST: Update is posted. The Elevio login issue is resolved. The issue with telephony inbound and outbound, as well as SMS and WhatsApp service, continues.\u00a0\n\nAt 12:58 pm CEST: The first calls were starting to get to Dixa infrastructure again, but the voice in the calls was still not operational.\u00a0\n\nAt 13:05 pm CEST: The connection issue with telephony continues. SMS is confirmed to be fully operational again.\u00a0\n\nAt 13:26 pm CEST: The inbound and outbound telephony is confirmed to be operational again.\n\nAt 14:21 pm CEST: WhatsApp is confirmed to be operational as well. All messages that were queued during the incident got successfully delivered. The incident status is changed to: Monitoring\n\nAt 15:19 pm CEST: All systems have been operational since the incident was moved to Monitoring, and the incident status was changed to: Resolved.\u00a0\n\n\u200c\n\n**Preventive measures**\u00a0\n\nDixa will evaluate implementing the following measures to mitigate the risk of similar issues in the future:\u00a0\n\n* evaluate the feasibility of enabling outbound and inbound routing via multi-regional providers in case the us-east-1 Twilio region fails.\n* Independent external health check monitoring outside of AWS and Twilio.\n* Service dependency mapping and redundancy revisit.\n* Incident communication redundancy\u00a0\n\n\u200c\n\nWe sincerely apologise for the inconvenience this has caused.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-20T15:19:26.640+02:00", "resolved_inferred": false, "started_at": "2025-10-20T09:16:46.353+02:00", @@ -246,7 +246,7 @@ "body": "### Summary\n\nDixa experienced partial degraded performance of AI-Co pilot features on October 14 2025 between 08:13-13:13 CEST. Users who never changed their translation settings were affected, experiencing unwanted auto-translations and non working translations. The issues were cause by an increased number of translation requests hitting our api, leading to overload. We eventually solved it by increasing the capacity for handing requests and by reverting the changes \n \n**Timeline**\n\nAt 08:13 am CEST A change was deployed for AI copilot to default the Auto summary and translations to \u201cAutomatic\u201d for users who never changed their preferences\n\nAt 09:48 am CEST First reports of difficulties with translations for AI Co-pilot that didn\u2019t work at all.\n\nAt 10:23 am CEST A fix is deployed to support the increased amount of requests incoming.\n\nAt 10:33 am CEST Fix is evaluated to have mitigated the issues.\n\nAt 11:33 CEST The requests to our API increase and issues come back, more reports are coming in from customers about conversations being automatically translated or translations not working at all.\n\nAt ~12:45 am CEST Fix is applied to support even more increased amount of requests to prevent translation failures and the quota on the model used by translation is increased to support the increased amount of requests.\n\nAt 13:13 am CEST A final fix is deployed - changes to AI copilot settings defaults are reverted and requires agents to reload to take effect. This decreased the system overload.\n\n### **Impact**\n\nThe incident had a major impact on the users of the AI Co-pilot feature that never changed their settings who experienced degraded performance with conversations not translating or unwanted increased amount of translations performed.\n\n## **Root cause**\n\nThe frontend changes to settings defaults for AI auto summary and translate flipped the settings from on-demand to automatic. It was applied to existing customers that never changed their settings. It appeared to be a significant amount of customers who had not done any changes to their settings. The change took effect over the course of multiple hours, because it required agents to reload the UI for the settings to take effect. This caused many more translations being performed where customers did not expect. Additionally, this caused increased amount of translation requests via rest-api, which made rest-api incapable of performing all requests due to it having a capped number on max open requests\n\n### **Resolution**\n\n* Support for and quota of translation requests were increased\n* The frontend change to settings defaults for AI Co-pilot were reverted\n\nWe have taken steps to improve our processes for control and increased the capacity limit so that this won\u2019t happen again. \n \nWe apologize for the inconvenience this caused and thank you for you cooperation", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-14T14:41:17.239+02:00", "resolved_inferred": false, "started_at": "2025-10-14T10:24:45.881+02:00", @@ -259,7 +259,7 @@ "body": "## Summary\n\nOn the 9th of September, 2025, a deployment at 2:45 PM CEST caused an ingestion delay affecting the Intelligence and the Realtime Dashboards. The incident was detected at 2:47 PM CEST by internal alerts as well as reports coming in to our Customer Support. A fix was released at 3:25 PM CEST, and all data was caught up at 3:51 PM CEST. The total incident was 66 minutes, with an impact on customers relying on our real-time dashboard and Intelligence module.\n\n## Timeline\n\n* **2:45 PM CEST** - Deployment released that caused the incident where ingestion of data to Intelligence- and the Realtime Dashboards was delayed\n* **2:47 PM CEST** - Internal alerts notified relevant stakeholders at Dixa around the incident, and a fix was worked on\n* **3:25 PM CEST** - A fix was released, and delayed data started catching up\n* **3:51 PM CEST** - All delayed data had caught up \n **Total Duration:** 66 minutes\n\n## Root Cause\n\nThe incident was caused by a deployment that resulted in a delay in the ingestion of data.\n\n## Impact\n\n* Realtime Dashboards\n* Intelligence/Analytics\n\n## Resolution\n\n**Immediate Resolution:**\n\n* The engineering team started working on a fix as soon as internal alarms notified relevant stakeholders\n* Service functionality was restored following the fix, and the delayed data started catching up\n\n**Prevention Measures:**\n\n* Expand test coverage", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-09T17:49:12.832+02:00", "resolved_inferred": false, "started_at": "2025-09-09T15:45:32.841+02:00", @@ -272,7 +272,7 @@ "body": "**Date**: August 22, 2025 \n**Duration**: 5 days \\(August 22-27, 2025\\) \n**Severity**: Degraded\n\n## Summary\n\nBetween August 22-27, 2025, our AI assistant \\(Mim\\) experienced degraded response quality due to inconsistent knowledge base indexing failures. The incident was caused by our OpenSearch cluster rejecting document index requests due to memory constraints from oversized embeddings. While Mim continued to operate with partial knowledge data, customers experienced reduced response accuracy for 5 days until the issue was resolved through cluster scaling.\n\n## Timeline\n\n* **August 22, 2025:** First indexing failures begin occurring\n* **August 22-25, 2025:** Indexing failures continue to grow in frequency\n* **August 25, 2025:** Issue escalated by CS team\n* **August 27, 2025 - 18:00 CEST:** Indexing failures stop occurring, and new knowledge bases can be indexed successfully\n* **August 28, 2025:** re-indexed existing Dixa Knowledge and elevio data sources\n* **August 28, 2025 - 12:00:** Full service restoration achieved\n\n## Root Cause\n\nThe system was unable to process knowledge base indexing requests due to insufficient computational resources relative to the data volume and complexity. Contributing factors included:\n\n* Inadequate system capacity for the current workload demands\n* Inefficient resource utilization patterns\n* Suboptimal data processing architecture that doesn't scale effectively with growth\n* Large data structures requiring more system resources than available\n\n## Impact\n\n* **Duration**: 5 days \\(August 22-27, 2025\\)\n* **Service Level**: Degraded \\(not complete outage\\)\n* **User Experience**: Mim responses had reduced accuracy and completeness due to operating with partial knowledge data\n\n## Resolution\n\n### Immediate Actions Taken\n\n1. **System Cleanup**: Removed unused data and optimized storage utilization\n2. **Capacity Scaling**: Increased available computational resources to handle workload demands\n3. **Performance Optimization**: Balanced system performance improvements with operational efficiency\n\n### Long-term Improvements Planned\n\n1. **Architecture Enhancement**:\n\n * Redesign data processing workflows for improved scalability\n * Implement more efficient system resource management\n \n2. **Data Optimization**:\n\n * Evaluate opportunities to reduce data processing overhead\n * Optimize data formats for better system performance\n \n3. **Monitoring Enhancement**:\n\n * Implement proactive alerting for system capacity issues\n * Add performance monitoring to prevent resource bottlenecks", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-28T08:52:13.801+02:00", "resolved_inferred": false, "started_at": "2025-08-26T16:30:36.692+02:00", @@ -285,7 +285,7 @@ "body": "**Date:** August 26, 2025 \n**Duration:** 25 minutes \\(14:20 - 14:45 CEST\\) \n**Severity:** High - Complete API unavailability\n\n## Summary\n\nA DNS configuration error during staging environment setup caused a complete outage of our public API at [dev.dixa.io](http://dev.dixa.io) for 25 minutes. All external integrations and services dependent on our API were affected.\n\n## Timeline\n\n* **14:20 CEST** - DNS records for [dev.dixa.io](http://dev.dixa.io) inadvertently deleted during staging setup\n* **14:20 CEST** - API connectivity issues began affecting all external services\n* **14:45 CEST** - DNS configuration restored, services resumed normal operation\n\n## Root Cause\n\nDuring the setup of staging DNS entries for [euw1.dev.dixa.io](http://euw1.dev.dixa.io), the existing DNS records for [dev.dixa.io](http://dev.dixa.io) were accidentally removed instead of being preserved alongside the new staging records. This caused all DNS queries for [dev.dixa.io](http://dev.dixa.io) to return NXDOMAIN responses.\n\n## Impact\n\n* **Duration:** 25 minutes of complete API unavailability\n* **Affected Services:** All external integrations including native integrations, custom cards, flow automations, Zapier, chatbots, and third-party API consumers\n* **User Impact:** Complete inability to access API-dependent functionality\n\n## Resolution\n\nThe DNS configuration was corrected by restoring the proper DNS records for [dev.dixa.io](http://dev.dixa.io), immediately resolving the connectivity issues.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-26T14:20:00.000+02:00", "resolved_inferred": false, "started_at": "2025-08-26T14:20:00.000+02:00", @@ -298,7 +298,7 @@ "body": "## Summary\n\nOn August 26, 2025, a deployment at 10:32 AM CEST caused a complete outage of the TrustPilot queue service, preventing agents from opening TrustPilot conversations in the agent interface. The incident was detected by Customer Support 20 minutes after deployment and resolved through a rollback at 11:30 AM CEST. Total downtime was 58 minutes, with a high impact on TrustPilot customer service operations.\n\n## Timeline\n\n* **10:32 CEST** - Image deployment initiated\n* **10:52 CEST** - Customer Support \\(CS\\) identified the TrustPilot queue service outage and notified the engineering team\n* **11:30 CEST** - Changes rolled back, service restored \n **Total Duration:** 58 minutes\n\n## Root Cause\n\nThe incident was caused by a deployment that contained changes incompatible with the TrustPilot queue service functionality.\n\n## Impact\n\n* TrustPilot Conversations could not be opened in the agent interface\n* Complete disruption of TrustPilot queue operations\n* Agent workflow interruption for TrustPilot-related customer inquiries\n\n## Resolution\n\n**Immediate Resolution:**\n\n* The engineering team executed a rollback of the deployed changes at 11:30 AM CEST\n* Service functionality was restored following the rollback\n* TrustPilot queue operations returned to normal\n\n**Prevention Measures:**\n\n* Expand integration test coverage for all third-party services\n* Implement automated health checks and alerting for critical service dependencies", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-26T11:52:14.701+02:00", "resolved_inferred": false, "started_at": "2025-08-26T10:58:35.516+02:00", diff --git a/api/v/dns-made-easy.json b/api/v/dns-made-easy.json index 26a02a37dae9ec3483505a73407163fd86bb41d6..9bd2217cbba851dee9cc38abad589cc01517bf31 100644 --- a/api/v/dns-made-easy.json +++ b/api/v/dns-made-easy.json @@ -3,7 +3,7 @@ "slug": "dns-made-easy", "platform": "status.io", "status_url": "https://dnsstatus.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": false, "first_watched": "2026-09-04T07:06:16Z", diff --git a/api/v/dnsfilter.json b/api/v/dnsfilter.json index 6a9e1c87704318fbc4db6def3fab63d7a74ff790..dc66fd0d22bdca5911500567d0907e33dafb20ff 100644 --- a/api/v/dnsfilter.json +++ b/api/v/dnsfilter.json @@ -3,7 +3,7 @@ "slug": "dnsfilter", "platform": "statuspage", "status_url": "https://status.dnsfilter.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "On June 3, 2026 between 6:47:00 and 6:53:00 UTC, some historical query data (older than ~2 weeks) was temporarily unavailable. Scheduled and queried reports that ran during this window may have returned zero or partial results. DNS filtering and traffic ingestion were not affected at any point. \n\nThe issue has been resolved. If you have any questions please reach out to our Support team.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-03T02:30:00.000-04:00", "resolved_inferred": false, "started_at": "2026-06-03T02:30:00.000-04:00", @@ -25,7 +25,7 @@ "body": "The issue causing certain domains to be incorrectly classified as malicious has been fully resolved. Our team implemented a rollback and completed monitoring to confirm classification behavior has returned to normal operation.\n\nThis issue did not impact DNS resolution or overall DNSFilter service availability.\n\nWe sincerely apologize for the disruption and appreciate your patience while we worked to quickly identify and resolve the issue.\n\nIf you continue to experience any related problems, please reach out to our Support team for further assistance.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-28T12:47:14.109-04:00", "resolved_inferred": false, "started_at": "2026-05-28T09:46:41.498-04:00", @@ -38,7 +38,7 @@ "body": "The issue impacting the Home Dashboard and Insights pages, as well as the \u201cFailed to Load QPS\u201d error message on the Site Deployment page, has been resolved. Functionality has returned to normal operation. \n\nIf you continue to experience any issues, please reach out to our Support team for further assistance.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-11T11:10:26.441-04:00", "resolved_inferred": false, "started_at": "2026-05-11T10:37:48.763-04:00", @@ -51,7 +51,7 @@ "body": "This incident has been resolved. Our cloud partner has resolved the issue impacting reporting performance. Functionality has now returned to normal operation.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-09T07:36:46.000-04:00", "resolved_inferred": false, "started_at": "2026-05-08T08:54:35.913-04:00", @@ -64,7 +64,7 @@ "body": "We\u2019ve resolved the issue that was causing DNS Query Log data to not appear in the dashboard. Our engineering team identified the root cause and implemented a fix, and data visibility has now been restored.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-27T10:28:42.755-04:00", "resolved_inferred": false, "started_at": "2026-04-27T07:09:54.957-04:00", @@ -77,7 +77,7 @@ "body": "This incident is now resolved. We have now shifted traffic back to the NYC region. \n\nThis issue was identified to be caused by a routing problem at an upstream Internet Exchange provider, which impacted connectivity and cascaded to our services.\n\nTo minimize customer impact, we temporarily rerouted traffic to our Washington, DC region. Once the issue was confirmed to be resolved by our upstream partner, traffic was safely restored to the NYC region.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-30T16:13:41.000-04:00", "resolved_inferred": false, "started_at": "2026-03-30T13:02:22.000-04:00", @@ -90,7 +90,7 @@ "body": "The cloud partner has resolved the issue on their end.\n\nOur engineers have confirmed that both Anycast and DNSFilter APIs remained fully operational throughout the event.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-05T04:37:33.203-05:00", "resolved_inferred": false, "started_at": "2025-12-05T04:15:24.597-05:00", @@ -103,7 +103,7 @@ "body": "An issue was identified affecting our DoH service that may have impacted customers in the London region. This did NOT affect DNS1/DNS2 UDP/TCP/TLS/DoT services. We identified the fault on Tuesday the 25th and resolved the it by 20:00 UTC by updating all affected servers. \n\nIn addition, we have improved our monitoring and automation by adding a new failsafe to avoid this from happening again in the future.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-25T15:00:00.000-05:00", "resolved_inferred": false, "started_at": "2025-11-25T15:00:00.000-05:00", @@ -116,7 +116,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-18T10:49:20.294-05:00", "resolved_inferred": false, "started_at": "2025-11-18T07:20:17.684-05:00", @@ -129,7 +129,7 @@ "body": "The cloud partner has resolved the issue on their end.\n\nOur engineers have confirmed that both Anycast and DNSFilter APIs remained fully operational throughout the event.\n\nNo customer-facing impact or service degradation was observed.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-20T08:22:30.690-04:00", "resolved_inferred": false, "started_at": "2025-10-20T05:57:11.357-04:00", @@ -142,7 +142,7 @@ "body": "A solution has been implemented, and performance has returned to normal. No further impact is expected. If you continue to experience related issues, please reach out directly to our Support team.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-29T16:51:39.729-04:00", "resolved_inferred": false, "started_at": "2025-09-29T11:02:23.734-04:00", @@ -155,7 +155,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-05T16:15:37.487-04:00", "resolved_inferred": false, "started_at": "2025-09-02T16:51:53.740-04:00", diff --git a/api/v/dnsimple.json b/api/v/dnsimple.json index 81613d4585627a3faf37feb6993bd6d2fd700e04..11c257050bcd4bde38f9db4b7c559c4478df1953 100644 --- a/api/v/dnsimple.json +++ b/api/v/dnsimple.json @@ -3,7 +3,7 @@ "slug": "dnsimple", "platform": "statuspage", "status_url": "https://dnsimple.statuspage.io", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-08T05:53:30.026Z", "resolved_inferred": false, "started_at": "2026-08-08T00:27:58.112Z", @@ -25,7 +25,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-23T14:46:15.414Z", "resolved_inferred": false, "started_at": "2026-07-23T14:02:53.483Z", @@ -38,7 +38,7 @@ "body": "The system has been stable; we consider this incident to be over.", "first_seen": "2026-09-04T07:06:16Z", "impact": "maintenance", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-22T07:59:45.402Z", "resolved_inferred": false, "started_at": "2026-07-22T05:09:11.381Z", @@ -51,7 +51,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-05T15:38:24.156Z", "resolved_inferred": false, "started_at": "2026-06-05T15:34:03.268Z", @@ -64,7 +64,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-22T22:18:33.200Z", "resolved_inferred": false, "started_at": "2026-05-22T10:44:37.064Z", @@ -77,7 +77,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-18T22:00:41.575Z", "resolved_inferred": false, "started_at": "2026-05-18T21:26:55.884Z", @@ -90,7 +90,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-08T10:00:51.913Z", "resolved_inferred": false, "started_at": "2026-05-08T05:18:13.428Z", @@ -103,7 +103,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-20T21:44:54.325Z", "resolved_inferred": false, "started_at": "2026-04-20T19:54:43.869Z", @@ -116,7 +116,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-05T12:46:10.052Z", "resolved_inferred": false, "started_at": "2026-03-05T10:14:01.112Z", @@ -129,7 +129,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-02T22:00:16.001Z", "resolved_inferred": false, "started_at": "2026-03-02T18:47:53.306Z", @@ -142,7 +142,7 @@ "body": "The rollback has completed, and DNS resolution has returned to normal behavior.\nWe will be making follow-up improvements to alias-resolution handling, including additional safeguards and testing to prevent recurrence.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-18T16:07:17.353Z", "resolved_inferred": false, "started_at": "2026-02-18T14:24:51.311Z", @@ -155,7 +155,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-10T23:18:10.278Z", "resolved_inferred": false, "started_at": "2026-02-10T17:06:06.727Z", @@ -168,7 +168,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-04T00:29:35.485Z", "resolved_inferred": false, "started_at": "2026-02-03T23:15:08.379Z", @@ -181,7 +181,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-03T23:41:39.360Z", "resolved_inferred": false, "started_at": "2026-02-03T19:55:26.222Z", @@ -194,7 +194,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-29T17:58:27.392Z", "resolved_inferred": false, "started_at": "2026-01-29T16:52:44.204Z", @@ -207,7 +207,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-22T08:41:34.287Z", "resolved_inferred": false, "started_at": "2026-01-22T07:29:30.232Z", @@ -220,7 +220,7 @@ "body": "Cache edge performance has been stable for some time, and we have seen no further issues. The incident is now closed.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-30T20:55:25.140Z", "resolved_inferred": false, "started_at": "2025-12-30T19:03:28.558Z", @@ -233,7 +233,7 @@ "body": "This network issue has been resolved fully. If you have any further issues please let us know by emailing support@dnsimple.com", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-16T02:06:07.899Z", "resolved_inferred": false, "started_at": "2025-12-16T01:06:25.399Z", @@ -246,7 +246,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-11T23:11:37.870Z", "resolved_inferred": false, "started_at": "2025-12-11T21:53:19.102Z", @@ -259,7 +259,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-07T13:44:14.107Z", "resolved_inferred": false, "started_at": "2025-12-07T13:05:52.447Z", @@ -272,7 +272,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-07T07:23:05.960Z", "resolved_inferred": false, "started_at": "2025-12-07T07:03:29.995Z", @@ -285,7 +285,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-04T09:27:16.815Z", "resolved_inferred": false, "started_at": "2025-12-04T09:24:25.000Z", @@ -298,7 +298,7 @@ "body": "The issue has been fully resolved. Services are back to normal.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-01T15:36:57.148Z", "resolved_inferred": false, "started_at": "2025-12-01T12:54:18.562Z", @@ -311,7 +311,7 @@ "body": "The update has finished and all assets are now being served correctly.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-28T16:42:39.006Z", "resolved_inferred": false, "started_at": "2025-11-28T16:28:36.351Z", @@ -324,7 +324,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-27T18:24:49.077Z", "resolved_inferred": false, "started_at": "2025-11-27T15:00:27.473Z", @@ -337,7 +337,7 @@ "body": "This network issue has been resolved fully. If you have any further issues please let us know by emailing support@dnsimple.com", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-10T19:48:30.457Z", "resolved_inferred": false, "started_at": "2025-11-10T17:52:34.793Z", @@ -350,7 +350,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-06T01:31:14.876Z", "resolved_inferred": false, "started_at": "2025-11-05T23:56:44.236Z", @@ -363,7 +363,7 @@ "body": "We are not seeing any more latency or issues in San Jose. if you are seeing any more issues please let us know at support@dnsimple.com", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-05T22:58:22.492Z", "resolved_inferred": false, "started_at": "2025-11-05T21:45:10.172Z", @@ -376,7 +376,7 @@ "body": "This incident has been fully resolved and we have not seen any further errors. If you see any problems please reach out at support@dnsimple.com", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-29T23:52:59.323Z", "resolved_inferred": false, "started_at": "2025-10-29T22:05:46.972Z", @@ -389,7 +389,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-24T02:00:07.193Z", "resolved_inferred": false, "started_at": "2025-10-24T00:21:17.519Z", @@ -402,7 +402,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-14T21:14:34.442Z", "resolved_inferred": false, "started_at": "2025-10-14T20:26:08.914Z", @@ -415,7 +415,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-10T14:11:37.965Z", "resolved_inferred": false, "started_at": "2025-10-10T12:53:07.354Z", @@ -428,7 +428,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-02T08:41:19.960Z", "resolved_inferred": false, "started_at": "2025-10-02T07:49:58.000Z", @@ -441,7 +441,7 @@ "body": "This incident has been resolved, and we are not seeing further routing issues. If you have any issues reach out at support@dnsimple.com", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-19T18:34:52.811Z", "resolved_inferred": false, "started_at": "2025-09-19T18:10:09.219Z", @@ -454,7 +454,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-16T08:04:39.806Z", "resolved_inferred": false, "started_at": "2025-09-16T06:49:01.327Z", @@ -467,7 +467,7 @@ "body": "We have identified the source of the intermittent resolution issues and resolved it.\n\nIf you're still experiencing this kind of issues, please email support@dnsimple.com with traceroutes and dig trace queries if you can.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-11T23:44:39.042Z", "resolved_inferred": false, "started_at": "2025-09-11T22:53:08.050Z", @@ -480,7 +480,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-01T15:50:16.891Z", "resolved_inferred": false, "started_at": "2025-09-01T14:32:52.489Z", @@ -493,7 +493,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-21T12:30:26.974Z", "resolved_inferred": false, "started_at": "2025-08-21T11:25:59.560Z", @@ -506,7 +506,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-11T10:54:04.584Z", "resolved_inferred": false, "started_at": "2025-08-11T10:32:54.041Z", diff --git a/api/v/docaposte.json b/api/v/docaposte.json index be1b21536f9be1d4fc313492fd5dcf1987ac25f2..bee732442f34269c30c23ff01ed5a71137398768 100644 --- a/api/v/docaposte.json +++ b/api/v/docaposte.json @@ -3,7 +3,7 @@ "slug": "docaposte", "platform": "betterstack", "status_url": "https://docaposte.betteruptime.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": false, "first_watched": "2026-09-04T07:06:16Z", diff --git a/api/v/docevent.json b/api/v/docevent.json index ee27f2ed93e53f82fda8e625a5aa23ee12cfba43..9ecc552a637a32b5bfaf1d85050bbda944f968ed 100644 --- a/api/v/docevent.json +++ b/api/v/docevent.json @@ -3,7 +3,7 @@ "slug": "docevent", "platform": "instatus", "status_url": "https://docevent.instatus.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": false, "first_watched": "2026-09-04T07:06:16Z", diff --git a/api/v/docker-hub.json b/api/v/docker-hub.json index 0d1bb15f1b92ee45bca688ebbb7dd5a3bd6051dc..e8dd19b3255cde1e0174ebe6071fb3c8520dcd31 100644 --- a/api/v/docker-hub.json +++ b/api/v/docker-hub.json @@ -3,7 +3,7 @@ "slug": "docker-hub", "platform": "statuspage", "status_url": "https://www.dockerstatus.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:16:22Z", @@ -12,7 +12,7 @@ "body": "Resolved", "first_seen": "2026-09-04T07:16:22Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-31T20:48:37Z", "resolved_inferred": false, "started_at": "2026-08-24T19:13:56Z", @@ -24,7 +24,7 @@ "body": "Service are restored back to normal", "first_seen": "2026-09-04T07:16:22Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-24T18:13:52Z", "resolved_inferred": false, "started_at": "2026-08-24T19:13:55Z", @@ -36,7 +36,7 @@ "body": "The system has been restored to normal operational levels", "first_seen": "2026-09-04T07:16:22Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-22T08:00:56Z", "resolved_inferred": false, "started_at": "2026-08-24T19:13:54Z", @@ -48,7 +48,7 @@ "body": "Vendor issue resolved", "first_seen": "2026-09-04T07:16:22Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-13T19:57:48Z", "resolved_inferred": false, "started_at": "2026-08-24T19:13:53Z", @@ -60,7 +60,7 @@ "body": "Error rates are back to normal", "first_seen": "2026-09-04T07:16:22Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-03T15:49:57Z", "resolved_inferred": false, "started_at": "2026-08-24T19:13:52Z", @@ -72,7 +72,7 @@ "body": "The issue is now resolved", "first_seen": "2026-09-04T07:16:22Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-04T13:43:08Z", "resolved_inferred": false, "started_at": "2026-08-24T19:13:52Z", @@ -84,7 +84,7 @@ "body": "Docker Hub performances are back to normal.", "first_seen": "2026-09-04T07:16:22Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-21T14:32:19Z", "resolved_inferred": false, "started_at": "2026-08-24T19:13:51Z", @@ -96,7 +96,7 @@ "body": "Issue appears to be resolved", "first_seen": "2026-09-04T07:16:22Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-15T16:43:51Z", "resolved_inferred": false, "started_at": "2026-08-24T19:13:50Z", @@ -108,7 +108,7 @@ "body": "Internal maintenance has completed, system has recovered.", "first_seen": "2026-09-04T07:16:22Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-25T19:18:36Z", "resolved_inferred": false, "started_at": "2026-08-24T19:13:49Z", @@ -120,7 +120,7 @@ "body": "Our authentication provider has concluded the incident, citing that authentication is functioning as expected. Docker authentication remains stable.", "first_seen": "2026-09-04T07:16:22Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-22T19:19:27Z", "resolved_inferred": false, "started_at": "2026-08-24T19:13:48Z", @@ -132,7 +132,7 @@ "body": "The system remains stable. We will continue monitoring and investigate the service degradation happened between 8AM and 10AM CET.", "first_seen": "2026-09-04T07:16:22Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-07T11:39:53Z", "resolved_inferred": false, "started_at": "2026-08-24T19:13:48Z", @@ -144,7 +144,7 @@ "body": "Authentication services remain stable. We are continuing to work directly with the affected customers on client-specific issues unrelated to Docker services.", "first_seen": "2026-09-04T07:16:22Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-08T00:31:13Z", "resolved_inferred": false, "started_at": "2026-08-24T19:13:47Z", @@ -156,7 +156,7 @@ "body": "Errors affecting organization creation have been resolved and systems remain stable.", "first_seen": "2026-09-04T07:16:22Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-05T22:56:51Z", "resolved_inferred": false, "started_at": "2026-08-24T19:13:46Z", @@ -168,7 +168,7 @@ "body": "The incident is resolved. Authentication is working normally.", "first_seen": "2026-09-04T07:16:22Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-17T17:09:27Z", "resolved_inferred": false, "started_at": "2026-08-24T19:13:45Z", @@ -180,7 +180,7 @@ "body": "Our provider communicated that they fixed their issue. We are resolving this incident as no related issue has been identified on our side.", "first_seen": "2026-09-04T07:16:22Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-18T15:29:00Z", "resolved_inferred": false, "started_at": "2026-08-24T19:13:44Z", @@ -192,7 +192,7 @@ "body": "Incident resolved.", "first_seen": "2026-09-04T07:16:22Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-05T09:58:07Z", "resolved_inferred": false, "started_at": "2026-08-24T19:13:44Z", @@ -204,7 +204,7 @@ "body": "Cloudflare has recovered and so have Testcontainers Cloud and Offload.", "first_seen": "2026-09-04T07:16:22Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-18T17:24:12Z", "resolved_inferred": false, "started_at": "2026-08-24T19:13:43Z", @@ -216,7 +216,7 @@ "body": "This issue is resolved. Thank you for your patience.", "first_seen": "2026-09-04T07:16:22Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-16T20:42:21Z", "resolved_inferred": false, "started_at": "2026-08-24T19:13:42Z", @@ -228,7 +228,7 @@ "body": "We are not seeing errors creating new DHI repository mirrors. This issue has been resolved. Thanks for your patience.", "first_seen": "2026-09-04T07:16:22Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-04T07:55:52Z", "resolved_inferred": false, "started_at": "2026-08-24T19:13:41Z", @@ -240,7 +240,7 @@ "body": "After rolling out fixes earlier, we have not seen a recurrence of the login failures. \r\n\r\nThe login issues have been resolved. Thank you for your patience", "first_seen": "2026-09-04T07:16:22Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-13T02:58:31Z", "resolved_inferred": false, "started_at": "2026-08-24T19:13:41Z", @@ -252,7 +252,7 @@ "body": "This has been fully resolved.", "first_seen": "2026-09-04T07:16:22Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-04T05:46:48Z", "resolved_inferred": false, "started_at": "2026-08-24T19:13:40Z", @@ -264,7 +264,7 @@ "body": "The issue has been resolved. Docker Build Cloud availability is back to normal.", "first_seen": "2026-09-04T07:16:22Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-28T20:12:37Z", "resolved_inferred": false, "started_at": "2026-08-24T19:13:39Z", @@ -276,7 +276,7 @@ "body": "Incident has been resolved. Users should now be able to retry their builds", "first_seen": "2026-09-04T07:16:22Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-21T09:42:14Z", "resolved_inferred": false, "started_at": "2026-08-24T19:13:38Z", @@ -288,7 +288,7 @@ "body": "This incident is resolved.", "first_seen": "2026-09-04T07:16:22Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-20T10:05:21Z", "resolved_inferred": false, "started_at": "2026-08-24T19:13:37Z", @@ -300,7 +300,7 @@ "body": "All systems are working normally.", "first_seen": "2026-09-04T07:16:22Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-21T00:38:14Z", "resolved_inferred": false, "started_at": "2026-08-24T19:13:37Z", diff --git a/api/v/doctolib.json b/api/v/doctolib.json index 6395c5e35044ea7489906dd7f824520e9692908c..ff0be254eaa9147a389cf6363d162b9ef4259d3e 100644 --- a/api/v/doctolib.json +++ b/api/v/doctolib.json @@ -3,7 +3,7 @@ "slug": "doctolib", "platform": "statuspage", "status_url": "https://status.doctolib.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-09-01T19:28:47.215+02:00", "resolved_inferred": false, "started_at": "2026-09-01T18:05:46.261+02:00", @@ -25,7 +25,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-09-01T11:52:53.351+02:00", "resolved_inferred": false, "started_at": "2026-09-01T11:38:50.887+02:00", @@ -38,7 +38,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-28T14:01:02.499+02:00", "resolved_inferred": false, "started_at": "2026-08-28T13:02:02.185+02:00", @@ -51,7 +51,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-18T17:51:22.169+02:00", "resolved_inferred": false, "started_at": "2026-08-18T17:24:56.020+02:00", @@ -64,7 +64,7 @@ "body": "The performance incident affecting the following component has been fully resolved:\n\nAll services are stable and operating normally.\n\nWe apologize for the inconvenience and thank you for your patience.\n\n\u2014 Your Doctolib Team", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-05T09:05:54.357+02:00", "resolved_inferred": false, "started_at": "2026-08-04T16:44:30.091+02:00", @@ -77,7 +77,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-28T13:01:35.237+02:00", "resolved_inferred": false, "started_at": "2026-07-28T10:54:41.628+02:00", @@ -90,7 +90,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-16T10:17:23.043+02:00", "resolved_inferred": false, "started_at": "2026-07-16T09:30:26.565+02:00", @@ -103,7 +103,7 @@ "body": "The performance incident affecting the following components has been fully resolved:\n\nAll services are stable and operating normally.\n\nWe apologize for the inconvenience and thank you for your patience.\n\n\u2014 Your Doctolib Team", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-30T12:36:33.431+02:00", "resolved_inferred": false, "started_at": "2026-06-30T12:18:39.816+02:00", @@ -116,7 +116,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-25T16:38:29.750+02:00", "resolved_inferred": false, "started_at": "2026-06-25T15:49:47.051+02:00", @@ -129,7 +129,7 @@ "body": "The performance incident affecting the following component has been fully resolved:\n\nAll services are stable and operating normally.\n\nWe apologize for the inconvenience and thank you for your patience.\n\n\u2014 Your Doctolib Team", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-23T15:07:19.266+02:00", "resolved_inferred": false, "started_at": "2026-06-23T14:58:51.240+02:00", @@ -142,7 +142,7 @@ "body": "The performance incident affecting the following component has been fully resolved:\n\nAll services are stable and operating normally.\n\nWe apologize for the inconvenience and thank you for your patience.\n\n\u2014 Your Doctolib Team", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-05T16:26:03.035+02:00", "resolved_inferred": false, "started_at": "2026-06-05T16:03:33.012+02:00", @@ -155,7 +155,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-30T15:43:48.100+02:00", "resolved_inferred": false, "started_at": "2026-05-29T17:11:14.457+02:00", @@ -168,7 +168,7 @@ "body": "The performance incident affecting the following component has been fully resolved:\n\nAll services are stable and operating normally.\n\nWe apologize for the inconvenience and thank you for your patience.\n\n\u2014 Your Doctolib Team", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-29T14:43:11.780+02:00", "resolved_inferred": false, "started_at": "2026-05-29T13:42:23.464+02:00", @@ -181,7 +181,7 @@ "body": "The performance incident affecting the following component has been fully resolved:\n\nAll services are stable and operating normally.\n\nWe apologize for the inconvenience and thank you for your patience.\n\n\u2014 Your Doctolib Team", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-20T17:44:51.378+02:00", "resolved_inferred": false, "started_at": "2026-05-20T17:28:42.478+02:00", @@ -194,7 +194,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-06T09:33:31.449+02:00", "resolved_inferred": false, "started_at": "2026-05-06T08:54:08.098+02:00", @@ -207,7 +207,7 @@ "body": "The performance incident affecting the following component has been fully resolved.\n\nAll services are stable and operating normally.\n\nWe apologize for the inconvenience and thank you for your patience.\n\n\u2014 Your Doctolib Team", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-05T10:59:04.497+02:00", "resolved_inferred": false, "started_at": "2026-05-05T09:57:05.298+02:00", @@ -220,7 +220,7 @@ "body": "The performance incident affecting the following component has been fully resolved.\n\nAll services are stable and operating normally.\n\nWe apologize for the inconvenience and thank you for your patience.\n\n\u2014 Your Doctolib Team", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-22T11:45:57.531+02:00", "resolved_inferred": false, "started_at": "2026-04-22T10:45:30.832+02:00", @@ -233,7 +233,7 @@ "body": "The performance incident affecting the following component has been fully resolved.\n\nAll services are stable and operating normally.\n\nWe apologize for the inconvenience and thank you for your patience.\n\n\u2014 Your Doctolib Team", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-10T16:43:41.236+02:00", "resolved_inferred": false, "started_at": "2026-04-10T15:21:31.242+02:00", @@ -246,7 +246,7 @@ "body": "The performance incident affecting the following components has been fully resolved:\n\nAll services are stable and operating normally.\n\nWe apologize for the inconvenience and thank you for your patience.\n\n\u2014 Your Doctolib Team", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-07T14:23:16.842+02:00", "resolved_inferred": false, "started_at": "2026-04-07T14:09:07.960+02:00", @@ -259,7 +259,7 @@ "body": "Doctolib fonctionne \u00e0 nouveau normalement pour tout le monde.\n\n---\n\nDoctolib ist wieder f\u00fcr alle Nutzer:innen verf\u00fcgbar.\n\n---\n\nDoctolib funziona per tutti gli utenti.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-05T13:18:31.103+01:00", "resolved_inferred": false, "started_at": "2025-12-05T10:51:14.999+01:00", @@ -272,7 +272,7 @@ "body": "Doctolib fonctionne \u00e0 nouveau normalement pour tout le monde.\n\n---\n\nDoctolib ist wieder f\u00fcr alle Nutzer:innen verf\u00fcgbar.\n\n---\n\nDoctolib funziona per tutti gli utenti.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-05T10:55:48.926+01:00", "resolved_inferred": false, "started_at": "2025-12-05T10:04:36.030+01:00", diff --git a/api/v/documo.json b/api/v/documo.json index 10bbff69c88c27f02fc7f08a695311965c26448e..28eba74f9659bcda7393fa884bf58a833c3f646d 100644 --- a/api/v/documo.json +++ b/api/v/documo.json @@ -3,7 +3,7 @@ "slug": "documo", "platform": "statuspage", "status_url": "https://status.documo.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-25T11:58:28.541-07:00", "resolved_inferred": false, "started_at": "2026-08-25T09:03:22.052-07:00", @@ -25,7 +25,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-03T07:02:23.483-07:00", "resolved_inferred": false, "started_at": "2026-08-03T05:52:04.326-07:00", @@ -38,7 +38,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-21T16:09:42.103-07:00", "resolved_inferred": false, "started_at": "2026-07-21T13:54:10.291-07:00", @@ -51,7 +51,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-08T10:39:54.904-07:00", "resolved_inferred": false, "started_at": "2026-07-08T09:56:52.498-07:00", @@ -64,7 +64,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-08T09:23:58.501-07:00", "resolved_inferred": false, "started_at": "2026-07-08T07:52:18.498-07:00", @@ -77,7 +77,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-29T14:46:46.346-07:00", "resolved_inferred": false, "started_at": "2026-06-29T08:26:48.088-07:00", @@ -90,7 +90,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-16T09:56:19.196-07:00", "resolved_inferred": false, "started_at": "2026-06-16T08:05:56.086-07:00", @@ -103,7 +103,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-15T09:41:42.587-07:00", "resolved_inferred": false, "started_at": "2026-06-15T07:51:18.000-07:00", @@ -116,7 +116,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-10T10:27:25.556-07:00", "resolved_inferred": false, "started_at": "2026-06-10T09:16:23.633-07:00", @@ -129,7 +129,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-03T08:09:47.258-07:00", "resolved_inferred": false, "started_at": "2026-06-03T06:26:49.771-07:00", @@ -142,7 +142,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-28T06:21:05.184-07:00", "resolved_inferred": false, "started_at": "2026-04-27T14:15:55.385-07:00", @@ -155,7 +155,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-31T08:09:03.698-07:00", "resolved_inferred": false, "started_at": "2026-03-31T05:27:04.768-07:00", @@ -168,7 +168,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-19T12:04:29.546-08:00", "resolved_inferred": false, "started_at": "2026-02-19T08:58:22.316-08:00", @@ -181,7 +181,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-18T12:28:28.338-08:00", "resolved_inferred": false, "started_at": "2026-02-18T11:24:04.072-08:00", @@ -194,7 +194,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-16T13:45:18.769-08:00", "resolved_inferred": false, "started_at": "2026-02-16T07:38:06.468-08:00", @@ -207,7 +207,7 @@ "body": "This incident has been resolved and the backlog has been cleared.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-12T09:46:53.092-08:00", "resolved_inferred": false, "started_at": "2026-01-12T06:35:49.473-08:00", @@ -220,7 +220,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-12T06:33:53.502-08:00", "resolved_inferred": false, "started_at": "2025-12-11T10:18:47.203-08:00", @@ -233,7 +233,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-07T12:04:32.189-07:00", "resolved_inferred": false, "started_at": "2025-10-06T13:01:33.084-07:00", @@ -246,7 +246,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-06T10:01:24.914-07:00", "resolved_inferred": false, "started_at": "2025-10-06T07:23:55.644-07:00", @@ -259,7 +259,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-25T11:21:50.149-07:00", "resolved_inferred": false, "started_at": "2025-08-25T08:20:18.747-07:00", @@ -272,7 +272,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-05T13:12:03.572-07:00", "resolved_inferred": false, "started_at": "2025-08-05T10:00:07.975-07:00", diff --git a/api/v/doit.json b/api/v/doit.json index 3d1ef5c898fc8e2dc86f7346c4a0f5ee15a505d5..066f70f194cfc2cafb1e0f309032c36f3f4d7951 100644 --- a/api/v/doit.json +++ b/api/v/doit.json @@ -3,7 +3,7 @@ "slug": "doit", "platform": "statuspage", "status_url": "https://status.doit.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "Google has resolved the incident and all components should be operational.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-09-02T17:23:13.305Z", "resolved_inferred": false, "started_at": "2026-09-01T16:07:30.027Z", @@ -25,7 +25,7 @@ "body": "The AWS billing data issue has now been resolved.\n\nWe have validated the recovery and confirmed that the affected cost data has stabilised. Related cost views and notifications in DoiT Cloud Intelligence should now reflect normal behaviour. \n\nThank you for your patience and understanding throughout this incident.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-19T09:01:56.719Z", "resolved_inferred": false, "started_at": "2026-07-17T10:13:45.786Z", @@ -38,7 +38,7 @@ "body": "The incident has been resolved. All systems are operating normally.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-28T13:02:00.344Z", "resolved_inferred": false, "started_at": "2026-06-26T23:12:00.098Z", @@ -51,7 +51,7 @@ "body": "CloudHealth\u2019s fix has been validated on our side, and we have confirmed that the affected April AWS cost data has been corrected. At this time, the issue is resolved, and we are no longer seeing unexpected behavior related to this incident. Thank you for your patience and understanding while we worked through the investigation, remediation, and validation process with CloudHealth.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-28T09:12:22.925Z", "resolved_inferred": false, "started_at": "2026-05-18T13:05:58.331Z", @@ -64,7 +64,7 @@ "body": "We are pleased to confirm that the AWS data ingestion issue in DoiT Cloud Intelligence, impacting consolidated resold customers, has now been resolved.\nAll affected data ingestion workflows are operating normally again.\nThank you for your patience and understanding while our teams worked to address this issue.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-13T17:05:53.843Z", "resolved_inferred": false, "started_at": "2026-05-08T11:49:18.445Z", @@ -77,7 +77,7 @@ "body": "We have fully resolved the AWS data ingestion issues in DoiT Cloud Intelligence, including those impacting customers with AWS accounts managed via CloudHealth on shared payer accounts. Data is now populating as expected for affected customers, and ingestion pipelines are operating normally.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-10T13:41:08.448Z", "resolved_inferred": false, "started_at": "2026-04-06T13:39:22.894Z", @@ -90,7 +90,7 @@ "body": "The AWS ingestion issue in DoiT Cloud Intelligence has been resolved, and the affected data has been updated. Thank you for your patience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-31T16:21:56.293Z", "resolved_inferred": false, "started_at": "2026-03-27T12:02:52.344Z", @@ -103,7 +103,7 @@ "body": "We have fixed the issue and expect data to be updated in your DCI console within the next few hours", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-26T10:57:05.162Z", "resolved_inferred": false, "started_at": "2026-03-26T09:58:34.757Z", @@ -116,7 +116,7 @@ "body": "Google has confirmed that the underlying issue causing delays in GCP Billing exports to BigQuery has been fixed, and data delivery has returned to normal. \nOur team has verified that recent billing data is being delivered successfully and does not expect further impact from this incident. We appreciate your patience and understanding.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-09T08:22:07.966Z", "resolved_inferred": false, "started_at": "2026-03-06T16:26:59.032Z", @@ -129,7 +129,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-28T00:52:24.829Z", "resolved_inferred": false, "started_at": "2026-02-16T19:43:33.140Z", @@ -142,7 +142,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-19T07:31:03.718Z", "resolved_inferred": false, "started_at": "2026-02-16T08:31:36.724Z", @@ -155,7 +155,7 @@ "body": "We have completed ingestion of the Google Cloud Platform (GCP) billing exports and are now seeing GCP cost and usage data fully up to date in the DoiT Console and Cloud Analytics. Our monitoring confirms that data freshness and completeness have returned to normal. We apologize for any inconvenience and appreciate your patience and understanding while we worked through this upstream issue.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-20T13:54:14.422Z", "resolved_inferred": false, "started_at": "2026-01-13T12:26:15.687Z", @@ -168,7 +168,7 @@ "body": "This incident has been resolved. Public APIs continue to operate normally and our monitoring has not detected any further issues. No additional customer impact is expected.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-03T07:35:19.638Z", "resolved_inferred": false, "started_at": "2026-01-03T00:02:49.315Z", @@ -181,7 +181,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-11T16:39:45.115Z", "resolved_inferred": false, "started_at": "2025-12-11T12:23:13.311Z", @@ -194,7 +194,7 @@ "body": "Access to Billing profiles in the DoiT console has been fully restored, and all services are operating as expected. We appreciate your understanding and thank you for your patience while our team worked to resolve this issue.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-10T10:49:25.902Z", "resolved_inferred": false, "started_at": "2025-12-08T14:15:42.908Z", @@ -207,7 +207,7 @@ "body": "We can confirm that service has been fully restored. Okta Single Sign-On (SSO) access to the DoiT Platform is now operating normally and sign-ins are completing as expected. \nThank you for your patience and understanding while we worked to resolve this.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-03T05:29:43.914Z", "resolved_inferred": false, "started_at": "2025-12-02T09:40:48.262Z", @@ -220,7 +220,7 @@ "body": "We can confirm that the issue with the third-party content delivery network has been fully resolved. Console access and performance have returned to normal. \nWe appreciate your patience and understanding.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-19T08:24:45.928Z", "resolved_inferred": false, "started_at": "2025-11-18T12:51:52.343Z", @@ -233,7 +233,7 @@ "body": "The incident has been resolved and we are now seeing correct BigQuery Lens storage Metrics", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-12T15:37:41.702Z", "resolved_inferred": false, "started_at": "2025-10-23T08:58:14.926Z", @@ -246,7 +246,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-23T12:11:40.358Z", "resolved_inferred": false, "started_at": "2025-10-23T05:06:24.000Z", @@ -259,7 +259,7 @@ "body": "The issue with our email service provider has been fully resolved. Email delivery is now operating normally across all features.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-31T15:05:55.992Z", "resolved_inferred": false, "started_at": "2025-08-31T10:10:22.799Z", @@ -272,7 +272,7 @@ "body": "The incident has been resolved and we are now seeing normal incoming billing data from GCP", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-07T09:47:13.879Z", "resolved_inferred": false, "started_at": "2025-08-03T15:39:13.384Z", diff --git a/api/v/dongee.json b/api/v/dongee.json index 4928b47357a788320f9c8c6c6e063f2cdb2453c2..82c9a58fc82a5b2c39f6991cb0fbfd64d87f2d4a 100644 --- a/api/v/dongee.json +++ b/api/v/dongee.json @@ -3,7 +3,7 @@ "slug": "dongee", "platform": "statuspage", "status_url": "https://status.dongee.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "Todos los servicios trabajan con normalidad. El equipo t\u00e9cnico continuar\u00e1 dando revisi\u00f3n.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-21T17:11:37Z", "resolved_inferred": false, "started_at": "2026-07-21T16:24:10Z", @@ -24,7 +24,7 @@ "body": "El inconveniente fue resuelto en nuestra \u00faltima notificaci\u00f3n y todos los servicios trabajan con normalidad desde entonces", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-15T02:41:19Z", "resolved_inferred": false, "started_at": "2026-07-14T11:18:57Z", @@ -36,7 +36,7 @@ "body": "El inconveniente fue resuelto y todos los usuarios pueden acceder de forma correcta a su cPanel y webmail.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-09T00:35:06Z", "resolved_inferred": false, "started_at": "2026-07-08T21:52:31Z", @@ -48,7 +48,7 @@ "body": "El inconveniente fue resuelto y los servicios trabajan con normalidad", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-08T21:48:39Z", "resolved_inferred": false, "started_at": "2026-06-24T11:26:35Z", @@ -60,7 +60,7 @@ "body": "En estos momentos ya son accesibles los portales con normalidad.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-22T16:24:51Z", "resolved_inferred": false, "started_at": "2026-06-22T15:28:06Z", @@ -72,7 +72,7 @@ "body": "El nodo afectado se encuentra trabajando con normalidad y se ha reintegrado a la carga de trabajo. Todos los servicios operan con normalidad.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-17T18:06:05Z", "resolved_inferred": false, "started_at": "2026-06-17T15:28:54Z", @@ -84,7 +84,7 @@ "body": "Los parches correspondientes han sido aplicados en las versiones m\u00e1s recientes de cPanel.\n\nPara el caso de los servidores compartidos los correspondientes parches se encuentran aplicados. Para los servidores Cloud y Dedicados recomendamos actualizar cPanel a su versi\u00f3n m\u00e1s reciente e instalar licencias de servicios de seguridad como Imunify360 para contar con una capa adicional de seguridad.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-19T19:28:16Z", "resolved_inferred": false, "started_at": "2026-04-30T20:26:35Z", @@ -96,7 +96,7 @@ "body": "El inconveniente ha sido resuelto y todos los servicios operan con normalidad.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-06T11:02:53Z", "resolved_inferred": false, "started_at": "2026-04-03T00:59:14Z", @@ -108,7 +108,7 @@ "body": "El servicio de red trabaja con normalidad", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-28T15:14:20Z", "resolved_inferred": false, "started_at": "2026-03-28T14:25:22Z", @@ -120,7 +120,7 @@ "body": "El inconveniente se encuentra resuelto", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-27T15:01:57Z", "resolved_inferred": false, "started_at": "2026-03-27T13:55:42Z", @@ -132,7 +132,7 @@ "body": "Se identifico cantidad alta de procesos en el servicio web solo afectando a paginas el cual fue corregido, no hubo afectaci\u00f3n a nivel de aplicaciones y/o bases de datos.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-21T19:25:05Z", "resolved_inferred": false, "started_at": "2026-03-21T18:58:31Z", @@ -144,7 +144,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-16T10:34:18Z", "resolved_inferred": false, "started_at": "2026-03-16T05:31:40Z", @@ -156,7 +156,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-13T09:28:20Z", "resolved_inferred": false, "started_at": "2026-03-13T09:15:40Z", @@ -168,7 +168,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-11T08:23:47Z", "resolved_inferred": false, "started_at": "2026-03-11T07:48:40Z", @@ -180,7 +180,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-11T05:25:32Z", "resolved_inferred": false, "started_at": "2026-03-11T05:16:40Z", @@ -192,7 +192,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-10T13:10:34Z", "resolved_inferred": false, "started_at": "2026-03-10T11:56:00Z", @@ -204,7 +204,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-05T17:48:13Z", "resolved_inferred": false, "started_at": "2026-03-05T17:45:00Z", @@ -216,7 +216,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-03T00:41:24Z", "resolved_inferred": false, "started_at": "2026-03-03T00:33:40Z", @@ -228,7 +228,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-03T00:19:28Z", "resolved_inferred": false, "started_at": "2026-03-03T00:07:40Z", @@ -240,7 +240,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-01T14:42:01Z", "resolved_inferred": false, "started_at": "2026-03-01T14:24:40Z", @@ -252,7 +252,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-28T17:54:09Z", "resolved_inferred": false, "started_at": "2026-02-28T17:45:00Z", @@ -264,7 +264,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-27T20:53:52Z", "resolved_inferred": false, "started_at": "2026-02-27T20:52:41Z", @@ -276,7 +276,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-26T21:56:46Z", "resolved_inferred": false, "started_at": "2026-02-26T21:55:40Z", @@ -288,7 +288,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-26T17:56:33Z", "resolved_inferred": false, "started_at": "2026-02-26T17:51:41Z", @@ -300,7 +300,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-26T16:51:01Z", "resolved_inferred": false, "started_at": "2026-02-26T16:50:00Z", diff --git a/api/v/doodle.json b/api/v/doodle.json index 152883caaeb706477172e55357f0e63d04b22bae..6a34f97bc5b9d0e27cb15c97ba1e5893ed9a4a16 100644 --- a/api/v/doodle.json +++ b/api/v/doodle.json @@ -3,7 +3,7 @@ "slug": "doodle", "platform": "statuspage", "status_url": "https://uptime.doodle.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-05T10:27:54.037+01:00", "resolved_inferred": false, "started_at": "2025-12-05T10:00:56.272+01:00", diff --git a/api/v/doppler.json b/api/v/doppler.json index 0d9597abcf83203c69671d97ad9f8bfa3407bc85..d412b94ca4bba9e3211496f4e48d941a546b1aab 100644 --- a/api/v/doppler.json +++ b/api/v/doppler.json @@ -3,7 +3,7 @@ "slug": "doppler", "platform": "statuspage", "status_url": "https://www.dopplerstatus.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "This incident has been resolved by our engineering team.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-16T17:08:47.765-07:00", "resolved_inferred": false, "started_at": "2026-07-16T17:03:47.390-07:00", @@ -25,7 +25,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-20T11:46:29.171-08:00", "resolved_inferred": false, "started_at": "2025-11-20T07:55:35.694-08:00", @@ -38,7 +38,7 @@ "body": "This incident is now resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-18T06:59:24.709-08:00", "resolved_inferred": false, "started_at": "2025-11-18T03:48:10.000-08:00", @@ -51,7 +51,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-20T12:58:59.685-07:00", "resolved_inferred": false, "started_at": "2025-08-20T11:52:22.000-07:00", @@ -64,7 +64,7 @@ "body": "The issue is resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-05T22:40:53.876-07:00", "resolved_inferred": false, "started_at": "2025-08-05T20:36:36.842-07:00", diff --git a/api/v/dracoon.json b/api/v/dracoon.json index 6e91d6e87ed1e89c7f9c314b7895a8b252cd20f3..9c38bcde78181dfd66fef789418afd1f3510b5ae 100644 --- a/api/v/dracoon.json +++ b/api/v/dracoon.json @@ -3,7 +3,7 @@ "slug": "dracoon", "platform": "statuspage", "status_url": "https://status.dracoon.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "We experienced an issue with DRACOON Cloud on 2026-07-16 from around 00:05 to 00:30 CEST. Our team has worked diligently to identify the root cause and implement a resolution. In this post-mortem, we want to share the details of what happened, why it happened, what we did to resolve it, and what we will do to prevent similar incidents in the future.\n\n\u200c\n\n**What happened?**\n\nOur datacenter provider experienced availability issues in a region and availability zone, where some our DRACOON Cloud infrastructure is running. As a result of that, parts of DRACOON Cloud were unavailable or had degraded performance during the time of the incident. \n\n\u200c\n\n**What did we do?** \n\nOur engineers analyzed the situation and applied a technical workaround to fully restore availability as fast as possible. \n\n\u200c\n\nWe apologize for any inconvenience this incident may have caused. We are committed to ensuring the stability and reliability of our services and will continue to take proactive measures to prevent similar incidents from happening in the future.\n\nIf you have any questions or concerns, please don't hesitate to reach out to our support team for assistance.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-16T00:05:00.000+02:00", "resolved_inferred": false, "started_at": "2026-07-16T00:05:00.000+02:00", @@ -25,7 +25,7 @@ "body": "The issue with DRACOON has been fully resolved. All systems are now operating normally. We apologize for any inconvenience this may have caused and appreciate your patience. If you continue to experience any issues, please don't hesitate to reach out to our support team for assistance.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-01T12:26:02.850+02:00", "resolved_inferred": false, "started_at": "2026-07-01T11:32:09.603+02:00", @@ -38,7 +38,7 @@ "body": "The issue with Virus Protection has been fully resolved. All systems are now operating normally. We apologize for any inconvenience this may have caused and appreciate your patience. If you continue to experience any issues, please don't hesitate to reach out to our support team for assistance.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-16T22:57:15.135+02:00", "resolved_inferred": false, "started_at": "2026-04-16T13:00:22.000+02:00", @@ -51,7 +51,7 @@ "body": "We experienced an issue with our WebApp on 2026-03-24 from around 9:30 to 11:00 CET. Our team has worked diligently to identify the root cause and implement a resolution. In this post-mortem, we want to share the details of what happened, why it happened, what we did to resolve it, and what we will do to prevent similar incidents in the future.\n\n**What happened?**\n\nWe experienced service instability caused by a bug in a third-party dependency. This resulted in intermittent errors and degraded performance of the Web App.\n\n**Why did this happen?**\n\nA bug in a third-party dependency caused unexpected errors in our Web App, leading to occasional crashes. This issue was triggered under specific conditions that were not caught in prior testing.\n\n**What did we do?**\n\nWe resolved the issue temporarily by implementing a safeguard and later by properly solving the issue with this dependency. Stability was restored once the temporary fix was deployed, with full recovery at around 10:40 CET.\n\n**What can we do to improve?**\n\nWe will expand our test coverage to better capture edge cases, ensuring that unusual or unexpected scenarios, especially those that lead to this incident, are identified and prevented before deployment.\n\nWe apologize for any inconvenience this incident may have caused. We are committed to ensuring the stability and reliability of our services and will continue to take proactive measures to prevent similar incidents from happening in the future.\n\nIf you have any questions or concerns, please don't hesitate to reach out to our support team for assistance.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-25T13:03:55.384+01:00", "resolved_inferred": false, "started_at": "2026-03-24T09:30:48.000+01:00", @@ -64,7 +64,7 @@ "body": "We have been experiencing issues with our DRACOON service from 11:00 to 11:40 on 2026-01-12. Our team was working to resolve the issue as quickly as possible. We apologize for any inconvenience this may have caused.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-12T11:40:00.000+01:00", "resolved_inferred": false, "started_at": "2026-01-12T11:00:00.000+01:00", @@ -77,7 +77,7 @@ "body": "The issue with DRACOON Cloud has been fully resolved. All systems are now operating normally. We apologize for any inconvenience this may have caused and appreciate your patience. If you continue to experience any issues, please don't hesitate to reach out to our support team for assistance.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-08T11:44:55.420+01:00", "resolved_inferred": false, "started_at": "2026-01-08T11:00:00.000+01:00", @@ -90,7 +90,7 @@ "body": "The issue with Virus Protection Scanning has been fully resolved. All systems are now operating normally. We apologize for any inconvenience this may have caused and appreciate your patience. If you continue to experience any issues, please don't hesitate to reach out to our support team for assistance.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-27T14:58:41.172+01:00", "resolved_inferred": false, "started_at": "2025-11-27T09:30:12.056+01:00", @@ -103,7 +103,7 @@ "body": "From 14:55 to 15:05 today, we experienced some issues and a partial outages of DRACOON Cloud. Our team quickly identified and resolved the issue. We apologize for any inconvenience this may have caused.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-20T14:55:00.000+01:00", "resolved_inferred": false, "started_at": "2025-11-20T14:55:00.000+01:00", @@ -116,7 +116,7 @@ "body": "The issue with DRACOON Virus Protection has been fully resolved. All systems are now operating normally. We apologize for any inconvenience this may have caused and appreciate your patience. If you continue to experience any issues, please don't hesitate to reach out to our support team for assistance.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-19T12:27:25.705+01:00", "resolved_inferred": false, "started_at": "2025-11-19T09:42:07.337+01:00", @@ -129,7 +129,7 @@ "body": "We experienced an issue with our Virus Protection feature on 13.08.2025 at around 12:00 CEST. Our team has worked diligently to identify the root cause and implement a resolution. In this post-mortem, we want to share the details of what happened, why it happened, what we did to resolve it, and what we will do to prevent similar incidents in the future.\n\n**What happened?** \nAt 12:00 CEST, monitoring alerted the team about increased latency in the Virus Protection service. Investigation revealed that unusually high load from a spike in file scanning requests overwhelmed the systems processing capacity, leading to degraded performance for a subset of customers.\n\n**Why did this happen?** \nThe Virus Protection service was able to keep up with the increased load for scanning files, but the responses were not processed fast enough by another service, leading to missing/delayed verdicts for the files that had to be scanned. \n\n**What did we do?** \nThe team manually scaled out the service to restore capacity. At 15:45, latency metrics returned to normal and the functionality was fully restored.\n\n**What can we do to improve?** \nWe are investigating the root cause of the slow response processing and will reconfigure the service in question to make sure to eliminate the bottleneck.\n\nWe apologize for any inconvenience this incident may have caused. We are committed to ensuring the stability and reliability of our services and will continue to take proactive measures to prevent similar incidents from happening in the future.\n\nIf you have any questions or concerns, please don't hesitate to reach out to our support team for assistance.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-13T16:59:45.686+02:00", "resolved_inferred": false, "started_at": "2025-08-13T12:00:03.567+02:00", @@ -142,7 +142,7 @@ "body": "The issue with our Support Portal has been fully resolved. We apologize for any inconvenience this may have caused and appreciate your patience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-04T09:25:05.261+02:00", "resolved_inferred": false, "started_at": "2025-08-04T08:58:31.021+02:00", diff --git a/api/v/drata.json b/api/v/drata.json index fa9402285bd2ab1ca1810c5a8dec531950332cf4..eac506c11a0fec135a3ea2c5c39038b0b6a5cc5c 100644 --- a/api/v/drata.json +++ b/api/v/drata.json @@ -3,7 +3,7 @@ "slug": "drata", "platform": "statuspage", "status_url": "https://dratastatus.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "unknown", "history_backfilled": false, "first_watched": "2026-09-04T07:06:16Z", diff --git a/api/v/drchrono.json b/api/v/drchrono.json index 3a6323a673d292336a45607a4cfd7d6901b8f1ed..769792e52927701d065c137300f31880c3f80433 100644 --- a/api/v/drchrono.json +++ b/api/v/drchrono.json @@ -3,7 +3,7 @@ "slug": "drchrono", "platform": "statuspage", "status_url": "https://status.drchrono.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "Our integration, Updox, has confirmed that the service disruption has been resolved and all services are operational.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-15T12:10:22.072-07:00", "resolved_inferred": false, "started_at": "2026-07-15T10:42:54.974-07:00", @@ -25,7 +25,7 @@ "body": "The system remains operational, and we have not observed any further issues since moving to monitoring yesterday. This incident has been resolved. Our Engineering team will continue to review the event as part of our ongoing efforts to maintain the reliability and performance of the platform. Thank you for your patience,", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-08T13:29:53.823-07:00", "resolved_inferred": false, "started_at": "2026-07-07T09:59:43.380-07:00", @@ -38,7 +38,7 @@ "body": "We have confirmed that the adjustments we implemented have fully resolved the issue and our systems are up and operational. We appreciate your patience as we worked through this matter.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-04T12:02:14.364-07:00", "resolved_inferred": false, "started_at": "2026-06-04T05:31:50.447-07:00", @@ -51,7 +51,7 @@ "body": "We have confirmed that the adjustments we implemented have fully resolved the issue and our systems are up and operational. We appreciate your patience as we worked through this matter.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-03T12:33:58.000-07:00", "resolved_inferred": false, "started_at": "2026-06-03T08:49:03.547-07:00", @@ -64,7 +64,7 @@ "body": "The issue impacting appointment reminders has been resolved. All systems are now operating normally. Thank you for your patience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-05T10:39:50.078-07:00", "resolved_inferred": false, "started_at": "2026-05-05T09:02:17.705-07:00", @@ -77,7 +77,7 @@ "body": "DrChrono has resolved the issue that was causing slowness for a limited set of users. System performance has returned to normal, and we will continue to monitor to ensure ongoing stability.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-07T10:34:20.460-07:00", "resolved_inferred": false, "started_at": "2026-04-06T12:37:08.555-07:00", @@ -90,7 +90,7 @@ "body": "Our third-party provider, ID.me, has resolved the issue that was impacting the ability to prescribe controlled substances. Push Notification MFA is now functioning as expected.\n \nRecommended Action:\nIf you previously switched to an alternate MFA method (such as an authenticator app or SMS), you may switch back to Push Notifications. \n \nFor steps to update your MFA method, visit:\nhttps://support.drchrono.com/home/360051657392-adding-or-changing-a-device-for-multi-factor-authentication-with-id-me\n \nIf you continue to experience login issues, you may still follow ID.me\u2019s recovery steps:\nhttps://help.id.me/hc/en-us/articles/360017927633-ID-me-MFA-recovery-steps-if-you-lost-access-or-can-t-sign-in", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-07T09:30:55.076-07:00", "resolved_inferred": false, "started_at": "2026-04-03T07:15:20.416-07:00", @@ -103,7 +103,7 @@ "body": "Our engineering team has resolved the issue, and system performance has returned to normal. We appreciate your patience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-30T15:05:30.638-07:00", "resolved_inferred": false, "started_at": "2026-03-30T13:48:56.084-07:00", @@ -116,7 +116,7 @@ "body": "We have resolved the intermittent system issues experienced over the past three days. The root cause was related to brief scenarios where one of the supporting databases was unable to accept new connections, resulting in a small percentage of requests (approximately 3%) returning errors.\n \nOvernight, we implemented performance improvements to reduce system strain and help isolate the issue. Today, we made additional infrastructure adjustments to address the connection limitations and monitored system performance throughout peak usage hours. The system is now operating normally.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-25T14:36:19.000-07:00", "resolved_inferred": false, "started_at": "2026-03-25T09:59:29.379-07:00", @@ -129,7 +129,7 @@ "body": "After a successful update, this issue will be monitored closely. If you have additional questions, please do not hesitate to contact support.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-25T06:18:42.000-07:00", "resolved_inferred": false, "started_at": "2026-03-24T12:17:23.000-07:00", @@ -142,7 +142,7 @@ "body": "The issue causing system slowness across portions of the DrChrono website has been resolved. All services are now functioning normally. We appreciate your patience and understanding.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-23T16:54:39.949-07:00", "resolved_inferred": false, "started_at": "2026-03-23T12:55:24.987-07:00", @@ -155,7 +155,7 @@ "body": "The performance of billing-related reporting has remained stable following the corrective measures implemented. All reports, including all tabs of the Financial Transactions Report, continue to load as expected. After an extended monitoring period confirming system stability, this incident is now considered resolved. We have implemented preventive measures to reduce the risk of recurrence.\n\nThank you for your patience while we worked through this issue.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-24T12:59:42.677-08:00", "resolved_inferred": false, "started_at": "2026-02-09T06:55:45.414-08:00", @@ -168,7 +168,7 @@ "body": "The issue affecting billing-related reports has been resolved and all reports are loading as expected. Our monitoring has remained stable with no further impact observed.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-06T17:25:45.658-08:00", "resolved_inferred": false, "started_at": "2026-02-06T10:25:44.000-08:00", @@ -181,7 +181,7 @@ "body": "The issue that caused some pages in the DrChrono web application to not load as expected has been resolved.\n\nAll services are now functioning normally.\n\nWe appreciate your patience and understanding.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-09T07:44:34.635-08:00", "resolved_inferred": false, "started_at": "2026-01-09T06:04:41.156-08:00", @@ -194,7 +194,7 @@ "body": "We identified the issue impacting prescription transmission and worked closely with our third-party vendor, Surescripts, to investigate and resolve the problem. The issue has now been fully resolved.\n \nAt this time, prescriptions should be sending successfully without interruption. Our team will continue to actively monitor the system to ensure stability and prevent recurrence.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-05T17:24:32.221-08:00", "resolved_inferred": false, "started_at": "2026-01-05T16:28:56.054-08:00", @@ -207,7 +207,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-18T13:23:17.697-08:00", "resolved_inferred": false, "started_at": "2025-12-17T08:32:42.904-08:00", @@ -220,7 +220,7 @@ "body": "This issue has been resolved. Please contact support if you are still experiencing issues.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-18T14:08:41.787-08:00", "resolved_inferred": false, "started_at": "2025-11-18T05:47:16.000-08:00", @@ -233,7 +233,7 @@ "body": "We\u2019re seeing significant improvements across the DrChrono platform following the earlier AWS-related issues. Reports, labs, referrals, and fax processing have recovered, and overall system performance has returned to normal.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-20T16:13:45.329-07:00", "resolved_inferred": false, "started_at": "2025-10-20T09:14:15.455-07:00", diff --git a/api/v/dreamhost.json b/api/v/dreamhost.json index 28140f6ee78aa406acc5134c3720a371ac83c359..e98d89aa649055657062fe9ec8a1efcf49c26358 100644 --- a/api/v/dreamhost.json +++ b/api/v/dreamhost.json @@ -3,7 +3,7 @@ "slug": "dreamhost", "platform": "status.io", "status_url": "https://www.dreamhoststatus.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": false, "first_watched": "2026-09-04T07:06:16Z", diff --git a/api/v/drmtoday.json b/api/v/drmtoday.json index a9a2ed6e6f08c828ea27d60e99bd01c4ceed39b8..a7c502a2721bb9f637e2caa20bef82cf412f024b 100644 --- a/api/v/drmtoday.json +++ b/api/v/drmtoday.json @@ -3,7 +3,7 @@ "slug": "drmtoday", "platform": "statuspage", "status_url": "https://status.drmtoday.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "AWS has reported that the issues have been resolved. We have enabled the us-east-1 region again.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-21T07:27:32.733Z", "resolved_inferred": false, "started_at": "2025-10-20T10:06:17.006Z", diff --git a/api/v/dronedeploy.json b/api/v/dronedeploy.json index 1b23fc8613759858e396ed97c333e401c5d7fb5f..763c2c13df67cf8d29e9d9e04fb636662d3b8a6a 100644 --- a/api/v/dronedeploy.json +++ b/api/v/dronedeploy.json @@ -3,7 +3,7 @@ "slug": "dronedeploy", "platform": "statuspage", "status_url": "https://status.dronedeploy.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "Between 2026-08-24 00:51 UTC (Aug 23, 4:51 PM PT) and 2026-08-25 13:20 UTC (Aug 25, 6:20 AM PDT) some users may have experienced failures with local uploading or processing of BIM files. Engineering has corrected the issue and no further impact is expected.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-25T06:30:00.000-07:00", "resolved_inferred": false, "started_at": "2026-08-25T06:30:00.000-07:00", @@ -25,7 +25,7 @@ "body": "Between 12:41 PM PT on 08/23 and 09:21 AM PT on 08/24 (19:41 UTC on 08/23 and 16:00 AM UTCon 08/24) some users may have noted their Dock showing as offline or their dock drone being unable to launch. Engineering has corrected the issue and no further impact is expected.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-24T11:30:01.264-07:00", "resolved_inferred": false, "started_at": "2026-08-24T08:21:31.395-07:00", @@ -38,7 +38,7 @@ "body": "Between 1:45AM PDT on Aug. 7th and 1:00PM PDT on Aug. 8th (2026-08-06 08:00 UTC - 2026-08-07 18:00 UTC), some users may have experienced failures in export of Safety AI reports. Engineering has implemented a fix and does not anticipate any additional impact.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-07T14:21:24.814-07:00", "resolved_inferred": false, "started_at": "2026-08-07T09:23:34.763-07:00", @@ -51,7 +51,7 @@ "body": "Between 7:45AM and 1:20PM Pacific Time (14:45 and 20:20 UTC), some users may have experienced issues with rendering the elevation layer. Engineering has made changes to prevent further impact.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-30T15:18:39.273-07:00", "resolved_inferred": false, "started_at": "2026-07-30T12:55:43.284-07:00", @@ -64,7 +64,7 @@ "body": "Between 1:00PM and 1:40PM Pacific time (20:00 and 20:40 UTC) some users may have experienced issues loading projects in DroneDeploy, as well as latency or errors when attempting to use DroneDeploy on web or mobile. If you attempted to upload or export during this window, please try your action again.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-14T14:04:30.540-07:00", "resolved_inferred": false, "started_at": "2026-07-14T13:32:48.771-07:00", @@ -77,7 +77,7 @@ "body": "Between 9:15AM and 10:30AM Pacific Time (16:15 and 17:30 UTC) some users may have been unable to access DroneDeploy on web and mobile, due to an outage with one of our service providers. Our Engineering team implemented a patch to restore service and continued to monitor stability until the service provider issue was confirmed resolved. We expect no further impact.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-10T14:17:02.000-07:00", "resolved_inferred": false, "started_at": "2026-07-10T09:36:27.865-07:00", @@ -90,7 +90,7 @@ "body": "Between 9:00AM Pacific Time on 06/26 and 2:57PM Pacific Time on 06/29 (16:00 UTC on 6/26 and 21:57 UTC on 06/29), some users may have experienced BIM upload processing failures. Engineering has corrected the underlying issue. Please try your upload again.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-29T16:02:16.000-07:00", "resolved_inferred": false, "started_at": "2026-06-29T14:51:01.077-07:00", @@ -103,7 +103,7 @@ "body": "Between 07:00AM and 12:15PM Pacific time (14:00 and 19:15 UTC), some users may have seen errors when attempting to import or export data between DroneDeploy and Procore. The issue has been resolved, but affected users will see missing data backfill between now and Monday. We appreciate your patience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-26T12:26:36.988-07:00", "resolved_inferred": false, "started_at": "2026-06-26T10:30:49.529-07:00", @@ -116,7 +116,7 @@ "body": "Between 9:18PM on 6/21 and 6:07AM PDT on 6/22 some users may have experienced issues with the Autodesk integration not working as expected. The issue has been resolved and no further impact is expected.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-22T07:04:59.000-07:00", "resolved_inferred": false, "started_at": "2026-06-22T02:05:14.130-07:00", @@ -129,7 +129,7 @@ "body": "Between 1:07PM and 1:27PM Pacific Time (20:07 and 20:27 UTC) some users may have experienced a 500 error when attempting to access dronedeploy.com. This was due to a service issue with a third party software provider. The issue has been resolved and our team will continue to monitor to ensure ongoing stability.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-11T14:08:59.886-07:00", "resolved_inferred": false, "started_at": "2026-06-11T13:10:19.850-07:00", @@ -142,7 +142,7 @@ "body": "Between 12:00PM and 2:23PM Pacific Time (19:20 and 21:23 UTC) some users may have been unable to access the Enterprise Analytics Dashboard. Engineering has deployed a fix and confirmed the issue is resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-08T14:36:59.690-07:00", "resolved_inferred": false, "started_at": "2026-06-08T13:55:17.047-07:00", @@ -155,7 +155,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-03T23:36:00.415-07:00", "resolved_inferred": false, "started_at": "2026-06-03T16:37:51.668-07:00", @@ -168,7 +168,7 @@ "body": "Between 2:51AM and 9:02AM Pacific Time (9:51 and 16:02 UTC), some users may have experienced issues with integrations not working as expected. Engineering has corrected the issue and no further impact is expected.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-19T09:08:47.503-07:00", "resolved_inferred": false, "started_at": "2026-05-19T08:52:03.080-07:00", @@ -181,7 +181,7 @@ "body": "Between 4:40 PM Pacific Time on 05/05 and 1:20 PM Pacific Time on 05/06 (23:20 UTC on 05/05 and 20:20 UTC on 05/06), some users may have experienced issues loading elevation data, as well as related impacts to location data, annotations, exports, and reports. The underlying issue has been corrected and no further impact is expected.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-06T14:01:14.724-07:00", "resolved_inferred": false, "started_at": "2026-05-06T13:25:15.742-07:00", @@ -194,7 +194,7 @@ "body": "Between 11:00AM PT and 4:30PM PT, some users may have experienced an issue where they got an error when attempting to embed a DroneDeploy project into Procore. This issue has been resolved. Please try your embed again.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-22T16:35:00.493-07:00", "resolved_inferred": false, "started_at": "2026-04-22T16:03:39.862-07:00", @@ -207,7 +207,7 @@ "body": "Between 08:00AM Pacific on 04/14 and 12:09PM Pacific Time on 04/20 (04/14/26 15:29pm UTC and 04/20/2026 19:05pm UTC), some users may have experienced failures when attempting to upload aerial data using the desktop Smart Uploader. Engineering has rolled back the change that caused the issue and no further impact is expected. If you had a failure during this window, please try your upload again.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-20T13:35:35.656-07:00", "resolved_inferred": false, "started_at": "2026-04-20T10:36:55.930-07:00", @@ -220,7 +220,7 @@ "body": "Between April 16 and 17, some users may have experienced an issue logging in to DroneDeploy's web app via Procore or Autodesk. Engineering has resolved the underlying issue and login via these methods are now working as expected.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-17T21:14:42.847-07:00", "resolved_inferred": false, "started_at": "2026-04-17T17:14:35.518-07:00", @@ -233,7 +233,7 @@ "body": "Between 6:30AM and 4:30PM Pacific Time (14:30 and 00:00 UTC), emails sent to DroneDeploy Support may not have been received due to an outage with our third-party ticketing system provider. This issue has been fully resolved and emails sent throughout the day are backfilling into our inbox. We appreciate your understanding.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-08T16:45:42.296-07:00", "resolved_inferred": false, "started_at": "2026-04-08T10:20:09.620-07:00", @@ -246,7 +246,7 @@ "body": "Between 12:53PM Pacific on 03/30 and 12:30PM Pacific Time on 03/31 (18:53 UTC on 03/30 and 18:30 UTC on 03/31), some users may have experienced failures when attempting to upload aerial data using the desktop Smart Uploader. Engineering has rolled back the change that caused the issue and no further impact is expected. If you had a failure during this window, please try your upload again.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-31T11:48:13.903-07:00", "resolved_inferred": false, "started_at": "2026-03-31T11:19:47.217-07:00", @@ -259,7 +259,7 @@ "body": "Between 2:30am and 2:37pm Pacific Time (09:30 and 21:37 UTC), some users may have experienced an issue where Safety AI reports were not delivered. Engineering has resolved the underlying defect, and reports are now being delivered as expected. All undelivered reports will be run retroactively. There is no need to resubmit your request. Thanks for your patience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-17T14:43:23.561-07:00", "resolved_inferred": false, "started_at": "2026-03-17T10:53:44.693-07:00", @@ -272,7 +272,7 @@ "body": "Safety AI is no longer experiencing delays with report delivery. We appreciate your patience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-03T19:05:39.421-08:00", "resolved_inferred": false, "started_at": "2026-03-03T10:28:27.756-08:00", @@ -285,7 +285,7 @@ "body": "Between 1:45PM and 3:05PM Pacific Time (21:45 - 23:05 UTC), some users may have noted failure of robot service calls. Engineering has taken action to resolve the issue.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-27T13:30:00.000-08:00", "resolved_inferred": false, "started_at": "2026-02-27T13:30:00.000-08:00", @@ -298,7 +298,7 @@ "body": "Between 02/11/2026 at 1:00PM PST (21:00 UTC) and 02/13/2026 at 12:28AM PST (08:28 UTC), new Safety AI reports were not being delivered due to a partial outage with a third-party vendor. Engineering has made updates to address the issue, and all queued reports are being reprocessed. We appreciate your patience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-13T13:57:34.377-08:00", "resolved_inferred": false, "started_at": "2026-02-12T13:12:02.784-08:00", @@ -311,7 +311,7 @@ "body": "Between Wednesday, Feb. 4, 10:38 AM PST and Friday, Feb. 6,11:15 AM PST (Feb. 04, 18:38 - Feb. 06, 19:15 UTC), when users uploaded multiple standard photos at once, only one photo per level/project was saved, and the rest of the photos in that batch did not reach our servers. The issue has been resolved by our engineering team, and new uploads are now working normally.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-09T14:00:16.237-08:00", "resolved_inferred": false, "started_at": "2026-02-09T14:00:16.183-08:00", @@ -324,7 +324,7 @@ "body": "A fix has been implemented to ensure a complete refresh of all Enterprise Analytics dashboard data. Please allow several hours for the dashboard to fully refresh.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-05T18:12:50.570-08:00", "resolved_inferred": false, "started_at": "2026-02-05T11:41:14.945-08:00", @@ -337,7 +337,7 @@ "body": "Between 8:24AM and 3:45PM Pacific time (16:24 and 23:45 UTC) some users may have experienced issues loading projects in the DroneDeploy Ground App. Engineering has resolved the issue and no further impact is expected. We appreciate your patience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-16T16:57:31.575-08:00", "resolved_inferred": false, "started_at": "2026-01-16T11:07:41.048-08:00", @@ -350,7 +350,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-12T13:18:06.453-08:00", "resolved_inferred": false, "started_at": "2026-01-12T12:18:18.165-08:00", @@ -363,7 +363,7 @@ "body": "Between 4:00PM and 5:25PM PT (00:00 - 01:25 UTC) some users may have experienced export failures. All failed exports have been restarted. Please allow a couple of hours for exports to complete.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-14T17:41:31.043-08:00", "resolved_inferred": false, "started_at": "2025-12-14T17:31:00.016-08:00", @@ -376,7 +376,7 @@ "body": "Between 1:00PM PST on 12/09 and 1:00AM PST on 12/11 (21:00 UTC on 12/09 and 09:00 UTC on 12/11), some users may have had PPK map processing failures due to an outage with our third-party PPK processing partner. All failed maps are being queued for reprocessing. Please allow several hours for the backlog to clear. No action by the user is needed.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-11T09:11:25.261-08:00", "resolved_inferred": false, "started_at": "2025-12-09T17:35:08.988-08:00", @@ -389,7 +389,7 @@ "body": "On Sunday, November 30th, between 4:00pm and 8:40pm PST (12/01/2025 00:00 and 4:40 UTC), some users may have noted that flight logs were not uploaded to Dock Drones. The issue was corrected and flight log data captured during that window is being backfilled. Please allow a few hours for that data backfill to complete.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-30T20:56:44.264-08:00", "resolved_inferred": false, "started_at": "2025-11-30T19:55:02.515-08:00", @@ -402,7 +402,7 @@ "body": "Between 3:38AM and 6:30AM Pacific Time (11:38 and 14:30 UTC) some users may have experienced intermittent issues accessing a variety of DroneDeploy's apps and services due to the Global Cloudflare service incident. Cloudflare has declared the incident over and all services are confirmed stable.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-18T10:59:15.625-08:00", "resolved_inferred": false, "started_at": "2025-11-18T04:20:27.674-08:00", @@ -415,7 +415,7 @@ "body": "On Tuesday, Oct. 20th, between 3:00AM and 8:00PM PDT (10:00 - 03:00 UTC), some users may have had PPK map processing failures due to an outage with our third-party PPK processing partner. All failed maps are being queued for reprocessing. Please allow several hours for the backlog to clear. No action by the user is needed.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-21T09:15:39.337-07:00", "resolved_inferred": false, "started_at": "2025-10-20T15:01:30.166-07:00", @@ -428,7 +428,7 @@ "body": "Between 8:34AM and 3:00PM PDT (15:34 and 22:00 UTC) some users may have experienced issues loading DroneDeploy.com or contacting our Support team via live chat or phone due to the global AWS outage. All services have returned to normal. We appreciate your patience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-20T15:08:16.003-07:00", "resolved_inferred": false, "started_at": "2025-10-20T08:39:36.518-07:00", @@ -441,7 +441,7 @@ "body": "Between 2025-09-25 1:00 PM PDT and 2025-09-28 9:00 AM PDT, some users may have had PPK map processing failures due to an outage with our third-party PPK processing partner. All failed maps are being queued for reprocessing. Please allow several hours for the backlog to clear. No action by the user is needed.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-28T12:57:27.471-07:00", "resolved_inferred": false, "started_at": "2025-09-26T13:24:02.133-07:00", @@ -454,7 +454,7 @@ "body": "Between 09/22 at 7:00AM PT and 09/23 at 10:00AM PT, some users may have had PPK map processing failures due to an outage with our third-party PPK processing partner. All failed maps are being queued for reprocessing. Please allow several hours for the backlog to clear. No action by the user is needed.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-23T10:01:25.055-07:00", "resolved_inferred": false, "started_at": "2025-09-22T14:20:49.971-07:00", @@ -467,7 +467,7 @@ "body": "Between 08/29/2025 and 09/15/2025, some users may have experienced the following issues:\n- GCP tagging is sometimes not working as expected\n- GCPs (including custom grids) are converted to WGS84 when uploading\n- The default CRS when uploading GCPs is WGS84\n\nEngineering has corrected the underlying issue, and no further action is needed. We appreciate your patience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-15T15:06:30.254-07:00", "resolved_inferred": false, "started_at": "2025-09-09T12:38:47.925-07:00", @@ -480,7 +480,7 @@ "body": "Between 9:00AM PDT to 10:35 PDT (16:00 - 17:35 UTC) some users may have experienced difficulties loading the DroneDeploy web and mobile apps. Uploads, exports, and map processing may also have been affected. If you are expecting a map delivery, please allow some time and then attempt your upload again. The underlying cause has been corrected and no further impact is expected. We appreciate your patience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-01T10:55:24.485-07:00", "resolved_inferred": false, "started_at": "2025-08-01T09:33:57.571-07:00", diff --git a/api/v/dropbox.json b/api/v/dropbox.json index a26a9344ee8d9b08b1e5a7cbb2282dff5facccbe..dec790ff03454c10683922ea92a7bfc20f59ad9b 100644 --- a/api/v/dropbox.json +++ b/api/v/dropbox.json @@ -3,7 +3,7 @@ "slug": "dropbox", "platform": "statuspage", "status_url": "https://status.dropbox.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-09-04T05:02:56.500Z", "resolved_inferred": false, "started_at": "2026-09-03T22:13:35.477Z", @@ -25,7 +25,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-26T11:01:25.652Z", "resolved_inferred": false, "started_at": "2026-08-25T23:14:32.000Z", @@ -38,7 +38,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-21T15:12:53.462Z", "resolved_inferred": false, "started_at": "2026-08-21T13:18:11.184Z", @@ -51,7 +51,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-23T15:36:52.174Z", "resolved_inferred": false, "started_at": "2026-07-23T15:12:08.882Z", @@ -64,7 +64,7 @@ "body": "Shared content downloads on Dropbox is back up and running! Thanks for bearing with us.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-12T16:54:48.009Z", "resolved_inferred": false, "started_at": "2026-06-08T19:43:48.449Z", @@ -77,7 +77,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-27T22:31:57.377Z", "resolved_inferred": false, "started_at": "2026-05-27T20:05:40.641Z", @@ -90,7 +90,7 @@ "body": "A number of services across Dropbox experienced slower than expected load times between 17:01:50 and 17:42:50 UTC. \nThis included the ability to add members to teams and share content.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-18T17:00:00.000Z", "resolved_inferred": false, "started_at": "2026-05-18T17:00:00.000Z", @@ -103,7 +103,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-15T04:16:33.686Z", "resolved_inferred": false, "started_at": "2026-04-15T03:51:52.798Z", @@ -116,7 +116,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-10T00:54:51.792Z", "resolved_inferred": false, "started_at": "2026-04-09T21:32:31.738Z", @@ -129,7 +129,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-22T10:00:34.000Z", "resolved_inferred": false, "started_at": "2026-01-22T01:30:41.000Z", @@ -142,7 +142,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-15T08:19:51.813Z", "resolved_inferred": false, "started_at": "2026-01-15T06:59:52.231Z", @@ -155,7 +155,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-18T14:53:39.066Z", "resolved_inferred": false, "started_at": "2025-11-18T14:38:23.260Z", @@ -168,7 +168,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-14T21:11:24.305Z", "resolved_inferred": false, "started_at": "2025-11-14T20:00:04.549Z", @@ -181,7 +181,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-21T21:13:12.109Z", "resolved_inferred": false, "started_at": "2025-10-21T14:32:54.628Z", @@ -194,7 +194,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-14T12:49:33.333Z", "resolved_inferred": false, "started_at": "2025-10-14T09:06:38.753Z", @@ -207,7 +207,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-23T19:17:29.502Z", "resolved_inferred": false, "started_at": "2025-09-23T18:55:17.493Z", @@ -220,7 +220,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-02T13:48:54.657Z", "resolved_inferred": false, "started_at": "2025-09-02T13:16:25.560Z", @@ -233,7 +233,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-30T10:01:05.343Z", "resolved_inferred": false, "started_at": "2025-08-29T19:17:03.447Z", diff --git a/api/v/duo-security.json b/api/v/duo-security.json index 36ef9c721e61482b470ce463275ddab6dcc82b7a..879a4b1af00c0ddb4a011c1886f4989469d88a23 100644 --- a/api/v/duo-security.json +++ b/api/v/duo-security.json @@ -3,7 +3,7 @@ "slug": "duo-security", "platform": "statuspage", "status_url": "https://status.duo.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "This issue has been resolved.\n\nDuo hardware token authentication is now functioning normally on affected US deployments. Other Duo authentication methods were not expected to be impacted.\n\nThank you for your patience. If you continue to experience issues, please contact Duo Support.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-09-03T19:24:45.141-04:00", "resolved_inferred": false, "started_at": "2026-09-03T18:04:57.446-04:00", @@ -25,7 +25,7 @@ "body": "This incident has been resolved.\n\nNew Duo account registrations are now functioning normally.\n\nThank you for your patience. If you continue to experience issues, please contact Duo Support.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-10T18:46:22.161-04:00", "resolved_inferred": false, "started_at": "2026-08-10T16:34:20.644-04:00", @@ -38,7 +38,7 @@ "body": "Phone call authentication delivery for customers in the United States has returned to normal operation.\nIf customers continue to experience issues, please contact Duo Support.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-08T20:07:49.607-04:00", "resolved_inferred": false, "started_at": "2026-08-08T17:13:48.193-04:00", @@ -51,7 +51,7 @@ "body": "The SMS and VoIP delivery issue affecting users in Israel has been resolved. If customers continue to experience issues, please contact Duo Support.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-27T16:41:00.126-04:00", "resolved_inferred": false, "started_at": "2026-07-23T14:02:17.681-04:00", @@ -64,7 +64,7 @@ "body": "The third-party carrier issue affecting VoIP and SMS services in the Australia region has been resolved.\n\nPhone call and SMS authentication services are operating normally. We appreciate your patience and understanding while we addressed this issue.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-08T11:01:47.978-04:00", "resolved_inferred": false, "started_at": "2026-07-07T19:15:30.087-04:00", @@ -77,7 +77,7 @@ "body": "The SMS delivery issue affecting the UAE region has been resolved.\n\u00a0\nOur team has verified that SMS services are operating normally and full functionality has been restored. Thank you for your patience while we resolved this issue", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-23T10:21:26.315-04:00", "resolved_inferred": false, "started_at": "2026-06-22T23:58:45.000-04:00", @@ -90,7 +90,7 @@ "body": "The issue affecting AI Assistant functionality in the US-W1 region has been resolved.\n\nOur team has verified that services are operating normally, and monitoring has confirmed system stability. Thank you for your patience while we resolved this issue.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-10T11:35:32.775-04:00", "resolved_inferred": false, "started_at": "2026-06-10T10:17:36.833-04:00", @@ -103,7 +103,7 @@ "body": "The issue affecting AI Assistant functionality across all US deployments has been resolved, and full functionality has been restored. We will continue to monitor service performance to ensure stability.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-18T16:30:27.365-04:00", "resolved_inferred": false, "started_at": "2026-05-18T14:37:07.769-04:00", @@ -116,7 +116,7 @@ "body": "The issue causing authentication failures on DUO57 with the Duo Core Authentication Service is now resolved and full functionality has been restored.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-13T12:03:58.557-04:00", "resolved_inferred": false, "started_at": "2026-05-13T09:22:34.649-04:00", @@ -129,7 +129,7 @@ "body": "The issue affecting first-time access to the AI Assistant for administrators in the EU has been fully resolved, and normal functionality has been restored.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-07T18:40:14.439-04:00", "resolved_inferred": false, "started_at": "2026-05-07T10:17:04.835-04:00", @@ -142,7 +142,7 @@ "body": "The issue has been resolved. Services have returned to normal operation, and customers should no longer experience delays or failures.\nWe apologize for any inconvenience caused and thank you for your patience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-30T14:07:29.028-04:00", "resolved_inferred": false, "started_at": "2026-04-30T13:54:25.955-04:00", @@ -155,7 +155,7 @@ "body": "The issue causing elevated authentication latency has been fully resolved. Authentication performance has returned to normal levels, and customers should no longer experience delays during login attempts.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-28T11:26:01.191-04:00", "resolved_inferred": false, "started_at": "2026-04-28T10:22:52.942-04:00", @@ -168,7 +168,7 @@ "body": "The SMS delivery issue impacting customers in the US region has been resolved. SMS passcode authentication is now functioning normally.\nWe apologize for any inconvenience caused and thank you for your patience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-18T03:09:46.010-04:00", "resolved_inferred": false, "started_at": "2026-04-18T00:30:07.406-04:00", @@ -181,7 +181,7 @@ "body": "VoIP authentication has returned to normal operation with sustained success rates observed.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-22T22:23:37.639-04:00", "resolved_inferred": false, "started_at": "2026-03-22T18:13:19.684-04:00", @@ -194,7 +194,7 @@ "body": "VoIP authentication has returned to normal operation with sustained success rates observed.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-22T16:33:37.195-04:00", "resolved_inferred": false, "started_at": "2026-03-22T13:18:21.000-04:00", @@ -207,7 +207,7 @@ "body": "The service outage affecting DUO81 has been resolved. \nAll impacted customers have been successfully migrated to an alternative Duo deployment. \nThis migration has restored full service functionality for all affected users.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-03T18:46:57.479-05:00", "resolved_inferred": false, "started_at": "2026-03-02T03:30:50.898-05:00", @@ -220,7 +220,7 @@ "body": "The issue was resolved by rerouting traffic.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-01T11:39:00.559-05:00", "resolved_inferred": false, "started_at": "2026-03-01T08:29:24.094-05:00", @@ -233,7 +233,7 @@ "body": "# Summary\n\nOn\u00a0February 23, 2026, US-based\u00a0users\u00a0utilizing\u00a0the Duo integration with Azure Identity management experienced\u00a0increased authentication failures\u00a0and timeouts. These errors were occurring specifically when accessing\u00a0applications using Microsoft Entra\u00a0and Duo\u00a0as the MFA provider. Duo engineering\u00a0was alerted to the issues via monitoring\u00a0at 9:15 AM and promptly began investigating various factors that could have caused this error to occur, including checking the health of the different third-party services involved. Finally, the root cause was identified to be\u00a0increased\u00a0CPU usage\u00a0resulting from\u00a0a code change that\u00a0added\u00a0additional\u00a0validation for security operations.\n\nThe incident was remediated by scaling the\u00a0backend services that support this integration.\n\nDuring the incident, updates were posted to the status page as new information became available. At the beginning of the incident, the impact of the issue was underestimated, and thus notifications were not set to go out along with these status updates. When the impact assessment changed, notifications should have been set to go out, but this was missed. Processes have been improved to help prevent this from happening in the future.\n\n# Timeline of Events\n\n| **Time \\(in EST\\) 2/23/2026** | **Event** |\n| --- | --- |\n| 9:15 am | Engineering begins investigating\u00a0AzureAuth\u00a0errors |\n| 9:27\u00a0am\u00a0 | Duo\u00a0begins receiving reports of 504 gateway timeout errors for customers\u00a0accessing\u00a0applications using Microsoft Entra and Duo.\u00a0\u00a0 |\n| 10:02\u00a0am\u00a0\u00a0 | First\u00a0status\u00a0page from Duo is put up\u00a0regarding\u00a0investigating the root cause. This status page is posted without notifications due to\u00a0assumed\u00a0scale of\u00a0incident.\u00a0\u00a0 |\n| 11:10\u00a0am\u00a0 | Duo scales resources for the\u00a0Azureauth\u00a0US\u00a0deployment.\u00a0 |\n| 11:19\u00a0am\u00a0\u00a0 | Errors\u00a0begin to\u00a0subside.\u00a0 |\n| 11:24\u00a0am | The incident is\u00a0moved\u00a0to monitoring.\u00a0 |\n| 11:30\u00a0am\u00a0 | The incident\u00a0is\u00a0resolved.\u00a0 |\n\n# Root Cause\\(s\\)\n\nThe Duo team follows a regular and disciplined release process across all services. Changes are routinely deployed to improve functionality, security posture, and overall reliability.\n\nAll releases undergo comprehensive validation, including:\n\n* Unit testing\n* Integration testing\n* Frontend testing\n* Performance testing\n\nThis layered testing strategy is designed to identify functional defects, regressions, and performance impacts prior to production deployment.\n\nIn the days leading up to the incident, a software update was deployed to the backend service that supports the Duo integration with Azure Identity management. This update was part of a broader security improvement effort. The change successfully passed all standard validation processes and was not expected to introduce downtime or performance degradation.\n\nDuring the Monday morning traffic peak, this backend\u00a0service experienced elevated CPU utilization, resulting in service degradation. The following points all contributed to the service interruption:\n\n* **Increased CPU Utilization Per Request**\n\n * The deployed change approximately doubled CPU consumption per request within this service.\n * This materially increased overall compute demand during peak traffic.\n \n* **Performance Test Coverage Gaps**\n\n * Existing performance tests did not identify the increased CPU usage introduced by the change.\n * The specific workload characteristics that amplified CPU consumption under peak conditions were not fully represented in pre-production testing.\n \n* **Monitoring Gaps**\n\n * A recent migration of our monitoring services missed CPU monitors for this service, leading to an alerting gap when CPU consumption started trending upward.\n * Alerts were triggered only after peak load conditions were reached.\n \n\n# Remediation and Future Work\n\nTo address all the causes for the incident, Duo is committed to doing the following:\n\n* **Addressing increased CPU Utilization per Request**\n\n * **This backend service has been scaled up \\(Completed\\)**\n \n * Additional resources have been added to the infrastructure powering this backend service to provide additional compute headroom.\n * This ensures sufficient capacity to absorb higher per-request of CPU costs.\n \n * **Connection Efficiency Improvements \\(In Progress\\)**\n \n * Investigate using persistent connection pooling, and/or caching mechanism to reduce connection overhead and lower per-request for CPU consumption.\n \n * **Graceful Degradation Enhancements \\(In Progress\\)**\n \n * Improvements being explored to ensure systems degrade gracefully under high CPU load, with the goal of protecting critical authentication flows and reducing user impact during resource saturation events.\n \n \n* **Addressing Performance Testing Coverage Gaps**\n\n * **Expanded Performance Test Coverage \\(In Progress\\)**\n \n * Performance testing will be updated to explicitly model this failure scenario.\n * Peak-load and stress conditions will be more accurately simulated.\n \n * **Performance-Based Release Gates \\(In Progress\\)**\n \n * Performance tests will become release-gating criteria.\n * Changes that materially impact resource consumption will be identified before production deployment.\n \n \n* **Addressing Monitoring\u00a0Gaps**\n\n * **Capacity Monitoring\u00a0Enhancement \\(Completed\\)**\n \n * Missing capacity monitors \\(inadvertently omitted during a recent migration\\) have been restored.\n * Monitoring coverage for this service has been expanded.\n \n * **Comprehensive Monitoring Audit \\(Completed\\)**\n \n * Full audit of all capacity monitors underway to ensure complete monitoring coverage and eliminate similar gaps across services.\n \n \n* **Customer Communication Improvements**\n\n * **Improved Status Page Notifications**\n \n * Status page processes have been updated to ensure faster and clearer communication.\n * Commitment to timely, transparent, and regular updates to all customers during future incidents, with notifications.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-23T12:52:14.082-05:00", "resolved_inferred": false, "started_at": "2026-02-23T10:04:40.642-05:00", @@ -246,7 +246,7 @@ "body": "The issue causing an abnormal phone call authentication success rate has been resolved by the third-party carrier.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-23T13:20:37.122-05:00", "resolved_inferred": false, "started_at": "2026-02-23T09:02:53.920-05:00", @@ -259,7 +259,7 @@ "body": "The issue causing the AI Assistant to be unavailable for administrators in India has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-19T13:01:56.530-05:00", "resolved_inferred": false, "started_at": "2026-02-19T09:46:52.000-05:00", @@ -272,7 +272,7 @@ "body": "The deployed fix for this incident has resolved the issue. We will continue to monitor these results.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-19T17:32:33.871-05:00", "resolved_inferred": false, "started_at": "2026-02-19T09:35:48.792-05:00", @@ -285,7 +285,7 @@ "body": "The issue causing the failures for administrators access of the AI Assistant is now resolved and full functionality is restored.\n\nWe will be posting a root-cause analysis (RCA) here once our engineering team has finished its thorough investigation of the issue.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-18T20:31:11.877-05:00", "resolved_inferred": false, "started_at": "2026-02-18T13:28:00.444-05:00", @@ -298,7 +298,7 @@ "body": "# **Enrollment Timeout Outage**\n\nIncident Report \u2013 02/04/2026\n\n## Summary\n\nA recent software update Duo made related to certificate security improvements inadvertently changed the order of operations for user sessions in our legacy enrollment experience. This resulted in user sessions not being properly initialized, prompting the system to mistakenly identify these sessions as expired. Affected users were unable to complete enrollment and saw the message: \u201cYour session has expired. Please try again.\u201d The issue only affected enrollment flows using the legacy Traditional Prompt.\u00a0Customers were able to successfully enroll by switching to the Universal Prompt enrollment experience as a workaround.\n\nDuo identified and corrected the issue by ensuring sessions are fully initialized before they are used. The fix was deployed on 2026-02-04, and enrollment is now functioning normally.\n\nDuo has implemented additional safeguards to prevent similar session handling issues in future updates.\n\n## Timeline of Events\n\n**Date/Time \\(in EST\\)**\n\n02/04/2026 03:57AM\u00a0\u00a0- Duo\u00a0receives\u00a0reports that\u00a0customers are unable to complete enrollments\n\n02/04/2026\u00a009:00\u00a0AM\u00a0- Authentication team starts investigating\n\n02/04/2026 10:42 AM\u00a0- Authentication team\u00a0identifies\u00a0root cause\n\n02/04/2026 3:40 PM\u00a0- The fix begins\u00a0rolling\u00a0out to customers\n\n02/04/2026 7:26\u00a0PM\u00a0- The fix finishes rolling out to customers\n\n02/04/2026 7:26 PM\u00a0- Duo confirms that enrollments are\u00a0working as intended", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-04T20:11:56.564-05:00", "resolved_inferred": false, "started_at": "2026-02-04T13:55:37.231-05:00", @@ -311,7 +311,7 @@ "body": "The issue causing authentication failures on our DUO4 deployment has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-22T15:18:19.234-05:00", "resolved_inferred": false, "started_at": "2026-01-22T13:36:01.034-05:00", @@ -324,7 +324,7 @@ "body": "We have identified the cause of the issue for authentication failures with newly created MSP Sub-accounts on all our deployments and remediation steps have been applied to correct this. \n\nIf you continue to experience any additional issues related to this, please contact us at https://duo.com/support referencing this incident, (https://status.duo.com/incidents/tymgyq32v7dw).", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-21T18:32:48.954-05:00", "resolved_inferred": false, "started_at": "2026-01-21T16:38:23.000-05:00", @@ -337,7 +337,7 @@ "body": "According to our telephony service provider, the issue affecting SMS, Phone Call, and Push delivery has been resolved. Currently our services are now back to normal.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-15T01:16:11.525-05:00", "resolved_inferred": false, "started_at": "2026-01-14T14:35:15.147-05:00", @@ -350,7 +350,7 @@ "body": "The issue affecting call connectivity between customers and our Support Engineers has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-23T03:59:45.791-05:00", "resolved_inferred": false, "started_at": "2025-12-23T02:35:54.490-05:00", @@ -363,7 +363,7 @@ "body": "The issue affecting Duo Trial signups has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-19T16:03:06.987-05:00", "resolved_inferred": false, "started_at": "2025-12-19T12:59:32.563-05:00", @@ -376,7 +376,7 @@ "body": "The issue affecting phone-based authentication and SMS delivery has now been resolved. System performance has remained stable, and all services are operating as expected across deployments.\nWe will continue to monitor for any anomalies, but no further impact is anticipated at this time.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-20T07:06:57.553-04:00", "resolved_inferred": false, "started_at": "2025-10-20T04:28:57.666-04:00", @@ -389,7 +389,7 @@ "body": "The issue affecting email delivery has been resolved. System performance has remained stable, and all services are functioning normally across deployments.\nWe\u2019ll continue to monitor to ensure ongoing reliability. Thank you for your patience throughout this incident.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-20T07:20:52.969-04:00", "resolved_inferred": false, "started_at": "2025-10-20T03:54:46.733-04:00", @@ -402,7 +402,7 @@ "body": "We have identified an issue with a recent Windows update that has caused Duo Desktop to not be recognized on Windows 11 24H2 and 25H2 and have provided remediation steps in a Knowledge Base article linked below.\n\nWhile we work with Microsoft to ensure a permanent solution is provided via update, we will be marking this incident resolved and providing further updates through the KB article as well as via email communications.\n\nWhy is Duo Desktop not detected on my Windows device after installing updates to Windows 11?\nhttps://help.duo.com/s/article/9527\n\nPlease check the KB article for any further updates.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-15T16:01:02.605-04:00", "resolved_inferred": false, "started_at": "2025-10-15T08:19:13.850-04:00", @@ -415,7 +415,7 @@ "body": "# **DUO34 Deployment Outage**\u00a0\n\n## Incident Report \u2013 10/7/2025\u00a0\n\n### Summary\u00a0\n\nOn October 7, 2025, between 2:40pm EDT and 3:40pm EDT, all services on Duo 34 were unavailable. This was due to a misconfiguration in our edge load balancer which stopped all traffic to that deployment. Duo engineering promptly fixed the misconfiguration and have fixed the underlying cause, to ensure our systems are more resilient.\u00a0\n\n### Details\u00a0\n\nDuo\u2019s application platform has two parts to manage our services. One-part handles creating the network setup, and the other controls how traffic reaches running services. A service disruption occurred because of a misalignment between these two key systems. Even though the network was set up correctly, changes were not reflected in the traffic routing settings. This caused traffic to stop reaching the services, resulting in the outage.\u00a0\u00a0\u00a0\n\nTo restore service, a manual fix was put in place to connect these network servers with the right settings. As a long-term solution, we have updated the system settings to point to the right destinations. This will ensure that the misalignment will not happen again. To avoid this problem in the future, we're reviewing how we manage system configurations, improving our setup process to avoid local files, and adding checks to stop changes that could cause similar issues.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-07T15:56:22.869-04:00", "resolved_inferred": false, "started_at": "2025-10-07T15:13:20.610-04:00", @@ -428,7 +428,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-29T12:52:53.610-04:00", "resolved_inferred": false, "started_at": "2025-09-29T05:46:36.025-04:00", @@ -441,7 +441,7 @@ "body": "We have confirmed the issue is now fully resolved. An RCA will be provided as soon as it is available.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-26T18:41:14.108-04:00", "resolved_inferred": false, "started_at": "2025-09-26T10:54:19.979-04:00", @@ -454,7 +454,7 @@ "body": "### Summary\n\nOn September 9, 2025, between approximately 12:10 pm ET and 12:40 pm ET, some multi-tenant administrators were unable to access the admin panel or use accounts API due to a configuration change that inadvertently disrupted traffic requests. \n\nDuo engineering promptly reverted the change to restore service and resolve the issue.\n\n### Details\n\nOn September 9, Duo engineering executed a planned integration of two services related to the admin panel and billing. This integration aimed to reduce database load and address infrequent internal errors. Although the change was tested in lower environments, it was incompatible with the production region it targeted, causing issues when deployed in production.\n\nDuo engineering promptly began reverting the change to address the errors and minimize customer impact. On the same day, the team implemented a fix to resolve the configuration incompatibilities.\n\nMoving forward, Duo is enhancing our testing processes to identify incompatibilities before implementing approved changes and to reduce downtime for our customers. \n\nWe apologize for any disruption this may have caused.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-09T13:09:28.771-04:00", "resolved_inferred": false, "started_at": "2025-09-09T12:43:58.221-04:00", @@ -467,7 +467,7 @@ "body": "### Summary\n\nAn apparent defect in v136 of Chromium-based browsers \\(such as Google Chrome and Microsoft Edge\\) caused newly added code in Duo\u2019s web-based prompt, when interacting with Duo Desktop, to freeze or crash the browser tab. The issue was specific to version 136; all other versions did not exhibit the problem.\u00a0Duo has deployed a fix to ensure this behavior is not present in these versions.\n\n### Timeline of Events\n\n* 8/29/2025 1:25am EST - Duo engineering is alerted of a customer reporting the issue \n* 8/29/2025 1:22pm EST - Incident created \n* 8/29/2025 9:35pm EST - Started deploying the update to fix the issue \n* 8/29/2025 11:36pm EST - Finished deploying the update to fix the issue \n* 8/30/2025 12:07am EST - Status page is updated to monitoring \n* 8/30/2025 1:02am EST - Status page is updated to resolved \n\n### Details\n\nUpdates were added to D322 to check whether the Chrome Local Network Access permission setting was enabled in the browser being used to authenticate. The Local Network Access permission is being added to Chromium-based browsers in v141, and changes were added to improve the user experience if the Local Network Access permission is not enabled. More details can be found in [this Duo Knowledge Base article](https://help.duo.com/s/article/9470?language=en_US). In v136 of Chromium-based browsers, the change that was added to check the Local Network Access permission caused the browser to freeze or crash.\n\nTo resolve this issue, Duo added a change to not check the Chrome Local Network Access permission if v136 of a Chromium based browser is being used. Since the Chrome Local Network Access permission is being released in v141, this change did not have any negative impact.\n\nDuo will explore adding additional testing and alerting for issues like this one, where only specific browser versions are impacted by an issue.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-30T01:03:18.274-04:00", "resolved_inferred": false, "started_at": "2025-08-29T13:30:46.812-04:00", @@ -480,7 +480,7 @@ "body": "The issue affecting updates or changes made to users in the Admin Panel on selected deployments has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-26T10:58:15.158-04:00", "resolved_inferred": false, "started_at": "2025-08-26T10:43:14.476-04:00", @@ -493,7 +493,7 @@ "body": "**Summary**\n\nA change in the D322 build triggered high database load by calling an unoptimized query. This resulted in disruptions across several deployments. The system was stabilized after recovery actions.\n\n**Timeline of Events**\n\n08/26/2025 06:47:00 UTC\u00a0- Alert fires that our service latency is above target.\u00a0\n\n08/26/2025 06:58:00 UTC\u00a0- On-call engineer confirms that autoscaling is in progress.\u00a0\n\n08/26/2025 07:00:00 UTC\u00a0- Separate alert fires that our service database CPU utilization is high, and requests backlog starts to grow.\u00a0\n\n08/26/2025 07:37:00 UTC\u00a0- On-call engineer disables certain features of our service to alleviate load.\u00a0\n\n08/26/2025 08:08:00 UTC\u00a0- Status page is published.\u00a0\n\n08/26/2025 08:45:00 UTC\u00a0- Service database is scaled up.\u00a0\n\n08/26/2025 08:50:00 UTC\u00a0- On-call engineer monitors recovery of systems.\n\n08/26/2025 10:40:00 UTC\u00a0- All features of our service are reenabled.\u00a0\n\n08/26/2025 11:44:00 UTC\u00a0- Status page is updated to resolved.\u00a0\n\n**Details**\n\nOur D322 build started calling an unoptimized API endpoint on an internal system which led to high database load, latency and request timeouts. This degraded multiple deployments \\(DUO3, DUO47, DUO57\\).\n\n\u200c\n\nTo alleviate load,\u00a0certain features were\u00a0disabled temporarily. However, because Duo Directory depends on this feature, customers received errors until it was re-enabled. At the same time, the database was scaled up vertically to allow for quicker processing of backlogged requests.\n\n\u200c\n\nOnce the backlog was cleared, all features were reenabled and the incident was resolved.\n\n\u200c\n\nDeep analysis was conducted to determine why the service database CPU utilization was higher than expected. A newly introduced unoptimized query was found and fixed promptly.\n\n\u200c\n\nFurthermore, our teams have plans to implement more rigorous testing and review processes for new database queries that are added to our services.\n\n\u200c\n\nAlso, our teams will work to improve our performance testing capabilities in the development environment to allow more accurate simulation of production load. This will aid us in being able to better detect unoptimized queries before they are released.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-26T07:43:56.719-04:00", "resolved_inferred": false, "started_at": "2025-08-26T04:08:34.011-04:00", @@ -506,7 +506,7 @@ "body": "Duo has confirmed that the issue affecting SMS delivery to phone numbers using T-Mobile services in the US has been fully resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-26T06:21:54.554-04:00", "resolved_inferred": false, "started_at": "2025-08-26T02:29:19.196-04:00", @@ -519,7 +519,7 @@ "body": "Duo has confirmed that the phone call authentication failures affecting all deployments in India have been fully resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-18T11:27:48.356-04:00", "resolved_inferred": false, "started_at": "2025-08-18T07:25:26.804-04:00", @@ -532,7 +532,7 @@ "body": "The issue affecting SMS delivery to US phone numbers has been resolved. Services are now fully operational.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-06T04:06:15.555-04:00", "resolved_inferred": false, "started_at": "2025-08-06T00:40:18.931-04:00", @@ -545,7 +545,7 @@ "body": "The issue causing login failures when attempting to access the Duo Admin Panel on the DUO41 deployment has been fully resolved and full functionality is restored.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-05T20:26:46.411-04:00", "resolved_inferred": false, "started_at": "2025-08-05T20:03:55.174-04:00", @@ -558,7 +558,7 @@ "body": "The issue with AI Assistant failures in all US deployments is now resolved and full functionality is restored.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-07-31T23:27:19.225-04:00", "resolved_inferred": false, "started_at": "2025-07-31T20:16:54.754-04:00", diff --git a/api/v/dynatrace.json b/api/v/dynatrace.json index a07843c44b5ec26f62446c22f3528254d92eb5f8..02f19fe14a9a3fcea3bda4dc5d93662e40957c1e 100644 --- a/api/v/dynatrace.json +++ b/api/v/dynatrace.json @@ -3,7 +3,7 @@ "slug": "dynatrace", "platform": "status.io", "status_url": "https://dynatrace.status.io", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": false, "first_watched": "2026-09-04T07:06:16Z", diff --git a/api/v/easypost.json b/api/v/easypost.json index 9679697f3834f5e5a929f0c10c341eceb9ed1732..148cd0c26a2ca1a5a1b66ca0046e66cc1810fc49 100644 --- a/api/v/easypost.json +++ b/api/v/easypost.json @@ -3,7 +3,7 @@ "slug": "easypost", "platform": "statuspage", "status_url": "https://www.easypoststatus.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "All systems have returned to normal and APIs are fully functional again.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-27T10:40:59.647-07:00", "resolved_inferred": false, "started_at": "2026-08-27T10:26:08.630-07:00", @@ -25,7 +25,7 @@ "body": "This incident is resolved. EasyPost services are fully operational. Any data delayed during the incident has been processed.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-23T15:26:00.479-07:00", "resolved_inferred": false, "started_at": "2026-07-23T07:57:52.000-07:00", @@ -38,7 +38,7 @@ "body": "UPS DAP operations have fully recovered. Customers using EasyPost-provided UPS (DAP) accounts can once again request UPS rates and create UPS shipments without issue. UPS BYOA accounts and other carriers operated normally. We appreciate your patience while we worked with UPS to resolve this issue.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-22T17:36:01.231-07:00", "resolved_inferred": false, "started_at": "2026-07-22T14:07:12.737-07:00", @@ -51,7 +51,7 @@ "body": "All API operations have returned to normal.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-09T11:28:20.085-07:00", "resolved_inferred": false, "started_at": "2026-07-09T11:18:48.881-07:00", @@ -64,7 +64,7 @@ "body": "UPS operations have returned to normal.\u00a0 Some impacted customers may need to re-authenticate their BYOA accounts. See https://support.easypost.com/hc/en-us/articles/26635027512717-UPS-OAuth-2-0-Update#:~:text=Account%20Authorization for more details.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-08T17:43:40.113-07:00", "resolved_inferred": false, "started_at": "2026-07-08T13:38:47.639-07:00", @@ -77,7 +77,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-26T14:16:15.382-07:00", "resolved_inferred": false, "started_at": "2026-06-26T09:32:17.517-07:00", @@ -90,7 +90,7 @@ "body": "We had a brief outage of USPS shipment buys.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-24T03:39:19.672-07:00", "resolved_inferred": false, "started_at": "2026-06-24T03:39:19.610-07:00", @@ -103,7 +103,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-11T13:57:02.983-07:00", "resolved_inferred": false, "started_at": "2026-06-11T10:00:03.187-07:00", @@ -116,7 +116,7 @@ "body": "Gori API timings have returned to baseline and the service is operating normally again.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-05T11:29:25.129-07:00", "resolved_inferred": false, "started_at": "2026-06-05T10:46:50.017-07:00", @@ -129,7 +129,7 @@ "body": "Service remains stable. This issue is resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-05T08:16:03.153-07:00", "resolved_inferred": false, "started_at": "2026-06-05T07:37:27.965-07:00", @@ -142,7 +142,7 @@ "body": "Service has continued to operate normally. This incident is resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-03T11:46:45.989-07:00", "resolved_inferred": false, "started_at": "2026-06-03T10:28:23.429-07:00", @@ -155,7 +155,7 @@ "body": "We identified and resolved the issue. The website is fully operational again", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-02T16:16:02.580-07:00", "resolved_inferred": false, "started_at": "2026-06-02T16:09:45.892-07:00", @@ -168,7 +168,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-27T15:47:19.763-07:00", "resolved_inferred": false, "started_at": "2026-05-27T14:18:33.587-07:00", @@ -181,7 +181,7 @@ "body": "Service remains stable and back to normal operation.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-22T12:02:37.230-07:00", "resolved_inferred": false, "started_at": "2026-05-22T11:49:09.710-07:00", @@ -194,7 +194,7 @@ "body": "This incident has been resolved. Canada Post wallet accounts are operating normally.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-22T15:36:38.175-07:00", "resolved_inferred": false, "started_at": "2026-05-21T18:18:41.135-07:00", @@ -207,7 +207,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-19T12:31:44.693-07:00", "resolved_inferred": false, "started_at": "2026-05-19T11:49:12.394-07:00", @@ -220,7 +220,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-11T09:59:19.770-07:00", "resolved_inferred": false, "started_at": "2026-05-11T09:26:19.973-07:00", @@ -233,7 +233,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-28T08:57:41.285-07:00", "resolved_inferred": false, "started_at": "2026-04-28T04:13:19.960-07:00", @@ -246,7 +246,7 @@ "body": "This incident has been resolved; users are once again able to link their bank accounts.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-03T13:46:54.152-07:00", "resolved_inferred": false, "started_at": "2026-04-03T11:01:47.895-07:00", @@ -259,7 +259,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-16T15:34:50.635-07:00", "resolved_inferred": false, "started_at": "2026-03-16T12:28:29.609-07:00", @@ -272,7 +272,7 @@ "body": "Purolator reports that all services have been restored.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-13T17:48:09.443-07:00", "resolved_inferred": false, "started_at": "2026-03-13T13:43:20.576-07:00", @@ -285,7 +285,7 @@ "body": "At this time, errors have ceased and the Tracking service has returned to normal.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-13T11:38:53.674-07:00", "resolved_inferred": false, "started_at": "2026-03-13T10:44:38.368-07:00", @@ -298,7 +298,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-27T11:56:33.336-08:00", "resolved_inferred": false, "started_at": "2026-02-27T08:34:31.420-08:00", @@ -311,7 +311,7 @@ "body": "FedEx carrier API performance has returned to normal.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-29T09:58:28.810-08:00", "resolved_inferred": false, "started_at": "2026-01-29T07:05:32.186-08:00", @@ -324,7 +324,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-24T10:26:43.041-08:00", "resolved_inferred": false, "started_at": "2025-12-23T15:11:58.671-08:00", @@ -337,7 +337,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-17T08:02:50.644-08:00", "resolved_inferred": false, "started_at": "2025-12-11T10:48:23.385-08:00", @@ -350,7 +350,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-10T09:06:11.784-08:00", "resolved_inferred": false, "started_at": "2025-12-10T08:57:09.027-08:00", @@ -363,7 +363,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-02T13:19:54.668-08:00", "resolved_inferred": false, "started_at": "2025-12-02T08:06:08.815-08:00", @@ -376,7 +376,7 @@ "body": "Service is again stable, with corrections made to prevent recurrence.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-01T12:59:39.392-08:00", "resolved_inferred": false, "started_at": "2025-12-01T10:54:47.946-08:00", @@ -389,7 +389,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-29T07:06:21.409-08:00", "resolved_inferred": false, "started_at": "2025-11-28T09:30:41.873-08:00", @@ -402,7 +402,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-22T07:24:33.597-08:00", "resolved_inferred": false, "started_at": "2025-11-21T20:25:49.597-08:00", @@ -415,7 +415,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-13T23:19:40.684-08:00", "resolved_inferred": false, "started_at": "2025-11-13T14:39:08.863-08:00", @@ -428,7 +428,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-12T11:41:34.703-08:00", "resolved_inferred": false, "started_at": "2025-11-12T08:26:03.422-08:00", @@ -441,7 +441,7 @@ "body": "This incident has been resolved", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-05T12:13:23.885-08:00", "resolved_inferred": false, "started_at": "2025-11-05T09:59:32.733-08:00", @@ -454,7 +454,7 @@ "body": "FedEx API has returned to normal error rates and response times.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-27T13:55:33.078-07:00", "resolved_inferred": false, "started_at": "2025-10-27T09:18:20.955-07:00", @@ -467,7 +467,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-05T07:54:49.481-07:00", "resolved_inferred": false, "started_at": "2025-10-05T06:09:22.676-07:00", @@ -480,7 +480,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-21T07:41:39.915-07:00", "resolved_inferred": false, "started_at": "2025-09-20T21:48:53.963-07:00", @@ -493,7 +493,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-20T13:32:55.716-07:00", "resolved_inferred": false, "started_at": "2025-09-20T12:40:46.576-07:00", @@ -506,7 +506,7 @@ "body": "FedEx API has remained stable and error rates have been at normal levels for over an hour. Incident appears to be resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-25T07:51:18.644-07:00", "resolved_inferred": false, "started_at": "2025-08-25T06:28:25.588-07:00", diff --git a/api/v/easyredir.json b/api/v/easyredir.json index 35cf1af0dbf230e5494753c9f47a0f15088b4f99..540fc3e5481c9cb3274ee5a49e19d51738ec6e4f 100644 --- a/api/v/easyredir.json +++ b/api/v/easyredir.json @@ -3,7 +3,7 @@ "slug": "easyredir", "platform": "statuspage", "status_url": "https://status.easyredir.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "All prior analytics data is now available in the urllo dashboard. This issue is now resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-18T13:11:39.752-07:00", "resolved_inferred": false, "started_at": "2025-12-17T18:48:18.157-07:00", @@ -25,7 +25,7 @@ "body": "Increased latency on redirects has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-29T10:10:35.661-06:00", "resolved_inferred": false, "started_at": "2025-08-28T12:04:39.729-06:00", @@ -38,7 +38,7 @@ "body": "Tail latencies on redirects have returned to normal levels.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-27T11:05:56.904-06:00", "resolved_inferred": false, "started_at": "2025-08-25T16:24:48.994-06:00", @@ -51,7 +51,7 @@ "body": "The brief increases in latency affecting some redirects have been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-15T10:06:17.633-06:00", "resolved_inferred": false, "started_at": "2025-08-11T12:48:01.097-06:00", @@ -64,7 +64,7 @@ "body": "A network-related issue with urllo\u2019s redirector may have caused some customers to experience increased latency for a short period of time. Services are back to normal and the issue is resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-10T14:00:00.000-06:00", "resolved_inferred": false, "started_at": "2025-08-10T14:00:00.000-06:00", diff --git a/api/v/ecostruxure-it.json b/api/v/ecostruxure-it.json index 6a17292a681271e29c82277e1e46689b17ed9993..44f099b0128c0021be61a6a012583362eba20021 100644 --- a/api/v/ecostruxure-it.json +++ b/api/v/ecostruxure-it.json @@ -3,7 +3,7 @@ "slug": "ecostruxure-it", "platform": "statuspage", "status_url": "https://status.ecostruxureit.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-29T19:09:20.862Z", "resolved_inferred": false, "started_at": "2026-06-29T18:14:55.397Z", @@ -25,7 +25,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-17T12:54:33.883Z", "resolved_inferred": false, "started_at": "2026-06-17T10:12:23.920Z", @@ -38,7 +38,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-16T17:36:42.130Z", "resolved_inferred": false, "started_at": "2026-06-16T11:21:53.781Z", @@ -51,7 +51,7 @@ "body": "The issue affecting SMS-based two-factor authentication (2FA) has now been resolved.\n\nUsers who were previously unable to log in using SMS as their 2FA method should now be able to access EcoStruxure IT Expert normally.\n\nThank you for your patience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-18T16:34:17.077Z", "resolved_inferred": false, "started_at": "2026-05-18T13:36:25.872Z", @@ -64,7 +64,7 @@ "body": "This incident has been resolved.\n\nDue to a data migration effort, 1 hour and 51 minutes of data are missing from EcoStruxure IT Expert and EcoStruxure Asset Advisor.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-08T10:15:23.000Z", "resolved_inferred": false, "started_at": "2026-04-08T07:55:56.606Z", @@ -77,7 +77,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-18T15:47:35.979Z", "resolved_inferred": false, "started_at": "2025-11-18T14:24:24.605Z", @@ -90,7 +90,7 @@ "body": "We have identified an issue with our mobile app push notifications.\nThe issue caused push notifications on mobile devices to be unavailable. That includes 2FA & alarm push notification", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-20T08:00:00.000Z", "resolved_inferred": false, "started_at": "2025-10-20T08:00:00.000Z", diff --git a/api/v/egnyte.json b/api/v/egnyte.json index cfae145168788c5fcac947de37cadc18f71360b6..22f8eddcfc112499b03e700667b2b4cf4f697ef5 100644 --- a/api/v/egnyte.json +++ b/api/v/egnyte.json @@ -3,7 +3,7 @@ "slug": "egnyte", "platform": "statuspage", "status_url": "https://status.egnyte.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "Our team confirmed that everything should be back to normal now. If you continue to experience any issues, please reach out to our support team for further assistance. We apologize for any inconvenience this may have caused and appreciate your patience during this time.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-09-03T10:37:15.638Z", "resolved_inferred": false, "started_at": "2026-09-03T10:06:28.875Z", @@ -25,7 +25,7 @@ "body": "Our team confirmed that everything should be back to normal now. If you continue to experience any issues, please reach out to our support team for further assistance. We apologize for any inconvenience this may have caused and appreciate your patience during this time.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-18T09:31:14.546Z", "resolved_inferred": false, "started_at": "2026-07-18T08:44:30.674Z", @@ -38,7 +38,7 @@ "body": "Our team confirmed that everything should be back to normal now. If you continue to experience any issues, please reach out to our support team for further assistance. We apologize for any inconvenience this may have caused and appreciate your patience during this time.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-16T14:50:46.332Z", "resolved_inferred": false, "started_at": "2026-06-16T13:38:37.419Z", @@ -51,7 +51,7 @@ "body": "Our team confirmed that everything should be back to normal now. If you continue to experience any issues, please reach out to our support team for further assistance. We apologize for any inconvenience this may have caused and appreciate your patience during this time.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-09T12:26:03.584Z", "resolved_inferred": false, "started_at": "2026-06-09T11:59:29.674Z", @@ -64,7 +64,7 @@ "body": "Our team confirmed that everything should be back to normal now. If you continue to experience any issues, please reach out to our support team for further assistance. We apologize for any inconvenience this may have caused and appreciate your patience during this time.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-01T14:02:12.504Z", "resolved_inferred": false, "started_at": "2026-06-01T12:35:21.357Z", @@ -77,7 +77,7 @@ "body": "Our team has confirmed that the authentication issue affecting SSO users on the Desktop App has been fully resolved. If you continue to experience any issues, please reach out to our support team for further assistance. We apologize for any inconvenience this may have caused and appreciate your patience during this time.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-13T21:36:33.326Z", "resolved_inferred": false, "started_at": "2026-05-13T21:15:44.000Z", @@ -90,7 +90,7 @@ "body": "Our team confirmed that everything should be back to normal now. If you continue to experience any issues, please reach out to our support team for further assistance. We apologize for any inconvenience this may have caused and appreciate your patience during this time.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-06T09:39:19.989Z", "resolved_inferred": false, "started_at": "2026-05-06T08:01:13.867Z", @@ -103,7 +103,7 @@ "body": "Our team confirmed that everything should be back to normal now. If you continue to experience any issues, please reach out to our support team for further assistance. We apologize for any inconvenience this may have caused and appreciate your patience during this time.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-04T15:22:34.426Z", "resolved_inferred": false, "started_at": "2026-05-04T13:16:57.115Z", @@ -116,7 +116,7 @@ "body": "Our team confirmed that everything should be back to normal now. If you continue to experience any issues, please reach out to our support team for further assistance. We apologize for any inconvenience this may have caused and appreciate your patience during this time.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-29T16:43:43.874Z", "resolved_inferred": false, "started_at": "2026-04-29T15:53:25.551Z", @@ -129,7 +129,7 @@ "body": "Our team confirmed that everything should be back to normal now. If you continue to experience any issues, please reach out to our support team for further assistance. We apologize for any inconvenience this may have caused and appreciate your patience during this time.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-29T15:45:46.367Z", "resolved_inferred": false, "started_at": "2026-04-29T14:15:58.120Z", @@ -142,7 +142,7 @@ "body": "Our team confirmed that everything should be back to normal now. If you continue to experience any issues, please reach out to our support team for further assistance. We apologize for any inconvenience this may have caused and appreciate your patience during this time.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-14T23:40:12.518Z", "resolved_inferred": false, "started_at": "2026-04-14T22:29:49.182Z", @@ -155,7 +155,7 @@ "body": "Our team confirmed that everything should be back to normal now. If you continue to experience any issues, please reach out to our support team for further assistance. We apologize for any inconvenience this may have caused and appreciate your patience during this time.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-08T09:36:41.244Z", "resolved_inferred": false, "started_at": "2026-04-07T22:31:37.516Z", @@ -168,7 +168,7 @@ "body": "The vendor-side issue has not yet been resolved; however, remediation plans have been provided to all impacted customers.\nWe apologize for any inconvenience and thank you for your patience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-19T16:13:28.277Z", "resolved_inferred": false, "started_at": "2026-03-16T16:43:26.227Z", @@ -181,7 +181,7 @@ "body": "Our team confirmed that everything should be back to normal now. If you continue to experience any issues, please reach out to our support team for further assistance. We apologize for any inconvenience this may have caused and appreciate your patience during this time.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-11T18:25:10.315Z", "resolved_inferred": false, "started_at": "2026-03-11T17:42:05.000Z", @@ -194,7 +194,7 @@ "body": "Our team confirmed that everything should be back to normal now. If you continue to experience any issues, please reach out to our support team for further assistance. We apologize for any inconvenience this may have caused and appreciate your patience during this time.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-25T20:44:37.735Z", "resolved_inferred": false, "started_at": "2026-02-25T19:44:54.441Z", @@ -207,7 +207,7 @@ "body": "Our team confirmed that everything should be back to normal now. If you continue to experience any issues, please reach out to our support team for further assistance. We apologize for any inconvenience this may have caused and appreciate your patience during this time.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-11T21:53:27.434Z", "resolved_inferred": false, "started_at": "2026-02-11T20:34:24.000Z", @@ -220,7 +220,7 @@ "body": "Our team confirmed that everything should be back to normal now. If you continue to experience any issues, please reach out to our support team for further assistance. We apologize for any inconvenience this may have caused and appreciate your patience during this time.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-04T21:47:53.005Z", "resolved_inferred": false, "started_at": "2026-02-04T20:42:24.910Z", @@ -233,7 +233,7 @@ "body": "Our team confirmed that everything should be back to normal now. If you continue to experience any issues, please reach out to our support team for further assistance. We apologize for any inconvenience this may have caused and appreciate your patience during this time.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-03T10:20:10.009Z", "resolved_inferred": false, "started_at": "2026-02-03T07:29:12.277Z", @@ -246,7 +246,7 @@ "body": "Our team confirmed that everything should be back to normal now. If you continue to experience any issues, please reach out to our support team for further assistance. We apologize for any inconvenience this may have caused and appreciate your patience during this time.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-31T07:17:31.378Z", "resolved_inferred": false, "started_at": "2026-01-31T06:31:01.192Z", @@ -259,7 +259,7 @@ "body": "Our team confirmed that everything should be back to normal now. If you continue to experience any issues, please reach out to our support team for further assistance. We apologize for any inconvenience this may have caused and appreciate your patience during this time.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-29T22:03:17.106Z", "resolved_inferred": false, "started_at": "2026-01-29T21:19:06.529Z", @@ -272,7 +272,7 @@ "body": "Our team confirmed that everything should be back to normal now. If you continue to experience any issues, please reach out to our support team for further assistance. We apologize for any inconvenience this may have caused and appreciate your patience during this time.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-21T15:28:58.793Z", "resolved_inferred": false, "started_at": "2026-01-21T15:04:34.763Z", @@ -285,7 +285,7 @@ "body": "Our team confirmed that everything should be back to normal now. If you continue to experience any issues, please reach out to our support team for further assistance. We apologize for any inconvenience this may have caused and appreciate your patience during this time.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-09T18:59:06.498Z", "resolved_inferred": false, "started_at": "2025-12-09T18:16:42.085Z", @@ -298,7 +298,7 @@ "body": "Our team confirmed that everything should be back to normal now. If you continue to experience any issues, please reach out to our support team for further assistance. We apologize for any inconvenience this may have caused and appreciate your patience during this time.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-09T06:32:14.290Z", "resolved_inferred": false, "started_at": "2025-12-09T01:19:22.524Z", @@ -311,7 +311,7 @@ "body": "Our team confirmed that everything should be back to normal now. If you continue to experience any issues, please reach out to our support team for further assistance. We apologize for any inconvenience this may have caused and appreciate your patience during this time.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-02T03:22:27.273Z", "resolved_inferred": false, "started_at": "2025-12-02T02:31:06.236Z", @@ -324,7 +324,7 @@ "body": "Our team confirmed that everything should be back to normal now. If you continue to experience any issues, please reach out to our support team for further assistance. We apologize for any inconvenience this may have caused and appreciate your patience during this time.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-22T14:42:43.956Z", "resolved_inferred": false, "started_at": "2025-10-22T14:07:52.622Z", @@ -337,7 +337,7 @@ "body": "Our team confirmed that everything should be back to normal now. If you continue to experience any issues, please reach out to our support team for further assistance. We apologize for any inconvenience this may have caused and appreciate your patience during this time.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-13T15:51:47.031Z", "resolved_inferred": false, "started_at": "2025-10-13T13:54:23.151Z", @@ -350,7 +350,7 @@ "body": "Our team confirmed that everything should be back to normal now. If you continue to experience any issues, please reach out to our support team for further assistance. We apologize for any inconvenience this may have caused and appreciate your patience during this time.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-18T20:07:26.695Z", "resolved_inferred": false, "started_at": "2025-09-18T19:47:16.175Z", @@ -363,7 +363,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-13T07:32:02.669Z", "resolved_inferred": false, "started_at": "2025-09-13T07:08:48.248Z", @@ -376,7 +376,7 @@ "body": "Our team confirmed that everything should be back to normal now. If you continue to experience any issues, please reach out to our support team for further assistance. We apologize for any inconvenience this may have caused and appreciate your patience during this time.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-04T16:57:10.996Z", "resolved_inferred": false, "started_at": "2025-09-04T15:58:36.000Z", @@ -389,7 +389,7 @@ "body": "Our team confirmed that everything should be back to normal now. If you continue to experience any issues, please reach out to our support team for further assistance. We apologize for any inconvenience this may have caused and appreciate your patience during this time.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-15T01:44:55.382Z", "resolved_inferred": false, "started_at": "2025-08-14T18:23:52.835Z", @@ -402,7 +402,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-08T17:54:10.124Z", "resolved_inferred": false, "started_at": "2025-08-08T17:14:29.000Z", @@ -415,7 +415,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-04T22:44:26.109Z", "resolved_inferred": false, "started_at": "2025-08-04T19:09:19.397Z", diff --git a/api/v/elastic.json b/api/v/elastic.json index cafe8541e606ad1bad34b3c59fadad5d78904304..de1550a4856c4bf917bc7bcd0e80e1574d67ec69 100644 --- a/api/v/elastic.json +++ b/api/v/elastic.json @@ -3,7 +3,7 @@ "slug": "elastic", "platform": "statuspage", "status_url": "https://status.elastic.co", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "partial", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "From 21:50 to 23:42 UTC, we encountered elevated error rates for Anthropic Claude Haiku 4.5, OpenAI GPT-5.6, and Google Gemini 2.5 Flash with the Elastic Inference Service in EU regions. This issue has now been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-09-02T00:04:57.959Z", "resolved_inferred": false, "started_at": "2026-09-02T00:04:57.903Z", @@ -25,7 +25,7 @@ "body": "This issue has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-09-01T20:05:48.162Z", "resolved_inferred": false, "started_at": "2026-09-01T15:18:03.380Z", @@ -38,7 +38,7 @@ "body": "Elasticsearch 9.5.3 has been released and all customers currently running 9.5.0, 9.5.1 or 9.5.2 are advised to update to this new version as soon as possible.\n\nImpacted customers are advised to follow the workaround steps from https://github.com/elastic/elasticsearch/issues/158212 after the upgrade.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "started_at": "2026-09-01T08:16:01.011Z", "state": "monitoring", "title": "Replication bug causing slow recoveries", @@ -49,7 +49,7 @@ "body": "This is now resolved", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-27T18:33:51.562Z", "resolved_inferred": false, "started_at": "2026-08-27T17:11:28.177Z", @@ -62,7 +62,7 @@ "body": "This incident has been resolved. The root cause has been identified and addressed. Customer workloads were not impacted during this incident.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-20T22:13:34.066Z", "resolved_inferred": false, "started_at": "2026-08-20T20:22:56.039Z", @@ -75,7 +75,7 @@ "body": "Azure's storage component issues in the eastus region have been resolved. Consequently, Serverless project creation times have returned to normal and are functioning as expected.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-20T16:22:32.492Z", "resolved_inferred": false, "started_at": "2026-08-20T12:48:02.267Z", @@ -88,7 +88,7 @@ "body": "Elasticsearch 9.5.2 has been released and contains the fix for this issue. Customers running 9.5.0 or 9.5.1 should upgrade to 9.5.2. At this time we are considering this issue resolved and will be providing no further updates.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-20T17:09:48.527Z", "resolved_inferred": false, "started_at": "2026-08-14T09:22:03.979Z", @@ -101,7 +101,7 @@ "body": "The microsoft-multilingual-e5-large model has been retired from the Elastic Inference Service. Requests to this model now return an error.\n\nCustomers who wish to use this model with Elastic cloud must create a custom inference endpoint using their own API key. See our inference documentation for further details: https://www.elastic.co/docs/api/doc/elasticsearch/group/endpoint-inference", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-17T11:40:59.675Z", "resolved_inferred": false, "started_at": "2026-08-13T08:32:50.464Z", @@ -114,7 +114,7 @@ "body": "We've resolved the issue affecting Serverless project creation and modifications. All systems are now operating normally.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-13T08:40:40.934Z", "resolved_inferred": false, "started_at": "2026-08-13T03:57:56.259Z", @@ -127,7 +127,7 @@ "body": "On 2026-08-06 between 0900 - 1200 UTC, customers in GCP asia-south1 may have experienced high latency when communicating with their Elasticsearch deployments during this window. The cause has been identified and mitigated.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-06T17:41:39.699Z", "resolved_inferred": false, "started_at": "2026-08-06T17:41:39.595Z", @@ -140,7 +140,7 @@ "body": "Elasticsearch 9.5.1 has been released and contains the fix for this issue. Customers running 9.5.0 should upgrade to 9.5.1. At this time we are considering this issue resolved and will be providing no further updates.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-12T08:59:15.843Z", "resolved_inferred": false, "started_at": "2026-08-05T22:59:15.267Z", @@ -153,7 +153,7 @@ "body": "All metering errors have been corrected. We will be issuing refunds to the small number of affected customers.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-22T23:14:33.351Z", "resolved_inferred": false, "started_at": "2026-07-21T14:24:05.759Z", @@ -166,7 +166,7 @@ "body": "This incident was resolved on Jul 20 14:00 UTC, and was posted retroactively.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-21T14:21:17.860Z", "resolved_inferred": false, "started_at": "2026-07-21T13:45:49.344Z", @@ -179,7 +179,7 @@ "body": "Delivery delays have been resolved, MFA email delivery is fully functional for all customers.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-23T16:37:31.944Z", "resolved_inferred": false, "started_at": "2026-07-21T09:36:40.303Z", @@ -192,7 +192,7 @@ "body": "Resolved \u2013 This incident is resolved. Between Jul 18 02:40 UTC and Jul 20 14:00 UTC, a subset of Elastic Agents were unable to report metrics to AutoOps across all regions. The underlying issue has been corrected and data is flowing normally. Impacted deployments may notice some gaps in their AutoOps monitoring data during this timeframe.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-18T02:45:00.000Z", "resolved_inferred": false, "started_at": "2026-07-18T00:30:00.000Z", @@ -205,7 +205,7 @@ "body": "This incident has been resolved", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-15T01:12:36.729Z", "resolved_inferred": false, "started_at": "2026-07-15T00:15:42.981Z", @@ -218,7 +218,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-13T12:19:15.905Z", "resolved_inferred": false, "started_at": "2026-07-13T12:15:22.822Z", @@ -231,7 +231,7 @@ "body": "The incident impacting a subset of customers with EIS in EMEA regions has been resolved. Services have been fully restored and the team has confirmed stability.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-02T03:00:07.544Z", "resolved_inferred": false, "started_at": "2026-07-02T00:54:12.620Z", @@ -244,7 +244,7 @@ "body": "The issue affecting EIS for Elastic Cloud customers with projects or deployments on GCP and Azure in EMEA regions has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-01T23:05:06.560Z", "resolved_inferred": false, "started_at": "2026-07-01T22:43:53.139Z", @@ -257,7 +257,7 @@ "body": "This issue has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-01T20:23:14.680Z", "resolved_inferred": false, "started_at": "2026-07-01T15:39:15.671Z", @@ -270,7 +270,7 @@ "body": "This issue has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-29T16:58:55.667Z", "resolved_inferred": false, "started_at": "2026-06-29T16:32:48.264Z", @@ -283,7 +283,7 @@ "body": "This issue has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-17T17:35:11.249Z", "resolved_inferred": false, "started_at": "2026-06-17T15:52:19.068Z", @@ -296,7 +296,7 @@ "body": "This issue is resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-17T00:59:24.525Z", "resolved_inferred": false, "started_at": "2026-06-16T22:54:27.476Z", @@ -309,7 +309,7 @@ "body": "We have identified the root cause and mitigated the issue. Users should now be able to log in to Kibana via the \"Log in with Elastic Cloud\" button.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-16T11:36:48.320Z", "resolved_inferred": false, "started_at": "2026-06-16T10:57:53.416Z", @@ -322,7 +322,7 @@ "body": "This issue has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-15T19:13:35.803Z", "resolved_inferred": false, "started_at": "2026-06-15T17:31:17.474Z", @@ -335,7 +335,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-04T09:20:24.724Z", "resolved_inferred": false, "started_at": "2026-06-04T01:51:36.029Z", @@ -348,7 +348,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-02T19:50:34.752Z", "resolved_inferred": false, "started_at": "2026-06-02T13:25:26.662Z", @@ -361,7 +361,7 @@ "body": "This issue has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-29T18:36:33.684Z", "resolved_inferred": false, "started_at": "2026-05-29T18:00:34.620Z", @@ -374,7 +374,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-31T21:33:25.989Z", "resolved_inferred": false, "started_at": "2026-05-29T06:32:00.000Z", @@ -387,7 +387,7 @@ "body": "Some users experienced missing metrics visualizations in the Cloud console due to a disruption in metric data ingestion affecting deployments in the Azure Southeast Asia region. We have already stabilized the situation.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-26T21:35:35.341Z", "resolved_inferred": false, "started_at": "2026-05-26T21:35:35.215Z", @@ -400,7 +400,7 @@ "body": "The system has recovered and functionality has returned to normal.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-23T22:26:10.126Z", "resolved_inferred": false, "started_at": "2026-05-23T21:42:03.892Z", @@ -413,7 +413,7 @@ "body": "Synthetics browser monitors running in Europe-Germany region (GCP europe-west3) for some of the users were experiencing delayed executions results and some of them being stopped. The issue affected both Elastic Cloud Hosted and Elastic Cloud Serverless in that region and other regions were not impacted.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-22T04:54:28.081Z", "resolved_inferred": false, "started_at": "2026-05-22T04:54:28.004Z", @@ -426,7 +426,7 @@ "body": "The permanent resolution has been implemented, thus concluding our resolution actions. This incident is resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-27T13:06:56.185Z", "resolved_inferred": false, "started_at": "2026-05-20T15:29:57.178Z", @@ -439,7 +439,7 @@ "body": "We have confirmed no further impact from this incident, and are now considering this issue resolved. Thank you for your patience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-11T11:11:48.756Z", "resolved_inferred": false, "started_at": "2026-05-11T08:00:42.000Z", @@ -452,7 +452,7 @@ "body": "This issue is now resolved. Email delivery has been successful with no monitored issues.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-09T01:01:25.584Z", "resolved_inferred": false, "started_at": "2026-05-08T18:10:52.477Z", @@ -465,7 +465,7 @@ "body": "This issue has now been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-30T22:36:54.680Z", "resolved_inferred": false, "started_at": "2026-04-30T21:46:01.598Z", @@ -478,7 +478,7 @@ "body": "The system has recovered and functionality has returned to normal.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-28T18:40:35.919Z", "resolved_inferred": false, "started_at": "2026-04-28T14:46:42.569Z", @@ -491,7 +491,7 @@ "body": "The connectivity issues affecting a subset of customers in our AWS EU West (Paris) region have been resolved. Failed probes recovered at 11:36 UTC following remediation of an issue with our underlying cloud infrastructure provider. We are no longer observing any elevated error rates or latency in the region. We apologise for any inconvenience caused and will conduct a post-incident review.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-27T12:40:52.501Z", "resolved_inferred": false, "started_at": "2026-04-27T11:49:33.000Z", @@ -504,7 +504,7 @@ "body": "An incident with an upstream service provider has been resolved, and access to the model is now restored.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-20T10:41:44.443Z", "resolved_inferred": false, "started_at": "2026-04-20T06:37:06.459Z", @@ -517,7 +517,7 @@ "body": "We have successfully deployed a fix for the PrivateLink hostname issue to the User Console. Customers who experienced incorrect PrivateLink URLs or connectivity issues with their deployments should now see correct hostnames. We apologize for the inconvenience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-10T19:54:36.238Z", "resolved_inferred": false, "started_at": "2026-04-09T20:46:43.845Z", @@ -530,7 +530,7 @@ "body": "We have confirmed no further impact from this incident, and are now marking it as resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-10T11:51:26.139Z", "resolved_inferred": false, "started_at": "2026-04-09T15:37:13.389Z", @@ -543,7 +543,7 @@ "body": "Issue has been fixed and there should be no more customer impact", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-06T20:43:53.394Z", "resolved_inferred": false, "started_at": "2026-04-06T17:58:07.321Z", @@ -556,7 +556,7 @@ "body": "Endpoints are operating normally", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-30T19:57:01.585Z", "resolved_inferred": false, "started_at": "2026-03-30T18:46:47.970Z", @@ -569,7 +569,7 @@ "body": "AutoOps is back to full functionality in the AWS us-east-1 region and the incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-27T07:23:08.363Z", "resolved_inferred": false, "started_at": "2026-03-27T04:33:19.440Z", @@ -582,7 +582,7 @@ "body": "This issue is resolved. Customers are now able to create new Serverless projects in the GCP europe-west3 region", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-26T17:42:42.430Z", "resolved_inferred": false, "started_at": "2026-03-26T10:51:36.213Z", @@ -595,7 +595,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-09T20:29:56.787Z", "resolved_inferred": false, "started_at": "2026-03-09T11:32:34.694Z", @@ -608,7 +608,7 @@ "body": "Update \u2014 Incident ongoing. AWS Bahrain (me-south-1) has been removed from new deployment selection on cloud.elastic.co. Existing deployments remain inaccessible due to the AWS infrastructure disruption, with no recovery timeline provided by AWS.\n\nAssume the region is unavailable for the foreseeable future.\n\nFor assistance, please open a case in our Support portal (https://support.elastic.co) or email support@elastic.co.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "started_at": "2026-03-02T06:23:20.799Z", "state": "identified", "title": "Connectivity disruption for AWS Bahrain (me-south-1)", @@ -619,7 +619,7 @@ "body": "This incident is resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-26T17:07:16.810Z", "resolved_inferred": false, "started_at": "2026-02-26T11:29:20.978Z", @@ -632,7 +632,7 @@ "body": "404 errors have been resolved on the elastic.co webpage.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-25T14:38:43.410Z", "resolved_inferred": false, "started_at": "2026-02-25T14:33:24.427Z", @@ -645,7 +645,7 @@ "body": "This issue is now resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-18T19:12:08.321Z", "resolved_inferred": false, "started_at": "2026-02-18T17:56:44.173Z", diff --git a/api/v/elation-health.json b/api/v/elation-health.json index 8fb117f050d3280b98c8301a534465b421a98dd0..e66ab468b8205dc7fc560d6048f20e605eec9a79 100644 --- a/api/v/elation-health.json +++ b/api/v/elation-health.json @@ -3,7 +3,7 @@ "slug": "elation-health", "platform": "status.io", "status_url": "https://elation.status.io", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": false, "first_watched": "2026-09-04T07:06:16Z", diff --git a/api/v/elevio.json b/api/v/elevio.json index 6b0d105873460847c037305d33aa43d745245b22..0c7fdeef2f217d8df226dece9dfd48ca38b7cfb7 100644 --- a/api/v/elevio.json +++ b/api/v/elevio.json @@ -3,7 +3,7 @@ "slug": "elevio", "platform": "statuspage", "status_url": "https://status.elev.io", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", diff --git a/api/v/ellucian.json b/api/v/ellucian.json index a422f6e6bbfea5f5a396e31db573bc453ad97595..a8cf4f97b3378b7043b782c1d29735c821e992cf 100644 --- a/api/v/ellucian.json +++ b/api/v/ellucian.json @@ -3,7 +3,7 @@ "slug": "ellucian", "platform": "statuspage", "status_url": "https://status.elluciancloud.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "Ellucian has resolved an issue affecting Ellucian Insights and Ellucian Intelligent Processes (EIP) for some customers. The service is operating as expected, and we will continue to monitor. \n\nThank You,\nYour Ellucian Team", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-09-02T13:30:44.275-04:00", "resolved_inferred": false, "started_at": "2026-09-02T11:11:43.800-04:00", @@ -25,7 +25,7 @@ "body": "Ellucian has resolved an issue affecting Smart Plan for some customers. The service is operating as expected, and we will continue to monitor. \n\nThank You,\nYour Ellucian Team", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-20T12:58:43.798-04:00", "resolved_inferred": false, "started_at": "2026-08-20T10:49:45.060-04:00", @@ -38,7 +38,7 @@ "body": "Mitigation strategies have been applied and Insights' transformation jobs are now completing within expected timeframes. Ellucian is continuing to monitor transformation execution.\n\nThank You,\nYour Ellucian Team", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-06T16:01:36.895-04:00", "resolved_inferred": false, "started_at": "2026-08-06T09:19:15.124-04:00", @@ -51,7 +51,7 @@ "body": "The short-term mitigations have been validated and operations are validated as returning to stable function. The team will continue to monitor the overall health of our core services over the remainder of this week.\n\nThank You,\nYour Ellucian Team", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-05T19:51:19.313-04:00", "resolved_inferred": false, "started_at": "2026-08-05T14:10:15.625-04:00", @@ -64,7 +64,7 @@ "body": "Microsoft fixed the issue causing the Azure outage. At this time the Ellucian Student Financial Success line of products is back online.\n\nThank You,\nYour Ellucian Team", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-23T16:48:06.429-04:00", "resolved_inferred": false, "started_at": "2026-07-23T12:28:10.645-04:00", @@ -77,7 +77,7 @@ "body": "Ellucian has resolved an issue affecting Ellucian Forms for some customers. The service is operating as expected, and we will continue to monitor. \n\nThank You,\nYour Ellucian Team", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-14T16:40:47.786-04:00", "resolved_inferred": false, "started_at": "2026-07-14T11:54:03.232-04:00", @@ -90,7 +90,7 @@ "body": "Ellucian has resolved an issue affecting Insights for some customers. The service is operating as expected, and we will continue to monitor. \n\nThank You,\nYour Ellucian Team", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-23T23:02:54.317-04:00", "resolved_inferred": false, "started_at": "2026-06-23T21:34:12.745-04:00", @@ -103,7 +103,7 @@ "body": "Ellucian has resolved an issue affecting workflows for some Ellucian Recruit customers. The service is operating as expected, and we will continue to monitor.\n\nThank You,\nYour Ellucian Team", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-26T17:52:32.411-04:00", "resolved_inferred": false, "started_at": "2026-05-26T15:27:36.736-04:00", @@ -116,7 +116,7 @@ "body": "Ellucian has resolved an issue affecting workflows for some Ellucian Recruit customers. The service is operating as expected, and we will continue to monitor. \n\nThank You,\nYour Ellucian Team", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-21T14:32:21.322-04:00", "resolved_inferred": false, "started_at": "2026-05-21T11:05:42.000-04:00", @@ -129,7 +129,7 @@ "body": "Ellucian has resolved an issue affecting email and workflows in Advance, Advise and Recruit for some customers. The service is operating as expected, and we will continue to monitor. \n\nThank You,\nYour Ellucian Team", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-15T02:14:14.316-04:00", "resolved_inferred": false, "started_at": "2026-05-14T12:03:49.000-04:00", @@ -142,7 +142,7 @@ "body": "Ellucian Engineers have implemented the solution to this issue, and all production services have been restored.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-06T11:54:15.120-04:00", "resolved_inferred": false, "started_at": "2026-05-06T10:47:08.919-04:00", @@ -155,7 +155,7 @@ "body": "Ellucian has resolved an issue affecting Ellucian Forms for some customers. The service is operating as expected, and we will continue to monitor. \n\nThank You,\nYour Ellucian Team", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-10T12:03:56.749-04:00", "resolved_inferred": false, "started_at": "2026-04-10T11:42:45.626-04:00", @@ -168,7 +168,7 @@ "body": "Ellucian has resolved an issue affecting Colleague Document download for some customers. The service is operating as expected, and we will continue to monitor. \n\nThank You,\nYour Ellucian Team", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-26T15:32:27.065-04:00", "resolved_inferred": false, "started_at": "2026-03-26T10:48:10.000-04:00", @@ -181,7 +181,7 @@ "body": "Ellucian has resolved an issue affecting Person Manager for some customers. The service is operating as expected, and we will continue to monitor. \n\nThank You,\nYour Ellucian Team", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-18T12:08:11.871-04:00", "resolved_inferred": false, "started_at": "2026-03-18T12:08:11.813-04:00", @@ -194,7 +194,7 @@ "body": "Ellucian has resolved an issue affecting Elevate for some customers in Canada. The service is operating as expected, and we will continue to monitor.\n\nThank You,\nYour Ellucian Team", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-14T10:43:12.000-04:00", "resolved_inferred": false, "started_at": "2026-03-14T08:36:34.928-04:00", @@ -207,7 +207,7 @@ "body": "Ellucian continues to work with AWS as we recover from the recent AWS outage that impacted our Middle East customers and certain services. Impact is now limited, and we will communicate directly with the small number of customers still affected moving forward. There will be no further updates for this incident on the Status Page.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-05T17:00:38.544-05:00", "resolved_inferred": false, "started_at": "2026-03-01T10:08:43.275-05:00", @@ -220,7 +220,7 @@ "body": "The regions of CA, and EU are fully restored and schedules are triggering again.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-20T12:39:37.391-05:00", "resolved_inferred": false, "started_at": "2026-02-20T11:19:46.493-05:00", @@ -233,7 +233,7 @@ "body": "Ellucian has resolved an issue affecting Person Manager for some customers with intermittent performance issues. The service is operating as expected, and we will continue to monitor. \n\nThank You,\nYour Ellucian Team", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-19T14:30:53.005-05:00", "resolved_inferred": false, "started_at": "2026-02-19T11:33:13.732-05:00", @@ -246,7 +246,7 @@ "body": "AWS performed an unscheduled minor upgrade of the PostgreSQL database, resulting in brief database downtime. During this window, Customer Data Connect pipeline runs experienced a momentary impact.\n\nAll services are now operating normally.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-16T05:00:00.000-05:00", "resolved_inferred": false, "started_at": "2026-02-16T05:00:00.000-05:00", @@ -259,7 +259,7 @@ "body": "Ellucian has identified and resolved the issue that was temporarily affecting some users on the Experience Dashboard. Some Data Connect jobs were also interrupted or did not start at the scheduled time. Service has been restored to normal. Access to Ethos, Data Connect, Insights, and EIP may have been temporarily impacted during this time.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-06T17:30:00.000-05:00", "resolved_inferred": false, "started_at": "2026-02-06T17:30:00.000-05:00", @@ -272,7 +272,7 @@ "body": "Ellucian Engineers remediated an issue impacting ILP processing, the system stabilized, message processing resumed at normal rates, and the backlog was cleared of all actionable messages. We will continue to closely monitor performance.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-22T16:05:36.014-05:00", "resolved_inferred": false, "started_at": "2026-01-22T11:02:00.945-05:00", @@ -285,7 +285,7 @@ "body": "Some customers experienced intermittent slow response times for Ethos API calls. Ellucian engineers investigated and confirmed that response times have recovered. We will continue to closely monitor the environment.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-12T18:26:04.215-05:00", "resolved_inferred": false, "started_at": "2026-01-12T17:12:39.792-05:00", @@ -298,7 +298,7 @@ "body": "Ellucian engineers resolved an issue impacting Experience cards. Normal system performance was restored and closely monitored overnight, engineers will continue to monitor the service.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-12T12:00:08.446-05:00", "resolved_inferred": false, "started_at": "2025-12-11T11:25:12.835-05:00", @@ -311,7 +311,7 @@ "body": "We closely monitored the widespread issue that Cloudflare was experiencing today. While we are unaware of any impacts to Ellucian SaaS or Cloud systems, it was possible that you may have experienced some intermittent issues until Cloudflare resolved the issue. Cloudflare updated that they implemented a fix and presently Cloudflare services are operating normally, they are no longer observing elevated errors or latency across the network. If you have any issues please submit a case to support. Thank you.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-18T13:00:33.155-05:00", "resolved_inferred": false, "started_at": "2025-11-18T09:40:23.780-05:00", @@ -324,7 +324,7 @@ "body": "Ellucian engineers have resolved the issue impacting Insights population jobs. Normal system performance has been restored.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-05T07:57:26.103-05:00", "resolved_inferred": false, "started_at": "2025-11-04T09:52:42.226-05:00", @@ -337,7 +337,7 @@ "body": "Ellucian is aware of an issue reported by Microsoft that Azure Front Door experienced issues resulting in a loss of connectivity to some services. Microsoft updated that they took remediation actions to restore access to the Azure management portal, they continue to see signs of recovery as they route traffic through health nodes. They anticipate full mitigation within the next four hours. Ellucian will continue to monitor. Please submit a ticket if any additional issues are encountered. Microsoft will continue to provide updates via https://azure.status.microsoft/en-us/status.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-29T16:28:54.553-04:00", "resolved_inferred": false, "started_at": "2025-10-29T13:08:30.839-04:00", @@ -350,7 +350,7 @@ "body": "All Ellucian cloud services have been restored. We continue to monitor AWS for further issues.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-20T20:59:20.681-04:00", "resolved_inferred": false, "started_at": "2025-10-20T06:21:00.915-04:00", @@ -363,7 +363,7 @@ "body": "The authentication issues have been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-14T22:19:44.757-04:00", "resolved_inferred": false, "started_at": "2025-10-14T21:43:35.838-04:00", @@ -376,7 +376,7 @@ "body": "Engineering teams remediated the issue impacting ILP real-time and bulk job processing, ILP is fully operational.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-16T12:32:20.901-04:00", "resolved_inferred": false, "started_at": "2025-09-16T11:14:24.340-04:00", @@ -389,7 +389,7 @@ "body": "The intermittent latency issues have been fully resolved and Experience is fully operational.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-19T12:47:48.288-04:00", "resolved_inferred": false, "started_at": "2025-08-19T11:49:58.819-04:00", @@ -402,7 +402,7 @@ "body": "Experience performance issues have been resolved. Ellucian engineers have identified and remediated the root cause.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-18T15:53:35.062-04:00", "resolved_inferred": false, "started_at": "2025-08-18T11:48:15.505-04:00", @@ -415,7 +415,7 @@ "body": "Ellucian engineers have identified and resolved an issue impacting Experience. Normal system performance is restored, and engineers will monitor the service.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-04T14:20:40.909-04:00", "resolved_inferred": false, "started_at": "2025-08-04T13:32:02.278-04:00", diff --git a/api/v/emnify.json b/api/v/emnify.json index c4f97c7e351574c13e38f6f252fd842e6fc50cb2..79aa5d7b8d61dfedfff81e7bf9efd6a6a9265b0b 100644 --- a/api/v/emnify.json +++ b/api/v/emnify.json @@ -3,7 +3,7 @@ "slug": "emnify", "platform": "statuspage", "status_url": "https://status.emnify.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "Dear emnify Customers,\n\nThe incident has been resolved. In case you are still having issues, please reach out to our Support Team via our Help Center.\n\n\nKind regards, \nemnify Support Team", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-01T10:22:52.461Z", "resolved_inferred": false, "started_at": "2026-08-01T09:56:04.773Z", @@ -25,7 +25,7 @@ "body": "Dear emnify Customers,\n\nThis incident has been resolved. The recovery process has been completed, and the temporary restriction on report filters has also been removed. Both current and historical data are now available in the affected reports in the emnify portal.\n\nIn case you are still having issues, please reach out to our Support Team via our Help Center.\n\n\nKind regards, \nemnify Support Team", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-03T12:37:47.920Z", "resolved_inferred": false, "started_at": "2026-07-27T13:15:19.744Z", @@ -38,7 +38,7 @@ "body": "Dear emnify Customers,\n\nThis incident has been resolved. In case you are still having issues, please reach out to our Support Team via our Help Center.\n\n\nKind regards, \nemnify Support Team", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-27T13:19:17.133Z", "resolved_inferred": false, "started_at": "2026-07-24T12:32:48.681Z", @@ -51,7 +51,7 @@ "body": "The incident has been resolved, and we confirm that portal authentication is fully functional again. \n\nIn case you are still having issues, please reach out to our Support Team via our Help Center.\n\nKind regards, \nemnify Support Team", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-10T19:12:50.851Z", "resolved_inferred": false, "started_at": "2026-07-10T17:12:28.499Z", @@ -64,7 +64,7 @@ "body": "Dear emnify Customers,\n\nThis incident has been resolved. In case you are still having issues, please reach out to our Support Team via our Help Center.\n\n\nKind regards, \nemnify Support Team", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-30T18:42:46.730Z", "resolved_inferred": false, "started_at": "2026-06-30T17:43:55.778Z", @@ -77,7 +77,7 @@ "body": "Dear emnify Customers,\n\nNetwork tests toward Cellcom are now passing, indicating that connectivity has been restored.\n\nAs the issue affecting MTN remains ongoing, we have temporarily removed MTN from the available networks in our Guinea data plans to minimize customer impact. Customers can continue using alternative networks in Guinea, which are operating normally.\n\nWe will continue to monitor the situation closely and will re-enable MTN once the network demonstrates stable and reliable service.\n\n\nKind regards, \nemnify Support Team", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-30T14:48:39.473Z", "resolved_inferred": false, "started_at": "2026-06-30T08:11:18.524Z", @@ -90,7 +90,7 @@ "body": "This incident has been resolved. \n\nIn case you are still having issues, please submit a ticket to our Customer Support team via the help center.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-26T20:44:54.912Z", "resolved_inferred": false, "started_at": "2026-06-26T19:58:17.115Z", @@ -103,7 +103,7 @@ "body": "The issue has since been resolved, and access to Vodafone Germany is fully operational again. \n\nIn case you are still having issues, please reach out to our Support Team via our Help Center.\n\nKind regards, \nemnify Support Team", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-23T13:54:07.499Z", "resolved_inferred": false, "started_at": "2026-06-23T12:49:18.535Z", @@ -116,7 +116,7 @@ "body": "This incident has been resolved. \n\nPlease reach out to our Customer Support team via the help center if you continue to face issues.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-21T07:11:10.954Z", "resolved_inferred": false, "started_at": "2026-06-20T22:35:42.415Z", @@ -129,7 +129,7 @@ "body": "This incident has been resolved. If you continue to experience any issues, please contact our Customer Support team.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-18T16:02:56.159Z", "resolved_inferred": false, "started_at": "2026-06-18T12:55:25.438Z", @@ -142,7 +142,7 @@ "body": "We have confirmed that Orange Guinea connectivity is now fully operational. Services have recovered and traffic is processing normally.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-08T13:30:41.096Z", "resolved_inferred": false, "started_at": "2026-06-04T13:48:25.051Z", @@ -155,7 +155,7 @@ "body": "## Summary\n\nDue to a full outage of emnify\u2019s LTE signalling carrier for the 90143XXX and 29509XXX IMSIs, customers were unable to attach to LTE networks during the impact duration of 29min.\n\nDue to static routing in 3GPP signalling systems, there is no failover to alternate carriers. Most devices were able to connect to alternative RAT types \\(2G/3G\\) or using alternate IMSIs. Existing data connections were not impacted.\n\n## Timeline \\(UTC\\)\n\n| Time | Event |\n| --- | --- |\n| 07:47 | **>>>INCIDENT STARTS HERE<<<** Carrier applies configuration change to their Diameter Routing Agents, which triggers a software bug. LTE signalling links between emnify and carrier are all shut down. |\n| 07:52 | Automated alert raised |\n| 08:04 | Internal incident created |\n| 08:16 | LTE signalling links up again **>>>INCIDENT STOPS HERE<<<** |", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-03T09:28:58.572Z", "resolved_inferred": false, "started_at": "2026-06-03T08:23:05.384Z", @@ -168,7 +168,7 @@ "body": "Dear emnify Customers,\n\nAt approximately 04:30 UTC today, we observed service degradation affecting connectivity to the Claro network in Paraguay, Uruguay, and Argentina. During this period, devices attempting to connect via Claro may have experienced intermittent connectivity issues or service disruptions.\n\nBeginning around 07:30 UTC, we observed traffic levels returning to normal, with network performance remaining stable since that time. Based on our monitoring, the incident has been resolved and services have recovered.\n\nWe are continuing to engage with Claro to better understand the underlying cause of the interruption and will review any findings made available by the operator.\n\nIf you continue to experience connectivity issues, please contact our Support Team through the Help Center for further assistance.\n\n\nKind regards, \nemnify Support Team", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-02T04:30:00.000Z", "resolved_inferred": false, "started_at": "2026-06-02T04:30:00.000Z", @@ -181,7 +181,7 @@ "body": "Dear emnify Customers,\n\nThis incident has been resolved. In case you are still having issues, please reach out to our Support Team via our Help Center.\n\n\nKind regards, \nemnify Support Team", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-20T17:05:26.619Z", "resolved_inferred": false, "started_at": "2026-05-18T07:18:46.089Z", @@ -194,7 +194,7 @@ "body": "This incident has been resolved", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-14T21:16:25.433Z", "resolved_inferred": false, "started_at": "2026-05-14T18:02:13.098Z", @@ -207,7 +207,7 @@ "body": "As the issue remains ongoing, we have temporarily removed MTN from the list of available networks in our data plans for Guinea-Bissau to minimize customer impact. Customers can continue to use alternative networks in Guinea-Bissau, which are operating normally.\n\nWe will continue to monitor the situation closely and will re-enable MTN once the network demonstrates stable and reliable service.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-17T08:35:32.589Z", "resolved_inferred": false, "started_at": "2026-05-11T15:24:55.429Z", @@ -220,7 +220,7 @@ "body": "Dear emnify Customers,\n\nThe incident has been resolved. \n\nOur monitoring and validation tests confirm that the operator MTN is now fully operational. \n\nIn case you are still having issues, please reach out to our Support Team via our Help Center.\n\nKind regards,\nemnify Support Team", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-30T13:06:03.318Z", "resolved_inferred": false, "started_at": "2026-04-27T14:30:21.761Z", @@ -233,7 +233,7 @@ "body": "The issue affecting event display has been resolved.\n\nIf you continue to experience any problems or have questions, please do not hesitate to contact our support team.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-27T03:54:29.531Z", "resolved_inferred": false, "started_at": "2026-04-27T02:42:25.000Z", @@ -246,7 +246,7 @@ "body": "Dear emnify Customers,\n\nThe incident has been resolved, and all services are now fully operational.\n\nIn case you are still having issues, please reach out to our Support Team via our Help Center.\n\nKind regards,\nemnify Support Team", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-22T13:01:10.525Z", "resolved_inferred": false, "started_at": "2026-04-22T07:56:20.033Z", @@ -259,7 +259,7 @@ "body": "The issue affecting connectivity in MTN Uganda has been fully resolved.\n\nIf you experience any further issues, please reach out to our support team.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-17T23:08:32.015Z", "resolved_inferred": false, "started_at": "2026-04-17T17:53:14.599Z", @@ -272,7 +272,7 @@ "body": "Dear emnify Customers,\n\nThe incident has been resolved, and the OpenVPN service is fully operational again. \n\nIn case you are still having issues, please reach out to our Support Team via our Help Center.\n\nKind regards, \nemnify Support Team", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-17T09:55:41.265Z", "resolved_inferred": false, "started_at": "2026-04-17T08:47:21.186Z", @@ -285,7 +285,7 @@ "body": "Dear emnify Customers,\n\nThe incident has been resolved. In case you are still having issues, please reach out to our Support Team via our Help Center.\n\n\nKind regards, \nemnify Support Team", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-08T19:12:41.107Z", "resolved_inferred": false, "started_at": "2026-04-08T16:17:10.441Z", @@ -298,7 +298,7 @@ "body": "The issue has been fully resolved, and all services are operating normally.\n\nIf you continue to experience any issues, please reach out to support.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-25T10:51:39.559Z", "resolved_inferred": false, "started_at": "2026-03-25T09:35:11.023Z", @@ -311,7 +311,7 @@ "body": "Dear emnify Customers,\n\nThe incident has been resolved. In case you are still having issues, please reach out to our Support Team via our Help Center.\n\n\nKind regards, \nemnify Support Team", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-13T14:06:56.046Z", "resolved_inferred": false, "started_at": "2026-03-13T11:55:18.411Z", @@ -324,7 +324,7 @@ "body": "Dear emnify Customers,\n\nThe incident has been resolved, and Diameter signaling metrics have now returned to normal levels. The temporary increase observed earlier has been identified as a result of the signaling degradation incident that occurred yesterday.\n\nIn case you are still having issues, please reach out to our Support Team via our Help Center.\n\n\nKind regards, \nemnify Support Team", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-12T06:07:54.539Z", "resolved_inferred": false, "started_at": "2026-03-12T05:34:38.000Z", @@ -337,7 +337,7 @@ "body": "On March 11, 2026, between approximately 13:20 UTC and 17:10 UTC, some devices on the emnify network experienced intermittent connectivity issues, including delayed session establishment and increased packet loss. Mitigation actions implemented by our engineering teams resulted in service progressively improving from approximately 14:45 UTC.\n\n**Incident overview** \nAn unexpected and sudden increase in data traffic volume on one of our carrier connectivity links in the EU region exceeded the available link capacity. Despite high spare capacity built into our platform, traffic volume increased approximately sixfold within a few minutes, which the link was not dimensioned to absorb. This led to congestion on the link, resulting in packet loss that affected the ability of some devices to establish and maintain data sessions. Impacted devices experienced intermittent connectivity and may have needed to reconnect or retransmit data.\n\n**Mitigation actions taken** \nOur engineering team identified the source of the traffic surge and took the following actions to restore service:\n\n* Isolated the traffic that was causing the link congestion\n* Redirected the identified traffic to a separate, dedicated link to eliminate congestion on the primary connectivity path\n* Scaled up signalling processing capacity to handle the elevated request volume during recovery\n* Monitored the network closely as devices reconnected and traffic patterns normalized\n\n**Preventive measures** \nWe are reviewing our link capacity planning and traffic management controls to improve our ability to absorb unexpected traffic surges without impact to customers. This includes higher capacity reserves and implementing traffic shaping mechanisms to better protect shared infrastructure.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-11T17:30:21.720Z", "resolved_inferred": false, "started_at": "2026-03-11T14:04:00.741Z", @@ -350,7 +350,7 @@ "body": "Dear emnify Customers,\n\nThe incident has been resolved, and network traffic has returned to normal levels.\n\nIn case you are still having issues, please reach out to our Support Team via our Help Center.\n\n\nKind regards, \nemnify Support Team", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-11T01:51:56.898Z", "resolved_inferred": false, "started_at": "2026-03-10T22:13:22.105Z", @@ -363,7 +363,7 @@ "body": "Dear emnify Customers, \n\nEarlier today, we observed a temporary degradation in the SMS services. Upon investigation, it was determined that A2P SMS-MT, or SMS messages sent from the portal/API to emnify devices, were affected. After applying a fix, we immediately started to see SMS-MT being processed as normal. \n\nAll SMS services are now fully operational as of writing.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-05T09:30:00.000Z", "resolved_inferred": false, "started_at": "2026-03-05T09:30:00.000Z", @@ -376,7 +376,7 @@ "body": "This incident has been resolved and all data has been successfully backfilled. \n\nIf you continue to experience any issues, please contact our Customer Support team via the help center.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-05T00:53:06.660Z", "resolved_inferred": false, "started_at": "2026-03-04T21:24:41.509Z", @@ -389,7 +389,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-17T15:37:40.901Z", "resolved_inferred": false, "started_at": "2026-02-17T08:39:51.833Z", @@ -402,7 +402,7 @@ "body": "This incident has been resolved..", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-17T09:22:42.293Z", "resolved_inferred": false, "started_at": "2026-02-11T09:16:14.965Z", @@ -415,7 +415,7 @@ "body": "Tigo Panama has confirmed that their 2G service has been permanently sunsetted. As a result, 2G connectivity is no longer available on the Tigo Panama network.\n\n-Other radio access types with Tigo Panama remain available and are operating normally\n-2G service is still available in Panama through alternative mobile network\n\nIf you have any questions, please contact our Customer Support team.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-04T21:33:28.165Z", "resolved_inferred": false, "started_at": "2026-02-04T20:56:08.064Z", @@ -428,7 +428,7 @@ "body": "This incident has been resolved. If you continue to experience any issues, please contact our Customer Support team", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-30T21:27:50.666Z", "resolved_inferred": false, "started_at": "2026-01-30T20:03:43.758Z", @@ -441,7 +441,7 @@ "body": "This incident has been resolved. If you continue to experience any issues, please contact our Customer Support team for further assistance.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-28T21:23:09.400Z", "resolved_inferred": false, "started_at": "2026-01-28T17:40:21.713Z", @@ -454,7 +454,7 @@ "body": "Dear emnify Customers,\n\nThe incident has been resolved, and all services are now fully operational.\n\nIn case you are still having issues, please reach out to our Support Team via our Help Center.\n\n\nKind regards,\nemnify Support Team", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-17T02:47:24.735Z", "resolved_inferred": false, "started_at": "2026-01-16T21:54:27.722Z", @@ -467,7 +467,7 @@ "body": "The incident has been resolved. Service in Uganda is now fully operational", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-27T18:19:27.470Z", "resolved_inferred": false, "started_at": "2026-01-13T19:45:09.321Z", @@ -480,7 +480,7 @@ "body": "Dear emnify Customers,\n\nThe incident has been resolved, and all services are now fully operational.\n\nIn case you are still having issues, please reach out to our Support Team via our Help Center.\n\n\nKind regards,\nemnify Support Team", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-07T04:17:51.543Z", "resolved_inferred": false, "started_at": "2026-01-07T03:28:19.926Z", @@ -493,7 +493,7 @@ "body": "We are currently experiencing service unavailability with the Vala network in Kosovo due to changes in their network configuration. As a result, Vala is temporarily unavailable until further notice.\n\nTo minimize service disruption, we have enabled connectivity through IPKO, now included in the same rate zone across most data plans.\n\nIf you have any questions or require assistance, please reach out to our emnify Support team.\n\nWe will continue to monitor the situation and provide updates as soon as more information becomes available.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-20T07:00:00.000Z", "resolved_inferred": false, "started_at": "2025-11-20T07:00:00.000Z", @@ -506,7 +506,7 @@ "body": "Dear emnify Customers,\n\nThe incident has been resolved, and all services are now fully operational.\n\nIn case you are still having issues, please reach out to our Support Team via our Help Center.\n\n\nKind regards,\nemnify Support Team", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-18T15:15:50.707Z", "resolved_inferred": false, "started_at": "2025-11-18T13:00:03.103Z", @@ -519,7 +519,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-30T09:14:04.933Z", "resolved_inferred": false, "started_at": "2025-10-30T08:01:50.632Z", @@ -532,7 +532,7 @@ "body": "Connectivity in Tanzania has recovered. The country-wide network shutdown has ended and affected mobile network operators, including Airtel and Halotel, are operating normally again. Devices are now attaching and passing traffic as expected. We\u2019ll continue to monitor for stability", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-04T12:18:41.030Z", "resolved_inferred": false, "started_at": "2025-10-29T15:47:56.813Z", @@ -545,7 +545,7 @@ "body": "Dear emnify Customers,\n\nThe incident has been resolved. Should you need further help, please reach out to our Support Team via our Help Center.\n\n\nKind regards,\nemnify Support Team", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-20T11:16:38.571Z", "resolved_inferred": false, "started_at": "2025-10-20T10:06:56.041Z", @@ -558,7 +558,7 @@ "body": "This incident has been resolved. Services on the Telcel network in Mexico are fully restored, and connectivity has returned to normal levels.\n\nIf you are still experiencing any issues, please contact our Customer Support team for assistance.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-11T07:35:33.776Z", "resolved_inferred": false, "started_at": "2025-10-10T20:38:55.013Z", @@ -571,7 +571,7 @@ "body": "We have temporarily blocked traffic to Vodacom in the Democratic Republic of Congo due to network issues identified on the partner side. The issue has been reported to our roaming partner for resolution. The block was implemented immediately to prevent extended disruption and will be automatically lifted once we confirm that the Vodacom network is operational again.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-08T13:04:19.169Z", "resolved_inferred": false, "started_at": "2025-10-08T13:04:19.109Z", @@ -584,7 +584,7 @@ "body": "This incident has been resolved", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-07T13:50:43.975Z", "resolved_inferred": false, "started_at": "2025-10-06T16:02:58.204Z", @@ -597,7 +597,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-30T15:33:04.944Z", "resolved_inferred": false, "started_at": "2025-09-30T14:27:08.398Z", @@ -610,7 +610,7 @@ "body": "Dear emnify Customers,\n\nThe incident has been resolved. In case you are still having issues, please reach out to our Support Team via our Help Center.\n\n\nKind regards,\nemnify Support Team", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-24T18:52:11.564Z", "resolved_inferred": false, "started_at": "2025-09-23T18:33:42.811Z", @@ -623,7 +623,7 @@ "body": "Dear emnify Customers,\n\nThis incident has been resolved. \n\nShould you continue to experience any issues, please do not hesitate to contact our Customer Support Team through the help center. \n\nKind regards,\nemnify Support Team", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-20T01:00:10.066Z", "resolved_inferred": false, "started_at": "2025-09-19T20:47:09.616Z", @@ -636,7 +636,7 @@ "body": "This incident has been resolved.\n\nShould you continue to experience any issues, please do not hesitate to contact our Customer Support Team through the help center.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-19T00:03:44.837Z", "resolved_inferred": false, "started_at": "2025-09-18T23:54:44.525Z", @@ -649,7 +649,7 @@ "body": "The incident is now resolved. Should you still encounter any problems, feel free to reach out to our Customer Support team", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-18T16:34:02.089Z", "resolved_inferred": false, "started_at": "2025-09-18T15:33:21.677Z", diff --git a/api/v/endless-group.json b/api/v/endless-group.json index a65574227c8fc2ab4c58a8f4d837f7c4849985a7..b061e1ae13afe650df890ac1f60bf8bd519cdfb0 100644 --- a/api/v/endless-group.json +++ b/api/v/endless-group.json @@ -3,7 +3,7 @@ "slug": "endless-group", "platform": "statuspage", "status_url": "https://status.theendlessweb.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", diff --git a/api/v/engine-yard.json b/api/v/engine-yard.json index 9a4d36a342637dc5fccd6f5abcfa05c0b2d44c48..63ebcf8e651e28f9463b19234a639515ea9852dd 100644 --- a/api/v/engine-yard.json +++ b/api/v/engine-yard.json @@ -3,7 +3,7 @@ "slug": "engine-yard", "platform": "statuspage", "status_url": "https://engineyard.statuspage.io", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "AWS has confirmed that the outage in the US-EAST-1 region has now been resolved, and all services are operational.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-20T23:11:17.977Z", "resolved_inferred": false, "started_at": "2025-10-20T11:38:23.825Z", @@ -25,7 +25,7 @@ "body": "The incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-29T02:48:33.164Z", "resolved_inferred": false, "started_at": "2025-08-28T03:15:09.502Z", @@ -38,7 +38,7 @@ "body": "Corrective actions were applied and the login to EngineYard Cloud should once again properly work.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-04T11:12:50.844Z", "resolved_inferred": false, "started_at": "2025-08-04T09:23:46.257Z", diff --git a/api/v/enjin.json b/api/v/enjin.json index 5b7981fc0ca0c299d9e95b706959296c824610c5..b075d1878fa1283183e8ea46c61ba22c949f9c68 100644 --- a/api/v/enjin.json +++ b/api/v/enjin.json @@ -3,7 +3,7 @@ "slug": "enjin", "platform": "statuspage", "status_url": "https://www.enjinstatus.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-20T09:56:17.956Z", "resolved_inferred": false, "started_at": "2026-08-20T09:30:14.281Z", @@ -25,7 +25,7 @@ "body": "The ENJ/EFI token claims functionality has now been re-enabled.", "first_seen": "2026-09-04T07:06:16Z", "impact": "maintenance", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-02T08:12:14.000Z", "resolved_inferred": false, "started_at": "2025-11-25T07:58:50.372Z", @@ -38,7 +38,7 @@ "body": "A distributed denial-of-service (DDoS) attack targeting Enjin Platform Cloud was observed earlier and appears to have caused the intermittent availability issues. Enjin Platform Cloud's behavior appears normal at this time: login and API requests are succeeding. Further investigation into the earlier DDoS-related disruptions is ongoing, and mitigations will be applied as needed.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-11T07:17:38.185Z", "resolved_inferred": false, "started_at": "2025-09-11T02:54:56.635Z", @@ -51,7 +51,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-02T06:41:47.275Z", "resolved_inferred": false, "started_at": "2025-09-02T03:51:35.000Z", @@ -64,7 +64,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-20T15:45:20.848Z", "resolved_inferred": false, "started_at": "2025-08-20T03:07:42.295Z", @@ -77,7 +77,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-07T06:21:52.093Z", "resolved_inferred": false, "started_at": "2025-08-07T02:41:15.000Z", diff --git a/api/v/entrata.json b/api/v/entrata.json index 40689f7ebf92f7b911d713efb57c393edf7559ac..586c3f800c28b6413468e295322c585b44e14e7b 100644 --- a/api/v/entrata.json +++ b/api/v/entrata.json @@ -3,7 +3,7 @@ "slug": "entrata", "platform": "statuspage", "status_url": "https://status.entrata.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-26T12:09:14.370-06:00", "resolved_inferred": false, "started_at": "2026-05-26T08:40:10.444-06:00", @@ -25,7 +25,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-10T09:35:46.373-07:00", "resolved_inferred": false, "started_at": "2026-02-09T10:46:54.764-07:00", diff --git a/api/v/epic-games.json b/api/v/epic-games.json index 0a60ea4d71b8b444691b4812c622ac4234d2da51..67a22ea38bdb028f3211ac41914c7a89e3469aca 100644 --- a/api/v/epic-games.json +++ b/api/v/epic-games.json @@ -3,7 +3,7 @@ "slug": "epic-games", "platform": "statuspage", "status_url": "https://status.epicgames.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "Login services on PlayStation 4 and 5 have returned to normal.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-28T14:32:33.759Z", "resolved_inferred": false, "started_at": "2026-08-28T13:55:01.981Z", @@ -25,7 +25,7 @@ "body": "The Support-A-Creator website has been restored.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-27T09:44:34.854Z", "resolved_inferred": false, "started_at": "2026-08-27T00:50:29.002Z", @@ -38,7 +38,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-27T13:36:08.100Z", "resolved_inferred": false, "started_at": "2026-08-19T20:07:29.000Z", @@ -51,7 +51,7 @@ "body": "We've fixed an issue with the Epic Games Launcher where players were unable to update or install games, or where they saw it appear blank. \n\nThis fix is out now, and if your launcher still appears blank please follow these steps:\nhttps://epic.gm/LibraryMissing", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-20T19:47:30.942Z", "resolved_inferred": false, "started_at": "2026-08-17T19:16:50.680Z", @@ -64,7 +64,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-14T03:10:09.009Z", "resolved_inferred": false, "started_at": "2026-08-14T02:36:11.879Z", @@ -77,7 +77,7 @@ "body": "Matchmaking and partying up are returned to normal.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-14T00:27:05.110Z", "resolved_inferred": false, "started_at": "2026-08-14T00:13:23.731Z", @@ -90,7 +90,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-11T18:13:52.118Z", "resolved_inferred": false, "started_at": "2026-08-10T14:20:44.744Z", @@ -103,7 +103,7 @@ "body": "Matchmaking in Fortnite Reload has returned to normal. We'll continue to monitor services to ensure everything remains stable.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-05T22:59:49.996Z", "resolved_inferred": false, "started_at": "2026-08-05T22:21:58.252Z", @@ -116,7 +116,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-31T00:53:57.457Z", "resolved_inferred": false, "started_at": "2026-07-31T00:31:29.885Z", @@ -129,7 +129,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-28T23:29:15.691Z", "resolved_inferred": false, "started_at": "2026-07-28T22:08:03.507Z", @@ -142,7 +142,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-22T19:22:40.259Z", "resolved_inferred": false, "started_at": "2026-07-22T19:08:39.240Z", @@ -155,7 +155,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-15T17:04:16.816Z", "resolved_inferred": false, "started_at": "2026-07-08T17:49:23.018Z", @@ -168,7 +168,7 @@ "body": "We're seeing matchmaking fully recovered and back to normal.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-11T02:24:08.693Z", "resolved_inferred": false, "started_at": "2026-06-11T01:35:39.670Z", @@ -181,7 +181,7 @@ "body": "Authentication to EOS Game Services failed or timed out between 12:03pm and 12:10pm EDT", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-06T16:00:00.000Z", "resolved_inferred": false, "started_at": "2026-06-06T16:00:00.000Z", @@ -194,7 +194,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-05T04:42:55.518Z", "resolved_inferred": false, "started_at": "2026-06-05T00:57:32.790Z", @@ -207,7 +207,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-04T22:28:45.316Z", "resolved_inferred": false, "started_at": "2026-06-04T18:34:08.332Z", @@ -220,7 +220,7 @@ "body": "Matchmaking has returned to normal and you should be able to queue up again without issue.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-02T22:23:21.254Z", "resolved_inferred": false, "started_at": "2026-06-02T21:01:45.983Z", @@ -233,7 +233,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-30T13:57:12.106Z", "resolved_inferred": false, "started_at": "2026-05-30T13:23:27.420Z", @@ -246,7 +246,7 @@ "body": "We pushed a change to our IDP service that blocked some valid OpenId tokens. We rolled the change back on 5/27/2026 6:00am", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-26T18:30:00.000Z", "resolved_inferred": false, "started_at": "2026-05-26T18:30:00.000Z", @@ -259,7 +259,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-18T23:51:44.499Z", "resolved_inferred": false, "started_at": "2026-05-18T23:13:39.194Z", @@ -272,7 +272,7 @@ "body": "Players who saw a delay in receiving V-Bucks should now have them available.\n\nAs part of this fix, players who qualify for the Showdown Umbrella styles introduced in today's update may see them granted at a later date.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-14T17:26:14.623Z", "resolved_inferred": false, "started_at": "2026-05-14T15:22:53.978Z", @@ -285,7 +285,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-14T12:37:17.065Z", "resolved_inferred": false, "started_at": "2026-05-14T11:45:06.468Z", @@ -298,7 +298,7 @@ "body": "We have rolled back a change to our backend that included additional claims in the EAS Auth Access token. This change could break the login flow in some games that allocated a fixed-size buffer to the access token.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-13T23:00:00.000Z", "resolved_inferred": false, "started_at": "2026-05-13T23:00:00.000Z", @@ -311,7 +311,7 @@ "body": "Matchmaking issues have been resolved. Players should now be able to queue into matches normally.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-12T01:01:38.622Z", "resolved_inferred": false, "started_at": "2026-05-12T00:05:02.153Z", @@ -324,7 +324,7 @@ "body": "Log-in and Matchmaking has recovered and we're no longer seeing any server delays. We'll continue to monitor these services and address any issues that arise.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-08T01:45:59.087Z", "resolved_inferred": false, "started_at": "2026-05-08T00:33:17.242Z", @@ -337,7 +337,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-24T06:03:43.888Z", "resolved_inferred": false, "started_at": "2026-04-24T05:45:11.569Z", @@ -350,7 +350,7 @@ "body": "\u2705 Matchmaking errors are fixed. Players can jump into a game again without issue. \n\nWe're monitoring game servers to make sure everything returns to normal.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-17T20:31:35.507Z", "resolved_inferred": false, "started_at": "2026-04-17T19:04:23.166Z", @@ -363,7 +363,7 @@ "body": "Issue with Unreal Revision Control in UEFN has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-17T15:13:40.761Z", "resolved_inferred": false, "started_at": "2026-04-17T10:35:25.667Z", @@ -376,7 +376,7 @@ "body": "This issue has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-15T12:57:13.568Z", "resolved_inferred": false, "started_at": "2026-04-15T09:51:51.932Z", @@ -389,7 +389,7 @@ "body": "There was an issue affecting Epic Online Services from 8:10 am to 8:55 am EDT. The likely symptom players faced was failure to log in.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-14T12:00:00.000Z", "resolved_inferred": false, "started_at": "2026-04-14T12:00:00.000Z", @@ -402,7 +402,7 @@ "body": "Log-ins and matchmaking are fixed! Players should be able to jump into a match again without issue", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-07T16:15:25.009Z", "resolved_inferred": false, "started_at": "2026-04-07T15:39:24.132Z", @@ -415,7 +415,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-01T06:11:59.086Z", "resolved_inferred": false, "started_at": "2026-04-01T05:53:13.178Z", @@ -428,7 +428,7 @@ "body": "Earlier issues affecting Epic Account Services and Game Services have been resolved. Players should now be able to access and play as normal.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-30T09:00:00.000Z", "resolved_inferred": false, "started_at": "2026-03-30T09:00:00.000Z", @@ -441,7 +441,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-30T09:08:12.998Z", "resolved_inferred": false, "started_at": "2026-03-30T08:43:44.043Z", @@ -454,7 +454,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-25T18:35:44.616Z", "resolved_inferred": false, "started_at": "2026-03-25T17:42:26.066Z", @@ -467,7 +467,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-30T18:57:25.522Z", "resolved_inferred": false, "started_at": "2026-03-24T18:18:09.721Z", @@ -480,7 +480,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-22T06:26:36.323Z", "resolved_inferred": false, "started_at": "2026-03-22T06:08:19.804Z", @@ -493,7 +493,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-22T04:55:11.167Z", "resolved_inferred": false, "started_at": "2026-03-22T01:41:21.080Z", @@ -506,7 +506,7 @@ "body": "This issue is fixed, all V-bucks and Outfit packs are available again on Xbox.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-21T21:55:04.528Z", "resolved_inferred": false, "started_at": "2026-03-21T15:27:04.365Z", @@ -519,7 +519,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-21T05:24:31.342Z", "resolved_inferred": false, "started_at": "2026-03-21T04:50:53.542Z", @@ -532,7 +532,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-14T01:38:33.701Z", "resolved_inferred": false, "started_at": "2026-03-14T01:02:00.194Z", @@ -545,7 +545,7 @@ "body": "Matchmaking services have been restored.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-02T17:20:37.493Z", "resolved_inferred": false, "started_at": "2026-03-02T06:16:59.084Z", @@ -558,7 +558,7 @@ "body": "\u2705 We've resolved an issue affecting Fortnite, Rocket League, Fall Guys and Epic Online Services logins.\n\nWe're continuing to monitor services to ensure everything remains stable.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-26T19:34:37.037Z", "resolved_inferred": false, "started_at": "2026-02-26T19:34:36.967Z", @@ -571,7 +571,7 @@ "body": "Some EOS analytics were not available in the DevPortal from Feb 25th 3:18 PM to Feb 26th 7:25 AM EST.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-25T20:00:00.000Z", "resolved_inferred": false, "started_at": "2026-02-25T20:00:00.000Z", @@ -584,7 +584,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-25T00:55:35.461Z", "resolved_inferred": false, "started_at": "2026-02-24T23:16:43.000Z", @@ -597,7 +597,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-24T00:53:31.110Z", "resolved_inferred": false, "started_at": "2026-02-23T23:52:32.881Z", @@ -610,7 +610,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-30T01:26:58.853Z", "resolved_inferred": false, "started_at": "2026-01-29T22:38:59.059Z", @@ -623,7 +623,7 @@ "body": "Connection attempts to EOS Voice received party join errors in Asia regions. This is resolved now and we are continuing to monitor.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-29T06:00:00.000Z", "resolved_inferred": false, "started_at": "2026-01-29T06:00:00.000Z", @@ -636,7 +636,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-23T09:19:43.916Z", "resolved_inferred": false, "started_at": "2026-01-23T03:05:48.436Z", @@ -649,7 +649,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-23T02:37:17.841Z", "resolved_inferred": false, "started_at": "2026-01-23T00:24:03.177Z", diff --git a/api/v/esa.json b/api/v/esa.json index 3a4c744ef19012d709abb7dd2665dba03cfa7981..c12b353246e7127f1eb5ee290c7f3a7ffed24468 100644 --- a/api/v/esa.json +++ b/api/v/esa.json @@ -3,7 +3,7 @@ "slug": "esa", "platform": "statuspage", "status_url": "https://status.esa.io", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-21T21:02:07.288+09:00", "resolved_inferred": false, "started_at": "2026-05-21T20:31:31.000+09:00", diff --git a/api/v/eset.json b/api/v/eset.json index 8ba60cb0df92b58241f4001fde2c2f5d698590a3..73e895444e57801c12c0e87f83036f28d3a36f18 100644 --- a/api/v/eset.json +++ b/api/v/eset.json @@ -3,7 +3,7 @@ "slug": "eset", "platform": "statuspage", "status_url": "https://status.eset.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -25,7 +25,7 @@ "body": "On 3 September at 13:10, a fix was successfully deployed. All affected instances should now be accessible and operating normally. Since the deployment, no new reports of the issue have been received, indicating that the incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-09-04T10:07:43.658+02:00", "resolved_inferred": false, "started_at": "2026-09-03T12:48:30.901+02:00", @@ -38,7 +38,7 @@ "body": "The incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-14T13:59:02.323+02:00", "resolved_inferred": false, "started_at": "2026-08-14T10:28:52.548+02:00", @@ -51,7 +51,7 @@ "body": "The incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-06T12:07:11.758+02:00", "resolved_inferred": false, "started_at": "2026-08-04T09:25:09.200+02:00", @@ -64,7 +64,7 @@ "body": "A fix has been deployed, according to SLA monitoring EP, EEIC and ECOS in US seem to have recovered.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-24T10:04:58.237+02:00", "resolved_inferred": false, "started_at": "2026-07-23T18:30:08.000+02:00", @@ -77,7 +77,7 @@ "body": "The issue should be resolved and the functionality restored.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-07T19:02:59.722+02:00", "resolved_inferred": false, "started_at": "2026-07-07T09:14:56.454+02:00", @@ -90,7 +90,7 @@ "body": "We are aware of an issue with the Telia internet service provider that prevents customers from accessing ESET Cloud Services. We will provide updates in due course.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "started_at": "2026-06-29T13:40:41.500+02:00", "state": "investigating", "title": "Customers connected via Telia ISP cannot connect to ESET Cloud Services", @@ -101,7 +101,7 @@ "body": "The situation has now been formally resolved, and all affected services have been fully restored to normal operational status", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-15T12:30:57.972+02:00", "resolved_inferred": false, "started_at": "2026-06-03T11:47:48.663+02:00", @@ -114,7 +114,7 @@ "body": "The issue was resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-05T09:12:58.863+02:00", "resolved_inferred": false, "started_at": "2026-05-04T16:15:09.382+02:00", @@ -127,7 +127,7 @@ "body": "The issue has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-04T10:56:49.336+02:00", "resolved_inferred": false, "started_at": "2026-04-30T17:18:13.014+02:00", @@ -140,7 +140,7 @@ "body": "The issue has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-20T15:05:28.954+02:00", "resolved_inferred": false, "started_at": "2026-04-20T10:15:08.841+02:00", @@ -153,7 +153,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-13T20:03:38.587+01:00", "resolved_inferred": false, "started_at": "2026-03-13T13:20:10.960+01:00", @@ -166,7 +166,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-10T20:49:54.456+01:00", "resolved_inferred": false, "started_at": "2026-03-10T10:40:48.104+01:00", @@ -179,7 +179,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-09T10:12:59.008+01:00", "resolved_inferred": false, "started_at": "2026-03-06T15:23:49.000+01:00", @@ -192,7 +192,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-04T09:26:42.386+01:00", "resolved_inferred": false, "started_at": "2026-03-04T08:59:38.698+01:00", @@ -205,7 +205,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-18T15:19:20.376+01:00", "resolved_inferred": false, "started_at": "2026-02-18T11:25:35.421+01:00", @@ -218,7 +218,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-02T12:29:51.739+01:00", "resolved_inferred": false, "started_at": "2026-01-30T13:47:45.518+01:00", @@ -231,7 +231,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-30T20:19:56.490+01:00", "resolved_inferred": false, "started_at": "2026-01-29T20:43:54.220+01:00", @@ -244,7 +244,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-26T11:36:05.101+01:00", "resolved_inferred": false, "started_at": "2026-01-23T21:36:51.859+01:00", @@ -257,7 +257,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-21T15:13:57.621+01:00", "resolved_inferred": false, "started_at": "2026-01-21T09:58:17.130+01:00", @@ -270,7 +270,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-12T18:47:15.348+01:00", "resolved_inferred": false, "started_at": "2025-12-12T12:36:42.967+01:00", @@ -283,7 +283,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-12T10:08:37.119+01:00", "resolved_inferred": false, "started_at": "2025-12-11T12:20:39.133+01:00", @@ -296,7 +296,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-10T20:14:30.889+01:00", "resolved_inferred": false, "started_at": "2025-12-10T13:59:01.811+01:00", @@ -309,7 +309,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-18T10:13:37.569+01:00", "resolved_inferred": false, "started_at": "2025-11-13T11:24:56.628+01:00", @@ -322,7 +322,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-17T11:07:36.176+01:00", "resolved_inferred": false, "started_at": "2025-11-12T22:30:37.242+01:00", @@ -335,7 +335,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-08T08:36:04.513+01:00", "resolved_inferred": false, "started_at": "2025-11-07T16:55:06.466+01:00", @@ -348,7 +348,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-05T17:39:48.825+01:00", "resolved_inferred": false, "started_at": "2025-11-05T10:45:23.000+01:00", @@ -361,7 +361,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-20T17:19:39.033+02:00", "resolved_inferred": false, "started_at": "2025-10-20T13:01:46.647+02:00", @@ -374,7 +374,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-20T13:13:59.946+02:00", "resolved_inferred": false, "started_at": "2025-10-20T11:13:02.678+02:00", @@ -387,7 +387,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-20T10:35:37.570+02:00", "resolved_inferred": false, "started_at": "2025-10-17T13:32:06.000+02:00", @@ -400,7 +400,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-08T16:40:23.677+02:00", "resolved_inferred": false, "started_at": "2025-10-08T12:51:04.201+02:00", @@ -413,7 +413,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-25T09:49:04.837+02:00", "resolved_inferred": false, "started_at": "2025-09-16T18:46:57.193+02:00", @@ -426,7 +426,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-19T17:32:45.110+02:00", "resolved_inferred": false, "started_at": "2025-08-19T12:27:45.215+02:00", @@ -439,7 +439,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-14T12:55:05.067+02:00", "resolved_inferred": false, "started_at": "2025-08-14T12:34:28.927+02:00", @@ -452,7 +452,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-13T18:10:03.666+02:00", "resolved_inferred": false, "started_at": "2025-08-13T12:08:21.959+02:00", diff --git a/api/v/etherscan.json b/api/v/etherscan.json index dedf745b8ebcd1b152d8baa7ccd5118d5f4f6548..0f4b693c5ad3a8e89d93b8244c3c49a9f4d71d39 100644 --- a/api/v/etherscan.json +++ b/api/v/etherscan.json @@ -3,7 +3,7 @@ "slug": "etherscan", "platform": "status.io", "status_url": "https://etherscan.freshstatus.io", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "unknown", "history_backfilled": false, "first_watched": "2026-09-04T07:06:16Z", diff --git a/api/v/etoro.json b/api/v/etoro.json index 4bb00dd37af7d5c555718c4e62fecd596c7f081d..59f1a6db285fa3b4ac72de850424ba93cb7157a0 100644 --- a/api/v/etoro.json +++ b/api/v/etoro.json @@ -3,7 +3,7 @@ "slug": "etoro", "platform": "statuspage", "status_url": "https://status.etoro.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "The issue affecting outbound payments from eToro Money has now been resolved.\n\nAll outbound payments are now fully enabled, and clients can complete their transactions as expected.\n\nWe sincerely apologize for the inconvenience and appreciate your patience while our team worked to resolve the issue.\n\nThank you for your understanding.\n\nSincerely,\nThe eToro Team", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-07T14:09:29.294Z", "resolved_inferred": false, "started_at": "2026-08-07T08:41:12.754Z", @@ -25,7 +25,7 @@ "body": "The issue affecting credit card deposits has now been resolved.\n\nCustomers can now enter their credit card details and complete deposits as expected.\n\nWe sincerely apologize for the inconvenience and appreciate your patience while our team worked to resolve the issue.\n\nThank you for your understanding.\n\nSincerely,\nThe eToro Team", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-07T14:13:51.959Z", "resolved_inferred": false, "started_at": "2026-07-07T13:45:28.633Z", @@ -38,7 +38,7 @@ "body": "We've restored all affected services, and the customer impact has been mitigated.\n\nDeposits, withdrawals, and the ability to open new positions are now functioning normally. Our team will continue to closely monitor the platform to ensure everything remains stable.\n\nWe sincerely apologize for the disruption and thank you for your patience and understanding throughout this incident.\n\nSincerely,\nThe eToro Team", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-28T17:12:34.199Z", "resolved_inferred": false, "started_at": "2026-06-28T13:20:11.757Z", @@ -51,7 +51,7 @@ "body": "Dear Customers,\n\nThe issue has been resolved. \n\nWe apologize for the inconvenience and appreciate your understanding in this matter.\n\nSincerely,\nThe eToro Team", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-25T15:16:19.603Z", "resolved_inferred": false, "started_at": "2026-06-25T14:21:57.000Z", @@ -64,7 +64,7 @@ "body": "Dear eToro Customers and Partners,\nThe incident has been resolved.\nWe apologize for the inconvenience and appreciate your understanding in this matter.\n\nSincerely, \nThe eToro Team", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-25T09:05:24.528Z", "resolved_inferred": false, "started_at": "2026-06-25T08:07:15.678Z", @@ -77,7 +77,7 @@ "body": "Dear eToro Customers and Partners,\n\nThe incident has been resolved.\n\nWe apologize for the inconvenience and appreciate your understanding in this matter.\n\nSincerely, \nThe eToro Team", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-23T12:11:38.199Z", "resolved_inferred": false, "started_at": "2026-06-23T09:29:24.291Z", @@ -90,7 +90,7 @@ "body": "The issue affecting some pages in the iOS app has been resolved.\n\nA hotfix was deployed, and our QA team has verified that it successfully restored functionality for the affected pages, including the Deposit, Registration, and News pages.\n\nWe apologize for any inconvenience this may have caused and appreciate your patience while we worked to resolve the issue.\n\nSincerely,\nThe eToro Team", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-20T05:16:38.556Z", "resolved_inferred": false, "started_at": "2026-06-19T17:45:55.839Z", @@ -103,7 +103,7 @@ "body": "Dear eToro Customers and Partners,\n\nThe incident has been resolved.\n\nWe apologize for the inconvenience and appreciate your understanding in this matter.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-11T20:59:51.456Z", "resolved_inferred": false, "started_at": "2026-06-11T17:53:40.598Z", @@ -116,7 +116,7 @@ "body": "Dear eToro Customers and Partners,\n \nThe incident has been resolved. Clients can now fully manage limit (rate) orders placed during the incident, including:\n- Canceling existing limit orders;\n- Having limit orders executed normally once the requested market rate is reached.\n\nWe apologize for the inconvenience and appreciate your understanding.\n\nSincerely, \nThe eToro Team", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-11T13:38:03.300Z", "resolved_inferred": false, "started_at": "2026-05-11T09:39:17.313Z", @@ -129,7 +129,7 @@ "body": "Dear eToro Customers and Partners,\n\nThe incident has been resolved.\n\nWe apologize for the inconvenience and appreciate your understanding in this matter.\n\nSincerely, \nThe eToro Team", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-29T17:59:37.189Z", "resolved_inferred": false, "started_at": "2026-04-29T15:24:41.564Z", @@ -142,7 +142,7 @@ "body": "Dear eToro Customers and Partners,\n\nThe incident has been resolved.\n\nWe apologize for the inconvenience and appreciate your understanding in this matter.\n\nSincerely, \nThe eToro Team", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-27T20:31:21.045Z", "resolved_inferred": false, "started_at": "2026-04-27T19:36:53.912Z", @@ -155,7 +155,7 @@ "body": "Dear eToro Customers and Partners,\n\nThe incident has been resolved.\n\nWe apologize for the inconvenience and appreciate your understanding in this matter.\n\nSincerely, \nThe eToro Team", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-30T11:21:54.230Z", "resolved_inferred": false, "started_at": "2026-03-30T10:41:37.896Z", @@ -168,7 +168,7 @@ "body": "Dear eToro Customers and Partners,\n\nThe incident has been resolved.\n\nWe apologize for the inconvenience and appreciate your understanding in this matter.\n\nSincerely, \nThe eToro Team", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-17T13:24:42.840Z", "resolved_inferred": false, "started_at": "2026-03-17T11:14:10.911Z", @@ -181,7 +181,7 @@ "body": "Dear eToro Customers and Partners,\n\nThe incident has been resolved.\n\nWe apologize for the inconvenience and appreciate your understanding in this matter.\n\nSincerely, \nThe eToro Team", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-15T14:36:36.278Z", "resolved_inferred": false, "started_at": "2026-03-15T14:27:14.000Z", @@ -194,7 +194,7 @@ "body": "Dear eToro Customers and Partners,\n\nThe incident has been resolved.\n\nWe apologize for the inconvenience and appreciate your understanding in this matter.\n\nSincerely, \nThe eToro Team", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-24T06:29:17.947Z", "resolved_inferred": false, "started_at": "2026-02-22T19:48:37.091Z", @@ -207,7 +207,7 @@ "body": "Dear eToro Customers,\n\nThe incident has been resolved.\n\nWe apologize for the inconvenience and appreciate your understanding in this matter.\n\nSincerely, \nThe eToro Team", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-22T15:06:49.443Z", "resolved_inferred": false, "started_at": "2026-02-22T12:17:56.634Z", @@ -220,7 +220,7 @@ "body": "Dear eToro Customers and Partners,\n\nThe incident has been resolved.\n\nWe apologize for the inconvenience and appreciate your understanding in this matter.\n\nSincerely, \nThe eToro Team", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-18T14:30:06.495Z", "resolved_inferred": false, "started_at": "2025-11-18T13:53:06.761Z", @@ -233,7 +233,7 @@ "body": "Dear eToro Customers and Partners,\n\nThe incident has been resolved.\n\nWe apologize for the inconvenience and appreciate your understanding in this matter.\n\nSincerely, \nThe eToro Team", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-21T10:32:30.065Z", "resolved_inferred": false, "started_at": "2025-10-21T10:18:03.184Z", diff --git a/api/v/exa.json b/api/v/exa.json index 438b17b5d1fc031bf7c90fce093ebce819ea6f83..5ffd2f9fd5c54e57679b74489376ebf2ee59ab29 100644 --- a/api/v/exa.json +++ b/api/v/exa.json @@ -3,7 +3,7 @@ "slug": "exa", "platform": "status.io", "status_url": "http://exa.freshstatus.io", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "unknown", "history_backfilled": false, "first_watched": "2026-09-04T07:06:16Z", diff --git a/api/v/exact.json b/api/v/exact.json index 7bf6f888f31692c45233f8f9b0a60ea75a13d326..a43a54824ac36499d5cb074fc01c4fb369ee3035 100644 --- a/api/v/exact.json +++ b/api/v/exact.json @@ -3,16 +3,27 @@ "slug": "exact", "platform": "statuspage", "status_url": "https://status.exact.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "degraded", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", "incidents": [ { +"body": "Emails sent from Exact Online may be delayed or not delivered. This includes but is not limited to password reset emails, invoices and reminders. Please refrain from resending messages until further notice to prevent duplicates. We are investigating this issue. This page will be updated as more information becomes available. Our apologies for the inconvenience.", +"first_seen": "2026-09-04T10:17:20Z", +"impact": "minor", +"last_seen": "2026-09-04T10:17:20Z", +"started_at": "2026-09-04T11:17:16.137+02:00", +"state": "investigating", +"title": "Exact Online - Emails delayed or not delivered (Global)", +"updated_at": "2026-09-04T11:32:25.531+02:00", +"url": "https://stspg.io/z8v95yy2tpzw" +}, +{ "body": "You may experience that delivery of an email, sent from Gripp to a recipient with an email address on a Microsoft domain, i.e. Outlook, will be delayed or fail. We are currently investigating this issue and will update this page as soon as more information is available. Our apologies for the inconvenience.", "first_seen": "2026-09-04T08:27:10Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "started_at": "2026-09-04T10:26:52.345+02:00", "state": "investigating", "title": "Exact Gripp - Emails delayed or not getting delivered to Microsoft mail-domains (NL/BE)", @@ -23,7 +34,7 @@ "body": "This issue has been resolved. The transactions from the affected period have now been successfully imported for most customers.\nFor a small number of customers, the remaining transactions are expected to be imported later today.\nIf you notice that some historical transactions are still missing tomorrow, you can retrieve them manually.\n\nFirst, please try selecting \"Retrieve Transactions\" via \"Manage Bank Connection\" from your bank account settings in Reeleezee.\nIf the missing transactions are still not displayed, you can download a CAMT.053 file containing the missing transactions from your online banking environment and import it into Reeleezee via the bank overview.\nOur apologies for the inconvenience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-09-03T15:44:31.148+02:00", "resolved_inferred": false, "started_at": "2026-09-02T11:19:01.007+02:00", @@ -36,7 +47,7 @@ "body": "The issue has been resolved. All Exact Online environments are available and work as intended again. Our apologies for the inconvenience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-09-02T14:06:12.938+02:00", "resolved_inferred": false, "started_at": "2026-09-02T09:20:35.000+02:00", @@ -49,7 +60,7 @@ "body": "The issue has been identified and a fix is being implemented.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "started_at": "2026-09-01T15:00:46.631+02:00", "state": "identified", "title": "Exact Online - EOL app 7.3 - Warning 'Invalid: Execution date' (NL)", @@ -60,7 +71,7 @@ "body": "This issue occurs when the company name contains a comma (,). In addition, the issue appears to affect Google Chrome and has not been reported in other browsers.\n\nAs a workaround, you can either:\n- Remove the comma from the company name, or\n- Perform the export using a different browser than Google Chrome.\n\nWe continue to investigate the underlying cause and will update this page as soon as more information becomes available.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "started_at": "2026-09-01T11:25:23.460+02:00", "state": "identified", "title": "Exact Online - Unable to export to Excel through overviews (Global)", @@ -71,7 +82,7 @@ "body": "This issue has been resolved and the purchase invoices that were sent have now been received in the digital postbox.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-09-01T13:18:26.103+02:00", "resolved_inferred": false, "started_at": "2026-09-01T10:27:59.477+02:00", @@ -84,7 +95,7 @@ "body": "This issue has been resolved. Our apologies for the inconvenience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-30T19:58:38.685+02:00", "resolved_inferred": false, "started_at": "2026-08-29T21:17:56.616+02:00", @@ -97,7 +108,7 @@ "body": "This issue has been resolved. Our apologies for the inconvenience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-09-04T11:00:32.220+02:00", "resolved_inferred": false, "started_at": "2026-08-28T11:41:31.810+02:00", @@ -110,7 +121,7 @@ "body": "The issue has been identified and a fix is being implemented.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "started_at": "2026-08-26T16:40:26.507+02:00", "state": "identified", "title": "Exact Online - New SSO users can't be created (Global)", @@ -121,7 +132,7 @@ "body": "This issue has been resolved and the percentage for 'Premie AOW' is correct again in this scenario. We urge you to verify whether the tax return has been correctly filled in according to the requirements of the Tax Authorities. Our apologies for the inconvenience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-09-04T10:23:09.092+02:00", "resolved_inferred": false, "started_at": "2026-08-25T16:16:16.941+02:00", @@ -134,7 +145,7 @@ "body": "The issue has been resolved. Our apologies for the inconvenience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-25T13:52:53.332+02:00", "resolved_inferred": false, "started_at": "2026-08-25T10:39:54.234+02:00", @@ -147,7 +158,7 @@ "body": "On certain occasions, the migration to Microsoft Authenticator cannot be executed. In those cases, you can perform a reset of your two factor authentication (2FA) by opening an InPrivate/Incognito browser session and complete the setup via Microsoft Security Information Setup.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "started_at": "2026-08-25T08:27:58.556+02:00", "state": "identified", "title": "Exact HR & Salaris Gemak / Exact Venice / Exact Multivers / Exact Cloud Services - SMS-authentication disabled as two factor authentication method (Global)", @@ -158,7 +169,7 @@ "body": "The issue has been resolved. From now on, when updating your E-invoice subscription, the status will be updated. If the E-invoice subscription status is currently incorrect you can correct it by deactivating and reactivating an option in the subscription. Our apologies for the inconvenience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-25T08:25:19.337+02:00", "resolved_inferred": false, "started_at": "2026-08-24T15:21:45.095+02:00", @@ -171,7 +182,7 @@ "body": "The API update (V1) has been rolled back, meaning the previous situation is now restored. The issues should not present themselves anymore. Our apologies for the inconvenience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-24T11:46:30.022+02:00", "resolved_inferred": false, "started_at": "2026-08-21T10:54:03.197+02:00", @@ -184,7 +195,7 @@ "body": "A fix is made available in Exact Globe Next Release 424SP46 as of the 1st of September 2026 for the Dutch and English language. We continue to work on a resolution for the other languages for Exact Globe Next. To apply the fix, update to this version after the mentioned date.\nA fix is already available for Exact Globe+ releases 507SP3, 506SP12 and 505SP19 as of the 27th of August.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "started_at": "2026-08-21T08:23:24.386+02:00", "state": "identified", "title": "Exact Globe+ - Excel Add-In returns error when started on Office build 2608.", @@ -195,7 +206,7 @@ "body": "This issue has been resolved. Our apologies for the inconvenience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-20T15:49:06.027+02:00", "resolved_inferred": false, "started_at": "2026-08-20T12:41:25.387+02:00", @@ -208,7 +219,7 @@ "body": "This issue has been resolved. Our apologies for the inconvenience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-24T10:01:19.680+02:00", "resolved_inferred": false, "started_at": "2026-08-20T10:21:01.000+02:00", @@ -221,7 +232,7 @@ "body": "The issue has been identified and we are working on a fix.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "started_at": "2026-08-18T14:43:45.957+02:00", "state": "identified", "title": "Exact Online - Deduplication not finding double accounts (NL/BE)", @@ -232,7 +243,7 @@ "body": "This issue has been resolved. Our apologies for the inconvenience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-20T10:04:18.448+02:00", "resolved_inferred": false, "started_at": "2026-08-18T12:55:39.575+02:00", @@ -245,7 +256,7 @@ "body": "This issue has been resolved and you can set the client relationship to \"Tot op heden\" again. The client will also be visible again in the client overview with an active client relationship if the end date is set in the future or is set to \"Tot op heden\". Our apologies for the inconvenience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-20T10:26:57.187+02:00", "resolved_inferred": false, "started_at": "2026-08-17T16:00:35.385+02:00", @@ -258,7 +269,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-20T11:05:17.620+02:00", "resolved_inferred": false, "started_at": "2026-08-17T11:08:25.103+02:00", @@ -271,7 +282,7 @@ "body": "This issue has been resolved. Our apologies for the inconvenience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-13T09:52:57.062+02:00", "resolved_inferred": false, "started_at": "2026-08-13T08:49:56.298+02:00", @@ -284,7 +295,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-24T09:55:36.589+02:00", "resolved_inferred": false, "started_at": "2026-08-12T15:22:40.983+02:00", @@ -297,7 +308,7 @@ "body": "The issue with approving invoices in Exact Multivers Online and Exact Boekhoud Gemak has been resolved. Invoices can be approved as usual again. Our apologies for the inconvenience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-14T08:09:57.822+02:00", "resolved_inferred": false, "started_at": "2026-08-11T15:25:12.000+02:00", @@ -310,7 +321,7 @@ "body": "This issue is now resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-11T11:38:31.705+02:00", "resolved_inferred": false, "started_at": "2026-08-11T09:05:58.000+02:00", @@ -323,7 +334,7 @@ "body": "This issue has been resolved. If you have temporarily enabled the right \u201ckoppelingen instellen\u201d in the category \u201calgemeen account\u201d as a workaround, we advise you to disable this right again. Our apologies for the inconvenience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-14T09:09:44.587+02:00", "resolved_inferred": false, "started_at": "2026-08-10T13:08:40.230+02:00", @@ -336,7 +347,7 @@ "body": "This issue is now resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-12T08:19:16.883+02:00", "resolved_inferred": false, "started_at": "2026-08-07T14:14:09.628+02:00", @@ -349,7 +360,7 @@ "body": "This issue has been resolved. Our apologies for the inconvenience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-14T08:55:02.349+02:00", "resolved_inferred": false, "started_at": "2026-08-07T10:49:48.406+02:00", @@ -362,7 +373,7 @@ "body": "This issue has been resolved. Our apologies for the inconvenience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-06T11:45:06.752+02:00", "resolved_inferred": false, "started_at": "2026-08-06T10:12:07.755+02:00", @@ -375,7 +386,7 @@ "body": "This issue has been resolved, payment files containing more than one payment date will no longer be rejected. Our apologies for the inconvenience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-12T09:52:17.472+02:00", "resolved_inferred": false, "started_at": "2026-08-06T09:17:54.023+02:00", @@ -388,7 +399,7 @@ "body": "This issue has been resolved and documents can be successfully archived to Hyarchis again. If your document is not automatically resent, you can archive the document manually by clicking on the three dots next to 'Jaarrekening openen' > 'Archiveren' on the project page. Our apologies for the inconvenience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-18T09:12:32.333+02:00", "resolved_inferred": false, "started_at": "2026-08-05T16:50:58.359+02:00", @@ -401,7 +412,7 @@ "body": "This issue has been resolved. You can now open entry proposals again, even those you haven\u2019t had regenerated. Our apologies for the inconvenience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-07T09:35:14.504+02:00", "resolved_inferred": false, "started_at": "2026-08-05T10:25:03.000+02:00", @@ -414,7 +425,7 @@ "body": "The issue has been resolved", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-06T15:11:25.078+02:00", "resolved_inferred": false, "started_at": "2026-08-05T08:50:56.682+02:00", @@ -427,7 +438,7 @@ "body": "This issue has been resolved. Our apologies for the inconvenience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-04T13:27:09.043+02:00", "resolved_inferred": false, "started_at": "2026-08-03T13:27:27.448+02:00", @@ -440,7 +451,7 @@ "body": "This issue has been resolved. The gift tax return 2026 can be submitted to the Tax Authorities without an error message. This also applies to the scenarios where the contact person is a legal entity, and you have checked this box. Our apologies for the inconvenience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-03T11:13:29.390+02:00", "resolved_inferred": false, "started_at": "2026-07-31T13:16:57.350+02:00", @@ -453,7 +464,7 @@ "body": "This issue has been resolved. Please note that tasks created between 9:00 a.m. CEST and 2:30 p.m. CEST on July 30 will not be processed automatically and must be restarted. Our apologies for the inconvenience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-30T16:06:01.533+02:00", "resolved_inferred": false, "started_at": "2026-07-30T13:48:05.399+02:00", @@ -466,7 +477,7 @@ "body": "This issue has been resolved and you will not receive incorrect crash reports anymore. Our apologies for the inconvenience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-30T09:57:56.278+02:00", "resolved_inferred": false, "started_at": "2026-07-30T08:44:39.285+02:00", @@ -479,7 +490,7 @@ "body": "This issue has been resolved. Our apologies for the inconvenience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-29T16:54:55.592+02:00", "resolved_inferred": false, "started_at": "2026-07-29T11:07:56.584+02:00", @@ -492,7 +503,7 @@ "body": "The issue has been resolved and you are able to send VAT and ICP returns again via Exact Multivers. You might need to reopen the returns in order to send the returns again. Our apologies for the inconvenience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-29T11:43:03.707+02:00", "resolved_inferred": false, "started_at": "2026-07-29T10:28:22.662+02:00", @@ -505,7 +516,7 @@ "body": "This issue has been resolved and there is no longer a delay in processing uploaded documents. Our apologies for the inconvenience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-26T11:12:55.123+02:00", "resolved_inferred": false, "started_at": "2026-07-26T09:48:35.649+02:00", @@ -518,7 +529,7 @@ "body": "This issue has been resolved. Our apologies for the inconvenience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-07T09:12:58.305+02:00", "resolved_inferred": false, "started_at": "2026-07-24T10:09:28.966+02:00", @@ -531,7 +542,7 @@ "body": "The Dutch Tax Authorities informed us that the issue is fixed and our software should be able to receive VIA's again.\nOur apologies for the inconvenience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-23T16:28:08.953+02:00", "resolved_inferred": false, "started_at": "2026-07-23T10:48:37.046+02:00", @@ -544,7 +555,7 @@ "body": "This issue has been resolved. Our apologies for the inconvenience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-05T10:00:46.848+02:00", "resolved_inferred": false, "started_at": "2026-07-23T09:30:13.034+02:00", @@ -557,7 +568,7 @@ "body": "This issue has been resolved. When still experiencing performance issues you can delete the cookies and cache in your browser. Our apologies for the inconvenience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-22T16:03:47.283+02:00", "resolved_inferred": false, "started_at": "2026-07-22T15:40:00.283+02:00", @@ -570,7 +581,7 @@ "body": "This issue has been resolved and the message does not get shown incorrectly any longer. If you have temporarily deactivated the right 'View Departments' you can activate this again. Our apologies for the inconvenience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-22T09:46:04.237+02:00", "resolved_inferred": false, "started_at": "2026-07-22T09:06:48.802+02:00", @@ -583,7 +594,7 @@ "body": "This issue has been resolved. When still experiencing performance issues you can delete the cookies and cache in your browser. Our apologies for the inconvenience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-21T16:23:19.085+02:00", "resolved_inferred": false, "started_at": "2026-07-21T09:32:08.000+02:00", @@ -609,7 +620,7 @@ "body": "This issue has been resolved. If you have finalized runs containing the issues you can correct this by creating a correction request for the employees in question and doing an extra run on the period. Our apologies for the inconvenience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-03T14:28:00.807+02:00", "resolved_inferred": false, "started_at": "2026-07-16T14:31:36.544+02:00", @@ -622,7 +633,7 @@ "body": "The issue has been resolved. E-mail notifications are now being sent as expected again. Our apologies for the inconvenience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-26T16:56:39.360+02:00", "resolved_inferred": false, "started_at": "2026-07-14T15:45:19.593+02:00", @@ -635,7 +646,7 @@ "body": "From the investigation of this issue we have found that the changes in behaviour are part of necessary larger changes. Therefore these changes will not be overturned. Please apply the previously communicated workaround as a permanent solution. Our apologies for the inconvenience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-24T12:46:14.598+02:00", "resolved_inferred": false, "started_at": "2026-07-13T10:14:12.049+02:00", @@ -648,7 +659,7 @@ "body": "We are continuing to work on a fix.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "started_at": "2026-06-30T08:40:16.960+02:00", "state": "identified", "title": "Bank links / PSD2 - Status column not updated after authorizing payment files via a PSD2 bank link (NL)", diff --git a/api/v/exalate.json b/api/v/exalate.json index dec58bd4761f2658a9a0eac3cb9b2366c1b7702d..92f2da5a4551a037edeb77d49b05442e766b0e2a 100644 --- a/api/v/exalate.json +++ b/api/v/exalate.json @@ -3,7 +3,7 @@ "slug": "exalate", "platform": "statuspage", "status_url": "https://status.exalate.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "All Atlassian systems are back to normal, and the synchronization is working as expected. \nIn case of any issues with your sync, please create a support ticket and we will be happy to assist.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-27T07:27:28.917+02:00", "resolved_inferred": false, "started_at": "2026-08-27T06:36:21.945+02:00", @@ -25,7 +25,7 @@ "body": "The proxy user name was reverted back to Exalate. \n\nWe are considering the incident as resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-24T18:33:41.433+02:00", "resolved_inferred": false, "started_at": "2026-07-24T08:12:42.939+02:00", @@ -38,7 +38,7 @@ "body": "After close monitoring, the issue is considered as fully resolved. We will be posting a RCA here in due course.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-16T19:18:22.171+02:00", "resolved_inferred": false, "started_at": "2026-07-16T13:28:02.375+02:00", @@ -51,7 +51,7 @@ "body": "**Impact:** Some Classic Exalate for Jira Cloud connections experienced repeated, duplicated synchronisations following an infrastructure migration to Atlassian's Forge platform. On affected connections customers saw:\n\n* **Duplicate activity** \u2014 the same update, comment, or field change applied to an issue over and over as the sync looped.\n* **Reopened / resurrected issues** \u2014 issues that had been closed being reopened, and other status or field values being overwritten back and forth between the paired issues.\n* **Distorted dashboards and reports** driven by the volume of duplicate changes.\n* **Broken automations and workflow validations** \u2014 because the integration user's name \\(and underlying ID\\) changed, customer-side Jira Automation rules and workflow validators that referenced the \"Exalate\" user by name stopped behaving as configured.\n* **Stuck or failed syncs**, and in some cases a connection going down, requiring manual retries or recovery.\n* Increased **manual effort** for teams to unstick syncs and correct affected issues.\n\nNot all customers were affected \u2014 impact depended on connection configuration. The most exposed were local connections and issues that had previously been created or updated under the original \"Exalate\" identity and were then touched under the renamed one.\n\n**Summary:** As part of moving Classic Exalate for Jira Cloud to Atlassian's Forge platform, the name shown for Exalate's integration user inside Jira changed \\(from \"Exalate\" to a longer variant\\). Exalate used that name to recognise its own updates and avoid re-synchronising them. Once the name changed, the app no longer recognised its own writes on affected connections and re-processed them as if they were new external changes \u2014 each write triggering another sync, producing loops. The same identity change also broke customer automations and validations that referenced the \"Exalate\" user by name.\n\n**Resolution:** A patch \\(5.35.4\\) that recognises Exalate's own updates by a stable user identifier rather than the display name was validated on affected customer environments and deployed across the Jira Cloud fleet. Synchronisation returned to normal once deployment completed. Atlassian has since restored and confirmed the integration user's name as \"Exalate\", and it is now stable \u2014 repairing automations that reference it by name. Where loops created duplicate or reopened items, we are working with affected customers to identify and correct the affected issues.\n\n**Preventive measures:** Loop-prevention no longer depends on a changeable display name; we are adding an impact-review and notification step around platform-driven changes and app updates, and automated detection of synchronisation loops and database saturation so recovery does not depend on customer reports.\n\nWe apologise for the disruption and remain committed to the reliability of the Exalate platform.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-15T00:14:53.867+02:00", "resolved_inferred": false, "started_at": "2026-07-14T00:15:07.444+02:00", @@ -64,7 +64,7 @@ "body": "**Duration:** 11:10 CEST - 11:26 CEST \\(approximately 16 minutes\\). Full stability confirmed at 14:47 CEST.\n\n**Impact:** The Exalate.app connection and dashboard pages were inaccessible during this window. Issue synchronisation was not affected - integrations continued to run normally throughout. No data was lost.\n\n**Summary:** On June 23, 2026, the Exalate.app interface became inaccessible after an internal authentication component failed to connect to its database. The failure was caused by a credential mismatch introduced during a production deployment.\n\n**Timeline:**\n\n* 11:10 CEST - Issue detected, investigation initiated\n* 11:26 CEST - Fix deployed, service restored\n* 14:47 CEST - Full stability confirmed\n\n**Root Cause:** During a production deployment on June 19, a database credential was configured independently in two systems. A subtle mismatch was introduced during a subsequent configuration update. The mismatch remained latent because the application maintained existing database connections. A routine GKE maintenance event on June 23 recycled the application, forcing new connections that exposed the mismatch.\n\n**Resolution:** The database credential was aligned and the application was restarted. Service returned to full operation with no data loss.\n\n**Preventive Measures:**\n\n* Post-deployment authentication verification checks have been added to the deployment runbook\n* Alerting for application database connectivity failures has been implemented\n* The credential configuration process is being consolidated to eliminate the dual-system mismatch risk\n\nWe apologize for the disruption. We remain committed to the reliability of the Exalate platform.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-23T14:47:15.232+02:00", "resolved_inferred": false, "started_at": "2026-06-23T11:10:12.633+02:00", @@ -77,7 +77,7 @@ "body": "The system has been under close observation and it has been stable. We will provide a post-mortem to the incident in due course.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-04T23:28:00.549+02:00", "resolved_inferred": false, "started_at": "2026-05-04T15:24:36.446+02:00", @@ -90,7 +90,7 @@ "body": "**Incident:** Exalate.app Not Loading Workspaces - April 15, 2026\n\n**Duration:** 11:03 CEST \u2013 12:16 CEST \\(approximately 73 minutes\\).\n\n**Impact:** The Exalate.app UI was inaccessible during this window. Issue synchronisation was not affected. No data was lost.\n\n**Summary:** On April 15, 2026, the Exalate.app interface became inaccessible following a planned infrastructure credential update. A secondary configuration dependency was not updated as part of the change, preventing the application from connecting to its database.\n\n**Timeline:**\n\n* 11:03 CEST - Issue detected, investigation initiated\n* 11:04 CEST - Root cause identified\n* 12:16 CEST - Fix deployed, service restored\n\n**Root Cause:** A configuration dependency missed during a credential update left the application unable to authenticate to its database. This was related to the April 6 incident; the additional dependency has now been identified and incorporated into the rotation procedure.\n\n**Resolution:** The affected configuration was regenerated and the application was restarted. Service returned to full operation with no data loss.\n\n**Preventive Measures:**\n\n* All credential dependencies have been fully mapped and the rotation procedure updated to cover them as a single atomic operation\n\nWe apologize for the disruption. We remain committed to the reliability of the Exalate platform.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-15T14:16:47.556+02:00", "resolved_inferred": false, "started_at": "2026-04-15T11:03:44.256+02:00", @@ -103,7 +103,7 @@ "body": "**Incident:** Exalate.app Not Loading Workspaces - April 6, 2026\n\n**Duration:** 13:07 CEST - 13:28 CEST \\(approximately 21 minutes\\).\n\n**Impact:** The Exalate.app UI was inaccessible during this window. Issue synchronisation was not affected - integrations continued to run normally throughout. No data was lost.\n\n**Summary:** On April 6, 2026, the Exalate.app interface became inaccessible after an infrastructure credential was rotated as part of a planned security improvement programme. The component responsible for database connectivity caches credentials at startup and does not reload them automatically. The previous credential was removed before the component had been restarted to pick up the new one, causing authentication failures.\n\n**Timeline:**\n\n* 13:07 CEST - Issue detected, investigation initiated\n* 13:28 CEST - Fix deployed, service restored\n\n**Root Cause:** A credential rotation completed out of sequence - the old credential was removed before the consuming component had been restarted with the new one.\n\n**Resolution:** The affected components were restarted with the correct credentials. Service returned to full operation with no data loss.\n\n**Preventive Measures:**\n\n* A credential rotation procedure has been established enforcing a mandatory sequence: update, restart consumers, verify, then remove old credentials\n* Direct monitoring for database connectivity authentication failures is being implemented\n* Migration to automated credential management that eliminates manual rotation for this workload is underway\n\nWe apologize for the disruption. We remain committed to the reliability of the Exalate platform.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-06T17:31:14.304+02:00", "resolved_inferred": false, "started_at": "2026-04-06T13:07:19.702+02:00", @@ -116,7 +116,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-02T23:26:46.402+02:00", "resolved_inferred": false, "started_at": "2026-04-02T17:41:49.000+02:00", @@ -129,7 +129,7 @@ "body": "**Incident:** Exalate Application Unavailability \u2014 March 16, 2026\n\n**Duration:** 16:13 CET \u2013 17:09 CET \\(approximately 56 minutes\\)\n\n**Impact:** The Exalate UI was inaccessible during this window. Issue synchronisation was not affected \u2014 integrations continued to run normally throughout. No data was lost.\n\n**Summary:** On March 16, 2026, the Exalate application became unavailable following a production infrastructure configuration change. A resource allocation adjustment applied to a critical authentication component proved insufficient under production load, causing repeated service interruptions.\n\n**Timeline:**\n\n* 16:13 CET \u2014 Issue reported, investigation initiated\n* 16:56 CET \u2014 Root cause identified, remediation initiated\n* 17:09 CET \u2014 Fix deployed, service restored\n* 18:13 CET \u2014 Full stability confirmed\n\n**Root Cause:** A resource limit adjustment deployed without cross-team review under-provisioned a critical authentication component. Under production load, the platform repeatedly terminated the component, rendering the application inaccessible.\n\n**Resolution:** Resource limits were corrected, restoring service. A further optimisation was applied during a subsequent scheduled maintenance window following joint engineering review.\n\n**Preventive Measures:**\n\n* All production infrastructure configuration changes now require joint sign-off from infrastructure and engineering leads before deployment\n* Resource and capacity parameters validated against production load baselines prior to deployment", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-16T18:13:49.862+01:00", "resolved_inferred": false, "started_at": "2026-03-16T16:13:29.699+01:00", @@ -142,7 +142,7 @@ "body": "**Date:** March 17, 2026 \n**Duration:** 12:10 CET - 15:00 CET \\(2 hours, 50 minutes\\) \n**Impact:** \nThe [exalate.com](http://exalate.com) website was completely inaccessible to all users for the duration of the incident. \n**Summary:** \nThe hosting environment experienced resource exhaustion triggered by a sudden surge in web traffic. This was further exacerbated by a malfunctioning security plugin. \n**Timeline:** \n12:10 CET: Incident start \\(resource exhaustion begins\\) \n12:28 CET: Issue detected \n14:40 CET: Root cause identified \n15:00 CET: Service fully restored \n**Root Cause:** \nA spike in unique visitors has led to resource depletion on the hosting server. During the investigation, it was discovered that an installed security plugin was behaving inefficiently under high load, significantly compounding the CPU and memory usage, preventing the server from recovering. \n**Resolution:** \nIdentified and blocked specific IP addresses responsible for an anomalous volume of requests. \nDeactivated and removed the problematic security plugin. \nImplemented an alternative solution to handle the plugin's core functionality without the performance overhead. \n**Preventive Measures:** \nInvestigate and implement automated rate-limiting and IP blocking solutions \\(e.g., WAF rules\\) to handle traffic spikes.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-13T19:19:19.354+01:00", "resolved_inferred": false, "started_at": "2026-03-13T12:56:32.372+01:00", @@ -155,7 +155,7 @@ "body": "**Incident:** Exalate Cloud Service Disruption - March 9, 2026\n\n**Duration:** 07:30 CET \u2013 08:10 CET \\(approximately 40 minutes\\)\n\n**Impact:** Some Exalate Cloud nodes experienced temporary service disruption. Database write operations were briefly affected. Issue synchronisation resumed automatically once the issue was resolved. No data was lost.\n\n**Summary:** On March 9, 2026, the primary database instance serving part of the Exalate Cloud infrastructure reached full storage capacity. This prevented the database from processing write operations, temporarily impacting node availability.\n\n**Timeline:**\n\n* 07:30 CET - Issue detected, investigation initiated\n* 08:05 CET - Storage expanded, database operations resumed\n* 08:10 CET - Fix verified, nodes confirmed operational\n* 10:00 CET - Full stability confirmed after extended monitoring\n\n**Root Cause:** The primary database storage volume gradually reached full capacity under normal operational growth. Proactive storage monitoring did not fire in time. \n\n**Resolution:** Database storage was expanded and the service returned to full operation automatically. Additional alerting configured.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-09T10:00:15.499+01:00", "resolved_inferred": false, "started_at": "2026-03-09T07:59:15.724+01:00", @@ -168,7 +168,7 @@ "body": "**Incident:** Exalate Application Unavailability \u2014 January 23, 2026\n\n**Duration:** 10:59 CET \u2013 11:18 CET \\(approximately 19 minutes\\)\n\n**Impact:** The Exalate UI was inaccessible during this window. Issue synchronisation was not affected \u2014 integrations continued to run normally throughout. No data was lost.\n\n**Summary:** On January 23, 2026, our monitoring detected a service outage affecting the Exalate application. The root cause was a deployment configuration change that unintentionally removed an active compute resource from the production environment.\n\n**Timeline:**\n\n* 10:59 CET \u2014 Issue detected, investigation initiated\n* 11:18 CET \u2014 Fix deployed, service restored\n* 13:18 CET \u2014 Full stability confirmed\n\n**Root Cause:** A deployment configuration change targeted the wrong resource section, resulting in an active production compute resource being removed and the application becoming inaccessible.\n\n**Resolution:** The affected resource was recreated and all services returned to full operation with no data loss.\n\n**Preventive Measures:**\n\n* Infrastructure-as-code changes must be validated in a non-production environment before production deployment\n* Peer review steps introduced to verify configuration targets prior to execution", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-23T13:18:08.623+01:00", "resolved_inferred": false, "started_at": "2026-01-23T10:59:34.897+01:00", @@ -181,7 +181,7 @@ "body": "**Incident: Service Outage - December 12, 2025**\n\n**Duration:** 16:35 CET - 03:01 CET \\(approximately 10 hours\\)\n\n**Impact:** A significant number of Exalate Cloud nodes experienced service unavailability, resulting in temporary disruption to data synchronization services. No data was lost during this incident.\n\n**Summary:** On December 12, 2025, our infrastructure monitoring detected a service outage affecting Exalate Cloud customers on our production clusters. The root cause was identified as a storage system failure triggered by network latency on a legacy infrastructure component, which caused storage connectivity issues for customer workloads.\n\n**Timeline:**\n\n* 16:35 CET - Issue detected by monitoring systems\n* 17:31 CET - Root cause identified, restoration initiated\n* 21:20 CET - Majority of nodes restored to service\n* 03:01 CET - Full service restoration confirmed\n\n**Root Cause:** A storage management component became unresponsive due to elevated network latency caused by a legacy networking layer. This resulted in storage disconnection for customer workloads. \n\n**Resolution:** The storage system was restored, all affected workloads were rescheduled, and the external dependency was updated to a supported version. All nodes were returned to full operation with no data loss.\n\n**Preventive Measures:**\n\n* Deploying patches to address the storage component stability issue\n* Accelerating migration away from the legacy networking layer to modern infrastructure\n* Implementing internal mirroring of critical external dependencies to eliminate reliance on third-party availability\n* Enhancing operational safeguards for infrastructure management procedures\n\nWe sincerely apologize for the disruption this incident caused. Our team remains committed to improving the reliability and resilience of the Exalate Cloud platform.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-13T05:26:23.891+01:00", "resolved_inferred": false, "started_at": "2025-12-12T17:15:42.392+01:00", @@ -194,7 +194,7 @@ "body": "**Incident: Service Degradation - November 27, 2025**\n\n**Duration:** 11:26 CET - 21:37 CET \\(~10 hours\\)\n\n**Impact:** Approximately 700 Exalate Cloud nodes experienced intermittent connectivity issues, resulting in temporary disruption to data synchronization services. No data was lost during this incident.\n\n**Summary:** On November 27, 2025, our infrastructure monitoring detected service degradation affecting a subset of Exalate Cloud customers. The root cause was identified as storage I/O contention on the underlying database infrastructure, which caused the primary database to become unresponsive intermittently.\n\n**Timeline:**\n\n* 11:26 CET - Issue detected by monitoring systems\n* 11:30 CET - Engineering team began investigation\n* 15:30 CET - Initial mitigation applied \\(infrastructure scaling\\)\n* 18:30 CET - Root cause identified and permanent remediation initiated\n* 21:37 CET - Full service restoration confirmed\n\n**Root Cause:** Database storage was experiencing resource contention due to shared infrastructure components, causing elevated I/O latency. This triggered automated health checks to restart the database service repeatedly, compounding the connectivity issues.\n\n**Resolution:** The database was migrated to dedicated storage resources and allocated additional compute capacity. All affected nodes were restored to full operation with no data loss.\n\n**Preventive Measures:**\n\n* Implementing enhanced storage latency monitoring and alerting\n* Reviewing infrastructure health check configurations for database workloads\n* Auditing storage allocation across all database clusters to prevent similar contention\n\nWe apologize for any inconvenience this incident may have caused. Our team remains committed to maintaining the reliability and performance of the Exalate Cloud platform.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-28T08:08:51.590+01:00", "resolved_inferred": false, "started_at": "2025-11-27T12:47:06.787+01:00", @@ -207,7 +207,7 @@ "body": "timeout", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-20T12:23:51.183+01:00", "resolved_inferred": false, "started_at": "2025-11-20T10:43:55.000+01:00", @@ -220,7 +220,7 @@ "body": "## **Summary**\n\nOn October 4, 2025, Exalate Cloud experienced an issue that caused some Exalate nodes to become temporarily inaccessible at 04:00 CEST. This resulted in UI access issues and potential synchronization interruptions for part of our customer base. All services were fully restored by 09:00 CEST.\n\n## **Impact**\n\nCustomers using Exalate cloud nodes experienced:\n\n* Inability to access nodes\n* Sync failures or delays\n* Temporary disruption of workflow automations\n\nNo data loss occurred.\n\n## **Root Cause**\n\nThere was an error in the certification renewal process. This prevented affected nodes from completing required secure connections, making them temporarily unreachable.\n\n## **Resolution**\n\nAfter identifying the cause, the certificate was renewed and deployed. Services began recovering immediately and full functionality was validated shortly thereafter.\n\n## **Preventive Measures**\n\nWe are implementing several improvements to prevent recurrence, including:\n\n* Expanded automated monitoring for certificate validity\n* Additional service health checks, including customer-facing endpoints\n* Automated renewal processes for critical certificates\n* Strengthened operational procedures around certificate lifecycle management", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-04T08:54:10.810+02:00", "resolved_inferred": false, "started_at": "2025-10-04T08:18:30.901+02:00", @@ -233,7 +233,7 @@ "body": "timeout", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-05T15:17:11.347+01:00", "resolved_inferred": false, "started_at": "2025-10-03T11:43:15.924+02:00", @@ -246,7 +246,7 @@ "body": "## Executive Summary\n\nOn September 24, 2025, Exalate experienced a service interruption lasting 17 hours and 28 minutes that affected our cloud-hosted integration nodes. During this time, customers were unable to synchronize data between their integrated systems. **No customer data was lost.** We sincerely apologize for the inconvenience and want to share what happened and how we're preventing future issues.\n\n## What Happened\n\n**Timeline:**\n\n* **10:02 UTC \\(Sept 24\\):** Infrastructure issue detected through customer reports\n* **13:00 UTC:** Partial service restoration achieved\n* **13:45 UTC:** Secondary technical issue caused complete service unavailability\n* **17:24 UTC:** Core infrastructure restored\n* **21:00 UTC:** Priority customer services online\n* **03:30 UTC \\(Sept 25\\):** Full service restoration completed\n\n**Root Cause:** A network connectivity issue on our hosting platform triggered a cascading infrastructure failure. The recovery process was complex due to database resilience challenges and infrastructure management system complications.\n\n## Customer Impact\n\n**During the outage:**\n\n* Data synchronization between systems \\(Jira, ServiceNow, etc.\\) was unavailable\n* Automated workflow processes were temporarily halted\n\n**What was NOT affected:**\n\n* **No customer data was lost or corrupted**\n* All existing synchronized data remained intact\n* Customer configurations and sync histories were preserved\n\n## Our Response\n\nWe immediately activated our 24/7 incident response team, maintained continuous status page updates, directly contacted Enterprise customers, and coordinated with infrastructure providers throughout the recovery.\n\n## Prevention Measures\n\nWe're implementing comprehensive improvements on an accelerated timeline:\n\n**Immediate \\(October 2025\\):**\n\n* Enhanced infrastructure monitoring and alerting systems\n* Comprehensive disaster recovery documentation\n\n**Short-term \\(November 2025\\):**\n\n* Infrastructure resilience improvements\n* Automated recovery procedures\n* Regular disaster recovery testing\n\n**Medium-term \\(Q1 2026\\):**\n\n* Multi-cloud architecture implementation\n* Advanced predictive monitoring\n\n## Customer Support\n\nIf you need assistance related to this outage:\n\n* **Enterprise Customers:** Use your dedicated support channels\n* **Standard Support:** Submit tickets through our support portal\n* **Status Updates:** Monitor our status page for ongoing information\n\nWe apologize for this service disruption and appreciate your patience. Your trust is essential to our business, and we're committed to earning it through reliable service delivery and continuous improvement.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-25T16:21:59.869+02:00", "resolved_inferred": false, "started_at": "2025-09-24T12:56:38.160+02:00", @@ -259,7 +259,7 @@ "body": "# Exalate v5.28 Issue Links Synchronization - Technical Incident Report\n\n**Incident Date:** 29/Aug/2025 \n**Duration:** ~4 hours from detection to rollback completion \n**Impact:** Issue link synchronization behavior change affecting multiple customer instances \n**Status:** Resolved with data restoration completed\n\n## Timeline\n\nThe incident was first detected\u00a0 on 29/Aug at 17:56 when a customer reported issue links being removed after upgrading to v5.28. Within eight minutes, at 18:04, the support team received multiple similar reports and immediately requested a rollback. The formal incident response was initiated at 18:17, and the rollback process to v5.27.0 began at 18:48. The rollback was completed across all affected instances by 22:12 the same day, approximately four hours after initial detection.\n\nRecovery efforts continued over the weekend. On 30/Aug at 09:43, the data restoration team was assembled and began developing recovery procedures. The comprehensive customer communication deployment occurred on 01/Sep at 17:05, providing affected customers with restoration instructions and individualized support. \n_\\(All times CET\\)_\n\n\u200c\n\n\u200c\n\n## Root Cause Analysis\n\nThe technical issue stemmed from a synchronization enhancement in v5.28 that compared issue links between source and destination systems. The implementation operated under the assumption that links present on the destination but not on the source represented synchronization inconsistencies requiring removal. This approach failed to distinguish between links managed by Exalate and links created independently outside the synchronization scope.\n\nSeveral contributing factors enabled this issue to reach production. The scope definition did not account for mixed environments where synchronized and non-synchronized links coexist on the same system. Test coverage focused primarily on standard synchronization flows rather than these mixed data environments. Additionally, the modification affected a broader scope than initially anticipated during the development and review process.\n\nThe impact characteristics were significant but recoverable. Multiple customer instances experienced removal of issue links that existed outside the intended synchronization scope. However, service functionality continued throughout the incident, and comprehensive audit logs preserved all affected link data, which enabled complete restoration of the removed links.Regarding data security and privacy, the audit logs contain only metadata elements such as issue identifiers, link types, and relationship mappings. No sensitive customer content, comments, or detailed issue information was captured in these logs. This metadata-only approach ensured that the restoration process could proceed while maintaining appropriate data protection standards.\n\n## Learnings\n\nOn the positive side, the incident response team made a rapid rollback decision, quickly identifying this as the appropriate technical solution rather than attempting a forward fix. The comprehensive logging infrastructure proved invaluable, enabling complete data restoration from audit trails. Cross-functional coordination worked well across engineering, customer success, and operations teams. The structured communication approach maintained clarity and transparency throughout the resolution process.\n\nThe incident also revealed important areas for system enhancement. Synchronization logic in complex integration scenarios requires better handling of mixed data environments where multiple systems manage different subsets of the same data types. Testing scope needs expansion to cover mixed synchronized and non-synchronized environments comprehensively. Change evaluation processes require enhancement for modifications that affect customer data. Monitoring capabilities need improvement to enable proactive detection of synchronization behavior changes before customer impact.\n\nSeveral process improvements have been \\(or are being\\) implemented as a result. Enhanced code review procedures now include additional requirements specifically for data modification operations. Expanded testing protocols cover scenarios involving mixed data environments and include dedicated data preservation validation. Improved monitoring systems detect synchronization pattern changes and unusual data modification activities. Updated release procedures include enhanced evaluation criteria for data-affecting changes and improved rollback automation capabilities.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-05T13:56:12.479+02:00", "resolved_inferred": false, "started_at": "2025-08-29T18:18:41.274+02:00", diff --git a/api/v/expedited-security.json b/api/v/expedited-security.json index 68ccf7538d7dbd70abb20c86cf491d761efa0ad4..19032d9daf026f594a1e1dad62fb5f4353b254e2 100644 --- a/api/v/expedited-security.json +++ b/api/v/expedited-security.json @@ -3,7 +3,7 @@ "slug": "expedited-security", "platform": "statuspage", "status_url": "https://expeditedsecurity.statuspage.io", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", diff --git a/api/v/expel.json b/api/v/expel.json index cff66b336f5c2b910f1986411472bbec6843f82c..fe1fa3c61a8e59ec7ea6a7ecfb8834f0d4ac6ec8 100644 --- a/api/v/expel.json +++ b/api/v/expel.json @@ -3,7 +3,7 @@ "slug": "expel", "platform": "statuspage", "status_url": "https://status.expel.io", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "This issue is resolved. Email delivery from Workbench has been restored, and phishing email submissions are processing normally.\n\nSuspected phishing emails submitted during this time were not received by Expel and could not be processed. Please ask your users to resubmit anything they reported during this period.\n\nNotification emails generated during this time have been delivered. Some may arrive later than the timestamp they were originally generated.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-30T15:53:53.528-04:00", "resolved_inferred": false, "started_at": "2026-08-30T05:43:18.895-04:00", @@ -25,7 +25,7 @@ "body": "The incident has been resolved, and all systems are once again fully available. No customer data was lost; SOC operations were impacted, but are back to normal.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-16T23:01:38.554-04:00", "resolved_inferred": false, "started_at": "2026-07-16T22:21:09.652-04:00", @@ -38,7 +38,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-12T13:47:51.794-04:00", "resolved_inferred": false, "started_at": "2026-07-13T16:20:51.365-04:00", @@ -51,7 +51,7 @@ "body": "All delayed messages have been delivered and the notifications system is fully operational.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-18T19:28:49.271-04:00", "resolved_inferred": false, "started_at": "2026-06-18T16:37:33.100-04:00", @@ -64,7 +64,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-18T09:29:31.307-04:00", "resolved_inferred": false, "started_at": "2026-06-17T19:11:36.837-04:00", @@ -77,7 +77,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-17T12:59:07.802-04:00", "resolved_inferred": false, "started_at": "2026-06-17T12:16:44.534-04:00", @@ -90,7 +90,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-09T13:33:31.416-04:00", "resolved_inferred": false, "started_at": "2026-06-09T11:40:12.452-04:00", @@ -103,7 +103,7 @@ "body": "The incident has been resolved, and all alerts counts are once again accurate. No customer data was lost, and SOC operations were not impacted.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-13T12:46:16.152-04:00", "resolved_inferred": false, "started_at": "2026-05-13T12:23:44.253-04:00", @@ -116,7 +116,7 @@ "body": "The incident has been resolved, and all systems are once again fully available. No customer data was lost, and all previously-accessible security devices are once again accessible and ingesting alerts.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-01T16:01:01.193-04:00", "resolved_inferred": false, "started_at": "2026-05-01T14:50:52.417-04:00", @@ -129,7 +129,7 @@ "body": "This issue has been resolved. All notifications in the backlog have been delivered and new notifications are being delivered as normal.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-25T14:09:58.208-04:00", "resolved_inferred": false, "started_at": "2026-04-25T13:42:40.064-04:00", @@ -142,7 +142,7 @@ "body": "We restored the credentials for the subset of devices, and are seeing that the majority of devices have returned to a healthy state. We investigated the remaining unhealthy devices, which are not related to the customer secrets vault upgrade. This incident is resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-20T16:54:07.773-04:00", "resolved_inferred": false, "started_at": "2026-04-20T12:20:52.323-04:00", @@ -155,7 +155,7 @@ "body": "Resolved: Microsoft has confirmed that the issues affecting Teams bots and message delivery are now fully resolved. All delayed messages have been reprocessed and delivered. Service is operating normally.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-24T17:12:56.102-04:00", "resolved_inferred": false, "started_at": "2026-03-24T12:58:42.908-04:00", @@ -168,7 +168,7 @@ "body": "Workaround is in place, we are bypassing the faulty AWS region and all impacted devices have resumed ingestion.\n\nOnce the outage in the faulty region is over, we will resume ingestion in that region.\n\nAlert Ingestion issue resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-02T15:36:02.232-05:00", "resolved_inferred": false, "started_at": "2026-03-02T13:35:43.480-05:00", @@ -181,7 +181,7 @@ "body": "The incident has been resolved, and all delayed notifications have been delivered. No customer data was lost, and SOC operations were not impacted.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-02T17:33:01.304-05:00", "resolved_inferred": false, "started_at": "2026-02-02T16:00:50.442-05:00", @@ -194,7 +194,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-20T18:02:02.636-05:00", "resolved_inferred": false, "started_at": "2026-01-20T15:31:38.847-05:00", @@ -207,7 +207,7 @@ "body": "The hotfix for phishing submission outcome emails was successful and behavior has returned to normal. This incident is resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-07T17:54:02.873-05:00", "resolved_inferred": false, "started_at": "2026-01-07T14:51:06.204-05:00", @@ -220,7 +220,7 @@ "body": "Detection pipelines are caught up. Service is nominal.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-29T17:09:01.373-05:00", "resolved_inferred": false, "started_at": "2025-12-29T16:26:28.060-05:00", @@ -233,7 +233,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-19T13:17:21.443-05:00", "resolved_inferred": false, "started_at": "2025-11-18T10:34:16.150-05:00", @@ -246,7 +246,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-17T09:52:08.999-04:00", "resolved_inferred": false, "started_at": "2025-11-12T10:28:40.892-05:00", @@ -259,7 +259,7 @@ "body": "Analysts are able to successfully SSO into the Wiz console. Incident is closed.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-03T14:43:47.433-05:00", "resolved_inferred": false, "started_at": "2025-11-03T11:56:31.825-05:00", @@ -272,7 +272,7 @@ "body": "Microsoft has confirmed that the O365 outage has been completely resolved.\nOur integration with O365 remains healthy and no customer data was lost.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-29T22:22:45.000-04:00", "resolved_inferred": false, "started_at": "2025-10-29T13:17:19.978-04:00", @@ -285,7 +285,7 @@ "body": "The third-party vendor responsible for the issues has provided a workaround which we have implemented in our infrastructure. The incident has been resolved, and all systems are once again fully available.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-21T00:59:43.782-04:00", "resolved_inferred": false, "started_at": "2025-10-20T15:41:40.721-04:00", @@ -298,7 +298,7 @@ "body": "The incident has been resolved, and all systems are once again fully available. No customer data was lost.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-20T08:35:26.153-04:00", "resolved_inferred": false, "started_at": "2025-10-20T06:06:39.459-04:00", @@ -311,7 +311,7 @@ "body": "The incident has been resolved, and all systems are once again fully available. All Microsoft Teams messages from Workbench that failed during the incident have been successfully delivered.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-17T02:59:30.132-04:00", "resolved_inferred": false, "started_at": "2025-10-17T01:55:38.968-04:00", @@ -324,7 +324,7 @@ "body": "The incident has been resolved and the Alert Analysis Dashboard is once again fully available. No customer data was lost, and SOC operations were not impacted.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-09T10:25:14.289-04:00", "resolved_inferred": false, "started_at": "2025-10-09T09:56:47.784-04:00", @@ -337,7 +337,7 @@ "body": "We have confirmed that the incident has been resolved. Email, slack and MS Teams notifications from Workbench are being delivered within normal timeframes.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-08T06:50:48.392-04:00", "resolved_inferred": false, "started_at": "2025-10-08T04:59:51.000-04:00", @@ -350,7 +350,7 @@ "body": "Wiz have confirmed that they have resolved the issue and our SOC Analysts are now able to triage and investigate Wiz alerts.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-09T09:34:11.247-04:00", "resolved_inferred": false, "started_at": "2025-09-09T09:17:32.608-04:00", @@ -363,7 +363,7 @@ "body": "The outage affecting the Azure Security Center API has been resolved, and all services are now fully operational. Our security alerts and recommendations are flowing as expected, and our integration with Azure is now reporting as healthy. No customer data was lost.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-20T02:11:53.835-04:00", "resolved_inferred": false, "started_at": "2025-08-19T21:24:53.849-04:00", @@ -376,7 +376,7 @@ "body": "Alert ingestion has caught up and is no longer delayed. This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-11T18:44:33.649-04:00", "resolved_inferred": false, "started_at": "2025-08-11T14:47:18.067-04:00", @@ -389,7 +389,7 @@ "body": "The incident has been resolved. All systems are once again fully available. No customer data was lost.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-08T12:07:37.370-04:00", "resolved_inferred": false, "started_at": "2025-08-08T06:45:46.354-04:00", @@ -402,7 +402,7 @@ "body": "The incident has been resolved, and all systems are once again fully available. No customer data was lost.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-08T01:21:54.112-04:00", "resolved_inferred": false, "started_at": "2025-08-07T23:28:06.173-04:00", diff --git a/api/v/experian.json b/api/v/experian.json index e4bb1e904ab42c7ea8b0a45ef8840fab257348b1..022d571842c56b37c7ea10f91df370ca8ede9ab9 100644 --- a/api/v/experian.json +++ b/api/v/experian.json @@ -3,7 +3,7 @@ "slug": "experian", "platform": "statuspage", "status_url": "https://status.edq.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-26T10:24:41.589Z", "resolved_inferred": false, "started_at": "2026-08-26T10:24:10.397Z", @@ -25,7 +25,7 @@ "body": "Service has returned to normal operating levels and remains stable. The incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-16T02:15:21.451Z", "resolved_inferred": false, "started_at": "2026-08-15T22:25:57.543Z", @@ -38,7 +38,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-24T04:59:56.315Z", "resolved_inferred": false, "started_at": "2026-07-24T04:21:55.693Z", @@ -51,7 +51,7 @@ "body": "Response times and errors rates stabilised, we are monitoring closely.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-13T07:34:34.511Z", "resolved_inferred": false, "started_at": "2026-07-13T02:11:32.849Z", @@ -64,7 +64,7 @@ "body": "Response times and errors rates have returned to normal, we are monitoring closely", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-10T09:21:30.133Z", "resolved_inferred": false, "started_at": "2026-07-10T07:17:35.051Z", @@ -77,7 +77,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-02T19:26:12.167Z", "resolved_inferred": false, "started_at": "2026-07-02T16:40:42.071Z", @@ -90,7 +90,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-01T01:58:38.227Z", "resolved_inferred": false, "started_at": "2026-07-01T01:35:42.751Z", @@ -103,7 +103,7 @@ "body": "The service is now responding normally - monitoring closely.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-22T14:20:35.966Z", "resolved_inferred": false, "started_at": "2026-06-22T11:09:10.943Z", @@ -116,7 +116,7 @@ "body": "This incident has been resolved, service is now operating normally.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-18T11:30:46.000Z", "resolved_inferred": false, "started_at": "2026-06-18T07:57:24.433Z", @@ -129,7 +129,7 @@ "body": "This is a retrospective notification to customers, that between 00:20 to 01:20 UTC on 11 May 2026, some customers using Email Validate real time might have seen connectivity and or timeouts against the Experian endpoint. This issue is now resolved and we are monitoring closely.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-11T11:01:08.946Z", "resolved_inferred": false, "started_at": "2026-05-11T11:01:08.874Z", @@ -142,7 +142,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-11T10:21:08.170Z", "resolved_inferred": false, "started_at": "2026-05-11T06:00:41.000Z", @@ -155,7 +155,7 @@ "body": "Incident is being closed as service is has been running with optimal performance.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-04T10:37:53.980Z", "resolved_inferred": false, "started_at": "2026-05-04T07:30:18.686Z", @@ -168,7 +168,7 @@ "body": "The issue have been identiified and the issue is now fixed.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-29T11:55:21.208Z", "resolved_inferred": false, "started_at": "2026-04-29T11:24:10.938Z", @@ -181,7 +181,7 @@ "body": "No further re-occurrences and the response times on the platform have been stable. This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-29T08:03:55.253Z", "resolved_inferred": false, "started_at": "2026-04-29T06:32:10.842Z", @@ -194,7 +194,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-28T00:45:10.000Z", "resolved_inferred": false, "started_at": "2026-04-28T00:15:59.000Z", @@ -207,7 +207,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-27T03:00:23.000Z", "resolved_inferred": false, "started_at": "2026-04-27T02:50:22.000Z", @@ -220,7 +220,7 @@ "body": "This incident has been resolved", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-23T05:30:31.000Z", "resolved_inferred": false, "started_at": "2026-04-23T04:45:22.000Z", @@ -233,7 +233,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-15T08:18:45.226Z", "resolved_inferred": false, "started_at": "2026-04-15T08:02:17.033Z", @@ -246,7 +246,7 @@ "body": "Some customers in ANZ region may have seen higher response times than normal for a short time, around 3am UTC. We are investigating.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-14T07:09:22.733Z", "resolved_inferred": false, "started_at": "2026-04-14T07:09:22.690Z", @@ -259,7 +259,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-30T15:02:01.118Z", "resolved_inferred": false, "started_at": "2026-03-30T07:40:36.713Z", @@ -272,7 +272,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-30T02:30:06.000Z", "resolved_inferred": false, "started_at": "2026-03-30T02:15:53.000Z", @@ -285,7 +285,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-25T00:20:51.000Z", "resolved_inferred": false, "started_at": "2026-03-24T23:42:00.000Z", @@ -298,7 +298,7 @@ "body": "This incident has been resolved, response time is back to normal", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-12T01:15:53.000Z", "resolved_inferred": false, "started_at": "2026-03-12T01:15:53.000Z", @@ -311,7 +311,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-07T17:15:05.135Z", "resolved_inferred": false, "started_at": "2026-03-07T14:59:13.334Z", @@ -324,7 +324,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-05T07:21:10.421Z", "resolved_inferred": false, "started_at": "2026-03-05T06:33:10.797Z", @@ -337,7 +337,7 @@ "body": "Between 12:08:05 (UTC) and 12:15:01 (UTC) - some customers may have seen intermittent timeouts on their phone validation requests. The platform is now stable and we are monitoring closely.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-11T14:15:07.557Z", "resolved_inferred": false, "started_at": "2026-02-11T14:15:07.506Z", @@ -350,7 +350,7 @@ "body": "The service response time is now stable - we are monitoring closely.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-06T10:20:09.945Z", "resolved_inferred": false, "started_at": "2026-02-06T09:23:02.019Z", @@ -363,7 +363,7 @@ "body": "Between 1600 and 1900 UTC on 30 Jan, some customers may have seen higher response times and intermittent errors during this time. The application is now stable, and we are monitoring closely.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-31T00:22:26.146Z", "resolved_inferred": false, "started_at": "2026-01-31T00:22:26.071Z", @@ -376,7 +376,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-14T13:30:41.845Z", "resolved_inferred": false, "started_at": "2026-01-14T10:34:05.788Z", @@ -389,7 +389,7 @@ "body": "This incident has been resolved. Errors have cleared and we are monitoring closely", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-07T13:36:59.089Z", "resolved_inferred": false, "started_at": "2026-01-07T12:30:54.977Z", @@ -402,7 +402,7 @@ "body": "Performance issues with format requests have been fixed, and performance is back to normal levels - we are monitoring closely.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-28T17:17:23.982Z", "resolved_inferred": false, "started_at": "2025-11-28T16:51:06.582Z", @@ -415,7 +415,7 @@ "body": "Some customers may have seen intermittent higher response times between 08:50 and 09:15 UTC. Services have stabilized, and we are monitoring closely.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-26T10:17:43.355Z", "resolved_inferred": false, "started_at": "2025-11-26T10:17:43.299Z", @@ -428,7 +428,7 @@ "body": "Some customers in North America may have seen a spike in response times for around 2 mins at 17:38 UTC. The system recovered itself, and is now responding normally. We are monitoring the platform closely.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-20T18:01:32.045Z", "resolved_inferred": false, "started_at": "2025-11-20T18:01:31.995Z", @@ -441,7 +441,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-15T11:15:51.000Z", "resolved_inferred": false, "started_at": "2025-11-15T10:15:17.000Z", @@ -454,7 +454,7 @@ "body": "Services are running normally now - we are monitoring closely.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-06T20:34:06.076Z", "resolved_inferred": false, "started_at": "2025-11-06T17:57:28.559Z", @@ -467,7 +467,7 @@ "body": "Performance is stable - we continue to monitor closely.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-05T09:55:42.582Z", "resolved_inferred": false, "started_at": "2025-11-05T08:47:57.429Z", @@ -480,7 +480,7 @@ "body": "This incident has been resolved. We are still monitoring performance closely.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-30T09:54:58.521Z", "resolved_inferred": false, "started_at": "2025-10-29T16:31:27.849Z", @@ -493,7 +493,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-23T20:27:01.736Z", "resolved_inferred": false, "started_at": "2025-10-23T19:41:29.690Z", @@ -506,7 +506,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-15T11:43:07.348Z", "resolved_inferred": false, "started_at": "2025-10-15T08:54:08.929Z", @@ -519,7 +519,7 @@ "body": "Some customers may have experienced connectivity issues to Autobatch, this issue is now resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-14T13:29:00.492Z", "resolved_inferred": false, "started_at": "2025-10-14T13:29:00.437Z", @@ -532,7 +532,7 @@ "body": "Service is now stable - we are monitoring closely", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-09T15:21:26.614Z", "resolved_inferred": false, "started_at": "2025-10-09T10:09:05.522Z", @@ -545,7 +545,7 @@ "body": "Some client may have experienced Increased response times and unknown rates from approximately 0748hrs UTC till 0815hrs UTC", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-30T08:37:02.574Z", "resolved_inferred": false, "started_at": "2025-09-30T08:37:02.528Z", @@ -558,7 +558,7 @@ "body": "Response times have returned to normal and we are monitoring.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-23T10:52:14.367Z", "resolved_inferred": false, "started_at": "2025-09-23T09:57:42.654Z", @@ -571,7 +571,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-15T14:20:41.000Z", "resolved_inferred": false, "started_at": "2025-09-15T13:30:49.000Z", @@ -584,7 +584,7 @@ "body": "Response times returned to normal - Operations team are monitoring closely.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-10T16:40:17.000Z", "resolved_inferred": false, "started_at": "2025-09-10T14:45:18.000Z", @@ -597,7 +597,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-27T04:19:35.239Z", "resolved_inferred": false, "started_at": "2025-08-27T03:17:34.527Z", @@ -610,7 +610,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-26T21:20:55.000Z", "resolved_inferred": false, "started_at": "2025-08-26T20:01:04.000Z", @@ -623,7 +623,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-14T06:19:58.975Z", "resolved_inferred": false, "started_at": "2025-08-14T02:35:03.000Z", diff --git a/api/v/expo.json b/api/v/expo.json index 9d1f81e5defe1ae9fdfb86cf39f6782d969b0e6e..906951bd919e665883459b6f031022dc2ec3dabd 100644 --- a/api/v/expo.json +++ b/api/v/expo.json @@ -3,7 +3,7 @@ "slug": "expo", "platform": "statuspage", "status_url": "https://status.expo.io", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "degraded", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "We are currently monitoring degraded performance on the NPM registry. The degradation may cause package installs to time out, and EAS Builds to fail when using NPM. We will provide updates from NPM when available.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "started_at": "2026-09-03T19:00:06.583-07:00", "state": "investigating", "title": "Degraded performance on the NPM registry", @@ -23,7 +23,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-09-03T09:06:55.991-07:00", "resolved_inferred": false, "started_at": "2026-09-03T08:39:43.614-07:00", @@ -36,7 +36,7 @@ "body": "A fix was deployed at 2:50pm PT/5:50pm ET. The job queue has been running as expected.\n\nThe root cause of this incident is that a new version of a cache needed more vCPUs than it was given, and we have increased the CPU count as the immediate fix along with additional monitoring for CPU usage on these cache instances.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-09-02T15:05:29.000-07:00", "resolved_inferred": false, "started_at": "2026-09-02T14:44:43.000-07:00", @@ -49,7 +49,7 @@ "body": "Our cloud provider's network is fully operational in all of the availability zones Expo uses.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-09-01T12:13:29.795-07:00", "resolved_inferred": false, "started_at": "2026-09-01T08:51:34.781-07:00", @@ -62,7 +62,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-09-01T05:41:29.237-07:00", "resolved_inferred": false, "started_at": "2026-09-01T04:45:33.848-07:00", @@ -75,7 +75,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-26T12:30:52.717-07:00", "resolved_inferred": false, "started_at": "2026-08-26T08:51:45.642-07:00", @@ -88,7 +88,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-18T17:52:30.853-07:00", "resolved_inferred": false, "started_at": "2026-08-18T09:25:34.450-07:00", @@ -101,7 +101,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-17T16:09:15.827-07:00", "resolved_inferred": false, "started_at": "2026-08-17T14:12:02.591-07:00", @@ -114,7 +114,7 @@ "body": "Fix deployed to server, `eas-cli@22.0.0` set back to `latest`.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-14T12:35:41.586-07:00", "resolved_inferred": false, "started_at": "2026-08-14T10:04:23.788-07:00", @@ -127,7 +127,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-12T20:07:01.843-07:00", "resolved_inferred": false, "started_at": "2026-08-12T19:59:06.293-07:00", @@ -140,7 +140,7 @@ "body": "Fix is deployed.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-12T17:00:59.381-07:00", "resolved_inferred": false, "started_at": "2026-08-12T12:00:32.000-07:00", @@ -153,7 +153,7 @@ "body": "At around 4 PM PDT, we experienced a temporary spike in EAS Update manifest serving errors. Service reliability has returned to normal, and we are monitoring the situation.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-08T16:00:00.000-07:00", "resolved_inferred": false, "started_at": "2026-08-08T16:00:00.000-07:00", @@ -166,7 +166,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-07T08:54:27.032-07:00", "resolved_inferred": false, "started_at": "2026-08-07T08:32:23.460-07:00", @@ -179,7 +179,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-07T06:13:28.303-07:00", "resolved_inferred": false, "started_at": "2026-08-07T05:39:51.457-07:00", @@ -192,7 +192,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-04T16:42:51.164-07:00", "resolved_inferred": false, "started_at": "2026-08-04T15:19:01.304-07:00", @@ -205,7 +205,7 @@ "body": "This incident is resolved. Android builds are completing normally.\n\nSome Android builds and Linux workflow jobs failed early with the error \"We've lost connection to the worker\". Builds and jobs that failed with this error were automatically excluded from billing and can be retried.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-04T14:15:32.179-07:00", "resolved_inferred": false, "started_at": "2026-08-04T10:54:52.658-07:00", @@ -218,7 +218,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-29T23:36:06.169-07:00", "resolved_inferred": false, "started_at": "2026-07-29T23:19:12.783-07:00", @@ -231,7 +231,7 @@ "body": "iOS submission success rates are back to normal as App Store Connect continues to recover. Submissions that failed during the outage won\u2019t be retried automatically \u2014 please resubmit those builds.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-26T17:55:51.908-07:00", "resolved_inferred": false, "started_at": "2026-07-26T16:22:58.781-07:00", @@ -244,7 +244,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-14T18:02:07.165-07:00", "resolved_inferred": false, "started_at": "2026-07-14T14:17:58.260-07:00", @@ -257,7 +257,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-10T06:37:43.379-07:00", "resolved_inferred": false, "started_at": "2026-07-10T06:18:57.760-07:00", @@ -270,7 +270,7 @@ "body": "All services are back to operational.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-08T14:29:20.456-07:00", "resolved_inferred": false, "started_at": "2026-07-08T13:39:20.000-07:00", @@ -283,7 +283,7 @@ "body": "It looks like users are not actually getting limited, but are getting a 100% build used warning ahead of time when triggering a build from the eas cli. Use eas-cli@latest for correct messaging.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-01T07:35:08.372-07:00", "resolved_inferred": false, "started_at": "2026-07-01T06:39:55.028-07:00", @@ -296,7 +296,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-29T08:41:56.096-07:00", "resolved_inferred": false, "started_at": "2026-06-29T08:28:05.756-07:00", @@ -309,7 +309,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-29T08:21:58.777-07:00", "resolved_inferred": false, "started_at": "2026-06-29T08:14:20.717-07:00", @@ -322,7 +322,7 @@ "body": "Between 9:04am PDT and 10:56am PDT, users experienced scrolling issues on the Build and Workflows pages of expo.dev. This was caused by a CSS issue introduced in a recent deployment. We rolled back the deployment and verified the issue is resolved. We apologize for the inconvenience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-26T09:00:00.000-07:00", "resolved_inferred": false, "started_at": "2026-06-26T09:00:00.000-07:00", @@ -335,7 +335,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-24T21:09:30.102-07:00", "resolved_inferred": false, "started_at": "2026-06-24T18:35:10.385-07:00", @@ -348,7 +348,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-23T12:45:06.408-07:00", "resolved_inferred": false, "started_at": "2026-06-23T10:28:48.655-07:00", @@ -361,7 +361,7 @@ "body": "The fix is deployed. Environment variables pages should now work after refreshing. We apologize for the disruption.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-19T02:13:26.182-07:00", "resolved_inferred": false, "started_at": "2026-06-19T02:02:50.200-07:00", @@ -374,7 +374,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-16T11:53:25.302-07:00", "resolved_inferred": false, "started_at": "2026-06-16T09:31:59.155-07:00", @@ -387,7 +387,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-10T18:04:39.167-07:00", "resolved_inferred": false, "started_at": "2026-06-10T15:51:45.000-07:00", @@ -400,7 +400,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-10T10:41:44.338-07:00", "resolved_inferred": false, "started_at": "2026-06-10T09:05:10.797-07:00", @@ -413,7 +413,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-08T20:18:12.010-07:00", "resolved_inferred": false, "started_at": "2026-06-08T19:35:54.426-07:00", @@ -426,7 +426,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-31T20:47:12.917-07:00", "resolved_inferred": false, "started_at": "2026-05-31T13:38:47.317-07:00", @@ -439,7 +439,7 @@ "body": "Starting at 3AM PDT we observed limited availability of EAS Update manifest endpoint. Availability has now recovered. We are looking into underlying causes.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-29T05:54:52.073-07:00", "resolved_inferred": false, "started_at": "2026-05-29T05:54:52.029-07:00", @@ -452,7 +452,7 @@ "body": "EAS Submit jobs of certain types have not been getting their status and logs updated in website, despite having been processed successfully. We have identified the issue, implemented a fix and have just finished updating all the old records to their right state.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-28T08:20:15.865-07:00", "resolved_inferred": false, "started_at": "2026-05-28T08:20:15.772-07:00", @@ -465,7 +465,7 @@ "body": "We observed an increased rate of timeouts for updates manifest requests. This issue has been resolved and the service is stable.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-25T08:38:46.763-07:00", "resolved_inferred": false, "started_at": "2026-05-25T08:38:46.712-07:00", @@ -478,7 +478,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-22T19:10:01.075-07:00", "resolved_inferred": false, "started_at": "2026-05-22T12:06:40.610-07:00", @@ -491,7 +491,7 @@ "body": "The project dashboard, hosting dashboard and \"eas deploy\" are operational again. For more information about the incident and timelines, see https://www.cloudflarestatus.com/incidents/znll7lfnd35h", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-22T09:42:13.561-07:00", "resolved_inferred": false, "started_at": "2026-05-22T09:04:19.010-07:00", @@ -504,7 +504,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-15T10:00:41.000-07:00", "resolved_inferred": false, "started_at": "2026-05-14T15:32:40.273-07:00", @@ -517,7 +517,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-14T14:09:04.271-07:00", "resolved_inferred": false, "started_at": "2026-05-14T10:12:17.650-07:00", @@ -530,7 +530,7 @@ "body": "This Incident has been resolved and services are operating normally again.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-13T22:53:16.586-07:00", "resolved_inferred": false, "started_at": "2026-05-13T22:39:53.558-07:00", @@ -543,7 +543,7 @@ "body": "A high percentage of Android builds failed to find workers due to us exceeding capacity. We have now provisioned additional resources to meet capacity.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-13T12:28:17.345-07:00", "resolved_inferred": false, "started_at": "2026-05-13T10:32:36.021-07:00", @@ -556,7 +556,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-05T18:08:40.355-07:00", "resolved_inferred": false, "started_at": "2026-05-05T15:00:31.924-07:00", @@ -569,7 +569,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-05T18:09:10.442-07:00", "resolved_inferred": false, "started_at": "2026-05-05T14:04:22.655-07:00", @@ -582,7 +582,7 @@ "body": "During a rollout of new, improved underlying Linux infrastructure for EAS we've noticed an increased rate of OOM errors. The change has been reverted.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-05T08:00:00.000-07:00", "resolved_inferred": false, "started_at": "2026-05-05T08:00:00.000-07:00", @@ -595,7 +595,7 @@ "body": "A fix has been deployed. EAS Update publishing is fully operational.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-01T01:05:21.146-07:00", "resolved_inferred": false, "started_at": "2026-05-01T00:02:54.535-07:00", @@ -608,7 +608,7 @@ "body": "Users received a 404 error when attempting to authenticate with Expo Go due to a server-side bug that wrongly overwrote the HTTP status code on one of our GraphQL endpoints. This has been fixed.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-30T13:13:00.000-07:00", "resolved_inferred": false, "started_at": "2026-04-30T13:13:00.000-07:00", @@ -621,7 +621,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-29T00:58:38.842-07:00", "resolved_inferred": false, "started_at": "2026-04-29T00:06:37.721-07:00", @@ -634,7 +634,7 @@ "body": "Between 3:44 PM and 4:08 PM PDT, existing sessions on expo.dev were treated as invalid, and users were unable to sign back in. During this window, login attempts from the website failed. The issue has been resolved and users can now sign in normally. We're investigating the root cause.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-28T15:44:00.000-07:00", "resolved_inferred": false, "started_at": "2026-04-28T15:44:00.000-07:00", @@ -647,7 +647,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-28T15:42:46.819-07:00", "resolved_inferred": false, "started_at": "2026-04-28T13:38:51.448-07:00", diff --git a/api/v/f-secure.json b/api/v/f-secure.json index 5b25fcd45d7a5c7f67526a0e5ef458dc816aa189..310eeb37c3dd7ff6c11d5857fda3c8e4f9c42326 100644 --- a/api/v/f-secure.json +++ b/api/v/f-secure.json @@ -3,7 +3,7 @@ "slug": "f-secure", "platform": "statuspage", "status_url": "https://status.f-secure.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-09-03T11:32:05.152Z", "resolved_inferred": false, "started_at": "2026-09-02T11:15:50.347Z", @@ -25,7 +25,7 @@ "body": "We're writing to confirm that the activation issue affecting partners in the APAC/Japan region has been resolved.\n\nSummary: Yesterday, a backend infrastructure fault in our ap-northeast-1 environment caused intermittent server errors, which prevented some customer activations in the region from completing.\n\nResolution: Our engineering team identified and restored the affected service. Activations are now processing normally, and we've confirmed no further errors since the fix was applied.\n\nWe regret inconvenience this may have caused your customers, and thank you for your patience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-29T10:36:18.329Z", "resolved_inferred": false, "started_at": "2026-07-28T10:34:49.594Z", @@ -38,7 +38,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-10T07:40:09.826Z", "resolved_inferred": false, "started_at": "2025-09-26T05:14:48.036Z", diff --git a/api/v/f5.json b/api/v/f5.json index e17a575aedb144a90714066eb2d213d5341216f1..bf1e66f6b29ad53d8669722ebd790ae0a670dbd4 100644 --- a/api/v/f5.json +++ b/api/v/f5.json @@ -3,7 +3,7 @@ "slug": "f5", "platform": "statuspage", "status_url": "https://www.f5cloudstatus.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "Dear Valued Customers,\n\nF5 Distributed Cloud Expands Global Footprint into Seoul, South Korea.\n\nWe are pleased to announce the launch of a new Regional Edge (RE) cluster in Seoul, South Korea (sel1-kr), further expanding the F5 Distributed Cloud global network. This new point of presence strengthens our coverage in East Asia.\n\nThe Seoul, South Korea RE site delivers:\n\n 1. Reduced latency for customers and end users in Seoul, South Korea.\n 2. Improved application performance through localized traffic processing closer to end users.\n 3. Full feature parity with all existing RE sites.\n\nGo-Live Schedule:\n8 September 2026 at 08:00 UTC\n\nTo ensure uninterrupted connectivity between the F5 Distributed Cloud PoP in Seoul, South Korea and your origin infrastructure, please update your firewall allowlists to include the network range 159.60.186.0/24 prior to the go-live date.\n\nIf you have any questions or concerns, please do not hesitate to contact us at support@cloud.f5.com.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "started_at": "2026-09-02T20:50:08.000Z", "state": "monitoring", "title": "Informational: New Regional Edge Site \u2014 Seoul, South Korea (sel1-kr)", @@ -23,7 +23,7 @@ "body": "The F5 Distributed Cloud team has concluded the monitoring period for the traffic and services impacted by this incident. Services remained stable and operating normally throughout this period, and the incident is now considered resolved.\n\nWe appreciate your patience and understanding throughout this event and remain committed to continuously improving the reliability of our services. Thank you for your continued trust in F5.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-09-01T01:28:14.796Z", "resolved_inferred": false, "started_at": "2026-08-31T16:54:31.429Z", @@ -36,7 +36,7 @@ "body": "The F5 Distributed Cloud team had successfully resolved the issue affecting AI powered Web Application Firewall, we can confirm that no further impact was observed and all services are operating normally. Our teams have validated system stability.\n\nIf you continue to experience any issues or have further questions, please don't hesitate to reach out to our support team.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-25T17:44:00.706Z", "resolved_inferred": false, "started_at": "2026-08-25T16:39:52.241Z", @@ -49,7 +49,7 @@ "body": "We are pleased to confirm that the service degradation previously affecting the Global Log Receiver and the delay in Access Log streaming have been fully resolved. All services are now fully recovered and functioning as expected.\n\nFollowing service restoration, our engineering teams have maintained close monitoring of the platform to ensure ongoing stability, and no further issues have been detected. As noted in our previous updates, there was no traffic interruption, and all core F5 Distributed Cloud Console services remained fully operational throughout the duration of this incident.\n\nThis incident is now considered closed.\n\nThank you for your patience and support.\n\nSincerely,\nF5 Distributed Cloud", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-24T22:54:09.953Z", "resolved_inferred": false, "started_at": "2026-08-24T13:50:15.600Z", @@ -62,7 +62,7 @@ "body": "The F5 Distributed Cloud team has successfully resolved the issue of the New York Regional Edge. After thorough monitoring, we can confirm that no additional impact has been observed.\n\nWe appreciate your patience and understanding while we worked to resolve this matter. If you continue to experience any issues or have further questions, please don't hesitate to reach out to our support team.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-21T10:02:25.008Z", "resolved_inferred": false, "started_at": "2026-08-21T05:57:04.986Z", @@ -75,7 +75,7 @@ "body": "The F5 Distributed Cloud team can confirm that the issue affecting the Paris (PA4) Regional Edge and the Global Log Receiver (GLR) service has been fully resolved.\n\nWe sincerely appreciate your patience and understanding throughout this event. All services are now operating as expected.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-14T19:03:20.257Z", "resolved_inferred": false, "started_at": "2026-08-14T16:31:11.000Z", @@ -88,7 +88,7 @@ "body": "Mexico Regional Edge site is now live", "first_seen": "2026-09-04T07:06:16Z", "impact": "maintenance", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-09-01T19:19:06.603Z", "resolved_inferred": false, "started_at": "2026-08-08T04:47:40.000Z", @@ -101,7 +101,7 @@ "body": "We're pleased to confirm the issue affecting the DNS service has been resolved, and the service is now operating normally.\n\nOur engineering teams have addressed the underlying issue and have verified system stability. We'll continue to keep a close watch on DNS performance to ensure everything remains stable and consistent.\n\nIf you have any questions or need assistance, please contact our Support team:\n\n- Email support: support@cloud.f5.com\n- Phone support: For region-specific contact details, please visit:\nhttps://my.f5.com/manage/s/article/K000135931\n\nThank you for your patience and understanding.\n\nSincerely,\nF5 Distributed Cloud", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-05T03:47:56.533Z", "resolved_inferred": false, "started_at": "2026-08-04T16:24:50.000Z", @@ -114,7 +114,7 @@ "body": "We are glad to confirm that the previously observed service degradation affecting Global Log Receiver (GLR) has been resolved, and GLR is operating normally.\n\nFollowing service restoration, our engineering teams have continued to monitor the platform to ensure sustained stability, and no further issues have been detected. There was no traffic interruption, and all core F5 Distributed Cloud Console services remained fully operational throughout the event.\n\nThis incident is now considered closed.\n\nThank you for your patience and understanding.\n\nSincerely,\nF5 Distributed Cloud", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-04T04:42:03.394Z", "resolved_inferred": false, "started_at": "2026-08-03T16:45:30.759Z", @@ -127,7 +127,7 @@ "body": "The F5 Distributed Cloud Team has resolved the issue causing delays in access logs appearing in the Distributed Cloud Console UI. The system is fully operational, and access logs have remained stable without further lag.\n\nThank you for your patience and understanding during this time.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-31T02:42:01.632Z", "resolved_inferred": false, "started_at": "2026-07-30T12:44:02.153Z", @@ -140,7 +140,7 @@ "body": "The F5 Distributed Cloud team had successfully resolved the issue affecting the connectivity in Mumbai Regional Edge (MB2), and after an extensive period of monitoring, we can confirm that no further impact was observed.\n\nWe appreciate your patience and understanding while we worked to resolve this matter. If you continue to experience any issues or have further questions, please don't hesitate to reach out to our support team.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-30T05:09:05.838Z", "resolved_inferred": false, "started_at": "2026-07-29T08:48:22.854Z", @@ -153,7 +153,7 @@ "body": "The F5 Distributed Cloud team had successfully resolved the issue affecting CDN edge connectivity in Dallas (DAL3), and after an extensive period of monitoring, we can confirm that no further impact was observed.\n\nWe appreciate your patience and understanding while we worked to resolve this matter. If you continue to experience any issues or have further questions, please don't hesitate to reach out to our support team.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-28T05:29:12.749Z", "resolved_inferred": false, "started_at": "2026-07-27T09:02:56.898Z", @@ -166,7 +166,7 @@ "body": "Between 2026-07-24 10:55 UTC and 11:15 UTC, a service degradation was observed due to an External Cloud Provider issue. This possibly affected communication between F5 services and customer origins, resulting in increased 5xx errors and higher origin latency.\n\nThe issue was confirmed to be related to the Cloud Provider and not F5 Distributed Cloud infrastructure. The issue has been fully resolved, and services are operating normally.\n\nIf you continue to experience any issues, please reach out to our support team through your established channels.\n\nWe apologize for any inconvenience caused and appreciate your understanding.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-24T13:49:18.482Z", "resolved_inferred": false, "started_at": "2026-07-24T12:05:48.616Z", @@ -179,7 +179,7 @@ "body": "The F5 Distributed Cloud team has successfully resolved the issue affecting the Routed DDoS functions in the XC Console and no further impact is expected.\n\nWe appreciate your patience and understanding while we worked to resolve this matter. If you continue to experience any issues or have further questions, please don't hesitate to reach out to our support team.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-17T23:04:08.195Z", "resolved_inferred": false, "started_at": "2026-07-16T06:22:30.000Z", @@ -192,7 +192,7 @@ "body": "The issue affecting support ticket creation in Distributed Cloud Console has been fully resolved, and all services are operating normally.\n\nOur teams have validated system stability and will continue to monitor to ensure consistent performance.\n\nThank you for your patience while we worked to resolve this issue. If you have any questions or concerns, please feel free to reach out to our support team.\n\nContact information\n- Email support: support@cloud.f5.com\n- Phone support: For region-specific contact details, please visit:\n https://my.f5.com/manage/s/article/K000135931\n\nWe appreciate your understanding and cooperation as we continue to improve our services.\n\nSincerely,\nF5 Distributed Cloud", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-15T15:26:11.678Z", "resolved_inferred": false, "started_at": "2026-07-15T11:43:33.464Z", @@ -205,7 +205,7 @@ "body": "The F5 Distributed Cloud team has successfully resolved the issue affecting display of metrics within the customer dashboard and CE\u00b4s, and no further impact is expected.\n\nWe appreciate your patience and understanding while we worked to resolve this matter. If you continue to experience any issues or have further questions, please don't hesitate to reach out to our support team.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-09T05:00:05.631Z", "resolved_inferred": false, "started_at": "2026-07-08T21:48:44.485Z", @@ -218,7 +218,7 @@ "body": "The issue affecting DNS visualization status has been fully resolved, and all services are operating normally.\n\nOur teams have validated system stability and will continue to monitor to ensure consistent performance.\n\nThank you for your patience while we worked to resolve this issue. If you have any questions or concerns, please feel free to reach out to our support team.\n\nContact information\n- Email support: support@cloud.f5.com\n- Phone support: For region-specific contact details, please visit:\n https://my.f5.com/manage/s/article/K000135931\n\nWe appreciate your understanding and cooperation as we continue to improve our services.\n\nSincerely,\nF5 Distributed Cloud", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-10T00:48:49.107Z", "resolved_inferred": false, "started_at": "2026-07-06T15:09:54.791Z", @@ -231,7 +231,7 @@ "body": "The F5 Distributed Cloud team has successfully resolved the issue affecting GLR log streaming in the Distributed Cloud console. Live log visibility has now been restored. The system is currently operating normally, and no further impact is expected.\n\nWe appreciate your patience and understanding while we worked to resolve this matter. If you continue to experience any issues or have further questions, please don't hesitate to reach out to our support team.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-02T13:03:18.236Z", "resolved_inferred": false, "started_at": "2026-07-01T21:03:14.409Z", @@ -244,7 +244,7 @@ "body": "## **Root Cause Statement**\n\nThe incident was caused by a **fiber cut on a major regional ISP\u2019s network \\(Airtel\\) between Indonesia and India.** This disruption led to **widespread congestion throughout the region, and across multiple networks with dependencies on Airtel. F5\u2019s network and infrastructure remained fully operational throughout the event and did not experience any outage or service degradation.**\n\nAs a result of the fiber cut, **some Internet traffic to/from India and nearby regions was degraded, leading to increased latency, intermittent timeouts/packet loss, and slowness.**\n\n**Mitigation: Upon detection of the event, F5 implemented traffic engineering measures within the F5 Distributed Cloud backbone to re-route our traffic away from the fault in Airtel\u2019s network,** deliberately avoiding the impacted network segment, reducing our exposure to the provider\u2019s outage, and improving overall service performance for our customers.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-26T17:14:24.296Z", "resolved_inferred": false, "started_at": "2026-06-26T11:58:37.469Z", @@ -257,7 +257,7 @@ "body": "We are pleased to confirm that the issue has been fully resolved.\n\nAll affected services have been restored and are operating normally, with no ongoing customer impact. Platform functionality has returned to expected operating levels, and this incident is now considered closed.\n\nWe appreciate your patience and support throughout this incident.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-27T17:10:03.095Z", "resolved_inferred": false, "started_at": "2026-06-24T18:10:47.262Z", @@ -270,7 +270,7 @@ "body": "Following a period of post-restoration monitoring, we have confirmed the issue impacting the ability to perform changes in Distributed Cloud components and Customer Dashboard loading has been resolved. Customers should now be able to create and modify endpoint configurations normally, and dashboards should load as expected. Services are fully operational. Thank you for your patience and understanding throughout this incident.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-24T00:15:11.033Z", "resolved_inferred": false, "started_at": "2026-06-23T11:29:36.377Z", @@ -283,7 +283,7 @@ "body": "Our engineering teams have restored full functionality for CDN Distributions, the CDN Dashboard and Purge Services.\nTraffic is flowing normally and this incident has now been resolved.\n\nIf you are still experiencing any issues please do not hesitate to contact F5 Support.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-17T11:04:26.438Z", "resolved_inferred": false, "started_at": "2026-06-16T09:36:55.407Z", @@ -296,7 +296,7 @@ "body": "The issue affecting the F5 Distributed Cloud Global Log Receiver has been resolved.\nAll XC Console core services remains fully operational, and the incident is now closed.\nPlease contact support if you continue to experience any issues.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-10T19:20:37.169Z", "resolved_inferred": false, "started_at": "2026-06-09T11:52:45.962Z", @@ -309,7 +309,7 @@ "body": "The issue affecting the F5 Distributed Cloud GLR (Global Logs Receiver) has been resolved. The service remains fully operational, and the incident is now closed.\n\nWe appreciate your patience and understanding while we worked to resolve this matter. If you continue to experience any issues or have further questions, please don't hesitate to reach out to our support team.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-09T03:07:05.795Z", "resolved_inferred": false, "started_at": "2026-06-08T14:58:22.020Z", @@ -322,7 +322,7 @@ "body": "The F5 Distributed Cloud team has successfully resolved the issue that was causing the false positives in rate-limiting policies. Services are now functioning as expected, and we will continue to monitor to ensure ongoing stability.\n\nIf you have any questions or continue to experience issues, please reach out to our support team through your established channels. This incident is now considered resolved.\n\nWe appreciate your patience and understanding while we worked to restore service.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-07T18:01:44.288Z", "resolved_inferred": false, "started_at": "2026-06-06T21:20:09.209Z", @@ -335,7 +335,7 @@ "body": "The F5 Distributed Cloud team has successfully resolved the issue affecting GLR log streaming. The system is currently operating normally, and no further impact is expected.\n\nWe appreciate your patience and understanding while we worked to resolve this matter. If you continue to experience any issues or have further questions, please don\u2019t hesitate to reach out to our support team.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-26T14:35:46.234Z", "resolved_inferred": false, "started_at": "2026-05-26T13:56:08.873Z", @@ -348,7 +348,7 @@ "body": "The F5 Distributed Cloud team has successfully resolved the issue that was causing Synthetic Monitoring service degradation. Services are now functioning as expected, and we will continue to monitor to ensure ongoing stability. Please note that all core XC Console services remained fully operational throughout the incident.\n\nIf you have any questions or continue to experience issues, please reach out to our support team through your established channels. This incident is now considered resolved.\n\nWe appreciate your patience and understanding while we worked to restore service.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-25T00:55:16.946Z", "resolved_inferred": false, "started_at": "2026-05-24T20:09:50.000Z", @@ -361,7 +361,7 @@ "body": "The F5 Distributed Cloud team confirmed that all CDN services and nodes are fully operational. Traffic is flowing normally, and this incident has now been resolved.\n\nIf you're still experiencing any issues, please do not hesitate to contact F5 Support for assistance.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-22T03:58:57.437Z", "resolved_inferred": false, "started_at": "2026-05-21T00:39:02.000Z", @@ -374,7 +374,7 @@ "body": "The issue affecting DNS resolution has been fully resolved, and all services are operating normally.\nOur teams have validated system stability and will continue to monitor to ensure consistent performance.\nThank you for your patience while we worked to resolve this issue. If you have any questions or concerns, please feel free to reach out to our support team.\n\nContact information\n- Email support: support@cloud.f5.com\n- Phone support: For region-specific contact details, please visit:\n https://my.f5.com/manage/s/article/K000135931\n\nWe appreciate your understanding and cooperation as we continue to improve our services.\n\nSincerely,\nF5 Distributed Cloud", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-20T21:55:29.689Z", "resolved_inferred": false, "started_at": "2026-05-20T17:01:49.030Z", @@ -387,7 +387,7 @@ "body": "The F5 Distributed Cloud team has successfully resolved the issue affecting F5 XC's internal DNS zone. After monitoring the system is currently operating normally and no further impact is expected.\n\nWe appreciate your patience and understanding while we worked to resolve this matter. If you continue to experience any issues or have further questions, please don't hesitate to reach out to our support team.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-12T01:48:22.666Z", "resolved_inferred": false, "started_at": "2026-05-11T13:27:14.038Z", @@ -400,7 +400,7 @@ "body": "The issue with the delays in configuration propagation for CDN deployments has been resolved and after monitoring the services remain fully operational.\n\nThis incident has been marked as resolved.\n\nWe appreciate your patience and understanding. If you continue to experience any issues or have concerns, please contact our support team.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-10T18:36:06.897Z", "resolved_inferred": false, "started_at": "2026-05-09T21:06:29.763Z", @@ -413,7 +413,7 @@ "body": "The issue with F5 Distributed Cloud that was causing intermittent DNS resolution failures, during which customers may have experienced occasional failures while attempting to reach certain endpoints or services relying on DNS lookups, has been resolved, and services are now fully operational. All other services remained fully operational throughout the incident.\n\nThis incident has been marked as resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-08T14:05:13.285Z", "resolved_inferred": false, "started_at": "2026-05-08T07:31:37.001Z", @@ -426,7 +426,7 @@ "body": "Our investigation confirmed that the DNS service remained fully operational throughout the observed timeframe, and no actual service impact occurred.\nWe would like to inform you that this incident has now been closed.\nWe apologize for any confusion this may have caused and appreciate your understanding.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-12T20:42:45.111Z", "resolved_inferred": false, "started_at": "2026-05-06T14:17:59.501Z", @@ -439,7 +439,7 @@ "body": "Dear Valued Customers,\n\nWe are adding new IP ranges to our F5 Distributed Cloud SaaS Services. To ensure uninterrupted access to our services, please whitelist these additional IP ranges before September 1st, 2026.\n\nNew IP Ranges:\n\nAmericas:\n159.60.177.0/24\n159.60.252.0/24\n\nPlease update your firewall and security settings to allow traffic from these IPs. This change is necessary to maintain seamless connectivity and avoid disruptions.\n\nThe full list of IP ranges can be found at https://docs.cloud.f5.com/docs-v2/platform/reference/network-cloud-ref\n\nIf you have any questions, please feel free to contact us at support@cloud.f5.com", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "started_at": "2026-05-05T09:50:34.501Z", "state": "monitoring", "title": "Informational : New IP ranges for F5 Distributed Cloud Regional Edge sites", @@ -450,7 +450,7 @@ "body": "The issue affecting the F5 Distributed Cloud GLR (Global Logs Receiver) has been resolved. \nThe service remains fully operational, and the incident is now closed. \nPlease contact support if you continue to experience any issues.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-05T03:12:26.372Z", "resolved_inferred": false, "started_at": "2026-05-04T14:37:52.079Z", @@ -463,7 +463,7 @@ "body": "Chicago Regional Edge site is now live", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-23T04:35:35.333Z", "resolved_inferred": false, "started_at": "2026-04-16T15:07:35.055Z", @@ -476,7 +476,7 @@ "body": "The F5 Distributed Cloud team has successfully resolved the issue affecting GLR log streaming and access log delays in the Distributed Cloud console. Live log visibility has now been restored, and any delayed logs have been successfully backfilled. The system is currently operating normally, and no further impact is expected.\n\nWe appreciate your patience and understanding while we worked to resolve this matter. If you continue to experience any issues or have further questions, please don\u2019t hesitate to reach out to our support team.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-12T15:08:11.326Z", "resolved_inferred": false, "started_at": "2026-04-11T23:51:15.262Z", @@ -489,7 +489,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-16T15:02:36.601Z", "resolved_inferred": false, "started_at": "2026-04-08T03:21:38.000Z", @@ -502,7 +502,7 @@ "body": "This incident has now been marked as resolved. All other services remained fully operational throughout the incident. If you continue to experience issues, please contact the F5 Support team for assistance.\n\nThank you for your patience and understanding while we worked to restore full service.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-07T07:40:58.145Z", "resolved_inferred": false, "started_at": "2026-04-06T14:49:14.911Z", @@ -515,7 +515,7 @@ "body": "The intermittent DNS resolution failures affecting the CDN domain in the U.S. region have now been fully resolved. All impacted services are operating normally.\n\nOur engineering team has completed the necessary remediation steps, and we do not anticipate any further disruption. \n\nIf you experience any related issues, please reach out to our support team for assistance.\n\nThank you for your patience and understanding while we worked to restore full service.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-28T04:08:03.293Z", "resolved_inferred": false, "started_at": "2026-03-27T23:00:05.653Z", @@ -528,7 +528,7 @@ "body": "Milan Regional Edge site is live and stable , closing the note", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-03T04:46:47.696Z", "resolved_inferred": false, "started_at": "2026-03-26T21:33:45.224Z", @@ -541,7 +541,7 @@ "body": "The issue affecting CDN purge operations on the Distributed Cloud Console has been resolved.\nCDN purge functionality is now fully restored and operating as expected. This incident has been marked as resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-25T13:48:27.252Z", "resolved_inferred": false, "started_at": "2026-03-25T12:19:26.977Z", @@ -554,7 +554,7 @@ "body": "The issue has been mitigated, and services are operating normally. This was a non-service-impacting event with no impact to traffic or core services.\nEverything is functioning as expected and we continue to monitor stability.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-25T11:17:33.313Z", "resolved_inferred": false, "started_at": "2026-03-25T08:24:29.211Z", @@ -567,7 +567,7 @@ "body": "The F5 Distributed Cloud team has successfully resolved the issue impacting the Global Logs Receiver (GLR). Live log visibility has been fully restored in the Distributed Cloud console dashboard, and backfill logs have been recovered as expected. The system is now functioning normally, with no further impact anticipated. We sincerely appreciate your patience and understanding throughout the resolution process.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-26T05:52:10.933Z", "resolved_inferred": false, "started_at": "2026-03-23T10:39:33.177Z", @@ -580,7 +580,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-14T23:20:14.890Z", "resolved_inferred": false, "started_at": "2026-03-14T17:09:17.484Z", @@ -593,7 +593,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-05T15:40:06.201Z", "resolved_inferred": false, "started_at": "2026-03-05T15:11:55.044Z", @@ -606,7 +606,7 @@ "body": "The XC Console and all associated services within the XC platform are operating as expected, with no interruptions to functionality. Enhanced monitoring has successfully ensured stability and performance during the recent implementation tasks.\n\nThis incident is now resolved, and the platform is fully restored to its optimal state. Should you experience any issues or have technical questions regarding F5 Distributed Cloud Services, please do not hesitate to contact our support team at support@cloud.f5.com.\n\nThank you for your patience and understanding throughout this process. We remain committed to delivering reliable and high-quality services.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-14T00:01:33.117Z", "resolved_inferred": false, "started_at": "2026-02-27T15:25:43.970Z", @@ -619,7 +619,7 @@ "body": "The F5 Distributed Cloud console continues to operate normally and remain in steady state. All other services remain fully operational. If you have any questions or concerns, please do not hesitate to contact our support team. This incident has been marked as resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-26T00:09:53.599Z", "resolved_inferred": false, "started_at": "2026-02-25T19:46:23.852Z", @@ -632,7 +632,7 @@ "body": "The F5 Distributed Cloud console continues to operate normally and remain in steady state. All other services remain fully operational. If you have any questions or concerns, please do not hesitate to contact our support team. This incident has been marked as resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-25T05:46:28.822Z", "resolved_inferred": false, "started_at": "2026-02-24T19:03:38.567Z", @@ -645,7 +645,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-03T04:47:13.479Z", "resolved_inferred": false, "started_at": "2025-10-21T19:48:52.293Z", diff --git a/api/v/fasterize.json b/api/v/fasterize.json index 0e2525aa4695c1a2895c68575cfb36a52e9789e1..b16f90edcddb3fe080d5649089a4d006f376cccf 100644 --- a/api/v/fasterize.json +++ b/api/v/fasterize.json @@ -3,7 +3,7 @@ "slug": "fasterize", "platform": "statuspage", "status_url": "https://status.fasterize.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "Incident is closed since 11:30am but we keep on monitoring as the incident on our hosting provider is not fully resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-22T17:18:20.609+02:00", "resolved_inferred": false, "started_at": "2026-05-22T11:33:50.733+02:00", @@ -25,7 +25,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-21T07:38:52.368+02:00", "resolved_inferred": false, "started_at": "2026-05-20T12:33:55.003+02:00", @@ -38,7 +38,7 @@ "body": "The issue affecting flush operations through the API and dashboard has been fixed.\n\nFlush actions are now working normally again.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-20T10:08:25.050+02:00", "resolved_inferred": false, "started_at": "2026-05-20T10:00:37.917+02:00", @@ -51,7 +51,7 @@ "body": "We experienced some issues with our European infrastructure. Service has been restored since 00:20. This has affected loading speeds. Some pages or websites have experienced slowdowns.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-10T22:30:00.000+02:00", "resolved_inferred": false, "started_at": "2026-04-10T22:30:00.000+02:00", @@ -64,7 +64,7 @@ "body": "We have identified an issue affecting the accuracy of INP data collected between Thursday, 5 February and Monday, 9 February.\n\nDuring this period, INP metrics were incorrectly reported for Safari on iPhone when the navigation type was back-forward cache (BFCache). This behaviour is related to a known issue in WebKit, which causes inflated INP values in this specific scenario.\nMore details are available in the related Safari bug report:\nhttps://bugs.webkit.org/show_bug.cgi?id=305251\n\nThe issue has been identified and mitigated on our side. Only the INP metric is impacted; other performance metrics remain unaffected.\n\nWe apologise for any confusion this may have caused and recommend caution when analysing INP data for Safari iPhone traffic over this time window.\n\nIf you have any questions, our team remains available.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-05T13:00:00.000+01:00", "resolved_inferred": false, "started_at": "2026-02-05T13:00:00.000+01:00", @@ -77,7 +77,7 @@ "body": "The incident has been resolved, everything is now operating normally", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-24T16:43:03.416+01:00", "resolved_inferred": false, "started_at": "2025-11-24T15:50:11.072+01:00", @@ -90,7 +90,7 @@ "body": "An in-memory database cluster failure occurred leading to service unavailability across multiple Fasterize components \u2014 primarily the **Optimisation Engine** and the **API**.\n\nAt **09:48**, an in-memory database cluster failure happens after restarting multiple nodes to release a new engine version. The database cluster began an automatic failover sequence, but each time a new node was promoted as primary, it **crashed under excessive connection load**.\n\nThis cluster serves as a **cache layer** providing access to configurations. During the outage, Engine instances attempted to reconnect at a very high frequency and fell back to retrieving data directly from the main database.This fallback mechanism worked as intended until **10:32**, allowing our optimization engine to continue operating in **degraded mode**.\n\nAt **10:32**, however, the **proxy layer** of our optimisation engine became **saturated in network resources**, rendering it unavailable from the front layer.\n\nWhen the proxy layer is unreachable, the platform automatically **unplugs the CDN and sites are served directly from their origin servers**, without Fasterize optimizations.\n\nWorking with our hosting provider, we **reduced the Optimisation Engine cluster size at 11:45** to limit reconnection attempts to Redis. By **12:16**, the Redis cluster had stabilised and full service was restored.\n\nLater, at **14:15**, we detected that the **API was unable to write to the Redis cluster**. The root cause was a **security patch applied by the hosting provider**, which **restricted the use of some commands** in the cluster.The API was patched to remove usage of these commands, and full functionality was restored by **20:15**.\n\n\u200c\n\n## **Impact**\n\n* **Duration:** 10h32 \u2013 12:16 \\(outage\\), API issue until 20:15 \n* **Affected components:** Optimisation Engine, API \n* **User impact:** Most websites temporarily served unoptimised content directly from origin; Some websites experienced unavailability due to an dysfunctional DNS fallback mechanismAPI write operations failed, blocking configuration update.\n\n## **Resolution Timeline**\n\n\u200c\n\n## Action plan\n\nShort term:\n\n* Improve **alerting and visibility** on in-memory database cluster health and failover events.\n* Review the in-memory database connection logic of the engine to avoid too many reconnection attempts in case of disconnections and avoid a case preventing the start of the process in case of an in-memory database outage.\u00a0\n* Adjust failover DNS logic to avoid redirection to the origin when the CDN/fronts are still able to accept the traffic.\n* Upscale in-memory database cluster in order to accept more connections \n\nMedium term:\u00a0\n\n* Review and test **disaster recovery procedures** for in-memory database cache clusters, including the ability to quickly activate a passive cluster.\n\nLong term:\n\n* Re-architecture the engine to reduce the number of connections on the itn-memory database cluster", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-09T20:23:39.092+02:00", "resolved_inferred": false, "started_at": "2025-10-09T11:01:04.847+02:00", @@ -103,7 +103,7 @@ "body": "A network maintenance caused a regression in the service responsible for extracting the True-Client-IP header from the X-Forwarded-For header. Around 6% of the platform trafic has been impacted. The issue has now been resolved. We apologize for the inconvenience.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-25T10:00:00.000+02:00", "resolved_inferred": false, "started_at": "2025-09-25T10:00:00.000+02:00", @@ -116,7 +116,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-09T15:51:42.777+02:00", "resolved_inferred": false, "started_at": "2025-09-09T15:11:52.763+02:00", @@ -129,7 +129,7 @@ "body": "# **\ud83d\udee0\ufe0f Incident Description**\n\n**On Tuesday, September 9th, 2025, Fasterize carried out a scheduled maintenance to modernize part of its private network infrastructure.**\n\n**During this operation, an unexpected configuration issue temporarily disrupted communication between some components of the platform. This resulted in an increased error rate on part of the traffic between 11:43 and 11:50 \\(Paris time\\).**\n\n# **\ud83d\udcc5 Timeline**\n\n* **11:40 \u2013 Update started on the first batch of machines** \n* **11:43 \u2013 Anomaly detected in communication between proxies and fronts** \n* **11:50 \u2013 Issue mitigated, service returned to normal** \n\n# **\u2705 Immediate Actions**\n\n* **Affected machines were taken out of rotation** \n* **Healthy machines were reactivated to absorb the traffic** \n* **Service stabilized within minutes of the anomaly** \n\n# **\ud83d\ude80 Next Steps**\n\n* **Strengthening our validation procedures during network migrations** \n* **Adding automated connectivity tests to detect similar issues earlier** \n* **Improving documentation and standardization of network configurations to minimize future risks**", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-09T12:13:56.714+02:00", "resolved_inferred": false, "started_at": "2025-09-09T12:13:56.657+02:00", @@ -142,7 +142,7 @@ "body": "## **\ud83d\udee0\ufe0f Incident Report**\n\n**Date:** Tuesday, September 9, 2025\n\n**Duration:** 14:50 \u2013 18:30 \\(Paris time\\)\n\n**Impact:** ~23% of traffic\n\n### **\ud83d\udccc Summary**\n\nOn September 9, Fasterize performed a planned network maintenance to replace an obsolete private network. As part of this operation, a new private IP address was introduced for our load balancers while keeping the existing ones in place.\n\nLater that afternoon, a DDoS attack led to the saturation and restart of one of the load balancers. Following this restart, the load balancer started using the new private IP address to communicate with the backend servers. Since this IP had not yet been registered as a trusted proxy, some requests were processed incorrectly.\n\n### **\ud83d\udcc8 Impact**\n\n* ~23% of traffic was affected between **14:50 and 18:30**. \n* Some users encountered **403 errors**. \n* In certain cases, client IP addresses were not correctly identified in the headers. \n\n### **\ud83d\udcc5 Timeline**\n\n* **10:25** \u2013 New private IP address added to the load balancers. \n* **14:49** \u2013 DDoS attack causes one load balancer to restart. \n* **14:50** \u2013 First incorrect headers observed \\(undetected at this stage\\). \n* **16:02** \u2013 Support receives a ticket mentioning 403 errors. \n* **17:16** \u2013 Ticket escalated to the platform team. \n* **18:16** \u2013 Root cause identified and linked to the network update. \n* **18:30** \u2013 New IP address added to the trusted list; incident resolved. \n\n**Total duration of impact:** 3h40\n\n### **\ud83d\udd0d Root Cause**\n\nThe new private IP address introduced during the maintenance was not yet included in the trusted proxy configuration. When one load balancer restarted, it began using this IP, leading to incorrect handling of client headers.\n\n### **\ud83d\ude80 Next Steps**\n\n* All load balancer IPs have now been added to the trusted configuration across environments. \n* Documentation has been updated to include this step in future network changes. \n* Additional monitoring will be set up to detect unexpected private IPs in client headers. \n* Escalation procedures between support and platform teams will be reviewed to ensure faster response times.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-09T02:30:00.000+02:00", "resolved_inferred": false, "started_at": "2025-09-09T02:30:00.000+02:00", diff --git a/api/v/figma.json b/api/v/figma.json index a329e2b2e690747de7e8180c03c571f0f6710274..0035c1d5cb277682721bcaeacb159f415834b22e 100644 --- a/api/v/figma.json +++ b/api/v/figma.json @@ -3,7 +3,7 @@ "slug": "figma", "platform": "statuspage", "status_url": "https://status.figma.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:16:22Z", @@ -12,7 +12,7 @@ "body": "The issue preventing some Codex and ChatGPT users from seeing MCP tools, such as use_figma, has been resolved. The impact began at 10:14 UTC, with recovery beginning at 14:03 UTC.", "first_seen": "2026-09-04T07:16:22Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-08-26T16:19:32.698Z", "resolved_inferred": false, "started_at": "2026-08-26T12:08:58.645Z", @@ -25,7 +25,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:16:22Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-07-27T22:49:58.791Z", "resolved_inferred": false, "started_at": "2026-07-27T19:29:19.000Z", @@ -38,7 +38,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:16:22Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-19T12:40:44.690Z", "resolved_inferred": false, "started_at": "2026-06-18T23:46:52.175Z", @@ -51,7 +51,7 @@ "body": "We've identified an issue leading to errors while prompting Figma Make and and Agent using Anthropic models. This has been resolved.", "first_seen": "2026-09-04T07:16:22Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-06-16T19:41:02.000Z", "resolved_inferred": false, "started_at": "2026-06-16T17:58:30.354Z", @@ -64,7 +64,7 @@ "body": "This incident has been resolved at 9:39 am UTC", "first_seen": "2026-09-04T07:16:22Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-20T15:50:45.000Z", "resolved_inferred": false, "started_at": "2026-04-20T06:42:20.620Z", @@ -77,7 +77,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:16:22Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-04-10T16:00:12.983Z", "resolved_inferred": false, "started_at": "2026-04-09T19:00:37.565Z", @@ -90,7 +90,7 @@ "body": "From 12:45 to 4:50 PM UTC today, we experienced an issue that prevented some users from previewing and publishing Figma Make files. We have updated this from Monitoring to Resolved.", "first_seen": "2026-09-04T07:16:22Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-12T22:11:36.626Z", "resolved_inferred": false, "started_at": "2026-03-12T14:00:18.239Z", @@ -103,7 +103,7 @@ "body": "From 5:50PM 3/6 UTC to 1:15AM 3/7 UTC, there was a bug that would cause library publishes to be incorrect. Files pulling in those updates would experience errors related to conflicting properties in variants. The issue with library publishes has been resolved. If you continue to see this error, please re-publish the affected components (by making a small change) and re-update the consuming files to apply the fix.", "first_seen": "2026-09-04T07:16:22Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-03-07T18:08:40.390Z", "resolved_inferred": false, "started_at": "2026-03-06T21:40:02.995Z", @@ -116,7 +116,7 @@ "body": "This issue has been resolved as of February 17 at 18:59 UTC.", "first_seen": "2026-09-04T07:16:22Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-17T20:00:26.000Z", "resolved_inferred": false, "started_at": "2026-02-17T14:16:20.236Z", @@ -129,7 +129,7 @@ "body": "From 7:05 PM UTC on Feb 5 to 12:00 AM UTC on Feb 6, some users experienced issues when prompting in Figma Make or Sites with code components. This issue has been resolved.", "first_seen": "2026-09-04T07:16:22Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-06T00:34:43.000Z", "resolved_inferred": false, "started_at": "2026-02-05T19:05:02.279Z", @@ -142,7 +142,7 @@ "body": "From 9:58 PM UTC on Jan 27 to 2:00 AM UTC on Feb 1, some users experienced issues when prompting in Figma Make or Sites with code components. This issue has been resolved.", "first_seen": "2026-09-04T07:16:22Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-02-02T01:57:54.967Z", "resolved_inferred": false, "started_at": "2026-01-29T19:39:23.797Z", @@ -155,7 +155,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:16:22Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-27T23:41:20.554Z", "resolved_inferred": false, "started_at": "2026-01-27T20:01:22.156Z", @@ -168,7 +168,7 @@ "body": "From 12AM to 5PM UTC, some users experienced issues while prompting in Figma Make. This has been resolved.", "first_seen": "2026-09-04T07:16:22Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-23T17:48:16.913Z", "resolved_inferred": false, "started_at": "2026-01-23T01:05:34.161Z", @@ -181,7 +181,7 @@ "body": "From 5:30 PM to 6:30 PM UTC, some users were experiencing issues when publishing Figma Make files or publishing Sites. This has been resolved.", "first_seen": "2026-09-04T07:16:22Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-01-07T20:24:58.700Z", "resolved_inferred": false, "started_at": "2026-01-07T18:19:24.835Z", @@ -194,7 +194,7 @@ "body": "From 06:30 UTC to 17:20 UTC, Figma Make was experiencing intermittent errors building Make files. A fix has been implemented in Figma Make and this incident is now resolved.", "first_seen": "2026-09-04T07:16:22Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-12-15T17:30:21.000Z", "resolved_inferred": false, "started_at": "2025-12-15T17:00:29.000Z", @@ -207,7 +207,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:16:22Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-11-18T18:04:13.065Z", "resolved_inferred": false, "started_at": "2025-11-18T14:01:25.000Z", @@ -220,7 +220,7 @@ "body": "From 19:38 UTC to 4:10 UTC, Figma was degraded or unavailable due to failures in AWS and other dependencies. We've completed all mitigations and have been monitoring the situation for a few hours now without issues. We haven't seen any abnormal issues since our 4:10 UTC update, so we are marking the incident resolved. We will continue to monitor closely through the night.", "first_seen": "2026-09-04T07:16:22Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-21T06:53:59.732Z", "resolved_inferred": false, "started_at": "2025-10-20T19:55:45.000Z", @@ -233,7 +233,7 @@ "body": "From 19:00 to 21:51 UTC, some users experienced issues while prompting in Figma Make. This has been resolved.", "first_seen": "2026-09-04T07:16:22Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-02T03:53:08.616Z", "resolved_inferred": false, "started_at": "2025-10-01T21:43:29.345Z", @@ -246,7 +246,7 @@ "body": "A fix has been implemented and prototypes and Mirror on iOS should now be operational. We are continuing to monitor.", "first_seen": "2026-09-04T07:16:22Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-06T04:40:57.892Z", "resolved_inferred": false, "started_at": "2025-09-06T03:16:04.407Z", diff --git a/api/v/filecoin.json b/api/v/filecoin.json index 4bc7c033e68c0ed08e6c3eafed48510d672cc6a6..294a9d8d749546813165380467c3921100b381c5 100644 --- a/api/v/filecoin.json +++ b/api/v/filecoin.json @@ -3,7 +3,7 @@ "slug": "filecoin", "platform": "statuspage", "status_url": "https://status.filecoin.io", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", diff --git a/api/v/filepicker.json b/api/v/filepicker.json index 5d6e1aaa27cebae909c0b4aea66582aac22f213d..87e2cfdefc8d9e712ff232f6006ce89eee34357b 100644 --- a/api/v/filepicker.json +++ b/api/v/filepicker.json @@ -3,7 +3,7 @@ "slug": "filepicker", "platform": "statuspage", "status_url": "http://status.filestack.com", -"last_checked": "2026-09-04T09:06:33Z", +"last_checked": "2026-09-04T10:17:20Z", "last_state": "ok", "history_backfilled": true, "first_watched": "2026-09-04T07:06:16Z", @@ -12,7 +12,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "major", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2026-05-06T16:40:54.973Z", "resolved_inferred": false, "started_at": "2026-05-06T15:28:56.784Z", @@ -25,7 +25,7 @@ "body": "The issue with the degradation of the Virus scan has been resolved. All queued items have been processed, and the service performance is now back to normal.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-23T20:35:57.496Z", "resolved_inferred": false, "started_at": "2025-10-23T19:23:14.037Z", @@ -38,7 +38,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "none", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-10-01T15:36:27.802Z", "resolved_inferred": false, "started_at": "2025-10-01T14:31:56.811Z", @@ -51,7 +51,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "critical", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-09-14T20:22:36.273Z", "resolved_inferred": false, "started_at": "2025-09-13T19:17:14.259Z", @@ -64,7 +64,7 @@ "body": "This incident has been resolved.", "first_seen": "2026-09-04T07:06:16Z", "impact": "minor", -"last_seen": "2026-09-04T09:06:33Z", +"last_seen": "2026-09-04T10:17:20Z", "resolved_at": "2025-08-20T12:33:18.226Z", "resolved_inferred": false, "started_at": "2025-08-19T22:35:53.126Z",