There were 6 Activepieces outages since March 19, 2026 totaling 43h 5m of downtime. Each is summarised below — incident details, duration, and resolution information.
Worker health went down.
Worker health went down.
Worker health recovered.
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.
The egress proxy change is now reverted
API Health went down.
API Health recovered.
Logs were experiencing significant delays (1-3 hours) in displaying. Flow execution continued normally.
Resolved. Log display delays have been fixed and logs are now showing in real-time.
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. The infinite loop bug has been fixed and Redis load is back to normal. All affected executions were replayed with no data loss.
Issues arose during Kubernetes-based worker architecture migration. System entered unstable intermediate state, requiring rollback to previous deployment system.
Resolved. Rolled back to previous deployment system. All services restored to normal operation.
Pingoru polls Activepieces's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.
5 free monitors · No credit card required