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/ 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/ Thu, 05 Jun 2025 11:58:03 +0000 https://status.pipeops.io/#ea570df1a4dd36b0cb05f421d11e070e071ec4585b5a0398c40c26fc172ff836 blog.pipeops.io recovered https://status.pipeops.io/ Thu, 05 Jun 2025 11:52:58 +0000 https://status.pipeops.io/#ea570df1a4dd36b0cb05f421d11e070e071ec4585b5a0398c40c26fc172ff836 blog.pipeops.io went down https://status.pipeops.io/ Wed, 04 Jun 2025 19:07:56 +0000 https://status.pipeops.io/#b9bf6671de98151135be62ee124148b8e7a47f696937f4a7dea5a0c629406996 blog.pipeops.io recovered https://status.pipeops.io/ Wed, 04 Jun 2025 19:03:38 +0000 https://status.pipeops.io/#b9bf6671de98151135be62ee124148b8e7a47f696937f4a7dea5a0c629406996 blog.pipeops.io went down https://status.pipeops.io/ Thu, 29 May 2025 11:23:15 +0000 https://status.pipeops.io/#b85eb0687294018929edffa0c0ee32633d2e7b80f65897c4730b63e13c895c24 api.pipeops.io recovered https://status.pipeops.io/ Thu, 29 May 2025 11:21:14 +0000 https://status.pipeops.io/#b85eb0687294018929edffa0c0ee32633d2e7b80f65897c4730b63e13c895c24 api.pipeops.io went down https://status.pipeops.io/ Thu, 22 May 2025 01:00:27 +0000 https://status.pipeops.io/#83c6e13481e05c370284318b805d9719239e20382ac64363979412cbdb3b9b55 blog.pipeops.io recovered https://status.pipeops.io/ Thu, 22 May 2025 00:56:16 +0000 https://status.pipeops.io/#83c6e13481e05c370284318b805d9719239e20382ac64363979412cbdb3b9b55 blog.pipeops.io went down https://status.pipeops.io/ Mon, 05 May 2025 17:48:52 +0000 https://status.pipeops.io/#5dc4a84f2b160367ffa9d42ce7ef0b269ebd2b129fba8608f74f037f63a783b7 blog.pipeops.io recovered https://status.pipeops.io/ Mon, 05 May 2025 17:44:36 +0000 https://status.pipeops.io/#5dc4a84f2b160367ffa9d42ce7ef0b269ebd2b129fba8608f74f037f63a783b7 blog.pipeops.io went down https://status.pipeops.io/ Sat, 03 May 2025 23:27:57 +0000 https://status.pipeops.io/#cf1d941abc83da058305e708d528b610922d960845ef92ff6145fdc216ef894b blog.pipeops.io recovered https://status.pipeops.io/ Sat, 03 May 2025 23:23:43 +0000 https://status.pipeops.io/#cf1d941abc83da058305e708d528b610922d960845ef92ff6145fdc216ef894b blog.pipeops.io went down https://status.pipeops.io/ Tue, 22 Apr 2025 01:29:42 +0000 https://status.pipeops.io/#2222db1ec144eac1041fb20f88af85657863a9eae922be4f662aa2420dabaceb blog.pipeops.io recovered https://status.pipeops.io/ Tue, 22 Apr 2025 01:25:29 +0000 https://status.pipeops.io/#2222db1ec144eac1041fb20f88af85657863a9eae922be4f662aa2420dabaceb blog.pipeops.io went down https://status.pipeops.io/ Tue, 22 Apr 2025 01:04:43 +0000 https://status.pipeops.io/#e57412e961a98788896b6cc710ba1e20317f2642a3c87f5a7f18e9ecefe65f66 blog.pipeops.io recovered https://status.pipeops.io/ Tue, 22 Apr 2025 01:00:29 +0000 https://status.pipeops.io/#e57412e961a98788896b6cc710ba1e20317f2642a3c87f5a7f18e9ecefe65f66 blog.pipeops.io went down https://status.pipeops.io/ Fri, 18 Apr 2025 05:15:07 +0000 https://status.pipeops.io/#d3e39e956adc27d44c5fd51bcbd108793d5c91954afb14d3320d4a7895f997fe console.pipeops.io recovered https://status.pipeops.io/ Fri, 18 Apr 2025 05:12:46 +0000 https://status.pipeops.io/#d3e39e956adc27d44c5fd51bcbd108793d5c91954afb14d3320d4a7895f997fe console.pipeops.io went down https://status.pipeops.io/ Sun, 13 Apr 2025 04:05:24 +0000 https://status.pipeops.io/#aa03e447d9495f1848b7b88df7ccba687ca98dc08e65d5bd075503ea54cf69c0 blog.pipeops.io recovered https://status.pipeops.io/ Sun, 13 Apr 2025 04:01:11 +0000 https://status.pipeops.io/#aa03e447d9495f1848b7b88df7ccba687ca98dc08e65d5bd075503ea54cf69c0 blog.pipeops.io went down https://status.pipeops.io/ Sat, 05 Apr 2025 15:05:34 +0000 https://status.pipeops.io/#4a0524065dc42383d176944d5940e459993a8629e7812462351954d98fa7128c blog.pipeops.io recovered https://status.pipeops.io/ Sat, 05 Apr 2025 15:00:59 +0000 https://status.pipeops.io/#4a0524065dc42383d176944d5940e459993a8629e7812462351954d98fa7128c blog.pipeops.io went down https://status.pipeops.io/ Wed, 02 Apr 2025 19:53:03 +0000 https://status.pipeops.io/#23c0c9d15346ecde8e6d32158718f217ea1c492d2a7cc57b6af78e8fcdbbfbfc blog.pipeops.io recovered https://status.pipeops.io/ Wed, 02 Apr 2025 19:48:17 +0000 https://status.pipeops.io/#23c0c9d15346ecde8e6d32158718f217ea1c492d2a7cc57b6af78e8fcdbbfbfc 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.