Historial de interrupciones de Kontentai

1. 20 de octubre de 2026 a las 14:56 UTCidentified

   Hemos identificado un problema donde cualquier solicitud que use el patrón de dominio "*.kenticocloud.com" está fallando debido a un problema relacionado con DNS. Esto incluye la API de entrega, API de gestión y otras solicitudes hechas dentro de la propia aplicación. Nuestros desarrolladores están actualmente en proceso de abordar esto, pero mientras tanto, las solicitudes se pueden cambiar para utilizar el dominio "kontent.ai".

2. 20 de octubre de 2026 a las 16:49 UTCmonitoring

   El cambio relevante de DNS para "kenticocloud.com" ha sido revertido, y estamos monitoreando los resultados. Para aquellos que utilizan un resolución local de DNS, el cambio puede tardar hasta 48 horas en propagarse, a menos que el caché se desborde manualmente. Sólo los dominios deprecados se vieron afectados por este problema, y todas las versiones SDK lanzadas desde finales de 2019 no fueron afectadas.

3. 20 de octubre de 2026 a las 18:48 UTCresolved

   Entre 13:30 UTC y 16:06 UTC, las solicitudes utilizando el patrón de dominio deprecated "*.kenticocloud.com" fallaron debido a un cambio hecho al dominio en el registrador de nombre de dominio. El cambio fue revertido alrededor de 16:06 UTC, y basado en el monitoreo de nuestros desarrolladores de los registros y verificación del dominio en el registrador de nombres de dominio, el problema parece ser resuelto. No se han observado ni notificado otras cuestiones.

Traducido automáticamente desde la actualización oficial del incidente.

1. 24 de septiembre de 2026 a las 6:48 UTCinvestigating

   Actualmente estamos experimentando una degradación parcial del rendimiento dentro de la aplicación. Algunos usuarios pueden encontrar problemas al guardar los elementos de contenido. Nuestro equipo está investigando activamente la causa raíz y trabajando para restaurar el servicio normal lo antes posible. Nos disculpamos por la molestia y proporcionaremos más actualizaciones tan pronto como se disponga de más información.

2. 24 de septiembre de 2026 a las 7:20 UTCmonitoring

   Hemos identificado la causa fundamental de la cuestión que afecta a las operaciones de ahorro de contenido y hemos aplicado medidas correctivas. La cuestión se limitaba a proyectos en nuestro centro de datos de la UE y afectaba específicamente los elementos de contenido que contienen elementos de texto o textos ricos con reglas de validación de regex. El servicio ha sido restaurado y las operaciones de ahorro funcionan normalmente. Nuestro equipo está monitoreando activamente la situación para garantizar la estabilidad continua. Nos disculpamos por la molestia y apreciamos su paciencia.

3. 24 de septiembre de 2026 a las 7:28 UTCresolved

   Hemos resuelto la cuestión que afecta a las operaciones de ahorro de contenido. El impacto se limitó a un subconjunto de proyectos hospedados en nuestro centro de datos de la UE y artículos de contenido afectados que contenían elementos de texto o texto rico con validación de regex. La solución ha sido implementada con éxito, y hemos recibido confirmación de clientes afectados que ahorran operaciones funcionan como se espera. Seguiremos vigilando la plataforma, pero el incidente se considera resuelto. Nos disculpamos por la molestia y les damos las gracias por su paciencia.

Traducido automáticamente desde la actualización oficial del incidente.

1. 16 de septiembre de 2026 a las 12:47 UTCinvestigating

   Actualmente estamos investigando un problema que afecta nuestro servicio de GraphQL. Nuestro equipo de ingeniería está trabajando activamente para identificar la causa raíz y restaurar la funcionalidad completa lo antes posible. Tenga en cuenta que tanto la API de entrega como la API de gestión siguen siendo plenamente operativos y no se ven afectados por este problema. Comprendemos el impacto que esto puede tener y sinceramente disculparnos por la inconveniencia. Proporcionaremos más actualizaciones tan pronto como se disponga de más información. Gracias por su paciencia y comprensión. En caso de preguntas, no dude en ponerse en contacto con nuestro equipo de soporte a través de chat o en [email protected]

2. 16 de septiembre de 2026 a las 12:52 UTCmonitoring

   Hemos identificado la causa raíz de la cuestión que afecta a nuestro servicio de GraphQL y hemos implementado medidas de mitigación para restaurar la funcionalidad del servicio. En este momento, el servicio de GraphQL funciona como se espera, y nuestro equipo está monitoreando activamente la situación para garantizar la estabilidad y confirmar que la cuestión se ha resuelto plenamente. A lo largo de todo esto, la API de entrega y la API de gestión siguieron siendo plenamente operativos y no fueron impactados. Sinceramente nos disculpamos por cualquier inconveniente que esta perturbación pueda haber causado y apreciar su paciencia mientras trabajamos para abordar el problema. Seguiremos vigilando de cerca y proporcionaremos nuevas actualizaciones si es necesario.

3. 16 de septiembre de 2026 a las 13:18 UTCresolved

   Se ha resuelto la cuestión que afecta a nuestro servicio de GraphQL. Después de identificar la causa raíz, implementamos medidas correctivas y monitoreamos de cerca el servicio para confirmar la estabilidad. La funcionalidad de GraphQL ha sido completamente restaurada, y no hemos observado ningún problema más. A lo largo de este incidente, la API de entrega y la API de gestión siguieron siendo plenamente operativos y no fueron impactados. Sinceramente nos disculpamos por cualquier inconveniente que esta perturbación pueda haber causado y apreciar su paciencia y comprensión mientras trabajamos para resolver el problema.

