Nango Outage History

This issue has been mitigated. We are now investigating the root cause and will update here when complete.

POSTMORTEM: A recent change caused the execution of all functions (actions, webhooks, syncs) to stop on Friday October 2nd between 17:22 and 17:54 UTC. We identified a performance regression introduced by a recent query refactor in our task scheduler. The change caused one database query to scale poorly when the number of fresh execution increased significantly. Under normal load, the query remained fast, which is why the issue was not immediately visible after deployment. 8 hours later, a spike in queued tasks triggered the inefficient execution path, increasing database work and causing the dequeuing query to time out. We have since corrected the query and are adding additional safeguards, including additional monitoring to reduce the likelihood of similar regressions in the future.

Issues which were impacting SSO login have been addressed by the third-party integration. We have seen full recovery of the SSO login flow for the last 10–20 minutes.

The issue was an internal telemetry ingestion delay. Function executions were not affected at all. No customers were impacted.

This issue has bee resolved.

Systems fully recovered

Metrics have recovered. Likely due to the Cloudflare incident mitigation.