Hey I, know I, hope she don't crash.

[Gavin 971]

It's getting worse every day for me; same thing happening on both connections.

 

[Joey 5]

Any update from Devs about that?

[MaurizioAM 919]

Connection sucks lately. I cant even play.

[GoG 59]

Connection issues, lag issues, disconnection issues.  Unplayable.  4x Prem toons, large expensive deed, over many days without any official response to the issue starts making me feel ripped off.

 

At the very least address the issue with communication.  I'd accept: 

 

"Acknowledged, we're working on it, sorry, you're not getting any value (prem) back."

 

"No idea why it's happening"

 

"We know why it's happening but it's out of our hands until we change ISP"

 

...Anything.

 

First get the technical side working, THEN try to shape our gaming habits with new superfluous servers.

[Brash_Endeavors 4,735]

removed as I think I was confused.

Edited February 19, 2015 by Brash_Endeavors

[Gumbo 1,563]

It would appear I'm now being routed slightly different than before. Connection has been pretty solid.

 

New Routing

Tracing route to jenn001.game.wurmonline.com [148.251.21.205]
over a maximum of 30 hops:

  1     5 ms    14 ms    <1 ms  192.168.1.1
  2    13 ms    10 ms     9 ms  7.11.163.1
  3    13 ms    11 ms    11 ms  209.148.245.193
  4    13 ms    19 ms    11 ms  69.63.248.185
  5    22 ms    24 ms    23 ms  24.156.144.178
  6     *        *        *     Request timed out.
  7    22 ms    24 ms    23 ms  be2005.ccr41.ord01.atlas.cogentco.com [66.28.4.73]
  8   114 ms   115 ms   118 ms  be2079.ccr21.yyz02.atlas.cogentco.com [154.54.27.182]
  9   123 ms   113 ms   112 ms  be2090.ccr21.ymq02.atlas.cogentco.com [154.54.30.206]
 10   115 ms   113 ms   113 ms  be2384.ccr21.lpl01.atlas.cogentco.com [154.54.44.138]
 11   114 ms   115 ms   118 ms  be2182.ccr41.ams03.atlas.cogentco.com [154.54.77.245]
 12   120 ms   118 ms   121 ms  be2261.ccr41.fra03.atlas.cogentco.com [154.54.37.30]
 13   127 ms   127 ms   126 ms  be2228.ccr21.muc01.atlas.cogentco.com [154.54.38.50]
 14   129 ms   134 ms   130 ms  be2279.rcr21.nue01.atlas.cogentco.com [154.54.37.145]
 15   131 ms   130 ms   130 ms  te0-0-1-0.nr11.b040138-0.nue01.atlas.cogentco.com [154.25.0.10]
 16   140 ms   133 ms   132 ms  149.6.158.22
 17   133 ms   135 ms   131 ms  core12.hetzner.de [213.239.245.25]
 18   137 ms   137 ms   138 ms  core21.hetzner.de [213.239.245.30]
 19   135 ms   141 ms   135 ms  juniper3.rz20.hetzner.de [213.239.245.230]
 20   138 ms   137 ms   138 ms  hos-tr5.ex3k18.rz20.hetzner.de [213.239.239.198]
 21   143 ms   165 ms   141 ms  jenn001.game.wurmonline.com [148.251.21.205]

Trace complete.

 

Old Routing

 

Tracing route to jenn001.game.wurmonline.com [148.251.21.205]
over a maximum of 30 hops:

  1     7 ms    14 ms    <1 ms  192.168.1.1
  2    17 ms    16 ms     9 ms  7.11.163.1
  3    16 ms    11 ms    12 ms  209.148.245.193
  4    27 ms    15 ms    15 ms  69.63.248.173
  5    12 ms    19 ms    15 ms  69.63.248.181
  6    27 ms    37 ms    14 ms  24.156.144.117
  7    31 ms    33 ms    26 ms  van58-9-229-138.dynamic.rogerstelecom.net [209.148.229.138]
  8    40 ms    56 ms    28 ms  PAIX-NYC.init7.net [198.32.118.38]
  9    99 ms   120 ms   104 ms  r1lon1.core.init7.net [77.109.140.193]
 10     *        *        *     Request timed out.
 11   154 ms     *        *     gw-hetzner.init7.net [77.109.135.102]
 12     *      119 ms   122 ms  core11.hetzner.de [213.239.203.137]
 13   118 ms     *        *     core21.hetzner.de [213.239.245.222]
 14   120 ms   120 ms     *     juniper3.rz20.hetzner.de [213.239.245.230]
 15   120 ms     *        *     hos-tr2.ex3k18.rz20.hetzner.de [213.239.203.38]
 16   125 ms   149 ms     *     jenn001.game.wurmonline.com [148.251.21.205]
 17   130 ms     *      124 ms  jenn001.game.wurmonline.com [148.251.21.205]

Trace complete.

 

 

[LouisC 74]

