Lag, Rubberbanding, and "Poor" connection [EMERALD]

Hi, I just came back to the game recently after a few months of hiatus and I find myself having SEVERE lag problems. I NEVER experienced this before before, I had a perfect gameplay experience (lag wise) yet now its really hard to play because of all the problems that lag brings.

The connection indicator says "Poor" but here are my speet test results with a host in Virginia where as I understand the East Coast servers are located.

http://www.speedtest.net/my-result/3695797082

I've been talking with people ingame and they are experiencing the same.

PLEASE for the love of VANU, FIX THIS!!

bump

lol this is funny because i was coming on the forums to say the exact same thing. I am getting a jumping from 25-60 fps at the warp gate along with stuttering and rubberbanding your not alone bud probably a problem with the servers that will be fixed tomorrow.

There are multiple reasons as to why this could be happening.


1.) Are you using a Wireless Connection?

- Using a wireless connection wouldn't be your best choice for this type of game play. I've heard many of people saying they're having problems with ping/latency. This is the first question I always ask whenever they ask for help. The reason it gives you a slower connection is because your router/modem is sending packets to your computer in which your computer then sends them elsewhere which is then sent to the magic places which shows you all the content going on in the game.

- Use a wired connection! Not sure how? There's a few different ways to connection your computer to an Ethernet Cable. Most computers (laptop and desktop alike), all have an Ethernet port. (Not entirely sure on what it's called. We'll just go with that, though.) If it's a laptop, check all around it. Most likely it will be on the side, but some manufacturers find it hilarious to place on the side closest to you, as well as on the side furthest from you. If you've got a desktop computer, check on the back of the tower. (It will most likely be there, if not, search around it.)

Now, finding the Ethernet cord! (FUN). Depending on what you're near, there may be one near you. Is there a home phone near you? Is the router/modem near you? Do you have TV access? If so, does it use internet to stream its content?

I'm currently using AT&T U-VERSE. My TV access is streamed to me via an Ethernet cord hooked to the back of the box. It's also hooked into a socket in the wall. Leave that part in and unhook it from the box. Hook that part into your Ethernet Port on/in your computer. Not sure what an Ethernet cord looks like? http://www.google.com/

2.) Are you using a Wired Connection?
- Where are you located? Are you further away from the server? As you may know, the server is located on the East Coast of USA. I feel like if you're about the middle of the USA and further west, you'll be getting a higher ping than ones more close to the servers location.

- Close to the servers? Close out of anything that you know/think is also using internet. (Except for Steam, as it is required to run PlanetSide 2 [I think]).




If this does not help, not sure what will. Sorry for the boring-ness and the horrible way of relaying the scrambled info in my head to this thread.



Regards!

Open a command window and type in "TRACERT LP.SOE.COM". Don't hit enter yet, just leave it like that in the background while you run PS2.

The moment you even start to think you're hitting a lag spike, alt-tab out quick as a wink and run that traceroute. Once PS2 reports some huge ping it's likely the spike is already over and you won't catch it in time, you've got to run it during the spike if at all possible.

If you see something like the text I've highlit in red:

Tracing route to lp.soe.com [64.37.171.24]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.0.1
2 24 ms 24 ms 22 ms 70-36-142-1.dsl.dynamic.sonic.net [70.36.142.1]
3 22 ms 22 ms 21 ms gig1-29.cr1.colaca01.sonic.net [70.36.228.109]
4 38 ms 43 ms 44 ms ae2.cr2.colaca01.sonic.net [50.0.79.201]
5 43 ms 35 ms 43 ms ae0.cr2.lsatca11.sonic.net [50.0.79.174]
6 22 ms 22 ms 23 ms 50.ae4.gw.pao1.sonic.net [69.12.211.165]
7 23 ms 24 ms 23 ms te0-0-0-15.ccr21.sjc04.atlas.cogentco.com [38.104.141.81]
8 24 ms 23 ms 23 ms be2013.ccr21.sjc03.atlas.cogentco.com [154.54.5.105]
9 25 ms 24 ms 24 ms be2000.ccr21.sjc01.atlas.cogentco.com [154.54.6.105]
10 64 ms 37 ms 37 ms be2162.mpd21.lax01.atlas.cogentco.com [154.54.27.173]
11 37 ms 37 ms 36 ms be2021.ccr21.lax04.atlas.cogentco.com [154.54.87.250]
12 36 ms 36 ms 36 ms level3.lax04.atlas.cogentco.com [154.54.14.130]
13 1853 ms 82 ms 55 ms vlan70.csw2.LosAngeles1.Level3.net [4.69.144.126]
14 * 2023 ms 1915 ms ae-71-71.ebr1.LosAngeles1.Level3.net [4.69.137.5]
15 38 ms 50 ms 39 ms ae-1-4.bar1.LasVegas1.Level3.net [4.69.133.109]
16 46 ms 206 ms 764 ms SWITCH-COMM.bar1.LasVegas1.Level3.net [205.129.16.50]
17 2196 ms 41 ms 49 ms lp.soe.com [64.37.171.24]
Trace complete.

