Getting a lot of High Ping Spikes

the_syco

Hey all,
Getting loads of high ping spikes, hitting 999 at times. Usual ping on most UK servers would be around 70 or so, but for no reason it's being hitting 999 lately, causing me to get kicked out of the game. I've opened up the relevant ports in port forwarding on my F1000 router, but still getting them.

Usual:


Ping Spike:


I did get a new motherboard, CPU, RAM, and graphics card lately, but I had a few days smooth gaming before this kicked in, so I don't think it is caused by the hardware upgrade.

This happens in game, but also happens whilst I'm just looking at the server page, thus I don't know why it's happening. I'm hoping a patch comes out that fixes this shortly....

Spear

That's not a matter of high ping, that's packet loss which has different implications.

Unfortunately, I don't suppose you're in a position to capture a traceroute to the server?

Sparks

Packet loss during really bad windstorms - maybe some actual physical effect if you're in a really rural sort of area where you're still going over telephone wires on poles instead of FTTH or FTTC or something like that?

the_syco

In Leixlip, on 50meg Fiber, so I'd assume the connection was somewhat decent.

Line Attenuation: 19.4 dB/ 22.6 dB

Got the server IP from here.

C:\>tracert 173.199.79.197

Tracing route to 173.199.79.197.choopa.net [173.199.79.197]
over a maximum of 30 hops:

1 <1 ms <1 ms 1 ms 192.168.1.254
2 23 ms 23 ms 35 ms 95.45.46.1
3 24 ms 23 ms 23 ms 86.43.10.177
4 30 ms 26 ms 26 ms tenge-4-1-1.core2.bdt.core.eircom.net [86.43.252.97]
5 24 ms 24 ms 23 ms ge0-0-0.peering1.csg.dublin.eircom.net [86.43.245.78]
6 24 ms 93 ms 40 ms 195.16.170.41
7 26 ms 28 ms 25 ms ae-0-4.bar1.Dublin1.Level3.net [4.69.153.237]
8 37 ms 39 ms 38 ms 4.69.153.229
9 38 ms 35 ms 36 ms ae-59-114.csw1.London1.Level3.net [4.69.153.126]

10 36 ms 35 ms 35 ms ae-121-3507.edge4.London1.Level3.net [4.69.166.9]
11 40 ms 36 ms 36 ms 195.50.122.158
12 36 ms 36 ms 35 ms 173.199.79.197.choopa.net [173.199.79.197]

Trace complete.

C:\>tracert 173.199.79.197

Tracing route to 173.199.79.197.choopa.net [173.199.79.197]
over a maximum of 30 hops:

1 <1 ms <1 ms 1 ms 192.168.1.254
2 30 ms 23 ms 23 ms 95.45.46.1
3 23 ms 23 ms 23 ms 86.43.10.177
4 24 ms 46 ms 26 ms tenge-4-1-1.core2.bdt.core.eircom.net [86.43.252.97]
5 25 ms 24 ms 24 ms ge0-0-0.peering1.csg.dublin.eircom.net [86.43.245.78]
6 24 ms 24 ms 24 ms 195.16.170.41
7 * 24 ms 25 ms ae-0-4.bar1.Dublin1.Level3.net [4.69.153.237]
8 36 ms 36 ms 37 ms 4.69.153.229
9 36 ms 35 ms 35 ms ae-59-114.csw1.London1.Level3.net [4.69.153.126]

10 35 ms 35 ms 35 ms ae-121-3507.edge4.London1.Level3.net[4.69.166.9]
11 36 ms 36 ms 36 ms 195.50.122.158
12 36 ms 37 ms 36 ms 173.199.79.197.choopa.net [173.199.79.197]

Trace complete.

C:\>tracert 173.199.79.197

Tracing route to 173.199.79.197.choopa.net [173.199.79.197]
over a maximum of 30 hops:

1 <1 ms 1 ms <1 ms 192.168.1.254
2 25 ms 23 ms 34 ms 95.45.46.1
3 24 ms 23 ms 23 ms 86.43.10.177
4 24 ms 24 ms 24 ms tenge-4-1-1.core2.bdt.core.eircom.net [86.43.252.97]
5 23 ms 24 ms 23 ms ge0-0-0.peering1.csg.dublin.eircom.net[86.43.245.78]
6 23 ms 24 ms 24 ms 195.16.170.41
7 * 25 ms 26 ms ae-0-4.bar1.Dublin1.Level3.net [4.69.153.237]
8 37 ms 36 ms 37 ms 4.69.153.229
9 35 ms 36 ms 36 ms ae-59-114.csw1.London1.Level3.net [4.69.153.126]

