MTNL Mumbai Routing problems on MTNL Broadband?

[panzer008]

They've switched to TATA, which is having its own issues :speechless:

Alcatel is still going through Reliance routing....

tracert riot.nl

Tracing route to riot.nl [213.136.12.232]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2     9 ms     9 ms     9 ms  static-mum-182.59.128.1.mtnl.net.in [182.59.128.1]
  3     9 ms     8 ms     8 ms  static-mum-59.185.212.50.mtnl.net.in [59.185.212.50]
  4     9 ms     9 ms     9 ms  static-mum-59.185.210.198.mtnl.net.in [59.185.210.198]
  5     *        *        *     Request timed out.
  6     *      106 ms   106 ms  62.216.147.45
  7   251 ms   262 ms   250 ms  xe-0-0-0.0.pjr03.ldn001.flagtel.com [85.95.26.238]
  8     *      250 ms   251 ms  linx-2602.ge-0-0-0.jun1.thn.network.bit.nl [195.66.237.51]
  9   266 ms     *      268 ms  806.xe-0-0-0.jun1.bit-2a.network.bit.nl [213.136.1.109]
 10   263 ms   264 ms   263 ms  http-linux.lb.network.bit.nl [213.136.12.232]

Trace complete.

 

[d5aqoëp]

SOTL is also going through Reliance (Flagtel)

C:\Windows\system32>tracert riot.nl

Tracing route to riot.nl [213.136.12.232]
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     8 ms     7 ms     7 ms  static-mum-59.185.211.253.mtnl.net.in [59.185.211.253]
  4     7 ms     8 ms     8 ms  static-mum-59.185.211.254.mtnl.net.in [59.185.211.254]
  5     *        *        *     Request timed out.
  6   108 ms   109 ms   107 ms  62.216.147.73
  7   253 ms   252 ms   251 ms  xe-0-0-0.0.pjr03.ldn001.flagtel.com [85.95.26.238]
  8     *      254 ms     *     linx-2602.ge-0-0-0.jun1.thn.network.bit.nl [195.66.237.51]
  9   270 ms   268 ms   269 ms  806.xe-0-0-0.jun1.bit-2a.network.bit.nl [213.136.1.109]
10     *      274 ms   274 ms  http-linux.lb.network.bit.nl [213.136.12.232]

Trace complete.

This is at my home.

 

[max8084]

They've switched to TATA, which is having its own issues :speechless:

How did you came to know about this?

riot.nl loading very very slow, almost took 3-4 minutes.

Tracing route to riot.nl [213.136.12.232]
over a maximum of 30 hops:

1 2 ms 1 ms 2 ms 192.168.1.1
2 * * * Request timed out.
3 15 ms 16 ms 15 ms static-mum-59.185.211.205.mtnl.net.in [59.185.21
1.205]
4 15 ms 15 ms 15 ms static-mum-59.185.211.206.mtnl.net.in [59.185.21
1.206]
5 * * * Request timed out.
6 123 ms 120 ms 120 ms 62.216.147.45
7 268 ms 263 ms 266 ms xe-0-0-0.0.pjr03.ldn001.flagtel.com [85.95.26.23
8]
8 271 ms 270 ms 267 ms linx-2602.ge-0-0-0.jun1.thn.network.bit.nl [195.
66.237.51]
9 280 ms 279 ms 280 ms 806.xe-0-0-0.jun1.bit-2a.network.bit.nl [213.136
.1.109]
10 283 ms 281 ms 281 ms http-linux.lb.network.bit.nl [213.136.12.232]

Trace complete.

 

[d5aqoëp]

Now at my office which is on SOTL static IP series 120.63.xx.xx

Internet is working flawlessly. No throttling on any torrents and I am getting full 8 Mbps even at 6:40 PM.
see here

Look at the tracert. Pings at flagtel are higer but in the end they again reduce.

C:\Windows\system32>tracert riot.nl

Tracing route to riot.nl [213.136.12.232]
over a maximum of 30 hops:

  1     2 ms     1 ms     1 ms  192.168.1.1
  2     *        *        *     Request timed out.
  3    49 ms     9 ms     9 ms  static-mum-59.185.211.253.mtnl.net.in [59.185.211.253]
  4     9 ms     9 ms     8 ms  static-mum-59.185.211.254.mtnl.net.in [59.185.211.254]
  5     *        *        *     Request timed out.
  6    78 ms    78 ms    78 ms  62.216.147.73
  7   210 ms   209 ms   209 ms  xe-0-0-0.0.pjr03.ldn001.flagtel.com [85.95.26.238]
  8   133 ms   134 ms   133 ms  linx-2602.ge-0-0-0.jun1.thn.network.bit.nl [195.66.237.51]
  9   214 ms   213 ms   215 ms  806.xe-0-0-0.jun1.bit-2a.network.bit.nl [213.136.1.109]
  10   216 ms   216 ms   225 ms  riot.nl [213.136.12.232]

