NEXTDNS Down?

Hello

NextDNS is working fine here. Yesterday we had reports of problems with NextDNS on the Brazilian carrier VIVO, but it has already been resolved.

Here in Brasília (Brazil), when I'm connected to Claro's 5G mobile network and using NextDNS, I can't resolve any hostnames—not even ping.nextdns.io.
 

When I disable NextDNS, everything works normally.
 

As a side note, it works perfectly fine on a wired connection.
 

I have been using NextDNS for over 3 years.

I did a little bit of troubleshooting and i believe the problem is that Claro's mobile network DNSs can´t resolve the address dns.nextdns.io.

I tried to access https://dns.nextdns.io on my browser and i get a dns error.

"It's not possible to find the dns address to dns.nextdns.io"

using other dns servers i can resolve it

dns.nextdns.io@9.9.9.10 (Default):

dns.nextdns.io.

176INCNAMEsteering.nextdns.io.
steering.nextdns.io.32INA45.76.21.53
steering.nextdns.io.32INA162.250.6.163

ping.nextdns.io or nextdns.io are resolved without problem.

If claro cannot resolve dns.nextdns.io it cannot resolve

<user account>.dns.nextdns.io and the DNS-over-TLS/QUIC are not arriving at nextdns.

I opened a case with claro.

Same problem here. I change to controlD because NextDNS no longer works, and it was working normally before.

VIVO, WIFI, CLARO BRAZIL SP

I started having issues about 24 hours ago and after exhaustive analysis, I think my issue is related to the issue here.  My mobile phone (Pixel 10 Pro, latest OS + patch), my Asus router, and my Alexa Show devices all report they aren't able to connect to the internet.  The commonality? NextDNS.

Digging through it, since my PC was working, I assumed there was probably a DNS query that all were attempting and all were failing.  This is true for Android devices, Alexa Show devices have their own (as do Alexa Echo pro devices), and, lastly, was a cause for my new Ring camera failing to be setup.  Here's the evidence:

PS C:\Users\Janeway> nslookup dns.msftncsi.com
DNS request timed out.
    timeout was 2 seconds.
Server:  UnKnown
Address:  [RedActed]

DNS request timed out.
    timeout was 2 seconds.
DNS request timed out.
    timeout was 2 seconds.
Non-authoritative answer:
Name: dns.msftncsi.com
Addresses:  fd3e:4f5a:5b81::1
          131.107.255.255

• Asus router reports disconnected: dns.msftncsi.com timing out through NextDNS
• Alexa devices report no internet: fireoscaptiveportal.com and www.example.com timing out through NextDNS
• Android phone intermittent issues: connectivitycheck.gstatic.com likely experiencing occasional delays through NextDNS
• PC works fine: www.google.com and Google-hosted domains resolve instantly through NextDNS

My general sense here is that NextDNS is having delays in responding to these queries intermittently (and/or consistently depending on the device).  Resolving this by removing NextDNS from the equation points squarely to NextDNS being the source of the problem.