MTNL Broadband Pathetic speeds for certain sites at random times

  • Thread starter Thread starter strideram
  • Start date Start date
  • Replies Replies 11
  • Views Views 3,240

strideram

Newbie
Messages
21
Location
NA
ISP
Local Cable (WNet), MTNL Mumbai
I am really perplexed by this behaviour of Triband. Say if I am downloading a file from a particular mirror on link-removed, say Level 3. I will get full speeds. 1.3Mbps. Now if I pause that download and try downloading the same file from another server, the speeds wouldnt go above 30-40 kBps. And this behaviour is not consistent. For example, I was downloading a file from msdn yesterday. The entire day I was getting very less speeds. I resumed the download today and I was getting full speed. I had restarted my modem many times yesterday hoping to get an ipaddress on which I would get full speeds. This is getting irritating off late, as many sites dont provide mirrors. So, am stuck with 30kBps speeds for an indefinite period. And obviously, this is also affecting browsing as well. The same site, infact the same page will render quickly sometimes and will timeout the remainging time.
 
what dns servers r u using ? seems more like a DNS issueuse below dns servers and check if u see any difference203.124.250.70 ( tata)59.144.127.16 (airtel )
 
@merc782, thanks for the reply. I had switched away from the default mtnl dns when the problem began. I had been using the google dns. And am now using the dns by tata. The problem persisted in all cases. And when you think about it, it shouldnt be a dns issue. The dns is queried only at the start, to get to ip address. Once that is resolved, its cached locally by the browser. So, the 2nd query onwards should hit the dns server at all. And secondly, dns shouldnt affect the download speeds one the download has begun. What makes matters more irritating is that mtnl staff has no clue what is happening. They keep pointing out that some sites are working, some downloads are getting full speeds, so the problem is not on their end...
 
run below command when a site works and when it doesnt work, and post the results herec:\> tracert -w 600 websitethat will help in identifying the issue behind the problem
 
I was downloading the java me 3.0 from the sun site yesterday and I wasn't going above 30kBps. Tried the same download today. 160kBps. The trace route results for the download server [for today, ie when I am getting proper speeds]
Code:
tracert -w 600 cds-esd.sun.comTracing route to a1827.d.akamai.net [203.124.225.40]over a maximum of 30 hops:  1
 
Youtube vids are barely streaming today. Yesterday, most vids were streaming properly. So, what exactly do the results tell us? Just an observation, even though the times shown are in ms, i was definitely waiting for close to a minute or 2 for the trace route to complete.

Slow youtube.
Code:
tracert -w 600 www.youtube.comTracing route to youtube-ui.l.google.com [72.14.203.139]over a maximum of 30 hops:  1
 
youtube has been rolling out their new page layout today. maybe that was the reason behind the problems today?
 
That is more or less what I am saying. This problem is difficult to prove. When ever I complain to mtnl they put it off saying that it must be a site problem. Youtube pulls its videos off various servers. Chances are the next video you watch will be from a server in a different geo location. And thats the problem. As long as I am on the same ipaddress, a particular video will just not stream. I try some other video, it may or may not work. But what I have noticed is, if I restart my modem a few times, I keep getting different ip addresses and with one of those ip addresses, the problematic video will start streaming properly. But now some other video will stop streaming. Its maddening. The problem is not just with stream, basically any kind of downloading. Sometimes they work, sometimes they dont... :(
 
My Orkut is very slow from last week even though M on 1Mbps Unlimited, some problem with the Google server from past few days, hope it get's resolved soon.
 
the problem sorted itself out some 2 weeks after posting. i still do not know what caused it in the first place though...
 
Back