Static IP improves service drastically

[chaibiskutbhai]

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?

PING 216.185.109.70 (216.185.109.70) 56(84) bytes of data.
64 bytes from 216.185.109.70: icmp_req=1 ttl=121 time=54.6 ms
64 bytes from 216.185.109.70: icmp_req=2 ttl=121 time=54.6 ms
64 bytes from 216.185.109.70: icmp_req=3 ttl=121 time=58.5 ms
64 bytes from 216.185.109.70: icmp_req=4 ttl=121 time=55.6 ms
64 bytes from 216.185.109.70: icmp_req=5 ttl=121 time=60.1 ms
64 bytes from 216.185.109.70: icmp_req=6 ttl=121 time=57.3 ms
64 bytes from 216.185.109.70: icmp_req=7 ttl=121 time=56.5 ms
64 bytes from 216.185.109.70: icmp_req=8 ttl=121 time=57.0 ms
64 bytes from 216.185.109.70: icmp_req=9 ttl=121 time=55.7 ms
64 bytes from 216.185.109.70: icmp_req=10 ttl=121 time=58.2 ms
64 bytes from 216.185.109.70: icmp_req=11 ttl=121 time=58.8 ms
64 bytes from 216.185.109.70: icmp_req=12 ttl=121 time=55.4 ms
64 bytes from 216.185.109.70: icmp_req=13 ttl=121 time=58.2 ms
64 bytes from 216.185.109.70: icmp_req=14 ttl=121 time=57.2 ms
64 bytes from 216.185.109.70: icmp_req=15 ttl=121 time=57.8 ms
64 bytes from 216.185.109.70: icmp_req=16 ttl=121 time=55.4 ms


Pretty ok, I guess. Tower is about 200m from my device. A few trees around too.

 

[jem456]

Amazing!! that's definately a 10/10 considering the fact that these servers are located in singapore AND it's wireless !can you ping this too?175.100.184.18It's a CS:GO server in India

 

[anonuser7]

My pings fluctuate a lot, I am also on secondary plan(post FUP) where first preference are users who haven't crossed FUP

Microsoft Windows [Version 6.2.9200](c) 2012 Microsoft Corporation. All rights reserved.C:UsersSAHIB>ping 175.100.184.18Pinging 175.100.184.18 with 32 bytes of data:Reply from 175.100.184.18: bytes=32 time=39ms TTL=120Reply from 175.100.184.18: bytes=32 time=37ms TTL=120Reply from 175.100.184.18: bytes=32 time=39ms TTL=120Reply from 175.100.184.18: bytes=32 time=33ms TTL=120Ping statistics for 175.100.184.18:    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),Approximate round trip times in milli-seconds:    Minimum = 33ms, Maximum = 39ms, Average = 37msC:UsersSAHIB>ping 175.100.184.18 -tPinging 175.100.184.18 with 32 bytes of data:Reply from 175.100.184.18: bytes=32 time=34ms TTL=120Reply from 175.100.184.18: bytes=32 time=37ms TTL=120Reply from 175.100.184.18: bytes=32 time=38ms TTL=120Reply from 175.100.184.18: bytes=32 time=34ms TTL=120Reply from 175.100.184.18: bytes=32 time=38ms TTL=120Reply from 175.100.184.18: bytes=32 time=34ms TTL=120Reply from 175.100.184.18: bytes=32 time=44ms TTL=120Reply from 175.100.184.18: bytes=32 time=40ms TTL=120Reply from 175.100.184.18: bytes=32 time=36ms TTL=120Reply from 175.100.184.18: bytes=32 time=34ms TTL=120Reply from 175.100.184.18: bytes=32 time=39ms TTL=120Reply from 175.100.184.18: bytes=32 time=30ms TTL=120Reply from 175.100.184.18: bytes=32 time=37ms TTL=120Reply from 175.100.184.18: bytes=32 time=32ms TTL=120Reply from 175.100.184.18: bytes=32 time=47ms TTL=120Reply from 175.100.184.18: bytes=32 time=41ms TTL=120Reply from 175.100.184.18: bytes=32 time=44ms TTL=120Reply from 175.100.184.18: bytes=32 time=34ms TTL=120Reply from 175.100.184.18: bytes=32 time=50ms TTL=120Reply from 175.100.184.18: bytes=32 time=32ms TTL=120Reply from 175.100.184.18: bytes=32 time=36ms TTL=120Reply from 175.100.184.18: bytes=32 time=33ms TTL=120Reply from 175.100.184.18: bytes=32 time=36ms TTL=120Reply from 175.100.184.18: bytes=32 time=33ms TTL=120Reply from 175.100.184.18: bytes=32 time=36ms TTL=120Reply from 175.100.184.18: bytes=32 time=42ms TTL=120Ping statistics for 175.100.184.18:    Packets: Sent = 26, Received = 26, Lost = 0 (0% loss),Approximate round trip times in milli-seconds:    Minimum = 30ms, Maximum = 50ms, Average = 37msC:UsersSAHIB>

 

