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.
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 |
Features | 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 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.
Status: Postmortem
Impact: Minor | Started At: June 3, 2024, 9:20 p.m.
Description: **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.
Status: Postmortem
Impact: Minor | Started At: May 27, 2024, 1:15 p.m.
Description: **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.
Status: Postmortem
Impact: Critical | Started At: May 24, 2024, 11:11 a.m.
Description: **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.
Status: Postmortem
Impact: Critical | Started At: May 22, 2024, 2:18 p.m.
Description: **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.
Status: Postmortem
Impact: Minor | Started At: May 17, 2024, 12:49 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.