Kontent.ai Outage History

Kontent.ai is up right now

Kontent.ai had 20 outages in the last 2 years totaling 258h 28m of downtime — averaging 0.8 incidents per month.

There were 20 Kontent.ai outages since June 27, 2024 totaling 258h 28m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.kontent.ai

Minor February 18, 2026

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

Detected by Pingoru
Feb 18, 2026, 10:17 AM UTC
Resolved
Feb 23, 2026, 11:43 AM UTC
Duration
5d 1h
Affected: Delivery REST APIDelivery REST APIDelivery REST APIDelivery REST API
Timeline · 4 updates
  1. identified Feb 18, 2026, 10:17 AM UTC

    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. identified Feb 18, 2026, 10:25 AM UTC

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

  3. monitoring Feb 19, 2026, 12:58 PM UTC

    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. resolved Feb 23, 2026, 11:43 AM UTC

    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.

Read the full incident report →

Minor February 16, 2026

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

Detected by Pingoru
Feb 16, 2026, 11:13 AM UTC
Resolved
Feb 17, 2026, 08:12 PM UTC
Duration
1d 8h
Affected: Delivery REST APIDelivery GraphQL API
Timeline · 2 updates
  1. identified Feb 16, 2026, 11:13 AM UTC

    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. resolved Feb 17, 2026, 08:12 PM UTC

    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.

Read the full incident report →

Major January 22, 2026

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

Detected by Pingoru
Jan 22, 2026, 04:32 PM UTC
Resolved
Jan 22, 2026, 07:25 PM UTC
Duration
2h 53m
Affected: Delivery REST APIDelivery REST APIDelivery GraphQL APIDelivery GraphQL API
Timeline · 3 updates
  1. investigating Jan 22, 2026, 04:32 PM UTC

    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. identified Jan 22, 2026, 05:16 PM UTC

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

  3. resolved Jan 22, 2026, 07:25 PM UTC

    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.

Read the full incident report →

Notice January 9, 2026

Support Chat (Intercom) Outage

Detected by Pingoru
Jan 09, 2026, 08:11 PM UTC
Resolved
Jan 09, 2026, 09:23 PM UTC
Duration
1h 11m
Timeline · 5 updates
  1. monitoring Jan 09, 2026, 08:11 PM UTC

    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. monitoring Jan 09, 2026, 08:59 PM UTC

    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. monitoring Jan 09, 2026, 09:22 PM UTC

    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. resolved Jan 09, 2026, 09:23 PM UTC

    This incident has been resolved.

  5. postmortem Jan 09, 2026, 09:24 PM UTC

    # **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.

Read the full incident report →

Minor October 20, 2025

Kontent.ai Learn Portal Experiencing Degraded Performance

Detected by Pingoru
Oct 20, 2025, 06:14 PM UTC
Resolved
Oct 20, 2025, 06:20 PM UTC
Duration
6m
Affected: Kontent.ai Learn and E-learning
Timeline · 2 updates
  1. identified Oct 20, 2025, 06:14 PM UTC

    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. resolved Oct 20, 2025, 06:20 PM UTC

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

Read the full incident report →

Notice October 20, 2025

Intercom chat tool performance decrease

Detected by Pingoru
Oct 20, 2025, 04:18 PM UTC
Resolved
Oct 20, 2025, 10:00 PM UTC
Duration
5h 42m
Timeline · 2 updates
  1. monitoring Oct 20, 2025, 04:18 PM UTC

    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. resolved Oct 20, 2025, 10:00 PM UTC

    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

Read the full incident report →

Critical October 14, 2025

The Kontent.ai app UI doesn't load

Detected by Pingoru
Oct 14, 2025, 12:40 PM UTC
Resolved
Oct 14, 2025, 02:00 PM UTC
Duration
1h 19m
Affected: ApplicationApplicationApplicationApplicationManagement REST APIManagement REST APIManagement REST APIManagement REST API
Timeline · 5 updates
  1. investigating Oct 14, 2025, 12:40 PM UTC

    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. investigating Oct 14, 2025, 12:58 PM UTC

    We are continuing to investigate this issue.

  3. identified Oct 14, 2025, 01:15 PM UTC

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

  4. monitoring Oct 14, 2025, 01:18 PM UTC

    The server was restored, and everything seems to be up and working as usual. We keep monitoring all the services for any issues.

  5. resolved Oct 14, 2025, 02:00 PM UTC

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

