Dreamweaver SERVER

HellSlayer - Lost City · April 2015

FIX THIS EAST COAST SERVER !!!
this is the worst server in game atm ...plz do something
this my 3 dr server i play on and the worst ,,,,no wonder ppl is quietting every day ,,
PLZ DO SOMETHING for a change

NRGLG - Heavens Tear · April 2015

Edit: Ignore post, I jumped the gun. Fail me. My teachers would have given me an F. b:surrender

I just did a trace and PWE's east bandwidth throughput provider is currently failing with 100% packet loss. Maybe they (not PWE) are doing maintenance. It may be out of PWE's hands to do anything about it, aside from getting a new provider.

Dreamweaver

C:\Users\Administrator>tracert -w 1000 -d pwieast2.perfectworld.com

Tracing route to pwieast2.perfectworld.com [198.49.243.16]
over a maximum of 30 hops:

  1     1 ms    <1 ms    <1 ms  192.168.1.1
  2     8 ms     7 ms     9 ms  10.72.80.1
  3    10 ms     9 ms    13 ms  72.31.201.216
  4     9 ms     9 ms    11 ms  72.31.200.150
  5    11 ms    16 ms    10 ms  72.31.200.181
  6    17 ms    19 ms    20 ms  107.14.16.236
  7    18 ms    17 ms    17 ms  66.109.9.26
  8    18 ms    22 ms    18 ms  154.54.10.249
  9    18 ms    16 ms    17 ms  154.54.41.57
 10    56 ms    55 ms    59 ms  154.54.5.65
 11    68 ms    67 ms    67 ms  154.54.29.17
 12    81 ms    79 ms    79 ms  154.54.31.94
 13    87 ms    86 ms    86 ms  154.54.31.118
 14    94 ms    91 ms    90 ms  154.54.30.14
 15    92 ms    95 ms    92 ms  154.54.46.134
 16   100 ms   103 ms   107 ms  38.111.40.114
 17     *        *        *     Request timed out.
 18   103 ms   103 ms   103 ms  198.49.243.16

Trace complete.

Raging Tide

C:\Users\Administrator>tracert -w 1000 -d pwieast3.perfectworld.com

Tracing route to pwieast3.perfectworld.com [198.49.243.17]
over a maximum of 30 hops:

  1     1 ms     1 ms     1 ms  192.168.1.1
  2    10 ms     9 ms     9 ms  10.72.80.1
  3     9 ms     9 ms     9 ms  72.31.201.216
  4     9 ms    11 ms     9 ms  72.31.200.144
  5     9 ms    10 ms    11 ms  72.31.200.181
  6    17 ms    23 ms    15 ms  107.14.16.236
  7    18 ms    17 ms    17 ms  66.109.9.26
  8    17 ms    15 ms    16 ms  154.54.11.133
  9    18 ms    18 ms    17 ms  154.54.41.81
 10    57 ms    56 ms    55 ms  154.54.7.53
 11    68 ms    67 ms    67 ms  154.54.29.117
 12    80 ms    79 ms    80 ms  154.54.31.98
 13    85 ms    85 ms    85 ms  154.54.31.126
 14    91 ms    91 ms    91 ms  154.54.30.42
 15    92 ms    91 ms    91 ms  154.54.46.130
 16   112 ms   107 ms   107 ms  38.111.40.114
 17     *        *        *     Request timed out.
 18   102 ms   101 ms   103 ms  198.49.243.17

Trace complete.

Harshlands

C:\Users\Administrator>tracert -w 1000 -d pwieast1.perfectworld.com

Tracing route to pwieast1.perfectworld.com [198.49.243.15]
over a maximum of 30 hops:

  1     1 ms     1 ms     1 ms  192.168.1.1
  2     8 ms     9 ms     8 ms  10.72.80.1
  3    10 ms     9 ms     8 ms  72.31.201.218
  4    10 ms     9 ms     9 ms  72.31.201.0
  5    17 ms    19 ms    21 ms  107.14.16.236
  6    19 ms    33 ms    27 ms  66.109.9.26
  7    19 ms    18 ms    19 ms  154.54.10.249
  8    18 ms    16 ms    17 ms  154.54.41.57
  9    55 ms    55 ms    53 ms  154.54.5.65
 10    68 ms    69 ms    69 ms  154.54.29.17
 11    82 ms    81 ms    81 ms  154.54.31.106
 12    95 ms    85 ms    85 ms  154.54.80.161
 13    93 ms    95 ms    91 ms  154.54.30.14
 14    91 ms    91 ms    93 ms  154.54.46.134
 15   101 ms   106 ms   107 ms  38.111.40.114
 16     *        *        *     Request timed out.
 17   101 ms   101 ms   101 ms  198.49.243.15

