BSNL Broadband Routing Issue [High Latency + Low Speeds]

[Nishant]

Same issue with me as well. Pathetic speed...

 

[mgcarley]

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*.

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.

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

1 1 ms 3 ms

 

[x720]

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

1 1 ms

 

[mgcarley]

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

1 1 ms

 

[x720]

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.

 

[mgcarley]

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.


Timeouts are to be expected, but to 218.254.79.182 and beyond... whoa!

to vodafone -





Being in Gurgaon, you *should* get much less.

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.

Another thank you to NIXI on this one, but as above, not completely awful for Gurgaon to Chennai.

 

---

[AgentX]

So now I'm on the affected gateway and my trace-routes are attached. Laggy internet and slow browsing has started once again.

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

1

 

[x720]

Got another call today, eta is 5 days approximately.

 

[essbebe]

Chennai circle : Home 750 speed upto 2 Mbps now
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\Kavika>tracert broadbandforum.co

Tracing route to broadbandforum.co [173.245.60.112]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.1.1
2 23 ms 22 ms 23 ms 117.193.48.1
3 23 ms 22 ms 23 ms 218.248.161.38 (*DELHI )
4 23 ms 23 ms 23 ms 218.248.255.6(*DELHI)

5 107 ms 135 ms 107 ms 59.163.206.157.static.chennai.vsnl.net.in [59.163.206.157]
6 133 ms * * 172.31.17.145(*Private LAN)

7 248 ms 246 ms 247 ms if-0-100.tcore1.MLV-Mumbai.as6453.net [180.87.38.5]
8 264 ms 286 ms 276 ms if-9-5.tcore1.WYN-Marseille.as6453.net [80.231.217.17]
9 264 ms 263 ms 263 ms if-8-1600.tcore1.PYE-Paris.as6453.net [80.231.217.6]
10 263 ms 262 ms 262 ms if-2-2.tcore1.PVU-Paris.as6453.net [80.231.154.17]

11 257 ms 258 ms 257 ms xe-6-3.r03.parsfr01.fr.bb.gin.ntt.net [129.250.8.177]
12 257 ms 257 ms 257 ms xe-4-1.r02.parsfr01.fr.bb.gin.ntt.net [129.250.2.156]
13 245 ms 245 ms 244 ms xe-0-0-3.cr1.cdg1.fr.nlayer.net [69.22.139.100]
14 263 ms 245 ms 245 ms as13335.xe-0-0-1-302.cr1.cdg1.fr.nlayer.net [63.141.223.18]
15 246 ms 245 ms 245 ms cf-173-245-60-112.cloudflare.com [173.245.60.112]

Trace complete.

Change DNS and try.

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\Kavika>tracert google.com

Tracing route to google.com [74.125.236.206]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.1.1
2 23 ms 23 ms 23 ms 117.193.48.1
3 23 ms 22 ms 22 ms 218.248.161.42
4 28 ms 22 ms 23 ms 218.248.255.50
5 114 ms 109 ms 106 ms 59.163.201.149.static.chennai.vsnl.net.in [59.163.201.149]

6 132 ms 108 ms 108 ms 121.240.1.50
7 115 ms 109 ms 110 ms 72.14.232.110
8 25 ms 23 ms 24 ms 209.85.240.147
9 108 ms 109 ms 109 ms maa03s17-in-f14.1e100.net [74.125.236.206]

Trace complete.

C:\Users\Kavika>

 

[mgcarley]

So now I'm on the affected gateway and my trace-routes are attached. Laggy internet and slow browsing has started once again.

