GreenR Community|The Community Run by You
cancel
Showing results for 
Search instead for 
Did you mean: 

Gface Warface latency issue

Highlighted
Honored Commentator

Gface Warface latency issue

Hi,

I am on Starhub Fibre 1Gbps now. The game that I am playing is Warface - https://www.warface.com/

 

Now whenever I am playing the game, I keep getting kicked out with the message :

"Kicked due to high latency"

 

Ping Test

=======

C:\Windows\System32>ping com-us.wfw.warface.com

Pinging com-us.wfw.warface.com [172.99.95.228] with 32 bytes of data:
Reply from 172.99.95.228: bytes=32 time=244ms TTL=49
Reply from 172.99.95.228: bytes=32 time=245ms TTL=49
Reply from 172.99.95.228: bytes=32 time=244ms TTL=49
Reply from 172.99.95.228: bytes=32 time=244ms TTL=49

Ping statistics for 172.99.95.228:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 244ms, Maximum = 245ms, Average = 244ms

 

Tracert

======

C:\Windows\System32>tracert com-us.wfw.warface.com

Tracing route to com-us.wfw.warface.com [172.99.95.228]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms XiaoQiang [192.168.1.1]
2 3 ms 3 ms 3 ms 3.229.55.182.in-addr.arpa [182.55.229.3]
3 3 ms 3 ms 3 ms 65.44.90.183.in-addr.arpa [183.90.44.65]
4 5 ms 4 ms 5 ms 9.44.90.183.in-addr.arpa [183.90.44.9]
5 174 ms 174 ms 174 ms las-b3-link.telia.net [80.239.160.213]
6 244 ms 244 ms 244 ms ash-bb3-link.telia.net [62.115.121.219]
7 244 ms 244 ms 244 ms ash-b1-link.telia.net [62.115.113.209]
8 245 ms 245 ms 246 ms rackspace-ic-302157-ash-b1.c.telia.net [62.115.3
2.122]
9 * * * Request timed out.
10 245 ms 246 ms 245 ms coreb-dcpe1.iad3.rackspace.net [69.20.2.165]
11 242 ms 242 ms 242 ms coreb-core8.iad3.rackspace.net [69.20.2.115]
12 241 ms 241 ms 241 ms core8-aggr501a-3.iad3.rackspace.net [72.4.122.21
5]
13 244 ms 245 ms 244 ms 228.95.99.172.in-addr.arpa [172.99.95.228]

Trace complete.

 

My PC hardware and software side has no issue as I am still able to play the game intermittently. But when the game gets intense, I get kicked due to high latency.

 

Please help resolve this issue. Do feel free to let me know any other information that you may need to help you resolve this.

 

Thank you so much.

 

Everyone's Tags (2)
7 REPLIES 7
Community Relationship Manager

Re: Gface Warface latency issue

Hi @i1magic, we understand that the issue has been resolved. Do you still encounter any issues with the speed? -Jolene 

Honored Commentator

Re: Gface Warface latency issue

It has improved a lot. For the last few days, I only got "kicked due to high latency" once or twice. Which is still acceptable. Will monitor further.

 

Thank you all for the fast response on this issue.

Alumni (Retired)

Re: Gface Warface latency issue

Thanks for the update, we appreciate it. 

Honored Commentator

Re: Gface Warface latency issue

Updates after almost a week. Just play last night, didn't get the "Kick due to high latency error" anymore.

Great job guys!
Honored Commentator

Re: Gface Warface latency issue

The problem of "Kicked due to high latency" is back.

