Calling all Time Warner Cable folks in SoCal

[misterdapi]

Thank to those sending in trace routes. When ever you get lag, spikes, slowdown, alt tab over and run another trace route. I make notes in the command prompt on what happened, what time it was and if it effected other connections or just the game.

scustomer@roadrunner.com ATTN: Dave

Exact end IP does not matter. All TC wants to know is the rough goal. Its all the same data center . Square owns Edios.

No this is NOT because of TWC, Level 3 and their hops are the problem. The only way to correct is that TC has to open a ticket.

If you are honestly a TWC customer they want your Trace routes so they have something to submit to Level 3. End of story.

[Raist]

Thank to those sending in trace routes. When ever you get lag, spikes, slowdown, alt tab over and run another trace route. I make notes in the command prompt on what happened, what time it was and if it effected other connections or just the game.

scustomer@roadrunner.com ATTN: Dave

Exact end IP does not matter. All TC wants to know is the rough goal. Its all the same data center . Square owns Edios.

No this is NOT because of TWC, Level 3 and their hops are the problem. The only way to correct is that TC has to open a ticket.

If you are honestly a TWC customer they want your Trace routes so they have something to submit to Level 3. End of story.

Because routes to the same subnet but ultimately on different IP's can vary slightly, endpoint IP may become important though, depending on just what/how they investigate. For instance, some have seen issues crop up while still in the LA/Palo Alto areas--while still on the TWC segments. Here's a comparison of the routes taken from this same laptop to the three IP's noted in this thread specifically for Midgard when logged fully into the game (.28 from ARRStatus, .35 from the OP's client connection, and the .25 my client uses):
<initial hops on local segments removed for security>

Tracing route to 199.91.189.28 over a maximum of 30 hops	Tracing route to 199.91.189.35 over a maximum of 30 hops	Tracing route to 199.91.189.25 over a maximum of 30 hops
												
  4  xe-5-1-1.chrlncpop-rtr1.southeast.rr.com [24.93.64.96]	4  xe-5-1-1.chrlncpop-rtr1.southeast.rr.com [24.93.64.96]	4  24.93.64.134
  5  bu-ether24.atlngamq46w-bcr00.tbone.rr.com [107.14.19.18]	5  bu-ether14.atlngamq46w-bcr00.tbone.rr.com [66.109.6.82]	5  bu-ether24.atlngamq46w-bcr00.tbone.rr.com [107.14.19.18]
  6  107.14.19.99						6  ae-0-0.pr0.atl20.tbone.rr.com [66.109.6.171]			6  107.14.19.11
  7  twc-telus.pr0.chi10.tbone.rr.com [66.109.9.70]		7  twc-telus.pr0.chi10.tbone.rr.com [66.109.9.70]		7  twc-telus.pr0.chi10.tbone.rr.com [66.109.9.70]
  8  vlan51.ebr1.Atlanta2.Level3.net [4.69.150.62]		8  vlan51.ebr1.Atlanta2.Level3.net [4.69.150.62]		8  vlan51.ebr1.Atlanta2.Level3.net [4.69.150.62]
  9  ae-6-6.ebr1.Washington12.Level3.net [4.69.148.106]		9  ae-6-6.ebr1.Washington12.Level3.net [4.69.148.106]		9  ae-6-6.ebr1.Washington12.Level3.net [4.69.148.106]
 10  ae-1-100.ebr2.Washington12.Level3.net [4.69.143.214]	10  ae-1-100.ebr2.Washington12.Level3.net [4.69.143.214]	10  ae-1-100.ebr2.Washington12.Level3.net [4.69.143.214]
 11  4.69.201.61						11  4.69.201.65					                11  4.69.201.65
 12  ae-61-61.csw1.NewYork1.Level3.net [4.69.134.66]		12  ae-71-71.csw2.NewYork1.Level3.net [4.69.134.70]		12  ae-71-71.csw2.NewYork1.Level3.net [4.69.134.70]
 13  ae-62-62.ebr2.NewYork1.Level3.net [4.69.148.33]		13  ae-72-72.ebr2.NewYork1.Level3.net [4.69.148.37]		13  ae-72-72.ebr2.NewYork1.Level3.net [4.69.148.37]
 14  ae-5-5.car1.Montreal2.Level3.net [4.69.141.5]		14  ae-5-5.car1.Montreal2.Level3.net [4.69.141.5]	        14  ae-5-5.car1.Montreal2.Level3.net [4.69.141.5]
 15  ae-11-11.car2.Montreal2.Level3.net [4.69.141.1]		15  ae-11-11.car2.Montreal2.Level3.net [4.69.141.1]	        15  ae-11-11.car2.Montreal2.Level3.net [4.69.141.1]
 16  ORMUCO-COMM.car2.Montreal2.Level3.net [4.59.178.74]	16  ORMUCO-COMM.car2.Montreal2.Level3.net [4.59.178.74]	        16  ORMUCO-COMM.car2.Montreal2.Level3.net [4.59.178.74]
 17  192.34.76.10						17  192.34.76.10						17  192.34.76.10
 18  199.91.189.242						18  199.91.189.242						18  199.91.189.242
 19  199.91.189.28						19  199.91.189.35						19  199.91.189.25
												
