Thread: Heavy daytime packet loss since thursday 25th august

Getting really heavy packet loss to all servers outside india for the last 2 days.

pings look like this :

Code:

eply from 66.199.244.82: bytes=32 time=345ms TTL=56
eply from 66.199.244.82: bytes=32 time=352ms TTL=56
eply from 66.199.244.82: bytes=32 time=353ms TTL=56
eply from 66.199.244.82: bytes=32 time=346ms TTL=56
eply from 66.199.244.82: bytes=32 time=325ms TTL=56
equest timed out.
equest timed out.
equest timed out.
eply from 66.199.244.82: bytes=32 time=326ms TTL=56
eply from 66.199.244.82: bytes=32 time=325ms TTL=56
eply from 66.199.244.82: bytes=32 time=324ms TTL=56
eply from 66.199.244.82: bytes=32 time=327ms TTL=56
eply from 66.199.244.82: bytes=32 time=326ms TTL=56
eply from 66.199.244.82: bytes=32 time=325ms TTL=56
eply from 66.199.244.82: bytes=32 time=324ms TTL=56
eply from 66.199.244.82: bytes=32 time=324ms TTL=56
eply from 66.199.244.82: bytes=32 time=325ms TTL=56
eply from 66.199.244.82: bytes=32 time=325ms TTL=56
eply from 66.199.244.82: bytes=32 time=325ms TTL=56
eply from 66.199.244.82: bytes=32 time=333ms TTL=56
eply from 66.199.244.82: bytes=32 time=327ms TTL=56
eply from 66.199.244.82: bytes=32 time=324ms TTL=56
eply from 66.199.244.82: bytes=32 time=325ms TTL=56
eply from 66.199.244.82: bytes=32 time=322ms TTL=56
eply from 66.199.244.82: bytes=32 time=325ms TTL=56
eply from 66.199.244.82: bytes=32 time=322ms TTL=56
eply from 66.199.244.82: bytes=32 time=323ms TTL=56
eply from 66.199.244.82: bytes=32 time=322ms TTL=56
eply from 66.199.244.82: bytes=32 time=325ms TTL=56
eply from 66.199.244.82: bytes=32 time=326ms TTL=56
eply from 66.199.244.82: bytes=32 time=321ms TTL=56
eply from 66.199.244.82: bytes=32 time=326ms TTL=56
eply from 66.199.244.82: bytes=32 time=323ms TTL=56
eply from 66.199.244.82: bytes=32 time=321ms TTL=56
eply from 66.199.244.82: bytes=32 time=325ms TTL=56
eply from 66.199.244.82: bytes=32 time=324ms TTL=56
eply from 66.199.244.82: bytes=32 time=322ms TTL=56
eply from 66.199.244.82: bytes=32 time=324ms TTL=56
eply from 66.199.244.82: bytes=32 time=324ms TTL=56
eply from 66.199.244.82: bytes=32 time=324ms TTL=56
eply from 66.199.244.82: bytes=32 time=323ms TTL=56
eply from 66.199.244.82: bytes=32 time=322ms TTL=56
eply from 66.199.244.82: bytes=32 time=323ms TTL=56
eply from 66.199.244.82: bytes=32 time=320ms TTL=56
eply from 66.199.244.82: bytes=32 time=323ms TTL=56
equest timed out.
equest timed out.
equest timed out.
eply from 66.199.244.82: bytes=32 time=322ms TTL=56
eply from 66.199.244.82: bytes=32 time=325ms TTL=56
eply from 66.199.244.82: bytes=32 time=326ms TTL=56
eply from 66.199.244.82: bytes=32 time=325ms TTL=56
eply from 66.199.244.82: bytes=32 time=324ms TTL=56
eply from 66.199.244.82: bytes=32 time=323ms TTL=56
eply from 66.199.244.82: bytes=32 time=324ms TTL=56
eply from 66.199.244.82: bytes=32 time=323ms TTL=56
eply from 66.199.244.82: bytes=32 time=326ms TTL=56
eply from 66.199.244.82: bytes=32 time=321ms TTL=56
eply from 66.199.244.82: bytes=32 time=326ms TTL=56
eply from 66.199.244.82: bytes=32 time=325ms TTL=56

Happens throughout the day, starting from around 8am up until 6-7pm.
Intermittent packet losses, then a string of 4-5 or more drops. Pages open erratically/slowly and streams just stop.

Any word on repairs or some such ?

Not experiencing any kind of similar packet loss on airtel right now.
Calling the bsnl call center seems pointless.

Have you tried writing to the Nodal officer and Appellate authority ?

No I haven't dilip. Is there any way to email them or talk to them on the phone ?

I'm almost positive that it's not my lines, it's possibly repairs on bsnl's end or maybe congestion in my area (other people torrenting maybe ?).

Do you have the info to contact nodal officer/appellate ?

Sure rsen, give this a try. Not sure how effective it will be.

Just check the backside of your bill. You can find their ID, phone no. and address. If you give them a written complaint, you will get a written reply (positive or negative) which you can use if you wish to take any further action. I have spoke to the Nodal officer once, he was very nice to me and ordered the SDE to deal my issue.

the numbers at the back of the BSNL bill for public relation/nodal officer are never answered. Tried calling these numbers many times.
There is no email address or address to write to for complaints.

I've complained about packet loss on the online complaint booking website but I didn't get any kind of response.

In the meantime packet loss is still awful every day and begins at around 8am and lasts until late in the evening.

It's probably worse than yesterday, not sure what's going on.

Code:

