Pipefy incident
We identify an issue affect Filters and reports.
Pipefy experienced a minor incident on January 15, 2026 affecting Filters and Reports, lasting 33m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Jan 15, 2026, 02:03 PM UTC
We are currently investigating this issue.
- monitoring Jan 15, 2026, 02:04 PM UTC
The issue was resolved and now we are monitoring the results.
- resolved Jan 15, 2026, 02:28 PM UTC
This incident has been resolved.
- postmortem Jan 20, 2026, 06:32 PM UTC
**Root Cause** We discovered an issue impacting filters and reports due to high memory usage in the database. The exact cause of the memory spike remains unidentified, prompting further investigation. **Resolution** The problem resolved itself without any manual intervention, and systems returned to normal operation. **Action Plan** We plan to enhance the reporting system to better monitor database performance. The team analyzed the situation and decided to optimize sorting methods to prevent future occurrences.