Is Pipedream down?
Pipedream is up
Right now
No. No incidents reported.
Last checked (2026-10-10 07:16 UTC) from status.pipedream.com · every 180s
For agents
proceed
Proceed.
GET upbutler.com/status/pipedream/status.agent.json
MCP: upstream_status {"service":"pipedream"}
Workflows and managed auth for 2,000+ APIs, including Pipedream Connect for agents.
What Pipedream says
Operational
Taken as is from Pipedream's own status page API. Incident titles and component names below are theirs.
Open status.pipedream.comWhat UpButler measured
There is no keyless endpoint of Pipedream that says anything useful, so UpButler does not probe it. To check your own Pipedream account, add a monitor with your key: it is yours alone and catches what a shared probe cannot.
Pipedream components
80 operational
Frontend
- PipedreamOperational
Backend
- Event Sources - HTTPOperational
- Workflows - TimerOperational
- Workflows - HTTPOperational
- Event Sources - TimerOperational
- Pipedream destinationsOperational
- Workflows - EmailOperational
- GitHub SyncOperational
Public APIs
- REST APIOperational
- Connect APIOperational
Integrations
- TwitterOperational
- OCRSpaceOperational
- LeadfeederOperational
- LIME GoOperational
- eSignatures.ioOperational
- ServiceM8Operational
- FreeAgentOperational
- MagneticOperational
- Mojo HelpdeskOperational
- MoonClerkOperational
- MoskitOperational
- TotangoOperational
- NicereplyOperational
- NoticeableOperational
- MegaventoryOperational
- Pivotal TrackerOperational
- Planyo Online BookingOperational
- bit.ioOperational
- PointagramOperational
- ConfluenceOperational
- RecurlyOperational
- PDF.coOperational
- PractiTestOperational
- ProdPadOperational
- Raven ToolsOperational
- RepairShoprOperational
- RevOperational
- Riddle Quiz MakerOperational
- RollOperational
- SalesflareOperational
- SendicateOperational
- shipcloudOperational
- SimplesatOperational
- SmooveOperational
- SnappyOperational
- Akeneo (in testing)Operational
- ChannelAdvisorOperational
- StormboardOperational
- StreakOperational
- SurveybotOperational
- ConfectionOperational
- TeamgateOperational
- TemiOperational
- TextItOperational
- TimeCampOperational
- TimekitOperational
- TransFormOperational
- UnisenderOperational
- CloudBeesOperational
- WaiverForeverOperational
- HTML/CSS to ImageOperational
- WebinarGeekOperational
- Visitor QueueOperational
- Voodoo SMSOperational
- VoilaNorbertOperational
- WisePopsOperational
- WistiaOperational
- Woodpecker.coOperational
- Workbooks CRMOperational
- WorkstackOperational
- YanadoOperational
- YouCanBook.MeOperational
- Zonka FeedbackOperational
- quentnOperational
- Online Live SupportOperational
- SendbirdOperational
- BeekeeperOperational
- SifterOperational
Connect
- ConnectOperational
- npm Package installationOperational
Pipedream incidents, last 90 days
- 2026-07-13: no record
- 2026-07-14: no record
- 2026-07-15: no record
- 2026-07-16: no record
- 2026-07-17: no record
- 2026-07-18: no record
- 2026-07-19: no record
- 2026-07-20: no record
- 2026-07-21: no record
- 2026-07-22: no record
- 2026-07-23: no record
- 2026-07-24: no record
- 2026-07-25: no record
- 2026-07-26: no record
- 2026-07-27: no record
- 2026-07-28: no record
- 2026-07-29: no record
- 2026-07-30: no record
- 2026-07-31: no record
- 2026-08-01: no record
- 2026-08-02: no record
- 2026-08-03: no record
- 2026-08-04: no record
- 2026-08-05: no record
- 2026-08-06: no record
- 2026-08-07: no record
- 2026-08-08: no record
- 2026-08-09: no record
- 2026-08-10: no record
- 2026-08-11: no record
- 2026-08-12: no record
- 2026-08-13: no record
- 2026-08-14: no record
- 2026-08-15: no record
- 2026-08-16: no record
- 2026-08-17: no record
- 2026-08-18: no record
- 2026-08-19: no record
- 2026-08-20: no record
- 2026-08-21: no record
- 2026-08-22: no record
- 2026-08-23: no record
- 2026-08-24: no record
- 2026-08-25: no record
- 2026-08-26: no record
- 2026-08-27: no record
- 2026-08-28: no record
- 2026-08-29: no record
- 2026-08-30: no record
- 2026-08-31: no record
- 2026-09-01: no record
- 2026-09-02: no record
- 2026-09-03: no record
- 2026-09-04: no record
- 2026-09-05: no record
- 2026-09-06: no record
- 2026-09-07: no record
- 2026-09-08: no record
- 2026-09-09: no record
- 2026-09-10: no record
- 2026-09-11: no record
- 2026-09-12: no record
- 2026-09-13: no record
- 2026-09-14: no record
- 2026-09-15: no record
- 2026-09-16: no record
- 2026-09-17: no record
- 2026-09-18: no record
- 2026-09-19: no record
- 2026-09-20: no record
- 2026-09-21: no record
- 2026-09-22: no record
- 2026-09-23: no record
- 2026-09-24: no record
- 2026-09-25: no record
- 2026-09-26: no record
- 2026-09-27: no record
- 2026-09-28: no record
- 2026-09-29: no record
- 2026-09-30: no record
- 2026-10-01: no record
- 2026-10-02: no record
- 2026-10-03: no record
- 2026-10-04: no record
- 2026-10-05: major incident
- 2026-10-06: no incident reported
- 2026-10-07: no incident reported
- 2026-10-08: no incident reported
- 2026-10-09: no incident reported
- 2026-10-10: no incident reported
Each bar is a day, coloured by the worst incident Pipedream reported. It is their incident record, not a measurement of uptime.
- Incidents
- 1
- 1 major or critical
- Typical time to resolve
- —
- median, needs 3 incidents
- Nine in ten within
- —
- 90th percentile
- Longest
- 35 min
- record since 2026-10-05
| Started (UTC) | Incident | Impact | Lasted |
|---|---|---|---|
| string.com temporarily unable to respond to chats | major | 35 min |
Get alerted when Pipedream goes down
No account. One email when Pipedream reports an incident, one when it is over. You confirm the address first, and every email has a one-click unsubscribe.
Or follow the RSS feed. On UpButler? Add Pipedream as a dependency to route it to Slack, Teams or a webhook.
Status badge
Show Pipedream's current status in a README or an internal wiki. It updates by itself.
[](https://upbutler.com/status/pipedream)Tell your outage from Pipedream's
Declare that your project depends on Pipedream. When one of your monitors fails while Pipedream has an incident that began around the same time, UpButler tags your incident "likely upstream" with their incident linked, says so in the alert and the AI report, and tells your on-call agent not to change code.
npx upbutler init finds the dependency from your env var names and packages. The catalog, dependencies and upstream-aware incidents are on every plan, including Free.
# upbutler.yaml
dependencies:
- pipedreamcurl -s https://upbutler.com/status/pipedream/status.agent.json{
"schema": "upbutler.upstream-status/v1",
"service": "pipedream",
"verdict": "proceed",
"status": "operational",
"reason": "No incidents reported",
"retryAfterSec": null,
"incident": null,
"probe": null
}Questions
- Is Pipedream down right now?
- No. As of 2026-10-10 07:16 UTC, Pipedream is up. This page reads the status again every 3 minutes.
- Where does this status come from?
- From Pipedream's own status page API at https://status.pipedream.com. UpButler reads it once for everyone (not once per visitor) every 3 minutes with conditional requests, and shows it unchanged: incident titles and component names are Pipedream's words.
- Can I get an alert when Pipedream goes down?
- Yes, without an account: enter your email on this page, confirm the link we send, and you get one email when Pipedream reports an incident and one when it is over. There is also an RSS feed at https://upbutler.com/status/pipedream/feed.rss. Teams on UpButler can route the same alert to Slack, Teams or a webhook.
- How can my agent or app check Pipedream status?
- Fetch https://upbutler.com/status/pipedream/status.agent.json: a small JSON document with a verdict (proceed, retry, fallback or pause) and retryAfterSec. No key is needed. The same answer is an MCP tool, upstream_status {"service":"pipedream"}, on https://upbutler.com/mcp/public.
- How do I know whether an outage is mine or Pipedream's?
- Add "pipedream" to the dependencies of your UpButler workspace. When one of your monitors fails while Pipedream has an incident that began around the same time, your incident is tagged "likely upstream" with their incident linked, and your on-call agent is told not to change code.
Also check
UpButler is not affiliated with Pipedream. Status and incident text belong to Pipedream and are read from their public status source; the probe result is UpButler's own measurement.