Search

Companies / Pipedream / incidents

Pipedream: Spike in Pipedream Internal Errors for workflows

Impact: majorStatus: resolvedStarted Resolved (5.0 h)1 updateSource: status.pipedream.com (opens in new tab)

Timeline of updates

  1. resolved

    All systems are operational. Incoming events should be processed successfully. We've also processed the backlog of events that arrived during the first part of the incident, from ~1:00am UTC to 3:51 UTC. From 3:51 AM UTC to 6:04 AM, we had to disable incoming events due to some of the load issues we were experiencing. Events sent during this time may be retried by the source services. At 6:04am, we re-enabled the collection of incoming events again. We'll follow up with a detailed retrospective of this incident as soon as possible.

From Pipedream’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.

Impact, status and times are the vendor’s own, as last archived. View on status.pipedream.com (opens in new tab). Pipedream profile · Recent Pipedream incidents · Markdown · JSON