Kontentai outage history

We have identified an issue where any requests using the "*.kenticocloud.com" domain pattern are failing due to a DNS-related issue. This includes the Delivery API, Management API, and other requests made within the application itself. Our developers are currently in the process of addressing this, but in the meantime, requests can be changed to use the "kontent.ai" domain instead.

The relevant DNS change for "kenticocloud.com" has now been reverted, and we are monitoring the results. For those using a local DNS resolver, the change may take up to 48 hours to propagate, unless the cache is flushed manually. Only deprecated domains were affected by this issue, and all SDK versions released since the end of 2019 were unaffected.

Between 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 based on our developers' monitoring of the logs and verification of the domain in the domain name registrar, the issue appears to be resolved. No further issues have been observed or reported.

We are currently experiencing a partial performance degradation within the application. Some users may encounter issues when saving content items. Our team is actively investigating the root cause and working to restore normal service as quickly as possible. We apologize for the inconvenience and will provide further updates as soon as more information becomes available.

We have identified the root cause of the issue affecting content item save operations and have implemented corrective measures. The issue was limited to projects in our EU data center and specifically affected content items that contain text or rich text elements with regex validation rules. Service has been restored, and save operations are functioning normally. Our team is actively monitoring the situation to ensure continued stability. We apologize for the inconvenience and appreciate your patience.

We 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 validation. The fix has been successfully deployed, and we have received confirmation from affected customers that save operations are functioning as expected. We will continue to monitor the platform, but the incident is now considered resolved. We apologize for the inconvenience and thank you for your patience.

We are currently investigating an issue affecting our GraphQL service. Our engineering team is actively working to identify the root cause and restore full functionality as quickly as possible. Please note that both the Delivery API and Management API remain fully operational and are unaffected by this issue. We understand the impact this may have and sincerely apologize for the inconvenience. We will provide further updates as soon as more information becomes available. Thank you for your patience and understanding. In case of any questions, do not hesitate to contact our support team via chat or at [email protected]

We have identified the root cause of the issue affecting our GraphQL service and have implemented mitigation measures to restore service functionality. At this time, the GraphQL service is operating as expected, and our team is actively monitoring the situation to ensure stability and confirm that the issue has been fully resolved. Throughout this, the Delivery API and Management API remained fully operational and were not impacted. We sincerely apologize for any inconvenience this disruption may have caused and appreciate your patience while we worked to address the issue. We will continue monitoring closely and provide further updates if necessary.

The 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 fully restored, and we have not observed any further issues. Throughout this incident, the Delivery API and Management API remained fully operational and were not impacted. We sincerely apologize for any inconvenience this disruption may have caused and appreciate your patience and understanding while we worked to resolve the issue.

We 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 hour. Please note that only access to app.kontent.ai was affected. API availability and performance remained unaffected throughout the incident. The impact occurred primarily during two distinct spikes, lasting approximately 5 minutes and 20 minutes, respectively. Our team identified the root cause, mitigated the immediate impact, and is implementing additional safeguards to prevent similar incidents from occurring in the future.

We are currently experiencing issues with user logins to the application. Our development team is actively investigating the problem, and resolving it is our top priority. We apologize for the inconvenience. We will provide updates as soon as more information becomes available. No APIs are affected. Do not hesitate to contact us at support chat with any questions.

Login functionality has been restored, and we are seeing normal service behavior. The issue stemmed from our authentication provider (Auth0) and has since been resolved. We will continue monitoring to confirm stability.

The service has recovered from the issue, and this incident is now resolved.

Changes to content may not be propagating to the Delivery API and Delivery Preview API in the AUEAST data center. Because of this, webhook notifications also may not be sent as expected.

Our developers are still investigating the root cause, but they have implemented a fix, and changes seem to be propagating successfully to the Delivery API. Webhook notifications also seem to be sending successfully.

The incident has been resolved. All affected services, including the Delivery API and webhook notifications, have fully recovered and are operating as expected.

We are currently experiencing a partial outage affecting the Delivery API and Preview Delivery API. The issue impacts only a subset of content items, which may result in inconsistent behavior for some requests. This is our top priority, and our development team is actively investigating and working on a resolution. If you have any questions or need assistance, please contact our support team via chat.

Update: The issue occurs only for requests that include the excludeElements parameter. Requests that do not use this parameter should function normally. Our developers are working on a fix to mitigate the issue, which is expected to be released soon. Our development team has identified the root cause of the partial outage and is currently working on a fix. Content items that were modified after approximately 9:25 AM (CET) today may be affected. This issue remains our top priority. If you have any questions or need assistance, please contact our support team via chat.

A fix has been implemented and deployed. We are monitoring the results.

We can now confirm that this issue has been resolved. All components are operational and functioning properly.

# 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 excludeElements query parameter to fail. Specifically, in certain cases an item could be returned without an expected field, and the excludeElements processing path did not handle that scenario. This resulted in an internal error and a 500 response. ## Impact to Customers Customer requests to the Deliver API that included the excludeElements query parameter could intermittently receive HTTP 500 responses during the incident window. The issue affected a limited subset of traffic \(only requests meeting specific conditions were impacted\). The failures occurred only when all of the following were true: * The requested variant \(or one of its dependencies\) had been updated after the deployment. * The request was served uncached \(or required a fresh origin fetch\). * The request included the excludeElements query parameter. ## Resolution ### Timeline \(CEST\): * 08:58 – Deployment completed. * 13:33 – Customer reported errors through Support; we started triage. * 13:37 – Engineering investigation started. * 14:17 – Root cause identified and fix prepared. * 15:32 – Fix deployed. * 16:00 – Service monitored; error rates returned to normal. ### Detection We became aware of the incident after a customer reported the issue via Support. We then confirmed elevated error rates on the affected request path and engaged engineering to investigate and mitigate. ### Guidance During the incident window, retrying the request could succeed depending on whether a fresh fetch was required. If errors were persistent for a specific call, temporarily removing excludeElements would avoid the affected code path \(with the tradeoff of a larger response\). No data loss occurred; this was a request-processing error only. ### Preventive actions * Add end-to-end test coverage for excludeElements, including missing-field scenarios. * Improve automated detection and alerting specifically for elevated 5xx rates on Deliver API request paths. * Add additional safeguards in the API code to handle missing/optional fields defensively. ### Duration Incident window: approximately 08:58–15:32 CEST

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.

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

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.

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.

