Previous incidents

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

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.

We have identified the root cause, a container image was misconfigured during deployment. Nango services are back to normal.

We have identified the root cause, services are back to normal

The systems seem to have fully recovered over the past 30 minutes. Still investigating the root cuase.

We have identified the root cause, execution is going back to normal.
We are actively monitoring for any regression.