Pipefy had 52 outages in the last 2 years totaling 120h 11m of downtime — averaging 2.1 incidents per month.
There were 52 Pipefy outages since September 22, 2025 totaling 120h 11m of downtime. Each is summarised below — incident details, duration, and resolution information.
We are investigating an issue affecting our primary AI endpoints (ABBY). To maintain availability and prevent disruptions to AI Agents, Assistants, and automations, traffic has been successfully rerouted to our secondary provider (OpenAI). Services remain operational
AI service Routing is working as expected and all AI services are back to normal.
We are currently investigating this issue.
This incident has been resolved.
The incident was resolved
We are currently investigating this issue.
We are monitoring the incident.
The incident was resolved
We are currently investigating this issue.
This incident has been resolved.
This incident has been resolved.
The issue has been resolved and we are now monitoring it.
The incident was resolved
We've spotted that something has gone wrong. We're currently investigating the issue, and will provide an update soon.
A fix was applied, and the incident was resolved.
The issue has been identified and a fix is being implemented.
This incident has been resolved.
We are currently investigating this issue.
This incident has been resolved.
**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 efficiency. **Resolution** The problematic automation was removed, which restored the system's performance back to its normal state, ensuring that operations could continue smoothly.
We are currently investigating this issue
The application is online, but users may still experience degraded performance or intermittent issues. Our engineering team is closely monitoring system health as we work towards full restoration
This incident has been resolved.
**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 down. **Resolution** The problem was resolved by starting the database on a new healthy instance, restoring the system's functionality. **Action Plan** - To prevent future occurrences, a manual switch-over will be performed before any instance restarts. - Additionally, a maintenance is scheduled for the system update to address the identified bug.
Dear customers, We are currently aware of an issue affecting a subset of our customers where iPaaS flow executions are experiencing longer-than-expected processing times. We want to be transparent: Your flows are running. The behavior some customers are noticing is a delay in the time it takes for each process to be picked up and started — once a run begins, it proceeds normally. Our engineering teams are actively investigating the root cause and working to restore standard processing times as quickly as possible. We do not have an ETA to share at this moment, but we are committed to keeping you informed as the situation evolves. If you have been impacted, no action is required on your end. We will provide updates in our Statuspage as they become available. We apologize for any inconvenience this may cause and appreciate your patience.
This incident was resolved after a fix being implemented
We are currently investigating this issue.
We are continuing to investigate this issue.
This incident has been resolved.
The issue has been identified and a fix is being implemented.
**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 problem permanently. **Resolution** A fix to address the issue was implemented in the application, ensuring the application's performance returned to normal. **Action Plan** The team will monitor new metrics in the scenario, to avoid the future impact
We have identified that a recent internal infrastructure update caused unexpected rate-limiting on our iPaaS platform, resulting in temporary delays or 429 errors in workflows for the custom integrations. Our Infrastructure team has identified the root cause and successfully applied a fix to restore normal traffic. We're closely monitoring the environment to ensure stability. Normal service operation is expected across all affected organizations.
This incident has been resolved. Additional information will be provided shortly in our postmortem report.
**Root Cause** Recently, efforts were made to separate the infrastructure for better handling of increased demand. This led to the failure of previously set exception rules. An update was applied to a specific host or domain without verifying its use in the integration, causing issues. **Resolution** The issue was resolved by modifying the configuration rules on Ipass app. **Action Plan** - An anomaly alert will be created for the Ipass to avoid this scenario happend again in the future
On March 30th, the platform experienced a degradation that impacted filter and search applications. This incident was opened retroactively to provide visibility to customers. The problem is no longer occurring at the moment. Thank you for your understanding.
This incident has been resolved.
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
We are continuing to monitor for any further issues.
This incident has been resolved.
**Root Cause** The issue was caused by a failure in the integration feature, which led to an overload in the system. An unoptimized job created thousands of subflows, quickly filling up memory and affecting system availability. The misuse of the integration was identified as the root cause, prompting the disabling of the problematic flow as an initial step to mitigate the issue. **Resolution** To resolve the issue, the team deactivated the problematic flow and partially cleared the queues. This initial solution aimed to prevent new calls and address the items stuck in the queue. **Action Plan** **We will continue to monitor the system closely to ensure stability and prevent future issues. Our focus remains on continuously improving the customer experience by optimizing our processes and enhancing communication between teams.**
We are currently investigating this issue.
We are continuing to investigate this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating an issue causing degraded performance and slowness in services that require background queues. Customers may notice that certain requests are taking longer than usual to process.
The root cause of the queue processing delays has been identified as an ongoing infrastructure issue on the side of our third-party provider, Oracle Cloud (OCI)
We are currently monitoring the services to ensure full stability as the backlog of requests clears up. Please note that some intermittent slowness might still be experienced until all queued tasks are fully processed
This incident has been resolved.
**Root Cause** The incident was caused by a cloud provider's routine maintenance which led to a problem with the network control system. This issue prevented the network from updating its configuration due to a slowdown in the internal database. Despite this, the Pipefy platform's performance remained unaffected. **Resolution** The incident was resolved after a series of actions were taken by a cloud provider’s team, which closed the issue.
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
We are continuing to monitor for any further issues.
This incident has been resolved.
**Root Cause** The issue was caused by exceeding the execution limit in integration queues, leading to a loop in automation that triggered numerous webhooks. This resulted in an overload of a specific flow, creating a large processing queue. Consequently, clients experienced delays in their process executions. **Resolution** To resolve the issue, the customer service account was deactivated, which helped alleviate the problem. **Action Plan** To prevent future occurrences, a rate limit will be activated on the system, and the timeout for execution flows will be reduced.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
**Root Cause** We encountered a significant delay due to a high volume of card deletions, which affected the processing queues. **Resolution** The issue with the queues resolved itself without any intervention from the team. The system returned to normal operations on its own with the team supervision. **Action Plan**
We are currently investigating this issue.
We identified that some emails are being blocked. We are working to resolve the issue.
We are continuing to investigate this issue.
This incident has been resolved.
We are informing you that an intability is occurring with our AI provider. Impact: Customers may experience slow document analysis by AI. The AI provider is already working on it. For more information, please follow the status page of our partner available at: https://status.abbyy.com/
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are informing you that an intability is occurring with our AI provider. Impact: Customers may experience slow document analysis by AI. The AI provider is already working on it. For more information, please follow the status page of our partner available at: https://status.abbyy.com/
This incident has been resolved.
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
**Root Cause** A sudden surge in login requests led to a failure due to the limited number of available connections for authentication. This caused users to be unable to log in, although those already logged in were not affected. **Resolution** The issue was resolved by rolling out the application after detecting a database failover. This action restored the system's functionality and allowed users to log in again. **Action Plan** We plan to set up alerts for database connections. Monitoring of connection pools will be enhanced. The security team is keeping an eye on suspicious login IP addresses to block them if necessary.