Pipedream

Affected: Pipedream

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: Anthropic (Claude).

1. 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.

2. resolved 2026-10-05 18:32 UTC

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

Excerpts are shortened. Read the full incident on Pipedream's status page.

Affected: Event Sources - HTTP, Workflows - HTTP

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-07-29 00:06 UTC

   The issue has been identified and a fix is being implemented.

2. monitoring 2026-07-29 00:22 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2026-07-29 00:34 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Pipedream's status page.

Affected: Event Sources - HTTP, Connect API, Workflows - HTTP

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-07-28 23:40 UTC

   We are currently investigating this issue.

2. monitoring 2026-07-28 23:53 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2026-07-28 23:59 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Pipedream's status page.

Affected: Event Sources - HTTP, Workflows - HTTP

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-07-14 17:45 UTC

   We are currently investigating this issue.

2. monitoring 2026-07-14 18:21 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2026-07-14 18:33 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Pipedream's status page.

Affected: Pipedream

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. investigating 2026-05-01 03:53 UTC

   We've disabled editing / building new Python code steps in the Pipedream UI due to a downstream AWS issue. We'll update this as soon as we hear more from AWS.

2. resolved 2026-05-03 19:15 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Pipedream's status page.

Affected: Event Sources - HTTP, Workflows - Timer, Workflows - HTTP, Event Sources - Timer

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-04-24 02:07 UTC

   We are currently investigating degraded performance for event sources and workflows.

2. resolved 2026-04-24 02:47 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Pipedream's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. resolved 2026-04-07 17:30 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Pipedream's status page.

Affected: REST API, Connect API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-02-24 00:39 UTC

   We are currently investigating this issue.

2. investigating 2026-02-24 00:45 UTC

   We are continuing to investigate this issue.

3. resolved 2026-02-24 00:45 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Pipedream's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-02-09 12:21 UTC

   We are currently investigating this issue.

2. identified 2026-02-09 13:08 UTC

   The issue has been identified and a fix is being implemented.

3. monitoring 2026-02-09 13:14 UTC

   A fix has been implemented and we are monitoring the results.

4. resolved 2026-02-09 17:35 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Pipedream's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-02-02 16:53 UTC

   We have identified that the Pipedream REST API is slightly degraded. We are currently working on a fix.

2. resolved 2026-02-02 21:08 UTC

   We have deployed a fix and are monitoring

Excerpts are shortened. Read the full incident on Pipedream's status page.

Affected: Event Sources - HTTP, Connect, Workflows - HTTP, Pipedream destinations

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-01-12 23:31 UTC

   We are currently investigating and will follow up once we identify the issue.

2. identified 2026-01-12 23:47 UTC

   We have identified the cause of the issues and are working on mitigating it.

3. monitoring 2026-01-13 00:50 UTC

   A fix has been implemented and we are monitoring the results.

4. resolved 2026-01-13 00:51 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Pipedream's status page.

Affected: Pipedream

Failure mode: Traffic surge or denial-of-service attack. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-11-19 13:15 UTC

   We are currently investigating this issue.

2. investigating 2025-11-19 13:45 UTC

   We are investigating instability with the Front End

3. resolved 2025-11-20 02:17 UTC

   Our front end services experienced unusual request patterns which led to degraded performance. We have updated our systems to address the issue and performance has returned to normal levels.

Excerpts are shortened. Read the full incident on Pipedream's status page.

Affected: REST API, Connect API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-11-04 15:53 UTC

   We are currently investigating this issue.

2. monitoring 2025-11-04 16:30 UTC

   Things have stabilized and we're continuing to monitor

3. resolved 2025-11-04 19:14 UTC

   root cause identified, Short term Mitigation efforts have been successful. Long term Mitigation solution has been identified and will be implemented as soon as the fix has passed our QA processes.

Excerpts are shortened. Read the full incident on Pipedream's status page.

Affected: Pipedream, Event Sources - HTTP, REST API, Connect, Workflows - Timer, Connect API, Workflows - HTTP, Event Sources - Timer, Pipedream destinations, Workflows - Email, GitHub Sync

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. investigating 2025-10-20 13:10 UTC

   We are seeing some HTTP triggers returning a 503 status and are investigating.

2. identified 2025-10-20 14:00 UTC

   These errors are due to our upstream provider (AWS) still having an ongoing outage.

3. identified 2025-10-20 16:11 UTC

   Multiple services are experiencing a service disruption as a result of a downstream provider (AWS). We are closely monitoring the status.