Traducido automáticamente desde la actualización oficial del incidente.

1. 30 de julio de 2026 a las 11:54 UTCresolved

   Experimentamos la degradación del servicio causada por el abuso de la validación perdida que sobrecarga nuestro sistema de autenticación. Como resultado, algunos clientes encontraron problemas para acceder a la solicitud durante aproximadamente una hora. Tenga en cuenta que sólo el acceso a app.kontent.ai fue afectado. La disponibilidad y el rendimiento de la API no se vieron afectados durante todo el incidente. El impacto ocurrió principalmente durante dos puntos distintos, que duraron aproximadamente 5 minutos y 20 minutos, respectivamente. Nuestro equipo identificó la causa raíz, mitigó el impacto inmediato, y está implementando salvaguardias adicionales para evitar que ocurran incidentes similares en el futuro.

Traducido automáticamente desde la actualización oficial del incidente.

1. 26 de junio de 2026 a las 7:09 UTCinvestigating

   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.

2. 26 de junio de 2026 a las 7:23 UTCmonitoring

   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.

3. 26 de junio de 2026 a las 10:18 UTCresolved

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

1. 24 de junio de 2026 a las 20:44 UTCinvestigating

   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.

2. 24 de junio de 2026 a las 21:30 UTCmonitoring

   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.

3. 25 de junio de 2026 a las 9:25 UTCresolved

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

1. 15 de abril de 2026 a las 12:16 UTCinvestigating

   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.

2. 15 de abril de 2026 a las 12:23 UTCidentified

   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.

3. 15 de abril de 2026 a las 13:46 UTCmonitoring

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

4. 15 de abril de 2026 a las 15:27 UTCresolved

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

5. 17 de abril de 2026 a las 14:45 UTCpostmortem

   # 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

1. 18 de febrero de 2026 a las 10:17 UTCidentified

   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. 18 de febrero de 2026 a las 10:25 UTCidentified

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

3. 19 de febrero de 2026 a las 12:58 UTCmonitoring

   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. 23 de febrero de 2026 a las 11:43 UTCresolved

   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.

1. 16 de febrero de 2026 a las 11:13 UTCidentified

   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.

2. 17 de febrero de 2026 a las 20:12 UTCresolved

   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.

1. 13 de febrero de 2026 a las 17:11 UTCidentified

   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.

2. 15 de febrero de 2026 a las 23:12 UTCresolved

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

1. 22 de enero de 2026 a las 16:32 UTCinvestigating

   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.

2. 22 de enero de 2026 a las 17:16 UTCidentified

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

3. 22 de enero de 2026 a las 19:25 UTCresolved

   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.

1. 9 de enero de 2026 a las 20:11 UTCmonitoring

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

2. 9 de enero de 2026 a las 20:59 UTCmonitoring

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

3. 9 de enero de 2026 a las 21:22 UTCmonitoring

   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

4. 9 de enero de 2026 a las 21:23 UTCresolved

   This incident has been resolved.

5. 9 de enero de 2026 a las 21:24 UTCpostmortem

   # **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.

1. 20 de octubre de 2025 a las 18:14 UTCidentified

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

2. 20 de octubre de 2025 a las 18:20 UTCresolved

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

1. 20 de octubre de 2025 a las 16:18 UTCmonitoring

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

2. 20 de octubre de 2025 a las 22:00 UTCresolved

   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

1. 14 de octubre de 2025 a las 12:40 UTCinvestigating

   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.

2. 14 de octubre de 2025 a las 12:58 UTCinvestigating

   We are continuing to investigate this issue.

3. 14 de octubre de 2025 a las 13:15 UTCidentified

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

4. 14 de octubre de 2025 a las 13:18 UTCmonitoring

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

5. 14 de octubre de 2025 a las 14:00 UTCresolved

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

1. 25 de septiembre de 2025 a las 20:57 UTCinvestigating

   We are currently investigating this issue.

2. 25 de septiembre de 2025 a las 21:16 UTCinvestigating

   We are continuing to investigate this issue.

3. 25 de septiembre de 2025 a las 21:27 UTCidentified

   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.

4. 25 de septiembre de 2025 a las 22:35 UTCmonitoring

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

5. 26 de septiembre de 2025 a las 8:44 UTCresolved

   This incident has been resolved.

1. 22 de agosto de 2025 a las 11:44 UTCinvestigating

   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.

2. 22 de agosto de 2025 a las 12:01 UTCidentified

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

3. 22 de agosto de 2025 a las 12:30 UTCidentified

   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.

4. 22 de agosto de 2025 a las 12:53 UTCresolved

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

1. 15 de abril de 2025 a las 14:29 UTCidentified

   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.

2. 15 de abril de 2025 a las 14:35 UTCidentified

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

3. 15 de abril de 2025 a las 15:45 UTCidentified

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

4. 15 de abril de 2025 a las 16:07 UTCmonitoring

   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.

5. 15 de abril de 2025 a las 16:39 UTCresolved

   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.

1. 14 de abril de 2025 a las 13:44 UTCidentified

   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.

2. 14 de abril de 2025 a las 14:32 UTCmonitoring

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

3. 14 de abril de 2025 a las 15:48 UTCresolved

   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.

1. 15 de marzo de 2025 a las 13:10 UTCinvestigating

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

2. 15 de marzo de 2025 a las 13:32 UTCmonitoring

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

3. 15 de marzo de 2025 a las 18:25 UTCresolved

   All changes are propagated to Delivery API with no delays.