Nango had 16 outages in the last 2 years totaling 283h 41m of downtime — averaging 0.7 incidents per month.
There were 16 Nango outages since August 11, 2025 totaling 283h 41m of downtime. Each is summarised below — incident details, duration, and resolution information.
Some syncs may be failing to persist records. We are investigating the root cause.
Some syncs may be failing to persist records. We are investigating the root cause.
This issue has been resolved
SSO login is currently failing due to an outage at a third-party authentication provider. Existing sessions and email/password login are unaffected. We're monitoring and will update here with more information.
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.
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.