Static IP improves service drastically

ChaiBiskutBhai said:
New billing cycle started today and speeds are back to normal!
Nice! I'm thinking of getting tikona myself, but what about pings? can you ping these servers and post the results here?
216.185.109.70
216.185.102.31
194.97.167.11
176.57.184.20

I'll highly appreciate it.
Thanks!!
EDIT: Also, how far is the tower from your place?
 
14 ms as good as being on FTTH :P
 
jem456 said:
Nice! I'm thinking of getting tikona myself, but what about pings? can you ping these servers and post the results here?216.185.109.70216.185.102.31194.97.167.11176.57.184.20
I'll highly appreciate it.
Thanks!!
EDIT: Also, how far is the tower from your place?
Code:
Microsoft Windows [Version 6.2.9200](c) 2012 Microsoft Corporation. All rights reserved.C:UsersSAHIB>ping 216.185.102.31 -tPinging 216.185.102.31 with 32 bytes of data:Reply from 216.185.102.31: bytes=32 time=79ms TTL=112Reply from 216.185.102.31: bytes=32 time=90ms TTL=112Reply from 216.185.102.31: bytes=32 time=84ms TTL=112Reply from 216.185.102.31: bytes=32 time=84ms TTL=112Reply from 216.185.102.31: bytes=32 time=85ms TTL=112Reply from 216.185.102.31: bytes=32 time=89ms TTL=112Reply from 216.185.102.31: bytes=32 time=82ms TTL=112Reply from 216.185.102.31: bytes=32 time=78ms TTL=112Reply from 216.185.102.31: bytes=32 time=74ms TTL=112Reply from 216.185.102.31: bytes=32 time=77ms TTL=112Reply from 216.185.102.31: bytes=32 time=90ms TTL=112Reply from 216.185.102.31: bytes=32 time=80ms TTL=112Reply from 216.185.102.31: bytes=32 time=80ms TTL=112Reply from 216.185.102.31: bytes=32 time=80ms TTL=112Reply from 216.185.102.31: bytes=32 time=73ms TTL=112Reply from 216.185.102.31: bytes=32 time=87ms TTL=112Reply from 216.185.102.31: bytes=32 time=83ms TTL=112Reply from 216.185.102.31: bytes=32 time=78ms TTL=112Reply from 216.185.102.31: bytes=32 time=85ms TTL=112Reply from 216.185.102.31: bytes=32 time=83ms TTL=112Reply from 216.185.102.31: bytes=32 time=88ms TTL=112Reply from 216.185.102.31: bytes=32 time=115ms TTL=112Reply from 216.185.102.31: bytes=32 time=82ms TTL=112Reply from 216.185.102.31: bytes=32 time=87ms TTL=112Reply from 216.185.102.31: bytes=32 time=83ms TTL=112Reply from 216.185.102.31: bytes=32 time=86ms TTL=112Reply from 216.185.102.31: bytes=32 time=78ms TTL=112Reply from 216.185.102.31: bytes=32 time=79ms TTL=112Ping statistics for 216.185.102.31:    Packets: Sent = 28, Received = 28, Lost = 0 (0% loss),Approximate round trip times in milli-seconds:    Minimum = 73ms, Maximum = 115ms, Average = 83msC:UsersSAHIB>

