Incident Library
Applied filters SymptomMonitoring outageFactorUnverified assumptionOrganisationMicrosoft AzureClear allEvery case under the filters, with no sentence; newest first.
Suggested filters Search, and the values found in your words appear here.

Graph

  • Root cause
  • Component
  • Symptom
  • Contributing factor
  • Case

Cases1 case

1 to 1 of 1

  1. Symptoms

    From 03:45 CST on 23 April 2024, FQDNs in two system domains of Azure in China, chinacloudapp.cn and chinacloudsites.cn, gradually stopped resolving, and customers in the Azure China regions had trouble connecting to many Azure services and managing resources. Internal monitors alerted engineers to the degradation at 04:37 CST.

    Trigger

    At 03:45 CST a configuration change made through a domain registrar, as a step of a domain decommissioning workflow, updated the nameservers of chinacloudapp.cn and chinacloudsites.cn to a set of inactive servers.

    Root cause
    Component
    Contributing factor
    Detection

    Internal monitors alerted engineers to the degradation in the Azure China Cloud at 04:37 CST and created an incident, which the engineering team acknowledged at 04:39 CST.

    Remediation
    • Reverted the two domains to their previous working nameservers
    Action items
    • Suspended further runs of the domain lifecycle process until the management tool covers Azure in China
    • Make the validation process of domain lifecycle management include signals from all cloud regions
    • Add validations that get nameserver information by resolving the zone directly over the Internet
Check your cluster for this

This case involves Authoritative DNS servers and records. kubegap audits a Kubernetes cluster for gaps like these, read-only, from Claude Code or Codex; its checks cite public reports like the ones in this library.

By root cause1