Can someone post their tracert results

Tracing route to 185.116.159.59 over a maximum of 30 hops

1 6 ms 1 ms 14 ms 192.168.0.1
2 5 ms 5 ms 2 ms 100.68.0.1
3 * 3 ms 6 ms dhcp-192-217-37.in2cable.com [203.192.217.37]
4 * * 4 ms 115.117.107.141.static-kolkatta.vsnl.net.in [115.117.107.141]
5 7 ms 6 ms 5 ms 172.28.177.206
6 5 ms 6 ms 6 ms ix-ae-1-100.tcore2.mlv-mumbai.as6453.net [180.87.39.25]
7 128 ms 130 ms 130 ms if-ae-2-2.tcore1.mlv-mumbai.as6453.net [180.87.38.1]
8 133 ms * * if-be-6-2.ecore1.emrs2-marseille.as6453.net [195.219.174.16]
9 * * * Request timed out.
10 * 133 ms * if-ae-50-2.tcore2.fnm-frankfurt.as6453.net [195.219.87.214]
11 128 ms 129 ms 130 ms if-be-11-2.ecore2.f2c-frankfurt.as6453.net [195.219.87.51]
12 * * * Request timed out.
13 * * * Request timed out.
14 133 ms 135 ms 133 ms 185.116.159.59

Trace complete.


Tracing route to 185.107.194.161 over a maximum of 30 hops

1 1 ms 1 ms 1 ms 192.168.0.1
2 4 ms 6 ms 7 ms 100.68.0.1
3 5 ms * 5 ms dhcp-192-217-37.in2cable.com [203.192.217.37]
4 * 13 ms * 115.117.107.141.static-kolkatta.vsnl.net.in [115.117.107.141]
5 33 ms 29 ms 33 ms 172.17.169.202
6 29 ms 29 ms 26 ms ix-ae-4-2.tcore1.cxr-chennai.as6453.net [180.87.36.9]
7 65 ms * * if-be-34-2.ecore2.esin4-singapore.as6453.net [180.87.36.41]
8 63 ms 62 ms 62 ms 180.87.108.145
9 68 ms 70 ms 72 ms 4.69.218.94
10 66 ms 66 ms 66 ms 8.245.6.70
11 61 ms 62 ms 62 ms sin-eqx-02t.voxility.net [103.31.184.6]
12 193 ms 194 ms 194 ms fra-eqx-02t.voxility.net [93.115.91.27]
13 192 ms 194 ms 194 ms fra-eq5-02c.voxility.net [5.254.61.221]
14 189 ms 190 ms 190 ms fra-eq5-04sw.voxility.net [5.254.68.150]
15 191 ms 190 ms 193 ms 5.254.14.94
16 203 ms 201 ms 199 ms lag6.core2-dus3.bb.as24961.net [62.141.47.86]
17 199 ms 196 ms 196 ms ae0-1014.r01-a1-7.dus.onecorp.eu [89.163.136.201]
18 195 ms 194 ms 195 ms 185.107.194.161

Trace complete.
 
@AD2011 For some reason it shows kolkatta in the traceroute but they aren't from Kolkata. My latency to 115.117.107.141.static-kolkatta.vsnl.net.in [115.117.107.141] is only 5ms so it's most likely located in Mumbai. Also, their latency to ix-ae-1-100.tcore2.mlv-mumbai.as6453.net [180.87.39.25] is 5 ms
 
Hmm.
TATA's latency to Kolkata is horrible.
70ms to Singapore
40ms to Mumbai
40ms to Chennai
compared to 55ms for singapore, 25-30ms for mumbai and chennai for jio and airtel
 
Most IPs, when shuffled, often do not get their DNS names changed. There is nothing alarming about that.