Reply from 66.199.244.82: bytes=32 time=324ms TTL=45
Reply from 66.199.244.82: bytes=32 time=326ms TTL=45
Reply from 66.199.244.82: bytes=32 time=322ms TTL=45
Reply from 66.199.244.82: bytes=32 time=323ms TTL=45
Reply from 66.199.244.82: bytes=32 time=322ms TTL=45
Reply from 66.199.244.82: bytes=32 time=323ms TTL=45
Reply from 66.199.244.82: bytes=32 time=324ms TTL=45
Reply from 66.199.244.82: bytes=32 time=323ms TTL=45
Reply from 66.199.244.82: bytes=32 time=351ms TTL=49
Reply from 66.199.244.82: bytes=32 time=351ms TTL=49
Reply from 66.199.244.82: bytes=32 time=352ms TTL=49
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 66.199.244.82: bytes=32 time=360ms TTL=44
Reply from 66.199.244.82: bytes=32 time=323ms TTL=44
Reply from 66.199.244.82: bytes=32 time=326ms TTL=44
Reply from 66.199.244.82: bytes=32 time=323ms TTL=44
Reply from 66.199.244.82: bytes=32 time=323ms TTL=44
Reply from 66.199.244.82: bytes=32 time=322ms TTL=44
Reply from 66.199.244.82: bytes=32 time=322ms TTL=44
Reply from 66.199.244.82: bytes=32 time=324ms TTL=44
Reply from 66.199.244.82: bytes=32 time=323ms TTL=44
Reply from 66.199.244.82: bytes=32 time=324ms TTL=44
Reply from 66.199.244.82: bytes=32 time=321ms TTL=45
Reply from 66.199.244.82: bytes=32 time=328ms TTL=44
Reply from 66.199.244.82: bytes=32 time=329ms TTL=44
Reply from 66.199.244.82: bytes=32 time=328ms TTL=44
Reply from 66.199.244.82: bytes=32 time=328ms TTL=44
Reply from 66.199.244.82: bytes=32 time=328ms TTL=44
Reply from 66.199.244.82: bytes=32 time=327ms TTL=44
Reply from 66.199.244.82: bytes=32 time=329ms TTL=44
Reply from 66.199.244.82: bytes=32 time=327ms TTL=44
Reply from 66.199.244.82: bytes=32 time=326ms TTL=44
Reply from 66.199.244.82: bytes=32 time=327ms TTL=44
Reply from 66.199.244.82: bytes=32 time=326ms TTL=44
Reply from 66.199.244.82: bytes=32 time=327ms TTL=44
Reply from 66.199.244.82: bytes=32 time=316ms TTL=47
Reply from 66.199.244.82: bytes=32 time=317ms TTL=47
Reply from 66.199.244.82: bytes=32 time=318ms TTL=47
Reply from 66.199.244.82: bytes=32 time=317ms TTL=47
Reply from 66.199.244.82: bytes=32 time=318ms TTL=47
Reply from 66.199.244.82: bytes=32 time=317ms TTL=47
Reply from 66.199.244.82: bytes=32 time=318ms TTL=47
Reply from 66.199.244.82: bytes=32 time=317ms TTL=47
Reply from 66.199.244.82: bytes=32 time=318ms TTL=47
Reply from 66.199.244.82: bytes=32 time=318ms TTL=47
Reply from 66.199.244.82: bytes=32 time=315ms TTL=47
Reply from 66.199.244.82: bytes=32 time=318ms TTL=47
Reply from 66.199.244.82: bytes=32 time=318ms TTL=47
Reply from 66.199.244.82: bytes=32 time=318ms TTL=47
Request timed out.
Request timed out.
Request timed out.
Reply from 66.199.244.82: bytes=32 time=270ms TTL=51
Reply from 66.199.244.82: bytes=32 time=271ms TTL=51
Reply from 66.199.244.82: bytes=32 time=270ms TTL=51
Reply from 66.199.244.82: bytes=32 time=271ms TTL=51
Reply from 66.199.244.82: bytes=32 time=272ms TTL=51
Reply from 66.199.244.82: bytes=32 time=271ms TTL=51
Reply from 66.199.244.82: bytes=32 time=272ms TTL=51
Reply from 66.199.244.82: bytes=32 time=271ms TTL=51
Reply from 66.199.244.82: bytes=32 time=272ms TTL=51
Request timed out.
Request timed out.
Request timed out.
Reply from 66.199.244.82: bytes=32 time=272ms TTL=51
Reply from 66.199.244.82: bytes=32 time=273ms TTL=51
Reply from 66.199.244.82: bytes=32 time=275ms TTL=51
Request timed out.
Reply from 66.199.244.82: bytes=32 time=321ms TTL=44
Reply from 66.199.244.82: bytes=32 time=326ms TTL=44
Reply from 66.199.244.82: bytes=32 time=325ms TTL=44

Please have a look at the above ping.
To any website outside india the ping trace is similar-
normal ping time is 273-280.
As you can see it starts a bit high with 320-330. Then there is a huge string of dropped packets then latency spikes up to 360, slowly drops down to ~320 then again there is a series of dropped packets; then normal latency for a few seconds then dropped packets again etc etc.

Huge jitter (fluctuating latency), packet loss and what seems like a complete outage frequently.

Meanwhile traces/pings to any server inside india are perfectly normal (45ms/under 60).

What could be going on ?

Does BSNL just randomly switch to a garbage 3rd party routing company and never check it for days together ?

And again at the moment airtel pings are completely fine and there is no packet loss. Yet on bsnl packet loss is so ridiculous I can't even post a proper trace route yet since the complete outage to anything outside india keeps happening every 10-15 seconds.

finally got a "good" trace to the same server as above:

Code:

Tracing route to 66-199-244-82.reverse.ezzi.net [66.199.244.82]
over a maximum of 30 hops:

  1    11 ms    11 ms    11 ms  59.93.240.1
  2    42 ms    40 ms    41 ms  218.248.255.6
  3    53 ms    40 ms    41 ms  59.163.206.157.static.chennai.vsnl.net.in [59.16
3.206.157]
  4    68 ms    75 ms    85 ms  172.31.16.173
  5    67 ms    67 ms    67 ms  if-0-100.tcore2.MLV-Mumbai.as6453.net [180.87.39
.25]
  6   180 ms   177 ms   177 ms  if-2-2.tcore1.MLV-Mumbai.as6453.net [180.87.38.1
]
  7   174 ms   175 ms   175 ms  if-3-2.tcore1.PYE-Paris.as6453.net [80.231.154.7
0]
  8   174 ms   175 ms   181 ms  if-2-2.tcore1.PVU-Paris.as6453.net [80.231.154.1
7]
  9   268 ms   268 ms   267 ms  80.231.153.66
 10   268 ms   267 ms   267 ms  ae-34-52.ebr2.Paris1.Level3.net [4.69.139.225]
 11   284 ms   281 ms   283 ms  ae-43-43.ebr2.Washington1.Level3.net [4.69.137.5
8]
 12   284 ms   281 ms   283 ms  ae-5-5.ebr2.Washington12.Level3.net [4.69.143.22
2]
 13   287 ms   287 ms   287 ms  4.69.148.49
 14   283 ms   287 ms   289 ms  ae-71-71.csw2.NewYork1.Level3.net [4.69.134.70]

 15   274 ms   275 ms   275 ms  ae-2-70.edge2.NewYork1.Level3.net [4.69.155.80]

 16   278 ms   275 ms   277 ms  ACCESSIT.car1.NewYork1.Level3.net [4.53.82.186]

 17   275 ms   275 ms   275 ms  ads-bsh-fwb4.ezzi.net [72.9.110.203]
 18   277 ms   275 ms   277 ms  66-199-244-82.reverse.ezzi.net [66.199.244.82]

Trace complete.

Here is a similar website in the USA, using Airtel (again, almost all foreign websites on airtel gives pings/traces similar to this server)
ping:

Code:

Reply from 67.207.192.146: bytes=32 time=296ms TTL=57
Reply from 67.207.192.146: bytes=32 time=291ms TTL=57
Reply from 67.207.192.146: bytes=32 time=297ms TTL=57
Reply from 67.207.192.146: bytes=32 time=297ms TTL=57
Reply from 67.207.192.146: bytes=32 time=297ms TTL=57
Reply from 67.207.192.146: bytes=32 time=297ms TTL=57
Reply from 67.207.192.146: bytes=32 time=291ms TTL=57
Reply from 67.207.192.146: bytes=32 time=295ms TTL=57
Reply from 67.207.192.146: bytes=32 time=292ms TTL=57
Reply from 67.207.192.146: bytes=32 time=292ms TTL=57
Reply from 67.207.192.146: bytes=32 time=291ms TTL=57
Reply from 67.207.192.146: bytes=32 time=291ms TTL=57
Reply from 67.207.192.146: bytes=32 time=319ms TTL=57
Reply from 67.207.192.146: bytes=32 time=300ms TTL=57
Reply from 67.207.192.146: bytes=32 time=298ms TTL=57
Reply from 67.207.192.146: bytes=32 time=291ms TTL=57
Reply from 67.207.192.146: bytes=32 time=291ms TTL=57
Reply from 67.207.192.146: bytes=32 time=309ms TTL=57
Reply from 67.207.192.146: bytes=32 time=298ms TTL=57
Reply from 67.207.192.146: bytes=32 time=292ms TTL=57
Reply from 67.207.192.146: bytes=32 time=291ms TTL=57
Reply from 67.207.192.146: bytes=32 time=291ms TTL=57
Reply from 67.207.192.146: bytes=32 time=297ms TTL=57
Reply from 67.207.192.146: bytes=32 time=297ms TTL=57
Reply from 67.207.192.146: bytes=32 time=291ms TTL=57
Reply from 67.207.192.146: bytes=32 time=292ms TTL=57
Reply from 67.207.192.146: bytes=32 time=298ms TTL=57
Reply from 67.207.192.146: bytes=32 time=297ms TTL=57
Reply from 67.207.192.146: bytes=32 time=293ms TTL=57
Reply from 67.207.192.146: bytes=32 time=299ms TTL=57
Reply from 67.207.192.146: bytes=32 time=291ms TTL=57
Reply from 67.207.192.146: bytes=32 time=290ms TTL=57
Reply from 67.207.192.146: bytes=32 time=298ms TTL=57
Reply from 67.207.192.146: bytes=32 time=297ms TTL=57
Reply from 67.207.192.146: bytes=32 time=291ms TTL=57
Reply from 67.207.192.146: bytes=32 time=291ms TTL=57
Reply from 67.207.192.146: bytes=32 time=291ms TTL=57
Reply from 67.207.192.146: bytes=32 time=294ms TTL=57
Reply from 67.207.192.146: bytes=32 time=294ms TTL=57
Reply from 67.207.192.146: bytes=32 time=291ms TTL=57
Reply from 67.207.192.146: bytes=32 time=297ms TTL=57
Reply from 67.207.192.146: bytes=32 time=297ms TTL=57
Reply from 67.207.192.146: bytes=32 time=291ms TTL=57
Reply from 67.207.192.146: bytes=32 time=291ms TTL=57
Reply from 67.207.192.146: bytes=32 time=292ms TTL=57
Reply from 67.207.192.146: bytes=32 time=292ms TTL=57
Reply from 67.207.192.146: bytes=32 time=297ms TTL=57
Reply from 67.207.192.146: bytes=32 time=297ms TTL=57
Reply from 67.207.192.146: bytes=32 time=298ms TTL=57
Reply from 67.207.192.146: bytes=32 time=297ms TTL=57
Reply from 67.207.192.146: bytes=32 time=297ms TTL=57
Reply from 67.207.192.146: bytes=32 time=297ms TTL=57
Reply from 67.207.192.146: bytes=32 time=291ms TTL=57
Reply from 67.207.192.146: bytes=32 time=291ms TTL=57
Reply from 67.207.192.146: bytes=32 time=296ms TTL=57
Reply from 67.207.192.146: bytes=32 time=292ms TTL=57
Reply from 67.207.192.146: bytes=32 time=296ms TTL=57
Reply from 67.207.192.146: bytes=32 time=294ms TTL=57

trace:

Code:

Tracing route to ss0434.svwh.net [67.207.192.146]
over a maximum of 30 hops:

  1    27 ms    27 ms    29 ms  ABTS-North-Static-136.237.160.122.airtelbroadban
d.in [122.160.237.136]
  2    28 ms    27 ms    27 ms  ABTS-North-Static-233.237.160.122.airtelbroadban
d.in [122.160.237.233]
  3    28 ms    27 ms    33 ms  AES-Static-021.78.22.125.airtel.in [125.22.78.21
]
  4   304 ms   327 ms   299 ms  125.62.187.113
  5   309 ms   309 ms   309 ms  te7-8.ccr01.lax04.atlas.cogentco.com [38.104.83.
81]
  6   293 ms   285 ms   283 ms  te0-3-0-7.mpd22.lax01.atlas.cogentco.com [154.54
.44.1]
  7   312 ms   313 ms   313 ms  te3-1.mpd01.sjc01.atlas.cogentco.com [154.54.5.1
81]
  8   316 ms   315 ms   317 ms  te7-1.mpd01.sjc05.atlas.cogentco.com [154.54.6.7
4]
  9   305 ms   305 ms   305 ms  SiliconValley_WebHosting.demarc.cogentco.com [38
.112.9.214]
 10   296 ms   303 ms   305 ms  vlan933.po33.g1-0-11-g1-0-12.dist01.sjc01.svwh.n
et [208.166.59.150]
 11   296 ms   291 ms   297 ms  ss0434.svwh.net [67.207.192.146]

Trace complete.

I read your posts. It is up to BSNL to attend this issue. Let us hope they will do something.

Don't rely on phone no. or email ID. Write a complaint with acknowledgement to the Nodal officer and Appellate authority. As I mentioned, you will get a written reply.

For West Bengal circle, SSA - Kolkata, try this

A.K.Mandal, DE(Com-1)

O/o GM Kolkata SSA, 135A, B.R.B. Bose Road, Kol-1.

email : pg_kolwb@bsnl.co.in

Phone no. : 3322428227

Try this link : CONSUMER GRIEVANCE REDRESSAL MECHANISM IN BSNL

@ rsen

Replied, but post gone to moderation.

I got a call from BSNL early in the morning today and they told me that 4 out of 6 gateways are "down" so that's why there was packet loss.
Right when they called there was no packet loss.


