Lag spikes

The problem happens immediately.
This is the first two lines of your WinMTR results:

| 192.168.0.1 - 0 | 523 | 523 | 0 | 0 | 1 | 0 |

| 10.1.55.1 - 1 | 519 | 518 | 1 | 8 | 155 | 1 |

The numbers I underlined are BAD. You shouldn't have packet loss, or jumps in latency right away like you have.

I suggest you start with the basics first. Turn off your modem and your router for 30 seconds. Turn them both back on again and run the test again. It looks like to problem is in your home network.

You are still seeing problems before your data even makes it out past your ISP network:
| 10.1.55.1 - 1 | 959 | 958 | 1 | 5 | 100 | 1 |

That is your second hop. You have packet loss, which is bad. You are also seeing latency spikes ( in this case up to 100ms ). Every hop things get worse for latency. I think you may need to do more troubleshooting on your local network. What is your current configuration? What's the model of your router and modem?

If you can't even get reliable traffic out of your house, it's going to make games like PoE ( which rely heavily on a solid internet connection ) very difficult to play.

There may be secondary problems to deal with, but You've got to deal with the quality of data coming out of your house.

"

rottedtotem wrote:

ping problems began with the Darkshire event. I've been playing more than 10 months and never had problems until the event , there it all started. I have no problems with other games , Wildstar , guild wars 2 , wow .

This is a local problem. The minute data tries to get past your router, you start seeing latency spikes at every single hop. Perhaps you don't notice the problem in other games as much, but that doesn't mean there isn't a problem. This problem is unrelated to any changes that occurred during the Darkshire event.

If you want to confirm this, try running WinMTR tests to other locations. However, to be clear, this is a problem at your location. You should NOT see spikes in latency over 100ms before data even leaves your house.

Here are your last results:
| 192.168.0.1 - 0 | 963 | 963 | 0 | 0 | 1 | 0 | - Your router

| 10.1.55.1 - 1 | 959 | 958 | 1 | 5 | 100 | 1 | - Immediately after your router you are getting spikes this is where the problem starts

| 10.232.8.1 - 1 | 959 | 958 | 2 | 31 | 608 | 5 | - It gets worse

| 10.230.1.1 - 1 | 959 | 958 | 3 | 31 | 610 | 5 | - each of these are bad

| 10.0.1.94 - 1 | 959 | 958 | 3 | 31 | 607 | 8 | - each of these are bad

| 10.0.1.59 - 1 | 959 | 958 | 3 | 31 | 611 | 6 | - each of these are bad

| 41.52.14.62.static.jazztel.es - 1 | 951 | 948 | 4 | 37 | 608 | 8 | - each of these are bad

| 97.216.106.212.static.jazztel.es - 2 | 905 | 890 | 13 | 40 | 560 | 15 | - each of these are bad

| 253.216.106.212.static.jazztel.es - 1 | 955 | 953 | 12 | 42 | 613 | 15 | - each of these are bad

| 142.216.106.212.static.jazztel.es - 1 | 952 | 949 | 47 | 76 | 634 | 48 | - each of these are bad

| bbr01.lon01.networklayer.com - 1 | 952 | 949 | 46 | 73 | 554 | 48 | --This is where data is moved towards the Frankfurt Gateway. By this point your average latency is beyond a quality level, and the spikes make the performance unplayable. Before you even get to Frankfurt.

| ae0.bbr01.xn01.fra01.networklayer.com - 1 | 959 | 958 | 72 | 101 | 676 | 76 |

| ae5.dar01.fra02.networklayer.com - 1 | 959 | 958 | 73 | 101 | 662 | 76 |

| po1.fcr01a.fra02.networklayer.com - 1 | 955 | 953 | 78 | 107 | 680 | 81 |

| c4.52.7a9f.ip4.static.sl-reverse.com - 1 | 955 | 953 | 72 | 98 | 631 | 73 | - By the time your data reaches the destination packet loss, latency, and spikes mean you aren't getting much of a good connection.

Things I would suggest-
1- Bypass the router. Remove it entirely and run a test without a router. Run the cable that plugs into the WAN / Internet port on your router directly into your computer. Run WinMTR without the router. Let us know the results.
2- If this isn't possible, try a different router if you have access to one.
3- If you don't have access to another router, shut down all but the machine you are testing from. Only one computer running off the router, and perform a WinMTR test. If it is still bad, shut that computer down and run the test from a different machine. Essentially, use process of elimination to determine if there is a device on the network creating problems for your connection.