Company Logo

Is there an Pipefy outage?

Pipefy status: Systems Active

Last checked: 7 minutes ago

Get notified about any outages, downtime or incidents for Pipefy and 1800+ other cloud vendors. Monitor 10 companies, for free.

Subscribe for updates

Pipefy outages and incidents

Outage and incident data over the last 30 days for Pipefy.

There have been 1 outages or incidents for Pipefy in the last 30 days.

Severity Breakdown:

Tired of searching for status updates?

Join OutLogger to be notified when any of your vendors or the components you use experience an outage. It's completely free and takes less than 2 minutes!

Sign Up Now

Components and Services Monitored for Pipefy

Outlogger tracks the status of these components for Xero:

API (GraphQL) Active
Application Active
Auth0 Management Dashboard (manage.auth0.com) Active
Auth0 User Authentication Active
Auth0 User Authentication Active
Auth0 User Authentication Active
Auth0 Web Site (auth0.com) Active
Authentication Active
Automation Active
CDN Active
Home page Active
Intercom Chats and Posts Active
Intercom Intercom APIs Active
Intercom Intercom Web Application Active
Mobile App Active
Portals Active
Public Form Active
Reports Active
Request tracker Active
SendGrid API Active
SendGrid Email Activity Active
Calendar Active
Email messaging Active
Email template Active
Importer Active
PDF Templates Active
Pipefy Bitbucket integration Active
Pipefy Github integration Active
Pipefy Gitlab integration Active
Pipefy Slack integration Active
Process templates Active
Sprint Planner Active
Activities Active
Activities Active
Advanced Reports Active
Billing Active
Dashboards Active
Database Active
Email inbox Active
Field Values Active
Filters Active
Lateness Active
Live updates Active
Notification Active
Webhooks Active
Pricing Active
Signup Active
Template store Active
Component Status
API (GraphQL) Active
Application Active
Auth0 Management Dashboard (manage.auth0.com) Active
Auth0 User Authentication Active
Auth0 User Authentication Active
Auth0 User Authentication Active
Auth0 Web Site (auth0.com) Active
Authentication Active
Automation Active
CDN Active
Home page Active
Intercom Chats and Posts Active
Intercom Intercom APIs Active
Intercom Intercom Web Application Active
Mobile App Active
Portals Active
Public Form Active
Reports Active
Request tracker Active
SendGrid API Active
SendGrid Email Activity Active
Active
Calendar Active
Email messaging Active
Email template Active
Importer Active
PDF Templates Active
Pipefy Bitbucket integration Active
Pipefy Github integration Active
Pipefy Gitlab integration Active
Pipefy Slack integration Active
Process templates Active
Sprint Planner Active
Active
Activities Active
Activities Active
Advanced Reports Active
Billing Active
Dashboards Active
Database Active
Email inbox Active
Field Values Active
Filters Active
Lateness Active
Live updates Active
Notification Active
Webhooks Active
Active
Pricing Active
Signup Active
Template store Active

Latest Pipefy outages and incidents.

View the latest incidents for Pipefy and check for official updates:

Updates:

  • Time: Sept. 24, 2024, 3:53 p.m.
    Status: Resolved
    Update: Filters are back to normal now. The actions we took did solve the issue, but the root cause is yet to be found. We'll post more about the root cause in the post-mortem.
  • Time: Sept. 24, 2024, 3:47 p.m.
    Status: Monitoring
    Update: We manually scaled our VMs to handle the queue, and it is normalized now. We're monitoring the next minutes.
  • Time: Sept. 24, 2024, 3:34 p.m.
    Status: Investigating
    Update: There was a high load in a queue that manages updates in card attributes (e.g.: title, current phase and labels), and this load led to a delay in the processing of data inside the queue. Even though it is decreasing now, we are investigating the genesis of this event.
  • Time: Sept. 24, 2024, 3:11 p.m.
    Status: Identified
    Update: For more context on the issue: when we apply a filter, matching cards are not being displayed. There are no pop-up error messages, but the expected results aren't show.
  • Time: Sept. 24, 2024, 3 p.m.
    Status: Identified
    Update: When we filter for data inside Pipefy, it might not come as expected. We are looking for the root cause.

Updates:

  • Time: Sept. 23, 2024, 6:16 p.m.
    Status: Resolved
    Update: We encountered a configuration issue while attempting to replicate our database, which blocked partial execution and led to related errors. This impacted card deletions, asynchronous card updates, and automation processes, ultimately resulting in delays on the platform. The root cause of the error will be detailed in the post-mortem report. Additionally, we plan to enhance our alert system to better monitor acceptable error levels in the logs.

