Is Kontent.ai down?

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.