Keep getting D/C symbol

[Rydis]

so your saying its my ISP..and not really anything I can do about it?

So why does the same issue present over 3 different ISPs? TWC, Verizon & ATT 4g.

Or is the game just not playable in my location??

I showed WTF traceroute because it shows the drop on the hop, where as a normal tracert doesn't, but here you go. The 2nd image was just to show..bandwidth on my end really wasn't an issue.

http://i.imgur.com/Yx9vNIy.png

I must say today wasn't an issue day either, as I didn't encounter the issue. Usually late Saturdays and Sundays I dont. but I got the issue earlier in the day on both days.

[Raist]

no.. they can help. They just aren't willing to...perhaps you are still stuck in Tier1 or Tier2 support level. I worked directly with Time Warner's Tier3 people...and they have done WONDERS with cleaning things up. Here is a snapshot from tonight:

Tracing route to neolobby02.ffxiv.com [199.91.189.74]
over a maximum of 30 hops:

  1    <1 ms    <1 ms     1 ms  LPTSRV [10.10.100.1]
  2    27 ms    18 ms    28 ms  cpe-75-176-160-1.sc.res.rr.com [75.176.160.1]
  3    29 ms    24 ms    33 ms  cpe-024-031-198-009.sc.res.rr.com [24.31.198.9]
  4    20 ms    20 ms    18 ms  24.31.196.212
  5    24 ms    25 ms    25 ms  be33.chrcnctr01r.southeast.rr.com [24.93.64.182]
  6    30 ms    26 ms    31 ms  bu-ether14.atlngamq46w-bcr00.tbone.rr.com [66.109.6.82]
  7    24 ms    25 ms    40 ms  0.ae2.pr0.atl20.tbone.rr.com [107.14.19.11]
  8    26 ms    26 ms    27 ms  te0-0-0-10.ccr21.atl02.atlas.cogentco.com [154.54.12.109]
  9    27 ms    25 ms    29 ms  be2050.ccr41.atl01.atlas.cogentco.com [154.54.0.165]
 10    35 ms    34 ms    33 ms  be2168.ccr41.dca01.atlas.cogentco.com [154.54.31.94]
 11    42 ms    39 ms    43 ms  be2148.ccr41.jfk02.atlas.cogentco.com [154.54.31.118]
 12    63 ms    60 ms    73 ms  be2106.ccr21.alb02.atlas.cogentco.com [154.54.3.50]
 13    52 ms    49 ms    51 ms  be2088.ccr21.ymq02.atlas.cogentco.com [154.54.43.17]
 14    65 ms    68 ms    68 ms  38.122.42.34
 15    65 ms    64 ms    64 ms  192.34.76.10
 16    65 ms    67 ms    63 ms  199.91.189.242
 17    74 ms    68 ms    74 ms  199.91.189.74

Trace complete.

Believe it or not... that is actually kind of sluggish for a Cogent routing. Don't get me wrong---that is still very solid from here in South Carolina. It's just that I often see the responses around 60 or better at the end. TATA is usually on the order of 70-80, with Level3 pushing up near the 90's (until it hits 150-ish and have to get it changed again).

When I started with them on my issues, we had lag spikes breaking a full second (1000ms), intermittent timeouts, random modem rebooting... you name it. They started at one end and worked their way out. Modem, the DMARC out back, up on the pole.... got everything cleaned up locally and then went to the CMTS (which was bad---no longer use a gateway here in Florence because of it), and on up the route. They routinely change my peering trying to stay ahead of the congestion. It IS manageable to some extent by your ISP---just have to find someone willing to work on it.