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

What to do

• Check whether you use Pipedream Pipedream, Event Sources - HTTP, REST API, Connect and 7 more. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 12h 15m it lasted.

  Anything that failed between 2025-10-20 13:10 UTC and 2025-10-21 01:26 UTC may need a replay.

• Subscribe to Pipedream's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=pipedream works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Pipedream 8

1. investigatingOct 20, 2025, 1:10 PM UTC

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

   provider

2. identifiedOct 20, 2025, 2:00 PM UTC

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

   provider

3. identifiedOct 20, 2025, 4:11 PM UTC

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

   provider

4. identifiedOct 20, 2025, 4:15 PM UTC

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

   provider

5. identifiedOct 20, 2025, 4:24 PM UTC

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

   provider

6. identifiedOct 20, 2025, 8:05 PM UTC

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

   provider

7. monitoringOct 20, 2025, 9:51 PM UTC

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

   provider

8. resolvedOct 21, 2025, 1:26 AM UTC

   This incident has been resolved.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.