...then please copy and paste the results to the Level3 thread here:

https://forums.station.sony.com/ps2/index.php?threads/level3-issues-post-some-info-here.193501/


Hopefully SOE will get their backbone issues with Level 3 worked out soon.

I'm connecting via ethernet and never had these problems before. Nothing has changed on my side, yet I stopped playing right before the server mergers and now that I have come back I DEFINITELY notice that my game play experience has gone from flawless (besides the aimbotters) to WTF-how-can-I-play-like-this.

Here are the Tracerts before/during/after lag spike

BEFORE:

Tracing route to lp.soe.com [64.37.171.24] over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms Not-Your-Router [192.168.1.1]
2 <1 ms <1 ms <1 ms 192.168.2.1
3 13 ms 40 ms 11 ms 186.74.22.129
4 11 ms 16 ms 12 ms 172.20.0.73
5 12 ms 18 ms 11 ms 201.224.254.225
6 67 ms 65 ms 66 ms tengigabitethernet2-2.ar3.pty1.gblx.net [64.208.7.233]
7 118 ms 110 ms 105 ms ae10.edge1.LosAngeles9.Level3.net [4.68.111.21]
8 117 ms 125 ms 118 ms vlan70.csw2.LosAngeles1.Level3.net [4.69.144.126]
9 111 ms 107 ms 111 ms ae-71-71.ebr1.LosAngeles1.Level3.net [4.69.137.5]
10 125 ms 115 ms 128 ms ae-1-4.bar1.LasVegas1.Level3.net [4.69.133.109]
11 112 ms 115 ms 112 ms SWITCH-COMM.bar1.LasVegas1.Level3.net [205.129.16.50]
12 119 ms 110 ms 128 ms lp.soe.com [64.37.171.24]


Trace complete.

DURING:

Tracing route to lp.soe.com [64.37.171.24] over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms Not-Your-Router [192.168.1.1]
2 <1 ms <1 ms <1 ms 192.168.2.1
3 31 ms 29 ms 29 ms 186.74.22.129
4 11 ms 12 ms 13 ms 172.20.0.73
5 12 ms 12 ms 13 ms 201.224.254.225
6 * * * Request timed out.
7 100 ms 103 ms 104 ms ae10.edge1.LosAngeles9.Level3.net [4.68.111.21]
8 136 ms 137 ms 142 ms vlan70.csw2.LosAngeles1.Level3.net [4.69.144.126]
9 109 ms 110 ms 109 ms ae-71-71.ebr1.LosAngeles1.Level3.net [4.69.137.5]
10 112 ms 127 ms 107 ms ae-1-4.bar1.LasVegas1.Level3.net [4.69.133.109]
11 * 616 ms 106 ms SWITCH-COMM.bar1.LasVegas1.Level3.net [205.129.16.50]
12 112 ms 108 ms 107 ms lp.soe.com [64.37.171.24]

Trace complete.

AFTER:

Tracing route to lp.soe.com [64.37.171.24] over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms Not-Your-Router [192.168.1.1]
2 <1 ms <1 ms <1 ms 192.168.2.1
3 23 ms 23 ms 15 ms 186.74.22.129
4 11 ms 32 ms 13 ms 172.20.0.73
5 98 ms 15 ms 14 ms 201.224.254.225
6 63 ms 78 ms * tengigabitethernet2-2.ar3.pty1.gblx.net [64.208.7.233]
7 121 ms 109 ms 128 ms ae10.edge1.LosAngeles9.Level3.net [4.68.111.21]
8 118 ms 119 ms 120 ms vlan70.csw2.LosAngeles1.Level3.net [4.69.144.126]
9 115 ms 116 ms 108 ms ae-71-71.ebr1.LosAngeles1.Level3.net [4.69.137.5]
10 122 ms 121 ms 114 ms ae-1-4.bar1.LasVegas1.Level3.net [4.69.133.109]
11 120 ms 112 ms 112 ms SWITCH-COMM.bar1.LasVegas1.Level3.net [205.129.16.50]
12 111 ms 112 ms 122 ms lp.soe.com [64.37.171.24]

