Pipedream Outage History

Pipedream is up right now

Pipedream had 34 outages in the last 2 years totaling 211h 19m of downtime — averaging 1.4 incidents per month.

There were 34 Pipedream outages since July 12, 2024 totaling 211h 19m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.pipedream.com

Major May 1, 2026

Building new Python code steps temporarily disabled

Detected by Pingoru
May 01, 2026, 03:53 AM UTC
Resolved
May 03, 2026, 07:15 PM UTC
Duration
2d 15h
Affected: Pipedream
Timeline · 2 updates
  1. investigating May 01, 2026, 03:53 AM 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 May 03, 2026, 07:15 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor April 24, 2026

Workflow executions failing

Detected by Pingoru
Apr 24, 2026, 02:07 AM UTC
Resolved
Apr 24, 2026, 02:47 AM UTC
Duration
39m
Affected: Event Sources - HTTPWorkflows - TimerWorkflows - HTTPEvent Sources - Timer
Timeline · 2 updates
  1. investigating Apr 24, 2026, 02:07 AM UTC

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

  2. resolved Apr 24, 2026, 02:47 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice February 9, 2026

Pipedream Event Source are Failing

Detected by Pingoru
Feb 09, 2026, 12:21 PM UTC
Resolved
Feb 09, 2026, 05:35 PM UTC
Duration
5h 14m
Timeline · 4 updates
  1. investigating Feb 09, 2026, 12:21 PM UTC

    We are currently investigating this issue.

  2. identified Feb 09, 2026, 01:08 PM UTC

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

  3. monitoring Feb 09, 2026, 01:14 PM UTC

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

  4. resolved Feb 09, 2026, 05:35 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice February 2, 2026

Pipedream REST API is degraded

Detected by Pingoru
Feb 02, 2026, 04:53 PM UTC
Resolved
Feb 02, 2026, 09:08 PM UTC
Duration
4h 14m
Timeline · 2 updates
  1. identified Feb 02, 2026, 04:53 PM UTC

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

  2. resolved Feb 02, 2026, 11:08 PM UTC

    We have deployed a fix and are monitoring

Read the full incident report →

Major January 12, 2026

Pipedream and Pipedream Connect Event Sources and Webhooks are failing

Detected by Pingoru
Jan 12, 2026, 11:31 PM UTC
Resolved
Jan 13, 2026, 12:51 AM UTC
Duration
1h 19m
Affected: Event Sources - HTTPConnectWorkflows - HTTPPipedream destinations
Timeline · 4 updates
  1. investigating Jan 12, 2026, 11:31 PM UTC

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

  2. identified Jan 12, 2026, 11:47 PM UTC

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

  3. monitoring Jan 13, 2026, 12:50 AM UTC

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

  4. resolved Jan 13, 2026, 12:51 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice November 19, 2025

Front End Instability

Detected by Pingoru
Nov 19, 2025, 01:15 PM UTC
Resolved
Nov 20, 2025, 02:17 AM UTC
Duration
13h 2m
Affected: Pipedream
Timeline · 3 updates
  1. investigating Nov 20, 2025, 02:03 AM UTC

    We are currently investigating this issue.

  2. investigating Nov 20, 2025, 02:03 AM UTC

    We are investigating instability with the Front End

  3. resolved Nov 20, 2025, 02:17 AM 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.

Read the full incident report →

Notice November 4, 2025

Currently facing backend issues

Detected by Pingoru
Nov 04, 2025, 03:53 PM UTC
Resolved
Nov 04, 2025, 07:14 PM UTC
Duration
3h 20m
Affected: REST APIConnect API
Timeline · 3 updates
  1. investigating Nov 04, 2025, 03:53 PM UTC

    We are currently investigating this issue.

  2. monitoring Nov 04, 2025, 04:30 PM UTC

    Things have stabilized and we're continuing to monitor

  3. resolved Nov 04, 2025, 07:14 PM 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.

Read the full incident report →

Notice October 20, 2025

The platform has recovered from a previous outage. We will continue to monitor.

Detected by Pingoru
Oct 20, 2025, 01:10 PM UTC
Resolved
Oct 21, 2025, 01:26 AM UTC
Duration
12h 15m
Affected: PipedreamEvent Sources - HTTPREST APIConnectWorkflows - TimerConnect APIWorkflows - HTTPEvent Sources - TimerPipedream destinationsWorkflows - EmailGitHub Sync
Timeline · 8 updates
  1. investigating Oct 20, 2025, 01:10 PM UTC

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

  2. identified Oct 20, 2025, 02:00 PM UTC

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

  3. identified Oct 20, 2025, 04:11 PM UTC

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

  4. identified Oct 20, 2025, 04:15 PM UTC

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

  5. identified Oct 20, 2025, 04:24 PM UTC

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

  6. identified Oct 20, 2025, 08:05 PM UTC

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

  7. monitoring Oct 20, 2025, 09:51 PM UTC

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

  8. resolved Oct 21, 2025, 01:26 AM UTC

    This incident has been resolved.

