https://approjects-vendor-status-watch.static.hf.space/v/pipefy.htmlIncidents from Pipefy's public status page, polled daily.Wed, 16 Sep 2026 12:28:20 +0000https://status.pipefy.compipefy:2026-08-26T20:27:46ZWed, 26 Aug 2026 20:27:46 +0000The incident was resolvedhttps://status.pipefy.compipefy:2026-08-17T16:44:09ZMon, 17 Aug 2026 16:44:09 +0000The incident was resolved after the domain was unblocked by the provider.https://status.pipefy.compipefy:2026-07-16T18:52:16ZThu, 16 Jul 2026 18:52:16 +0000**Latest update** The incident has been resolved following mitigation by the teamhttps://status.pipefy.compipefy:2026-07-08T20:24:43ZWed, 08 Jul 2026 20:24:43 +0000AI service Routing is working as expected and all AI services are back to normal.https://status.pipefy.compipefy:2026-06-15T20:45:34ZMon, 15 Jun 2026 20:45:34 +0000The incident was resolvedhttps://status.pipefy.compipefy:2026-06-15T20:07:21ZMon, 15 Jun 2026 20:07:21 +0000The incident was resolvedhttps://status.pipefy.compipefy:2026-06-03T20:38:50ZWed, 03 Jun 2026 20:38:50 +0000The incident was resolvedhttps://status.pipefy.compipefy:2026-05-28T17:49:46ZThu, 28 May 2026 17:49:46 +0000This incident has been resolved.https://status.pipefy.compipefy:2026-05-28T16:41:53ZThu, 28 May 2026 16:41:53 +0000A fix was applied, and the incident was resolved.https://status.pipefy.compipefy:2026-05-19T20:08:38ZTue, 19 May 2026 20:08:38 +0000This incident has been resolved.https://status.pipefy.compipefy:2026-05-13T21:08:41ZWed, 13 May 2026 21:08:41 +0000**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.https://status.pipefy.compipefy:2026-05-08T23:06:26ZFri, 08 May 2026 23:06:26 +0000**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.https://status.pipefy.compipefy:2026-05-05T15:06:41ZTue, 05 May 2026 15:06:41 +0000This incident was resolved after a fix being implementedhttps://status.pipefy.compipefy:2026-05-04T19:06:34ZMon, 04 May 2026 19:06:34 +0000**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 impacthttps://status.pipefy.compipefy:2026-04-23T18:48:49ZThu, 23 Apr 2026 18:48:49 +0000Some new performance patches was applied during the monitoring period and we consider the incident resolved now. The app performance is back to an expected level and all operations are running normally. We apologize for the incident and the entire team evolved both technically and operationally to prevent this in the future.https://status.pipefy.compipefy:2026-04-23T18:48:48ZThu, 23 Apr 2026 18:48:48 +0000This incident has been resolved.https://status.pipefy.compipefy:2026-04-23T18:48:48ZThu, 23 Apr 2026 18:48:48 +0000All data is restored and reindexed again in our Elastic Search. We are investigating whats happen in a post mortem meeting and find a better solution to prevent that it's happens again.https://status.pipefy.compipefy:2026-04-23T18:48:48ZThu, 23 Apr 2026 18:48:48 +0000This incident has been resolved. Today at 1:58 PM (UTC) our monitoring service identified a failure to communicate with the Redis database service responsible for background jobs. At 2:00 PM (UTC) our team decided to put our disaster recovery in action, creating a new database that was finished successfully at 14:10 (UTC). Our automated test was run to check the overall status of the system. We've also put it online again for all users at 14:12 (UTC).https://status.pipefy.compipefy:2026-04-23T18:48:48ZThu, 23 Apr 2026 18:48:48 +0000This incident has been resolved.https://status.pipefy.compipefy:2026-04-23T18:48:47ZThu, 23 Apr 2026 18:48:47 +0000During a Redis migration our team identified a failure in HA, provided by our PaaS, which didn't run as expected. That failure occurred between 0:14 AM and 0:17 AM (UTC) and was promptly handled by our Ops Team.https://status.pipefy.compipefy:2026-04-23T18:48:47ZThu, 23 Apr 2026 18:48:47 +0000This incident has been resolved.https://status.pipefy.compipefy:2026-04-23T18:48:47ZThu, 23 Apr 2026 18:48:47 +0000This incident has been resolved.https://status.pipefy.compipefy:2026-04-23T18:48:47ZThu, 23 Apr 2026 18:48:47 +0000The tests were successful and the system is working again. We are working to improving this script so that this problem does not happen again.https://status.pipefy.compipefy:2026-04-23T18:48:47ZThu, 23 Apr 2026 18:48:47 +0000This incident has been resolved.https://status.pipefy.compipefy:2026-04-23T18:48:46ZThu, 23 Apr 2026 18:48:46 +0000We identify the problem, it happened because the gem [sequenced](https://github.com/derrickreimer/sequenced) that we use in our Ruby project locked the phase table, after that this process died and table stay locked. We kill the process and restart the application that returns to respond as expected. Now we are removing that gem and move this logic to our database that can do this job in the same process and prevent this error.