There is currently a delay in the appearance of assets when accessing an asset's preview URL due to our preview storage being overloaded in the U.S. data center. Accessing the published version of an asset still functions as expected.

Our 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.

There is currently a delay in the appearance of assets when accessing an asset's preview URL due to our preview storage being overloaded in the U.S. data center. Accessing the published version of an asset still functions as expected.

Delays accessing assets by preview URL have resolved. Accessing both published and preview versions of assets is functioning normally.

We are experiencing a problem in which the Fastly API isn't purging outdated content in the US and EU regions. We are currently investigating the issue and will provide updates as soon as possible.

The problem has been identified as a bug in a recent update. We are working to fix this currently.

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 works as intended. We will continue to investigate how this occurred, but the Delivery API shouldn't be returning stale content at this point.

Our integrated chat tool is currently experiencing a full outage: https://www.intercomstatus.com/us-hosting/incidents/01KEJ5AZFPGWKRV57MMEAR9M0W If you're in need of technical support, please reach out to our Support team using the following email: [email protected].

Intercom has implemented a fix, and our integrated chat tool is now only experiencing degraded performance: https://www.intercomstatus.com/us-hosting/incidents/01KEJ5AZFPGWKRV57MMEAR9M0W

Our integrated chat tool, Intercom, reports a full recovery of services as of 4:18pm EST. Full functionality of the support chat function is now fully restored. https://www.intercomstatus.com/us-hosting/incidents/01KEJ5AZFPGWKRV57MMEAR9M0W#updates

This incident has been resolved.

# **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 our third party chat integration Intercom. Intercom’s RCA regarding the issue will be available soon at the following: [Intercom is down - US Hosting Status](https://www.intercomstatus.com/us-hosting/incidents/01KEJ5AZFPGWKRV57MMEAR9M0W#updates). Customers were still able to contact the Support Team via email. The Support team monitored the shared inbox for any incoming issues, promptly updated the [Kontent.ai](http://Kontent.ai) status page to ensure customers were aware of the issue, and monitored Intercom’s status to make sure that any updates were promptly communicated to customers via our status page.

Our Learn portal is currently experiencing slower loading times. Our development team has identified the root cause and is actively working on a fix.

Our development team has implemented the fix, and the Learn portal is fully operational.

Our integrated chat tool experiences problems occasionally -> https://www.intercomstatus.com/us-hosting/incidents/01K806QKYFHM9TEA167TNMT12F If you can't contact our technical support via the in-app chat, please send it to [email protected].

The issues with our integrated chat tool have been resolved, and it is now functioning as expected -> https://www.intercomstatus.com/us-hosting/incidents/01K806QKYFHM9TEA167TNMT12F

The UI of Kontent.ai doesn't load properly due to internal api and Management API problems. We are investigating the issue at the moment. All other public APIs (Delivery API, Preview API, GraphQL, Subscription API) work properly.

We are continuing to investigate this issue.

We have identified the issue, and currently we are restoring our server to its working state.

The server was restored, and everything seems to be up and working as usual. We keep monitoring all the services for any issues.

The incident has been fully resolved. All services are now operational.

We are currently investigating this issue.

We are continuing to investigate this issue.

Our developers have identified the root cause as a network issue within Microsoft Azure, and they are cooperating with Microsoft Azure to resolve the issue.

All services seem to be functioning normally. We are continuing to monitor performance.

This incident has been resolved.

We have identified an outage of GraphQL in the US East region (both Live and Preview), which started around 11:25 AM UTC. Our team is actively investigating the issue.

Our team has identified the issue: the recent release caused a problem with production and staging settings. We are working to fix it.

GraphQL is now functional. More app services were affected, but the GraphQL-related ones should be fine already. We are continuing to work on a fix for the remaining issues.

The incident has been fully resolved. All services and components are now operational.

We have identified an issue where the Delivery API, Delivery Preview API, and Delivery GraphQL API are currently returning outdated content. Our development team will be releasing a fix soon.

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

We have identified that our webhooks are also being affected. Our development team is continuing to work on a fix.

Our development team has released a fix, and we are monitoring the results. The latest changes to content should now be reflected in the Delivery API.

Between 13:56 UTC and 15:59 UTC, we experienced an issue with the latest content changes not being reflected in the Delivery API, Delivery Preview API, and Delivery GraphQL API. Webhook functionality was also affected because of this. These issues impacted all regions. Our development team released a fix at 15:59 UTC, and after a period of monitoring, no further issues have been observed.

We are currently experiencing significant delays in our content inventory search functionality. Our development team has identified the root cause and is actively working on a fix. We appreciate your patience and will keep you updated.

We have issued a fix for the delays in our content inventory search functionality and are monitoring the results.

Between 11:25 UTC and 15:20 UTC, we experienced an issue with delays in our content inventory search functionality. This impacted users with projects in our East US data center. After a period of monitoring, no further delays have been observed.

We are investigating an issue with slower propagation of changes to Delivery API in EU data center.

We have found and fixed the issue. We are now monitoring our services and everything should work as usual.

All changes are propagated to Delivery API with no delays.