Is servicebus.windows.net down for anyone else currently?

Robert Martin 0 Reputation points

I'm currently getting lots of Microsoft Azure NotificationHub errors:

System.Net.WebException: The remote name could not be resolved: 'XXXXXXXX.servicebus.windows.net'

Is there an issue that's not being reported currently, or has something changed that I need to address?

  1. Praneeth Maddali 10,460 Reputation points • Microsoft External Staff • Moderator

    Hi @robert martin

    I'm just reaching out to see if your issue has been resolved or if you've had a chance to review my previous comment?

Sign in to comment

2 answers

  1. Praneeth Maddali 10,460 Reputation points • Microsoft External Staff • Moderator

    HI @Robert Martin

    The error you’re seeing — System.Net.WebException: The remote name could not be resolved: '<namespace>.servicebus.windows.net' — typically points to a DNS name-resolution issue on the client or network side, rather than a service outage.

    At this time, there’s no reported Azure Service Bus or Notification Hubs outage. This exception means the environment where your application is running isn’t able to resolve the Service Bus namespace to an IP address.

    What to check next

    1. Validate DNS resolution from the affected machine From the same host (VM, App Service Kudu console, on-prem server, etc.), run: 
       nslookup <namespace>.servicebus.windows.net
      If this fails, it confirms a DNS issue on that host/network path.
    2. Review network and firewall settings Ensure outbound access is allowed for: DNS (TCP/UDP port 53) Azure Service Bus connectivity (AMQP 5671/5672 or HTTPS 443)
    3. Check DNS configuration If using custom DNS servers, a corporate proxy, or a VNet with overridden DNS, ensure those resolvers can reach public Azure endpoints (*.servicebus.windows.net).
    4. Confirm the namespace state In the Azure portal, go to your Notification Hubs Namespace → Resource health and verify it shows as “Healthy” / “Active”. While rare, a disabled or inconsistent namespace state can cause resolution failures.

    Reference:

    https://learn.microsoft.com/en-us/azure/service-bus-messaging/service-bus-troubleshooting-guide

    https://learn.microsoft.com/en-us/azure/service-bus-messaging/service-bus-messaging-exceptions-latest

    https://learn.microsoft.com/en-us/troubleshoot/azure/dns/troubleshoot-dns

    If the nslookup fails from the app host but succeeds from your local machine, the issue is almost certainly in the application’s network path, firewall, proxy, or custom DNS settings

    Kindly let us know if the above helps or you need further assistance on this issue.

    Please "upvote" if the information helped you. This will help us and others in the community as well.

    0 comments No comments
    Sign in to comment

  2. AI answer

    The error indicates a DNS/name-resolution problem for *.servicebus.windows.net, not necessarily that the Azure Service Bus platform is down.

    For System.Net.WebException: The remote name could not be resolved: 'XXXXXXXX.servicebus.windows.net', the documented root cause is that the machine hosting the application cannot resolve the Service Bus namespace to an IP address.

    Troubleshoot as follows:

    1. From the VM/host where Notification Hubs code runs, run: 
       nslookup XXXXXXXXX.servicebus.windows.net
      Replace XXXXXXXXX with the actual namespace.
    2. Interpret the result:
      • If name does not resolve to an IP and alias, there is a DNS issue:
        • Check with the network administrator to verify the DNS server configuration.
        • If Azure DNS is used for resolution, open a support case with Azure Support.
      • If name does resolve correctly, then check connectivity:
        • Ensure outbound connections to Azure Service Bus endpoints and ports are allowed (firewall, proxy, NSG, corporate filters). See the connectivity guidance under “connectivity, certificate, or timeout issues”.
    3. If DNS and connectivity are both correct, treat this as a transient connectivity issue and monitor for recurrence, but the specific exception strongly points to DNS misconfiguration or a temporary DNS outage on the client side.

    There is nothing in the provided documentation indicating a global outage; the prescribed fix is to correct DNS and network connectivity for the Service Bus namespace.

    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.
Sign in to answer

Your answer