Xperience by Kentico Status Page

Mar 24, 2026 · resolved Mar 28

Users accessing Xperience by Kentico administration interfaces at `*.xperience-sites.com/admin/*` were shown a "Dangerous site" warning in browsers relying on Google Safe Browsing \(e.g. Chrome, Safari, Firefox\). Because all subdomains of xperience-sites.com share a single domain-level safety score, the flag affected every customer hosted on the domain. Our investigation found no social engineering or deceptive content — as defined by [Google's social engineering guidelines](https://developers.google.com/search/docs/monitor-debug/security/social-engineering) — on any customer site. A third-party dependency was injecting an advertisement into the browser console, which we identified as a likely contributor to the flag. We applied two mitigations: removing the console advertisement injected by the dependency, and updating the admin login page to clearly identify the instance as managed by Kentico. These changes are documented in our [changelog](https://docs.kentico.com/documentation/changelog#saas-update-march-27-2026-march-27-2026). Following both changes, the sites were removed from Google Safe Browsing's blocklist.

Feb 7, 2026 · resolved Feb 7

The outage was caused by Azure Services unavailability. For more info, follow: [https://azure.status.microsoft/en-us/status/history/](https://azure.status.microsoft/en-us/status/history/) \(**Tracking ID**: \_SVS-5\_G\)

Nov 18, 2025 · resolved Nov 18

One of our core 3rd party dependencies Cloudflare experienced an outage and failed to deliver core network traffic. More about the Cloudflare incident can be read in their [Postmortem](https://blog.cloudflare.com/18-november-2025-outage/). The Cloudflare outage impacted all of our customer’s domains which are routed through Cloudflare by default causing all of our customer’s websites to be unavailable. Additionally, the Xperience Portal \(also routed through Cloudflare\) was made unavailable which not only impacted the Xperience Portal UI but also the Deployments API. Cloudflare eventually recovered their services and we did not record any further availability drops.

Nov 10, 2025 · resolved Nov 10

Deployment pipelines were failing in cases where a new deployment package was uploaded or an offline deployment was required. The deployment pipeline requires the AzCopy utility dependency in these cases, however the AzCopy download link was broken by the third-party provider and the pipeline was unable to resolve the new version 10.31.0. We mitigated the issue by releasing a hotfix that directs the download link to a specific previous version of AzCopy.

Aug 7, 2025 · resolved Aug 7

Deployment pipeline agents were unable to retrieve the AzCopy dependency, which is required for deployments involving database and/or storage changes. The issue was caused by a contract change on a third-party side used by the pipeline to download AzCopy. A hotfix was applied to the deployment pipeline to resolve the issue.