Is Kontent.ai Down Right Now? Check if there is a current outage ongoing.

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.

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.

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

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

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.

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.

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

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.

All changes are propagated to Delivery API with no delays.

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

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

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.

A fix has been implemented and we are monitoring the situation. We apologize for any inconvenience.

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.

After 12 hours of monitoring, we can consider this as resolved.

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.

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.

After three hours of monitoring, everything seems to be operational with no further delays.

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.

The Kontent.ai UI is taking longer than usual to load. We are currently investigating the issue.

All services are fully operational. Most of the projects were not impacted at all.

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.

At 3:17 p.m. (UTC) on 7/15/2024, we released a new version of our application that unfortunately contained a misconfiguration. This misconfiguration caused assets and items with assets to be unviewable. As of 5:09 p.m. (UTC) on 7/15/2024, our hotfix to address this issue has been fully deployed. We apologize for any inconvenience this may have caused and appreciate your patience and understanding as we worked to resolve the matter.

The hotfix has been deployed. We are monitoring the situation for any further disruptions. If you run into anything please let us know at support@kontent.ai, thank you!

Our developers, have identified the problem and are working on a hotfix.

After our recent release we are getting reports of users not being able to access Items and being redirected to their content inventory. Our developers are looking into this.

Due to major infrastructure changes, you might experience an outage of the GraphQL and Delivery APIs between 9:05 AM UTC and 9:30 AM UTC. All the changes were applied, so it shouldn't cause any more issues.

At 14:17 UTC we saw a brief spike of high database server latency which caused some requests sent from projects in our US data center to timeout. This resulted in some users experiencing an unresponsive user interface for approximately 15 minutes before latency returned to normal. Since then we have been monitoring our metrics, and don't see any indicators of a prolonged issue or a clear cause of the original spike. At this point we believe it may have been caused by some glitch in one of our service providers, and we are confident that it is resolved and all services are operating without issue.

Since 2:30 pm UTC our service has been fully operational, though we are continuing to monitor the situation.

There was a brief period of failing requests to our service leading to unresponsiveness of the Kontent.ai user interface. This issue affected projects in the US data center between 2:20 and 2:30 pm UTC. We are currently monitoring the situation and working to ensure it does not happen again.

The application became unresponsive in EU data center between 8:47 UTC and 9:15 UTC due to misconfiguration after deploying the new version. We have implemented additional checks to prevent this from happening in the future.

The fix has been applied, the UI is up again. We are monitoring the service now.

We are continuing to investigate this issue.

You may experience an infinite loading bar while accessing UI of Kontent.ai. We are working on a fix.

The incident has been resolved by the vendor and the asset services are stable.

Microsoft has marked the issue as resolved we are currently monitoring for any further issues.

We've been informed by Microsoft that Azure Storage Service in the EU had degraded availability. Kontent.ai asset services are currently operational, but Microsoft is still investigating the issue.

We are currently experiencing degradation in our EU center regarding our asset services. Users may encounter difficulties uploading or requesting assets. Our team is actively working on a solution to resolve this issue.

This incident has been resolved.

There was a brief increase in CPU usage and traffic on our Learn portal. Currently, everything has returned to normal, and we are actively monitoring the service.

Our Learn Portal is currently inaccessible - we are investigating this issue. More information will be provided here when available.

On the date of March 27th, 2024, the user interface (UI) of our system experienced unresponsiveness from 3:47 UTC to 4:19 UTC. This occurrence was attributed to connectivity issues encountered between our servers and Content Delivery Network (CDN).

Hotfix has been implemented and continuation tokens will now work regardless of creation time. Please reach out to support@kontent.ai if you have any further issues or questions.

Because of the newly released code, users might encounter failed requests for the Delivery REST API items feed endpoint when using older continuation tokens (created before the release, roughly 3 hours ago). The workaround is to stop using those tokens and start consuming the feed from scratch. We are currently investigating further and working on a fix. Delivery REST API is fully operational, only older continuation tokens might be causing failed requests.

After a 7-day monitoring period, no issues were detected with the implemented solution. The performance challenges experienced in our US data center were caused by a bug within Microsoft's Azure Cosmos DB SDK, which is currently a top priority for resolution on their side. Kontent.ai has successfully applied a workaround guaranteeing complete functionality until Microsoft addresses the underlying issue.

