BSNL Broadband Routing Issue [High Latency + Low Speeds]

  • Thread starter Thread starter AgentX
  • Start date Start date
  • Replies Replies 108
  • Views Views 26,521

AgentX

The Secret Agent
Messages
495
Location
Chennai
ISP
Airtel / BSNL
Hey guys,

I seem to be experiencing a problem with BSNL (and a couple of other friends based in Chennai with the same issue) and I'd like to know if anyone else here is experiencing the same as well as it's been 15 days since the problem started and there hasn't been a resolution yet.

Here's the deal, I'm currently on BBG Combo ULD 1350 (4mbps) and my connection works superb at 11:30PM to 09:00AM (only at these times) and at the rest of the times, it's screwed up completely and I can't even reach 1mbps. I've sufficient proofs advocating my claims and I've been monitoring my connection day/night from the past 2 months just because of this.

Before anyone can put a blame on my modem/router/snr values/dns, here's a screenshot from my router page:
(note: I use G.DMT for stability reasons and no torrents or downloads were on during the tests were taken)



As you can see, my connection and my line is perfectly configured and I should be getting speeds of 4mbps, but what do I get? This :



From my diagnosis, my connection, at the 90% of the times, passes through this VSNL router (or gateway, or switch or whatever that is) :
59.163.206.157.static.chennai.vsnl.net.in [59.163.206.157] - and it's pathetic. I have to be getting around 20ms or lower, but it gives me 200+ which not only increases my latency to other servers, it also craps out my speed and it's extremely laggy. Here's a graphical representation on what exactly happens when I traceroute Google (via its Chennai server as it's cached on my end already) :



It's been going on like this for a while and it's at the top of my head right now. Who should I be contacting to get this fixed? I can't just wait for a 'magical' gateway as it's not easier these days. I tried for an hour earlier today and failed while yesterday, it took me only a couple of minutes.

For the record, below are the speedtest/traceroutes done at the prime time (i.e, Early morning / Midnight) with the same 117.201.0.1 local gateway :



And a traceroute to Google as well, and you can clearly see the difference :



Any ideas guys? Anyone I should be contacted specifically? Any email addresses I should forward these reports to? Anything will be appreciated as I'm not the only one experiencing such a laggy connection, more than 3 of my friends in Chennai are reporting the same.
 
experiencing same problem here in bangalore.seeing this from 3 days.
 
As I'd posted in the other thread, same thing happens, now that you mentioned it, the speed test is perfect from 11 30 pm to 9 am and goes haywire after that, though if you've noticed, all downloads run at full speeds at all times, its only the speedtest results that are screwed ( for me both on DSL and fibre) , also the pings on fibre are alright, its only on DSL that they suck during the day. I'm thinking of emailing the noc
 
In short: it's screwy routing, partially because of BSNL ineptitude and partially because you are using Google's public DNS and partially there should probably be some blame on Tata as well for allowing BSNL to, I guess, over-utilize their capacity. I don't blame you for using Google's DNS, though - it is more reliable and in most cases, better. Assuming, of course, that the route to 8.8.8.8 and 8.8.4.4 are correct with your ISP. For me, those servers are 2ms away, but for you, it may not be even using one of the mirrors of those servers located in India. Sometimes.

But something is causing routing to be funky - from where I sit, the IP address of that Google server suggests it to be physically located in Japan, yet that you can get 22ms to it some other times suggests maybe it's not. Maybe there is some weird things going on with multicasting which are causing things to go haywire - even I'm confused by what's going on here!

Considering that Google has servers both in Chennai and Mumbai (including web, cache, dns and youtube at the very least!) - in theory, you should be hitting a server that is like maa03s05-in-f20.1e100.net or worst case, bom03s02-in-f20.1e100.net.

Please post a trace to speedtestmum.vodafone.ind.in, speedtestdel.vodafone.ind.in or chenapplg.vodafone.ind.in and let us know what you get.
 
Last edited by a moderator:
its only on DSL that they suck during the day.


