Kontentai の障害履歴

1. 2026年10月20日 14:56 UTCidentified

   DNS関連の問題により「*.kenticocloud.com」ドメインパターンが失敗しているという問題を特定しました。 これらには、アプリケーション内で行われたデリバリーAPI、管理API、その他の要求が含まれます。 開発者は現在、このアドレス処理の過程でいますが、その間に、代わりに「kontent.ai」ドメインを使用するようにリクエストを変更することができます.

2. 2026年10月20日 16:49 UTCmonitoring

   "kenticocloud.com" の関連する DNS の変更が再変換され、その結果を監視しています。 ローカルDNSのリゾルバーを使用している人にとって、キャッシュが手動でフラッシュされていない限り、変更は最大48時間かかることがあります。 この問題では非推奨ドメインのみの影響を受け、2019年末以降にリリースされたすべてのSDKバージョンが影響を受けました.

3. 2026年10月20日 18:48 UTCresolved

   13:30 UTC と 16:06 UTC の間に, ドメインの名前レジストラのドメインに作られた変更による失敗した "*.kenticocloud.com" ドメインパターンの廃止によるリクエスト. 変更は16:06 UTCの周りで再変換され、ドメインネームレジストラのドメインのログと検証の開発者の監視に基づいて、問題は解決されるように見えます。 さらなる問題が観察されるか、報告されていない.

公式のインシデント更新を自動翻訳しています。

1. 2026年9月24日 6:48 UTCinvestigating

   現在、アプリケーション内で部分的な性能劣化を経験しています。 コンテンツアイテムを保存したときに、一部のユーザーは問題が発生することがあります。 私たちのチームは、根本的な原因を積極的に調査し、できるだけ迅速に正常なサービスを回復するために働いています。 不便をおかけしますが、ご迷惑をおかけいたしますが、何卒ご了承くださいますようお願い申し上げます.

2. 2026年9月24日 7:20 UTCmonitoring

   コンテンツアイテムの保存操作に影響を与える問題の根本原因を特定し、是正措置を実施しました。 問題は、EUデータセンターのプロジェクトに制限され、特にテキストや豊富なテキスト要素を含むコンテンツ項目に正規表現の検証規則に影響を与えました。 サービスは元通りにされ、保存操作は普通機能します。 当社のチームは、継続的な安定性を確保するための状況を積極的に監視しています。 ご不便をおかけし、ご迷惑をおかけしますが、何卒ご了承ください.

3. 2026年9月24日 7:28 UTCresolved

   コンテンツアイテムの保存操作に影響を与える問題が解決しました。 影響は、EUデータセンターでホストされているプロジェクトのサブセットに制限され、テキストや豊富なテキスト要素を含むコンテンツ項目は、regexの検証を含む影響を受けました。 修正が正常に導入され、想定どおりに作業を保存した影響を受けたお客様からの確認が届きました。 今後もプラットフォームの監視を続けていきますが、この事件は解決しました。 ご迷惑をおかけし、ご迷惑をおかけいたしますが、何卒宜しくお願い申し上げます.

公式のインシデント更新を自動翻訳しています。

1. 2026年9月16日 12:47 UTCinvestigating

   現在、GraphQLサービスに関する問題について調査しています。 当社のエンジニアリングチームは、根本的な原因を特定し、可能な限り迅速にフル機能の復元に積極的に取り組んでいます。 デリバリー API と Management API の両方が完全に動作し、この問題に影響を受けていないことに注意してください。 誠に有難うございますので、ご迷惑をおかけいたしますが、何卒ご理解のほどよろしくお願い申し上げます。 情報が増え次第、順次更新をいたします。 誠に有難うございます。 ご不明な点がございましたら、お気軽にサポートチームにお問い合わせください

