Nango Outage History

Nango is up right now

Nango 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.

Source: https://status.nango.dev

Minor December 5, 2025

High function errors

Detected by Pingoru
Dec 05, 2025, 09:10 AM UTC
Resolved
Dec 05, 2025, 09:16 AM UTC
Duration
6m
Affected: Nango Cloud Health
Timeline · 2 updates
  1. investigating Dec 05, 2025, 09:10 AM UTC

    We're seeing elevated error rates for function executions, both actions & syncs. Investigating.

  2. resolved Dec 05, 2025, 09:16 AM UTC

    Metrics have recovered. Likely due to the Cloudflare incident mitigation.

Read the full incident report →

Minor September 23, 2025

Degraded performance for syncs

Detected by Pingoru
Sep 23, 2025, 08:52 PM UTC
Resolved
Sep 24, 2025, 07:55 PM UTC
Duration
23h 3m
Affected: Nango Cloud Health
Timeline · 2 updates
  1. investigating Sep 23, 2025, 08:52 PM UTC

    Syncs are currently running slower than usual. We are investigating.

  2. 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.

Read the full incident report →

Minor September 9, 2025

Actions and Syncs degraded.

Detected by Pingoru
Sep 09, 2025, 04:44 PM UTC
Resolved
Sep 09, 2025, 04:51 PM UTC
Duration
7m
Affected: Nango Cloud Health
Timeline · 2 updates
  1. investigating Sep 09, 2025, 04:44 PM UTC

    We are investigating a wave of actions and syncs failures.

  2. resolved Sep 09, 2025, 04:51 PM UTC

    We have identified the root cause and deployed the fix. Operation back to normal.

Read the full incident report →

Minor August 27, 2025

Higher latency & failure rates

Detected by Pingoru
Aug 27, 2025, 01:28 PM UTC
Resolved
Aug 27, 2025, 02:01 PM UTC
Duration
33m
Affected: Nango Cloud Health
Timeline · 2 updates
  1. investigating Aug 27, 2025, 01:28 PM UTC

    Higher latency & failure rates for some operations.

  2. resolved Aug 27, 2025, 02:01 PM UTC

    Actions have recovered too, fully recovered.

Read the full incident report →

Minor August 12, 2025

Saving Sync Records Degraded

Detected by Pingoru
Aug 12, 2025, 12:04 PM UTC
Resolved
Aug 13, 2025, 02:33 PM UTC
Duration
1d 2h
Affected: Nango Cloud Health
Timeline · 2 updates
  1. 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.

  2. resolved Aug 13, 2025, 02:33 PM UTC

    This issue has been resolved, and operations should be back to normal.

Read the full incident report →

Minor July 17, 2025

Slow actions & syncs

Detected by Pingoru
Jul 17, 2025, 04:45 PM UTC
Resolved
Jul 17, 2025, 05:05 PM UTC
Duration
20m
Affected: Nango Cloud Health
Timeline · 2 updates
  1. investigating Jul 17, 2025, 04:45 PM UTC

    Slows actions & syncs, investigating.

  2. 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.

Read the full incident report →

Minor July 15, 2025

Task Heartbeats Expiring

Detected by Pingoru
Jul 15, 2025, 07:52 AM UTC
Resolved
Jul 15, 2025, 10:30 AM UTC
Duration
2h 38m
Affected: Nango Cloud Health
Timeline · 2 updates
  1. 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.

  2. investigating Jul 15, 2025, 10:30 AM UTC

    Heartbeat timeouts have ceased. We're investigating the root cause.

Read the full incident report →

Minor May 12, 2025

Syncs and actions are not p...

Detected by Pingoru
May 12, 2025, 05:35 PM UTC
Resolved
May 12, 2025, 06:20 PM UTC
Duration
45m
Affected: Nango Cloud Health
Timeline · 2 updates
  1. investigating May 12, 2025, 05:35 PM UTC

    Syncs and actions are not processing correctly. We are investigating.

  2. resolved May 12, 2025, 06:20 PM UTC

    Everything is back to normal.

Read the full incident report →

Minor May 6, 2025

Refresh token failure

Detected by Pingoru
May 06, 2025, 10:05 AM UTC
Resolved
May 06, 2025, 11:30 AM UTC
Duration
1h 25m
Affected: Nango Cloud Health
Timeline · 2 updates
  1. investigating May 06, 2025, 10:05 AM UTC

    OAuth token refresh operations are failing.

  2. 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.

Read the full incident report →

Minor March 16, 2025

Slack notifications are dis...

Detected by Pingoru
Mar 16, 2025, 02:48 AM UTC
Resolved
Mar 18, 2025, 02:35 PM UTC
Duration
2d 11h
Affected: Nango Cloud Health
Timeline · 2 updates
  1. 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

  2. resolved Mar 18, 2025, 02:35 PM UTC

    Slack Notifications are now enabled again. Thank you for your patience

Read the full incident report →

Minor March 7, 2025

Degraded logging performance

Detected by Pingoru
Mar 07, 2025, 12:37 AM UTC
Resolved
Mar 07, 2025, 01:30 AM UTC
Duration
53m
Affected: Nango Cloud Health
Timeline · 2 updates
  1. 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.

  2. 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.

Read the full incident report →

Major March 3, 2025

Downtime

Detected by Pingoru
Mar 03, 2025, 01:50 PM UTC
Resolved
Mar 03, 2025, 02:05 PM UTC
Duration
15m
Affected: Nango Cloud Health
Timeline · 2 updates
  1. investigating Mar 03, 2025, 01:50 PM UTC

    Downtime: API/dashboard down, syncs/actions errors.

  2. 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.

Read the full incident report →