Incidents reported on status page for PipeOps https://status.pipeops.io/ https://d1lppblt9t2x15.cloudfront.net/logos/49bdf5cc125710782bdd53d54017742e.gif https://status.pipeops.io/ en https://status.pipeops.io/ Sat, 23 Aug 2025 23:00:21 +0000 https://status.pipeops.io/#876ddc354c7bd3a4d84095645dbcc53b734189bbdbd83def9f75465f8cf39e8c api.pipeops.io recovered https://status.pipeops.io/ Sat, 23 Aug 2025 22:58:16 +0000 https://status.pipeops.io/#876ddc354c7bd3a4d84095645dbcc53b734189bbdbd83def9f75465f8cf39e8c api.pipeops.io went down https://status.pipeops.io/ Wed, 06 Aug 2025 11:21:58 +0000 https://status.pipeops.io/#6411d45443777f1ad2615091a76db74284473b98ad407e23adf48f009711dc96 blog.pipeops.io went down https://status.pipeops.io/ Sat, 05 Jul 2025 13:28:27 +0000 https://status.pipeops.io/#def85e76261555fa9eb76a47fe23de88d9eff471509289f04a4e07d1bb9a68f3 blog.pipeops.io recovered https://status.pipeops.io/ Sat, 05 Jul 2025 13:19:09 +0000 https://status.pipeops.io/#def85e76261555fa9eb76a47fe23de88d9eff471509289f04a4e07d1bb9a68f3 blog.pipeops.io went down https://status.pipeops.io/ Tue, 01 Jul 2025 06:34:04 +0000 https://status.pipeops.io/#f329773c967a96ce87ca68cd32d4865d0a28d80f792756222f74ab91cf53799b api.pipeops.io recovered https://status.pipeops.io/ Tue, 01 Jul 2025 06:33:12 +0000 https://status.pipeops.io/#f329773c967a96ce87ca68cd32d4865d0a28d80f792756222f74ab91cf53799b api.pipeops.io went down https://status.pipeops.io/ Fri, 27 Jun 2025 00:19:06 +0000 https://status.pipeops.io/#9cffce766427780b57f6f36777bc45835ae7bb48bcd04f39cefdee8e00943803 blog.pipeops.io recovered https://status.pipeops.io/ Fri, 27 Jun 2025 00:14:48 +0000 https://status.pipeops.io/#9cffce766427780b57f6f36777bc45835ae7bb48bcd04f39cefdee8e00943803 blog.pipeops.io went down https://status.pipeops.io/ Wed, 11 Jun 2025 06:52:37 +0000 https://status.pipeops.io/#89de6a58bff55aae50482f4150ed957d35c165730f2d09df53c746de4497d27e blog.pipeops.io recovered https://status.pipeops.io/ Wed, 11 Jun 2025 06:48:28 +0000 https://status.pipeops.io/#89de6a58bff55aae50482f4150ed957d35c165730f2d09df53c746de4497d27e blog.pipeops.io went down https://status.pipeops.io/incident/225349 Tue, 27 Jun 2023 13:21:00 -0000 https://status.pipeops.io/incident/225349#f829db21a41eb3db515de87bc2306a57993fcf3ce185030b6be481db8a1ac632 We recently rolled out an update (V1) for pipeops.io, which resulted in the removal of the health check page on the frontend. As a consequence, health checks were returning a 404 error for over 4 hours. We want to clarify that this issue only impacted the health check functionality and there was no actual downtime for the console dashboard or other services. Resolution: Our team has identified and resolved the issue causing the health check page to be unavailable. As of now, the problem has been fixed, and health checks are now functioning as expected. We sincerely apologize for any inconvenience caused during this incident. We are actively reviewing our deployment processes to ensure that similar issues are prevented in the future. If you encounter any further issues or have any concerns, please don't hesitate to reach out to our support team at support@pipeops.io We appreciate your patience and understanding.