Skip to main content
Pipedream

Xfinity outage affecting access to Pipedream services

Degraded Lasted 27m · started · Pipedream's page

Level
confirmed
Worst impact
Degraded
Components
REST API, Workflows - HTTP
Down Index
16of 100

What to do

  • Check whether you use Pipedream REST API, Workflows - 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 27m it lasted.

    Anything that failed between 2024-03-05 21:25 UTC and 2024-03-05 21:51 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

  1. identified

    We've seen reports of some users failing to access Pipedream HTTP endpoints and the Pipedream API. We've isolated this to an issue with the Xfinity ISP and will post updates here as services become available.

    provider

  2. resolved

    The Xfinity outage 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-3faaf7c55b

Is Pipedream still down?

No, this incident was resolved 2024-03-05 21:51 UTC. For Pipedream's live state, see https://down.guide/pipedream.

How long did it last?

27m, from 2024-03-05 21:25 UTC to 2024-03-05 21:51 UTC, by the times Pipedream posted.

What was affected?

Pipedream named REST API, Workflows - 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.