Activepieces incident

DNS Issue

Minor Resolved View vendor source →

Activepieces experienced a minor incident on May 6, 2026 affecting Health (Worker health), lasting 8h 35m. The incident has been resolved; the full update timeline is below.

Started
May 06, 2026, 06:30 AM UTC
Resolved
May 06, 2026, 03:05 PM UTC
Duration
8h 35m
Detected by Pingoru
May 06, 2026, 06:30 AM UTC

Affected components

Health (Worker health)

Update timeline

  1. 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..

  2. resolved May 06, 2026, 03:05 PM UTC

    The issue is fixed and all failed runs has been retried from failing step..

Looking to track Activepieces downtime and outages?

Pingoru polls Activepieces's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when Activepieces reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track Activepieces alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring Activepieces for free

5 free monitors · No credit card required