Istoricul incidentelor Kontentai

1. 20 octombrie 2026 la 14:56 UTCidentified

   Am identificat o problemă în cazul în care orice cereri folosind modelul de domeniu "*.kenticocloud.com" nu reușesc din cauza unei probleme legate de DNS. Aceasta include API de livrare, API de management, și alte cereri făcute în cadrul cererii în sine. Dezvoltatorii noștri sunt în prezent în proces de abordare a acestui lucru, dar între timp, cererile pot fi schimbate pentru a utiliza domeniul "kontent.ai.".

2. 20 octombrie 2026 la 16:49 UTCmonitoring

   Modificarea DNS relevantă pentru "kenticocloud.com" a fost acum reversibilă și monitorizăm rezultatele. Pentru cei care utilizează un rezolver DNS local, schimbarea poate dura până la 48 de ore pentru a se propaga, cu excepția cazului în care cache-ul este spălat manual. Doar domenii depreciate au fost afectate de această problemă, iar toate versiunile SDK lansate de la sfârșitul anului 2019 nu au fost afectate.

3. 20 octombrie 2026 la 18:48 UTCresolved

   Între 13:30 UTC și 16:06 UTC, cererile de utilizare a modelului de domeniu "*.kenticocloud.com" au eșuat din cauza unei modificări aduse domeniului în registrul numelui de domeniu. Schimbarea a fost returnată în jurul orei 16:06 UTC și pe baza monitorizării de către dezvoltatori a jurnalelor și verificării domeniului în registrul numelui de domeniu, problema pare să fie rezolvată. Nu au fost observate sau raportate alte probleme.

Traducere automată din actualizarea oficială a incidentului.

1. 24 septembrie 2026 la 06:48 UTCinvestigating

   În prezent, ne confruntăm cu o degradare parțială a performanței în cadrul cererii. Unii utilizatori pot întâmpina probleme atunci când economisesc elemente de conținut. Echipa noastră investighează în mod activ cauza rădăcină și lucrează pentru a restabili serviciul normal cât mai repede posibil. Ne cerem scuze pentru inconveniente și va oferi actualizări suplimentare de îndată ce mai multe informații devin disponibile.

2. 24 septembrie 2026 la 07:20 UTCmonitoring

   Am identificat cauza principală a problemei care afectează elementele de conținut salva operațiunile și au implementat măsuri corective. Problema a fost limitată la proiectele din centrul nostru de date al UE și a afectat în mod specific elementele de conținut care conțin text sau elemente de text bogate cu reguli de validare regex. Serviciul a fost restaurat, iar operațiunile de salvare funcționează normal. Echipa noastră monitorizează activ situaţia pentru a asigura stabilitatea continuă. Ne cerem scuze pentru deranj şi apreciem răbdarea ta.

3. 24 septembrie 2026 la 07:28 UTCresolved

   Am rezolvat problema care afectează elementele de conținut salva operațiuni. Impactul s-a limitat la un subset de proiecte găzduite în centrul nostru de date din UE și a afectat elementele de conținut care conțin text sau elemente de text bogate cu validarea regex. Fixarea a fost implementată cu succes și am primit confirmarea de la clienții afectați care salvează operațiunile funcționează conform așteptărilor. Vom continua să monitorizăm platforma, dar incidentul este acum considerat rezolvat. Ne cerem scuze pentru deranj şi vă mulţumim pentru răbdare.

Traducere automată din actualizarea oficială a incidentului.

1. 16 septembrie 2026 la 12:47 UTCinvestigating

   Investigăm în prezent o problemă care afectează serviciul nostru GraphQL. Echipa noastră de inginerie este activ de lucru pentru a identifica cauza rădăcină și de a restabili funcționalitatea completă cât mai repede posibil. Vă rugăm să rețineți că atât API de livrare, cât și API de management rămân pe deplin operaționale și nu sunt afectate de această problemă. Înţelegem impactul pe care acest lucru îl poate avea şi ne cerem sincer scuze pentru neplăceri. Vom furniza actualizări suplimentare de îndată ce mai multe informații devin disponibile. Vă mulţumesc pentru răbdare şi înţelegere. În caz de întrebări, nu ezitați să contactați echipa noastră de suport prin chat sau la [email protected]

2. 16 septembrie 2026 la 12:52 UTCmonitoring

   Am identificat cauza principală a problemei care afectează serviciul nostru GraphQL și am implementat măsuri de atenuare pentru a restabili funcționalitatea serviciului. În acest moment, serviciul GraphQL funcționează conform așteptărilor, iar echipa noastră monitorizează în mod activ situația pentru a asigura stabilitatea și a confirma că problema a fost pe deplin rezolvată. De-a lungul acesteia, API-ul de livrare și Management a rămas pe deplin operațional și nu a fost afectat. Ne cerem sincer scuze pentru orice neplăceri pe care le - a cauzat această întrerupere şi vă apreciem răbdarea în timp ce ne străduim să abordăm această problemă. Vom continua monitorizarea îndeaproape și vom furniza actualizări suplimentare, dacă este necesar.