But amusingly right now at 4pm it has started again ...

Code:

Reply from 66.199.244.82: bytes=32 time=265ms TTL=51
Reply from 66.199.244.82: bytes=32 time=266ms TTL=51
Reply from 66.199.244.82: bytes=32 time=265ms TTL=51
Reply from 66.199.244.82: bytes=32 time=267ms TTL=51
Reply from 66.199.244.82: bytes=32 time=267ms TTL=51
Request timed out.
Reply from 66.199.244.82: bytes=32 time=330ms TTL=44
Reply from 66.199.244.82: bytes=32 time=342ms TTL=44
Reply from 66.199.244.82: bytes=32 time=365ms TTL=44
Reply from 66.199.244.82: bytes=32 time=374ms TTL=44
Reply from 66.199.244.82: bytes=32 time=383ms TTL=43
Reply from 66.199.244.82: bytes=32 time=398ms TTL=43
Reply from 66.199.244.82: bytes=32 time=397ms TTL=43
Reply from 66.199.244.82: bytes=32 time=404ms TTL=43
Reply from 66.199.244.82: bytes=32 time=407ms TTL=43
Reply from 66.199.244.82: bytes=32 time=405ms TTL=43
Reply from 66.199.244.82: bytes=32 time=411ms TTL=43
Reply from 66.199.244.82: bytes=32 time=413ms TTL=43
Reply from 66.199.244.82: bytes=32 time=414ms TTL=43
Reply from 66.199.244.82: bytes=32 time=412ms TTL=43
Reply from 66.199.244.82: bytes=32 time=408ms TTL=43
Reply from 66.199.244.82: bytes=32 time=408ms TTL=43
Reply from 66.199.244.82: bytes=32 time=411ms TTL=43
Reply from 66.199.244.82: bytes=32 time=410ms TTL=43
Reply from 66.199.244.82: bytes=32 time=407ms TTL=43
Reply from 66.199.244.82: bytes=32 time=405ms TTL=43
Reply from 66.199.244.82: bytes=32 time=411ms TTL=43
Reply from 66.199.244.82: bytes=32 time=403ms TTL=43
Reply from 66.199.244.82: bytes=32 time=404ms TTL=43
Reply from 66.199.244.82: bytes=32 time=402ms TTL=43
Reply from 66.199.244.82: bytes=32 time=409ms TTL=43
Reply from 66.199.244.82: bytes=32 time=414ms TTL=44
Reply from 66.199.244.82: bytes=32 time=411ms TTL=44
Reply from 66.199.244.82: bytes=32 time=398ms TTL=47
Reply from 66.199.244.82: bytes=32 time=399ms TTL=47
Reply from 66.199.244.82: bytes=32 time=404ms TTL=48
Reply from 66.199.244.82: bytes=32 time=399ms TTL=48
Reply from 66.199.244.82: bytes=32 time=409ms TTL=47
Reply from 66.199.244.82: bytes=32 time=398ms TTL=51
Reply from 66.199.244.82: bytes=32 time=396ms TTL=51
Reply from 66.199.244.82: bytes=32 time=394ms TTL=51
Reply from 66.199.244.82: bytes=32 time=395ms TTL=51
Reply from 66.199.244.82: bytes=32 time=396ms TTL=51
Reply from 66.199.244.82: bytes=32 time=395ms TTL=51
Reply from 66.199.244.82: bytes=32 time=398ms TTL=51
Reply from 66.199.244.82: bytes=32 time=405ms TTL=51
Reply from 66.199.244.82: bytes=32 time=404ms TTL=51
Reply from 66.199.244.82: bytes=32 time=406ms TTL=51
Reply from 66.199.244.82: bytes=32 time=398ms TTL=51
Reply from 66.199.244.82: bytes=32 time=399ms TTL=51
Reply from 66.199.244.82: bytes=32 time=402ms TTL=51
Reply from 66.199.244.82: bytes=32 time=403ms TTL=51
Reply from 66.199.244.82: bytes=32 time=414ms TTL=45
Reply from 66.199.244.82: bytes=32 time=409ms TTL=45
Reply from 66.199.244.82: bytes=32 time=406ms TTL=45
Reply from 66.199.244.82: bytes=32 time=409ms TTL=45
Reply from 66.199.244.82: bytes=32 time=407ms TTL=45
Reply from 66.199.244.82: bytes=32 time=409ms TTL=45
Reply from 66.199.244.82: bytes=32 time=345ms TTL=49
Reply from 66.199.244.82: bytes=32 time=344ms TTL=49
Request timed out.
Reply from 66.199.244.82: bytes=32 time=284ms TTL=49
Reply from 66.199.244.82: bytes=32 time=279ms TTL=48
Reply from 66.199.244.82: bytes=32 time=281ms TTL=48
Reply from 66.199.244.82: bytes=32 time=279ms TTL=48
Reply from 66.199.244.82: bytes=32 time=280ms TTL=48
Reply from 66.199.244.82: bytes=32 time=263ms TTL=51
Reply from 66.199.244.82: bytes=32 time=261ms TTL=51

more from 4:30pm:

Code:

Request timed out.
Reply from 66.199.244.82: bytes=32 time=390ms TTL=51
Reply from 66.199.244.82: bytes=32 time=389ms TTL=51
Reply from 66.199.244.82: bytes=32 time=390ms TTL=51
Reply from 66.199.244.82: bytes=32 time=389ms TTL=51
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 66.199.244.82: bytes=32 time=793ms TTL=10
Request timed out.
Reply from 66.199.244.82: bytes=32 time=408ms TTL=52
Reply from 66.199.244.82: bytes=32 time=407ms TTL=52
Reply from 66.199.244.82: bytes=32 time=410ms TTL=52
Reply from 66.199.244.82: bytes=32 time=402ms TTL=52
Reply from 66.199.244.82: bytes=32 time=403ms TTL=52
Request timed out.
Reply from 66.199.244.82: bytes=32 time=402ms TTL=52
Reply from 66.199.244.82: bytes=32 time=401ms TTL=52
Reply from 66.199.244.82: bytes=32 time=400ms TTL=52
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 66.199.244.82: bytes=32 time=408ms TTL=46
Request timed out.
Reply from 66.199.244.82: bytes=32 time=411ms TTL=46
Reply from 66.199.244.82: bytes=32 time=409ms TTL=46
Reply from 66.199.244.82: bytes=32 time=409ms TTL=46

ping to google :

Code:

