Pipefy Outage History

Pipefy is up right now

Pingoru has recorded 78 incidents for Pipefy: 69 in the last 12 months and 12 in the last 90 days.

Source: status.pipefy.com

78incidents recorded
69last 12 months
12last 90 days
3 hourstypical duration
Incidents per month
01020AprMayJunJulAugSepOct7
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct1%
Pingoru began tracking Pipefy in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 2026119 of 720 (3%)
May 2026128 of 744 (1%)
June 202630 of 720 (0%)
July 202622 of 744 (0%)
August 202625 of 744 (1%)
September 202633 of 720 (0%)
October 202674 of 585 (1%)

Incidents, newest first

Minor December 1, 2025 Task and Request unable 22m Portals

Started Dec 01, 2025, 09:48 PM UTC· resolved Dec 01, 2025, 10:11 PM UTC

  1. identified Dec 01, 2025, 09:48 PM UTC

    The issue has been identified and a fix is being implemented.

  2. resolved Dec 01, 2025, 10:11 PM UTC

    This incident has been resolved.

  3. postmortem Dec 09, 2025, 06:50 PM UTC

    **Root Cause** The issue was caused by a failure in the system due to implementation in the project. This led to data fields displaying incorrect formats, affecting forms for users who were logged in. **Resolution** The problem was resolved by applying a fix that reverted the previous changes, which corrected the data format issues for logged users. **Action Plan** Moving forward, the system will be updated to preventing similar issues from occurring in the future.

Read the full incident report →

Notice December 1, 2025 Date fields showing in an incorrect format in public forms 1h 36m Application, Public Form

Started Dec 01, 2025, 07:14 PM UTC· resolved Dec 01, 2025, 08:50 PM UTC

  1. identified Dec 01, 2025, 07:14 PM UTC

    Date fields are showing in an incorrect format in public forms. Currently, the issue has been identified and a fix is being implemented.

  2. monitoring Dec 01, 2025, 08:47 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Dec 01, 2025, 08:50 PM UTC

    This incident has been resolved.

  4. postmortem Dec 09, 2025, 10:05 PM UTC

    **Summary** Data fields within the platform were displaying incorrect formats, which specifically affected forms accessed by logged-in users. This issue was identified and resolved without causing the platform to become inaccessible. **Impact** The incorrect data formats impacted the user experience for those who were logged into the platform, potentially causing confusion or errors in form submissions. However, the platform remained accessible, ensuring that users could continue to perform other tasks without interruption. **Root Cause** The root cause of the issue was traced back to a merge request in the app, where the correct configuration was not implemented. This oversight led to the incorrect data formats being displayed. ‌ **Corrective Actions** The issue was resolved by applying a merge request to revert the changes that caused the problem. **Next Steps | Conclusion** We will maintain vigilant monitoring of the system to ensure ongoing stability and to prevent future occurrences of similar issues. Our commitment to enhancing the customer experience remains a top priority as we continue to refine and improve our platform.

Read the full incident report →

Minor November 28, 2025 AI Analytics slowness 17m AI Assistant

Started Nov 28, 2025, 02:50 PM UTC· resolved Nov 28, 2025, 03:08 PM UTC

  1. investigating Nov 28, 2025, 02:50 PM UTC

    We are currently investigating this issue.

  2. identified Nov 28, 2025, 02:59 PM UTC

    The issue has been identified and a fix is being implemented.

  3. investigating Nov 28, 2025, 03:05 PM UTC

    The team identified an issue and still working on solution

  4. resolved Nov 28, 2025, 03:08 PM UTC

    This incident has been resolved.

  5. postmortem Dec 08, 2025, 03:26 PM UTC

    **Root Cause** The AI Analytics feature experienced a complete failure, causing the system to hang in a 'processing' state without returning results. This issue arose after a deployment implemented **Resolution** The problem was resolved by implementing a fix to address the system's failure. This action restored the functionality of the AI Analytics feature, allowing it to process queries and return results as expected. **Action Plan** To prevent future incidents, we will enhance tests to better identify failures, Conduct post-implementation tests and improve the telemetry monitoring for the AI analytics feature.

