I appreciate you trying to help here Konstantinn, but any one of the traces in this thread makes it clear this is a routing issue. BE has since issued the following statement on their usergroup: "We are dealing with the issue and cooperating with our transit providers to resolve it as soon as possible. There is still no estimation for this, but I can assure you that we are working hard to fix this, as it is affecting too many of our customers."
I am so glad I am not the only one. I was even wondering it could come from my own connection (even if I had some doubts). For me it happens since the GU11 and it even disconnects my wifi router Oo Btw I'm from france and I play on Mattherson
Taken from http://status.bememberservices.com/ I wonder if this planned work relates to our packet loss issues?
Because I want to^^ do I have to justify everything while I am just paying to play a game? The fact is I didn't have the problem before. I hope it's the reason why...
Guys this is a tech support forum, take your handbag duels elsewhere please. It's possible, but that looks like an internal thing to me.
no, no, no. don't join a conversation about a problem you don't have and offer a useless advice, just don't do that. the problem is clearly on the servers and it should be fixed, there's nothing my ISP can do once the connection leaves their servers. whats really annoying is that there's no acknowledgment of the problem, i play EVE online, and almost a year back there was a connectivity issue affecting a small population using one particular isp. the problem ultimately was on CCPs ISP, so on day one they said "sorry, were working on a solution" and they kept a channel open informing us on how things were going, the problem took a whopping 4 weeks to get resolved, but no one lost their **** over it, the company was honest and gave us reports on how things were going... and since its a subscription based game all the game time was reimbursed, they even issued an fun ingame item commemorating the problem i been having this problem for almost 2 weeks now, cant play at all. im yet to see any official acknowledgment. and if i ticket it, im told "oh well, packet loss is on your side" really? on my side? if i connect to any other of your own servers im fine! i don't even have to "test" by playing another game!
I'm from Argentina and I have the same issue, so it seems it's not a UK-based problem, it's something on their side. It started with GU11 for me, it was annoying but still playable though, but this weekend it became completely unplayable, I see people warping everywhere, etc. My ping with US East servers in any game (including PS2) has always been 150-200, but now I'm getting 260-300ms all the time. The strange thing is that I tried getting into Connery and it works just fine, Waterson and Mattherson are equally unplayable. This is the result of a trace to all 3 servers Waterson: Mattherson: Connery:
The problem is, and has already been acknowledged as peering between level3 causing traffic to be bounced around the world instead of going via a direct route. Peering is essentially a shortcut between your ISP and other major networks and as such it is entirely up to your ISP to leverage a solution. Please can we stop throwing things around and beating our chests in this thread, there are plenty of other places to do that. This is a technical support forum, keep the information technical so we can expedite a resolution rather than creating another YouTube quality flame-a-thon. Thanks.
The thing that bugs me about this packet loss issue is that for a few hours during the day (when I'm normally at work) everything seems fine and the packet loss is gone, but then on "peak" hours, and for some time before and after, packets are being lost left right and centre (However over the weekend I got constant packet loss regardless of time, but if I'm honest had pretty much given up hope and wasn't looking at the connection as often as last time this happened). It was the exact same thing going on when I originally made this thread, and TBH kinda makes it feel like its intentional, or at the very least points to being something to do with peak time routing/throttling. here's some stats from earlier today and a few minutes ago...
It's definitely better during the daytime before around 4pm, but I've checked the traces and ping times. The route is the same, and ping times are still 220+. The only difference is the frequency of lost packets which is what actually makes the game unplayable as opposed to just laggy and unresponsive, but dropped packets could be attributed to load. Even if packets weren't being dropped so frequently, London to Amsterdam should not go via four places in Paris, three in Frankfurt and 2 in Dusseldorf, and the ping should be 23 not 223. At the moment I actually get a lower ping to west coast America and Australia; if that isn't an indication that the peering is hopelessly busted I don't know what is. Yours does look a different to the other traces I've seen though, so perhaps it's not the same issue. Everyone else I've looked at is hitting the level3 network and that's where the enormous pings kick in. I've apparently gained a few more hops since I first posted here too, making it even longer. Code: Tracing route to amspsn-liv-gw04.planetside2.com [195.33.132.168] over a maximum of 30 hops: 1 2 ms <1 ms <1 ms jimmeh [192.168.0.1] 2 19 ms 25 ms 18 ms 94-193-104-1.zone7.bethere.co.uk [94.193.104.1] 3 19 ms 19 ms 20 ms 10.1.3.178 4 * * * Request timed out. 5 52 ms 20 ms 20 ms xe4-1-6-0-GRTLONTL1.red.telefonica-wholesale.net [94.142.103.137] 6 35 ms 46 ms 20 ms Xe1-0-0-0-grtloneq1.red.telefonica-wholesale.net [94.142.117.201] 7 54 ms 22 ms 41 ms Xe0-0-6-0-grtpareq1.red.telefonica-wholesale.net [94.142.117.82] 8 213 ms * 242 ms xe-9-0-0.edge4.Paris1.Level3.net [213.242.111.5] 9 228 ms 224 ms 230 ms vlan90.csw4.Paris1.Level3.net [4.69.168.254] 10 223 ms 229 ms 247 ms ae-92-92.ebr2.Paris1.Level3.net [4.69.161.105] 11 232 ms 229 ms * ae-46-46.ebr1.Frankfurt1.Level3.net [4.69.143.137] 12 223 ms 237 ms 228 ms ae-71-71.csw2.Frankfurt1.Level3.net [4.69.140.6] 13 224 ms 224 ms 226 ms ae-93-93.ebr3.Frankfurt1.Level3.net [4.69.163.13] 14 237 ms 246 ms 244 ms ae-48-48.ebr1.Dusseldorf1.Level3.net [4.69.143.177] 15 * 227 ms 225 ms ae-22-22.ebr2.Dusseldorf1.Level3.net [4.69.143.186] 16 231 ms 235 ms 235 ms ae-47-47.ebr1.Amsterdam1.Level3.net [4.69.143.205] 17 239 ms 229 ms 237 ms ae-58-113.csw1.Amsterdam1.Level3.net [4.69.153.194] 18 240 ms * * 4.69.162.189 19 148 ms 149 ms 149 ms SONY-ONLINE.edge4.Amsterdam1.Level3.net [212.72.42.182] 20 242 ms 228 ms 232 ms amspsn-liv-gw04.planetside2.com [195.33.132.168]
Code: 3 * 18 ms 18 ms O2UK-5-0-8-GRTLONTL1.6.16.84.in-addr.arpa [84.16 .6.190] 4 49 ms 58 ms 43 ms xe4-1-6-0-GRTLONTL1.red.telefonica-wholesale.net [94.142.103.137] 5 19 ms 95 ms 69 ms Xe6-1-2-0-grtparix1.red.telefonica-wholesale.net [84.16.14.145] 6 25 ms 32 ms 25 ms Xe5-2-0-0-grtpartv1.red.telefonica-wholesale.net [84.16.14.181] 7 25 ms 26 ms 26 ms 212.73.205.225 8 49 ms 41 ms 41 ms vlan80.csw3.Paris1.Level3.net [4.69.168.190] 9 42 ms 49 ms 41 ms ae-82-82.ebr2.Paris1.Level3.net [4.69.161.101] 10 41 ms 41 ms 41 ms ae-46-46.ebr1.Frankfurt1.Level3.net [4.69.143.13 7] 11 49 ms 49 ms 42 ms ae-71-71.csw2.Frankfurt1.Level3.net [4.69.140.6] 12 41 ms 41 ms 41 ms ae-73-73.ebr3.Frankfurt1.Level3.net [4.69.163.5] 13 41 ms 48 ms 49 ms ae-45-45.ebr1.Dusseldorf1.Level3.net [4.69.143.1 65] 14 49 ms 41 ms 46 ms ae-22-22.ebr2.Dusseldorf1.Level3.net [4.69.143.1 86] 15 49 ms 41 ms 41 ms ae-48-48.ebr1.Amsterdam1.Level3.net [4.69.143.20 9] 16 41 ms 42 ms 42 ms ae-59-114.csw1.Amsterdam1.Level3.net [4.69.153.1 98] 17 49 ms 41 ms 42 ms 4.69.162.189 18 43 ms 49 ms 42 ms SONY-ONLINE.edge4.Amsterdam1.Level3.net [212.72. 42.182] 19 41 ms 41 ms 40 ms amspsn-liv-gw04.planetside2.com [195.33.132.168] My tracert is similarly bonkers and most people suffering from this problem with Be/O2 are seeing the same thing -- and it's affecting lots of different services not just Planetisde. I also highly doubt it is throttling because the problem wouldn't be intermittent and seemingly affect any given on-line service by potluck.
Looks like it's finally sorted. It's still going the same convoluted route, but the the pings are much more acceptable. 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 19 ms 19 ms 19 ms 94-193-104-1.zone7.bethere.co.uk [94.193.104.1] 3 21 ms 19 ms 21 ms 10.1.3.178 4 * * * Request timed out. 5 18 ms 19 ms 20 ms xe4-1-6-0-GRTLONTL1.red.telefonica-wholesale.net [94.142.103.137] 6 26 ms 28 ms 17 ms Xe1-0-0-0-grtloneq1.red.telefonica-wholesale.net [94.142.117.201] 7 91 ms 23 ms 27 ms 176.52.250.113 8 24 ms 32 ms 34 ms xe-9-0-0.edge4.Paris1.Level3.net [213.242.111.5] 9 50 ms 48 ms 50 ms vlan90.csw4.Paris1.Level3.net [4.69.168.254] 10 41 ms 39 ms 38 ms ae-62-62.ebr2.Paris1.Level3.net [4.69.161.93] 11 44 ms 39 ms 39 ms ae-46-46.ebr1.Frankfurt1.Level3.net [4.69.143.137] 12 51 ms 49 ms 50 ms ae-91-91.csw4.Frankfurt1.Level3.net [4.69.140.14] 13 41 ms 46 ms 49 ms ae-73-73.ebr3.Frankfurt1.Level3.net [4.69.163.5] 14 44 ms 46 ms 42 ms ae-46-46.ebr1.Dusseldorf1.Level3.net [4.69.143.169] 15 41 ms 41 ms 46 ms ae-22-22.ebr2.Dusseldorf1.Level3.net [4.69.143.186] 16 48 ms 42 ms 39 ms ae-47-47.ebr1.Amsterdam1.Level3.net [4.69.143.205] 17 42 ms 40 ms 39 ms ae-58-113.csw1.Amsterdam1.Level3.net [4.69.153.194] 18 56 ms 49 ms 57 ms 4.69.162.189 19 47 ms 49 ms 42 ms SONY-ONLINE.edge4.Amsterdam1.Level3.net [212.72.42.182] 20 53 ms 47 ms 42 ms amspsn-liv-gw04.planetside2.com [195.33.132.168]
Not fixed for me Still getting packet loss and the bonkers routing. Trace for Waterson is below.... Code: Tracing route to abepsn-liv-gw04.planetside2.com [199.108.194.41] over a maximum of 30 hops: 1 73 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 40 ms 40 ms 40 ms 10.17.88.1 4 * 39 ms 40 ms O2UK-5-0-8-GRTLONTL1.6.16.84.in-addr.arpa [84.16.6.190] 5 39 ms 61 ms 59 ms xe-3-0-8-0-grtlontl1.red.telefonica-wholesale.net [84.16.6.209] 6 113 ms 108 ms 110 ms Xe4-1-1-0-grtnycpt2.red.telefonica-wholesale.net [94.142.119.65] 7 177 ms 176 ms 176 ms Xe0-1-0-0-grtpaopx2.red.telefonica-wholesale.net [94.142.125.81] 8 185 ms 186 ms 185 ms te-4-2.car1.SanJose2.Level3.net [4.59.0.225] 9 309 ms 305 ms 308 ms vlan80.csw3.SanJose1.Level3.net [4.69.152.190] 10 301 ms 300 ms 303 ms ae-81-81.ebr1.SanJose1.Level3.net [4.69.153.9] 11 300 ms 303 ms 302 ms ae-2-2.ebr2.NewYork1.Level3.net [4.69.135.186] 12 305 ms 306 ms 308 ms 4.69.201.38 13 299 ms 300 ms * ae-1-100.ebr1.NewYork2.Level3.net [4.69.135.253] 14 299 ms 332 ms 300 ms 4.69.201.89 15 301 ms 302 ms 304 ms ae-62-62.csw1.Washington1.Level3.net [4.69.134.146] 16 * * 302 ms ae-1-60.edge1.Washington4.Level3.net [4.69.149.15] 17 217 ms 223 ms 217 ms SONY-ONLINE.edge1.Washington4.Level3.net [4.53.112.6] 18 301 ms 300 ms 300 ms abepsn-liv-gw04.planetside2.com [199.108.194.41] Trace complete. Hop 5 - 6 is London to New York and is normal, 6 - 7 is where is all goes wrong when it jumps from NYC to Palo Alto
EU players might want to check their ping, mine is down to a tolerable level (though not checked packetloss and still going on a silly route). However no change to the US server where my main is
My tracert to Miller [195.33.132.168] is showing erratic pings compared to yours. Jimmeh, is there any chance you can do a trace route to Mattherson [199.108.194.38] and post the results, I'd like to see if your route and ping times are similar to mine. (In your comment above regarding my earlier post, my tracert was to Mattherson, hence why it looks different to your EU server trace routes). If anyone else who is based in the UK on O2/BE and is suffering from packet loss can post their trace routes to Mattherson [199.108.194.38] as well, that may be useful. Thanks. Code: Tracing route to amspsn-liv-gw04.planetside2.com [195.33.132.168] over a maximum of 30 hops: 1 102 ms 99 ms 99 ms O2wirelessbox.lan 2 * * * Request timed out. 3 * * * Request timed out. 4 * 21 ms 21 ms 10.1.3.214 5 * * * Request timed out. 6 56 ms 109 ms 29 ms O2-UK-4-0-8-0-GRTLONTL1.red.telefonica-wholesale.net [94.142.103.133] 7 28 ms 67 ms 21 ms Xe1-0-0-0-grtloneq1.red.telefonica-wholesale.net[94.142.117.201] 8 56 ms 28 ms 28 ms Xe7-1-8-0-grtpareq1.red.telefonica-wholesale.net[84.16.14.113] 9 82 ms 80 ms 79 ms xe-9-0-0.edge4.Paris1.Level3.net [213.242.111.5] 10 97 ms 96 ms 103 ms ae-60-60.csw1.Paris1.Level3.net [4.69.168.62] 11 89 ms 95 ms 95 ms ae-92-92.ebr2.Paris1.Level3.net [4.69.161.105] 12 97 ms 89 ms 90 ms ae-47-47.ebr1.Frankfurt1.Level3.net [4.69.143.141] 13 * * * Request timed out. 14 99 ms 91 ms 99 ms ae-63-63.ebr3.Frankfurt1.Level3.net [4.69.163.1] 15 98 ms 105 ms 98 ms ae-47-47.ebr1.Dusseldorf1.Level3.net [4.69.143.173] 16 113 ms 109 ms 102 ms ae-24-24.ebr2.Dusseldorf1.Level3.net [4.69.143.194] 17 104 ms 105 ms 106 ms ae-47-47.ebr1.Amsterdam1.Level3.net [4.69.143.205] 18 100 ms 99 ms 98 ms ae-56-111.csw1.Amsterdam1.Level3.net [4.69.153.186] 19 95 ms 93 ms 101 ms 4.69.162.181 20 53 ms 45 ms 45 ms SONY-ONLINE.edge4.Amsterdam1.Level3.net [212.72.42.182] 21 98 ms 96 ms 107 ms amspsn-liv-gw04.planetside2.com [195.33.132.168] Trace complete.
Still pretty awful to Matterson for me, certainly much worse than yours anyway. 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 jimmeh [192.168.0.1] 2 * * * Request timed out. 3 15 ms 19 ms 20 ms 10.1.3.178 4 17 ms 19 ms 20 ms 10.1.4.241 5 20 ms 19 ms 24 ms O2-UK-4-0-8-0-GRTLONTL1.red.telefonica-wholesale.net [94.142.103.133] 6 85 ms 84 ms 85 ms Xe5-0-2-0--grtnycpt3.red.telefonica-wholesale.net [213.140.38.157] 7 154 ms 154 ms 155 ms Xe9-3-0-0-grtpaopx2.red.telefonica-wholesale.net [94.142.118.186] 8 168 ms 170 ms 180 ms te-4-2.car1.SanJose2.Level3.net [4.59.0.225] 9 276 ms 275 ms 274 ms vlan80.csw3.SanJose1.Level3.net [4.69.152.190] 10 * 274 ms 276 ms ae-81-81.ebr1.SanJose1.Level3.net [4.69.153.9] 11 276 ms 275 ms 274 ms ae-2-2.ebr2.NewYork1.Level3.net [4.69.135.186] 12 * 275 ms 274 ms ae-46-46.ebr2.NewYork2.Level3.net [4.69.201.30] 13 * 273 ms 274 ms ae-1-100.ebr1.NewYork2.Level3.net [4.69.135.253] 14 * 283 ms 283 ms 4.69.132.89 15 275 ms 273 ms 278 ms ae-92-92.csw4.Washington1.Level3.net [4.69.134.158] 16 271 ms * 313 ms ae-4-90.edge1.Washington4.Level3.net [4.69.149.207] 17 204 ms 204 ms 203 ms SONY-ONLINE.edge1.Washington4.Level3.net [4.53.112.6] 18 285 ms * 280 ms abepsn-liv-gw01.planetside2.com [199.108.194.38]
Kind of important update to this... The following was posted by a outfit member of mine. Info given is from a email and explains pretty much everything - lag and bonkers routing. ---------- There is work being done on the TAT-14 system. It is a major trans Atlantic fiber system. >>>>> Originally Posted by : 20-06-2013 16:16 UTC: TAT-14 will be replacing six repeaters on Segment K in a two ship operat ion in J uly which will minimize segment downtime. The current POW indicates segment operations commencing on July 6th and continuing until July 30th. There are no contingencies built into this schedule. A ring switch to remove all NPE traffic from Segment K is currently scheduled for July 5th occurring at the beginning of the maintenance window at 2300hrs UTC. DWA traffic will remain up until PSC is turned over to the ships on July 6th. The dates may change slightly to accommodate the ships actual mobilization and transit to the cable grounds. There will be ring switch hits on STM-16 below and all the wavelength (10G) circuits riding on segment K will be down for the duration of the activity. 08-07-2013, 22:37 UTC: The Cable Stations have shutdown DWA traffic and depowered Segment K as of July 8 2210hrs UTC. The C.S. Rene Descartes has arrived on the cable grounds and will commence with the KR-087 repeater replacement shortly. >>>>> As far as I can tell by the link I have that uses it the system is still down. I don't have an ETA but it could be a while. They are replacing 6 repeaters at the bottom of the ocean. So it could be that way until the end of the month or longer if the ship has any troubles like bad weather. ------------ The above is highly likely to be the cause of our woes Will let you know if I can get any more info.
Heh, well I posted all that stuff above and 3 hours later I find that the latency is much more acceptable with no packet loss. The bonkers routing issue is still there but for now, I'll take the 190ms ping and play again!
