Lag on Adamantoise.

[Cimyr]

I just came back after a few months break and as Im running around doing FATES Im noticing a lot of lag spikes. People stopping and then running forward, my skills taking a moment to go off, etc.

Ive checked my connection on other games, Diablo 3, WoW, LoL, and even my Vent ping and everything is normal, ranging from 15-40 as usual. I havent changed my ISP or internet plan since I left a few months ago, the only change is that I switched from Cactuar to Adamantoise before leaving. But both are on a NA Data Center, Im on the east coast so I dont know if thats the problem or not.

[Raist]

A lot of people are still having a lot of trouble in route... could run traces to your server to see if you can spot any signs of congestion. Or you could check downdetector.com to see if they've logged any issues with your ISP or any of their partners in your region or along your path to Montreal. They also have feeds for different services there too--pull up Hulu, Netflix, or XBL for instance and will often see posts about issues with certain ISP's that are having issues. The XBL map is showing a lot of areas having issues. TWC is still fighting with issues in Ohio, New York, and North Carolina (hubs that a lot of their stuff goes through). A few blips in Main showed up on the TWC map as well.

http://downdetector.com/status/time-warner-cable/map/


Bounce around the downdetector maps, and you will see a pattern forming. Areas around New York and Florida are almost always showing up for a lot of services... as usual, LA and Chicago come up frequently too (the NSA scan happens in Illinois, so Chicago is usually a lag point). The Portland/Seatle Corridor is still getting flaky from time to time as well... nothing new.

[Cimyr]

A lot of people are still having a lot of trouble in route... could run traces to your server to see if you can spot any signs of congestion. Or you could check downdetector.com to see if they've logged any issues with your ISP or any of their partners in your region or along your path to Montreal. They also have feeds for different services there too--pull up Hulu, Netflix, or XBL for instance and will often see posts about issues with certain ISP's that are having issues. The XBL map is showing a lot of areas having issues. TWC is still fighting with issues in Ohio, New York, and North Carolina (hubs that a lot of their stuff goes through). A few blips in Main showed up on the TWC map as well.

http://downdetector.com/status/time-warner-cable/map/


Bounce around the downdetector maps, and you will see a pattern forming. Areas around New York and Florida are almost always showing up for a lot of services... as usual, LA and Chicago come up frequently too (the NSA scan happens in Illinois, so Chicago is usually a lag point). The Portland/Seatle Corridor is still getting flaky from time to time as well... nothing new.

Im not really sure how to run a trace route or what have you but Im beginning to think it'll show the same results as everyone else. I feel silly for not reading the ISP stickied thread at the top to start but I did while waiting for a reply here. From what it looks likes TWC has been having issues non stop so I guess my only option is to wait it out?

At the moment I feel like Im one of the lucky ones, my connection isnt kicking me off every two seconds or anything, just a minor hiccup during prime time hours, but it's still noticeable. Also Im sure it goes without saying but FF is the only service being affected by it. I was just on another MMO not even 10 minutes ago and I had no lag. Get on FF and theres an occasional jump.

[Raist]

If you are indeed with Time Warner, then there may well be issues with your service. Some areas have been struggling for a long time... and it isn't isolated to just FFXIV. I've managed to get nearly all of my route to Midgard cleaned up by working with Tier3---just having a problem at the TWC headend now, which has become another side of this coin we can't seem to get them to address properly.

http://forums.timewarnercable.com/t5...p/connectivity

A month old thread for League of Legends just got revived last week. Saw some other threads a couple weeks back also mentioning LoL, XBL, WoW, D3, and GW2. Recurring posts about issues with VoD, Netflix, etc. come up from time to time as well. XO, Cox, and Comcast have been getting complaints as well, so it hasn't been isolated to just TWC either. It's more of a regional thing---depending on where you are and where you are getting routed through seems to be the more common factor at play.

It's especially troublesome for FFXIV's NA/EU servers because we have a limited number of entry points to Canada. The backbones that get us across the border and through the Great Lakes area just routinely have issues under high levels of traffic--and the more active the player base becomes, the worse the congestion gets. When you start throwing in all the people that are cutting their cable broadcast tiers and switching to streaming services, the worse it's going to get as well. Some of those peering/transit agreements just weren't set up to handle the load and congestion control starts clamping down on us. That's why it becomes important for people to communicate with their ISP's. THEY need to provision wider pipes for us so we can get to where we need/want to go.

