1

Routing Optimization Request: High Latency in Azerbaijan (78-82ms) compared to competitors

Hello NextDNS Team,

 

I am writing to request a routing optimization for users connecting from Azerbaijan. Currently, NextDNS latency hovers around 78-82ms, which is suboptimal compared to other major providers in our region.

 

For context, here is the current network ecosystem latency from my ISP in Azerbaijan:

- Cloudflare (1.1.1.1): ~7ms (Utilizing a local Edge node in Baku)

- Google DNS (8.8.8.8): ~38ms

- AdGuard DNS (94.140.14.49): ~63ms (They recently optimized routing to Frankfurt fra-23 via Anycast after a community request)

 

Here is my NextDNS ping result (45.90.28.0):

64 bytes from 45.90.28.0: icmp_seq=1 ttl=53 time=78.4 ms

64 bytes from 45.90.28.0: icmp_seq=2 ttl=53 time=78.3 ms

64 bytes from 45.90.28.0: icmp_seq=3 ttl=53 time=76.7 ms

 

Here is my AdGuard ping result for comparison (94.140.14.49):

64 bytes from 94.140.14.49: icmp_seq=1 ttl=56 time=63.3 ms

64 bytes from 94.140.14.49: icmp_seq=2 ttl=56 time=62.8 ms

64 bytes from 94.140.14.49: icmp_seq=3 ttl=56 time=66.3 ms

 

Since I cannot run the diagnostic script due to not having root access on my device, I am providing these direct ping metrics. Our traffic to NextDNS seems to be taking an inefficient path.

 

Given that other providers have successfully optimized their Anycast routing for Azerbaijani ASNs, we believe NextDNS can achieve a much better response time (closer to ~60ms or lower) by adjusting the BGP announcements or partnering with closer transit nodes.

 

Could your network engineers please look into optimizing the routing for Azerbaijan? 

 

Thank you!

2 replies

null
    • NextDNs
    • 6 hrs ago
    • Reported - view

    Please provide a https://nextdns.io/diag and paste the URL here.

      • Mirli
      • 5 hrs ago
      • Reported - view

      Thank you for looking into this! 

       

      I am currently running NextDNS on a non-rooted Android/iOS mobile device, so running the official `nextdns.io/diag` script is not giving me a URL due to permission constraints.

       

      However, here are the exact network details, Anycast IP, and route information from my connection in Azerbaijan so your team can pinpoint the routing issue:

       

      ### 1. Ping Metrics to NextDNS Anycast (45.90.28.0):

      ```bash

      64 bytes from 45.90.28.0: icmp_seq=1 ttl=53 time=78.4 ms

      64 bytes from 45.90.28.0: icmp_seq=2 ttl=53 time=78.3 ms

      64 bytes from 45.90.28.0: icmp_seq=3 ttl=53 time=76.7 ms

      2. Provider Context (Azerbaijan) My ISP: Azfibernet Current Latency: ~78ms - 82ms (Usually routed through suboptimal European transit nodes) 3. Comparison with Competitors: Cloudflare (1.1.1.1): ~7ms (Via local Baku edge) AdGuard DNS: ~63ms (Recently optimized their BGP routing to Frankfurt fra-23 for Azerbaijan ASNs after a similar request) 

       

      Since we cannot generate the automated diag URL from this mobile terminal, could you please share the specific IP/server (e.g., FRA, MXP, etc.) that Azerbaijani traffic is currently hitting? We believe a quick BGP adjustment with upstream transit providers could lower this to ~60ms, just like AdGuard did.

       

      Thank you for your support!

Login to reply

Content aside

  • 1 Votes
  • 5 hrs agoLast active
  • 2Replies
  • 26Views
  • 2 Following