A small number of users experienced CORS errors and HTTP 425 Too Early responses when calling the Delivery API after the latest Chrome update

Update timeline

1. identified Feb 18, 2026, 10:17 AM UTC

   A recent Chrome update (version 145) introduced an issue that may lead to occasional CORS errors and HTTP 425 responses when making Delivery API calls. Our CDN provider and the Chromium team are already investigating the root cause. In the meantime, a simple workaround is to update your front‑end to perform a dummy Delivery API request in the background, ignore its errors, and wait briefly before sending further Delivery API requests. Thanks to this, all the other calls should not be affected. Please note that this does not affect users who are using the latest version of our SDK or have a properly implemented retry policy in their codebase. If you have any questions, feel free to contact our Technical Support Team via chat.

2. identified Feb 18, 2026, 10:25 AM UTC

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

3. monitoring Feb 19, 2026, 12:58 PM UTC

   A workaround has been implemented on our side. The Chromium team is currently testing their fix together with our CDN provider. We are monitoring the situation, and everything should remain fully operational even before their fix is officially released, as our workaround already addresses it.

4. resolved Feb 23, 2026, 11:43 AM UTC

   Following the update implemented by our developers, CORS and HTTP 425 errors no longer occur. After monitoring, we can confirm that the issue is now resolved.