Pipefy incident

Users can't sign in to the system.

Notice Resolved View vendor source →

Pipefy experienced a notice incident on October 22, 2025 affecting Application, lasting 15m. The incident has been resolved; the full update timeline is below.

Started
Oct 22, 2025, 03:20 PM UTC
Resolved
Oct 22, 2025, 03:35 PM UTC
Duration
15m
Detected by Pingoru
Oct 22, 2025, 03:20 PM UTC

Affected components

Application

Update timeline

  1. investigating Oct 22, 2025, 03:20 PM UTC

    We are currently investigating this issue. Already logged-in users can continue using the system.

  2. identified Oct 22, 2025, 03:29 PM UTC

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

  3. monitoring Oct 22, 2025, 03:33 PM UTC

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

  4. resolved Oct 22, 2025, 03:35 PM UTC

    This incident has been resolved.

  5. postmortem Oct 29, 2025, 05:24 PM UTC

    **Root Cause** The issue was caused by a database instance being unavailable due to a node failure. This led to a large number of open transactions, resulting in errors and preventing users from signing in. **Resolution** The affected node was recycled and restored, allowing users to log in again without further issues. **Action Plan** New alerts have been set up to monitor errors related to open transactions. Further investigation will be conducted to understand why these transactions were left open, and regular maintenance will be performed to prevent them from remaining unresolved.