4. identified 2025-10-20 16:15 UTC

   We are continuing to work on a fix for this issue.

5. identified 2025-10-20 16:24 UTC

   Multiple services are experiencing a service disruption as a result of a downstream provider (AWS). We are closely monitoring the status.

6. identified 2025-10-20 20:05 UTC

   Some services are starting to come back online, some of the queued events are being processed.

7. monitoring 2025-10-20 21:51 UTC

   Event queues have caught up. We are continuing to monitor the platform.

8. resolved 2025-10-21 01:26 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Pipedream's status page.

Affected: Event Sources - HTTP, Workflows - HTTP

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-09-16 17:56 UTC

   We are currently investigating this issue.

2. monitoring 2025-09-16 18:15 UTC

   A fix has been implemented and we are monitoring the results.

3. monitoring 2025-09-16 19:09 UTC

   We are continuing to monitor for any further issues.

4. resolved 2025-09-16 19:09 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Pipedream's status page.

Affected: Connect, Connect API

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-09-02 16:38 UTC

   We are currently investigating this issue.

2. investigating 2025-09-02 16:40 UTC

   We are continuing to investigate this issue.

3. monitoring 2025-09-02 16:59 UTC

   Service has improved and is back to normal. We are monitoring the performance.

4. resolved 2025-09-02 18:32 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Pipedream's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-08-21 18:46 UTC

   The Discord integration isn't working properly. We are looking into it.

2. monitoring 2025-08-22 20:40 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2025-08-22 20:51 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Pipedream's status page.

Affected: Connect, Connect API

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2025-08-21 17:23 UTC

   We are currently investigating this issue.

2. identified 2025-08-21 18:53 UTC

   We have identified a latency issue with one of our downstream partner providers. We are currently evaluating ways to mitigate the effect.

3. resolved 2025-08-21 19:40 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Pipedream's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-08-15 23:40 UTC

   We are currently investigating this issue.

2. monitoring 2025-08-16 00:29 UTC

   Webhooks have caught up and we are monitoring.

3. resolved 2025-08-16 00:51 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Pipedream's status page.

Affected: Workflows - Timer, Workflows - HTTP, Workflows - Email

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-08-09 15:43 UTC

   We are currently investigating this issue.

2. resolved 2025-08-11 16:57 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Pipedream's status page.

Affected: Event Sources - HTTP

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-07-24 19:05 UTC

   We are currently investigating this issue.

2. monitoring 2025-07-24 19:17 UTC

   sources are no longer delayed and we are currently monitoring.

3. resolved 2025-07-24 19:31 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Pipedream's status page.

Affected: Connect, Connect API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-07-21 17:34 UTC

   We are currently investigating this issue.

2. investigating 2025-07-21 17:41 UTC

   Affected components: - Connect Component Configure - Connect Reload Props - Connect Run Action - Async options loading - Additional props loading - Step tests

3. identified 2025-07-21 17:42 UTC

   The issue has been identified and a fix is being implemented.

4. monitoring 2025-07-21 18:13 UTC

   A fix has been implemented and we are monitoring the results.

5. resolved 2025-07-21 19:35 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Pipedream's status page.

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-06-12 18:45 UTC

   We are currently investigating this issue.

2. monitoring 2025-06-12 19:28 UTC

   The systems are operating normally. We will continue monitoring the situation

3. resolved 2025-06-12 20:30 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Pipedream's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-06-03 16:24 UTC

   We are currently investigating this issue.

2. identified 2025-06-03 17:49 UTC

   The issue has been identified and a fix is being implemented.

3. monitoring 2025-06-03 17:51 UTC

   Connect Webhooks have now resumed their normal execution.

4. resolved 2025-06-03 19:32 UTC

   We are no longer seeing issues with Connect Webhooks. Triggers are executing normally once again.

Excerpts are shortened. Read the full incident on Pipedream's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2025-05-28 23:30 UTC

   Our data processing infrastructure is running behind which is causing delays for some Connect webhook triggers. No data has been lost and the system has caught up shortly.

Excerpts are shortened. Read the full incident on Pipedream's status page.

Affected: Pipedream, Event Sources - HTTP

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-05-27 08:00 UTC

   Some customers are reporting an issue with workflow triggers.

2. monitoring 2025-05-27 11:15 UTC

   The issue impacting workflow triggers appears to be resolved. Events are processing again and we are monitoring our systems to ensure that triggers continue working as expected.

3. resolved 2025-05-27 12:30 UTC

   We are no longer seeing issues with the impacted workflows and all workflows are properly running again.

