Incidents reported on status page for Zerops https://status.zerops.io/ en https://status.zerops.io/ Fri, 21 Nov 2025 15:12:36 +0000 https://status.zerops.io/#6edfb8d173992d4003362901e5636295467e2792fcf5b66a2b67ea1a8c7cdcd1 Object Storage Write Quorum recovered https://status.zerops.io/ Fri, 21 Nov 2025 15:08:28 +0000 https://status.zerops.io/#95415baa8a419f56e09ad66cf88b32c5a7c3f245125882cc244ef0cb316fc22a Object Storage Read Quorum recovered https://status.zerops.io/incident/771686 Fri, 21 Nov 2025 15:05:00 -0000 https://status.zerops.io/incident/771686#fac8fda8ac68b7ea9cd276168cd2d77b530aeb0da6bf42d8a62a5278f04c3f8a We are currently solving a production problem on object storage. Its outage results in the inability to deploy. Running client services are unaffected. Object storage operation has been restored. The application is fully functional again. The cause was an internal network configuration error. https://status.zerops.io/incident/771686 Fri, 21 Nov 2025 15:05:00 -0000 https://status.zerops.io/incident/771686#fac8fda8ac68b7ea9cd276168cd2d77b530aeb0da6bf42d8a62a5278f04c3f8a We are currently solving a production problem on object storage. Its outage results in the inability to deploy. Running client services are unaffected. Object storage operation has been restored. The application is fully functional again. The cause was an internal network configuration error. https://status.zerops.io/incident/771686 Fri, 21 Nov 2025 15:05:00 -0000 https://status.zerops.io/incident/771686#fac8fda8ac68b7ea9cd276168cd2d77b530aeb0da6bf42d8a62a5278f04c3f8a We are currently solving a production problem on object storage. Its outage results in the inability to deploy. Running client services are unaffected. Object storage operation has been restored. The application is fully functional again. The cause was an internal network configuration error. https://status.zerops.io/ Fri, 21 Nov 2025 13:06:09 +0000 https://status.zerops.io/#95415baa8a419f56e09ad66cf88b32c5a7c3f245125882cc244ef0cb316fc22a Object Storage Read Quorum went down https://status.zerops.io/ Fri, 21 Nov 2025 13:00:40 +0000 https://status.zerops.io/#6edfb8d173992d4003362901e5636295467e2792fcf5b66a2b67ea1a8c7cdcd1 Object Storage Write Quorum went down https://status.zerops.io/ Wed, 15 Oct 2025 18:13:14 +0000 https://status.zerops.io/#0f5e2016e04d5b5ba79b298827c0b1fff6a077498383c16b1798b9eac4318d5d API & Dashboard recovered https://status.zerops.io/ Wed, 15 Oct 2025 18:04:21 +0000 https://status.zerops.io/#0f5e2016e04d5b5ba79b298827c0b1fff6a077498383c16b1798b9eac4318d5d API & Dashboard went down https://status.zerops.io/incident/495837 Tue, 14 Jan 2025 19:42:00 -0000 https://status.zerops.io/incident/495837#a0ac8b41a046adeed834a2bcd262018c331497e5286c38a01584ca8da1803483 As part of ongoing effort to repair our billing database cluster, which caused the previous accident ealier this week a critical internal component was restarted which caused a cascade of fails which shortly affected user applications. We are working on restoring the system to full health. Update: user apps back up and dashboard / API access restored https://status.zerops.io/incident/495837 Tue, 14 Jan 2025 19:42:00 -0000 https://status.zerops.io/incident/495837#a0ac8b41a046adeed834a2bcd262018c331497e5286c38a01584ca8da1803483 As part of ongoing effort to repair our billing database cluster, which caused the previous accident ealier this week a critical internal component was restarted which caused a cascade of fails which shortly affected user applications. We are working on restoring the system to full health. Update: user apps back up and dashboard / API access restored https://status.zerops.io/incident/494621 Sun, 12 Jan 2025 09:10:00 -0000 https://status.zerops.io/incident/494621#9098b730285339ab85e2ce6272e050f5c14b94ae6bcdacebbc8a66a3456d06c6 We are working on resolving the issue. User applications unaffected. https://status.zerops.io/incident/351459 Fri, 05 Apr 2024 20:42:00 -0000 https://status.zerops.io/incident/351459#b0040b8a72bc9d1062b01743e7c78ffe1feb0559362452d1dbd5567e482166ff There was 7hrs downtime caused by wrongly configured igmp queries within multicast vxlans during migration to the new hardware.