Read the full incident report →

Major September 16, 2025

Elevated workflow and source errors.

Detected by Pingoru
Sep 16, 2025, 05:56 PM UTC
Resolved
Sep 16, 2025, 07:09 PM UTC
Duration
1h 13m
Affected: Event Sources - HTTPWorkflows - HTTP
Timeline · 4 updates
  1. investigating Sep 16, 2025, 05:56 PM UTC

    We are currently investigating this issue.

  2. monitoring Sep 16, 2025, 06:15 PM UTC

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

  3. monitoring Sep 16, 2025, 07:09 PM UTC

    We are continuing to monitor for any further issues.

  4. resolved Sep 16, 2025, 07:09 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor September 2, 2025

Degraded service due to possible problems with Google Drive

Detected by Pingoru
Sep 02, 2025, 04:38 PM UTC
Resolved
Sep 02, 2025, 06:32 PM UTC
Duration
1h 54m
Affected: ConnectConnect API
Timeline · 4 updates
  1. investigating Sep 02, 2025, 04:38 PM UTC

    We are currently investigating this issue.

  2. investigating Sep 02, 2025, 04:40 PM UTC

    We are continuing to investigate this issue.

  3. monitoring Sep 02, 2025, 04:59 PM UTC

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

  4. resolved Sep 02, 2025, 06:32 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor August 21, 2025

Discord integration

Detected by Pingoru
Aug 21, 2025, 06:46 PM UTC
Resolved
Aug 22, 2025, 08:51 PM UTC
Duration
1d 2h
Timeline · 3 updates
  1. investigating Aug 22, 2025, 08:23 PM UTC

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

  2. monitoring Aug 22, 2025, 08:40 PM UTC

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

  3. resolved Aug 22, 2025, 08:51 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor August 21, 2025

Connect API Latency

Detected by Pingoru
Aug 21, 2025, 05:23 PM UTC
Resolved
Aug 21, 2025, 07:40 PM UTC
Duration
2h 17m
Affected: ConnectConnect API
Timeline · 3 updates
  1. investigating Aug 21, 2025, 05:23 PM UTC

    We are currently investigating this issue.

  2. identified Aug 21, 2025, 06:53 PM 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 Aug 21, 2025, 07:40 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice August 15, 2025

Connect webhooks are delayed

Detected by Pingoru
Aug 15, 2025, 11:40 PM UTC
Resolved
Aug 16, 2025, 12:51 AM UTC
Duration
1h 10m
Timeline · 3 updates
  1. investigating Aug 15, 2025, 11:40 PM UTC

    We are currently investigating this issue.

  2. monitoring Aug 16, 2025, 12:29 AM UTC

    Webhooks have caught up and we are monitoring.

  3. resolved Aug 16, 2025, 12:51 AM UTC

    This incident has been resolved.

Read the full incident report →

Major August 9, 2025

Timeouts on a small number for workflows

Detected by Pingoru
Aug 09, 2025, 03:43 PM UTC
Resolved
Aug 11, 2025, 04:57 PM UTC
Duration
2d 1h
Affected: Workflows - TimerWorkflows - HTTPWorkflows - Email
Timeline · 2 updates
  1. investigating Aug 11, 2025, 03:43 PM UTC

    We are currently investigating this issue.

  2. resolved Aug 11, 2025, 04:57 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice July 24, 2025

delayed sources

Detected by Pingoru
Jul 24, 2025, 07:05 PM UTC
Resolved
Jul 24, 2025, 07:31 PM UTC
Duration
25m
Affected: Event Sources - HTTP
Timeline · 3 updates
  1. investigating Jul 24, 2025, 07:05 PM UTC

    We are currently investigating this issue.

  2. monitoring Jul 24, 2025, 07:17 PM UTC

    sources are no longer delayed and we are currently monitoring.

  3. resolved Jul 24, 2025, 07:31 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor July 21, 2025

Elevated Latency Observed in Connect API