Mine looks horrid, and wurm is sucking quite a bit. Those techno vikings at hetzner are not doing well.

 

Tracing route to jenn001.game.wurmonline.com [148.251.21.205]

over a maximum of 30 hops:

 

  1    <1 ms    <1 ms    <1 ms  192.168.200.1

  2    29 ms    22 ms    15 ms  cpe-065-188-200-001.triad.res.rr.com [65.188.200

.1]

  3    24 ms    21 ms    32 ms  gig0-3.gnboncsg-ubr2.triad.rr.com [24.28.229.157

]

  4    12 ms    12 ms    13 ms  cpe-024-028-255-002.triad.res.rr.com [24.28.255.

2]

  5    20 ms    16 ms    18 ms  be34.chrcnctr01r.southeast.rr.com [24.93.64.198]

 

  6    20 ms    27 ms    23 ms  bu-ether14.atlngamq46w-bcr00.tbone.rr.com [66.10

9.6.82]

  7    20 ms    19 ms    18 ms  0.ae5.pr0.atl20.tbone.rr.com [107.14.19.99]

  8     *        *        *     Request timed out.

  9   113 ms   112 ms     *     ae-4-90.edge7.Frankfurt1.Level3.net [4.69.154.20

3]

 10   112 ms   115 ms     *     ae-4-90.edge7.Frankfurt1.Level3.net [4.69.154.20

3]

 11   117 ms   175 ms   118 ms  195.16.162.254

 12   126 ms   121 ms   118 ms  core12.hetzner.de [213.239.245.25]

 13   125 ms   126 ms   122 ms  core21.hetzner.de [213.239.245.30]

 14   125 ms   125 ms   123 ms  juniper4.rz20.hetzner.de [213.239.245.242]

 15   127 ms   127 ms   126 ms  hos-tr4.ex3k18.rz20.hetzner.de [213.239.203.102]

 

 16   122 ms   122 ms   121 ms  jenn001.game.wurmonline.com [148.251.21.205]

 

Trace complete.

Edited February 24, 2015 by LouisC

[Alectrys 2,040]

Allright,

 

our investigations lead us to believe that there are issues with the nets leading to hetzner in that they throttle outbound or inbound traffic. We need you to contact us when this happens the next time at a large scale so we can create some statistics for Hetzner.

 

Please prepare by reading this.

>http://whatismyip.com)

 

We try to work normal office hours in Sweden so we will start by responding to this between 9 am and 16 pm CEST. We should be able to get enough interesting data that way.

We need to be able to ping your computer, so make sure it's possible to ping. You can test from for instance this site https://www.dotcom-tools.com/ping-test.aspx

 

Once you've emailed us, start pinging jenn001.game.wurmonline.com using the instructions above and email the result to the same address.

 

One of the ping servers at https://www.dotcom-tools.com/ping-test.aspx is based in Frankfurt, which may actually mean it's hosted by Hetzner.

 

Thanks!

 

Followed procedure and sent the info, posting here just for the record:  2:30 EST time

 

Tracing route to jenn001.game.wurmonline.com [148.251.21.205]

over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.0.1

  2    33 ms    27 ms    19 ms  cpe-104-229-240-1.twcny.res.rr.com [104.229.240.

1]

  3    27 ms    25 ms    21 ms  tge0-0-0.ltfdny0402h.northeast.rr.com [24.24.16.

129]

  4    14 ms    13 ms    11 ms  agg25.esyrnydr02r.northeast.rr.com [24.58.47.126

]

  5    18 ms    19 ms    19 ms  be27.albynyyf01r.northeast.rr.com [24.58.32.80]

  6    27 ms    27 ms    27 ms  bu-ether26.nycmny837aw-bcr00.tbone.rr.com [107.1

4.19.26]

  7    26 ms    24 ms    25 ms  0.ae0.pr1.nyc20.tbone.rr.com [107.14.17.216]

  8    27 ms    26 ms    25 ms  209.220.18.33.ptr.us.xo.net [209.220.18.33]

  9    31 ms    28 ms    25 ms  209.220.18.50.ptr.us.xo.net [209.220.18.50]

10    98 ms   100 ms    98 ms  r1lon2.core.init7.net [77.109.128.69]

11    94 ms    93 ms    99 ms  r1lon1.core.init7.net [82.197.168.41]

12   116 ms   122 ms   124 ms  r1nue1.core.init7.net [77.109.140.254]

13   120 ms   135 ms     *     gw-hetzner.init7.net [77.109.135.102]

14   123 ms   121 ms     *     core12.hetzner.de [213.239.245.25]

15   124 ms   123 ms   121 ms  core21.hetzner.de [213.239.245.30]

16   132 ms     *      122 ms  juniper3.rz20.hetzner.de [213.239.245.230]

17   122 ms     *        *     hos-tr2.ex3k18.rz20.hetzner.de [213.239.203.38]

18   125 ms   123 ms   125 ms  jenn001.game.wurmonline.com [148.251.21.205]

Trace complete.