The fixing process has been finished and all projects in the US data center now seem to be fully operational.

We have applied a fix for the US data center, and projects are continuously returning to normal. It should take a maximum of a few hours to get everything sorted. If you still encounter any issues with your US projects, please let us know.

We are now rolling back changes we made for US datacenter that caused this issue. Hopefully, this should be fixed soon and we'll keep you updated.

Our developers have identified recent infrastructure changes, leading to increased resource consumption, as the probable cause. We are working to mitigate this issue.

Content Production (both via user interface and MAPI) performance for projects in the US data center is still severely degraded. Some number of requests fail, but most are eventually successful after some delay. We believe the issue is due to abnormally high memory usage, and we are continuing to investigate the cause. Thank you for your patience while we continue working toward a solution.

Some users are still unable to access Kontent.ai, and some number of Management API requests are also failing as a result of this issue. Our team is continuing to investigate and work towards a solution. Thank you for your patience.

Some users are still unable to access Kontent.ai, our team is continuing to investigate and work towards a solution. Thank you for your patience.

Our service should now be back online after about 40 minutes of downtime. Delivery API functionality was not affected. We are still investigating the initial cause of the outage.

Our service should now be back online after about 40 minutes of downtime. Delivery API functionality was not affected. We are still investigating the initial cause of the outage.

Several users have reported an inability to log in or access Kontent.ai. Currently we believe the issue is isolated to projects located in the US data center and our development team is actively investigating. Thank you for your patience while we work to resolve this issue.

This incident was resolved and affected security services whitelisted our us asset domain. They also stated our domain was incorrectly blocked and to prevent it again they updated their security rating. If you are still affected by this asset domain block due to some services not being quick enough in whitelisting us, you can temporary use "assets-us-01-tlsnext.kc-usercontent.com" asset domain instead. For more information please contact our technical support.

We have identified that one of our US asset domains has been placed on a blacklist. If you encounter any issues with assets being blocked by security controls or vendors, please contact us immediately. Our Information Security team is actively working to address this matter. Your reports, including the names of the security vendors involved, are invaluable to our resolution efforts. We appreciate your understanding and cooperation and will provide updates as the situation progresses.

We have resolved the partial outage caused by a vendor's code bug that led to a misconfiguration of our services. We have implemented a fix and all systems are now fully operational. We apologize for any inconvenience and appreciate your understanding.

A fix has been implemented, and we are monitoring the results. Delivery APIs for the USA-East region returned to working at 8.45UTC and are working as expected.

We are currently experiencing a disruption in the Kontent.ai APIs specifically affecting the USA East region. Our technical team is doing their best to identify and resolve the root cause. Customers can contact us via chat or email if they need further help. We apologize for any inconvenience.

Between 22:00 UTC and 23:15 UTC, multifactor authentication was not operational due to a bug introduced in a recent deployment. This issue has now been mitigated. Customers using other types of authentication were not affected, and no credentials were compromised. We are working on a full root cause analysis and investigating options to prevent similar bugs from reaching production.

We are continuing to monitor for any further issues.

Between 22:00 UTC and 23:15 UTC, the MFA was not operational due to a bug in our recent deployment. The issue has been mitigated.

The issue with our authentication provider was solved by the provider. Customers experienced problems with signing in for about 25 minutes between 7:55 PM and 8:20 PM on October 30, 2023.

At this time our services have been functional for some time. Auth0 has reported an incident https://status.auth0.com/incidents/0wnt9fdgq7q3 which caused the outage. That issue is now resolved, and we will continue monitoring to ensure no further impact.

We experienced a brief outage (around 20 minutes) that left users unable to log in to Kontent.ai. We believe the issue may have been related to an issue with our 3rd-party login provider and are continuing to monitor the issue.

This incident has been resolved.

There was a short spike (10 min) on AU server. Everything seems to be working as expected now. We are monitoring the server.

We are continuing to investigate this issue.

We are continuing to investigate this issue.

There could be failing requests in Australia data center for GraphQL API. We are investigating the issue.

The problems that were occurring with the environment endpoint of the Management API have now been fixed.