2. 2026年9月16日 12:52 UTCmonitoring

   グラフQLサービスに影響を及ぼす問題の根本原因を特定し、サービス機能の復元に向けた緩和策を実施しました。 今回、GraphQLサービスは想定通り稼働しており、安定性を確保し、問題が完全に解決したことを確認するために、当社のチームは積極的に状況を監視しています。 これにより、デリバリー API と Management API は完全に運用されず、影響を受けていない。 誠に申し訳ございませんが、ご迷惑をおかけいたしますが、何卒ご了承くださいますようお願い申し上げます。 今後もモニタリングを継続し、必要に応じてさらなるアップデートを提供してまいります.

3. 2026年9月16日 13:18 UTCresolved

   グラフQLサービスに関する問題は解決されています。 根本原因を特定した後、是正措置を実施し、安定性を確認するためのサービスを密接に監視しました。 グラフQL機能は完全に復元されており、さらなる問題は観察されていません。 このインシデントを通して、デリバリー API と Management API は完全に運用されず、影響を受けていませんでした。 誠に誠に申し訳ございませんが、本件を解決し、ご迷惑をお掛けし、ご理解とご協力をお願い申し上げます.

公式のインシデント更新を自動翻訳しています。

1. 2026年7月30日 11:54 UTCresolved

   認証システムを積み過ぎた不正検証によるサービス劣化を経験しました。 その結果、一部の顧客は、約1時間アプリケーションにアクセスする問題に遭遇しました。 app.kontent.ai へのアクセスのみが影響されました。 API の可用性とパフォーマンスは、インシデント全体で影響を受けないままになりました。 それぞれ2つの異なるスパイク、約5分、20分の間に生じる影響。 私たちのチームは、根本的な原因を特定し、即時の影響を緩和し、同様の事故が将来起こるのを防ぐための追加の保護策を実施しています.

公式のインシデント更新を自動翻訳しています。

1. 2026年6月26日 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. 2026年6月26日 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. 2026年6月26日 10:18 UTCresolved

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

1. 2026年6月24日 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. 2026年6月24日 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. 2026年6月25日 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. 2026年4月15日 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. 2026年4月15日 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. 2026年4月15日 13:46 UTCmonitoring

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

4. 2026年4月15日 15:27 UTCresolved

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

5. 2026年4月17日 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. 2026年2月18日 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. 2026年2月18日 10:25 UTCidentified

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

3. 2026年2月19日 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. 2026年2月23日 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. 2026年2月16日 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. 2026年2月17日 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. 2026年2月13日 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. 2026年2月15日 23:12 UTCresolved

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

1. 2026年1月22日 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. 2026年1月22日 17:16 UTCidentified

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

3. 2026年1月22日 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. 2026年1月9日 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. 2026年1月9日 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. 2026年1月9日 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. 2026年1月9日 21:23 UTCresolved

   This incident has been resolved.

5. 2026年1月9日 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. 2025年10月20日 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. 2025年10月20日 18:20 UTCresolved

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

1. 2025年10月20日 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. 2025年10月20日 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. 2025年10月14日 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. 2025年10月14日 12:58 UTCinvestigating

   We are continuing to investigate this issue.

3. 2025年10月14日 13:15 UTCidentified

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

4. 2025年10月14日 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. 2025年10月14日 14:00 UTCresolved

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

1. 2025年9月25日 20:57 UTCinvestigating

   We are currently investigating this issue.

2. 2025年9月25日 21:16 UTCinvestigating

   We are continuing to investigate this issue.

3. 2025年9月25日 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. 2025年9月25日 22:35 UTCmonitoring

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

5. 2025年9月26日 8:44 UTCresolved

   This incident has been resolved.

1. 2025年8月22日 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. 2025年8月22日 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. 2025年8月22日 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. 2025年8月22日 12:53 UTCresolved

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

1. 2025年4月15日 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. 2025年4月15日 14:35 UTCidentified

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

3. 2025年4月15日 15:45 UTCidentified

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

4. 2025年4月15日 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. 2025年4月15日 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. 2025年4月14日 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. 2025年4月14日 14:32 UTCmonitoring

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

3. 2025年4月14日 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. 2025年3月15日 13:10 UTCinvestigating

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

2. 2025年3月15日 13:32 UTCmonitoring

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

3. 2025年3月15日 18:25 UTCresolved

   All changes are propagated to Delivery API with no delays.