Incident Summary — CI/CD Deployment Failures (UK South region)
What happened Customers with projects hosted in the UK South region experienced CI/CD deployments timing out or failing to complete. The issue was isolated to the deployment pipeline; live websites were not affected and remained online throughout.
Probable cause The incident was most likely caused by a regional capacity/availability issue in UK South affecting container provisioning. CI/CD deployments rely on creating a container in the region to run deployment steps. During the incident window, these container provisioning operations were intermittently failing or taking long enough that deployment pipelines exceeded their timeout thresholds. The issue was limited to the deployment path and did not affect already-running workloads.
Impact
Affected: CI/CD deployments for projects hosted in UK South.
Symptom: deployments timed out or failed to complete, preventing affected customers from publishing new versions/updates via the automated pipeline.
Not affected: live websites stayed online.
Timeline
Earliest known impact: ~1 June 2026, 22:00 UTC
Incident declared: 3 June 2026, 11:10 CEST
Deployments completing normally again: 3 June 2026, 12:39 CEST
Resolution Container creation and deployments in UK South returned to normal. We published updates via the status page and Umbraco Portal, kept the incident in monitoring until behavior remained stable, then resolved it.
Action we are taking To reduce the likelihood of this recurring, we are changing the way we provision the ad-hoc containers used during deployments to make the process more resilient.
