# Pipedream: Spike in Pipedream Internal Errors for workflows

- Impact (vendor’s label): major
- Status: resolved
- Started: 2023-02-14 02:04 UTC · Resolved: 2023-02-14 07:06 UTC · Duration: 5.0 h
- Updates: 1
- [Vendor status page: https://status.pipedream.com/incidents/rwlhwg15mcf3](https://status.pipedream.com/incidents/rwlhwg15mcf3)
- [Company: Pipedream](https://rewindex.com/company/pipedream.md)

## Timeline of updates

- **resolved** 2023-02-14 07:06 UTC: 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 the vendor’s published history: only the final update text is available for incidents before Rewindex began polling this page._


---
Canonical: https://rewindex.com/company/pipedream/incidents/rwlhwg15mcf3 · Markdown: https://rewindex.com/company/pipedream/incidents/rwlhwg15mcf3.md · JSON: https://rewindex.com/api/v1/companies/pipedream/incidents/rwlhwg15mcf3 · Generated 2026-10-18T11:27:20.645Z