First let me say I'm a pretty active PS2 player, I log in almost everyday and play for a few hours. I'm based in the UK. Yesterday evening I logged on (23/04/13 sometime around 20:00 GMT) and I noticed people were starting to warp, it got considerably worse until people and vehicles were flying everywhere all over my screen. During this, in game VOIP worked perfectly, I could send and receive coms with no stutter or loss of quality. A few restarts didn't sort it out so I decided to leave it for the evening and try again tomorrow. I logged in today (24/03/13) about 2 hours before the servers were brought down for the update (sometime before mid day GMT) and all seemed well again, I played for appx 2 hours during an alert which ended around the time of the 15 minute server shut down notice and throughout my 2 hour play session I don't recall noticing anything untoward. I logged out before the server shut down. I logged in this evening at around 20:30 GMT and the warping is back again. I suspected packet loss so I done a ping test to Mattherson (the server I play on) and sure enough up to 10% of packets sent are being lost. I done a ping test to some UK sites like bbc.co.uk and I'm not loosing any packets to them. I decided to ping test Waterson (East coast) and again it shows up to 10% packets lost. I then done ping tests to Helios and Connery (West coast servers) and they had 0% packet loss. There is not much I can do about this from my end.... I'm not even sure SOE can do anything about it from their end but I figured I should point it out with the hope that a forum official see's this and has someone take a look, because unless something is done, as of right now I can no longer play PS2 on my only character I have invested time and money into.
The desync issues appear to be back on matherson. I'm glad I'm not the only one suffering from no bullet damage/medkits not working etc.
I'm in the UK and I also play mainly on Mattherson. Since GU07 I've been getting de-syncs, terrible lag and crashes. I raised a ticket and the reply was to try disabling any OC'ing I might have. Just to humour them I've tried that and the problems are still there at default CPU Hz Like the OP I can play for a while with no problems than out of the blue my fps drops and players start warping around the place. Similarly I don't get these problems on Miller (EU) or Connery (US WEST).
I'd like to point out that although I know people have reported various issues before, the issue of loosing packets to East coast servers started yesterday. As I mentioned I play every day on Mattherson, and although similar, and I stress the word similar, things have been reported as happening before yesterday, the effects of packet loss are very distinct and only started yesterday. At least for me personally from my connection route to the server. What I am trying to say is that I believe the issue I am reporting is separate from those reported earlier, although I have experienced things prior to yesterday that could possibly be attributed to server stability or stress, the majority of my time playing up to yesterday was without any major incident (unless the whole server was experiencing it) and I very rarely experience any lag in its true sense. Generally speaking, as far as connectivity issues go, up until yesterday things were fine for me with GU07 (I don't believe this is a build fault). Although I'll confess bugs like the random crash on deploy is really starting to wear my patience thin. What I don't get is why I was able to play for 2 hours earlier on in the day (GMT) without packet loss, but in the evening I'm loosing packets again.
After tracert and pathping tests to the game ip I've just done a ipconfig /flushdns losses showed 0% on the test after this. Logging into game now to see if problem is gone or not.
Just out of curiousity, why would anyone want to live across the pond and play on a US East coast server? I would think that the EU servers would be a more effective place for you to game.
I've been playing on the East coast server(s) since the start of beta. Also I've been part of a pretty large US based multinational community since 2006 (tacticalgamer.com) that decided to make Mattherson its home in PS2. Ping has never been an issue for me. A little update... So earlier today I tested the servers (around 10:30 GMT +1) and I got the same results as the day before around mid day.... 0% packets lost and around 128ms ping times, everything as it should be, perfect. Tested the servers after I got home from work tonight (around 19:30 GMT+1) and I'm back to around 10% packet loss and 250+ms ping times... Something very strange is going on here.... It's like sometime in the evening of the 23rd someone just flicked a switch, and they keep flicking it every night. Also, I started a conversation with TSR AlexS where I have provided a number of ping test and trace route results from the past couple of days... But I haven't had a response from Alex in the conversation. So Alex, if you see this can you please confirm that you have received the information I provided, just so it doesn't feel like I'm talking to myself
Just checked and for me it is also only happening during "peak" hours. Because of this I think I have a reasonable suspicion for what's happening because I've experienced it before with another ISP. During peak hours a bad ISP will run their exchanges very hot and when this happens you get lots of jitter, high latencies and frequent packet loss. That this is only happening to a noticeable extent on the East coast servers tells me the problem is somewhere in the chain of exchanges between the UK and SOE's servers in Virginia. If it was at my local exchange or where ever the local node is that Be are renting from BT Openreach I'd be expecting the same problems be manifesting everywhere, e.g. by web pages being very slow to load or timing out frequently.
Well it seems the packet loss is gone. So far this evening my connection to Mattherson has been fine. A ping test I just completed shows 0% packet loss and it seems the time is averaging around 93ms for me personally... better than before. Think some new hardware may have been installed somewhere? Either way, fingers crossed it stays this way
I'm having the same issues on Miller (EU) Location - Bracknell, UK ISP: O2 (transitioning to Sky due to acquisition) Type: ADSL Modem - Netgear DM111P Router - Linksys WRT54GL (Tomato 1.28) Speedtest.net Results: Ping - 20ms Down - 8.78Mbps Up - 0.78Mbps Pinging Miller (EU): Code: Pinging 195.33.132.168 with 32 bytes of data: Reply from 195.33.132.168: bytes=32 time=227ms TTL=106 Request timed out. Reply from 195.33.132.168: bytes=32 time=238ms TTL=106 Reply from 195.33.132.168: bytes=32 time=230ms TTL=106 Ping statistics for 195.33.132.168: Packets: Sent = 4, Received = 3, Lost = 1 (25% loss), Approximate round trip times in milli-seconds: Minimum = 227ms, Maximum = 238ms, Average = 231ms Pinging Matterson (US East): Code: Pinging 199.108.194.38 with 32 bytes of data: Reply from 199.108.194.38: bytes=32 time=290ms TTL=111 Reply from 199.108.194.38: bytes=32 time=290ms TTL=111 Reply from 199.108.194.38: bytes=32 time=296ms TTL=111 Request timed out. Ping statistics for 199.108.194.38: Packets: Sent = 4, Received = 3, Lost = 1 (25% loss), Approximate round trip times in milli-seconds: Minimum = 290ms, Maximum = 296ms, Average = 292ms Pinging Connery (US West): Code: Pinging 64.37.174.140 with 32 bytes of data: Reply from 64.37.174.140: bytes=32 time=155ms TTL=113 Reply from 64.37.174.140: bytes=32 time=156ms TTL=113 Reply from 64.37.174.140: bytes=32 time=154ms TTL=113 Reply from 64.37.174.140: bytes=32 time=159ms TTL=113 Ping statistics for 64.37.174.140: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 154ms, Maximum = 159ms, Average = 156ms It's basically unplayable at the moment, let me know if you need any more information.
Im also in the UK and play on Waterson with my outfit and am getting the packet loss etc. Trace routes show that my connection is fine until it leaves the UK as it jumps to SanJose, LA, Washington before back to the SOE centre. All of these hops are on the Level3 network. The same applies to the UK servers, It jumps to Paris on the Level3 network, then London, Amsterdam and then to SOE. West coast servers avoid the Level3 network all together and as such I have no issues. Guess its just a case of waiting for Level3 to sort their s*#t out uless SOE can do something with that info??? EU Code: C:\Users\James>tracert 195.33.132.168 Tracing route to amspsn-liv-gw04.planetside2.com [195.33.132.168] over a maximum of 30 hops: 1 53 ms 99 ms 99 ms O2wirelessbox.lan [192.168.1.254] 2 39 ms 38 ms 41 ms 87-194-114-185.bethere.co.uk [87.194.114.185] 3 90 ms 60 ms 63 ms 10.17.88.1 4 * 48 ms 80 ms 10.17.8.238 5 40 ms 39 ms 40 ms 10.17.8.237 6 39 ms 40 ms 61 ms O2-UK-4-0-8-0-GRTLONTL1.red.telefonica-wholesale.net [94.142.103.133] 7 46 ms 46 ms 40 ms Xe1-0-0-0-grtloneq1.red.telefonica-wholesale.net [94.142.117.201] 8 47 ms * * 176.52.250.113 9 250 ms 243 ms * 213.242.111.29 10 394 ms 385 ms 258 ms ae-60-60.csw1.Paris1.Level3.net [4.69.168.62] 11 572 ms 412 ms 433 ms ae-91-91.ebr1.Paris1.Level3.net [4.69.161.89] 12 423 ms 411 ms 395 ms ae-45-45.ebr1.London1.Level3.net [4.69.143.101] 13 407 ms 388 ms 389 ms vlan102.ebr2.London1.Level3.net [4.69.143.90] 14 * 398 ms 407 ms ae-48-48.ebr2.Amsterdam1.Level3.net [4.69.143.81] 15 387 ms 400 ms 266 ms ae-57-222.csw2.Amsterdam1.Level3.net [4.69.153.206] 16 286 ms 245 ms 243 ms 4.69.162.201 17 324 ms 319 ms 317 ms SONY-ONLINE.edge4.Amsterdam1.Level3.net [212.72.42.182] 18 396 ms 400 ms * amspsn-liv-gw04.planetside2.com [195.33.132.168] 19 395 ms 400 ms 395 ms amspsn-liv-gw04.planetside2.com [195.33.132.168] EAST COAST Code: C:\Users\James>tracert 199.108.194.41 Tracing route to abepsn-liv-gw04.planetside2.com [199.108.194.41] over a maximum of 30 hops: 1 15 ms 99 ms 99 ms O2wirelessbox.lan [192.168.1.254] 2 53 ms 39 ms 41 ms 87-194-114-185.bethere.co.uk [87.194.114.185] 3 40 ms 39 ms 40 ms 10.17.88.1 4 * 39 ms 43 ms O2UK-5-0-8-GRTLONTL1.6.16.84.in-addr.arpa [84.16.6.190] 5 39 ms 40 ms 39 ms xe-3-0-8-0-grtlontl1.red.telefonica-wholesale.net [84.16.6.209] 6 169 ms 107 ms 108 ms Xe3-0-2-0-grtnycpt3.red.telefonica-wholesale.net [213.140.38.221] 7 176 ms 179 ms 176 ms Xe1-2-0-0-grtpaopx2.red.telefonica-wholesale.net [94.142.125.85] 8 184 ms 186 ms 185 ms te-4-2.car1.SanJose2.Level3.net [4.59.0.225] 9 301 ms 300 ms 298 ms vlan90.csw4.SanJose1.Level3.net [4.69.152.254] 10 300 ms 302 ms 299 ms ae-91-91.ebr1.SanJose1.Level3.net [4.69.153.13] 11 * 299 ms 299 ms ae-2-2.ebr3.LosAngeles1.Level3.net [4.69.132.10] 12 * 298 ms 299 ms ae-12-12.ebr3.LosAngeles1.Level3.net [4.69.132.82] 13 303 ms 299 ms 299 ms ae-81-81.csw3.Washington1.Level3.net [4.69.134.138] 14 298 ms 300 ms 299 ms ae-3-80.edge1.Washington4.Level3.net [4.69.149.143] 15 228 ms 255 ms 226 ms SONY-ONLINE.edge1.Washington4.Level3.net [4.53.112.6] 16 307 ms 298 ms 299 ms abepsn-liv-gw04.planetside2.com [199.108.194.41] WEST COAST Code: tracert 64.37.174.140 Tracing route to lvspsn-liv-gw01.station.sony.com [64.37.174.140] over a maximum of 30 hops: 1 80 ms 99 ms 99 ms O2wirelessbox.lan [192.168.1.254] 2 41 ms 39 ms 40 ms 87-194-114-185.bethere.co.uk [87.194.114.185] 3 42 ms 39 ms 40 ms 10.17.88.1 4 * 60 ms 40 ms 195.66.225.189 5 56 ms 47 ms 42 ms linx.10ge.lon.bboi.net [195.66.224.233] 6 114 ms 115 ms 114 ms ny60-vl14-lon-vl14.bboi.net [66.216.48.213] 7 112 ms 115 ms 112 ms ny111-po1-ny60-po1.bboi.net [66.216.1.90] 8 134 ms 132 ms 132 ms 66.216.1.150 9 177 ms 176 ms 177 ms lv-ten1-3-chi-ten1-6.bboi.net [64.127.128.130] 10 179 ms 179 ms 179 ms switch-vegas-bboi.bboi.net [66.186.192.46] 11 177 ms 179 ms 179 ms te0-0-0-4.las-core7-2.switchnap.com [66.209.64.109] 12 233 ms 228 ms 221 ms te3-5.las-core2-1.switchnap.com [66.209.64.42] 13 179 ms 178 ms 180 ms po10.las-agg7s1-1.switchnap.com [66.209.64.34] 14 182 ms 180 ms 179 ms demarc1.soe.switchnap.com [216.115.64.74] 15 179 ms 179 ms 182 ms vl3104.lvssw-2.sonyonline.net [64.37.168.26] 16 178 ms 178 ms 179 ms lvspsn-liv-gw01.station.sony.com [64.37.174.140]
Waterson, and Mattherson, seem to suffer from the same problem, can any soe tell us whats whats going o, on the line.
No sign of improvement yet. My traceroute looks similar: Code: Tracing route to amspsn-liv-gw04.planetside2.com [195.33.132.168] over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms jimmeh [192.168.0.1] 2 22 ms 35 ms 61 ms 94-193-104-1.zone7.bethere.co.uk [94.193.104.1] 3 61 ms 39 ms 29 ms 10.1.3.178 4 * * * Request timed out. 5 151 ms 49 ms 103 ms xe4-1-6-0-GRTLONTL1.red.telefonica-wholesale.net [94.142.103.137] 6 110 ms 59 ms 25 ms Xe6-1-2-0-grtparix1.red.telefonica-wholesale.net [84.16.14.145] 7 39 ms 61 ms 51 ms Xe0-0-6-0-grtpareq1.red.telefonica-wholesale.net [94.142.117.82] 8 230 ms 218 ms * xe-9-0-0.edge4.Paris1.Level3.net [213.242.111.5] 9 228 ms * * ae-60-60.csw1.Paris1.Level3.net [4.69.168.62] 10 225 ms 260 ms 341 ms ae-61-61.ebr1.Paris1.Level3.net [4.69.161.77] 11 301 ms 413 ms 237 ms ae-45-45.ebr1.London1.Level3.net [4.69.143.101] 12 * 232 ms 236 ms vlan103.ebr2.London1.Level3.net [4.69.143.94] 13 * 291 ms 232 ms ae-47-47.ebr2.Amsterdam1.Level3.net [4.69.143.77] 14 279 ms 240 ms 225 ms ae-56-221.csw2.Amsterdam1.Level3.net [4.69.153.202] 15 232 ms 226 ms 235 ms 4.69.162.193 16 139 ms 138 ms 140 ms SONY-ONLINE.edge4.Amsterdam1.Level3.net [212.72.42.182] 17 235 ms 232 ms 306 ms amspsn-liv-gw04.planetside2.com [195.33.132.168] Trace complete.
Same problem here with Woodman (EU) since Monday night around 9:30pm GMT. Everything was running fine before. The game is unplayable right now. Once I log in at the warpgate it takes around 10 sec for terminals and players to load and another 10 sec before I can use terminals/abilities (cloak, heal etc.). Everything that I do at the warpgate such as switching classes or using abilities has a delay of about 2-3 sec. When I Instant Action drop into a battle nothing works anymore. The delay for any action is 10-20 sec. players and vehicles warp all over the place. My location is Devon (UK) and my ISP is O2. I have done the same traceroutes today at work with other computers in Cornwall and Somerset (all O2) with the same results. As soon as it hits the Level3 network in London/Paris it's game over. Not sure if SOE can do anything about it as it does not seem like the actual PS2 servers are the problem, but the routing to get there (Level3). Anyways here are the traceroutes in case they are of help. (Pretty much the same as Eskara and Jimmeh have already posted) Woodman (EU) Code: Tracing route to amspsn-liv-gw05.planetside2.com [195.33.132.169] over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms www.routerlogin.com [192.168.0.1] 2 21 ms 21 ms 21 ms 93-96-177-1.zone4.bethere.co.uk [93.96.177.1] 3 24 ms 24 ms 24 ms 10.1.3.50 4 * 23 ms * 10.1.4.241 5 27 ms 93 ms 22 ms xe2-0-6-0-GRTLONTL1.red.telefonica-wholesale.net [94.142.103.141] 6 38 ms 24 ms 68 ms Xe1-0-0-0-grtloneq1.red.telefonica-wholesale.net [94.142.117.201] 7 29 ms 29 ms 38 ms Xe7-1-8-0-grtpareq1.red.telefonica-wholesale.net [84.16.14.113] 8 219 ms * 219 ms 213.242.111.29 9 234 ms 227 ms 227 ms vlan90.csw4.Paris1.Level3.net [4.69.168.254] 10 228 ms 226 ms 227 ms ae-91-91.ebr1.Paris1.Level3.net [4.69.161.89] 11 238 ms 240 ms 241 ms ae-47-47.ebr1.London1.Level3.net [4.69.143.109] 12 233 ms 234 ms 226 ms vlan102.ebr2.London1.Level3.net [4.69.143.90] 13 * 235 ms 232 ms ae-47-47.ebr2.Amsterdam1.Level3.net [4.69.143.77] 14 225 ms * * ae-58-223.csw2.Amsterdam1.Level3.net [4.69.153.210] 15 236 ms * 228 ms 4.69.162.205 16 146 ms 153 ms 145 ms SONY-ONLINE.edge4.Amsterdam1.Level3.net [212.72.42.182] 17 233 ms 241 ms 224 ms amspsn-liv-gw05.planetside2.com [195.33.132.169] Trace complete. Mattherson (US East) - I don't play on this server, but it shows the problem with Level3 again. Code: Tracing route to abepsn-liv-gw01.planetside2.com [199.108.194.38] over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms www.routerlogin.com [192.168.0.1] 2 21 ms 21 ms 21 ms 93-96-177-1.zone4.bethere.co.uk [93.96.177.1] 3 24 ms 24 ms 24 ms 10.1.3.50 4 * 23 ms 22 ms 10.1.4.241 5 24 ms 25 ms 24 ms XE1-0-3-0-GRTLONTL1.red.telefonica-wholesale.net [84.16.6.189] 6 90 ms 90 ms 90 ms Xe5-0-2-0--grtnycpt3.red.telefonica-wholesale.net [213.140.38.157] 7 160 ms 159 ms 160 ms Xe0-1-0-0-grtpaopx2.red.telefonica-wholesale.net [94.142.125.81] 8 167 ms 167 ms 167 ms te-4-2.car1.SanJose2.Level3.net [4.59.0.225] 9 286 ms 285 ms 286 ms vlan70.csw2.SanJose1.Level3.net [4.69.152.126] 10 283 ms 283 ms 282 ms ae-71-71.ebr1.SanJose1.Level3.net [4.69.153.5] 11 289 ms 289 ms * ae-2-2.ebr2.NewYork1.Level3.net [4.69.135.186] 12 284 ms 285 ms 290 ms 4.69.201.38 13 284 ms 282 ms 282 ms ae-1-100.ebr1.NewYork2.Level3.net [4.69.135.253] 14 282 ms 284 ms 282 ms 4.69.201.89 15 284 ms 283 ms 284 ms ae-62-62.csw1.Washington1.Level3.net [4.69.134.146] 16 283 ms 283 ms 284 ms ae-1-60.edge1.Washington4.Level3.net [4.69.149.15] 17 205 ms 205 ms 205 ms SONY-ONLINE.edge1.Washington4.Level3.net [4.53.112.6] 18 284 ms 282 ms 283 ms abepsn-liv-gw01.planetside2.com [199.108.194.38] Trace complete.
