Sep <var data-var='date'>24</var>, <var data-var='time'>07:28</var> UTC Resolved - 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. Sep <var data-var='date'>24</var>, <var data-var='time'>07:20</var> UTC Monitoring - 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. Sep <var data-var='date'>24</var>, <var data-var='time'>06:48</var> UTC Investigating - 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.

EU data center projects were encountering issues when saving content items

Sep <var data-var='date'>16</var>, <var data-var='time'>13:18</var> UTC Resolved - 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. Sep <var data-var='date'>16</var>, <var data-var='time'>12:52</var> UTC Monitoring - 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. Sep <var data-var='date'>16</var>, <var data-var='time'>12:47</var> UTC Investigating - 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 support@kontent.ai

Investigating GraphQL Service Disruption

Jul <var data-var='date'>29</var>, <var data-var='time'>11:30</var> UTC Resolved - We experienced service degradation caused by the abuse of missing validation that overloaded our authentication system. As a result, some clients encountered issues accessing the application for approximately one hour. Please note that only access to app.kontent.ai was affected. API availability and performance remained unaffected throughout the incident. The impact occurred primarily during two distinct spikes, lasting approximately 5 minutes and 20 minutes, respectively. Our team identified the root cause, mitigated the immediate impact, and is implementing additional safeguards to prevent similar incidents from occurring in the future.

Kontent.ai app degradation

Jun <var data-var='date'>26</var>, <var data-var='time'>10:18</var> UTC Resolved - The service has recovered from the issue, and this incident is now resolved. Jun <var data-var='date'>26</var>, <var data-var='time'>07:23</var> UTC Update - 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. Jun <var data-var='date'>26</var>, <var data-var='time'>07:23</var> UTC Monitoring - 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. Jun <var data-var='date'>26</var>, <var data-var='time'>07:09</var> UTC Investigating - 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.

Login Issues Affecting Application Access

Jun <var data-var='date'>25</var>, <var data-var='time'>09:25</var> UTC Resolved - The incident has been resolved. All affected services, including the Delivery API and webhook notifications, have fully recovered and are operating as expected. Jun <var data-var='date'>24</var>, <var data-var='time'>21:30</var> UTC Monitoring - 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. Jun <var data-var='date'>24</var>, <var data-var='time'>20:44</var> UTC Investigating - 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.

Delivery API Returning Outdated Content in AUEAST Data Center

Apr <var data-var='date'>15</var>, <var data-var='time'>15:27</var> UTC Resolved - We can now confirm that this issue has been resolved. All components are operational and functioning properly. Apr <var data-var='date'>15</var>, <var data-var='time'>13:46</var> UTC Monitoring - A fix has been implemented and deployed. We are monitoring the results. Apr <var data-var='date'>15</var>, <var data-var='time'>12:23</var> UTC Identified - 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. Apr <var data-var='date'>15</var>, <var data-var='time'>12:16</var> UTC Investigating - 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.

Delivery API and Preview Delivery API are experiencing partial outage when using excludeElements parameter

Feb <var data-var='date'>23</var>, <var data-var='time'>11:43</var> UTC Resolved - 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. Feb <var data-var='date'>19</var>, <var data-var='time'>12:58</var> UTC Monitoring - 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. Feb <var data-var='date'>18</var>, <var data-var='time'>10:25</var> UTC Update - We are continuing to work on a fix for this issue. Feb <var data-var='date'>18</var>, <var data-var='time'>10:17</var> UTC Identified - 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.

A small number of users experienced CORS errors and HTTP 425 Too Early responses when calling the Delivery API after the latest Chrome update

Feb <var data-var='date'>17</var>, <var data-var='time'>20:12</var> UTC Resolved - 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. Feb <var data-var='date'>16</var>, <var data-var='time'>11:13</var> UTC Identified - 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.

Delay in Preview Asset Uploads due to Overloaded Preview Storage in the U.S. Data Center

Feb <var data-var='date'>15</var>, <var data-var='time'>23:12</var> UTC Resolved - Delays accessing assets by preview URL have resolved. Accessing both published and preview versions of assets is functioning normally. Feb <var data-var='date'>13</var>, <var data-var='time'>17:11</var> UTC Identified - 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.

Jan <var data-var='date'>22</var>, <var data-var='time'>19:25</var> UTC Resolved - 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. Jan <var data-var='date'>22</var>, <var data-var='time'>17:16</var> UTC Identified - The problem has been identified as a bug in a recent update. We are working to fix this currently. Jan <var data-var='date'>22</var>, <var data-var='time'>16:32</var> UTC Investigating - 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.

Problems With Fastly API Could Cause Stale Content to Be Served to Customers in Some Regions.

