Outage in Kontent

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

Minor

February 18, 2026 - Started 2 days ago
Official incident page

Incident Report

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.

Components affected

Kontent Content Delivery API Kontent Content Delivery API Kontent Content Delivery API

Need to monitor Kontent outages?

Monitor all your external dependencies in one place
Get instant alerts when outages are detected
Be the first to know if service is down
Show real-time status on private or public status page
Keep your team informed

Start monitoring for free

Latest Updates ( sorted recent to last )

MONITORING about 17 hours ago - at 02/19/2026 12:58PM

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.

IDENTIFIED 2 days ago - at 02/18/2026 10:25AM

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

IDENTIFIED 2 days ago - at 02/18/2026 10:17AM

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.

Latest Kontent outages

Delay in Preview Asset Uploads due to Overloaded Preview Storage in the U.S. Data Center - 4 days ago

Delay in Preview Asset Uploads due to Overloaded Preview Storage in the U.S. Data Center - 7 days ago

Problems With Fastly API Could Cause Stale Content to Be Served to Customers in Some Regions. - 29 days ago

Support Chat (Intercom) Outage - about 1 month ago

Intercom chat tool performance decrease - 4 months ago

The Status Page Aggregator with Early Outage Detection

With IsDown, you can monitor all your critical services' official status pages from one centralized dashboard and receive instant alerts the moment an outage is detected. Say goodbye to constantly checking multiple sites for updates and stay ahead of outages with IsDown.

Start free trial

No credit card required · Cancel anytime · 5850 services available

Integrations with Slack Microsoft Teams Google Chat Datadog PagerDuty Zapier Discord Webhook