BSNL Broadband Routing Issue [High Latency + Low Speeds]

[itzmynet]

@mgcarley can you explain this? both the tracert done at the same time

Tracing route to maa03s04-in-f24.1e100.net [74.125.236.56]over a maximum of 30 hops:  1     4 ms     2 ms     2 ms  192.168.1.1  2     *        *        *     Request timed out.  3    29 ms    28 ms    29 ms  ABTS-AP-Static-241.240.169.122.airtelbroadband.in [122.169.240.241]  4    28 ms    29 ms    28 ms  125.16.7.125  5    48 ms    49 ms    48 ms  182.79.255.1  6   124 ms    47 ms   108 ms  72.14.223.145  7    57 ms    48 ms    58 ms  66.249.94.170  8    48 ms    49 ms    50 ms  209.85.241.33  9    41 ms    40 ms    41 ms  maa03s04-in-f24.1e100.net [74.125.236.56]Trace complete.Tracing route to google.co.in [74.125.235.56]over a maximum of 30 hops:  1     2 ms     2 ms     2 ms  192.168.1.1  2     *       30 ms     *     ABTS-AP-Dynamic-001.128.169.122.airtelbroadband.in [122.169.128.1]  3    30 ms    33 ms    28 ms  ABTS-AP-Static-241.240.169.122.airtelbroadband.in [122.169.240.241]  4    29 ms    28 ms    28 ms  125.16.7.125  5    55 ms    55 ms    55 ms  182.79.255.1  6   147 ms    56 ms   147 ms  72.14.223.145  7    56 ms    57 ms    54 ms  66.249.94.168  8    82 ms    81 ms    81 ms  66.249.94.72  9    86 ms    85 ms    85 ms  72.14.233.199 10    87 ms    89 ms    88 ms  sin01s05-in-f24.1e100.net [74.125.235.56]Trace complete.

 

[mgcarley]

@mgcarley can you explain this? both the tracert done at the same time

Tracing route to maa03s04-in-f24.1e100.net [74.125.236.56]over a maximum of 30 hops:  1     4 ms     2 ms     2 ms  192.168.1.1  2     *        *        *     Request timed out.  3    29 ms    28 ms    29 ms  ABTS-AP-Static-241.240.169.122.airtelbroadband.in [122.169.240.241]  4    28 ms    29 ms    28 ms  125.16.7.125  5    48 ms    49 ms    48 ms  182.79.255.1  6   124 ms    47 ms   108 ms  72.14.223.145  7    57 ms    48 ms    58 ms  66.249.94.170  8    48 ms    49 ms    50 ms  209.85.241.33  9    41 ms    40 ms    41 ms  maa03s04-in-f24.1e100.net [74.125.236.56]Trace complete.Tracing route to google.co.in [74.125.235.56]over a maximum of 30 hops:  1     2 ms     2 ms     2 ms  192.168.1.1  2     *       30 ms     *     ABTS-AP-Dynamic-001.128.169.122.airtelbroadband.in [122.169.128.1]  3    30 ms    33 ms    28 ms  ABTS-AP-Static-241.240.169.122.airtelbroadband.in [122.169.240.241]  4    29 ms    28 ms    28 ms  125.16.7.125  5    55 ms    55 ms    55 ms  182.79.255.1  6   147 ms    56 ms   147 ms  72.14.223.145  7    56 ms    57 ms    54 ms  66.249.94.168  8    82 ms    81 ms    81 ms  66.249.94.72  9    86 ms    85 ms    85 ms  72.14.233.199 10    87 ms    89 ms    88 ms  sin01s05-in-f24.1e100.net [74.125.235.56]Trace complete.

What's to explain? DNS might be a little wonky though because it's pointing at a server in Singapore for reasons unknown... but your pings seem largely fine, all things considered.

Also, you're on Airtel, not BSNL... Airtel's got more capacity than it knows what to do with between here and Singapore and your pings for hops 8-10 are about 20-25ms higher than mine: almost exactly what I would expect from a DSL user on a half decent network considering the distance to the server (generally speaking, not referring to Airtel specifically here).

 

[ripunjay]

@mgcarley can you explain this? both the tracert done at the same time

