Pipefy incident

Users can't login

Major Resolved View vendor source →

Pipefy experienced a major incident on January 20, 2026 affecting Authentication, lasting 10m. The incident has been resolved; the full update timeline is below.

Started
Jan 20, 2026, 05:03 PM UTC
Resolved
Jan 20, 2026, 05:14 PM UTC
Duration
10m
Detected by Pingoru
Jan 20, 2026, 05:03 PM UTC

Affected components

Authentication

Update timeline

  1. investigating Jan 20, 2026, 05:03 PM UTC

    We are currently investigating this issue.

  2. identified Jan 20, 2026, 05:04 PM UTC

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

  3. monitoring Jan 20, 2026, 05:08 PM UTC

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

  4. resolved Jan 20, 2026, 05:14 PM UTC

    This incident has been resolved.

  5. postmortem Jan 21, 2026, 06:21 PM UTC

    **Root Cause** A sudden surge in login requests led to a failure due to the limited number of available connections for authentication. This caused users to be unable to log in, although those already logged in were not affected. **Resolution** The issue was resolved by rolling out the application after detecting a database failover. This action restored the system's functionality and allowed users to log in again. **Action Plan** We plan to set up alerts for database connections. Monitoring of connection pools will be enhanced. The security team is keeping an eye on suspicious login IP addresses to block them if necessary.