- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 20of 100
What to do
Check whether your product depends on Pipedream. Check your stack
Drop a package.json, lockfile, Terraform or a list of domains at down.guide to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 3h 9m it lasted.
Anything that failed between 2025-06-03 16:24 UTC and 2025-06-03 19:32 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 4
- investigating
We are currently investigating this issue.
provider
- identified
The issue has been identified and a fix is being implemented.
provider
- monitoring
Connect Webhooks have now resumed their normal execution.
provider
- resolved
We are no longer seeing issues with Connect Webhooks. Triggers are executing normally once again.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-f796a1ced5
Is Pipedream still down?
No, this incident was resolved 2025-06-03 19:32 UTC. For Pipedream's live state, see https://down.guide/providers/pipedream.
How long did it last?
3h 9m, from 2025-06-03 16:24 UTC to 2025-06-03 19:32 UTC, by the times Pipedream posted.
What caused it?
Pipedream hasn't published a root cause. If it does, it shows here.
Where does this come from?
Pipedream's official status page, https://status.pipedream.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.