SE contact your ISP and fix the lag. Info inside.

[remidi]

From ReplicaX in this post: http://forum.square-enix.com/ffxiv/t...me-to-deliever...

I made a post in the general forum as well as this is affecting a ridiculous amount of people.

If what this customer says is true you need to fix this ASAP SE. Initiate contacting the correct people please. I am getting tired of other users on these forums pointing fingers and blaming everyone but SE for this issue. Get rid of the character limit as well...we are all just editing to bypass it....


"In the case of Verizon in the NE USA. SE pays Ormuco for Data Solutions. Ormuco pays Level 3 for bandwidth. Verizon has a Peering agreement with Level 3.
The problem isn't the Peer Exchange. The Data is getting lost after it in Level 3's network. This is not Verizon's issue. It is between Ormuco and Level 3 but also involves SE as they pay Ormuco.

Right outside the NA DataCenter's internal network:

IP Location: Montreal, Canada Level 3 Communications Inc.
ASN: Canada AS3356 LEVEL3 Level 3 Communications (registered Mar 10, 2000)
Resolve Host: ORMUCO-COMM.car2.Montreal2.Level3.net
IP Address: 4.59.178.74

SE pays Ormuco. SE customers are affected by Ormuco/Level 3. We don't complain to them SE does as they pay them for the service.

As far as other ISPs and different routing idk. I'm only familiar with what I can test."


**More from ReplicaX

"IP Location: Montreal, Canada Level 3 Communications Inc.
ASN: Canada AS3356 LEVEL3 Level 3 Communications (registered Mar 10, 2000)
Resolve Host: ORMUCO-COMM.car2.Montreal2.Level3.net
IP Address: 4.59.178.74

IP Location: Canada, Montreal Ormuco
ASN: Canada AS174 COGENT Cogent/PSI (registered May 16, 1996)
IP Address: 38.122.42.34

Source: whois.arin.net"


I guess the real question is..is this true?

[Raist]

Is what true? Who owns the line, or where your problems lie? I only hit the PSINET line (Cogent partner) in my route now, but 38.122.42.34 does not give me trouble--it's the main residential gateway at 98.25.64.1 (TWC). And I'm not the only one... there have been people along the eastern seaboard having issues at that gateway--and for different services I might add, not just online games. This dates back to at least the spring of 2013 by the way, back before XIV released. There were issues with JustinTV and Twitch that they had to enter into new peering agreements with to resolve, and after peeling that onion a little further people then discovered it was a more systemic problem closer to home. Since discovering this issue after cuting the cord and relying on my Roku for TV content, I've been after TWC like a rabid dog to clean up their network.

We've been in contact with TWC help for some time now off and on, and they've gotten the routes tweaked out pretty good with their partners closer to the end points. Unfortunately, they haven't been able to fix issues revolving around their gateways, which is a problem affecting all TWC customers at the moment and not just FFXIV traffic. Their gateways are just fubar at the moment, and the screwy weather isn't helping any. Let me state this again... I've been in contact with my ISP, and NOT SE or Ormuco over this battle. I pay TWC for the service, and thus have a right and means to pressure them directly to work towards a remedy, and so far it has been working to my benefit, slow though it may be... it IS working.

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  LPTSRV [10.10.100.1]
  2     *        *        *     Request timed out.
  3    12 ms    14 ms    14 ms  cpe-024-031-198-005.sc.res.rr.com [24.31.198.5]
  4    28 ms    27 ms    27 ms  xe-7-0-0.rlghncpop-rtr1.southeast.rr.com [24.93.64.40]
  5    29 ms    30 ms    39 ms  107.14.19.44
  6    30 ms    29 ms    31 ms  ae-2-0.pr0.dca10.tbone.rr.com [66.109.6.169]
  7    82 ms    85 ms    85 ms  te0-16-0-23.ccr41.iad02.atlas.cogentco.com [154.54.10.209]
  8    85 ms    82 ms    84 ms  be2176.ccr21.dca01.atlas.cogentco.com [154.54.41.54]
  9    88 ms    92 ms    94 ms  be2148.ccr21.jfk02.atlas.cogentco.com [154.54.31.118]
 10    66 ms    64 ms    68 ms  be2106.ccr21.ymq02.atlas.cogentco.com [154.54.3.50]
 11    46 ms    45 ms    44 ms  38.122.42.34
 12    44 ms    45 ms    46 ms  192.34.76.10
 13    44 ms    48 ms    46 ms  199.91.189.242
 14    46 ms    45 ms    44 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  LPTSRV [10.10.100.1]
  2    26 ms    18 ms    33 ms  cpe-098-025-064-001.sc.res.rr.com [98.25.64.1]
  3    14 ms    12 ms    11 ms  cpe-024-031-198-005.sc.res.rr.com [24.31.198.5]
  4    27 ms    26 ms    26 ms  xe-7-0-0.rlghncpop-rtr1.southeast.rr.com [24.93.64.40]
  5    45 ms    31 ms    30 ms  107.14.19.44
  6    35 ms    36 ms    30 ms  ae-2-0.pr0.dca10.tbone.rr.com [66.109.6.169]
  7    84 ms    82 ms    84 ms  te0-16-0-23.ccr41.iad02.atlas.cogentco.com [154.54.10.209]
  8    83 ms    86 ms    84 ms  be2113.mpd21.dca01.atlas.cogentco.com [154.54.6.170]
  9    86 ms    90 ms    92 ms  be2150.mpd21.jfk02.atlas.cogentco.com [154.54.31.130]
 10    65 ms    65 ms    67 ms  be2108.ccr21.ymq02.atlas.cogentco.com [154.54.3.134]
 11    44 ms    46 ms    45 ms  38.122.42.34
 12    51 ms    59 ms    47 ms  192.34.76.10
 13    45 ms    43 ms    43 ms  199.91.189.242
 14    44 ms    43 ms    45 ms  199.91.189.25

