Too Much Packet Loss

  • Thread starter Thread starter manu4rhyme
  • Start date Start date
  • Replies Replies 2
  • Views Views 2,064
M

manu4rhyme

Newbie
Messages
5
Location
NA
ISP
Sify Broadband
Suddenly, from morning i am getting too much of packet loss.
On pingtest.net,

http://www.pingtest.net

I was getting a B grade yesterday with 0 packet loss and a ping of 80ms.

my traceroute to google is :

Tracing route to Google [209.85.231.104]

over a maximum of 30 hops:



1 36 ms 39 ms 28 ms 117.205.144.1

2 31 ms 36 ms 32 ms 218.248.175.186

3 203 ms * 200 ms 218.248.246.130

4 209 ms 204 ms * 115.113.128.17.static-mumbai.vsnl.net.in [115.113.128.17]

5 227 ms 225 ms 232 ms 59.163.25.242.static.vsnl.net.in [59.163.25.242]

6 486 ms * 465 ms 121.240.0.10.static-Mumbai.vsnl.net.in [121.240.0.10]

7 466 ms 470 ms 459 ms 216.239.43.214

8 * 460 ms 461 ms 72.14.232.100

9 464 ms 493 ms 464 ms 72.14.238.90

10 461 ms 467 ms * maa03s01-in-f104.1e100.net [209.85.231.104]



Trace complete.


My pings to IP 218.248.175.186 :

Pinging 218.248.175.186 with 32 bytes of data:



Reply from 218.248.175.186: bytes=32 time=35ms TTL=254

Reply from 218.248.175.186: bytes=32 time=49ms TTL=254

Reply from 218.248.175.186: bytes=32 time=27ms TTL=254

Reply from 218.248.175.186: bytes=32 time=41ms TTL=254

Reply from 218.248.175.186: bytes=32 time=36ms TTL=254

Reply from 218.248.175.186: bytes=32 time=37ms TTL=254

Reply from 218.248.175.186: bytes=32 time=34ms TTL=254

Reply from 218.248.175.186: bytes=32 time=31ms TTL=254

Reply from 218.248.175.186: bytes=32 time=30ms TTL=254

Reply from 218.248.175.186: bytes=32 time=35ms TTL=254

Reply from 218.248.175.186: bytes=32 time=34ms TTL=254

Reply from 218.248.175.186: bytes=32 time=37ms TTL=254

Reply from 218.248.175.186: bytes=32 time=34ms TTL=254

Reply from 218.248.175.186: bytes=32 time=31ms TTL=254

Reply from 218.248.175.186: bytes=32 time=32ms TTL=254

Reply from 218.248.175.186: bytes=32 time=29ms TTL=254

Reply from 218.248.175.186: bytes=32 time=30ms TTL=254

Reply from 218.248.175.186: bytes=32 time=29ms TTL=254

Reply from 218.248.175.186: bytes=32 time=34ms TTL=254

Reply from 218.248.175.186: bytes=32 time=29ms TTL=254

Reply from 218.248.175.186: bytes=32 time=30ms TTL=254

Reply from 218.248.175.186: bytes=32 time=29ms TTL=254



Ping statistics for 218.248.175.186:

Packets: Sent = 22, Received = 22, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 27ms, Maximum = 49ms, Average = 33ms

Control-C



My pings to Google :

Pinging Google [209.85.231.104] with 32 bytes of data:



Reply from 209.85.231.104: bytes=32 time=452ms TTL=44

Request timed out.

Reply from 209.85.231.104: bytes=32 time=458ms TTL=44

Reply from 209.85.231.104: bytes=32 time=453ms TTL=44

Reply from 209.85.231.104: bytes=32 time=456ms TTL=44

Reply from 209.85.231.104: bytes=32 time=455ms TTL=44

Reply from 209.85.231.104: bytes=32 time=458ms TTL=44

Reply from 209.85.231.104: bytes=32 time=458ms TTL=44

Reply from 209.85.231.104: bytes=32 time=451ms TTL=44

Reply from 209.85.231.104: bytes=32 time=454ms TTL=44

Reply from 209.85.231.104: bytes=32 time=455ms TTL=44

Reply from 209.85.231.104: bytes=32 time=454ms TTL=44

Reply from 209.85.231.104: bytes=32 time=458ms TTL=44

Request timed out.

Reply from 209.85.231.104: bytes=32 time=457ms TTL=44



Ping statistics for 209.85.231.104:

Packets: Sent = 15, Received = 13, Lost = 2 (13% loss),

Approximate round trip times in milli-seconds:

Minimum = 451ms, Maximum = 458ms, Average = 455ms

Control-C


So i guess maybe the problem is after the IP 218.248.175.186.

What do you guys think?
And how long could it take for this problem to be fixed since it has been the whole day today and i also experienced slow browsing a week b4 but i did not check packet losses that time and i got a feeling it was this packet loss that time too.
Moreover pings to google were just ~90ms yesterday too.

Thanks, Avinash.
 
Similar problem - very high latency + packet loss; it happens randomly for random durations.BSNL seems to be changing routing paths a lot in the last few days for whatever reason; and some of these routes are highly congested.Traffic to USA seem to be routed via london/nyc savvis.net routers sometimes and then TATA mcore/icore servers in LA at other times.Each of these routes have horrible congestion at different times.BSNL is very slow in picking up congestion and switching to a different routing.In any case overall reliability and packet loss/line quality is simply awful.Latencies to the US are 320-340 ms at the very best (even singapore gets 150-200)And EU are around 200ms.This shoots up to 500-600ms (US) and 350-400ms (EU) very often accompanied with terrible packet loss.You will probably get the default answer "switch to open dns", but frankly no matter what dns you use it's mostly irrelevant when the entire routing infrastructure is a steaming pile of crap.Personally I'm fed up of the lack of any interest from any party whatsoever to remedy the situation.
 

Top