Read the full incident report →

Minor November 28, 2025 Unable to purchase or update plans 1h 37m Billing

Started Nov 28, 2025, 02:03 PM UTC· resolved Nov 28, 2025, 03:40 PM UTC

  1. identified Nov 28, 2025, 02:03 PM UTC

    The issue has been identified and a fix is being implemented.

  2. identified Nov 28, 2025, 03:22 PM UTC

    We are continuing working on this fix

  3. resolved Nov 28, 2025, 03:40 PM UTC

    This incident has been resolved.

  4. postmortem Dec 04, 2025, 08:05 PM UTC

    **Root Cause** The problem was cause by new implementation using transaction finance API, which affected the purchasing service. The issue was identified and resolved by reverting the change. **Resolution** The problem was resolved by reverting the implementation, restoring the service to normal. **Action Plan**

Read the full incident report →

Minor November 11, 2025 Dashboard not Loading 19m Dashboards

Started Nov 11, 2025, 07:39 PM UTC· resolved Nov 11, 2025, 07:58 PM UTC

  1. investigating Nov 11, 2025, 07:39 PM UTC

    We are currently investigating this issue.

  2. identified Nov 11, 2025, 07:54 PM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring Nov 11, 2025, 07:57 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved Nov 11, 2025, 07:58 PM UTC

    This incident has been resolved.

  5. postmortem Nov 13, 2025, 08:05 PM UTC

    **Root Cause** The exact cause of the issue is still under investigation. The team responsible for the dashboards is exploring a new strategy involving cache tecnologies to determine its impact on the problem. **Resolution** The issue was resolved by restarting the system responsible for data caching, which restored normal functionality. **Action Plan** To prevent future occurrences, the team will enhance the monitoring system for the dashboard application to better detect and track failures. Additionally, they are considering replacing the current data caching system with a more efficient solution.

Read the full incident report →

Minor November 3, 2025 The information is not loading on the Dashboard. 1h 28m Dashboards

Started Nov 03, 2025, 02:06 PM UTC· resolved Nov 03, 2025, 03:34 PM UTC

  1. investigating Nov 03, 2025, 02:06 PM UTC

    We are currently investigating this issue.

  2. identified Nov 03, 2025, 02:13 PM UTC

    The issue has been identified and a fix is being implemented.

  3. identified Nov 03, 2025, 03:27 PM UTC

    We are continuing to work on a fix for this issue.

  4. monitoring Nov 03, 2025, 03:29 PM UTC

    A fix has been implemented and we are monitoring the results.

  5. resolved Nov 03, 2025, 03:34 PM UTC

    This incident has been resolved.

  6. postmortem Nov 13, 2025, 08:12 PM UTC

    **Root Cause** The exact cause of the issue is still being investigated. The team responsible for the dashboard is exploring a new method involving the cache technologie to determine if it will effectively address the problem. **Resolution** The issue was resolved by changing the system from using new cache data, which restored the functionality of the dashboard. **Action Plan**

Read the full incident report →

Minor October 31, 2025 E-mails being blocked by Spamhaus 38m Email Messaging

Started Oct 31, 2025, 03:21 PM UTC· resolved Oct 31, 2025, 04:00 PM UTC

  1. investigating Oct 31, 2025, 03:21 PM UTC

    We are currently investigating this issue.

  2. identified Oct 31, 2025, 03:27 PM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring Oct 31, 2025, 03:44 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved Oct 31, 2025, 04:00 PM UTC

    This incident has been resolved.

  5. postmortem Nov 11, 2025, 06:08 PM UTC

    **Root Cause** Some organizations faced email delivery issues due to their emails being blacklisted. This was caused by certain IPs being blocked, which affected the ability to send emails. **Resolution** The issue was mitigated by removing the problematic IP from the range, allowing emails to be sent through other available IPs. Additionally, a support ticket was opened to resolve the IP block.

