Pipefy status history
Current state: operational — “All Systems Operational” per https://status.pipefy.com (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.
How long do Pipefy incidents last?
From 12 incidents with a vendor-posted start and resolve time. Longest on record: (Integrations) Flow executions are experiencing delay on processing time — 4.5 h (2026-05-05 15:06 UTC). Excluded, never estimated: 13 resolved before started (vendor data error). 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 (25)
| Started | Incident | Status | Impact | Duration |
|---|---|---|---|---|
| 2026-08-26 20:27 UTC | Files are inaccessible in some cards | resolved | minor | 11 min |
| 2026-08-17 16:44 UTC | Outbound Email Blocked | resolved | minor | 4 h 23 min |
| 2026-07-16 18:52 UTC | Degraded Performance | resolved | minor | 4 min |
| 2026-07-08 20:24 UTC | Degraded Performance - AI Service Routing | resolved | minor | 1 h 51 min |
| 2026-06-15 20:45 UTC | Cards are not opening due to the missing "from_name" | resolved | minor | 1 min |
| 2026-06-15 20:07 UTC | Pipefy Core Slowness | resolved | minor | 16 min |
| 2026-06-03 20:38 UTC | Pipefy slowness | resolved | minor | 8 min |
| 2026-05-28 17:49 UTC | Integrations downtime | resolved | major | 1 min |
| 2026-05-28 16:41 UTC | The embedded start form iframe is not working | resolved | none | 18 min |
| 2026-05-19 20:08 UTC | Search and filters Slowness | resolved | minor | — |
| 2026-05-13 21:08 UTC | Automations Slowness | resolved | minor | 42 min |
| 2026-05-08 23:06 UTC | Application is down | resolved | critical | — |
| 2026-05-05 15:06 UTC | (Integrations) Flow executions are experiencing delay on processing time | resolved | none | 4 h 28 min |
| 2026-05-04 19:06 UTC | Integrations slowness | resolved | minor | 41 min |
| 2026-04-23 18:48 UTC | Pipefy App instability - Pipe & Card load instability | resolved | none | — |
| 2026-04-23 18:48 UTC | Degraded performance on app servers | resolved | none | — |
| 2026-04-23 18:48 UTC | Indexing server majer outage | resolved | none | — |
| 2026-04-23 18:48 UTC | Massive outage on app servers | resolved | none | — |
| 2026-04-23 18:48 UTC | Pipefy App instability - Pipe & Card load instability | resolved | none | — |
| 2026-04-23 18:48 UTC | Partial Outage | resolved | none | — |
| 2026-04-23 18:48 UTC | Degraded performance on app servers | resolved | none | — |
| 2026-04-23 18:48 UTC | Degraded performance on app servers | resolved | none | — |
| 2026-04-23 18:48 UTC | Database Problems | resolved | none | — |
| 2026-04-23 18:48 UTC | Major Incident detected | resolved | none | — |
| 2026-04-23 18:48 UTC | Application Instability | resolved | none | — |
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 Pipefy with the template
Put this in config.json of your fork and add a WEBHOOK_URL secret:
{
"vendors": [
"pipefy"
],
"format": "auto",
"map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
"unreachable_after": 3,
"mute_maintenance": false
}
