MTNL Mumbai Routing problems on MTNL Broadband?

  • Thread starter Thread starter sandeep410
  • Start date Start date
  • Replies Replies 59
  • Views Views 13,357
@chromaniac
Any recommendations on which VPN to use to get around this routing issues?

I have been using HotSpot Shield & CyberGhost 5..... but both cant get me around this routing issues......

I need a VPN to reroute my traffic from India before it leaves the country.....
 
I guess you need to find a VPN that is not on the fucked up routes :|
 
panzer008 said:
So just when Reliance fixed the cable cut...... and everything returned back to normal.... MTNL thinks, now its time to switch routing...... to TATA......at least on my Alcatel port 182.59.x.x

EU ping almost 70-80ms higher than normal.....

Code: 
tracert 141.136.100.50

Tracing route to riot-games-gw.ip4.gtt.net [141.136.100.50]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2     9 ms     8 ms     9 ms  static-mum-182.59.128.1.mtnl.net.in [182.59.128.1]
  3     9 ms     8 ms     9 ms  static-mum-59.185.212.50.mtnl.net.in [59.185.212.50]
  4     9 ms     8 ms     8 ms  static-mum-59.185.210.198.mtnl.net.in [59.185.210.198]
  5    64 ms    81 ms    64 ms  121.244.47.193     ***TATA***
  6     *        *        *     Request timed out.
  7    71 ms    71 ms    71 ms  ix-0-100.tcore1.MLV-Mumbai.as6453.net [180.87.38.5]
  8   208 ms   210 ms   210 ms  if-9-5.tcore1.WYN-Marseille.as6453.net [80.231.217.17]
  9   219 ms   212 ms   209 ms  if-8-1600.tcore1.PYE-Paris.as6453.net [80.231.217.6]
10   211 ms   219 ms   217 ms  if-2-2.tcore1.PVU-Paris.as6453.net [80.231.154.17]
11   220 ms   216 ms   217 ms  80.231.153.202
12   235 ms   235 ms   235 ms  et-2-1-0.ams12.ip4.gtt.net [141.136.105.237]
13   230 ms   227 ms   229 ms  riot-games-gw.ip4.gtt.net [141.136.100.50]

Trace complete.

Ericsson.... SOTL.... any routing change??
Click to expand...

Mine is SOTL 120.62.XX.XX Range

Code: 
C:\Windows\system32>tracert 141.136.100.50

Tracing route to riot-games-gw.ip4.gtt.net [141.136.100.50]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  router.asus.com [100.100.100.1]
  2     *        *        *     Request timed out.
  3     7 ms     7 ms     7 ms  static-mum-59.185.211.221.mtnl.net.in [59.185.211.221]
  4     7 ms     7 ms     7 ms  static-mum-59.185.211.222.mtnl.net.in [59.185.211.222]
  5     8 ms     8 ms     8 ms  121.244.47.189
  6     7 ms     7 ms     6 ms  ix-0-100.tcore1.MLV-Mumbai.as6453.net [180.87.38.5]
  7   125 ms   124 ms   124 ms  if-9-5.tcore1.WYN-Marseille.as6453.net [80.231.217.17]
  8   128 ms   126 ms   126 ms  if-8-1600.tcore1.PYE-Paris.as6453.net [80.231.217.6]
  9   126 ms   126 ms   126 ms  if-2-2.tcore1.PVU-Paris.as6453.net [80.231.154.17]
10   123 ms   124 ms   122 ms  80.231.153.202
11   133 ms   133 ms   133 ms  et-2-1-0.ams12.ip4.gtt.net [141.136.105.237]
12   133 ms   133 ms   132 ms  riot-games-gw.ip4.gtt.net [141.136.100.50]

Trace complete.
 
Code: 
tracert 141.136.100.50

Tracing route to riot-games-gw.ip4.gtt.net [141.136.100.50]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2     9 ms     8 ms     9 ms  static-mum-182.59.128.1.mtnl.net.in [182.59.128.1]
  3     9 ms     9 ms     8 ms  static-mum-59.185.212.50.mtnl.net.in [59.185.212.50]
  4     8 ms     8 ms     8 ms  static-mum-59.185.210.50.mtnl.net.in [59.185.210.50]
  5     *      145 ms     *     121.244.47.189
  6   154 ms     *      153 ms  ix-0-100.tcore1.MLV-Mumbai.as6453.net [180.87.38.5]
  7     *      291 ms   291 ms  if-9-5.tcore1.WYN-Marseille.as6453.net [80.231.217.17]
  8     *        *        *     Request timed out.
  9   226 ms   225 ms   227 ms  if-2-2.tcore1.PVU-Paris.as6453.net [80.231.154.17]
 10   224 ms   224 ms   224 ms  80.231.153.202
 11   250 ms   250 ms   250 ms  et-2-1-0.ams12.ip4.gtt.net [141.136.105.237]
 12   283 ms   283 ms   283 ms  riot-games-gw.ip4.gtt.net [141.136.100.50]

Trace complete.

So link from MTNL to TATA is the culprit on my line...... hopefully they fix it...
 
Code: 
tracert 141.136.100.50

Tracing route to riot-games-gw.ip4.gtt.net [141.136.100.50]
over a maximum of 30 hops:

  1    15 ms    15 ms    16 ms  10.8.0.1
  2    16 ms    17 ms    16 ms  103.250.184.62
  3    16 ms    16 ms    15 ms  103.224.243.1
  4     *        *        *     Request timed out.
  5    83 ms    84 ms    83 ms  62.216.147.45
  6   207 ms   207 ms   208 ms  xe-0-0-0.0.pjr03.ldn001.flagtel.com [85.95.26.238]
  7   146 ms   146 ms   146 ms  ae2-230.lon10.ip4.gtt.net [46.33.95.165]
  8   152 ms   152 ms   151 ms  xe-1-2-4.ams12.ip4.gtt.net [89.149.180.141]
  9   154 ms   153 ms   152 ms  riot-games-gw.ip4.gtt.net [141.136.100.50]

Trace complete.

Now using ZenVPN (Free)....... reduced ping by 120ms.....

It has a Pune server....

Phew..... things we have to do when MTNL fucks up.......
 

Yesterday I was probably routed through Mars:rock:....... Today back on Earth..... :party:

ubzkJrg.png
1er2uuZ.png
 
Ho gaya slow. I mean, the download speeds are not going above 200 kBps.

In torrents, it is not connecting to any peers.

So it is confirmed, whenever MTNL senses some traffic problem, they first throttle torrents.

But PIA SG is giving full 8 Mbps. :D

FU MTNL>
 

Similar threads

D
Routing problems on Reliance Jio leading to slow loading websites
Replies
2
Views
2,989
dexterseo01
Sushubh
  • Locked
Routing Problems on Reliance Broadband?
6 7 8 9 10
Replies
97
Views
14,264
digitized
F
BSNL Broadband routing problem seems to have been resolved
2 3 4 5
Replies
47
Views
17,630
probuddha
A
problems with mtnl fttc.
2
Replies
15
Views
10,764
adI-torrentesness
Back