We are currently experiencing issues with the environment endpoint of the Management API, which is responding with 404. We are actively investigating this matter.

The issue was the result of a small misconfiguration in our infrastructure. We shouldn't happen again and we are concluding our investigation.

Kontent.ai is now back online, we are continuing to investigate the cause of this issue to ensure it does not reappear. If you experience any further issue please report it directly to our support team, thank you!

We are currently investigating an issue preventing users from logging into Kontent.ai. We will provide an update as soon as possible. Thank you for your patience while we work to resolve this issue.

Our services in the AU data center have been without issue for 18 hours. We will continue to monitor Azure's status but as of now it seems they are nearing full recovery.

Our Australian Data Center is up and running without issue since 17:14 UTC. We are continuing to monitor the situation until Azure lists the disruption as fully resolved. Please report any recurring issues to us so we may continue our investigation. Thank you.

Azure has reported their impacted hardware has been stabilized and restarted. Impacted customers like us should begin to see improvement over time. We are continuing to monitor the situation and will provide an update once our systems are fully restored.

We are currently investigating this issue related to: https://azure.status.microsoft/en-us/status (Azure issues in AU EAST) - propagation of changes might be affected (delay or not coming at all) - delivery API (or graph) could be affected

The issue has been completely solved.

We are currently looking into a partial issue with the webhook endpoints in MAPI which appear to be having difficulty.

This incident has been resolved.

The fix was applied. Now, we are monitoring GraphQL, but the issue should be solved.

We have found a bug that prevents GraphQL API calls to finish when Secured access is enabled. We are working on a fix.

This incident has been resolved. The Learn Portal is operational again.

The Learn Portal has been restored. We are monitoring this service while investigating the root cause of the outage.

We are continuing to investigate this issue.

Our Learn Portal is currently inacessible - we are investigating this issue. More information will be provided here when available.

This incident has been resolved; scheduled publishing is functioning as expected.

We are aware of a disruption to scheduled publishing, currently affecting all datacenters. We are currently investigating this issue, and will provide further updates.

Microsoft has repaired the damaged lines causing unavailable data links. It does not appear that Kontent.ai was affected by the cut lines. For more information you can view Microsoft Azure's status history: https://azure.status.microsoft/en-us/status/history if you have any questions please contact us at support@kontent.ai.

After conducting a thorough investigation, our developers have determined that the problem reported by Microsoft only affects internal processes and has not had any impact on our customer projects or API performance. We are actively monitoring the situation, which is being tracked on the Microsoft Azure status page: https://azure.status.microsoft/en-us/status. Rest assured, we will promptly inform our customers of any relevant developments as they occur.

Microsoft Azure is experiencing degradation of performance in EU and AU regions. This means that projects in EU and AU can serve content with increased propagation time.

Between Jun 16, 06:52 UTC, and Jun 17, 06:04 UTC we experienced an issue with our backend service's item indexing, impacting the editing experience in the user interface. Please note that our APIs were not affected. Due to the nature of the issue, we had to perform item reindexing across all projects to ensure full functionality, which has now been completed in all regions. Thank you for your patience and understanding while we addressed this matter. If you have any lingering concerns or questions, please don't hesitate to reach out to our dedicated support team.

Reindexing tasks are complete for all projects in the European and Australian data centers and this issue should be resolved for customers in those regions. Reindexing of the US data center is still in progress. We will update this status again once that process is complete. Thank you for your patience and understanding while we work to resolve this issue.

The fix is being applied to all data centers. This should resolve the UI issue.

Our UI is encountering problems because of which it might be temporarily returning outdated results. It may manifest by - Showing outdated data - New or updated items not being shown in full-text search results - New or updated items showing as non-existing when they are used as linked items We have identified the problem and are working on a fix for the affected projects. Delivery API is not affected by this.

For around 45 minutes, we encountered an outage for Delivery Preview REST API in AU EAST DC and for Delivery Live GraphQL in AU SCC DC. The situation is stable now and the outage has been resolved.

This incident has been resolved.

Following an unusually high number of failed requests, we're glad to inform you that the Delivery API has stabilized. We don't anticipate any further issues with response times and will continue to monitor the status closely.