Jan <var data-var='date'> 9</var>, <var data-var='time'>21:23</var> UTC Resolved - This incident has been resolved. Jan <var data-var='date'> 9</var>, <var data-var='time'>21:22</var> UTC Update - 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 Jan <var data-var='date'> 9</var>, <var data-var='time'>20:59</var> UTC Update - Intercom has implemented a fix, and our integrated chat tool is now only experiencing degraded performance: https://www.intercomstatus.com/us-hosting/incidents/01KEJ5AZFPGWKRV57MMEAR9M0W Jan <var data-var='date'> 9</var>, <var data-var='time'>20:11</var> UTC Monitoring - 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: support@kontent.ai.

Support Chat (Intercom) Outage

Oct <var data-var='date'>20</var>, <var data-var='time'>22:00</var> UTC Resolved - 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 Oct <var data-var='date'>20</var>, <var data-var='time'>16:18</var> UTC Monitoring - 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 support@kontent.ai.

Intercom chat tool performance decrease

Oct <var data-var='date'>20</var>, <var data-var='time'>18:20</var> UTC Resolved - Our development team has implemented the fix, and the Learn portal is fully operational. Oct <var data-var='date'>20</var>, <var data-var='time'>18:14</var> UTC Identified - Our Learn portal is currently experiencing slower loading times. Our development team has identified the root cause and is actively working on a fix.

Kontent.ai Learn Portal Experiencing Degraded Performance

Oct <var data-var='date'>14</var>, <var data-var='time'>14:00</var> UTC Resolved - The incident has been fully resolved. All services are now operational. Oct <var data-var='date'>14</var>, <var data-var='time'>13:18</var> UTC Monitoring - The server was restored, and everything seems to be up and working as usual. We keep monitoring all the services for any issues. Oct <var data-var='date'>14</var>, <var data-var='time'>13:15</var> UTC Identified - We have identified the issue, and currently we are restoring our server to its working state. Oct <var data-var='date'>14</var>, <var data-var='time'>12:58</var> UTC Update - We are continuing to investigate this issue. Oct <var data-var='date'>14</var>, <var data-var='time'>12:40</var> UTC Investigating - 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.

The Kontent.ai app UI doesn't load

Sep <var data-var='date'>26</var>, <var data-var='time'>08:44</var> UTC Resolved - This incident has been resolved. Sep <var data-var='date'>25</var>, <var data-var='time'>22:35</var> UTC Monitoring - All services seem to be functioning normally. We are continuing to monitor performance. Sep <var data-var='date'>25</var>, <var data-var='time'>21:27</var> UTC Identified - 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. Sep <var data-var='date'>25</var>, <var data-var='time'>21:16</var> UTC Update - We are continuing to investigate this issue. Sep <var data-var='date'>25</var>, <var data-var='time'>20:57</var> UTC Investigating - We are currently investigating this issue.

Changes are likely not propagating to Delivery Preview API for projects in the AU data center

Aug <var data-var='date'>22</var>, <var data-var='time'>12:53</var> UTC Resolved - The incident has been fully resolved. All services and components are now operational. Aug <var data-var='date'>22</var>, <var data-var='time'>12:30</var> UTC Update - 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. Aug <var data-var='date'>22</var>, <var data-var='time'>12:01</var> UTC Identified - Our team has identified the issue: the recent release caused a problem with production and staging settings. We are working to fix it. Aug <var data-var='date'>22</var>, <var data-var='time'>11:44</var> UTC Investigating - 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.

Outage of GraphQL in the US East (Live and Preview)

Jul <var data-var='date'>13</var>, <var data-var='time'>10:00</var> UTC Completed - The scheduled maintenance has been completed. Jun <var data-var='date'>26</var>, <var data-var='time'>12:57</var> UTC Scheduled - On 13 July 2025, from 08:00 to 09:00 UTC, we’ll be migrating our webhook servers to new datacenters to enhance performance and reliability. - No webhooks will be lost, but delivery may be temporarily delayed during the maintenance. - After the migration, new source IP addresses for webhooks will be added. You can find the updated list here: https://kontent.ai/learn/docs/webhooks/webhooks/php#a-outbound-ip-addresses If you experience any problems, please contact us through our in-app chat. Thank you for your understanding!

Webhook Server Migration

Apr <var data-var='date'>15</var>, <var data-var='time'>16:39</var> UTC Resolved - 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. Apr <var data-var='date'>15</var>, <var data-var='time'>16:07</var> UTC Monitoring - 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. Apr <var data-var='date'>15</var>, <var data-var='time'>15:45</var> UTC Update - We have identified that our webhooks are also being affected. Our development team is continuing to work on a fix. Apr <var data-var='date'>15</var>, <var data-var='time'>14:35</var> UTC Update - We are continuing to work on a fix for this issue. Apr <var data-var='date'>15</var>, <var data-var='time'>14:29</var> UTC Identified - 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.

Delivery API, Delivery Preview API, and Delivery GraphQL API Returning Outdated Content

Apr <var data-var='date'>14</var>, <var data-var='time'>15:48</var> UTC Resolved - 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. Apr <var data-var='date'>14</var>, <var data-var='time'>14:32</var> UTC Monitoring - We have issued a fix for the delays in our content inventory search functionality and are monitoring the results. Apr <var data-var='date'>14</var>, <var data-var='time'>13:44</var> UTC Identified - 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.

