Pipefy incident
[Oracle Cloud / OCI] Third-Party Service Degradation
Pipefy experienced a minor incident on March 2, 2026 affecting Application, lasting 1d 13h. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- 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.