Exactly the same problem is with me.No idea why this happens everyday.Very inconsistent during daytime.It doesn't affect the d/l speed but the browsing is horrible.(during daytime)
 


I don't blame you for using Google's DNS, though - it is more reliable and in most cases, better. Assuming, of course, that the route to 8.8.8.8 and 8.8.4.4 are correct with your ISP. For me, those servers are 2ms away, but for you, it may not be even using one of the mirrors of those servers located in India. Sometimes.

When I'm connected to the proper gateway, and when its midnight/early morning, I get the following to Google's DNS, which is why I'm using them in the first place. BSNL's DNS itself is 25ms+ away for me.

Tracing route to google-public-dns-a.google.com [8.8.8.8]
over a maximum of 30 hops:

1
 
facing the same issue here in bangalore as well, latency has increased to 300-400 ms from around 90-100ms to chennai/mumbai server
 
Got a call from the PG cell. Apparently, they're aware of the issue and the noc has told them that the estimated time for fixing the issue is going to approximately one week. The PG Guy said, he'd call as and when they receive updates from the noc, the thing is the noc people haven't told them what the issue is. 😕
 
x720 said:
Why is it that latency on Tata's network is high, and not when it goes via reliance ? Here is a tracert to rcom.co.in :

Tracing route to Welcome to Reliance Communications [220.226.182.128]
over a maximum of 30 hops:

1 1 ms 100ms. Yes, we're 1200km apart but it shouldn't be *this bad*.

x720 said:
To vodafone delhi :

Tracing route to speedtestdel.vodafone.ind.in [182.19.95.104]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms DD-WRT [10.0.0.1]
2 2 ms 1 ms 1 ms 117.198.120.1
3 2 ms 3 ms 2 ms 218.248.169.38
4 74 ms 72 ms 72 ms 218.100.48.28
5 68 ms 69 ms 71 ms 182.19.95.125
6 76 ms 82 ms 81 ms speedtestdel.vodafone.ind.in [182.19.95.104]

Trace complete.

See the efficiency of NIXI at work! (218.100.48.x is a NIXI range).

BSNL probably needs to do what Ripunjay did for us the other night and force some BGP magic to ensure the cleanest routing to that server (it took him literally 30 seconds when I informed him of the issue, I don't see why it should take them any longer) - instead of going via NIXI it should go via some other network.

x720 said:
Tracing route to chenapplg.vodafone.ind.in [182.19.95.68]
over a maximum of 30 hops:

1 1 ms 3 ms
 
Tracing route to Google [74.125.236.209]
over a maximum of 30 hops:

1 1 ms
 
1 1 ms 1 ms 1 ms 192.168.1.1
2 7 ms 6 ms 6 ms 117.198.128.1
3 7 ms 5 ms 6 ms 218.248.169.42
4 30 ms 32 ms 31 ms 218.248.251.62
5 380 ms 382 ms 380 ms 218.254.79.182.airtelbroadband.in [182.79.254.218]
6 412 ms 419 ms 422 ms 203.101.100.186
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * *

and right now, I am one the good gateway.

to vodafone -




Tracing route to sifycorp.com [202.144.75.66]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.1.1
2 7 ms 6 ms 6 ms 117.198.128.1
3 7 ms 7 ms 7 ms 218.248.169.46
4 42 ms 42 ms 43 ms 218.100.48.12
5 42 ms 42 ms 42 ms segment-119-227.sify.net [119.227.107.107]
6 41 ms 41 ms 41 ms segment-119-227.sify.net [119.227.4.186]
7 42 ms 41 ms 42 ms segment-119-227.sify.net [119.227.117.22]
8 43 ms 42 ms 42 ms segment-119-227.sify.net [119.227.106.2]
9 43 ms 43 ms 43 ms 221-134-30-244.sify.net [221.134.30.244]
10 41 ms 41 ms 41 ms lan-75-144-202-66.maa.sify.net [202.144.75.66]

Trace complete.
 

Top