Why has my Azure SQL Database Hyperscale instance been effectively down for the past 30 minutes?

Question

Why has my Azure SQL Database Hyperscale instance been effectively down for the past 30 minutes?

Dominique Northecide 0

The database is Azure SQL Database Hyperscale (PRMS, 24 vCores). CPU utilization was consistently between 60–80%, then suddenly dropped to 0% about 30 minutes ago and has not recovered. The database appears unresponsive.

Can you help determine:

Whether there is an ongoing Azure platform issue affecting this Hyperscale database.
If the compute replica has crashed, restarted, or become unavailable.
Whether there are any resource throttling, failover, or storage-related events.
What diagnostics or logs I should review to identify the root cause and restore service.

Dominique Northecide 0 Reputation points

2026-07-17T14:52:07.9566667+00:00

A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: TCP Provider, error: 35 - An internal exception was caught)
Manoj Kumar Boyini 18,920 Reputation points Microsoft External Staff Moderator

2026-07-17T15:00:20.8466667+00:00

Hi @Dominique Northecide

I kindly request you to please share the details requested in the private message for further investigation.

1 answer

Your answer

Dominique Northecide 0 Reputation points

2026-07-17T14:52:07.9566667+00:00

A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: TCP Provider, error: 35 - An internal exception was caught)
Manoj Kumar Boyini 18,920 Reputation points Microsoft External Staff Moderator

2026-07-17T15:00:20.8466667+00:00

Hi @Dominique Northecide

I kindly request you to please share the details requested in the private message for further investigation.

Answer 1

Hi @Dominique Northecide

We have reviewed the incident, and it was a transient issue that affected a subset of instances in the environment. The engineering team identified inconsistencies related to server audit policy configuration on some instances and has been actively investigating the issue. At this time, the service has recovered.

As part of our ongoing improvements, the engineering team is continuously enhancing automated detection and recovery mechanisms to identify similar situations earlier and minimize the potential impact on customer workloads.

If you encounter a similar issue in the future, please don't hesitate to reach out to us.