- Level
- confirmed
- Worst impact
- Degraded
- Components
- Event Sources - HTTP
- Down Index
- 15of 100
What to do
Check whether you use Pipedream Event Sources - HTTP. 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 26m it lasted.
Anything that failed between 2025-07-24 19:05 UTC and 2025-07-24 19:31 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
We are currently investigating this issue.
provider
- monitoring
sources are no longer delayed and we are currently monitoring.
provider
- resolved
This incident has been resolved.
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-6fe8c46833
Is Pipedream still down?
No, this incident was resolved 2025-07-24 19:31 UTC. For Pipedream's live state, see https://down.guide/pipedream.
How long did it last?
26m, from 2025-07-24 19:05 UTC to 2025-07-24 19:31 UTC, by the times Pipedream posted.
What was affected?
Pipedream named 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.