Is there an Pipefy outage?
Pipefy status: Systems Active
Last checked: 6 minutes ago
Get notified about any outages, downtime or incidents for Pipefy and 1800+ other cloud vendors. Monitor 10 companies, for free.
Last checked: 6 minutes ago
Get notified about any outages, downtime or incidents for Pipefy and 1800+ other cloud vendors. Monitor 10 companies, for free.
Outage and incident data over the last 30 days for Pipefy.
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 NowOutlogger tracks the status of these components for Xero:
| 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 |
| Apps | 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 |
| Components | 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 |
| Pipefy website | Active |
| Pricing | Active |
| Signup | Active |
| Template store | Active |
View the latest incidents for Pipefy and check for official updates:
Description: **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.
Status: Postmortem
Impact: Critical | Started At: Aug. 16, 2024, 3:09 p.m.
Description: **Root Cause** The delay occurred because we failed to process a specific update, which was unable to be sent to the queue that later goes to the external system. This happened due to a connection field being incorrectly updated through the API. **Resolution** As several updates were taking place during the incident, we had to implement a solution in the application to deal with this exception. Essentially, the payload size is now validated before being sent to the queue, which solved the problem during the incident. Other actions have been mapped for further analysis. **Action Plan** We will create a disaster recovery process and resume discussion on alarm systems.
Status: Postmortem
Impact: Minor | Started At: Aug. 4, 2024, 1:25 p.m.
Description: **Root Cause** The reports stopped generating because we hit a limit in our data system. This happened because we didn't close the data search when an error occurred. The error was due to a problem with how numbers were being read, as some fields were text and not numbers, causing the search to remain open. **Resolution** We increased the data search size. Additionally, we reverted the code to a previous version. **Action Plan** We configured Elasticsearch to handle report data and will implement specific monitoring for reports.
Status: Postmortem
Impact: Major | Started At: Aug. 1, 2024, 12:04 a.m.
Description: **Root Cause** The outage was caused by emergency maintenance on a Third-party service that manages our data processing system. **Resolution** We started investigating the issue and soon after, the Third-party maintenance window was completed, restoring the service. **Action Plan** We initiated an investigation, and the service was restored shortly after. Also, we opened a ticket with the service provider to gather more information.
Status: Postmortem
Impact: Minor | Started At: July 24, 2024, 2:45 p.m.
Description: **Root Cause** The data source used by our apps (reports and filters) became out of sync with the database due to a weekend process required for compliance coupled with database connection issues. **Resolution** We adjusted the syncronization to skip changes from the compliance process and increased its throughput. Subsequently, a manual synchronization of all updated cards was performed to ensure everything was up to date. **Action Plan** Improve alerts to also encompass issues found on the incident, document the changes made for future reference, and improve and streamline the internal process that loads the application during weekends.
Status: Postmortem
Impact: Minor | Started At: July 15, 2024, 5:01 p.m.
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.
