Incidents reported on status page for Nango https://status.nango.dev/ https://d1lppblt9t2x15.cloudfront.net/logos/ce52849abb5a99f83f70bd12ff491ed0.png https://status.nango.dev/ en https://status.nango.dev/incident/965822 Thu, 16 Jul 2026 10:45:00 -0000 https://status.nango.dev/incident/965822#f8b23e9fd33646ce1d6837bcc71db77786d4dcc93a716d548479f95f1e9f917b 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. https://status.nango.dev/incident/965822 Thu, 16 Jul 2026 09:43:00 -0000 https://status.nango.dev/incident/965822#289b353680520eaf453a87b933b15c3c3482e9271ee0670bbca3a89802c2edbe We continue to see problems with SSO logins due to a third-party issue. https://status.nango.dev/incident/965822 Thu, 16 Jul 2026 08:30:00 -0000 https://status.nango.dev/incident/965822#bee44b67244d4d69075fd33a1359d23805bdbe0d2447ee73e9604e8e9dc8cd82 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. https://status.nango.dev/incident/925996 Tue, 16 Jun 2026 21:21:00 -0000 https://status.nango.dev/incident/925996#cf0a2f1378860d636197250c19a2beac1bd5aef6eed569405d6bea2e52176f40 The issue was an internal telemetry ingestion delay. Function executions were not affected at all. No customers were impacted. https://status.nango.dev/incident/925996 Tue, 16 Jun 2026 20:42:00 -0000 https://status.nango.dev/incident/925996#b553ce8582ee1f08c367e99e6615747b57f5732a0f4ab2cf67a3312cd62190f7 We are experiencing an issue executing functions on Nango (actions, syncs, and webhooks). We are currently investigating and will provide updates here. https://status.nango.dev/incident/925856 Tue, 16 Jun 2026 18:10:00 -0000 https://status.nango.dev/incident/925856#6b8f916b3f189f61758a8e1734bd1e4fecf3ae59d4789d09067e4cf894815b59 # 2026-06-11 Incident post-mortem ## Summary On **June 11, 2026**, our jobs service (which runs syncs, actions, and webhooks) became progressively overloaded and then unavailable for a period of roughly **five hours**, with customer impact concentrated in the final ~80 minutes. During this window, actions and syncs were slow, some timed out (failed), and queued work built up before being processed. No data was lost, delayed tasks were retried and worked off once the service recovered. We have fully mitigated the incident and have a concrete plan to prevent recurrence. ## Customer impact - **What:** Elevated latency on actions and syncs, some actions and syncs timed out, webhook and sync processing was delayed as a backlog formed. - **When:** June 11, 2026, from approximately **21:20 UTC** (gradual degradation) to **02:03 UTC** on June 12 (mitigated). The heaviest impact was between ~00:40 and ~02:03 UTC. - **Data integrity:** No data was lost. Delayed work was queued and processed once the service recovered. ## What happened Our processing service was sized with very little spare capacity relative to its normal load. At about 20:00 UTC a first instance stopped responding due to being overloaded. This triggered escalating crash-and-recover waves: when the service came back, each instance immediately picked up the full incoming workload plus the work that had queued during the restart. Because there was little headroom, the instances ran out of CPU faster than they could work through the backlog. Overloaded instances failed their health checks and were automatically restarted by our infrastructure, which returned them to the same overloaded starting point. This created a self-reinforcing loop: each restart left more work queued, which made the next start-up harder, until the service could no longer keep up. ## Resolution We broke the loop by significantly increasing the processing capacity available to the service (raising its scaling ceiling). With more instances sharing the load, each one had enough CPU headroom to pass its health checks, stay running, and work through the backlog. The service returned to normal latency and the queued work was fully processed. ## What we're doing to prevent recurrence - **Right-sizing the service**: increasing its CPU allocation and lowering the threshold at which it scales out, so it always runs with meaningful headroom. We are reviewing our other services for the same pattern. - **Earlier detection**: adding monitoring on the leading indicators (runtime/CPU health, unavailable instances, and scaling-at-maximum) so we catch this class of degradation well before it affects customers. We apologize for the disruption. If you have questions about how this affected you, please reach out. https://status.nango.dev/incident/924827 Mon, 15 Jun 2026 21:28:00 -0000 https://status.nango.dev/incident/924827#c319acaa2af98604aa7ee21bca27702809a432118227a049335f52ea0dddd09c This issue has bee resolved. https://status.nango.dev/incident/924827 Mon, 15 Jun 2026 21:27:00 -0000 https://status.nango.dev/incident/924827#260c3ecd83bb6e3e454cf33afe564c9943f20cdaa581c74eb784cdaa0301ade8 We have identified the root cause of the issue affecting the Connect UI popup and have restored the feature. The popup now closes successfully once a connection is created. We'll continue to monitor closely and will publish a full post-mortem later this week. https://status.nango.dev/incident/924827 Mon, 15 Jun 2026 20:25:00 -0000 https://status.nango.dev/incident/924827#58d32b2802756030de21b89dfcff0172e0d5cb97b6df358354385724a85c935b Nango Connect UI isn't closing when a connection is successfully created. https://status.nango.dev/incident/919924 Mon, 15 Jun 2026 08:09:00 -0000 https://status.nango.dev/incident/919924#bf5562fe4a37c1b7dbfb32321df85495ca757d6d42229359a2c54dffed2d7406 # 2026-06-11 Incident post-mortem ## Summary On June 11, 2026, part of our platform that stores the data produced by syncs began rejecting writes for a subset of syncs over a window of roughly 15 minutes. During this period, affected syncs were unable to save their fetched data and reported failures. The issue was caused by an internal change that was rolled out ahead of the component that still depended on the previous behavior. We have fully mitigated the incident and have a concrete plan to prevent recurrence. ## Customer impact - What: Saving of synced data failed for a portion of syncs. Affected sync runs reported errors and did not store their data during the window. - When: June 11, 2026, from approximately 13:13 UTC (incident start) to 13:30 UTC (mitigated), with full resolution shortly after. - Data integrity: No data was lost. Once the fix was in place, affected syncs resumed saving data normally on their subsequent runs. ## What happened As part of ongoing maintenance, we were retiring something internal that was no longer needed. This was planned as a multi-step rollout: first update everything that relied on it, then remove it. During the rollout, one of those updates was missed. As a result, when the cleanup step was completed, one part of the system was still relying on what had just been removed. This caused the affected writes to fail, and the impacted syncs to error. ## Resolution We applied the missing update, after which the errors stopped immediately. Affected syncs recovered on their next run. ## What we're doing to prevent recurrence - Ensuring changes reach every impacted component: improving our process so that a change in our codebase reliably triggers an update and rollout of all the components it affects, removing the chance of one being left running an older, incompatible version. We apologize for the disruption. If you have questions about how this affected you, please reach out. https://status.nango.dev/incident/921479 Fri, 12 Jun 2026 02:04:00 -0000 https://status.nango.dev/incident/921479#2bdd574c6bd18ed6ab454d6b31d794dd8d2a6f5e979d6f12edff6b03f9ce853c Systems fully recovered https://status.nango.dev/incident/921479 Fri, 12 Jun 2026 01:10:00 -0000 https://status.nango.dev/incident/921479#8bd4c08a9706b9276f2cd2a56cfbda17627c5e21227b2ff4235a308f656a81e8 We have identified and mitigated the root cause of the issue, action and sync run should recover now https://status.nango.dev/incident/921479 Fri, 12 Jun 2026 00:40:00 -0000 https://status.nango.dev/incident/921479#0ecc1e2945c12a8eb17b8f5bef927a49c5017f2c1d11a84acb20e88aec35f3f4 We are investigating a degradation on our action executions https://status.nango.dev/incident/919924 Wed, 10 Jun 2026 13:42:00 -0000 https://status.nango.dev/incident/919924#943834b31df8a14487a8372c2d105b24797f8117ad2b0094469f4edad4ab0613 We have confirmed the incident is now resolved. https://status.nango.dev/incident/919924 Wed, 10 Jun 2026 13:32:00 -0000 https://status.nango.dev/incident/919924#b58a666778b88726302bd51a1f724d4239420cb4a3d694ca23c010f47ed40d47 We have identified the issue and rolled out the fix. We will continue monitoring. https://status.nango.dev/incident/919924 Wed, 10 Jun 2026 13:24:00 -0000 https://status.nango.dev/incident/919924#7b1beb093c9e3f072ef83607244ec4bf3390244dcfb15f53964ec10104cab326 We are currently experiencing degraded performance in Nango syncs. We are currently investigating and will update here. https://status.nango.dev/incident/880914 Wed, 29 Apr 2026 08:25:00 -0000 https://status.nango.dev/incident/880914#ddccc6c41deca46cb5191b8c13c55ea7c2fcde1dd276c04d1d12ba584b7a770a **Post-Incident Summary** Date: 29 April 2026 **Summary** A gradual increase in Records API response payload size eventually exceeded the memory available to the pods serving those requests, causing them to be terminated. As pods were terminated and replaced, the load balancer returned 502 errors for requests routed to them. The growth had been building over several days and was not caught by internal monitoring before a customer reported the issue. **Timeline (UTC)** * Issue began: 24 April, ~12:00 * Reported by customer: 25 April, ~00:00 * Investigation started: 27 April, ~07:00 * Mitigated: 27 April, 15:00 * Resolved: 27 April, 15:00 **Root Cause** The Records API response payload size had been growing gradually for several days. Once the payloads crossed the available pod memory headroom, the pods serving those requests began being terminated for exceeding memory limits. As terminated pods were replaced, the load balancer returned 502 errors for requests routed to pods that were shutting down or starting up. The growth was gradual rather than sudden, which meant our internal monitoring did not flag it before user-visible errors occurred. Diagnosis was also slowed because the default per-pod memory view smoothed out the underlying spikes, masking the memory-pressure pattern until the smoothing was removed and pod termination state was inspected directly. **Resolution** Per-pod memory limits on the affected service were increased, restoring headroom for the larger payloads and stopping the terminations. Once the new limits were in place, the load balancer stopped returning 502s and the service returned to normal. **Follow-Up Actions** Detection A monitor now pages the on-call team when load-balancer 5XX rates rise, so future user-impacting issues are caught immediately rather than relying on customer reports. System safeguards Bound peak memory per Records API request so response sizes cannot pressure pod memory. Improve telemetry around per-request response size so unusual growth surfaces in monitoring before it impacts users. https://status.nango.dev/incident/880914 Mon, 27 Apr 2026 14:59:00 -0000 https://status.nango.dev/incident/880914#3359184ccf373e0f54e90d7f410217a9f0553b7e747a92e59515d4cd4531ba47 This has now been resolved. https://status.nango.dev/incident/880914 Mon, 27 Apr 2026 12:16:00 -0000 https://status.nango.dev/incident/880914#61f76e3a01bce8ae89c0449df47981c739e3748ef09ced487f36941dcef5019d We are experiencing an increase in 502s on our public API. We believe we have found the cause and are preparing a release to resolve it. https://status.nango.dev/incident/869794 Tue, 14 Apr 2026 08:00:00 -0000 https://status.nango.dev/incident/869794#aae493e55b4535be22b290a34dd0aa5bec20423418b22766d0619ad905efc45b **Post-Incident Summary** Date: 12 April 2026 Impact: Degraded sync execution and delayed actions and webhook processing Status: Resolved **Summary** A webhook flood originating from a single customer environment caused one of our databases to saturate, resulting in broad degradation of asynchronous job processing. Sync execution dropped to near zero, and a large portion of actions and webhook-driven work were delayed or unable to run. A secondary bug in the scheduling system amplified the incident and blocked two consecutive recovery attempts before a fix was deployed. **Timeline (UTC)** * Issue began: 07:00 * Detected by monitoring: 07:00 * Status page updated: 07:00 * Mitigated: 15:30 * Resolved: 15:55 **Root Cause** A single customer environment generated a sustained webhook flood, well above the typical baseline. Each incoming webhook triggered a database query to check the current queue depth for that customer's group before deciding whether to admit a new task. Under flood conditions, this query saturated one of our databases' CPU, preventing other work — including syncs and actions from all customers — from being scheduled or processed. Once the per-group queue cap was reached, new work could no longer be enqueued, and the system remained effectively stalled. Recovery was complicated by a separate bug in the recurring schedule path. When the scheduler encountered a group that had already hit the queue cap, an error in the code caused the exception to be swallowed silently. As a result, affected schedules were never marked as processed and were repeatedly retried on each scheduler tick, adding further load to an already saturated database. This caused two consecutive recovery attempts to fail. **Resolution** * A fix was deployed to correct the scheduling bug, ensuring that capped groups are handled correctly and schedules are properly advanced after each pass. * Task execution times were shifted forward in bulk to drain pressure from the database, then restored in batches. * Once the backlog cleared, the system returned to a healthy state and full processing resumed by 15:55 UTC. **Follow-Up Actions** *System safeguards* * Improve the current per-enqueue queue-depth admission-control mechanism to reduce database load under flood conditions. * Define a rate limiting and load shedding strategy for webhook ingestion to protect the platform when a single customer generates sustained enqueue pressure. * Fix the scheduling bug to correctly handle capped groups without silent failures (completed). https://status.nango.dev/incident/869794 Sun, 12 Apr 2026 15:55:00 -0000 https://status.nango.dev/incident/869794#2986d0a892fb85e91c1438769068808ec474fadaeb450a34243c71b6a8efdd36 We are seeing full recovery over the last 10 minutes and will continue monitoring our metrics. https://status.nango.dev/incident/869794 Sun, 12 Apr 2026 15:37:00 -0000 https://status.nango.dev/incident/869794#620fdf1a47935457a2792e42c92e07bc94f07409261697a81d1110eb1c246e3b We have found an infrastructure issue that may have been preventing recovery and have already fixed it. We are seeing partial recovery on syncs and actions and continue moving traffic over to bring the system to full recovery. https://status.nango.dev/incident/869794 Sun, 12 Apr 2026 14:45:00 -0000 https://status.nango.dev/incident/869794#5754050f9ef88f601308facb0d8f32676f5201bba2f7627541027353967b033e We have not yet fully recovered as some underlying infrastructure issues caused by high load have not been fully addressed. We are working towards a solution to fully reduce the load. https://status.nango.dev/incident/869794 Sun, 12 Apr 2026 13:13:00 -0000 https://status.nango.dev/incident/869794#bfec5d26bad50f74797f57a9cffd8f5e456ab3c1338142638d474b1937db9468 We are still seeing partial recovery for actions and syncs but are still working towards a full recovery. https://status.nango.dev/incident/869794 Sun, 12 Apr 2026 12:01:00 -0000 https://status.nango.dev/incident/869794#b534c0701e4b439862d0f66a6fcb5630cdade84888c7da667c0948b487714fdf We are seeing some partial recovery for actions but syncs remain fully impacted. We are working on reducing the load in one of our infrastructure components. https://status.nango.dev/incident/869794 Sun, 12 Apr 2026 10:50:00 -0000 https://status.nango.dev/incident/869794#0d10e8d0dd7869080f3347fb82802364dab036d0683940168193735910489a4f Syncs and actions remain impacted. We've identified a load-related issue in our infrastructure and are actively working on mitigation. https://status.nango.dev/incident/869794 Sun, 12 Apr 2026 09:49:00 -0000 https://status.nango.dev/incident/869794#8a14b383c50fb4f687a278f19316bd1fba4a78c8f3a1fdac5219bc4de727e713 We have deployed a first step to mitigate the issue but are not seeing recovery yet; we continue investigating how to speed up recovery. https://status.nango.dev/incident/869794 Sun, 12 Apr 2026 09:05:00 -0000 https://status.nango.dev/incident/869794#815c03d4b06aae19f4e2b7852a94077ab09db62fd6fdf1288fa69dc9a1be51ea We are still investigating the issues impacting syncs and actions, and working on early mitigation steps. https://status.nango.dev/incident/869794 Sun, 12 Apr 2026 08:00:00 -0000 https://status.nango.dev/incident/869794#8ac9becfcdb2b9ccf362a0befe8b19c2ee2088a6a14d8788bed1287831ae2d2c Syncs are still delayed, while actions appear unaffected. The issue seems to be related to how the database is handling sync schedules. Once sync processing recovers, synced data will catch up automatically. https://status.nango.dev/incident/841469 Thu, 05 Mar 2026 16:15:00 -0000 https://status.nango.dev/incident/841469#68ebb6ebb5aec180c4b728df2cf4aa78c409531728f74b88fedf3e3ad6bd3349 Functions recovered. Post mortem: # Post-Incident Summary **Date:** 6 March 2026 **Impact:** Degraded function execution for actions and webhooks **Status:** Resolved --- ## Summary A bug in the task scheduling system disabled per-environment concurrency limits, allowing a single tenant to generate an unbounded burst of invocations. At the same time, the tenant’s functions were significantly longer running than typical workloads (120–150 seconds), which caused execution environments to remain occupied for extended periods. As the burst of tasks exceeded the rate at which execution environments became available, a backlog formed in the asynchronous invocation queue. This backlog increased the age of queued events and introduced elevated action latency. Eventually, queued tasks began exceeding the expiration limits enforced by the task system and expired before execution. Monitoring detected the issue through elevated latency metrics, after which the workload was identified and mitigated. --- ## Timeline (CET) - **Issue began:** 16:00 - **Detected by monitoring / on-call paged:** 16:20 - **Mitigated:** 17:15 --- ## Root Cause A bug in the task system disabled per-environment concurrency limits, allowing a single tenant environment to generate an unbounded burst of invocations. The tenant’s functions were also significantly longer running than typical workloads (120–150 seconds), which meant execution environments remained occupied for extended periods and did not recycle quickly. Because provisioned concurrency was configured with a low maximum, most of the burst traffic was handled by on-demand capacity. While the function runtime continued scaling additional execution environments, the combination of burst traffic and long-running executions caused capacity to ramp more slowly than the incoming workload required. This created a backlog in the asynchronous invocation queue, which increased async event age and action latency. As the backlog grew, queued tasks eventually exceeded the expiration limits enforced by the task system and expired before they could be executed. Detection was delayed because alerting relies on latency averaged over 15-minute windows. --- ## Resolution - The source tenant generating the burst workload was identified and incoming traffic was halted. - Task system throttling logic was fixed to restore per-environment concurrency limits. - After the workload was stopped and backlog drained, function processing returned to normal. All systems were fully operational by **17:15 CET**. --- ## Follow-Up Actions ### System safeguards - Fix the task system throttling bug to ensure per-environment concurrency limits are always enforced (**completed**). ### Capacity & scaling - Increase provisioned concurrency autoscaling limits to better absorb bursts and reduce cold-start spillover. ### Monitoring & alerting - Add alerts for **AsyncEventAge** to detect queue backlogs earlier. - Add alerts for **ProvisionedConcurrencySpilloverInvocations**. - Add anomaly detection on **actions executed per minute / throughput drops**. https://status.nango.dev/incident/841469 Thu, 05 Mar 2026 16:13:00 -0000 https://status.nango.dev/incident/841469#22df041de4e5888307bff99166204ea7d315960c115c96e078d146b471390327 We're implementing a fix that will take effect shortly. Still investigating the root cause. https://status.nango.dev/incident/841469 Thu, 05 Mar 2026 15:05:00 -0000 https://status.nango.dev/incident/841469#538c7e4ec7aced04764c8728aac947af9e02bc28407dd74228db2e4487ab69c3 We are experiencing an issue executing functions on Nango (actions, syncs, and webhooks). We are currently investigating and will provide updates here. https://status.nango.dev/incident/780617 Fri, 05 Dec 2025 09:16:00 -0000 https://status.nango.dev/incident/780617#bb2c0ed4ca64e9a8fc3b618c939a6fe29a01387a050a9009aa6d8c202daeae81 Metrics have recovered. Likely due to the Cloudflare incident mitigation. https://status.nango.dev/incident/780617 Fri, 05 Dec 2025 09:14:00 -0000 https://status.nango.dev/incident/780617#64cff4ae472d362d7c6f90eb03f0f8a4a5db30d8a023c4616eb5b93060e74dbd We suspect errors are due to external APIs being impacted by the Cloudflare outage, in particular token refreshing. Still investigating. https://status.nango.dev/incident/780617 Fri, 05 Dec 2025 09:10:00 -0000 https://status.nango.dev/incident/780617#0366a4d336cc81cffabbbd006987542009ecc530f0037663e1af4c5603a4a6b3 We're seeing elevated error rates for function executions, both actions & syncs. Investigating. https://status.nango.dev/incident/742079 Sun, 12 Oct 2025 09:42:00 -0000 https://status.nango.dev/incident/742079#d3a274f2583ed1dc0d589f13e809758ecd3f64c57932ad14644895e7c8bdb3eb All syncs have caught up. https://status.nango.dev/incident/742079 Sun, 12 Oct 2025 08:53:00 -0000 https://status.nango.dev/incident/742079#40dd41834ba6034e2fba934972d99dd4591b17ebe98a23e3c9cc1b1d6e77750e The Nango syncs are delayed as we catchup with the processing that was missed during the maintenance period. Please be patient, we will provide updates here. https://status.nango.dev/incident/728926 Sun, 12 Oct 2025 06:00:15 -0000 https://status.nango.dev/incident/728926#a97f166866f9857d25eb035110d20ed4bd0c257459829b3bf092396fabf4536f This is an exceptional downtime which completes our migration to a new cloud provider (AWS). We expect the downtime to take between 1 and 3 hours. https://status.nango.dev/incident/738638 Tue, 07 Oct 2025 09:02:00 -0000 https://status.nango.dev/incident/738638#6a95a1a438ad147e55f071f5b1ecdc239a96a7d2fe3464d35a3c32ff92affd4b **Post-Incident Summary — Database Lock Contention and Service Outage** **Date:** 6 October 2025 **Impact:** Temporary outage of Nango services **Status:** Resolved **Summary** A **sustained, high-volume workload** from a downstream integration generated a large number of webhook events over an extended period. The follow-on fetches (getRecords) executed concurrently at scale, and a small update in that code path (persisting a “last fetched” timestamp) created heavy database contention. Lock saturation and connection exhaustion led to elevated latencies and 499 responses across public APIs until mitigations were applied. **Timeline (CET)** - **Issue began:** 19:21 - **Detected by monitoring:** 19:37 - **Mitigated:** 20:35 - **Fully resolved:** 23:17 **Root Cause** The getRecords flow includes a database write to persist a “last fetched” timestamp. Under extreme concurrency, these updates serialized and waited on one another, creating widespread lock contention. As locks piled up, available connections were exhausted, which introduced long response times and impacted all Nango services. **Resolution** - Logs and metrics showed elevated lock waits and deadlock messages (over 18,000 waiting operations at peak). - High-load webhook sources were temporarily disabled to shed database work, after which services recovered to normal. - The “last fetched” update in getRecords was determined to be unnecessary and **removed** to eliminate this contention pattern. All systems were fully operational by **20:35 CET**. **Follow-Up Actions** - Rate limiting on webhook endpoints. - More controls to limit the blast-radius of isolated single-tenant spikes. - Enhanced observability for lock growth and connection-pool saturation to enable earlier, automated mitigation. https://status.nango.dev/incident/738638 Mon, 06 Oct 2025 19:13:00 -0000 https://status.nango.dev/incident/738638#ece73e9b09eb7ece7f1705834e50c3a82047b3eea5f561a0641adc4463d6ff4f Nango services are up and running again. We will follow up with a postmortem here. https://status.nango.dev/incident/738638 Mon, 06 Oct 2025 18:35:00 -0000 https://status.nango.dev/incident/738638#e6d1503d2347492cc20fd4742ae78bd89c0cd06fa8d85f63ba71c0a35a7f2926 It looks like we are back but still monitoring the situation and will provide further updates. https://status.nango.dev/incident/738638 Mon, 06 Oct 2025 18:19:00 -0000 https://status.nango.dev/incident/738638#67cfbfb2b83be15380fdfe57ab939517768e8f8c3042155115de5a70a7b76ee5 We have a lead on the route cause and working on restoring services asap. https://status.nango.dev/incident/738638 Mon, 06 Oct 2025 17:22:00 -0000 https://status.nango.dev/incident/738638#d71709910abefcee214d1a453f2df86df1c9f705cfb12916643caacbe373fef8 Nango is experiencing problems and we are investigating. https://status.nango.dev/incident/730334 Wed, 24 Sep 2025 19:55:00 -0000 https://status.nango.dev/incident/730334#1126a1b835c4f90a22c821ce50e28d9691bf23e787fd443de249958bdb9d9c60 We have identified and fixed the root cause of this issue and syncs are now operating as normal. https://status.nango.dev/incident/730334 Wed, 24 Sep 2025 09:09:00 -0000 https://status.nango.dev/incident/730334#368053179277e0e54d8f0661c2cee7d64d537e281dfa2ef89a99e05d77ffbb70 Syncs are periodically degraded. We are currently investigating. https://status.nango.dev/incident/730334 Tue, 23 Sep 2025 21:08:00 -0000 https://status.nango.dev/incident/730334#93d7b12266c28de14b6f358edd66ae61cc7be06cf53089801aef13c552de5724 Services are back to normal https://status.nango.dev/incident/730334 Tue, 23 Sep 2025 20:52:00 -0000 https://status.nango.dev/incident/730334#70bb7e4e020826b693b6a5acb1e2ee62683af3d09bdc4cd3a4a606c90579ad71 Syncs are currently running slower than usual. We are investigating. https://status.nango.dev/incident/721261 Tue, 09 Sep 2025 16:51:00 -0000 https://status.nango.dev/incident/721261#44f348ac810fd07ebdc39662003adb1fca96f8698e55ff928d145126316f3792 We have identified the root cause and deployed the fix. Operation back to normal. https://status.nango.dev/incident/721261 Tue, 09 Sep 2025 16:44:00 -0000 https://status.nango.dev/incident/721261#f15108bde9d25629ac67c72a7e989883e4d12f6db7146c1a772084135cfdcc66 We are investigating a wave of actions and syncs failures. https://status.nango.dev/incident/713495 Wed, 27 Aug 2025 14:01:00 -0000 https://status.nango.dev/incident/713495#8d33f3e01bc347ec7ff30dabd7f597adce513575c830861f36771784528f7066 Actions have recovered too, fully recovered. https://status.nango.dev/incident/713495 Wed, 27 Aug 2025 13:42:00 -0000 https://status.nango.dev/incident/713495#85747185056efc9d6b1e96af213711e4272182404d1fe8e57b6b995e306609d4 Actions are still degraded, the rest has recovered. https://status.nango.dev/incident/713495 Wed, 27 Aug 2025 13:28:00 -0000 https://status.nango.dev/incident/713495#faa39c5a6831d8b6df49e598b8e1160e4cd3a826a51e69c8910410b8d14e5ac9 Higher latency & failure rates for some operations. https://status.nango.dev/incident/704868 Wed, 13 Aug 2025 14:33:00 -0000 https://status.nango.dev/incident/704868#c5e4202612b57597088dea3f1c73a3f1f33811595f6ac39532fc21a669832c1c This issue has been resolved, and operations should be back to normal. https://status.nango.dev/incident/704868 Tue, 12 Aug 2025 22:06:00 -0000 https://status.nango.dev/incident/704868#0a7ffb4f8332979a1c784b0bfa9429d405c277609626f74d70b5b8338679a0f1 We have a mitigation in place and will be monitoring it over the next few hours. https://status.nango.dev/incident/704868 Tue, 12 Aug 2025 12:04:00 -0000 https://status.nango.dev/incident/704868#ff1f257b14545c1519363c34126388fddefc8af0fa5ae2112a7d0021f586803a 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. https://status.nango.dev/incident/704345 Mon, 11 Aug 2025 17:17:00 -0000 https://status.nango.dev/incident/704345#e82f241b18d4c87df6948fa3f219cee4a91d60d19012072c1de5a184459dccfc This issue has been resolved and operations should be back to normal. https://status.nango.dev/incident/704345 Mon, 11 Aug 2025 16:08:00 -0000 https://status.nango.dev/incident/704345#fc5ef54bb30ef9e69c34bb16ddfdd925ac2aaff2b37fef85645d06fdd085a10b We are currently experiencing an issue with saving of sync records and are currently investigating. Updates to follow. https://status.nango.dev/incident/621517 Thu, 17 Jul 2025 17:05:00 -0000 https://status.nango.dev/incident/621517#cbaa14d8fd9d8446c696f8cf5a292deb748fe74774dcc9e0f1d32c6f48164986 Slows actions & syncs. Root cause: burst of actions with large payloads. Mitigation: putting more stringent limitations on action payloads and optimize payload serialization. https://status.nango.dev/incident/621517 Thu, 17 Jul 2025 16:45:00 -0000 https://status.nango.dev/incident/621517#5f272fe48e2ff2d48087e59879479ad3e1f0a4f3e759eaf4b807cdc48424fe8c Slows actions & syncs, investigating. https://status.nango.dev/incident/618059 Tue, 15 Jul 2025 14:00:40 -0000 https://status.nango.dev/incident/618059#693390332992512de78804074fab93563204d72813801c8a05c8afb9a53c94e3 We will be performing a planned database upgrade to improve system performance, reliability, and scalability. This should only take a few minutes and the UI and API will be unavailable during this time. https://status.nango.dev/incident/619909 Tue, 15 Jul 2025 10:30:00 -0000 https://status.nango.dev/incident/619909#cf4cc2908806af71e594ecb4e954b4f8f83d2e48a5dafc23c46eb64caf15578a Heartbeat timeouts have ceased. We're investigating the root cause. https://status.nango.dev/incident/619909 Tue, 15 Jul 2025 07:52:00 -0000 https://status.nango.dev/incident/619909#5a048bf4ebc8242050bc0162e6d65b0afef95484d9ff999b60123fb8979f7c6b ⚠️ We are investigating intermittent heartbeat timeouts in our task and scheduling infrastructure. This may affect background processing and certain API endpoints. Updates to follow. https://status.nango.dev/incident/605155 Tue, 24 Jun 2025 14:00:28 -0000 https://status.nango.dev/incident/605155#6ee4201604b3d15e6c8e53c73ae5bfae214447d5b8145c4d009d3ddba4e354b4 Our provider, Render, will perform maintenance on our databases on June 24rd, 2025 at 10:00 AM EST. The UI and the API will be unavailable for a few minutes. https://status.nango.dev/incident/561025 Mon, 12 May 2025 18:20:00 -0000 https://status.nango.dev/incident/561025#814d97848e321b5b3b2a5a2ed9ba7e540c6a818a025e1bd2784f9dac4ecdc0db Everything is back to normal. https://status.nango.dev/incident/561025 Mon, 12 May 2025 18:15:00 -0000 https://status.nango.dev/incident/561025#b1247b31eb298883553e0ec6b8545767d7a6d9a34f37de76bf6cfe060f0924e7 We have identified the issue, scripts are slowly executing again. We are continuously monitoring the situation https://status.nango.dev/incident/561025 Mon, 12 May 2025 17:35:00 -0000 https://status.nango.dev/incident/561025#664c9b9fa69d9870507ca034a1e29cf989f202b3af595e6ca43418e4bc7aaa94 Syncs and actions are not processing correctly. We are investigating. https://status.nango.dev/incident/557538 Tue, 06 May 2025 11:30:00 -0000 https://status.nango.dev/incident/557538#76b576d40e9ae051af97a3932af7e473f6adc97d4438d4d9532da52c65b2fcf7 OAuth token refresh operations have recovered. Details on the Slack community's #incidents channel: https://nango.dev/slack. https://status.nango.dev/incident/557538 Tue, 06 May 2025 10:05:00 -0000 https://status.nango.dev/incident/557538#ff217dba7f311deb749ea7f43ac1440e6ab2fdd3f466d056fffc61d2bad6195c OAuth token refresh operations are failing. https://status.nango.dev/incident/553218 Mon, 28 Apr 2025 15:15:00 -0000 https://status.nango.dev/incident/553218#5e465b7e10324c36ef6c1a13cbc05c8f9c27fcf9ed8ced3df6ea8ce3b90c5e70 Records saving is now fully operational https://status.nango.dev/incident/553218 Mon, 28 Apr 2025 15:11:00 -0000 https://status.nango.dev/incident/553218#1e7f961aaa62c2f01298262f32e556f2f19ec87645f4028ca15ef57cc5c2a981 A maintenance operation of our records database caused some records saving operations to failed, resulting in erroring syncs. https://status.nango.dev/incident/535577 Wed, 02 Apr 2025 13:30:13 -0000 https://status.nango.dev/incident/535577#1c481c16f58a2c0b96469183767f246c2f99e4098121d5b9e4355eedcc23a7b4 We will be performing planned maintenance on April 2nd, 2025 at 15:30 CEST (9:30 EDT), affecting both the API and Dashboard services. We are migrating our service and certificates to a more robust system. This maintenance should last between 1 and 2 minutes. During this period, all services will be unavailable and will return either SSL errors or 502 errors. Syncs and actions may be affected if they attempt to reach the API. https://status.nango.dev/incident/528923 Tue, 18 Mar 2025 14:35:00 -0000 https://status.nango.dev/incident/528923#09e4ece68458de1fab0775b00958987bd328456616efc42f2b733acd4e08436e Slack Notifications are now enabled again. Thank you for your patience https://status.nango.dev/incident/528923 Sun, 16 Mar 2025 02:48:00 -0000 https://status.nango.dev/incident/528923#e084be0c59bfabe2da00e0863b260df11de301b6fd1ade515609fb5bda3839cd 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 https://status.nango.dev/incident/524005 Fri, 07 Mar 2025 01:30:00 -0000 https://status.nango.dev/incident/524005#9feeffc1a3f4ace4e9bfc5f6d3e5dfff1719a7ed7fb9fb9e43d82193026d43e4 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. https://status.nango.dev/incident/524005 Fri, 07 Mar 2025 00:37:00 -0000 https://status.nango.dev/incident/524005#717db09142a2640986096c1f105521a6d97c06c9ad30366a072d6870f7c86149 Our platform logging system is experiencing some slowdown and intermittent failure, resulting in lost messages. We are investigating. https://status.nango.dev/incident/521943 Mon, 03 Mar 2025 14:05:00 -0000 https://status.nango.dev/incident/521943#a5844db7d60fda02f4447cbef7de625de89919386a66d8955fcf58b6393c33ad 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. https://status.nango.dev/incident/521943 Mon, 03 Mar 2025 13:50:00 -0000 https://status.nango.dev/incident/521943#94dd98ab141d4194c6f58613d9176f2bee0c65fc0197a82ab5f7ab4bcd0cdbee Downtime: API/dashboard down, syncs/actions errors. https://status.nango.dev/incident/518911 Tue, 25 Feb 2025 21:06:00 -0000 https://status.nango.dev/incident/518911#9121d319fe819e4642b300914d3a81a8a7340d296c06d987d675e20453018a07 Downtime: resolved. Root cause: Our cloud provider restarted Redis during a scheduled maintenance operation. A race condition bug in Nango's Redis reconnection logic led to the creation of orphans Redis clients that eventually used all available connections, preventing any logic that depends on Redis to run successfully. Mitigation: We fixed our Redis disconnection logic. We're investigating how to recover better from Redis's unavailability. We plan to migrate to a different cloud provider, which doesn't require database maintenance. https://status.nango.dev/incident/518911 Tue, 25 Feb 2025 20:48:00 -0000 https://status.nango.dev/incident/518911#e3432862801eddc0c8ca1b4e1f6d7e4f831964aab6f24c7ca6beed7524748221 Downtime: API/dashboard down, sync/action errors. https://status.nango.dev/incident/517696 Sun, 23 Feb 2025 20:45:00 -0000 https://status.nango.dev/incident/517696#e17a9d22bc4220d6990d02da35946b02b4751de4882fd2b8eac0586349629074 Occasional errors: resolved. Root cause: As we scaled our services horizontally, we exhausted our database connection pool. Mitigation: use a database connection pooler + optimize our database client code to consume less connections. https://status.nango.dev/incident/517696 Sun, 23 Feb 2025 14:00:00 -0000 https://status.nango.dev/incident/517696#361243ca85a2a3ce01908777f2b5c6a6b04447faf3ad02d6ed204f4a79a9a5fe Occasional errors: we're seeing a low % of sync/action errors. https://status.nango.dev/incident/500142 Wed, 22 Jan 2025 15:56:00 -0000 https://status.nango.dev/incident/500142#108a478f6eb5290b0cb3376406f649bdc46b64dde3b4b8ec86a1f037971c3629 We have identified the root cause, a container image was misconfigured during deployment. Nango services are back to normal. https://status.nango.dev/incident/500142 Wed, 22 Jan 2025 15:47:00 -0000 https://status.nango.dev/incident/500142#4860092c4e3cb9b6f5c3f8c2353f8fe6de64f67047b5cbb46642a95a15c28d36 Nango is having issue processing syncs and actions, we are actively looking for the root cause https://status.nango.dev/incident/497467 Fri, 17 Jan 2025 14:24:00 -0000 https://status.nango.dev/incident/497467#bb0ba6b29fb051d6f9a54db97d149c4fb2e747c4fc98f905130f8a109b321833 We have identified the root cause, services are back to normal https://status.nango.dev/incident/497467 Fri, 17 Jan 2025 14:13:00 -0000 https://status.nango.dev/incident/497467#df33fc0aed157dfe9b76f7ccbf11bbdfef1bd3fe1b84766df6121fd005a3b48b A network error is impacting our server, scheduled jobs are unaffected https://status.nango.dev/incident/484979 Sun, 22 Dec 2024 19:10:33 -0000 https://status.nango.dev/incident/484979#a526bf3251635440a79fdc13cd33bcd3e8a0a48fefc4ced0d24e6a91d03be2bc Migrating our database to augment the connection pool. An exhaustion of the pool was the reason for our last incident. https://status.nango.dev/incident/484938 Fri, 20 Dec 2024 15:39:00 -0000 https://status.nango.dev/incident/484938#a3c13ead3bf9ab0e26619d57300b00354c9b463acdbca80810fcf47269529ad6 The systems seem to have fully recovered over the past 30 minutes. Still investigating the root cuase. https://status.nango.dev/incident/484938 Fri, 20 Dec 2024 15:37:00 -0000 https://status.nango.dev/incident/484938#3bc2ea4f84ea7a29004ae4f68c5e237991b0494fe64c62b0c341d430628a8d70 The service is continuing its recovery. We will send an update when the full recovery is confirmed and the root cause is identified. https://status.nango.dev/incident/484938 Fri, 20 Dec 2024 15:27:00 -0000 https://status.nango.dev/incident/484938#47536cb087d21cc3b282d6357630b9d56692b570d3c4753152f35a80d7acf1d2 We are seeing a slight recovery but the root-cause is still not identified. The team is still investigating... https://status.nango.dev/incident/484938 Fri, 20 Dec 2024 14:35:00 -0000 https://status.nango.dev/incident/484938#b2914224dcc4c66c65090caa2c8e5c19627c78c6219903d56729f1855cf63766 Syncs & actions are failing. We are investigating... https://status.nango.dev/incident/473144 Fri, 06 Dec 2024 00:32:00 -0000 https://status.nango.dev/incident/473144#5bc2ed4f46cea3c50eab290e68e87623fab0207fc93a6aca4a0d66b5a08e9b60 We have identified the root cause, execution is going back to normal. We are actively monitoring for any regression. https://status.nango.dev/incident/473144 Thu, 05 Dec 2024 22:12:00 -0000 https://status.nango.dev/incident/473144#d414fea8f113481d96b2d7aaab821fd1d0cc009be96422379d61edaea0ff9994 Jobs execution is slower than normal and execution can timeout. We are investigating the root cause. https://status.nango.dev/incident/467437 Mon, 25 Nov 2024 14:20:00 -0000 https://status.nango.dev/incident/467437#5d86ea55e406bd3595bc61388ba365cc46fe4386f32d892dcb0f5b3a815cea8a Situations was mitigated, investigating the root cause. https://status.nango.dev/incident/467437 Mon, 25 Nov 2024 14:04:00 -0000 https://status.nango.dev/incident/467437#939661da3a2f275b492357407fe9f25f4f437363a73900bdbe52a47b7c1c6391 Actions are failing and syncs are not running. https://status.nango.dev/incident/461513 Thu, 14 Nov 2024 14:30:00 -0000 https://status.nango.dev/incident/461513#cea17953769e2d41fc465ef764b8be6dad1bb42369d300618b1858534664bc3d A service restart solved the issue. The incident started following a short scheduled maintenance of our database provider, after which a service didn't recover. https://status.nango.dev/incident/460956 Thu, 14 Nov 2024 14:00:02 -0000 https://status.nango.dev/incident/460956#0d1b102c66852e7c825d280f312b14aa0671ba0e0c923c7e73e95a127bdc4125 Our provider, Render, will perform maintenance on our database on November 14, 2024 at 9:00 AM EST. This usually takes less than 5 minutes. During this time, the UI and the API will be unavailable. https://status.nango.dev/incident/461513 Thu, 14 Nov 2024 14:00:00 -0000 https://status.nango.dev/incident/461513#5866cdc849291c15c3ebed4f94295413d3527b973d86e5938442c9388d29c0ad 10% of scripts fail to execute (both syncs & actions). https://status.nango.dev/incident/389673 Thu, 27 Jun 2024 12:02:02 -0000 https://status.nango.dev/incident/389673#7967484edf2ef010b1c517949a784e05364391c1dd91162393ebb8f20c4f5603 Maintenance completed https://status.nango.dev/incident/389673 Thu, 27 Jun 2024 12:00:00 -0000 https://status.nango.dev/incident/389673#4ac2783c6d928420a22c3ccc026068291f2b97cb4c312253d99e4363b09f30e1 Our provider, Render, will perform maintenance on our database on June 27, 2024, at 2:00 PM GMT+2. This usually takes less than 5 minutes. During this time, the UI and the API will be unavailable. https://status.nango.dev/incident/387046 Thu, 20 Jun 2024 20:17:00 -0000 https://status.nango.dev/incident/387046#4c57d77f8f03513383fe494aacd6ddefb13b3ef9ac12944af51a40d199debaa9 The root cause of the issue causing syncs slow scheduling has been resolved. Thank you for your patience https://status.nango.dev/incident/387046 Thu, 20 Jun 2024 15:48:00 -0000 https://status.nango.dev/incident/387046#9d136d198ac3aeed5fffd9ab4aba0265155fcb77f8711e9d8860c22a651aa493 We have identified an issue with our syncs scheduling. Operations are still executed but at a slower pace. We have identified and fixed a second issue with our actions execution. https://status.nango.dev/incident/385535 Mon, 17 Jun 2024 15:45:00 -0000 https://status.nango.dev/incident/385535#8ecb04e37b693c988c692b9800d6768b47856148e9602244fbb2c12175816db9 Some requests to the Nango API get back the following error: ENOTFOUND. Cloudflare incident: https://www.cloudflarestatus.com/incidents/55w67hz7kjw5 https://status.nango.dev/incident/385535 Mon, 17 Jun 2024 15:31:00 -0000 https://status.nango.dev/incident/385535#f109d56870b51c1f030b48fa618f126eea2dfee9c5eaa150c7b8275f5aded31d Some requests to the Nango API get back the following error: ENOTFOUND. Cloudflare incident: https://www.cloudflarestatus.com/incidents/55w67hz7kjw5 https://status.nango.dev/incident/346429 Tue, 26 Mar 2024 18:30:00 -0000 https://status.nango.dev/incident/346429#a29b2dbee441d73c05a90dc0ecbcfa0a474bda38c94562f360db282192132524 API/dashboard unavailable: incident resolved. Post mortem: https://nangohq.notion.site/Mar-27-2024-API-dashboard-unavailable-2380b737a43e4ab5a4416102b78b0cdb?pvs=4 https://status.nango.dev/incident/346429 Tue, 26 Mar 2024 18:08:00 -0000 https://status.nango.dev/incident/346429#b0b2a35abb10941a637e2085ebe6aca6361e1c00f69d77053211b012fc9473e3 API/dashboard unavailable: upstream provider estimates it will recover within 1h. https://status.nango.dev/incident/346429 Tue, 26 Mar 2024 16:45:00 -0000 https://status.nango.dev/incident/346429#12f470735ffebe5a47c1aea72656fd3af42fc9b0f1f67535c6f5e5db43aee69a API/dashboard unavailable: our cloud provider outage is still ongoing, we are in contact with them and will send regular updates. https://status.nango.dev/incident/346429 Tue, 26 Mar 2024 16:15:00 -0000 https://status.nango.dev/incident/346429#483d93bd27917d911932b60d4a9aca2c6b54582d775582908c770762acfa9785 API/dashboard unavailable: our cloud provider is experiencing an outage reported on https://status.render.com https://status.nango.dev/incident/330355 Thu, 22 Feb 2024 05:00:00 -0000 https://status.nango.dev/incident/330355#ad1f3a7241d6ad08d0be00e7ed1346e7dbabf7aa03962c7b4df03cce44bce61e Actions & syncs backlogged: issue resolved. https://status.nango.dev/incident/330355 Thu, 22 Feb 2024 01:00:00 -0000 https://status.nango.dev/incident/330355#593e9ac8aad96636553edf4bfaa0074a35ca49266147ef6d6cb40e63cfbd7669 Investigating the root cause. https://status.nango.dev/incident/327131 Thu, 15 Feb 2024 09:00:00 -0000 https://status.nango.dev/incident/327131#2098d2d01c47210f9b8399904ec2da42af2c7ab8db563515c2ae730882e15119 Actions & syncs backlogged: issue resolved. https://status.nango.dev/incident/327131 Wed, 14 Feb 2024 23:30:00 -0000 https://status.nango.dev/incident/327131#1246cf4c982375391d7c66ec8d88d0d4fca38f01d22d74eb144a185d8ac0a045 Actions & syncs backlogged: we're investigating the root cause. https://status.nango.dev/incident/310218 Mon, 08 Jan 2024 17:35:00 -0000 https://status.nango.dev/incident/310218#8be4ccb25c188896130efe3778424c15cdf4d25a47f78131c35e4373ee4e5b62 520 errors: issue resolved (caused by the outage of upstream service [Render](https://status.render.com/incidents/07h4310f6gct), itself caused by the outage of upstream service [Cloudflare](https://www.cloudflarestatus.com/incidents/0lr96pfk333t)) https://status.nango.dev/incident/310218 Mon, 08 Jan 2024 17:30:00 -0000 https://status.nango.dev/incident/310218#74e46ecce77971f0abe647c00b47e489ace663ce4f801231f1007c4602245bc5 520 errors https://status.nango.dev/incident/303420 Thu, 21 Dec 2023 16:55:00 -0000 https://status.nango.dev/incident/303420#0c905c7947031f555df606c95ee84bfc62c45630ee9468f6eaa44cf1ca855d83 Actions & syncs errors: issue resolved (caused by outage of upstream service Render). https://status.nango.dev/incident/303420 Thu, 21 Dec 2023 15:55:00 -0000 https://status.nango.dev/incident/303420#29f175d7845bae905b713d1cacee50629fef66bfdc1778adcf86de2a564d75bf Actions & syncs errors: investigating root cause. https://status.nango.dev/incident/301953 Wed, 13 Dec 2023 16:45:00 -0000 https://status.nango.dev/incident/301953#0c8f6814dc8713c8a467020f48c459bce72293e3db9bb173fd07d310b0e975d3 Server latency: [Post-Mortem](https://nangohq.notion.site/Post-Mortem-Dec-13-Outage-769b18124b914fad8d3ca08ae7b1a571?pvs=4)