HUGE CONNECTION PROBLEM

[Raist]

yup that would probably be it near stl charter hub and charter is only cable provider here,
tracerouting the ip my client uses only 5 ms difference in response times, no * events

Might want to submit a formal ticket to SE then...and give them that tracert data. Last fall Time Warner caught what they thought was potentially a VLAN issue on the other side of Ormuco that was a potential problem (inside the SE/Ormuco "sphere of influence" it was pegging over 200ms periodically when the rest of the route was always under 100 during their testing). They forwarded their findings to Ormuco's admin email and I submitted the data to SE through the support portal--and it cleared up like 3 days later (and we haven't seen the issue since either).

It's worth a shot since you have the actual road map (tracert) for them to look at. Probably one of the biggest problems we've run up against with these issues...lots of people complaining but not enough people submitting useful data to the people that may be able to actually do something about it.

Edit:
grrr....popped in during my lunch break to reload the market and send retainers back out and was getting a bit of stutter not usually there. Took two runs to catch it, but looks like something may be up with TATA right now.

Mom was streaming to the Roku downstairs (she finally learned how to look things up on 1CH and can't get her off the d@mn thing now) which can cause some wonkiness, but it's never been too impactful. Still dealing with a bit of weirdness getting around to Columbia---they've been wrangling with gateway problems in SC for a while now, so it's kind of normal these days. So long as I stay in a decent range things are OK. What first caught my eye was the stray * spike coming out of Ashburn towards Montreal (think that was Albany last time I checked) and then a 107 spike from 54 right after the hand-off into Ormuco-Montreal that concerns me. Not game-breaking for me yet since I'm so close... but it may be something for people further out to keep an eye on if it continues acting up. If it gets much worse TWC often cuts me over to Cogent or Level3 for a bit---usually have to hit up near 200ms for them to cut me over though. Will have to see what happens by the time I get home tonight.

Tracing route to 199.91.189.30 over a maximum of 30 hops

  1     2 ms     1 ms     1 ms  LPTSRV [10.10.100.1]
  2    41 ms    43 ms    49 ms  cpe-75-176-160-1.sc.res.rr.com [75.176.160.1]
  3    35 ms    31 ms    36 ms  cpe-024-031-198-005.sc.res.rr.com [24.31.198.5]
  4    15 ms    12 ms    13 ms  clmasoutheastmyr-rtr2.sc.rr.com [24.31.196.210]
  5    27 ms    26 ms    26 ms  be33.drhmncev01r.southeast.rr.com [24.93.64.180]
  6    34 ms    31 ms    33 ms  bu-ether35.asbnva1611w-bcr00.tbone.rr.com [107.14.19.42]
  7    30 ms    29 ms    29 ms  0.ae1.pr1.dca10.tbone.rr.com [107.14.17.202]
  8    30 ms    29 ms    32 ms  ix-17-0.tcore2.AEQ-Ashburn.as6453.net [216.6.87.149]
  9    52 ms    54 ms    53 ms  if-2-2.tcore1.AEQ-Ashburn.as6453.net [216.6.87.2]
 10    52 ms    52 ms    54 ms  64.86.85.1
 11    50 ms    54 ms    53 ms  if-10-2.tcore1.TTT-Toronto.as6453.net [64.86.32.33]
 12    51 ms    53 ms    53 ms  if-9-9.tcore1.TNK-Toronto.as6453.net [64.86.33.25]
 13    51 ms    53 ms    53 ms  if-7-2.tcore1.W6C-Montreal.as6453.net [66.198.96.61]
 14    51 ms    53 ms    54 ms  66.198.96.50
 15    53 ms    53 ms    53 ms  192.34.76.2
 16    52 ms    52 ms    54 ms  199.91.189.234
 17    51 ms    55 ms    51 ms  199.91.189.30

Trace complete.

C:\Windows\System32>tracert 199.91.189.30

Tracing route to 199.91.189.30 over a maximum of 30 hops

  1     2 ms     1 ms     1 ms  LPTSRV [10.10.100.1]
  2    34 ms    27 ms    26 ms  cpe-75-176-160-1.sc.res.rr.com [75.176.160.1]
  3    28 ms    64 ms    38 ms  cpe-024-031-198-005.sc.res.rr.com [24.31.198.5]
  4    29 ms    14 ms    15 ms  clmasoutheastmyr-rtr2.sc.rr.com [24.31.196.210]
  5    28 ms    25 ms    26 ms  be33.drhmncev01r.southeast.rr.com [24.93.64.180]
  6    31 ms    33 ms    35 ms  bu-ether35.asbnva1611w-bcr00.tbone.rr.com [107.14.19.42]
  7    28 ms    30 ms    29 ms  0.ae1.pr1.dca10.tbone.rr.com [107.14.17.202]
  8    53 ms    56 ms    46 ms  ix-17-0.tcore2.AEQ-Ashburn.as6453.net [216.6.87.149]
  9    52 ms    54 ms    53 ms  if-2-2.tcore1.AEQ-Ashburn.as6453.net [216.6.87.2]
 10     *       54 ms    55 ms  64.86.85.1
 11    53 ms    55 ms    52 ms  if-10-2.tcore1.TTT-Toronto.as6453.net [64.86.32.33]
 12    51 ms    52 ms    54 ms  if-9-9.tcore1.TNK-Toronto.as6453.net [64.86.33.25]
 13    51 ms    52 ms    53 ms  if-7-2.tcore1.W6C-Montreal.as6453.net [66.198.96.61]
 14    53 ms    53 ms    54 ms  66.198.96.50
 15    54 ms   107 ms    55 ms  192.34.76.2
 16    55 ms    54 ms    55 ms  199.91.189.234
 17    54 ms    53 ms    52 ms  199.91.189.30

Trace complete.

[Lexie]

C:\Users\Amy>tracert 184.107.107.176

Tracing route to 184.107.107.176 over a maximum of 30 hops

1 4 ms 7 ms 7 ms Amys [0.0.0.0]
2 5 ms 7 ms 7 ms dtr01cpgrmo-tge-0-7-0-0.cpgr.mo.charter.com [96.
34.56.4]
3 10 ms 12 ms 9 ms dtr01frtnmo-bue-4.frtn.mo.charter.com [96.34.56.
32]
4 16 ms 10 ms 11 ms dtr01hlbomo-bue-2.hlbo.mo.charter.com [96.34.50.
230]
5 11 ms 12 ms 13 ms crr02olvemo-bue-40.olve.mo.charter.com [96.34.76
.183]
6 19 ms 14 ms 15 ms bbr01olvemo-bue-60.olve.mo.charter.com [96.34.2.
166]
7 * * * Request timed out.
8 63 ms 138 ms 57 ms ae-10-10.car2.Montreal2.Level3.net [4.69.153.86]

9 57 ms 81 ms 100 ms ae-10-10.car2.Montreal2.Level3.net [4.69.153.86]

10 57 ms 59 ms 57 ms 4.59.178.62
11 58 ms 58 ms 58 ms te8-3.dr10.mtl.iweb.com [67.205.127.238]
12 60 ms 57 ms 57 ms 72.55.128.44
13 60 ms 60 ms 61 ms 184.107.107.176

Trace complete.

this is what I am getting found there was 2 time outs in the pathing but looking at the ip address your tracing a different one so trying that one now

[Lexie]

this is the new one

C:\Users\Amy>tracert 199.91.189.30

Tracing route to 199.91.189.30 over a maximum of 30 hops

  1    10 ms     6 ms     8 ms  Amys [0.0.0.0]
  2    13 ms     6 ms    11 ms  dtr01cpgrmo-tge-0-7-0-0.cpgr.mo.charter.com [96.
34.56.4]
  3    10 ms    10 ms     9 ms  dtr01frtnmo-bue-4.frtn.mo.charter.com [96.34.56.
32]
  4    11 ms    11 ms    12 ms  dtr01hlbomo-bue-2.hlbo.mo.charter.com [96.34.50.
230]
  5    10 ms    12 ms    12 ms  crr02olvemo-bue-40.olve.mo.charter.com [96.34.76
.183]
  6    11 ms    13 ms    21 ms  bbr01olvemo-bue-60.olve.mo.charter.com [96.34.2.
166]
  7    36 ms    44 ms    37 ms  10-1-21.ear1.Dallas1.Level3.net [4.15.36.25]
  8   259 ms    60 ms   245 ms  ae-10-10.car2.Montreal2.Level3.net [4.69.153.86]

  9   127 ms   242 ms   239 ms  ae-10-10.car2.Montreal2.Level3.net [4.69.153.86]

 10    58 ms    58 ms    57 ms  ORMUCO-COMM.car2.Montreal2.Level3.net [4.59.178.
74]
 11    51 ms    50 ms    51 ms  192.34.76.10
 12    52 ms    53 ms    57 ms  199.91.189.242
 13    53 ms    54 ms    51 ms  199.91.189.30

[Mika_Stoneheart]

Lexie mine is very similar to yours except I come out of alter.net from FIOS then go to level3. Do a ping test on the last 3 even though Ormuco has less latency issues you actually get most of your packet loss there, at 4.59.178.74

[Raist]

Eep...you got stuck on level3's car2 lines in Montreal. See those show up a lot in threads where people are having problems (and not just for XIV either).

You got a nice capture with that one...would definately look into getting that one to your ISP's tier3 team. It is bad enough you caught a 60 to 200+ swing at the same hop...but notice also that both those hops with the long response times are showing the same address. Something odd is going on there that someone needs to address or route you around.

[Mika_Stoneheart]

And by last three I mean 8, 9, and 10. It's the same thing for me I go through he same hop twice with the same ip. I can't post it now because I'm on my phone. Also can't figure out how to edit messages in mobile site.

[Necroman]

After i click Start on the Heavensward Screen and go to character selection screen. It show goblin and my toon name on the right but no character shows up on the screen. If i click toon name and choose log in and say ok, it says "World data could not be obtained. Please try logging in later." there is an error code of 1014 in bottom right corner.


Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\@@@@@>pathping 184.107.107.176

Tracing route to 184.107.107.176 over a maximum of 30 hops

0 @@@@@@@ [192.168.2.10]
1 router.asus.com [192.168.2.1]
2 192.168.1.1
3 L100.LSANCA-VFTTP-123.verizon-gni.net [98.119.153.1]
4 G0-6-1-7.LSANCA-LCR-21.verizon-gni.net [130.81.138.88]
5 so-3-1-0-0.LAX01-BB-RTR1.verizon-gni.net [130.81.151.236]
6 * * *
Computing statistics for 125 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 @@@@@@@ [192.168.2.10]
0/ 100 = 0% |
1 2ms 0/ 100 = 0% 0/ 100 = 0% router.asus.com [192.168.2.1]
0/ 100 = 0% |
2 2ms 0/ 100 = 0% 0/ 100 = 0% 192.168.1.1
0/ 100 = 0% |
3 6ms 0/ 100 = 0% 0/ 100 = 0% L100.LSANCA-VFTTP-123.verizon-gni.
net [98.119.153.1]
0/ 100 = 0% |
4 10ms 0/ 100 = 0% 0/ 100 = 0% G0-6-1-7.LSANCA-LCR-21.verizon-gni
.net [130.81.138.88]
0/ 100 = 0% |
5 12ms 0/ 100 = 0% 0/ 100 = 0% so-3-1-0-0.LAX01-BB-RTR1.verizon-g
ni.net [130.81.151.236]

Trace complete.

C:\Users\@@@@@@@>ping 184.107.107.176

Pinging 184.107.107.176 with 32 bytes of data:
Reply from 184.107.107.176: bytes=32 time=81ms TTL=52
Reply from 184.107.107.176: bytes=32 time=81ms TTL=52
Reply from 184.107.107.176: bytes=32 time=81ms TTL=52
Reply from 184.107.107.176: bytes=32 time=82ms TTL=52

Ping statistics for 184.107.107.176:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 81ms, Maximum = 82ms, Average = 81ms


Tracing route to 184.107.107.176 over a maximum of 30 hops

1 2 ms 1 ms 1 ms router.asus.com [192.168.2.1]
2 2 ms 1 ms 1 ms 192.168.1.1
3 6 ms 5 ms 5 ms L100.LSANCA-VFTTP-123.verizon-gni.net [98.119.15
3.1]
4 9 ms 10 ms 12 ms G0-6-1-7.LSANCA-LCR-21.verizon-gni.net [130.81.1
38.88]
5 31 ms 40 ms 18 ms so-3-1-0-0.LAX01-BB-RTR1.verizon-gni.net [130.81
.151.236]
6 * * * Request timed out.
7 10 ms 9 ms 10 ms 0.ae6.BR1.LAX15.ALTER.NET [140.222.225.137]
8 10 ms 9 ms 10 ms ix-10-0.tcore1.LVW-Los-Angeles.as6453.net [64.86
.252.97]
9 80 ms 81 ms 80 ms if-3-2.tcore1.PDI-Palo-Alto.as6453.net [66.198.1
27.25]
10 82 ms 81 ms 81 ms if-2-2.tcore2.PDI-Palo-Alto.as6453.net [66.198.1
27.2]
11 82 ms 81 ms 80 ms if-11-3.tcore2.CT8-Chicago.as6453.net [66.198.14
4.58]
12 81 ms 82 ms 82 ms if-3-2.tcore1.W6C-Montreal.as6453.net [66.198.96
.45]
13 82 ms 82 ms 82 ms 66.198.96.58
14 81 ms 81 ms 81 ms te7-3.dr9.mtl.iweb.com [67.205.127.214]
15 81 ms 81 ms 81 ms 72.55.128.44
16 81 ms 81 ms 82 ms 184.107.107.176

Trace complete.

[Raist]

184.107.107.176 is not used for the game. That is hosting websites for mostly the EIDOS arm of SE. It is also on i-web lines and physically in a different section of town.

Either use the neolobby servers or get the IP you actually connect to when logged into the game. You can find them with netstat or by expanding the network related sections of resmon. The Canada IP's start with 199, and the Japan ones start with 124 (if one starting with 202, shows up it is their nameserver in Japan).

[NanaWiloh]

Here is my tracert

Tracing route to 199.91.189.34 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.0.1
2 7 ms 6 ms 8 ms 10.109.152.1
3 15 ms 7 ms 7 ms 192.168.62.89
4 7 ms 7 ms 7 ms 10.224.252.181
5 32 ms 35 ms 35 ms xe-8-2-2.edge2.Seattle1.Level3.net [4.53.158.5]
6 208 ms 147 ms 98 ms ae-10-10.car2.Montreal2.Level3.net [4.69.153.86]
7 225 ms 212 ms 213 ms ae-10-10.car2.Montreal2.Level3.net [4.69.153.86]
8 92 ms 93 ms 93 ms ORMUCO-COMM.car2.Montreal2.Level3.net [4.59.178.74]
9 92 ms 93 ms 93 ms 192.34.76.10
10 94 ms 93 ms 93 ms 199.91.189.242
11 93 ms 93 ms 93 ms 199.91.189.34

Trace complete.

This was from a day ago

[Raist]

Level3's car2 hops in Montreal again.... imagine that?

6 208 ms 147 ms 98 ms ae-10-10.car2.Montreal2.Level3.net [4.69.153.86]
7 225 ms 212 ms 213 ms ae-10-10.car2.Montreal2.Level3.net [4.69.153.86]