Azure Static Web App Custom DNS name stuck in Deletion for over 18hrs.

Hi,

Please retry deleting your custom domains. The underlying issue has been mitigated. I retried deleting mine earlier and it successfully deleted after about 2-3 minutes. Previously it had been stuck for many hours.

Below is excerpt from Post Incident Review (PIR) DZXC-65Z:

What happened?

Between 14:30 UTC on 11 August 2026 and 15:50 UTC on 13 August 2026, a platform issue resulted in an impact to the Azure Static Web Apps service in multiple regions. Impacted customers may have experienced failures or delays when deleting or adding custom domains for Azure Static Web Apps resources hosted in the affected regions. The impact was limited to a subset of customers.

What went wrong, and why?

A platform issue caused an increase in processing backlog for operations responsible for managing custom domain configuration changes. As a result, requests to delete or add custom domains were delayed or failed for a subset of Azure Static Web Apps customers. The issue was mitigated after service processing queues recovered to normal operating levels and pending operations were cleared.

How did we respond?

• 14:30 UTC on 11 August 2026 – Customer impact began.
• 13:04 UTC on 12 August 2026 – The issue was identified through customer reports of failures and delays when deleting custom domains.
• 23:28 UTC on 12 August 2026 – We identified elevated service processing queues as a contributing factor and initiated mitigation activities.
• 15:50 UTC on 13 August 2026 – Service processing queues recovered to normal levels and the impact was mitigated. Customers were advised to retry previously failed operations.

What happens next?

• This Mitigation Statement is the final communication for this incident. For details about which Azure incidents qualify for which Post Incident Reviews (PIRs), refer to https://aka.ms/AzurePIRs
• The impact times above represent the full incident duration, so are not specific to any individual customer. Actual impact to service availability may vary between customers and resources – for guidance on implementing monitoring to understand granular impact: https://aka.ms/AzPIR/Monitoring
• To stay informed about future Azure service issues, make sure that you configure and maintain Azure Service Health alerts – these can trigger emails, SMS, push notifications, webhooks, and more: https://aka.ms/ash-alerts
• For broader guidance on preparing for cloud incidents, refer to https://aka.ms/incidentreadiness

Please click Accept Answer and upvote if the above was helpful.

Thanks.

-TP