Companies / Pipedream / changes
Pipedream change history
| When (UTC) | Change | Kind |
|---|---|---|
| Major incident: string.com temporarily unable to respond to chats 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 | |
| Critical incident: Connect and HTTP Trigger issues Pipedream reported a critical incident affecting Connect API and HTTP event sources and workflows, starting at 2026-07-28 23:40 UTC. A fix was implemented by 2026-07-28 23:53 UTC, and the incident was resolved at 2026-07-28 23:59 UTC; the reported duration was 18 min. | Major incident | |
| Major incident: Building new Python code steps temporarily disabled Pipedream disabled editing and building new Python code steps in its UI due to a downstream AWS issue. The vendor rated the incident major; it started at 2026-05-01 03:53 UTC and was resolved at 2026-05-03 19:15 UTC, lasting 2 days 15 h. | Major incident | |
| Major incident: API services degraded Pipedream reported a major degradation of API services, with a listed start of 2026-04-09 17:47 UTC. The incident was marked resolved at 2026-04-07 17:30 UTC, before the listed start; duration is unknown, and no cause or fix was stated. | Major incident | |
| Major incident: Pipedream and Pipedream Connect Event Sources and Webhooks are failing Pipedream reported a major outage affecting Pipedream and Pipedream Connect Event Sources and Webhooks, disrupting HTTP event sources, HTTP workflows, destinations and Connect. It started at 2026-01-12 23:31 UTC and resolved at 2026-01-13 00:51 UTC, lasting 1 h 19 min. Pipedream implemented a fix but did not disclose the cause. | Major incident | |
| Major incident: Elevated workflow and source errors. Pipedream reported a major incident with elevated errors affecting HTTP workflows and event sources from 2025-09-16 17:56 UTC to 2025-09-16 19:09 UTC, lasting 1 h 13 min. A fix was implemented at 18:15 UTC, followed by monitoring and resolution. | Major incident | |
| Major incident: Timeouts on a small number for workflows Pipedream reported a major incident involving timeouts on a small number of workflows, affecting Email, HTTP and Timer workflow components and their backend counterparts. It started at 2025-08-09 15:43 UTC and was resolved at 2025-08-11 16:57 UTC, lasting 2 days 1 h; no cause or specific fix was stated. | Major incident | |
| Major incident: Elevated Error Rates | Major incident | |
| Major incident: Gateway timeouts in HTTP workflow executions | Major incident | |
| Major incident: Experiencing significant delay with HTTP event sources | Major incident | |
| Major incident: Event History inaccessible | Major incident | |
| Major incident: Degraded functionality for git-synced projects | Major incident | |
| Major incident: 502 Bad Gateway on pipedream.com | Major incident | |
| Critical incident: Pipedream API down, affecting https://pipedream.com | Major incident | |
| Major incident: v1 email sources not emitting events | Major incident | |
| Critical incident: HTTP Sources Outage | Major incident | |
| Major incident: Timer-based triggers not running | Major incident | |
| Critical incident: GitHub incident affecting Pipedream GitHub sync | Major incident | |
| Major incident: Package installation through npm yielding "Failed to fetch" errors | Major incident |