Problems with connection (R0) lag

[Azuvidexus]

What address do you guys use for ping and traceroute tests?

[Max_Ohm]

What address do you guys use for ping and traceroute tests?

If you open up your windows Task Manager, and open resource monitor, you will be able to locate the IP address of the server you are connecting to via the network statistics monitor. Just make sure you're playing when you access it.

[Azuvidexus]

If you open up your windows Task Manager, and open resource monitor, you will be able to locate the IP address of the server you are connecting to via the network statistics monitor. Just make sure you're playing when you access it.

I'm on PS3 :/

[Choyi]

Game is unplayable as of last 2 days, constant lagg spikes, now not only while inside instance but also while in town crafting and in the field gathering/questing, yesterdays maintanance just seems to have made things 10x worse.
Pinging the servers showed a request timeout happenign frequently, around every 3-4 pings it would timeout.

Is this being looked into and can we have any responce here?
Cause if this continues for much longer its absolutely no reason for me to stay subbed.

[Azakiah]

Game is unplayable as of last 2 days, constant lagg spikes, now not only while inside instance but also while in town crafting and in the field gathering/questing, yesterdays maintanance just seems to have made things 10x worse.
Pinging the servers showed a request timeout happenign frequently, around every 3-4 pings it would timeout.

Is this being looked into and can we have any responce here?
Cause if this continues for much longer its absolutely no reason for me to stay subbed.

What percentage of the player base is suffering from this right now, I wonder

[Berezo]

Great, can't wait to log on today and find that we are still having these issues. SE really should release a statement.

[Rache]

I am currently experiencing random lag spike lasting 3~5 seconds. Following is the tracert log to Gilgamesh.

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\USER>tracert 199.91.189.47

Tracing route to 199.91.189.47 over a maximum of 30 hops

1 84 ms 1 ms 1 ms
2 67 ms 50 ms 26 ms
3 20 ms 11 ms 10 ms
4 13 ms 15 ms 28 ms
5 15 ms 18 ms 18 ms he-5-2-0-0-11-cr01.ashburn.va.ibone.comcast.net[68.86.90.245]
6 15 ms 16 ms 18 ms be-11-pe04.ashburn.va.ibone.comcast.net [68.86.84.206]
7 21 ms 19 ms 19 ms as174.ashburn.va.ibone.comcast.net [66.208.229.142]
8 19 ms 37 ms 39 ms be2113.mpd21.dca01.atlas.cogentco.com [154.54.6.170]
9 43 ms 18 ms 21 ms te0-7-0-8.mpd21.jfk02.atlas.cogentco.com [154.54.5.97]
10 28 ms 37 ms 28 ms be2108.ccr21.ymq02.atlas.cogentco.com [154.54.3.134]
11 38 ms 30 ms 28 ms 38.122.42.34
12 * * * Request timed out.
13 112 ms * 67 ms 192.34.76.2
14 28 ms 29 ms 28 ms 199.91.189.234
15 28 ms 30 ms 67 ms 199.91.189.47

Trace complete.

C:\Users\USER>tracert 199.91.189.47

Tracing route to 199.91.189.47 over a maximum of 30 hops

1 1 ms <1 ms <1 ms
2 75 ms 25 ms 33 ms
3 10 ms 9 ms 31 ms
4 44 ms 14 ms 13 ms
5 17 ms 52 ms 57 ms he-5-4-0-0-11-cr01.ashburn.va.ibone.comcast.net[68.86.90.173]
6 15 ms 14 ms 15 ms be-11-pe04.ashburn.va.ibone.comcast.net [68.86.84.206]
7 20 ms 22 ms 20 ms as174.ashburn.va.ibone.comcast.net [66.208.229.142]
8 26 ms 42 ms 20 ms be2176.ccr21.dca01.atlas.cogentco.com [154.54.41.54]
9 19 ms 20 ms 24 ms te0-7-0-8.mpd21.jfk02.atlas.cogentco.com [154.54.5.97]
10 29 ms 28 ms 39 ms be2106.ccr21.ymq02.atlas.cogentco.com [154.54.3.50]
11 27 ms 30 ms 29 ms 38.122.42.34
12 * * * Request timed out.
13 54 ms 97 ms 95 ms 192.34.76.2
14 44 ms 27 ms 29 ms 199.91.189.234
15 * 109 ms 108 ms 199.91.189.47

Trace complete.

C:\Users\USER>tracert 199.91.189.47

