Skip to main content
Pipedream

Currently facing backend issues

Degraded Lasted 3h 21m · started · Pipedream's page

Level
confirmed
Worst impact
Degraded
Components
REST API, Connect API
Down Index
20of 100

What to do

  • Check whether you use Pipedream REST API, Connect API. 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 3h 21m it lasted.

    Anything that failed between 2025-11-04 15:53 UTC and 2025-11-04 19:14 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

  1. investigating

    We are currently investigating this issue.

    provider

  2. monitoring

    Things have stabilized and we're continuing to monitor

    provider

  3. resolved

    root cause identified, Short term Mitigation efforts have been successful. Long term Mitigation solution has been identified and will be implemented as soon as the fix has passed our QA processes.

    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-57d34ce5de

Is Pipedream still down?

No, this incident was resolved 2025-11-04 19:14 UTC. For Pipedream's live state, see https://down.guide/pipedream.

How long did it last?

3h 21m, from 2025-11-04 15:53 UTC to 2025-11-04 19:14 UTC, by the times Pipedream posted.

What was affected?

Pipedream named REST API, Connect API.

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.