Incidents reported on status page for Activepieces https://status.activepieces.com/ https://d1lppblt9t2x15.cloudfront.net/logos/1a56c336e9f92bb4944ef84297025bfa.png https://status.activepieces.com/ en https://status.activepieces.com/incident/943246 Sat, 04 Jul 2026 10:40:27 -0000 https://status.activepieces.com/incident/943246#6794bf32fcbf69f997e4ee554d7d02faf8b33b8a95434d66493f3a594e3cf847 Worker health recovered. https://status.activepieces.com/incident/943246 Sat, 04 Jul 2026 10:10:48 -0000 https://status.activepieces.com/incident/943246#f0bb6bce66f363c8e4e2f0e778b0591b6a37e9d7eee2c63b6a8340186c63f709 Worker health went down. https://status.activepieces.com/incident/937599 Sun, 28 Jun 2026 15:53:58 -0000 https://status.activepieces.com/incident/937599#3f73413d7f91840272103fc8f445fb58cf28e2df297f61a41e763028549cf97c Worker health recovered. https://status.activepieces.com/incident/937599 Sun, 28 Jun 2026 15:50:18 -0000 https://status.activepieces.com/incident/937599#86e21ca55b1d287a0778347e123d0c0e680211c7798c0b74ef5524b8abbfac20 API Health recovered. https://status.activepieces.com/incident/937599 Sun, 28 Jun 2026 15:46:11 -0000 https://status.activepieces.com/incident/937599#d01d61f9f0d2135eba0bf564f4f8ad7477a4c5da1acb4c7a4c0f981d100a1f7b API Health went down. https://status.activepieces.com/incident/937599 Sun, 28 Jun 2026 14:56:08 -0000 https://status.activepieces.com/incident/937599#091abcc28204ba825473b3f6c75a80a233fbe6a33318068d24579dad2190336f Worker health went down. https://status.activepieces.com/incident/937599 Sun, 28 Jun 2026 10:54:28 -0000 https://status.activepieces.com/incident/937599#fdbfbd40f793480b586edad727197355764cb00867900a74dd60d061f1b803a3 Worker health recovered. https://status.activepieces.com/incident/937599 Sun, 28 Jun 2026 10:25:35 -0000 https://status.activepieces.com/incident/937599#b1c6ac57d41dc2e9a54160a0c37a24f13982931abea86f0a1012f27d73e3832f Worker health went down. https://status.activepieces.com/incident/937154 Sat, 27 Jun 2026 21:09:33 -0000 https://status.activepieces.com/incident/937154#d27c6cea670c0d47381399b511c3e52cab3a5a2f4bddacd06fada5dce4120912 Worker health recovered. https://status.activepieces.com/incident/937154 Sat, 27 Jun 2026 20:30:46 -0000 https://status.activepieces.com/incident/937154#b2d3da35be458d3b802160acc8d122b3ea99689f8a7bbe408a4add7e5a38a1f6 Worker health went down. https://status.activepieces.com/incident/909982 Mon, 01 Jun 2026 12:16:00 -0000 https://status.activepieces.com/incident/909982#92e2af76e92ced2ca4c6e2c9ac91545b3555ef7a1dcb293fba5701b172b734d4 API Health recovered. flows are active https://status.activepieces.com/incident/909982 Mon, 01 Jun 2026 11:59:00 -0000 https://status.activepieces.com/incident/909982#b0bd97cb4795a63c993482bf5d619ea5cee23a3df4683f181e55196233d92149 API Health went down, the website is not responding and flows are not running but not lost https://status.activepieces.com/incident/900715 Wed, 20 May 2026 20:00:00 -0000 https://status.activepieces.com/incident/900715#25390f5bbf0fb4f108a0270a17e900e44419f51cc9304cc2957eb1adb370b333 There will be around 5 minutes expected downtime for our cloud due to infrastucture maintenance https://status.activepieces.com/incident/889461 Wed, 06 May 2026 15:05:00 -0000 https://status.activepieces.com/incident/889461#a42a7fd59deaf39efe1d56ca7f2fe6e4fb31381205b935cc540254816007047f The issue is fixed and all failed runs has been retried from failing step.. https://status.activepieces.com/incident/889461 Wed, 06 May 2026 06:30:00 -0000 https://status.activepieces.com/incident/889461#de0bff1a67e5e7eb82cdbc8b1f04fb478845e4ae349f3928a62bd9387a8e6514 Between 06:30 and 15:00 UTC on 2026-05-06, flow runs that made outbound HTTP calls (OpenAI, Anthropic, and most third-party pieces) failed with `getaddrinfo EAI_AGAIN`. The sandbox could not resolve public hostnames because its DNS servers were not on the kernel egress allowlist. A fix has been deployed and flows are running normally and all failed runs has been retried from failing step.. https://status.activepieces.com/incident/903562 Sun, 03 May 2026 15:05:37 -0000 https://status.activepieces.com/incident/903562#3117f7a62ef99026e5e3399ad366c92750864e0f1daf909a558f7f3eb7d9c73a Maintenance completed https://status.activepieces.com/incident/903562 Sun, 03 May 2026 14:05:37 -0000 https://status.activepieces.com/incident/903562#8b08946bad7e6d204d19f2efe2dc5455ce9ec528dd5bc0839884ba74d37f6952 API health will be down for some minutes due to a change in our infrastucture https://status.activepieces.com/incident/887106 Sun, 03 May 2026 10:00:00 -0000 https://status.activepieces.com/incident/887106#59ac172bd375e56000428fea195f688c152aa7a44e5c2b0dc6ea5b1dd3c98883 Users that try to sign up for first time on cloud.activepieces.com via google/saml authentication were getting redirected to wrong page. which blocked them from getting into their accounts. https://status.activepieces.com/incident/877982 Thu, 23 Apr 2026 08:20:00 -0000 https://status.activepieces.com/incident/877982#474cbce9973251b208a76275f15b2a34a68334e3c2617545adba1439693ba274 The egress proxy change is now reverted https://status.activepieces.com/incident/877982 Thu, 23 Apr 2026 07:20:00 -0000 https://status.activepieces.com/incident/877982#f3abf46c6191e6b90405ac3c5de300e5826105b9182f4deb76db4cdc75f84520 If you have a piece of code that calls an external API using an HTTPS URL, it may fail with the error getaddrinfo EAI_AGAIN. The change has been reverted. https://status.activepieces.com/incident/867015 Wed, 08 Apr 2026 10:32:06 -0000 https://status.activepieces.com/incident/867015#98f53ef6833ac9762f23d08a3a1db16152a7eb3239d2f10805f6797ab77c332b API Health recovered. https://status.activepieces.com/incident/867015 Wed, 08 Apr 2026 10:28:13 -0000 https://status.activepieces.com/incident/867015#069c18f818a14faa771e05dd942802de94a6632088b8f0d5e08fe784e1dda2de API Health went down. https://status.activepieces.com/incident/856519 Sun, 22 Mar 2026 18:00:00 -0000 https://status.activepieces.com/incident/856519#eb57003161dc0427ea1b66f6af5b8edae57aa7543d360a115231dd574fbe0ee3 Resolved. Log display delays have been fixed and logs are now showing in real-time. https://status.activepieces.com/incident/856519 Sat, 21 Mar 2026 12:00:00 -0000 https://status.activepieces.com/incident/856519#76769ebe856fbc02d599ad4ec171a1e7e7cdcfc7c9b8696383ded702242c85e3 Logs were experiencing significant delays (1-3 hours) in displaying. Flow execution continued normally. https://status.activepieces.com/incident/856518 Thu, 19 Mar 2026 18:00:00 -0000 https://status.activepieces.com/incident/856518#9a6ee1fca9826803c9fc04c1901a08804c8036c0633535f5720c756687c330a1 Resolved. The infinite loop bug has been fixed and Redis load is back to normal. All affected executions were replayed with no data loss. https://status.activepieces.com/incident/856516 Thu, 19 Mar 2026 16:00:00 -0000 https://status.activepieces.com/incident/856516#af476e821dbd73dca5ae81ba30a658b369ae38ecfc8fb592cf7f4780da44a2b8 Resolved. Rolled back to previous deployment system. All services restored to normal operation. https://status.activepieces.com/incident/856518 Thu, 19 Mar 2026 14:00:00 -0000 https://status.activepieces.com/incident/856518#34c53aefa5ab755be0a1c251a8be509a394d7f9f7ffde7608cd27c6fe523fa6c Flows with delay steps experienced repeated executions due to a bug causing infinite loops, overloading Redis. All affected executions were replayed after restoration with no data loss. https://status.activepieces.com/incident/856516 Thu, 19 Mar 2026 08:00:00 -0000 https://status.activepieces.com/incident/856516#f0cad7a689bce18573c41102a765dc5e77c152357b4cf83cfbc30ee46f933e73 Issues arose during Kubernetes-based worker architecture migration. System entered unstable intermediate state, requiring rollback to previous deployment system.