Pipedream incident

The platform has recovered from a previous outage. We will continue to monitor.

Notice Resolved View vendor source →

Pipedream experienced a notice incident on October 20, 2025 affecting Pipedream and Event Sources - HTTP and 1 more component, lasting 12h 15m. The incident has been resolved; the full update timeline is below.

Started
Oct 20, 2025, 01:10 PM UTC
Resolved
Oct 21, 2025, 01:26 AM UTC
Duration
12h 15m
Detected by Pingoru
Oct 20, 2025, 01:10 PM UTC

Affected components

PipedreamEvent Sources - HTTPREST APIConnectWorkflows - TimerConnect APIWorkflows - HTTPEvent Sources - TimerPipedream destinationsWorkflows - Email

Update timeline

  1. investigating Oct 20, 2025, 01:10 PM UTC

    We are seeing some HTTP triggers returning a 503 status and are investigating.

  2. identified Oct 20, 2025, 02:00 PM UTC

    These errors are due to our upstream provider (AWS) still having an ongoing outage.

  3. identified Oct 20, 2025, 04:11 PM UTC

    Multiple services are experiencing a service disruption as a result of a downstream provider (AWS). We are closely monitoring the status.

  4. identified Oct 20, 2025, 04:15 PM UTC

    We are continuing to work on a fix for this issue.

  5. identified Oct 20, 2025, 04:24 PM UTC

    Multiple services are experiencing a service disruption as a result of a downstream provider (AWS). We are closely monitoring the status.

  6. identified Oct 20, 2025, 08:05 PM UTC

    Some services are starting to come back online, some of the queued events are being processed.

  7. monitoring Oct 20, 2025, 09:51 PM UTC

    Event queues have caught up. We are continuing to monitor the platform.

  8. resolved Oct 21, 2025, 01:26 AM UTC

    This incident has been resolved.