Kentico Outage History
Kentico is up right nowKentico had 6 outages in the last 2 years totaling 132h 41m of downtime — averaging 0.2 incidents per month.
There were 6 Kentico outages since November 10, 2025 totaling 132h 41m of downtime. Each is summarised below — incident details, duration, and resolution information.
Intermittent errors and high latency in West US
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.
Google Chrome - xperience-sites.com marked as dangerous
Timeline · 9 updates
Azure services unavailability in the West US region
Timeline · 4 updates
- investigating Feb 07, 2026, 05:19 PM UTC
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.
- monitoring Feb 07, 2026, 06:51 PM UTC
All affected services in the West US region seem to be online.
- resolved Feb 07, 2026, 08:42 PM UTC
This incident has been resolved.
- postmortem Feb 25, 2026, 03:18 PM UTC
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 Global Network outage
Timeline · 5 updates
- investigating Nov 18, 2025, 12:07 PM UTC
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
- monitoring Nov 18, 2025, 12:32 PM UTC
Cloudflare has recovered its services, but customers may continue to see higher-than-normal error rates due to their remediation efforts.
- monitoring Nov 18, 2025, 03:16 PM UTC
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.
- resolved Nov 18, 2025, 06:20 PM UTC
Cloudflare states their services are operating normally now.
- postmortem Nov 19, 2025, 01:03 PM UTC
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.
Deployments with new packages or storage/database changes failing
Timeline · 4 updates
- identified Nov 10, 2025, 07:44 AM UTC
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.
- monitoring Nov 10, 2025, 11:21 AM UTC
Hotfix has been applied to the deployment pipeline.
- resolved Nov 10, 2025, 11:58 AM UTC
The hotfix has been applied to the deployment pipeline.
- postmortem Nov 11, 2025, 09:25 AM UTC
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.