Pipedream Outage History

13 incidents recorded over the last 365 days, 13 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.

Live Pipedream status100.00% uptime history

Every Recorded Pipedream Incident

Pipedream incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Nov 2, 2026Docs unavailableThis incident has been resolved.6 minResolved
Oct 5, 2026string.com temporarily unable to respond to chatsstring.com chats are working, and service has been restored.34 minResolved
Jul 29, 2026HTTP Triggers issuesThis incident has been resolved.28 minResolved
Jul 28, 2026Connect and HTTP Trigger issuesThis incident has been resolved.18 minResolved
Jul 14, 2026Degraded performance for HTTP triggers and workflowsThis incident has been resolved.48 minResolved
May 1, 2026Building new Python code steps temporarily disabledThis incident has been resolved.63h 22mResolved
Apr 24, 2026Workflow executions failingThis incident has been resolved.39 minResolved
Apr 9, 2026API services degradedThis incident has been resolved.-2897 minResolved
Feb 24, 2026API services degradedThis incident has been resolved.6 minResolved
Feb 9, 2026Pipedream Event Source are FailingThis incident has been resolved.5h 14mResolved
Feb 2, 2026Pipedream REST API is degradedWe have deployed a fix and are monitoring4h 14mResolved
Jan 12, 2026Pipedream and Pipedream Connect Event Sources and Webhooks are failingThis incident has been resolved.1h 19mResolved
Nov 19, 2025Front End InstabilityOur 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.13h 2mResolved

Hear about the next one while it is open

Everything above is a record written after the fact. We can email you when the next Pipedream incident opens instead, at the point where knowing still changes what you do.

Free, no password, no card. Unsubscribe in one click.

How to Read This Pipedream Incident Log

Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Pipedream acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.

Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.

The longest single Pipedream outage in this window ran 2d 15h, against a mean recovery of 7h 31m. If you depend on Pipedream in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.