Pinging www.l.google.com [74.125.236.50] with 32 byt
Request timed out.
Reply from 74.125.236.50: bytes=32 time=161ms TTL=57
Reply from 74.125.236.50: bytes=32 time=175ms TTL=57
Reply from 74.125.236.50: bytes=32 time=175ms TTL=57
Reply from 74.125.236.50: bytes=32 time=164ms TTL=57
Reply from 74.125.236.50: bytes=32 time=175ms TTL=57
Reply from 74.125.236.50: bytes=32 time=166ms TTL=57
Reply from 74.125.236.50: bytes=32 time=174ms TTL=57
Reply from 74.125.236.50: bytes=32 time=167ms TTL=57
Reply from 74.125.236.50: bytes=32 time=162ms TTL=57
Request timed out.
Reply from 74.125.236.50: bytes=32 time=167ms TTL=57
Reply from 74.125.236.50: bytes=32 time=175ms TTL=57
Reply from 74.125.236.50: bytes=32 time=166ms TTL=57
Reply from 74.125.236.50: bytes=32 time=179ms TTL=57
Reply from 74.125.236.50: bytes=32 time=162ms TTL=57
Reply from 74.125.236.50: bytes=32 time=177ms TTL=57
Reply from 74.125.236.50: bytes=32 time=176ms TTL=57
Reply from 74.125.236.50: bytes=32 time=151ms TTL=57
Reply from 74.125.236.50: bytes=32 time=181ms TTL=57
Reply from 74.125.236.50: bytes=32 time=162ms TTL=57
Reply from 74.125.236.50: bytes=32 time=173ms TTL=57
Reply from 74.125.236.50: bytes=32 time=164ms TTL=57
Reply from 74.125.236.50: bytes=32 time=324ms TTL=45
Reply from 74.125.236.50: bytes=32 time=365ms TTL=45
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 74.125.236.50: bytes=32 time=139ms TTL=56
Reply from 74.125.236.50: bytes=32 time=180ms TTL=56
Reply from 74.125.236.50: bytes=32 time=147ms TTL=56
Request timed out.
Reply from 74.125.236.50: bytes=32 time=137ms TTL=56
Reply from 74.125.236.50: bytes=32 time=94ms TTL=56
Reply from 74.125.236.50: bytes=32 time=129ms TTL=56
Reply from 74.125.236.50: bytes=32 time=140ms TTL=56
Reply from 74.125.236.50: bytes=32 time=137ms TTL=56

thnx for the link dilip i'll try that.

Additional link here :: Grievance Redress Mechanism in Government ::

sent an email to the nodal officer for kolkata, he forwarded my mail to "DGM(NWO)SOUTH".

So far packet loss problems are still the same, and there's the same latency fluctuations (40-50ms jitter regularly, periods during the day with 100-150ms higher latencies for extended periods like a few hours).

I'm really confused, is this just a normal problem with BSNL ?

No one else seems to report packet loss or latency problems on any of the popular forums.

I rarely experience anything like this on airtel although tariffs are higher and the average "good" latency is at least 30ms over bsnl. Also bandwidth is lower and plans are crap with FUP.

Did you go through the links provided above?

Believe me its the most effective in all, if you register a complaint in the links provided, it will directly go to the GM(TD) of your circle and your problem is bound to be solved within 7 days(at most 15 days).

Well, higher latency is normal but the problem for you is the higher jitters, it should be less than 10 ms(for BSNL) and one more thing there should not be any packet loss.

I got the nodal officer's email id from the "CONSUMER GRIEVANCE REDRESSAL MECHANISM IN BSNL" link that meetdilip posted.

I sent him a mail and he just forwarded it to DGM(NWO)SOUTH, I'm not sure who that is.

I'm just curious - do you guys not get any packet loss at all usually ?
(especially to servers outside India).

10ms jitter sounds very good though.

Ok, wait for 2 days and see if they contact you or not.If not then go and register a complaint in the link posted by me.

Since 1 week, I am also getting packet loss and high pings and bsnl people have no idea about it.

Code:

                               WinMTR statistics                                   |

|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |

|------------------------------------------------|------|------|------|------|------|------|

|                             192.168.1.1 -    0 |  148 |  148 |    0 |    0 |    6 |    3 |

|                            117.198.32.1 -    3 |  135 |  132 |   26 |   29 |   56 |   34 |

|                         218.248.168.166 -   10 |  105 |   95 |   28 |   74 |  315 |   69 |

|59.163.207.81.static.chennai.vsnl.net.in -    2 |  139 |  137 |   64 |   67 |   91 |   70 |

|                           172.31.16.173 -    3 |  135 |  132 |   89 |   94 |  188 |   90 |

|   if-0-100.tcore2.MLV-Mumbai.as6453.net -    4 |  127 |  122 |   89 |   93 |  234 |   91 |

|     if-2-2.tcore1.MLV-Mumbai.as6453.net -    6 |  117 |  110 |  199 |  205 |  267 |  239 |

|      if-3-2.tcore1.PYE-Paris.as6453.net -    5 |  122 |  116 |  200 |  203 |  239 |  201 |

|      if-2-2.tcore1.PVU-Paris.as6453.net -    6 |  121 |  114 |  199 |  201 |  208 |  202 |

|      Vlan13.icore1.PVU-Paris.as6453.net -    4 |  127 |  122 |  200 |  207 |  224 |  204 |

|   xe-6-3.r03.parsfr01.fr.bb.gin.ntt.net -    4 |  131 |  127 |  198 |  222 |  444 |  200 |

| xe-6-0-0.r21.parsfr01.fr.bb.gin.ntt.net -    5 |  122 |  116 |  200 |  203 |  219 |  202 |

|     as-4.r22.amstnl02.nl.bb.gin.ntt.net -    5 |  122 |  116 |  219 |  224 |  266 |  223 |

|     as-0.r25.tokyjp01.jp.bb.gin.ntt.net -    2 |  140 |  138 |  455 |  495 |  644 |  460 |

|     ae-0.r21.tokyjp01.jp.bb.gin.ntt.net -    2 |  140 |  138 |  454 |  473 |  644 |  464 |

|     ae-0.ocn.tokyjp01.jp.bb.gin.ntt.net -    6 |  118 |  111 |  452 |  466 |  603 |  465 |

|                            118.23.168.3 -    3 |  135 |  132 |  452 |  471 |  494 |  455 |

|                            122.1.245.13 -    6 |  119 |  112 |  460 |  474 |  629 |  470 |

|                         210.254.188.214 -    6 |  118 |  111 |  477 |  486 |  515 |  488 |

|                            221.184.5.86 -    6 |  118 |  111 |  468 |  476 |  509 |  469 |

|                            118.23.96.90 -    3 |  135 |  132 |  479 |  489 |  512 |  489 |

|                             118.23.7.78 -    4 |  126 |  121 |  478 |  488 |  535 |  484 |