10 35 ms 36 ms 35 ms ae-121-3507.edge4.London1.Level3.net [4.69.166.9]
11 63 ms 41 ms 36 ms 195.50.122.158
12 36 ms 36 ms 35 ms 173.199.79.197.choopa.net [173.199.79.197]

Trace complete.

C:\>tracert 173.199.79.197

Tracing route to 173.199.79.197.choopa.net [173.199.79.197]
over a maximum of 30 hops:

1 <1 ms 1 ms <1 ms 192.168.1.254
2 23 ms 23 ms 29 ms 95.45.46.1
3 25 ms 28 ms 26 ms 86.43.10.177
4 25 ms 24 ms 24 ms tenge-4-1-1.core2.bdt.core.eircom.net [86.43.252.97]
5 24 ms 30 ms 23 ms ge0-0-0.peering1.csg.dublin.eircom.net [86.43.245.78]
6 24 ms 24 ms 24 ms 195.16.170.41
7 * 24 ms 25 ms ae-0-4.bar1.Dublin1.Level3.net [4.69.153.237]
8 44 ms 36 ms 36 ms 4.69.153.229
9 36 ms 36 ms 36 ms ae-59-114.csw1.London1.Level3.net [4.69.153.126]

10 36 ms 36 ms 37 ms ae-121-3507.edge4.London1.Level3.net [4.69.166.9]
11 36 ms 36 ms 36 ms 195.50.122.158
12 36 ms 37 ms 36 ms 173.199.79.197.choopa.net [173.199.79.197]

Trace complete.

Spear

the_syco wrote: »

In Leixlip, on 50meg Fiber, so I'd assume the connection was somewhat decent.

Line Attenuation: 19.4 dB/ 22.6 dB

Got the server IP from here.

Hmm, those all seem clean and stable at least.

the_syco

Spear wrote: »

Hmm, those all seem clean and stable at least.

Got a nice dirty one

C:\>tracert 173.199.79.197

Tracing route to 173.199.79.197.choopa.net [173.199.79.197]
over a maximum of 30 hops:

1 1 ms <1 ms 1 ms 192.168.1.254
2 34 ms 45 ms 23 ms 95.45.46.1
3 23 ms 23 ms 23 ms 86.43.10.177
4 55 ms 24 ms 24 ms tenge-4-1-1.core2.bdt.core.eircom.net [86.43.252.97]
5 23 ms 24 ms 23 ms ge0-0-0.peering1.csg.dublin.eircom.net [86.43.245.78]
6 33 ms * 128 ms 195.16.170.41
7 * 25 ms 25 ms ae-0-4.bar1.Dublin1.Level3.net [4.69.153.237]
8 37 ms 36 ms 37 ms 4.69.153.229
9 35 ms 35 ms 36 ms ae-59-114.csw1.London1.Level3.net [4.69.153.126]

10 35 ms 35 ms 35 ms ae-121-3507.edge4.London1.Level3.net [4.69.166.9]
11 408 ms * 37 ms 195.50.122.158
12 36 ms 36 ms 36 ms 173.199.79.197.choopa.net [173.199.79.197]

Trace complete.

It seems to pause at hop 6 for some time, and sometimes a mini pause at hop 7, and this causes a spike at hop 11 (see the 2nd of three above, in the OP), and in the below, at hop 12;

C:\>tracert 173.199.79.197

Tracing route to 173.199.79.197.choopa.net [173.199.79.197]
over a maximum of 30 hops:

1 <1 ms <1 ms 1 ms 192.168.1.254
2 37 ms 23 ms 48 ms 95.45.46.1
3 23 ms 23 ms 23 ms 86.43.10.177
4 24 ms 26 ms 24 ms tenge-4-1-1.core2.bdt.core.eircom.net [86.43.252.97]
5 24 ms 23 ms 24 ms ge0-0-0.peering1.csg.dublin.eircom.net [86.43.245.78]
6 24 ms 24 ms 24 ms 195.16.170.41
7 * 25 ms 24 ms ae-0-4.bar1.Dublin1.Level3.net [4.69.153.237]
8 37 ms 36 ms 37 ms 4.69.153.229
9 35 ms 36 ms 35 ms ae-59-114.csw1.London1.Level3.net [4.69.153.126]