Trace complete.

SylenThunder - Twilight Temple · April 2015

NRGLG - Heavens Tear wrote: »

I just did a trace and PWE's east bandwidth throughput provider is currently failing with 100% packet loss. Maybe they (not PWE) are doing maintenance. It may be out of PWE's hands to do anything about it, aside from getting a new provider.

...

Actually, that's most likely PWE's ISP and it won't ever return pings. IF there was an issue, you'd see a huge spike at the hop afterwards, and that isn't the case.

The hop where it hits triple digits, is a hub in Boston.

I just ran a trace, and I'm not seeing huge numbers like that here.

D:\PWI>tracert -h 18 pwieast2.perfectworld.com

Tracing route to pwieast2.perfectworld.com [198.49.243.16]
over a maximum of 18 hops:

  1     1 ms    <1 ms    <1 ms  homeportal [192.168.1.254]
  2    21 ms    34 ms    27 ms  76-250-208-2.lightspeed.livnmi.sbcglobal.net [76.250.208.2]
  3     *        *        *     Request timed out.
  4    24 ms    24 ms    22 ms  12.83.32.169
  5    31 ms    31 ms    29 ms  ggr4.cgcil.ip.att.net [12.122.133.33]
  6    29 ms    29 ms    29 ms  be2000.ccr21.ord03.atlas.cogentco.com [154.54.12.85]
  7    28 ms    27 ms    28 ms  be2003.ccr42.ord01.atlas.cogentco.com [154.54.29.21]
  8    38 ms    37 ms    36 ms  be2185.ccr22.cle04.atlas.cogentco.com [154.54.43.178]
  9    63 ms    70 ms    47 ms  be2189.ccr22.alb02.atlas.cogentco.com [154.54.43.185]
 10    49 ms    50 ms    49 ms  be2302.ccr22.bos01.atlas.cogentco.com [154.54.43.13]
 11    49 ms    50 ms    50 ms  te0-0-0-0.rcr11.b002133-1.bos01.atlas.cogentco.com [154.54.46.130]
 12    59 ms    53 ms    53 ms  38.111.40.114
 13     *        *        *     Request timed out.
 14    51 ms    50 ms    50 ms  198.49.243.16

Trace complete.

D:\PWI>pause
Press any key to continue . . .

Take note, that once it hits the Boston area the pings are higher. Also, an odd note. Every time I do a lookup on hop 9, it comes up as Wichita, which doesn't seem right at all for going from Michigan to New York.

EDIT: Also note, hop 3 did not return any pings either. I know that's a hub in Ohio, and I know there is not an issue, they just don't return ping requests. You can easily tell there isn't an issue because of the lack of a spike in latency at the hop immediately following it.

NRGLG - Heavens Tear · April 2015

Bandwidth throughput provider is ISP. I just like to separate it from ISP which people most commonly associate with their own connections.

As for pings, I've seen PWE's east ISP return an expired TTL ICMP packet. So they must have only shut out ICMP replies in the last few years (while I was away). I thinking they had a DDoS attack at some point, because I also sent a TCP packet and the ISP failed to return the handshake (ACK). There are definitely mitigation systems in place at the ISP. I've actually never seen this kind of behavior before (in real life). That was something I only really dealt with in a theoretical situation and networking never was my strong point, so it threw me off.

Edit: I confirm that there are no issues at present. I jumped the gun a bit because I saw a number of complaints about, what I assumed to be, the same thing. Didn't even bother to study the results clearly because I'm actually supposed to be working. (also known as making an excuse for my failure to analyse correctly)

Much later edit: Thanks to my mishap, I was inspired to add an auto issue detection into my software based on responding ICMP packets.

RepubIican - Raging Tide · April 2015

Ive been complaining to pwi about this issue for a week now, they told me I need to contact my internet service provider have them check my end. PWI doesn't want to admit the problem is on there end so sad.b:bye

NRGLG - Heavens Tear · April 2015

It's really not in this case or most cases. I jumped ahead of myself before I actually analysed the samples I had taken. I looked at the asterisks and jumped to a conclusion without checking it twice. Sylen is correct that there would be a somewhat substantial jump in response time from the next responding node.

If you wish to educate yourself on a simplified version of the inner-workings of the web, I do have a guide in the Technical Support Forum. Although I plan to revise a portion of it based on recommendations from a friend who said I put in too much fluff, forgot to explain IP and DNS, had confusing wording in some parts, did not add enough images, and may have unintentionally insulted my audience on multiple occasions. So bare that in mind at the moment. b:surrender

Dreamweaver SERVER

Comments

Categories