Kontent.ai logo

Is Kontent.ai Down?

SaaSLive status, outages, and incident history

No. Kontent.ai is up right now.

Every monitored Kontent.ai system is operational as of November 9, 2026. PulsAPI did not find an outage in its latest check of the official status feed.

OperationalChecked just nowLive · every 60s

Know the moment Kontent.ai breaks

Kontent.ai is healthy right now. We keep checking (every 60 seconds) and email you when that changes.

Free, no password, no card. Unsubscribe in one click.

How we know: the official Kontent.ai status page, PulsAPI's own check (every 60 seconds), and outage reports from engineers. How PulsAPI monitoring works

Status report

Kontent.ai Status Summary

As of 13:57 UTC on 9 November 2026, Kontent.ai is operational. PulsAPI checked Kontent.ai's official status page and found 23 of 23 components operational, with no active incidents. Over the last 30 days PulsAPI measured 99.82% uptime for Kontent.ai, counting degraded performance as up. The latest incident, "Requests Using the "*.kenticocloud.com" Domain Pattern Failing", was on Oct 20, 2026 and lasted 3h 51m.

Cite as: PulsAPI, “Kontent.ai status”, checked 9 November 2026, 13:57 UTC. https://www.pulsapi.com/services/kontent-ai

Kontent.ai Component Status

The main Kontent.ai systems on this page. All 23 are operational right now.

23operational
APAC » Application
Operational
APAC » Delivery GraphQL API
Operational
APAC » Delivery REST API
Operational

20 more components tracked

Their status is in the bar above. Free accounts see every component by name.

Also tracking APAC » Management REST API, APAC » Webhook dispatcher, Authentication service, Canada » Application, Canada » Delivery GraphQL API, Canada » Delivery REST API, Canada » Management REST API, Canada » Webhook dispatcher, Europe » Application, Europe » Delivery GraphQL API, Europe » Delivery REST API, Europe » Management REST API, and 8 more.

See all of them free

Component statuses may change independently during partial outages.

Recent Kontent.ai Outages & Incidents

Incident history from the official Kontent.ai status page, including resolution updates.

Requests Using the "*.kenticocloud.com" Domain Pattern FailingResolved Oct 20, 2026 · 3h 51mResolved

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. --- [2026-10-20T16:49:01.722Z] (monitoring) 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. --- [2026-10-20T15:12:35.848Z] (identified) 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.

EU data center projects were encountering issues when saving content itemsResolved Sep 24, 2026 · 40 minResolved

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. --- [2026-09-24T07:20:43.246Z] (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. --- [2026-09-24T06:48:06.657Z] (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.

Investigating GraphQL Service DisruptionResolved Sep 16, 2026 · 30 minResolved

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. --- [2026-09-16T12:52:28.530Z] (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. --- [2026-09-16T12:47:26.260Z] (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

Kontent.ai Uptime History

Daily uptime recorded by PulsAPI over the last 90 days, with the days that carried a Kontent.ai incident marked. Each day is measured from our own checks, so the record continues even when the vendor publishes nothing.

Uptime history91 days observed
Aug 1199.99% average · 3 days with incidentsNov 9

Going further back: Kontent.ai uptime by month and every recorded Kontent.ai outage.

Live Kontent.ai Outage Reports

Problems reported by engineers using Kontent.ai. Reports often appear 10 to 20 minutes before the official status page moves, and stay on this page for 90 days.

Reports, last 24 hours0 total
24h agoNothing reportednow

No Kontent.ai problems reported yet.

Something wrong with Kontent.ai on your end?

Reports are anonymous, take about ten seconds, and help the next engineer who checks.

About Kontent.ai

Is Kontent.ai down? Kontent.ai reports live availability for 27 components at status.kontent.ai, among them USA, Application and Management REST API. Track Kontent.ai outages, degradations and past incidents here, with uptime history and alerts across your SaaS stack.

Over the past 30 days, PulsAPI has measured Kontent.ai uptime at 99.82%. Response times, incident history, and SLA tracking for Kontent.ai are available on the PulsAPI dashboard.

Kontent.ai Status FAQ

Is Kontent.ai down right now?

The verdict at the top of this page comes from the latest poll of the official Kontent.ai status feed and refreshes automatically, so you are not looking at a stale cached answer. PulsAPI re-checks it every 60 seconds.

What should I do if Kontent.ai is not working?

Check the component list on this page first to see if your failure matches a known outage. If it does, you can report the issue for other engineers, follow the incident timeline for vendor updates, and run any fallback your app supports until Kontent.ai recovers.

How do I check Kontent.ai uptime history?

PulsAPI tracks Kontent.ai uptime over 30, 60, and 90-day rolling windows. The current 30-day uptime is 99.82%. The 90-day uptime strip on this page is public: no account needed. A free account adds alerts whenever Kontent.ai changes state, plus 15 days of incident detail; Pro extends that to 90 days and Business to 13 months.

How fast does PulsAPI detect Kontent.ai outages?

PulsAPI reads the official Kontent.ai status page. PulsAPI re-checks it every 60 seconds. Alerts reach Slack, Discord, Microsoft Teams, PagerDuty, or email once a change has held for 5 minutes, so a one-minute blip does not page you.

Does PulsAPI track individual Kontent.ai components?

Yes. PulsAPI monitors 23 individual Kontent.ai components, so you can see which service or region is affected instead of a generic "service degraded" banner.

Can I get alerts when Kontent.ai goes down?

Yes. Create a free account and subscribe to Kontent.ai: the free plan covers three services with unlimited email alerts and no monthly notification cap. Paid plans lift the monitor limit entirely (Pro and above do not meter how many vendors you watch) and route the same alerts into Slack, Discord, Microsoft Teams, PagerDuty and webhooks.

How do I report an issue with Kontent.ai to the community?

Click "Report an issue" at the top of this page, pick the issue type and severity, and optionally add your region and a short note. Reports are anonymous and help other engineers spot Kontent.ai problems early. Official status pages often lag real incidents by 10 to 20 minutes.

Is there a free way to monitor Kontent.ai?

Yes. The free plan covers 3 monitored services with unlimited email alerts, permanently, so Kontent.ai plus two more costs nothing. Every new account also opens with a 30-day Business trial (unlimited monitors, Slack alerts, SLA reporting) with no credit card.

Track Kontent.ai with the rest of your stack

2660+ vendors in one dashboard, and an email the moment any of them changes state. Three free, and no monitor limit at all from $29/mo, unlike the alternatives, which keep charging by the monitor.

Start free, 3 services