Trace complete.

When it gets busy, the response times will go up slightly along the route and break into the 100-120ms times at a couple hops like DC and Chicago (you can thank the NSA for that headache), but I'm not getting the high packet losses from the other side of Washington and Chicago anymore. It still happens intermittently, but is very minimal and always in the US when it happens--NOT in Canada, but it shows up within the US corridors.

The TWC/RR gateways and backbones are the larger part of my problems now. This has been tested and proven to be an issue both on a residential and business class line (in the case of the biz class, it was 10.149.64.1 acting up). They routinely break the 100ms response times and periodically time out like one just did in this trace. Ping them over time and they will crap out with times ranging from 8ms on up to 400+ with occasional timeouts. That's at the first hop past our modems, not somewhere out in Canada. Again , that is now the FIRST hop to show evidence of trouble, and it has been their gateway or backbone, which potentially affects everything that follows. Have to understand how the system works... when you trace you test hop 1, then go through hop 1 to test hop 2, then through 1 & 2 to test 3, etc. If you have trouble at hop 2, then you may show the same problem when testing every hop after that, as hop 2 is still being used along your route when you trace it through the rest of your path. It is now down to a systemic problem with how TWC has oversold markets and under maintained their system over time, resulting in grossly overloaded trunks/gateways that THEY are 100% responsible for. They've tried kicking the can down the road, and now it's coming back to bite them in the butt. There's a reason they've lost over 600,000 subscribers in the last year---over 200,000 in the last quarter.

So, you have to be looking at it in the proper perspective I guess. Since it's now been shown there are issues around ther main gateways, EVERYTHING is potentially effected... including streaming video and just trying to get to Google or Yahoo. They tried to pawn it off on the other end, and we aggressively pursued those ends and got them addressed. And now the last piece of the puzzle is squarely in Time Warner's court to address. At least, in my case this seems to be where the problem resides. There are definitely problems in their own network... we're just having a hard time getting the locals to address it. Just take a look at their forums... they have serious problems in house at the moment:
http://forums.timewarnercable.com/t5...p/connectivity

So... I guess it all depends on just where your problems are cropping up, and to what severity as to how relevant who Ormuco is partnering with for peering and transit versus who your ISP is partnering with for their peering and transit. In my case it first appeared to be issues with who TWC was partnering with for their exchanges getting me to Canada (it appears there's only like 3 main companies providing entry points that EVERYONE uses). They've managed to tweak that end out quite nicely, but the problem persists... only now we are able to see it closer to home. So, now they need to focus on issues with their own gateways/backbones here in the states.

This is where many TWC customers are stuck now... waiting on Time Warner to get their sh!t together.

[Discordia]

Comcast is in the process of buying out Time Warner ... so good luck getting any issues resolved. The telcos must be regulated and all lines nationalized, but that won't happen, and with metering, capping and throttling going on, who knows if any of this will get resolved.

[Raist]

Comcast is in the process of buying out Time Warner ... so good luck getting any issues resolved. The telcos must be regulated and all lines nationalized, but that won't happen, and with metering, capping and throttling going on, who knows if any of this will get resolved.

Yeah.. not too excited about that prospect. Though, it may lower our costs slightly... on the other hand, Comcast hasn't faired much better in reputation in some markets. But, the deal is far from done... it still has to be accepted by the shareholders of both companies as well as pass regulatory review. May not see it actually move forward until the end of the year, possibly later if there's enough push-back.

In the mean time, people are still going to harass the h3ll out of them on their own forums and twitter feeds to fix their network. They recently announced proposed upgrades starting this year in the LA and NY markets, with expansion to the remaining markets rolling into 2015/2016. Who knows just how far they've progressed towards that rollout and the actual timeline... hope they keep their word and start it at least with NY and LA. Those markets are really hosed at the moment, and it's affecting everyone that has to go through those corridors.. not just the locals in those markets. May provide some relief to the Oceania and other Pacific regions that are using the NA servers and have to come through California, possibly the EU players also if their coming through that NE region of the US.

Time will tell... hopefully it will be an improvement. If not, there is always AT&T's DSL... if they would just upgrade from the stupid 6Mb cap with the ADSL crap. VDSL is breaking into the Carolinas now though... which gives a glimmer of hope for some real competition one day. FiOS has virtually stalled for our area... which really bites. But, if AT&T manages to break through the local regulatory authorities and can start competing in the 10Mb+ markets, it will make a big difference.

Until then... we have to just stay on the current slackers to actually do the job we pay them to do....