Nango incident

Degraded logging performance

Minor Resolved View vendor source →

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

Started
Mar 07, 2025, 12:37 AM UTC
Resolved
Mar 07, 2025, 01:30 AM UTC
Duration
53m
Detected by Pingoru
Mar 07, 2025, 12:37 AM UTC

Affected components

Nango Cloud Health

Update timeline

  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.