API connectivity issues

Update timeline

1. identified Apr 28, 2026, 02:39 PM UTC

   An AWS major incident on the Paris region is causing connectivity issues on our APIs since March, 27th. We're currently trying to mitigate the impact by changing the way we handle our API's network.

2. identified Apr 28, 2026, 02:39 PM UTC

   We are continuing to work on a fix for this issue.

3. identified Apr 28, 2026, 02:52 PM UTC

   A temporary fix is in place to bypass the failing resources. ⚠️ Customers using outbound IP whitelisting to our API are not be able to make their calls anymore for now. Calls relying on FQDN whitelist are not impacted.

4. monitoring Apr 28, 2026, 04:04 PM UTC

   API is now considered as stable. ℹ️ We didn't detected any customers being blocked because of IP whitelisting, but are still closely monitoring API calls to detect them, and may adapt our network later depending on these results and customer requirements.

5. identified Apr 29, 2026, 08:52 AM UTC

   Our fix seems to only have stabilized part of the calls. Customers are still raising connectivity issue this morning, we're investigating on a deeper issue.

6. identified Apr 29, 2026, 12:07 PM UTC

   Incident has be escalated on AWS side. The root cause has been identified, one specific network resource has a flaky health status, causing API calls to randomly fail. We are currently working on a fix to bypass this resource and stabilize our APIs.

7. identified Apr 29, 2026, 12:28 PM UTC

   Minor interruptions have to be expected during the incoming deployment of our fix.

8. monitoring Apr 29, 2026, 02:07 PM UTC

   A fix has been deployed to bypass the failing network resource. All APIs should now be stable.

9. resolved Apr 29, 2026, 04:06 PM UTC

   This incident has been resolved.