0

Latency Issues - possible issue w/ Atlanta

First noticed this back on 5/10, during MS Teams calls started to get audio drop , after doing some troubleshooting saw that my jitter was really high and latency was also higher than normal with some transient packet dropping.  First step was to remove NextDNS from my network chain - I use a router with OpnSense, using Unbound DNS to do DNS over TLS to my NextDNS anycast ips.

Reintroduced NextDNS back into my network today and immediately experienced the same thing.  I have found the bufferbloat test on waveform also mimics the same behaviour as I see in MS Teams - with NextDns in the loop my latency and jitter go way up.  With it not there everything is fine.  Furthermore I have found if I only include the ip for Chicago, and not Atlanta - these are the two I am resolving to currently, that I also do not get any issues.  So it appears there might be issues with my route to Atlanta

Here are my diag results https://nextdns.io/diag/1a43d840-191b-11ef-8f30-0bcec8ec0f19

 

Also attaching waveform test results with and without nextdns

3 replies

null
    • NextDNs
    • 6 mths ago
    • Reported - view

    DNS has no impact on buffer bloat. It is likely something else going on between the two tests.

    • Jeremy_Lee
    • 6 mths ago
    • Reported - view

    Cool well I guess I am killing my subscription because as of 2 weeks ago with NextDNS in the mix the performance with MS Teams is unacceptable for some unknown reason and if I remove it from the equation then its fine. If you have guidance on how I could troubleshoot great - otherwise I guess I will look for a different solution

    I only included the buffer bloat results as those co-related to the issues I was seeing in MS Teams

      • NextDNs
      • 5 mths ago
      • Reported - view

       your diag looks good and DNS shouldn't cause this kind of issue. There is not much we can do at our level.

Content aside

  • 5 mths agoLast active
  • 3Replies
  • 57Views
  • 2 Following