Activepieces incident

DNS Issue

Resolved after 8 hours 35 minutes, affecting section-313838 (Worker health) and section-313838 (Worker health), on May 6, 2026.

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

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

section-313838 (Worker health)section-313838 (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..

Your product runs on more than Activepieces

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.

Add your stack →