Random zones with huge latency spikes

It happens on both Texas and DC. some areas are ok and some areas constantly freeze. Maybe a map will be fine then I'll enter a mirage and it will keep freezing or maybe it will do it when I get back to the map from the mirage. It seems like if it's happening if I change zones them come back, then it stops. Here is a shot of when it was happening in my hideout.







|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| router.home.local - 0 | 93 | 93 | 0 | 0 | 1 | 0 |
| 38.130.58.1 - 0 | 93 | 93 | 6 | 20 | 69 | 9 |
| 10.136.118.17 - 2 | 89 | 88 | 6 | 19 | 55 | 8 |
| 10.1.255.177 - 2 | 89 | 88 | 6 | 21 | 67 | 13 |
| 10.136.222.9 - 3 | 86 | 84 | 13 | 32 | 103 | 24 |
| 74.118.201.232 - 2 | 89 | 88 | 9 | 24 | 65 | 13 |
| 74.118.201.210 - 2 | 89 | 88 | 10 | 26 | 69 | 23 |
| 74.118.201.192 - 2 | 89 | 88 | 10 | 25 | 67 | 18 |
| e0-52.switch2.stl2.he.net - 2 | 90 | 89 | 9 | 17 | 97 | 12 |
| port-channel11.core1.stl1.he.net - 3 | 86 | 84 | 8 | 21 | 89 | 9 |
| port-channel15.core3.mci3.he.net - 0 | 93 | 93 | 14 | 28 | 87 | 16 |
| port-channel10.core4.dal1.he.net - 68 | 25 | 8 | 27 | 32 | 45 | 45 |
| 206.223.119.188 - 4 | 82 | 79 | 24 | 35 | 92 | 28 |
| 173.233.144.213 - 3 | 86 | 84 | 24 | 28 | 62 | 28 |
| se-us01-l63-r1.servers.com - 20 | 51 | 41 | 25 | 63 | 996 | 26 |
| 64.87.48.244 - 2 | 89 | 88 | 25 | 39 | 107 | 33 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

"

Necrogue#4186 wrote:

| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| router.home.local - 0 | 93 | 93 | 0 | 0 | 1 | 0 |
| 38.130.58.1 - 0 | 93 | 93 | 6 | 20 | 69 | 9 |
| 10.136.118.17 - 2 | 89 | 88 | 6 | 19 | 55 | 8 |
| 10.1.255.177 - 2 | 89 | 88 | 6 | 21 | 67 | 13 |

Your log is < 20% of the requested size and already shows persistent packet loss throughout the file.

It may be worth showing Wisper's support team this log in its entirety tomorrow.

"

Sarno#0493 wrote:

"

Necrogue#4186 wrote:

| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| router.home.local - 0 | 93 | 93 | 0 | 0 | 1 | 0 |
| 38.130.58.1 - 0 | 93 | 93 | 6 | 20 | 69 | 9 |
| 10.136.118.17 - 2 | 89 | 88 | 6 | 19 | 55 | 8 |
| 10.1.255.177 - 2 | 89 | 88 | 6 | 21 | 67 | 13 |

Your log is < 20% of the requested size and already shows persistent packet loss throughout the file.

It may be worth showing Wisper's support team this log in its entirety tomorrow.

Here is a bigger log. Are you saying it's Whisper with the loss because down lower it says 75% for port-channel10.core4.dal1.he.net

You can also see in my screenshot my "ping -t" to google and it doesn't seem to have any problems.


|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| router.home.local - 0 | 2295 | 2295 | 0 | 0 | 17 | 0 |
| 38.130.58.1 - 1 | 2269 | 2262 | 5 | 14 | 355 | 14 |
| 10.136.118.17 - 1 | 2227 | 2209 | 6 | 14 | 285 | 9 |
| 10.1.255.177 - 1 | 2213 | 2191 | 6 | 17 | 425 | 12 |
| 10.136.222.9 - 2 | 2206 | 2182 | 11 | 32 | 553 | 25 |
| 74.118.201.232 - 2 | 2209 | 2186 | 8 | 17 | 414 | 22 |
| 74.118.201.210 - 1 | 2227 | 2209 | 8 | 19 | 263 | 17 |
| 74.118.201.192 - 2 | 2210 | 2187 | 9 | 20 | 522 | 18 |
| e0-52.switch2.stl2.he.net - 2 | 2148 | 2109 | 9 | 17 | 440 | 15 |
| port-channel11.core1.stl1.he.net - 2 | 2199 | 2173 | 8 | 18 | 494 | 18 |
| port-channel15.core3.mci3.he.net - 2 | 2134 | 2092 | 13 | 26 | 3249 | 16 |
| port-channel10.core4.dal1.he.net - 75 | 578 | 145 | 24 | 40 | 447 | 27 |
| 206.223.119.188 - 3 | 2089 | 2035 | 23 | 33 | 861 | 31 |
| 173.233.144.213 - 2 | 2182 | 2152 | 23 | 33 | 578 | 31 |
| se-us01-l63-r1.servers.com - 11 | 1608 | 1433 | 24 | 45 | 2940 | 47 |
| 64.87.48.244 - 2 | 2168 | 2134 | 23 | 33 | 605 | 26 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

"

Necrogue#4186 wrote:

Are you saying it's Whisper with the loss

Yes.

"

Necrogue#4186 wrote:

down lower it says 75% for port-channel10.core4.dal1.he.net

And lower than that again we see 3%. :)

Remember that we're interested in your connection to the server. Routers refusing to respond to your internet traffic is not, in itself, a problem - playing the game doesn't require that they process messages sent to them and reply; merely that they forward traffic on to other destinations.

"

Sarno#0493 wrote:

"

Necrogue#4186 wrote:

Are you saying it's Whisper with the loss

Yes.

"

Necrogue#4186 wrote:

down lower it says 75% for port-channel10.core4.dal1.he.net

And lower than that again we see 3%. :)

Remember that we're interested in your connection to the server. Routers refusing to respond to your internet traffic is not, in itself, a problem - playing the game doesn't require that they process messages sent to them and reply; merely that they forward traffic on to other destinations.

Now I remember some stops ignore pings. The lags are more than 3%. Look at this screenshot. You can see the latency is over 7000 but it's not showing in winmtr even though its the latest ip in the log. Could my POE client be corrupted?



This one shows 0% when there was a big lag that just happened.

"

Necrogue#4186 wrote:

The lags are more than 3%. Look at this screenshot. You can see the latency is over 7000 but it's not showing in winmtr even though it's the latest ip in the log.

Packet loss results in the client waiting for multiple entire seconds (thousands of ms) to receive an acknowledgment, not getting one, and then finally giving up and trying again.

"

Necrogue#4186 wrote:

Could my POE client be corrupted?

No.

"

Necrogue#4186 wrote:

This one shows 0% when there was a big lag that just happened.

That's not meaningful; the sample size is tiny.

"

Sarno#0493 wrote:

"

Necrogue#4186 wrote:

The lags are more than 3%. Look at this screenshot. You can see the latency is over 7000 but it's not showing in winmtr even though it's the latest ip in the log.

Packet loss results in the client waiting for multiple entire seconds (thousands of ms) to receive an acknowledgment, not getting one, and then finally giving up and trying again.

"

Necrogue#4186 wrote:

Could my POE client be corrupted?

No.

"

Necrogue#4186 wrote:

This one shows 0% when there was a big lag that just happened.

That's not meaningful; the sample size is tiny.

So you are saying a single dropped packet makes the client wait for seconds?

This is not happening at all with POE2