Routing Issue when using Mobile LTE - Optus in Melbourne, Australia

I seem to have routing issue when im using mobile LTE via optus. Im using nextdns app with Ultra Low Latency enable. As you can see in the picture, using ping.nextdns.io, it seems I am not connected to any of the server. But when i do test.nextdns.io, i am connected to gsl-mel which is not ultra low. Been happening for three days now.

I can’t run diag on mobile..

also why is anycast2 in anexia-ams or sometimes in lax? Sometimes it goes there and my mobile internet is extremely slow. I believe all my connections regardless of its ultra low or anycast should be in the Oceania / Australian region.

note that this does not happen when im connected to my wifi which is Superloop - my isp. It only happens when i’m connected to LTE which is optus.

1reply Oldest first
  • Oldest first
  • Newest first
  • Active threads
  • Popular
  • I guess this question and issue is dead now as no one seems to be checking this routing issue from nextdns team,

    I really think that you guys need to up your support. I am willing to pay extra for the proper support. Probably it’s time to upgrade your Pro subscription (i have this) to include support not just for business users.

    this kind of community support is not helpful and it sucks if the issue requires checking in the server.

    it would be ok, if im always at home, but the thing is i work out side and most of the time in LTE.

    my connections goes to LAX or AMS most of the time in mobile. using ping.nextdns.io, its not showing me where i am connected, i only came to know when i do the browserleak and the test.nextdns.io.

    Sometimes Its slow, sometimes i need to wait for the connection to kick in after i wake my mobile from sleep.

Like Follow
  • 2 mths agoLast active
  • 1Replies
  • 51Views
  • 2 Following