Nikhil Soni
Newbie
- Messages
- 90
- Location
- NA
My route during day times ::
Tracing route to google.com [74.125.236.133]
over a maximum of 30 hops:
1
Tracing route to google.com [74.125.236.133]
over a maximum of 30 hops:
1
-
Amazon Deals - ToS - Warp
Screwed up routes in BSNL
- Thread starter elepton
- Start date
- Replies 43
- Views 8,042
The same with me too. Right now I am getting a bandwidth of 0.02 mbps on Speedtest Delhi server. BSNL may as well take away even that and shut down the broadband since it's unusable as of now anyways.
The routing is badly screwed up
Tracing route to google.com [74.125.236.162] over a maximum of 30 hops:
1 2 ms 2 ms 2 ms 192.168.0.1
2 * * * Request timed out.
3 10 ms 9 ms 11 ms 117.194.64.1
4 10 ms 9 ms 11 ms 218.248.162.70
5 292 ms 298 ms 294 ms 218.248.255.70
6 434 ms 403 ms 485 ms 59.163.206.45.static.chennai.vsnl.net.in [59.163.206.45]
7 370 ms 369 ms * 121.240.1.46
8 370 ms * 376 ms 72.14.233.204
9 369 ms * 370 ms 209.85.240.145
10 369 ms * 368 ms maa03s16-in-f2.1e100.net [74.125.236.162]
Trace complete.
The routing is badly screwed up
Tracing route to google.com [74.125.236.162] over a maximum of 30 hops:
1 2 ms 2 ms 2 ms 192.168.0.1
2 * * * Request timed out.
3 10 ms 9 ms 11 ms 117.194.64.1
4 10 ms 9 ms 11 ms 218.248.162.70
5 292 ms 298 ms 294 ms 218.248.255.70
6 434 ms 403 ms 485 ms 59.163.206.45.static.chennai.vsnl.net.in [59.163.206.45]
7 370 ms 369 ms * 121.240.1.46
8 370 ms * 376 ms 72.14.233.204
9 369 ms * 370 ms 209.85.240.145
10 369 ms * 368 ms maa03s16-in-f2.1e100.net [74.125.236.162]
Trace complete.
Yep, same here.
The latency jumps as soon as the packet reaches TATA/VSNL.
Code:
$ date; traceroute google.comTue May 22 12:14:17 IST 2012traceroute to google.com (74.125.236.64), 30 hops max, 60 byte packets 1 117.205.xxx.1 (117.205.xxx.1) 5.428 ms 6.311 ms 7.014 ms 2 218.248.175.246 (218.248.175.246) 12.944 ms 13.109 ms 13.600 ms 3 115.113.128.17.static-mumbai.vsnl.net.in (115.113.128.17) 390.310 ms * 393.490 ms 4 * 115.113.165.98.static-mumbai.vsnl.net.in (115.113.165.98) 388.527 ms 390.930 ms 5 72.14.232.202 (72.14.232.202) 397.052 ms 396.820 ms * 6 72.14.232.100 (72.14.232.100) 396.812 ms 391.846 ms 72.14.232.93 (72.14.232.93) 390.610 ms 7 209.85.249.235 (209.85.249.235) 394.999 ms 388.505 ms 389.135 ms 8 maa03s05-in-f0.1e100.net (74.125.236.64) 389.351 ms 383.266 ms 381.830 msOn different TATA/VSNL gateways:
115.113.128.17
59.163.206.45
59.163.201.149
59.163.206.181
Seems to be a problem with TATA/VSNL again!!
Lolz at 218.248.255.70
New VSNL gateway every now and then, surely a case of routing gone haywire.
Have to spend hours on phone explaining to BSNL people :yawn:
@x720, tracert please 🙂
115.113.128.17
Code:
3 8 ms 10 ms 11 ms 218.248.162.70 4 47 ms 45 ms 49 ms 218.248.255.26 5 402 ms 405 ms 403 ms 115.113.128.17.static-mumbai.vsnl.net.in [115.113.128.17] 6 376 ms 457 ms 367 ms 121.240.1.46 7 368 ms 369 ms 367 ms 72.14.233.204 8 369 ms 367 ms 367 ms 209.85.240.145 9 367 ms 367 ms 367 ms maa03s16-in-f6.1e100.net [74.125.236.166]
Code:
3 8 ms 9 ms 9 ms 218.248.162.74 4 304 ms 303 ms 303 ms 218.248.255.70 5 370 ms * 369 ms 59.163.206.45.static.chennai.vsnl.net.in [59.163.206.45] 6 * * 367 ms 121.240.1.46 7 369 ms 367 ms * 72.14.233.204 8 370 ms * 367 ms 209.85.240.145 9 365 ms 367 ms 365 ms maa03s16-in-f3.1e100.net [74.125.236.163]
Code:
3 10 ms 9 ms 18 ms 218.248.162.74 4 296 ms 297 ms 297 ms 218.248.255.70 5 362 ms 361 ms * 59.163.201.149.static.chennai.vsnl.net.in [59.163.201.149] 6 365 ms 365 ms 365 ms 121.240.1.50 7 365 ms 365 ms 365 ms 72.14.233.204 8 365 ms 363 ms 363 ms 209.85.240.145 9 366 ms 365 ms 365 ms maa03s16-in-f1.1e100.net [74.125.236.161]
Code:
3 10 ms 9 ms 9 ms 218.248.162.70 4 61 ms 59 ms 59 ms 218.248.255.22 5 419 ms * 419 ms 59.163.206.181.static.chennai.vsnl.net.in [59.163.206.181] 6 * 396 ms 399 ms 121.240.1.46 7 396 ms 395 ms 397 ms 72.14.233.204 8 402 ms * 382 ms 209.85.240.145 9 399 ms 395 ms 397 ms maa03s16-in-f14.1e100.net [74.125.236.174]Seems to be a problem with TATA/VSNL again!!
Lolz at 218.248.255.70
New VSNL gateway every now and then, surely a case of routing gone haywire.
Have to spend hours on phone explaining to BSNL people :yawn:
@x720, tracert please 🙂
mgcarley
Founder, Hayai Broadband
We've been over this in at least 2 other threads: it's not a Tata issue, it's a capacity issue. These links are way oversubscribed.
See https://broadband.forum/bsnl-broadband/76312-bsnl-broadband-routing-issue-high/3/#post602468 (the images in these posts are real-time, not static, so these are current).
Reversing the traceroute in your direction, I get:
Trace #1
Reply from 218.248.162.70: bytes=32 time=337ms TTL=244Reply from 218.248.255.26: bytes=32 time=62ms TTL=244Reply from 115.113.128.17: bytes=32 time=4ms TTL=58
(to force the same route, I'm having to ping each IP individually - I'm also posting hops in the same order as your trace appears, so these ping times descend from worst to best... using hops #3,4,5 to illustrate the point).
Trace #2
Trace #3
Trace #4
It appears that there are switches and/or routers in between your hop #3 & #4 that are way oversubscribed, working way too hard and causing huge performance issues.
----------
Peering is unregulated except at NIXI isn't it? Or is peering between two private companies regulated too?
That depends what you mean by "regulated" - it's all covered in the same license agreement. Any licensed ISP is free to privately peer with any other licensed ISP without going through NIXI.
The idea behind NIXI is that it should be a single point (with redundant backups all over the country, of course) where licensed ISPs can freely trade traffic at a single location to maximize efficiency.
Unfortunately, nobody has quite "got it" and NIXI isn't doing what it should be, so you have a massive hodgepodge of ISP A peers with ISP C but not ISP B, so the route to ISP B from ISP A goes through ISP D and so on.
What's happening here, however, is not related to peering, it's that BSNL purchases part of it's links to the outside world from Tata, arguably the best of the wholesale providers in India. But, either it's not purchasing enough and running it's links "too hot" (over the 80% average load that it's supposed to limit itself to per the regulations) or it's running equipment that desperately needs upgrading... there could be some switch in some data center that's a 100mbit/s switch but it should be gigabit, or maybe an interface is malfunctioning and dropping packets or maybe they just need to add more core routers in that particular facility - who knows - but it always seems to be problems in the north and east part of the country when BSNL routes through Chennai that we see this sort of thing happening far more frequently than it should.
----------
Maybe BSNL needs to start thinking about maybe peering directly with Google and some others to fix some of it's issues.
Can someone try a trace to say, rcom.co.in, att.com, cw.com or inteliquent.com
See https://broadband.forum/bsnl-broadband/76312-bsnl-broadband-routing-issue-high/3/#post602468 (the images in these posts are real-time, not static, so these are current).
Reversing the traceroute in your direction, I get:
Trace #1
Reply from 218.248.162.70: bytes=32 time=337ms TTL=244Reply from 218.248.255.26: bytes=32 time=62ms TTL=244Reply from 115.113.128.17: bytes=32 time=4ms TTL=58
(to force the same route, I'm having to ping each IP individually - I'm also posting hops in the same order as your trace appears, so these ping times descend from worst to best... using hops #3,4,5 to illustrate the point).
Trace #2
Code:
Reply from 218.248.162.74: bytes=32 time=411ms TTL=244Reply from 218.248.255.70: bytes=32 time=51ms TTL=247Reply from 59.163.206.45: bytes=32 time=30ms TTL=57
Code:
Reply from 218.248.162.74: bytes=32 time=411ms TTL=244Reply from 218.248.255.70: bytes=32 time=51ms TTL=247Reply from 59.163.201.149: bytes=32 time=29ms TTL=56
Code:
Reply from 218.248.162.70: bytes=32 time=359ms TTL=244Reply from 218.248.255.22: bytes=32 time=73ms TTL=244Reply from 59.163.206.181: bytes=32 time=34ms TTL=57----------
Peering is unregulated except at NIXI isn't it? Or is peering between two private companies regulated too?
That depends what you mean by "regulated" - it's all covered in the same license agreement. Any licensed ISP is free to privately peer with any other licensed ISP without going through NIXI.
The idea behind NIXI is that it should be a single point (with redundant backups all over the country, of course) where licensed ISPs can freely trade traffic at a single location to maximize efficiency.
Unfortunately, nobody has quite "got it" and NIXI isn't doing what it should be, so you have a massive hodgepodge of ISP A peers with ISP C but not ISP B, so the route to ISP B from ISP A goes through ISP D and so on.
What's happening here, however, is not related to peering, it's that BSNL purchases part of it's links to the outside world from Tata, arguably the best of the wholesale providers in India. But, either it's not purchasing enough and running it's links "too hot" (over the 80% average load that it's supposed to limit itself to per the regulations) or it's running equipment that desperately needs upgrading... there could be some switch in some data center that's a 100mbit/s switch but it should be gigabit, or maybe an interface is malfunctioning and dropping packets or maybe they just need to add more core routers in that particular facility - who knows - but it always seems to be problems in the north and east part of the country when BSNL routes through Chennai that we see this sort of thing happening far more frequently than it should.
----------
Maybe BSNL needs to start thinking about maybe peering directly with Google and some others to fix some of it's issues.
Can someone try a trace to say, rcom.co.in, att.com, cw.com or inteliquent.com
Hmm,
218.248.162.70
218.248.255.10
218.248.x.x
are having trouble reaching TATA then? congested/overloaded/malfunctioning, right?
Code:
3 10 ms 9 ms 9 ms 218.248.162.70 4 253 ms 253 ms 253 ms 218.248.255.10 5 618 ms 637 ms * 59.163.206.181.static.chennai.vsnl.net.in [59.163.206.181] 6 618 ms 617 ms 617 ms 59.163.206.181.static.chennai.vsnl.net.in [59.163.206.181]218.248.255.10
218.248.x.x
are having trouble reaching TATA then? congested/overloaded/malfunctioning, right?
mgcarley
Founder, Hayai Broadband
are having trouble reaching TATA then? congested/overloaded/malfunctioning, right?
He says, not having read my previous post.
He says, not having read my previous post.
Code:
Pinging 59.163.206.181 with 32 bytes of data:Reply from 59.163.206.181: bytes=32 time=34ms TTL=57Reply from 59.163.206.181: bytes=32 time=32ms TTL=57Reply from 59.163.206.181: bytes=32 time=35ms TTL=57Reply from 59.163.206.181: bytes=32 time=34ms TTL=57Pinging 218.248.255.10 with 32 bytes of data:Reply from 218.248.255.10: bytes=32 time=78ms TTL=244Reply from 218.248.255.10: bytes=32 time=79ms TTL=244Reply from 218.248.255.10: bytes=32 time=78ms TTL=244Reply from 218.248.255.10: bytes=32 time=78ms TTL=244Pinging 218.248.162.70 with 32 bytes of data:Reply from 218.248.162.70: bytes=32 time=57ms TTL=244Reply from 218.248.162.70: bytes=32 time=56ms TTL=244Reply from 218.248.162.70: bytes=32 time=56ms TTL=244Reply from 218.248.162.70: bytes=32 time=57ms TTL=244mgcarley = Mr. Know-it-all/ Mr. High and Mighty/ The Veritable Windbag From now on, your posts will be like the Bible to me... I'll read them day and night, lest I anger you, my Lord. I observed your avatar closely, think I spotted a halo!I shudder to think where we, the poor Indian chumps, would've been, if you had not chosen to grace our shores with your divine presence !!!!!I can't thank you enough for shining the light on us. I am overwhelmed with your sheer genius, I am a fan, nay, a follower !!!!!Btw, you might want to tone it down a notch as you sound like a SUPER PRICK... No wonder people steer clear of you!
x720
Incoherent Poster
M05f3t 😛 . What do you want me to tracert to ?rcom.co.in is not pingable anymore.
mgcarley
Founder, Hayai Broadband
mgcarley = Mr. Know-it-all/ Mr. High and Mighty/ The Veritable Windbag
From now on, your posts will be like the Bible to me... I'll read them day and night, lest I anger you, my Lord. I observed your avatar closely, think I spotted a halo!
I shudder to think where we, the poor Indian chumps, would've been, if you had not chosen to grace our shores with your divine presence !!!!!
I can't thank you enough for shining the light on us. I am overwhelmed with your sheer genius, I am a fan, nay, a follower !!!!!
Unless you're seriously suggesting that everything in India is peachy, then please consider me aware of and having duly noted your sarcasm, but... where the hell did that come from? Based on what you wrote in your previous post it appeared that you hadn't gone over what was there.
I'm so sorry for trying to enlighten people on a subject which I happen to know one or two things about and attempting to provide enough diagnostic information so that *maybe* someone more involved with BSNL than myself will be able to get the problem resolved.
Either I'm right or I'm wrong that it's not a Tata problem but a BSNL problem (I've stated my case suggesting it's BSNL).
Btw, you might want to tone it down a notch as you sound like a SUPER PRICK...
I don't know what your problem is, but the personal attack is not really necessary. I'm not going to deny that I can be abrasive at times (even frequently) but if you have a problem with me, by all means, send me a PM and tell me about it - otherwise, this is a thread about a problem with BSNL broadband for which I was attempting to give a little insight on, and thus should stay on topic.
No wonder people steer clear of you!
Do they? Like who? I've not noticed anyone missing from my life.
----------------
So, anyone on BSNL in Kolkata or Chennai or somewhere got any traceroutes to the websites I asked for? rcom.co.in, att.com, cw.com or inteliquent.com
----------
rcom.co.in is not pingable anymore.
No, but it should get close enough that we can see if hops #3,4,5 are still playing up.
From now on, your posts will be like the Bible to me... I'll read them day and night, lest I anger you, my Lord. I observed your avatar closely, think I spotted a halo!
I shudder to think where we, the poor Indian chumps, would've been, if you had not chosen to grace our shores with your divine presence !!!!!
I can't thank you enough for shining the light on us. I am overwhelmed with your sheer genius, I am a fan, nay, a follower !!!!!
Unless you're seriously suggesting that everything in India is peachy, then please consider me aware of and having duly noted your sarcasm, but... where the hell did that come from? Based on what you wrote in your previous post it appeared that you hadn't gone over what was there.
I'm so sorry for trying to enlighten people on a subject which I happen to know one or two things about and attempting to provide enough diagnostic information so that *maybe* someone more involved with BSNL than myself will be able to get the problem resolved.
Either I'm right or I'm wrong that it's not a Tata problem but a BSNL problem (I've stated my case suggesting it's BSNL).
Btw, you might want to tone it down a notch as you sound like a SUPER PRICK...
I don't know what your problem is, but the personal attack is not really necessary. I'm not going to deny that I can be abrasive at times (even frequently) but if you have a problem with me, by all means, send me a PM and tell me about it - otherwise, this is a thread about a problem with BSNL broadband for which I was attempting to give a little insight on, and thus should stay on topic.
No wonder people steer clear of you!
Do they? Like who? I've not noticed anyone missing from my life.
----------------
So, anyone on BSNL in Kolkata or Chennai or somewhere got any traceroutes to the websites I asked for? rcom.co.in, att.com, cw.com or inteliquent.com
----------
rcom.co.in is not pingable anymore.
No, but it should get close enough that we can see if hops #3,4,5 are still playing up.
Hi , Mr sheldon cooper :disdain:
here u go. . . .
yes its u mg
----------
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\HOME>tracert AT&T | Cell Phones, U-verse, Digital TV, DSL Internet, and Phone Service
Tracing route to e2318.c.akamaiedge.net [118.215.225.145]
over a maximum of 30 hops:
1 10 ms 1 ms 1 ms 192.168.1.1
2 24 ms 24 ms 24 ms ********
3 23 ms 24 ms 24 ms 218.248.160.70
4 24 ms 24 ms 24 ms 218.248.255.66
5 31 ms 45 ms 32 ms 59.163.201.153.static.chennai.vsnl.net.in [59.16
3.201.153]
6 57 ms 58 ms 68 ms 172.31.19.149
7 58 ms 57 ms 56 ms 59.163.25.242.static.vsnl.net.in [59.163.25.242]
8 305 ms 323 ms 305 ms 59.163.52.29.static.vsnl.net.in [59.163.52.29]
9 304 ms 300 ms 303 ms ge-4-0-4-0.sngc3-cr2.ix.singtel.com [203.208.182
.77]
10 306 ms 328 ms 325 ms 203.208.153.110
11 319 ms 309 ms 319 ms a118-215.225-145.deploy.akamaitechnologies.com [
118.215.225.145]
Trace complete.
C:\Users\HOME>
----------
it s from bangalore
----------
----------
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\HOME>tracert Google
Tracing route to Google [74.125.236.82]
over a maximum of 30 hops:
1 6 ms 1 ms 1 ms 192.168.1.1
2 24 ms 23 ms 24 ms @@@@@@@
3 25 ms 24 ms 23 ms 218.248.160.70
4 25 ms 23 ms 24 ms 218.248.255.2
5 48 ms 47 ms 47 ms 218.248.246.130
6 55 ms 56 ms 55 ms 115.114.131.141.static-mumbai.vsnl.net.in [115.1
14.131.141]
7 84 ms 55 ms 54 ms 115.113.165.98.static-mumbai.vsnl.net.in [115.11
3.165.98]
8 64 ms 73 ms 63 ms 72.14.232.202
9 57 ms 56 ms 57 ms 72.14.232.100
10 65 ms 58 ms 56 ms 209.85.249.235
11 58 ms 64 ms 58 ms maa03s05-in-f18.1e100.net [74.125.236.82]
Trace complete.
here u go. . . .
yes its u mg
----------
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\HOME>tracert AT&T | Cell Phones, U-verse, Digital TV, DSL Internet, and Phone Service
Tracing route to e2318.c.akamaiedge.net [118.215.225.145]
over a maximum of 30 hops:
1 10 ms 1 ms 1 ms 192.168.1.1
2 24 ms 24 ms 24 ms ********
3 23 ms 24 ms 24 ms 218.248.160.70
4 24 ms 24 ms 24 ms 218.248.255.66
5 31 ms 45 ms 32 ms 59.163.201.153.static.chennai.vsnl.net.in [59.16
3.201.153]
6 57 ms 58 ms 68 ms 172.31.19.149
7 58 ms 57 ms 56 ms 59.163.25.242.static.vsnl.net.in [59.163.25.242]
8 305 ms 323 ms 305 ms 59.163.52.29.static.vsnl.net.in [59.163.52.29]
9 304 ms 300 ms 303 ms ge-4-0-4-0.sngc3-cr2.ix.singtel.com [203.208.182
.77]
10 306 ms 328 ms 325 ms 203.208.153.110
11 319 ms 309 ms 319 ms a118-215.225-145.deploy.akamaitechnologies.com [
118.215.225.145]
Trace complete.
C:\Users\HOME>
----------
it s from bangalore
----------
----------
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\HOME>tracert Google
Tracing route to Google [74.125.236.82]
over a maximum of 30 hops:
1 6 ms 1 ms 1 ms 192.168.1.1
2 24 ms 23 ms 24 ms @@@@@@@
3 25 ms 24 ms 23 ms 218.248.160.70
4 25 ms 23 ms 24 ms 218.248.255.2
5 48 ms 47 ms 47 ms 218.248.246.130
6 55 ms 56 ms 55 ms 115.114.131.141.static-mumbai.vsnl.net.in [115.1
14.131.141]
7 84 ms 55 ms 54 ms 115.113.165.98.static-mumbai.vsnl.net.in [115.11
3.165.98]
8 64 ms 73 ms 63 ms 72.14.232.202
9 57 ms 56 ms 57 ms 72.14.232.100
10 65 ms 58 ms 56 ms 209.85.249.235
11 58 ms 64 ms 58 ms maa03s05-in-f18.1e100.net [74.125.236.82]
Trace complete.
mgcarley
Founder, Hayai Broadband
Hi , Mr sheldon cooper
here u go. . . .
yes its u mg
...right. I don't see the resemblance for a myriad of reasons, but OK.
Tracing route to e2318.c.akamaiedge.net [118.215.225.145]
over a maximum of 30 hops:
1 10 ms 1 ms 1 ms 192.168.1.1
2 24 ms 24 ms 24 ms ********
3 23 ms 24 ms 24 ms 218.248.160.70
4 24 ms 24 ms 24 ms 218.248.255.66
5 31 ms 45 ms 32 ms 59.163.201.153.static.chennai.vsnl.net.in [59.16
3.201.153]
6 57 ms 58 ms 68 ms 172.31.19.149
7 58 ms 57 ms 56 ms 59.163.25.242.static.vsnl.net.in [59.163.25.242]
8 305 ms 323 ms 305 ms 59.163.52.29.static.vsnl.net.in [59.163.52.29]
9 304 ms 300 ms 303 ms ge-4-0-4-0.sngc3-cr2.ix.singtel.com [203.208.182
.77]
10 306 ms 328 ms 325 ms 203.208.153.110
11 319 ms 309 ms 319 ms a118-215.225-145.deploy.akamaitechnologies.com [
118.215.225.145]
Damn, not really what I was hoping for. Forgot that AT&T's website is delivered by Akamai, so that trace is entirely irrelevant... try route-server.ip.att.net instead.
here u go. . . .
yes its u mg
...right. I don't see the resemblance for a myriad of reasons, but OK.
Tracing route to e2318.c.akamaiedge.net [118.215.225.145]
over a maximum of 30 hops:
1 10 ms 1 ms 1 ms 192.168.1.1
2 24 ms 24 ms 24 ms ********
3 23 ms 24 ms 24 ms 218.248.160.70
4 24 ms 24 ms 24 ms 218.248.255.66
5 31 ms 45 ms 32 ms 59.163.201.153.static.chennai.vsnl.net.in [59.16
3.201.153]
6 57 ms 58 ms 68 ms 172.31.19.149
7 58 ms 57 ms 56 ms 59.163.25.242.static.vsnl.net.in [59.163.25.242]
8 305 ms 323 ms 305 ms 59.163.52.29.static.vsnl.net.in [59.163.52.29]
9 304 ms 300 ms 303 ms ge-4-0-4-0.sngc3-cr2.ix.singtel.com [203.208.182
.77]
10 306 ms 328 ms 325 ms 203.208.153.110
11 319 ms 309 ms 319 ms a118-215.225-145.deploy.akamaitechnologies.com [
118.215.225.145]
Damn, not really what I was hoping for. Forgot that AT&T's website is delivered by Akamai, so that trace is entirely irrelevant... try route-server.ip.att.net instead.