Read the full incident report →

Notice October 22, 2025 Users can't sign in to the system. 15m Application

Started Oct 22, 2025, 03:20 PM UTC· resolved Oct 22, 2025, 03:35 PM UTC

  1. investigating Oct 22, 2025, 03:20 PM UTC

    We are currently investigating this issue. Already logged-in users can continue using the system.

  2. identified Oct 22, 2025, 03:29 PM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring Oct 22, 2025, 03:33 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved Oct 22, 2025, 03:35 PM UTC

    This incident has been resolved.

  5. postmortem Oct 29, 2025, 05:24 PM UTC

    **Root Cause** The issue was caused by a database instance being unavailable due to a node failure. This led to a large number of open transactions, resulting in errors and preventing users from signing in. **Resolution** The affected node was recycled and restored, allowing users to log in again without further issues. **Action Plan** New alerts have been set up to monitor errors related to open transactions. Further investigation will be conducted to understand why these transactions were left open, and regular maintenance will be performed to prevent them from remaining unresolved.

Read the full incident report →

Minor October 20, 2025 Third-party support platform slowness issue 1d Intercom Chats and Posts

Started Oct 20, 2025, 01:06 PM UTC· resolved Oct 21, 2025, 01:33 PM UTC

  1. monitoring Oct 20, 2025, 01:06 PM UTC

    Although all of our services are up and running, the third-party app responsible for connecting our customers with our support team is currently being affected by the global AWS incident If you need to contact support, please send an email to [email protected]

  2. resolved Oct 21, 2025, 01:33 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor October 13, 2025 AI Assistants issues 9m AI Assistant

Started Oct 13, 2025, 01:48 PM UTC· resolved Oct 13, 2025, 01:57 PM UTC

  1. investigating Oct 13, 2025, 01:48 PM UTC

    We are currently investigating this issue.

  2. identified Oct 13, 2025, 01:56 PM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring Oct 13, 2025, 01:56 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. monitoring Oct 13, 2025, 01:57 PM UTC

    We are continuing to monitor for any further issues.

  5. resolved Oct 13, 2025, 01:57 PM UTC

    This incident has been resolved.

  6. postmortem Oct 28, 2025, 06:13 PM UTC

    **Root Cause** The issue arose because the chat records were not linked to the channel object as expected. This lack of connection led to the problems experienced. **Resolution** To resolve the issue, the project was rolled back to a previous version, and changes were reversed. A fix was then applied to ensure that the chat and channel relationship is established, preventing further errors. **Action Plan** During the incident, changes were reversed. Afterward, a fix was implemented to establish the chat-channel relationship, preventing recurrence. Additionally, alerts were set up to notify about any future issues.

Read the full incident report →

Major October 9, 2025 Interfaces Out 13m

Started Oct 09, 2025, 07:08 PM UTC· resolved Oct 09, 2025, 07:22 PM UTC

  1. investigating Oct 09, 2025, 07:08 PM UTC

    We are currently investigating this issue.

  2. identified Oct 09, 2025, 07:16 PM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring Oct 09, 2025, 07:17 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved Oct 09, 2025, 07:22 PM UTC

    This incident has been resolved.

  5. postmortem Oct 15, 2025, 08:38 PM UTC

    **Root Cause** The issue arose because the subscription plan records in production were missing a crucial field, leading to a failure in the system. This caused the interfaces to become inaccessible as they couldn't retrieve the necessary information. **Resolution** The solution involved reverting the changes that introduced the bug in the production environment, thereby restoring the system's functionality. **Action Plan** To prevent future occurrences, improvements were made to the error handling screen, a deployment was executed to enhance query resilience, and additional validation was implemented in testing to ensure subscription functionality.

Read the full incident report →