Excerpts are shortened. Read the full incident on Pipedream's status page.

Affected: Event Sources - HTTP, REST API, Workflows - Timer, Workflows - HTTP, Event Sources - Timer, Workflows - Email

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-02-12 18:19 UTC

   We are currently investigating this issue.

2. monitoring 2025-02-12 18:20 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2025-02-12 19:36 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Pipedream's status page.

Affected: Event Sources - HTTP, Workflows - Timer, Workflows - HTTP, Event Sources - Timer

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-02-12 04:41 UTC

   We are currently investigating this issue.

2. resolved 2025-02-12 06:44 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Pipedream's status page.

Affected: Workflows - HTTP

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-01-24 15:30 UTC

   We are currently investigating this issue.

2. resolved 2025-01-24 17:37 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Pipedream's status page.

Affected: Dropbox

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2025-01-20 06:47 UTC

   The issue has been identified and a fix is being implemented.

2. resolved 2025-01-20 15:26 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Pipedream's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2024-11-19 19:29 UTC

   We are currently investigating this issue.

2. identified 2024-11-19 19:35 UTC

   The issue has been identified and a fix is being implemented.

3. monitoring 2024-11-19 19:53 UTC

   A fix has been implemented and we are monitoring the results.

4. resolved 2024-11-19 20:07 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Pipedream's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2024-11-05 13:54 UTC

   We are currently experiencing issues due to an outage on the Google Drive API. File uploads are being rejected and receiving HTTP 429 errors for all requests. We are monitoring the situation and will update once normal service is restored.

2. resolved 2024-11-05 19:48 UTC

   The issue with the Google Drive API (HTTP 429 errors) has been resolved. Google has restored normal service, and all file uploads through the API are now functioning correctly. We appreciate your patience during this outage.

Excerpts are shortened. Read the full incident on Pipedream's status page.

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2024-10-16 17:53 UTC

   We are currently investigating this issue.

2. investigating 2024-10-16 17:54 UTC

   We are continuing to investigate this issue.

3. identified 2024-10-16 18:18 UTC

   The backend service powering http events encountered an issue during maintenance failover. We're waiting for services to come back up.

4. monitoring 2024-10-16 18:27 UTC

   Services are back online. We'll continue monitoring.

5. resolved 2024-10-16 18:43 UTC

   Services are back up and events have caught up processing.

Excerpts are shortened. Read the full incident on Pipedream's status page.

Affected: Pipedream

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2024-08-30 17:15 UTC

   We've identified a bug that causes workflows to throw a 404 error. We're addressing and will update here when it's resolved.

2. resolved 2024-08-30 17:19 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Pipedream's status page.

Affected: Event Sources - HTTP, Event Sources - Timer

Failure mode: Traffic surge or denial-of-service attack. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2024-08-27 16:26 UTC

   We're seeing a spike in volume on event sources, leading to a delay in event processing. We're investigating and will post updates ASAP.

2. resolved 2024-08-27 16:35 UTC

   We've disabled the traffic source causing the spike, and delays are back to normal

Excerpts are shortened. Read the full incident on Pipedream's status page.