Code:
Microsoft Windows [Version 6.2.9200](c) 2012 Microsoft Corporation. All rights reserved.C:UsersSAHIB>ping 194.97.167.11 -tPinging 194.97.167.11 with 32 bytes of data:Reply from 194.97.167.11: bytes=32 time=161ms TTL=109Reply from 194.97.167.11: bytes=32 time=159ms TTL=109Reply from 194.97.167.11: bytes=32 time=168ms TTL=109Reply from 194.97.167.11: bytes=32 time=161ms TTL=109Reply from 194.97.167.11: bytes=32 time=158ms TTL=109Reply from 194.97.167.11: bytes=32 time=165ms TTL=109Reply from 194.97.167.11: bytes=32 time=165ms TTL=109Reply from 194.97.167.11: bytes=32 time=164ms TTL=109Reply from 194.97.167.11: bytes=32 time=161ms TTL=109Reply from 194.97.167.11: bytes=32 time=157ms TTL=109Reply from 194.97.167.11: bytes=32 time=161ms TTL=109Reply from 194.97.167.11: bytes=32 time=158ms TTL=109Reply from 194.97.167.11: bytes=32 time=169ms TTL=109Reply from 194.97.167.11: bytes=32 time=165ms TTL=109Reply from 194.97.167.11: bytes=32 time=163ms TTL=109Reply from 194.97.167.11: bytes=32 time=168ms TTL=109Reply from 194.97.167.11: bytes=32 time=170ms TTL=109Reply from 194.97.167.11: bytes=32 time=162ms TTL=109Reply from 194.97.167.11: bytes=32 time=158ms TTL=109Reply from 194.97.167.11: bytes=32 time=156ms TTL=109Reply from 194.97.167.11: bytes=32 time=165ms TTL=109Reply from 194.97.167.11: bytes=32 time=178ms TTL=109Reply from 194.97.167.11: bytes=32 time=156ms TTL=109Reply from 194.97.167.11: bytes=32 time=163ms TTL=109Reply from 194.97.167.11: bytes=32 time=156ms TTL=109Reply from 194.97.167.11: bytes=32 time=202ms TTL=109Reply from 194.97.167.11: bytes=32 time=166ms TTL=109Reply from 194.97.167.11: bytes=32 time=164ms TTL=109Reply from 194.97.167.11: bytes=32 time=163ms TTL=109Reply from 194.97.167.11: bytes=32 time=162ms TTL=109Reply from 194.97.167.11: bytes=32 time=160ms TTL=109Reply from 194.97.167.11: bytes=32 time=158ms TTL=109Reply from 194.97.167.11: bytes=32 time=162ms TTL=109Reply from 194.97.167.11: bytes=32 time=167ms TTL=109Reply from 194.97.167.11: bytes=32 time=156ms TTL=109Reply from 194.97.167.11: bytes=32 time=158ms TTL=109Reply from 194.97.167.11: bytes=32 time=172ms TTL=109Reply from 194.97.167.11: bytes=32 time=160ms TTL=109Reply from 194.97.167.11: bytes=32 time=162ms TTL=109Reply from 194.97.167.11: bytes=32 time=160ms TTL=109Reply from 194.97.167.11: bytes=32 time=163ms TTL=109Reply from 194.97.167.11: bytes=32 time=162ms TTL=109Ping statistics for 194.97.167.11:    Packets: Sent = 42, Received = 42, Lost = 0 (0% loss),Approximate round trip times in milli-seconds:    Minimum = 156ms, Maximum = 202ms, Average = 163msC:UsersSAHIB>
Code:
Microsoft Windows [Version 6.2.9200](c) 2012 Microsoft Corporation. All rights reserved.C:UsersSAHIB>ping 176.57.184.20 -tPinging 176.57.184.20 with 32 bytes of data:Reply from 176.57.184.20: bytes=32 time=159ms TTL=113Reply from 176.57.184.20: bytes=32 time=154ms TTL=113Reply from 176.57.184.20: bytes=32 time=174ms TTL=113Reply from 176.57.184.20: bytes=32 time=155ms TTL=113Reply from 176.57.184.20: bytes=32 time=155ms TTL=113Reply from 176.57.184.20: bytes=32 time=159ms TTL=113Reply from 176.57.184.20: bytes=32 time=170ms TTL=113Reply from 176.57.184.20: bytes=32 time=154ms TTL=113Reply from 176.57.184.20: bytes=32 time=159ms TTL=113Reply from 176.57.184.20: bytes=32 time=155ms TTL=113Reply from 176.57.184.20: bytes=32 time=158ms TTL=113Reply from 176.57.184.20: bytes=32 time=157ms TTL=113Reply from 176.57.184.20: bytes=32 time=159ms TTL=113Reply from 176.57.184.20: bytes=32 time=160ms TTL=113Reply from 176.57.184.20: bytes=32 time=159ms TTL=113Reply from 176.57.184.20: bytes=32 time=155ms TTL=113Reply from 176.57.184.20: bytes=32 time=173ms TTL=113Reply from 176.57.184.20: bytes=32 time=157ms TTL=113Reply from 176.57.184.20: bytes=32 time=151ms TTL=113Reply from 176.57.184.20: bytes=32 time=157ms TTL=113Reply from 176.57.184.20: bytes=32 time=159ms TTL=113Reply from 176.57.184.20: bytes=32 time=155ms TTL=113Reply from 176.57.184.20: bytes=32 time=157ms TTL=113Reply from 176.57.184.20: bytes=32 time=156ms TTL=113Reply from 176.57.184.20: bytes=32 time=153ms TTL=113Ping statistics for 176.57.184.20:    Packets: Sent = 25, Received = 25, Lost = 0 (0% loss),Approximate round trip times in milli-seconds:    Minimum = 151ms, Maximum = 174ms, Average = 158msC:UsersSAHIB>
 
