3 ms·
Azure global DNS failure
- q-base 10y agoAnyone else hit by this? I can't connect to any of our services on Azure. I can see via the dashboard that everything should be fine - but no one is able to connect to any of them.
- PerfectElement 10y agoYes, I have a SQL instance on Central and a failover on East. Both have been unavailable for 40 minutes now :(
- q-base 10y agoYeah, the frustration is real. No contact to either SQL Servers or Web App's so absolutely no way of determining how many end users are affected at the moment.
- jeroen 10y agoAPI management and VSO git on one project, SQL DB on another. Web apps and storage seems to be working everywhere, SQL DB on all but one of my setups.
- jasonkostempski 10y agoI just can't connect to my development SQL server even though it's in the same region as production. The only difference being the service tier, I wonder if that's playing a role. UPDATE: Just got in at 10:53 EST.
- q-base 10y agoStarting at 11:48 UTC 15 Sep, 2016 a subset of customers using DNS in multiple regions may experience difficulties connecting to their resources hosted in this region. This issue is also having knock-on impact on multiple Azure services, including SQL Database, Virtual Machines, Visual Studio Team Services, Service Bus, API Management and App Service \ Web Apps. Engineers are aware of this issue and are actively investigating. The next update will be provided in 60 minutes, or as events warrant.