3

My NextDNS Analytics and Logs are broken

I don't know if this is only my issue, but it looks to me like it's failing to fetch the API.

21 replies

null
    • NextDNs
    • 12 days ago
    • Official response
    • Reported - view

    We are working on a resolution. 

      • NextDNs
      • 12 days ago
      • Reported - view

       logs and analytics access is restored. Apologies for the inconvenience.

      • Harp_Gosal
      • 12 days ago
      • Reported - view

      works but loading analytics and log pages takes a very long time.

      • Harp_Gosal
      • 12 days ago
      • Reported - view

       longer loading times and I get the network error come up quickly and disappear on the Analytics screen. On the Logs page I can’t stream log events. And the page takes a long while to load. I don’t think it’s entirely fixed 

      • CraigpII
      • 12 days ago
      • Reported - view

       Mine is still very much broken. I can't access individual devices in my logs. And loading of the analytics page is slow and has crashes. Using on browser and Android app. If I wait for long enough the devices drop down becomes selectable. If I select an individual profile it doesn't load any of the log data. Just an infinite buffer.

    • Dan.46
    • 12 days ago
    • Reported - view

    Having the same issue

    • Franky
    • 12 days ago
    • Reported - view

    I'm getting errors on GET calls when I go there as well.  I just signed up for Pro yesterday and hadn't gone to them since so was worried this was somehow related to that.

     

    'Network Error
    GET /profiles/xxxxxx/analytics/domains'

    and

    'Network Error
    GET /profiles/xxxxxx/logs'

    Lots of stuff like that.

    • Harp_Gosal
    • 12 days ago
    • Reported - view

    Yep same issue here too

    • Lucasa
    • 12 days ago
    • Reported - view

    same here

    • Mell
    • 12 days ago
    • Reported - view

    Here too

    • Colleen
    • 12 days ago
    • Reported - view

    same, I was freaking out thinking I did somethings wrong

    • Changho_Hwang
    • 12 days ago
    • Reported - view

    I just checked and it's like that.

    • Dhunt
    • 12 days ago
    • Reported - view

    Historic similar topics answered by updates in progress. 

    • Lucasa
    • 12 days ago
    • Reported - view

    I don’t think it’s entirely fixed

    • Lucasa
    • 12 days ago
    • Reported - view

    I don’t think it’s entirely fixed

    • Rey.2
    • 11 days ago
    • Reported - view

    Same issue here

    • A_drianne
    • 4 days ago
    • Reported - view

    I was having the same major issues with the app, I had to uninstall it and just use the browser until it's fixed...

    • Lucasa
    • 2 days ago
    • Reported - view

    1) API = Slow again this morning!   

    • Jlchandler
    • 2 days ago
    • Reported - view

    I'm experiencing the same issue. Logs are taking very long to load. Hopefully this is still being worked on.

    • Harp_Gosal
    • 2 days ago
    • Reported - view

    Yes same here, everything is super slow again <sigh>

    • Lucasa
    • 2 days ago
    • Reported - view

    2) There may be a misconfiguration of routing to DNS servers in the East Coast to locate "US servers"? 
     - Usually there are "2-3 US DNS servers" that NextDNS uses to resolve queries.
    - Today we are seeing that NextDNS is using 1 DNS server. https://browserleaks.com/dns
     - 66.135.25.157    The Constant Company, LLC    United States, Piscataway.
    - This usually happens right before NextDNS services failover to overseas DNS servers in Australia, Russia, etc for queries.

Login to reply

Content aside

  • Status Fixed
  • 3 Likes
  • 2 days agoLast active
  • 21Replies
  • 330Views
  • 14 Following