Tideswell Mass DC during NW
Comments
-
This content has been removed.
-
I'm not an alt and I'm having the same problem. 100% sure they need to upgrade some stuff.
http://i60.tinypic.com/2zemfxl.jpg0 -
I was not in NW but did have some severe lag, however never fully DCed so I doubt it was the server. It was probably their ISP which like any ISP can have issues.
Be Strong! Be Fierce! Be Vicious!
Vicious Marshal - Tideswell0 -
Here we go again. Kitty got booted again exactly one hour into NW.
Tracert:7 95 ms 28 ms 28 ms ae2-20.br2.esp1.fi.eunetip.net [213.192.191.34]
8 77 ms 55 ms 55 ms so0-0-0-0.bbr1.ldn1.uk.eunetip.net [213.192.191.
178]
9 59 ms 59 ms 59 ms ge-2-1-0.mpr1.lhr2.uk.above.net [195.66.224.76]
10 59 ms 57 ms 58 ms ae10.mpr2.lhr2.uk.zip.zayo.com [64.125.31.194]
11 125 ms 124 ms 123 ms v113.ae29.cr1.lga5.us.zip.zayo.com [64.125.30.10
8]
12 149 ms 129 ms 136 ms ae7.mpr3.bos2.us.zip.zayo.com [64.125.21.225]
13 141 ms 127 ms 128 ms 208.184.110.70.IPYX-072053-002-ZYO.above.net [20
8.184.110.70]
14 165 ms 130 ms 130 ms border11.te8-1-bbnet2.bsn.pnap.net [63.251.128.1
04]
15 205 ms 127 ms 126 ms perfectworldent-4.border11.bsn.pnap.net [216.52.
61.78]
16 138 ms 165 ms 144 ms 198.49.243.250
17 217 ms 135 ms 138 ms 198.49.243.253
18 * * * Pyyntö aikakatkaistiin.
19 * * * Pyyntö aikakatkaistiin.
20 138 ms 134 ms 135 ms 198.49.243.16
Seuranta suoritettu.
But, Kitty thinks she figured how to get back into NW: just wait until NW has room again.
Kitty tried to take a screenshot of that "max instance reached message", but her login timed out while copypastaing tracert and when she logged back in she didn't get that message again and she spawned in nation base. That was like 3rd relog.
So, if you get booted from NW, wait like 5 mins and try relogging. If the message comes up, press cancel and wait a bit more.
And this makes it pretty obvious that it's an instance server-issue like Kitty previously thought. 
Kitty's gone. She gave up on PWI. And she's a black metal Kitty naow.
Kitty's Youtube-channel("Kitty does eet"-series and much moar): KittysamaRT
Get the Forums Enhancement Extension!0 -
Well, you left out the first 6 hops, so it's hard to say how much of a problem you're having there.kittyempressa wrote: »Here we go again. Kitty got booted again exactly one hour into NW.
Tracert:7 95 ms 28 ms 28 ms ae2-20.br2.esp1.fi.eunetip.net [213.192.191.34]
8 77 ms 55 ms 55 ms so0-0-0-0.bbr1.ldn1.uk.eunetip.net [213.192.191.
178]
9 59 ms 59 ms 59 ms ge-2-1-0.mpr1.lhr2.uk.above.net [195.66.224.76]
10 59 ms 57 ms 58 ms ae10.mpr2.lhr2.uk.zip.zayo.com [64.125.31.194]
11 125 ms 124 ms 123 ms v113.ae29.cr1.lga5.us.zip.zayo.com [64.125.30.10
8]
12 149 ms 129 ms 136 ms ae7.mpr3.bos2.us.zip.zayo.com [64.125.21.225]
13 141 ms 127 ms 128 ms 208.184.110.70.IPYX-072053-002-ZYO.above.net [20
8.184.110.70]
14 165 ms 130 ms 130 ms border11.te8-1-bbnet2.bsn.pnap.net [63.251.128.1
04]
15 205 ms 127 ms 126 ms perfectworldent-4.border11.bsn.pnap.net [216.52.
61.78]
16 138 ms 165 ms 144 ms 198.49.243.250
17 217 ms 135 ms 138 ms 198.49.243.253
18 * * * Pyyntö aikakatkaistiin.
19 * * * Pyyntö aikakatkaistiin.
20 138 ms 134 ms 135 ms 198.49.243.16
Seuranta suoritettu.
But, Kitty thinks she figured how to get back into NW: just wait until NW has room again.
Kitty tried to take a screenshot of that "max instance reached message", but her login timed out while copypastaing tracert and when she logged back in she didn't get that message again and she spawned in nation base. That was like 3rd relog.
So, if you get booted from NW, wait like 5 mins and try relogging. If the message comes up, press cancel and wait a bit more.
And this makes it pretty obvious that it's an instance server-issue like Kitty previously thought.
Your route goes to **** pretty much starting right at the section you posted, then just continues downhill from there. It starts to really tank at hop 11, but it wasn't healthy before that.
Basically, you've shown a traceroute that indicates the issue is not on the server side, and begins about halfway before you get to the server at least. (It might start earlier, but we cannot tell because you excluded that information.)0 -
sylenthunder wrote: »Well, you left out the first 6 hops, so it's hard to say how much of a problem you're having there.
Your route goes to **** pretty much starting right at the section you posted, then just continues downhill from there. It starts to really tank at hop 11, but it wasn't healthy before that.
Basically, you've shown a traceroute that indicates the issue is not on the server side, and begins about halfway before you get to the server at least. (It might start earlier, but we cannot tell because you excluded that information.)
Kitty left out first 6 hops as she'd rather not have her IP easily locateable. And that tracert was completely normal for Kitty's 4G mobile broadband connection. If Kitty had any real problems with her connection, some hops would be like 300-500ms at least. Actually, tracert usually gives higher ping than the one Kitty posted.
And once again, if the issue WEREN'T on the server side, client shouldn't give that "max instances reached"-message. Just how you think nodes outside PWE could be related to that message? You seem to be ignoring that "max instances reached" completely. THAT's the real problem here, Kitty thinks. If it were interwebz problem, we should be able to instantly enter PWI once we get to character selection-screen (and trying to get to character selection-screen would be the problem if the problem was with interwebz), appearing in nation base.
Kitty tried to remember details from Friday's NW and from what she remembered, lots of people kicked were from same battles Kitty had participated just a little earlier.
So Kitty can think of two possible circumstances for this bug to happen. First: the issue might be that server can't keep enough many NW battle instances open at once and thus kicks people from instances it can't load properly, disconnecting them to make them able to return to that battle instance(which server doesn't seem to understand can't be returned to directly after dc)...while, if it wasn't bugged, server should return players to base instead. The problem with this theory would be that what happens to empty instances as they'd be visible on map as 0vs0? Also how many battle instances would be max? Kitty doesn't know 'cause she got kicked in both NWs (though managed to return today by waiting) and thus doesn't know what exactly happened to player numbers/stuff WHILE she was offline(except that on Friday lots of people, about 100-120, appeared in Wellspring after that mass dc).
Another chance might be that server's NW-instance has limited amount of players it can withstand and thus starts kicking after player quota is full. And again, kicking off to login screen so they can wait 'til NW has room again. That would also explain why it offers returning to Wellspring Village if "max instances reached".
If the latter is the case, Tideswell's NW instance can hold max. 550-600 players. That would explain why more people got kicked during Friday's NW(NW had about 700 participants at start, Kitty doesn't know how many after server kicked lots of people off) than during today's NW(about 600 participants at start, 500 about 1h 20 mins into NW).
Kitty's gone. She gave up on PWI. And she's a black metal Kitty naow.
Kitty's Youtube-channel("Kitty does eet"-series and much moar): KittysamaRT
Get the Forums Enhancement Extension!0 -
Isn't the cap on the instance 500 people? If you have 600-700 go in, and the cap is 500, then 1-200 are getting kicked out.
I may be wrong, but pretty sure that it was stated the limit on NW is 500.0 -
sylenthunder wrote: »Isn't the cap on the instance 500 people? If you have 600-700 go in, and the cap is 500, then 1-200 are getting kicked out.
I may be wrong, but pretty sure that it was stated the limit on NW is 500.
Then that would explain it. But Kitty thinks the cap wasn't always that low.
When NW was quite a new thingie there were 800+ participant NWs on most active servers if Kitty's not totally mistaken.
So, to resolve this issue they better increase the cap if that's the problem. Current cap isn't enough for merged servers.
Kitty's gone. She gave up on PWI. And she's a black metal Kitty naow.
Kitty's Youtube-channel("Kitty does eet"-series and much moar): KittysamaRT
Get the Forums Enhancement Extension!0 -
kittyempressa wrote: »Kitty left out first 6 hops as she'd rather not have her IP easily locateable.
I usually ignore your posts because I hate when people refer to themselves in the third person and use horrible colors. However I'll make an exclusion for just this: if you're that worried about the first six hops revealing information, just replace the IP and DNS entry with something else or say "Hidden 1", "Hidden 2", etc (try to note which ones are your devices though). Leaving the first six out entirely though leaves us with very little to understand about the rest of the trace. For all we know the first hop was 26ms and so the 7th hop being 28ms would not be unusual. If you understand what I mean.
Did anyone bother to monitor the server while playing during NW? I'm not talking a single trace done with the tracert command. I'm talking monitoring through PingPlotter or similar software. For all we know at this point is that if a lot of people were having problems, it could conceivably, but not necessarily, be any of these things: failing regional node, PWE's ISP (Cogent) failing, PWE's east routing device failing, server overcrowding (the server has a limit of people that can log in without pushing memory out of its limit), or unknown other issues regarding other things.
What I'm trying to say is, like usual, sitting here without really substantial proof, it all just looks like who ****ing knows. You guys, I beg of you, instead of writing long stories about your problems and speculating about what-ifs based on nothing more than anecdotal evidence and limited experiences, just post data. Lots and lots of data. Nothing is as important to understanding all of this except for data. Sylen and I both couldn't care less about your ideas on how you think things work or how you think they should work. Data is the only thing that will bring out any idea of what's happening so that blame can be put in the right place as to cause some type of change. If it's Cogent, we can complain to Cogent. If it's PWE, we can send in tickets with proven data. My point is that this cycle of repeated blame without substantial evidence is just getting really irritating. You're doing nothing more than being a judge in court who, without seeing any evidence, finds the defendant, PWE in this case, guilty.
Now that I'm done ranting, I'm going to go enjoy my night.
GAME FORUMS (Direct Link & Arc Frame)Forum Enhancements and Visual Improvements(Greasemonkey/Tampermonkey and/or Stylish required)PWI vBulletin Forum Data Dumps and Backups0 -
I'm from Argentina and got the same dc as other ppl in Europe, USA and other countrys, all at the same time and after relog almost no one was able to enter NW again.
C:\WINDOWS\system32>tracert pwigc2.perfectworld.com
Traza a la dirección pwigc2.perfectworld.com [66.151.133.71]
sobre un máximo de 30 saltos:
1 1 ms 3 ms 1 ms 192.168.1.1
2 15 ms 15 ms 15 ms host132.200-3-60.telecom.net.ar [200.3.60.132]
3 24 ms 27 ms 26 ms host9.186-153-152.telecom.net.ar [186.153.152.9]
4 24 ms 36 ms 24 ms host189.190-225-254.telecom.net.ar [190.225.254.189]
5 28 ms 23 ms 23 ms host162.190-225-252.telecom.net.ar [190.225.252.162]
6 22 ms 23 ms 23 ms 195.22.220.213
7 171 ms 150 ms 152 ms 195.22.199.177
8 139 ms 139 ms 139 ms 89.221.41.175
9 139 ms 139 ms 140 ms xe-1-2-0.mia10.ip4.gtt.net [77.67.71.97]
10 222 ms 223 ms 222 ms et-4-1-0.sjc10.ip4.gtt.net [89.149.129.205]
11 226 ms 224 ms 304 ms internap-gw.ip4.gtt.net [77.67.70.26]
12 216 ms 234 ms 213 ms border2.t7-1-bbnet1.sje004.pnap.net [66.151.144.20]
13 228 ms 228 ms 228 ms perfectworld-10.border2.sje004.pnap.net [64.95.143.190]
14 228 ms 231 ms 233 ms 66.151.133.71
Traza completa.
0 -
See that huge spike it takes at hop 7?. That's where your data stream starts going south. Not seeing any noticeable increase on PWE's end at all there.sunsetrower wrote: »I'm from Argentina and got the same dc as other ppl in Europe, USA and other countrys, all at the same time and after relog almost no one was able to enter NW again.
C:\WINDOWS\system32>tracert pwigc2.perfectworld.com
Traza a la dirección pwigc2.perfectworld.com [66.151.133.71]
sobre un máximo de 30 saltos:
1 1 ms 3 ms 1 ms 192.168.1.1
2 15 ms 15 ms 15 ms host132.200-3-60.telecom.net.ar [200.3.60.132]
3 24 ms 27 ms 26 ms host9.186-153-152.telecom.net.ar [186.153.152.9]
4 24 ms 36 ms 24 ms host189.190-225-254.telecom.net.ar [190.225.254.189]
5 28 ms 23 ms 23 ms host162.190-225-252.telecom.net.ar [190.225.252.162]
6 22 ms 23 ms 23 ms 195.22.220.213
7 171 ms 150 ms 152 ms 195.22.199.177
8 139 ms 139 ms 139 ms 89.221.41.175
9 139 ms 139 ms 140 ms xe-1-2-0.mia10.ip4.gtt.net [77.67.71.97]
10 222 ms 223 ms 222 ms et-4-1-0.sjc10.ip4.gtt.net [89.149.129.205]
11 226 ms 224 ms 304 ms internap-gw.ip4.gtt.net [77.67.70.26]
12 216 ms 234 ms 213 ms border2.t7-1-bbnet1.sje004.pnap.net [66.151.144.20]
13 228 ms 228 ms 228 ms perfectworld-10.border2.sje004.pnap.net [64.95.143.190]
14 228 ms 231 ms 233 ms 66.151.133.71
Traza completa.0 -
Not doing anything in game atm came back to read through the thread. Having read some of the other posts in the thread here - if the NW event has a max player capacity of EG: 500 - that would mean 125 players per nation on average. I know that attendance was quite near that amount prior to the mass DC that happened before I posted - and I know that nation attendance was close to that much AFTER the DC as well, having asked someone who hadnt been booted. What may have happened is IF several people were logging in to NW late (it happens, but im not sure how 40 or so people could manage it all at once beyond sheer coincidence) then it MAY be possible that IF the server were reading high ping rates on certain players it MIGHT have read them as not inside the instance at the moment when others were entering. This could be - 4 squads of people making a late entry or perhaps at the most extreme someone logging a bunch of alt accounts on LAN connection. Possible? I guess. Probable? Who knows.
Well, you left out the first 6 hops, so it's hard to say how much of a problem you're having there.sylenthunder said:kittyempressa wrote: »Here we go again. Kitty got booted again exactly one hour into NW.
Tracert:Spoiler:7 95 ms 28 ms 28 ms ae2-20.br2.esp1.fi.eunetip.net [213.192.191.34]
8 77 ms 55 ms 55 ms so0-0-0-0.bbr1.ldn1.uk.eunetip.net [213.192.191.
178]
9 59 ms 59 ms 59 ms ge-2-1-0.mpr1.lhr2.uk.above.net [195.66.224.76]
10 59 ms 57 ms 58 ms ae10.mpr2.lhr2.uk.zip.zayo.com [64.125.31.194]
11 125 ms 124 ms 123 ms v113.ae29.cr1.lga5.us.zip.zayo.com [64.125.30.10
8]
12 149 ms 129 ms 136 ms ae7.mpr3.bos2.us.zip.zayo.com [64.125.21.225]
13 141 ms 127 ms 128 ms 208.184.110.70.IPYX-072053-002-ZYO.above.net [20
8.184.110.70]
14 165 ms 130 ms 130 ms border11.te8-1-bbnet2.bsn.pnap.net [63.251.128.1
04]
15 205 ms 127 ms 126 ms perfectworldent-4.border11.bsn.pnap.net [216.52.
61.78]
16 138 ms 165 ms 144 ms 198.49.243.250
17 217 ms 135 ms 138 ms 198.49.243.253
18 * * * Pyyntö aikakatkaistiin.
19 * * * Pyyntö aikakatkaistiin.
20 138 ms 134 ms 135 ms 198.49.243.16
Seuranta suoritettu.
But, Kitty thinks she figured how to get back into NW: just wait until NW has room again.
Kitty tried to take a screenshot of that "max instance reached message", but her login timed out while copypastaing tracert and when she logged back in she didn't get that message again and she spawned in nation base. That was like 3rd relog.
So, if you get booted from NW, wait like 5 mins and try relogging. If the message comes up, press cancel and wait a bit more.
And this makes it pretty obvious that it's an instance server-issue like Kitty previously thought.
Your route goes to **** pretty much starting right at the section you posted, then just continues downhill from there. It starts to really tank at hop 11, but it wasn't healthy before that.
Basically, you've shown a traceroute that indicates the issue is not on the server side, and begins about halfway before you get to the server at least. (It might start earlier, but we cannot tell because you excluded that information.)
perhaps she's got some high ping rates there - arguably much higher than my own even. However I've compared the routes I posted along with the route she posted, as well as the latest tracert I just took myself and none of the hops we go through match up until hitting PWE's own routers starting (on my end) at 198.49.243.253By the light of the moon, our true forms are revealed.0 -
So today, mass dc'ing again today. Still saying it's on my end? Well funny how out of the 3 PCs that where running in my house, all of them on PWI none dc'ed the 1st round of dcs, then only 2 dc'ed in the 2nd round of dcs. The third round only one PC, the 4 only one, the 5th 2 pcs. This last one all three and we can't get back on. We also had lag spikes, so if it's on my end wonder why only some of us had issues and why there were so many in the game that had the same issues. They here not all at my house. lol Well I'm done. Going to go play ~removed~ Since PWI can't get there ~removed~together.Post edited by sylenthunder on0
-
Simply the fact that not everyone DC'ed at once proves it's not on the server. What you're describing is almost exactly the description of a regional hub issue.sensualsoul wrote: »So today, mass dc'ing again today. Still saying it's on my end? Well funny how out of the 3 PCs that where running in my house, all of them on PWI none dc'ed the 1st round of dcs, then only 2 dc'ed in the 2nd round of dcs. The third round only one PC, the 4 only one, the 5th 2 pcs. This last one all three and we can't get back on. We also had lag spikes, so if it's on my end wonder why only some of us had issues and why there were so many in the game that had the same issues. They here not all at my house. lol Well I'm done. Going to go play G W 2 Since PWI can't get there chit together.
Not your end.
Not PWE's end.
However, right now there's a thread I stickied on this already. PWE's East Coast servers are under a DDoS attack.
Also, each client connection has it's own individual packet stream. It's very possible for one client's packets to get dropped where another client's won't.
Don't let the door hit you in the **** on the way out.
0 -
not seeing that sticky thread youre talking about, but i just tracerted a few more times after getting dc'd only a few minutes after logging on (which coincidentally was right after NW ended).
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Chris>tracert pwieast2.perfectworld.com
Tracing route to pwieast2.perfectworld.com [198.49.243.16]
over a maximum of 30 hops:
1 12 ms 12 ms 14 ms 192.168.0.1
2 36 ms 41 ms 29 ms cpe-65-184-160-1.ec.res.rr.com [65.184.160.1]
3 50 ms 51 ms 45 ms 174.111.108.33
4 33 ms 27 ms 30 ms cpe-024-025-055-234.ec.res.rr.com [24.25.55.234]
5 41 ms 39 ms 41 ms be35.drhmncev01r.southeast.rr.com [24.93.64.192]
6 40 ms 62 ms 37 ms bu-ether15.asbnva1611w-bcr00.tbone.rr.com [66.10
9.6.80]
7 48 ms 39 ms 39 ms 0.ae2.pr0.dca10.tbone.rr.com [66.109.6.169]
8 49 ms 45 ms 44 ms be3021.ccr41.iad02.atlas.cogentco.com [154.54.10
.209]
9 61 ms 49 ms 49 ms be2171.ccr41.dca01.atlas.cogentco.com [154.54.31
.105]
10 51 ms 61 ms 60 ms be2148.ccr41.jfk02.atlas.cogentco.com [154.54.31
.118]
11 61 ms 57 ms 59 ms be2094.ccr21.bos01.atlas.cogentco.com [154.54.30
.14]
12 61 ms 63 ms 65 ms te0-0-1-0.rcr11.b002133-1.bos01.atlas.cogentco.c
om [154.54.46.134]
13 112 ms 127 ms * 38.111.40.114
14 213 ms * * 198.49.243.253
15 156 ms 167 ms 159 ms 10.251.192.21
16 * * * Request timed out.
17 213 ms * * 198.49.243.16
18 208 ms * 62 ms 198.49.243.16
Trace complete.
C:\Users\Chris>tracert pwieast2.perfectworld.com
Tracing route to pwieast2.perfectworld.com [198.49.243.16]
over a maximum of 30 hops:
1 10 ms 2 ms 5 ms 192.168.0.1
2 207 ms 25 ms 29 ms cpe-65-184-160-1.ec.res.rr.com [65.184.160.1]
3 37 ms 39 ms 142 ms 174.111.108.33
4 28 ms 37 ms 28 ms cpe-024-025-055-234.ec.res.rr.com [24.25.55.234]
5 33 ms 41 ms 34 ms be35.drhmncev01r.southeast.rr.com [24.93.64.192]
6 42 ms 47 ms 39 ms bu-ether15.asbnva1611w-bcr00.tbone.rr.com [66.10
9.6.80]
7 53 ms 36 ms 36 ms 0.ae2.pr0.dca10.tbone.rr.com [66.109.6.169]
8 39 ms 52 ms 43 ms be3021.ccr41.iad02.atlas.cogentco.com [154.54.10
.209]
9 50 ms 49 ms 39 ms be2171.ccr41.dca01.atlas.cogentco.com [154.54.31
.105]
10 49 ms 49 ms 52 ms be2148.ccr41.jfk02.atlas.cogentco.com [154.54.31
.118]
11 81 ms 58 ms 60 ms be2094.ccr21.bos01.atlas.cogentco.com [154.54.30
.14]
12 72 ms 59 ms 59 ms te0-0-1-0.rcr11.b002133-1.bos01.atlas.cogentco.c
om [154.54.46.134]
13 120 ms 115 ms 149 ms 38.111.40.114
14 * * * Request timed out.
15 * * 213 ms 10.251.192.21
16 * * * Request timed out.
17 * * 229 ms 198.49.243.16
Trace complete.
C:\Users\Chris>tracert pwieast2.perfectworld.com
Tracing route to pwieast2.perfectworld.com [198.49.243.16]
over a maximum of 30 hops:
1 8 ms 15 ms 5 ms 192.168.0.1
2 51 ms 22 ms 27 ms cpe-65-184-160-1.ec.res.rr.com [65.184.160.1]
3 42 ms 37 ms 46 ms 174.111.108.33
4 29 ms 35 ms 35 ms cpe-024-025-055-234.ec.res.rr.com [24.25.55.234]
5 40 ms 50 ms 38 ms be35.drhmncev01r.southeast.rr.com [24.93.64.192]
6 41 ms 50 ms 48 ms bu-ether15.asbnva1611w-bcr00.tbone.rr.com [66.10
9.6.80]
7 46 ms 72 ms 50 ms 0.ae2.pr0.dca10.tbone.rr.com [66.109.6.169]
8 52 ms 44 ms 50 ms be3021.ccr41.iad02.atlas.cogentco.com [154.54.10
.209]
9 56 ms 72 ms 49 ms be2171.ccr41.dca01.atlas.cogentco.com [154.54.31
.105]
10 49 ms 47 ms 45 ms be2148.ccr41.jfk02.atlas.cogentco.com [154.54.31
.118]
11 60 ms 61 ms 54 ms be2094.ccr21.bos01.atlas.cogentco.com [154.54.30
.14]
12 59 ms 58 ms 55 ms te0-0-1-0.rcr11.b002133-1.bos01.atlas.cogentco.c
om [154.54.46.134]
13 55 ms 63 ms 55 ms 38.111.40.114
14 62 ms 58 ms 50 ms 198.49.243.253
15 75 ms 69 ms 62 ms 10.251.192.21
16 * * * Request timed out.
17 68 ms 45 ms 50 ms 198.49.243.16
Trace complete.
C:\Users\Chris>tracert pwieast2.perfectworld.com
Tracing route to pwieast2.perfectworld.com [198.49.243.16]
over a maximum of 30 hops:
1 6 ms 13 ms 8 ms 192.168.0.1
2 63 ms 42 ms 28 ms cpe-65-184-160-1.ec.res.rr.com [65.184.160.1]
3 99 ms 596 ms 45 ms 174.111.108.33
4 49 ms 34 ms 42 ms cpe-024-025-055-234.ec.res.rr.com [24.25.55.234]
5 41 ms 30 ms 37 ms be35.drhmncev01r.southeast.rr.com [24.93.64.192]
6 52 ms 49 ms 51 ms bu-ether15.asbnva1611w-bcr00.tbone.rr.com [66.10
9.6.80]
7 50 ms 43 ms 32 ms 0.ae2.pr0.dca10.tbone.rr.com [66.109.6.169]
8 47 ms 48 ms 52 ms be3021.ccr41.iad02.atlas.cogentco.com [154.54.10
.209]
9 48 ms 40 ms 44 ms be2171.ccr41.dca01.atlas.cogentco.com [154.54.31
.105]
10 46 ms 57 ms 58 ms be2148.ccr41.jfk02.atlas.cogentco.com [154.54.31
.118]
11 58 ms 63 ms 56 ms be2094.ccr21.bos01.atlas.cogentco.com [154.54.30
.14]
12 55 ms 60 ms 56 ms te0-0-1-0.rcr11.b002133-1.bos01.atlas.cogentco.c
om [154.54.46.134]
13 125 ms 121 ms 108 ms 38.111.40.114
14 * 212 ms 239 ms 198.49.243.253
15 56 ms 75 ms 63 ms 10.251.192.21
16 * * * Request timed out.
17 63 ms 70 ms 59 ms 198.49.243.16
Trace complete.
The current issue seems to be contained within PWE's routing system beginning with their connection to Cogent. Of course that is one freakishly large spike in my third hop on that last trace o.0By the light of the moon, our true forms are revealed.0 -
The sticky thread....
Network Issues, East Servers - 9/13
Which completely explains the current issue, and is not related to this thread at all.0
Categories
- All Categories
- 181.9K PWI
- 699 Official Announcements
- 2 Rules of Conduct
- 264 Cabbage Patch Notes
- 61.1K General Discussion
- 1.5K Quality Corner
- 11.1K Suggestion Box
- 77.4K Archosaur City
- 3.5K Cash Shop Huddle
- 14.3K Server Symposium
- 18.1K Dungeons & Tactics
- 2K The Crafting Nook
- 4.9K Guild Banter
- 6.6K The Trading Post
- 28K Class Discussion
- 1.9K Arigora Colosseum
- 78 TW & Cross Server Battles
- 337 Nation Wars
- 8.2K Off-Topic Discussion
- 3.7K The Fanatics Forum
- 207 Screenshots and Videos
- 22.8K Support Desk