So if someone wouldn't mind testing a trace to the same ip from other parts of US, like central, south and west, that would be great thanks..
The address range that has problems seems to be 62.179.100.0 to 62.179.102.255
Its owned by Chello Europe, they have the block of 62.178.0.0 - 62.179.255.255 but as far as I can all the other ranges routes fine...
I've been testing on 62.179.100.80 and 62.179.100.50
here is my trace:
Code: Select all
traceroute to 62.179.100.80 (62.179.100.80), 30 hops max, 38 byte packets
1 192.168.230.254 (192.168.230.254) 16.193 ms 1.550 ms 1.506 ms
2 10.15.1.1 (10.15.1.1) 17.425 ms 20.400 ms 18.082 ms
3 at-1-1-0-1710.CORE-RTR1.BUFF.verizon-gni.net (130.81.8.242) 19.497 ms 20.100 ms 18.218 ms
4 so-0-3-1-0.CORE-RTR2.BUFF.verizon-gni.net (130.81.4.149) 18.819 ms 19.019 ms 18.809 ms
5 t3-0-0-2-0.CORE-RTR1.NY5030.verizon-gni.net (130.81.4.89) 87.631 ms 77.098 ms 26.729 ms
6 so-0-2-0-0.BB-RTR2.NY5030.verizon-gni.net (130.81.8.74) 26.411 ms 27.830 ms 26.406 ms
7 so-4-0-0-0.CORE-RTR1.NY60.verizon-gni.net (130.81.4.106) 28.160 ms 27.040 ms 28.922 ms
8 so-1-0-0-0.PEER-RTR1.NY60.verizon-gni.net (130.81.4.210) 29.601 ms 30.676 ms 29.067 ms
9 jfk-edge-20.inet.qwest.net (65.116.172.85) 28.363 ms 62.599 ms 35.235 ms
10 jfk-core-01.inet.qwest.net (205.171.230.14) 29.157 ms 30.370 ms 74.118 ms
11 jfk-brdr-01.inet.qwest.net (205.171.30.14) 37.092 ms 28.586 ms 29.389 ms
12 pos1-1.core1.NewYork1.Level3.net (209.244.160.129) 30.082 ms 29.547 ms 29.429 ms
13 gige7-2.ipcolo2.NewYork1.Level3.net (64.159.17.164) 31.290 ms 29.740 ms 28.366 ms
14 * * *
15 * * *