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/ Fri, 06 Jun 2025 18:03:45 +0000 https://status.nango.dev/#c22c4fa2169a725fc095357fe221eaf54acc2ce44ce83a05296a685441068ed3 Nango Cloud Health recovered https://status.nango.dev/ Fri, 06 Jun 2025 18:03:17 +0000 https://status.nango.dev/#c22c4fa2169a725fc095357fe221eaf54acc2ce44ce83a05296a685441068ed3 Nango Cloud Health went down 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:35:13 +0000 https://status.nango.dev/incident/535577#8859535cc47bcd4b022fd48d9708338ff46d549a4ccbf6d6626f8ca0aeb1c89f Maintenance completed https://status.nango.dev/ Wed, 02 Apr 2025 13:31:00 +0000 https://status.nango.dev/#b0ddbb802e23a0b40b703846ef96aa714f15f382b029a1764ce63e9e097ad535 Nango Cloud Health recovered https://status.nango.dev/ Wed, 02 Apr 2025 13:30:32 +0000 https://status.nango.dev/#b0ddbb802e23a0b40b703846ef96aa714f15f382b029a1764ce63e9e097ad535 Nango Cloud Health went down 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 21:15:33 +0000 https://status.nango.dev/incident/484979#ca7ca93def26bbc65e1f7f37621c00ac6d6114f8580685137a81babf238679a3 Maintenance completed 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:05:02 +0000 https://status.nango.dev/incident/460956#2ecfbb723b6f4879f690a97de25ea789f4625030d42c51e5dc70e5faa45bac64 Maintenance completed 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:07:02 -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/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)