Companies / Pipedream / incidents

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

Affected components: Backend - GitHub SyncGitHub SyncConnectConnect - ConnectBackend - Event Sources - HTTPEvent Sources - HTTPBackend - Pipedream destinationsPipedream destinationsBackend - Workflows - TimerWorkflows - TimerBackend - Event Sources - TimerEvent Sources - TimerBackend - Workflows - HTTPWorkflows - HTTPPublic APIs - REST APIREST APIBackend - Workflows - EmailWorkflows - EmailConnect APIPublic APIs - Connect APIFrontend - PipedreamPipedream

Timeline of updates

1. investigating2025-10-20 13:10 UTC

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

2. identified2025-10-20 14:00 UTC

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

3. identified2025-10-20 16:11 UTC

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

4. identified2025-10-20 16:15 UTC

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

5. identified2025-10-20 16:24 UTC

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

6. identified2025-10-20 20:05 UTC

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

7. monitoring2025-10-20 21:51 UTC

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

8. resolved2025-10-21 01:26 UTC

   This incident has been resolved.

Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab). Pipedream profile · Recent Pipedream incidents · Markdown · JSON