Azure SQL Database
An Azure relational database service.
5,681 questions
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(9.6, 31%, 10%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EM%3C/text%3E%3C/svg%3E)
We are having the same issue
Failed to connect to server *****.database.windows.net - Error: 40613
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(169.60000000000002, 46%, 26%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EP1%3C/text%3E%3C/svg%3E)
Phil-1348
20
Reputation points
Hi Folks,
We cannot connect to our customer's Azure SQL databases from the web app or management studio for over 7 hours now:
Database '*****' on server '*****.database.windows.net' is not currently available. Please retry the connection later. If the problem persists, contact customer support, and provide them the session tracing ID of '{B3E4CD06-1A64-4468-BC21-D8D61C13DA68}'. (Microsoft SQL Server, Error: 40613)
Please advise.
{count} votes
-
Phil-1348 20 Reputation points
2023-09-16T14:49:21.1666667+00:00 This is the server info:
Name: cr3.eastus1-a.control.database.windows.net Address: 40.79.153.12 Aliases: dataslice6.eastus.database.windows.net dataslice6eastus.trafficmanager.net
Sign in to comment
3 answers
Sort by: Most helpful
-
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(179.20000000000002, 53%, 27%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESD%3C/text%3E%3C/svg%3E)
Spencer Dube 6 Reputation points2023-09-16T15:43:57.9+00:00 Currently seeing the exact same issue. Likely related to current ongoing outage Tracking ID 2LZ0-3DG
Current Status: We have identified that during a brief period of time an underlying network infrastructure has suffered with power issues, resulting on downstream impact for SQL Database in East US region. After further investigation, we have found some unhealthy compute nodes impacting our service on East US region as well. We continue directing all our efforts towards bringing the affected nodes back to a healthy state. The next update will be provided in 60 minutes, or as events warrant. (As of 33 minutes ago)
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(284.8, 87%, 37%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMX%3C/text%3E%3C/svg%3E)
Milton Xavier Sarmiento 0 Reputation points2023-09-16T17:07:11.06+00:00 Is there any news about the outage?
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(300.8, 34%, 39%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EGB%3C/text%3E%3C/svg%3E)
Gerardo Bonell 0 Reputation points2023-09-16T17:33:37.58+00:00 Hi, we're having the same issue since the early morning, it's been like 10 hours with no access to our SQL DBs, do you have any idea when it's going to be solved?
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(54.400000000000006, 21%, 15%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EDJ%3C/text%3E%3C/svg%3E)
DON JONNY 0 Reputation points2023-09-16T17:44:07.3166667+00:00 sigue igual hay alguna recomendacion aparte de esperar?
Sign in to comment -
-
Nandan Hegde 32,411 Reputation points MVP2023-09-16T17:57:08.8766667+00:00 Please monitor via :https://azure.status.microsoft/en-in/status There seems to be some outage going on which might be the cause note: Starting at 07:33 UTC on 16 Sep 2023, you have been identified as a customer using Azure SQL Database in East US who may experience issues when trying to connect to your Database. Connections to databases hosted in a subset of this region may result in an error or timeout.
Workaround: Impacted customers with DR enabled on their database can do failover.
Current Status: We have identified that during a brief period of time an underlying network infrastructure has suffered with power issues, resulting in a downstream impact for SQL Database in East US region. In addition, we have found some unhealthy compute nodes impacting our service on East US region as well. We are manually rebooting affected instances, which should bring the databases back online. Some signs of recovery are being observed with instances that have been rebooted. The next update will be provided in 60 minutes, or as events warrant.
-
Milton Xavier Sarmiento 0 Reputation points
2023-09-16T18:11:31.2366667+00:00 When I try to create a failover I receive an error
{ "status": "Failed", "error": { "code": "InternalServerError", "message": "An unexpected error occured while processing the request. Tracking ID: 'e4d159ce-ce0b-4fbe-9547-ee318d3875bb'" } } -
GeethaThatipatri-MSFT 29,387 Reputation points Microsoft Employee2023-09-18T15:06:28.3166667+00:00 Check Status here : https://azure.status.microsoft/en-in/status
Preliminary Root Cause: We identified that during a brief period of time an underlying network infrastructure experienced power issue. This caused compute nodes to become unhealthy, resulting in failures and timeouts for SQL Database. In addition, multiple downstream services that rely on SQL Database were impacted.
Mitigation: We were notified of this issue through our internal monitoring systems, prompting us to initiate a thorough investigation. In order to mitigate the initial impact, we rebooted the affected compute nodes, thereby restoring functionality to majority of databases. Subsequently, the remaining SQL DB instances was brought back online to bring service to full functionality.
Regards
Geetha
Sign in to comment -