Nango had 15 outages in the last 2 years totaling 278h 56m of downtime — averaging 0.6 incidents per month.
There were 15 Nango outages since July 15, 2025 totaling 278h 56m of downtime. Each is summarised below — incident details, duration, and resolution information.
We are experiencing an issue executing functions on Nango (actions, syncs, and webhooks). We are currently investigating and will provide updates here.
The issue was an internal telemetry ingestion delay. Function executions were not affected at all. No customers were impacted.
Nango Connect UI isn't closing when a connection is successfully created.
Nango Connect UI isn't closing when a connection is successfully created.
This issue has bee resolved.
We are investigating a degradation on our action executions
Systems fully recovered
We're seeing elevated error rates for function executions, both actions & syncs. Investigating.
Metrics have recovered. Likely due to the Cloudflare incident mitigation.
Syncs are currently running slower than usual. We are investigating.
We have identified and fixed the root cause of this issue and syncs are now operating as normal.
We are investigating a wave of actions and syncs failures.
We have identified the root cause and deployed the fix. Operation back to normal.
Higher latency & failure rates for some operations.
Actions have recovered too, fully recovered.
A small percentage of sync record saving is failing. These operations are retried and there will be no data loss. We will update the status here regularly as we proceed with our investigation.
This issue has been resolved, and operations should be back to normal.
Slows actions & syncs, investigating.
Slows actions & syncs. Root cause: burst of actions with large payloads. Mitigation: putting more stringent limitations on action payloads and optimize payload serialization.
⚠️ We are investigating intermittent heartbeat timeouts in our task and scheduling infrastructure. This may affect background processing and certain API endpoints. Updates to follow.
Heartbeat timeouts have ceased. We're investigating the root cause.