Computing statistics for 475 seconds...						Computing statistics for 475 seconds...						Computing statistics for 475 seconds...

For whatever reason, the routes are not completely the same, even though they all are documented as going to Midgard. Granted, they are using the same hops for the majority of the route, but they deviate at a couple points. What if an issue exists at one of those hops that is only being used by that one IP, it happens to be the one you actually use but you send them the wrong IP to investigate? So, yes, this may become important depending on what is found and how it needs to be tested.

After several months of trying, you guys finally have someone willing to commit to a proper investigation of the routing issues... why not take an extra minute (or two or 5 if that's what it takes) to make sure you are providing accurate information about your specific connection?

[misterdapi]

Because it's the same route.

Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.

C:\Windows\System32>tracert 199.91.189.25

Tracing route to 199.91.189.25 over a maximum of 30 hops

  1     4 ms     7 ms    10 ms  R6300|DD-WRT [192.168.1.1]
  2     *        *       34 ms  cpe-75-85-32-1.socal.res.rr.com [75.85.32.1]
  3     *        *        *     Request timed out.
  4    23 ms    27 ms    28 ms  tge0-9-0-8.ontrcacp01r.socal.rr.com [72.129.6.16
0]
  5    18 ms    23 ms    28 ms  agg21.lsancarc01r.socal.rr.com [72.129.5.0]
  6    22 ms    25 ms    21 ms  107.14.19.32
  7    17 ms    18 ms    28 ms  107.14.19.138
  8    31 ms    39 ms    38 ms  66.109.9.122
  9   101 ms    92 ms    94 ms  vlan60.csw1.LosAngeles1.Level3.net [4.69.144.62]

 10    94 ms    95 ms   101 ms  ae-62-62.ebr2.LosAngeles1.Level3.net [4.69.137.1
7]
 11    90 ms    99 ms    87 ms  ae-3-3.ebr3.Dallas1.Level3.net [4.69.132.78]
 12   112 ms   118 ms    98 ms  ae-73-73.csw2.Dallas1.Level3.net [4.69.151.145]

 13    93 ms    93 ms   103 ms  ae-71-71.ebr1.Dallas1.Level3.net [4.69.151.138]

 14    92 ms    99 ms   103 ms  ae-14-14.ebr2.Chicago2.Level3.net [4.69.151.117]

 15    98 ms    98 ms   118 ms  ae-1-100.ebr1.Chicago2.Level3.net [4.69.132.113]

 16    89 ms    89 ms   101 ms  ae-6-6.ebr1.Chicago1.Level3.net [4.69.140.189]
 17    96 ms     *       93 ms  ae-10-10.car2.Montreal2.Level3.net [4.69.153.86]

 18    98 ms   108 ms    99 ms  ORMUCO-COMM.car2.Montreal2.Level3.net [4.59.178.
74]
 19    93 ms    99 ms    96 ms  192.34.76.10
 20  1652 ms  1599 ms  1638 ms  199.91.189.242
 21   282 ms   287 ms   282 ms  199.91.189.25

Trace complete.

C:\Windows\System32>

Line 20 is Square's problem.

[Raist]

Because it's the same route.

Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.

C:\Windows\System32>tracert 199.91.189.25

Tracing route to 199.91.189.25 over a maximum of 30 hops

  1     4 ms     7 ms    10 ms  R6300|DD-WRT [192.168.1.1]
  2     *        *       34 ms  cpe-75-85-32-1.socal.res.rr.com [75.85.32.1]
  3     *        *        *     Request timed out.
  4    23 ms    27 ms    28 ms  tge0-9-0-8.ontrcacp01r.socal.rr.com [72.129.6.160]
  5    18 ms    23 ms    28 ms  agg21.lsancarc01r.socal.rr.com [72.129.5.0]
  6    22 ms    25 ms    21 ms  107.14.19.32
  7    17 ms    18 ms    28 ms  107.14.19.138
  8    31 ms    39 ms    38 ms  66.109.9.122
  9   101 ms    92 ms    94 ms  vlan60.csw1.LosAngeles1.Level3.net [4.69.144.62]
 10    94 ms    95 ms   101 ms  ae-62-62.ebr2.LosAngeles1.Level3.net [4.69.137.17]
 11    90 ms    99 ms    87 ms  ae-3-3.ebr3.Dallas1.Level3.net [4.69.132.78]
 12   112 ms   118 ms    98 ms  ae-73-73.csw2.Dallas1.Level3.net [4.69.151.145]
 13    93 ms    93 ms   103 ms  ae-71-71.ebr1.Dallas1.Level3.net [4.69.151.138]
 14    92 ms    99 ms   103 ms  ae-14-14.ebr2.Chicago2.Level3.net [4.69.151.117]
 15    98 ms    98 ms   118 ms  ae-1-100.ebr1.Chicago2.Level3.net [4.69.132.113]
 16    89 ms    89 ms   101 ms  ae-6-6.ebr1.Chicago1.Level3.net [4.69.140.189]
 17    96 ms     *       93 ms  ae-10-10.car2.Montreal2.Level3.net [4.69.153.86]
 18    98 ms   108 ms    99 ms  ORMUCO-COMM.car2.Montreal2.Level3.net [4.59.178.74]
 19    93 ms    99 ms    96 ms  192.34.76.10
 20  1652 ms  1599 ms  1638 ms  199.91.189.242
 21   282 ms   287 ms   282 ms  199.91.189.25

Trace complete.

C:\Windows\System32>

Line 20 is Square's problem.

But you also seem to have some weirdness before SE's network (cleaned up the stray wrap arounds in the quote to save space, and colored some lines). Especially interesting is how you got 2 timeouts right off the bat at your doorstep.

Also.. are you sure it is the exact same route? Hard to verify that when you only post the trace to .25, without including ones for .28 and .35 as I did. Those paths clearly showed differences along the way. Out of curiosity, I compared them from a PC during some downtime at work today and got the same sort of mixed results there as well. You may in fact have identical routes, but I have seen different routes each time I test it on both residential and business class lines here from South Carolina. That alone shows that it is not necessarily the same route to different IP's in the same subnet for everyone all the time. Even if they do test out the same one day, it could be different the next day depending on how active they are in monitoring/compensating for congestion.

So, again to try to further illustrate, I'll show them from my laptop again--but this time I am including the tracert to raise another interesting point:

Tracing route to 199.91.189.25 over a maximum of 30 hops					Tracing route to 199.91.189.28 over a maximum of 30 hops					Tracing route to 199.91.189.35 over a maximum of 30 hops
																		
  4    36 ms    30 ms    26 ms  24.93.64.134							4    24 ms    25 ms    26 ms  xe-5-1-1.chrlncpop-rtr1.southeast.rr.com [24.93.64.96]		4    24 ms    25 ms    30 ms  xe-5-1-1.chrlncpop-rtr1.southeast.rr.com [24.93.64.96]
  5    30 ms    30 ms    31 ms  bu-ether24.atlngamq46w-bcr00.tbone.rr.com [107.14.19.18]	5    31 ms    30 ms    31 ms  bu-ether24.atlngamq46w-bcr00.tbone.rr.com [107.14.19.18]		5    28 ms    31 ms    29 ms  bu-ether14.atlngamq46w-bcr00.tbone.rr.com [66.109.6.82]
  6    27 ms    27 ms    56 ms  107.14.19.11							6    28 ms    27 ms    39 ms  107.14.19.99							6    37 ms    46 ms    27 ms  ae-0-0.pr0.atl20.tbone.rr.com [66.109.6.171]
  7    29 ms    30 ms    27 ms  twc-telus.pr0.chi10.tbone.rr.com [66.109.9.70]			7    30 ms    27 ms    30 ms  twc-telus.pr0.chi10.tbone.rr.com [66.109.9.70]			7    47 ms    50 ms    26 ms  twc-telus.pr0.chi10.tbone.rr.com [66.109.9.70]
  8    50 ms    48 ms    50 ms  vlan51.ebr1.Atlanta2.Level3.net [4.69.150.62]			8    49 ms    73 ms    52 ms  vlan51.ebr1.Atlanta2.Level3.net [4.69.150.62]			8    68 ms    49 ms    59 ms  vlan51.ebr1.Atlanta2.Level3.net [4.69.150.62]
  9    51 ms    49 ms    50 ms  ae-6-6.ebr1.Washington12.Level3.net [4.69.148.106]		9    49 ms    49 ms    50 ms  ae-6-6.ebr1.Washington12.Level3.net [4.69.148.106]		9    51 ms    50 ms    49 ms  ae-6-6.ebr1.Washington12.Level3.net [4.69.148.106]
 10    48 ms    49 ms    50 ms  ae-1-100.ebr2.Washington12.Level3.net [4.69.143.214]		10    49 ms    59 ms    49 ms  ae-1-100.ebr2.Washington12.Level3.net [4.69.143.214]		10    48 ms    50 ms    50 ms  ae-1-100.ebr2.Washington12.Level3.net [4.69.143.214]
 11    50 ms    58 ms    49 ms  4.69.201.65							11    51 ms    49 ms    69 ms  4.69.201.61							11    49 ms    50 ms    49 ms  4.69.201.65
 12    50 ms    50 ms    49 ms  ae-71-71.csw2.NewYork1.Level3.net [4.69.134.70]			12    48 ms    50 ms    51 ms  ae-61-61.csw1.NewYork1.Level3.net [4.69.134.66]			12    52 ms    49 ms    50 ms  ae-71-71.csw2.NewYork1.Level3.net [4.69.134.70]
 13    48 ms    49 ms    50 ms  ae-72-72.ebr2.NewYork1.Level3.net [4.69.148.37]			13    49 ms    50 ms    50 ms  ae-62-62.ebr2.NewYork1.Level3.net [4.69.148.33]			13    50 ms    50 ms    49 ms  ae-72-72.ebr2.NewYork1.Level3.net [4.69.148.37]
 14   189 ms    83 ms    71 ms  ae-5-5.car1.Montreal2.Level3.net [4.69.141.5]			14    49 ms    49 ms    50 ms  ae-5-5.car1.Montreal2.Level3.net [4.69.141.5]			14    51 ms    49 ms    49 ms  ae-5-5.car1.Montreal2.Level3.net [4.69.141.5]
 15    50 ms    49 ms    50 ms  ae-11-11.car2.Montreal2.Level3.net [4.69.141.1]			15    58 ms    50 ms    50 ms  ae-11-11.car2.Montreal2.Level3.net [4.69.141.1]			15    61 ms    74 ms    76 ms  ae-11-11.car2.Montreal2.Level3.net [4.69.141.1]
 16    61 ms    59 ms    50 ms  ORMUCO-COMM.car2.Montreal2.Level3.net [4.59.178.74]		16    51 ms    49 ms    49 ms  ORMUCO-COMM.car2.Montreal2.Level3.net [4.59.178.74]		16    51 ms    49 ms    49 ms  ORMUCO-COMM.car2.Montreal2.Level3.net [4.59.178.74]
 17    51 ms    61 ms    50 ms  192.34.76.10							17    53 ms    52 ms    54 ms  192.34.76.10							17    49 ms    59 ms    46 ms  192.34.76.10
 18    50 ms    49 ms    49 ms  199.91.189.242							18    60 ms    49 ms    50 ms  199.91.189.242							18    69 ms    50 ms    52 ms  199.91.189.242
 19    49 ms    50 ms    49 ms  199.91.189.25							19    50 ms    51 ms    60 ms  199.91.189.28							19    49 ms    58 ms    47 ms  199.91.189.35
																		
Trace complete.											Trace complete.											Trace complete.

Look closely at my ping times. For the most part, the variances are much tighter overall, and I am not picking up that 1k+ ping at the .242 IP. Which begs the question of why it can be so solid at the same Ormuco IP addresses for people elsewhere, and yet so crappy for you guys? Could it possibly be because of multiple little problems along the route compounding each other and creating a much bigger problem by the time it hits the end point? This could be something that needs to be flushed out, and if you are providing them a route that takes them around a different corner than the one you are actually taking, it may not be addressed as fully as if the proper routes were being presented and investigated.

Note also my routes are periodically changing as well--they've changed since I ran them this afternoon. Guess TWCSC is still tinkering with things... or perhaps they've gotten a little more pro-active with monitoring/correcting for congestion over here. Which may be a large part of the problem you guys are struggling with on the West Coast. SE may have finally corrected the snafu with their headers after O2 discovered it, so there may very well be something that needs to be addressed on the flow control from hop to hop now. If so, that makes it even more important for them to get a proper roadmap so they can better identify/compensate where the congestion issues are cropping up.

[misterdapi]

Raist I know we are on the same server, where are you located geo wise?

Here is all night to .25

I a 90k's half a dozen times tonight. Yet my wife sitting next to never caught one.

SOmetimes i would lag, sometimes she would. Repeat, cat 6 cable, wired, r6300 netgear w/ ddwrt, sb6141 modem.

Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.

C:\Windows\System32>tracert 199.91.189.25

Tracing route to 199.91.189.25 over a maximum of 30 hops

  1     4 ms     7 ms    10 ms  R6300|DD-WRT [192.168.1.1]
  2     *        *       34 ms  cpe-75-85-32-1.socal.res.rr.com [75.85.32.1]
  3     *        *        *     Request timed out.
  4    23 ms    27 ms    28 ms  tge0-9-0-8.ontrcacp01r.socal.rr.com [72.129.6.16
0]
  5    18 ms    23 ms    28 ms  agg21.lsancarc01r.socal.rr.com [72.129.5.0]
  6    22 ms    25 ms    21 ms  107.14.19.32
  7    17 ms    18 ms    28 ms  107.14.19.138
  8    31 ms    39 ms    38 ms  66.109.9.122
  9   101 ms    92 ms    94 ms  vlan60.csw1.LosAngeles1.Level3.net [4.69.144.62]

 10    94 ms    95 ms   101 ms  ae-62-62.ebr2.LosAngeles1.Level3.net [4.69.137.1
7]
 11    90 ms    99 ms    87 ms  ae-3-3.ebr3.Dallas1.Level3.net [4.69.132.78]
 12   112 ms   118 ms    98 ms  ae-73-73.csw2.Dallas1.Level3.net [4.69.151.145]

 13    93 ms    93 ms   103 ms  ae-71-71.ebr1.Dallas1.Level3.net [4.69.151.138]

 14    92 ms    99 ms   103 ms  ae-14-14.ebr2.Chicago2.Level3.net [4.69.151.117]

 15    98 ms    98 ms   118 ms  ae-1-100.ebr1.Chicago2.Level3.net [4.69.132.113]

 16    89 ms    89 ms   101 ms  ae-6-6.ebr1.Chicago1.Level3.net [4.69.140.189]
 17    96 ms     *       93 ms  ae-10-10.car2.Montreal2.Level3.net [4.69.153.86]

 18    98 ms   108 ms    99 ms  ORMUCO-COMM.car2.Montreal2.Level3.net [4.59.178.
74]
 19    93 ms    99 ms    96 ms  192.34.76.10
 20  1652 ms  1599 ms  1638 ms  199.91.189.242
 21   282 ms   287 ms   282 ms  199.91.189.25

Trace complete.

C:\Windows\System32>tracert 199.91.189.25

Tracing route to 199.91.189.25 over a maximum of 30 hops

  1    <1 ms    <1 ms     5 ms  R6300|DD-WRT [192.168.1.1]
  2    53 ms    47 ms    32 ms  cpe-75-85-32-1.socal.res.rr.com [75.85.32.1]
  3    14 ms    29 ms    28 ms  tge7-2.covncafi01h.socal.rr.com [76.166.2.193]
  4    20 ms    16 ms    24 ms  tge0-9-0-8.ontrcacp01r.socal.rr.com [72.129.6.16
0]
  5    20 ms    28 ms    28 ms  agg21.lsancarc01r.socal.rr.com [72.129.5.0]
  6    49 ms    34 ms    26 ms  107.14.19.32
  7    10 ms    19 ms    27 ms  107.14.19.138
  8    30 ms    36 ms    33 ms  66.109.9.122
  9    93 ms    94 ms   103 ms  vlan60.csw1.LosAngeles1.Level3.net [4.69.144.62]

 10    96 ms    99 ms    98 ms  ae-62-62.ebr2.LosAngeles1.Level3.net [4.69.137.1
7]
 11    95 ms    98 ms    88 ms  ae-3-3.ebr3.Dallas1.Level3.net [4.69.132.78]
 12    85 ms    92 ms    95 ms  ae-73-73.csw2.Dallas1.Level3.net [4.69.151.145]

 13    95 ms    92 ms   100 ms  ae-71-71.ebr1.Dallas1.Level3.net [4.69.151.138]

 14    90 ms    98 ms    98 ms  ae-14-14.ebr2.Chicago2.Level3.net [4.69.151.117]

 15    96 ms   139 ms    99 ms  ae-1-100.ebr1.chicago2.level3.net [4.69.132.113]

 16    92 ms    99 ms    99 ms  ae-6-6.ebr1.chicago1.level3.net [4.69.140.189]
 17   116 ms    94 ms   103 ms  ae-10-10.car2.montreal2.level3.net [4.69.153.86]

 18   106 ms    98 ms    99 ms  ORMUCO-COMM.car2.Montreal2.Level3.net [4.59.178.
74]
 19    94 ms   100 ms    97 ms  192.34.76.10
 20   130 ms    99 ms    93 ms  199.91.189.242
 21   111 ms   125 ms   111 ms  199.91.189.25

Trace complete.

C:\Windows\System32>tracert 199.91.189.25

Tracing route to 199.91.189.25 over a maximum of 30 hops

  1     2 ms    <1 ms     1 ms  R6300|DD-WRT [192.168.1.1]
  2    27 ms    24 ms    33 ms  cpe-75-85-32-1.socal.res.rr.com [75.85.32.1]
  3    18 ms    19 ms    18 ms  tge7-2.covncafi01h.socal.rr.com [76.166.2.193]
  4    23 ms    22 ms    25 ms  tge0-9-0-8.ontrcacp01r.socal.rr.com [72.129.6.16
0]
  5    24 ms    15 ms    18 ms  agg21.lsancarc01r.socal.rr.com [72.129.5.0]
  6    15 ms    22 ms    24 ms  107.14.19.32
  7    22 ms    24 ms    19 ms  107.14.19.138
  8    27 ms    93 ms    68 ms  66.109.9.122
  9    93 ms    91 ms    95 ms  vlan60.csw1.LosAngeles1.Level3.net [4.69.144.62]

 10    86 ms    93 ms    94 ms  ae-62-62.ebr2.LosAngeles1.Level3.net [4.69.137.1
7]
 11    93 ms    99 ms    96 ms  ae-3-3.ebr3.Dallas1.Level3.net [4.69.132.78]
 12    94 ms    89 ms    98 ms  ae-73-73.csw2.Dallas1.Level3.net [4.69.151.145]

 13    86 ms    93 ms    96 ms  ae-71-71.ebr1.Dallas1.Level3.net [4.69.151.138]

 14    91 ms    94 ms    93 ms  ae-14-14.ebr2.Chicago2.Level3.net [4.69.151.117]

 15    96 ms    92 ms    96 ms  ae-1-100.ebr1.chicago2.level3.net [4.69.132.113]

 16    99 ms    98 ms    99 ms  ae-6-6.ebr1.chicago1.level3.net [4.69.140.189]
 17   204 ms   108 ms   209 ms  ae-10-10.car2.montreal2.level3.net [4.69.153.86]

 18    92 ms    98 ms    98 ms  ORMUCO-COMM.car2.Montreal2.Level3.net [4.59.178.
74]
 19    92 ms    89 ms    98 ms  192.34.76.10
 20    97 ms   114 ms    97 ms  199.91.189.242
 21   110 ms   108 ms   108 ms  199.91.189.25

Trace complete.

C:\Windows\System32>tracert 199.91.189.25

Tracing route to 199.91.189.25 over a maximum of 30 hops

  1     5 ms     8 ms     4 ms  R6300|DD-WRT [192.168.1.1]
  2    48 ms    57 ms    90 ms  cpe-75-85-32-1.socal.res.rr.com [75.85.32.1]
  3    14 ms    19 ms    18 ms  tge7-2.covncafi01h.socal.rr.com [76.166.2.193]
  4    23 ms    28 ms    19 ms  tge0-9-0-8.ontrcacp01r.socal.rr.com [72.129.6.16
0]
  5    22 ms    29 ms    18 ms  agg21.lsancarc01r.socal.rr.com [72.129.5.0]
  6    18 ms    23 ms    28 ms  107.14.19.32
  7    45 ms    28 ms    17 ms  107.14.19.138
  8    20 ms    28 ms    27 ms  66.109.9.122
  9    98 ms    98 ms    98 ms  vlan60.csw1.LosAngeles1.Level3.net [4.69.144.62]

 10   100 ms    96 ms    99 ms  ae-62-62.ebr2.LosAngeles1.Level3.net [4.69.137.1
7]
 11    87 ms    91 ms   100 ms  ae-3-3.ebr3.Dallas1.Level3.net [4.69.132.78]
 12    95 ms    99 ms    98 ms  ae-73-73.csw2.Dallas1.Level3.net [4.69.151.145]

 13   100 ms    98 ms    99 ms  ae-71-71.ebr1.Dallas1.Level3.net [4.69.151.138]

 14    99 ms    99 ms    98 ms  ae-14-14.ebr2.Chicago2.Level3.net [4.69.151.117]

 15    95 ms   111 ms    89 ms  ae-1-100.ebr1.chicago2.level3.net [4.69.132.113]

 16    95 ms    96 ms    91 ms  ae-6-6.ebr1.chicago1.level3.net [4.69.140.189]
 17    97 ms    97 ms    98 ms  ae-10-10.car2.montreal2.level3.net [4.69.153.86]

 18    89 ms    98 ms    97 ms  ORMUCO-COMM.car2.Montreal2.Level3.net [4.59.178.
74]
 19    90 ms    99 ms   108 ms  192.34.76.10
 20    95 ms    98 ms   107 ms  199.91.189.242
 21   116 ms   118 ms   118 ms  199.91.189.25

Trace complete.

C:\Windows\System32>tracert 199.91.189.25

Tracing route to 199.91.189.25 over a maximum of 30 hops

  1    10 ms     6 ms     8 ms  R6300|DD-WRT [192.168.1.1]
  2    34 ms    28 ms    28 ms  cpe-75-85-32-1.socal.res.rr.com [75.85.32.1]
  3    14 ms    18 ms    19 ms  tge7-2.covncafi01h.socal.rr.com [76.166.2.193]
  4    24 ms    18 ms    19 ms  tge0-9-0-8.ontrcacp01r.socal.rr.com [72.129.6.16
0]
  5    24 ms    19 ms    28 ms  agg21.lsancarc01r.socal.rr.com [72.129.5.0]
  6    23 ms    17 ms    30 ms  107.14.19.32
  7    26 ms    23 ms    15 ms  107.14.19.138
  8    28 ms    28 ms    33 ms  66.109.9.122
  9    92 ms    98 ms    98 ms  vlan60.csw1.LosAngeles1.Level3.net [4.69.144.62]

 10    90 ms    98 ms    98 ms  ae-62-62.ebr2.LosAngeles1.Level3.net [4.69.137.1
7]
 11    93 ms    95 ms    92 ms  ae-3-3.ebr3.Dallas1.Level3.net [4.69.132.78]
 12    98 ms    96 ms    93 ms  ae-73-73.csw2.Dallas1.Level3.net [4.69.151.145]

 13    94 ms    91 ms    99 ms  ae-71-71.ebr1.Dallas1.Level3.net [4.69.151.138]

 14    94 ms    99 ms    97 ms  ae-14-14.ebr2.Chicago2.Level3.net [4.69.151.117]

 15    90 ms    99 ms    97 ms  ae-1-100.ebr1.chicago2.level3.net [4.69.132.113]

 16    91 ms    98 ms   108 ms  ae-6-6.ebr1.chicago1.level3.net [4.69.140.189]
 17   163 ms   213 ms   213 ms  ae-10-10.car2.montreal2.level3.net [4.69.153.86]

 18    95 ms    92 ms    98 ms  ORMUCO-COMM.car2.Montreal2.Level3.net [4.59.178.
74]
 19    92 ms   119 ms    98 ms  192.34.76.10
 20    91 ms    98 ms    99 ms  199.91.189.242
 21   106 ms   105 ms   113 ms  199.91.189.25

Trace complete.

C:\Windows\System32>tracert 199.91.189.25

Tracing route to 199.91.189.25 over a maximum of 30 hops

  1    10 ms     8 ms     8 ms  R6300|DD-WRT [192.168.1.1]
  2    45 ms    31 ms    29 ms  cpe-75-85-32-1.socal.res.rr.com [75.85.32.1]
  3    12 ms    19 ms    17 ms  tge7-2.covncafi01h.socal.rr.com [76.166.2.193]
  4    24 ms    18 ms    28 ms  tge0-9-0-8.ontrcacp01r.socal.rr.com [72.129.6.16
0]
  5    23 ms    28 ms    28 ms  agg21.lsancarc01r.socal.rr.com [72.129.5.0]
  6    14 ms    16 ms    18 ms  107.14.19.32
  7    22 ms    38 ms    27 ms  107.14.19.138
  8    28 ms    22 ms    21 ms  66.109.9.122
  9    92 ms    98 ms    98 ms  vlan60.csw1.LosAngeles1.Level3.net [4.69.144.62]

 10    93 ms    88 ms    98 ms  ae-62-62.ebr2.LosAngeles1.Level3.net [4.69.137.1
7]
 11    91 ms    93 ms    93 ms  ae-3-3.ebr3.Dallas1.Level3.net [4.69.132.78]
 12    98 ms    98 ms    98 ms  ae-73-73.csw2.Dallas1.Level3.net [4.69.151.145]

 13    92 ms    88 ms    98 ms  ae-71-71.ebr1.Dallas1.Level3.net [4.69.151.138]

 14    93 ms    97 ms    90 ms  ae-14-14.ebr2.Chicago2.Level3.net [4.69.151.117]

 15    95 ms    98 ms    97 ms  ae-1-100.ebr1.chicago2.level3.net [4.69.132.113]

 16    92 ms    98 ms    98 ms  ae-6-6.ebr1.chicago1.level3.net [4.69.140.189]
 17    94 ms    98 ms    96 ms  ae-10-10.car2.montreal2.level3.net [4.69.153.86]

 18    91 ms    98 ms    88 ms  ORMUCO-COMM.car2.Montreal2.Level3.net [4.59.178.
74]
 19    91 ms   116 ms    91 ms  192.34.76.10
 20    98 ms    98 ms    98 ms  199.91.189.242
 21   110 ms   118 ms   104 ms  199.91.189.25

Trace complete.

C:\Windows\System32>tracert 199.91.189.25

Tracing route to 199.91.189.25 over a maximum of 30 hops

  1     5 ms     9 ms     9 ms  R6300|DD-WRT [192.168.1.1]
  2    43 ms    38 ms    38 ms  cpe-75-85-32-1.socal.res.rr.com [75.85.32.1]
  3    14 ms    18 ms    18 ms  tge7-2.covncafi01h.socal.rr.com [76.166.2.193]
  4    24 ms    28 ms    22 ms  tge0-9-0-8.ontrcacp01r.socal.rr.com [72.129.6.16
0]
  5    24 ms    24 ms    23 ms  agg21.lsancarc01r.socal.rr.com [72.129.5.0]
  6    21 ms    26 ms    28 ms  107.14.19.32
  7    21 ms    16 ms    13 ms  107.14.19.138
  8    13 ms    21 ms    87 ms  66.109.9.122
  9    99 ms    98 ms    98 ms  vlan60.csw1.LosAngeles1.Level3.net [4.69.144.62]

 10    94 ms    98 ms    98 ms  ae-62-62.ebr2.LosAngeles1.Level3.net [4.69.137.1
7]
 11   102 ms    92 ms    95 ms  ae-3-3.ebr3.Dallas1.Level3.net [4.69.132.78]
 12    99 ms    98 ms    98 ms  ae-73-73.csw2.Dallas1.Level3.net [4.69.151.145]

 13    91 ms    96 ms    90 ms  ae-71-71.ebr1.Dallas1.Level3.net [4.69.151.138]

 14    94 ms    98 ms    92 ms  ae-14-14.ebr2.Chicago2.Level3.net [4.69.151.117]

 15    93 ms    98 ms    98 ms  ae-1-100.ebr1.chicago2.level3.net [4.69.132.113]

 16    91 ms    98 ms    98 ms  ae-6-6.ebr1.chicago1.level3.net [4.69.140.189]
 17    94 ms    98 ms    89 ms  ae-10-10.car2.montreal2.level3.net [4.69.153.86]

 18    92 ms    99 ms    88 ms  ORMUCO-COMM.car2.Montreal2.Level3.net [4.59.178.
74]
 19    93 ms    98 ms    96 ms  192.34.76.10
 20    99 ms    98 ms   108 ms  199.91.189.242
 21   112 ms   112 ms   115 ms  199.91.189.25

Trace complete.

C:\Windows\System32>

[Furlamseere]

It seems that there have not been any further posts about this concern being an ongoing issue. Because of this, we are considering it to be resolved. If this does continue to be a concern, please create another thread to further discuss resolutions or contact the Support Center at support.na.square-enix.com for assistance.

- Furlamseere