Pipefy Outage History

Pipefy is up right now

Pipefy had 58 outages in the last 2 years totaling 62h 36m of downtime — averaging 2.4 incidents per month.

There were 58 Pipefy outages since October 8, 2025 totaling 62h 36m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.pipefy.com

Minor October 7, 2026

Pipefy Slowness

Detected by Pingoru
Oct 07, 2026, 06:22 PM UTC
Resolved
Oct 07, 2026, 07:14 PM UTC
Duration
52m
Timeline · 4 updates
  1. investigating Oct 07, 2026, 06:22 PM UTC

    Investigating: We are investigating slowness on the platform.

  2. investigating Oct 07, 2026, 06:33 PM UTC

    We are currently investigating reports of slowness on the Pipefy platform; our team is already working to resolve the issue.

  3. monitoring Oct 07, 2026, 07:07 PM UTC

    The issue was resolved following analysis by the team, and the incident is now being monitored.

  4. resolved Oct 07, 2026, 07:14 PM UTC

    The incident has been resolved.

Read the full incident report →

Minor October 5, 2026

Customer emails for Pipefy were delayed

Detected by Pingoru
Oct 05, 2026, 08:15 PM UTC
Resolved
Oct 05, 2026, 09:10 PM UTC
Duration
54m
Timeline · 3 updates
  1. investigating Oct 05, 2026, 08:15 PM UTC

    Impact: Customer emails for Pipefy were delayed. Were are investigating the issue.

  2. investigating Oct 05, 2026, 08:37 PM UTC

    **Impact clarification:** We inform you that the delay is limited to notification emails handled by the assignee, mentions, comments, phase changes, overdue, etc.

  3. resolved Oct 05, 2026, 09:10 PM UTC

    The issue was resolved after a team intervention. The email delivery returned to normal.

Read the full incident report →

Minor October 1, 2026

Automation failures

Detected by Pingoru
Oct 01, 2026, 05:43 PM UTC
Resolved
Oct 01, 2026, 06:00 PM UTC
Duration
17m
Timeline · 3 updates
  1. investigating Oct 01, 2026, 05:43 PM UTC

    We are investigating some failures during the automation process

  2. monitoring Oct 01, 2026, 05:49 PM UTC

    The issue was mitigated and now is under monitoring

  3. resolved Oct 01, 2026, 06:00 PM UTC

    The issue was resolved after applying a mitigation

Read the full incident report →

Minor September 29, 2026

AI Agents could have degrated performance

Detected by Pingoru
Sep 29, 2026, 02:55 PM UTC
Resolved
Sep 29, 2026, 04:28 PM UTC
Duration
1h 33m
Timeline · 5 updates
  1. investigating Sep 29, 2026, 02:55 PM UTC

    There is a third-party outage going on in one of the services Pipefy uses as the engine of our AI agents, so customers may face degradated performance in some of their agents. We are monitoring the situation with our provider and will keep our status page up to date as this issue goes on.

  2. monitoring Sep 29, 2026, 02:57 PM UTC

    We are checking our provider and will update with new information soon.

  3. monitoring Sep 29, 2026, 03:32 PM UTC

    All services have been operating normally since 14:59 UTC. We are continuing to monitor.

  4. monitoring Sep 29, 2026, 03:37 PM UTC

    All services have been operating normally.

  5. resolved Sep 29, 2026, 04:28 PM UTC

    **All Systems Operational.**

Read the full incident report →

Notice September 28, 2026

Usage stats are unstable

Detected by Pingoru
Sep 28, 2026, 06:21 PM UTC
Resolved
Sep 28, 2026, 07:26 PM UTC
Duration
1h 4m
Timeline · 3 updates
  1. investigating Sep 28, 2026, 06:21 PM UTC

    Investigation: User stats are unstable

  2. monitoring Sep 28, 2026, 06:33 PM UTC

    **Summary** Problem: The User Stats feature is unstable, causing a brief degraded performance. The team applied a mitigation and is now under monitoring

  3. resolved Sep 28, 2026, 07:26 PM UTC

    User Stats is working as expected and the service is back to normal

