0

Bad routing to Fastly (Reddit) and Twitch via anexia-mow-1 since late March

Hello,
I am experiencing constant buffering on Reddit and Twitch when using NextDNS Private DNS (DoT) on Android. This issue started in late March.

My current node is anexia-mow-1.
When I check fastly-debug.com, it shows I am being routed to RTM (Rotterdam), which seems to be congested or has poor peering with my ISP.

In contrast, AdGuard DNS routes me through CPH (Copenhagen) to BMA (Stockholm), where everything works perfectly.

Is it possible to optimize the routing for the Moscow node or adjust the CDN steering for Fastly/Twitch?

My setup:
Protocol: DNS-over-TLS (Android Private DNS)
Node: anexia-mow-1
ISP: [https://chetelecom.ru/]

2 replies

null
    • NextDNs
    • 4 days ago
    • Reported - view

    Please provide a https://nextdns.io/diag

      • qubwez
      • 4 days ago
      • Reported - view

       
      Testing IPv6 connectivity
        available: false
      Fetching https://test.nextdns.io
        status: unconfigured
        client: 178.57.99.203
        resolver: 74.125.114.145
      Fetching PoP name for ultra low latency primary IPv4 (ipv4.dns1.nextdns.io)
        anexia-mow: 12.006ms
      Fetching PoP name for ultra low latency secondary IPv4 (ipv4.dns2.nextdns.io)
        zepto-mow: 22.078ms
      Fetching PoP name for anycast primary IPv4 (45.90.28.0)
        zepto-mow: 15.168ms
      Fetching PoP name for anycast secondary IPv4 (45.90.30.0)
        anexia-fra: 42.016ms
      Pinging PoPs
        anexia-mow: 12.526ms
        zepto-mow: 16.994ms
        hetzner-hel: 23.765ms
        edis-vno: 33.536ms
        zepto-sto: 48.103ms
        hostens-vno: 52.313ms
        anexia-iev: 55.635ms
        tavu-hel: 59.702ms
        zepto-iev: 67.847ms
        anexia-sto: 51.261ms
      Traceroute for ultra low latency primary IPv4 (37.252.254.39)
          3  192.168.39.53    1ms   1ms   4ms
          4  192.168.39.17    1ms   4ms   1ms
          5   178.57.96.29    2ms   3ms   2ms
          6  188.43.30.126    4ms   4ms   4ms
          7 139.45.232.247   13ms  12ms  12ms
          8 139.45.232.246   12ms  11ms  11ms
          9   139.45.243.6   15ms  14ms  12ms
         10  139.45.254.33   12ms  13ms  12ms
         11   94.16.101.32   12ms  11ms  17ms
         12  37.252.254.39   12ms  11ms  11ms
      Traceroute for ultra low latency secondary IPv4 (45.142.246.128)
          3  192.168.39.53    1ms   1ms   1ms
          4  192.168.39.17    1ms   1ms   1ms
          5   178.57.96.29    5ms   1ms   4ms
          6  188.43.30.126    5ms   4ms   4ms
          7 217.150.45.102   11ms  10ms  10ms
          8 217.150.45.101   17ms  20ms  26ms
          9     10.32.0.25   20ms  20ms  19ms
         10  45.11.107.227   16ms  17ms  16ms
         11                   *     *     *
         12 45.142.246.128   16ms  17ms  16ms
      Traceroute for anycast primary IPv4 (45.90.28.0)
          2    10.64.200.1    1ms   1ms   1ms
          3  192.168.39.53    1ms   2ms   1ms
          4  192.168.39.17    4ms   1ms   4ms
          5   178.57.96.29    8ms  11ms   8ms
          6  188.43.30.126    4ms   4ms   6ms
          7 217.150.45.102   16ms  17ms  16ms
          8 217.150.45.101   23ms  22ms  22ms
          9     10.32.0.25   25ms  23ms  22ms
         10  45.11.107.227   21ms  21ms  24ms
         11                   *     *     *
         12     45.90.28.0   20ms  20ms  20ms
      Traceroute for anycast secondary IPv4 (45.90.30.0)
          2    10.64.200.1    1ms   1ms   1ms
          3  192.168.39.53    1ms   4ms   1ms
          4  192.168.39.17    2ms   3ms   6ms
          5   178.57.96.29    4ms   4ms   2ms
          6  188.43.30.126    6ms   6ms   4ms
          7  80.81.194.117   49ms  51ms  49ms
          8   80.81.192.68   47ms   *    60ms
          9 144.208.208.146   46ms  46ms  45ms
         10 144.208.208.144   45ms  45ms 110ms
         11     45.90.30.0   45ms   *    46ms

Login to reply

Content aside

  • 14 hrs agoLast active
  • 2Replies
  • 36Views
  • 2 Following