Server lagging badly and gettting dced

Anything and everything!
Post Reply
Amphora
Posts: 6
Joined: Thu May 30, 2013 5:39 pm
Class: Mage
Town: Quanato

Server lagging badly and gettting dced

Post by Amphora »

hello players and gms .. the server is lagging i am pinging to a3server its gving timeput whereas yahoo going good
Attachments
ping.JPG
ping.JPG (127.13 KiB) Viewed 3818 times
ping.JPG
ping.JPG (127.13 KiB) Viewed 3818 times
Top
User avatar
Gmstorm
A3 Gamemaster
Posts: 1829
Joined: Fri Jun 08, 2007 12:27 am
Class: Mage
Town: Temoz
Location: Redyan
Contact:
Contact Gmstorm

Re: Server lagging badly and gettting dced

Post by Gmstorm »

Could you please provide us with the name of your Internet Service Provider so that we can diagnose the issue?
[GM]Storm
Top
Borninsane
Posts: 23
Joined: Sat Feb 08, 2014 1:35 pm
Class: Archer
Town: Temoz

Re: Server lagging badly and gettting dced

Post by Borninsane »

Sir i am having the same issue since 3-4 days only, i never had this pings fluctuation since years with my service provider and server as well even during hyderabad flooding time. I already discussed with my act fibernet technicians they already came to my house and checked the wiring, cmd reports and everything else they could from their side, everything is NEAT!
Only when i ping to services.a3india.com i get packet loss maximum 6% minimum 2%, still its an issue i used to have 15ms constant pin and rarely it goes up to 31 ms. If its at least little convenient with that packetloss i wouldnt be even writing this post here, in the morning time its normal like it was usually, 0% packet loss and constant 15ms ping, in-game lag starts from afternoon and then i get 4-5% packetloss, i have been checking cmd reports since 3-4days. I am sending one of my cmd report.txt please check once, server is also hosted from hyderabad ACT office right, so please try to communicate with them to know whats the issue or if you could fix it from your end. I tried everything from my side im just relying on you guys now :| Kindly reply with whatever solutions you have, i have done a full scan on my laptop as well, i use windows 10 and no threats at all, i did because sometimes malware also affects ping and packet loss. So whatever it is its up to you now :(

Pinging a3india.com [202.53.11.53] with 32 bytes of data:
Reply from 202.53.11.53: bytes=32 time=28ms TTL=56
Reply from 202.53.11.53: bytes=32 time=28ms TTL=56
Reply from 202.53.11.53: bytes=32 time=30ms TTL=56
Reply from 202.53.11.53: bytes=32 time=29ms TTL=56
Reply from 202.53.11.53: bytes=32 time=27ms TTL=56
Reply from 202.53.11.53: bytes=32 time=30ms TTL=56
Reply from 202.53.11.53: bytes=32 time=28ms TTL=56
Reply from 202.53.11.53: bytes=32 time=49ms TTL=56
Reply from 202.53.11.53: bytes=32 time=27ms TTL=56
Reply from 202.53.11.53: bytes=32 time=28ms TTL=56
Reply from 202.53.11.53: bytes=32 time=28ms TTL=56
Reply from 202.53.11.53: bytes=32 time=27ms TTL=56
Reply from 202.53.11.53: bytes=32 time=29ms TTL=56
Request timed out.
Reply from 202.53.11.53: bytes=32 time=28ms TTL=56
Request timed out.
Reply from 202.53.11.53: bytes=32 time=27ms TTL=56
Reply from 202.53.11.53: bytes=32 time=65ms TTL=56
Reply from 202.53.11.53: bytes=32 time=30ms TTL=56
Reply from 202.53.11.53: bytes=32 time=76ms TTL=56
Reply from 202.53.11.53: bytes=32 time=28ms TTL=56
Reply from 202.53.11.53: bytes=32 time=27ms TTL=56
Reply from 202.53.11.53: bytes=32 time=111ms TTL=56
Reply from 202.53.11.53: bytes=32 time=27ms TTL=56
Reply from 202.53.11.53: bytes=32 time=36ms TTL=56
Reply from 202.53.11.53: bytes=32 time=28ms TTL=56
Reply from 202.53.11.53: bytes=32 time=29ms TTL=56
Reply from 202.53.11.53: bytes=32 time=42ms TTL=56
Reply from 202.53.11.53: bytes=32 time=28ms TTL=56
Reply from 202.53.11.53: bytes=32 time=38ms TTL=56
Reply from 202.53.11.53: bytes=32 time=28ms TTL=56
Reply from 202.53.11.53: bytes=32 time=30ms TTL=56
Reply from 202.53.11.53: bytes=32 time=36ms TTL=56
Reply from 202.53.11.53: bytes=32 time=29ms TTL=56
Reply from 202.53.11.53: bytes=32 time=27ms TTL=56
Reply from 202.53.11.53: bytes=32 time=28ms TTL=56
Reply from 202.53.11.53: bytes=32 time=28ms TTL=56
Request timed out.
Reply from 202.53.11.53: bytes=32 time=28ms TTL=56
Reply from 202.53.11.53: bytes=32 time=61ms TTL=56
Reply from 202.53.11.53: bytes=32 time=27ms TTL=56
Reply from 202.53.11.53: bytes=32 time=39ms TTL=56
Reply from 202.53.11.53: bytes=32 time=27ms TTL=56
Reply from 202.53.11.53: bytes=32 time=28ms TTL=56
Reply from 202.53.11.53: bytes=32 time=31ms TTL=56
Reply from 202.53.11.53: bytes=32 time=28ms TTL=56
Reply from 202.53.11.53: bytes=32 time=28ms TTL=56
Reply from 202.53.11.53: bytes=32 time=29ms TTL=56
Reply from 202.53.11.53: bytes=32 time=28ms TTL=56
Reply from 202.53.11.53: bytes=32 time=27ms TTL=56
Reply from 202.53.11.53: bytes=32 time=33ms TTL=56
Reply from 202.53.11.53: bytes=32 time=27ms TTL=56
Reply from 202.53.11.53: bytes=32 time=27ms TTL=56
Reply from 202.53.11.53: bytes=32 time=27ms TTL=56
Reply from 202.53.11.53: bytes=32 time=29ms TTL=56
Reply from 202.53.11.53: bytes=32 time=27ms TTL=56
Reply from 202.53.11.53: bytes=32 time=28ms TTL=56
Reply from 202.53.11.53: bytes=32 time=27ms TTL=56
Reply from 202.53.11.53: bytes=32 time=27ms TTL=56
Reply from 202.53.11.53: bytes=32 time=27ms TTL=56
Reply from 202.53.11.53: bytes=32 time=27ms TTL=56
Reply from 202.53.11.53: bytes=32 time=27ms TTL=56
Reply from 202.53.11.53: bytes=32 time=30ms TTL=56
Reply from 202.53.11.53: bytes=32 time=31ms TTL=56
Reply from 202.53.11.53: bytes=32 time=28ms TTL=56
Reply from 202.53.11.53: bytes=32 time=28ms TTL=56
Reply from 202.53.11.53: bytes=32 time=27ms TTL=56
Reply from 202.53.11.53: bytes=32 time=28ms TTL=56
Reply from 202.53.11.53: bytes=32 time=27ms TTL=56
Reply from 202.53.11.53: bytes=32 time=28ms TTL=56
Reply from 202.53.11.53: bytes=32 time=27ms TTL=56
Request timed out.
Reply from 202.53.11.53: bytes=32 time=27ms TTL=56
Reply from 202.53.11.53: bytes=32 time=27ms TTL=56
Reply from 202.53.11.53: bytes=32 time=69ms TTL=56
Request timed out.
Reply from 202.53.11.53: bytes=32 time=27ms TTL=56
Reply from 202.53.11.53: bytes=32 time=27ms TTL=56
Reply from 202.53.11.53: bytes=32 time=27ms TTL=56
Reply from 202.53.11.53: bytes=32 time=27ms TTL=56
Reply from 202.53.11.53: bytes=32 time=27ms TTL=56
Reply from 202.53.11.53: bytes=32 time=27ms TTL=56
Reply from 202.53.11.53: bytes=32 time=28ms TTL=56
Reply from 202.53.11.53: bytes=32 time=36ms TTL=56
Reply from 202.53.11.53: bytes=32 time=83ms TTL=56
Reply from 202.53.11.53: bytes=32 time=57ms TTL=56
Reply from 202.53.11.53: bytes=32 time=29ms TTL=56
Reply from 202.53.11.53: bytes=32 time=28ms TTL=56
Reply from 202.53.11.53: bytes=32 time=27ms TTL=56
Reply from 202.53.11.53: bytes=32 time=28ms TTL=56
Reply from 202.53.11.53: bytes=32 time=30ms TTL=56
Reply from 202.53.11.53: bytes=32 time=27ms TTL=56
Reply from 202.53.11.53: bytes=32 time=27ms TTL=56
Reply from 202.53.11.53: bytes=32 time=27ms TTL=56
Reply from 202.53.11.53: bytes=32 time=27ms TTL=56
Reply from 202.53.11.53: bytes=32 time=28ms TTL=56
Reply from 202.53.11.53: bytes=32 time=58ms TTL=56
Reply from 202.53.11.53: bytes=32 time=27ms TTL=56
Reply from 202.53.11.53: bytes=32 time=28ms TTL=56
Reply from 202.53.11.53: bytes=32 time=28ms TTL=56
Reply from 202.53.11.53: bytes=32 time=29ms TTL=56
Reply from 202.53.11.53: bytes=32 time=28ms TTL=56
Reply from 202.53.11.53: bytes=32 time=47ms TTL=56
Request timed out.

Ping statistics for 202.53.11.53:
Packets: Sent = 104, Received = 98, Lost = 6 (5% loss),
Approximate round trip times in milli-seconds:
Minimum = 27ms, Maximum = 111ms, Average = 32ms
Top
User avatar
Gmstorm
A3 Gamemaster
Posts: 1829
Joined: Fri Jun 08, 2007 12:27 am
Class: Mage
Town: Temoz
Location: Redyan
Contact:
Contact Gmstorm

Re: Server lagging badly and gettting dced

Post by Gmstorm »

Please try to ping actcorp.in and acttv.in and post the ping reports.
[GM]Storm
Top
Borninsane
Posts: 23
Joined: Sat Feb 08, 2014 1:35 pm
Class: Archer
Town: Temoz

Re: Server lagging badly and gettting dced

Post by Borninsane »

This is act portal!

Pinging actcorp.in [202.53.8.32] with 32 bytes of data:
Reply from 202.53.8.32: bytes=32 time=33ms TTL=55
Reply from 202.53.8.32: bytes=32 time=36ms TTL=55
Reply from 202.53.8.32: bytes=32 time=32ms TTL=55
Reply from 202.53.8.32: bytes=32 time=34ms TTL=55
Reply from 202.53.8.32: bytes=32 time=33ms TTL=55
Reply from 202.53.8.32: bytes=32 time=33ms TTL=55
Request timed out.
Reply from 202.53.8.32: bytes=32 time=35ms TTL=55
Reply from 202.53.8.32: bytes=32 time=32ms TTL=55
Reply from 202.53.8.32: bytes=32 time=33ms TTL=55
Reply from 202.53.8.32: bytes=32 time=32ms TTL=55
Reply from 202.53.8.32: bytes=32 time=50ms TTL=55
Reply from 202.53.8.32: bytes=32 time=33ms TTL=55
Reply from 202.53.8.32: bytes=32 time=32ms TTL=55
Reply from 202.53.8.32: bytes=32 time=32ms TTL=55
Reply from 202.53.8.32: bytes=32 time=35ms TTL=55
Reply from 202.53.8.32: bytes=32 time=35ms TTL=55
Reply from 202.53.8.32: bytes=32 time=33ms TTL=55
Reply from 202.53.8.32: bytes=32 time=32ms TTL=55
Reply from 202.53.8.32: bytes=32 time=33ms TTL=55
Reply from 202.53.8.32: bytes=32 time=34ms TTL=55
Reply from 202.53.8.32: bytes=32 time=32ms TTL=55
Reply from 202.53.8.32: bytes=32 time=34ms TTL=55
Reply from 202.53.8.32: bytes=32 time=35ms TTL=55
Reply from 202.53.8.32: bytes=32 time=33ms TTL=55
Reply from 202.53.8.32: bytes=32 time=32ms TTL=55
Reply from 202.53.8.32: bytes=32 time=33ms TTL=55
Reply from 202.53.8.32: bytes=32 time=33ms TTL=55
Reply from 202.53.8.32: bytes=32 time=36ms TTL=55
Reply from 202.53.8.32: bytes=32 time=33ms TTL=55
Reply from 202.53.8.32: bytes=32 time=33ms TTL=55
Reply from 202.53.8.32: bytes=32 time=33ms TTL=55
Reply from 202.53.8.32: bytes=32 time=33ms TTL=55
Reply from 202.53.8.32: bytes=32 time=34ms TTL=55
Reply from 202.53.8.32: bytes=32 time=33ms TTL=55
Reply from 202.53.8.32: bytes=32 time=32ms TTL=55
Reply from 202.53.8.32: bytes=32 time=33ms TTL=55
Reply from 202.53.8.32: bytes=32 time=35ms TTL=55
Reply from 202.53.8.32: bytes=32 time=33ms TTL=55
Reply from 202.53.8.32: bytes=32 time=32ms TTL=55
Reply from 202.53.8.32: bytes=32 time=33ms TTL=55
Reply from 202.53.8.32: bytes=32 time=32ms TTL=55
Reply from 202.53.8.32: bytes=32 time=32ms TTL=55
Reply from 202.53.8.32: bytes=32 time=35ms TTL=55
Reply from 202.53.8.32: bytes=32 time=33ms TTL=55
Reply from 202.53.8.32: bytes=32 time=35ms TTL=55
Reply from 202.53.8.32: bytes=32 time=32ms TTL=55
Reply from 202.53.8.32: bytes=32 time=33ms TTL=55
Reply from 202.53.8.32: bytes=32 time=36ms TTL=55
Reply from 202.53.8.32: bytes=32 time=37ms TTL=55
Reply from 202.53.8.32: bytes=32 time=33ms TTL=55
Reply from 202.53.8.32: bytes=32 time=33ms TTL=55
Reply from 202.53.8.32: bytes=32 time=32ms TTL=55
Reply from 202.53.8.32: bytes=32 time=34ms TTL=55
Reply from 202.53.8.32: bytes=32 time=36ms TTL=55
Reply from 202.53.8.32: bytes=32 time=32ms TTL=55
Reply from 202.53.8.32: bytes=32 time=33ms TTL=55
Reply from 202.53.8.32: bytes=32 time=34ms TTL=55
Reply from 202.53.8.32: bytes=32 time=33ms TTL=55
Reply from 202.53.8.32: bytes=32 time=32ms TTL=55
Request timed out.
Reply from 202.53.8.32: bytes=32 time=32ms TTL=55
Reply from 202.53.8.32: bytes=32 time=33ms TTL=55
Reply from 202.53.8.32: bytes=32 time=32ms TTL=55
Reply from 202.53.8.32: bytes=32 time=36ms TTL=55
Reply from 202.53.8.32: bytes=32 time=34ms TTL=55
Reply from 202.53.8.32: bytes=32 time=33ms TTL=55
Reply from 202.53.8.32: bytes=32 time=41ms TTL=55
Reply from 202.53.8.32: bytes=32 time=33ms TTL=55
Reply from 202.53.8.32: bytes=32 time=32ms TTL=55
Reply from 202.53.8.32: bytes=32 time=33ms TTL=55
Reply from 202.53.8.32: bytes=32 time=33ms TTL=55
Reply from 202.53.8.32: bytes=32 time=32ms TTL=55
Reply from 202.53.8.32: bytes=32 time=32ms TTL=55
Reply from 202.53.8.32: bytes=32 time=33ms TTL=55

Ping statistics for 202.53.8.32:
Packets: Sent = 75, Received = 73, Lost = 2 (2% loss),
Approximate round trip times in milli-seconds:
Minimum = 32ms, Maximum = 50ms, Average = 33ms

This is actportl


Pinging portal.acttv.in [202.53.8.52] with 32 bytes of data:
Reply from 202.53.8.52: bytes=32 time=33ms TTL=54
Request timed out.
Reply from 202.53.8.52: bytes=32 time=34ms TTL=54
Reply from 202.53.8.52: bytes=32 time=33ms TTL=54
Reply from 202.53.8.52: bytes=32 time=32ms TTL=54
Request timed out.
Request timed out.
Reply from 202.53.8.52: bytes=32 time=33ms TTL=54
Reply from 202.53.8.52: bytes=32 time=33ms TTL=54
Reply from 202.53.8.52: bytes=32 time=34ms TTL=54
Reply from 202.53.8.52: bytes=32 time=33ms TTL=54
Reply from 202.53.8.52: bytes=32 time=38ms TTL=54
Reply from 202.53.8.52: bytes=32 time=33ms TTL=54
Reply from 202.53.8.52: bytes=32 time=33ms TTL=54
Reply from 202.53.8.52: bytes=32 time=35ms TTL=54
Reply from 202.53.8.52: bytes=32 time=36ms TTL=54
Reply from 202.53.8.52: bytes=32 time=33ms TTL=54
Reply from 202.53.8.52: bytes=32 time=32ms TTL=54
Reply from 202.53.8.52: bytes=32 time=35ms TTL=54
Reply from 202.53.8.52: bytes=32 time=36ms TTL=54
Reply from 202.53.8.52: bytes=32 time=33ms TTL=54
Reply from 202.53.8.52: bytes=32 time=32ms TTL=54
Reply from 202.53.8.52: bytes=32 time=34ms TTL=54
Reply from 202.53.8.52: bytes=32 time=33ms TTL=54
Reply from 202.53.8.52: bytes=32 time=33ms TTL=54
Reply from 202.53.8.52: bytes=32 time=32ms TTL=54
Reply from 202.53.8.52: bytes=32 time=39ms TTL=54
Reply from 202.53.8.52: bytes=32 time=33ms TTL=54
Reply from 202.53.8.52: bytes=32 time=33ms TTL=54
Reply from 202.53.8.52: bytes=32 time=36ms TTL=54
Reply from 202.53.8.52: bytes=32 time=36ms TTL=54
Reply from 202.53.8.52: bytes=32 time=36ms TTL=54
Reply from 202.53.8.52: bytes=32 time=34ms TTL=54
Reply from 202.53.8.52: bytes=32 time=36ms TTL=54
Reply from 202.53.8.52: bytes=32 time=33ms TTL=54
Reply from 202.53.8.52: bytes=32 time=33ms TTL=54
Reply from 202.53.8.52: bytes=32 time=34ms TTL=54
Reply from 202.53.8.52: bytes=32 time=33ms TTL=54
Reply from 202.53.8.52: bytes=32 time=33ms TTL=54
Reply from 202.53.8.52: bytes=32 time=37ms TTL=54
Reply from 202.53.8.52: bytes=32 time=35ms TTL=54
Reply from 202.53.8.52: bytes=32 time=33ms TTL=54
Reply from 202.53.8.52: bytes=32 time=37ms TTL=54
Reply from 202.53.8.52: bytes=32 time=33ms TTL=54
Reply from 202.53.8.52: bytes=32 time=32ms TTL=54
Reply from 202.53.8.52: bytes=32 time=34ms TTL=54
Reply from 202.53.8.52: bytes=32 time=33ms TTL=54
Reply from 202.53.8.52: bytes=32 time=36ms TTL=54
Reply from 202.53.8.52: bytes=32 time=38ms TTL=54
Reply from 202.53.8.52: bytes=32 time=34ms TTL=54
Reply from 202.53.8.52: bytes=32 time=33ms TTL=54
Reply from 202.53.8.52: bytes=32 time=35ms TTL=54
Reply from 202.53.8.52: bytes=32 time=33ms TTL=54
Reply from 202.53.8.52: bytes=32 time=33ms TTL=54
Reply from 202.53.8.52: bytes=32 time=33ms TTL=54
Reply from 202.53.8.52: bytes=32 time=35ms TTL=54
Reply from 202.53.8.52: bytes=32 time=32ms TTL=54
Reply from 202.53.8.52: bytes=32 time=36ms TTL=54
Reply from 202.53.8.52: bytes=32 time=35ms TTL=54
Reply from 202.53.8.52: bytes=32 time=33ms TTL=54
Reply from 202.53.8.52: bytes=32 time=34ms TTL=54
Reply from 202.53.8.52: bytes=32 time=33ms TTL=54
Reply from 202.53.8.52: bytes=32 time=33ms TTL=54
Reply from 202.53.8.52: bytes=32 time=35ms TTL=54
Reply from 202.53.8.52: bytes=32 time=36ms TTL=54
Reply from 202.53.8.52: bytes=32 time=33ms TTL=54
Reply from 202.53.8.52: bytes=32 time=37ms TTL=54
Reply from 202.53.8.52: bytes=32 time=36ms TTL=54
Reply from 202.53.8.52: bytes=32 time=33ms TTL=54
Reply from 202.53.8.52: bytes=32 time=37ms TTL=54
Reply from 202.53.8.52: bytes=32 time=35ms TTL=54
Reply from 202.53.8.52: bytes=32 time=32ms TTL=54
Reply from 202.53.8.52: bytes=32 time=32ms TTL=54
Reply from 202.53.8.52: bytes=32 time=33ms TTL=54
Reply from 202.53.8.52: bytes=32 time=33ms TTL=54
Reply from 202.53.8.52: bytes=32 time=33ms TTL=54
Reply from 202.53.8.52: bytes=32 time=38ms TTL=54
Reply from 202.53.8.52: bytes=32 time=33ms TTL=54
Reply from 202.53.8.52: bytes=32 time=36ms TTL=54
Reply from 202.53.8.52: bytes=32 time=33ms TTL=54
Reply from 202.53.8.52: bytes=32 time=33ms TTL=54
Reply from 202.53.8.52: bytes=32 time=33ms TTL=54
Reply from 202.53.8.52: bytes=32 time=36ms TTL=54
Reply from 202.53.8.52: bytes=32 time=33ms TTL=54
Reply from 202.53.8.52: bytes=32 time=32ms TTL=54
Reply from 202.53.8.52: bytes=32 time=38ms TTL=54
Reply from 202.53.8.52: bytes=32 time=33ms TTL=54
Reply from 202.53.8.52: bytes=32 time=33ms TTL=54
Reply from 202.53.8.52: bytes=32 time=36ms TTL=54
Reply from 202.53.8.52: bytes=32 time=33ms TTL=54
Reply from 202.53.8.52: bytes=32 time=36ms TTL=54
Reply from 202.53.8.52: bytes=32 time=32ms TTL=54
Reply from 202.53.8.52: bytes=32 time=32ms TTL=54
Reply from 202.53.8.52: bytes=32 time=38ms TTL=54
Reply from 202.53.8.52: bytes=32 time=36ms TTL=54
Reply from 202.53.8.52: bytes=32 time=32ms TTL=54
Reply from 202.53.8.52: bytes=32 time=36ms TTL=54
Reply from 202.53.8.52: bytes=32 time=33ms TTL=54
Reply from 202.53.8.52: bytes=32 time=33ms TTL=54
Reply from 202.53.8.52: bytes=32 time=39ms TTL=54
Reply from 202.53.8.52: bytes=32 time=35ms TTL=54
Reply from 202.53.8.52: bytes=32 time=33ms TTL=54
Reply from 202.53.8.52: bytes=32 time=37ms TTL=54
Reply from 202.53.8.52: bytes=32 time=35ms TTL=54
Reply from 202.53.8.52: bytes=32 time=33ms TTL=54
Reply from 202.53.8.52: bytes=32 time=38ms TTL=54
Reply from 202.53.8.52: bytes=32 time=33ms TTL=54
Reply from 202.53.8.52: bytes=32 time=32ms TTL=54
Reply from 202.53.8.52: bytes=32 time=62ms TTL=54
Reply from 202.53.8.52: bytes=32 time=33ms TTL=54
Reply from 202.53.8.52: bytes=32 time=32ms TTL=54
Reply from 202.53.8.52: bytes=32 time=33ms TTL=54
Reply from 202.53.8.52: bytes=32 time=33ms TTL=54
Reply from 202.53.8.52: bytes=32 time=33ms TTL=54
Reply from 202.53.8.52: bytes=32 time=41ms TTL=54
Reply from 202.53.8.52: bytes=32 time=35ms TTL=54
Reply from 202.53.8.52: bytes=32 time=33ms TTL=54
Reply from 202.53.8.52: bytes=32 time=34ms TTL=54
Reply from 202.53.8.52: bytes=32 time=32ms TTL=54
Reply from 202.53.8.52: bytes=32 time=33ms TTL=54
Reply from 202.53.8.52: bytes=32 time=32ms TTL=54
Reply from 202.53.8.52: bytes=32 time=33ms TTL=54
Reply from 202.53.8.52: bytes=32 time=33ms TTL=54
Reply from 202.53.8.52: bytes=32 time=32ms TTL=54
Reply from 202.53.8.52: bytes=32 time=35ms TTL=54
Reply from 202.53.8.52: bytes=32 time=33ms TTL=54
Reply from 202.53.8.52: bytes=32 time=33ms TTL=54
Reply from 202.53.8.52: bytes=32 time=33ms TTL=54
Reply from 202.53.8.52: bytes=32 time=33ms TTL=54
Reply from 202.53.8.52: bytes=32 time=33ms TTL=54
Reply from 202.53.8.52: bytes=32 time=34ms TTL=54
Reply from 202.53.8.52: bytes=32 time=34ms TTL=54
Request timed out.
Reply from 202.53.8.52: bytes=32 time=34ms TTL=54
Reply from 202.53.8.52: bytes=32 time=35ms TTL=54
Reply from 202.53.8.52: bytes=32 time=35ms TTL=54
Reply from 202.53.8.52: bytes=32 time=34ms TTL=54
Reply from 202.53.8.52: bytes=32 time=33ms TTL=54
Reply from 202.53.8.52: bytes=32 time=32ms TTL=54
Reply from 202.53.8.52: bytes=32 time=34ms TTL=54
Reply from 202.53.8.52: bytes=32 time=33ms TTL=54
Request timed out.
Reply from 202.53.8.52: bytes=32 time=33ms TTL=54
Reply from 202.53.8.52: bytes=32 time=33ms TTL=54
Reply from 202.53.8.52: bytes=32 time=37ms TTL=54
Reply from 202.53.8.52: bytes=32 time=33ms TTL=54
Reply from 202.53.8.52: bytes=32 time=39ms TTL=54
Reply from 202.53.8.52: bytes=32 time=39ms TTL=54
Reply from 202.53.8.52: bytes=32 time=37ms TTL=54
Reply from 202.53.8.52: bytes=32 time=32ms TTL=54
Reply from 202.53.8.52: bytes=32 time=35ms TTL=54
Reply from 202.53.8.52: bytes=32 time=33ms TTL=54
Reply from 202.53.8.52: bytes=32 time=35ms TTL=54
Reply from 202.53.8.52: bytes=32 time=34ms TTL=54
Reply from 202.53.8.52: bytes=32 time=33ms TTL=54

Ping statistics for 202.53.8.52:
Packets: Sent = 155, Received = 150, Lost = 5 (3% loss),
Approximate round trip times in milli-seconds:
Minimum = 32ms, Maximum = 62ms, Average = 34ms

My location divison head had told me to tell the a3india management to raise ticket to hyderbad act fibernet so that they might check the path and theres definitely a line choking issue. Its fine from cheanni to nellore gateway side itseems, my location is nellore :|
Top
Borninsane
Posts: 23
Joined: Sat Feb 08, 2014 1:35 pm
Class: Archer
Town: Temoz

Re: Server lagging badly and gettting dced

Post by Borninsane »

Sir these are the ping statistics for a3india, actportal and intermediate ip in the morning, please check!

Ping statistics for 202.53.8.52:
Packets: Sent = 387, Received = 385, Lost = 2 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 22ms, Maximum = 160ms, Average = 24ms

Ping statistics for 183.82.14.222:
Packets: Sent = 442, Received = 442, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 20ms, Maximum = 102ms, Average = 22ms

Ping statistics for 202.53.11.53:
Packets: Sent = 723, Received = 723, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 21ms, Maximum = 253ms, Average = 24ms

Theres not even single millisecond fluctuation right now in the morning, you see hows it working! But when i get back by 8pm and when i sit to play, it all starts there and lasts till i sleep i.e 12pm don't know if i would still get packet loss after that time. ISP is blaming game, game is blaming ISP. This is unfortunate for me :(
Top
User avatar
Gmstorm
A3 Gamemaster
Posts: 1829
Joined: Fri Jun 08, 2007 12:27 am
Class: Mage
Town: Temoz
Location: Redyan
Contact:
Contact Gmstorm

Re: Server lagging badly and gettting dced

Post by Gmstorm »

Borninsane wrote: Ping statistics for 202.53.8.52:
Packets: Sent = 387, Received = 385, Lost = 2 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 22ms, Maximum = 160ms, Average = 24ms
You are having packet loss to your ISP's website. It's pretty surely an issue with your ISP itself.
[GM]Storm
Top
Borninsane
Posts: 23
Joined: Sat Feb 08, 2014 1:35 pm
Class: Archer
Town: Temoz

Re: Server lagging badly and gettting dced

Post by Borninsane »

That is common for them itseems,
but actually the issue is fixed they called me today and said there was some choking issue in the previous path we applied for new static ip and now your path has changed, the ping is reduced and no reuqest timed out now. Accordingly i checked it seems fine now yeah the ping has reduced to 16ms and sometimes i get 0ms as well, but for 15-20 mins i get 1 ping rise to 300+ms and gets back to 16 not consistently but quite rarely. Still its playable it could affect me in wars though, but something is better than nothing. So cheers :D
Top
User avatar
Gmstorm
A3 Gamemaster
Posts: 1829
Joined: Fri Jun 08, 2007 12:27 am
Class: Mage
Town: Temoz
Location: Redyan
Contact:
Contact Gmstorm

Re: Server lagging badly and gettting dced

Post by Gmstorm »

Borninsane wrote:That is common for them itseems,
This is NOT normal. Your ISP seems to be facing issues internally. You should contact them with the ping reports the ISP's website and portal pages. It's very unusual to get packet loss to a local website hosted by your ISP.
[GM]Storm
Top
Post Reply

Return to “General”