Nango Outage History
Nango is up right nowNango had 16 outages in the last 2 years totaling 225h 20m of downtime — averaging 0.7 incidents per month.
There were 16 Nango outages since March 3, 2025 totaling 225h 20m of downtime. Each is summarised below — incident details, duration, and resolution information.
Degradation in sync executions
Timeline · 2 updates
Function executions are cur...
Timeline · 2 updates
High function errors
Timeline · 2 updates
- investigating Dec 05, 2025, 09:10 AM UTC
We're seeing elevated error rates for function executions, both actions & syncs. Investigating.
- resolved Dec 05, 2025, 09:16 AM UTC
Metrics have recovered. Likely due to the Cloudflare incident mitigation.
Nango is experiencing probl...
Timeline · 2 updates
Degraded performance for syncs
Timeline · 2 updates
- investigating Sep 23, 2025, 08:52 PM UTC
Syncs are currently running slower than usual. We are investigating.
- resolved Sep 24, 2025, 07:55 PM UTC
We have identified and fixed the root cause of this issue and syncs are now operating as normal.
Actions and Syncs degraded.
Timeline · 2 updates
- investigating Sep 09, 2025, 04:44 PM UTC
We are investigating a wave of actions and syncs failures.
- resolved Sep 09, 2025, 04:51 PM UTC
We have identified the root cause and deployed the fix. Operation back to normal.
Higher latency & failure rates
Timeline · 2 updates
- investigating Aug 27, 2025, 01:28 PM UTC
Higher latency & failure rates for some operations.
- resolved Aug 27, 2025, 02:01 PM UTC
Actions have recovered too, fully recovered.
Saving Sync Records Degraded
Timeline · 2 updates
- investigating Aug 12, 2025, 12:04 PM UTC
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.
- resolved Aug 13, 2025, 02:33 PM UTC
This issue has been resolved, and operations should be back to normal.
Slow actions & syncs
Timeline · 2 updates
- investigating Jul 17, 2025, 04:45 PM UTC
Slows actions & syncs, investigating.
- investigating Jul 17, 2025, 05:05 PM UTC
Slows actions & syncs. Root cause: burst of actions with large payloads. Mitigation: putting more stringent limitations on action payloads and optimize payload serialization.
Task Heartbeats Expiring
Timeline · 2 updates
- investigating Jul 15, 2025, 07:52 AM UTC
⚠️ We are investigating intermittent heartbeat timeouts in our task and scheduling infrastructure. This may affect background processing and certain API endpoints. Updates to follow.
- investigating Jul 15, 2025, 10:30 AM UTC
Heartbeat timeouts have ceased. We're investigating the root cause.
Syncs and actions are not p...
Timeline · 2 updates
- investigating May 12, 2025, 05:35 PM UTC
Syncs and actions are not processing correctly. We are investigating.
- resolved May 12, 2025, 06:20 PM UTC
Everything is back to normal.
Refresh token failure
Timeline · 2 updates
- investigating May 06, 2025, 10:05 AM UTC
OAuth token refresh operations are failing.
- resolved May 06, 2025, 11:30 AM UTC
OAuth token refresh operations have recovered. Details on the Slack community's #incidents channel: https://nango.dev/slack.
Slack notifications are dis...
Timeline · 2 updates
- investigating Mar 16, 2025, 02:48 AM UTC
Slack notifications are currently disabled due to a technical issue. Our team is working to restore this functionality as soon as possible. Thank you for your patience
- resolved Mar 18, 2025, 02:35 PM UTC
Slack Notifications are now enabled again. Thank you for your patience
Degraded logging performance
Timeline · 2 updates
- investigating Mar 07, 2025, 12:37 AM UTC
Our platform logging system is experiencing some slowdown and intermittent failure, resulting in lost messages. We are investigating.
- resolved Mar 07, 2025, 01:30 AM UTC
We have identified the root cause of the issue. The sharding for our log database was too small, creating a bottleneck. During the incident, syncs and actions were slower, but logging was not on the critical path. Only some log messages have been lost.
Downtime
Timeline · 2 updates
- investigating Mar 03, 2025, 01:50 PM UTC
Downtime: API/dashboard down, syncs/actions errors.
- resolved Mar 03, 2025, 02:05 PM UTC
Downtime: resolved. Root cause: a table from the main database had grown very large. A database client used for Business Intelligence performed an exact count on this table, locking the database. Mitigation: the database client now points to a read replica. The large table is being cleaned up.