# Pipedream: string.com temporarily unable to respond to chats

- Impact (vendor’s label): major
- Status: resolved
- Started: 2026-10-05 17:58 UTC · Resolved: 2026-10-05 18:32 UTC · Duration: 35 min
- Updates: 2 · Affected components: Frontend - Pipedream, Pipedream
- [Vendor status page: https://stspg.io/h6r53cjbc81n](https://stspg.io/h6r53cjbc81n)
- [Company: Pipedream](https://rewindex.com/company/pipedream.md)

## 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, sol)_
## Timeline of updates

- **investigating** 2026-10-05 17:58 UTC: We're investigating an issue with our Anthropic account that powers string.com chats. All pipedream.com services and workflows should be unaffected.
- **resolved** 2026-10-05 18:32 UTC: string.com chats are working, and service has been restored.

## Rewindex changes for this incident

- 2026-10-05 17:58 UTC: [Major incident: string.com temporarily unable to respond to chats](https://rewindex.com/change/icb75b2f50e24ef.md)


---
Canonical: https://rewindex.com/company/pipedream/incidents/zrdnyp32r0xd · Markdown: https://rewindex.com/company/pipedream/incidents/zrdnyp32r0xd.md · JSON: https://rewindex.com/api/v1/companies/pipedream/incidents/zrdnyp32r0xd · Generated 2026-10-18T11:30:27.674Z