Awesome!! how far is the tower from your place?
BTW those servers you pinged are actually battlefield 3 online servers located in singapore and germany..the ~150 ping servers are the germany ones
 
I don't have any idea where it is but i get 80% signal in my device which is on my roof(tall building, and signal is also coming from a tall building i guess)
BTW what would be the rating of these pings on a scale of 10?
Above post edited and removed where there was packet loss, sister was watching youtube
216.185.109.70
Code:
Microsoft Windows [Version 6.2.9200](c) 2012 Microsoft Corporation. All rights reserved.C:UsersSAHIB>ping 216.185.109.70 -tPinging 216.185.109.70 with 32 bytes of data:Reply from 216.185.109.70: bytes=32 time=84ms TTL=112Reply from 216.185.109.70: bytes=32 time=75ms TTL=112Reply from 216.185.109.70: bytes=32 time=82ms TTL=112Reply from 216.185.109.70: bytes=32 time=83ms TTL=112Reply from 216.185.109.70: bytes=32 time=74ms TTL=112Reply from 216.185.109.70: bytes=32 time=76ms TTL=112Reply from 216.185.109.70: bytes=32 time=76ms TTL=112Reply from 216.185.109.70: bytes=32 time=82ms TTL=112Reply from 216.185.109.70: bytes=32 time=79ms TTL=112Reply from 216.185.109.70: bytes=32 time=98ms TTL=112Reply from 216.185.109.70: bytes=32 time=75ms TTL=112Reply from 216.185.109.70: bytes=32 time=89ms TTL=112Reply from 216.185.109.70: bytes=32 time=75ms TTL=112Reply from 216.185.109.70: bytes=32 time=90ms TTL=112Reply from 216.185.109.70: bytes=32 time=78ms TTL=112Reply from 216.185.109.70: bytes=32 time=77ms TTL=112Reply from 216.185.109.70: bytes=32 time=73ms TTL=112Reply from 216.185.109.70: bytes=32 time=73ms TTL=112Reply from 216.185.109.70: bytes=32 time=75ms TTL=112Reply from 216.185.109.70: bytes=32 time=80ms TTL=112Reply from 216.185.109.70: bytes=32 time=78ms TTL=112Reply from 216.185.109.70: bytes=32 time=77ms TTL=112Reply from 216.185.109.70: bytes=32 time=74ms TTL=112Ping statistics for 216.185.109.70:    Packets: Sent = 23, Received = 23, Lost = 0 (0% loss),Approximate round trip times in milli-seconds:    Minimum = 73ms, Maximum = 98ms, Average = 79msC:UsersSAHIB>
 
I'd say, compared to other ISP's who play BF3 in India, around 7-8
 


quite decent pings. if you want to compare here u go
Pinging 216.185.109.70 with 32 bytes of data:Reply from 216.185.109.70: bytes=32 time=71ms TTL=118Reply from 216.185.109.70: bytes=32 time=71ms TTL=118Reply from 216.185.109.70: bytes=32 time=71ms TTL=118Reply from 216.185.109.70: bytes=32 time=71ms TTL=118 pings from a vdsl line.
 
But you have MTNL and jem456 is having BSNL in his area

EDIT : We should discuss about this in another thread as this one is for static ip
 
sahibunlimited said:
But you have MTNL and jem456 is having BSNL in his area

EDIT : We should talk about this in another thread as this one is for static ip
Do you have a static IP?
 
Nope, still there isn't a complete proof that static ip increases upload speed and pings, after i get a complete proof i will get it.
 

Back