Affected: Pipedream

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2024-08-22 21:16 UTC

   The backend service powering the event history UI (https://pipedream.com/@/event-history) is down, we're working to recover it.

2. resolved 2024-08-23 00:37 UTC

   The event history UI is back, and events have caught up processing.

Excerpts are shortened. Read the full incident on Pipedream's status page.

Affected: GitHub Sync

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: GitHub.

1. monitoring 2024-08-14 23:50 UTC

   Syncing changes with GitHub is currently unavailable due to a downstream outage. See https://www.githubstatus.com/ for details. It is still possible to view and monitor events in GitHub synced projects. Workflow execution for synced projects is generally unaffected but workflows...

2. resolved 2024-08-15 00:29 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Pipedream's status page.

Failure mode: CDN or edge layer failed or served bad content. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2024-07-23 23:14 UTC

   We are currently investigating pipedream.com frontend returning a 502 error

2. resolved 2024-07-23 23:21 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Pipedream's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2024-07-12 20:31 UTC

   We are currently investigating an issue with Pipedream's integration with Google Drive and Google Sheets. We are receiving fewer webhooks from Google Drive and Google Sheets than expected. As a result, some users may experience delays with their workflows which use Google's...

2. monitoring 2024-07-13 07:07 UTC

   Google Drive sources seems to be recovering, and we are continuing to monitor Google Sheets sources.

3. resolved 2024-07-15 05:15 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Pipedream's status page.

Affected: Pipedream

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2024-04-05 23:26 UTC

   We're seeing elevated CPU on pipedream.com services, causing the service to return a 502 error.

2. resolved 2024-04-05 23:28 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Pipedream's status page.

Affected: REST API, Workflows - HTTP

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2024-03-05 21:25 UTC

   We've seen reports of some users failing to access Pipedream HTTP endpoints and the Pipedream API. We've isolated this to an issue with the Xfinity ISP and will post updates here as services become available.

2. resolved 2024-03-05 21:51 UTC

   The Xfinity outage has been resolved

Excerpts are shortened. Read the full incident on Pipedream's status page.

Affected: Pipedream, REST API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2024-02-03 22:42 UTC

   We are currently investigating this issue.

2. investigating 2024-02-03 22:43 UTC

   We are continuing to investigate this issue.

3. resolved 2024-02-03 22:47 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Pipedream's status page.

Affected: Workflows - Email

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2024-01-06 21:00 UTC

   Email sources tied to v1 workflows are failing to emit events. We're investigating.

2. resolved 2024-01-06 23:31 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Pipedream's status page.

Affected: Pipedream, Event Sources - HTTP, REST API, Workflows - Timer, Workflows - HTTP, Event Sources - Timer, Pipedream destinations, Workflows - Email, GitHub Sync

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2023-12-14 02:41 UTC

   We are experiencing timeouts from HTTP sources, and we're investigating the causes of them.

2. investigating 2023-12-14 02:51 UTC

   We identified a potential root cause for the downtime, and are working towards mitigating its impact. This will temporarily affect our website, public API, and platform, for a potentially short period.

3. investigating 2023-12-14 02:57 UTC

   We identified a potential root cause for the downtime, and are working towards mitigating its impact. This will temporarily affect our website, public API, and platform, for a potentially short period.

4. investigating 2023-12-14 03:03 UTC

   The issue has been identified and we were able to mitigate its impact to a good extent. We will continue monitoring the issue until its full resolution.

5. investigating 2023-12-14 03:05 UTC

   The issue has been identified and we were able to mitigate its impact to a good extent. We will continue monitoring the issue until its full resolution.

6. monitoring 2023-12-14 03:14 UTC

   At this moment, timer-based sources and workflows are degraded due to a backlog of events that still need to be processed. We will continue monitoring the situation until it comes back to normal.

7. resolved 2023-12-14 03:28 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Pipedream's status page.

Affected: Pipedream

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2023-11-08 14:31 UTC

   An upstream AI provider is having a major outage. A.I. code generation in Node.js code steps are affected.

2. resolved 2023-11-08 16:53 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Pipedream's status page.

Affected: Workflows - Timer, Event Sources - Timer

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2023-11-03 21:49 UTC

   Timer-based triggers — like the Scheduler trigger, and other app-based triggers that run on a schedule — stopped running around 21:30 UTC. Our team is investigating and will post updates here.

2. identified 2023-11-03 21:52 UTC

   We've reverted the code that introduced the bug. This also only affects v1 workflow triggers, not those using v2 (the latest version of workflows).

3. resolved 2023-11-03 22:00 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Pipedream's status page.

Affected: GitHub Sync

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: GitHub.

1. investigating 2023-11-03 19:06 UTC

   A GitHub incident (https://www.githubstatus.com/) is affecting our GitHub integration. When GitHub resolves this, we'll update you here.

2. resolved 2023-11-03 19:18 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Pipedream's status page.

Affected: npm Package installation

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2023-10-30 20:19 UTC

   We're seeing 500 errors reported from npm trying to install packages. You may see a "Failed to fetch" error when trying to test / deploy code steps that use third-party npm packages. We'll update this when the incident is resolved.

2. resolved 2023-10-30 20:44 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Pipedream's status page.

Affected: Pipedream destinations

Failure mode: A configuration change caused the failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. monitoring 2023-10-27 23:40 UTC

   S3 object delivery is delayed because of a bad configuration change. We've corrected the change. All objects sent to $.send.s3 have been retained, but delivery to the destination bucket will be delayed while we're recovering from the change.

2. resolved 2023-10-28 22:04 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Pipedream's status page.

Affected: Pipedream

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2023-10-13 11:08 UTC

   We are currently investigating this issue.

2. monitoring 2023-10-13 13:40 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2023-10-13 13:44 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Pipedream's status page.