|p6009-ipngn801sapodori.hokkaido.ocn.ne.jp -    4 |  127 |  122 |  469 |

The server is located in Japan then why its going via paris?

Yea that's exactly like what I've been facing. This kind of crap seems to happen every few weeks and only with BSNL, and no one on their end seems to know anything.

So far after complaining to the nodal officer I got 3-4 phonecalls from my exchange with the same question "is ur phone ok?".

Every time I say my phone is fine but that i'm getting a lot of packet loss. They don't seem to understand what packet loss is or jitter/bad latency. I don't get it :/

The server is located in Japan then why its going via paris?

Probably a cheaper route. BSNL changes routing very frequently probably to choose the cheapest routes at any given time.

The line may not be good so, better ask them to change the line from the DP.

I dont think, it's a line problem. This problem started a week ago and my voice line is working perfectly. This is 100% bsnl problem.

Probably a cheaper route. BSNL changes routing very frequently probably to choose the cheapest routes at any given time.

as6453 is TATA right?

More packet loss

Code:

-----------------------------------------------------------------------------------------|

|                                      WinMTR statistics                                   |

|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |

|------------------------------------------------|------|------|------|------|------|------|

|                             192.168.1.1 -    0 |  416 |  416 |    0 |    0 |   70 |    0 |

|                            117.198.32.1 -   13 |  269 |  236 |   26 |   30 |  121 |   30 |

|                         218.248.168.166 -   16 |  246 |  207 |   26 |   41 |  224 |   33 |

|59.163.207.81.static.chennai.vsnl.net.in -   16 |  250 |  212 |   63 |   68 |  217 |   68 |

|    ix-4-2.tcore1.CXR-Chennai.as6453.net -   16 |  246 |  208 |    0 |   70 |  225 |   68 |

|    if-3-3.tcore2.CXR-Chennai.as6453.net -   14 |  260 |  225 |    0 |  102 |  227 |   98 |

|  if-5-2.tcore2.SVW-Singapore.as6453.net -   17 |  240 |  200 |   95 |  103 |  206 |   96 |

|                              116.0.71.2 -   18 |  233 |  192 |   96 |  111 |  600 |   98 |

|             an-ats-int10.starhub.net.sg -   18 |  233 |  192 |   96 |  123 |  949 |  102 |

|                           203.117.6.210 -   12 |  273 |  241 |  101 |  309 |  712 |  319 |

|            203-174-80-210.rev.ne.com.sg -   17 |  236 |  196 |  101 |  315 | 2264 |  303 |

|                mail.newmediaexpress.com -   17 |  241 |  202 |  101 |  312 |  423 |  321 |

I live in near Ranchi. BTW

Yeah definitely not a line problem; also I've had my line checked multiple times and my phone line is perfectly fine.

It's a regular routing problem to any server outside India; happens every few days. Everyone who uses BSNL in India should experience this packet loss unless bsnl uses different routing for different regions.

yes as6453 is TATA

Problem fixed

Code:

                                 WinMTR statistics                                   |

|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |

|------------------------------------------------|------|------|------|------|------|------|

|                             192.168.1.1 -    0 |  279 |  279 |    0 |    1 |   74 |    0 |

|                            117.198.32.1 -    0 |  278 |  278 |   26 |   31 |  181 |   26 |

|                         218.248.168.166 -    0 |  279 |  279 |   27 |  134 |  705 |   28 |

|59.163.207.81.static.chennai.vsnl.net.in -    0 |  278 |  278 |   68 |   79 |  231 |   70 |

|    ix-4-2.tcore1.CXR-Chennai.as6453.net -    0 |  278 |  278 |   68 |   79 |  236 |   69 |

|  if-5-2.tcore1.SVW-Singapore.as6453.net -    0 |  279 |  279 |  100 |  110 |  273 |  112 |

|  if-2-2.tcore2.SVW-Singapore.as6453.net -    0 |  279 |  279 |   99 |  107 |  273 |  137 |

|                              116.0.71.2 -    0 |  279 |  279 |  101 |  110 |  260 |  103 |

|             an-ats-int10.starhub.net.sg -    0 |  278 |  278 |  101 |  115 |  296 |  101 |

|                           203.117.6.210 -    0 |  279 |  279 |  101 |  113 |  306 |  113 |

|            203-174-80-210.rev.ne.com.sg -    0 |  279 |  279 |  102 |  113 |  336 |  106 |

|                mail.newmediaexpress.com -    0 |  278 |  278 |  102 |  113 |  263 |  106 |

Can any one ping or traceroute 61.197.203.81

Yesterday It was 170 ms.

Thanks

@buttonmasher

ping to ur server:

Code:

Reply from 61.197.203.81: bytes=32 time=348ms TTL=109
Reply from 61.197.203.81: bytes=32 time=343ms TTL=109
Reply from 61.197.203.81: bytes=32 time=349ms TTL=109
Reply from 61.197.203.81: bytes=32 time=360ms TTL=109
Reply from 61.197.203.81: bytes=32 time=345ms TTL=109
Reply from 61.197.203.81: bytes=32 time=353ms TTL=109
Reply from 61.197.203.81: bytes=32 time=358ms TTL=109
Reply from 61.197.203.81: bytes=32 time=345ms TTL=109
Reply from 61.197.203.81: bytes=32 time=350ms TTL=109
Reply from 61.197.203.81: bytes=32 time=359ms TTL=109
Reply from 61.197.203.81: bytes=32 time=358ms TTL=109
Reply from 61.197.203.81: bytes=32 time=495ms TTL=109
Reply from 61.197.203.81: bytes=32 time=376ms TTL=109
Reply from 61.197.203.81: bytes=32 time=339ms TTL=109
Reply from 61.197.203.81: bytes=32 time=346ms TTL=109
Reply from 61.197.203.81: bytes=32 time=349ms TTL=109
Reply from 61.197.203.81: bytes=32 time=348ms TTL=109
Reply from 61.197.203.81: bytes=32 time=352ms TTL=109
Reply from 61.197.203.81: bytes=32 time=347ms TTL=109
Reply from 61.197.203.81: bytes=32 time=355ms TTL=109
Reply from 61.197.203.81: bytes=32 time=346ms TTL=109
Reply from 61.197.203.81: bytes=32 time=350ms TTL=109
Reply from 61.197.203.81: bytes=32 time=346ms TTL=109
Reply from 61.197.203.81: bytes=32 time=345ms TTL=109
Reply from 61.197.203.81: bytes=32 time=342ms TTL=109
Reply from 61.197.203.81: bytes=32 time=351ms TTL=109
Reply from 61.197.203.81: bytes=32 time=348ms TTL=109
Reply from 61.197.203.81: bytes=32 time=361ms TTL=109
Reply from 61.197.203.81: bytes=32 time=348ms TTL=109
Reply from 61.197.203.81: bytes=32 time=341ms TTL=109
Reply from 61.197.203.81: bytes=32 time=346ms TTL=109
Reply from 61.197.203.81: bytes=32 time=373ms TTL=109
Reply from 61.197.203.81: bytes=32 time=347ms TTL=109
Reply from 61.197.203.81: bytes=32 time=495ms TTL=109
Reply from 61.197.203.81: bytes=32 time=355ms TTL=109
Reply from 61.197.203.81: bytes=32 time=347ms TTL=109
Reply from 61.197.203.81: bytes=32 time=348ms TTL=109
Reply from 61.197.203.81: bytes=32 time=346ms TTL=109
Reply from 61.197.203.81: bytes=32 time=361ms TTL=109
Reply from 61.197.203.81: bytes=32 time=349ms TTL=109
Reply from 61.197.203.81: bytes=32 time=359ms TTL=109
Reply from 61.197.203.81: bytes=32 time=344ms TTL=109
Reply from 61.197.203.81: bytes=32 time=343ms TTL=109
Reply from 61.197.203.81: bytes=32 time=348ms TTL=109
Reply from 61.197.203.81: bytes=32 time=339ms TTL=109
Reply from 61.197.203.81: bytes=32 time=356ms TTL=109

