Help tracert excitel

[CDS]

Hi,

Anyone using excitel please share tracert to following ip 165.197.65.15

Thanks in advance

 

[JB701]

Host                                                                        Loss%   Snt   Last   Avg  Best  Wrst StDev
 1. 103.48.199.50                                                            50.0%     5    1.9   2.3   1.9   2.6   0.5
 2. (waiting for reply)
 3. 103.56.228.65                                                            25.0%     5    3.7   5.2   3.4   8.3   2.7
 4. 14.141.116.229.static-Delhi.vsnl.net.in                                   0.0%     5    2.8   2.2   1.7   2.8   0.4
 5. 172.31.180.57                                                             0.0%     5   41.7  41.7  41.0  42.1   0.4
 6. ix-ae-4-2.tcore1.cxr-chennai.as6453.net                                   0.0%     5   41.6  41.8  41.6  42.2   0.3
 7. if-ae-20-39.tcore2.svw-singapore.as6453.net                               0.0%     4   80.7  81.5  80.7  83.7   1.5
 8. if-ae-2-2.tcore1.svw-singapore.as6453.net                                 0.0%     4   79.5  80.9  79.5  82.6   1.3
 9. if-xe-0-0-0-6.thar1.ih4-singapore.as6453.net                              0.0%     4   71.5  71.4  70.6  71.9   0.6
10. 180.87.140.150                                                            0.0%     4   71.9  71.6  70.7  72.7   0.8
11. (waiting for reply)
12. 165.197.65.15                                                             0.0%     4   72.1  72.2  72.0  72.9   0.4

 

[CDS]

Thanks overall time is good, but don't understand why there is 50% packet lose at first point

 

[JB701]

idk Excitel's gateway seems to drop ping packets often (prevent flooding maybe?). i think its fine though as target has no Packet Loss.

Here ya go after running it 1 minute ish:

 Host                                                                        Loss%   Snt   Last   Avg  Best  Wrst StDev
 1. 103.48.199.50                                                            59.5%    89    1.8   1.9   1.1   2.9   0.5
 2. (waiting for reply)
 3. 103.56.228.65                                                            18.0%    89    4.7   9.1   2.8  64.7  11.3
 4. 14.141.116.229.static-Delhi.vsnl.net.in                                   0.0%    89    2.5   2.9   1.4  20.1   2.1
 5. 172.31.180.57                                                             0.0%    89   55.3  44.2  40.6  79.0   4.7
 6. ix-ae-4-2.tcore1.cxr-chennai.as6453.net                                  11.2%    89   41.8  42.8  40.6  73.2   4.5
 7. if-ae-20-39.tcore2.svw-singapore.as6453.net                               9.0%    89   80.6  81.6  79.7 100.7   3.4
 8. if-ae-2-2.tcore1.svw-singapore.as6453.net                                 0.0%    89   82.2  81.4  79.2 108.5   3.8
 9. if-xe-0-0-0-6.thar1.ih4-singapore.as6453.net                              0.0%    89   72.2  73.8  70.8 101.1   5.7
10. 180.87.140.150                                                            0.0%    89   71.5  71.2  70.3  75.1   0.7
11. (waiting for reply)
12. 165.197.65.15                                                             0.0%    88   71.2  72.4  71.0  80.3   1.5

 

[CDS]

02 gif

on Airtel, just see the weird route

 

[JB701]

Delhi->London->Singapore->HK->Singapore

Wtf lol

 

---

[CDS]

I have highlighted this, but they are saying can't help it

 

[JB701]

You could use a VPN temporarily.

I think you should contact Pepisco too, they can control routing as its their own ASN.

 

[CDS]

Not clear on ASN thing. Pepsico can control how many packets route from airtel to there server?

 

[JB701]

Yes to an extent , I've noticed that many server providers have a reroute tool to change the Transit provider used

NovoServe Looking Glass

Looking Glass

LookingGlass - Open source PHP looking glass

LG.yisp.nl

 

[CDS]

but on Jio, ACT and Excitel its the direct route reflecting to this server, why would they do this only for Airtel. Maybe there is configuration issue at Airtel side.

 

[igloo]

For my Airtel its london to sg. No hk trip.

 

[tapmal5]

traceroute to 165.197.65.15, 20 hops max, 38 byte packets
1 0.409ms 0.298ms 0.191ms 192.168.1.1(192.168.1.1)
2 3.849ms 44.198ms 1.714ms 172.16.0.1(172.16.0.1)
3 2.752ms 4.536ms 2.356ms 205.254.170.34(205.254.170.34)
4 2.131ms 2.271ms 1.723ms 14.141.116.229.static-Delhi.vsnl.net.in(14.141.116.229)
5 37.803ms 144.707ms 37.207ms 172.31.180.57(172.31.180.57)
6 40.800ms 41.165ms 40.699ms ix-ae-4-2.tcore1.cxr-chennai.as6453.net(180.87.36.9)
7 80.165ms 80.544ms 80.319ms if-ae-20-39.tcore2.svw-singapore.as6453.net(180.87.36.13)
8 79.504ms 79.563ms 79.712ms if-ae-2-2.tcore1.svw-singapore.as6453.net(180.87.12.1)
9 70.580ms 71.001ms 70.789ms if-xe-0-0-0-6.thar1.ih4-singapore.as6453.net(180.87.126.9)
10 70.520ms 70.164ms 70.761ms 180.87.140.150(180.87.140.150)
11 * * * Request timed out
12 72.945ms 73.099ms 72.522ms 165.197.65.15(165.197.65.15)
Trace Complete.