test content
Logo
What is the Arc Client?
Install Arc
Options
Horrendous Lag since Summer Event started
joccat
Member Posts: 117 Arc User
I am constantly thrown around like a ping pong ball every time I 
1. Log in with a new character
2. Join a group in a dungeon, etc.
3. Change zones or instances
This lag lasts 2 - 5 min each time and then settles down and is playable. I am on a 50mb fiber line and when this has happened, have jumped on a laptop to run a tracert to the patch servers....always one of the servers around hop 28 or 29 is not responding.....so this is not on my end.
Are you aware of this issue or not? Can we expect any kind of resolution in the near future?
Do you intend to reply about this or should I try and maybe contact your data center?
Signed...
A Very Frustrated Player
1. Log in with a new character
2. Join a group in a dungeon, etc.
3. Change zones or instances
This lag lasts 2 - 5 min each time and then settles down and is playable. I am on a 50mb fiber line and when this has happened, have jumped on a laptop to run a tracert to the patch servers....always one of the servers around hop 28 or 29 is not responding.....so this is not on my end.
Are you aware of this issue or not? Can we expect any kind of resolution in the near future?
Do you intend to reply about this or should I try and maybe contact your data center?
Signed...
A Very Frustrated Player
0
Comments
This only seems to happen immediatly after switching characters, instances, joining groups.....soon as I attempt one of those things my character is locked in place, lagging terribly. After about 2-5 min I am able to move, invoke, etc. and all seems fine.
Infortunately I am unable to run any group content as I just lag while everyone else does their thing. Last straw was attempting to do an etos run and as soon as I logged into the group, I lagged right off the cliff ad died.....totally useless right now in this state.
does this happen to anyone else?
There could be someone else causes it, so they would not be aware and cannot provide resolution. So, it may not be on your end, but that doesn't necessarily means that it is on Cryptics end either.
They won't reply, you haven't provided any evidence that they should, and good luck contacting the data center.
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Windows\system32>tracert patchserver.crypticstudios.com
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 18 ms 15 ms 1 ms 192.168.1.1
2 16 ms 31 ms 13 ms 112.201.0.1.pldt.net [112.201.0.1]
3 19 ms 12 ms 26 ms 122.2.175.174.static.pldt.net [122.2.175.174]
4 32 ms 28 ms 29 ms 210.213.133.134.static.pldt.net [210.213.133.134
]
5 41 ms 29 ms 35 ms 122.2.175.30.static.pldt.net [122.2.175.30]
6 66 ms 31 ms 33 ms 210.213.130.170.static.pldt.net [210.213.130.170
]
7 237 ms 172 ms 247 ms te0-2-0-25.ccr41.lax04.atlas.cogentco.com [38.88
.197.145]
8 220 ms 185 ms 262 ms be2965.ccr22.lax01.atlas.cogentco.com [154.54.45
.1]
9 263 ms 222 ms 197 ms be2932.ccr22.phx02.atlas.cogentco.com [154.54.45
.161]
10 267 ms 451 ms 327 ms be2930.ccr21.elp01.atlas.cogentco.com [154.54.42
.78]
11 239 ms 324 ms 219 ms be2927.ccr41.iah01.atlas.cogentco.com [154.54.29
.221]
12 224 ms 219 ms 226 ms be2687.ccr41.atl01.atlas.cogentco.com [154.54.28
.69]
13 249 ms 245 ms 248 ms be2112.ccr41.dca01.atlas.cogentco.com [154.54.7.
157]
14 242 ms 246 ms 241 ms be2806.ccr41.jfk02.atlas.cogentco.com [154.54.40
.105]
15 244 ms 251 ms 259 ms be2094.ccr31.bos01.atlas.cogentco.com [154.54.30
.14]
16 245 ms 249 ms 246 ms te0-0-1-0.rcr11.b002133-1.bos01.atlas.cogentco.c
om [154.54.46.134]
17 247 ms 244 ms 248 ms 38.111.40.114
18 241 ms 254 ms 238 ms 198.49.243.253
19 * * * Request timed out.
20 242 ms 239 ms 237 ms patchserver2.crypticstudios.com [208.95.185.41]
Trace complete.
Dunno if that helps at all, but its always the same timing out near the end - so no idea who's server that is.
What you are forgetting is that your PS4 connects to Sony, then Cryptic. Your PC does not, so it may take a totally different route.
On this route, Request timed out doesn't necessarily mean a delay, it likely means that machine does not respond to ICMP packets (Many machines no longer respond to Pings and Traceroutes, unfortunately). The biggest delays are at Hop 10 & 11 in Cogentco. Hop 17 is still Cogent, Cryptic doesn't start until hop 18.
Cryptic should check whatever machine is responsible for hop 19 anyways. Since you used the approved server for testing, the machine at hop 19 should be responding to packets.