Nango incident

Downtime

Major Resolved View vendor source →

Nango experienced a major incident on March 3, 2025 affecting Nango Cloud Health, lasting 15m. The incident has been resolved; the full update timeline is below.

Started
Mar 03, 2025, 01:50 PM UTC
Resolved
Mar 03, 2025, 02:05 PM UTC
Duration
15m
Detected by Pingoru
Mar 03, 2025, 01:50 PM UTC

Affected components

Nango Cloud Health

Update timeline

  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.