[Cimyr]

Yeah, Im currently with Time Warner Cable, it did look like a good part of North Carolina, around Raleigh(Which is about an hour away) was in the yellow around 6-8pm yesterday when I checked that Down Detector website, hell it seemed like TWC has had constant problems since the start of the year if that website is accurate. I havent tried many of the things you listed, I believe my family has been using Netflix and they havent had issues with that, and thats never made my connection shoddy before so I dont think thats the cause of my issues.

I'll be playing more D3 in the next few days so I can probably see what happens when I play that, Id like to see if it's just all the outages in my general area that are causing issues for me as a lot of the spikes seemed to have occured around the times that the problems were listed on Downdetector, but then again everything else was fine.

Ugh I guess I'll have to give TWC a call, but I have no idea where to even begin with them.

Edit- Sorry, typing this before bed and Im tired. I hope I didnt go in circles or say something stupid.

[Raist]

yeah.. sorry.. was typing late last night as well thanks to an all night binge-watch of Blue Exorcist... neglected to go over any how to for gathering/submitting data to TWC help. Just threw something up for someone in the UK about how to test and gather some data to send to their ISP. Ideally, you would want to get the IP of your game server with netstat or resmon, but this should give them enough info to start with, as it is hitting servers the game uses in both Japan and Canada:

http://forum.square-enix.com/ffxiv/t...=1#post1969275

They actually should have such info on file already because we've been hammering them about it for months now (I'm in SC, and typically go through Charlotte or Raleigh). Unfortunately, the way their support structure is laid out, you can be talking to someone in a different region each time you contact them--and they don't appear to share their information often, so if you get someone in Milwaukee they may not have access to the reports generated through Atlanta. I've given up on the phone support and just use email anymore. It's like pulling your own teeth to get through the menus, past the helpdesk, and finally to Tier3. I've just been sending my complaints/reports to their email addy that gets posted at the forums a lot: TWCable.Help@twcable.com

Make sure to reply/forward from your last email each time you contact them, that way all your information stays together in a chain for them to review--you may be dealing with several different reps. After sending them a couple reports about issues with my gateway (98.25.64.1), they finally started calling me back and I got a number to call directly into Tier3 to setup appointments and such. Unfortunately, it does no good to pass the number out, as it goes to a specific group and you have to put in an authorization number specific to your case that expires after a couple days. Things still aren't quite right with my route... but it's a helluva lot better than it used to be:

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    <1 ms  LPTSRV [10.10.100.1]
  2    36 ms    30 ms    11 ms  cpe-098-025-064-001.sc.res.rr.com [98.25.64.1]
  3    13 ms    10 ms    11 ms  cpe-024-031-198-005.sc.res.rr.com [24.31.198.5]
  4    27 ms    26 ms    22 ms  xe-7-0-0.rlghncpop-rtr1.southeast.rr.com [24.93.64.40]
  5    31 ms    31 ms    31 ms  107.14.19.44
  6    34 ms    30 ms    30 ms  ae-2-0.pr0.dca10.tbone.rr.com [66.109.6.169]
  7    35 ms    34 ms    34 ms  te0-16-0-23.ccr41.iad02.atlas.cogentco.com [154.54.10.209]
  8    43 ms    33 ms    36 ms  be2112.mpd22.dca01.atlas.cogentco.com [154.54.5.234]
  9    47 ms    44 ms    40 ms  be2151.mpd22.jfk02.atlas.cogentco.com [154.54.40.74]
 10    45 ms    43 ms    44 ms  be2109.ccr21.alb02.atlas.cogentco.com [154.54.3.138]
 11    68 ms    66 ms    65 ms  be2088.ccr21.ymq02.atlas.cogentco.com [154.54.43.17]
 12    43 ms    43 ms    44 ms  38.122.42.34
 13    46 ms    47 ms    46 ms  192.34.76.10
 14    46 ms    45 ms    47 ms  199.91.189.242
 15    46 ms    44 ms    46 ms  199.91.189.25

