Worker health is down
Affected: Health (Worker health)
Timeline · 1 update
- investigating Jun 07, 2026, 12:11 PM UTC
Worker health went down.
Activepieces Outage History
Activepieces is up right nowActivepieces had 9 outages in the last 2 years totaling 52h 24m of downtime — averaging 0.4 incidents per month.
There were 9 Activepieces outages since March 19, 2026 totaling 52h 24m of downtime. Each is summarised below — incident details, duration, and resolution information.
API Health and Worker healt...
Affected: Health (API Health)Health (Worker health)
Timeline · 3 updates
- investigating Jun 01, 2026, 11:29 AM UTC
Worker health went down.
- investigating Jun 01, 2026, 11:59 AM UTC
API Health went down. no data was lost
- resolved Jun 01, 2026, 12:16 PM UTC
API Health recovered.
DNS Issue
Affected: Health (Worker health)
Timeline · 2 updates
- investigating May 06, 2026, 06:30 AM UTC
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..
- resolved May 06, 2026, 03:05 PM UTC
The issue is fixed and all failed runs has been retried from failing step..
Users see error page after ...
Affected: Health (API Health)
Timeline · 1 update
- resolved May 03, 2026, 10:00 AM UTC
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.
Outbound DNS Issue
Affected: Health (Worker health)
Timeline · 2 updates
- investigating Apr 23, 2026, 07:20 AM UTC
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.
- resolved Apr 23, 2026, 08:20 AM UTC
The egress proxy change is now reverted
API Health is down
Affected: Health (API Health)
Timeline · 2 updates
- investigating Apr 08, 2026, 10:28 AM UTC
API Health went down.
- resolved Apr 08, 2026, 10:32 AM UTC
API Health recovered.
Delay in Showing Logs
Affected: Health (API Health)
Timeline · 2 updates
- investigating Mar 21, 2026, 12:00 PM UTC
Logs were experiencing significant delays (1-3 hours) in displaying. Flow execution continued normally.
- resolved Mar 22, 2026, 06:00 PM UTC
Resolved. Log display delays have been fixed and logs are now showing in real-time.
Repeated Execution for Flow...
Affected: Health (Worker health)
Timeline · 2 updates
- investigating Mar 19, 2026, 02:00 PM UTC
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.
- resolved Mar 19, 2026, 06:00 PM UTC
Resolved. The infinite loop bug has been fixed and Redis load is back to normal. All affected executions were replayed with no data loss.
Accident during Infrastruct...
Affected: Health (Worker health)
Timeline · 2 updates
- investigating Mar 19, 2026, 08:00 AM UTC
Issues arose during Kubernetes-based worker architecture migration. System entered unstable intermediate state, requiring rollback to previous deployment system.
- resolved Mar 19, 2026, 04:00 PM UTC
Resolved. Rolled back to previous deployment system. All services restored to normal operation.