Kontentai 中断历史

1. 2026年10月20日 UTC 14:56identified

   我们发现一个问题,任何使用"*.kenticocloud.com"域名模式的请求都因DNS相关问题而失败. 这包括交付API,管理API,以及应用程序本身内提出的其他请求. 我们的开发者目前正在解决这个问题,但与此同时,可以更改请求,取而代之使用"kontent.ai"域名.

2. 2026年10月20日 UTC 16:49monitoring

   有关"kenticocloud.com"的DNS更改现已恢复,我们正在监测结果. 对于使用本地 DNS 解析器的人,更改可能需要48小时才能传播,除非缓存是手动冲出. 只有被贬损的域被这个问题所影响,自2019年底以来发布的所有SDK版本都未受影响.

3. 2026年10月20日 UTC 18:48resolved

   在协调世界时13:30至协调世界时16:06之间,由于域名注册员对域名的更改,使用已贬值的"*.kenticocloud.com"域名模式的请求失败. 该变更在协调世界时16:06左右被恢复,根据我们开发者对域名注册员中的日志和域名的验证,这个问题似乎已经解决了. 没有观察到或报告其他问题.

自动翻译自官方事件更新。

1. 2026年9月24日 UTC 06:48investigating

   我们目前正在申请中出现部分性能下降。 一些用户在保存内容项目时可能会遇到问题. 我们的小组正在积极调查根源,并努力尽快恢复正常服务。 我们对造成的不便表示歉意,并将在获得更多信息后立即提供进一步的最新资料.

2. 2026年9月24日 UTC 07:20monitoring

   我们查明了影响内容项目节省业务的问题的根源,并实施了纠正措施。 这个问题仅限于我们欧盟数据中心的项目,并特别影响到包含有regex验证规则的文本或内容丰富的文本元素的内容项目. 服务已经恢复,节省的操作正常运行. 我们的小组正在积极监测局势,以确保持续稳定。 我们为不便而道歉,并感谢你的耐心.

3. 2026年9月24日 UTC 07:28resolved

   我们已经解决了影响内容项目节省业务的问题。 影响仅限于我们欧盟数据中心主持的一个子项目,并影响到包含文本或内容丰富的文本内容,并经过regex验证。 固定装置已经成功部署,我们得到了受影响客户的确认,即节省业务正在按预期运作。 我们将继续监测该平台,但目前认为这一事件已得到解决。 我们为不便而道歉,并感谢你的耐心.

自动翻译自官方事件更新。

1. 2026年9月16日 UTC 12:47investigating

   我们正在调查一个影响我们GraphQL服务的问题。 我们的工程组正积极开展工作,找出根源,尽快恢复全部功能. 请注意,交付物价指数和管理物价指数都仍然充分运作,不受这一问题的影响。 我们理解这可能产生的影响,并真诚地为不便道歉。 一旦获得更多信息,我们将立即提供进一步的最新资料。 谢谢你的耐心和理解。 如果有任何问题,请毫不犹豫地通过聊天或支持与我们的支助小组联系@kontent.ai

2. 2026年9月16日 UTC 12:52monitoring

   我们已查明影响我们GraphQL服务的问题的根源,并已实施缓解措施来恢复服务功能。 此时,GraphQL服务正在按预期运作,我们小组正在积极监测局势,以确保稳定,并证实这一问题已经得到全面解决。 在整个过程中, " API交付 " 和管理API仍然全面运作,没有受到影响。 我们为这种干扰可能造成的任何不便表示诚挚的歉意,并赞赏你在我们努力解决这一问题期间的耐心。 我们将继续密切监测并在必要时提供进一步的最新资料.

3. 2026年9月16日 UTC 13:18resolved

   影响GraphQL服务的问题已经解决。 在查明了根源之后,我们采取了纠正措施并密切监测这项服务,以确认稳定。 GraphQL功能已完全恢复,我们没有观察到任何进一步的问题。 在整个事件中,交付API和管理API仍然全面运作,没有受到影响。 我们为这种干扰在我们努力解决这一问题期间可能造成的任何不便表示诚挚的歉意并赞赏你的耐心和理解.

自动翻译自官方事件更新。

1. 2026年7月30日 UTC 11:54resolved

   我们经历了由于滥用缺失的验证而导致的服务退化,这使我们的认证系统超负荷了。 因此,一些客户在访问申请时遇到约一小时的问题。 请注意,只有App.kontent.ai的使用权受到影响。 在整个事件中,API的可用性和性能没有受到影响。 其影响主要发生在两个不同的高峰期,分别为大约5分钟和20分钟。 我们的小组查明了根源,减轻了直接影响,并正在执行额外的保障措施,以防止今后发生类似事件.

自动翻译自官方事件更新。

1. 2026年6月26日 UTC 07:09investigating

   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日 UTC 07:23monitoring

   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日 UTC 10:18resolved

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

1. 2026年6月24日 UTC 20:44investigating

   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日 UTC 21:30monitoring

   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日 UTC 09:25resolved

   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日 UTC 12:16investigating

   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日 UTC 12:23identified

   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日 UTC 13:46monitoring

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

4. 2026年4月15日 UTC 15:27resolved

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

5. 2026年4月17日 UTC 14:45postmortem

   # 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日 UTC 10:17identified

   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日 UTC 10:25identified

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

3. 2026年2月19日 UTC 12:58monitoring

   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日 UTC 11:43resolved

   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日 UTC 11:13identified

   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日 UTC 20:12resolved

   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日 UTC 17:11identified

   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日 UTC 23:12resolved

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

1. 2026年1月22日 UTC 16:32investigating

   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日 UTC 17:16identified

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

3. 2026年1月22日 UTC 19:25resolved

   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日 UTC 20:11monitoring

   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日 UTC 20:59monitoring

   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日 UTC 21:22monitoring

   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日 UTC 21:23resolved

   This incident has been resolved.

5. 2026年1月9日 UTC 21:24postmortem

   # **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日 UTC 18:14identified

   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日 UTC 18:20resolved

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

1. 2025年10月20日 UTC 16:18monitoring

   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日 UTC 22:00resolved

   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日 UTC 12:40investigating

   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日 UTC 12:58investigating

   We are continuing to investigate this issue.

3. 2025年10月14日 UTC 13:15identified

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

4. 2025年10月14日 UTC 13:18monitoring

   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日 UTC 14:00resolved

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

1. 2025年9月25日 UTC 20:57investigating

   We are currently investigating this issue.

2. 2025年9月25日 UTC 21:16investigating

   We are continuing to investigate this issue.

3. 2025年9月25日 UTC 21:27identified

   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日 UTC 22:35monitoring

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

5. 2025年9月26日 UTC 08:44resolved

   This incident has been resolved.

1. 2025年8月22日 UTC 11:44investigating

   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日 UTC 12:01identified

   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日 UTC 12:30identified

   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日 UTC 12:53resolved

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

1. 2025年4月15日 UTC 14:29identified

   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日 UTC 14:35identified

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

3. 2025年4月15日 UTC 15:45identified

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

4. 2025年4月15日 UTC 16:07monitoring

   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日 UTC 16:39resolved

   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日 UTC 13:44identified

   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日 UTC 14:32monitoring

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

3. 2025年4月14日 UTC 15:48resolved

   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日 UTC 13:10investigating

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

2. 2025年3月15日 UTC 13:32monitoring

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

3. 2025年3月15日 UTC 18:25resolved

   All changes are propagated to Delivery API with no delays.