Trace complete.

Used to get massive response times (300ms plus) and timeouts (*'s) in the middle where the cogentco segments come in. That is where a lot of lag and packet loss for most people is being found, in the middle of the route with their ISP's routing partners. It took a while for them to clean that section up, and it's good so long as that 2nd hop in my route remains stable. When it starts acting up and stays above about 60ms, things start to go bad. When it crosses a 200ms time, instances start to lag out, past 300ms and they can be unmanageable. This is because once one hop starts misbehaving, it compounds any issues that come at hops after it. We've resolved things down the line now, but just can't seem to get things stable at the first gateway.

My big fear is that we may be stuck with their outdated CMTS until they finish rolling out the DOCSIS 3.0 upgrades (the bleeding things are over a decade old and barely even DOCSIS 2.0 compliant). We've been dogging them at the forums though... hopefully we will get some progress soon. Will be interesting to see what happens if AT&T continues their U-Verse rollouts... VDSL is slowly creeping into the Carolinas, and can match the basic cable package with 16M download speeds for about the same price. Keeping my fingers crossed for some healthy competition in our market. That's what really sucks about the situation... currently the only other wired option is ADSL at 6M download speed, which just won't cut it with how much we use our internet here.

[Cimyr]

yeah.. sorry.. was typing late last night as well thanks to an all night binge-watch of Blue Exorcist... neglected to go over any how to for gathering/submitting data to TWC help. Just threw something up for someone in the UK about how to test and gather some data to send to their ISP. Ideally, you would want to get the IP of your game server with netstat or resmon, but this should give them enough info to start with, as it is hitting servers the game uses in both Japan and Canada:

http://forum.square-enix.com/ffxiv/t...=1#post1969275

They actually should have such info on file already because we've been hammering them about it for months now (I'm in SC, and typically go through Charlotte or Raleigh). Unfortunately, the way their support structure is laid out, you can be talking to someone in a different region each time you contact them--and they don't appear to share their information often, so if you get someone in Milwaukee they may not have access to the reports generated through Atlanta. I've given up on the phone support and just use email anymore. It's like pulling your own teeth to get through the menus, past the helpdesk, and finally to Tier3. I've just been sending my complaints/reports to their email addy that gets posted at the forums a lot: TWCable.Help@twcable.com

Make sure to reply/forward from your last email each time you contact them, that way all your information stays together in a chain for them to review--you may be dealing with several different reps. After sending them a couple reports about issues with my gateway (98.25.64.1), they finally started calling me back and I got a number to call directly into Tier3 to setup appointments and such. Unfortunately, it does no good to pass the number out, as it goes to a specific group and you have to put in an authorization number specific to your case that expires after a couple days. Things still aren't quite right with my route... but it's a helluva lot better than it used to be:

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    <1 ms  LPTSRV [10.10.100.1]
  2    36 ms    30 ms    11 ms  cpe-098-025-064-001.sc.res.rr.com [98.25.64.1]
  3    13 ms    10 ms    11 ms  cpe-024-031-198-005.sc.res.rr.com [24.31.198.5]
  4    27 ms    26 ms    22 ms  xe-7-0-0.rlghncpop-rtr1.southeast.rr.com [24.93.64.40]
  5    31 ms    31 ms    31 ms  107.14.19.44
  6    34 ms    30 ms    30 ms  ae-2-0.pr0.dca10.tbone.rr.com [66.109.6.169]
  7    35 ms    34 ms    34 ms  te0-16-0-23.ccr41.iad02.atlas.cogentco.com [154.54.10.209]
  8    43 ms    33 ms    36 ms  be2112.mpd22.dca01.atlas.cogentco.com [154.54.5.234]
  9    47 ms    44 ms    40 ms  be2151.mpd22.jfk02.atlas.cogentco.com [154.54.40.74]
 10    45 ms    43 ms    44 ms  be2109.ccr21.alb02.atlas.cogentco.com [154.54.3.138]
 11    68 ms    66 ms    65 ms  be2088.ccr21.ymq02.atlas.cogentco.com [154.54.43.17]
 12    43 ms    43 ms    44 ms  38.122.42.34
 13    46 ms    47 ms    46 ms  192.34.76.10
 14    46 ms    45 ms    47 ms  199.91.189.242
 15    46 ms    44 ms    46 ms  199.91.189.25

