Company Logo

Is there an Pipefy outage?

Pipefy status: Systems Active

Last checked: 9 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 0 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: June 4, 2024, 5:36 p.m.
    Status: Postmortem
    Update: **Root Cause** The issue was caused by a lack of validation in the API mutation regarding the blank value sent, which led to a lag on data replication. **Resolution** A rollback to the previous version of data replication process was performed. A long-term solution involves fixing the field to handle invalid values and redeploying the new flow. **Action Plan** We'll handle the validation of invalid values, and improve our monitoring system related to events like these.
  • Time: June 4, 2024, 12:11 a.m.
    Status: Resolved
    Update: The fix has been applied, and the filters are now working fine.
  • Time: June 3, 2024, 11:17 p.m.
    Status: Monitoring
    Update: A fix has been applied, and we're now monitoring.
  • Time: June 3, 2024, 10:28 p.m.
    Status: Identified
    Update: We've identified the issue occurs only to a few customer and not the whole base, along with we have found the root cause and we are implementing a fix for it.
  • Time: June 3, 2024, 9:20 p.m.
    Status: Investigating
    Update: We are currently investigating this issue.

Updates:

  • Time: May 29, 2024, 1:50 p.m.
    Status: Postmortem
    Update: **Root Cause** our autoscaler experienced a prolonged restart process, causing other components of the system to fail to scale appropriately in response to platform usage. This resulted in a degradation of platform performance, impacting user experience. **Resolution** Initial steps involved manual scaling to improve performance. Further investigation led to adjustments in system parameters for stability. **Action Plan** A monitoring system will be developed to oversee scaling operations, ensuring smoother platform performance.
  • Time: May 27, 2024, 1:38 p.m.
    Status: Resolved
    Update: The incident has been successfully resolved.
  • Time: May 27, 2024, 1:28 p.m.
    Status: Monitoring
    Update: We've applied the fix, and we're now monitoring it.
  • Time: May 27, 2024, 1:20 p.m.
    Status: Identified
    Update: We've identified the cause of the issue, and we're now arranging the fix.
  • Time: May 27, 2024, 1:15 p.m.
    Status: Investigating
    Update: We are currently investigating this issue.

Updates:

  • Time: May 28, 2024, 2:37 p.m.
    Status: Postmortem
    Update: **Root Cause** The issue was due to a deactivated SSL certificate, impacting our website's availability. Unfortunately, specific details are unavailable due to data retention policies. **Resolution** The resolution involved reactivating the SSL certificate to restore service. **Action Plan** We've completed a contingency plan to ensure service continuity and implemented a monitoring system for certificate expiration to maintain secure, uninterrupted service.
  • Time: May 24, 2024, 12:16 p.m.
    Status: Resolved
    Update: The fix has been applied, and after our monitoring and checking everything is back to normal
  • Time: May 24, 2024, 12:07 p.m.
    Status: Monitoring
    Update: Fix has been applied, and we're now monitoring it.
  • Time: May 24, 2024, noon
    Status: Identified
    Update: We've already identified the issue, and the team is working on resolving it as quickly as possible.
  • Time: May 24, 2024, 11:29 a.m.
    Status: Investigating
    Update: We are currently investigating the issue
  • Time: May 24, 2024, 11:11 a.m.
    Status: Investigating
    Update: Pipefy website (pipefy.com) is offline. The app (app.pipefy.com) is working normally.

Updates:

  • Time: May 27, 2024, 6:31 p.m.
    Status: Postmortem
    Update: **Root Cause** During the setup of our connection manager, the specified image in the configuration file was not present in the container registry. Consequently, when attempting to launch pods, they encountered issues due to the unavailability of the required image. **Resolution** The issue was resolved by reverting to previous settings, improving the changes in settings process to ensure stability. **Action Plan** All necessary details within the connection manager setup have been arranged to facilitate future deployments.
  • Time: May 22, 2024, 2:33 p.m.
    Status: Resolved
    Update: This incident has been resolved.
  • Time: May 22, 2024, 2:26 p.m.
    Status: Monitoring
    Update: A fix has been implemented and we are monitoring the results.
  • Time: May 22, 2024, 2:24 p.m.
    Status: Identified
    Update: We are continuing to work on a fix for this issue.
  • Time: May 22, 2024, 2:21 p.m.
    Status: Identified
    Update: We've identified the root cause. Working on the fix.
  • Time: May 22, 2024, 2:18 p.m.
    Status: Investigating
    Update: We are currently investigating this issue.

Updates:

  • Time: May 20, 2024, 5:27 p.m.
    Status: Postmortem
    Update: **Root Cause** A task initiated caused an overload, leading to system slowness. **Resolution** The issue was resolved by removing the source causing the overload and addressing the root cause to prevent future occurrences. **Action Plan** Implemented a solution to block problematic processes and explored enhancements in our process to improve system resilience.
  • Time: May 17, 2024, 1:22 p.m.
    Status: Resolved
    Update: This incident has been successfully resolved. All good!
  • Time: May 17, 2024, 1:15 p.m.
    Status: Monitoring
    Update: The fix has been applied, and we're now monitoring the post-action events.
  • Time: May 17, 2024, 1:05 p.m.
    Status: Identified
    Update: We've identified the reason, and we're working on the fix. Automations may have a delay of 1 minute to run.
  • Time: May 17, 2024, 12:49 p.m.
    Status: Investigating
    Update: We are currently investigating the issue

Check the status of similar companies and alternatives to Pipefy

Avalara
Avalara

Systems Active

Crisis Text Line
Crisis Text Line

Systems Active

Jamf
Jamf

Systems Active

Mulesoft
Mulesoft

Systems Active

Meltwater
Meltwater

Systems Active

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.