Postmortem -
Read details
Aug 26, 10:02 CEST
Resolved -
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.
Aug 25, 12:35 CEST
Monitoring -
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.
Aug 25, 08:15 CEST
Update -
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.
Aug 25, 07:33 CEST
Update -
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.
Aug 25, 06:33 CEST
Identified -
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.
Aug 25, 06:11 CEST
Investigating -
We are currently investigating this issue.
Aug 25, 06:04 CEST