11 replies to this topic

[Dingo Battler]

Anyone experiencing this? The ping is 700+ to the NA server, so I can only play oceanic, and cannot play CW. This has been going on for the whole week. I'm based in Melbourne, with TPG.

[ShinVector]

Glad that SEA servers now exist huh ?

Faced similar issue last month and a half when a undersea cable break issue increase the latency from my SEA ISP to NA.

[Daidachi]

I would suggest running a trace - if your ISP is routing traffic via Sydney for some bizarro reason, it may well have been effected by the weather we've had in NSW the past week.

I mean I'd make a comment about fraudband, but anyone with half a clue already has similar issues with the shambolic state of the NBN delivery.

[Troutmonkey]

Daidachi, on 06 January 2016 - 01:30 AM, said:

I mean I'd make a comment about fraudband, but anyone with half a clue already has similar issues with the shambolic state of the NBN delivery.

Grumble grumble NBN....
https://delimiter.co...campaign=buffer

[MW222]

KBurn85, on 05 January 2016 - 11:19 PM, said:

Anyone experiencing this? The ping is 700+ to the NA server, so I can only play oceanic, and cannot play CW. This has been going on for the whole week. I'm based in Melbourne, with TPG.

This may help.

7 Reasons to Use a Third-Party DNS Service
http://www.howtogeek...ty-dns-service/

[Dingo Battler]

MW222, on 06 January 2016 - 04:33 PM, said:

This may help.

7 Reasons to Use a Third-Party DNS Service
http://www.howtogeek...ty-dns-service/

This made the problem slightly better. The ping has gone down to 500+, Any PGI employees looking at this?

[ShinVector]

KBurn85, on 06 January 2016 - 10:59 PM, said:

This made the problem slightly better. The ping has gone down to 500+, Any PGI employees looking at this?

Hmmm... DNS have no direct impact to network latency what so, ever..

Using a different DNS server can only do the following:
1. Make dns queries faster or slower. It depends on the performance and latency from you to the dns server.
2. Point you to a different IP address. Again can be faster or slowness...

This has little impact to gaming servers since their IP addresses are fixed.
One of few times dns can make a huge difference is when the server that you go to uses, Content Delivery Networks.
Affects things like downloading software patches by redirecting you to the closest ISP cache.

Edited by ShinVector, 06 January 2016 - 11:21 PM.

[MW222]

ShinVector, on 06 January 2016 - 11:20 PM, said:

Hmmm... DNS have no direct impact to network latency what so, ever..

Using a different DNS server can only do the following:
1. Make dns queries faster or slower. It depends on the performance and latency from you to the dns server.
2. Point you to a different IP address. Again can be faster or slowness...

This has little impact to gaming servers since their IP addresses are fixed.
One of few times dns can make a huge difference is when the server that you go to uses, Content Delivery Networks.
Affects things like downloading software patches by redirecting you to the closest ISP cache.

If it was a local PC issue the DNS change would not have made a difference. This shows the ISP may be throttling the connection, or there is degradation some where in the connection. A Trace route may point to bad link jump. You may also be able squeeze more out of the connection with DRTCIP.
http://www.dslreports.com/tools

Edited by MW222, 07 January 2016 - 10:21 PM.

[SmithMPBT]

I live in California and get a 100 ping on the North American servers. PGI told me a few years back there was a low quality internet hub on the route to their server causing this. Anyone got any ideas?

[ShinVector]

SmithMPBT, on 07 January 2016 - 03:11 PM, said:

I live in California and get a 100 ping on the North American servers. PGI told me a few years back there was a low quality internet hub on the route to their server causing this. Anyone got any ideas?

Ask you friends in the same area on the same and different ISPs to help you do ping tests.
This will help you find out which ISPs has the better connection to MWO.

I am mentioned to someone in the same ISP to do a ping test as well to verify if it is an ISP problem.
Else call the ISP tech support to troubleshoot.

[Dingo Battler]

Still having ultra-high ping. Tracert and Ping results:

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\GadToy>ping 198.27.73.207

Pinging 198.27.73.207 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 198.27.73.207:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

C:\Users\GadToy>ping 192.99.109.192

Pinging 192.99.109.192 with 32 bytes of data:
Reply from 192.99.109.192: bytes=32 time=295ms TTL=55
Reply from 192.99.109.192: bytes=32 time=294ms TTL=55
Reply from 192.99.109.192: bytes=32 time=299ms TTL=55
Reply from 192.99.109.192: bytes=32 time=296ms TTL=55

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

C:\Users\GadToy>ping 66.198.127.6

Pinging 66.198.127.6 with 32 bytes of data:
Reply from 66.198.127.6: bytes=32 time=313ms TTL=52
Reply from 66.198.127.6: bytes=32 time=311ms TTL=52
Reply from 66.198.127.6: bytes=32 time=311ms TTL=52
Reply from 66.198.127.6: bytes=32 time=311ms TTL=52

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

C:\Users\GadToy>ping 192.99.109.192

Pinging 192.99.109.192 with 32 bytes of data:
Reply from 192.99.109.192: bytes=32 time=293ms TTL=55
Reply from 192.99.109.192: bytes=32 time=294ms TTL=55
Reply from 192.99.109.192: bytes=32 time=294ms TTL=55
Reply from 192.99.109.192: bytes=32 time=294ms TTL=55

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

C:\Users\GadToy>traceit 192.99.109.192
'traceit' is not recognized as an internal or external command,
operable program or batch file.

C:\Users\GadToy>tracert 192.99.109.192

Tracing route to mwomercs.com [192.99.109.192]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms home.gateway.home.gateway [192.168.1.254]
2 23 ms 23 ms 23 ms 10.20.22-151.tpgi.com.au [10.20.22.151]
3 24 ms 23 ms 23 ms nme-apt-bur-agr1-Te2-3.tpgi.com.au [203.219.5.61
]
4 23 ms 28 ms 26 ms nme-apt-bur-crt2-te-gi-0-7-0-13.tpgi.com.au [203
.219.106.81]
5 40 ms 38 ms 39 ms 203-219-106-205.tpgi.com.au [203.219.106.205]
6 36 ms 35 ms 35 ms syd-sot-ken-int2-be-10.tpgi.com.au [203.219.35.4
]
7 242 ms 233 ms 239 ms ix-8-1-2-0.tcore2.SQN-San-Jose.as6453.net [64.86
.21.57]
8 281 ms 281 ms 280 ms if-29-2.tcore1.CT8-Chicago.as6453.net [64.86.21.
105]
9 * * * Request timed out.
10 297 ms 297 ms 297 ms bhs-g2-a9.qc.ca [198.27.73.89]
11 650 ms 637 ms 615 ms bhs-g5-a9.qc.ca [198.27.73.233]
12 294 ms 295 ms 295 ms mwomercs.com [192.99.109.192]

Trace complete.

[Cerberus_9]

11 650 ms 637 ms 615 ms bhs-g5-a9.qc.ca [198.27.73.233]

This looks suspicious to me. The fact it's almost what you are reporting your ping to be?
Run the trace again and see if it happens again.

I ran it myself but I didn't get the ping spike like that.

It might have been a coincidence but it's best to test it.