Code: 
 1  110.226.143.255  0%       3  3.5ms    4.2    3.5    5.3    0.8
 2  122.186.210.5    0%       3  3.5ms    3.8    3.5    4.2    0.3
 3  116.119.57.86    0%       3  100.2ms  100.4  100.2  100.7  0.2
 4  80.81.193.252    0%       3  135.4ms  135.4  135.3  135.4  0.1
 5                   100%     2  timeout
 6                   100%     2  timeout
 7                   100%     2  timeout
 8                   100%     2  timeout
 9  169.254.253.2    0%       2  124.7ms  125.3  124.7  125.9  0.6
10  185.116.159.59   0%       2  124.2ms  124.2  124.1  124.2  0.1

 1  100.68.0.1      0%       2  1.5ms    1.7    1.5    1.9    0.2
 2  203.192.217.37  50%      2  timeout  1.1    1.1    1.1    0
 3                  100%     2  timeout
 4  172.28.177.206  0%       2  1.8ms    1.9    1.8    1.9    0.1
 5  180.87.39.25    0%       2  1.3ms    1.6    1.3    1.8    0.3
 6  180.87.38.1     0%       2  124.4ms  124.2  123.9  124.4  0.3      <MPLS:L=618899,E=1>
 7  195.219.174.16  50%      2  timeout  123.8  123.8  123.8  0
 8                  100%     2  timeout
 9  195.219.87.214  50%      2  125ms    125    125    125    0        <MPLS:L=104677,E=1>
10  195.219.87.51   0%       2  124.9ms  124.9  124.9  124.9  0
11                  100%     2  timeout
12  169.254.253.2   0%       2  124.5ms  124.6  124.5  124.7  0.1
13  185.116.159.59  0%       2  128.4ms  128.4  128.4  128.4  0

Code: 
 1  110.226.143.255  0%       3  3.9ms    4.5    3.4    6.1    1.2
 2  122.186.210.5    0%       3  4ms      3.9    3.6    4      0.2
 3  116.119.57.82    0%       3  101.6ms  100.8  100.2  101.6  0.6
 4  80.81.193.252    0%       3  130.4ms  130.6  130.4  130.7  0.2
 5                   100%     2  timeout
 6                   100%     2  timeout
 7                   100%     2  timeout
 8                   100%     2  timeout
 9  169.254.253.2    0%       2  118.9ms  119.2  118.9  119.4  0.3
10  185.107.194.161  0%       2  119.6ms  119.8  119.6  119.9  0.2

 1  100.68.0.1       0%        3  0.9ms    1.4    0.9    1.9    0.4
 2  203.192.217.37   33.3%     3  1.1ms    1.2    1.1    1.2    0.1
 3  115.117.107.141  0%        3  1.9ms    1.8    1.8    1.9    0
 4  172.28.177.206   0%        3  1.9ms    1.9    1.8    1.9    0
 5  180.87.39.25     0%        3  1.2ms    1.7    1.2    2      0.4
 6  180.87.38.1      0%        3  123.7ms  123.7  123.7  123.7  0        <MPLS:L=618899,E=1>
 7                   100%      2  timeout
 8                   100%      2  timeout
 9  195.219.87.214   50%       2  timeout  124.6  124.6  124.6  0        <MPLS:L=104677,E=1>
10  195.219.87.51    0%        2  124.8ms  124.9  124.8  124.9  0.1
11                   100%      2  timeout
12  169.254.253.2    0%        2  124.1ms  124.6  124.1  125    0.5
13  185.107.194.161  0%        2  124ms    124    124    124    0
 
@Lolita_Magnum thanks

Also, I recently took ION broadband and tried doing a traceroute but seems like they have blocked tracerouting which is weird. I contacted the technician and he said you can't traceroute on dynamic ip on pppoe and if you take static ip then you can which makes no sense at all. Do you know any workaround for doing traceroute? I just want to figure out which transit they are using.
 
Ah, yes. You cannot do traceroute on ION Broadband, even with a static IP. He's trying to upsell you.

ION primarily uses Tata, so there should not be much difference.
 
You must log in or register to reply here.
Back