Incidents reported on status page for ExtendlyOS https://status.extendly.com/ en https://status.extendly.com/ Mon, 16 Mar 2026 13:57:00 +0000 https://status.extendly.com/#1fed6e85f92d11c8fe92d5dcbaa2ff6bf10eed072ff1add1cc8ae6fabe8df632 News & Announcements Worker Service recovered https://status.extendly.com/ Mon, 16 Mar 2026 13:57:00 +0000 https://status.extendly.com/#4b837b0f2991a6d4ae5cc4cfb275ff2916d3da16a107b9f91ac90cbd4e0de35d News & Announcements Orchestrator Service recovered https://status.extendly.com/ Mon, 16 Mar 2026 13:09:51 +0000 https://status.extendly.com/#1fed6e85f92d11c8fe92d5dcbaa2ff6bf10eed072ff1add1cc8ae6fabe8df632 News & Announcements Worker Service went down https://status.extendly.com/ Mon, 16 Mar 2026 13:09:51 +0000 https://status.extendly.com/#4b837b0f2991a6d4ae5cc4cfb275ff2916d3da16a107b9f91ac90cbd4e0de35d News & Announcements Orchestrator Service went down https://status.extendly.com/ Mon, 16 Mar 2026 13:09:40 +0000 https://status.extendly.com/#661112c17b386f5948f9238ae3af5279dcd248626bef7c990e3e39925e8f5876 News & Announcements Worker Service recovered https://status.extendly.com/ Mon, 16 Mar 2026 13:09:40 +0000 https://status.extendly.com/#b3d152503a4c427f7460efaa565a95c5b7a7805efa2c2fe5264a8426459e393a News & Announcements Orchestrator Service recovered https://status.extendly.com/ Mon, 16 Mar 2026 13:05:57 +0000 https://status.extendly.com/#661112c17b386f5948f9238ae3af5279dcd248626bef7c990e3e39925e8f5876 News & Announcements Worker Service went down https://status.extendly.com/ Mon, 16 Mar 2026 13:05:57 +0000 https://status.extendly.com/#b3d152503a4c427f7460efaa565a95c5b7a7805efa2c2fe5264a8426459e393a News & Announcements Orchestrator Service went down https://status.extendly.com/ Mon, 16 Mar 2026 12:37:40 +0000 https://status.extendly.com/#7f523e51ae82c918ac2fa1d6ae05c0c0c1c4ae5f1d00391366742cde0314ffd6 KB Indexing Worker Service recovered https://status.extendly.com/ Mon, 16 Mar 2026 12:37:40 +0000 https://status.extendly.com/#8e9c492d1223e9dab0c9126be3e874b83153464c1afc9ece8516e0a0a6b14de1 KB Indexing Orchestrator Service recovered https://status.extendly.com/ Mon, 16 Mar 2026 12:00:41 +0000 https://status.extendly.com/#8e9c492d1223e9dab0c9126be3e874b83153464c1afc9ece8516e0a0a6b14de1 KB Indexing Orchestrator Service went down https://status.extendly.com/ Mon, 16 Mar 2026 12:00:40 +0000 https://status.extendly.com/#7f523e51ae82c918ac2fa1d6ae05c0c0c1c4ae5f1d00391366742cde0314ffd6 KB Indexing Worker Service went down https://status.extendly.com/ Fri, 13 Mar 2026 02:31:39 +0000 https://status.extendly.com/#9a53c9beaaf203c9a4882533e8b80ccee83747ed1b3190634dc7a23d3be25e0f News & Announcements Worker Service recovered https://status.extendly.com/ Fri, 13 Mar 2026 02:29:36 +0000 https://status.extendly.com/#9a53c9beaaf203c9a4882533e8b80ccee83747ed1b3190634dc7a23d3be25e0f News & Announcements Worker Service went down https://status.extendly.com/ Thu, 12 Mar 2026 06:43:52 +0000 https://status.extendly.com/#f20e6da8f99cd324e46e2a731bc0ecf780591914eb2aefb3f0b3a64b499f179b KB Indexing Orchestrator Service recovered https://status.extendly.com/ Thu, 12 Mar 2026 06:43:52 +0000 https://status.extendly.com/#7ff704373faa2bd9e3d54ac232d7d1ffa1cfc4ee76c1f95b268474b02092872c KB Indexing Worker Service recovered https://status.extendly.com/ Thu, 12 Mar 2026 06:03:21 +0000 https://status.extendly.com/#7ff704373faa2bd9e3d54ac232d7d1ffa1cfc4ee76c1f95b268474b02092872c KB Indexing Worker Service went down https://status.extendly.com/ Thu, 12 Mar 2026 06:03:21 +0000 https://status.extendly.com/#f20e6da8f99cd324e46e2a731bc0ecf780591914eb2aefb3f0b3a64b499f179b KB Indexing Orchestrator Service went down https://status.extendly.com/ Thu, 12 Mar 2026 03:00:41 +0000 https://status.extendly.com/#d5bc81d9c63bb2d35e2f8b4952d954425202481d23c493b9d922f4824aa873a2 ExtendlyOS Features Service recovered https://status.extendly.com/ Thu, 12 Mar 2026 02:53:46 +0000 https://status.extendly.com/#d5bc81d9c63bb2d35e2f8b4952d954425202481d23c493b9d922f4824aa873a2 ExtendlyOS Features Service went down https://status.extendly.com/ Thu, 12 Mar 2026 02:42:36 +0000 https://status.extendly.com/#58c0e9550cb49225c43e5568312a930cf7caaf79bd1aea16f21e5506aed49d5b ExtendlyOS Features Service recovered https://status.extendly.com/ Thu, 12 Mar 2026 02:37:52 +0000 https://status.extendly.com/#58c0e9550cb49225c43e5568312a930cf7caaf79bd1aea16f21e5506aed49d5b ExtendlyOS Features Service went down https://status.extendly.com/ Thu, 12 Mar 2026 02:30:21 +0000 https://status.extendly.com/#27cc6a352b2139dfacf5f29871b739711c411b8a479989a812484f4ee394ddd3 ExtendlyOS Data Graph recovered https://status.extendly.com/ Thu, 12 Mar 2026 02:28:44 +0000 https://status.extendly.com/#27cc6a352b2139dfacf5f29871b739711c411b8a479989a812484f4ee394ddd3 ExtendlyOS Data Graph went down https://status.extendly.com/ Wed, 11 Mar 2026 12:29:52 +0000 https://status.extendly.com/#8459b8363b114d343eadb483a59011ed211738dcaf26cccc967a79cc4f483c12 ExtendlyOS Data Graph recovered https://status.extendly.com/ Wed, 11 Mar 2026 12:28:15 +0000 https://status.extendly.com/#8459b8363b114d343eadb483a59011ed211738dcaf26cccc967a79cc4f483c12 ExtendlyOS Data Graph went down https://status.extendly.com/ Wed, 11 Mar 2026 03:15:55 +0000 https://status.extendly.com/#68ecad0eb73f08304ec59a5eab9fd5092bbfb9dd52731e9724a254b43b9ea348 ExtendlyOS Features Service recovered https://status.extendly.com/ Wed, 11 Mar 2026 02:28:39 +0000 https://status.extendly.com/#68ecad0eb73f08304ec59a5eab9fd5092bbfb9dd52731e9724a254b43b9ea348 ExtendlyOS Features Service went down https://status.extendly.com/ Wed, 11 Mar 2026 01:10:03 +0000 https://status.extendly.com/#319e1c045c0ddfc1b5ad933da6ee78c62c85150170fc8f8a811718218e5c3610 KB Indexing Worker Service recovered https://status.extendly.com/ Wed, 11 Mar 2026 01:10:03 +0000 https://status.extendly.com/#03ff777e823357c47a4096ca2cbea726e78d77269f69abf39e7750ff593e8c2c KB Indexing Orchestrator Service recovered https://status.extendly.com/ Tue, 10 Mar 2026 23:59:22 +0000 https://status.extendly.com/#319e1c045c0ddfc1b5ad933da6ee78c62c85150170fc8f8a811718218e5c3610 KB Indexing Worker Service went down https://status.extendly.com/ Tue, 10 Mar 2026 23:59:21 +0000 https://status.extendly.com/#03ff777e823357c47a4096ca2cbea726e78d77269f69abf39e7750ff593e8c2c KB Indexing Orchestrator Service went down https://status.extendly.com/ Tue, 10 Mar 2026 21:47:07 +0000 https://status.extendly.com/#117220e2839d100beb6abb3c99eec01f781fb5a0f0b60348cabde6cf3f6e11af ExtendlyOS Features Service recovered https://status.extendly.com/ Tue, 10 Mar 2026 21:46:53 +0000 https://status.extendly.com/#ee69e4989966204b8818f1826cf8506643b15dcd2f1ece932d960d518d494ce4 ExtendlyOS Data Graph recovered https://status.extendly.com/ Tue, 10 Mar 2026 21:44:50 +0000 https://status.extendly.com/#ee69e4989966204b8818f1826cf8506643b15dcd2f1ece932d960d518d494ce4 ExtendlyOS Data Graph went down https://status.extendly.com/ Tue, 10 Mar 2026 21:44:41 +0000 https://status.extendly.com/#117220e2839d100beb6abb3c99eec01f781fb5a0f0b60348cabde6cf3f6e11af ExtendlyOS Features Service went down https://status.extendly.com/ Tue, 10 Mar 2026 21:03:41 +0000 https://status.extendly.com/#15c02fdaae76b83dfba5a0cf3fb6bab8dd5b526bdeccaa0744aec95780e996f4 ExtendlyOS Features Service recovered https://status.extendly.com/ Tue, 10 Mar 2026 20:59:16 +0000 https://status.extendly.com/#fb5cecc0933ab108949e2ed3c708ad228f352ef7e0ab2aa4f9f39705d63e5c89 ExtendlyOS Support AI v2 recovered https://status.extendly.com/ Tue, 10 Mar 2026 20:50:28 +0000 https://status.extendly.com/#fb5cecc0933ab108949e2ed3c708ad228f352ef7e0ab2aa4f9f39705d63e5c89 ExtendlyOS Support AI v2 went down https://status.extendly.com/ Tue, 10 Mar 2026 20:49:03 +0000 https://status.extendly.com/#2b6008d98579265e123b50262323750c15991ab3b72ccba6fb5fca5cb0fa1145 ExtendlyOS Support AI v2 recovered https://status.extendly.com/ Tue, 10 Mar 2026 20:42:30 +0000 https://status.extendly.com/#2b6008d98579265e123b50262323750c15991ab3b72ccba6fb5fca5cb0fa1145 ExtendlyOS Support AI v2 went down https://status.extendly.com/ Tue, 10 Mar 2026 20:41:27 +0000 https://status.extendly.com/#15c02fdaae76b83dfba5a0cf3fb6bab8dd5b526bdeccaa0744aec95780e996f4 ExtendlyOS Features Service went down https://status.extendly.com/ Tue, 10 Mar 2026 20:40:16 +0000 https://status.extendly.com/#7669f5deab8dc5d2327168c5836d3e9e47afeba3777179b51c932b8738d14ad1 ExtendlyOS Features Service recovered https://status.extendly.com/ Tue, 10 Mar 2026 20:36:44 +0000 https://status.extendly.com/#e2ea29b711b6194282d6a8f0af610880e6bc97710e1a6df98cec674789d97099 ExtendlyOS Support AI v2 recovered https://status.extendly.com/ Tue, 10 Mar 2026 20:29:56 +0000 https://status.extendly.com/#e2ea29b711b6194282d6a8f0af610880e6bc97710e1a6df98cec674789d97099 ExtendlyOS Support AI v2 went down https://status.extendly.com/ Tue, 10 Mar 2026 20:29:53 +0000 https://status.extendly.com/#7669f5deab8dc5d2327168c5836d3e9e47afeba3777179b51c932b8738d14ad1 ExtendlyOS Features Service went down https://status.extendly.com/ Tue, 10 Mar 2026 19:03:14 +0000 https://status.extendly.com/#953fbf6ed82d76f9ddc595d2800c3de84d5466dbcebba0e734acf867273c9864 ExtendlyOS Support AI v2 recovered https://status.extendly.com/ Tue, 10 Mar 2026 19:03:10 +0000 https://status.extendly.com/#82a1c99c8ba70baa11f4b692e844dda2a13d20edb88af5101757eadd2bf30096 ExtendlyOS Features Service recovered https://status.extendly.com/ Tue, 10 Mar 2026 19:01:20 +0000 https://status.extendly.com/#953fbf6ed82d76f9ddc595d2800c3de84d5466dbcebba0e734acf867273c9864 ExtendlyOS Support AI v2 went down https://status.extendly.com/ Tue, 10 Mar 2026 18:58:02 +0000 https://status.extendly.com/#78df06e55749bd7e31dd9b257a7978da3baba77fe7c76f743ee4c43698c4c869 GHL Sync Orchestrator Service recovered https://status.extendly.com/ Tue, 10 Mar 2026 18:58:02 +0000 https://status.extendly.com/#06b25010e078c29e1dffb77434c15563cdbb4b16ef8f37d5ef9cef14b69bbcb8 News & Announcements Orchestrator Service recovered https://status.extendly.com/ Tue, 10 Mar 2026 18:58:01 +0000 https://status.extendly.com/#e21dc2e8d175e18602c63c5ab4898d6c34e96ddc65ab1008a6dd227212f5a3dc News & Announcements Worker Service recovered https://status.extendly.com/ Tue, 10 Mar 2026 18:56:27 +0000 https://status.extendly.com/#06b25010e078c29e1dffb77434c15563cdbb4b16ef8f37d5ef9cef14b69bbcb8 News & Announcements Orchestrator Service went down https://status.extendly.com/ Tue, 10 Mar 2026 18:56:27 +0000 https://status.extendly.com/#78df06e55749bd7e31dd9b257a7978da3baba77fe7c76f743ee4c43698c4c869 GHL Sync Orchestrator Service went down https://status.extendly.com/ Tue, 10 Mar 2026 18:56:27 +0000 https://status.extendly.com/#e21dc2e8d175e18602c63c5ab4898d6c34e96ddc65ab1008a6dd227212f5a3dc News & Announcements Worker Service went down https://status.extendly.com/ Tue, 10 Mar 2026 18:56:07 +0000 https://status.extendly.com/#225d625ccd601d81757834b0dfb19eb12c7de295c3d9a481d5519513318103f1 ExtendlyOS Support AI v2 recovered https://status.extendly.com/ Tue, 10 Mar 2026 18:45:26 +0000 https://status.extendly.com/#82a1c99c8ba70baa11f4b692e844dda2a13d20edb88af5101757eadd2bf30096 ExtendlyOS Features Service went down https://status.extendly.com/ Tue, 10 Mar 2026 18:43:23 +0000 https://status.extendly.com/#225d625ccd601d81757834b0dfb19eb12c7de295c3d9a481d5519513318103f1 ExtendlyOS Support AI v2 went down https://status.extendly.com/ Tue, 10 Mar 2026 18:29:10 +0000 https://status.extendly.com/#dd03cfb34d6736fb84eb6b9bea289be5c43b6aa561b792c8cbaf2ba7f07871f5 ExtendlyOS Features Service recovered https://status.extendly.com/ Tue, 10 Mar 2026 18:26:29 +0000 https://status.extendly.com/#2283870e295a21bb3e95f267233003c2736694b1bf652a605324ee38f0dd3938 ExtendlyOS Support AI v2 recovered https://status.extendly.com/ Tue, 10 Mar 2026 18:24:30 +0000 https://status.extendly.com/#dd03cfb34d6736fb84eb6b9bea289be5c43b6aa561b792c8cbaf2ba7f07871f5 ExtendlyOS Features Service went down https://status.extendly.com/ Tue, 10 Mar 2026 18:24:13 +0000 https://status.extendly.com/#2283870e295a21bb3e95f267233003c2736694b1bf652a605324ee38f0dd3938 ExtendlyOS Support AI v2 went down https://status.extendly.com/ Tue, 10 Mar 2026 17:55:36 +0000 https://status.extendly.com/#6c54d9eff690eba68520f645db43079b95f2a09bcccb4d49b5015604cd8ec8e9 ExtendlyOS Features Service recovered https://status.extendly.com/ Tue, 10 Mar 2026 17:39:41 +0000 https://status.extendly.com/#6c54d9eff690eba68520f645db43079b95f2a09bcccb4d49b5015604cd8ec8e9 ExtendlyOS Features Service went down https://status.extendly.com/ Tue, 10 Mar 2026 15:15:44 +0000 https://status.extendly.com/#eba2d841f1f7d3eba48d9f4f3915df9517f4a549fc134ea4b5f457f482287f8c ExtendlyOS Features Service recovered https://status.extendly.com/ Tue, 10 Mar 2026 15:09:44 +0000 https://status.extendly.com/#eba2d841f1f7d3eba48d9f4f3915df9517f4a549fc134ea4b5f457f482287f8c ExtendlyOS Features Service went down https://status.extendly.com/ Mon, 09 Mar 2026 11:13:58 +0000 https://status.extendly.com/#932a58ff0649a4c1150addf58cd85e9af6d32c069e9a9ab2b255bdd6e8014a55 SupportOS V1 Auth Service recovered https://status.extendly.com/ Mon, 09 Mar 2026 11:10:03 +0000 https://status.extendly.com/#932a58ff0649a4c1150addf58cd85e9af6d32c069e9a9ab2b255bdd6e8014a55 SupportOS V1 Auth Service went down https://status.extendly.com/ Mon, 02 Mar 2026 00:13:24 +0000 https://status.extendly.com/#3f1ff6a2675a65f0918df950641ef3a17ff1095d5543c1e8a7165b58d90df0ba KB Indexing Orchestrator Service recovered https://status.extendly.com/ Mon, 02 Mar 2026 00:13:24 +0000 https://status.extendly.com/#1e09e00432338f33d7f1a8183359f70cbfcf838b9163e4c88d52024d56878409 KB Indexing Worker Service recovered https://status.extendly.com/ Mon, 02 Mar 2026 00:11:37 +0000 https://status.extendly.com/#1e09e00432338f33d7f1a8183359f70cbfcf838b9163e4c88d52024d56878409 KB Indexing Worker Service went down https://status.extendly.com/ Mon, 02 Mar 2026 00:11:37 +0000 https://status.extendly.com/#3f1ff6a2675a65f0918df950641ef3a17ff1095d5543c1e8a7165b58d90df0ba KB Indexing Orchestrator Service went down https://status.extendly.com/ Sun, 01 Mar 2026 19:01:44 +0000 https://status.extendly.com/#637dc68f674b60924a84bc689bf26ab6be145ec639030450a179646356f4f4d0 ExtendlyOS Support AI v2 recovered https://status.extendly.com/ Sun, 01 Mar 2026 18:57:58 +0000 https://status.extendly.com/#637dc68f674b60924a84bc689bf26ab6be145ec639030450a179646356f4f4d0 ExtendlyOS Support AI v2 went down https://status.extendly.com/ Sun, 01 Mar 2026 10:19:34 +0000 https://status.extendly.com/#c2779e857e2f3db65ffe039e123a40cc91e93e7ab79ba18a69d5a2206c3f3cc9 ExtendlyOS Support AI v2 recovered https://status.extendly.com/ Sun, 01 Mar 2026 10:09:44 +0000 https://status.extendly.com/#c2779e857e2f3db65ffe039e123a40cc91e93e7ab79ba18a69d5a2206c3f3cc9 ExtendlyOS Support AI v2 went down https://status.extendly.com/ Tue, 24 Feb 2026 02:55:37 +0000 https://status.extendly.com/#871ddb0958cfe419cc64a06e249aab0050e286c33bbae3cdee62f463cfa341a5 ExtendlyOS Support AI v2 recovered https://status.extendly.com/ Tue, 24 Feb 2026 01:59:09 +0000 https://status.extendly.com/#871ddb0958cfe419cc64a06e249aab0050e286c33bbae3cdee62f463cfa341a5 ExtendlyOS Support AI v2 went down https://status.extendly.com/ Sat, 21 Feb 2026 05:50:57 +0000 https://status.extendly.com/#e39e0a88e0ee205a57c9abc84dec1a6550e446ba99547bd883a21a7cc5a1ef3f Theme Customizer V1 Backend recovered https://status.extendly.com/ Sat, 21 Feb 2026 05:36:42 +0000 https://status.extendly.com/#e39e0a88e0ee205a57c9abc84dec1a6550e446ba99547bd883a21a7cc5a1ef3f Theme Customizer V1 Backend went down https://status.extendly.com/ Fri, 20 Feb 2026 18:29:09 +0000 https://status.extendly.com/#d90ada677636e3edc457aa13f4327602504763ac697d638d692fc8cecfeb7149 Theme Customizer V1 Backend recovered https://status.extendly.com/ Fri, 20 Feb 2026 18:17:22 +0000 https://status.extendly.com/#d90ada677636e3edc457aa13f4327602504763ac697d638d692fc8cecfeb7149 Theme Customizer V1 Backend went down https://status.extendly.com/ Thu, 19 Feb 2026 22:10:45 +0000 https://status.extendly.com/#6bb2aef16264dc3771468b1d5173f3a41af1bcc4817a0ac3aad443b6826c6dd7 ExtendlyOS Data Graph recovered https://status.extendly.com/ Thu, 19 Feb 2026 22:08:42 +0000 https://status.extendly.com/#6bb2aef16264dc3771468b1d5173f3a41af1bcc4817a0ac3aad443b6826c6dd7 ExtendlyOS Data Graph went down https://status.extendly.com/ Thu, 19 Feb 2026 20:07:00 +0000 https://status.extendly.com/#2cd6f3eac34e25d01e2902cc72024d539a7c6bace71d1e618eb04ddc6bf34847 GHL Sync Orchestrator Service recovered https://status.extendly.com/ Thu, 19 Feb 2026 20:06:40 +0000 https://status.extendly.com/#c24903fbbe56ffbe85d966621db9d66006ddf18ecaf694f91d35e64931382cfd GHL Sync Worker Service recovered https://status.extendly.com/ Thu, 19 Feb 2026 18:53:44 +0000 https://status.extendly.com/#d841edc6a20af5eb0e1f8b8f78f17868985d0b8f33d28598ce02a128382271de Theme Customizer V1 Backend recovered https://status.extendly.com/ Thu, 19 Feb 2026 18:51:34 +0000 https://status.extendly.com/#d841edc6a20af5eb0e1f8b8f78f17868985d0b8f33d28598ce02a128382271de Theme Customizer V1 Backend went down https://status.extendly.com/ Thu, 19 Feb 2026 15:49:22 +0000 https://status.extendly.com/#c24903fbbe56ffbe85d966621db9d66006ddf18ecaf694f91d35e64931382cfd GHL Sync Worker Service went down https://status.extendly.com/ Thu, 19 Feb 2026 15:48:00 +0000 https://status.extendly.com/#2cd6f3eac34e25d01e2902cc72024d539a7c6bace71d1e618eb04ddc6bf34847 GHL Sync Orchestrator Service went down https://status.extendly.com/ Wed, 18 Feb 2026 08:24:20 +0000 https://status.extendly.com/#bd45013f4791e515c9d75ca2ea78f55d548d31d9be346a1431d3b141cf821352 Theme Customizer V1 Backend recovered https://status.extendly.com/ Wed, 18 Feb 2026 08:22:12 +0000 https://status.extendly.com/#bd45013f4791e515c9d75ca2ea78f55d548d31d9be346a1431d3b141cf821352 Theme Customizer V1 Backend went down https://status.extendly.com/ Mon, 26 Jan 2026 23:07:33 +0000 https://status.extendly.com/#b82ce906db9dd7fe639f88d622abaa337ba7a5fdabf78c5f64a1b7ad1d81cd9a ExtendlyOS Support AI v2 recovered https://status.extendly.com/ Mon, 26 Jan 2026 20:00:20 +0000 https://status.extendly.com/#aedb9a320d5ab5e56b9a96510a35af493aa6dbd5ef4b1ba5f0acae4c02bf6975 ExtendlyOS Features Service recovered https://status.extendly.com/ Mon, 26 Jan 2026 19:54:47 +0000 https://status.extendly.com/#4b4ab898a1cc657934e31155fe8edfb8cd5a227996ce210156f8334e34f2290f ExtendlyOS Data Graph recovered https://status.extendly.com/ Mon, 26 Jan 2026 18:03:43 +0000 https://status.extendly.com/#4b4ab898a1cc657934e31155fe8edfb8cd5a227996ce210156f8334e34f2290f ExtendlyOS Data Graph went down https://status.extendly.com/ Mon, 26 Jan 2026 18:02:53 +0000 https://status.extendly.com/#aedb9a320d5ab5e56b9a96510a35af493aa6dbd5ef4b1ba5f0acae4c02bf6975 ExtendlyOS Features Service went down https://status.extendly.com/ Mon, 26 Jan 2026 18:02:51 +0000 https://status.extendly.com/#b82ce906db9dd7fe639f88d622abaa337ba7a5fdabf78c5f64a1b7ad1d81cd9a ExtendlyOS Support AI v2 went down https://status.extendly.com/ Thu, 08 Jan 2026 15:18:06 +0000 https://status.extendly.com/#abada8d7975b39ed811dae2c34ea5bbb3e34742b5f8c5f6d32c64526b93e5053 ExtendlyOS Features Service recovered https://status.extendly.com/ Thu, 08 Jan 2026 15:16:12 +0000 https://status.extendly.com/#abada8d7975b39ed811dae2c34ea5bbb3e34742b5f8c5f6d32c64526b93e5053 ExtendlyOS Features Service went down https://status.extendly.com/ Mon, 05 Jan 2026 16:26:46 +0000 https://status.extendly.com/#1e4a6168ad68f3bcbd909dab42de2d6a6775fd193fcd9a0cb7caaf32bd5a1ee2 ExtendlyOS Data Graph recovered https://status.extendly.com/ Mon, 05 Jan 2026 16:24:44 +0000 https://status.extendly.com/#1e4a6168ad68f3bcbd909dab42de2d6a6775fd193fcd9a0cb7caaf32bd5a1ee2 ExtendlyOS Data Graph went down https://status.extendly.com/incident/797956 Sat, 03 Jan 2026 18:38:00 -0000 https://status.extendly.com/incident/797956#296350130d97080debb9bd8b1f81d8f7bdcfaf38f87b01ad327f00f45657e316 # Incident Post-Mortem: Service Outage (2026-01-03) ## Summary **Incident ID:** EXT-2026-01-03-01 **Date / Time (UTC):** 2026-01-03 05:45–07:25 **Duration:** ~100 minutes **Severity:** High **Services Affected:** ExtendlyOS Backend Services, Background Workers At approximately 12:45 AM EST, multiple ExtendlyOS backend services became unavailable. Monitoring confirmed service outages due to failures in the production infrastructure control plane and database layer. --- ## Impact - Production operations relying on ExtendlyOS backend services were affected. - API requests failed or timed out. - Background jobs did not execute. - Full production outage during the incident window. --- ## Timeline (UTC) | Time | Event | |------|------| | **00:45** | First signal detected: Background worker services missed heartbeat. | | **00:52** | Proxy services began returning errors. | | **01:08** | Multiple services unable to connect to server. | | **01:10** | Widespread background service failures. | | **01:59** | Full connectivity loss for API and support services. | | **02:36** | Intermittent connectivity during partial recovery. | | **03:30** | System stabilized; full service restored. | --- ## Root Cause A routine operating system update on infrastructure nodes introduced a version incompatibility with the container orchestration platform. This caused a loss of coordination between services. Consequently, the database cluster experienced replication issues requiring a rebuild of specific nodes. --- ## Resolution - Upgraded infrastructure proxy and orchestration agents to compatible versions. - Repaired the database cluster by rebuilding affected replicas. - Verified data integrity and service connectivity. --- ## Corrective & Preventative Measures - **Version Locking:** Implemented stricter version pinning for all infrastructure components to prevent implicit upgrades. - **Enhanced Monitoring:** Added specific alerts for database replication lag to detect similar issues earlier. - **Process Improvements:** Updated change management procedures to include stricter compatibility checks for infrastructure updates. https://status.extendly.com/incident/797956 Sat, 03 Jan 2026 18:38:00 -0000 https://status.extendly.com/incident/797956#296350130d97080debb9bd8b1f81d8f7bdcfaf38f87b01ad327f00f45657e316 # Incident Post-Mortem: Service Outage (2026-01-03) ## Summary **Incident ID:** EXT-2026-01-03-01 **Date / Time (UTC):** 2026-01-03 05:45–07:25 **Duration:** ~100 minutes **Severity:** High **Services Affected:** ExtendlyOS Backend Services, Background Workers At approximately 12:45 AM EST, multiple ExtendlyOS backend services became unavailable. Monitoring confirmed service outages due to failures in the production infrastructure control plane and database layer. --- ## Impact - Production operations relying on ExtendlyOS backend services were affected. - API requests failed or timed out. - Background jobs did not execute. - Full production outage during the incident window. --- ## Timeline (UTC) | Time | Event | |------|------| | **00:45** | First signal detected: Background worker services missed heartbeat. | | **00:52** | Proxy services began returning errors. | | **01:08** | Multiple services unable to connect to server. | | **01:10** | Widespread background service failures. | | **01:59** | Full connectivity loss for API and support services. | | **02:36** | Intermittent connectivity during partial recovery. | | **03:30** | System stabilized; full service restored. | --- ## Root Cause A routine operating system update on infrastructure nodes introduced a version incompatibility with the container orchestration platform. This caused a loss of coordination between services. Consequently, the database cluster experienced replication issues requiring a rebuild of specific nodes. --- ## Resolution - Upgraded infrastructure proxy and orchestration agents to compatible versions. - Repaired the database cluster by rebuilding affected replicas. - Verified data integrity and service connectivity. --- ## Corrective & Preventative Measures - **Version Locking:** Implemented stricter version pinning for all infrastructure components to prevent implicit upgrades. - **Enhanced Monitoring:** Added specific alerts for database replication lag to detect similar issues earlier. - **Process Improvements:** Updated change management procedures to include stricter compatibility checks for infrastructure updates. https://status.extendly.com/incident/797956 Sat, 03 Jan 2026 18:38:00 -0000 https://status.extendly.com/incident/797956#296350130d97080debb9bd8b1f81d8f7bdcfaf38f87b01ad327f00f45657e316 # Incident Post-Mortem: Service Outage (2026-01-03) ## Summary **Incident ID:** EXT-2026-01-03-01 **Date / Time (UTC):** 2026-01-03 05:45–07:25 **Duration:** ~100 minutes **Severity:** High **Services Affected:** ExtendlyOS Backend Services, Background Workers At approximately 12:45 AM EST, multiple ExtendlyOS backend services became unavailable. Monitoring confirmed service outages due to failures in the production infrastructure control plane and database layer. --- ## Impact - Production operations relying on ExtendlyOS backend services were affected. - API requests failed or timed out. - Background jobs did not execute. - Full production outage during the incident window. --- ## Timeline (UTC) | Time | Event | |------|------| | **00:45** | First signal detected: Background worker services missed heartbeat. | | **00:52** | Proxy services began returning errors. | | **01:08** | Multiple services unable to connect to server. | | **01:10** | Widespread background service failures. | | **01:59** | Full connectivity loss for API and support services. | | **02:36** | Intermittent connectivity during partial recovery. | | **03:30** | System stabilized; full service restored. | --- ## Root Cause A routine operating system update on infrastructure nodes introduced a version incompatibility with the container orchestration platform. This caused a loss of coordination between services. Consequently, the database cluster experienced replication issues requiring a rebuild of specific nodes. --- ## Resolution - Upgraded infrastructure proxy and orchestration agents to compatible versions. - Repaired the database cluster by rebuilding affected replicas. - Verified data integrity and service connectivity. --- ## Corrective & Preventative Measures - **Version Locking:** Implemented stricter version pinning for all infrastructure components to prevent implicit upgrades. - **Enhanced Monitoring:** Added specific alerts for database replication lag to detect similar issues earlier. - **Process Improvements:** Updated change management procedures to include stricter compatibility checks for infrastructure updates. https://status.extendly.com/incident/797956 Sat, 03 Jan 2026 18:38:00 -0000 https://status.extendly.com/incident/797956#296350130d97080debb9bd8b1f81d8f7bdcfaf38f87b01ad327f00f45657e316 # Incident Post-Mortem: Service Outage (2026-01-03) ## Summary **Incident ID:** EXT-2026-01-03-01 **Date / Time (UTC):** 2026-01-03 05:45–07:25 **Duration:** ~100 minutes **Severity:** High **Services Affected:** ExtendlyOS Backend Services, Background Workers At approximately 12:45 AM EST, multiple ExtendlyOS backend services became unavailable. Monitoring confirmed service outages due to failures in the production infrastructure control plane and database layer. --- ## Impact - Production operations relying on ExtendlyOS backend services were affected. - API requests failed or timed out. - Background jobs did not execute. - Full production outage during the incident window. --- ## Timeline (UTC) | Time | Event | |------|------| | **00:45** | First signal detected: Background worker services missed heartbeat. | | **00:52** | Proxy services began returning errors. | | **01:08** | Multiple services unable to connect to server. | | **01:10** | Widespread background service failures. | | **01:59** | Full connectivity loss for API and support services. | | **02:36** | Intermittent connectivity during partial recovery. | | **03:30** | System stabilized; full service restored. | --- ## Root Cause A routine operating system update on infrastructure nodes introduced a version incompatibility with the container orchestration platform. This caused a loss of coordination between services. Consequently, the database cluster experienced replication issues requiring a rebuild of specific nodes. --- ## Resolution - Upgraded infrastructure proxy and orchestration agents to compatible versions. - Repaired the database cluster by rebuilding affected replicas. - Verified data integrity and service connectivity. --- ## Corrective & Preventative Measures - **Version Locking:** Implemented stricter version pinning for all infrastructure components to prevent implicit upgrades. - **Enhanced Monitoring:** Added specific alerts for database replication lag to detect similar issues earlier. - **Process Improvements:** Updated change management procedures to include stricter compatibility checks for infrastructure updates. https://status.extendly.com/incident/797956 Sat, 03 Jan 2026 18:38:00 -0000 https://status.extendly.com/incident/797956#296350130d97080debb9bd8b1f81d8f7bdcfaf38f87b01ad327f00f45657e316 # Incident Post-Mortem: Service Outage (2026-01-03) ## Summary **Incident ID:** EXT-2026-01-03-01 **Date / Time (UTC):** 2026-01-03 05:45–07:25 **Duration:** ~100 minutes **Severity:** High **Services Affected:** ExtendlyOS Backend Services, Background Workers At approximately 12:45 AM EST, multiple ExtendlyOS backend services became unavailable. Monitoring confirmed service outages due to failures in the production infrastructure control plane and database layer. --- ## Impact - Production operations relying on ExtendlyOS backend services were affected. - API requests failed or timed out. - Background jobs did not execute. - Full production outage during the incident window. --- ## Timeline (UTC) | Time | Event | |------|------| | **00:45** | First signal detected: Background worker services missed heartbeat. | | **00:52** | Proxy services began returning errors. | | **01:08** | Multiple services unable to connect to server. | | **01:10** | Widespread background service failures. | | **01:59** | Full connectivity loss for API and support services. | | **02:36** | Intermittent connectivity during partial recovery. | | **03:30** | System stabilized; full service restored. | --- ## Root Cause A routine operating system update on infrastructure nodes introduced a version incompatibility with the container orchestration platform. This caused a loss of coordination between services. Consequently, the database cluster experienced replication issues requiring a rebuild of specific nodes. --- ## Resolution - Upgraded infrastructure proxy and orchestration agents to compatible versions. - Repaired the database cluster by rebuilding affected replicas. - Verified data integrity and service connectivity. --- ## Corrective & Preventative Measures - **Version Locking:** Implemented stricter version pinning for all infrastructure components to prevent implicit upgrades. - **Enhanced Monitoring:** Added specific alerts for database replication lag to detect similar issues earlier. - **Process Improvements:** Updated change management procedures to include stricter compatibility checks for infrastructure updates. https://status.extendly.com/incident/797956 Sat, 03 Jan 2026 18:38:00 -0000 https://status.extendly.com/incident/797956#296350130d97080debb9bd8b1f81d8f7bdcfaf38f87b01ad327f00f45657e316 # Incident Post-Mortem: Service Outage (2026-01-03) ## Summary **Incident ID:** EXT-2026-01-03-01 **Date / Time (UTC):** 2026-01-03 05:45–07:25 **Duration:** ~100 minutes **Severity:** High **Services Affected:** ExtendlyOS Backend Services, Background Workers At approximately 12:45 AM EST, multiple ExtendlyOS backend services became unavailable. Monitoring confirmed service outages due to failures in the production infrastructure control plane and database layer. --- ## Impact - Production operations relying on ExtendlyOS backend services were affected. - API requests failed or timed out. - Background jobs did not execute. - Full production outage during the incident window. --- ## Timeline (UTC) | Time | Event | |------|------| | **00:45** | First signal detected: Background worker services missed heartbeat. | | **00:52** | Proxy services began returning errors. | | **01:08** | Multiple services unable to connect to server. | | **01:10** | Widespread background service failures. | | **01:59** | Full connectivity loss for API and support services. | | **02:36** | Intermittent connectivity during partial recovery. | | **03:30** | System stabilized; full service restored. | --- ## Root Cause A routine operating system update on infrastructure nodes introduced a version incompatibility with the container orchestration platform. This caused a loss of coordination between services. Consequently, the database cluster experienced replication issues requiring a rebuild of specific nodes. --- ## Resolution - Upgraded infrastructure proxy and orchestration agents to compatible versions. - Repaired the database cluster by rebuilding affected replicas. - Verified data integrity and service connectivity. --- ## Corrective & Preventative Measures - **Version Locking:** Implemented stricter version pinning for all infrastructure components to prevent implicit upgrades. - **Enhanced Monitoring:** Added specific alerts for database replication lag to detect similar issues earlier. - **Process Improvements:** Updated change management procedures to include stricter compatibility checks for infrastructure updates. https://status.extendly.com/incident/797956 Sat, 03 Jan 2026 18:38:00 -0000 https://status.extendly.com/incident/797956#296350130d97080debb9bd8b1f81d8f7bdcfaf38f87b01ad327f00f45657e316 # Incident Post-Mortem: Service Outage (2026-01-03) ## Summary **Incident ID:** EXT-2026-01-03-01 **Date / Time (UTC):** 2026-01-03 05:45–07:25 **Duration:** ~100 minutes **Severity:** High **Services Affected:** ExtendlyOS Backend Services, Background Workers At approximately 12:45 AM EST, multiple ExtendlyOS backend services became unavailable. Monitoring confirmed service outages due to failures in the production infrastructure control plane and database layer. --- ## Impact - Production operations relying on ExtendlyOS backend services were affected. - API requests failed or timed out. - Background jobs did not execute. - Full production outage during the incident window. --- ## Timeline (UTC) | Time | Event | |------|------| | **00:45** | First signal detected: Background worker services missed heartbeat. | | **00:52** | Proxy services began returning errors. | | **01:08** | Multiple services unable to connect to server. | | **01:10** | Widespread background service failures. | | **01:59** | Full connectivity loss for API and support services. | | **02:36** | Intermittent connectivity during partial recovery. | | **03:30** | System stabilized; full service restored. | --- ## Root Cause A routine operating system update on infrastructure nodes introduced a version incompatibility with the container orchestration platform. This caused a loss of coordination between services. Consequently, the database cluster experienced replication issues requiring a rebuild of specific nodes. --- ## Resolution - Upgraded infrastructure proxy and orchestration agents to compatible versions. - Repaired the database cluster by rebuilding affected replicas. - Verified data integrity and service connectivity. --- ## Corrective & Preventative Measures - **Version Locking:** Implemented stricter version pinning for all infrastructure components to prevent implicit upgrades. - **Enhanced Monitoring:** Added specific alerts for database replication lag to detect similar issues earlier. - **Process Improvements:** Updated change management procedures to include stricter compatibility checks for infrastructure updates. https://status.extendly.com/incident/797956 Sat, 03 Jan 2026 18:38:00 -0000 https://status.extendly.com/incident/797956#296350130d97080debb9bd8b1f81d8f7bdcfaf38f87b01ad327f00f45657e316 # Incident Post-Mortem: Service Outage (2026-01-03) ## Summary **Incident ID:** EXT-2026-01-03-01 **Date / Time (UTC):** 2026-01-03 05:45–07:25 **Duration:** ~100 minutes **Severity:** High **Services Affected:** ExtendlyOS Backend Services, Background Workers At approximately 12:45 AM EST, multiple ExtendlyOS backend services became unavailable. Monitoring confirmed service outages due to failures in the production infrastructure control plane and database layer. --- ## Impact - Production operations relying on ExtendlyOS backend services were affected. - API requests failed or timed out. - Background jobs did not execute. - Full production outage during the incident window. --- ## Timeline (UTC) | Time | Event | |------|------| | **00:45** | First signal detected: Background worker services missed heartbeat. | | **00:52** | Proxy services began returning errors. | | **01:08** | Multiple services unable to connect to server. | | **01:10** | Widespread background service failures. | | **01:59** | Full connectivity loss for API and support services. | | **02:36** | Intermittent connectivity during partial recovery. | | **03:30** | System stabilized; full service restored. | --- ## Root Cause A routine operating system update on infrastructure nodes introduced a version incompatibility with the container orchestration platform. This caused a loss of coordination between services. Consequently, the database cluster experienced replication issues requiring a rebuild of specific nodes. --- ## Resolution - Upgraded infrastructure proxy and orchestration agents to compatible versions. - Repaired the database cluster by rebuilding affected replicas. - Verified data integrity and service connectivity. --- ## Corrective & Preventative Measures - **Version Locking:** Implemented stricter version pinning for all infrastructure components to prevent implicit upgrades. - **Enhanced Monitoring:** Added specific alerts for database replication lag to detect similar issues earlier. - **Process Improvements:** Updated change management procedures to include stricter compatibility checks for infrastructure updates. https://status.extendly.com/incident/797956 Sat, 03 Jan 2026 18:38:00 -0000 https://status.extendly.com/incident/797956#296350130d97080debb9bd8b1f81d8f7bdcfaf38f87b01ad327f00f45657e316 # Incident Post-Mortem: Service Outage (2026-01-03) ## Summary **Incident ID:** EXT-2026-01-03-01 **Date / Time (UTC):** 2026-01-03 05:45–07:25 **Duration:** ~100 minutes **Severity:** High **Services Affected:** ExtendlyOS Backend Services, Background Workers At approximately 12:45 AM EST, multiple ExtendlyOS backend services became unavailable. Monitoring confirmed service outages due to failures in the production infrastructure control plane and database layer. --- ## Impact - Production operations relying on ExtendlyOS backend services were affected. - API requests failed or timed out. - Background jobs did not execute. - Full production outage during the incident window. --- ## Timeline (UTC) | Time | Event | |------|------| | **00:45** | First signal detected: Background worker services missed heartbeat. | | **00:52** | Proxy services began returning errors. | | **01:08** | Multiple services unable to connect to server. | | **01:10** | Widespread background service failures. | | **01:59** | Full connectivity loss for API and support services. | | **02:36** | Intermittent connectivity during partial recovery. | | **03:30** | System stabilized; full service restored. | --- ## Root Cause A routine operating system update on infrastructure nodes introduced a version incompatibility with the container orchestration platform. This caused a loss of coordination between services. Consequently, the database cluster experienced replication issues requiring a rebuild of specific nodes. --- ## Resolution - Upgraded infrastructure proxy and orchestration agents to compatible versions. - Repaired the database cluster by rebuilding affected replicas. - Verified data integrity and service connectivity. --- ## Corrective & Preventative Measures - **Version Locking:** Implemented stricter version pinning for all infrastructure components to prevent implicit upgrades. - **Enhanced Monitoring:** Added specific alerts for database replication lag to detect similar issues earlier. - **Process Improvements:** Updated change management procedures to include stricter compatibility checks for infrastructure updates. https://status.extendly.com/ Sat, 03 Jan 2026 09:27:49 +0000 https://status.extendly.com/#ce02419d713bd1babb2eec0a20572a761bc37650cd76465d50f6441f132d6298 ExtendlyOS Data Graph recovered https://status.extendly.com/ Sat, 03 Jan 2026 09:27:40 +0000 https://status.extendly.com/#7f9c2a947528401d1b411200d7f5e95565107dbc07dbb5af3326e516d79192b5 News & Announcements Worker Service recovered https://status.extendly.com/ Sat, 03 Jan 2026 09:27:20 +0000 https://status.extendly.com/#a57847382f91e1b52a77e94e2e9bd341867557e737185b0ac6d58edff942f02a News & Announcements Orchestrator Service recovered https://status.extendly.com/ Sat, 03 Jan 2026 09:27:05 +0000 https://status.extendly.com/#a0a4a8404a73b0c5dea3ee653823567887d16e8463d30bbcd444465b27e11f6d ExtendlyOS Features Service recovered https://status.extendly.com/ Sat, 03 Jan 2026 09:27:00 +0000 https://status.extendly.com/#4b6dcac1c28b0352fc3fc65418e66a2a23536b9879eaa39ceb74f66bfaf99d1d KB Indexing Orchestrator Service recovered https://status.extendly.com/ Sat, 03 Jan 2026 09:27:00 +0000 https://status.extendly.com/#6c1b3e47979dff089a758351ef44c13d2403e5858bebe96508d065062a887673 KB Indexing Worker Service recovered https://status.extendly.com/ Sat, 03 Jan 2026 09:27:00 +0000 https://status.extendly.com/#7780f2034b11c3eaad08363d38d91cdc9e528d59a2041bdcf09ba3e26848f727 GHL Sync Worker Service recovered https://status.extendly.com/ Sat, 03 Jan 2026 09:27:00 +0000 https://status.extendly.com/#6f047dcfb20d66b97dc45cfb160d5bdfb05ddcf540333c6c03b55c24e02c54f4 GHL Sync Orchestrator Service recovered https://status.extendly.com/ Sat, 03 Jan 2026 07:44:49 +0000 https://status.extendly.com/#7fff41dc57a96667f8af192e8af2037f86d3eb9cb3c99336ec719b68f98d574c ExtendlyOS Support AI v2 recovered https://status.extendly.com/ Sat, 03 Jan 2026 07:43:04 +0000 https://status.extendly.com/#7fff41dc57a96667f8af192e8af2037f86d3eb9cb3c99336ec719b68f98d574c ExtendlyOS Support AI v2 went down https://status.extendly.com/ Sat, 03 Jan 2026 07:38:16 +0000 https://status.extendly.com/#7f9c2a947528401d1b411200d7f5e95565107dbc07dbb5af3326e516d79192b5 News & Announcements Worker Service went down https://status.extendly.com/ Sat, 03 Jan 2026 07:38:16 +0000 https://status.extendly.com/#6c1b3e47979dff089a758351ef44c13d2403e5858bebe96508d065062a887673 KB Indexing Worker Service went down https://status.extendly.com/ Sat, 03 Jan 2026 07:38:15 +0000 https://status.extendly.com/#a57847382f91e1b52a77e94e2e9bd341867557e737185b0ac6d58edff942f02a News & Announcements Orchestrator Service went down https://status.extendly.com/ Sat, 03 Jan 2026 07:38:15 +0000 https://status.extendly.com/#4b6dcac1c28b0352fc3fc65418e66a2a23536b9879eaa39ceb74f66bfaf99d1d KB Indexing Orchestrator Service went down https://status.extendly.com/ Sat, 03 Jan 2026 07:38:15 +0000 https://status.extendly.com/#6f047dcfb20d66b97dc45cfb160d5bdfb05ddcf540333c6c03b55c24e02c54f4 GHL Sync Orchestrator Service went down https://status.extendly.com/ Sat, 03 Jan 2026 07:04:38 +0000 https://status.extendly.com/#8a8d2b6920328a9e0baf0c6789ad6c11749935959bbad72b16226d44d2e94e54 ExtendlyOS Support AI v2 recovered https://status.extendly.com/ Sat, 03 Jan 2026 06:59:44 +0000 https://status.extendly.com/#ce02419d713bd1babb2eec0a20572a761bc37650cd76465d50f6441f132d6298 ExtendlyOS Data Graph went down https://status.extendly.com/ Sat, 03 Jan 2026 06:59:36 +0000 https://status.extendly.com/#a0a4a8404a73b0c5dea3ee653823567887d16e8463d30bbcd444465b27e11f6d ExtendlyOS Features Service went down https://status.extendly.com/ Sat, 03 Jan 2026 06:59:26 +0000 https://status.extendly.com/#6170e2fdc26af5de0c864d53c5ce47ff60132a47fa37081e2a1f11f8bf12835d ExtendlyOS Data Graph recovered https://status.extendly.com/ Sat, 03 Jan 2026 06:59:26 +0000 https://status.extendly.com/#8f2217635c7f0673234f268a51b13d33b39fa0aafc7b1401db80dcdbbff98af8 ExtendlyOS Features Service recovered https://status.extendly.com/ Sat, 03 Jan 2026 06:59:06 +0000 https://status.extendly.com/#8a8d2b6920328a9e0baf0c6789ad6c11749935959bbad72b16226d44d2e94e54 ExtendlyOS Support AI v2 went down https://status.extendly.com/ Sat, 03 Jan 2026 06:32:35 +0000 https://status.extendly.com/#76085fa2b9889a48013d698c9b2a3409d9bec5a8a355f9e051cd2189f7e0e5a9 ExtendlyOS Support AI v2 recovered https://status.extendly.com/ Sat, 03 Jan 2026 06:18:06 +0000 https://status.extendly.com/#7780f2034b11c3eaad08363d38d91cdc9e528d59a2041bdcf09ba3e26848f727 GHL Sync Worker Service went down https://status.extendly.com/ Sat, 03 Jan 2026 06:08:17 +0000 https://status.extendly.com/#6170e2fdc26af5de0c864d53c5ce47ff60132a47fa37081e2a1f11f8bf12835d ExtendlyOS Data Graph went down https://status.extendly.com/ Sat, 03 Jan 2026 06:08:05 +0000 https://status.extendly.com/#8f2217635c7f0673234f268a51b13d33b39fa0aafc7b1401db80dcdbbff98af8 ExtendlyOS Features Service went down https://status.extendly.com/ Sat, 03 Jan 2026 06:08:02 +0000 https://status.extendly.com/#76085fa2b9889a48013d698c9b2a3409d9bec5a8a355f9e051cd2189f7e0e5a9 ExtendlyOS Support AI v2 went down https://status.extendly.com/ Sat, 03 Jan 2026 06:03:15 +0000 https://status.extendly.com/#867c352e8e30250b61d1f9128ee3a25db70bb40ec0b6cdfece4a793e42c354a8 ExtendlyOS Features Service recovered https://status.extendly.com/ Sat, 03 Jan 2026 06:03:00 +0000 https://status.extendly.com/#0f171f50b13bd3a01561c5e0786a7da1fff5217e07931185976894e41cc14e96 GHL Sync Worker Service recovered https://status.extendly.com/ Sat, 03 Jan 2026 05:52:59 +0000 https://status.extendly.com/#867c352e8e30250b61d1f9128ee3a25db70bb40ec0b6cdfece4a793e42c354a8 ExtendlyOS Features Service went down https://status.extendly.com/ Sat, 03 Jan 2026 05:45:29 +0000 https://status.extendly.com/#0f171f50b13bd3a01561c5e0786a7da1fff5217e07931185976894e41cc14e96 GHL Sync Worker Service went down https://status.extendly.com/ Mon, 29 Dec 2025 15:17:19 +0000 https://status.extendly.com/#28696dd441eefde4f0da808c1e160fb86ee019dbb5c6b4a10ddcda7f30ccbfb6 ExtendlyOS Support AI v2 recovered https://status.extendly.com/ Mon, 29 Dec 2025 15:17:09 +0000 https://status.extendly.com/#54e9ad78993c29a684569baa8e9ae1e130a2d6ab5974af1be0bc087986ace1d8 ExtendlyOS Features Service recovered https://status.extendly.com/ Mon, 29 Dec 2025 15:16:59 +0000 https://status.extendly.com/#3940ac5e2b137aa1a902292825c45eb088377a7d823aef514187941e31e9a1cd ExtendlyOS Data Graph recovered https://status.extendly.com/ Mon, 29 Dec 2025 15:12:37 +0000 https://status.extendly.com/#28696dd441eefde4f0da808c1e160fb86ee019dbb5c6b4a10ddcda7f30ccbfb6 ExtendlyOS Support AI v2 went down https://status.extendly.com/ Mon, 29 Dec 2025 15:12:32 +0000 https://status.extendly.com/#54e9ad78993c29a684569baa8e9ae1e130a2d6ab5974af1be0bc087986ace1d8 ExtendlyOS Features Service went down https://status.extendly.com/ Mon, 29 Dec 2025 15:12:16 +0000 https://status.extendly.com/#3940ac5e2b137aa1a902292825c45eb088377a7d823aef514187941e31e9a1cd ExtendlyOS Data Graph went down https://status.extendly.com/ Mon, 29 Dec 2025 15:03:14 +0000 https://status.extendly.com/#7c1f4d6a5816b36f6457ae065f4c97bfd3854d8055ee54910f20e9422cb1dd3a ExtendlyOS Support AI v2 recovered https://status.extendly.com/ Mon, 29 Dec 2025 15:03:14 +0000 https://status.extendly.com/#1532a6dce82275ac707bc306df607991dd911e633371ffd1b917d1176dba2325 ExtendlyOS Features Service recovered https://status.extendly.com/ Mon, 29 Dec 2025 15:03:09 +0000 https://status.extendly.com/#002d476d3fb729cb62bb640d58cb6026e71bd448af911b048d88b27640238a59 ExtendlyOS Data Graph recovered https://status.extendly.com/ Mon, 29 Dec 2025 14:59:13 +0000 https://status.extendly.com/#1532a6dce82275ac707bc306df607991dd911e633371ffd1b917d1176dba2325 ExtendlyOS Features Service went down https://status.extendly.com/ Mon, 29 Dec 2025 14:59:11 +0000 https://status.extendly.com/#002d476d3fb729cb62bb640d58cb6026e71bd448af911b048d88b27640238a59 ExtendlyOS Data Graph went down https://status.extendly.com/ Mon, 29 Dec 2025 14:58:40 +0000 https://status.extendly.com/#7c1f4d6a5816b36f6457ae065f4c97bfd3854d8055ee54910f20e9422cb1dd3a ExtendlyOS Support AI v2 went down https://status.extendly.com/ Mon, 29 Dec 2025 14:56:07 +0000 https://status.extendly.com/#72947ecae2b58d38fb7fe27b95dfca76bdcaaeb83af6bd28964b055f6133e5ad ExtendlyOS Support AI v2 recovered https://status.extendly.com/ Mon, 29 Dec 2025 14:55:45 +0000 https://status.extendly.com/#73af43df599d106ef935a7b3e5f768608ab0c94c8ccb818814e6e0a1ccfde952 ExtendlyOS Data Graph recovered https://status.extendly.com/ Mon, 29 Dec 2025 14:54:12 +0000 https://status.extendly.com/#72947ecae2b58d38fb7fe27b95dfca76bdcaaeb83af6bd28964b055f6133e5ad ExtendlyOS Support AI v2 went down https://status.extendly.com/ Mon, 29 Dec 2025 14:54:11 +0000 https://status.extendly.com/#73af43df599d106ef935a7b3e5f768608ab0c94c8ccb818814e6e0a1ccfde952 ExtendlyOS Data Graph went down https://status.extendly.com/ Mon, 29 Dec 2025 14:48:53 +0000 https://status.extendly.com/#f23a6e9eb392b1b5bb12f50f8e5346f74ae99f8e1ba260e8a4a1f067d49b49f4 SupportOS V1 Auth Service recovered https://status.extendly.com/ Mon, 29 Dec 2025 14:46:06 +0000 https://status.extendly.com/#79e652d6388fc0d15359aef774b780c3efb07c6d8fb21e85b9aade72213e0102 SupportOS V1 Backend Service recovered https://status.extendly.com/ Mon, 29 Dec 2025 14:44:51 +0000 https://status.extendly.com/#f23a6e9eb392b1b5bb12f50f8e5346f74ae99f8e1ba260e8a4a1f067d49b49f4 SupportOS V1 Auth Service went down https://status.extendly.com/ Mon, 29 Dec 2025 14:44:35 +0000 https://status.extendly.com/#79e652d6388fc0d15359aef774b780c3efb07c6d8fb21e85b9aade72213e0102 SupportOS V1 Backend Service went down https://status.extendly.com/ Sun, 21 Dec 2025 20:39:04 +0000 https://status.extendly.com/#ced6de9c137326c6a699ace680bdb6e115dd9e2d165ac3b22d00bc63c82a942c ExtendlyOS Features Service recovered https://status.extendly.com/ Sun, 21 Dec 2025 19:56:58 +0000 https://status.extendly.com/#ced6de9c137326c6a699ace680bdb6e115dd9e2d165ac3b22d00bc63c82a942c ExtendlyOS Features Service went down https://status.extendly.com/ Sat, 20 Dec 2025 01:52:32 +0000 https://status.extendly.com/#ae8c0d1634fb40cc9e87c50657ff7b50a126ff9595b0288bcd2b1b02ab1d4e00 ExtendlyOS Features Service recovered https://status.extendly.com/ Sat, 20 Dec 2025 01:52:20 +0000 https://status.extendly.com/#ce593195d8983d01c46f9a1033613c5bf91ec50008c123c58037b0d4ea90798c GHL Sync Worker Service recovered https://status.extendly.com/ Sat, 20 Dec 2025 01:36:40 +0000 https://status.extendly.com/#ae8c0d1634fb40cc9e87c50657ff7b50a126ff9595b0288bcd2b1b02ab1d4e00 ExtendlyOS Features Service went down https://status.extendly.com/ Sat, 20 Dec 2025 01:36:12 +0000 https://status.extendly.com/#ce593195d8983d01c46f9a1033613c5bf91ec50008c123c58037b0d4ea90798c GHL Sync Worker Service went down