I'm also having connection problems, I notice several of the above are also on o2/Be (same company, owned by Telefonica). However there seems to be issues with both Telefonica and level3, which appear to provide the connection for the game server, so I am surprised this isn't an issue for everyone playing from outside the East coast. Or maybe it is, but that one issue hasn't been enough to have people realise it is something other than a PS2/game server problem? Before I post the data I note that historically my ping to Waterson has been in the 100 range. Very playable. Then, for a time there was some strange routing with issues seemly at llw.net (I think it was) hops putting me at 160. This is annoying but playable. However for the last month or so it has been going through level13.net and I have been consistently getting ~160 during UK daytime then between 5 - 6pm UK time it steadily increased up to 260. The evening is unplayable, though sometimes I did it anyway and played revive medic. For the last few days it has been ~280 at all times and I suspect substantial packet loss. This is not just unplayable, the game is broken (I will post a separate comment regarding the connection to EU servers) Trace data from UK to Waterson: Code: C:\Users\Dave>tracert 199.108.194.41 Tracing route to abepsn-liv-gw04.planetside2.com [199.108.194.41] over a maximum of 30 hops: 1 88 ms 99 ms 99 ms bebox.config [192.168.1.254] 2 14 ms 15 ms 18 ms 94-193-240-1.zone7.bethere.co.uk [94.193.240.1] 3 13 ms 13 ms 12 ms 10.1.3.245 4 20 ms 24 ms 20 ms 10.1.2.169 5 * * * Request timed out. 6 20 ms 20 ms 20 ms xe2-0-6-0-GRTLONTL1.red.telefonica-wholesale.net [94.142.103.141] 7 88 ms 96 ms 88 ms Xe5-0-2-0--grtnycpt3.red.telefonica-wholesale.net [213.140.38.157] 8 159 ms 158 ms 156 ms Xe0-1-0-0-grtpaopx2.red.telefonica-wholesale.net [94.142.125.81] 9 186 ms 173 ms 172 ms te-4-2.car1.SanJose2.Level3.net [4.59.0.225] 10 279 ms 280 ms * vlan70.csw2.SanJose1.Level3.net [4.69.152.126] 11 285 ms 286 ms 285 ms ae-71-71.ebr1.SanJose1.Level3.net [4.69.153.5] 12 281 ms 283 ms 283 ms ae-2-2.ebr2.NewYork1.Level3.net [4.69.135.186] 13 279 ms 281 ms 280 ms ae-46-46.ebr2.NewYork2.Level3.net [4.69.201.30] 14 287 ms 280 ms 280 ms ae-1-100.ebr1.NewYork2.Level3.net [4.69.135.253] 15 280 ms 280 ms 279 ms 4.69.132.89 16 281 ms 282 ms * ae-92-92.csw4.Washington1.Level3.net [4.69.134.158] 17 279 ms 280 ms 282 ms ae-4-90.edge1.Washington4.Level3.net [4.69.149.207] 18 202 ms 203 ms 203 ms SONY-ONLINE.edge1.Washington4.Level3.net [4.53.112.6] 19 278 ms * 278 ms abepsn-liv-gw04.planetside2.com [199.108.194.41] Trace complete. Comment: I see the first spike is on the telefonica network: I have a suspicion that GRTLONTL1 to grtnycpt3 is London to NY so looks OK. I see second spike is again on Telefonica: if above suspicion is true then grtnycpt3 to grtpaopx2 which might be NY to ... Palo Alto? Ping seems appropriate for that distance, and the small ping to the next hop which identifies itself as San Jose. I have no idea why Telefonica are routing me to Washington via California, this seems to be a Telefonica issue. I see third spike SanJose2.Level3.net to SanJose1.Level3.net of over 100msec... This seems to be a level3 internal network problem. Noting the "negative" hop at SONY-ONLINE.edge1.Washington4.Level3.net, this is a fluke and should be ignored, it is inconsistent with the numerous traces. The above 3 issues are consistent however over my many traces. I point this line out mostly as it appears SOE's connection is supplied by level3.net, hence SOE may be able to nudge level3 into looking into that issue. I'll post the pathping but with the caveat that it has been inconsistent. This was the second run and the first only had packet loss at one of the Washington level3 hops. Subsequent runs have failed, maybe one of the hops has triggered anti-flooding or something. Code: C:\Users\Dave>pathping 199.108.194.41 Tracing route to abepsn-liv-gw04.planetside2.com [199.108.194.41] over a maximum of 30 hops: 0 Dave-PC.config [192.168.1.78] 1 bebox.config [192.168.1.254] 2 94-193-240-1.zone7.bethere.co.uk [94.193.240.1] 3 10.1.3.245 4 10.1.2.169 5 10.1.4.245 6 xe2-0-6-0-GRTLONTL1.red.telefonica-wholesale.net [94.142.103.141] 7 Xe5-0-2-0--grtnycpt3.red.telefonica-wholesale.net [213.140.38.157] 8 Xe9-2-0-0-grtpaopx2.red.telefonica-wholesale.net [94.142.118.178] 9 te-4-2.car1.SanJose2.Level3.net [4.59.0.225] 10 vlan70.csw2.SanJose1.Level3.net [4.69.152.126] 11 ae-71-71.ebr1.SanJose1.Level3.net [4.69.153.5] 12 ae-2-2.ebr2.NewYork1.Level3.net [4.69.135.186] 13 ae-46-46.ebr2.NewYork2.Level3.net [4.69.201.30] 14 ae-1-100.ebr1.NewYork2.Level3.net [4.69.135.253] 15 4.69.132.89 16 ae-92-92.csw4.Washington1.Level3.net [4.69.134.158] 17 ae-4-90.edge1.Washington4.Level3.net [4.69.149.207] 18 SONY-ONLINE.edge1.Washington4.Level3.net [4.53.112.6] 19 abepsn-liv-gw04.planetside2.com [199.108.194.41] Computing statistics for 475 seconds... Source to Here This Node/Link Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address 0 Dave-PC.config [192.168.1.78] 0/ 100 = 0% | 1 1ms 0/ 100 = 0% 0/ 100 = 0% bebox.config [192.168.1.254] 0/ 100 = 0% | 2 15ms 0/ 100 = 0% 0/ 100 = 0% 94-193-240-1.zone7.bethere.co.uk [94.193.240.1] 0/ 100 = 0% | 3 13ms 0/ 100 = 0% 0/ 100 = 0% 10.1.3.245 0/ 100 = 0% | 4 18ms 14/ 100 = 14% 14/ 100 = 14% 10.1.2.169 0/ 100 = 0% | 5 20ms 0/ 100 = 0% 0/ 100 = 0% 10.1.4.245 0/ 100 = 0% | 6 32ms 0/ 100 = 0% 0/ 100 = 0% xe2-0-6-0-GRTLONTL1.red.telefonica-wholesale.net [94.142.103.141] 0/ 100 = 0% | 7 98ms 16/ 100 = 16% 16/ 100 = 16% Xe5-0-2-0--grtnycpt3.red.telefonica-wholesale.net [213.140.38.157] 0/ 100 = 0% | 8 161ms 0/ 100 = 0% 0/ 100 = 0% Xe9-2-0-0-grtpaopx2.red.telefonica-wholesale.net [94.142.118.178] 9/ 100 = 9% | 9 261ms 21/ 100 = 21% 12/ 100 = 12% te-4-2.car1.SanJose2.Level3.net [4.59.0.225] 0/ 100 = 0% | 10 253ms 15/ 100 = 15% 6/ 100 = 6% vlan70.csw2.SanJose1.Level3.net [4.69.152.126] 0/ 100 = 0% | 11 255ms 14/ 100 = 14% 5/ 100 = 5% ae-71-71.ebr1.SanJose1.Level3.net [4.69.153.5] 0/ 100 = 0% | 12 212ms 14/ 100 = 14% 5/ 100 = 5% ae-2-2.ebr2.NewYork1.Level3.net [4.69.135.186] 0/ 100 = 0% | 13 215ms 9/ 100 = 9% 0/ 100 = 0% ae-46-46.ebr2.NewYork2.Level3.net [4.69.201.30] 0/ 100 = 0% | 14 211ms 14/ 100 = 14% 5/ 100 = 5% ae-1-100.ebr1.NewYork2.Level3.net [4.69.135.253] 0/ 100 = 0% | 15 212ms 10/ 100 = 10% 1/ 100 = 1% 4.69.132.89 0/ 100 = 0% | 16 214ms 26/ 100 = 26% 17/ 100 = 17% ae-92-92.csw4.Washington1.Level3.net [4.69.134.158] 0/ 100 = 0% | 17 214ms 22/ 100 = 22% 13/ 100 = 13% ae-4-90.edge1.Washington4.Level3.net [4.69.149.207] 0/ 100 = 0% | 18 223ms 21/ 100 = 21% 12/ 100 = 12% SONY-ONLINE.edge1.Washington4.Level3.net [4.53.112.6] 0/ 100 = 0% | 19 279ms 9/ 100 = 9% 0/ 100 = 0% abepsn-liv-gw04.planetside2.com [199.108.194.41] Trace complete. Summary of ping via a .bat that was posted to Reddit a while back - US West obviously fair but obviously problems to EU and US East: Code: Australia: Paddington, New South Wales - (AU) Briggs: 331ms ====================================== Europa: Amsterdam, Holanda - (EU) Ceres: 224ms - (EU) Cobalt: 222ms - (EU) Lithcorp: 233ms - (EU) Mallory: 226ms - (EU) Miller): 226ms - (EU) Woodman: 223ms ====================================== US West: San Diego, California - (US West) Connery: 157ms - (US West) Genudine: 158ms - (US West) Helios: 157ms ====================================== US East: Ashburn, Virginia - (US East) Jaeger: 279ms - (US East) Mattherson: 278ms - (US East) SolTech: 279ms - (US East) Waterson: 279ms ======================================
On to the EU servers... Oh dear, same problems as the o2/Be users above. However it is Telefonica taking the connection to Paris (grtparix1) and it is the Telefonica to level3 connection where the ping spikes. Is this a Telefonica or Level3 issue? Code: C:\Users\Dave>tracert 195.33.132.169 Tracing route to amspsn-liv-gw05.planetside2.com [195.33.132.169] over a maximum of 30 hops: 1 33 ms 99 ms 99 ms bebox.config [192.168.1.254] 2 * * * Request timed out. 3 14 ms 14 ms 14 ms 10.1.3.245 4 * 20 ms 21 ms 10.1.2.169 5 * * 21 ms 10.1.4.245 6 59 ms 18 ms 18 ms xe4-1-6-0-GRTLONTL1.red.telefonica-wholesale.net [94.142.103.137] 7 19 ms 25 ms 25 ms Xe6-1-2-0-grtparix1.red.telefonica-wholesale.net [84.16.14.145] 8 27 ms 26 ms 27 ms Xe5-2-0-0-grtpartv1.red.telefonica-wholesale.net [84.16.14.181] 9 216 ms 214 ms * xe-9-0-0.edge4.Paris1.Level3.net [213.242.111.5] 10 222 ms * 220 ms ae-70-70.csw2.Paris1.Level3.net [4.69.168.126] 11 * 226 ms 228 ms ae-71-71.ebr1.Paris1.Level3.net [4.69.161.81] 12 223 ms 222 ms 230 ms ae-46-46.ebr1.London1.Level3.net [4.69.143.105] 13 229 ms 224 ms 228 ms vlan104.ebr2.London1.Level3.net [4.69.143.98] 14 230 ms 230 ms 231 ms ae-47-47.ebr2.Amsterdam1.Level3.net [4.69.143.77] 15 234 ms 231 ms * ae-59-224.csw2.Amsterdam1.Level3.net [4.69.153.214] 16 236 ms 229 ms 228 ms 4.69.162.193 17 141 ms 140 ms 140 ms SONY-ONLINE.edge4.Amsterdam1.Level3.net [212.72.42.182] 18 224 ms 229 ms 230 ms amspsn-liv-gw05.planetside2.com [195.33.132.169] Trace complete.
Interesting to see another o2 user having issues and following exactly the same route I have been.Mine has been like this since the evening (GMT) of July 1st. I think most of the problems are steming from Level3 rather than Telefonica however the hop does go from NYC to Palo Alto for some reason before Level3 takes over. The ping then goes through the roof when it really shouldnt. So as you said above, looks like both companies have issues but Level3 seems to be the more severe of the two. Heres hoping thye get it fixed soon as the game is unplayable currently. Although I do find it strange that the west coast servers are completely unaffected! No problems with ping, packet loss or routing, but it does avoid the Level3 network so that is probably why...
If Telefonica fix their routing and stop sending us to California both the big hops get cut out and it is problem solved. Mind trace routes are a bit iffy. I suspect there is also an issue with level3 but the biggest red flag here is everyone is on o2/Be. edit: come to think of it, maybe the issue is the telefonica to level3 connection in NYC, could be either at fault. If that is the case though there are surely more direct alternate routes http://www.internationalservices.telefonica.com/en/mapaFlash.html
I'm also with BE (o2 network). The game has been unplayable for the last few nights. It sucks Microsoft Windows [Version 6.0.6002] Copyright (c) 2006 Microsoft Corporation. All rights reserved. C:\Users\Mark>tracert 195.33.132.169 Tracing route to amspsn-liv-gw05.planetside2.com [195.33.132.169] over a maximum of 30 hops: 1 16 ms 98 ms 99 ms bebox.config [192.168.1.254] 2 14 ms 14 ms 14 ms 94-193-240-1.zone7.bethere.co.uk [94.193.240.1] 3 13 ms 13 ms 13 ms 10.1.3.245 4 20 ms 20 ms 21 ms 10.1.2.169 5 20 ms 20 ms 21 ms 10.1.4.245 6 18 ms 24 ms 99 ms xe4-1-6-0-GRTLONTL1.red.telefonica-wholesale.net [94.142.103.137] 7 25 ms 25 ms 20 ms Xe1-0-0-0-grtloneq1.red.telefonica-wholesale.net [94.142.117.201] 8 27 ms 73 ms 86 ms Xe0-0-6-0-grtpareq1.red.telefonica-wholesale.net [94.142.117.82] 9 212 ms 262 ms 220 ms 212.73.205.225 10 219 ms 219 ms 219 ms vlan80.csw3.Paris1.Level3.net [4.69.168.190] 11 220 ms 222 ms 229 ms ae-61-61.ebr1.Paris1.Level3.net [4.69.161.77] 12 226 ms 220 ms * ae-47-47.ebr1.London1.Level3.net [4.69.143.109] 13 225 ms 232 ms 224 ms vlan102.ebr2.London1.Level3.net [4.69.143.90] 14 234 ms 233 ms 226 ms ae-47-47.ebr2.Amsterdam1.Level3.net [4.69.143.77 ] 15 236 ms * 236 ms ae-58-223.csw2.Amsterdam1.Level3.net [4.69.153.2 10] 16 * 241 ms 221 ms 4.69.162.205 17 147 ms 147 ms 155 ms SONY-ONLINE.edge4.Amsterdam1.Level3.net [212.72. 42.182] 18 232 ms 220 ms 221 ms amspsn-liv-gw05.planetside2.com [195.33.132.169] Trace complete.
I'm also with BE (o2 network). Has anyone asked them also? have to wait till morning i guess.But we need lot of guys to tell them, on the tickets or forum or the live chat helpdesk
I have spoken to O2 customer support via Live Chat earlier this morning without any result. I explained the situation about the routing which seems fine until it hits the Level3 network, but apparently they are not aware of any issues. The Live Chat window did not allow to paste traceroutes in a readable form so I pasted the link for this thread, but they cannot open external links. The CS rep was friendly and did try, but it was mostly thing like "It might be the server which is lagging", "At peak times the internet can slow down" and "Try resetting your router" etc. When we got to the point of "Did you try a different browser" I knew I was not getting anywhere In the end he gave me the number of O2 customer support and suggested I give them a call. I am not really sure what to do anymore. Often internet problems are a case of "Waiting it out", but this problem has been going on since Monday now so I am a bit worried.
I managed to get a response via twitter, so hopefully they are looking at the info here https://twitter.com/O2/status/352747466099138562
Looks like Be might be on the case, there are a few threads on the forums but the mod there said any update will be posted to https://avatar.bethere.co.uk/forum/viewtopic.php?t=45868&highlight=
Having the same issues, again with Be, and not for the first time. I move in a month so shall be dumping them for BT.
I've made a post on the o2 community forums as requested by @o2 on twitter. If you have anything to add as an o2 customer, put it here: http://community.o2.co.uk/t5/Home-Broadband-Home-Phone/Packet-Loss-and-Bonkers-Routing/td-p/494762
Same issue. Also O2 customer. However, only trying to get in to Miller. Can't chime in with the thread as I'm not the one who stands for the contract. My housemate is and I don't have her password. But I've run the ping/traces and get very similar results.
Thanks. Between these three threads (here, o2 forums and BE forums) and twitter I'm sure they must be aware of the issue by now, the question now is do they care enough to fix it? Considering this thread was originally posted in April before we hijacked it, the answer to that question appears to be no. I've kicked off my installation process with Virgin, so we'll see which happens first.
I'm prerry sure the problem is on the interconnect from your provider with red.telefonica-wholesale.net edit: ah seems like you are already on to it, I didn't read further then the traces
Iam having the same problem since july 1st. I am from Argentina and never have this kind of lattency.I do not understand why iam passing through california and then to miami. Connecting to Connery (West US) with another character its ok of course. Posse from Argentina also in Waterson had the same issue (different ISP) but nows he told me his ping still 250ms but not lag at all. really weird. this is my current trace route 1 1 ms <1 ms <1 ms 192.168.1.1 2 25 ms 10 ms 10 ms 10.30.0.1 3 14 ms 29 ms 28 ms cpe-181-47-254-13.telecentro-reversos.com.ar [181.47.254.13] 4 22 ms 16 ms 22 ms 192.168.31.14 5 9 ms 20 ms 9 ms xe-0-1-0.ar3.eze1.gblx.net [208.178.195.209] [CALIFORNIA] 6 289 ms 212 ms 208 ms po2.ar3.MIA2.gblx.net [67.17.68.234] [FLORIDA] 7 140 ms 142 ms 149 ms LIMELIGHT-NETWORKS.TenGigabitEthernet8-2.ar3.MIA2.gblx.net [208.51.198.114] 8 147 ms 143 ms 153 ms ve5.fr3.mia1.llnw.net [68.142.125.97] 9 161 ms 165 ms 174 ms tge9-1.fr3.iad.llnw.net [69.28.189.73] 10 186 ms 185 ms 192 ms sony.ge4-12.fr3.iad.llnw.net [68.142.111.254] 11 269 ms * 285 ms abepsn-liv-gw04.planetside2.com [199.108.194.41]
I thought something like this might be going on. Haven't been able to get stable game play on Waterson for days. Connery, no problem
O2 customer here and i have the same issues, i guess my weekend of planetside double xp fun is pretty much not happening, as the last time they had an issue like this it took well over a week for them to get around to fixing, and that was before they were being bought out by another company
Bah, I was hoping I'd never see this thread again... I've not been able to log on all week due to work, just booted up PS2 to get some double exp action and like others it seems I'm suffering from packet loss again so the game is unplayable.... I almost purchased a 7 day exp boost when I logged in too, so I'm lucky I held off on that. I cant see this being fixed over the weekend, fingers crossed though I guess FYI, I didn't get a single response from TSR AlexS in the private conversation I started with him last time there was a packet loss issue, despite the fact he asked for details and data which I provided a lot of, I'm not sure they were even looked at. If I'm wrong then I apologise but some confirmation that they were read would have been nice. From experience, issues like this seem to get fixed after some time while game techies pretend they are interested and your ISP tells you it's anything but their service or something completely out of their control.
This is 100% an ISP issue and it's not the first time its happened with O2/Be because of absolutely bonkers routing and last time it took them well over a week to fix it and that was before they were in the middle of a take-over. My advice would be dump them first chance you get for a different ISP.
It's usually bad connection from ISP for me. When I get some warping around and de-sync I alt-tab open up command prompt and do a ping 8.8.8.8 -t 8.8.8.8 is google DNS, just something stable to ping -t is constant pinging not the default 4 pings that you get without it (as in it won't stop pinging until you cntr z or exit cmd prompt) Almost all of the time it's my connection to everything not just to game. Try it out.
