Previous incidents

Everything is back to normal.

OAuth token refresh operations have recovered. Details on the Slack community's #incidents channel: https://nango.dev/slack.

Records saving is now fully operational

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

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.

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.