Search in Content Inventory Experiencing Slowness

Mar <var data-var='date'>15</var>, <var data-var='time'>18:25</var> UTC Resolved - All changes are propagated to Delivery API with no delays. Mar <var data-var='date'>15</var>, <var data-var='time'>13:32</var> UTC Monitoring - We have found and fixed the issue. We are now monitoring our services and everything should work as usual. Mar <var data-var='date'>15</var>, <var data-var='time'>12:45</var> UTC Investigating - We are investigating an issue with slower propagation of changes to Delivery API in EU data center.

Slower propagation to Delivery API in EU data center

Feb <var data-var='date'>21</var>, <var data-var='time'>16:14</var> UTC Resolved - Between 11:00 UTC and 14:32 UTC, we experienced an issue with scheduled publishing and unpublishing not functioning as expected. A fix was released at 14:32 UTC, and after a period of monitoring, the affected features seem to be functioning properly. No additional issues have been observed. Feb <var data-var='date'>21</var>, <var data-var='time'>14:36</var> UTC Monitoring - A fix has been implemented and we are monitoring the situation. We apologize for any inconvenience. Feb <var data-var='date'>21</var>, <var data-var='time'>14:14</var> UTC Investigating - We are currently experiencing an issue in the AUEAST data center where scheduled publishing and unpublishing are not functioning as expected. Regular (manual) publishing remains fully operational and unaffected. Our development team is actively investigating and working on a resolution. We will provide updates as soon as more information is available. This issue is limited to the AUEAST data center and does not impact other regions. In case of any questions, do not hesitate to contact our support team at support@kontent.ai or in the chat.

Schedule publishing and unpublishing not working in AUEAST data center

Jan <var data-var='date'>24</var>, <var data-var='time'>08:51</var> UTC Resolved - After 12 hours of monitoring, we can consider this as resolved. Jan <var data-var='date'>23</var>, <var data-var='time'>20:08</var> UTC Monitoring - We have issued a fix for the reported issue and are monitoring the results. We will provide a more detailed summary of the issue as soon as possible. Please check back here or subscribe above for further updates. Jan <var data-var='date'>23</var>, <var data-var='time'>17:45</var> UTC Identified - Starting at 4:00 pm UTC, the 'Schedule publish' feature has experienced an unscheduled disruption. We have identified the issue, and a fix will be released shortly.

Schedule Publish Currently Down

Dec <var data-var='date'>16</var>, <var data-var='time'>12:45</var> UTC Resolved - After three hours of monitoring, everything seems to be operational with no further delays. Dec <var data-var='date'>16</var>, <var data-var='time'>10:09</var> UTC Monitoring - The EU data center experienced performance degradation due to a higher-than-usual operational load. We scaled up the data center to handle the additional operations efficiently. We are monitoring the traffic. Dec <var data-var='date'>16</var>, <var data-var='time'>09:26</var> UTC Investigating - The Kontent.ai UI is taking longer than usual to load. We are currently investigating the issue.

Longer loading time of the UI

Dec <var data-var='date'> 2</var>, <var data-var='time'>07:58</var> UTC Resolved - All services are fully operational. Most of the projects were not impacted at all. Dec <var data-var='date'> 1</var>, <var data-var='time'>12:50</var> UTC Monitoring - We are currently investigating the issue that occurred on 2024-12-01 from UTC 11:48:39 to 12:20 in the US-CH data center. During this time, the Delivery REST, GraphQL, and Sync APIs (both live and preview) were returning outdated content. Everything is now operational, and we are monitoring the situation. All services are functioning as expected.

Outdated content Issue in US-CH data center

Oct <var data-var='date'>14</var>, <var data-var='time'>14:00</var> UTC Completed - The scheduled maintenance has been completed. Oct <var data-var='date'>14</var>, <var data-var='time'>06:00</var> UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Sep <var data-var='date'>30</var>, <var data-var='time'>07:05</var> UTC Scheduled - We are excited to announce an upcoming infrastructure upgrade designed to further enhance our platform's scalability and performance. No service outage is planned for this time period. All systems will remain fully operational, though you may experience occasional slowdowns in publishing or API responses. We appreciate your understanding as we work to provide you with an even better experience. If you have any questions or concerns, please don't hesitate to reach out to our support team.

Is Kontent.ai down?

Kontent.ai status is UP

Lastest published events

EU data center projects were encountering issues when saving content items

Investigating GraphQL Service Disruption

Kontent.ai app degradation

Kontent.ai Services, Components and Regions

Recent Kontent.ai events

EU data center projects were encountering issues when saving content items

Investigating GraphQL Service Disruption

Kontent.ai app degradation

Login Issues Affecting Application Access

Delivery API Returning Outdated Content in AUEAST Data Center

Delivery API and Preview Delivery API are experiencing partial outage when using excludeElements parameter