A fix has been deployed to bypass the failing network resource. All APIs should now be stable.
Posted Apr 29, 2026 - 14:07 UTC
Update
Minor interruptions have to be expected during the incoming deployment of our fix.
Posted Apr 29, 2026 - 12:28 UTC
Update
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.
Posted Apr 29, 2026 - 12:07 UTC
Identified
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.
Posted Apr 29, 2026 - 08:52 UTC
Monitoring
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.
Posted Apr 28, 2026 - 16:04 UTC
Update
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.
Posted Apr 28, 2026 - 14:52 UTC
Update
We are continuing to work on a fix for this issue.
Posted Apr 28, 2026 - 14:39 UTC
Identified
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.