Skip to content

Why does my German VPS route through US?

VPS Hosting Locked by pdxltd 27 replies 3.2K views
This thread is locked — new replies are not accepted. (Closed: the question was answered)
10 #1

My German VPS routes through the US
Traceroute shows Ashburn hops
Ping from Lisbon is 120ms
Users complain about slow SSL
Is this normal or a misconfig

#2

So I got this CloudCone vps in Los Angeles supposedly right but my traceroute shows me going through ashburn virginia what gives im pinging from lisbon and getting 120ms instead of like 40 this makes no sense my users are complaining about slow ssl handshake and I dont even know if this is my fault or theirs or what — https://www.ssllabs.com/ssltest/

#3
  • Check your DNS first
  • Run mtr not just traceroute
  • Post the full route here
  • What resolver are you using
#4

Zats wild bro lol U using there anycast dns or sumzin Check if ur vps provider using cloudflare or google dns by default

world record: 4min Arch install
#5
Lou1 said:
Run mtr not just traceroute

How do I run mtr? I installed it but it says I need root. Is that safe? My site is live and I dont want to break anything

Also my ping from Berlin to my RackNerd server shows US hops too. Thought it was just me.

3 #6

This is classic Anycast problem bro. I see this on Vultr too, they use same DNS setup, is very good for DDoS but geolocation goes crazy 😂

We make a test: change your /etc/resolv.conf to 185.228.168.168 (CleanBrowsing) and see if route fixes!

#7

So I looked into this because I had the exact same problem with my OVHcloud box last year and it turned out to be a combination of things and the provider was using anycast dns and the anycast nodes were announcing the same ip space from multiple locations and my traffic was getting sucked into the closest anycast node which happened to be in virginia instead of germany and the dns resolution was happening at the anycast node so the return path was all wrong and the latency was terrible and I spent like three days on this and the support ticket kept bouncing between departments and nobody understood what I was talking about and eventually I figured out that if I just ran my own unbound resolver locally on the vps and pointed everything at that instead of using the providers dns then the outbound queries went straight from Frankfurt to wherever they needed to go and the geolocation datab

#8

I had this exact same problem with anycast dns, drove me nuts

#9

What kernel you running on that CloudCone box

3 #10
HieuTce said:
Eventually I figured out that if I just ran my own unbound

Did you finish that sentence? What happened with unbound? I need to know if this fixes it before I open another ticket with CloudCone. Their support takes forever.

Thread closed

Replies are closed on this thread. Closed: the question was answered.