Slow performance and bad routing
Olivier Poitrey
I've noticed considerably slower performance on NextDNS compared to other providers. I see frequently that my traffic to CDN providers is being routed incorrectly, sometimes even to other countries.
I'm also seeing several hundred ms response to the primary server when the secondary is in the single digits.
There are multiple reports of the same on the forum but little to no support being offered. How do we get this corrected? I paid for a membership to the service but am so far very unhappy.
Screenshots can be found in the other thread I posted in: https://help.nextdns.io/t/35htz6q?r=x2htzbt
17 replies
-
Submitted diagnostics
Here's an example of a CDN (fastly) incorrectly routing traffic
NextDNS:Tracing route to 151.101.6.114 over a maximum of 30 hops 1 2 ms 1 ms 1 ms <removed> 2 7 ms 15 ms 4 ms <removed> 3 * * * Request timed out. 4 8 ms 8 ms 5 ms 12.242.116.11 5 5 ms 5 ms 5 ms mai-b1-link.telia.net [62.115.11.1] 6 6 ms 5 ms 5 ms mai-b2-link.ip.twelve99.net [62.115.125.6] 7 17 ms 17 ms 19 ms fastly-svc073090-ic360831.c.telia.net [62.115.148.111] 8 224 ms 202 ms 202 ms 151.101.6.1144.2.2.1
Tracing route to 151.101.206.114 over a maximum of 30 hops 1 1 ms 1 ms 1 ms <removed> 2 6 ms 4 ms 12 ms <removed> 3 * * * Request timed out. 4 25 ms 22 ms 30 ms 12.240.210.118 5 20 ms 21 ms 20 ms cr2.ormfl.ip.att.net [12.123.6.50] 6 23 ms 24 ms 18 ms attga21crs.ip.att.net [12.122.28.197] 7 18 ms 18 ms 20 ms 12.240.212.165 8 * * * Request timed out. 9 17 ms 18 ms 16 ms 151.101.206.114 -
Olivier Poitrey
I understand you can't control issues with fastly, but the point is that NextDNS is resolving to the first trace I posted and other providers (4.2.2.1, Google, OpenDNS) are resolving to the second.
I've had to add several Rewrites to the second IP just to be able to get them to load.
Please take a look at these domains and see why NextDNS is resolving them differently than so many other providers.
I submitted the diag but do not have the ID anymore. I did include my email, so hopefully you can locate it that way.
-
FYI I've opened a case with Fastly to investigate as well: Case (#332562)
Regardless of their findings, I would like to know why there is a discrepancy between NextDNS, Level3, OpenDNS and Google resolution.
I would also like to know why I'm seeing 100-200+ ms response from vultr-mia and why Olivier Poitrey has repeatedly ignored my post reporting this and flagged me as needing moderation
-
tobycth3 the forum we use sometime flag posts when it contains links or images, we always manually approve them. I can't find repeated post from you about this subject. I just spent some time chasing your diag ID as you won't provide it, and it seems that you are getting an unstable ping to vultr-mia. Please perform another diag to confirm.
-
Olivier Poitrey You've switched community forums so I can no longer link to the previous posts that I've made, however here are at least 2 posts I've made since you've switched. I never refused to provide a diag ID, I simply closed out of the window and didn't access to it. I will DM you the new ID since it contains PII that anyone can access.
-
tobycth3 those are comments on other posts, I missed them. PII is redacted in diag.
-
Olivier Poitrey FYI still seeing 100+ms latency
-
tobycth3 vultr didn’t find anything abnormal
-
Olivier Poitrey can you have them check during the evening hours? During the day the latency is normal 5-25ms response. From 5pm on it keeps getting worse until it's 100-200+ms response
To me it sounds like congestion or oversubscription on their network
How can I route around this? Seeing that it's the primary "ultra low" resolver, it's making everything super slow during peak times.
-
Olivier Poitrey Sorry to see you having to deal with high maintenance and attitude from inconsiderate users such as thistobycth3
-
James G what makes you say I am an inconsiderate user? 200+ ms response times indicate an major issue which is impacting performance. I'm here asking for help and reporting an issue...
-
tobycth3 You are being somewhat entitled and combative with the person who is making an effort to assist you, that's all. No need for that here.
-
James G asking for support and reporting issues in the proper location, using the proper channels is entitled?
I'm providing feedback and troubleshooting data, most via DM that you can't see, to help resolve an issue and improve their service.
There are several threads reporting performance and routing issues, which is exactly what this forum is for - it even says so right in the title
"Bug Reports
Help us improve NextDNS by reporting bugs."
-
-
NextDNS resolve time very slow for me as well, several seconds to resolve most sites. Frustrating!
-
Olivier Poitrey Any update? Still seeing insane latency during peak times. How can I stop connecting to vultr? Can I route to a different pop if you are unable to fix this?
Content aside
- 1 yr agoLast active
- 17Replies
- 720Views
-
6
Following