We are experiencing an unusually high number of failed requests in the North American Deliver REST API. We are investigating the issue.

For the last three hours of monitoring, we have had no new reports of any issues, and our metrics suggest that our back end has stabilized. We have received assurance from our back-end service provider that they are aware of the issue and are taking the necessary steps to make sure that it doesn’t happen again. We would like to thank everyone once again for their understanding and patience. If you run into any issues or have any questions, please don’t hesitate to reach out to our support team.

Our metrics are showing strong improvement, and at this point users should be able to access projects in the US data center with only minor slowdown or load time. Please keep in mind there may be some delay on API propagation due to traffic, but our initial tests are showing good speed. We will continue to monitor the state of the database which serves the US data center, and work with the service provider to determine the root cause and how this can be prevented in the future. Thank you for your patience and understanding.

The application outage in the US data center no longer appears intermittently, but constantly. After testing we've confirmed the Management API for US projects is also affected by the outage. We are doing everything we can to find a solution and bring the system back online. Thank you for your understanding and patience.

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

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

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

We are currently experiencing intermittent UI issues in the North American area. You may experience longer response times of our application UI. No API is affected by this. We have identified one of our backend service providers as the source of the issue and are currently in contact with this provider to find a solution.

Microsoft Azure fixed their configuration issue that was causing problems with UI and after few hours of monitoring the incident seems to be resolved.

We have issued a fix for the reported issue and are monitoring the results. If you are still having issues using our UI please let us know at support@kontent.ai. Please check back here or subscribe above for further updates.

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

We are still experiencing intermittent outage of the editor user interface in the European data center, but Australian projects are fully operational again. We are still in contact with our backend provider, and will provide further updates as we receive more information from them. Thank you for your patience as we work to get this issue resolved and our systems fully operational.

We have identified one of our backend service providers as the source of the issue and are currently in contact with this provider to find a solution.

We are continuing to investigate this issue.

We are continuing to investigate this issue.

We are currently investigating intermittent UI issues in the APAC and EMEA area. You may experience longer response times of our application UI. No API is affected by this.

After extended monitoring, services have been working as expected.

The service affecting the reported intermittent UI issues in the APAC area has stabilized. We are confident that the application is now responding normally. However, we will continue to keep a close eye on the performance and will provide updates as necessary.

We are currently investigating intermittent UI issues in the APAC area. You may experience longer response times of our application UI. No API is affected by this.

After a few hours of monitoring, all of our services work as expected.

We have found a solution and put a fix in place which has restored Delivery API functionality. Content changes made during the outage may still take longer than anticipated to be reflected due to the time it will take to process the accumulated traffic. We will continue to monitor the situation and provide an update when we feel confident the issue is totally resolved. Thank you for your patience and understanding.

We have identified the cause of the outage in our system, which was related to our backend service provider. We're actively working with them to resolve the issue as quickly as possible. Our team is working diligently to get everything back up and running smoothly, and we'll provide updates as soon as we have more information. We appreciate your patience and understanding.

The issue is also causing webhook notifications for content changes not to be sent.

We are continuing to investigate this issue.

After testing this appears to be affecting graphQL as well

We are aware of an issue causing both preview and delivery APIs to not deliver updated content. We are currently working to identify the cause.

Between 03, 01, 18:22 UTC and 03, 01, 21:22 UTC we experienced an issue with delayed and failed requests to the Delivery API. This impacted customers using our US data center. Please check back later to see details on how we have resolved the issue and how we are taking steps to ensure similar incidents do not occur in the future.

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.

The Delivery API is currently experiencing an unscheduled disruption in service for projects in the US data center. At this time customers may experience longer than normal response times when querying the API. We are investigating the issue and will have an update soon.

This incident has been resolved.

A very low number of notifications are not being sent. We are working on a fix.

The incident was resolved on Microsoft Azure side and our services are operational again: "Between 07:05 UTC and 09:45 UTC on 25 January 2023, customers experienced issues with networking connectivity, manifesting as network latency and/or timeouts when attempting to connect to Azure resources in Public Azure regions."

The publishing could be delayed in Australia region. The incident started at 7:08 AM UTC and now all services are getting back to normal.

The UI and APIs may take longer to load or fail in some cases due to performance issues on Microsoft Azure https://status.azure.com/en-us/status.

