Pipefy incident

Application is down

Critical Resolved View vendor source →

Pipefy experienced a critical incident on May 8, 2026 affecting Application, lasting 22m. The incident has been resolved; the full update timeline is below.

Started
May 08, 2026, 10:37 PM UTC
Resolved
May 08, 2026, 10:59 PM UTC
Duration
22m
Detected by Pingoru
May 08, 2026, 10:37 PM UTC

Affected components

Application

Update timeline

  1. investigating May 08, 2026, 11:02 PM UTC

    We are currently investigating this issue

  2. monitoring May 08, 2026, 11:11 PM UTC

    The application is online, but users may still experience degraded performance or intermittent issues. Our engineering team is closely monitoring system health as we work towards full restoration

  3. resolved May 08, 2026, 11:38 PM UTC

    This incident has been resolved.

  4. postmortem May 12, 2026, 05:38 PM UTC

    **Root Cause** The issue was traced back to a firmware update in a database instance, which led to a failure in the system's ability to switch over to a backup. This caused the main application to go down. **Resolution** The problem was resolved by starting the database on a new healthy instance, restoring the system's functionality. **Action Plan** - To prevent future occurrences, a manual switch-over will be performed before any instance restarts. - Additionally, a maintenance is scheduled for the system update to address the identified bug.