High Ping Times to Airtel Servers from TATA network

  • Thread starter Thread starter merc782
  • Start date Start date
  • Replies Replies 1
  • Views Views 3,509
Status
Not open for further replies.
M

merc782

Regular
Messages
409
Location
NA
ISP
BSNL, Reliance netconnect
Started observing high ping times to all Airtel Servers and IP addresses from TATA wimax connection in Bangalore, any body else seeing this behavior.

tracert shows spike in latency at hop 59.163.16.229, which is a TATA IP, so issue seems to be on tata side.

Code: 
C:\>tracert -w 600 airtel.inTracing route to airtel.in [125.19.17.20]over a maximum of 30 hops:  1     2 ms     1 ms     1 ms  dataone-adsl-router [192.168.1.1]  2    36 ms    39 ms    40 ms  121.243.182.33.static-bangalore.vsnl.net.in [121.243.182.33]  3    37 ms   119 ms    39 ms  172.31.241.25  4    34 ms    40 ms    89 ms  172.31.78.66  5    36 ms    49 ms    39 ms  172.31.78.85  6    76 ms    39 ms    39 ms  172.31.9.197  7   124 ms    39 ms    39 ms  172.31.2.226  8    54 ms    39 ms    40 ms  172.31.1.230  9    36 ms    39 ms    79 ms  172.31.2.69 10    76 ms    70 ms   119 ms  59.163.16.58.static.vsnl.net.in [59.163.16.58] 11    96 ms    69 ms    69 ms  59.163.16.13.static.vsnl.net.in [59.163.16.13] 12   105 ms    69 ms    69 ms  59.163.16.13.static.vsnl.net.in [59.163.16.13] 13    76 ms    69 ms    79 ms  59.163.55.209.static.vsnl.net.in [59.163.55.209] 14   276 ms   279 ms   289 ms  59.163.16.229.static.vsnl.net.in [59.163.16.229] 15   236 ms   239 ms   249 ms  203.101.100.106 16   237 ms   236 ms   259 ms  125.21.167.86 17   248 ms   292 ms   246 ms  203.101.100.182 18     *        *        *     Request timed out. 19     *        *     125.18.121.118  reports: Destination net unreachable.Trace complete.C:\>tracert -w 600 tpghyd.homeip.netTracing route to tpghyd.homeip.net [122.169.152.37]over a maximum of 30 hops:  1     1 ms     1 ms     1 ms  dataone-adsl-router [192.168.1.1]  2    34 ms    39 ms    39 ms  121.243.182.33.static-bangalore.vsnl.net.in [121.243.182.33]  3    35 ms    42 ms    36 ms  172.31.241.25  4    42 ms    39 ms    40 ms  172.31.78.66  5    36 ms    39 ms    39 ms  172.31.78.85  6    35 ms    39 ms    39 ms  172.31.9.197  7    46 ms    40 ms    39 ms  172.31.50.194  8    36 ms    39 ms    39 ms  172.31.14.97  9    37 ms    50 ms    39 ms  172.31.2.69 10    68 ms    69 ms    69 ms  59.163.16.58.static.vsnl.net.in [59.163.16.58] 11    67 ms    70 ms    69 ms  59.163.55.149.static.vsnl.net.in [59.163.55.149] 12    67 ms    69 ms    69 ms  59.163.55.149.static.vsnl.net.in [59.163.55.149] 13    67 ms    69 ms   109 ms  59.163.55.209.static.vsnl.net.in [59.163.55.209] 14   267 ms   269 ms   311 ms  59.163.16.229.static.vsnl.net.in [59.163.16.229] 15   218 ms   220 ms   359 ms  203.101.100.106 16   218 ms   229 ms   230 ms  125.21.167.78 17   219 ms   259 ms   220 ms  203.101.100.102 18   230 ms   219 ms   269 ms  125.16.7.126 19   227 ms   229 ms   229 ms  ABTS-AP-Static-253.240.169.122.airtelbroadband.in [122.169.240.253] 20   257 ms   249 ms   259 ms  ABTS-AP-dynamic-037.152.169.122.airtelbroadband.in [122.169.152.37]
 
Is your IP 121.243.182.33? Traffic between two ISPs within India should ideally be exchanged via NIXI. From the traceroute output, it appears that this might not be the case (contributing to the high latency). And Tata looks like the suspect.
 
Status
Not open for further replies.

Top