Read the full incident report →

Notice September 25, 2026

Automations screen is not opening

Detected by Pingoru
Sep 25, 2026, 07:46 PM UTC
Resolved
Sep 25, 2026, 08:01 PM UTC
Duration
15m
Timeline · 2 updates
  1. investigating Sep 25, 2026, 07:46 PM UTC

    Problem: The automations screen is not opening for some pipes.

  2. resolved Sep 25, 2026, 08:01 PM UTC

    Resolved The incident was resolved after the domain and the automations screen returned to normal

Read the full incident report →

Minor August 26, 2026

Files are inaccessible in some cards

Detected by Pingoru
Aug 26, 2026, 08:27 PM UTC
Resolved
Aug 26, 2026, 08:39 PM UTC
Duration
11m
Timeline · 2 updates
  1. investigating Aug 26, 2026, 08:27 PM UTC

    Some customers are reporting files being inaccessible in some specific cards, returning a not found error. We are currently investigating this issue.

  2. resolved Aug 26, 2026, 08:39 PM UTC

    The incident was resolved

Read the full incident report →

Minor July 16, 2026

Degraded Performance

Detected by Pingoru
Jul 16, 2026, 06:52 PM UTC
Resolved
Jul 16, 2026, 06:56 PM UTC
Duration
4m
Timeline · 2 updates
  1. investigating Jul 16, 2026, 06:52 PM UTC

    Problem: Clients may experience outdated card information for a few seconds.

  2. resolved Jul 16, 2026, 06:56 PM UTC

    **Latest update** The incident has been resolved following mitigation by the team

Read the full incident report →

Minor July 8, 2026

Degraded Performance - AI Service Routing

Detected by Pingoru
Jul 08, 2026, 08:24 PM UTC
Resolved
Jul 08, 2026, 10:16 PM UTC
Duration
1h 51m
Timeline · 2 updates
  1. investigating Jul 08, 2026, 08:24 PM UTC

    We are investigating an issue affecting our primary AI endpoints (ABBY). To maintain availability and prevent disruptions to AI Agents, Assistants, and automations, traffic has been successfully rerouted to our secondary provider (OpenAI). Services remain operational

  2. resolved Jul 08, 2026, 10:16 PM UTC

    AI service Routing is working as expected and all AI services are back to normal.

Read the full incident report →

Minor June 15, 2026

Cards are not opening due to the missing "from_name"

Detected by Pingoru
Jun 15, 2026, 08:45 PM UTC
Resolved
Jun 15, 2026, 08:46 PM UTC
Duration
1m
Timeline · 3 updates
  1. investigating Jun 15, 2026, 08:45 PM UTC

    We are currently investigating this issue.

  2. monitoring Jun 15, 2026, 08:46 PM UTC

    This incident has been resolved.

  3. resolved Jun 15, 2026, 08:46 PM UTC

    The incident was resolved

Read the full incident report →

Minor June 15, 2026

Pipefy Core Slowness

Detected by Pingoru
Jun 15, 2026, 08:07 PM UTC
Resolved
Jun 15, 2026, 08:23 PM UTC
Duration
16m
Timeline · 3 updates
  1. investigating Jun 15, 2026, 08:07 PM UTC

    We are currently investigating this issue.

  2. monitoring Jun 15, 2026, 08:23 PM UTC

    We are monitoring the incident.

  3. resolved Jun 15, 2026, 08:23 PM UTC

    The incident was resolved

Read the full incident report →

Minor June 3, 2026

Pipefy slowness

Detected by Pingoru
Jun 03, 2026, 08:38 PM UTC
Resolved
Jun 03, 2026, 08:47 PM UTC
Duration
8m
Timeline · 5 updates
  1. investigating Jun 03, 2026, 08:38 PM UTC

    We are currently investigating this issue.

  2. monitoring Jun 03, 2026, 08:43 PM UTC

    This incident has been resolved.

  3. resolved Jun 03, 2026, 08:47 PM UTC

    This incident has been resolved.

  4. monitoring Jun 03, 2026, 08:55 PM UTC

    The issue has been resolved and we are now monitoring it.

  5. resolved Jun 03, 2026, 09:10 PM UTC

    The incident was resolved

