DNS latency fom


#1

Hi,

The latency between one of Maltas ISPs, Melita, and 1.1.1.1 is avg 55.24 ms, while the avg to 8.8.8.8 is 33 ms.

Can we do something about the peering or have a DNS pop in Malta?

Thanks!

Traceroute

$ traceroute 1.1.1.1
traceroute to 1.1.1.1 (1.1.1.1), 64 hops max, 52 byte packets
1 192.168.0.1 (192.168.0.1) 4.035 ms 2.889 ms 3.040 ms
2 XX.XX.XX.XX (XX.XX.XX.XX) 10.871 ms 11.475 ms 11.899 ms
3 185.89.137.169 (185.89.137.169) 12.433 ms 10.841 ms 15.902 ms
4 185.89.136.18 (185.89.136.18) 10.126 ms 11.970 ms 11.930 ms
5 mno-b2-link.telia.net (62.115.45.49) 46.049 ms 44.854 ms 43.874 ms
6 cloudflare-ic-306776-mno-b2.c.telia.net (213.248.94.54) 58.105 ms 57.005 ms 55.823 ms
7 1dot1dot1dot1.cloudflare- (1.1.1.1) 56.211 ms 55.312 ms 55.475 ms


#2

Would you mind just copying the result from here?


#3

#4

You are connecting to Milan’s POP, it’s kinda distant… Maybe @ryan can see why you are connecting so far away, maybe some kinda peering problem like you were saying.


#5

Would be great! Rome seems like a better peering point than Milano, geographically speaking.


#6

Yeah, it would. Even though Rome is worse in some respects (worse connections to the rest of Europe, especially for the likes of the standard Cloudflare offering). There is also Athens, but I presume you are mainly connected to us Italians! It could even be Telecom Italia Sparkle’s Seabone, don’t recall exactly the path.

Would you mind posting a traceroutes to 8.8.8.8? Just curious where it goes.


#7

Sure!

$ traceroute 8.8.8.8
traceroute to 8.8.8.8 (8.8.8.8), 64 hops max, 52 byte packets
1 192.168.0.1 (192.168.0.1) 3.629 ms 3.065 ms 3.003 ms
2 XX.XX.XX.XX (XX.XX.XX.XX) 11.049 ms 12.770 ms 15.749 ms
3 185.89.137.169 (185.89.137.169) 10.143 ms 11.421 ms 9.864 ms
4 185.89.136.38 (185.89.136.38) 10.289 ms 11.540 ms 10.048 ms
5 72.14.213.214 (72.14.213.214) 37.044 ms 33.639 ms 34.092 ms
6 108.170.245.65 (108.170.245.65) 34.875 ms 35.426 ms 34.207 ms
7 209.85.248.223 (209.85.248.223) 35.024 ms
209.85.255.223 (209.85.255.223) 35.907 ms
209.85.249.123 (209.85.249.123) 33.725 ms
8 google-public-dns-a.google.com (8.8.8.8) 35.103 ms 33.703 ms 33.985 ms


#8

I’ve asked our network team to look at the traceroute provided, and they believe there is room for improvement here, even if your requests are still served from Milan. They’ve reached out to a potential alternate peer, and we’re hopeful we can get that latency below 8.8.8.8!


#9

Any update, @amart? Packets are taking the same route with avg of 50 ms.
Thanks!


#10

I’m sorry, there’s been no news yet! Our network team has reached out to some alternate contacts as well, having not heard back on our first attempt. I’ll provide another update here by the end of the week. Thank you for sticking with us!


#11

Happy Friday! Just wanted to provide you with an update. The alternate peer solution does not appear to be viable at this time, due to some capacity issues at a third-party. However, our network team did reach out to Melita to see if we can work with them to address this latency. We’ll let you know if we’re able to make any progress on this front.