Fastweb Italy not resolving to the closet datacenter


#1

Hi guys,

so I am at a friend’s house and his Fastweb internet link, while interconnected at MIX sends the traffic to NaMeX.

It’s the same kind of issue that happened here with Tiscali:

The network connection is still in Turin.

1.1.1.1 and all of Cloudflare’s network goes to Rome, while as demonstrated below by Google (which is only in Milan) MIX is faster.

Since you already dealt with Fastweb, can you help this @amart?

traceroute to 1.1.1.1 (1.1.1.1), 64 hops max, 52 byte packets
 1  myfastgate (192.168.1.254)  1.069 ms  0.512 ms  0.445 ms
 2  10.1.3.151 (10.1.3.151)  1.846 ms  1.808 ms  1.277 ms
 3  10.1.96.30 (10.1.96.30)  2.536 ms  1.805 ms
    10.1.96.38 (10.1.96.38)  2.449 ms
 4  10.1.31.106 (10.1.31.106)  2.142 ms  2.282 ms  1.567 ms
 5  10.1.31.101 (10.1.31.101)  2.392 ms  1.990 ms  1.369 ms
 6  10.254.20.213 (10.254.20.213)  2.973 ms  4.119 ms  3.829 ms
 7  62-101-124-125.fastres.net (62.101.124.125)  3.900 ms
    62-101-124-129.fastres.net (62.101.124.129)  4.129 ms
    62-101-124-125.fastres.net (62.101.124.125)  4.417 ms
 8  93.57.68.9 (93.57.68.9)  13.470 ms  13.085 ms
    93.57.68.13 (93.57.68.13)  13.632 ms
 9  93.57.68.221 (93.57.68.221)  13.889 ms
    93.57.68.217 (93.57.68.217)  12.697 ms  14.133 ms
10  cloudflare-nap.namex.it (193.201.28.33)  14.128 ms  13.793 ms  13.922 ms
11  1dot1dot1dot1.cloudflare-dns.com (1.1.1.1)  13.885 ms  13.814 ms  13.707 ms
traceroute to google.com (216.58.205.206), 64 hops max, 52 byte packets
 1  myfastgate (192.168.1.254)  0.822 ms  0.300 ms  0.233 ms
 2  10.1.3.151 (10.1.3.151)  1.527 ms  0.769 ms  1.227 ms
 3  10.1.96.38 (10.1.96.38)  1.300 ms  1.915 ms
    10.1.96.30 (10.1.96.30)  1.298 ms
 4  10.1.31.106 (10.1.31.106)  2.545 ms  1.801 ms  2.112 ms
 5  10.1.31.101 (10.1.31.101)  2.510 ms  1.455 ms  2.651 ms
 6  10.254.20.213 (10.254.20.213)  4.045 ms  4.225 ms  3.774 ms
 7  62-101-124-129.fastres.net (62.101.124.129)  4.143 ms
    62-101-124-125.fastres.net (62.101.124.125)  4.382 ms
    62-101-124-129.fastres.net (62.101.124.129)  4.347 ms
 8  89.96.200.122 (89.96.200.122)  3.735 ms  4.307 ms
    89.96.200.46 (89.96.200.46)  13.961 ms
 9  93.62.86.153 (93.62.86.153)  3.530 ms  3.988 ms  3.763 ms
10  * * *
11  216.239.42.14 (216.239.42.14)  6.193 ms
    216.239.48.230 (216.239.48.230)  4.723 ms
    216.239.48.228 (216.239.48.228)  4.790 ms
12  216.239.42.27 (216.239.42.27)  4.384 ms  4.469 ms
    216.239.42.25 (216.239.42.25)  3.616 ms
13  mil04s29-in-f14.1e100.net (216.58.205.206)  4.546 ms  3.406 ms  3.673 ms
``

#2

I’ve asked the same engineer who helped me last time if this is something we’ll be able to help with. I can’t guarantee anything. I do see that we’re still responding pretty quickly here, but hopefully we can improve things even further.


#3

With the other ISP it was relatively a quick fix! It should get down from 12ms to around 4. Plus it should distribute the load (especially for 1.1.1.1). This applies to all of Cloudflare’s network, not only 1.1.1.1.

Thanks!


#4

Just wanted to give you an update that we haven’t had a response to our request yet. I’ll let you know as soon as we’ve made progress.


#5

Thanks a lot! It doesn’t surprise me given Fastweb’s reputation here… Hope they reply!


#6

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.