Trace complete.

Used to get massive response times (300ms plus) and timeouts (*'s) in the middle where the cogentco segments come in. That is where a lot of lag and packet loss for most people is being found, in the middle of the route with their ISP's routing partners. It took a while for them to clean that section up, and it's good so long as that 2nd hop in my route remains stable. When it starts acting up and stays above about 60ms, things start to go bad. When it crosses a 200ms time, instances start to lag out, past 300ms and they can be unmanageable. This is because once one hop starts misbehaving, it compounds any issues that come at hops after it. We've resolved things down the line now, but just can't seem to get things stable at the first gateway.

My big fear is that we may be stuck with their outdated CMTS until they finish rolling out the DOCSIS 3.0 upgrades (the bleeding things are over a decade old and barely even DOCSIS 2.0 compliant). We've been dogging them at the forums though... hopefully we will get some progress soon. Will be interesting to see what happens if AT&T continues their U-Verse rollouts... VDSL is slowly creeping into the Carolinas, and can match the basic cable package with 16M download speeds for about the same price. Keeping my fingers crossed for some healthy competition in our market. That's what really sucks about the situation... currently the only other wired option is ADSL at 6M download speed, which just won't cut it with how much we use our internet here.

Yeah, I know what you mean. I live out in farm land almost at the moment so TWC was the only one that would come out this far, well Century Link will but I found their service to be garbage. So at the moment Im pretty much stuck with TWC.

Anyway thanks for everything Raist, you've been a huge help. I'll keep an eye on my connection the next few days to see if I can figure out the exact times it starts to go haywire and then start sending emails to them. Maybe they'll get things straightened out a bit for me, a guy can hope right?

[Cimyr]

yeah.. sorry.. was typing late last night as well thanks to an all night binge-watch of Blue Exorcist... neglected to go over any how to for gathering/submitting data to TWC help. Just threw something up for someone in the UK about how to test and gather some data to send to their ISP. Ideally, you would want to get the IP of your game server with netstat or resmon, but this should give them enough info to start with, as it is hitting servers the game uses in both Japan and Canada:

http://forum.square-enix.com/ffxiv/t...=1#post1969275

They actually should have such info on file already because we've been hammering them about it for months now (I'm in SC, and typically go through Charlotte or Raleigh). Unfortunately, the way their support structure is laid out, you can be talking to someone in a different region each time you contact them--and they don't appear to share their information often, so if you get someone in Milwaukee they may not have access to the reports generated through Atlanta. I've given up on the phone support and just use email anymore. It's like pulling your own teeth to get through the menus, past the helpdesk, and finally to Tier3. I've just been sending my complaints/reports to their email addy that gets posted at the forums a lot: TWCable.Help@twcable.com

Make sure to reply/forward from your last email each time you contact them, that way all your information stays together in a chain for them to review--you may be dealing with several different reps. After sending them a couple reports about issues with my gateway (98.25.64.1), they finally started calling me back and I got a number to call directly into Tier3 to setup appointments and such. Unfortunately, it does no good to pass the number out, as it goes to a specific group and you have to put in an authorization number specific to your case that expires after a couple days. Things still aren't quite right with my route... but it's a helluva lot better than it used to be:

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    <1 ms  LPTSRV [10.10.100.1]
  2    36 ms    30 ms    11 ms  cpe-098-025-064-001.sc.res.rr.com [98.25.64.1]
  3    13 ms    10 ms    11 ms  cpe-024-031-198-005.sc.res.rr.com [24.31.198.5]
  4    27 ms    26 ms    22 ms  xe-7-0-0.rlghncpop-rtr1.southeast.rr.com [24.93.64.40]
  5    31 ms    31 ms    31 ms  107.14.19.44
  6    34 ms    30 ms    30 ms  ae-2-0.pr0.dca10.tbone.rr.com [66.109.6.169]
  7    35 ms    34 ms    34 ms  te0-16-0-23.ccr41.iad02.atlas.cogentco.com [154.54.10.209]
  8    43 ms    33 ms    36 ms  be2112.mpd22.dca01.atlas.cogentco.com [154.54.5.234]
  9    47 ms    44 ms    40 ms  be2151.mpd22.jfk02.atlas.cogentco.com [154.54.40.74]
 10    45 ms    43 ms    44 ms  be2109.ccr21.alb02.atlas.cogentco.com [154.54.3.138]
 11    68 ms    66 ms    65 ms  be2088.ccr21.ymq02.atlas.cogentco.com [154.54.43.17]
 12    43 ms    43 ms    44 ms  38.122.42.34
 13    46 ms    47 ms    46 ms  192.34.76.10
 14    46 ms    45 ms    47 ms  199.91.189.242
 15    46 ms    44 ms    46 ms  199.91.189.25

