Kentico had 7 outages in the last 2 years totaling 125h 2m of downtime — averaging 0.3 incidents per month.
There were 7 Kentico outages since July 24, 2025 totaling 125h 2m of downtime. Each is summarised below — incident details, duration, and resolution information.
Starting at 08:00 UTC on February 7, 2026, some customers in the West US region may experience intermittent service interruptions or delays due to Azure Services being unavailable.
All affected services in the West US region seem to be online.
This incident has been resolved.
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\)
Cloudflare's global network is currently experiencing an outage, and some of the cloud infrastructure, including customers' websites, are not available. See: https://www.cloudflarestatus.com/incidents/8gmgl950y3h7
Cloudflare has recovered its services, but customers may continue to see higher-than-normal error rates due to their remediation efforts.
Cloudflare has applied a fix, and we believe the incident is now resolved. We are continuing to monitor for errors to ensure all services return to normal.
Cloudflare states their services are operating normally now.
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.
Deployment pipelines are failing in some cases (new deployment packages or storage/database changes in the deployment package) due to not being able to download the azcopy utility dependency. azcopy version 10.31.0 cannot be resolved correctly (https://github.com/Azure/azure-storage-azcopy/issues/3284). We are working on a fix.
Hotfix has been applied to the deployment pipeline.
The hotfix has been applied to the deployment pipeline.
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.
We are investigating the issue
Deployment pipeline agents are unable to get azcopy dependency which is required for deployments with db and/or storage changes, Deployments without db or storage changes working.
Hotfix has been applied to deployment pipelines.
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.
The project metrics section of the customer portal is currently unavailable, and graphs are not loading. Our team is working to resolve the issue. All other areas of the portal are functioning normally. We’ll share updates as progress is made.
The issue has been identified, and a fix is being implemented.
The fix for the metrics section in Xperience Portal was resolved.
There was an issue with loading the metrics for projects that were using expired/old service plans. Hotfix was applied to the Xperience Portal application.
There is an outage in portal
This incident has been resolved.
During our scheduled maintenance, an automated monitoring alert was mistakenly triggered, indicating a service outage. This was a false positive caused by the expected temporary unavailability during the planned work.