MTNL Mumbai MTNL Throttling speed or just overload of infrastructure

[Sushubh]

for screen recording, try out sharex. it works great for me. i have used jing in the past and i never really could get used to it. sharex is wonderful.

 

[panzer008]

@FireSword

I use Greenshot to capture screenshots......

For Video use Sharex as @chromaniac suggested

 

[FireSword]

@FireSword
I use Greenshot to capture screenshots......

For Video use Sharex as @chromaniac suggested

@panzer008
@Satyajeet
I think I'm not communicating properly. My question is, HOW to get timeout/packetloss proof? What site, or software or utility or command to get this proof?
Thanks for the tips on image and video recording softwares anyways, will need them I guess

 

[x720]

Ping Google or whatever server on which you're facing packet loss?

ping google.com -t

 

[FireSword]

Thanks for the reply.

I dont see any packet loss on google though, what server should use? What did you guys use for the emails?

 

[x720]

Ping the game server on which you're facing issues and post the result here.

I'd complain on PGPortal explicitly asking for a port change to SOTL/Huawei or Alcatel. If you want to send an email, @Satyajeet or @panzer008 should be able to help.

 

[FireSword]

Yes, since the lag time for today is over, I will do so tomorrow. Some help regarding how to phrase the email and how much proof to attach will be very helpful.

 

[FireSword]

Pingtest during working hours above
Pingtest after 7 pm below

 

[x720]

Pinging 216.12.203.92 with 32 bytes of data:
Reply from 216.12.203.92: bytes=32 time=92ms TTL=51
Reply from 216.12.203.92: bytes=32 time=92ms TTL=51
Reply from 216.12.203.92: bytes=32 time=91ms TTL=51
Reply from 216.12.203.92: bytes=32 time=92ms TTL=51
Reply from 216.12.203.92: bytes=32 time=92ms TTL=51
Reply from 216.12.203.92: bytes=32 time=92ms TTL=51
Reply from 216.12.203.92: bytes=32 time=93ms TTL=51
Reply from 216.12.203.92: bytes=32 time=92ms TTL=51
Reply from 216.12.203.92: bytes=32 time=92ms TTL=51
Reply from 216.12.203.92: bytes=32 time=91ms TTL=51
Reply from 216.12.203.92: bytes=32 time=92ms TTL=51
Reply from 216.12.203.92: bytes=32 time=92ms TTL=51
Reply from 216.12.203.92: bytes=32 time=92ms TTL=51
Reply from 216.12.203.92: bytes=32 time=92ms TTL=51
Reply from 216.12.203.92: bytes=32 time=92ms TTL=51
Reply from 216.12.203.92: bytes=32 time=92ms TTL=51

Tracing route to 216.12.203.92-static.reverse.softlayer.com [216.12.203.92]
over a maximum of 30 hops:

  1     1 ms     3 ms     1 ms  www.asusnetwork.net [192.168.2.1]
  2     2 ms     1 ms     2 ms  ADSL [192.168.1.1]
  3     7 ms     8 ms     7 ms  static-mum-59.185.4.41.mtnl.net.in [59.185.4.41]
  4    12 ms     8 ms     7 ms  static-mum-59.185.211.229.mtnl.net.in [59.185.211.229]
  5    96 ms    97 ms    99 ms  115.248.150.70
  6     *        *        *     Request timed out.
  7    32 ms    32 ms    31 ms  62.216.145.229
  8    91 ms    63 ms    90 ms  xe-1-0-4.0.cjr01.sin001.flagtel.com [62.216.129.157]
  9    91 ms    90 ms    91 ms  36351.sgw.equinix.com [202.79.197.69]
10    92 ms    91 ms    90 ms  ae5.dar01.sr03.sng01.networklayer.com [50.97.18.197]
11    92 ms     *      143 ms  ae5.dar01.sr03.sng01.networklayer.com [50.97.18.197]
12     *       91 ms     *     216.12.203.92-static.reverse.softlayer.com [216.12.203.92]
13    93 ms    92 ms    92 ms  216.12.203.92-static.reverse.softlayer.com [216.12.203.92]

Trace complete.

Post your tracert too during the issue hours.

 

[panzer008]

@x720
which router are you using? Modem is different unit?