Kontent.ai Outage History
12 incidents recorded over the last 365 days, 12 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.
Every Recorded Kontent.ai Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Oct 20, 2026 | Requests Using the "*.kenticocloud.com" Domain Pattern FailingBetween 13:30 UTC and 16:06 UTC, requests using the deprecated "*.kenticocloud.com" domain pattern failed due to a change made to the domain in the domain name registrar. The change was reverted at around 16:06 UTC, and… | 3h 51m | Resolved |
| Sep 24, 2026 | EU data center projects were encountering issues when saving content itemsWe have resolved the issue affecting content item save operations. The impact was limited to a subset of projects hosted in our EU data center and affected content items containing text or rich text elements with regex… | 40 min | Resolved |
| Sep 16, 2026 | Investigating GraphQL Service DisruptionThe issue affecting our GraphQL service has been resolved. After identifying the root cause, we implemented corrective measures and closely monitored the service to confirm stability. GraphQL functionality has been… | 30 min | Resolved |
| Jul 30, 2026 | Kontent.ai app degradationWe experienced service degradation caused by the abuse of missing validation that overloaded our authentication system. As a result, some clients encountered issues accessing the application for approximately one… | -1464 min | Resolved |
| Jun 26, 2026 | Login Issues Affecting Application AccessThe service has recovered from the issue, and this incident is now resolved. | 3h 8m | Resolved |
| Jun 24, 2026 | Delivery API Returning Outdated Content in AUEAST Data CenterThe incident has been resolved. All affected services, including the Delivery API and webhook notifications, have fully recovered and are operating as expected. | 12h 41m | Resolved |
| Apr 15, 2026 | Delivery API and Preview Delivery API are experiencing partial outage when using excludeElements parameter# Incident summary – Deliver API excludeElements error \(2026-04-15\) ## Summary On 2026-04-15, a change introduced an incompatibility in our content processing that caused some Deliver API requests using the… | 3h 10m | Resolved |
| Feb 18, 2026 | A small number of users experienced CORS errors and HTTP 425 Too Early responses when calling the Delivery API after the latest Chrome updateFollowing 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. | 121h 25m | Resolved |
| Feb 16, 2026 | Delay in Preview Asset Uploads due to Overloaded Preview Storage in the U.S. Data CenterOur development team has implemented a fix, and accessing an asset via its preview URL after upload is functioning as expected, with minimal delay in processing. | 32h 58m | Resolved |
| Feb 13, 2026 | Delay in Preview Asset Uploads due to Overloaded Preview Storage in the U.S. Data CenterDelays accessing assets by preview URL have resolved. Accessing both published and preview versions of assets is functioning normally. | 54h 0m | Resolved |
| Jan 22, 2026 | Problems With Fastly API Could Cause Stale Content to Be Served to Customers in Some Regions.This incident has been resolved. Ultimately, the issue stemmed from an error that prevented entities from being deleted in a given database table. All of the failed deletions were manually cleared, and now cache purging… | 2h 53m | Resolved |
| Jan 9, 2026 | Support Chat (Intercom) Outage# **Intercom Outage** There was an interval of time \(approximately from 3:00pm - 4:25pm EST\) in which customers were unable to reach the [Kontent.ai](http://Kontent.ai) Support team via chat due to an issue with… | 1h 11m | Resolved |
Hear about the next one while it is open
Everything above is a record written after the fact. We can email you when the next Kontent.ai incident opens instead, at the point where knowing still changes what you do.
Free, no password, no card. Unsubscribe in one click.
How to Read This Kontent.ai Incident Log
Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Kontent.ai acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.
Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.
The longest single Kontent.ai outage in this window ran 5d 1h, against a mean recovery of 21h 30m. If you depend on Kontent.ai in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.