Kentico Outage History

Started Aug 25, 2026, 04:04 AM UTC· resolved Aug 25, 2026, 10:35 AM UTC

1. investigating Aug 25, 2026, 04:04 AM UTC

   We are currently investigating this issue.

2. 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.

3. 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.

4. 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.

5. 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.

6. 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.

7. 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.

Read the full incident report →

Started Jul 23, 2026, 03:29 PM UTC· resolved Jul 23, 2026, 08:55 PM UTC

1. 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.

2. 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.

3. 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.

4. 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.

Read the full incident report →

Started Mar 24, 2026, 07:57 AM UTC· resolved Mar 28, 2026, 06:52 PM UTC

1. identified Mar 24, 2026, 07:57 AM UTC

   Google Chrome is currently marking certain *.xperience-sites.com domains as potentially unsafe, resulting in a red warning screen for users. This appears to be a false positive and is limited to Chrome—other browsers such as Microsoft Edge are not affected. We have contacted Google and submitted a review request to correct the classification. Updates will follow as soon as they are available.

2. identified Mar 25, 2026, 09:00 AM UTC

   We are continuing to investigate why Google Safe Browsing is flagging *.xperience-sites.com domains, initially reported in Google Chrome. Any browser using Google Safe Browsing (https://developers.google.com/safe-browsing/) may be affected. We have narrowed the incident to only /admin/* paths being affected. We are actively working on mitigation and will provide further updates as available.

3. identified Mar 25, 2026, 03:05 PM UTC

   We are continuing our investigation into the Google Safe Browsing flags on /admin/ paths across .xperience-sites.com domains. We have identified a promotional console message from a third-party dependency that may have contributed to the classification. We are evaluating additional mitigations and will provide further updates as available.

4. monitoring Mar 26, 2026, 07:59 AM UTC

   The identified issue has been resolved, and most affected domains are no longer flagged. We are now moving to a monitoring phase to confirm the fix is fully propagated across all affected domains. We will continue to track the status and provide a final update once all domains are confirmed clear.

5. identified Mar 26, 2026, 01:54 PM UTC

   After further monitoring, we have determined that the initial mitigation was not fully effective. Some domains remain flagged by Google Safe Browsing. We are resuming our investigation and will provide further updates as new information becomes available.

6. identified Mar 27, 2026, 12:17 PM UTC

   Investigation is ongoing. We have applied several mitigations that may help resolve the flagging. As a reminder, any browser using Google Safe Browsing may be affected, while browsers with their own protection systems (e.g. Microsoft Edge) are working normally. We will continue to provide updates as the investigation progresses.

7. monitoring Mar 27, 2026, 03:43 PM UTC

   We have applied a mitigation that seems to have resolved the false-positive Google Safe Browsing blocks. We continue to monitor the situation and are working on a permanent long-term fix.

8. resolved Mar 28, 2026, 06:52 PM UTC

   The issue has been resolved. All affected .xperience-sites.com domains are no longer flagged by Google Safe Browsing.

9. postmortem Apr 02, 2026, 02:35 PM UTC

   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.

Read the full incident report →

Started Feb 07, 2026, 05:19 PM UTC· resolved Feb 07, 2026, 08:42 PM UTC

1. 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.

2. monitoring Feb 07, 2026, 06:51 PM UTC

   All affected services in the West US region seem to be online.

3. resolved Feb 07, 2026, 08:42 PM UTC

   This incident has been resolved.

4. 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\)

Read the full incident report →

Started Nov 18, 2025, 12:07 PM UTC· resolved Nov 18, 2025, 06:20 PM UTC

1. 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

2. 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.

3. 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.

4. resolved Nov 18, 2025, 06:20 PM UTC

   Cloudflare states their services are operating normally now.

5. 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.

Read the full incident report →

Started Nov 10, 2025, 07:44 AM UTC· resolved Nov 10, 2025, 11:58 AM UTC

1. 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.

2. monitoring Nov 10, 2025, 11:21 AM UTC

   Hotfix has been applied to the deployment pipeline.

3. resolved Nov 10, 2025, 11:58 AM UTC

   The hotfix has been applied to the deployment pipeline.

4. 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.

Read the full incident report →

Started Aug 07, 2025, 04:20 AM UTC· resolved Aug 07, 2025, 05:56 AM UTC

1. investigating Aug 07, 2025, 04:20 AM UTC

   We are investigating the issue

2. identified Aug 07, 2025, 04:44 AM UTC

   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.

3. resolved Aug 07, 2025, 05:56 AM UTC

   Hotfix has been applied to deployment pipelines.

4. postmortem Aug 07, 2025, 06:21 AM UTC

   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.

Read the full incident report →

Started Jul 24, 2025, 11:31 AM UTC· resolved Jul 24, 2025, 01:13 PM UTC

1. investigating Jul 24, 2025, 11:31 AM UTC

   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.

2. identified Jul 24, 2025, 11:52 AM UTC

   The issue has been identified, and a fix is being implemented.

3. resolved Jul 24, 2025, 01:13 PM UTC

   The fix for the metrics section in Xperience Portal was resolved.

4. postmortem Aug 07, 2025, 04:45 PM UTC

   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.

Read the full incident report →

Started Jul 24, 2025, 07:44 AM UTC· resolved Jul 24, 2025, 08:43 AM UTC

1. investigating Jul 24, 2025, 07:44 AM UTC

   There is an outage in portal

2. resolved Jul 24, 2025, 08:43 AM UTC

   This incident has been resolved.

3. postmortem Jul 24, 2025, 09:07 AM UTC

   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.

Read the full incident report →

Started Feb 13, 2025, 04:56 PM UTC· resolved Feb 21, 2025, 08:14 AM UTC

1. investigating Feb 13, 2025, 04:56 PM UTC

   Our monitoring system detected a problem with SendGrid that's preventing our SaaS customers from creating a new email channel or applying a custom domain to their existing email channels. Currently configured email channels are not affected and are functioning normally. We are working with SendGrid Support to resolve the issue and we will provide a new update soon.

2. identified Feb 18, 2025, 08:06 PM UTC

   After a complex troubleshooting process we concluded that the issue is caused by an unexpected change in the SendGrid API behaviour, and we are working on fix. We will apply the fix to our systems as soon as it is ready and thoroughly tested.

3. monitoring Feb 20, 2025, 11:48 AM UTC

   The fix has been applied and our services are fully operational. We had to adjust our implementation to accommodate the change in the SendGrid API behavior. This allowed us to resume normal operations. We are actively monitoring the situation to ensure stability.

4. resolved Feb 21, 2025, 08:14 AM UTC

   Following our previous update, the issue has been fully resolved, and the system is now stable. We have completed our monitoring, and the incident is now closed.

5. postmortem Aug 07, 2025, 07:08 AM UTC

   Between February 13 and 21, 2025, Xperience by Kentico experienced an issue that prevented SaaS customers from creating new email channels or applying custom domains via SendGrid. Existing channels remained fully functional. The root cause was traced to an unexpected change in SendGrid’s API behavior, which led to incompatibilities with our integration. After identifying the issue, we updated our implementation to align with the new API behavior and restored full functionality by February 20. The system remained stable during post-fix monitoring and the incident was closed on February 21. To prevent similar issues, we’re improving our monitoring of third-party API changes and enhancing communication channels with SendGrid.

Read the full incident report →