Pipefy incident

Slowness in Pipefy functionalities

Major Resolved View vendor source →
Started
Feb 14, 2026, 12:43 PM UTC
Resolved
Feb 14, 2026, 02:50 PM UTC
Duration
2h 6m
Detected by Pingoru
Feb 14, 2026, 12:43 PM UTC

Affected components

Advanced ReportsFiltersReports

Update timeline

  1. identified Feb 14, 2026, 12:43 PM UTC

    The issue has been identified and a fix is being implemented.

  2. monitoring Feb 14, 2026, 02:30 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Feb 14, 2026, 02:50 PM UTC

    This incident has been resolved.

  4. postmortem Feb 24, 2026, 06:08 PM UTC

    **Root Cause** We encountered a significant delay due to a high volume of card deletions, which affected the processing queues. **Resolution** The issue with the queues resolved itself without any intervention from the team. The system returned to normal operations on its own with the team supervision. **Action Plan**

Looking to track Pipefy downtime and outages?

Pingoru polls Pipefy's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when Pipefy reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track Pipefy alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring Pipefy for free

5 free monitors · No credit card required