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
Next steps
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.