Kontent.ai Outage History

Kontent.ai is up right now

Kontent.ai had 12 outages in the last 2 years totaling 196h 25m of downtime — averaging 0.5 incidents per month.

There were 12 Kontent.ai outages since September 25, 2025 totaling 196h 25m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.kontent.ai

Notice July 30, 2026

Kontent.ai app degradation

Detected by Pingoru
Jul 30, 2026, 11:54 AM UTC
Resolved
Jul 29, 2026, 11:30 AM UTC
Duration
—
Timeline · 1 update
  1. resolved Jul 30, 2026, 11:54 AM UTC

    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.

Read the full incident report →

Notice June 26, 2026

Login Issues Affecting Application Access

Detected by Pingoru
Jun 26, 2026, 07:09 AM UTC
Resolved
Jun 26, 2026, 10:18 AM UTC
Duration
3h 8m
Affected: ApplicationApplicationApplicationApplication
Timeline · 4 updates
  1. investigating Jun 26, 2026, 07:09 AM UTC

    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. monitoring Jun 26, 2026, 07:23 AM UTC

    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. monitoring Jun 26, 2026, 07:23 AM UTC

    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.

  4. resolved Jun 26, 2026, 10:18 AM UTC

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

Read the full incident report →

Major June 24, 2026

Delivery API Returning Outdated Content in AUEAST Data Center

Detected by Pingoru
Jun 24, 2026, 08:44 PM UTC
Resolved
Jun 25, 2026, 09:25 AM UTC
Duration
12h 41m
Affected: Delivery REST APIDelivery GraphQL APIWebhook dispatcher
Timeline · 3 updates
  1. investigating Jun 24, 2026, 08:44 PM UTC

    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. monitoring Jun 24, 2026, 09:30 PM UTC

    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. resolved Jun 25, 2026, 09:25 AM UTC

    The incident has been resolved. All affected services, including the Delivery API and webhook notifications, have fully recovered and are operating as expected.

Read the full incident report →

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 →