Read the full incident report →

Major September 25, 2025

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

Detected by Pingoru
Sep 25, 2025, 08:57 PM UTC
Resolved
Sep 26, 2025, 08:44 AM UTC
Duration
11h 47m
Affected: Delivery REST API
Timeline · 5 updates
  1. investigating Sep 25, 2025, 08:57 PM UTC

    We are currently investigating this issue.

  2. investigating Sep 25, 2025, 09:16 PM UTC

    We are continuing to investigate this issue.

  3. identified Sep 25, 2025, 09:27 PM UTC

    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. monitoring Sep 25, 2025, 10:35 PM UTC

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

  5. resolved Sep 26, 2025, 08:44 AM UTC

    This incident has been resolved.

Read the full incident report →

Critical August 22, 2025

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

Detected by Pingoru
Aug 22, 2025, 11:44 AM UTC
Resolved
Aug 22, 2025, 12:53 PM UTC
Duration
1h 9m
Affected: Delivery REST APIDelivery GraphQL API
Timeline · 4 updates
  1. investigating Aug 22, 2025, 11:44 AM UTC

    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. identified Aug 22, 2025, 12:01 PM UTC

    Our team has identified the issue: the recent release caused a problem with production and staging settings. We are working to fix it.

  3. identified Aug 22, 2025, 12:30 PM UTC

    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. resolved Aug 22, 2025, 12:53 PM UTC

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

Read the full incident report →

Major April 15, 2025

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

Detected by Pingoru
Apr 15, 2025, 02:29 PM UTC
Resolved
Apr 15, 2025, 04:39 PM UTC
Duration
2h 10m
Affected: Delivery REST APIDelivery REST APIDelivery REST APIDelivery REST APIDelivery GraphQL APIDelivery GraphQL APIDelivery GraphQL APIDelivery GraphQL APIWebhook dispatcherWebhook dispatcherWebhook dispatcherWebhook dispatcher
Timeline · 5 updates
  1. identified Apr 15, 2025, 02:29 PM UTC

    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. identified Apr 15, 2025, 02:35 PM UTC

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

  3. identified Apr 15, 2025, 03:45 PM UTC

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

  4. monitoring Apr 15, 2025, 04:07 PM UTC

    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. resolved Apr 15, 2025, 04:39 PM UTC

    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.

Read the full incident report →

Minor April 14, 2025

Search in Content Inventory Experiencing Slowness

Detected by Pingoru
Apr 14, 2025, 01:44 PM UTC
Resolved
Apr 14, 2025, 03:48 PM UTC
Duration
2h 3m
Affected: Application
Timeline · 3 updates
  1. identified Apr 14, 2025, 01:44 PM UTC

    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. monitoring Apr 14, 2025, 02:32 PM UTC

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

  3. resolved Apr 14, 2025, 03:48 PM UTC

    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.

Read the full incident report →

Minor March 15, 2025

Slower propagation to Delivery API in EU data center

Detected by Pingoru
Mar 15, 2025, 12:45 PM UTC
Resolved
Mar 15, 2025, 06:25 PM UTC
Duration
5h 39m
Affected: Delivery REST API
Timeline · 3 updates
  1. investigating Mar 15, 2025, 01:10 PM UTC

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

  2. monitoring Mar 15, 2025, 01:32 PM UTC

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

  3. resolved Mar 15, 2025, 06:25 PM UTC

    All changes are propagated to Delivery API with no delays.

Read the full incident report →

Minor February 21, 2025

Schedule publishing and unpublishing not working in AUEAST data center

