100% packet loss at plaync.com

Does anyone still work there?


Windows Trace route:

Tracing route to 216-107-245-95.plaync.com [216.107.245.95]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms 192.168.1.1
2 9 ms 7 ms 9 ms cpe-98-28-64-1.columbus.res.rr.com [98.28.64.1]
3 14 ms 12 ms 12 ms network-024-029-163-073.woh.rr.com [24.29.163.73]
4 13 ms 23 ms 14 ms srp5-0.limaoh1-rtr2.woh.rr.com [24.29.163.141]
5 21 ms 21 ms 20 ms son3-0-2.mtgmoh1-rtr0.columbus.rr.com [65.25.128.157]
6 32 ms 25 ms 26 ms ae-4-0.cr0.chi30.tbone.rr.com [66.109.6.68]
7 25 ms 23 ms 27 ms ae-1-0.pr0.chi10.tbone.rr.com [66.109.6.155]
8 27 ms 27 ms 24 ms ge9-4.br03.chc01.pccwbtn.net [209.8.108.37]
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

C:\WINDOWS\system32>





In game diagnostics:

Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 comp1.columbus.rr.com [192.168.1.101]
0/ 3 = 0% |
1 0ms 0/ 3 = 0% 0/ 3 = 0% 192.168.1.1
0/ 3 = 0% |
2 10ms 0/ 3 = 0% 0/ 3 = 0% cpe-98-28-64-1.columbus.res.rr.com [98.28.64.1]
0/ 3 = 0% |
3 12ms 0/ 3 = 0% 0/ 3 = 0% network-024-029-163-073.woh.rr.com [24.29.163.73]
0/ 3 = 0% |
4 13ms 0/ 3 = 0% 0/ 3 = 0% srp5-0.limaoh1-rtr1.woh.rr.com [24.29.163.140]
0/ 3 = 0% |
5 21ms 0/ 3 = 0% 0/ 3 = 0% network-065-025-128-189.columbus.rr.com [65.25.128.189]
0/ 3 = 0% |
6 27ms 0/ 3 = 0% 0/ 3 = 0% ae-3-0.cr0.dca20.tbone.rr.com [66.109.6.70]
0/ 3 = 0% |
7 40ms 0/ 3 = 0% 0/ 3 = 0% ae-1-0.pr0.dca10.tbone.rr.com [66.109.6.165]
0/ 3 = 0% |
8 45ms 0/ 3 = 0% 0/ 3 = 0% ge6-3.br02.ash01.pccwbtn.net [63.216.0.117]
0/ 3 = 0% |
9 --- 3/ 3 =100% 3/ 3 =100% ncsoft.ge5-11.br01.lax05.pccwbtn.net [63.218.73.2]
0/ 3 = 0% |
10 --- 3/ 3 =100% 3/ 3 =100% 216-107-255-70.plaync.com [216.107.255.70]
0/ 3 = 0% |
11 90ms 0/ 3 = 0% 0/ 3 = 0% 216-107-246-36.plaync.com
[216.107.246.36]






Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 comp1.columbus.rr.com [192.168.1.101]
0/ 3 = 0% |
1 0ms 0/ 3 = 0% 0/ 3 = 0% 192.168.1.1
0/ 3 = 0% |
2 8ms 0/ 3 = 0% 0/ 3 = 0% cpe-98-28-64-1.columbus.res.rr.com [98.28.64.1]
0/ 3 = 0% |
3 11ms 0/ 3 = 0% 0/ 3 = 0% network-024-029-163-073.woh.rr.com [24.29.163.73]
0/ 3 = 0% |
4 13ms 0/ 3 = 0% 0/ 3 = 0% srp5-0.limaoh1-rtr2.woh.rr.com [24.29.163.141]
0/ 3 = 0% |
5 27ms 0/ 3 = 0% 0/ 3 = 0% son3-0-2.mtgmoh1-rtr0.columbus.rr.com [65.25.128.157]
0/ 3 = 0% |
6 28ms 0/ 3 = 0% 0/ 3 = 0% ae-4-0.cr0.chi30.tbone.rr.com [66.109.6.68]
0/ 3 = 0% |
7 50ms 0/ 3 = 0% 0/ 3 = 0% ae-0-0.cr0.chi10.tbone.rr.com [66.109.6.20]
0/ 3 = 0% |
8 103ms 0/ 3 = 0% 0/ 3 = 0% ae-3-0.cr0.sjc10.tbone.rr.com [66.109.6.14]
0/ 3 = 0% |
9 96ms 0/ 3 = 0% 0/ 3 = 0% ae-0-0.pr0.sjc10.tbone.rr.com [66.109.6.141]
0/ 3 = 0% |
10 --- 3/ 3 =100% 3/ 3 =100% 66-109-10-210.tbone.rr.com [66.109.10.210]
0/ 3 = 0% |
11 221ms 0/ 3 = 0% 0/ 3 = 0% po4-0-0.cr1.nrt1.asianetcom.net [202.147.0.33]
0/ 3 = 0% |
12 244ms 0/ 3 = 0% 0/ 3 = 0% po6-1.gw2.sel2.asianetcom.net [202.147.8.109]
0/ 3 = 0% |
13 235ms 0/ 3 = 0% 0/ 3 = 0% KIDC.gw2.SEL2.asianetcom.net [203.192.165.178]
0/ 3 = 0% |
14 --- 3/ 3 =100% 3/ 3 =100% 211.233.88.151
0/ 3 = 0% |
15 --- 3/ 3 =100% 3/ 3 =100% 211.233.95.202
0/ 3 = 0% |
16 --- 3/ 3 =100% 3/ 3 =100% 211.174.55.250
0/ 3 = 0% |
17 --- 3/ 3 =100% 3/ 3 =100% 192.168.253.6
0/ 3 = 0% |
18 240ms 0/ 3 = 0% 0/ 3 = 0% 222.231.14.228






Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 comp1.columbus.rr.com [192.168.1.101]
0/ 3 = 0% |
1 0ms 0/ 3 = 0% 0/ 3 = 0% 192.168.1.1
0/ 3 = 0% |
2 10ms 0/ 3 = 0% 0/ 3 = 0% cpe-98-28-64-1.columbus.res.rr.com [98.28.64.1]
0/ 3 = 0% |
3 11ms 0/ 3 = 0% 0/ 3 = 0% network-024-029-163-073.woh.rr.com [24.29.163.73]
0/ 3 = 0% |
4 15ms 0/ 3 = 0% 0/ 3 = 0% srp5-0.limaoh1-rtr2.woh.rr.com [24.29.163.141]
0/ 3 = 0% |
5 30ms 0/ 3 = 0% 0/ 3 = 0% son3-0-2.mtgmoh1-rtr0.columbus.rr.com [65.25.128.157]
0/ 3 = 0% |
6 30ms 0/ 3 = 0% 0/ 3 = 0% ae-4-0.cr0.chi30.tbone.rr.com [66.109.6.68]
0/ 3 = 0% |
7 67ms 0/ 3 = 0% 0/ 3 = 0% ae-1-0.pr0.chi10.tbone.rr.com [66.109.6.155]
0/ 3 = 0% |
8 34ms 0/ 3 = 0% 0/ 3 = 0% ge9-4.br03.chc01.pccwbtn.net [209.8.108.37]
0/ 3 = 0% |
9 --- 3/ 3 =100% 3/ 3 =100% ncsoft.ge4-12.br02.frf02.pccwbtn.net [63.218.15.42]
0/ 3 = 0% |
10 --- 3/ 3 =100% 3/ 3 =100% 206-127-156-82.plaync.com [206.127.156.82]
0/ 3 = 0% |
11 134ms 0/ 3 = 0% 0/ 3 = 0% 206-127-145-228.plaync.com [206.127.145.228]

I'm not having any issue with the plaync site. I'm accessing the US site. Which one are you going to?

The 100% packet loss at the entry to PLay NC's domain is due to their firewall. It's normal and not a sign of any kind of lag or error.

This is also entirely possible. And more probable than anything else.

Understandably with echo turned off hop 9 will not return a response.

Below are three screen shots of a ten minute ping session.

The first image shows that hop 8 is in good shape and working as intended.

The second will show a spike and packet loss of 10%.

The third shows a spike and a packet loss of 25%.

The lower graph in each shot depicts a ten minute history with the red lines as high latency and loss.

This is just a ten minute session. As I play for a few hours the latency will sometimes jump into the 1000's of milliseconds for short periods of time.
This occurs morning, noon or night. Not just at peak hours.


1.



2.



3.