No problems detected.

We've continued monitoring our fix and have not seen a single failure since 2026-01-29 04:28:04 UTC. Response times and connection pool saturation for the US API are also back in a healthy state since then.

We're considering this incident resolved, but we'll be running a diligent post-mortem process in the next days to prevent a similar failure in the future. The overall impact of this has been limited as only a small percentage of API requests for a subset of environments has experienced problems, but this is still not the standard we want to live up to.

To all affected customers: We sincerely apologize for any impact this has had on your production workloads. We'll be working hard to act on the learnings we've made from this incident.

Please don't hesitate to reach out to our team if you, e.g., need support in retrying failed write actions during the time frame.

We've traced the root cause of the connection pool congestion to a slow query on our "/ats/applications" endpoint that's disproportionately affecting a handful of integrations.

We've temporarily reverted these to a slower but compatible query approach and will investigate the performance issue in more detail in the coming days.

We've already seen a greatly reduced number of failures in the past hour before rolling out this fix - in general, only a small percentage of customers were affected overall - but we expect remaining failures to stop in the next half an hour.

We're continuing to monitor the situation to ensure full recovery.

We've identified an issue with the database connection pooling on one of our API services and have deployed an initial mitigation. We've already observed a significant drop in 500 errors before that. We're continuing to investigate the root cause and monitor the mitigation.

Syncs (EU and US) remain unaffected. Customers on the EU region remain unaffected.

We're seeing an elevated rate of 500 API errors affecting some customers across our US region. We're investigating the cause of the issue. EU does not appear to be impacted.