Tracing route to maa03s04-in-f24.1e100.net [74.125.236.56]over a maximum of 30 hops:  1     4 ms     2 ms     2 ms  192.168.1.1  2     *        *        *     Request timed out.  3    29 ms    28 ms    29 ms  ABTS-AP-Static-241.240.169.122.airtelbroadband.in [122.169.240.241]  4    28 ms    29 ms    28 ms  125.16.7.125  5    48 ms    49 ms    48 ms  182.79.255.1  6   124 ms    47 ms   108 ms  72.14.223.145  7    57 ms    48 ms    58 ms  66.249.94.170  8    48 ms    49 ms    50 ms  209.85.241.33  9    41 ms    40 ms    41 ms  maa03s04-in-f24.1e100.net [74.125.236.56]Trace complete.Tracing route to google.co.in [74.125.235.56]over a maximum of 30 hops:  1     2 ms     2 ms     2 ms  192.168.1.1  2     *       30 ms     *     ABTS-AP-Dynamic-001.128.169.122.airtelbroadband.in [122.169.128.1]  3    30 ms    33 ms    28 ms  ABTS-AP-Static-241.240.169.122.airtelbroadband.in [122.169.240.241]  4    29 ms    28 ms    28 ms  125.16.7.125  5    55 ms    55 ms    55 ms  182.79.255.1  6   147 ms    56 ms   147 ms  72.14.223.145  7    56 ms    57 ms    54 ms  66.249.94.168  8    82 ms    81 ms    81 ms  66.249.94.72  9    86 ms    85 ms    85 ms  72.14.233.199 10    87 ms    89 ms    88 ms  sin01s05-in-f24.1e100.net [74.125.235.56]Trace complete.

Airtel / Google both use link redundancy and link load sharing, so on your first trace the trace went as expected to a server / cache box hosted by google in India, second one could due to multiple reasons mostly load sharing, went to the server hosted in SG, google with its thousands of servers cannot really allocate dedicated static ip's to all servers so it uses BGP AnyCast routing to have the same ip address given to multiple servers all across the world and the clients will reach the one that is the closest, and in case the servers are down for some reason they can go to any other that the ISP's routes are advertising.

 

[itzmynet]

nslookup google.co.inServer:  ABTS-AP-Static-130.240.169.122.airtelbroadband.inAddress:  122.169.240.130Non-authoritative answer:Name:    google.co.inAddress:  74.125.235.56nslookup 74.125.235.56Server:  ABTS-AP-Static-130.240.169.122.airtelbroadband.inAddress:  122.169.240.130Name:    sin01s05-in-f24.1e100.netAddress:  74.125.235.56nslookup 74.125.235.56 8.8.8.8Server:  google-public-dns-a.google.comAddress:  8.8.8.8Name:    sin01s05-in-f24.1e100.netAddress:  74.125.235.56

 

[ripunjay]

Had setup some monitoring for the above gateways from our NMS, interesting results.


Router_BSNL_GW06 [218.248.174.201]









Router_BSNL_GW05 [218.248.174.202]










Router_TATA_RTR09 [59.163.206.158]









As you can see its mostly a link capacity issue, or just the BSNL tech team being lazy with their routing setup.

RB

 

[rsen]

BSNL Kolkata:

Ping to google:

Reply from 74.125.236.208: bytes=32 time=412ms TTL=44Reply from 74.125.236.208: bytes=32 time=414ms TTL=44Reply from 74.125.236.208: bytes=32 time=412ms TTL=44Reply from 74.125.236.208: bytes=32 time=413ms TTL=44Reply from 74.125.236.208: bytes=32 time=410ms TTL=44Reply from 74.125.236.208: bytes=32 time=413ms TTL=44Reply from 74.125.236.208: bytes=32 time=410ms TTL=44Reply from 74.125.236.208: bytes=32 time=411ms TTL=44Reply from 74.125.236.208: bytes=32 time=412ms TTL=44Reply from 74.125.236.208: bytes=32 time=411ms TTL=42Reply from 74.125.236.208: bytes=32 time=412ms TTL=44Reply from 74.125.236.208: bytes=32 time=411ms TTL=44Reply from 74.125.236.208: bytes=32 time=414ms TTL=44Reply from 74.125.236.208: bytes=32 time=410ms TTL=44Reply from 74.125.236.208: bytes=32 time=412ms TTL=44Reply from 74.125.236.208: bytes=32 time=411ms TTL=44Reply from 74.125.236.208: bytes=32 time=412ms TTL=44Reply from 74.125.236.208: bytes=32 time=412ms TTL=44Reply from 74.125.236.208: bytes=32 time=409ms TTL=44Reply from 74.125.236.208: bytes=32 time=412ms TTL=44Reply from 74.125.236.208: bytes=32 time=409ms TTL=44Reply from 74.125.236.208: bytes=32 time=410ms TTL=44Reply from 74.125.236.208: bytes=32 time=411ms TTL=44Reply from 74.125.236.208: bytes=32 time=408ms TTL=44Reply from 74.125.236.208: bytes=32 time=417ms TTL=44Reply from 74.125.236.208: bytes=32 time=410ms TTL=44Reply from 74.125.236.208: bytes=32 time=411ms TTL=44Reply from 74.125.236.208: bytes=32 time=404ms TTL=44Reply from 74.125.236.208: bytes=32 time=493ms TTL=44Reply from 74.125.236.208: bytes=32 time=514ms TTL=44Reply from 74.125.236.208: bytes=32 time=412ms TTL=44Reply from 74.125.236.208: bytes=32 time=410ms TTL=44Reply from 74.125.236.208: bytes=32 time=414ms TTL=44Reply from 74.125.236.208: bytes=32 time=412ms TTL=44Reply from 74.125.236.208: bytes=32 time=410ms TTL=44Reply from 74.125.236.208: bytes=32 time=407ms TTL=44Reply from 74.125.236.208: bytes=32 time=410ms TTL=44Reply from 74.125.236.208: bytes=32 time=405ms TTL=44Reply from 74.125.236.208: bytes=32 time=412ms TTL=44Reply from 74.125.236.208: bytes=32 time=411ms TTL=44Reply from 74.125.236.208: bytes=32 time=410ms TTL=44Reply from 74.125.236.208: bytes=32 time=411ms TTL=44Reply from 74.125.236.208: bytes=32 time=412ms TTL=44Reply from 74.125.236.208: bytes=32 time=411ms TTL=44

