Guild Wars 2

Thanks again sirsquishy, I have opened a ticket with my ISP.

I also downloaded PingPlotter, the problem really jumps out when looking at the graph and seeing how many packets are being lost.

A more recent diag run:

Tracing route to p4-23-c0-ncdc-pub.plaync.net [206.127.158.1]
over a maximum of 30 hops:
0 Dad-PC [192.168.1.3]
1 router.asus.com [192.168.1.1]
2 7.11.161.61
3 van58-6-240-157.dynamic.rogerstelecom.net [209.148.240.157]
4 gw01.hnsn.phub.net.cable.rogers.com [66.185.80.25]
5 pos-4-0.igw01.front.phub.net.cable.rogers.com [64.71.240.53]
6 ae53.edge1.Toronto2.Level3.net [4.31.208.129]
7 * * ae-23-23.bar2.Toronto1.Level3.net [4.69.200.237]
8 ae-7-1.ebr2.NewYork1.Level3.net [4.69.151.114]
9 ae-92-92.csw4.NewYork1.Level3.net [4.69.148.46]
10 * ae-91-91.ebr1.NewYork1.Level3.net [4.69.134.77]
11 ae-42-42.ebr2.London1.Level3.net [4.69.137.69]
12 ae-21-21.ebr2.Frankfurt1.Level3.net [4.69.148.186]
13 * * ae-72-72.csw2.Frankfurt1.Level3.net [4.69.140.22]
14 ae-2-70.edge6.Frankfurt1.Level3.net [4.69.154.74]
15 195.16.161.58
16 * 206-127-157-86.plaync.com [206.127.157.86]
17 p4-23-c0-ncdc-pub.plaync.net [206.127.158.1]

Computing statistics for 106 seconds…
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 Dad-PC [192.168.1.3]
0/ 25 = 0% |
1 10ms 1/ 25 = 4% 1/ 25 = 4% router.asus.com [192.168.1.1]
0/ 25 = 0% |
2 —- 25/ 25 =100% 25/ 25 =100% 7.11.161.61
0/ 25 = 0% |
3 31ms 0/ 25 = 0% 0/ 25 = 0% van58-6-240-157.dynamic.rogerstele
com.net [209.148.240.157]
2/ 25 = 8% |
4 —- 25/ 25 =100% 23/ 25 = 92% gw01.hnsn.phub.net.cable.rogers.co
m [66.185.80.25]
0/ 25 = 0% |
5 —- 25/ 25 =100% 23/ 25 = 92% pos-4-0.igw01.front.phub.net.cable
.rogers.com [64.71.240.53]
0/ 25 = 0% |
6 44ms 2/ 25 = 8% 0/ 25 = 0% ae53.edge1.Toronto2.Level3.net [4.
31.208.129]
0/ 25 = 0% |
7 27ms 2/ 25 = 8% 0/ 25 = 0% ae-23-23.bar2.Toronto1.Level3.net
[4.69.200.237]
0/ 25 = 0% |
8 40ms 2/ 25 = 8% 0/ 25 = 0% ae-7-1.ebr2.NewYork1.Level3.net [4
.69.151.114]
0/ 25 = 0% |
9 52ms 3/ 25 = 12% 1/ 25 = 4% ae-92-92.csw4.NewYork1.Level3.net
[4.69.148.46]
0/ 25 = 0% |
10 46ms 2/ 25 = 8% 0/ 25 = 0% ae-91-91.ebr1.NewYork1.Level3.net
[4.69.134.77]
3/ 25 = 12% |
11 121ms 6/ 25 = 24% 1/ 25 = 4% ae-42-42.ebr2.London1.Level3.net [
4.69.137.69]
0/ 25 = 0% |
12 127ms 6/ 25 = 24% 1/ 25 = 4% ae-21-21.ebr2.Frankfurt1.Level3.ne
t [4.69.148.186]
0/ 25 = 0% |
13 118ms 6/ 25 = 24% 1/ 25 = 4% ae-72-72.csw2.Frankfurt1.Level3.ne
t [4.69.140.22]
0/ 25 = 0% |
14 118ms 5/ 25 = 20% 0/ 25 = 0% ae-2-70.edge6.Frankfurt1.Level3.ne
t [4.69.154.74]
1/ 25 = 4% |
15 126ms 6/ 25 = 24% 0/ 25 = 0% 195.16.161.58
2/ 25 = 8% |
16 —- 25/ 25 =100% 17/ 25 = 68% 206-127-157-86.plaync.com [206.127
.157.86]
0/ 25 = 0% |
17 133ms 8/ 25 = 32% 0/ 25 = 0% p4-23-c0-ncdc-pub.plaync.net [206.
127.158.1]

