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/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/895818 Thu, 14 May 2026 11:40:30 -0000 https://status.activepieces.com/incident/895818#a38449e99d83e6875165ec3d4874d62501af3144f2a92bed6ca19ee919ca3151 Worker health recovered. https://status.activepieces.com/incident/895818 Thu, 14 May 2026 10:53:47 -0000 https://status.activepieces.com/incident/895818#88d2025900c38cf59b2aa053206dce10cfe1d4e66e8902c10622b7d614dda593 Worker health went down. https://status.activepieces.com/incident/895196 Wed, 13 May 2026 16:03:47 -0000 https://status.activepieces.com/incident/895196#7a512f1c91b498c59108a791b566c2dca4a91bb4af3891809107525a7f5b4f75 Worker health recovered. https://status.activepieces.com/incident/895196 Wed, 13 May 2026 15:58:13 -0000 https://status.activepieces.com/incident/895196#990214a571c31ff201f0772e9fc9eda8cfe19b232dc75cf128e5cf7ecdf3f298 Worker health went down. 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.