Resolved after 18 hours 42 minutes, affecting Integrations, on April 1, 2026.
**Root Cause** Recently, efforts were made to separate the infrastructure for better handling of increased demand. This led to the failure of previously set exception rules. An update was applied to a specific host or domain without verifying its use in the integration, causing issues. **Resolution** The issue was resolved by modifying the configuration rules on Ipass app. **Action Plan** - An anomaly alert will be created for the Ipass to avoid this scenario happend again in the future
Affected components
Update timeline
- monitoring Apr 02, 2026, 01:15 PM UTC
We have identified that a recent internal infrastructure update caused unexpected rate-limiting on our iPaaS platform, resulting in temporary delays or 429 errors in workflows for the custom integrations. Our Infrastructure team has identified the root cause and successfully applied a fix to restore normal traffic. We're closely monitoring the environment to ensure stability. Normal service operation is expected across all affected organizations.
- resolved Apr 02, 2026, 02:23 PM UTC
This incident has been resolved. Additional information will be provided shortly in our postmortem report.
- postmortem Apr 06, 2026, 07:14 PM UTC
**Root Cause** Recently, efforts were made to separate the infrastructure for better handling of increased demand. This led to the failure of previously set exception rules. An update was applied to a specific host or domain without verifying its use in the integration, causing issues. **Resolution** The issue was resolved by modifying the configuration rules on Ipass app. **Action Plan** - An anomaly alert will be created for the Ipass to avoid this scenario happend again in the future
Your product runs on more than Pipefy
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services