As you can probably tell, the problem does NOT seem to be with VSNL, but with the links between BSNL and VSNL (hop's #3 & #4). Why you're experiencing these problems I can't say for sure as I don't know enough about the internal workings of BSNL's network, I can only extract information based on what you are showing me.

It could be a broken load balancer, faulty network interface, busy network interface, slow network interface, underpowered router(s), not enough memory in the routers or simply congestion as a result of any of the above - who knows - if I had to guess, I'd be thinking congestion.


Here you go :

...

Oh well.. NIXI..

Similar story here, by the looks of it - the links to Reliance, Airtel and NIXI seem to ALL be congested. But that seems unlikely, no? 4 separate "upstream providers" all giving shoddy speeds when BSNL's gateway is the only really consistent thing in any of the traces? Maybe it's not the links themselves, but overloading of the core switches. Underpowered equipment etc as mentioned above.

I must say, I'm somewhat flabbergasted that they let this happen. I'd be just about ready to run to the DoT if I were you... this is woeful.

I hope that was easy, I'm complaining to my area's JTO from, like, 3 months and they're not 'sure' of the problem. I had the 8mbps business plan last month and it was more pathetic as they switched me to NIB1; oh boy, that had lame pings 24/7 and laggy browsing with no additional gateways to connect to.

The problem is not necessarily the part that's difficult to figure out - it's how to solve it when they have no money to work with.

----------

C:\Users\Kavika>tracert broadbandforum.co

Tracing route to broadbandforum.co [173.245.60.112]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.1.1
2 23 ms 22 ms 23 ms 117.193.48.1
3 23 ms 22 ms 23 ms 218.248.161.38 (*DELHI )
4 23 ms 23 ms 23 ms 218.248.255.6(*DELHI)

5 107 ms 135 ms 107 ms 59.163.206.157.static.chennai.vsnl.net.in [59.163.206.157]
6 133 ms * * 172.31.17.145(*Private LAN)

7 248 ms 246 ms 247 ms if-0-100.tcore1.MLV-Mumbai.as6453.net [180.87.38.5]
8 264 ms 286 ms 276 ms if-9-5.tcore1.WYN-Marseille.as6453.net [80.231.217.17]
9 264 ms 263 ms 263 ms if-8-1600.tcore1.PYE-Paris.as6453.net [80.231.217.6]
10 263 ms 262 ms 262 ms if-2-2.tcore1.PVU-Paris.as6453.net [80.231.154.17]

11 257 ms 258 ms 257 ms xe-6-3.r03.parsfr01.fr.bb.gin.ntt.net [129.250.8.177]
12 257 ms 257 ms 257 ms xe-4-1.r02.parsfr01.fr.bb.gin.ntt.net [129.250.2.156]
13 245 ms 245 ms 244 ms xe-0-0-3.cr1.cdg1.fr.nlayer.net [69.22.139.100]
14 263 ms 245 ms 245 ms as13335.xe-0-0-1-302.cr1.cdg1.fr.nlayer.net [63.141.223.18]
15 246 ms 245 ms 245 ms cf-173-245-60-112.cloudflare.com [173.245.60.112]

Trace complete.


I'm seeing similar results on Tata tonight too. I get the same IP address and similar pings for this route - normally to broadbandforum and hayai I get like 50 or 60ms, so maybe cloudflare is being weird. It's not BSNL for a change!

C:\Users\Kavika>tracert google.com

Tracing route to google.com [74.125.236.206]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.1.1
2 23 ms 23 ms 23 ms 117.193.48.1
3 23 ms 22 ms 22 ms 218.248.161.42
4 28 ms 22 ms 23 ms 218.248.255.50
5 114 ms 109 ms 106 ms 59.163.201.149.static.chennai.vsnl.net.in [59.163.201.149]

6 132 ms 108 ms 108 ms 121.240.1.50
7 115 ms 109 ms 110 ms 72.14.232.110
8 25 ms 23 ms 24 ms 209.85.240.147
9 108 ms 109 ms 109 ms maa03s17-in-f14.1e100.net [74.125.236.206]

Trace complete.

C:\Users\Kavika>

This... this isn't good.

C:\Users\Mathew Carley>tracert -d maa03s17-in-f14.1e100.net


Tracing route to maa03s17-in-f14.1e100.net [74.125.236.206]
over a maximum of 30 hops:


1 1 ms