Vendor Status Watch

← all vendors

Pipedream status history

Current state: operational — “All Systems Operational” per https://status.pipedream.com (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.

0incidents, last 30 days
3incidents, last 90 days
18incidents on record
Incidents per week, last 12 weeks:

How long do Pipedream incidents last?

96 minmedian incident duration18 measured
13.0 h90th percentile1 in 10 ran longer
73 minmedian, major/critical only5 incidents

From 18 incidents with a vendor-posted start and resolve time. Longest on record: Building new Python code steps temporarily disabled — 2.6 days (2026-05-01 03:53 UTC). Excluded, never estimated: nothing. Duration is the gap between the vendor's own posted timestamps — it is not measured downtime, uptime or an SLA figure, and a vendor that posts every blip will look worse here than one that posts nothing. Same rule as the outage-duration dataset.

Incidents on record (18)

StartedIncidentStatusImpactDuration
2026-07-29 00:06 UTCHTTP Triggers issuesresolvedminor28 min
2026-07-28 23:40 UTCConnect and HTTP Trigger issuesresolvedcritical18 min
2026-07-14 17:45 UTCDegraded performance for HTTP triggers and workflowsresolvedminor48 min
2026-05-01 03:53 UTCBuilding new Python code steps temporarily disabledresolvedmajor2 d 15 h
2026-04-24 02:07 UTCWorkflow executions failingresolvedminor39 min
2026-04-07 17:30 UTCAPI services degradedresolvedmajor0 min
2026-02-24 00:39 UTCAPI services degradedresolvedminor6 min
2026-02-09 12:21 UTCPipedream Event Source are Failingresolvednone5 h 14 min
2026-02-02 16:53 UTCPipedream REST API is degradedresolvednone4 h 14 min
2026-01-12 23:31 UTCPipedream and Pipedream Connect Event Sources and Webhooks are failingresolvedmajor1 h 19 min
2025-11-19 13:15 UTCFront End Instabilityresolvednone13 h 02 min
2025-11-04 15:53 UTCCurrently facing backend issuesresolvednone3 h 20 min
2025-10-20 13:10 UTCThe platform has recovered from a previous outage. We will continue to monitor.resolvednone12 h 15 min
2025-09-16 17:56 UTCElevated workflow and source errors.resolvedmajor1 h 13 min
2025-09-02 16:38 UTCDegraded service due to possible problems with Google Driveresolvedminor1 h 54 min
2025-08-21 18:46 UTCDiscord integrationresolvedminor26 h 04 min
2025-08-21 17:23 UTCConnect API Latencyresolvedminor2 h 17 min
2025-08-15 23:40 UTCConnect webhooks are delayedresolvednone1 h 10 min

Titles, statuses and impact levels are the vendor's own words. Durations marked approx. are inferred from the poll that first found the incident gone. Shows the latest 60; the JSON has everything we hold (up to 400 days).

Watch Pipedream with the template

Put this in config.json of your fork and add a WEBHOOK_URL secret:

{
  "vendors": [
    "pipedream"
  ],
  "format": "auto",
  "map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
  "unreachable_after": 3,
  "mute_maintenance": false
}