Pipefy Outage History
Pipefy is up right nowPingoru has recorded 78 incidents for Pipefy: 69 in the last 12 months and 12 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 1 | 19 of 720 (3%) |
| May 2026 | 12 | 8 of 744 (1%) |
| June 2026 | 3 | 0 of 720 (0%) |
| July 2026 | 2 | 2 of 744 (0%) |
| August 2026 | 2 | 5 of 744 (1%) |
| September 2026 | 3 | 3 of 720 (0%) |
| October 2026 | 7 | 4 of 590 (1%) |
Incidents, newest first
Notice March 30, 2026 Filters and search interfaces degradations 4h Dashboards, Filters
Started Mar 30, 2026, 12:53 PM UTC· resolved Mar 30, 2026, 04:53 PM UTC
- investigating Mar 31, 2026, 07:50 PM UTC
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.
- resolved Mar 31, 2026, 07:51 PM UTC
This incident has been resolved.
Minor March 6, 2026 Integrations failure 8m
Started Mar 06, 2026, 03:00 PM UTC· resolved Mar 06, 2026, 03:09 PM UTC
- investigating Mar 06, 2026, 03:08 PM UTC
We are currently investigating this issue.
- monitoring Mar 06, 2026, 03:08 PM UTC
A fix has been implemented and we are monitoring the results.
- monitoring Mar 06, 2026, 03:09 PM UTC
We are continuing to monitor for any further issues.
- resolved Mar 06, 2026, 03:09 PM UTC
This incident has been resolved.
- postmortem Mar 10, 2026, 09:10 PM UTC
**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.**
Notice March 4, 2026 Dashboards Outage 27m Dashboards
Started Mar 04, 2026, 09:23 PM UTC· resolved Mar 04, 2026, 09:50 PM UTC
- investigating Mar 04, 2026, 09:23 PM UTC
We are currently investigating this issue.
- investigating Mar 04, 2026, 09:23 PM UTC
We are continuing to investigate this issue.
- monitoring Mar 04, 2026, 09:45 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Mar 04, 2026, 09:50 PM UTC
This incident has been resolved.
Minor March 4, 2026 Third-party provider, Oracle Cloud (OCI) Platform Instability 21h 11m Application, Dashboards
Started Mar 04, 2026, 01:34 PM UTC· resolved Mar 05, 2026, 10:46 AM UTC
- investigating Mar 04, 2026, 01:34 PM UTC
We are currently investigating this issue.
- identified Mar 04, 2026, 01:54 PM UTC
Customers may notice that certain requests are taking longer than usual to process.
- identified Mar 04, 2026, 02:03 PM UTC
We identified the queue processing delays has been identified as an ongoing infrastructure issue on the side of our third-party provider, Oracle Cloud (OCI)
- identified Mar 04, 2026, 02:04 PM UTC
We identified the queue processing delays has been identified as an ongoing infrastructure issue on the side of our third-party provider, Oracle Cloud (OCI)
- identified Mar 04, 2026, 02:51 PM UTC
We are continuing to work on a fix for this issue.
- identified Mar 04, 2026, 03:04 PM UTC
Platform Instability We are currently experiencing platform instability affecting Pipefy. Our team has identified that the issue is related to a network problem in the Oracle Cloud Infrastructure (OCI) region where our servers are hosted. Due to this infrastructure issue, we are temporarily unable to allocate enough machines to keep our multi-tenant environment fully stable. As a result, some users may experience slowness or intermittent access to the platform. What we are doing: Our engineering team is actively working together with OCI to resolve the issue as quickly as possible. We are dedicating all necessary resources and efforts to restore full platform stability. Impact: Some customers may experience degraded performance or intermittent availability while the incident is ongoing. At this moment, there is no indication of data loss or data exposure. Next Steps: We will continue to monitor the situation closely and provide updates as progress is made. Once the incident is fully resolved, we will conduct a detailed Root Cause Analysis (RCA) and share the findings and preventive actions with our customers. We sincerely apologize for the disruption and appreciate your patience and understanding while we work to restore normal service. Next update: In 2 hours
- identified Mar 04, 2026, 05:01 PM UTC
Major update: Performance Improvement and Ongoing Monitoring We would like to share an update regarding the platform instability affecting Pipefy. Our engineering team has implemented mitigation measures that have significantly improved platform performance and stability. The service is currently operating in a more stable state compared to earlier during the incident. We continue to closely monitor the environment together with the third party to ensure stability is maintained and to quickly address any remaining impact. Current Status: Most platform functionalities should now be operating normally, although some users may still experience occasional performance fluctuations while we complete our monitoring and stabilization efforts. Data Integrity: There is no indication of data loss, exposure, or compromise. We will continue to monitor the situation and will provide another update once we confirm the platform is fully stable. Next update in 2 hours.
- identified Mar 04, 2026, 07:36 PM UTC
Major update: Performance Improvement and Ongoing Monitoring We would like to share an update regarding the platform instability affecting Pipefy. The service is currently operating in a more stable state now We continue to closely monitor the environment together with the third party to ensure stability is maintained and to quickly address any remaining impact. Current Status: Most platform functionalities should now be operating normally, while we complete our monitoring and stabilization efforts and waiting for the official update of our third party. We will continue to monitor the situation and will provide another update once we confirm the platform is fully stable. Follow the third party updates on: https://ocistatus.oraclecloud.com/#/incidents/ocid1.oraclecloudincident.oc1.phx.amaaaaaavwew44aahmtvmmxusawis4baxh73alctlnntgb3jtf2lakwtp27a
- monitoring Mar 04, 2026, 08:54 PM UTC
A fix has been implemented and we are monitoring the results.
- monitoring Mar 04, 2026, 09:13 PM UTC
We are continuing to monitor for any further issues.
- monitoring Mar 04, 2026, 09:14 PM UTC
We are continuing to monitor for any further issues.
- monitoring Mar 04, 2026, 09:23 PM UTC
We are continuing to monitor for any further issues.
- resolved Mar 05, 2026, 10:46 AM UTC
This incident has been resolved.
- postmortem Mar 13, 2026, 07:01 PM UTC
**Summary** On March 4, 2026, an incident occurred affecting multiple services in Oracle Cloud Infrastructure \(OCI\). Pipefy identified the disruption at 13:20 UTC, which impacted connectivity and service management operations for resources. As the Pipefy infrastructure relies on OCI, which affects the availability and normal behavior of certain platform functionalities for some customers. Oracle engineers investigated the issue, identified its source, and implemented mitigation actions. Full service functionality was confirmed as restored on March 4, 2026 at 19:40 UTC. Although Pipefy was back to normal at 19:40 UTC, we chose to wait for the provider to resolve the incident, which occurred on March 5, 2026 04:00am UTC . **Impact** During the incident window, customers have experienced intermittent latency or connection failures due to an underlying issue within the infrastructure. Because certain Pipefy components rely on OCI networking, services were temporarily degraded. We would like to emphasize that there was no loss or exposure of data. Full functionality was restored once the infrastructure issues were resolved. **Root Cause** The root cause of the incident was identified as an important and massive incident on Oracle's infrastructure that impacted the Pipefy platform. The disruption was caused by an issue affecting multiple Oracle Cloud Infrastructure \(OCI\) services, particularly involving components related to the Virtual Cloud Network \(VCN\). This issue affected the ability of services and resources to communicate reliably. The incident was triggered by OCI routine maintenance, the issue occurred because the Virtual Cloud Network Control Plane \(VCNCP\) was unable to propagate network configuration to the network dataplane services due to performance degradation of VCNCP’s internal database. At Pipefy, we identified the disruption at 13:20 UTC, this resulted in an inability to perform lifecycle actions, such as provisioning or scaling compute resources. Following that, OCI service teams were informed and the escalation process started. Oracle engineering teams identified the source of the disruption and implemented corrections to stabilize the affected infrastructure and restore normal connectivity and service operations for Pipefy on March 04 at 16:18 UTC, which resulted in full control plane recovery at OCI on March 05 at 04:40 UTC **Preventive Measures Performed** * To prevent this scenario from happening again, OCI implemented rigorous improvements to its infrastructure, such as migrating VCNCP services to hosts with greater memory capacity. \[Done\] * It also implemented performance optimizations in the VCNCP internal database, in addition to improvements in service monitoring. \[Done\] Next steps * Improvements in the monitoring and observability process of the Pipefy platform. **Additional informations** We would like to point out that all information regarding incidents will be available on our support tool, but we reiterate that official communication is done through our status page [https://status.pipefy.com](https://status.pipefy.com). We will continue to monitor the system closely to ensure stability and prevent future issues, while continuously working to enhance the customer experience.
Minor March 2, 2026 [Oracle Cloud / OCI] Third-Party Service Degradation 1d 13h Application
Started Mar 02, 2026, 10:00 PM UTC· resolved Mar 04, 2026, 11:47 AM UTC
- investigating Mar 03, 2026, 03:02 AM UTC
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.
- identified Mar 03, 2026, 03:03 AM UTC
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)
- monitoring Mar 03, 2026, 03:05 AM UTC
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
- resolved Mar 04, 2026, 11:47 AM UTC
This incident has been resolved.
- postmortem Mar 13, 2026, 07:25 PM UTC
**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.
Major February 25, 2026 Custom Integrations | Slowness when executing any action 1h 23m Integrations
Started Feb 25, 2026, 02:32 PM UTC· resolved Feb 25, 2026, 03:56 PM UTC
- investigating Feb 25, 2026, 02:32 PM UTC
We are currently investigating this issue.
- monitoring Feb 25, 2026, 02:50 PM UTC
A fix has been implemented and we are monitoring the results.
- monitoring Feb 25, 2026, 03:31 PM UTC
We are continuing to monitor for any further issues.
- resolved Feb 25, 2026, 03:56 PM UTC
This incident has been resolved.
- postmortem Mar 02, 2026, 09:14 PM UTC
**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.
Major February 14, 2026 Slowness in Pipefy functionalities 2h 6m Advanced Reports, Filters, Reports
Started Feb 14, 2026, 12:43 PM UTC· resolved Feb 14, 2026, 02:50 PM UTC
- identified Feb 14, 2026, 12:43 PM UTC
The issue has been identified and a fix is being implemented.
- monitoring Feb 14, 2026, 02:30 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Feb 14, 2026, 02:50 PM UTC
This incident has been resolved.
- postmortem Feb 24, 2026, 06:08 PM UTC
**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**
Notice February 12, 2026 Cards are not beeing created by the pipe email 2h 5m Email Inbox
Started Feb 12, 2026, 03:16 PM UTC· resolved Feb 12, 2026, 05:21 PM UTC
- investigating Feb 12, 2026, 03:16 PM UTC
Hello Pipefy customers! We've identified a slowdown in receiving emails for card creation; during our analysis, we determined the slowness was due to our email provider. A ticket has been opened with our partner, and we are working to resolve the issue as quickly as possible.
- identified Feb 12, 2026, 05:01 PM UTC
The issue has been identified and a fix is being implemented.
- resolved Feb 12, 2026, 05:21 PM UTC
This incident has been resolved.
- postmortem Feb 13, 2026, 08:01 PM UTC
**Summary:** **The issue at hand involved the inability to create cards via the pipe email in Pipefy. This was due to a rule on firewall provider that was inadvertently blocking incoming emails, which are essential for the automatic creation of cards.** **Impact:** **The impact of this issue was significant as it disrupted the workflow of users relying on email-triggered card creation. This could have led to delays in task management and project tracking, affecting overall productivity and efficiency for users who depend on this feature for seamless operations.** **Root Cause:** **The root cause of the problem was identified as a specific rule on Cloudflare that was blocking incoming emails. This blockage prevented the emails from reaching the system, thereby halting the automatic card creation process.** **Corrective Actions:** * **The team disabled the problematic rule on Cloudflare, which restored the normal flow of incoming emails and resumed the card creation process. - A ticket was opened with SendGrid to request a range of IP addresses to ensure smoother operations in the future. - An alert system is to be created to monitor the incoming emails from the SendGrid endpoint to prevent similar issues.** **Next Steps/Conclusion:** **We will continue to monitor the system closely to ensure stability and prevent future occurrences of similar issues. Our ongoing efforts are focused on enhancing the customer experience by ensuring that all features function seamlessly and efficiently.**
Critical January 28, 2026 Issues affecting AI Features (Analytics, Builder, and Assistant) 21m AI Assistant
Started Jan 28, 2026, 11:58 AM UTC· resolved Jan 28, 2026, 12:19 PM UTC
- investigating Jan 28, 2026, 11:58 AM UTC
We are currently investigating an issue that is causing downtime for our AI-powered tools, including AI Analytics, AI Builder, and the AI Assistant. Our engineering team is working to restore service as quickly as possible. We apologize for any inconvenience.
- identified Jan 28, 2026, 11:59 AM UTC
The root cause has been identified and we are currently deploying a resolution to fix the outages in our AI suite. We are monitoring the recovery of AI Analytics, AI Builder, and AI Assistant and expect services to return to normal shortly.
- resolved Jan 28, 2026, 12:19 PM UTC
We have successfully deployed a fix and confirmed that AI Analytics, AI Builder, and AI Assistant are fully operational. We will continue to monitor the performance for a short period to ensure ongoing stability. Thank you for sticking with us!
- postmortem Mar 10, 2026, 09:18 PM UTC
Summary: **The incident involved an outage affecting AI analytics, AI builder, and AI Assistant functionalities. Although the platform itself remained accessible, these specific AI applications experienced disruptions due to a configuration error.** Impact: **The outage impacted the AI-related functionalities within the platform, potentially affecting users who rely on AI analytics, AI builder, and AI Assistant for their operations. While the core platform was not down, the unavailability of these AI features could have hindered users' ability to perform tasks that depend on AI capabilities.** Root Cause: **The root cause of the issue was identified as an incorrect configuration in the SDK package, which led to the malfunction of the AI applications. This misconfiguration necessitated corrective actions to restore functionality.** Corrective Actions: * The issue with the SDK configuration was fixed. - Smoke tests on the SDK pipeline were enhanced to prevent similar issues in the future. - Initiated the process to invalidate the cache on the SDK. - Improvements were made to the rollback process to ensure quicker recovery in case of future incidents. Next Steps/Conclusion: **We will continue to monitor the system closely to ensure stability and prevent future issues. Our ongoing efforts are focused on enhancing the customer experience by ensuring the reliability and performance of our AI functionalities.**
Notice January 23, 2026 Send email Issues 4h 50m Email Messaging
Started Jan 23, 2026, 03:24 PM UTC· resolved Jan 23, 2026, 08:15 PM UTC
- investigating Jan 23, 2026, 03:24 PM UTC
We are currently investigating this issue.
- investigating Jan 23, 2026, 03:42 PM UTC
We identified that some emails are being blocked. We are working to resolve the issue.
- investigating Jan 23, 2026, 08:03 PM UTC
We are continuing to investigate this issue.
- resolved Jan 24, 2026, 06:16 PM UTC
This incident has been resolved.
Notice January 21, 2026 AI provider issue 9h 19m ABBYY
Started Jan 21, 2026, 09:22 PM UTC· resolved Jan 22, 2026, 06:41 AM UTC
- investigating Jan 21, 2026, 09:22 PM UTC
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/
- monitoring Jan 22, 2026, 03:03 AM UTC
A fix has been implemented and we are monitoring the results.
- resolved Jan 22, 2026, 06:41 AM UTC
This incident has been resolved.
Notice January 20, 2026 Issue with Ai Provider 9h 5m ABBYY
Started Jan 20, 2026, 05:52 PM UTC· resolved Jan 21, 2026, 02:57 AM UTC
- investigating Jan 20, 2026, 08:52 PM UTC
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/
- resolved Jan 21, 2026, 02:57 AM UTC
This incident has been resolved.
Major January 20, 2026 Users can't login 10m Authentication
Started Jan 20, 2026, 05:03 PM UTC· resolved Jan 20, 2026, 05:14 PM UTC
- investigating Jan 20, 2026, 05:03 PM UTC
We are currently investigating this issue.
- identified Jan 20, 2026, 05:04 PM UTC
The issue has been identified and a fix is being implemented.
- monitoring Jan 20, 2026, 05:08 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Jan 20, 2026, 05:14 PM UTC
This incident has been resolved.
- postmortem Jan 21, 2026, 06:21 PM UTC
**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.
Minor January 15, 2026 We identify an issue affect Filters and reports. 33m Filters, Reports
Started Jan 15, 2026, 01:55 PM UTC· resolved Jan 15, 2026, 02:28 PM UTC
- investigating Jan 15, 2026, 02:03 PM UTC
We are currently investigating this issue.
- monitoring Jan 15, 2026, 02:04 PM UTC
The issue was resolved and now we are monitoring the results.
- resolved Jan 15, 2026, 02:28 PM UTC
This incident has been resolved.
- postmortem Jan 20, 2026, 06:32 PM UTC
**Root Cause** We discovered an issue impacting filters and reports due to high memory usage in the database. The exact cause of the memory spike remains unidentified, prompting further investigation. **Resolution** The problem resolved itself without any manual intervention, and systems returned to normal operation. **Action Plan** We plan to enhance the reporting system to better monitor database performance. The team analyzed the situation and decided to optimize sorting methods to prevent future occurrences.
Minor January 13, 2026 Ipass - Save button disabled after completing all authentication fields 2h 22m
Started Jan 13, 2026, 05:40 PM UTC· resolved Jan 13, 2026, 08:03 PM UTC
- investigating Jan 13, 2026, 05:40 PM UTC
We are currently investigating this issue.
- identified Jan 13, 2026, 06:17 PM UTC
The issue has been identified and a fix is being implemented.
- resolved Jan 13, 2026, 08:03 PM UTC
This incident has been resolved.
- postmortem Jan 21, 2026, 06:33 PM UTC
**Root Cause** The issue was caused by a recent third party software update, which led to the save button being disabled even after all authentication fields were completed. We identified the problem and addressed it with a new version that includes the necessary bug fix. **Resolution** We resolved the issue by implementing a new software update that contains the required bug fix, ensuring that the save button functions correctly after all fields are filled. **Action Plan** We plan to enhance our testing pipeline to ensure it is fully updated and consider involving experienced users to test in a staging environment for better reliability.
Major January 9, 2026 Customer Service Platform is Experiencing Difficulties 1h 1m Intercom Chats and Posts
Started Jan 09, 2026, 07:51 PM UTC· resolved Jan 09, 2026, 08:52 PM UTC
- investigating Jan 09, 2026, 07:51 PM UTC
We are currently experiencing technical difficulties with our third party customer service platform, which may lead to delays in response times. Pipefy remains fully operational, with no impact on its core functionalities.
- resolved Jan 09, 2026, 08:52 PM UTC
This incident has been resolved.
Major January 9, 2026 Error when acessing Admin Panel 15m Application
Started Jan 09, 2026, 02:16 PM UTC· resolved Jan 09, 2026, 02:31 PM UTC
- investigating Jan 09, 2026, 02:16 PM UTC
There's currently an issue when trying to acess the admin panel. Users may find themselves unable to access it. We're currently investigating this issue.
- identified Jan 09, 2026, 02:17 PM UTC
The issue has been identified and a fix is being implemented.
- monitoring Jan 09, 2026, 02:31 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Jan 09, 2026, 02:31 PM UTC
This incident has been resolved.
- postmortem Jan 15, 2026, 05:57 PM UTC
**Root Cause** The admin panel was unavailable for all organizations due to an error during the deployment process. A manual step in the code migration was missed, leading to missing data and a front-end failure. **Resolution** The issue was resolved by rolling back the changes and re-executing the migrations with the help of the support team. A fix was implemented to address the problem. **Action Plan** Improvements will be made to the migration pipeline to prevent similar issues in the future.
Major January 9, 2026 Issue with Filters in Databases 12m Filters
Started Jan 09, 2026, 02:02 PM UTC· resolved Jan 09, 2026, 02:14 PM UTC
- investigating Jan 09, 2026, 02:02 PM UTC
We have identified an issue where some records might not be visible when searching with filters in databases.
- monitoring Jan 09, 2026, 02:02 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Jan 09, 2026, 02:14 PM UTC
This incident has been resolved.
- postmortem Jan 13, 2026, 05:22 PM UTC
**Root Cause** The issue was caused by a non-optimized query that struggled when handling more than 50 records, leading to problems in database searches. **Resolution** The problem was resolved by applying a revert to address the issue. **Action Plan** To prevent similar issues in the future, unit tests will be created to avoid this type of failure scenario.
Major December 19, 2025 Third party Cloudflare incident 1d Cloudflare
Started Dec 19, 2025, 03:21 PM UTC· resolved Dec 20, 2025, 03:36 PM UTC
- investigating Dec 19, 2025, 03:16 PM UTC
We are currently investigating this issue.
- investigating Dec 19, 2025, 03:21 PM UTC
More details about the issue on their status page: https://www.cloudflarestatus.com/
- investigating Dec 19, 2025, 03:25 PM UTC
Our provider is facing an incident, Cloudflare is investigating intermittent issues with network performance. More details follow on cloudflare Status Page: https://www.cloudflarestatus.com/
- investigating Dec 19, 2025, 05:22 PM UTC
Our provider are still investigating this issue. More details follow on cloudflare Status Page: https://www.cloudflarestatus.com/
- monitoring Dec 19, 2025, 06:28 PM UTC
Our provider has implemented a fix and now is under monitoring
- resolved Dec 20, 2025, 03:36 PM UTC
This incident has been resolved.
Minor December 18, 2025 Failure on personal acess token 32m
Started Dec 18, 2025, 03:00 PM UTC· resolved Dec 18, 2025, 03:33 PM UTC
- investigating Dec 18, 2025, 03:00 PM UTC
We identified that some personal acess token are experience some issue, we already working on this fix
- investigating Dec 18, 2025, 03:29 PM UTC
The team is working on script to running to the personal accounts that did not log in for the past 90 days
- resolved Dec 18, 2025, 03:33 PM UTC
This incident has been resolved.
- postmortem Dec 18, 2025, 08:32 PM UTC
**Root Cause** A critical incident occurred due to a strategic update aimed at resolving security issues related to email feature. This incident affected key processes, including Integrations and AI automations, leading to failures in customer workflows. **Resolution** To resolve the issue, the team had to reverse the changes and execute a script to restore user accounts. This action was necessary to ensure the stability and functionality of the affected users. **Action Plan** * Future actions include setting up alerts for agent requests and specific error codes * Understanding the limitations of current alerts to be more proactive on this scenarios * Improve tests scenarios for cacth error previously
Major December 18, 2025 Service Account Instability –
Started Dec 18, 2025, 12:54 PM UTC· resolved Dec 18, 2025, 12:54 PM UTC
- identified Dec 18, 2025, 11:55 AM UTC
The issue has been identified and a fix is being implemented.
- identified Dec 18, 2025, 12:27 PM UTC
We are continuing to work on a fix for this issue.
- identified Dec 18, 2025, 12:47 PM UTC
We are continuing to work on a fix for this issue.
- resolved Dec 18, 2025, 12:54 PM UTC
Pipefy's customers Today, December 18th, at 02:00 am until 10:00 am we had a critical incident that impacted some important processes such as integrations, agents 2.0, and AI automations. During this period, AI automations on customers flow failed and could impact critical processes. After the issue was detected, our team took the actions to resolve the problem, reducing customer impact. Incident period December 18th from 02:00 am to 10:00 am UTC -3 Impact All processes on integrations, agents 2.0, and AI automations were severely impacted. How to fix Due to this incident, some integrations did not work properly at that time and need some manual actions. A manually trigger in the Workato recipes is required, so things get back to work, as well as on the integrations configured in IPaaS. For AI automations, to ensure all processes run correctly, they must be initiated again. Conclusion We will continue to monitor the system closely to ensure stability and prevent future issues. We also inform that our team is working to identify the root cause and will communicate as soon as possible in our Statuspage. We totally understand the impact caused by the incident and are available for any questions or help.
- postmortem Dec 18, 2025, 07:17 PM UTC
**Root Cause** A critical incident occurred due to a strategic update aimed at resolving security issues related to email feature. This incident affected key processes, including Integrations and AI automations, leading to failures in customer workflows. **Resolution** To resolve the issue, the team had to reverse the changes and execute a script to restore user accounts. This action was necessary to ensure the stability and functionality of the affected users. **Action Plan** - Future actions include setting up alerts for agent requests and specific error codes - Understanding the limitations of current alerts to be more proactive on this scenarios - Improve tests scenarios for cacth error previously
Minor December 17, 2025 Platform Slowness 1h 5m Application
Started Dec 17, 2025, 07:15 PM UTC· resolved Dec 17, 2025, 08:21 PM UTC
- investigating Dec 17, 2025, 08:02 PM UTC
We are currently investigating this issue.
- monitoring Dec 17, 2025, 08:03 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Dec 17, 2025, 08:21 PM UTC
This incident has been resolved.
- postmortem Dec 22, 2025, 06:21 PM UTC
**Root Cause** An issue was detected with the system responsible for transferring data from our main database to another system. This was due to a temporary loss of connection, which caused delays in data processing. The system kept trying to reconnect until the issue was resolved, but this caused some delays in data. **Resolution** Fortunately, no data was lost during this incident. Once the connection was restored, all delayed data was successfully processed and updated in the system. **Action Plan**
Major December 10, 2025 Users cannot signup using Pipefy Mobile App 43m Mobile App
Started Dec 10, 2025, 03:53 PM UTC· resolved Dec 10, 2025, 04:37 PM UTC
- investigating Dec 10, 2025, 03:53 PM UTC
We are currently investigating this issue.
- identified Dec 10, 2025, 04:23 PM UTC
The issue has been identified and a fix is being implemented.
- resolved Dec 10, 2025, 04:37 PM UTC
This incident has been resolved.
- postmortem Dec 17, 2025, 05:43 PM UTC
**Root Cause** The issue was caused by users attempting to sign up with emails that are blacklisted, which led to failures during the account creation process. This behavior is expected in such scenarios. **Resolution** There were no specific resolution actions taken during the incident. **Action Plan** - We plan to create a fallback for customers in the user signup flow to prevent this scenario. - Improve internal communication to prevent similar tests issues in the future. - To create a mobile app deprecating communication to the customers
Major December 5, 2025 Third part Cloudflare incident 24m
Started Dec 05, 2025, 05:50 AM UTC· resolved Dec 05, 2025, 06:15 AM UTC
- investigating Dec 05, 2025, 12:02 PM UTC
We are currently investigating this issue.
- identified Dec 05, 2025, 12:03 PM UTC
We identified that multiple alerts were triggered due to an intermittent instability affecting Cloudflare’s edge network.
- resolved Dec 05, 2025, 12:07 PM UTC
This problem was resolved after third part interventions. Root cause will be share in the future post mortem
- postmortem Dec 09, 2025, 09:12 PM UTC
**Root Cause** The issue occurred because a change was made to only one part of a system element, but it needed to be applied to another part as well. This oversight led to a failure in loading the necessary data. **Resolution** The problem was resolved by reversing the previous change, which restored the system's ability to display the correct information. **Action Plan**
Minor December 3, 2025 Interfaces experiencing issues in displaying card data 1h 31m Application, Portals
Started Dec 03, 2025, 07:53 PM UTC· resolved Dec 03, 2025, 09:24 PM UTC
- identified Dec 03, 2025, 08:53 PM UTC
The issue has been identified and a fix is being implemented.
- resolved Dec 03, 2025, 09:24 PM UTC
This incident has been resolved.
- postmortem Dec 12, 2025, 05:02 PM UTC
**Summary:** The issue was identified as filtered data on interfaces not displaying the necessary information. This problem was isolated to a specific query that was not correctly applied across all necessary elements. **Impact:** The impact of this issue was that users were unable to view filtered data on interfaces as expected. This could have led to confusion and inefficiencies in workflow management, as users rely on accurate data presentation for decision-making and process execution. **Root Cause:** The root cause of the issue was a misapplied merge request \(MR\) that altered fragments in one part of an element but failed to apply the necessary changes to another part that utilized the same query for loading fields. This oversight resulted in the failure of data display. **Next Steps/Conclusion:** We will maintain vigilant monitoring of the system to ensure stability and prevent similar issues in the future. Our commitment to enhancing the customer experience remains a priority as we continuously improve our platform.