A short performance degradation of CDN (Fastly CDN) occurred between 11:00 PM UTC and 11:06 PM UTC.

This incident has been resolved.

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

Email notifications are currently experiencing an unscheduled partial disruption in service. At this time customers may not receive automated emails such as workflow notification emails, billing reports, or invitation emails. Verification and password reset emails are now operating as expected. We are working with our email service provider and hope to have the issue completely resolved soon.

We are currently investigating this issue.

All systems are confirmed to be functional as expected. Today (26 Oct 2022) between 00:43 an 06:00 UTC our Azure datacenter in US experienced connectivity issues that could lead to problems with scheduling publishing and unpublishing of items in this datacenter. Azure should apply a fix for this within 48 hours so it won't happen again.

The issue should be resolved. We are now monitoring our services and checking for all data consistencies.

We are currently facing Scheduled publishing/unpublishing issue in the region of East US. Our team has identified the cause and will resolve it ASAP.

We are currently investigating the issue.

Between September 17, 2022, 03:13 AM UTC and September 17, 2022, 03:55 AM UTC, Management API and UI in USA data center were unavailable. The Delivery API experienced partial outage (small part of the content was unavailable in US data center). The issue has been resolved and all Kontent.ai services are operational again.

The performance has stabilized and no further issues have been found.

We have identified the cause of the performance issue. Performance seems to have stabilized. We will be monitoring it, and making any changes as necessary.

Full-text search in the Kontent.ai application is causing slower load times. We are currently investigating the cause of the issue.

No further issue is detected. Service resumed as normal.

Preview changes are now successfully propagating, service should be back to normal. We will continue monitoring for the time being.

We have restarted the service. Please allow some time for all changes made since the outage to be processed. We will continue monitoring the service.

Since 12:48 UTC changes are not propagating to the preview Delivery API for projects hosted in the US data center. We are currently investigating and will provide more information as we have it.

The affected services are expected to return to normal.

We are currently investigating a service degradation which affects our customers who host data in US region. The incident started around 1:00 UTC. You may experience intermediate interruptions when retrieving asset from us.

Between JUN, 22, 21:00 UTC and JUN, 23, 09:00 UTC we experienced an issue with delayed content propagation to the Preview and Delivery APIs. Customers may have experienced a delay in updates being reflected in their API responses.

We have deployed a fix and the Delivery API should now work as expected. Some changes prior to the fix can still take some time (minutes) to be propagated to Delivery API.

For small subset of projects we found random spikes in content propagation to Delivery API. This means that either Preview API or Delivery API can encounter delays in serving updated content. We are working on a fix.

After 14 hours of monitoring there were no other issues recognized and all services are fully responsive.

Since 6/15/2022 18:16 (UTC), everything seems to back on track. We are monitoring our services now.

We have found that the SchedulerTasks webjob couldn't connect to CosmosDBs in US between 12:00 and 18:16 (UTC). Cause is still unknown and our investigation remains ongoing

The scheduled publishing feature appears to be functioning as expected again. We are still working to investigate its cause and prevent it from happening again.

We have become aware of an issue causing scheduled publishing to fail. The process begins on time but displays the publishing now message indefinitely, never publishing. We are currently investigating.

Between JUN, 13, 7:55 UTC and JUN, 13, 08:21 UTC we experienced an issue with failed Delivery Requests impacting users implementing image optimization. This was caused by an issue with Fastly's CDN which has since been resolved. (see here https://status.fastly.com/incidents/k1lt2nrfm6gt)

Between as early as 07:30 UTC and 15:31 UTC on 16 Feb 2022, Microsoft Azure experienced service degradation that impacted the Kontent by Kentico UI performance for a subset of our customers. Microsoft has since resolved the issue and provided more details, as well as mitigation and next steps, here: https://status.azure.com/en-us/status/history/

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

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

The Kontent UI is currently experiencing an unscheduled disruption in service. At this time customers may experience slowdowns when accessing the CMS UI, which may take severl minutes to load. We believe this to be related to issues with SQL servers on Azure, utilized by Kontent. We are monitoring the situation and awaiting updates from Microsoft https://status.azure.com/en-us/status