Traceroute to google.com:

Tracing route to google.com [74.125.236.207]over a maximum of 30 hops:  1    11 ms    11 ms    11 ms  59.93.192.1  2   126 ms   119 ms   119 ms  218.248.255.50  3    58 ms    57 ms    57 ms  59.163.206.161.static.chennai.vsnl.net.in [59.163.206.161]  4   404 ms   411 ms   419 ms  121.240.1.46  5   412 ms   411 ms   411 ms  72.14.232.110  6   413 ms   411 ms   411 ms  209.85.240.147  7   409 ms   411 ms   411 ms  maa03s17-in-f15.1e100.net [74.125.236.207]Trace complete.

Used to be mostly fine during the day with perfect connection during the nighttime (2-8) period.
Something messed up around last week and it's been horrible during the day and mostly ok in the night.
Now since yesterday it's just trash at all times wtf ?

So sick of this garbage. I'm using an Airtel connection when I need to get anything done but that's limited and has FUP with lower speeds
/rage

btw whenever this crap happens there's almost always accompanying intermittent packet loss, why is this ?
also does reconnecting and disconnecting sometimes give a good gateway ? 1/10 times I get normal latencies when I connect
saw the post about googledns being problematic so trying namebench to find a better dns, even that's taking forevvvvver .......

 

---

[mS8^Y4prh8]

Same here in Bangalore.....somehow DL speed is as advertised but Speedtest.net and browsing/streaming are downright horrible...Oh and the best part? My pings are nearly the same from Bangalore to Chennai https://www.speedtest.net and Bangalore to Wisconsin https://www.speedtest.net and I'm supposed to be on a 4mbps line

 

[mgcarley]

Had setup some monitoring for the above gateways from our NMS, interesting results.

As you can see its mostly a link capacity issue, or just the BSNL tech team being lazy with their routing setup.

RB


See, see, see... what have I been saying

 

[AgentX]

As you can see its mostly a link capacity issue, or just the BSNL tech team being lazy with their routing setup.
RB
See, see, see... what have I been saying

Thank you so much for your insights at this, it's extremely useful for consumers like myself and the others who are not informed at all.

Same here in Bangalore.....somehow DL speed is as advertised but Speedtest.net and browsing/streaming are downright horrible...Oh and the best part? My pings are nearly the same from Bangalore to Chennai and Bangalore to Wisconsin and I'm supposed to be on a 4mbps line

You're not alone buddy, even I'm on the 4mbps plan and the pings are pathetic

Got another call today, eta is 5 days approximately.

Any update from your side? It's not 5 days yet but, was just wondering. Thank you as well for keeping us updated on this.

 

[x720]

I'd asked the fibre guys to shift me permanently to the good gateway (few subscribers, so they agreed to it) here, so that's kinda been sorted out.For DSL, the noc team haven't given any more updates to the PG cell, and the PG cell says there's only so much they can doI'll probably contact the Noc, if anyone here hasn't already. Nothing much for me to say here.