Game currently unplayable- packet loss/latency

[eoh7678]

Is there some issue at the datacenter or edge network? The game is currently unplayable- interacting with objects takes 30+ seconds, crafting times out, all kinds of problems. Traceroute below:

Tracing route to 199.91.189.29 over a maximum of 30 hops

  1     1 ms     1 ms     1 ms  10.255.251.8
  2     2 ms   4 ms     9 ms  10.255.251.9
  3   4 ms   5 ms   3 ms  10.255.251.2
  4   3 ms   5 ms   8 ms  10.255.248.54
  5   6 ms   5 ms     4 ms  10.255.248.18
  6     6 ms     6 ms     6 ms  38.104.162.57
  7    13 ms    13 ms    13 ms  154.54.80.181
  8    21 ms    21 ms    21 ms  154.54.44.86
  9     *       98 ms    28 ms  154.54.31.54
 10    39 ms    42 ms    57 ms  154.54.30.206
 11    99 ms    35 ms    66 ms  38.122.42.34
 12   177 ms    78 ms     *     192.34.76.10
 13     *        *      124 ms  199.91.189.242
 14   102 ms     *        *     199.91.189.29
 15   118 ms    94 ms     *     199.91.189.29
 16   148 ms   117 ms   130 ms  199.91.189.29

Trace complete.

Ping for ~10 minutes shows 18% packet loss:

Ping statistics for 199.91.189.29:
    Packets: Sent = 653, Received = 529, Lost = 124 (18% loss),
Approximate round trip times in milli-seconds:
    Minimum = 34ms, Maximum = 160ms, Average = 77ms

[Diert]

I am experiencing the same issue. A constant ping to other sites and services shows no loss and no speed issues. Ping and speed tests all show normal. I only just started having this problem this morning.

[DancingFatman]

Yeah this is happening to me too.......

[Dyskord]

I am also experiencing this on the Coeurl world server. Curiously, it seemed worse when I was on the dungeon server, as I had several disconnections and extreme latency there. Smaller sample size, but my results are remarkably similar to eoh7678, showing about 17% packet loss

Ping statistics for 199.91.189.27:
Packets: Sent = 170, Received = 141, Lost = 29 (17% loss),
Approximate round trip times in milli-seconds:
Minimum = 29ms, Maximum = 136ms, Average = 51ms

My traceroute also shows a few issues, with timeouts occurring outside tier 1 locations, one of them even occurring on the world server itself:

Tracing route to 199.91.189.27 over a maximum of 30 hops

1 1 ms 1 ms 1 ms 192.168.0.1
2 3 ms 2 ms 3 ms CN1-DSL-208-102-224-1.fuse.net [208.102.224.1]
3 2 ms 2 ms 2 ms 172.17.122.34
4 3 ms 3 ms 2 ms WS-ZT-1.CIN1.core.fuse.net [216.68.14.52]
5 5 ms 2 ms 2 ms te0-0-2-0.nr11.b016343-1.cvg02.atlas.cogentco.co
m [38.122.234.33]
6 3 ms 3 ms 3 ms te0-0-1-1.rcr12.cvg02.atlas.cogentco.com [154.24
.0.129]
7 5 ms 5 ms 5 ms te3-1.ccr01.cmh02.atlas.cogentco.com [154.54.84.
174]
8 12 ms * * te0-7-0-35.ccr21.cle04.atlas.cogentco.com [154.5
4.44.77]
9 * 16 ms 17 ms be2596.ccr21.yyz02.atlas.cogentco.com [154.54.31
.54]
10 101 ms 82 ms 23 ms be2090.ccr21.ymq02.atlas.cogentco.com [154.54.30
.206]
11 * 66 ms * 38.122.42.34
12 * 26 ms 44 ms 192.34.76.10
13 51 ms 26 ms 56 ms 199.91.189.242
14 * 37 ms 29 ms 199.91.189.27

This started occurring for me around 2am Eastern time this morning, and seems to have become worse at this time, as the game is now entirely unplayable.

[Raist]

Looks like issues around the Psinet segment (part of Cogentco) in the D.C. area. Several ISP's had reports of problems in that area the past couple weeks. Verizon, TWC, AT&T, amongst others.

Need to get your tier3 techs on it.

[eoh7678]

Just as I finished setting up a VPN to try and approach from a different geographic location, it looks like they may have gotten the message and resolved the issue.

Haven't dropped a packet in the last 5 minutes, latency dropped to a uniform 34-35ms and am in-game playing smoothly.

Fingers crossed that this is truly resolved!

Tracing route to 199.91.189.29 over a maximum of 30 hops

  1     1 ms     2 ms     2 ms  10.255.251.8
  2     8 ms     7 ms     9 ms  10.255.251.9
  3     5 ms     8 ms     9 ms  10.255.251.2
  4     4 ms     8 ms     8 ms  10.255.248.54
  5     7 ms     8 ms     9 ms  10.255.248.18
  6     6 ms     5 ms     5 ms  te0-0-0-7.rcr21.stl03.atlas.cogentco.com [38.104.162.57]
  7    12 ms    13 ms    13 ms  be2349.ccr41.ord01.atlas.cogentco.com [154.54.80.181]
  8    21 ms    22 ms    21 ms  be2351.ccr21.cle04.atlas.cogentco.com [154.54.44.86]
  9    27 ms    27 ms    28 ms  be2596.ccr21.yyz02.atlas.cogentco.com [154.54.31.54]
 10    35 ms    36 ms    36 ms  be2090.ccr21.ymq02.atlas.cogentco.com [154.54.30.206]
 11    35 ms    36 ms    35 ms  38.122.42.34
 12    35 ms    74 ms    36 ms  192.34.76.10
 13    35 ms    35 ms    36 ms  199.91.189.242
 14    34 ms    36 ms    35 ms  199.91.189.29

Trace complete.

Ping statistics for 199.91.189.29:
    Packets: Sent = 323, Received = 323, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 34ms, Maximum = 41ms, Average = 34ms

[Whiteroom]

Had the same thing earlier. Lucky for me I had a capible and understanding group to get me through my daily ex.

It sure is hard holding aggro when it takes 2-3 tries to get every RoH combo off...