{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
Edited by boomerKELLY:
9/29/2018 8:38:56 PM
13
WOW Way Internet, Connectivity Issues, and YOU
I'm consolidating some of my posts into a new thread to provide some guidance on reporting this issue and what my personal findings are.
The following are Bungie's IP blocks, according to https://ipinfo.io/AS394073 ;
Netblock Description Num IPs
172.97.56.0/22 Bungie Inc. 1,024
205.209.16.0/21 Bungie Inc. 2,048
205.209.20.0/24 Bungie Inc. 256
205.209.21.0/24 Bungie Inc. 256
205.234.118.0/23 Bungie Inc. 512
Running some /tracert from my home network yields the following results;
[i]Microsoft Windows [Version 10.0.17134.285]
(c) 2018 Microsoft Corporation. All rights reserved.
C:\Users\BK>tracert 172.97.56.1
Tracing route to 172.97.56.1 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms GypsyDanger [192.168.1.1]
2 * * * Request timed out.
3 8 ms 8 ms 8 ms dynamic-76-73-172-225.knology.net [76.73.172.225]
4 10 ms 10 ms 10 ms 76-73-167-194.knology.net [76.73.167.194]
[b]5 652 ms 686 ms 729 ms xe-11-1-0.bar2.Cincinnati1.Level3.net [4.59.42.33][/b]
6 814 ms 742 ms 728 ms ae-1-6.bar2.LasVegas1.Level3.net [4.69.148.1]
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 ^C
C:\Users\BK>
C:\Users\BK>tracert 205.209.16.1
Tracing route to 205.209.16.1 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms GypsyDanger [192.168.1.1]
2 * * * Request timed out.
3 10 ms 8 ms 8 ms dynamic-76-73-172-225.knology.net [76.73.172.225]
4 11 ms 9 ms 7 ms 76-73-167-194.knology.net [76.73.167.194]
[b]5 601 ms 673 ms 646 ms xe-11-1-0.bar2.Cincinnati1.Level3.net [4.59.42.33][/b]
6 625 ms 596 ms 634 ms ae-1-6.bar2.LasVegas1.Level3.net [4.69.148.1]
7 * * * Request timed out.
8 * * * Request timed out.
9 ^C
C:\Users\BK>
C:\Users\BK>tracert 205.209.20.1
Tracing route to 205.209.20.1 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms GypsyDanger [192.168.1.1]
2 * * * Request timed out.
3 10 ms 8 ms 10 ms dynamic-76-73-172-225.knology.net [76.73.172.225]
4 9 ms 8 ms 9 ms 76-73-167-194.knology.net [76.73.167.194]
5 12 ms 8 ms 8 ms 76-73-166-126.knology.net [76.73.166.126]
6 12 ms 11 ms 10 ms 76-73-166-125.knology.net [76.73.166.125]
7 20 ms 19 ms 19 ms user-24-214-131-160.knology.net [24.214.131.160]
8 19 ms 19 ms 17 ms dynamic-75-76-35-8.knology.net [75.76.35.8]
9 19 ms 22 ms 21 ms chi-b21-link.telia.net [62.115.63.86]
10 19 ms 18 ms 18 ms xe-8-1-1.er2.ord7.us.zip.zayo.com [64.125.12.177]
11 18 ms 19 ms 20 ms ae17.cr2.ord2.us.zip.zayo.com [64.125.31.82]
12 79 ms 77 ms 82 ms ae27.cs2.ord2.us.eth.zayo.com [64.125.30.244]
13 78 ms 78 ms 79 ms ae5.cs2.den5.us.eth.zayo.com [64.125.29.216]
14 80 ms 80 ms 80 ms ae11.cs2.las2.us.eth.zayo.com [64.125.27.35]
15 79 ms 80 ms 78 ms ae0.cs1.las2.us.eth.zayo.com [64.125.28.108]
16 79 ms 78 ms 79 ms ae7.mpr2.las1.us.zip.zayo.com [64.125.28.111]
17 * * * Request timed out.
18 * ^C
C:\Users\BK>
C:\Users\BK>tracert 205.209.21.1
Tracing route to 205.209.21.1 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms GypsyDanger [192.168.1.1]
2 * * * Request timed out.
3 8 ms 9 ms 9 ms dynamic-76-73-172-225.knology.net [76.73.172.225]
4 11 ms 9 ms 8 ms 76-73-167-194.knology.net [76.73.167.194]
5 * 9 ms 8 ms 76-73-166-126.knology.net [76.73.166.126]
6 10 ms 10 ms 12 ms 76-73-166-125.knology.net [76.73.166.125]
7 20 ms 19 ms 19 ms user-24-214-131-160.knology.net [24.214.131.160]
8 19 ms 17 ms 19 ms dynamic-75-76-35-8.knology.net [75.76.35.8]
9 21 ms 22 ms 19 ms chi-b21-link.telia.net [62.115.63.86]
10 18 ms 19 ms 19 ms xe-8-1-1.er2.ord7.us.zip.zayo.com [64.125.12.177]
11 23 ms 18 ms 19 ms ae17.cr2.ord2.us.zip.zayo.com [64.125.31.82]
12 * 102 ms 79 ms ae27.cs2.ord2.us.eth.zayo.com [64.125.30.244]
13 83 ms 81 ms 77 ms ae5.cs2.den5.us.eth.zayo.com [64.125.29.216]
14 80 ms 80 ms 80 ms ae11.cs2.las2.us.eth.zayo.com [64.125.27.35]
15 79 ms 80 ms 79 ms ae0.cs1.las2.us.eth.zayo.com [64.125.28.108]
16 80 ms 80 ms 78 ms ae7.mpr2.las1.us.zip.zayo.com [64.125.28.111]
17 * * ^C
C:\Users\BK>
C:\Users\BK>tracert 205.234.118.1
Tracing route to 205.234.118.1 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms GypsyDanger [192.168.1.1]
2 * * * Request timed out.
3 8 ms 9 ms 7 ms dynamic-76-73-172-225.knology.net [76.73.172.225]
4 8 ms 8 ms 9 ms 76-73-167-194.knology.net [76.73.167.194]
[b]5 670 ms 683 ms 642 ms xe-11-1-0.bar2.Cincinnati1.Level3.net [4.59.42.33][/b]
6 675 ms 630 ms 658 ms ae-1-6.bar2.LasVegas1.Level3.net [4.69.148.1]
7 * * * Request timed out.
8 * * * Request timed out.
9 ^C
C:\Users\BK>
[/i]
I cut all of the the trace's short (ctrl-c) when their results became clear (I'm impatient) but the culprit, at least for me, is clear.
Two of the trace's looked fine. The other three spiked at the hop called;
[b][u]xe-11-1-0.bar2.Cincinnati1.Level3.net[/u][/b]
To verify this, I also ran some trace's on two application hosts my company utilizes, one in Philadelphia and the other in Phoenix, both of which I noticed performance issues when connecting to from home the last couple days...
[i]Microsoft Windows [Version 10.0.17134.285]
(c) 2018 Microsoft Corporation. All rights reserved.
C:\Users\BK>tracert 206.27.163.28
Tracing route to 206.27.163.28 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms GypsyDanger [192.168.1.1]
2 * * * Request timed out.
3 9 ms 7 ms 7 ms dynamic-76-73-172-225.knology.net [76.73.172.225]
4 9 ms 8 ms 10 ms 76-73-167-194.knology.net [76.73.167.194]
[b]5 540 ms 517 ms 564 ms xe-11-1-0.bar2.Cincinnati1.Level3.net [4.59.42.33][/b]
6 * * * Request timed out.
7 570 ms 534 ms 532 ms 4.68.74.146
8 630 ms 611 ms 594 ms chp-brdr-03.inet.qwest.net [67.14.8.194]
9 645 ms 602 ms 681 ms 208.174.226.229
10 677 ms 671 ms 659 ms 206.28.101.170
11 641 ms 596 ms 592 ms cr2-te-0-5-0-2.dan.savvis.net [204.70.194.74]
12 655 ms 683 ms 629 ms cr1-tengig0-7-0-0.dallas.savvis.net [204.70.196.213]
13 684 ms 655 ms 513 ms hr2-xe-2-0-0.ph1.savvis.net [206.27.160.46]
14 555 ms 600 ms 613 ms 63.136.4.78
15 68 ms 67 ms 68 ms 206.27.160.118
16 623 ms 633 ms 579 ms 206.27.163.28
Trace complete.
C:\Users\BK>tracert 8.41.193.212
Tracing route to 8.41.193.212 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms GypsyDanger [192.168.1.1]
2 * * * Request timed out.
3 8 ms 11 ms 10 ms dynamic-76-73-172-225.knology.net [76.73.172.225]
4 10 ms 11 ms 11 ms 76-73-167-194.knology.net [76.73.167.194]
[b]5 656 ms 679 ms 651 ms xe-11-1-0.bar2.Cincinnati1.Level3.net [4.59.42.33][/b]
6 674 ms 670 ms 742 ms 4.69.217.198
7 670 ms 659 ms 651 ms SUNESYS-INC.bar1.Philadelphia1.Level3.net [4.34.194.154]
8 43 ms 42 ms 42 ms 8.41.192.82
9 710 ms 694 ms 682 ms 8.41.193.212
Trace complete.
C:\Users\BK>[/i]
Looks like I have Cincinnati to blame for my issues with Destiny and otherwise.
I would encourage anyone interested to perform the same traces and provide this information to WOW technical support.
service
General questions, billing, technical support, or to transfer existing service:
1-866-496-9669
-
4 RepliesEdited by Tribunal: 10/2/2018 12:05:59 AMI don't want to get everyone's hopes up prematurely, but it 8:00 PM EST and the choke point hops aren't showing the lag spikes. Now, it's Monday, which is a low traffic night, but here are my numbers. [Cinci route] Tonight 5 19 ms 32 ms 19 ms xe-11-1-0.bar2.cincinnati1.level3.net [4.59.42.33] Saturday night 5 663 ms 657 ms 676 ms xe-11-1-0.bar2.cincinnati1.level3.net [4.59.42.33] [Chicago route] Tonight 9 24 ms 20 ms 20 ms chi-b21-link.telia.net [62.115.63.86] Saturday night 9 141 ms 133 ms 138 ms chi-b21-link.telia.net [62.115.63.86] The 9-midnight time frame will be the real test, but this is encouraging. I haven't logged in yet either. I've just been running trace routes every hour, starting around noon EST. So far though, with an exception at 3:00 PM which jumped to 160ms, latency has stayed low and consistent all day.
