Ryzom

Below is a pingplot to where i was told to ping plot. as you can see, tis not a very great example of amazing conectivity. Lol

Help?

Oh and yes. port are open.

Target Name: rslogin.juk.shards.nevrax.com
IP: 83.141.21.136
Date/Time: 09/03/2007 02:53:25 to 09/03/2007 02:53:58

1 N/A 74 ms 1 ms 0 ms 0 ms 0 ms 1 ms 1 ms 0 ms 1 ms my.router [192.168.4.254]
2 N/A 133 ms 11 ms 12 ms * * * * * 12 ms l1.ar01.gs1.dsl.pipex.net [xx.xx.xx.xx]
3 N/A 90 ms 14 ms * * * * 11 ms 10 ms 11 ms ge-0-0-0-0.cr01.gs1.dsl.pipex.net [62.241.161.90]
4 N/A 58 ms 11 ms 12 ms * 25 ms * 11 ms 11 ms 11 ms g3-22-3802.cr05.tn5.bb.pipex.net [62.72.141.25]
5 N/A 20 ms 20 ms * 62 ms 25 ms * 19 ms 19 ms 19 ms te1-4.cr01.ixf.bb.pipex.net [62.72.137.250]
6 N/A 20 ms 19 ms 20 ms * 19 ms * * 19 ms 19 ms ge4-1-0-1000M.ar1.AMS1.gblx.net [195.69.144.80]
7 N/A 32 ms 140 ms * 31 ms * * 31 ms 30 ms 31 ms ge1-1-1000M.ar3.FRA3.gblx.net [67.17.94.33]
8 N/A 32 ms 31 ms * * * * * 32 ms 33 ms [64.209.100.186]
9 N/A 33 ms 32 ms 286 ms * 32 ms 31 ms * * 32 ms 83-141-21-136.gfsrv.net [83.141.21.136]

Ping statistics for rslogin.juk.shards.nevrax.com
Packets: Sent = 9, Received = 6, Lost = 3 (33.3%)
Round Trip Times: Minimum = 31ms, Maximum = 286ms, Average = 74ms

Target Name: rslogin.juk.shards.nevrax.com
IP: 83.141.21.136
Date/Time: 09/03/2007 02:59:39 to 09/03/2007 02:59:48

1 0 ms 1 ms 2 ms 0 ms 0 ms 1 ms 17 ms 10 ms 9 ms 7 ms my.router [192.168.4.254]
2 17 ms 11 ms 11 ms 21 ms * 22 ms 12 ms * * 11 ms l1.ar01.gs1.dsl.pipex.net [xx.xx.xx.xx]
3 11 ms 11 ms * 12 ms 11 ms * * * * 11 ms ge-0-0-0-0.cr01.gs1.dsl.pipex.net [62.241.161.90]
4 * * 11 ms * 11 ms * 35 ms 31 ms * 29 ms g3-22-3802.cr05.tn5.bb.pipex.net [62.72.141.25]
5 20 ms 20 ms 23 ms * 20 ms * 19 ms * * 19 ms te1-4.cr01.ixf.bb.pipex.net [62.72.137.250]
6 * * 27 ms * * * 19 ms * * 19 ms ge4-1-0-1000M.ar1.AMS1.gblx.net [195.69.144.80]
7 * * 31 ms 31 ms 31 ms * * 31 ms * 88 ms ge1-1-1000M.ar3.FRA3.gblx.net [67.17.94.33]
8 31 ms 32 ms 35 ms 31 ms 86 ms * 31 ms 32 ms * 45 ms [64.209.100.186]
9 * * * * * 34 ms 31 ms * 32 ms 32 ms 83-141-21-136.gfsrv.net [83.141.21.136]

Ping statistics for rslogin.juk.shards.nevrax.com

Packets: Sent = 10, Received = 4, Lost = 6 (60.0%)
Round Trip Times: Minimum = 31ms, Maximum = 34ms, Average = 32ms

Your PL seem especially bad... but we ALL feel it.

Please dont sweep this under the carpet, i played again tonight the ingame ticket was saying 34+ packet loss.

I need a solution, In fact. Lots of people need a solution. the problem is not my end, its not in the middle. its the GF side of things.

The problem is, is the fact on how one is routed to the servers. Upon the move I experience a better ping and no packet loss. I live in the US, however I ensure that the service I pay for with my ISP is the service I receive. Try making sure that you are given the bandwidth you pay for.

On another note, the hops your computer needs to go through to get to GameForge servers is also an issue, one that cannot be fixed by Gameforge, unfortunately, because they are not connected to the company. It seems that the packet loss you are receiving starts right in your own backyard as the loss of connection is shown directly after your private network is displayed - jump 2:

2 N/A 133 ms 11 ms 12 ms * * * * * 12 ms l1.ar01.gs1.dsl.pipex.net [xx.xx.xx.xx]

There is also some missing data when you finally connect to the Gameforge service, however, that is expected from the instability of your connection. As you can see, there is a corelation between the hops your ISP decides to route you through, and your gameplay, however, one depends on the other, and as much as we'd like to fix it ourselves, this is an issue which you'll need to call up your ISP's tech support as it may be faulty wiring in your neighborhood.

You can try to force a new route by resetting your modem, but being that your disruptions happen so close to your network, it is presumably bad hardware or wiring outside your house or in the neighborhood.