Detected by Pingoru
Jul 21, 2025, 05:34 PM UTC
Resolved
Jul 21, 2025, 07:35 PM UTC
Duration
2h
Affected: ConnectConnect API
Timeline · 5 updates
  1. investigating Jul 21, 2025, 05:34 PM UTC

    We are currently investigating this issue.

  2. investigating Jul 21, 2025, 05:41 PM UTC

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

  3. identified Jul 21, 2025, 06:03 PM UTC

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

  4. monitoring Jul 21, 2025, 06:13 PM UTC

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

  5. resolved Jul 21, 2025, 07:35 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice June 12, 2025

Experiencing degraded performance across authentication and deployments

Detected by Pingoru
Jun 12, 2025, 06:45 PM UTC
Resolved
Jun 12, 2025, 08:30 PM UTC
Duration
1h 44m
Timeline · 3 updates
  1. investigating Jun 12, 2025, 06:45 PM UTC

    We are currently investigating this issue.

  2. monitoring Jun 12, 2025, 07:28 PM UTC

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

  3. resolved Jun 12, 2025, 08:30 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor June 3, 2025

Some Connect Webhooks Experiencing Delays with Execution

Detected by Pingoru
Jun 03, 2025, 04:24 PM UTC
Resolved
Jun 03, 2025, 07:32 PM UTC
Duration
3h 8m
Timeline · 4 updates
  1. investigating Jun 03, 2025, 04:24 PM UTC

    We are currently investigating this issue.

  2. identified Jun 03, 2025, 05:49 PM UTC

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

  3. monitoring Jun 03, 2025, 05:51 PM UTC

    Connect Webhooks have now resumed their normal execution.

  4. resolved Jun 03, 2025, 07:32 PM UTC

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

Read the full incident report →

Notice May 28, 2025

Delayed Connect Webhook Trigger Emits

Detected by Pingoru
May 28, 2025, 11:30 PM UTC
Resolved
May 28, 2025, 11:30 PM UTC
Duration
—
Timeline · 1 update
  1. resolved Jun 03, 2025, 07:59 PM 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.

Read the full incident report →

Notice May 27, 2025

Some Workspaces Experiencing Delays with Trigger Execution

Detected by Pingoru
May 27, 2025, 08:00 AM UTC
Resolved
May 27, 2025, 12:30 PM UTC
Duration
4h 30m
Affected: PipedreamEvent Sources - HTTP
Timeline · 3 updates
  1. investigating May 27, 2025, 01:30 PM UTC

    Some customers are reporting an issue with workflow triggers.

  2. monitoring May 27, 2025, 01:55 PM 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 May 27, 2025, 08:16 PM UTC

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

Read the full incident report →

Notice February 12, 2025

Elevated timeouts and error rates

Detected by Pingoru
Feb 12, 2025, 06:19 PM UTC
Resolved
Feb 12, 2025, 07:36 PM UTC
Duration
1h 16m
Affected: Event Sources - HTTPREST APIWorkflows - TimerWorkflows - HTTPEvent Sources - TimerWorkflows - Email
Timeline · 3 updates
  1. investigating Feb 12, 2025, 06:19 PM UTC

    We are currently investigating this issue.

  2. monitoring Feb 12, 2025, 06:20 PM UTC

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

  3. resolved Feb 12, 2025, 07:36 PM UTC

    This incident has been resolved.

Read the full incident report →

Major February 12, 2025

Elevated Error Rates

Detected by Pingoru
Feb 12, 2025, 04:41 AM UTC
Resolved
Feb 12, 2025, 06:44 AM UTC
Duration
2h 2m
Affected: Event Sources - HTTPWorkflows - TimerWorkflows - HTTPEvent Sources - Timer
Timeline · 2 updates
  1. investigating Feb 12, 2025, 04:41 AM UTC

    We are currently investigating this issue.

  2. resolved Feb 12, 2025, 06:44 AM UTC

    This incident has been resolved.

Read the full incident report →

Major January 24, 2025

Gateway timeouts in HTTP workflow executions

Detected by Pingoru
Jan 24, 2025, 03:30 PM UTC
Resolved
Jan 24, 2025, 05:37 PM UTC
Duration
2h 7m
Affected: Workflows - HTTP
Timeline · 2 updates
  1. investigating Jan 24, 2025, 03:30 PM UTC

    We are currently investigating this issue.

  2. resolved Jan 24, 2025, 05:37 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor January 20, 2025

Dropbox Source Events Delayed

Detected by Pingoru
Jan 20, 2025, 06:47 AM UTC
Resolved
Jan 20, 2025, 03:26 PM UTC
Duration
8h 39m
Affected: Dropbox
Timeline · 2 updates
  1. identified Jan 20, 2025, 06:47 AM UTC

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

  2. resolved Jan 20, 2025, 03:26 PM UTC

    This incident has been resolved.

Read the full incident report →