MSSQL error 40613

Peter Bancso 0 Reputation points
2026-09-11T19:36:30.13+00:00

Today I can't connect to azure SQL at all., I didn't make any change, the IP is ok.
The query editor in the Azure portal doesn't work either, however it shows the service available when i check.

It is for more than 12 hours already, im not awr of any planned maintenance, please help

Database 'AdvoTime' on server 'sansoft-at.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 '{AA587236-93BF-4371-9507-E74259E5269D}'. (Microsoft SQL Server, Error: 40613)

For help, click: https://go.microsoft.com/fwlink?ProdName=Microsoft%20SQL%20Server&EvtSrc=MSSQLServer&EvtID=40613&LinkId=20476

Azure SQL Database
0 comments

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Deepesh Dhake 1,165 Reputation points
    2026-09-12T18:41:08.56+00:00

    Error 40613 = the database can't be brought online; almost always Azure-side, so IP/firewall/DNS aren't the issue. At 12+ hours it's stuck or a platform incident.

    You can try in order:

    Resource Health (Portal then AdvoTime then Resource Health) tells you if it's a platform issue.

    Manual failover - fixed an identical case:

    Invoke-AzSqlDatabaseFailover -ResourceGroupName <rg> -ServerName sansoft-at -DatabaseName AdvoTime

    Test master / another DB on the server - isolates DB-specific vs. server-wide.

    Open support with tracing ID AA587236-93BF-4371-9507-E74259E5269D if the above fails.

    Was this answer helpful?

  2. AI answer

    2026-09-11T19:36:49.4266667+00:00

    Error 40613 means the Azure SQL database is currently unavailable. This is typically a transient condition caused by failover, reconfiguration, or a scale operation. Since it has lasted more than 12 hours, this is no longer a normal brief interruption.

    Recommended actions:

    1. Check the database health in Azure portal.
      • Open the SQL database resource.
      • Review Resource Health for any platform issue affecting the database.
      • Also check whether the database state is Online.
    2. Check for service incidents during the affected period.
      • Review the Microsoft Azure Service Dashboard for outages around the time the failures started.
    3. Retry with backoff from applications.
      • 40613 is a retryable transient connectivity error.
      • Production applications should implement retry logic instead of surfacing the error directly.
    4. Use the session tracing ID if the issue persists.
      • The error message explicitly says to provide the session tracing ID when contacting support.
      • Because the outage has continued far beyond the expected brief window, capture the tracing ID {AA587236-93BF-4371-9507-E74259E5269D} and open an Azure support request.
    5. If a Dedicated Admin Connection is being used, verify there is not already an active DAC session.
      • In Azure SQL Database, 40613 can also occur if another session is already connected through DAC.
      • Only one DAC session can connect to a single database or elastic pool at a time.

    Relevant behavior for this case:

    • Azure documents 40613 as: Database '%.*ls' on server '%.*ls' is not currently available. Please retry the connection later...
    • Brief occurrences can happen during failover or scale operations.
    • If the duration exceeds 60 seconds or there are repeated occurrences in a day, the documented guidance is to file an Azure support request.
    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.