Read the full incident report →

Notice May 28, 2026

The embedded start form iframe is not working

Detected by Pingoru
May 28, 2026, 04:41 PM UTC
Resolved
May 28, 2026, 05:00 PM UTC
Duration
18m
Timeline · 2 updates
  1. investigating May 28, 2026, 04:41 PM UTC

    We've spotted that something has gone wrong. We're currently investigating the issue, and will provide an update soon.

  2. resolved May 28, 2026, 05:00 PM UTC

    A fix was applied, and the incident was resolved.

Read the full incident report →

Minor May 19, 2026

Search and filters Slowness

Detected by Pingoru
May 19, 2026, 07:47 PM UTC
Resolved
May 19, 2026, 07:47 PM UTC
Duration
—
Timeline · 2 updates
  1. identified May 19, 2026, 08:08 PM UTC

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

  2. resolved May 19, 2026, 08:08 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 13, 2026

Automations Slowness

Detected by Pingoru
May 13, 2026, 09:08 PM UTC
Resolved
May 13, 2026, 09:51 PM UTC
Duration
42m
Timeline · 3 updates
  1. investigating May 13, 2026, 09:08 PM UTC

    We are currently investigating this issue.

  2. resolved May 13, 2026, 10:07 PM UTC

    This incident has been resolved.

  3. resolved May 19, 2026, 10:11 PM UTC

    **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.

Read the full incident report →

Critical May 8, 2026

Application is down

Detected by Pingoru
May 08, 2026, 10:59 PM UTC
Resolved
May 08, 2026, 10:59 PM UTC
Duration
—
Timeline · 4 updates
  1. investigating May 08, 2026, 11:06 PM UTC

    We are currently investigating this issue

  2. monitoring May 09, 2026, 12:06 AM UTC

    The application is online, but users may still experience degraded performance or intermittent issues. Our engineering team is closely monitoring system health as we work towards full restoration

  3. resolved May 09, 2026, 12:06 AM UTC

    This incident has been resolved.

  4. resolved May 12, 2026, 06:06 PM UTC

    **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.

Read the full incident report →

Notice May 5, 2026

(Integrations) Flow executions are experiencing delay on processing time

Detected by Pingoru
May 05, 2026, 03:06 PM UTC
Resolved
May 05, 2026, 07:35 PM UTC
Duration
4h 28m
Timeline · 2 updates
  1. investigating May 05, 2026, 03:06 PM UTC

    Dear customers, We are currently aware of an issue affecting a subset of our customers where iPaaS flow executions are experiencing longer-than-expected processing times. We want to be transparent: Your flows are running. The behavior some customers are noticing is a delay in the time it takes for each process to be picked up and started — once a run begins, it proceeds normally. Our engineering teams are actively investigating the root cause and working to restore standard processing times as quickly as possible. We do not have an ETA to share at this moment, but we are committed to keeping you informed as the situation evolves. If you have been impacted, no action is required on your end. We will provide updates in our Statuspage as they become available. We apologize for any inconvenience this may cause and appreciate your patience.

  2. resolved May 05, 2026, 08:05 PM UTC

    This incident was resolved after a fix being implemented

Read the full incident report →

Minor May 4, 2026

Integrations slowness

Detected by Pingoru
May 04, 2026, 07:06 PM UTC
Resolved
May 04, 2026, 07:48 PM UTC
Duration
41m
Timeline · 5 updates
  1. investigating May 04, 2026, 07:06 PM UTC

    We are currently investigating this issue.

  2. investigating May 04, 2026, 08:06 PM UTC

    We are continuing to investigate this issue.

  3. resolved May 04, 2026, 08:06 PM UTC

    This incident has been resolved.

  4. identified May 04, 2026, 08:06 PM UTC

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

  5. resolved May 11, 2026, 05:06 PM UTC

    **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 impact

