Skip to main content
Pipedream

string.com temporarily unable to respond to chats

Partial outage Lasted 35m · started · Pipedream's page

Level
confirmed
Worst impact
Partial outage
Components
Pipedream
Down Index
26of 100

What to do

  • Check whether you use Pipedream Pipedream. 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 35m it lasted.

    Anything that failed between 2026-10-05 17:58 UTC and 2026-10-05 18:32 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. investigating

    We're investigating an issue with our Anthropic account that powers string.com chats. All pipedream.com services and workflows should be unaffected.

    provider

  2. resolved

    string.com chats are working, and service has been restored.

    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-642721dd6e

Is Pipedream still down?

No, this incident was resolved 2026-10-05 18:32 UTC. For Pipedream's live state, see https://down.guide/pipedream.

How long did it last?

35m, from 2026-10-05 17:58 UTC to 2026-10-05 18:32 UTC, by the times Pipedream posted.

What was affected?

Pipedream named Pipedream.

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.