Pinging com-us.wfw.warface.com [172.99.95.229] with 32 bytes of data:
Reply from 172.99.95.229: bytes=32 time=250ms TTL=49
Reply from 172.99.95.229: bytes=32 time=250ms TTL=49
Reply from 172.99.95.229: bytes=32 time=250ms TTL=49
Reply from 172.99.95.229: bytes=32 time=250ms TTL=49
Reply from 172.99.95.229: bytes=32 time=250ms TTL=49
Reply from 172.99.95.229: bytes=32 time=251ms TTL=49
Reply from 172.99.95.229: bytes=32 time=250ms TTL=49
Reply from 172.99.95.229: bytes=32 time=250ms TTL=49
Reply from 172.99.95.229: bytes=32 time=251ms TTL=49
Reply from 172.99.95.229: bytes=32 time=250ms TTL=49
Reply from 172.99.95.229: bytes=32 time=250ms TTL=49
Reply from 172.99.95.229: bytes=32 time=250ms TTL=49
Reply from 172.99.95.229: bytes=32 time=250ms TTL=49
Reply from 172.99.95.229: bytes=32 time=250ms TTL=49
Reply from 172.99.95.229: bytes=32 time=249ms TTL=49
Reply from 172.99.95.229: bytes=32 time=250ms TTL=49
Reply from 172.99.95.229: bytes=32 time=249ms TTL=49
Reply from 172.99.95.229: bytes=32 time=250ms TTL=49
Reply from 172.99.95.229: bytes=32 time=250ms TTL=49
Reply from 172.99.95.229: bytes=32 time=250ms TTL=49
Reply from 172.99.95.229: bytes=32 time=250ms TTL=49
Reply from 172.99.95.229: bytes=32 time=250ms TTL=49
Reply from 172.99.95.229: bytes=32 time=250ms TTL=49
Reply from 172.99.95.229: bytes=32 time=250ms TTL=49
Reply from 172.99.95.229: bytes=32 time=250ms TTL=49
Reply from 172.99.95.229: bytes=32 time=250ms TTL=49
Reply from 172.99.95.229: bytes=32 time=250ms TTL=49
Reply from 172.99.95.229: bytes=32 time=250ms TTL=49
Reply from 172.99.95.229: bytes=32 time=250ms TTL=49
Reply from 172.99.95.229: bytes=32 time=250ms TTL=49
Reply from 172.99.95.229: bytes=32 time=250ms TTL=49
Reply from 172.99.95.229: bytes=32 time=250ms TTL=49
Reply from 172.99.95.229: bytes=32 time=250ms TTL=49
Reply from 172.99.95.229: bytes=32 time=250ms TTL=49
Reply from 172.99.95.229: bytes=32 time=250ms TTL=49
Reply from 172.99.95.229: bytes=32 time=250ms TTL=49
Reply from 172.99.95.229: bytes=32 time=250ms TTL=49
Reply from 172.99.95.229: bytes=32 time=250ms TTL=49
Reply from 172.99.95.229: bytes=32 time=250ms TTL=49
Reply from 172.99.95.229: bytes=32 time=250ms TTL=49
Reply from 172.99.95.229: bytes=32 time=250ms TTL=49
Reply from 172.99.95.229: bytes=32 time=250ms TTL=49
Reply from 172.99.95.229: bytes=32 time=250ms TTL=49
Reply from 172.99.95.229: bytes=32 time=250ms TTL=49
Reply from 172.99.95.229: bytes=32 time=250ms TTL=49
Reply from 172.99.95.229: bytes=32 time=251ms TTL=49
Reply from 172.99.95.229: bytes=32 time=250ms TTL=49
Reply from 172.99.95.229: bytes=32 time=250ms TTL=49
Reply from 172.99.95.229: bytes=32 time=250ms TTL=49
Reply from 172.99.95.229: bytes=32 time=250ms TTL=49

 

Ping statistics for 172.99.95.229:
Packets: Sent = 50, Received = 50, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 249ms, Maximum = 251ms, Average = 250ms

Honored Commentator

Re: Gface Warface latency issue

This is the tracert.


Tracing route to com-us.wfw.warface.com [172.99.95.228]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms XiaoQiang [192.168.1.1]
2 3 ms 4 ms 3 ms 3.229.55.182.in-addr.arpa [182.55.229.3]
3 3 ms 3 ms 3 ms 65.44.90.183.in-addr.arpa [183.90.44.65]
4 5 ms 4 ms 4 ms 9.44.90.183.in-addr.arpa [183.90.44.9]
5 3 ms 3 ms 2 ms 229.34.117.203.in-addr.arpa [203.117.34.229]
6 3 ms 3 ms 3 ms 77.35.117.203.in-addr.arpa [203.117.35.77]
7 4 ms 3 ms 2 ms six2utli2.starhub.net.sg [203.117.34.14]
8 186 ms 185 ms 185 ms xe-7-0-0.edge1.LosAngeles6.Level3.net [4.26.0.73]
9 * * * Request timed out.
10 249 ms 249 ms 249 ms 54.145.59.4.in-addr.arpa [4.59.145.54]
11 * * * Request timed out.
12 249 ms 249 ms 249 ms corea-dcpe2.iad3.rackspace.net [69.20.2.169]
13 253 ms 253 ms 253 ms corea-core8.iad3.rackspace.net [69.20.2.99]
14 248 ms 248 ms 248 ms core8-aggr501a-3.iad3.rackspace.net [72.4.122.215]
15 252 ms 252 ms 252 ms 228.95.99.172.in-addr.arpa [172.99.95.228]

Trace complete.

Alumni (Retired)

Re: Gface Warface latency issue

Hi @i1magic,

 

Are you still facing a issue with connectivity to Warface? If yes, do PM us your account and email address details and we will be in touch. Thanks


Some of my posts are unofficial and may contain personal opinions which may not represent the positions and opinions of StarHub.

If my post answers your question, please click on the "Accept as Solution" button!