Updates:

  • Time: Sept. 19, 2024, 8:17 p.m.
    Status: Resolved
    Update: After this rollout, logins are all good now. We'll post more details about this episode in the post-mortem.
  • Time: Sept. 19, 2024, 8:09 p.m.
    Status: Monitoring
    Update: After a rollout in our infra, the login seems to be more stable. We're now monitoring the next login events.
  • Time: Sept. 19, 2024, 8:09 p.m.
    Status: Identified
    Update: After a rollout in our infra, the login seems to be more stable. We're now monitoring.
  • Time: Sept. 19, 2024, 8:06 p.m.
    Status: Identified
    Update: Our authentication tool is unstable, and this instability led to login issues. It works every now and then, but we're investigating more details on what could have caused this issue.
  • Time: Sept. 19, 2024, 7:53 p.m.
    Status: Investigating
    Update: We are continuing to investigate this issue.
  • Time: Sept. 19, 2024, 7:52 p.m.
    Status: Investigating
    Update: Users that are already logged in will not be affected, but users that are trying to login now may face difficulties. We're investigating the root cause, and we'll send updates as we progress.

Updates:

  • Time: Aug. 22, 2024, 2:52 p.m.
    Status: Postmortem
    Update: **Root Cause** After the upgrade, the new version failed to use the replication slot. **Resolution** A script was executed to correct the data for the period it was unavailable. **Action Plan** During the incident, a correction script was updated and run.
  • Time: Aug. 18, 2024, 7:28 p.m.
    Status: Resolved
    Update: The issue has been resolved. The correction has been made and the data is being mirrored. We are still monitoring data performance and will provide further details in our post-mortem report.
  • Time: Aug. 18, 2024, 7 p.m.
    Status: Monitoring
    Update: The correction has been applied, we'll still monitoring the data performance.
  • Time: Aug. 18, 2024, 4:33 p.m.
    Status: Identified
    Update: With the fix underway, the data is gradually being updated. The dashboard and IA Response will still present outdated data until the correction is completed.
  • Time: Aug. 18, 2024, 3:26 p.m.
    Status: Identified
    Update: We are applying a fix to resolve the issue. Our team is closely monitoring the situation and will provide more information soon.
  • Time: Aug. 18, 2024, 2:53 p.m.
    Status: Identified
    Update: We are continuing to work on a fix for this issue.
  • Time: Aug. 18, 2024, 2:28 p.m.
    Status: Identified
    Update: Due to some complications during the maintenance window, the data reflected in dashboards and IA responses are reflecting until 9 am GMT-3 today. We're working to solve this issue.

Updates:

  • Time: Aug. 22, 2024, 2:03 p.m.
    Status: Postmortem
    Update: **Root Cause** The service experienced downtime due to a failover in our system's cache instance, which impacted our application. The underlying reason for this failover is still being investigated. **Resolution** The issue was addressed by reverting to a previous setup to restore service functionality. **Action Plan** We are actively communicating with our partners to identify the root cause. If no satisfactory response is received, we will reconsider our cache migration strategy. Additionally, we will enhance monitoring of our systems to prevent future occurrences.
  • Time: Aug. 16, 2024, 3:24 p.m.
    Status: Resolved
    Update: The issue was with our third-party software. The connection was restored with a parallel fix. The root cause analysis is still in progress, and we will provide more details in our Post-Mortem.
  • Time: Aug. 16, 2024, 3:21 p.m.
    Status: Investigating
    Update: A fix has been implemented and we are monitoring the results.
  • Time: Aug. 16, 2024, 3:09 p.m.
    Status: Investigating
    Update: We are currently investigating this issue.

Check the status of similar companies and alternatives to Pipefy

Avalara
Avalara

Systems Active

Crisis Text Line
Crisis Text Line

Issues Detected

Jamf
Jamf

Systems Active

Mulesoft
Mulesoft

Systems Active

Meltwater
Meltwater

Issues Detected

HashiCorp
HashiCorp

Systems Active

Datto
Datto

Issues Detected

Vox Media
Vox Media

Systems Active

Cradlepoint
Cradlepoint

Systems Active

Liferay
Liferay

Systems Active

Zapier
Zapier

Systems Active

Workato US
Workato US

Systems Active

Frequently Asked Questions - Pipefy

Is there a Pipefy outage?
The current status of Pipefy is: Systems Active
Where can I find the official status page of Pipefy?
The official status page for Pipefy is here
How can I get notified if Pipefy is down or experiencing an outage?
To get notified of any status changes to Pipefy, simply sign up to OutLogger's free monitoring service. OutLogger checks the official status of Pipefy every few minutes and will notify you of any changes. You can veiw the status of all your cloud vendors in one dashboard. Sign up here
What does Pipefy do?
Pipefy is a software that automates workflows for HR, Procurement, CS, and other teams with low-code business process automation.

Start monitoring now!

Join OutLogger to be notified when any of your vendors or the components you use experience an outage or down time. Join for free - no credit card required.

Get Started for Free