Incidents reported on status page for unique.app https://status.prod.unique.app/ en https://status.prod.unique.app/ Thu, 18 Dec 2025 08:38:02 +0000 https://status.prod.unique.app/#60eb3954014765e06d6aa2c1f459e4a0cb566c0ba9fc4064e5b6d9f093f4190c Scope Management recovered https://status.prod.unique.app/ Thu, 18 Dec 2025 08:35:05 +0000 https://status.prod.unique.app/#60eb3954014765e06d6aa2c1f459e4a0cb566c0ba9fc4064e5b6d9f093f4190c Scope Management went down https://status.prod.unique.app/ Tue, 16 Dec 2025 10:39:56 +0000 https://status.prod.unique.app/#ac618714db0b40ddfe37f198940d48c1a762200ec9f1c0e952d3c22225e98f06 Knowledge Base recovered https://status.prod.unique.app/ Tue, 16 Dec 2025 10:39:54 +0000 https://status.prod.unique.app/#23b02dcb33fc37660e7e7999d2b595fe4c416adeb2286be9887a57b03e70f392 Recording recovered https://status.prod.unique.app/ Tue, 16 Dec 2025 10:39:47 +0000 https://status.prod.unique.app/#097f77d209302d5774f02ea42db81b460a2f149f3ab525a40c5b26c8ab41d843 Chat recovered https://status.prod.unique.app/ Tue, 16 Dec 2025 10:39:24 +0000 https://status.prod.unique.app/#687c12e03f49c56a4fc083ff13435d55dfe0111dd61b08c3e94f3c88fd574c35 Google Calendar recovered https://status.prod.unique.app/ Tue, 16 Dec 2025 10:39:18 +0000 https://status.prod.unique.app/#5e5e45885cdfa370acfd7b834c2cb0b4716f7159f803317e19a3e21ad2220f13 Sidebar recovered https://status.prod.unique.app/ Tue, 16 Dec 2025 10:39:07 +0000 https://status.prod.unique.app/#aebc2d8eb5fcff76995cd9d4e2349b98db2af960f8132c95ba9a2158f8f0c106 Sidebar recovered https://status.prod.unique.app/ Tue, 16 Dec 2025 10:39:00 +0000 https://status.prod.unique.app/#8015cad96c32b90df80a41e21a206cd6fd273d942f5b77a8359376af975b9695 IDP recovered https://status.prod.unique.app/ Tue, 16 Dec 2025 10:38:45 +0000 https://status.prod.unique.app/#9a2703a3aadf82fab4e6c312a1d122533e36d3de6a3d74604f17d3daf0531b2b Google Meets recovered https://status.prod.unique.app/ Tue, 16 Dec 2025 10:38:27 +0000 https://status.prod.unique.app/#e680c63bdab4c66c4886dc6503a0c3a94160683a16ee8c8e4e74481cd77b8e21 Chat recovered https://status.prod.unique.app/ Tue, 16 Dec 2025 10:38:16 +0000 https://status.prod.unique.app/#be146d5a5f0a11520af3bde865e782e2bf6308d221a8913e209f363d63217bba Microsoft recovered https://status.prod.unique.app/ Tue, 16 Dec 2025 10:38:06 +0000 https://status.prod.unique.app/#e29ecfda6864f8cc03435fcfdc8fbdbe4dbf96e6238e5ee020d43e2035d23313 Scope Management recovered https://status.prod.unique.app/ Tue, 16 Dec 2025 10:38:04 +0000 https://status.prod.unique.app/#ebfb6d97c4516adf035e56cd5af146e7ae62ba4f429cacdbb62a8efca1c1a797 Recording recovered https://status.prod.unique.app/ Tue, 16 Dec 2025 10:37:55 +0000 https://status.prod.unique.app/#11fb1a5a7abcc354873dd598434ab36f8f5b60d918d5847d8a6279f62ef241a8 Webhooks recovered https://status.prod.unique.app/ Tue, 16 Dec 2025 10:35:22 +0000 https://status.prod.unique.app/#e680c63bdab4c66c4886dc6503a0c3a94160683a16ee8c8e4e74481cd77b8e21 Chat went down https://status.prod.unique.app/ Tue, 16 Dec 2025 10:35:17 +0000 https://status.prod.unique.app/#be146d5a5f0a11520af3bde865e782e2bf6308d221a8913e209f363d63217bba Microsoft went down https://status.prod.unique.app/ Tue, 16 Dec 2025 10:35:10 +0000 https://status.prod.unique.app/#e29ecfda6864f8cc03435fcfdc8fbdbe4dbf96e6238e5ee020d43e2035d23313 Scope Management went down https://status.prod.unique.app/ Tue, 16 Dec 2025 10:35:06 +0000 https://status.prod.unique.app/#ebfb6d97c4516adf035e56cd5af146e7ae62ba4f429cacdbb62a8efca1c1a797 Recording went down https://status.prod.unique.app/ Tue, 16 Dec 2025 10:35:00 +0000 https://status.prod.unique.app/#11fb1a5a7abcc354873dd598434ab36f8f5b60d918d5847d8a6279f62ef241a8 Webhooks went down https://status.prod.unique.app/ Tue, 16 Dec 2025 10:34:03 +0000 https://status.prod.unique.app/#ac618714db0b40ddfe37f198940d48c1a762200ec9f1c0e952d3c22225e98f06 Knowledge Base went down https://status.prod.unique.app/ Tue, 16 Dec 2025 10:33:42 +0000 https://status.prod.unique.app/#23b02dcb33fc37660e7e7999d2b595fe4c416adeb2286be9887a57b03e70f392 Recording went down https://status.prod.unique.app/ Tue, 16 Dec 2025 10:33:35 +0000 https://status.prod.unique.app/#097f77d209302d5774f02ea42db81b460a2f149f3ab525a40c5b26c8ab41d843 Chat went down https://status.prod.unique.app/ Tue, 16 Dec 2025 10:33:28 +0000 https://status.prod.unique.app/#687c12e03f49c56a4fc083ff13435d55dfe0111dd61b08c3e94f3c88fd574c35 Google Calendar went down https://status.prod.unique.app/ Tue, 16 Dec 2025 10:33:16 +0000 https://status.prod.unique.app/#5e5e45885cdfa370acfd7b834c2cb0b4716f7159f803317e19a3e21ad2220f13 Sidebar went down https://status.prod.unique.app/ Tue, 16 Dec 2025 10:33:07 +0000 https://status.prod.unique.app/#aebc2d8eb5fcff76995cd9d4e2349b98db2af960f8132c95ba9a2158f8f0c106 Sidebar went down https://status.prod.unique.app/ Tue, 16 Dec 2025 10:32:56 +0000 https://status.prod.unique.app/#8015cad96c32b90df80a41e21a206cd6fd273d942f5b77a8359376af975b9695 IDP went down https://status.prod.unique.app/ Tue, 16 Dec 2025 10:32:50 +0000 https://status.prod.unique.app/#9a2703a3aadf82fab4e6c312a1d122533e36d3de6a3d74604f17d3daf0531b2b Google Meets went down https://status.prod.unique.app/ Thu, 04 Dec 2025 23:49:06 +0000 https://status.prod.unique.app/#a0076f74bbe4e26dd8c6a0336d1a96cd868983b991b41c3ff5768049932ea171 Sidebar recovered https://status.prod.unique.app/ Thu, 04 Dec 2025 23:45:47 +0000 https://status.prod.unique.app/#9a958c82a9a7e65aa24f64b488be7be482842be117b25c19dd199f4c04af4244 IDP recovered https://status.prod.unique.app/ Thu, 04 Dec 2025 23:31:07 +0000 https://status.prod.unique.app/#a0076f74bbe4e26dd8c6a0336d1a96cd868983b991b41c3ff5768049932ea171 Sidebar went down https://status.prod.unique.app/ Thu, 04 Dec 2025 23:21:45 +0000 https://status.prod.unique.app/#9a958c82a9a7e65aa24f64b488be7be482842be117b25c19dd199f4c04af4244 IDP went down https://status.prod.unique.app/ Wed, 03 Dec 2025 17:36:35 +0000 https://status.prod.unique.app/#cc0f4d4c65447066c813a488b5b822a77af94f01b6fa816436771fa135767f17 Sidebar recovered https://status.prod.unique.app/ Wed, 03 Dec 2025 17:33:33 +0000 https://status.prod.unique.app/#cc0f4d4c65447066c813a488b5b822a77af94f01b6fa816436771fa135767f17 Sidebar went down https://status.prod.unique.app/ Wed, 03 Dec 2025 08:44:47 +0000 https://status.prod.unique.app/#02a51bff9a3f3426293efe88e6e0a258f327e7a66f2c5df2a678f3dd1aff135d Sidebar recovered https://status.prod.unique.app/ Wed, 03 Dec 2025 08:41:46 +0000 https://status.prod.unique.app/#02a51bff9a3f3426293efe88e6e0a258f327e7a66f2c5df2a678f3dd1aff135d Sidebar went down https://status.prod.unique.app/ Tue, 02 Dec 2025 14:53:22 +0000 https://status.prod.unique.app/#992f6c1a34203e5c8c3b5157316a01f19ae9b053190af6a305a253d746d43158 Sidebar recovered https://status.prod.unique.app/ Tue, 02 Dec 2025 14:50:21 +0000 https://status.prod.unique.app/#992f6c1a34203e5c8c3b5157316a01f19ae9b053190af6a305a253d746d43158 Sidebar went down https://status.prod.unique.app/ Thu, 27 Nov 2025 17:23:05 +0000 https://status.prod.unique.app/#8688d6a7bfda489a38a31acf92a60938fa67b41e057c3351f039f4e8aedc5fc8 Webhooks recovered https://status.prod.unique.app/ Thu, 27 Nov 2025 17:21:34 +0000 https://status.prod.unique.app/#692a0097587cf8e56601804dc22953528778b0d941e35b6edb31562deff69bb0 Google Calendar recovered https://status.prod.unique.app/ Thu, 27 Nov 2025 17:21:25 +0000 https://status.prod.unique.app/#6d5bdc1703755443db79c343521b38a06f5b68b8ee197ab921f52024534cf228 Sidebar recovered https://status.prod.unique.app/ Thu, 27 Nov 2025 17:20:04 +0000 https://status.prod.unique.app/#8688d6a7bfda489a38a31acf92a60938fa67b41e057c3351f039f4e8aedc5fc8 Webhooks went down https://status.prod.unique.app/ Thu, 27 Nov 2025 17:18:35 +0000 https://status.prod.unique.app/#692a0097587cf8e56601804dc22953528778b0d941e35b6edb31562deff69bb0 Google Calendar went down https://status.prod.unique.app/ Thu, 27 Nov 2025 17:18:22 +0000 https://status.prod.unique.app/#6d5bdc1703755443db79c343521b38a06f5b68b8ee197ab921f52024534cf228 Sidebar went down https://status.prod.unique.app/ Tue, 25 Nov 2025 17:30:45 +0000 https://status.prod.unique.app/#439c62d6690191e1f4fbd389132e1f83fd39533ee93c4772b3354c787ca9d547 Sidebar recovered https://status.prod.unique.app/ Tue, 25 Nov 2025 17:30:16 +0000 https://status.prod.unique.app/#6b7f60701893f60bbcb40a39c5491c2af6047ad55afa5bd6d8c8df7ef132dd80 Google Meets recovered https://status.prod.unique.app/ Tue, 25 Nov 2025 17:27:46 +0000 https://status.prod.unique.app/#439c62d6690191e1f4fbd389132e1f83fd39533ee93c4772b3354c787ca9d547 Sidebar went down https://status.prod.unique.app/ Tue, 25 Nov 2025 17:27:16 +0000 https://status.prod.unique.app/#6b7f60701893f60bbcb40a39c5491c2af6047ad55afa5bd6d8c8df7ef132dd80 Google Meets went down https://status.prod.unique.app/ Mon, 24 Nov 2025 11:14:24 +0000 https://status.prod.unique.app/#a4cbce4702e0322d19b73ce74bccee657946bbc2c0f2d79e0ff6e07096312440 Sidebar recovered https://status.prod.unique.app/ Mon, 24 Nov 2025 11:11:22 +0000 https://status.prod.unique.app/#a4cbce4702e0322d19b73ce74bccee657946bbc2c0f2d79e0ff6e07096312440 Sidebar went down https://status.prod.unique.app/ Fri, 21 Nov 2025 13:41:36 +0000 https://status.prod.unique.app/#d45415433ac9d7c9dd84046aca31248a6e7a0d1725aaad2fb6a0d1deceba602a Google Meets recovered https://status.prod.unique.app/ Fri, 21 Nov 2025 13:19:49 +0000 https://status.prod.unique.app/#b797c8804dcfddce52fbeb398c0ba87a7e8d45221156de3eb6eb4b7bcc7ca32d Webhooks recovered https://status.prod.unique.app/ Fri, 21 Nov 2025 13:17:37 +0000 https://status.prod.unique.app/#d45415433ac9d7c9dd84046aca31248a6e7a0d1725aaad2fb6a0d1deceba602a Google Meets went down https://status.prod.unique.app/ Fri, 21 Nov 2025 13:16:46 +0000 https://status.prod.unique.app/#b797c8804dcfddce52fbeb398c0ba87a7e8d45221156de3eb6eb4b7bcc7ca32d Webhooks went down https://status.prod.unique.app/ Thu, 20 Nov 2025 21:18:40 +0000 https://status.prod.unique.app/#d0fdaf8d4de3c41b9b19ea8184e262de1da75a44b5df99be19fea90eb9e817ef Webhooks recovered https://status.prod.unique.app/ Thu, 20 Nov 2025 20:21:39 +0000 https://status.prod.unique.app/#d0fdaf8d4de3c41b9b19ea8184e262de1da75a44b5df99be19fea90eb9e817ef Webhooks went down https://status.prod.unique.app/ Mon, 17 Nov 2025 02:52:26 +0000 https://status.prod.unique.app/#a8480610026a85cd50d9d6d38aef4bad0708eefb372e21f4c180fcca40e8d544 Google Calendar recovered https://status.prod.unique.app/ Mon, 17 Nov 2025 02:49:25 +0000 https://status.prod.unique.app/#a8480610026a85cd50d9d6d38aef4bad0708eefb372e21f4c180fcca40e8d544 Google Calendar went down https://status.prod.unique.app/ Thu, 13 Nov 2025 19:36:05 +0000 https://status.prod.unique.app/#54758406d5b5b72369ad057bed0da002f339e01eb490c1643cc212174c6c3852 Knowledge/Ingestion recovered https://status.prod.unique.app/ Thu, 13 Nov 2025 19:34:05 +0000 https://status.prod.unique.app/#504fc964f46c8155f1c0925ac59cdce33469285f524e32bf4ac051cacf9779e7 Chat recovered https://status.prod.unique.app/ Thu, 13 Nov 2025 19:33:04 +0000 https://status.prod.unique.app/#54758406d5b5b72369ad057bed0da002f339e01eb490c1643cc212174c6c3852 Knowledge/Ingestion went down https://status.prod.unique.app/ Thu, 13 Nov 2025 19:28:04 +0000 https://status.prod.unique.app/#504fc964f46c8155f1c0925ac59cdce33469285f524e32bf4ac051cacf9779e7 Chat went down https://status.prod.unique.app/ Mon, 03 Nov 2025 03:32:05 +0000 https://status.prod.unique.app/#707128c41cbe3d14baac558191c383c1d3ca2f8a0477558b6819ea25580d08ec Google Meets recovered https://status.prod.unique.app/ Mon, 03 Nov 2025 03:29:05 +0000 https://status.prod.unique.app/#707128c41cbe3d14baac558191c383c1d3ca2f8a0477558b6819ea25580d08ec Google Meets went down https://status.prod.unique.app/ Mon, 03 Nov 2025 03:11:05 +0000 https://status.prod.unique.app/#7d6fbfe5ef81ad83ed43557a220787d97c456da833583354756a06147be575bc Google Meets recovered https://status.prod.unique.app/ Mon, 03 Nov 2025 03:08:04 +0000 https://status.prod.unique.app/#7d6fbfe5ef81ad83ed43557a220787d97c456da833583354756a06147be575bc Google Meets went down https://status.prod.unique.app/ Wed, 29 Oct 2025 20:54:54 +0000 https://status.prod.unique.app/#3d4d0c131d96a9e8ced79f740c11c0e100ce8632beb58ecf107b478557c39f21 Google Meets recovered https://status.prod.unique.app/ Wed, 29 Oct 2025 20:54:28 +0000 https://status.prod.unique.app/#d5f65cb04ef959df7a700b13c64e1188239e410ba82dd83a9fa4460661021b72 Microsoft recovered https://status.prod.unique.app/ Wed, 29 Oct 2025 20:54:09 +0000 https://status.prod.unique.app/#8d732d179965383a5457fda259eb9bd736aba87a677eaa31c0f67814f501ee49 Webhooks recovered https://status.prod.unique.app/ Wed, 29 Oct 2025 20:52:15 +0000 https://status.prod.unique.app/#3d4d0c131d96a9e8ced79f740c11c0e100ce8632beb58ecf107b478557c39f21 Google Meets went down https://status.prod.unique.app/ Wed, 29 Oct 2025 20:51:28 +0000 https://status.prod.unique.app/#d5f65cb04ef959df7a700b13c64e1188239e410ba82dd83a9fa4460661021b72 Microsoft went down https://status.prod.unique.app/ Wed, 29 Oct 2025 20:51:09 +0000 https://status.prod.unique.app/#8d732d179965383a5457fda259eb9bd736aba87a677eaa31c0f67814f501ee49 Webhooks went down https://status.prod.unique.app/ Wed, 29 Oct 2025 12:12:33 +0000 https://status.prod.unique.app/#bb923c2166ba7b01285481cedfe29880953cfbc88449e3253e828122d184b3a3 Chat recovered https://status.prod.unique.app/ Wed, 29 Oct 2025 12:09:32 +0000 https://status.prod.unique.app/#bb923c2166ba7b01285481cedfe29880953cfbc88449e3253e828122d184b3a3 Chat went down https://status.prod.unique.app/ Tue, 28 Oct 2025 13:24:04 +0000 https://status.prod.unique.app/#8a427c91171f84ae94e907e74d7ca2ef15d0779cb70d423f079e4682d5ba0784 Google Meets recovered https://status.prod.unique.app/ Tue, 28 Oct 2025 13:23:34 +0000 https://status.prod.unique.app/#0ac8e4208bc66bc24d6409672eb39e6be50b1c86d25b6b2b8aa7dbba6e164703 Microsoft recovered https://status.prod.unique.app/ Tue, 28 Oct 2025 13:23:21 +0000 https://status.prod.unique.app/#a6d2f70ec98e665ce0b776f3df1fdc3c7aa7bf781e9b1fdb6d87d49ec3956f25 Webhooks recovered https://status.prod.unique.app/ Tue, 28 Oct 2025 13:21:48 +0000 https://status.prod.unique.app/#3252e774b77bdf3f7ef676e9f8e64de5f32787d32af89a45f9c626ad132c229f Google Calendar recovered https://status.prod.unique.app/ Tue, 28 Oct 2025 13:21:04 +0000 https://status.prod.unique.app/#8a427c91171f84ae94e907e74d7ca2ef15d0779cb70d423f079e4682d5ba0784 Google Meets went down https://status.prod.unique.app/ Tue, 28 Oct 2025 13:20:34 +0000 https://status.prod.unique.app/#0ac8e4208bc66bc24d6409672eb39e6be50b1c86d25b6b2b8aa7dbba6e164703 Microsoft went down https://status.prod.unique.app/ Tue, 28 Oct 2025 13:20:23 +0000 https://status.prod.unique.app/#a6d2f70ec98e665ce0b776f3df1fdc3c7aa7bf781e9b1fdb6d87d49ec3956f25 Webhooks went down https://status.prod.unique.app/ Tue, 28 Oct 2025 13:19:46 +0000 https://status.prod.unique.app/#3252e774b77bdf3f7ef676e9f8e64de5f32787d32af89a45f9c626ad132c229f Google Calendar went down https://status.prod.unique.app/ Mon, 27 Oct 2025 17:42:13 +0000 https://status.prod.unique.app/#3be9ffeb8b1360ca09e0ba0f72d311069a465d6d7f9f7610cbcb36b2e4b4b146 Google Calendar recovered https://status.prod.unique.app/ Mon, 27 Oct 2025 17:41:07 +0000 https://status.prod.unique.app/#e607123be35ed1fb9980880b402a468e3c42d839db41e40508e80f743cc6e661 Microsoft recovered https://status.prod.unique.app/ Mon, 27 Oct 2025 17:40:42 +0000 https://status.prod.unique.app/#465538363ddd77d15cc3ade1ed9ee9c87a6da4c690844cf7b81ea1cb530620b1 Webhooks recovered https://status.prod.unique.app/ Mon, 27 Oct 2025 17:39:38 +0000 https://status.prod.unique.app/#3be9ffeb8b1360ca09e0ba0f72d311069a465d6d7f9f7610cbcb36b2e4b4b146 Google Calendar went down https://status.prod.unique.app/ Mon, 27 Oct 2025 17:38:01 +0000 https://status.prod.unique.app/#e607123be35ed1fb9980880b402a468e3c42d839db41e40508e80f743cc6e661 Microsoft went down https://status.prod.unique.app/ Mon, 27 Oct 2025 17:37:41 +0000 https://status.prod.unique.app/#465538363ddd77d15cc3ade1ed9ee9c87a6da4c690844cf7b81ea1cb530620b1 Webhooks went down https://status.prod.unique.app/ Mon, 27 Oct 2025 16:24:18 +0000 https://status.prod.unique.app/#686fde7203d9dc339869a39783eea87c24b2b5eacdea5d4a5a76b1b709537afc Google Calendar recovered https://status.prod.unique.app/ Mon, 27 Oct 2025 16:24:15 +0000 https://status.prod.unique.app/#0bc6a4c5879395a9a678d2fdf232b220b06a596596aaf84b81d03e026b04f44a Microsoft recovered https://status.prod.unique.app/ Mon, 27 Oct 2025 16:23:48 +0000 https://status.prod.unique.app/#0ba4fef6f1d1b052e08cdc1cb6fbdc663ce5fd3a4e618c304fa892b380481d29 Webhooks recovered https://status.prod.unique.app/ Mon, 27 Oct 2025 16:23:39 +0000 https://status.prod.unique.app/#2066e41a5ca1ed660d124ad83de437425da5cabe1f2531e3c2d5cea090d807b7 Google Meets recovered https://status.prod.unique.app/ Mon, 27 Oct 2025 16:21:30 +0000 https://status.prod.unique.app/#686fde7203d9dc339869a39783eea87c24b2b5eacdea5d4a5a76b1b709537afc Google Calendar went down https://status.prod.unique.app/ Mon, 27 Oct 2025 16:20:32 +0000 https://status.prod.unique.app/#2066e41a5ca1ed660d124ad83de437425da5cabe1f2531e3c2d5cea090d807b7 Google Meets went down https://status.prod.unique.app/ Mon, 27 Oct 2025 16:20:18 +0000 https://status.prod.unique.app/#0ba4fef6f1d1b052e08cdc1cb6fbdc663ce5fd3a4e618c304fa892b380481d29 Webhooks went down https://status.prod.unique.app/ Mon, 27 Oct 2025 16:20:10 +0000 https://status.prod.unique.app/#0bc6a4c5879395a9a678d2fdf232b220b06a596596aaf84b81d03e026b04f44a Microsoft went down https://status.prod.unique.app/ Mon, 27 Oct 2025 15:45:14 +0000 https://status.prod.unique.app/#b502c192c93da9e2eb71cf3a7ad01ebc5ad19ae5a4ec72b636f07bd3ff37d567 Google Calendar recovered https://status.prod.unique.app/ Mon, 27 Oct 2025 15:44:32 +0000 https://status.prod.unique.app/#98ad14ff2b225156926258156d1cb9dc69e1f14b80bcfedff6396ea4e0d902e3 Google Meets recovered https://status.prod.unique.app/ Mon, 27 Oct 2025 15:43:59 +0000 https://status.prod.unique.app/#5a1b1efb858b7a947082482dfe5d975c27be896a47f50e057aee6ca4097fd2a3 Microsoft recovered https://status.prod.unique.app/ Mon, 27 Oct 2025 15:43:41 +0000 https://status.prod.unique.app/#4bef34f3d473c1f16d6e08b36b5d113b839480b6fdcc501f5e7d2e8ea26cab0d Webhooks recovered https://status.prod.unique.app/ Mon, 27 Oct 2025 15:42:34 +0000 https://status.prod.unique.app/#b502c192c93da9e2eb71cf3a7ad01ebc5ad19ae5a4ec72b636f07bd3ff37d567 Google Calendar went down https://status.prod.unique.app/ Mon, 27 Oct 2025 15:41:30 +0000 https://status.prod.unique.app/#98ad14ff2b225156926258156d1cb9dc69e1f14b80bcfedff6396ea4e0d902e3 Google Meets went down https://status.prod.unique.app/ Mon, 27 Oct 2025 15:41:23 +0000 https://status.prod.unique.app/#4bef34f3d473c1f16d6e08b36b5d113b839480b6fdcc501f5e7d2e8ea26cab0d Webhooks went down https://status.prod.unique.app/ Mon, 27 Oct 2025 15:41:03 +0000 https://status.prod.unique.app/#5a1b1efb858b7a947082482dfe5d975c27be896a47f50e057aee6ca4097fd2a3 Microsoft went down https://status.prod.unique.app/ Mon, 27 Oct 2025 03:10:52 +0000 https://status.prod.unique.app/#3823f370af4757326c804e2e67dc6c88d95b7fbbc200cc19923af62b9ed02546 Microsoft recovered https://status.prod.unique.app/ Mon, 27 Oct 2025 03:10:32 +0000 https://status.prod.unique.app/#9cd1f6ae31971268324224c961e742d8f31a8c0b34ec69066bcbea0cfb51d955 Webhooks recovered https://status.prod.unique.app/ Mon, 27 Oct 2025 03:09:01 +0000 https://status.prod.unique.app/#5ffe3646f0240367f679ee13ed629b7f2a134dd24c99045a874d5f30f4adb24f Google Calendar recovered https://status.prod.unique.app/ Mon, 27 Oct 2025 03:08:02 +0000 https://status.prod.unique.app/#3823f370af4757326c804e2e67dc6c88d95b7fbbc200cc19923af62b9ed02546 Microsoft went down https://status.prod.unique.app/ Mon, 27 Oct 2025 03:07:29 +0000 https://status.prod.unique.app/#9cd1f6ae31971268324224c961e742d8f31a8c0b34ec69066bcbea0cfb51d955 Webhooks went down https://status.prod.unique.app/ Mon, 27 Oct 2025 03:06:21 +0000 https://status.prod.unique.app/#5ffe3646f0240367f679ee13ed629b7f2a134dd24c99045a874d5f30f4adb24f Google Calendar went down https://status.prod.unique.app/ Wed, 22 Oct 2025 13:08:56 +0000 https://status.prod.unique.app/#5bf07d5e38721e043c35c0363da3784fcb5a7d6fd01dd50d06f8fc5631e6eed9 Google Meets recovered https://status.prod.unique.app/ Wed, 22 Oct 2025 13:08:36 +0000 https://status.prod.unique.app/#2a8420d109aa391e3292c882f427ceaf7d040f9dc1cb0315c230a43572e277b1 Microsoft recovered https://status.prod.unique.app/ Wed, 22 Oct 2025 13:08:25 +0000 https://status.prod.unique.app/#46a57abba06018788f627bf321454d471fe47bbf34550afa9d1ce6908f291a43 Webhooks recovered https://status.prod.unique.app/ Wed, 22 Oct 2025 13:05:56 +0000 https://status.prod.unique.app/#5bf07d5e38721e043c35c0363da3784fcb5a7d6fd01dd50d06f8fc5631e6eed9 Google Meets went down https://status.prod.unique.app/ Wed, 22 Oct 2025 13:05:28 +0000 https://status.prod.unique.app/#2a8420d109aa391e3292c882f427ceaf7d040f9dc1cb0315c230a43572e277b1 Microsoft went down https://status.prod.unique.app/ Wed, 22 Oct 2025 13:05:10 +0000 https://status.prod.unique.app/#46a57abba06018788f627bf321454d471fe47bbf34550afa9d1ce6908f291a43 Webhooks went down https://status.prod.unique.app/ Tue, 21 Oct 2025 16:23:05 +0000 https://status.prod.unique.app/#c17da9c507e6d6e7c464386fdaed3efcf898b695752ce41f30201dd746cccb10 Google Meets recovered https://status.prod.unique.app/ Tue, 21 Oct 2025 16:22:35 +0000 https://status.prod.unique.app/#5a18381c73ab8b81c0a25dcb75160cf3ef0a796ee20c09d8f07095605a138b2a Microsoft recovered https://status.prod.unique.app/ Tue, 21 Oct 2025 16:22:15 +0000 https://status.prod.unique.app/#0fd68811a3aa90f9b386bc71a36dbc5d54cf42392fa00cc87e0f50eebec229ec Webhooks recovered https://status.prod.unique.app/ Tue, 21 Oct 2025 16:20:05 +0000 https://status.prod.unique.app/#c17da9c507e6d6e7c464386fdaed3efcf898b695752ce41f30201dd746cccb10 Google Meets went down https://status.prod.unique.app/ Tue, 21 Oct 2025 16:19:34 +0000 https://status.prod.unique.app/#5a18381c73ab8b81c0a25dcb75160cf3ef0a796ee20c09d8f07095605a138b2a Microsoft went down https://status.prod.unique.app/ Tue, 21 Oct 2025 16:19:13 +0000 https://status.prod.unique.app/#0fd68811a3aa90f9b386bc71a36dbc5d54cf42392fa00cc87e0f50eebec229ec Webhooks went down https://status.prod.unique.app/ Tue, 21 Oct 2025 13:10:23 +0000 https://status.prod.unique.app/#6cd6b59dc11aa454bf50d19378817e1a5545f810b8017880df9ef503227fea40 Google Meets recovered https://status.prod.unique.app/ Tue, 21 Oct 2025 13:09:55 +0000 https://status.prod.unique.app/#ca4e3f49399eceb572d6ff55bae1c7ff64dbe84d0e7c25d80a7cdf4617cd9d68 Microsoft recovered https://status.prod.unique.app/ Tue, 21 Oct 2025 13:07:37 +0000 https://status.prod.unique.app/#6cd6b59dc11aa454bf50d19378817e1a5545f810b8017880df9ef503227fea40 Google Meets went down https://status.prod.unique.app/ Tue, 21 Oct 2025 13:06:52 +0000 https://status.prod.unique.app/#ca4e3f49399eceb572d6ff55bae1c7ff64dbe84d0e7c25d80a7cdf4617cd9d68 Microsoft went down https://status.prod.unique.app/ Mon, 20 Oct 2025 16:54:23 +0000 https://status.prod.unique.app/#f3f2326a02b24ffd43377029c79269927aeadc47920888b87d105b8ef29d2cb7 Webhooks recovered https://status.prod.unique.app/ Mon, 20 Oct 2025 16:50:08 +0000 https://status.prod.unique.app/#f3f2326a02b24ffd43377029c79269927aeadc47920888b87d105b8ef29d2cb7 Webhooks went down https://status.prod.unique.app/ Mon, 20 Oct 2025 14:33:34 +0000 https://status.prod.unique.app/#d14865ddf5d15e9a71b323199a11d93af06c836f46a2a40e855d0c3d3e44b318 Webhooks recovered https://status.prod.unique.app/ Mon, 20 Oct 2025 14:30:36 +0000 https://status.prod.unique.app/#d14865ddf5d15e9a71b323199a11d93af06c836f46a2a40e855d0c3d3e44b318 Webhooks went down https://status.prod.unique.app/ Mon, 20 Oct 2025 03:08:46 +0000 https://status.prod.unique.app/#b35a68d44142b85c9a7591a84a305a1c16a476576b2068b4ced81c2f4e4d2b63 Webhooks recovered https://status.prod.unique.app/ Mon, 20 Oct 2025 03:05:47 +0000 https://status.prod.unique.app/#b35a68d44142b85c9a7591a84a305a1c16a476576b2068b4ced81c2f4e4d2b63 Webhooks went down https://status.prod.unique.app/ Fri, 17 Oct 2025 14:23:10 +0000 https://status.prod.unique.app/#a3304fabba7a6da4af47df5cae421e0349f2af43a68aa8717fd2f4cf827d0067 Sidebar recovered https://status.prod.unique.app/ Fri, 17 Oct 2025 14:20:10 +0000 https://status.prod.unique.app/#a3304fabba7a6da4af47df5cae421e0349f2af43a68aa8717fd2f4cf827d0067 Sidebar went down https://status.prod.unique.app/ Thu, 16 Oct 2025 04:33:25 +0000 https://status.prod.unique.app/#90f2adb0c08848cc18e9a3a37effe12b43422e5d40cf13831ff60132c360930c Knowledge/Ingestion recovered https://status.prod.unique.app/ Thu, 16 Oct 2025 04:30:23 +0000 https://status.prod.unique.app/#90f2adb0c08848cc18e9a3a37effe12b43422e5d40cf13831ff60132c360930c Knowledge/Ingestion went down https://status.prod.unique.app/ Wed, 15 Oct 2025 01:04:51 +0000 https://status.prod.unique.app/#8143f25e940e269a3e05edf9f419103a8a11066f4b5d0200cc18856bae5de3e9 Knowledge/Ingestion recovered https://status.prod.unique.app/ Wed, 15 Oct 2025 01:01:56 +0000 https://status.prod.unique.app/#8143f25e940e269a3e05edf9f419103a8a11066f4b5d0200cc18856bae5de3e9 Knowledge/Ingestion went down https://status.prod.unique.app/ Mon, 13 Oct 2025 01:48:44 +0000 https://status.prod.unique.app/#759b967a7c32bd70c7bad93891693d0cfa559c184639b72ca716c4f78e1bceb1 Knowledge/Ingestion recovered https://status.prod.unique.app/ Mon, 13 Oct 2025 01:45:54 +0000 https://status.prod.unique.app/#759b967a7c32bd70c7bad93891693d0cfa559c184639b72ca716c4f78e1bceb1 Knowledge/Ingestion went down https://status.prod.unique.app/ Sun, 12 Oct 2025 00:57:15 +0000 https://status.prod.unique.app/#ea07089bd5ba68a8e95651a59df73e6804d566dab20eb2f7d13567c3e6b9413e Knowledge/Ingestion recovered https://status.prod.unique.app/ Sun, 12 Oct 2025 00:54:24 +0000 https://status.prod.unique.app/#ff681a9a08b84514a76382b210aca1eff1978628e6f107a4267525bd977c322b Google Meets recovered https://status.prod.unique.app/ Sun, 12 Oct 2025 00:54:16 +0000 https://status.prod.unique.app/#ea07089bd5ba68a8e95651a59df73e6804d566dab20eb2f7d13567c3e6b9413e Knowledge/Ingestion went down https://status.prod.unique.app/ Sun, 12 Oct 2025 00:48:25 +0000 https://status.prod.unique.app/#ff681a9a08b84514a76382b210aca1eff1978628e6f107a4267525bd977c322b Google Meets went down https://status.prod.unique.app/ Sun, 12 Oct 2025 00:14:47 +0000 https://status.prod.unique.app/#ce7c09d68ff23f668c59df739a1f75ba5bab362e71da668d9a48609d9587ae1b Scope Management recovered https://status.prod.unique.app/ Sun, 12 Oct 2025 00:12:26 +0000 https://status.prod.unique.app/#1a1e19e8db396c9c943beed8a13e698e7127f4fa4ad36c36a059b13f343b3812 Google Meets recovered https://status.prod.unique.app/ Sun, 12 Oct 2025 00:11:41 +0000 https://status.prod.unique.app/#8987e7b1d0d7b028ea4dd928b656bcf44757a11beca433586224310494799ca0 Webhooks recovered https://status.prod.unique.app/ Sun, 12 Oct 2025 00:10:07 +0000 https://status.prod.unique.app/#b2c7201aad3306ae87614212171da30033618ef3ba7823b1ac3874139c473a32 Google Calendar recovered https://status.prod.unique.app/ Sun, 12 Oct 2025 00:09:15 +0000 https://status.prod.unique.app/#ce7c09d68ff23f668c59df739a1f75ba5bab362e71da668d9a48609d9587ae1b Scope Management went down https://status.prod.unique.app/ Sun, 12 Oct 2025 00:05:05 +0000 https://status.prod.unique.app/#b2c7201aad3306ae87614212171da30033618ef3ba7823b1ac3874139c473a32 Google Calendar went down https://status.prod.unique.app/ Sun, 12 Oct 2025 00:04:26 +0000 https://status.prod.unique.app/#1a1e19e8db396c9c943beed8a13e698e7127f4fa4ad36c36a059b13f343b3812 Google Meets went down https://status.prod.unique.app/ Sun, 12 Oct 2025 00:03:51 +0000 https://status.prod.unique.app/#8987e7b1d0d7b028ea4dd928b656bcf44757a11beca433586224310494799ca0 Webhooks went down https://status.prod.unique.app/ Sat, 11 Oct 2025 01:38:54 +0000 https://status.prod.unique.app/#156b14690fcb4b115fe4e78d815e9fcaed81ffc180dd1219a2d3383a9d38edc1 Knowledge/Ingestion recovered https://status.prod.unique.app/ Sat, 11 Oct 2025 01:36:45 +0000 https://status.prod.unique.app/#156b14690fcb4b115fe4e78d815e9fcaed81ffc180dd1219a2d3383a9d38edc1 Knowledge/Ingestion went down https://status.prod.unique.app/ Fri, 10 Oct 2025 02:10:17 +0000 https://status.prod.unique.app/#b5fb4db50b64378dc9e47515d2a8cdfdfac7d5ac308927fe480e72b87151b192 Knowledge/Ingestion recovered https://status.prod.unique.app/ Fri, 10 Oct 2025 02:01:18 +0000 https://status.prod.unique.app/#b5fb4db50b64378dc9e47515d2a8cdfdfac7d5ac308927fe480e72b87151b192 Knowledge/Ingestion went down https://status.prod.unique.app/ Wed, 08 Oct 2025 20:11:57 +0000 https://status.prod.unique.app/#2c1fa4c324ae209a0ee3b8e6afed9cf33b5b95532d5178c4fa40ba5b3c2688c4 Sidebar recovered https://status.prod.unique.app/ Wed, 08 Oct 2025 20:08:54 +0000 https://status.prod.unique.app/#2c1fa4c324ae209a0ee3b8e6afed9cf33b5b95532d5178c4fa40ba5b3c2688c4 Sidebar went down https://status.prod.unique.app/ Wed, 08 Oct 2025 11:28:58 +0000 https://status.prod.unique.app/#6cf1d94ec6b33117e7a6840eed1dbdeae58c0cf9a4b0fbb8bedf073c5d798e68 Sidebar recovered https://status.prod.unique.app/ Wed, 08 Oct 2025 11:25:47 +0000 https://status.prod.unique.app/#6cf1d94ec6b33117e7a6840eed1dbdeae58c0cf9a4b0fbb8bedf073c5d798e68 Sidebar went down https://status.prod.unique.app/ Thu, 02 Oct 2025 17:09:36 +0000 https://status.prod.unique.app/#365b28a3d1b6d6089e2bdeea024c99a202a2da42bbad5daf6a275922502ef190 Sidebar recovered https://status.prod.unique.app/ Thu, 02 Oct 2025 17:06:36 +0000 https://status.prod.unique.app/#365b28a3d1b6d6089e2bdeea024c99a202a2da42bbad5daf6a275922502ef190 Sidebar went down https://status.prod.unique.app/ Thu, 02 Oct 2025 16:56:15 +0000 https://status.prod.unique.app/#82f58116482bfcf677e5a61cad0023c11a9a7a08cf501d57e768b7f9f1d251e4 Webhooks recovered https://status.prod.unique.app/ Thu, 02 Oct 2025 16:53:15 +0000 https://status.prod.unique.app/#82f58116482bfcf677e5a61cad0023c11a9a7a08cf501d57e768b7f9f1d251e4 Webhooks went down https://status.prod.unique.app/ Thu, 02 Oct 2025 07:22:02 +0000 https://status.prod.unique.app/#2982c83490c6736f457d314e1dee0a81e2fa371057ecdf7431841842a9d0e8a0 Knowledge Base recovered https://status.prod.unique.app/ Thu, 02 Oct 2025 07:19:03 +0000 https://status.prod.unique.app/#2982c83490c6736f457d314e1dee0a81e2fa371057ecdf7431841842a9d0e8a0 Knowledge Base went down https://status.prod.unique.app/ Sun, 28 Sep 2025 01:25:24 +0000 https://status.prod.unique.app/#70a7cb37334b827431f5ac12b2d93cf539cb59ac8243f479bf7c1470edd18b61 Google Calendar recovered https://status.prod.unique.app/ Sun, 28 Sep 2025 01:24:46 +0000 https://status.prod.unique.app/#985165103b2e5552af2f3751f350704183345f6946313d4bc613263b0e951d36 Google Meets recovered https://status.prod.unique.app/ Sun, 28 Sep 2025 01:22:26 +0000 https://status.prod.unique.app/#70a7cb37334b827431f5ac12b2d93cf539cb59ac8243f479bf7c1470edd18b61 Google Calendar went down https://status.prod.unique.app/ Sun, 28 Sep 2025 01:21:45 +0000 https://status.prod.unique.app/#985165103b2e5552af2f3751f350704183345f6946313d4bc613263b0e951d36 Google Meets went down https://status.prod.unique.app/ Sun, 28 Sep 2025 00:57:15 +0000 https://status.prod.unique.app/#f6271f060118c45d2d6e912fe95c508dbbab62028e42369c39d86769e617ad4e Microsoft recovered https://status.prod.unique.app/ Sun, 28 Sep 2025 00:56:56 +0000 https://status.prod.unique.app/#f064fc6a0436efd343af37b84b42fee4a43136d7bd2634552ccdf404fdff1b7a Webhooks recovered https://status.prod.unique.app/ Sun, 28 Sep 2025 00:55:14 +0000 https://status.prod.unique.app/#97162e1abbb91be58772f620740bafbaf6b63a110a281aade3ad2f1be3d58e5b Sidebar recovered https://status.prod.unique.app/ Sun, 28 Sep 2025 00:53:58 +0000 https://status.prod.unique.app/#f064fc6a0436efd343af37b84b42fee4a43136d7bd2634552ccdf404fdff1b7a Webhooks went down https://status.prod.unique.app/ Sun, 28 Sep 2025 00:52:15 +0000 https://status.prod.unique.app/#97162e1abbb91be58772f620740bafbaf6b63a110a281aade3ad2f1be3d58e5b Sidebar went down https://status.prod.unique.app/ Sun, 28 Sep 2025 00:51:45 +0000 https://status.prod.unique.app/#f6271f060118c45d2d6e912fe95c508dbbab62028e42369c39d86769e617ad4e Microsoft went down https://status.prod.unique.app/ Sun, 28 Sep 2025 00:45:11 +0000 https://status.prod.unique.app/#70a3493ce80c58c1359cb132e7e43fc9bb2b11e415929607c07b942b79ae9f67 Scope Management recovered https://status.prod.unique.app/ Sun, 28 Sep 2025 00:43:56 +0000 https://status.prod.unique.app/#fb8819509567ea19336481bb24b167b2a7466d0d1179822ed366480689308fbe Knowledge Base recovered https://status.prod.unique.app/ Sun, 28 Sep 2025 00:42:06 +0000 https://status.prod.unique.app/#70a3493ce80c58c1359cb132e7e43fc9bb2b11e415929607c07b942b79ae9f67 Scope Management went down https://status.prod.unique.app/ Sun, 28 Sep 2025 00:41:55 +0000 https://status.prod.unique.app/#fb8819509567ea19336481bb24b167b2a7466d0d1179822ed366480689308fbe Knowledge Base went down https://status.prod.unique.app/ Sun, 28 Sep 2025 00:39:45 +0000 https://status.prod.unique.app/#2c9ff0dd20a7c43d013e6a0e8abf28572e7778526176bd45fb6f91497f08a773 Google Meets recovered https://status.prod.unique.app/ Sun, 28 Sep 2025 00:36:45 +0000 https://status.prod.unique.app/#2c9ff0dd20a7c43d013e6a0e8abf28572e7778526176bd45fb6f91497f08a773 Google Meets went down https://status.prod.unique.app/ Sat, 27 Sep 2025 14:22:36 +0000 https://status.prod.unique.app/#9f7b4e0d479de81732dfc83c4d0f86e9d8fd860c66e45a0df234fd1d67370431 Chat recovered https://status.prod.unique.app/ Sat, 27 Sep 2025 03:34:34 +0000 https://status.prod.unique.app/#8869eba4d9c0d966e9f276cdf4bad1e7a6736a3929072e8df2f5c1d6ef67e266 Recording recovered https://status.prod.unique.app/ Sat, 27 Sep 2025 03:31:05 +0000 https://status.prod.unique.app/#dec2bcfdb73a520c34aa67e8b8f89441fffb8644e620e43c41b5f9c07bb7aec9 Sidebar recovered https://status.prod.unique.app/ Sat, 27 Sep 2025 03:30:15 +0000 https://status.prod.unique.app/#e8af22440d7102195c3932bc684677f8768ff68dfa725bb3d6d48a93b8759935 Scope Management recovered https://status.prod.unique.app/ Sat, 27 Sep 2025 03:30:13 +0000 https://status.prod.unique.app/#e3bd51dd52b10083b5ebae0a9ee567b73c33f7c1b69c082b2a06a7bf39594f02 Recording recovered https://status.prod.unique.app/ Sat, 27 Sep 2025 03:29:45 +0000 https://status.prod.unique.app/#0063d79eb9deb58187150dccfdcdf62ef5e4c8a435f8dfe52c0af237b40adeec Webhooks recovered https://status.prod.unique.app/ Sat, 27 Sep 2025 03:28:46 +0000 https://status.prod.unique.app/#6df69769eab2dabcd638fd9a4f9e43db473cf61e59b4c3e276867df2e3dd7856 Knowledge Base recovered https://status.prod.unique.app/ Sat, 27 Sep 2025 03:28:14 +0000 https://status.prod.unique.app/#cebdd3c36e0537608df7b61e8ad18d7b832d0c9ea2edb0f8a98b6e92f66767af Google Calendar recovered https://status.prod.unique.app/ Sat, 27 Sep 2025 03:27:54 +0000 https://status.prod.unique.app/#5ea2bd137447db1b1002ad98c5d8cab4ca1606e56196abb42e5e68ae9c475973 Sidebar recovered https://status.prod.unique.app/ Sat, 27 Sep 2025 03:27:45 +0000 https://status.prod.unique.app/#631f3f1789dacfcc9d09238309887c167fb6609f2437d3f3de076c117d609da0 IDP recovered https://status.prod.unique.app/ Sat, 27 Sep 2025 03:27:35 +0000 https://status.prod.unique.app/#d5a3678e0993e2e9d9b318e1dc6b2a38bf98274474323b73ffb10fdfc5d9df36 Google Meets recovered https://status.prod.unique.app/ Sat, 27 Sep 2025 03:27:26 +0000 https://status.prod.unique.app/#f032f4d6790bf3a63cce3b9149625bb9a3bac11c2781f0d9c1406379a262490f Knowledge/Ingestion recovered https://status.prod.unique.app/ Sat, 27 Sep 2025 03:27:24 +0000 https://status.prod.unique.app/#236a97a58ee7a6df0290872e02bd997a07fa6f80a2fcad863fdb7de5443ab909 Microsoft recovered https://status.prod.unique.app/ Sat, 27 Sep 2025 03:27:24 +0000 https://status.prod.unique.app/#c86030c41ffceaa3e110196901ea16b1b748dc4b21cb30b12884d3a4b2bf399b Chat recovered https://status.prod.unique.app/ Fri, 26 Sep 2025 23:56:42 +0000 https://status.prod.unique.app/#6df69769eab2dabcd638fd9a4f9e43db473cf61e59b4c3e276867df2e3dd7856 Knowledge Base went down https://status.prod.unique.app/ Fri, 26 Sep 2025 23:54:51 +0000 https://status.prod.unique.app/#e3bd51dd52b10083b5ebae0a9ee567b73c33f7c1b69c082b2a06a7bf39594f02 Recording went down https://status.prod.unique.app/ Fri, 26 Sep 2025 23:54:51 +0000 https://status.prod.unique.app/#e8af22440d7102195c3932bc684677f8768ff68dfa725bb3d6d48a93b8759935 Scope Management went down https://status.prod.unique.app/ Fri, 26 Sep 2025 23:54:42 +0000 https://status.prod.unique.app/#0063d79eb9deb58187150dccfdcdf62ef5e4c8a435f8dfe52c0af237b40adeec Webhooks went down https://status.prod.unique.app/ Fri, 26 Sep 2025 23:53:36 +0000 https://status.prod.unique.app/#8869eba4d9c0d966e9f276cdf4bad1e7a6736a3929072e8df2f5c1d6ef67e266 Recording went down https://status.prod.unique.app/ Fri, 26 Sep 2025 23:53:23 +0000 https://status.prod.unique.app/#9f7b4e0d479de81732dfc83c4d0f86e9d8fd860c66e45a0df234fd1d67370431 Chat went down https://status.prod.unique.app/ Fri, 26 Sep 2025 23:53:18 +0000 https://status.prod.unique.app/#cebdd3c36e0537608df7b61e8ad18d7b832d0c9ea2edb0f8a98b6e92f66767af Google Calendar went down https://status.prod.unique.app/ Fri, 26 Sep 2025 23:53:10 +0000 https://status.prod.unique.app/#dec2bcfdb73a520c34aa67e8b8f89441fffb8644e620e43c41b5f9c07bb7aec9 Sidebar went down https://status.prod.unique.app/ Fri, 26 Sep 2025 23:53:05 +0000 https://status.prod.unique.app/#5ea2bd137447db1b1002ad98c5d8cab4ca1606e56196abb42e5e68ae9c475973 Sidebar went down https://status.prod.unique.app/ Fri, 26 Sep 2025 23:52:41 +0000 https://status.prod.unique.app/#631f3f1789dacfcc9d09238309887c167fb6609f2437d3f3de076c117d609da0 IDP went down https://status.prod.unique.app/ Fri, 26 Sep 2025 23:52:27 +0000 https://status.prod.unique.app/#d5a3678e0993e2e9d9b318e1dc6b2a38bf98274474323b73ffb10fdfc5d9df36 Google Meets went down https://status.prod.unique.app/ Fri, 26 Sep 2025 23:52:18 +0000 https://status.prod.unique.app/#f032f4d6790bf3a63cce3b9149625bb9a3bac11c2781f0d9c1406379a262490f Knowledge/Ingestion went down https://status.prod.unique.app/ Fri, 26 Sep 2025 23:52:12 +0000 https://status.prod.unique.app/#c86030c41ffceaa3e110196901ea16b1b748dc4b21cb30b12884d3a4b2bf399b Chat went down https://status.prod.unique.app/ Fri, 26 Sep 2025 23:52:02 +0000 https://status.prod.unique.app/#236a97a58ee7a6df0290872e02bd997a07fa6f80a2fcad863fdb7de5443ab909 Microsoft went down https://status.prod.unique.app/ Wed, 24 Sep 2025 21:49:04 +0000 https://status.prod.unique.app/#bb1ccc66cc2b5ba1bbed721443332cff865b92250b0547293b76ace50eab222d Google Calendar recovered https://status.prod.unique.app/ Wed, 24 Sep 2025 21:46:06 +0000 https://status.prod.unique.app/#bb1ccc66cc2b5ba1bbed721443332cff865b92250b0547293b76ace50eab222d Google Calendar went down https://status.prod.unique.app/ Wed, 24 Sep 2025 10:57:14 +0000 https://status.prod.unique.app/#964974595ab7bc6b6046a7e30c389b3b08952ad93500423db08196016e64b7f1 Knowledge/Ingestion recovered https://status.prod.unique.app/ Wed, 24 Sep 2025 10:54:12 +0000 https://status.prod.unique.app/#964974595ab7bc6b6046a7e30c389b3b08952ad93500423db08196016e64b7f1 Knowledge/Ingestion went down https://status.prod.unique.app/incident/546339 Wed, 16 Apr 2025 19:57:25 -0000 https://status.prod.unique.app/incident/546339#3b9fe53beb85191ced92eca7c428b64da77d970dcc50b22ce248e122fa604a8e Maintenance completed https://status.prod.unique.app/incident/546339 Wed, 16 Apr 2025 19:57:25 -0000 https://status.prod.unique.app/incident/546339#3b9fe53beb85191ced92eca7c428b64da77d970dcc50b22ce248e122fa604a8e Maintenance completed https://status.prod.unique.app/incident/546339 Wed, 16 Apr 2025 19:57:25 -0000 https://status.prod.unique.app/incident/546339#3b9fe53beb85191ced92eca7c428b64da77d970dcc50b22ce248e122fa604a8e Maintenance completed https://status.prod.unique.app/incident/546339 Wed, 16 Apr 2025 19:57:25 -0000 https://status.prod.unique.app/incident/546339#3b9fe53beb85191ced92eca7c428b64da77d970dcc50b22ce248e122fa604a8e Maintenance completed https://status.prod.unique.app/incident/546339 Wed, 16 Apr 2025 19:57:25 -0000 https://status.prod.unique.app/incident/546339#3b9fe53beb85191ced92eca7c428b64da77d970dcc50b22ce248e122fa604a8e Maintenance completed https://status.prod.unique.app/incident/546339 Wed, 16 Apr 2025 19:57:25 -0000 https://status.prod.unique.app/incident/546339#3b9fe53beb85191ced92eca7c428b64da77d970dcc50b22ce248e122fa604a8e Maintenance completed https://status.prod.unique.app/incident/546339 Wed, 16 Apr 2025 19:57:25 -0000 https://status.prod.unique.app/incident/546339#3b9fe53beb85191ced92eca7c428b64da77d970dcc50b22ce248e122fa604a8e Maintenance completed https://status.prod.unique.app/incident/546339 Wed, 16 Apr 2025 19:57:25 -0000 https://status.prod.unique.app/incident/546339#3b9fe53beb85191ced92eca7c428b64da77d970dcc50b22ce248e122fa604a8e Maintenance completed https://status.prod.unique.app/incident/546339 Wed, 16 Apr 2025 19:57:25 -0000 https://status.prod.unique.app/incident/546339#3b9fe53beb85191ced92eca7c428b64da77d970dcc50b22ce248e122fa604a8e Maintenance completed https://status.prod.unique.app/incident/546339 Wed, 16 Apr 2025 19:57:25 -0000 https://status.prod.unique.app/incident/546339#3b9fe53beb85191ced92eca7c428b64da77d970dcc50b22ce248e122fa604a8e Maintenance completed https://status.prod.unique.app/incident/546339 Wed, 16 Apr 2025 19:57:25 -0000 https://status.prod.unique.app/incident/546339#3b9fe53beb85191ced92eca7c428b64da77d970dcc50b22ce248e122fa604a8e Maintenance completed https://status.prod.unique.app/incident/546339 Wed, 16 Apr 2025 19:57:25 -0000 https://status.prod.unique.app/incident/546339#3b9fe53beb85191ced92eca7c428b64da77d970dcc50b22ce248e122fa604a8e Maintenance completed https://status.prod.unique.app/incident/546339 Wed, 16 Apr 2025 19:57:25 -0000 https://status.prod.unique.app/incident/546339#3b9fe53beb85191ced92eca7c428b64da77d970dcc50b22ce248e122fa604a8e Maintenance completed https://status.prod.unique.app/incident/546339 Wed, 16 Apr 2025 19:57:25 -0000 https://status.prod.unique.app/incident/546339#3b9fe53beb85191ced92eca7c428b64da77d970dcc50b22ce248e122fa604a8e Maintenance completed https://status.prod.unique.app/incident/546339 Wed, 16 Apr 2025 19:00:58 -0000 https://status.prod.unique.app/incident/546339#ee60abf751b9553a204cd7c386b1110113a65329cd1ffe70b353b6404d00ac93 We upgraded the underlying Kubernetes cluster to a newer version. No noticeable degradations occurred. https://status.prod.unique.app/incident/546339 Wed, 16 Apr 2025 19:00:58 -0000 https://status.prod.unique.app/incident/546339#ee60abf751b9553a204cd7c386b1110113a65329cd1ffe70b353b6404d00ac93 We upgraded the underlying Kubernetes cluster to a newer version. No noticeable degradations occurred. https://status.prod.unique.app/incident/546339 Wed, 16 Apr 2025 19:00:58 -0000 https://status.prod.unique.app/incident/546339#ee60abf751b9553a204cd7c386b1110113a65329cd1ffe70b353b6404d00ac93 We upgraded the underlying Kubernetes cluster to a newer version. No noticeable degradations occurred. https://status.prod.unique.app/incident/546339 Wed, 16 Apr 2025 19:00:58 -0000 https://status.prod.unique.app/incident/546339#ee60abf751b9553a204cd7c386b1110113a65329cd1ffe70b353b6404d00ac93 We upgraded the underlying Kubernetes cluster to a newer version. No noticeable degradations occurred. https://status.prod.unique.app/incident/546339 Wed, 16 Apr 2025 19:00:58 -0000 https://status.prod.unique.app/incident/546339#ee60abf751b9553a204cd7c386b1110113a65329cd1ffe70b353b6404d00ac93 We upgraded the underlying Kubernetes cluster to a newer version. No noticeable degradations occurred. https://status.prod.unique.app/incident/546339 Wed, 16 Apr 2025 19:00:58 -0000 https://status.prod.unique.app/incident/546339#ee60abf751b9553a204cd7c386b1110113a65329cd1ffe70b353b6404d00ac93 We upgraded the underlying Kubernetes cluster to a newer version. No noticeable degradations occurred. https://status.prod.unique.app/incident/546339 Wed, 16 Apr 2025 19:00:58 -0000 https://status.prod.unique.app/incident/546339#ee60abf751b9553a204cd7c386b1110113a65329cd1ffe70b353b6404d00ac93 We upgraded the underlying Kubernetes cluster to a newer version. No noticeable degradations occurred. https://status.prod.unique.app/incident/546339 Wed, 16 Apr 2025 19:00:58 -0000 https://status.prod.unique.app/incident/546339#ee60abf751b9553a204cd7c386b1110113a65329cd1ffe70b353b6404d00ac93 We upgraded the underlying Kubernetes cluster to a newer version. No noticeable degradations occurred. https://status.prod.unique.app/incident/546339 Wed, 16 Apr 2025 19:00:58 -0000 https://status.prod.unique.app/incident/546339#ee60abf751b9553a204cd7c386b1110113a65329cd1ffe70b353b6404d00ac93 We upgraded the underlying Kubernetes cluster to a newer version. No noticeable degradations occurred. https://status.prod.unique.app/incident/546339 Wed, 16 Apr 2025 19:00:58 -0000 https://status.prod.unique.app/incident/546339#ee60abf751b9553a204cd7c386b1110113a65329cd1ffe70b353b6404d00ac93 We upgraded the underlying Kubernetes cluster to a newer version. No noticeable degradations occurred. https://status.prod.unique.app/incident/546339 Wed, 16 Apr 2025 19:00:58 -0000 https://status.prod.unique.app/incident/546339#ee60abf751b9553a204cd7c386b1110113a65329cd1ffe70b353b6404d00ac93 We upgraded the underlying Kubernetes cluster to a newer version. No noticeable degradations occurred. https://status.prod.unique.app/incident/546339 Wed, 16 Apr 2025 19:00:58 -0000 https://status.prod.unique.app/incident/546339#ee60abf751b9553a204cd7c386b1110113a65329cd1ffe70b353b6404d00ac93 We upgraded the underlying Kubernetes cluster to a newer version. No noticeable degradations occurred. https://status.prod.unique.app/incident/546339 Wed, 16 Apr 2025 19:00:58 -0000 https://status.prod.unique.app/incident/546339#ee60abf751b9553a204cd7c386b1110113a65329cd1ffe70b353b6404d00ac93 We upgraded the underlying Kubernetes cluster to a newer version. No noticeable degradations occurred. https://status.prod.unique.app/incident/546339 Wed, 16 Apr 2025 19:00:58 -0000 https://status.prod.unique.app/incident/546339#ee60abf751b9553a204cd7c386b1110113a65329cd1ffe70b353b6404d00ac93 We upgraded the underlying Kubernetes cluster to a newer version. No noticeable degradations occurred. https://status.prod.unique.app/incident/515093 Wed, 19 Feb 2025 00:00:00 -0000 https://status.prod.unique.app/incident/515093#fdaca75094cf09d4ade66094e8ee99e82ee9681b655b4935b1f448251fde8169 Maintenance completed https://status.prod.unique.app/incident/515093 Wed, 19 Feb 2025 00:00:00 -0000 https://status.prod.unique.app/incident/515093#fdaca75094cf09d4ade66094e8ee99e82ee9681b655b4935b1f448251fde8169 Maintenance completed https://status.prod.unique.app/incident/515093 Wed, 19 Feb 2025 00:00:00 -0000 https://status.prod.unique.app/incident/515093#fdaca75094cf09d4ade66094e8ee99e82ee9681b655b4935b1f448251fde8169 Maintenance completed https://status.prod.unique.app/incident/515093 Wed, 19 Feb 2025 00:00:00 -0000 https://status.prod.unique.app/incident/515093#fdaca75094cf09d4ade66094e8ee99e82ee9681b655b4935b1f448251fde8169 Maintenance completed https://status.prod.unique.app/incident/515093 Wed, 19 Feb 2025 00:00:00 -0000 https://status.prod.unique.app/incident/515093#fdaca75094cf09d4ade66094e8ee99e82ee9681b655b4935b1f448251fde8169 Maintenance completed https://status.prod.unique.app/incident/515093 Wed, 19 Feb 2025 00:00:00 -0000 https://status.prod.unique.app/incident/515093#fdaca75094cf09d4ade66094e8ee99e82ee9681b655b4935b1f448251fde8169 Maintenance completed https://status.prod.unique.app/incident/515093 Wed, 19 Feb 2025 00:00:00 -0000 https://status.prod.unique.app/incident/515093#fdaca75094cf09d4ade66094e8ee99e82ee9681b655b4935b1f448251fde8169 Maintenance completed https://status.prod.unique.app/incident/515093 Wed, 19 Feb 2025 00:00:00 -0000 https://status.prod.unique.app/incident/515093#fdaca75094cf09d4ade66094e8ee99e82ee9681b655b4935b1f448251fde8169 Maintenance completed https://status.prod.unique.app/incident/515093 Wed, 19 Feb 2025 00:00:00 -0000 https://status.prod.unique.app/incident/515093#fdaca75094cf09d4ade66094e8ee99e82ee9681b655b4935b1f448251fde8169 Maintenance completed https://status.prod.unique.app/incident/515093 Wed, 19 Feb 2025 00:00:00 -0000 https://status.prod.unique.app/incident/515093#fdaca75094cf09d4ade66094e8ee99e82ee9681b655b4935b1f448251fde8169 Maintenance completed https://status.prod.unique.app/incident/515093 Wed, 19 Feb 2025 00:00:00 -0000 https://status.prod.unique.app/incident/515093#fdaca75094cf09d4ade66094e8ee99e82ee9681b655b4935b1f448251fde8169 Maintenance completed https://status.prod.unique.app/incident/515093 Wed, 19 Feb 2025 00:00:00 -0000 https://status.prod.unique.app/incident/515093#fdaca75094cf09d4ade66094e8ee99e82ee9681b655b4935b1f448251fde8169 Maintenance completed https://status.prod.unique.app/incident/515093 Wed, 19 Feb 2025 00:00:00 -0000 https://status.prod.unique.app/incident/515093#fdaca75094cf09d4ade66094e8ee99e82ee9681b655b4935b1f448251fde8169 Maintenance completed https://status.prod.unique.app/incident/515093 Wed, 19 Feb 2025 00:00:00 -0000 https://status.prod.unique.app/incident/515093#fdaca75094cf09d4ade66094e8ee99e82ee9681b655b4935b1f448251fde8169 Maintenance completed https://status.prod.unique.app/incident/515093 Tue, 18 Feb 2025 21:00:00 -0000 https://status.prod.unique.app/incident/515093#2460a8166702ff6e7e035fc828c55611311cfe2c1c3ef40681c090fe1475a830 Correcting https://status.prod.unique.app/incident/514786, cluster will experience downtime https://status.prod.unique.app/incident/515093 Tue, 18 Feb 2025 21:00:00 -0000 https://status.prod.unique.app/incident/515093#2460a8166702ff6e7e035fc828c55611311cfe2c1c3ef40681c090fe1475a830 Correcting https://status.prod.unique.app/incident/514786, cluster will experience downtime https://status.prod.unique.app/incident/515093 Tue, 18 Feb 2025 21:00:00 -0000 https://status.prod.unique.app/incident/515093#2460a8166702ff6e7e035fc828c55611311cfe2c1c3ef40681c090fe1475a830 Correcting https://status.prod.unique.app/incident/514786, cluster will experience downtime https://status.prod.unique.app/incident/515093 Tue, 18 Feb 2025 21:00:00 -0000 https://status.prod.unique.app/incident/515093#2460a8166702ff6e7e035fc828c55611311cfe2c1c3ef40681c090fe1475a830 Correcting https://status.prod.unique.app/incident/514786, cluster will experience downtime https://status.prod.unique.app/incident/515093 Tue, 18 Feb 2025 21:00:00 -0000 https://status.prod.unique.app/incident/515093#2460a8166702ff6e7e035fc828c55611311cfe2c1c3ef40681c090fe1475a830 Correcting https://status.prod.unique.app/incident/514786, cluster will experience downtime https://status.prod.unique.app/incident/515093 Tue, 18 Feb 2025 21:00:00 -0000 https://status.prod.unique.app/incident/515093#2460a8166702ff6e7e035fc828c55611311cfe2c1c3ef40681c090fe1475a830 Correcting https://status.prod.unique.app/incident/514786, cluster will experience downtime https://status.prod.unique.app/incident/515093 Tue, 18 Feb 2025 21:00:00 -0000 https://status.prod.unique.app/incident/515093#2460a8166702ff6e7e035fc828c55611311cfe2c1c3ef40681c090fe1475a830 Correcting https://status.prod.unique.app/incident/514786, cluster will experience downtime https://status.prod.unique.app/incident/515093 Tue, 18 Feb 2025 21:00:00 -0000 https://status.prod.unique.app/incident/515093#2460a8166702ff6e7e035fc828c55611311cfe2c1c3ef40681c090fe1475a830 Correcting https://status.prod.unique.app/incident/514786, cluster will experience downtime https://status.prod.unique.app/incident/515093 Tue, 18 Feb 2025 21:00:00 -0000 https://status.prod.unique.app/incident/515093#2460a8166702ff6e7e035fc828c55611311cfe2c1c3ef40681c090fe1475a830 Correcting https://status.prod.unique.app/incident/514786, cluster will experience downtime https://status.prod.unique.app/incident/515093 Tue, 18 Feb 2025 21:00:00 -0000 https://status.prod.unique.app/incident/515093#2460a8166702ff6e7e035fc828c55611311cfe2c1c3ef40681c090fe1475a830 Correcting https://status.prod.unique.app/incident/514786, cluster will experience downtime https://status.prod.unique.app/incident/515093 Tue, 18 Feb 2025 21:00:00 -0000 https://status.prod.unique.app/incident/515093#2460a8166702ff6e7e035fc828c55611311cfe2c1c3ef40681c090fe1475a830 Correcting https://status.prod.unique.app/incident/514786, cluster will experience downtime https://status.prod.unique.app/incident/515093 Tue, 18 Feb 2025 21:00:00 -0000 https://status.prod.unique.app/incident/515093#2460a8166702ff6e7e035fc828c55611311cfe2c1c3ef40681c090fe1475a830 Correcting https://status.prod.unique.app/incident/514786, cluster will experience downtime https://status.prod.unique.app/incident/515093 Tue, 18 Feb 2025 21:00:00 -0000 https://status.prod.unique.app/incident/515093#2460a8166702ff6e7e035fc828c55611311cfe2c1c3ef40681c090fe1475a830 Correcting https://status.prod.unique.app/incident/514786, cluster will experience downtime https://status.prod.unique.app/incident/515093 Tue, 18 Feb 2025 21:00:00 -0000 https://status.prod.unique.app/incident/515093#2460a8166702ff6e7e035fc828c55611311cfe2c1c3ef40681c090fe1475a830 Correcting https://status.prod.unique.app/incident/514786, cluster will experience downtime https://status.prod.unique.app/incident/514786 Mon, 17 Feb 2025 16:47:00 -0000 https://status.prod.unique.app/incident/514786#16ea211542e44dd3ae16e9605d5b5af1132827df5161842ec44b75e2ffadd73a # Postmortem: Involuntary Security Upgrade ## Incident Timeline 1. **14:43 CET**: Initiation of a security upgrade. 2. **14:58 CET**: First service began experiencing significant degradations, escalating to disruptions. 3. **14:58 - 16:34 CET**: Continued degradations and disruptions as the upgrade progressed. 4. **16:34 CET**: Completion of the upgrade, restoring the cluster to its operational state. 5. **Post-Upgrade Inspection**: Document ingestion was found to be non-functional. 6. **17:47 CET**: Document ingestion pipelines were repaired, fully resolving the incident. ## Root Cause Analysis 1. The upgrade was intended to update the system to a newer Kubernetes version to enhance maintainability and security. 2. The upgrade should have been scheduled outside of business hours to minimize impact during periods of high load. 3. An uncoordinated change led to the upgrade being triggered prematurely during peak operational hours. 4. This premature upgrade caused significant strain on Kubernetes, leading to the observed service disruptions. ## Impact Assessment - **Duration of Severe Degradations**: 1 hour and 33 minutes (partial system availability was maintained). - **Affected Services**: unique.app multitenant features (Chat and Recording). Other tenants remained unaffected. ## Preventative Measures 1. Implement additional safeguards in the infrastructure upgrade process to prevent unscheduled changes. 2. Allocate more resources during daytime operations to allow for cluster rebalancing, reducing the impact of involuntary disruptions. 3. Further segment unique workloads into smaller, independently upgradable pools to minimize the blast radius of similar incidents in the future. https://status.prod.unique.app/incident/514786 Mon, 17 Feb 2025 16:47:00 -0000 https://status.prod.unique.app/incident/514786#16ea211542e44dd3ae16e9605d5b5af1132827df5161842ec44b75e2ffadd73a # Postmortem: Involuntary Security Upgrade ## Incident Timeline 1. **14:43 CET**: Initiation of a security upgrade. 2. **14:58 CET**: First service began experiencing significant degradations, escalating to disruptions. 3. **14:58 - 16:34 CET**: Continued degradations and disruptions as the upgrade progressed. 4. **16:34 CET**: Completion of the upgrade, restoring the cluster to its operational state. 5. **Post-Upgrade Inspection**: Document ingestion was found to be non-functional. 6. **17:47 CET**: Document ingestion pipelines were repaired, fully resolving the incident. ## Root Cause Analysis 1. The upgrade was intended to update the system to a newer Kubernetes version to enhance maintainability and security. 2. The upgrade should have been scheduled outside of business hours to minimize impact during periods of high load. 3. An uncoordinated change led to the upgrade being triggered prematurely during peak operational hours. 4. This premature upgrade caused significant strain on Kubernetes, leading to the observed service disruptions. ## Impact Assessment - **Duration of Severe Degradations**: 1 hour and 33 minutes (partial system availability was maintained). - **Affected Services**: unique.app multitenant features (Chat and Recording). Other tenants remained unaffected. ## Preventative Measures 1. Implement additional safeguards in the infrastructure upgrade process to prevent unscheduled changes. 2. Allocate more resources during daytime operations to allow for cluster rebalancing, reducing the impact of involuntary disruptions. 3. Further segment unique workloads into smaller, independently upgradable pools to minimize the blast radius of similar incidents in the future. https://status.prod.unique.app/incident/514786 Mon, 17 Feb 2025 16:47:00 -0000 https://status.prod.unique.app/incident/514786#16ea211542e44dd3ae16e9605d5b5af1132827df5161842ec44b75e2ffadd73a # Postmortem: Involuntary Security Upgrade ## Incident Timeline 1. **14:43 CET**: Initiation of a security upgrade. 2. **14:58 CET**: First service began experiencing significant degradations, escalating to disruptions. 3. **14:58 - 16:34 CET**: Continued degradations and disruptions as the upgrade progressed. 4. **16:34 CET**: Completion of the upgrade, restoring the cluster to its operational state. 5. **Post-Upgrade Inspection**: Document ingestion was found to be non-functional. 6. **17:47 CET**: Document ingestion pipelines were repaired, fully resolving the incident. ## Root Cause Analysis 1. The upgrade was intended to update the system to a newer Kubernetes version to enhance maintainability and security. 2. The upgrade should have been scheduled outside of business hours to minimize impact during periods of high load. 3. An uncoordinated change led to the upgrade being triggered prematurely during peak operational hours. 4. This premature upgrade caused significant strain on Kubernetes, leading to the observed service disruptions. ## Impact Assessment - **Duration of Severe Degradations**: 1 hour and 33 minutes (partial system availability was maintained). - **Affected Services**: unique.app multitenant features (Chat and Recording). Other tenants remained unaffected. ## Preventative Measures 1. Implement additional safeguards in the infrastructure upgrade process to prevent unscheduled changes. 2. Allocate more resources during daytime operations to allow for cluster rebalancing, reducing the impact of involuntary disruptions. 3. Further segment unique workloads into smaller, independently upgradable pools to minimize the blast radius of similar incidents in the future. https://status.prod.unique.app/incident/514786 Mon, 17 Feb 2025 16:47:00 -0000 https://status.prod.unique.app/incident/514786#16ea211542e44dd3ae16e9605d5b5af1132827df5161842ec44b75e2ffadd73a # Postmortem: Involuntary Security Upgrade ## Incident Timeline 1. **14:43 CET**: Initiation of a security upgrade. 2. **14:58 CET**: First service began experiencing significant degradations, escalating to disruptions. 3. **14:58 - 16:34 CET**: Continued degradations and disruptions as the upgrade progressed. 4. **16:34 CET**: Completion of the upgrade, restoring the cluster to its operational state. 5. **Post-Upgrade Inspection**: Document ingestion was found to be non-functional. 6. **17:47 CET**: Document ingestion pipelines were repaired, fully resolving the incident. ## Root Cause Analysis 1. The upgrade was intended to update the system to a newer Kubernetes version to enhance maintainability and security. 2. The upgrade should have been scheduled outside of business hours to minimize impact during periods of high load. 3. An uncoordinated change led to the upgrade being triggered prematurely during peak operational hours. 4. This premature upgrade caused significant strain on Kubernetes, leading to the observed service disruptions. ## Impact Assessment - **Duration of Severe Degradations**: 1 hour and 33 minutes (partial system availability was maintained). - **Affected Services**: unique.app multitenant features (Chat and Recording). Other tenants remained unaffected. ## Preventative Measures 1. Implement additional safeguards in the infrastructure upgrade process to prevent unscheduled changes. 2. Allocate more resources during daytime operations to allow for cluster rebalancing, reducing the impact of involuntary disruptions. 3. Further segment unique workloads into smaller, independently upgradable pools to minimize the blast radius of similar incidents in the future. https://status.prod.unique.app/incident/514786 Mon, 17 Feb 2025 16:47:00 -0000 https://status.prod.unique.app/incident/514786#16ea211542e44dd3ae16e9605d5b5af1132827df5161842ec44b75e2ffadd73a # Postmortem: Involuntary Security Upgrade ## Incident Timeline 1. **14:43 CET**: Initiation of a security upgrade. 2. **14:58 CET**: First service began experiencing significant degradations, escalating to disruptions. 3. **14:58 - 16:34 CET**: Continued degradations and disruptions as the upgrade progressed. 4. **16:34 CET**: Completion of the upgrade, restoring the cluster to its operational state. 5. **Post-Upgrade Inspection**: Document ingestion was found to be non-functional. 6. **17:47 CET**: Document ingestion pipelines were repaired, fully resolving the incident. ## Root Cause Analysis 1. The upgrade was intended to update the system to a newer Kubernetes version to enhance maintainability and security. 2. The upgrade should have been scheduled outside of business hours to minimize impact during periods of high load. 3. An uncoordinated change led to the upgrade being triggered prematurely during peak operational hours. 4. This premature upgrade caused significant strain on Kubernetes, leading to the observed service disruptions. ## Impact Assessment - **Duration of Severe Degradations**: 1 hour and 33 minutes (partial system availability was maintained). - **Affected Services**: unique.app multitenant features (Chat and Recording). Other tenants remained unaffected. ## Preventative Measures 1. Implement additional safeguards in the infrastructure upgrade process to prevent unscheduled changes. 2. Allocate more resources during daytime operations to allow for cluster rebalancing, reducing the impact of involuntary disruptions. 3. Further segment unique workloads into smaller, independently upgradable pools to minimize the blast radius of similar incidents in the future. https://status.prod.unique.app/incident/514786 Mon, 17 Feb 2025 16:47:00 -0000 https://status.prod.unique.app/incident/514786#16ea211542e44dd3ae16e9605d5b5af1132827df5161842ec44b75e2ffadd73a # Postmortem: Involuntary Security Upgrade ## Incident Timeline 1. **14:43 CET**: Initiation of a security upgrade. 2. **14:58 CET**: First service began experiencing significant degradations, escalating to disruptions. 3. **14:58 - 16:34 CET**: Continued degradations and disruptions as the upgrade progressed. 4. **16:34 CET**: Completion of the upgrade, restoring the cluster to its operational state. 5. **Post-Upgrade Inspection**: Document ingestion was found to be non-functional. 6. **17:47 CET**: Document ingestion pipelines were repaired, fully resolving the incident. ## Root Cause Analysis 1. The upgrade was intended to update the system to a newer Kubernetes version to enhance maintainability and security. 2. The upgrade should have been scheduled outside of business hours to minimize impact during periods of high load. 3. An uncoordinated change led to the upgrade being triggered prematurely during peak operational hours. 4. This premature upgrade caused significant strain on Kubernetes, leading to the observed service disruptions. ## Impact Assessment - **Duration of Severe Degradations**: 1 hour and 33 minutes (partial system availability was maintained). - **Affected Services**: unique.app multitenant features (Chat and Recording). Other tenants remained unaffected. ## Preventative Measures 1. Implement additional safeguards in the infrastructure upgrade process to prevent unscheduled changes. 2. Allocate more resources during daytime operations to allow for cluster rebalancing, reducing the impact of involuntary disruptions. 3. Further segment unique workloads into smaller, independently upgradable pools to minimize the blast radius of similar incidents in the future. https://status.prod.unique.app/incident/514786 Mon, 17 Feb 2025 16:47:00 -0000 https://status.prod.unique.app/incident/514786#16ea211542e44dd3ae16e9605d5b5af1132827df5161842ec44b75e2ffadd73a # Postmortem: Involuntary Security Upgrade ## Incident Timeline 1. **14:43 CET**: Initiation of a security upgrade. 2. **14:58 CET**: First service began experiencing significant degradations, escalating to disruptions. 3. **14:58 - 16:34 CET**: Continued degradations and disruptions as the upgrade progressed. 4. **16:34 CET**: Completion of the upgrade, restoring the cluster to its operational state. 5. **Post-Upgrade Inspection**: Document ingestion was found to be non-functional. 6. **17:47 CET**: Document ingestion pipelines were repaired, fully resolving the incident. ## Root Cause Analysis 1. The upgrade was intended to update the system to a newer Kubernetes version to enhance maintainability and security. 2. The upgrade should have been scheduled outside of business hours to minimize impact during periods of high load. 3. An uncoordinated change led to the upgrade being triggered prematurely during peak operational hours. 4. This premature upgrade caused significant strain on Kubernetes, leading to the observed service disruptions. ## Impact Assessment - **Duration of Severe Degradations**: 1 hour and 33 minutes (partial system availability was maintained). - **Affected Services**: unique.app multitenant features (Chat and Recording). Other tenants remained unaffected. ## Preventative Measures 1. Implement additional safeguards in the infrastructure upgrade process to prevent unscheduled changes. 2. Allocate more resources during daytime operations to allow for cluster rebalancing, reducing the impact of involuntary disruptions. 3. Further segment unique workloads into smaller, independently upgradable pools to minimize the blast radius of similar incidents in the future. https://status.prod.unique.app/incident/514786 Mon, 17 Feb 2025 16:47:00 -0000 https://status.prod.unique.app/incident/514786#16ea211542e44dd3ae16e9605d5b5af1132827df5161842ec44b75e2ffadd73a # Postmortem: Involuntary Security Upgrade ## Incident Timeline 1. **14:43 CET**: Initiation of a security upgrade. 2. **14:58 CET**: First service began experiencing significant degradations, escalating to disruptions. 3. **14:58 - 16:34 CET**: Continued degradations and disruptions as the upgrade progressed. 4. **16:34 CET**: Completion of the upgrade, restoring the cluster to its operational state. 5. **Post-Upgrade Inspection**: Document ingestion was found to be non-functional. 6. **17:47 CET**: Document ingestion pipelines were repaired, fully resolving the incident. ## Root Cause Analysis 1. The upgrade was intended to update the system to a newer Kubernetes version to enhance maintainability and security. 2. The upgrade should have been scheduled outside of business hours to minimize impact during periods of high load. 3. An uncoordinated change led to the upgrade being triggered prematurely during peak operational hours. 4. This premature upgrade caused significant strain on Kubernetes, leading to the observed service disruptions. ## Impact Assessment - **Duration of Severe Degradations**: 1 hour and 33 minutes (partial system availability was maintained). - **Affected Services**: unique.app multitenant features (Chat and Recording). Other tenants remained unaffected. ## Preventative Measures 1. Implement additional safeguards in the infrastructure upgrade process to prevent unscheduled changes. 2. Allocate more resources during daytime operations to allow for cluster rebalancing, reducing the impact of involuntary disruptions. 3. Further segment unique workloads into smaller, independently upgradable pools to minimize the blast radius of similar incidents in the future. https://status.prod.unique.app/incident/514786 Mon, 17 Feb 2025 16:47:00 -0000 https://status.prod.unique.app/incident/514786#16ea211542e44dd3ae16e9605d5b5af1132827df5161842ec44b75e2ffadd73a # Postmortem: Involuntary Security Upgrade ## Incident Timeline 1. **14:43 CET**: Initiation of a security upgrade. 2. **14:58 CET**: First service began experiencing significant degradations, escalating to disruptions. 3. **14:58 - 16:34 CET**: Continued degradations and disruptions as the upgrade progressed. 4. **16:34 CET**: Completion of the upgrade, restoring the cluster to its operational state. 5. **Post-Upgrade Inspection**: Document ingestion was found to be non-functional. 6. **17:47 CET**: Document ingestion pipelines were repaired, fully resolving the incident. ## Root Cause Analysis 1. The upgrade was intended to update the system to a newer Kubernetes version to enhance maintainability and security. 2. The upgrade should have been scheduled outside of business hours to minimize impact during periods of high load. 3. An uncoordinated change led to the upgrade being triggered prematurely during peak operational hours. 4. This premature upgrade caused significant strain on Kubernetes, leading to the observed service disruptions. ## Impact Assessment - **Duration of Severe Degradations**: 1 hour and 33 minutes (partial system availability was maintained). - **Affected Services**: unique.app multitenant features (Chat and Recording). Other tenants remained unaffected. ## Preventative Measures 1. Implement additional safeguards in the infrastructure upgrade process to prevent unscheduled changes. 2. Allocate more resources during daytime operations to allow for cluster rebalancing, reducing the impact of involuntary disruptions. 3. Further segment unique workloads into smaller, independently upgradable pools to minimize the blast radius of similar incidents in the future. https://status.prod.unique.app/incident/514786 Mon, 17 Feb 2025 16:47:00 -0000 https://status.prod.unique.app/incident/514786#16ea211542e44dd3ae16e9605d5b5af1132827df5161842ec44b75e2ffadd73a # Postmortem: Involuntary Security Upgrade ## Incident Timeline 1. **14:43 CET**: Initiation of a security upgrade. 2. **14:58 CET**: First service began experiencing significant degradations, escalating to disruptions. 3. **14:58 - 16:34 CET**: Continued degradations and disruptions as the upgrade progressed. 4. **16:34 CET**: Completion of the upgrade, restoring the cluster to its operational state. 5. **Post-Upgrade Inspection**: Document ingestion was found to be non-functional. 6. **17:47 CET**: Document ingestion pipelines were repaired, fully resolving the incident. ## Root Cause Analysis 1. The upgrade was intended to update the system to a newer Kubernetes version to enhance maintainability and security. 2. The upgrade should have been scheduled outside of business hours to minimize impact during periods of high load. 3. An uncoordinated change led to the upgrade being triggered prematurely during peak operational hours. 4. This premature upgrade caused significant strain on Kubernetes, leading to the observed service disruptions. ## Impact Assessment - **Duration of Severe Degradations**: 1 hour and 33 minutes (partial system availability was maintained). - **Affected Services**: unique.app multitenant features (Chat and Recording). Other tenants remained unaffected. ## Preventative Measures 1. Implement additional safeguards in the infrastructure upgrade process to prevent unscheduled changes. 2. Allocate more resources during daytime operations to allow for cluster rebalancing, reducing the impact of involuntary disruptions. 3. Further segment unique workloads into smaller, independently upgradable pools to minimize the blast radius of similar incidents in the future. https://status.prod.unique.app/incident/514786 Mon, 17 Feb 2025 16:47:00 -0000 https://status.prod.unique.app/incident/514786#16ea211542e44dd3ae16e9605d5b5af1132827df5161842ec44b75e2ffadd73a # Postmortem: Involuntary Security Upgrade ## Incident Timeline 1. **14:43 CET**: Initiation of a security upgrade. 2. **14:58 CET**: First service began experiencing significant degradations, escalating to disruptions. 3. **14:58 - 16:34 CET**: Continued degradations and disruptions as the upgrade progressed. 4. **16:34 CET**: Completion of the upgrade, restoring the cluster to its operational state. 5. **Post-Upgrade Inspection**: Document ingestion was found to be non-functional. 6. **17:47 CET**: Document ingestion pipelines were repaired, fully resolving the incident. ## Root Cause Analysis 1. The upgrade was intended to update the system to a newer Kubernetes version to enhance maintainability and security. 2. The upgrade should have been scheduled outside of business hours to minimize impact during periods of high load. 3. An uncoordinated change led to the upgrade being triggered prematurely during peak operational hours. 4. This premature upgrade caused significant strain on Kubernetes, leading to the observed service disruptions. ## Impact Assessment - **Duration of Severe Degradations**: 1 hour and 33 minutes (partial system availability was maintained). - **Affected Services**: unique.app multitenant features (Chat and Recording). Other tenants remained unaffected. ## Preventative Measures 1. Implement additional safeguards in the infrastructure upgrade process to prevent unscheduled changes. 2. Allocate more resources during daytime operations to allow for cluster rebalancing, reducing the impact of involuntary disruptions. 3. Further segment unique workloads into smaller, independently upgradable pools to minimize the blast radius of similar incidents in the future. https://status.prod.unique.app/incident/514786 Mon, 17 Feb 2025 16:47:00 -0000 https://status.prod.unique.app/incident/514786#16ea211542e44dd3ae16e9605d5b5af1132827df5161842ec44b75e2ffadd73a # Postmortem: Involuntary Security Upgrade ## Incident Timeline 1. **14:43 CET**: Initiation of a security upgrade. 2. **14:58 CET**: First service began experiencing significant degradations, escalating to disruptions. 3. **14:58 - 16:34 CET**: Continued degradations and disruptions as the upgrade progressed. 4. **16:34 CET**: Completion of the upgrade, restoring the cluster to its operational state. 5. **Post-Upgrade Inspection**: Document ingestion was found to be non-functional. 6. **17:47 CET**: Document ingestion pipelines were repaired, fully resolving the incident. ## Root Cause Analysis 1. The upgrade was intended to update the system to a newer Kubernetes version to enhance maintainability and security. 2. The upgrade should have been scheduled outside of business hours to minimize impact during periods of high load. 3. An uncoordinated change led to the upgrade being triggered prematurely during peak operational hours. 4. This premature upgrade caused significant strain on Kubernetes, leading to the observed service disruptions. ## Impact Assessment - **Duration of Severe Degradations**: 1 hour and 33 minutes (partial system availability was maintained). - **Affected Services**: unique.app multitenant features (Chat and Recording). Other tenants remained unaffected. ## Preventative Measures 1. Implement additional safeguards in the infrastructure upgrade process to prevent unscheduled changes. 2. Allocate more resources during daytime operations to allow for cluster rebalancing, reducing the impact of involuntary disruptions. 3. Further segment unique workloads into smaller, independently upgradable pools to minimize the blast radius of similar incidents in the future. https://status.prod.unique.app/incident/514786 Mon, 17 Feb 2025 16:47:00 -0000 https://status.prod.unique.app/incident/514786#16ea211542e44dd3ae16e9605d5b5af1132827df5161842ec44b75e2ffadd73a # Postmortem: Involuntary Security Upgrade ## Incident Timeline 1. **14:43 CET**: Initiation of a security upgrade. 2. **14:58 CET**: First service began experiencing significant degradations, escalating to disruptions. 3. **14:58 - 16:34 CET**: Continued degradations and disruptions as the upgrade progressed. 4. **16:34 CET**: Completion of the upgrade, restoring the cluster to its operational state. 5. **Post-Upgrade Inspection**: Document ingestion was found to be non-functional. 6. **17:47 CET**: Document ingestion pipelines were repaired, fully resolving the incident. ## Root Cause Analysis 1. The upgrade was intended to update the system to a newer Kubernetes version to enhance maintainability and security. 2. The upgrade should have been scheduled outside of business hours to minimize impact during periods of high load. 3. An uncoordinated change led to the upgrade being triggered prematurely during peak operational hours. 4. This premature upgrade caused significant strain on Kubernetes, leading to the observed service disruptions. ## Impact Assessment - **Duration of Severe Degradations**: 1 hour and 33 minutes (partial system availability was maintained). - **Affected Services**: unique.app multitenant features (Chat and Recording). Other tenants remained unaffected. ## Preventative Measures 1. Implement additional safeguards in the infrastructure upgrade process to prevent unscheduled changes. 2. Allocate more resources during daytime operations to allow for cluster rebalancing, reducing the impact of involuntary disruptions. 3. Further segment unique workloads into smaller, independently upgradable pools to minimize the blast radius of similar incidents in the future. https://status.prod.unique.app/incident/514786 Mon, 17 Feb 2025 16:47:00 -0000 https://status.prod.unique.app/incident/514786#16ea211542e44dd3ae16e9605d5b5af1132827df5161842ec44b75e2ffadd73a # Postmortem: Involuntary Security Upgrade ## Incident Timeline 1. **14:43 CET**: Initiation of a security upgrade. 2. **14:58 CET**: First service began experiencing significant degradations, escalating to disruptions. 3. **14:58 - 16:34 CET**: Continued degradations and disruptions as the upgrade progressed. 4. **16:34 CET**: Completion of the upgrade, restoring the cluster to its operational state. 5. **Post-Upgrade Inspection**: Document ingestion was found to be non-functional. 6. **17:47 CET**: Document ingestion pipelines were repaired, fully resolving the incident. ## Root Cause Analysis 1. The upgrade was intended to update the system to a newer Kubernetes version to enhance maintainability and security. 2. The upgrade should have been scheduled outside of business hours to minimize impact during periods of high load. 3. An uncoordinated change led to the upgrade being triggered prematurely during peak operational hours. 4. This premature upgrade caused significant strain on Kubernetes, leading to the observed service disruptions. ## Impact Assessment - **Duration of Severe Degradations**: 1 hour and 33 minutes (partial system availability was maintained). - **Affected Services**: unique.app multitenant features (Chat and Recording). Other tenants remained unaffected. ## Preventative Measures 1. Implement additional safeguards in the infrastructure upgrade process to prevent unscheduled changes. 2. Allocate more resources during daytime operations to allow for cluster rebalancing, reducing the impact of involuntary disruptions. 3. Further segment unique workloads into smaller, independently upgradable pools to minimize the blast radius of similar incidents in the future. https://status.prod.unique.app/incident/514786 Mon, 17 Feb 2025 15:34:00 -0000 https://status.prod.unique.app/incident/514786#a75645934aa4b6c744560ef6d1e81b8e9f0cb16b987b6433edeabc01fb5592c8 An unplanned security upgrade to a newer Kubernetes version during peak hours caused significant service degradations and disruptions for 1 hour and 33 minutes, affecting Unique.app's multitenant features. The incident was resolved by 17:47 CET after repairing document ingestion pipelines. To prevent future occurrences, we will implement stricter safeguards, allocate more resources for daytime operations, and segment workloads for independent upgrades. https://status.prod.unique.app/incident/514786 Mon, 17 Feb 2025 15:34:00 -0000 https://status.prod.unique.app/incident/514786#a75645934aa4b6c744560ef6d1e81b8e9f0cb16b987b6433edeabc01fb5592c8 An unplanned security upgrade to a newer Kubernetes version during peak hours caused significant service degradations and disruptions for 1 hour and 33 minutes, affecting Unique.app's multitenant features. The incident was resolved by 17:47 CET after repairing document ingestion pipelines. To prevent future occurrences, we will implement stricter safeguards, allocate more resources for daytime operations, and segment workloads for independent upgrades. https://status.prod.unique.app/incident/514786 Mon, 17 Feb 2025 15:34:00 -0000 https://status.prod.unique.app/incident/514786#a75645934aa4b6c744560ef6d1e81b8e9f0cb16b987b6433edeabc01fb5592c8 An unplanned security upgrade to a newer Kubernetes version during peak hours caused significant service degradations and disruptions for 1 hour and 33 minutes, affecting Unique.app's multitenant features. The incident was resolved by 17:47 CET after repairing document ingestion pipelines. To prevent future occurrences, we will implement stricter safeguards, allocate more resources for daytime operations, and segment workloads for independent upgrades. https://status.prod.unique.app/incident/514786 Mon, 17 Feb 2025 15:34:00 -0000 https://status.prod.unique.app/incident/514786#a75645934aa4b6c744560ef6d1e81b8e9f0cb16b987b6433edeabc01fb5592c8 An unplanned security upgrade to a newer Kubernetes version during peak hours caused significant service degradations and disruptions for 1 hour and 33 minutes, affecting Unique.app's multitenant features. The incident was resolved by 17:47 CET after repairing document ingestion pipelines. To prevent future occurrences, we will implement stricter safeguards, allocate more resources for daytime operations, and segment workloads for independent upgrades. https://status.prod.unique.app/incident/514786 Mon, 17 Feb 2025 15:34:00 -0000 https://status.prod.unique.app/incident/514786#a75645934aa4b6c744560ef6d1e81b8e9f0cb16b987b6433edeabc01fb5592c8 An unplanned security upgrade to a newer Kubernetes version during peak hours caused significant service degradations and disruptions for 1 hour and 33 minutes, affecting Unique.app's multitenant features. The incident was resolved by 17:47 CET after repairing document ingestion pipelines. To prevent future occurrences, we will implement stricter safeguards, allocate more resources for daytime operations, and segment workloads for independent upgrades. https://status.prod.unique.app/incident/514786 Mon, 17 Feb 2025 15:34:00 -0000 https://status.prod.unique.app/incident/514786#a75645934aa4b6c744560ef6d1e81b8e9f0cb16b987b6433edeabc01fb5592c8 An unplanned security upgrade to a newer Kubernetes version during peak hours caused significant service degradations and disruptions for 1 hour and 33 minutes, affecting Unique.app's multitenant features. The incident was resolved by 17:47 CET after repairing document ingestion pipelines. To prevent future occurrences, we will implement stricter safeguards, allocate more resources for daytime operations, and segment workloads for independent upgrades. https://status.prod.unique.app/incident/514786 Mon, 17 Feb 2025 15:34:00 -0000 https://status.prod.unique.app/incident/514786#a75645934aa4b6c744560ef6d1e81b8e9f0cb16b987b6433edeabc01fb5592c8 An unplanned security upgrade to a newer Kubernetes version during peak hours caused significant service degradations and disruptions for 1 hour and 33 minutes, affecting Unique.app's multitenant features. The incident was resolved by 17:47 CET after repairing document ingestion pipelines. To prevent future occurrences, we will implement stricter safeguards, allocate more resources for daytime operations, and segment workloads for independent upgrades. https://status.prod.unique.app/incident/514786 Mon, 17 Feb 2025 15:34:00 -0000 https://status.prod.unique.app/incident/514786#a75645934aa4b6c744560ef6d1e81b8e9f0cb16b987b6433edeabc01fb5592c8 An unplanned security upgrade to a newer Kubernetes version during peak hours caused significant service degradations and disruptions for 1 hour and 33 minutes, affecting Unique.app's multitenant features. The incident was resolved by 17:47 CET after repairing document ingestion pipelines. To prevent future occurrences, we will implement stricter safeguards, allocate more resources for daytime operations, and segment workloads for independent upgrades. https://status.prod.unique.app/incident/514786 Mon, 17 Feb 2025 15:34:00 -0000 https://status.prod.unique.app/incident/514786#a75645934aa4b6c744560ef6d1e81b8e9f0cb16b987b6433edeabc01fb5592c8 An unplanned security upgrade to a newer Kubernetes version during peak hours caused significant service degradations and disruptions for 1 hour and 33 minutes, affecting Unique.app's multitenant features. The incident was resolved by 17:47 CET after repairing document ingestion pipelines. To prevent future occurrences, we will implement stricter safeguards, allocate more resources for daytime operations, and segment workloads for independent upgrades. https://status.prod.unique.app/incident/514786 Mon, 17 Feb 2025 15:34:00 -0000 https://status.prod.unique.app/incident/514786#a75645934aa4b6c744560ef6d1e81b8e9f0cb16b987b6433edeabc01fb5592c8 An unplanned security upgrade to a newer Kubernetes version during peak hours caused significant service degradations and disruptions for 1 hour and 33 minutes, affecting Unique.app's multitenant features. The incident was resolved by 17:47 CET after repairing document ingestion pipelines. To prevent future occurrences, we will implement stricter safeguards, allocate more resources for daytime operations, and segment workloads for independent upgrades. https://status.prod.unique.app/incident/514786 Mon, 17 Feb 2025 15:34:00 -0000 https://status.prod.unique.app/incident/514786#a75645934aa4b6c744560ef6d1e81b8e9f0cb16b987b6433edeabc01fb5592c8 An unplanned security upgrade to a newer Kubernetes version during peak hours caused significant service degradations and disruptions for 1 hour and 33 minutes, affecting Unique.app's multitenant features. The incident was resolved by 17:47 CET after repairing document ingestion pipelines. To prevent future occurrences, we will implement stricter safeguards, allocate more resources for daytime operations, and segment workloads for independent upgrades. https://status.prod.unique.app/incident/514786 Mon, 17 Feb 2025 15:34:00 -0000 https://status.prod.unique.app/incident/514786#a75645934aa4b6c744560ef6d1e81b8e9f0cb16b987b6433edeabc01fb5592c8 An unplanned security upgrade to a newer Kubernetes version during peak hours caused significant service degradations and disruptions for 1 hour and 33 minutes, affecting Unique.app's multitenant features. The incident was resolved by 17:47 CET after repairing document ingestion pipelines. To prevent future occurrences, we will implement stricter safeguards, allocate more resources for daytime operations, and segment workloads for independent upgrades. https://status.prod.unique.app/incident/514786 Mon, 17 Feb 2025 15:34:00 -0000 https://status.prod.unique.app/incident/514786#a75645934aa4b6c744560ef6d1e81b8e9f0cb16b987b6433edeabc01fb5592c8 An unplanned security upgrade to a newer Kubernetes version during peak hours caused significant service degradations and disruptions for 1 hour and 33 minutes, affecting Unique.app's multitenant features. The incident was resolved by 17:47 CET after repairing document ingestion pipelines. To prevent future occurrences, we will implement stricter safeguards, allocate more resources for daytime operations, and segment workloads for independent upgrades. https://status.prod.unique.app/incident/514786 Mon, 17 Feb 2025 15:34:00 -0000 https://status.prod.unique.app/incident/514786#a75645934aa4b6c744560ef6d1e81b8e9f0cb16b987b6433edeabc01fb5592c8 An unplanned security upgrade to a newer Kubernetes version during peak hours caused significant service degradations and disruptions for 1 hour and 33 minutes, affecting Unique.app's multitenant features. The incident was resolved by 17:47 CET after repairing document ingestion pipelines. To prevent future occurrences, we will implement stricter safeguards, allocate more resources for daytime operations, and segment workloads for independent upgrades. https://status.prod.unique.app/incident/514786 Mon, 17 Feb 2025 13:43:00 -0000 https://status.prod.unique.app/incident/514786#db2e2c7b22458a95e64d5a5b58346809bd3e75fed119de8e6c60243119dff9eb An unplanned security upgrade to a newer Kubernetes version during peak hours caused significant service degradations and disruptions for 1 hour and 33 minutes, affecting Unique.app's multitenant features. The incident was resolved by 17:47 CET after repairing document ingestion pipelines. To prevent future occurrences, we will implement stricter safeguards, allocate more resources for daytime operations, and segment workloads for independent upgrades. https://status.prod.unique.app/incident/514786 Mon, 17 Feb 2025 13:43:00 -0000 https://status.prod.unique.app/incident/514786#db2e2c7b22458a95e64d5a5b58346809bd3e75fed119de8e6c60243119dff9eb An unplanned security upgrade to a newer Kubernetes version during peak hours caused significant service degradations and disruptions for 1 hour and 33 minutes, affecting Unique.app's multitenant features. The incident was resolved by 17:47 CET after repairing document ingestion pipelines. To prevent future occurrences, we will implement stricter safeguards, allocate more resources for daytime operations, and segment workloads for independent upgrades. https://status.prod.unique.app/incident/514786 Mon, 17 Feb 2025 13:43:00 -0000 https://status.prod.unique.app/incident/514786#db2e2c7b22458a95e64d5a5b58346809bd3e75fed119de8e6c60243119dff9eb An unplanned security upgrade to a newer Kubernetes version during peak hours caused significant service degradations and disruptions for 1 hour and 33 minutes, affecting Unique.app's multitenant features. The incident was resolved by 17:47 CET after repairing document ingestion pipelines. To prevent future occurrences, we will implement stricter safeguards, allocate more resources for daytime operations, and segment workloads for independent upgrades. https://status.prod.unique.app/incident/514786 Mon, 17 Feb 2025 13:43:00 -0000 https://status.prod.unique.app/incident/514786#db2e2c7b22458a95e64d5a5b58346809bd3e75fed119de8e6c60243119dff9eb An unplanned security upgrade to a newer Kubernetes version during peak hours caused significant service degradations and disruptions for 1 hour and 33 minutes, affecting Unique.app's multitenant features. The incident was resolved by 17:47 CET after repairing document ingestion pipelines. To prevent future occurrences, we will implement stricter safeguards, allocate more resources for daytime operations, and segment workloads for independent upgrades. https://status.prod.unique.app/incident/514786 Mon, 17 Feb 2025 13:43:00 -0000 https://status.prod.unique.app/incident/514786#db2e2c7b22458a95e64d5a5b58346809bd3e75fed119de8e6c60243119dff9eb An unplanned security upgrade to a newer Kubernetes version during peak hours caused significant service degradations and disruptions for 1 hour and 33 minutes, affecting Unique.app's multitenant features. The incident was resolved by 17:47 CET after repairing document ingestion pipelines. To prevent future occurrences, we will implement stricter safeguards, allocate more resources for daytime operations, and segment workloads for independent upgrades. https://status.prod.unique.app/incident/514786 Mon, 17 Feb 2025 13:43:00 -0000 https://status.prod.unique.app/incident/514786#db2e2c7b22458a95e64d5a5b58346809bd3e75fed119de8e6c60243119dff9eb An unplanned security upgrade to a newer Kubernetes version during peak hours caused significant service degradations and disruptions for 1 hour and 33 minutes, affecting Unique.app's multitenant features. The incident was resolved by 17:47 CET after repairing document ingestion pipelines. To prevent future occurrences, we will implement stricter safeguards, allocate more resources for daytime operations, and segment workloads for independent upgrades. https://status.prod.unique.app/incident/514786 Mon, 17 Feb 2025 13:43:00 -0000 https://status.prod.unique.app/incident/514786#db2e2c7b22458a95e64d5a5b58346809bd3e75fed119de8e6c60243119dff9eb An unplanned security upgrade to a newer Kubernetes version during peak hours caused significant service degradations and disruptions for 1 hour and 33 minutes, affecting Unique.app's multitenant features. The incident was resolved by 17:47 CET after repairing document ingestion pipelines. To prevent future occurrences, we will implement stricter safeguards, allocate more resources for daytime operations, and segment workloads for independent upgrades. https://status.prod.unique.app/incident/514786 Mon, 17 Feb 2025 13:43:00 -0000 https://status.prod.unique.app/incident/514786#db2e2c7b22458a95e64d5a5b58346809bd3e75fed119de8e6c60243119dff9eb An unplanned security upgrade to a newer Kubernetes version during peak hours caused significant service degradations and disruptions for 1 hour and 33 minutes, affecting Unique.app's multitenant features. The incident was resolved by 17:47 CET after repairing document ingestion pipelines. To prevent future occurrences, we will implement stricter safeguards, allocate more resources for daytime operations, and segment workloads for independent upgrades. https://status.prod.unique.app/incident/514786 Mon, 17 Feb 2025 13:43:00 -0000 https://status.prod.unique.app/incident/514786#db2e2c7b22458a95e64d5a5b58346809bd3e75fed119de8e6c60243119dff9eb An unplanned security upgrade to a newer Kubernetes version during peak hours caused significant service degradations and disruptions for 1 hour and 33 minutes, affecting Unique.app's multitenant features. The incident was resolved by 17:47 CET after repairing document ingestion pipelines. To prevent future occurrences, we will implement stricter safeguards, allocate more resources for daytime operations, and segment workloads for independent upgrades. https://status.prod.unique.app/incident/514786 Mon, 17 Feb 2025 13:43:00 -0000 https://status.prod.unique.app/incident/514786#db2e2c7b22458a95e64d5a5b58346809bd3e75fed119de8e6c60243119dff9eb An unplanned security upgrade to a newer Kubernetes version during peak hours caused significant service degradations and disruptions for 1 hour and 33 minutes, affecting Unique.app's multitenant features. The incident was resolved by 17:47 CET after repairing document ingestion pipelines. To prevent future occurrences, we will implement stricter safeguards, allocate more resources for daytime operations, and segment workloads for independent upgrades. https://status.prod.unique.app/incident/514786 Mon, 17 Feb 2025 13:43:00 -0000 https://status.prod.unique.app/incident/514786#db2e2c7b22458a95e64d5a5b58346809bd3e75fed119de8e6c60243119dff9eb An unplanned security upgrade to a newer Kubernetes version during peak hours caused significant service degradations and disruptions for 1 hour and 33 minutes, affecting Unique.app's multitenant features. The incident was resolved by 17:47 CET after repairing document ingestion pipelines. To prevent future occurrences, we will implement stricter safeguards, allocate more resources for daytime operations, and segment workloads for independent upgrades. https://status.prod.unique.app/incident/514786 Mon, 17 Feb 2025 13:43:00 -0000 https://status.prod.unique.app/incident/514786#db2e2c7b22458a95e64d5a5b58346809bd3e75fed119de8e6c60243119dff9eb An unplanned security upgrade to a newer Kubernetes version during peak hours caused significant service degradations and disruptions for 1 hour and 33 minutes, affecting Unique.app's multitenant features. The incident was resolved by 17:47 CET after repairing document ingestion pipelines. To prevent future occurrences, we will implement stricter safeguards, allocate more resources for daytime operations, and segment workloads for independent upgrades. https://status.prod.unique.app/incident/514786 Mon, 17 Feb 2025 13:43:00 -0000 https://status.prod.unique.app/incident/514786#db2e2c7b22458a95e64d5a5b58346809bd3e75fed119de8e6c60243119dff9eb An unplanned security upgrade to a newer Kubernetes version during peak hours caused significant service degradations and disruptions for 1 hour and 33 minutes, affecting Unique.app's multitenant features. The incident was resolved by 17:47 CET after repairing document ingestion pipelines. To prevent future occurrences, we will implement stricter safeguards, allocate more resources for daytime operations, and segment workloads for independent upgrades. https://status.prod.unique.app/incident/514786 Mon, 17 Feb 2025 13:43:00 -0000 https://status.prod.unique.app/incident/514786#db2e2c7b22458a95e64d5a5b58346809bd3e75fed119de8e6c60243119dff9eb An unplanned security upgrade to a newer Kubernetes version during peak hours caused significant service degradations and disruptions for 1 hour and 33 minutes, affecting Unique.app's multitenant features. The incident was resolved by 17:47 CET after repairing document ingestion pipelines. To prevent future occurrences, we will implement stricter safeguards, allocate more resources for daytime operations, and segment workloads for independent upgrades.