Detected by Pingoru
Feb 21, 2025, 02:14 PM UTC
Resolved
Feb 21, 2025, 04:14 PM UTC
Duration
1h 59m
Affected: ApplicationManagement REST API
Timeline · 3 updates
  1. investigating Feb 21, 2025, 02:14 PM UTC

    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 [email protected] or in the chat.

  2. monitoring Feb 21, 2025, 02:36 PM UTC

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

  3. resolved Feb 21, 2025, 04:14 PM UTC

    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.

Read the full incident report →

Notice January 23, 2025

Schedule Publish Currently Down

Detected by Pingoru
Jan 23, 2025, 05:45 PM UTC
Resolved
Jan 24, 2025, 08:51 AM UTC
Duration
15h 5m
Timeline · 3 updates
  1. identified Jan 23, 2025, 05:45 PM UTC

    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.

  2. monitoring Jan 23, 2025, 08:08 PM UTC

    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.

  3. resolved Jan 24, 2025, 08:51 AM UTC

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

Read the full incident report →

Minor December 16, 2024

Longer loading time of the UI

Detected by Pingoru
Dec 16, 2024, 09:26 AM UTC
Resolved
Dec 16, 2024, 12:45 PM UTC
Duration
3h 19m
Affected: Application
Timeline · 3 updates
  1. investigating Dec 16, 2024, 09:26 AM UTC

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

  2. monitoring Dec 16, 2024, 10:09 AM UTC

    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.

  3. resolved Dec 16, 2024, 12:45 PM UTC

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

Read the full incident report →

Notice December 1, 2024

Outdated content Issue in US-CH data center

Detected by Pingoru
Dec 01, 2024, 12:50 PM UTC
Resolved
Dec 02, 2024, 07:58 AM UTC
Duration
19h 8m
Affected: Delivery REST APIDelivery GraphQL API
Timeline · 2 updates
  1. monitoring Dec 01, 2024, 12:50 PM UTC

    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.

  2. resolved Dec 02, 2024, 07:58 AM UTC

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

Read the full incident report →

Major July 15, 2024

Issue Accessing Items in Kontent.ai

Detected by Pingoru
Jul 15, 2024, 03:36 PM UTC
Resolved
Jul 16, 2024, 03:10 PM UTC
Duration
23h 34m
Affected: ApplicationApplicationApplicationApplication
Timeline · 4 updates
  1. investigating Jul 15, 2024, 03:36 PM UTC

    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.

  2. identified Jul 15, 2024, 04:06 PM UTC

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

  3. monitoring Jul 15, 2024, 05:16 PM UTC

    The hotfix has been deployed. We are monitoring the situation for any further disruptions. If you run into anything please let us know at [email protected], thank you!

  4. resolved Jul 16, 2024, 03:10 PM UTC

    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.

Read the full incident report →

Minor July 15, 2024

Partial outage of Delivery and GraphQL APIs

Detected by Pingoru
Jul 15, 2024, 11:26 AM UTC
Resolved
Jul 15, 2024, 09:00 AM UTC
Duration
Timeline · 1 update
  1. resolved Jul 15, 2024, 11:26 AM UTC

    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.

Read the full incident report →

Minor June 27, 2024

Brief period of UI unresponsiveness

Detected by Pingoru
Jun 27, 2024, 02:55 PM UTC
Resolved
Jun 27, 2024, 06:37 PM UTC
Duration
3h 42m
Affected: ApplicationApplicationApplicationApplicationManagement REST APIManagement REST APIManagement REST APIManagement REST APIDelivery REST APIDelivery REST APIDelivery REST APIDelivery REST APIDelivery GraphQL APIDelivery GraphQL APIDelivery GraphQL APIDelivery GraphQL APIWebhook dispatcherWebhook dispatcherWebhook dispatcherWebhook dispatcher
Timeline · 3 updates
  1. monitoring Jun 27, 2024, 02:55 PM UTC

    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.

  2. monitoring Jun 27, 2024, 04:06 PM UTC

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

  3. resolved Jun 27, 2024, 06:37 PM UTC

    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.

Read the full incident report →