Is Kentico down?

We are currently investigating an issue where deployments are failing for a subset of projects. Affected deployments may not complete or may return an error. Existing, already-deployed environments remain unaffected and are serving traffic normally.

We have identified that the deployment service of the underlying cloud platform is unavailable for some environments, and we have escalated the issue to our cloud provider. On affected projects, a deployment may appear as queued and then disappear from the deployment list without an error. Restarting the environment does not resolve the issue. Already-deployed environments are not affected and continue to serve traffic normally.

We're still working with Microsoft on this. The number of affected environments has been going down this evening, but the issue isn't resolved yet, and new environments can still become affected. Deployments to an affected environment may fail and won't appear in the deployment history. If that happens, please retry later. Running websites are not affected.

Deployments are working again for all environments. Microsoft is investigating the root cause on their side, and we're monitoring the situation. If a deployment disappears from the in-progress list after a few minutes and doesn't show up in the deployment history, please retry it, and contact support if it happens again.

The issue was caused by a problem on the Microsoft Azure platform side, which Microsoft is still investigating. Deployments have been working normally since 28 Oct. If a deployment disappears from the in-progress list after a few minutes and doesn't show up in the deployment history, please contact support

We are currently investigating this issue.

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.

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.

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.

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.

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.

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.