Changes / Pipedream / string.com temporarily unable to respond to chats
Pipedream: Major incident: string.com temporarily unable to respond to chats
Summary
Pipedream reported a major outage preventing string.com from responding to chats, starting 2026-10-05 17:58 UTC and resolved at 2026-10-05 18:32 UTC after 34 min. The vendor investigated an issue with its Anthropic account and confirmed chats were restored; all pipedream.com services and workflows were expected to be unaffected.
Machine-written from the diff below (Sol; type: incident outage). Check the diff before relying on it.
What changed
Before: not present
After: string.com temporarily unable to respond to chats
Before: not present
After: major
Before: not present
After: resolved
Before: not present
After: 2026-10-05 17:58 UTC
Before: not present
After: 2026-10-05 18:32 UTC
Before: not present
After: Frontend - Pipedream, Pipedream
Before: not present
After: We're investigating an issue with our Anthropic account that powers string.com chats. All pipedream.com services and workflows should be unaffected.
Before: not present
After: string.com chats are working, and service has been restored.
First version of this incident archived by Rewindex. View the live incident.
History of this incident
| When (UTC) | Change | Kind |
|---|---|---|
| Major incident: string.com temporarily unable to respond to chats (this change) Pipedream reported a major outage preventing string.com from responding to chats, starting 2026-10-05 17:58 UTC and resolved at 2026-10-05 18:32 UTC after 34 min. The vendor investigated an issue with its Anthropic account and confirmed chats were restored; all pipedream.com services and workflows were expected to be unaffected. | Major incident |
All Pipedream changes → · Pipedream profile · Markdown · JSON