Trace complete.

sirsquishy, thanks for taking the time to respond.

I have contacted my ISP and they indicated that ping tests to my modem performed very well with no loss.

For my own knowledge can you let me know what in the diag text or tracert info indicates that this is a transport issue with my ISP?

Tracert info as requested (btw tried a different router to eliminate that as a possibility)

Tracing route to 206-127-159-116.plaync.com [206.127.159.116]
over a maximum of 30 hops:

1 4 ms 4 ms 4 ms router.asus.com [192.168.1.1]
2 11 ms 12 ms 11 ms 7.11.161.61
3 18 ms 18 ms 15 ms van58-6-240-157.dynamic.rogerstelecom.net [209.1
48.240.157]
4 19 ms 18 ms 22 ms gw01.hnsn.phub.net.cable.rogers.com [66.185.80.2
5]
5 16 ms 28 ms 18 ms 69.63.251.142
6 15 ms 13 ms 14 ms ae53.edge1.Toronto2.Level3.net [4.31.208.129]
7 * * * Request timed out.
8 110 ms 110 ms 110 ms ae-7-1.ebr2.NewYork1.Level3.net [4.69.151.114]
9 109 ms 110 ms 110 ms ae-72-72.csw2.NewYork1.Level3.net [4.69.148.38]

10 108 ms 111 ms 109 ms ae-71-71.ebr1.NewYork1.Level3.net [4.69.134.69]

11 109 ms 108 ms 108 ms ae-44-44.ebr2.London1.Level3.net [4.69.137.77]
12 173 ms 126 ms 118 ms ae-23-23.ebr2.Frankfurt1.Level3.net [4.69.148.19
4]
13 111 ms 107 ms 109 ms ae-72-72.csw2.Frankfurt1.Level3.net [4.69.140.22
]
14 140 ms 108 ms 110 ms ae-2-70.edge6.Frankfurt1.Level3.net [4.69.154.74
]
15 1135 ms 114 ms 133 ms 195.16.161.58
16 116 ms 117 ms 116 ms 206-127-157-86.plaync.com [206.127.157.86]
17 119 ms 121 ms 121 ms 206-127-157-102.plaync.com [206.127.157.102]
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.

Tracing route to static-72-38-25-46.ipcom.comunitel.net [46.25.38.72]
over a maximum of 30 hops:

1 3 ms 4 ms 4 ms router.asus.com [192.168.1.1]
2 14 ms 12 ms 13 ms 7.11.161.61
3 1584 ms 42 ms 45 ms van58-6-240-157.dynamic.rogerstelecom.net [209.1
48.240.157]
4 17 ms 20 ms 18 ms gw01.hnsn.phub.net.cable.rogers.com [66.185.80.2
5]
5 34 ms 32 ms 32 ms 69.63.249.26
6 35 ms 36 ms 32 ms 195.2.17.65
7 129 ms 129 ms 132 ms ae0-xcr1.ash.cw.net [195.2.30.45]
8 144 ms 132 ms 129 ms ae10-xcr1.prp.cw.net [195.2.25.210]
9 114 ms 112 ms 117 ms ae1-xcr1.ptl.cw.net [195.2.10.90]
10 132 ms 131 ms 132 ms ae0-xcr1.mal.cw.net [195.2.30.182]
11 134 ms 134 ms 137 ms 195.10.46.2
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 *

Seeing the same codes as Nehtor, and have tried the same steps to resolve. Been experiencing the issue for at least two weeks. Playing from Ontario Canada.

Problem is most noticeable during peak times like 9:00pm – 11:00pm EDT, but have also just seen it at 9:30am.