azureIs Azure Kubernetes Service down?
Last 90 days
100% uptime · 0 incidentsWhat Azure Kubernetes Service does - and how it fails
Azure Kubernetes Service runs the managed control plane for containerized workloads. AKS incidents split into two very different classes: control-plane problems (API server unavailable, scaling and deployments blocked) that leave running pods serving traffic, and node/networking problems that take workloads down. Knowing which class you are in is the first triage step.
- API server unavailability or latency - kubectl and CI/CD fail while workloads keep running
- Node provisioning or upgrade failures pinning clusters to degraded capacity
- Cluster autoscaler unable to add nodes during a regional capacity event
- CNI/networking or DNS issues inside clusters after platform updates
Azure Kubernetes Service questions
Is AKS down right now?
Check the live status above, then check whether your workloads are actually failing or only the control plane: if kubectl times out but your services still answer, it is a control-plane event and running pods are typically unaffected.
Does AKS have an SLA?
The AKS control-plane uptime SLA (99.95% with availability zones, 99.9% without) applies only to clusters on the paid Standard/Premium tiers - the Free tier carries a service-level objective, not a financially-backed SLA. Your workloads’ availability is additionally governed by the VM SLAs of the node pools.
What should an AKS business-continuity plan cover?
Multiple node pools across availability zones, tested cluster-recreation automation (GitOps), image and chart registries outside the failure domain, and a documented answer for “the API server is down for four hours” - which blocks deploys but should not block serving.
Get alerted when Azure Kubernetes Service breaks
Instant email the moment we detect an incident - affected services and regions included.
Get outage alerts