# Pipedream change history Filter: kind=all. Query: `?kind=notable|all|pages|pricing|trust|legal|incident|incident_edit|incident_deleted|incident_update&history=&page=N`. Company profile: [Pipedream](https://rewindex.com/company/pipedream.md) ## Changes by kind | Kind | Changes | Notable | Latest (UTC) | | --- | --- | --- | --- | | Major incident | 19 | 19 | 2026-10-05 17:58 UTC | ## Timeline | When (UTC) | Kind | Change | Label | Summary | | --- | --- | --- | --- | --- | | 2026-10-05 17:58 UTC | Major incident | [Major incident: string.com temporarily unable to respond to chats](https://rewindex.com/change/icb75b2f50e24ef.md) | outage | 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. | | 2026-07-28 23:40 UTC | Major incident | [Critical incident: Connect and HTTP Trigger issues](https://rewindex.com/change/ie6c12f564db721.md) | outage | 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. | | 2026-05-01 03:53 UTC | Major incident | [Major incident: Building new Python code steps temporarily disabled](https://rewindex.com/change/i962e0decee3680.md) | outage | 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. | | 2026-04-09 17:47 UTC | Major incident | [Major incident: API services degraded](https://rewindex.com/change/i67aec26362d99c.md) | degradation | 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. | | 2026-01-12 23:31 UTC | Major incident | [Major incident: Pipedream and Pipedream Connect Event Sources and Webhooks are failing](https://rewindex.com/change/i6458b6f78077ab.md) | outage | 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. | | 2025-09-16 17:56 UTC | Major incident | [Major incident: Elevated workflow and source errors.](https://rewindex.com/change/i1fafacf3dda8b8.md) | outage | 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. | | 2025-08-09 15:43 UTC | Major incident | [Major incident: Timeouts on a small number for workflows](https://rewindex.com/change/i7da52f9d5fdcb0.md) | degradation | 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. | | 2025-02-12 04:41 UTC | Major incident | [Major incident: Elevated Error Rates](https://rewindex.com/change/i0064021ec208ba.md) | outage | Pipedream reported major elevated error rates affecting HTTP and Timer event sources and workflows, including backend components. The incident started at 2025-02-12 04:41 UTC and was resolved at 2025-02-12 06:44 UTC, lasting 2 h 2 min; no cause or specific fix was stated. | | 2025-01-24 15:30 UTC | Major incident | [Major incident: Gateway timeouts in HTTP workflow executions](https://rewindex.com/change/i155b41c1463c95.md) | outage | Pipedream reported a major incident causing gateway timeouts in HTTP workflow executions, affecting Backend - Workflows - HTTP and Workflows - HTTP. It started at 2025-01-24 15:30 UTC and was resolved at 2025-01-24 17:37 UTC, lasting 2 h 7 min; no cause or specific fix was stated. | | 2024-10-16 17:53 UTC | Major incident | [Major incident: Experiencing significant delay with HTTP event sources](https://rewindex.com/change/i22191d871ac6b1.md) | degradation | Pipedream reported a major degradation causing significant delays with HTTP event sources, starting 2024-10-16 17:53 UTC and resolved at 2024-10-16 18:43 UTC (49 min). The backend service powering HTTP events encountered an issue during maintenance failover; services returned online and event processing caught up. | | 2024-08-22 21:16 UTC | Major incident | [Major incident: Event History inaccessible](https://rewindex.com/change/i2ad74aa1c39cbc.md) | outage | Pipedream reported a major outage of Event History starting 2024-08-22 21:16 UTC, leaving the event history UI inaccessible because its backend service was down. The incident lasted 3 h 20 min and was resolved at 2024-08-23 00:37 UTC, when the UI was restored and events had caught up processing. | | 2024-08-14 23:50 UTC | Major incident | [Major incident: Degraded functionality for git-synced projects](https://rewindex.com/change/i2c27f7feab83e1.md) | outage | Pipedream reported a major GitHub Sync outage starting 2024-08-14 23:50 UTC, resolved at 2024-08-15 00:29 UTC after 39 min. GitHub syncing was unavailable due to a downstream outage; event viewing and monitoring remained available, and workflow execution was generally unaffected, though workflows relying on GitHub webhooks or APIs could be affected. | | 2024-04-05 23:26 UTC | Major incident | [Major incident: 502 Bad Gateway on pipedream.com](https://rewindex.com/change/ic2715c7ef682a6.md) | outage | Pipedream reported a major outage affecting pipedream.com, with elevated CPU causing 502 errors. It started at 2024-04-05 23:26 UTC and was resolved at 2024-04-05 23:28 UTC, lasting 2 min. | | 2024-02-03 22:42 UTC | Major incident | [Critical incident: Pipedream API down, affecting https://pipedream.com](https://rewindex.com/change/i10fe9a871e39b7.md) | outage | Pipedream reported a critical API outage affecting https://pipedream.com and the REST API, starting at 2024-02-03 22:42 UTC. The incident lasted 4 min and was resolved at 2024-02-03 22:47 UTC; no cause or fix was stated. | | 2024-01-06 21:00 UTC | Major incident | [Major incident: v1 email sources not emitting events](https://rewindex.com/change/i10f84c341c1e48.md) | outage | Email sources tied to Pipedream v1 workflows failed to emit events, affecting email-triggered workflows. The vendor rated the incident major; it started at 2024-01-06 21:00 UTC and was resolved at 2024-01-06 23:31 UTC, with a reported duration of 2 h 30 min. No cause or fix was stated. | | 2023-12-14 03:05 UTC | Major incident | [Critical incident: HTTP Sources Outage](https://rewindex.com/change/i7cf806f4146d89.md) | outage | Pipedream reported a critical outage involving HTTP source timeouts, with temporary impact to its website, public API and platform; timer-based sources and workflows were later degraded by an event backlog. The incident started at 2023-12-14 03:05 UTC and was resolved at 2023-12-14 03:28 UTC, lasting 22 min; Pipedream reported mitigation but did not specify the root cause. | | 2023-11-03 21:49 UTC | Major incident | [Major incident: Timer-based triggers not running](https://rewindex.com/change/icb2a3c77139d3a.md) | outage | Timer-based triggers, including Scheduler and scheduled app triggers, stopped around 21:30 UTC, affecting v1 workflows but not v2. Pipedream classified the outage as major, logged its start at 2023-11-03 21:49 UTC, and resolved it at 2023-11-03 22:00 UTC (computed duration: 10 min) after reverting code that introduced the bug. | | 2023-11-03 19:06 UTC | Major incident | [Critical incident: GitHub incident affecting Pipedream GitHub sync](https://rewindex.com/change/id85964e2c58013.md) | outage | Pipedream reported a critical incident affecting its GitHub integration and GitHub Sync, attributed to a GitHub incident. It started at 2023-11-03 19:06 UTC and was resolved at 2023-11-03 19:18 UTC, with a reported duration of 11 min. | | 2023-10-30 20:19 UTC | Major incident | [Major incident: Package installation through npm yielding "Failed to fetch" errors](https://rewindex.com/change/id8f6893fdbac40.md) | outage | Pipedream reported a major incident affecting npm package installation: 500 errors could cause "Failed to fetch" errors when testing or deploying code steps using third-party npm packages. It started at 2023-10-30 20:19 UTC and was resolved at 2023-10-30 20:44 UTC, lasting 25 min; no cause or fix was stated. | --- Canonical: https://rewindex.com/company/pipedream/changes · Markdown: https://rewindex.com/company/pipedream/changes.md · JSON: https://rewindex.com/api/v1/companies/pipedream/changes · Generated 2026-10-18T02:24:29.142Z