Trace complete.

Used to get massive response times (300ms plus) and timeouts (*'s) in the middle where the cogentco segments come in. That is where a lot of lag and packet loss for most people is being found, in the middle of the route with their ISP's routing partners. It took a while for them to clean that section up, and it's good so long as that 2nd hop in my route remains stable. When it starts acting up and stays above about 60ms, things start to go bad. When it crosses a 200ms time, instances start to lag out, past 300ms and they can be unmanageable. This is because once one hop starts misbehaving, it compounds any issues that come at hops after it. We've resolved things down the line now, but just can't seem to get things stable at the first gateway.

My big fear is that we may be stuck with their outdated CMTS until they finish rolling out the DOCSIS 3.0 upgrades (the bleeding things are over a decade old and barely even DOCSIS 2.0 compliant). We've been dogging them at the forums though... hopefully we will get some progress soon. Will be interesting to see what happens if AT&T continues their U-Verse rollouts... VDSL is slowly creeping into the Carolinas, and can match the basic cable package with 16M download speeds for about the same price. Keeping my fingers crossed for some healthy competition in our market. That's what really sucks about the situation... currently the only other wired option is ADSL at 6M download speed, which just won't cut it with how much we use our internet here.

Sorry to bump this again, but I wanted to post this here.

This is my Trace from me to the Adamantoise server during my usual spiking period.


Tracing route to 199.91.189.30 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms READYSHARE [192.168.1.1]
2 <1 ms 1 ms 1 ms 192.168.0.1
3 7 ms 6 ms 6 ms 142.254.198.61
4 8 ms 8 ms 8 ms gig7-2.fyvlncr-rtr1.nc.rr.com [24.88.225.100]
5 18 ms 15 ms 12 ms xe-7-1-3.rlghncpop-rtr1.southeast.rr.com [24.93.64.46]
6 27 ms 25 ms 24 ms 107.14.19.44
7 26 ms 29 ms 22 ms 107.14.19.133
8 24 ms 23 ms 22 ms te0-13-0-23.ccr41.iad02.atlas.cogentco.com [154.54.13.157]
9 25 ms 23 ms 24 ms be2112.mpd22.dca01.atlas.cogentco.com [154.54.5.234]
10 32 ms 29 ms 33 ms be2148.ccr21.jfk02.atlas.cogentco.com [154.54.31.118]
11 34 ms 32 ms 33 ms be2108.ccr21.alb02.atlas.cogentco.com [154.54.3.134]
12 62 ms 61 ms 65 ms be2088.ccr21.ymq02.atlas.cogentco.com [154.54.43.17]
13 48ms 51ms 51ms 38.122.42.34
14 51ms 55ms 62ms 192.34.76.10
15 53ms 52ms 53ms 199.91.189.242
16 51ms 54ms 51ms 199.91.189.30

Thats the full report, though I had to hand type the last 4 entries as it wouldnt show up on my text document. I ran about 4 traces and the results were always the same, my friend who is using Charter Communications was saying she was getting 200ms around her 19th spike in Montreal but from what Im seeing Im not going through Montreal.

I dont think, anyway, I'll have to send an email to TWC soon I think.