Pipefy Outage History

55 incidents recorded over the last 365 days, 54 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 Pipefy status100.00% uptime history

Every Recorded Pipefy Incident

Pipefy incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Jan 1, 2027Integration Platform Transition**Hello Pipefy Customers!** **INFORMATIVE** As part of the evolution of Pipefy’s roadmap, we are beginning the transition of our integration infrastructure to the next version, which is now native to the Pipefy…59 minScheduled
Nov 4, 2026Login issuesThe incident has been resolved.12 minResolved
Oct 29, 2026Delays in automated actionsIncident resolved.-34542 minResolved
Oct 27, 2026iPaaS high latencyIncident resolved-19790 minResolved
Oct 26, 2026PipeUI navigation updateMaintenance has started53h 48mResolved
Oct 24, 2026Delay in scheduled automation processingThe incident has been resolved.1 minResolved
Oct 22, 2026default queue latency above 30s SLOWe’ve recovered the default Sidekiq queue and it has drained. The overload was driven by repeated field-condition save mutations (`Resolvers::FieldConditions::Save`) on a single customer pipe (`307245277`, Copa…1h 14mResolved
Oct 14, 2026Login request failures**Resolved:** The incident was resolved following the team's intervention.2 minResolved
Oct 14, 2026Trial outbound email accepted but not deliveredThe incident was resolved.22 minResolved
Oct 8, 2026Title: Modernization of Date and Time HandlingMaintenance has started372h 53mResolved
Oct 7, 2026Pipefy SlownessThe incident has been resolved.52 minResolved
Oct 5, 2026Title Integration Service Update To 0.92.1 VersionMaintenance has started2h 3mResolved
Oct 5, 2026Customer emails for Pipefy were delayedThe issue was resolved after a team intervention. The email delivery returned to normal.54 minResolved
Oct 1, 2026Automation failuresThe issue was resolved after applying a mitigation17 minResolved
Oct 1, 2026(Emergency) Platform MaintenanceMaintenance has started48 minResolved
Sep 29, 2026AI Agents could have degrated performance**All Systems Operational.**1h 33mResolved
Sep 28, 2026Usage stats are unstableUser Stats is working as expected and the service is back to normal1h 4mResolved
Sep 25, 2026Automations screen is not openingResolved The incident was resolved after the domain and the automations screen returned to normal15 minResolved
Sep 24, 2026Upgrade activepieces to version 0.91.2Maintenance has started100h 14mResolved
Sep 23, 2026Scheduled Maintenance Maintenance has started28h 48mResolved
Aug 27, 2026Planned Maintenance -Maintenance — Activepieces (iPaaS) Platform UpdateMaintenance has started107h 17mResolved
Aug 27, 2026Planned Maintenance -Maintenance — Activepieces (iPaaS) Platform UpdateMaintenance has started11h 33mResolved
Aug 26, 2026Files are inaccessible in some cardsThe incident was resolved11 minResolved
Aug 25, 2026Schedule Maintenance (iPaaS) Platform upgrade Active PiecesMaintenance has started31h 26mResolved
Aug 24, 2026Emergency Maintenance — Activepieces (iPaaS) Platform UpdateMaintenance has started2h 42mResolved
Aug 19, 2026Scheduled Maintenance — Scheduled Maintenance: Pipefy Website Database Service UpgradeMaintenance has started148h 48mResolved
Aug 17, 2026Outbound Email BlockedThe incident was resolved after the domain was unblocked by the provider.4h 23mResolved
Aug 14, 2026Scheduled Maintenance — Activepieces (iPaaS) Platform UpdateMaintenance has started148h 28mResolved
Aug 10, 2026Scheduled database infrastructure maintenanceMaintenance has started978h 33mResolved
Jul 31, 2026Scheduled Maintenance – AI Agents PlatformMaintenance has started379h 5mResolved
Jul 16, 2026Degraded Performance**Latest update** The incident has been resolved following mitigation by the team4 minResolved
Jul 8, 2026Degraded Performance - AI Service RoutingAI service Routing is working as expected and all AI services are back to normal.1h 51mResolved
Jun 15, 2026Cards are not opening due to the missing "from_name"The incident was resolved1 minResolved
Jun 15, 2026Pipefy Core SlownessThe incident was resolved16 minResolved
Jun 3, 2026Pipefy slownessThe incident was resolved8 minResolved
May 28, 2026Integrations downtimeThis incident has been resolved.1 minResolved
May 28, 2026The embedded start form iframe is not workingA fix was applied, and the incident was resolved.18 minResolved
May 19, 2026Search and filters SlownessThis incident has been resolved.-21 minResolved
May 13, 2026Automations Slowness**Root Cause** The issue was caused by an automation process that affected the system's performance. During this time, the speed of processing tasks was slower than usual, impacting the overall…42 minResolved
May 8, 2026Application is down**Root Cause** The issue was traced back to a firmware update in a database instance, which led to a failure in the system's ability to switch over to a backup. This caused the main application to go…-6 minResolved
May 5, 2026(Integrations) Flow executions are experiencing delay on processing timeThis incident was resolved after a fix being implemented4h 28mResolved
May 4, 2026Integrations slowness**Root Cause** The application experienced performance issues due to a spike in executing flows that affected the app's performance. During the investigation, an issue was identified, requiring a fix to resolve the…41 minResolved
Apr 23, 2026Pipefy App instability - Pipe & Card load instabilitySome new performance patches was applied during the monitoring period and we consider the incident resolved now. The app performance is back to an expected level and all operations are running normally. We…-4635659 minResolved
Apr 23, 2026Degraded performance on app serversThis incident has been resolved.-4484192 minResolved
Apr 23, 2026Indexing server majer outageAll data is restored and reindexed again in our Elastic Search. We are investigating whats happen in a post mortem meeting and find a better solution to prevent that it's happens again.-4489676 minResolved
Apr 23, 2026Massive outage on app serversThis incident has been resolved. Today at 1:58 PM (UTC) our monitoring service identified a failure to communicate with the Redis database service responsible for background jobs. At 2:00 PM (UTC) our team…-4540582 minResolved
Apr 23, 2026Pipefy App instability - Pipe & Card load instabilityThis incident has been resolved.-4569101 minResolved
Apr 23, 2026Partial OutageDuring a Redis migration our team identified a failure in HA, provided by our PaaS, which didn't run as expected. That failure occurred between 0:14 AM and 0:17 AM (UTC) and was promptly handled by our Ops Team.-4263514 minResolved
Apr 23, 2026Degraded performance on app serversThis incident has been resolved.-4288562 minResolved
Apr 23, 2026Degraded performance on app serversThis incident has been resolved.-4342922 minResolved
Apr 23, 2026Database ProblemsThe tests were successful and the system is working again. We are working to improving this script so that this problem does not happen again.-4451716 minResolved
Apr 23, 2026Major Incident detectedThis incident has been resolved.-4479734 minResolved
Apr 23, 2026Application InstabilityWe identify the problem, it happened because the gem [sequenced](https://github.com/derrickreimer/sequenced) that we use in our Ruby project locked the phase table, after that this process died and table stay…-4235314 minResolved
Apr 23, 2026Partial Provider OutageWe're monitoring our infrastructure for approximately 1 hour and everything looks ok. Heroku also closed their incident: https://status.heroku.com/incidents/1539-4204726 minResolved
Apr 23, 2026Partial OutageThis incident has been resolved.-4207973 minResolved

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 Pipefy 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 Pipefy 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 Pipefy 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 Pipefy outage in this window ran 40d 18h, against a mean recovery of 2d 14h. If you depend on Pipefy 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.