Status: Resolved This incident has been resolved. Affected components
 <ul>
 <li>Integrations (Operational)</li>
 </ul>

Integrations downtime

Status: Resolved A fix was applied, and the incident was resolved. Affected components
 <ul>
 <li>Public Form (Operational)</li>
 </ul>

The embedded start form iframe is not working

Status: Complete The scheduled maintenance has been completed.

Maintenance: OCI Cloud Provider Maintenance

Status: 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.

Automations Slowness

Status: Resolved This incident has been resolved. Affected components
 <ul>
 <li>Filters (Operational)</li>
 </ul>

Search and filters Slowness

Maintenance: Emergency OCI Provider Maintenance

Status: Scheduled Scheduled maintenance — infrastructure security upgrade

We are upgrading our production infrastructure to a newer version to meet enhanced security requirements and improve platform stability. The migration has been carefully planned, validated in advance, and includes an immediate rollback path.

Maintenance window: Sunday, 14 June 2026, 11:00 – 13:00 UTC (2 hours)

Expected impact: Total or partial unavailability may occur during the maintenance window.

Why we're doing this

• Moving to a newer infrastructure version strengthens our security posture and meets updated security requirements.
• The upgrade also improves platform security and stability.
• Internal database components are being updated in parallel for improved security and compatibility.

How we're minimizing risk

• The new environment has been fully built and validated ahead of the maintenance window.
• A live standby copy of the database has been running in the new environment for days, kept continuously in sync — and the previous database remains available, allowing us to roll back to it without any data loss if needed.
• An immediate rollback path is in place if anything unexpected occurs.

We appreciate your patience. For any questions, please get in touch with the support.

Maintenance: Scheduled maintenance — infrastructure security upgrade

Maintenance: Mandatory Infrastructure upgrade — Cache System

Status: 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.

Application is down

Status: Complete The scheduled maintenance has been completed. Affected components
 <ul>
 <li>Activities (Operational)</li>
 </ul>

Maintenance: Activities database maintenance

Status: Resolved 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

Integrations slowness

Status: Resolved This incident was resolved after a fix being implemented Affected components
 <ul>
 <li>Integrations (Operational)</li>
 </ul>

(Integrations) Flow executions are experiencing delay on processing time

Status: Complete The scheduled maintenance has been completed. Affected components
 <ul>
 <li>Automation (Operational)</li>
 </ul>

Maintenance: [Scheduled Maintenance] Enhancements to Pipefy Automations [HTTP Request] – April 13 to April 24

Status: Resolved 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

Custom Integrations/iPaaS : Rate Limiting Issues

Status: Resolved This incident has been resolved. Affected components
 <ul>
 <li>Filters (Operational)</li>
<li>Dashboards (Operational)</li>
 </ul>

Filters and search interfaces degradations

Status: 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.

[Oracle Cloud / OCI] Third-Party Service Degradation

Status: Resolved 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.

We will continue to monitor the system closely to ensure stability and prevent future issues, while continuously working to enhance the customer experience.

Third-party provider, Oracle Cloud (OCI) Platform Instability

Status: Resolved 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.

Issues affecting AI Features (Analytics, Builder, and Assistant)

Status: 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.

Integrations failure

Status: Resolved This incident has been resolved. Affected components
 <ul>
 <li>Dashboards (Operational)</li>
 </ul>

Dashboards Outage

Status: 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.

Is Pipefy down?

Pipefy status is UP

Lastest published events

Integrations downtime

The embedded start form iframe is not working

Maintenance: OCI Cloud Provider Maintenance

Pipefy Services, Components and Regions

Recent Pipefy events

Integrations downtime

The embedded start form iframe is not working

Maintenance: OCI Cloud Provider Maintenance

Automations Slowness

Search and filters Slowness

Maintenance: Emergency OCI Provider Maintenance

Get your FREE account now,
5 monitors included!

Is Pipefy down?

Pipefy status is UP

Lastest published events

Integrations downtime

The embedded start form iframe is not working

Maintenance: OCI Cloud Provider Maintenance

Pipefy Services, Components and Regions

Recent Pipefy events

Integrations downtime

The embedded start form iframe is not working

Maintenance: OCI Cloud Provider Maintenance

Automations Slowness

Search and filters Slowness

Maintenance: Emergency OCI Provider Maintenance

Get your FREE account now,5 monitors included!

Get your FREE account now,
5 monitors included!