Incidents reported on status page for ExtendlyOS https://status.extendly.com/ en 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 https://status.extendly.com/ Fri, 12 Dec 2025 06:15:48 +0000 https://status.extendly.com/#555d603bb0996ca7268509314f2679fdbc75e624ecd17dcd407ef10c440f72fb SupportOS V1 Auth Service recovered https://status.extendly.com/ Fri, 12 Dec 2025 06:10:49 +0000 https://status.extendly.com/#555d603bb0996ca7268509314f2679fdbc75e624ecd17dcd407ef10c440f72fb SupportOS V1 Auth Service went down https://status.extendly.com/ Fri, 12 Dec 2025 05:40:50 +0000 https://status.extendly.com/#897e7aa31a1c4febee53b36e29c5265d41aacb278cf29f916ff450b4c98de10a SupportOS V1 Auth Service recovered https://status.extendly.com/ Fri, 12 Dec 2025 05:30:44 +0000 https://status.extendly.com/#897e7aa31a1c4febee53b36e29c5265d41aacb278cf29f916ff450b4c98de10a SupportOS V1 Auth Service went down https://status.extendly.com/ Wed, 10 Dec 2025 05:01:38 +0000 https://status.extendly.com/#3fca9636c466458dce5e49c8ec98b08a78467aaf73953c4d5cf55d72cac76b64 ExtendlyOS Data Graph recovered https://status.extendly.com/ Wed, 10 Dec 2025 04:57:37 +0000 https://status.extendly.com/#3fca9636c466458dce5e49c8ec98b08a78467aaf73953c4d5cf55d72cac76b64 ExtendlyOS Data Graph went down https://status.extendly.com/ Tue, 09 Dec 2025 19:46:28 +0000 https://status.extendly.com/#2a97d8fe1fb63264e4ceed56a6c688248dc34bf7157c1c02fe42a91c95208e99 ExtendlyOS Features Service recovered https://status.extendly.com/ Tue, 09 Dec 2025 19:45:58 +0000 https://status.extendly.com/#fc8cd3807670892089a3b8eb85b4bc45c06e96a5f7c4053b1b4782bed7e6d686 ExtendlyOS Support AI v2 recovered https://status.extendly.com/ Tue, 09 Dec 2025 19:45:09 +0000 https://status.extendly.com/#78c78ec63193f334d174205f0e5f240fba3d55195f4b9d738d5c4266935516fa ExtendlyOS Data Graph recovered https://status.extendly.com/ Tue, 09 Dec 2025 19:04:04 +0000 https://status.extendly.com/#78c78ec63193f334d174205f0e5f240fba3d55195f4b9d738d5c4266935516fa ExtendlyOS Data Graph went down https://status.extendly.com/ Tue, 09 Dec 2025 19:01:18 +0000 https://status.extendly.com/#2a97d8fe1fb63264e4ceed56a6c688248dc34bf7157c1c02fe42a91c95208e99 ExtendlyOS Features Service went down https://status.extendly.com/ Tue, 09 Dec 2025 19:01:06 +0000 https://status.extendly.com/#fc8cd3807670892089a3b8eb85b4bc45c06e96a5f7c4053b1b4782bed7e6d686 ExtendlyOS Support AI v2 went down https://status.extendly.com/ Tue, 18 Nov 2025 15:57:34 +0000 https://status.extendly.com/#f4dc7d837c3c988d2064ba0f5300fb41453b395ae07e51cea75108ad5b41cc92 ExtendlyOS Data Graph recovered https://status.extendly.com/ Tue, 18 Nov 2025 14:37:01 +0000 https://status.extendly.com/#f4dc7d837c3c988d2064ba0f5300fb41453b395ae07e51cea75108ad5b41cc92 ExtendlyOS Data Graph went down https://status.extendly.com/ Tue, 18 Nov 2025 11:54:55 +0000 https://status.extendly.com/#d85df9d14246472d89bd37f13819036a48982b38e1b60ba4e89d84c44742f739 News & Announcements Worker Service recovered https://status.extendly.com/ Tue, 18 Nov 2025 11:46:07 +0000 https://status.extendly.com/#60650d9d580cfb9d48f119afc2be990199587dba3b7111faaf4e64370c257bcc KB Indexing Orchestrator Service recovered https://status.extendly.com/ Tue, 18 Nov 2025 11:43:54 +0000 https://status.extendly.com/#d85df9d14246472d89bd37f13819036a48982b38e1b60ba4e89d84c44742f739 News & Announcements Worker Service went down https://status.extendly.com/ Tue, 18 Nov 2025 11:41:52 +0000 https://status.extendly.com/#363e888b4433f1ff8b83301b33fe070707f1e2b289f4c6313114336eff9a9e75 News & Announcements Worker Service recovered https://status.extendly.com/ Tue, 18 Nov 2025 11:38:59 +0000 https://status.extendly.com/#87fc82ef1d081d8fc4d0cb453337c7a754a2f64de418e2a3fca1a2467694f2f1 KB Indexing Worker Service recovered https://status.extendly.com/ Tue, 18 Nov 2025 11:37:20 +0000 https://status.extendly.com/#65e831b2e0b847bcbf118b912b9882d7bce208c0e191fe7b4e325d08bac497c1 GHL Sync Orchestrator Service recovered https://status.extendly.com/ Tue, 18 Nov 2025 11:37:18 +0000 https://status.extendly.com/#d71fba6e8c498d453a8993194d64c3a5f1df15822c0b16d7ddba5b0e15a4a07e News & Announcements Orchestrator Service recovered https://status.extendly.com/ Tue, 18 Nov 2025 11:36:36 +0000 https://status.extendly.com/#87fc82ef1d081d8fc4d0cb453337c7a754a2f64de418e2a3fca1a2467694f2f1 KB Indexing Worker Service went down https://status.extendly.com/ Tue, 18 Nov 2025 11:36:15 +0000 https://status.extendly.com/#363e888b4433f1ff8b83301b33fe070707f1e2b289f4c6313114336eff9a9e75 News & Announcements Worker Service went down https://status.extendly.com/ Tue, 18 Nov 2025 11:35:36 +0000 https://status.extendly.com/#60650d9d580cfb9d48f119afc2be990199587dba3b7111faaf4e64370c257bcc KB Indexing Orchestrator Service went down https://status.extendly.com/ Tue, 18 Nov 2025 11:35:36 +0000 https://status.extendly.com/#65e831b2e0b847bcbf118b912b9882d7bce208c0e191fe7b4e325d08bac497c1 GHL Sync Orchestrator Service went down https://status.extendly.com/ Tue, 18 Nov 2025 11:35:35 +0000 https://status.extendly.com/#d71fba6e8c498d453a8993194d64c3a5f1df15822c0b16d7ddba5b0e15a4a07e News & Announcements Orchestrator Service went down https://status.extendly.com/ Mon, 17 Nov 2025 23:59:00 +0000 https://status.extendly.com/#b28600fe53f881de50f097759deb0ed5676c279838b2990544de860b5f4f1e32 KB Indexing Orchestrator Service recovered https://status.extendly.com/ Fri, 14 Nov 2025 23:17:56 +0000 https://status.extendly.com/#b28600fe53f881de50f097759deb0ed5676c279838b2990544de860b5f4f1e32 KB Indexing Orchestrator Service went down https://status.extendly.com/ Thu, 06 Nov 2025 15:33:44 +0000 https://status.extendly.com/#fdffb4e4c0a64dac85b81535e524f2db6f84027bf6b52a8ad9454d87d657720d ExtendlyOS Data Graph recovered https://status.extendly.com/ Thu, 06 Nov 2025 15:31:36 +0000 https://status.extendly.com/#2fcef0918db545223b0ccff130d143ac52832e385a1133b19b773cf314cab795 ExtendlyOS Features Service recovered https://status.extendly.com/ Thu, 06 Nov 2025 15:31:34 +0000 https://status.extendly.com/#9f8cc84fca0e321e16f65e2ca619982c6bb3a9484b1dd10cf624015fcbe2c19b ExtendlyOS Support AI v2 recovered https://status.extendly.com/ Thu, 06 Nov 2025 15:11:10 +0000 https://status.extendly.com/#fdffb4e4c0a64dac85b81535e524f2db6f84027bf6b52a8ad9454d87d657720d ExtendlyOS Data Graph went down https://status.extendly.com/ Thu, 06 Nov 2025 15:02:25 +0000 https://status.extendly.com/#2fcef0918db545223b0ccff130d143ac52832e385a1133b19b773cf314cab795 ExtendlyOS Features Service went down https://status.extendly.com/ Thu, 06 Nov 2025 15:02:24 +0000 https://status.extendly.com/#9f8cc84fca0e321e16f65e2ca619982c6bb3a9484b1dd10cf624015fcbe2c19b ExtendlyOS Support AI v2 went down https://status.extendly.com/ Tue, 04 Nov 2025 02:33:22 +0000 https://status.extendly.com/#9b89e60c4df07ff2a6e4e4c23213082fc94aa14ec9ba3dc3e121039db131ef3a ExtendlyOS Features Service recovered https://status.extendly.com/ Tue, 04 Nov 2025 02:30:32 +0000 https://status.extendly.com/#9b89e60c4df07ff2a6e4e4c23213082fc94aa14ec9ba3dc3e121039db131ef3a ExtendlyOS Features Service went down https://status.extendly.com/ Sun, 02 Nov 2025 16:39:53 +0000 https://status.extendly.com/#714e66e8692b679eb7905b1554afa9d689c9545b504f785dff996b4963b6c92e ExtendlyOS Features Service recovered https://status.extendly.com/ Sun, 02 Nov 2025 16:37:54 +0000 https://status.extendly.com/#714e66e8692b679eb7905b1554afa9d689c9545b504f785dff996b4963b6c92e ExtendlyOS Features Service went down https://status.extendly.com/ Wed, 29 Oct 2025 18:31:28 +0000 https://status.extendly.com/#6be2e5293a68e58cdf442add63ff0ba7aa989102d0857fde7f7d1dc18ac3dc10 ExtendlyOS Data Graph recovered https://status.extendly.com/ Wed, 29 Oct 2025 18:30:48 +0000 https://status.extendly.com/#5562b24c7f9ad5235c48a1274b561e1f2df2182d11f4bd49a9d85f5e60484f47 ExtendlyOS Features Service recovered https://status.extendly.com/ Wed, 29 Oct 2025 16:51:47 +0000 https://status.extendly.com/#6be2e5293a68e58cdf442add63ff0ba7aa989102d0857fde7f7d1dc18ac3dc10 ExtendlyOS Data Graph went down https://status.extendly.com/ Wed, 29 Oct 2025 16:50:37 +0000 https://status.extendly.com/#5562b24c7f9ad5235c48a1274b561e1f2df2182d11f4bd49a9d85f5e60484f47 ExtendlyOS Features Service went down https://status.extendly.com/ Thu, 23 Oct 2025 16:17:33 +0000 https://status.extendly.com/#60835b9f2cc2384dd303699bdfef42dbfe7e8155491d4386e731e64d1233def7 ExtendlyOS Features Service recovered https://status.extendly.com/ Thu, 23 Oct 2025 16:17:10 +0000 https://status.extendly.com/#c4d6473cb7731e2bcfeb8bd08c9f531575c3c3671145868c4c17abdf68433144 ExtendlyOS Data Graph recovered https://status.extendly.com/ Thu, 23 Oct 2025 16:11:57 +0000 https://status.extendly.com/#c4d6473cb7731e2bcfeb8bd08c9f531575c3c3671145868c4c17abdf68433144 ExtendlyOS Data Graph went down https://status.extendly.com/ Thu, 23 Oct 2025 16:07:11 +0000 https://status.extendly.com/#e7c05a5db7327eff57a9517634d9d08871745d4f81f0b2d06fe811d078c82f7a ExtendlyOS Data Graph recovered https://status.extendly.com/ Thu, 23 Oct 2025 16:05:08 +0000 https://status.extendly.com/#e7c05a5db7327eff57a9517634d9d08871745d4f81f0b2d06fe811d078c82f7a ExtendlyOS Data Graph went down https://status.extendly.com/ Thu, 23 Oct 2025 16:02:28 +0000 https://status.extendly.com/#473e8803d0f55ea4b70cc6c5887d06cefe09f39cbd7c48e6c4e286880af8bea7 ExtendlyOS Data Graph recovered https://status.extendly.com/ Thu, 23 Oct 2025 15:25:21 +0000 https://status.extendly.com/#60835b9f2cc2384dd303699bdfef42dbfe7e8155491d4386e731e64d1233def7 ExtendlyOS Features Service went down https://status.extendly.com/ Thu, 23 Oct 2025 15:24:36 +0000 https://status.extendly.com/#89f2e038755ee9bc92204acce6ddbbc150e93401faed4a06d975b583f5391a35 ExtendlyOS Features Service recovered https://status.extendly.com/ Thu, 23 Oct 2025 15:22:34 +0000 https://status.extendly.com/#473e8803d0f55ea4b70cc6c5887d06cefe09f39cbd7c48e6c4e286880af8bea7 ExtendlyOS Data Graph went down https://status.extendly.com/ Thu, 23 Oct 2025 15:17:13 +0000 https://status.extendly.com/#89f2e038755ee9bc92204acce6ddbbc150e93401faed4a06d975b583f5391a35 ExtendlyOS Features Service went down https://status.extendly.com/ Thu, 23 Oct 2025 15:09:52 +0000 https://status.extendly.com/#24720115b69158738492a41e8728c4f18e3ed794154dfa184d25c9d32e65e4ad ExtendlyOS Features Service recovered https://status.extendly.com/ Thu, 23 Oct 2025 15:02:41 +0000 https://status.extendly.com/#24720115b69158738492a41e8728c4f18e3ed794154dfa184d25c9d32e65e4ad ExtendlyOS Features Service went down https://status.extendly.com/ Thu, 23 Oct 2025 14:54:51 +0000 https://status.extendly.com/#8b100ec4230229e2380b8b9e8a75eb20b1ab6c1f27882d7fc48abaaa320df3dd ExtendlyOS Features Service recovered https://status.extendly.com/ Thu, 23 Oct 2025 14:51:37 +0000 https://status.extendly.com/#8b100ec4230229e2380b8b9e8a75eb20b1ab6c1f27882d7fc48abaaa320df3dd ExtendlyOS Features Service went down https://status.extendly.com/ Thu, 23 Oct 2025 14:32:51 +0000 https://status.extendly.com/#3a8cdfd5c6be4f8239872e71666ef452f3917fa7488444657977b1126fe2cb16 ExtendlyOS Features Service recovered https://status.extendly.com/ Thu, 23 Oct 2025 14:23:13 +0000 https://status.extendly.com/#3a8cdfd5c6be4f8239872e71666ef452f3917fa7488444657977b1126fe2cb16 ExtendlyOS Features Service went down https://status.extendly.com/ Thu, 23 Oct 2025 14:20:04 +0000 https://status.extendly.com/#1168aaa153b3c04dc5837c7cee0bec7677523dbc92b725b9040f9b74f4336e0a ExtendlyOS Features Service recovered https://status.extendly.com/ Thu, 23 Oct 2025 14:12:57 +0000 https://status.extendly.com/#1168aaa153b3c04dc5837c7cee0bec7677523dbc92b725b9040f9b74f4336e0a ExtendlyOS Features Service went down https://status.extendly.com/ Thu, 23 Oct 2025 14:09:26 +0000 https://status.extendly.com/#c3a7e2bd32f2aa17c3557b484938e9d10fc46ed50063c87e261f04438f7f4c86 ExtendlyOS Features Service recovered https://status.extendly.com/ Thu, 23 Oct 2025 14:07:33 +0000 https://status.extendly.com/#c3a7e2bd32f2aa17c3557b484938e9d10fc46ed50063c87e261f04438f7f4c86 ExtendlyOS Features Service went down https://status.extendly.com/ Thu, 23 Oct 2025 13:57:00 +0000 https://status.extendly.com/#6c1f4f3860fd43a7e2964bb808bb9f513d44b105b4a40ace481d61b5b6e47579 ExtendlyOS Features Service recovered https://status.extendly.com/ Thu, 23 Oct 2025 13:41:45 +0000 https://status.extendly.com/#6c1f4f3860fd43a7e2964bb808bb9f513d44b105b4a40ace481d61b5b6e47579 ExtendlyOS Features Service went down https://status.extendly.com/ Thu, 23 Oct 2025 02:49:29 +0000 https://status.extendly.com/#3fc81fd5a13dac346e721691dbc00515273bdf50602296608b0f2e83f4940990 ExtendlyOS Features Service recovered https://status.extendly.com/ Thu, 23 Oct 2025 02:44:36 +0000 https://status.extendly.com/#3fc81fd5a13dac346e721691dbc00515273bdf50602296608b0f2e83f4940990 ExtendlyOS Features Service went down https://status.extendly.com/ Thu, 23 Oct 2025 02:34:15 +0000 https://status.extendly.com/#3b4e422cd8ec1bbb2c0851bf108dac2b8a07dac7de20eb3bf22dd7173149b8e6 ExtendlyOS Features Service recovered https://status.extendly.com/ Thu, 23 Oct 2025 02:31:42 +0000 https://status.extendly.com/#3b4e422cd8ec1bbb2c0851bf108dac2b8a07dac7de20eb3bf22dd7173149b8e6 ExtendlyOS Features Service went down