- Level
- confirmed
- Worst impact
- Operational
- Components
- Event Sources - HTTP, Event Sources - Timer
What to do
Check whether you use Pipedream Event Sources - HTTP, Event Sources - Timer. 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 9m it lasted.
Anything that failed between 2024-08-27 16:26 UTC and 2024-08-27 16:35 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 2
- investigating
We're seeing a spike in volume on event sources, leading to a delay in event processing. We're investigating and will post updates ASAP.
provider
- resolved
We've disabled the traffic source causing the spike, and delays are back to normal
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-6fbb441ed2
Is Pipedream still down?
No, this incident was resolved 2024-08-27 16:35 UTC. For Pipedream's live state, see https://down.guide/providers/pipedream.
How long did it last?
9m, from 2024-08-27 16:26 UTC to 2024-08-27 16:35 UTC, by the times Pipedream posted.
What was affected?
Pipedream named Event Sources - HTTP, Event Sources - Timer.
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.