Pipefy Outage History
Pipefy is up right nowPingoru has recorded 77 incidents for Pipefy: 68 in the last 12 months and 11 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 1 | 19 of 720 (3%) |
| May 2026 | 12 | 8 of 744 (1%) |
| June 2026 | 3 | 0 of 720 (0%) |
| July 2026 | 2 | 2 of 744 (0%) |
| August 2026 | 2 | 5 of 744 (1%) |
| September 2026 | 3 | 3 of 720 (0%) |
| October 2026 | 6 | 4 of 526 (1%) |
Incidents, newest first
Notice October 22, 2026 default queue latency above 30s SLO 1h 14m
Started Oct 22, 2026, 08:21 PM UTC· resolved Oct 22, 2026, 09:35 PM UTC
- investigating Oct 22, 2026, 08:21 PM UTC
We are investigating the default queue latency above 30s.
- resolved Oct 22, 2026, 09:35 PM UTC
We’ve recovered the default Sidekiq queue and it has drained. The overload was driven by repeated field-condition save mutations (`Resolvers::FieldConditions::Save`) on a single customer pipe (`307245277`, Copa Energia). Each condition created enqueued a `Cache::PipeInvalidatorWorker` job on the `default` queue, and for this pipe (≈25k cards) each job took ~80–110s, dominating the queue. As mitigation, we scaled up the Core workers around 5:53pm -03 (America/Buenos_Aires). By ~6:17pm -03 (America/Buenos_Aires), Grafana showed default queue latency dropping back to ~0 and the backlog clearing. The queue has drained, and high latency is no longer occurring. As aligned with the stakeholders, the incident is being closed.
Minor October 14, 2026 Login request failures 2m
Started Oct 14, 2026, 07:54 PM UTC· resolved Oct 14, 2026, 07:56 PM UTC
- identified Oct 14, 2026, 07:54 PM UTC
**Impact:** We saw a short-lived login degradation on Pipefy
- resolved Oct 14, 2026, 07:56 PM UTC
**Resolved:** The incident was resolved following the team's intervention.
Notice October 14, 2026 Trial outbound email accepted but not delivered 22m
Started Oct 14, 2026, 06:36 PM UTC· resolved Oct 14, 2026, 06:59 PM UTC
- investigating Oct 14, 2026, 06:36 PM UTC
We are investigating an issue affecting email delivery.
- resolved Oct 14, 2026, 06:59 PM UTC
The incident was resolved.
Minor October 7, 2026 Pipefy Slowness 52m
Started Oct 07, 2026, 06:22 PM UTC· resolved Oct 07, 2026, 07:14 PM UTC
- investigating Oct 07, 2026, 06:22 PM UTC
Investigating: We are investigating slowness on the platform.
- 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.
- monitoring Oct 07, 2026, 07:07 PM UTC
The issue was resolved following analysis by the team, and the incident is now being monitored.
- resolved Oct 07, 2026, 07:14 PM UTC
The incident has been resolved.
Minor October 5, 2026 Customer emails for Pipefy were delayed 54m
Started Oct 05, 2026, 08:15 PM UTC· resolved Oct 05, 2026, 09:10 PM UTC
- investigating Oct 05, 2026, 08:15 PM UTC
Impact: Customer emails for Pipefy were delayed. Were are investigating the issue.
- 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.
- resolved Oct 05, 2026, 09:10 PM UTC
The issue was resolved after a team intervention. The email delivery returned to normal.
Minor October 1, 2026 Automation failures 17m
Started Oct 01, 2026, 05:43 PM UTC· resolved Oct 01, 2026, 06:00 PM UTC
- investigating Oct 01, 2026, 05:43 PM UTC
We are investigating some failures during the automation process
- monitoring Oct 01, 2026, 05:49 PM UTC
The issue was mitigated and now is under monitoring
- resolved Oct 01, 2026, 06:00 PM UTC
The issue was resolved after applying a mitigation
Minor September 29, 2026 AI Agents could have degrated performance 1h 33m
Started Sep 29, 2026, 02:55 PM UTC· resolved Sep 29, 2026, 04:28 PM UTC
- 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.
- monitoring Sep 29, 2026, 02:57 PM UTC
We are checking our provider and will update with new information soon.
- monitoring Sep 29, 2026, 03:32 PM UTC
All services have been operating normally since 14:59 UTC. We are continuing to monitor.
- monitoring Sep 29, 2026, 03:37 PM UTC
All services have been operating normally.
- resolved Sep 29, 2026, 04:28 PM UTC
**All Systems Operational.**
Notice September 28, 2026 Usage stats are unstable 1h 4m
Started Sep 28, 2026, 06:21 PM UTC· resolved Sep 28, 2026, 07:26 PM UTC
- investigating Sep 28, 2026, 06:21 PM UTC
Investigation: User stats are unstable
- 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
- resolved Sep 28, 2026, 07:26 PM UTC
User Stats is working as expected and the service is back to normal
Notice September 25, 2026 Automations screen is not opening 15m
Started Sep 25, 2026, 07:46 PM UTC· resolved Sep 25, 2026, 08:01 PM UTC
- investigating Sep 25, 2026, 07:46 PM UTC
Problem: The automations screen is not opening for some pipes.
- resolved Sep 25, 2026, 08:01 PM UTC
Resolved The incident was resolved after the domain and the automations screen returned to normal
Minor August 26, 2026 Files are inaccessible in some cards 11m
Started Aug 26, 2026, 08:27 PM UTC· resolved Aug 26, 2026, 08:39 PM UTC
- 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.
- resolved Aug 26, 2026, 08:39 PM UTC
The incident was resolved
Minor August 17, 2026 Outbound Email Blocked 4h 23m
Started Aug 17, 2026, 04:44 PM UTC· resolved Aug 17, 2026, 09:07 PM UTC
- investigating Aug 17, 2026, 04:44 PM UTC
Pipefy's email domain has been temporarily added to a block list of emails. Thus, some customers and partners' email servers are preemptively blocking any messages coming from our domain.
- identified Aug 17, 2026, 04:45 PM UTC
Our internal teams already identified the cause of the issue and we are taking the necessary actions to get this corrected.
- monitoring Aug 17, 2026, 05:54 PM UTC
We would like to inform you that action has been taken with our email provider and the issue has been resolved. We are monitoring the results.
- resolved Aug 17, 2026, 09:07 PM UTC
The incident has been resolved following mitigation by the team
- monitoring Aug 18, 2026, 01:01 PM UTC
We would like to inform you that we are monitoring.
- monitoring Aug 18, 2026, 05:07 PM UTC
Our team is continuing to work on resolving the issue in collaboration with our email provider. **Impact:** Some emails sent by clients are not reaching the destination email address in Pipefy. Reinforcing that, while we are still working in the permanent solution for this issue, you can add our [**IPs and domains**](https://help.pipefy.com/en/articles/9167556-how-to-add-pipefy-to-the-email-server-s-allowlist) to your email server as trusted addresses. **Next update** in 2 hours.
- monitoring Aug 18, 2026, 07:28 PM UTC
Our team is still working on the solution to the issue in collaboration with our email provider. **Impact:** Some emails sent by clients are not reaching the destination email address in Pipefy. Reinforcing that, while we are still working in the permanent solution for this issue, you can add our [**IPs and domains**](https://help.pipefy.com/en/articles/9167556-how-to-add-pipefy-to-the-email-server-s-allowlist) to your email server as trusted addresses. **Next update** in 2 hours.
- monitoring Aug 19, 2026, 01:13 PM UTC
Our team is still working on the solution to the issue in collaboration with our email provider.
- monitoring Aug 19, 2026, 05:55 PM UTC
We continue to work with our provider to mitigate and resolve the issue once and for all. **Recomendations:** As a workaround, we are advising our customers to configure our domain as trusted on their servers. We also encourage customers to contact our support team if they need assistance with this process.
- identified Aug 19, 2026, 09:08 PM UTC
We apologize for the inconvenience and want to reiterate that we continue to urge our email service provider to prioritize a resolution to unblocking our emails. We will provide a status update as soon as we receive new information from our provider. **Recomendations:** We are advising our customers to configure our domain as trusted on their servers. We also encourage customers to contact our support team if they need assistance with this process.
- monitoring Aug 20, 2026, 04:04 AM UTC
We apologize for the inconvenience and want to reiterate that we continue to urge our email service provider to prioritize a resolution unblocking our emails. We will provide a status update as soon as we receive new information from our provider. **Recomendations:** We are advising our customers to configure our domain as trusted on their servers. We also encourage customers to contact our support team if they need assistance with this process.
- monitoring Aug 20, 2026, 12:54 PM UTC
We continue to escalate the issue and work closely with our provider to resolve the failure. We will provide a status update as soon as we receive new information from our provider. **Impact:** Some emails sent to or from Pipefy are being affected and failing to deliver. **Recommendations:** We are advising our customers to configure our domain as trusted on their servers. We also encourage customers to contact our support team if they need assistance with this process.
- monitoring Aug 20, 2026, 06:51 PM UTC
Following the actions taken, we saw an improvement with a reduction in email blocks. We continue to monitor the situation and work with the provider to ensure the blocks are fully lifted. We will provide a status update as soon as we receive new information from our provider. **Impact:** Some emails sent to or from Pipefy are being affected and failing to deliver. **Recommendations:** We are advising our customers to configure our domain as trusted on their servers. We also encourage customers to contact our support team if they need assistance with this process.
- monitoring Aug 20, 2026, 09:15 PM UTC
We continue to monitor the situation and work with the provider to ensure the blocks are fully lifted. We will provide a status update as soon as we receive new information from our provider. **Impact:** Some emails sent to or from Pipefy are being affected and failing to deliver. **Recommendations:** We are advising our customers to configure our domain as trusted on their servers. We also encourage customers to contact our support team if they need assistance with this process.
- monitoring Aug 21, 2026, 04:13 AM UTC
We apologize for the inconvenience and want to reiterate that we continue to urge our email service provider to prioritize a resolution unblocking our emails. We will provide a status update as soon as we receive new information from our provider. **Recomendations:** We are advising our customers to configure our domain as trusted on their servers. We also encourage customers to contact our support team if they need assistance with this process.
- monitoring Aug 21, 2026, 01:19 PM UTC
We inform you that our provider has removed the block on [pipefy.com](http://pipefy.com "pipefy.com"). Any remaining blocks related to this listing should be due to outdated recipient-side blocklists. We’re validating that deliverability remains stable and will continue routing any customer-reported cases through support.
- resolved Aug 21, 2026, 02:15 PM UTC
We apologize for the inconvenience caused. We would like to inform you that our domain has been fully cleared and the incident is resolved. We’re validating that deliverability remains stable and will continue routing any customer-reported cases through support.
- monitoring Aug 21, 2026, 07:48 PM UTC
We would like to inform you that we have identified a small percentage—less than 1%—of emails still being blocked. We are working with the provider to ensure they are fully unblocked. We will provide a status update as soon as we receive new information from our provider.
- monitoring Aug 24, 2026, 12:12 PM UTC
We are working with the provider to ensure they are fully unblocked. We will provide a status update as soon as we receive new information from our provider.
- monitoring Aug 24, 2026, 07:16 PM UTC
We continue to identify a small percentage of email blocks. Our team is actively working with our provider to ensure full email delivery. We will provide a status update as soon as we receive new information from our provider.
- monitoring Aug 25, 2026, 02:57 AM UTC
We apologize for the inconvenience and want to reiterate that we continue to urge our email service provider to prioritize a resolution unblocking our emails. We will provide a status update as soon as we receive new information from our provider. **Recomendations:** We are advising our customers to configure our domain as trusted on their servers. We also encourage customers to contact our support team if they need assistance with this process.
- monitoring Aug 25, 2026, 03:18 PM UTC
We continue working closely with our email service provider to prioritize a resolution to unblock our emails. We will provide a status update as soon as we receive new information from our provider. **Recomendations:** We are advising our customers to configure our domain as trusted on their servers. We also encourage customers to contact our support team if they need assistance with this process.
- monitoring Aug 25, 2026, 10:34 PM UTC
We continue working closely with our email service provider to prioritize a resolution to unblock our emails. We will provide a status update as soon as we receive new information from our provider. **Recomendations:** We are advising our customers to configure our domain as trusted on their servers. We also encourage customers to contact our support team if they need assistance with this process.
- monitoring Aug 26, 2026, 05:35 AM UTC
We apologize for the inconvenience and want to reiterate that we continue to urge our email service provider to prioritize a resolution unblocking our emails. We will provide a status update as soon as we receive new information from our provider. **Recomendations:** We are advising our customers to configure our domain as trusted on their servers. We also encourage customers to contact our support team if they need assistance with this process.
- monitoring Aug 26, 2026, 04:53 PM UTC
We're letting you know that deliverability remains degraded for some email providers. We continue to work with our email provider on the delisting and are monitoring delivery by recipient provider. We will provide a status update as soon as we receive new information from our provider. Recomendations: We are advising our customers to configure our domain as trusted on their servers. We also encourage customers to contact our support team if they need assistance with this process.
- monitoring Aug 26, 2026, 10:05 PM UTC
We apologize for the inconvenience and want to reiterate that we continue to urge our email service provider to prioritize a resolution unblocking our emails. We will provide a status update as soon as we receive new information from our provider. **Recomendations:** We are advising our customers to configure our domain as trusted on their servers. We also encourage customers to contact our support team if they need assistance with this process.
- monitoring Aug 27, 2026, 03:10 AM UTC
We're letting you know that deliverability remains degraded for some email providers. We continue to work with our email provider on the delisting and are monitoring delivery by recipient provider. We will provide a status update as soon as we receive new information from our provider. **Recomendations:** We are advising our customers to configure our domain as trusted on their servers. We also encourage customers to contact our support team if they need assistance with this process.
- monitoring Aug 27, 2026, 05:38 PM UTC
Deliverability remains degraded. We continue to work with our email provider on the delisting and are monitoring delivery by recipient provider. We will provide a status update as soon as we receive new information from our provider.
- monitoring Aug 27, 2026, 11:01 PM UTC
We apologize for the inconvenience and want to reiterate that we continue to urge our email service provider to prioritize a resolution unblocking our emails. We will provide a status update as soon as we receive new information from our provider. **Recomendations:** We are advising our customers to configure our domain as trusted on their servers. We also encourage customers to contact our support team if they need assistance with this process.
- monitoring Aug 28, 2026, 04:54 AM UTC
Deliverability remains degraded. We continue to work with our email provider on the delisting and are monitoring delivery by recipient provider. We will provide a status update as soon as we receive new information from our provider.
- monitoring Aug 28, 2026, 05:39 PM UTC
Unfortunately, our deliverability remains degraded for some recipient providers. We apologize for the inconvenience and want to reiterate that we are still working with our email provider on the delisting and are monitoring delivery with the recipient provider. We will provide a status update as soon as we receive new information from our provider.
- monitoring Aug 31, 2026, 01:11 PM UTC
We would like to inform you that our domain has been unblocked, and we are now monitoring the results.
- resolved Sep 01, 2026, 01:26 PM UTC
The incident was resolved after the domain was unblocked by the provider.
Minor July 16, 2026 Degraded Performance 4m
Started Jul 16, 2026, 06:52 PM UTC· resolved Jul 16, 2026, 06:56 PM UTC
- investigating Jul 16, 2026, 06:52 PM UTC
Problem: Clients may experience outdated card information for a few seconds.
- resolved Jul 16, 2026, 06:56 PM UTC
**Latest update** The incident has been resolved following mitigation by the team
Minor July 8, 2026 Degraded Performance - AI Service Routing 1h 51m
Started Jul 08, 2026, 08:24 PM UTC· resolved Jul 08, 2026, 10:16 PM UTC
- 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
- resolved Jul 08, 2026, 10:16 PM UTC
AI service Routing is working as expected and all AI services are back to normal.
Minor June 15, 2026 Cards are not opening due to the missing "from_name" 1m
Started Jun 15, 2026, 08:45 PM UTC· resolved Jun 15, 2026, 08:46 PM UTC
- investigating Jun 15, 2026, 08:45 PM UTC
We are currently investigating this issue.
- monitoring Jun 15, 2026, 08:46 PM UTC
This incident has been resolved.
- resolved Jun 15, 2026, 08:46 PM UTC
The incident was resolved
Minor June 15, 2026 Pipefy Core Slowness 16m
Started Jun 15, 2026, 08:07 PM UTC· resolved Jun 15, 2026, 08:23 PM UTC
- investigating Jun 15, 2026, 08:07 PM UTC
We are currently investigating this issue.
- monitoring Jun 15, 2026, 08:23 PM UTC
We are monitoring the incident.
- resolved Jun 15, 2026, 08:23 PM UTC
The incident was resolved
Minor June 3, 2026 Pipefy slowness 8m
Started Jun 03, 2026, 08:38 PM UTC· resolved Jun 03, 2026, 08:47 PM UTC
- investigating Jun 03, 2026, 08:38 PM UTC
We are currently investigating this issue.
- monitoring Jun 03, 2026, 08:43 PM UTC
This incident has been resolved.
- resolved Jun 03, 2026, 08:47 PM UTC
This incident has been resolved.
- monitoring Jun 03, 2026, 08:55 PM UTC
The issue has been resolved and we are now monitoring it.
- resolved Jun 03, 2026, 09:10 PM UTC
The incident was resolved
Major May 28, 2026 Integrations downtime 1m
Started May 28, 2026, 05:49 PM UTC· resolved May 28, 2026, 05:50 PM UTC
- investigating May 28, 2026, 05:49 PM UTC
- resolved May 28, 2026, 05:50 PM UTC
Notice May 28, 2026 The embedded start form iframe is not working 18m
Started May 28, 2026, 04:41 PM UTC· resolved May 28, 2026, 05:00 PM UTC
- 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.
- resolved May 28, 2026, 05:00 PM UTC
A fix was applied, and the incident was resolved.
Minor May 19, 2026 Search and filters Slowness –
Started May 19, 2026, 07:47 PM UTC· resolved May 19, 2026, 07:47 PM UTC
- identified May 19, 2026, 08:08 PM UTC
The issue has been identified and a fix is being implemented.
- resolved May 19, 2026, 08:08 PM UTC
This incident has been resolved.
Minor May 13, 2026 Automations Slowness 42m
Started May 13, 2026, 09:08 PM UTC· resolved May 13, 2026, 09:51 PM UTC
- investigating May 13, 2026, 09:08 PM UTC
We are currently investigating this issue.
- resolved May 13, 2026, 10:07 PM UTC
This incident has been resolved.
- 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.
Critical May 8, 2026 Application is down –
Started May 08, 2026, 10:59 PM UTC· resolved May 08, 2026, 10:59 PM UTC
- investigating May 08, 2026, 11:06 PM UTC
We are currently investigating this issue
- 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
- resolved May 09, 2026, 12:06 AM UTC
This incident has been resolved.
- 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.
Notice May 5, 2026 (Integrations) Flow executions are experiencing delay on processing time 4h 28m
Started May 05, 2026, 03:06 PM UTC· resolved May 05, 2026, 07:35 PM UTC
- 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.
- resolved May 05, 2026, 08:05 PM UTC
This incident was resolved after a fix being implemented
Minor May 4, 2026 Integrations slowness 41m
Started May 04, 2026, 07:06 PM UTC· resolved May 04, 2026, 07:48 PM UTC
- investigating May 04, 2026, 07:06 PM UTC
We are currently investigating this issue.
- investigating May 04, 2026, 08:06 PM UTC
We are continuing to investigate this issue.
- resolved May 04, 2026, 08:06 PM UTC
This incident has been resolved.
- identified May 04, 2026, 08:06 PM UTC
The issue has been identified and a fix is being implemented.
- 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
Notice April 1, 2026 Custom Integrations/iPaaS : Rate Limiting Issues 18h 42m Integrations
Started Apr 01, 2026, 07:40 PM UTC· resolved Apr 02, 2026, 02:23 PM UTC
- 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.
- resolved Apr 02, 2026, 02:23 PM UTC
This incident has been resolved. Additional information will be provided shortly in our postmortem report.
- 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
Notice March 30, 2026 Filters and search interfaces degradations 4h Dashboards, Filters
Started Mar 30, 2026, 12:53 PM UTC· resolved Mar 30, 2026, 04:53 PM UTC
- 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.
- resolved Mar 31, 2026, 07:51 PM UTC
This incident has been resolved.