tracert to ur server: (used the same tool you used)

Code:

|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                             59.93.254.1 -    0 |  331 |  331 |    9 |   33 |  199 |   25 |
|                          218.248.255.66 -    0 |  331 |  331 |   58 |   74 |  254 |   74 |
|59.163.201.153.static.chennai.vsnl.net.in -    0 |  331 |  331 |   55 |   72 |  239 |   68 |
|                            172.31.43.42 -    0 |  331 |  331 |  117 |  137 |  323 |  137 |
|                         203.131.241.157 -    0 |  331 |  331 |  337 |  357 |  545 |  354 |
| xe-3-1-0.r21.newthk02.hk.bb.gin.ntt.net -    1 |  327 |  326 |  333 |  346 |  466 |  345 |
|     as-1.r25.tokyjp01.jp.bb.gin.ntt.net -    0 |  331 |  331 |  335 |  360 |  576 |  347 |
|     ae-5.a20.tokyjp01.jp.ra.gin.ntt.net -    0 |  331 |  331 |  334 |  355 |  527 |  350 |
|                          203.105.72.162 -    1 |  327 |  326 |  317 |  330 |  517 |  330 |
|     xg1-4-notemachi-core16.sphere.ad.jp -    1 |  327 |  326 |  322 |  345 |  570 |  324 |
|         xg7-4-kanda-core16.sphere.ad.jp -    1 |  327 |  326 |  333 |  350 |  558 |  344 |
|                         210.165.252.206 -    1 |  327 |  326 |  338 |  348 |  404 |  345 |
|                         210.165.252.225 -    0 |  331 |  331 |  322 |  341 |  515 |  337 |
|                           210.139.58.66 -    0 |  331 |  331 |  342 |  357 |  536 |  355 |
|             nas932.p-nagano.nttpc.ne.jp -    0 |  331 |  331 |  339 |  350 |  525 |  344 |
|                           61.197.203.80 -   15 |  211 |  181 |  342 |  350 |  384 |  347 |
|                           61.197.203.81 -    0 |  331 |  331 |  340 |  361 |  529 |  353 |
|________________________________________________|______|______|______|______|______|______|
   WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

This is really early in the morning (5:30am). Pings to US are around 282-290ms, and EU is oddly the same. Japan is higher still with 330-350ms right now.

Thanks

Are you sill getting packet loss?

I always get over 300ms to USA.

Originally Posted by button_masher

Thanks

Are you sill getting packet loss?

I always get over 300ms to USA.

yes, still getting packet loss and latency to the USA never seems to be lower than 310-330ms (as opposed to the normal good latency of 285-300ms).

Code:

Reply from 66.199.244.82: bytes=32 time=327ms TTL=56
Reply from 66.199.244.82: bytes=32 time=327ms TTL=56
Reply from 66.199.244.82: bytes=32 time=326ms TTL=56
Request timed out.
Request timed out.
Reply from 66.199.244.82: bytes=32 time=324ms TTL=56
Reply from 66.199.244.82: bytes=32 time=325ms TTL=56
Reply from 66.199.244.82: bytes=32 time=328ms TTL=56
Reply from 66.199.244.82: bytes=32 time=327ms TTL=56
Reply from 66.199.244.82: bytes=32 time=328ms TTL=56
Reply from 66.199.244.82: bytes=32 time=329ms TTL=56
Reply from 66.199.244.82: bytes=32 time=346ms TTL=56
Reply from 66.199.244.82: bytes=32 time=329ms TTL=56
Reply from 66.199.244.82: bytes=32 time=328ms TTL=56
Reply from 66.199.244.82: bytes=32 time=327ms TTL=56
Reply from 66.199.244.82: bytes=32 time=328ms TTL=56
Reply from 66.199.244.82: bytes=32 time=327ms TTL=56
Reply from 66.199.244.82: bytes=32 time=328ms TTL=56
Reply from 66.199.244.82: bytes=32 time=329ms TTL=56
Reply from 66.199.244.82: bytes=32 time=330ms TTL=56
Reply from 66.199.244.82: bytes=32 time=330ms TTL=56
Reply from 66.199.244.82: bytes=32 time=327ms TTL=56
Reply from 66.199.244.82: bytes=32 time=329ms TTL=56
Reply from 66.199.244.82: bytes=32 time=328ms TTL=56
Reply from 66.199.244.82: bytes=32 time=327ms TTL=56
Reply from 66.199.244.82: bytes=32 time=328ms TTL=56
Reply from 66.199.244.82: bytes=32 time=327ms TTL=56
Reply from 66.199.244.82: bytes=32 time=330ms TTL=56
Reply from 66.199.244.82: bytes=32 time=327ms TTL=56
Reply from 66.199.244.82: bytes=32 time=340ms TTL=56
Reply from 66.199.244.82: bytes=32 time=327ms TTL=56
Reply from 66.199.244.82: bytes=32 time=330ms TTL=56
Reply from 66.199.244.82: bytes=32 time=325ms TTL=56
Reply from 66.199.244.82: bytes=32 time=328ms TTL=56
Reply from 66.199.244.82: bytes=32 time=327ms TTL=56
Reply from 66.199.244.82: bytes=32 time=326ms TTL=56
Reply from 66.199.244.82: bytes=32 time=327ms TTL=56
Reply from 66.199.244.82: bytes=32 time=329ms TTL=56
Reply from 66.199.244.82: bytes=32 time=327ms TTL=56
Reply from 66.199.244.82: bytes=32 time=331ms TTL=56
Reply from 66.199.244.82: bytes=32 time=327ms TTL=56
Reply from 66.199.244.82: bytes=32 time=326ms TTL=56
Reply from 66.199.244.82: bytes=32 time=325ms TTL=56
Reply from 66.199.244.82: bytes=32 time=332ms TTL=56
Reply from 66.199.244.82: bytes=32 time=327ms TTL=56
Reply from 66.199.244.82: bytes=32 time=326ms TTL=56
Reply from 66.199.244.82: bytes=32 time=327ms TTL=56
Request timed out.
Request timed out.
Reply from 66.199.244.82: bytes=32 time=327ms TTL=56
Reply from 66.199.244.82: bytes=32 time=328ms TTL=56
Reply from 66.199.244.82: bytes=32 time=329ms TTL=56
Reply from 66.199.244.82: bytes=32 time=324ms TTL=56
Reply from 66.199.244.82: bytes=32 time=331ms TTL=56
Reply from 66.199.244.82: bytes=32 time=328ms TTL=56
Reply from 66.199.244.82: bytes=32 time=327ms TTL=56
Reply from 66.199.244.82: bytes=32 time=330ms TTL=56