10 35 ms 35 ms 36 ms ae-121-3507.edge4.London1.Level3.net [4.69.166.9]
11 36 ms 36 ms 36 ms 195.50.122.158
12 150 ms 56 ms 64 ms 173.199.79.197.choopa.net [173.199.79.197]

Trace complete.

Spear

the_syco wrote: »

Got a nice dirty one

It seems to pause at hop 6 for some time, and sometimes a mini pause at hop 7, and this causes a spike at hop 11 (see the 2nd of three above, in the OP), and in the below, at hop 12;

The pause could just be an attempt to do a reverse DNS lookup at that point. ICMP traffic is inherently deprioritised by the big iron routers used at that level, so the odd high value or a complete drop of the ICMP packets is normal.

the_syco

Spear wrote: »

The pause could just be an attempt to do a reverse DNS lookup at that point. ICMP traffic is inherently deprioritised by the big iron routers used at that level, so the odd high value or a complete drop of the ICMP packets is normal.

Seems the pause didn't happen this time at 5 and 6, although the ping was higher.

C:\>tracert 173.199.79.197

Tracing route to 173.199.79.197.choopa.net [173.199.79.197]
over a maximum of 30 hops:

1 <1 ms 1 ms <1 ms 192.168.1.254
2 23 ms 24 ms 23 ms 95.45.46.1
3 24 ms 24 ms 24 ms 86.43.10.177
4 24 ms 25 ms 24 ms tenge-4-1-1.core2.bdt.core.eircom.net [86.43.252.97]
5 119 ms 138 ms 37 ms ge0-0-0.peering1.csg.dublin.eircom.net [86.43.245.78]
6 109 ms * * 195.16.170.41
7 24 ms 25 ms * ae-0-4.bar1.Dublin1.Level3.net [4.69.153.237]
8 38 ms 35 ms 37 ms 4.69.153.229
9 36 ms 35 ms 36 ms ae-59-114.csw1.London1.Level3.net [4.69.153.126]

10 36 ms 35 ms 35 ms ae-121-3507.edge4.London1.Level3.net [4.69.166.9]
11 39 ms * 36 ms 195.50.122.158
12 282 ms 66 ms 57 ms 173.199.79.197.choopa.net [173.199.79.197]

Trace complete.

Seems the problem is not on any set hop, as hop 7 is showing a high ping;

7 124 ms 26 ms 35 ms ae-0-4.bar1.Dublin1.Level3.net [4.69.153.237]

And in another tracert, hops 9 and 11 suffered;

9 211 ms 48 ms 59 ms ae-59-114.csw1.London1.Level3.net [4.69.153.126]

10 72 ms 97 ms 82 ms ae-121-3507.edge4.London1.Level3.net [4.69.166.9]
11 107 ms 81 ms 213 ms 195.50.122.158

Do you think when the bad weather stops, it should go back to normal?

On the server that I was playing on, continued breaches of a 180 ping would have me kicked, but it would happen over the space of 5 to 10 minutes, so it looks like the following high pings every so often that would cause this.

C:\>tracert 173.199.79.197

Tracing route to 173.199.79.197.choopa.net [173.199.79.197]
over a maximum of 30 hops:

1 <1 ms <1 ms 1 ms 192.168.1.254
2 24 ms 50 ms 23 ms 95.45.46.1
3 203 ms 309 ms 23 ms 86.43.10.177
4 25 ms 24 ms 24 ms tenge-4-1-1.core2.bdt.core.eircom.net [86.43.252.97]
5 23 ms 24 ms 23 ms ge0-0-0.peering1.csg.dublin.eircom.net [86.43.245.78]
6 24 ms 24 ms 24 ms 195.16.170.41
7 299 ms 152 ms 153 ms ae-0-4.bar1.Dublin1.Level3.net [4.69.153.237]
8 36 ms 36 ms 35 ms 4.69.153.229
9 36 ms 36 ms 35 ms ae-59-114.csw1.London1.Level3.net [4.69.153.126]

10 57 ms 35 ms 35 ms ae-121-3507.edge4.London1.Level3.net [4.69.166.9]
11 36 ms 36 ms 36 ms 195.50.122.158
12 35 ms 36 ms 36 ms 173.199.79.197.choopa.net [173.199.79.197]

Trace complete.

Spear

