- Level
- confirmed
- Worst impact
- Operational
- Components
- Pipedream, Event Sources - HTTP
What to do
Check whether you use Pipedream Pipedream, Event Sources - HTTP. 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 4h 30m it lasted.
Anything that failed between 2025-05-27 08:00 UTC and 2025-05-27 12:30 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 3
- investigating
Some customers are reporting an issue with workflow triggers.
provider
- monitoring
The issue impacting workflow triggers appears to be resolved. Events are processing again and we are monitoring our systems to ensure that triggers continue working as expected.
provider
- resolved
We are no longer seeing issues with the impacted workflows and all workflows are properly running 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-c2d06f906b
Is Pipedream still down?
No, this incident was resolved 2025-05-27 12:30 UTC. For Pipedream's live state, see https://down.guide/providers/pipedream.
How long did it last?
4h 30m, from 2025-05-27 08:00 UTC to 2025-05-27 12:30 UTC, by the times Pipedream posted.
What was affected?
Pipedream named Pipedream, Event Sources - HTTP.
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.