Tracing route to 199.91.189.47 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms
2 32 ms 19 ms 27 ms
3 9 ms 46 ms 24 ms
4 13 ms 15 ms 13 ms
5 16 ms 19 ms 19 ms he-5-3-0-0-11-cr01.ashburn.va.ibone.comcast.net[68.86.93.137]
6 16 ms 18 ms 14 ms be-11-pe04.ashburn.va.ibone.comcast.net [68.86.84.206]
7 20 ms 20 ms 38 ms as174.ashburn.va.ibone.comcast.net [66.208.229.142]
8 25 ms 23 ms 21 ms be2176.ccr21.dca01.atlas.cogentco.com [154.54.41.54]
9 21 ms 18 ms 18 ms te0-7-0-2.ccr21.jfk02.atlas.cogentco.com [154.54.25.237]
10 33 ms 48 ms 32 ms be2106.ccr21.ymq02.atlas.cogentco.com [154.54.3.50]
11 28 ms 27 ms 28 ms 38.122.42.34
12 * * * Request timed out.
13 122 ms * 122 ms 192.34.76.2
14 33 ms 29 ms 28 ms 199.91.189.234
15 67 ms 62 ms 64 ms 199.91.189.47

Trace complete.

C:\Users\USER>tracert 199.91.189.47

Tracing route to 199.91.189.47 over a maximum of 30 hops

1 <1 ms <1 ms 1 ms
2 27 ms 27 ms 30 ms
3 10 ms 25 ms 11 ms
4 13 ms 16 ms 17 ms
5 16 ms 17 ms 20 ms he-5-2-0-0-10-cr01.ashburn.va.ibone.comcast.net[68.86.90.241]
6 15 ms 33 ms 16 ms be-11-pe04.ashburn.va.ibone.comcast.net [68.86.84.206]
7 29 ms 29 ms 27 ms as174.ashburn.va.ibone.comcast.net [66.208.229.142]
8 29 ms 28 ms 29 ms be2176.ccr21.dca01.atlas.cogentco.com [154.54.41.54]
9 33 ms 38 ms 34 ms te0-7-0-8.mpd21.jfk02.atlas.cogentco.com [154.54.5.97]
10 38 ms 37 ms 39 ms be2108.ccr21.ymq02.atlas.cogentco.com [154.54.3.134]
11 32 ms 34 ms 32 ms 38.122.42.34
12 * * * Request timed out.
13 * 118 ms 125 ms 192.34.76.2
14 29 ms 27 ms 29 ms 199.91.189.234
15 113 ms 110 ms 111 ms 199.91.189.47

Trace complete.

C:\Users\USER>
C:\Users\USER>tracert 199.91.189.47

Tracing route to 199.91.189.47 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms
2 36 ms 29 ms 29 ms
3 11 ms 9 ms 11 ms
4 13 ms 16 ms 14 ms
5 16 ms 17 ms 18 ms he-5-1-0-0-10-cr01.ashburn.va.ibone.comcast.net[68.86.91.13]
6 15 ms 14 ms 16 ms be-11-pe04.ashburn.va.ibone.comcast.net [68.86.84.206]
7 39 ms 39 ms 39 ms as174.ashburn.va.ibone.comcast.net [66.208.229.142]
8 39 ms 68 ms 39 ms be2176.ccr21.dca01.atlas.cogentco.com [154.54.41.54]
9 39 ms 39 ms 41 ms te0-7-0-2.ccr21.jfk02.atlas.cogentco.com [154.54.25.237]
10 45 ms 47 ms 48 ms be2108.ccr21.ymq02.atlas.cogentco.com [154.54.3.134]
11 50 ms 49 ms 49 ms 38.122.42.34
12 * * * Request timed out.
13 114 ms 115 ms 114 ms 192.34.76.2
14 28 ms 29 ms 28 ms 199.91.189.234
15 112 ms 184 ms * 199.91.189.47
16 147 ms * 110 ms 199.91.189.47

Trace complete.

C:\Users\USER>
C:\Users\USER>tracert 199.91.189.47

Tracing route to 199.91.189.47 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms
2 32 ms 29 ms 29 ms
3 10 ms 10 ms 11 ms
4 46 ms 13 ms 12 ms
5 17 ms 15 ms 14 ms he-5-2-0-0-11-cr01.ashburn.va.ibone.comcast.net
[68.86.90.245]
6 15 ms 13 ms 15 ms be-11-pe04.ashburn.va.ibone.comcast.net [68.86.84.206]
7 62 ms 71 ms 44 ms as174.ashburn.va.ibone.comcast.net [66.208.229.142]
8 29 ms 27 ms 42 ms be2113.mpd21.dca01.atlas.cogentco.com [154.54.6.170]
9 41 ms 42 ms 41 ms te0-7-0-8.mpd21.jfk02.atlas.cogentco.com [154.54.5.97]
10 38 ms 36 ms 45 ms be2106.ccr21.ymq02.atlas.cogentco.com [154.54.3.50]
11 40 ms 40 ms 40 ms 38.122.42.34
12 * * * Request timed out.
13 111 ms 112 ms 110 ms 192.34.76.2
14 28 ms 26 ms 27 ms 199.91.189.234
15 111 ms 110 ms 112 ms 199.91.189.47