the_syco wrote: »

Seems the pause didn't happen this time at 5 and 6, although the ping was higher.



Seems the problem is not on any set hop, as hop 7 is showing a high ping;


And in another tracert, hops 9 and 11 suffered;


Do you think when the bad weather stops, it should go back to normal?

On the server that I was playing on, continued breaches of a 180 ping would have me kicked, but it would happen over the space of 5 to 10 minutes, so it looks like the following high pings every so often that would cause this.

What's the complete line stats from your modem? Water could have gotten into the local part of the phone line.

the_syco

Spear wrote: »

What's the complete line stats from your modem? Water could have gotten into the local part of the phone line.

Would the following be my line stats?

============================================================================
VDSL Training Status: Showtime
Mode: VDSL2 Annex B
VDSL Profile: Profile 17a
Traffic Type: PTM Mode
Link Uptime: 24 days: 5 hours: 59 minutes
============================================================================
VDSL Port Details Upstream Downstream
Line Rate: 15.417 Mbps 50.268 Mbps
Actual Net Data Rate: 15.359 Mbps 50.170 Mbps
Trellis Coding: ON ON
SNR Margin: 11.5 dB 10.4 dB
Actual Delay: 7 ms 8 ms
Transmit Power: 1.8 dBm 12.5 dBm
Receive Power: -17.6 dBm -10.1 dBm
Actual INP: 2.0 symbols 3.0 symbols
Total Attenuation: 19.4 dB 22.6 dB
Attainable Net Data Rate: 24.587 Mbps 72.468 Mbps
============================================================================
VDSL Band Status U0 U1 U2 U3 D1 D2 D3
Line Attenuation(dB): 4.8 26.8 40.2 N/A 14.2 34.5 53.7
Signal Attenuation(dB): 4.8 25.9 39.0 N/A 18.6 34.2 53.6
SNR Margin(dB): 11.4 11.5 11.5 N/A 10.4 10.4 10.4
Transmit Power(dBm):-13.2 - 3.5 0.1 N/A 8.3 7.8 6.9
============================================================================

Cuddlesworth

Spear wrote: »

The pause could just be an attempt to do a reverse DNS lookup at that point. ICMP traffic is inherently deprioritised by the big iron routers used at that level, so the odd high value or a complete drop of the ICMP packets is normal.

Or contention on the links to Level 3? Bad weather means more people staying home, coupled with a large increase in bandwidth to the customers(God knows if they actually upgraded anything else).

If there is contention, it might take them a while to respond to it.

Spear

Cuddlesworth wrote: »

Or contention on the links to Level 3? Bad weather means more people staying home, coupled with a large increase in bandwidth to the customers(God knows if they actually upgraded anything else).

If there is contention, it might take them a while to respond to it.

A sudden jump in the latencies at the peering point with give that away, those points aren't saturated.

Luck100

I was getting the 999 pings a few nights ago as well. I had to quit for the night and do something else. Seems okay since then.

MajesticDonkey

I was also getting this issue with a few nights. On some server's I'd get stuck on the Connecting stage (after "Logging in"). I'd have to restart my PC and everything would be fine after that.

the_syco

MajesticDonkey wrote: »

I was also getting this issue with a few nights. On some server's I'd get stuck on the Connecting stage (after "Logging in"). I'd have to restart my PC and everything would be fine after that.

The following command usually fixes the "connecting stage" problem (also requires a restart);

netsh winsock reset catalog

But it seems my problem was certain hops getting a high ping every few minutes, and thus getting kicked after maybe 5 minutes of gameplay at times.

Meh. Will be RMA'ing the new mobo as it's a tad bit bent, so hopefully all will be good by the time I get it back

jonski

the_syco wrote: »

Meh. Will be RMA'ing the new mobo as it's a tad bit bent, so hopefully all will be good by the time I get it back

Yikes !

Luck100

The dreaded 999 ping is back

Booted out of locker. Wasn't noticing any problems in game but I saw ping spiking up in battelog afterwards.

5uspect

Luck100 wrote: »

The dreaded 999 ping is back

Booted out of locker. Wasn't noticing any problems in game but I saw ping spiking up in battelog afterwards.

I have it too.

dreamers75

Getting low pings to serious lag the last few days.

carti2k

For me, I can't even join a multiplayer session: "disconnected to EA Online". GOD WHY?!

5uspect

I've found a solution; I've stopped playing. It was just too painful.