Trace complete.

ping... err I mean bump

Are you sure that you weren't playing on Miller or Cobalt? Even if you're from the EU, that's normal stuff on there right now.

First batch is a trace with Planetside 2 offline.

Tracing route to lp.soe.com [64.37.171.24]
over a maximum of 30 hops:
1 3 ms 4 ms 3 ms 192.168.1.1
2 21 ms 19 ms 31 ms mi.airadvantage.net
3 23 ms 19 ms 24 ms gli-216-25-179-201.greatlakes.net [216.25.179.201]
4 27 ms 25 ms 23 ms 216.176.29.37
5 48 ms 44 ms 36 ms ge-7-44.car2.Detroit1.Level3.net [4.53.74.161]
6 47 ms 39 ms 39 ms ae-2-5.bar2.Detroit1.Level3.net [4.69.202.237]
7 37 ms 29 ms 41 ms ae-0-11.bar1.Detroit1.Level3.net [4.69.202.221]
8 83 ms 124 ms 79 ms vl-4.ebr2.Chicago1.Level3.net [4.69.202.226]
9 * * * Request timed out.
10 81 ms 83 ms 79 ms ae-6-6.ebr1.Chicago2.Level3.net [4.69.140.190]
11 77 ms 84 ms 79 ms ae-3-3.ebr2.Denver1.Level3.net [4.69.132.61]
12 * * * Request timed out.
13 92 ms 135 ms 165 ms ae-1-6.bar2.LasVegas1.Level3.net [4.69.148.1]
14 207 ms 147 ms 164 ms ae-0-11.bar1.lasvegas1.level3.net [4.69.148.125]
15 171 ms 126 ms 185 ms SWITCH-COMM.bar1.LasVegas1.Level3.net [205.129.16.50]
16 123 ms 153 ms 152 ms lp.soe.com [64.37.171.24]
Trace complete.

This is with Planetside 2 online at a 48+ both side engagement.

1 60 ms 89 ms 82 ms 192.168.1.1
2 116 ms 115 ms 101 ms mi.airadvantage.net
3 125 ms 112 ms 115 ms gli-216-25-179-201.greatlakes.net [216.25.179.201]
4 105 ms 117 ms 129 ms 216.176.29.37
5 157 ms * 372 ms ge-7-44.car2.Detroit1.Level3.net [4.53.74.161]
6 349 ms 380 ms 336 ms ae-2-5.bar2.Detroit1.Level3.net [4.69.202.237]
7 518 ms 476 ms 421 ms ae-0-11.bar1.Detroit1.Level3.net [4.69.202.221]
8 659 ms 499 ms 639 ms vl-4.ebr2.Chicago1.Level3.net [4.69.202.226]
9 * * * Request timed out.
10 814 ms 758 ms 738 ms ae-6-6.ebr1.Chicago2.Level3.net [4.69.140.190]
11 798 ms 818 ms 984 ms ae-3-3.ebr2.Denver1.Level3.net [4.69.132.61]
12 * * * Request timed out.
13 543 ms 682 ms 595 ms ae-1-6.bar2.LasVegas1.Level3.net [4.69.148.1]
14 634 ms 559 ms 548 ms ae-0-11.bar1.LasVegas1.Level3.net [4.69.148.125]
15 620 ms 526 ms 492 ms SWITCH-COMM.bar1.LasVegas1.Level3.net [205.129.16.50]
16 805 ms 598 ms 619 ms lp.soe.com [64.37.171.24]
Trace complete.

Game is unplayable for me in it's current state.

Yeah same problem here. Was fine until a few weeks ago. Same as some others above... something is dorked up between Denver1 and LasVegas1.