I had 3-4 torrents on last night and only 300mb was downloaded (2 very well seeded games an emulator ROM iso image and some random software).
The graph on utorrent was also a mess.

So I'd assume there was severe latency problems/jitter/loss during the night also.

10:53 am, september 12th
This what pings look like, every 5-10 minutes:

Code:

Reply from 66.199.244.82: bytes=32 time=272ms TTL=49
Reply from 66.199.244.82: bytes=32 time=271ms TTL=49
Reply from 66.199.244.82: bytes=32 time=272ms TTL=49
Request timed out.
Reply from 66.199.244.82: bytes=32 time=323ms TTL=45
Request timed out.
Reply from 66.199.244.82: bytes=32 time=410ms TTL=45
Reply from 66.199.244.82: bytes=32 time=411ms TTL=45
Reply from 66.199.244.82: bytes=32 time=407ms TTL=45
Reply from 66.199.244.82: bytes=32 time=414ms TTL=45
Reply from 66.199.244.82: bytes=32 time=408ms TTL=45
Reply from 66.199.244.82: bytes=32 time=415ms TTL=45
Reply from 66.199.244.82: bytes=32 time=416ms TTL=45
Reply from 66.199.244.82: bytes=32 time=410ms TTL=45
Reply from 66.199.244.82: bytes=32 time=411ms TTL=45
Reply from 66.199.244.82: bytes=32 time=414ms TTL=45
Reply from 66.199.244.82: bytes=32 time=413ms TTL=45
Reply from 66.199.244.82: bytes=32 time=412ms TTL=45
Reply from 66.199.244.82: bytes=32 time=485ms TTL=45
Reply from 66.199.244.82: bytes=32 time=489ms TTL=45
Reply from 66.199.244.82: bytes=32 time=495ms TTL=45
Reply from 66.199.244.82: bytes=32 time=483ms TTL=45
Reply from 66.199.244.82: bytes=32 time=482ms TTL=45
Reply from 66.199.244.82: bytes=32 time=460ms TTL=45
Reply from 66.199.244.82: bytes=32 time=456ms TTL=45
Reply from 66.199.244.82: bytes=32 time=456ms TTL=45
Reply from 66.199.244.82: bytes=32 time=458ms TTL=45
Reply from 66.199.244.82: bytes=32 time=433ms TTL=45
Reply from 66.199.244.82: bytes=32 time=422ms TTL=45
Request timed out.
Reply from 66.199.244.82: bytes=32 time=413ms TTL=45
Reply from 66.199.244.82: bytes=32 time=415ms TTL=45
Reply from 66.199.244.82: bytes=32 time=417ms TTL=45
Reply from 66.199.244.82: bytes=32 time=345ms TTL=47
Reply from 66.199.244.82: bytes=32 time=345ms TTL=47
Reply from 66.199.244.82: bytes=32 time=344ms TTL=47
Reply from 66.199.244.82: bytes=32 time=345ms TTL=47
Reply from 66.199.244.82: bytes=32 time=346ms TTL=47
Reply from 66.199.244.82: bytes=32 time=346ms TTL=47
Reply from 66.199.244.82: bytes=32 time=286ms TTL=49
Reply from 66.199.244.82: bytes=32 time=287ms TTL=49
Reply from 66.199.244.82: bytes=32 time=288ms TTL=49
Reply from 66.199.244.82: bytes=32 time=287ms TTL=49
Reply from 66.199.244.82: bytes=32 time=288ms TTL=49
Reply from 66.199.244.82: bytes=32 time=271ms TTL=49
Reply from 66.199.244.82: bytes=32 time=272ms TTL=49
Reply from 66.199.244.82: bytes=32 time=271ms TTL=49

So far I've emailed the nodal officer he just forwarded my email to the local exchange. They called me about 4 times, each time asking if my phone was ok. Although I told them it wasn't my phone, nothing was done. They didn't give any information about internet.

And this time i cant login to PSN and websites are opening very slowly....

Code:

        192.168.1.1 -    0 |  106 |  106 |    0 |    1 |   57 |    0 |

|                            117.198.32.1 -   28 |   48 |   35 |   29 |   37 |  119 |   64 |

|                         218.248.168.166 -   22 |   55 |   43 |   30 |   42 |  140 |   31 |

|59.163.207.81.static.chennai.vsnl.net.in -   39 |   39 |   24 |    0 |   78 |  122 |   75 |

|    ix-4-2.tcore1.CXR-Chennai.as6453.net -   38 |   40 |   25 |   73 |   78 |  111 |   77 |

|    if-3-3.tcore2.CXR-Chennai.as6453.net -   36 |   42 |   27 |  105 |  115 |  142 |  109 |

|  if-5-2.tcore2.SVW-Singapore.as6453.net -   39 |   39 |   24 |  105 |  113 |  174 |  106 |

|                              116.0.71.2 -   37 |   41 |   26 |  105 |  116 |  209 |  132 |

|             an-ats-int10.starhub.net.sg -   48 |   34 |   18 |    0 |  116 |  209 |  109 |

|                           203.117.6.210 -   32 |   44 |   30 |  106 |  124 |  299 |  107 |

|            203-174-80-210.rev.ne.com.sg -   37 |   41 |   26 |  107 |  117 |  209 |  109 |

|                mail.newmediaexpress.com -   22 |   56 |   44 |  106 |  114 |  181 |  1

Whats wrong with BSNL?

Nothing can be done as far as the latency is concerned(BSNL).