Read the full incident report →

Notice April 1, 2026

Custom Integrations/iPaaS : Rate Limiting Issues

Detected by Pingoru
Apr 01, 2026, 07:40 PM UTC
Resolved
Apr 02, 2026, 02:23 PM UTC
Duration
18h 42m
Affected: Integrations
Timeline · 3 updates
  1. monitoring Apr 02, 2026, 01:15 PM UTC

    We have identified that a recent internal infrastructure update caused unexpected rate-limiting on our iPaaS platform, resulting in temporary delays or 429 errors in workflows for the custom integrations. Our Infrastructure team has identified the root cause and successfully applied a fix to restore normal traffic. We're closely monitoring the environment to ensure stability. Normal service operation is expected across all affected organizations.

  2. resolved Apr 02, 2026, 02:23 PM UTC

    This incident has been resolved. Additional information will be provided shortly in our postmortem report.

  3. postmortem Apr 06, 2026, 07:14 PM UTC

    **Root Cause** Recently, efforts were made to separate the infrastructure for better handling of increased demand. This led to the failure of previously set exception rules. An update was applied to a specific host or domain without verifying its use in the integration, causing issues. **Resolution** The issue was resolved by modifying the configuration rules on Ipass app. **Action Plan** - An anomaly alert will be created for the Ipass to avoid this scenario happend again in the future

Read the full incident report →

Notice March 30, 2026

Filters and search interfaces degradations

Detected by Pingoru
Mar 30, 2026, 12:53 PM UTC
Resolved
Mar 30, 2026, 04:53 PM UTC
Duration
4h
Affected: DashboardsFilters
Timeline · 2 updates
  1. investigating Mar 31, 2026, 07:50 PM UTC

    On March 30th, the platform experienced a degradation that impacted filter and search applications. This incident was opened retroactively to provide visibility to customers. The problem is no longer occurring at the moment. Thank you for your understanding.

  2. resolved Mar 31, 2026, 07:51 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor March 6, 2026

Integrations failure

Detected by Pingoru
Mar 06, 2026, 03:00 PM UTC
Resolved
Mar 06, 2026, 03:09 PM UTC
Duration
8m
Timeline · 5 updates
  1. investigating Mar 06, 2026, 03:08 PM UTC

    We are currently investigating this issue.

  2. monitoring Mar 06, 2026, 03:08 PM UTC

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

  3. monitoring Mar 06, 2026, 03:09 PM UTC

    We are continuing to monitor for any further issues.

  4. resolved Mar 06, 2026, 03:09 PM UTC

    This incident has been resolved.

  5. postmortem Mar 10, 2026, 09:10 PM UTC

    **Root Cause** The issue was caused by a failure in the integration feature, which led to an overload in the system. An unoptimized job created thousands of subflows, quickly filling up memory and affecting system availability. The misuse of the integration was identified as the root cause, prompting the disabling of the problematic flow as an initial step to mitigate the issue. **Resolution** To resolve the issue, the team deactivated the problematic flow and partially cleared the queues. This initial solution aimed to prevent new calls and address the items stuck in the queue. **Action Plan** **We will continue to monitor the system closely to ensure stability and prevent future issues. Our focus remains on continuously improving the customer experience by optimizing our processes and enhancing communication between teams.**

Read the full incident report →

Notice March 4, 2026

Dashboards Outage

Detected by Pingoru
Mar 04, 2026, 09:23 PM UTC
Resolved
Mar 04, 2026, 09:50 PM UTC
Duration
27m
Affected: Dashboards
Timeline · 4 updates
  1. investigating Mar 04, 2026, 09:23 PM UTC

    We are currently investigating this issue.

  2. investigating Mar 04, 2026, 09:23 PM UTC

    We are continuing to investigate this issue.

  3. monitoring Mar 04, 2026, 09:45 PM UTC

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

  4. resolved Mar 04, 2026, 09:50 PM UTC

    This incident has been resolved.

Read the full incident report →