Tracing route to lp.soe.com [64.37.171.24]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 25 ms 25 ms 26 ms mpls-dsl-gw57.mpls.qwest.net [207.225.140.57]
3 24 ms 25 ms 25 ms mpls-agw1.inet.qwest.net [75.168.229.193]
4 35 ms 35 ms 35 ms chp-brdr-03.inet.qwest.net [67.14.8.194]
5 125 ms 123 ms 125 ms 63.146.27.18
6 173 ms 170 ms 173 ms vlan51.ebr1.Chicago2.Level3.net [4.69.138.158]
7 171 ms 175 ms 171 ms ae-3-3.ebr2.Denver1.Level3.net [4.69.132.61]
8 * * * Request timed out.
9 173 ms 172 ms 173 ms ae-1-6.bar2.LasVegas1.Level3.net [4.69.148.1]
10 172 ms 173 ms 175 ms ae-0-11.bar1.LasVegas1.Level3.net [4.69.148.125]
11 173 ms 174 ms 174 ms SWITCH-COMM.bar1.LasVegas1.Level3.net [205.129.16.50]
12 173 ms 176 ms 173 ms lp.soe.com [64.37.171.24]

Trace complete.

If your like me and play at different times and days, you will notice that during the off hours your ping is normal.. mine being 60-100. But as prime time approaches the latency gets worse and worse, during prime time (I'm assuming thats 5-midnight based on my latency during that time being the worst) I am lucky to get a ping below 5,000. Which is completely unplayable and that's when all the people I play with are on which is a bummer. It seems that since the mergers either my internet can't handle the amount of traffic (which it did fine for the year and a half before the mergers) or SOE's servers/bandwidth just can't handle the amount of players on at the time.

Edit: I play on Emerald and I live in NY

It's probably because the in game ping meter - also factors in however long it takes the server to process your packets. This is evident by the difference between my in-game ping (28-40ms) and my direct ping to the servers's IP (3-5ms). Sheer load during peak times can account for a difference of 15-10ms. But nearly 35ms? No.

same as you guys

UNPLAYABLE

1 1 ms <1 ms <1 ms 192.168.1.1
2 21 ms 21 ms 21 ms 10.10.10.10
3 20 ms 20 ms 20 ms pool-64-222-213-167.port.east.myfairpoint.net [6
4.222.213.167]
4 21 ms 20 ms 21 ms pool-64-222-213-134.port.east.myfairpoint.net [6
4.222.213.134]
5 25 ms 24 ms 24 ms xe-3-2-0.mpr4.bos2.us.above.net [208.184.223.233
]
6 30 ms 29 ms 31 ms ae2.mpr3.bos2.us.above.net [64.125.25.41]
7 40 ms 35 ms 39 ms xe-9-3-0.cr1.lga5.us.above.net [64.125.21.226]
8 66 ms 35 ms 35 ms ae1.cr2.lga5.us.above.net [64.125.29.38]
9 35 ms 35 ms 34 ms ae3.er4.lga5.us.above.net [64.125.31.246]
10 36 ms 34 ms 35 ms L3-Zayo.lga5.us.above.net [64.125.13.30]
11 95 ms 95 ms 96 ms vlan80.csw3.NewYork1.Level3.net [4.69.155.190]
12 * * * Request timed out.
13 * * * Request timed out.
14 96 ms 95 ms 96 ms ae-6-6.ebr2.Chicago2.Level3.net [4.69.148.146]
15 95 ms 95 ms 96 ms ae-1-100.ebr1.Chicago2.Level3.net [4.69.132.113]

16 99 ms 98 ms 99 ms ae-3-3.ebr2.Denver1.Level3.net [4.69.132.61]
17 * * * Request timed out.
18 97 ms 95 ms 95 ms ae-1-6.bar2.LasVegas1.Level3.net [4.69.148.1]
19 95 ms 95 ms 96 ms ae-0-11.bar1.LasVegas1.Level3.net [4.69.148.125]

20 97 ms 97 ms 97 ms SWITCH-COMM.bar1.LasVegas1.Level3.net [205.129.1
6.50]
21 101 ms 100 ms 100 ms lp.soe.com [64.37.171.24]

Trace complete.

Bump, let's hope today's patch fixes things.
If things like this remain, I have doubts on the ps4 version of planetside 2, having Destiny around the corner

I kind of doubt any patch could fix backbone routing issues...

I'm having the same problem lately, too.

still happening


still ddos?

I did the traceroute, and had /7/ timeouts.
/7/.

That's some serious packet loss, but the connection status doesn't change whatsoever.

Ya still having issues on Emerald although i live in Wisconsin. I never had issues prior to merge.

I've been dealing with this since i think a couple weeks after the Valk update. used to get a stable ping of around 70-100ms, now it's all over the place. One second it'll say i have 54 ping, the next it'll shoot all the way up to 5000 ping(and then never go any lower than 200ms). I play on Emerald and live in Kentucky.