Resolved -
This incident has been resolved.
Mar 5, 10:46 UTC
Update -
We are continuing to monitor for any further issues.
Mar 4, 21:23 UTC
Update -
We are continuing to monitor for any further issues.
Mar 4, 21:14 UTC
Update -
We are continuing to monitor for any further issues.
Mar 4, 21:13 UTC
Monitoring -
A fix has been implemented and we are monitoring the results.
Mar 4, 20:54 UTC
Update -
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
Mar 4, 19:36 UTC
Update -
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.
Mar 4, 17:01 UTC
Update -
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
Mar 4, 15:04 UTC
Update -
We are continuing to work on a fix for this issue.
Mar 4, 14:51 UTC
Update -
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)
Mar 4, 14:04 UTC
Update -
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)
Mar 4, 14:03 UTC
Identified -
Customers may notice that certain requests are taking longer than usual to process.
Mar 4, 13:54 UTC
Investigating -
We are currently investigating this issue.
Mar 4, 13:34 UTC