Trace complete.

C:\Users\USER>
C:\Users\USER>tracert 199.91.189.47

Tracing route to 199.91.189.47 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms
2 36 ms 26 ms 29 ms
3 10 ms 9 ms 11 ms
4 14 ms 12 ms 11 ms
5 17 ms 34 ms 13 ms he-5-4-0-0-11-cr01.ashburn.va.ibone.comcast.net[68.86.90.173]
6 14 ms 14 ms 13 ms be-11-pe04.ashburn.va.ibone.comcast.net [68.86.84.206]
7 31 ms 31 ms 31 ms as174.ashburn.va.ibone.comcast.net [66.208.229.142]
8 39 ms 33 ms 43 ms be2113.mpd21.dca01.atlas.cogentco.com [154.54.6.170]
9 44 ms 57 ms 36 ms te0-7-0-8.mpd21.jfk02.atlas.cogentco.com [154.54.5.97]
10 44 ms 44 ms 43 ms be2106.ccr21.ymq02.atlas.cogentco.com [154.54.3.50]
11 39 ms 40 ms 40 ms 38.122.42.34
12 * * * Request timed out.
13 * 109 ms 111 ms 192.34.76.2
14 28 ms 28 ms 26 ms 199.91.189.234
15 111 ms 108 ms 45 ms 199.91.189.47

Trace complete.

C:\Users\USER>

I am no internet networking engineer but it seems the problem lies within SE data center & ISP?

[WickedTheory]

That's exactly what it is, the problem has been occurring or at least present from what I can see up to a month. I called my ISP, and they looked and checked up on anything they could and nothing seems out of place. My buddy got a tech out for him just yesterday morning, and the tech checked everything and was unable to find anything wrong. It's not a question if it's on SE's side or not, there is way to many people having this issue at the same exact time. My problem just occurred yesterday morning, and a few days before that having the same problem that went away until Oct.1. I am pretty sure we can agree the game is unplayable, and I am not here to be one of those people who blame the game for lags but it's also to the point where I cannot even fate grind without me getting little to no credit due to the 3-8 second delay. They need to get on this, a month late is better then never I suppose.

[Bensmack]

I can confirm the same/similar tracert findings, ran two tests and the higher pings/timeouts don't occur until the data center IP's or close to it.

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\..............>tracert 199.91.189.40

Tracing route to 199.91.189.40 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms
2 <1 ms <1 ms <1 ms 10.0.0.1
3 34 ms 22 ms 19 ms 24.99.165.1
4 12 ms 17 ms 8 ms xe-10-0-0-32767-sr02.k1winder.ga.atlanta.comcast
.net [68.85.173.249]
5 9 ms 10 ms 10 ms xe-0-0-0-0-sur01.k2gwinnett.ga.atlanta.comcast.n
et [68.85.109.77]
6 12 ms 16 ms 10 ms xe-1-0-2-0-ar01.b0atlanta.ga.atlanta.comcast.net
[68.85.232.125]
7 17 ms 12 ms 14 ms he-5-12-0-0-11-cr01.56marietta.ga.ibone.comcast.
net [68.86.95.197]
8 15 ms 16 ms 15 ms pos-0-2-0-0-pe01.56marietta.ga.ibone.comcast.net
[68.86.86.166]
9 24 ms 24 ms 34 ms te0-0-0-19.ccr21.atl02.atlas.cogentco.com [154.5
4.10.233]
10 26 ms 26 ms 26 ms be2052.mpd21.atl01.atlas.cogentco.com [154.54.40
.249]
11 26 ms 29 ms 27 ms te0-4-0-7.mpd21.dca01.atlas.cogentco.com [154.54
.25.249]
12 67 ms 59 ms 66 ms te0-0-0-20.mpd21.jfk02.atlas.cogentco.com [154.5
4.26.178]
13 68 ms 67 ms 67 ms be2106.ccr21.ymq02.atlas.cogentco.com [154.54.3.
50]
14 72 ms 72 ms 70 ms 38.122.42.34
15 * * * Request timed out.
16 132 ms 129 ms 131 ms 192.34.76.2
17 48 ms 50 ms 48 ms 199.91.189.234
18 137 ms 134 ms 138 ms 199.91.189.40

Trace complete.

[Noah_]

snip

if you ran a whois on the 2 IP before and after that time out you will come up with this and this