Trace complete.

They are treating business customers with static IP with priority.

 

[panzer008]

Something has improved..... Reliance is probably fixing the cable.......

No timeouts..... No packet loss..... Websites are opening quickly.....

Ping Riot.nl

ping riot.nl

Reply from 213.136.12.232: bytes=32 time=212ms TTL=239
Reply from 213.136.12.232: bytes=32 time=210ms TTL=239
Reply from 213.136.12.232: bytes=32 time=210ms TTL=239
Reply from 213.136.12.232: bytes=32 time=210ms TTL=239
Reply from 213.136.12.232: bytes=32 time=210ms TTL=239
Reply from 213.136.12.232: bytes=32 time=210ms TTL=239
Reply from 213.136.12.232: bytes=32 time=210ms TTL=239
Reply from 213.136.12.232: bytes=32 time=210ms TTL=239
Reply from 213.136.12.232: bytes=32 time=211ms TTL=239
Reply from 213.136.12.232: bytes=32 time=211ms TTL=239
Reply from 213.136.12.232: bytes=32 time=211ms TTL=239
Reply from 213.136.12.232: bytes=32 time=212ms TTL=239
Reply from 213.136.12.232: bytes=32 time=209ms TTL=239
Reply from 213.136.12.232: bytes=32 time=210ms TTL=239
Reply from 213.136.12.232: bytes=32 time=210ms TTL=239
Reply from 213.136.12.232: bytes=32 time=210ms TTL=239
Reply from 213.136.12.232: bytes=32 time=210ms TTL=239
Reply from 213.136.12.232: bytes=32 time=210ms TTL=239
Reply from 213.136.12.232: bytes=32 time=210ms TTL=239
Reply from 213.136.12.232: bytes=32 time=210ms TTL=239
Reply from 213.136.12.232: bytes=32 time=210ms TTL=239

Still Reliance Route.....

tracert riot.nl

Tracing route to riot.nl [213.136.12.232]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2     *       46 ms    21 ms  static-mum-182.59.128.1.mtnl.net.in [182.59.128.1]
  3     9 ms     9 ms     9 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.198.mtnl.net.in [59.185.210.198]
  5     *        *        *     Request timed out.
  6    74 ms    74 ms    73 ms  62.216.147.45
  7   210 ms   219 ms   211 ms  xe-0-1-1.0.pjr03.ldn001.flagtel.com [85.95.26.233]
  8   134 ms   134 ms   134 ms  linx-2602.ge-0-0-0.jun1.thn.network.bit.nl [195.66.237.51]
  9   215 ms   214 ms   213 ms  805.xe-0-0-0.jun1.bit-1.network.bit.nl [213.136.1.105]
 10   211 ms   212 ms   210 ms  http-linux.lb.network.bit.nl [213.136.12.232]

Trace complete.

 

[Mr.cool]

Just rebooted the modem and now no internet -.- from past 2 hour . DSL stable but no internet light , any one else facing this issue ??

 

[Raju ram din]

DSL stable but no internet light , any one else facing this issue ??

This seems to be odd. Can you check modem logs and see if any crc errors are happening. Also if possiable can you post logs here?

 

[Mr.cool]

Crc error is 6 and hec error is 3.
This thing happens many times but it gets resolved on its own in less that 15 minutes. But today its still not resolved even after 3 hours .
Line stats
Attenuation 170
SNt 81
Attainable rate 6404 kbps.

 

[Raju ram din]

This is definately odd....the snr and atten doesnt seems to be correct. Please recheck. Also, if these are correct, then i think your has a leak or two pairs are joined at peer box to make 1 pair for your connection. It happenes generally when line man doesnt get a loopback and then he tries to find a free pair with same isssue and jumper them together at exchange cron to make one pair. The problem with this is, at time if by mistake someone jumpered the second wire too and as the pair was in leak status, false dsl pusle is generated and modem thinks i am negotiated. Till that pulse remains, the modem stays in that session and then try to renegotiate.

To resolve this, ask mtnl guy to change you pair ...and to convince him, take multimetere with you, ask for a loop and connect both probe of multimeter to the end of wire and take resistance reading. Ideally it should be upto 1ohms for every 100-150mtrs of twisted wire. And generally with mtnl it should not be more than 60-65 till your house. Anything less than 50 is great. You should also check voltage, it should be near to -50v dc, anything lesser than this would create issues, anything above this will fry your phone and modem .

 

[amish]

Looks like issue is resolved.

Atleast right now I am getting 1mbps!