Packet Loss and Slow Speed Problems on Airtel Broadband

  • Thread starter Thread starter anshu
  • Start date Start date
  • Replies Replies 933
  • Views Views 193,160
mine too, speeds dropped to about 256kbps
 
I am getting 500+ ping on 90 % of the european servers since 1 week and I am getting really bad lag in games like counter strike. I heard that airtel is having dns issues since few days but their customer care doesn't care about anything except proper speed. So my question is are they going to solve this problem?
 
BSNL having similar issues, all this started with the free double bandwidth offer they have for this month. Hopefully next month will bring some sanity.
 
airtel is routing europe traffic via singapore ,tokyo, USA using tata comm (teleglobe) cables, so high pings are expected.

I expect that this actually depends entirely on where your traffic is going...
 


Code:
Tracing route to itek.seedbox.cc [213.251.166.132]over a maximum of 30 hops:  1     5 ms     1 ms     1 ms  adsl-router [192.168.1.1]  2     *       29 ms     *     ABTS-KK-Dynamic-001.64.167.122.airtelbroadband.in [122.167.64.1]  3     *       30 ms    28 ms  ABTS-KK-Static-017.32.166.122.airtelbroadband.in [122.166.32.17]  4    27 ms    30 ms    26 ms  ABTS-KK-Static-009.32.166.122.airtelbroadband.in [122.166.32.9]  5    38 ms    28 ms    32 ms  122.175.255.29  6   110 ms   110 ms   109 ms  AES-Static-118.36.144.59.airtel.in [59.144.36.118]  7   121 ms   119 ms   119 ms  if-11-0-0.core1.SVQ-Singapore.as6453.net [120.29.214.5]  8    80 ms    73 ms    85 ms  Vlan1107.icore1.SVQ-Singapore.as6453.net [120.29.214.2]  9   128 ms   125 ms   125 ms  Vlan1717.icore1.SVW-Singapore.as6453.net [116.0.71.13] 10   196 ms     *        *     Vlan34.icore1.TV2-Tokyo.as6453.net [116.0.88.5] 11     *        *        *     Request timed out. 12     *      249 ms   249 ms  if-12-0-0.mcore4.PDI-PaloAlto.as6453.net [216.6.86.25] 13     *        *      336 ms  if-9-0-0-1186.mcore5.NYY-NewYork.as6453.net [216.6.86.58] 14     *      414 ms   411 ms  if-0-0-0-1230.core1.PYE-Paris.as6453.net [64.86.71.46] 15     *      449 ms   447 ms  if-11-4.har1.PV0-Paris.as6453.net [195.219.224.77] 16     *      411 ms   434 ms  30g.teleglobe.vss-1-6k.routers.chtix.eu [213.251.130.49] 17     *      415 ms   411 ms  80g.p19-7-6k.routers.chtix.eu [213.186.32.133] 18     *      414 ms   413 ms  p19-18-m1.routers.ovh.net [213.186.32.56] 19   416 ms   420 ms   413 ms  rev-09-1-52-89.otw99-idtel.net [213.251.166.132] Tracing route to rs232dt.link-removed.com [62.153.244.33]over a maximum of 30 hops:  1     1 ms     1 ms     1 ms  adsl-router [192.168.1.1]  2     *       47 ms    31 ms  ABTS-KK-Dynamic-001.64.167.122.airtelbroadband.in [122.167.64.1]  3    28 ms    28 ms    30 ms  ABTS-KK-Static-169.32.166.122.airtelbroadband.in [122.166.32.169]  4    28 ms    29 ms    29 ms  ABTS-KK-Static-009.32.166.122.airtelbroadband.in [122.166.32.9]  5    29 ms    29 ms    28 ms  122.175.255.29  6   113 ms   116 ms   114 ms  AES-Static-118.36.144.59.airtel.in [59.144.36.118]  7    69 ms    68 ms    69 ms  pos11-0.cr02.sin02.pccwbtn.net [63.218.165.213]  8     *        *      367 ms  tenge13-3.br03.hkg04.pccwbtn.net [63.218.60.146]  9     *      108 ms   110 ms  194.25.209.77 10     *      382 ms   383 ms  217.239.39.46 11   441 ms   441 ms     *     aprot.ihotspot.de [62.153.244.33] 12   449 ms   449 ms   450 ms  aprot.ihotspot.de [62.153.244.33]Tracing route to newswww.bbc.net.uk [212.58.226.139]over a maximum of 30 hops:  1     9 ms     2 ms     1 ms  adsl-router [192.168.1.1]  2     *        *       62 ms  ABTS-KK-Dynamic-001.64.167.122.airtelbroadband.in [122.167.64.1]  3    28 ms    28 ms    28 ms  ABTS-KK-Static-177.32.166.122.airtelbroadband.in [122.166.32.177]  4     *       30 ms    31 ms  ABTS-KK-Static-009.32.166.122.airtelbroadband.in [122.166.32.9]  5    30 ms    30 ms    29 ms  122.175.255.29  6   116 ms   116 ms   119 ms  AES-Static-122.36.144.59.airtel.in [59.144.36.122]  7   119 ms   115 ms   115 ms  if-11-0-0.core1.SVQ-Singapore.as6453.net [120.29.214.5]  8    81 ms    71 ms    71 ms  Vlan1107.icore1.SVQ-Singapore.as6453.net [120.29.214.2]  9   124 ms   127 ms   123 ms  Vlan1717.icore1.SVW-Singapore.as6453.net [116.0.71.13] 10     *        *        *     Request timed out. 11     *      197 ms   197 ms  209.58.61.93 12   296 ms   448 ms   251 ms  if-12-0-0.mcore4.PDI-PaloAlto.as6453.net [216.6.86.25] 13   326 ms   321 ms   521 ms  if-0-0-0-892.mcore3.NJY-Newark.as6453.net [209.58.124.25] 14   519 ms   480 ms   541 ms  if-4-0-0.core1.FV0-Frankfurt.as6453.net [195.219.69.29] 15   458 ms   459 ms   459 ms  if-1-1.har1.FR1-Frankfurt.as6453.net [195.219.69.14] 16   416 ms   409 ms   409 ms  rt-decix.fft.bbc.co.uk [80.81.192.59] 17   408 ms   408 ms   406 ms  ge0-1-10.rt0.tcman.bbc.co.uk [212.58.239.245] 18     *      411 ms   411 ms  212.58.238.38 19   413 ms   413 ms   411 ms  te12-1.hsw1.cwwtf.bbc.co.uk [212.58.239.234] 20   397 ms   400 ms   397 ms  nol-vip02.cwwtf.bbc.co.uk [212.58.226.139]
@mgcarley, everything i see is going via sg route. all these hosts used to give around 200ms avg before the cable fault
 
To those locations, yes, it is taking the long way around. That being said, 400/420/450ms isn't awful to london/paris/munich respectively, considering it's 3x the distance on that route.The only one I'm having trouble with is where PCCW and Deutsche Telekom peer. DT must have presence in HKG, but then where does the cabling go? It seems to hop straight through the US without jumping on to any of their provider networks - how typically German and efficient ;)
 

Back