Is Kentico down?

Last checked just now
Current status
Kentico is up

No incidents right now.

Official status page: https://status.xperience-portal.com · Polled every 5 minutes · 22 components tracked

Kentico is operational right now. Last checked just now; the most recent incident resolved 22d ago.

Real-time Kentico status, recent outages, and incident history — pulled directly from Kentico's official status page at https://status.xperience-portal.com every 5 minutes. Pingoru tracks 22 Kentico services and has captured 5 incidents in the last 90 days (99.82% uptime). Get email, Slack, Discord, or webhook alerts the moment Kentico reports a new incident — free for 5 monitors, no credit card.

Users who monitor Kentico also follow these Marketing services: Mailgun Klaviyo Iterable Braze Brevo Customer.io ZoomInfo Optimizely SurveyMonkey Yotpo View all 6,000+ providers
Kentico uptime 99.82% uptime · past 90 days
Mon Wed Fri
JunJulAugSep
Less More

Recent outages & incidents

Past 90 days
  1. Resolved 6h 30m
    Started Aug 25, 2026, 04:04 AM UTC · Resolved Aug 25, 2026, 10:35 AM UTC
    Production sites
    Timeline · 7 updates
    • investigating · Aug 25, 2026, 04:04 AM UTC

      We are currently investigating this issue.

    • identified · Aug 25, 2026, 04:11 AM UTC

      Beginning at 03:13 UTC on 25 August 2026, customers hosted in our Southeast Asia region may experience outages or timeouts across their applications. The cause is an ongoing Microsoft Azure platform incident affecting Azure Key Vault in the Southeast Asia region (https://app.azure.com/h/TP8W-S1G/c06b6a). The service issue is preventing our application instances from retrieving the secrets they need to serve requests. Azure has acknowledged the incident and is actively working on mitigation. We are monitoring the situation and will post an update as soon as Azure reports progress on their side.

    • identified · Aug 25, 2026, 04:33 AM UTC

      Some sites in Southeast Asia have come back online and are serving traffic normally. Microsoft has not yet reported a change on the underlying Azure Key Vault incident, so we are treating this recovery as partial and are continuing to monitor.

    • identified · Aug 25, 2026, 05:33 AM UTC

      Microsoft has confirmed a second platform issue in Southeast Asia, this one affecting Azure SQL Database, beginning at 03:47 UTC. Alongside the ongoing Key Vault incident, this means database queries may fail or run slowly, and new database connections may error or time out, in addition to the site availability issues already reported. Both incidents are with Microsoft and neither has been mitigated yet.

    • monitoring · Aug 25, 2026, 06:15 AM UTC

      Microsoft has resolved the Azure Key Vault incident, and all customer sites in Southeast Asia are now online and serving traffic normally. The Azure SQL Database incident in the region remains open on Microsoft's side, so intermittent database errors or slow queries are still possible. We are keeping this incident open and monitoring until Microsoft confirms full mitigation.

    • resolved · Aug 25, 2026, 10:35 AM UTC

      Microsoft has confirmed mitigation of the Azure SQL Database incident in Southeast Asia. Both underlying Azure platform incidents are now closed on Microsoft's side. All customer sites in the region are online and serving traffic normally, and we are no longer seeing database errors or elevated query latency.

    • postmortem · Aug 25, 2026, 02:28 PM UTC

      Between 03:05 and 05:05 UTC on 25 August 2026, a power event in a single datacenter in the Azure Southeast Asia region disrupted network infrastructure and affected a wide range of Azure services, including Azure Key Vault and Azure SQL Database. Customer applications depend on Azure Key Vault for configuration and on Azure SQL Database for all data operations. While these were unavailable, sites hosted in Southeast Asia were unavailable or returned errors, and database queries failed or ran slowly. Customers in other regions were unaffected. Impact began at 03:05 UTC. The majority of services recovered by 04:33 UTC. Microsoft mitigated the incident at 05:05 UTC.

    Latest: Between 03:05 and 05:05 UTC on 25 August 2026, a power event in a single datacenter in the Azure Southeast Asia region disrupted network infrastructure and affected a wide range of…

  2. Resolved 5h 25m
    Started Jul 23, 2026, 03:29 PM UTC · Resolved Jul 23, 2026, 08:55 PM UTC
    Production sites
    Timeline · 4 updates
    • identified · Jul 23, 2026, 03:29 PM UTC

      We are currently experiencing intermittent HTTP 500 errors, timeouts, and elevated latency affecting some projects hosted in the West US region. The issue has been traced to an ongoing incident with our cloud provider (Microsoft Azure App Service), which is actively being investigated. We are monitoring the situation closely and will post updates as more information becomes available.

    • identified · Jul 23, 2026, 05:31 PM UTC

      Our cloud provider (Microsoft Azure) has identified a potential trigger and is applying mitigation measures, including redirecting traffic to healthy infrastructure. Early signs of recovery are being monitored. We continue to track the situation and will share further updates as they become available.

    • monitoring · Jul 23, 2026, 06:52 PM UTC

      Our cloud provider (Microsoft Azure) has rolled back a recent change identified as the likely cause of the issue. Telemetry shows services are recovering, and customers should be observing improvement at this time. We continue to monitor until full recovery is confirmed.

    • resolved · Jul 23, 2026, 08:55 PM UTC

      Our cloud provider (Microsoft Azure) has confirmed the underlying issue has been resolved. All services in the West US region are fully operational and our monitoring confirms normal error rates and latency. We apologize for any inconvenience caused. This incident is now resolved.

    Latest: Our cloud provider (Microsoft Azure) has confirmed the underlying issue has been resolved. All services in the West US region are fully operational and our monitoring confirms norm…

Outage history

Past 90 days · 2 incidents View full outage history →