3. 16 septembrie 2026 la 13:18 UTCresolved

   Problema care afectează serviciul nostru GraphQL a fost rezolvată. După identificarea cauzei profunde, am implementat măsuri corective și am monitorizat îndeaproape serviciul pentru a confirma stabilitatea. Funcţionalitatea GraphQL a fost complet restaurată şi nu am mai observat alte probleme. Pe parcursul acestui incident, API-ul de livrare și Management a rămas pe deplin operațional și nu a fost afectat. Ne cerem sincer scuze pentru orice inconveniente pe care le - a cauzat această întrerupere şi poate că am apreciat răbdarea şi înţelegerea voastră în timp ce ne străduiam să rezolvăm această problemă.

Traducere automată din actualizarea oficială a incidentului.

1. 30 iulie 2026 la 11:54 UTCresolved

   Am experimentat degradarea serviciilor cauzată de abuzul de validare lipsă care a supraîncărcat sistemul nostru de autentificare. Ca urmare, unii clienți au întâmpinat probleme accesând aplicația timp de aproximativ o oră. Vă rugăm să rețineți că numai accesul la app.kontent.ai a fost afectat. Disponibilitatea și performanța API au rămas neafectate pe parcursul incidentului. Impactul a avut loc în principal în timpul a două piroane distincte, care au durat aproximativ 5 minute, respectiv 20 minute. Echipa noastră a identificat cauza principală, a atenuat impactul imediat și implementează garanții suplimentare pentru a preveni apariția unor incidente similare în viitor.

Traducere automată din actualizarea oficială a incidentului.

1. 26 iunie 2026 la 07: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 iunie 2026 la 07: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 iunie 2026 la 10:18 UTCresolved

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

1. 24 iunie 2026 la 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 iunie 2026 la 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 iunie 2026 la 09: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 aprilie 2026 la 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 aprilie 2026 la 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 aprilie 2026 la 13:46 UTCmonitoring

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

4. 15 aprilie 2026 la 15:27 UTCresolved

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

5. 17 aprilie 2026 la 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 februarie 2026 la 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 februarie 2026 la 10:25 UTCidentified

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

3. 19 februarie 2026 la 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 februarie 2026 la 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 februarie 2026 la 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 februarie 2026 la 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 februarie 2026 la 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 februarie 2026 la 23:12 UTCresolved

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

1. 22 ianuarie 2026 la 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 ianuarie 2026 la 17:16 UTCidentified

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

3. 22 ianuarie 2026 la 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 ianuarie 2026 la 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 ianuarie 2026 la 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 ianuarie 2026 la 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 ianuarie 2026 la 21:23 UTCresolved

   This incident has been resolved.

5. 9 ianuarie 2026 la 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 octombrie 2025 la 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 octombrie 2025 la 18:20 UTCresolved

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

1. 20 octombrie 2025 la 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 octombrie 2025 la 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 octombrie 2025 la 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 octombrie 2025 la 12:58 UTCinvestigating

   We are continuing to investigate this issue.

3. 14 octombrie 2025 la 13:15 UTCidentified

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

4. 14 octombrie 2025 la 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 octombrie 2025 la 14:00 UTCresolved

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

1. 25 septembrie 2025 la 20:57 UTCinvestigating

   We are currently investigating this issue.

2. 25 septembrie 2025 la 21:16 UTCinvestigating

   We are continuing to investigate this issue.

3. 25 septembrie 2025 la 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 septembrie 2025 la 22:35 UTCmonitoring

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

5. 26 septembrie 2025 la 08:44 UTCresolved

   This incident has been resolved.

1. 22 august 2025 la 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 august 2025 la 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 august 2025 la 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 august 2025 la 12:53 UTCresolved

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

1. 15 aprilie 2025 la 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 aprilie 2025 la 14:35 UTCidentified

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

3. 15 aprilie 2025 la 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 aprilie 2025 la 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 aprilie 2025 la 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 aprilie 2025 la 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 aprilie 2025 la 14:32 UTCmonitoring

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

3. 14 aprilie 2025 la 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 martie 2025 la 13:10 UTCinvestigating

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

2. 15 martie 2025 la 13:32 UTCmonitoring

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

3. 15 martie 2025 la 18:25 UTCresolved

   All changes are propagated to Delivery API with no delays.