Activepieces Outage History
Activepieces is up right nowPingoru has recorded 27 incidents for Activepieces: 27 in the last 12 months and 5 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 3 | 1 of 720 (0%) |
| May 2026 | 9 | 35 of 744 (5%) |
| June 2026 | 6 | 8 of 720 (1%) |
| July 2026 | 3 | 6 of 744 (1%) |
| August 2026 | 4 | 19 of 744 (3%) |
| September 2026 | 0 | 0 of 720 (0%) |
| October 2026 | 0 | 0 of 511 (0%) |
Incidents, newest first
Major August 17, 2026 Worker health is down 18h 26m Health (Worker health)
Started Aug 17, 2026, 10:00 PM UTC· resolved Aug 18, 2026, 04:27 PM UTC
No vendor updates were posted for this incident.
Major June 28, 2026 Worker health and API Healt... 5h 28m Health (API Health), Health (Worker health)
Started Jun 28, 2026, 10:25 AM UTC· resolved Jun 28, 2026, 03:53 PM UTC
No vendor updates were posted for this incident.
Major June 1, 2026 API Health and Worker health are down 17m Health (API Health), Health (Worker health), Health (API Health)
Started Jun 01, 2026, 11:59 AM UTC· resolved Jun 01, 2026, 12:16 PM UTC
- 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. flows are active
Minor May 6, 2026 DNS Issue 8h 35m Health (Worker health), Health (Worker health)
Started May 06, 2026, 06:30 AM UTC· resolved May 06, 2026, 03:05 PM UTC
- 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..
Minor May 3, 2026 Users see error page after signup with google on cloud – Health (API Health), Health (API Health)
Started May 03, 2026, 10:00 AM UTC· resolved May 03, 2026, 10:00 AM UTC
- 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.
Minor April 23, 2026 Outbound DNS Issue 1h Health (Worker health), Health (Worker health)
Started Apr 23, 2026, 07:20 AM UTC· resolved Apr 23, 2026, 08:20 AM UTC
- 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
Major April 8, 2026 API Health is down 3m Health (API Health), Health (API Health)
Started Apr 08, 2026, 10:28 AM UTC· resolved Apr 08, 2026, 10:32 AM UTC
- investigating Apr 08, 2026, 10:28 AM UTC
API Health went down.
- resolved Apr 08, 2026, 10:32 AM UTC
API Health recovered.
Minor March 21, 2026 Delay in Showing Logs 1d 6h Health (API Health), Health (API Health)
Started Mar 21, 2026, 12:00 PM UTC· resolved Mar 22, 2026, 06:00 PM UTC
- 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.
Minor March 19, 2026 Repeated Execution for Flows with Delay 4h Health (Worker health), Health (Worker health)
Started Mar 19, 2026, 02:00 PM UTC· resolved Mar 19, 2026, 06:00 PM UTC
- 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.