[jem456]

It's still better than BSNL, where it's not going below 65 for me, thanks alot!How's the packet loss and jitter?? That too affects gameplay , if packet loss too high then it's the same as lagging out XD
I think pingtest results would tell the jitterI contacted the tikona guy who posted ads here, said he'll call me in 10 mins, been hours and no call -.-Anyways, once I get the demo from the guy i'll get to know the signal strength, so +-80% should be the threshold, otherwise i'll stick to BSNL..I don't wanna risk stable internet

 

[jem456]

Pretty ok, I guess. Tower is about 200m from my device. A few trees around too.

So, If the tower is 200m away from your device, what's the signal strength you're getting?

 

[anonuser7]

3 continues pingtests to Singapore





Germany :

 

---

[jem456]

Thanks!The jitters seem acceptable..i'm used to small fluctuations

 

[chaibiskutbhai]

Amazing!! that's definately a 10/10 considering the fact that these servers are located in singapore AND it's wireless !
can you ping this too?

175.100.184.18

It's a CS:GO server in India

PING 175.100.184.18 (175.100.184.18) 56(84) bytes of data.
64 bytes from 175.100.184.18: icmp_req=1 ttl=121 time=33.3 ms
64 bytes from 175.100.184.18: icmp_req=2 ttl=121 time=34.1 ms
64 bytes from 175.100.184.18: icmp_req=3 ttl=121 time=44.7 ms
64 bytes from 175.100.184.18: icmp_req=5 ttl=121 time=49.8 ms
64 bytes from 175.100.184.18: icmp_req=6 ttl=121 time=33.1 ms
64 bytes from 175.100.184.18: icmp_req=7 ttl=121 time=31.8 ms
64 bytes from 175.100.184.18: icmp_req=8 ttl=121 time=44.9 ms
64 bytes from 175.100.184.18: icmp_req=9 ttl=121 time=42.6 ms
64 bytes from 175.100.184.18: icmp_req=11 ttl=121 time=35.2 ms

So, If the tower is 200m away from your device, what's the signal strength you're getting?

The device shows full signal.

http://www.pingtest.net

 

[jem456]

PING 175.100.184.18 (175.100.184.18) 56(84) bytes of data.
64 bytes from 175.100.184.18: icmp_req=1 ttl=121 time=33.3 ms
64 bytes from 175.100.184.18: icmp_req=2 ttl=121 time=34.1 ms
64 bytes from 175.100.184.18: icmp_req=3 ttl=121 time=44.7 ms
64 bytes from 175.100.184.18: icmp_req=5 ttl=121 time=49.8 ms
64 bytes from 175.100.184.18: icmp_req=6 ttl=121 time=33.1 ms
64 bytes from 175.100.184.18: icmp_req=7 ttl=121 time=31.8 ms
64 bytes from 175.100.184.18: icmp_req=8 ttl=121 time=44.9 ms
64 bytes from 175.100.184.18: icmp_req=9 ttl=121 time=42.6 ms
64 bytes from 175.100.184.18: icmp_req=11 ttl=121 time=35.2 ms



The device shows full signal.

http://www.pingtest.net

Talked to the tikona guy today, according to him the nearest tower from my place is on a building 100-200m from here, so i should expect full signal..
BUT, I'm still skeptical about their service, i asked for a demo but this guy already asked me to get all documents ready when they come
What's your opinion? have you faced any problems?

 

[chaibiskutbhai]

Tikona has the first demo, then pay policy.
When the demo guy comes, do all your checks. Physically check if the signal on your device is full. If it is not, you might encounter lag. Also, get the guy to install a slightly longer cable, which would help you move around your device/router if needed.
Also, never pay cash. Always pay by account payee cheque only. Ensures that the money goes to the company directly. There have been cases where freelance agents run away with the cash. If he says he wont accept cheque, throw him out and complain to Tikona CC about such a guy.