Specific content is buggered primarily because the servers hosting content can't handle the load too well, and that is getting further compounded by documented routing issues across North America. The pending maintenance should be addressing this in part by <hopefully> alleviating some of the server side congestion issues... but we still have transmission problems at the ISP levels that need addressing.
There is still an issue with many people's routing. Depending on just where the problems are occurring in each specific route, such problems actually fall to those user's ISP to address, which is why SE keeps sloughing it off to them. Your ISP negotiates with other carriers for access to their routes to get you to Montreal to get on SE's ISP's lines. If the problem occurs between your ISP's segments and SE's ISP's segments, then it falls to your ISP to enforce their quality of service agreement with those partners.
SE really has no influence here. Now, if it is happening within Ormuco's segments or SE's internal network, that's a different story. But, if it's a congestion issue at level3, cogentco, TATA, i-WEB, etc. that your ISP has commissioned to carry your data to Montreal--then your ISP needs to get involved to either lean on them to fix the issue, purchase a fatter pipe from them, or route you to a different partner that can better handle the load. Plain and simple--it is an issue with the routing your ISP has negotiated based on their and their partner's analytics that is putting you on a bad path to Montreal.
Think of it like a popular GPS system that keeps sending everyone down the same highways. Something happens to cause a major traffic jam. That GPS system needs to be notified of the impeded traffic flow and begin routing people to an alternate route. If that system does not get those notifications or otherwise does not adjust to move people away from the now congested route, everyone using that GPS system to get to the same location may get stuck in that traffic jam. For whatever reason, the mechanisms put in place with our routing is not kicking in like it should to do just that--we need to let them know. Once they have been notified, it is up to them to resolve our congested routing--NOT SE. The problem is, many people are only in contact with tier1 or tier2 people that can only look at and address localized issues.
In most cases, this is much deeper than a localized problem, so it needs to be addressed by tier3 people and possibly escalated to even higher departments to address peering/exchange/transit agreements for a proper resolution. Don't accept the "reboot your modem/router" and "your connection/signal looks fine" as an answer from your ISP. The problem is typically not at this localized level... you need to push the issue further into tier3 territory, as it is NOT isolated to just SE's servers. It has been reported for multiple games and services--it has affected Netflix and even access to Google content. It is a deeply rooted systemic problem with specific ISP's, and the only way to get it addressed is for their paying customers to push for the changes (be that you to your ISP, or your ISP to their partners). Go check out your ISP's own forums if you don't believe me. TWC's forums are LITTERED with complaints at the moment... and it is NOT just for FFXIV.
http://forums.timewarnercable.com/t5...p/connectivity
Case in point, we've been dealing with TWC to work on our routing issues, and the results have improved dramatically. Aside from a recent issue that has cropped up specific to the RR gateways we use locally, they have managed to get us set up with a pretty clean route now from my area:
Code:
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 296 ms 65 ms 25 ms cpe-098-025-064-001.sc.res.rr.com [98.25.64.1]
3 11 ms 11 ms 17 ms cpe-024-031-198-005.sc.res.rr.com [24.31.198.5]
4 33 ms 30 ms 24 ms xe-7-0-0.rlghncpop-rtr1.southeast.rr.com [24.93.64.40]
5 33 ms 34 ms 32 ms 107.14.19.44
6 28 ms 40 ms 30 ms ae-2-0.pr0.dca10.tbone.rr.com [66.109.6.169]
7 33 ms 43 ms 35 ms te0-16-0-23.ccr41.iad02.atlas.cogentco.com [154.54.10.209]
8 36 ms 32 ms 34 ms be2177.ccr22.dca01.atlas.cogentco.com [154.54.41.206]
9 45 ms 42 ms 44 ms be2148.ccr21.jfk02.atlas.cogentco.com [154.54.31.118]
10 42 ms 43 ms 61 ms be2106.ccr21.alb02.atlas.cogentco.com [154.54.3.50]
11 66 ms 67 ms 71 ms be2088.ccr21.ymq02.atlas.cogentco.com [154.54.43.17]
12 62 ms 61 ms 60 ms 38.122.42.34
13 46 ms 45 ms 46 ms 192.34.76.10
14 42 ms 43 ms 43 ms 199.91.189.242
15 43 ms 44 ms 46 ms 199.91.189.25
Trace complete.
This is from Florence, SC... during prime-time. I can ping SE's servers for 50-80 ms response times all day until the RR gateways get overloaded, then it starts breaking 100ms and goes to crap. The problem comes into play because of an issue with the Time Warner/Road Runner lines... the first ones in the route.
The ONLY time I have issues with my connection now in the general world areas now is when that first gateway gets flakey (which it is on the cusp of doing now, as we just hit primetime). Instanced content still has a bit of a problem even when my conx is good, and SE needs to address their load issues there--but as for the normal world environment, normal quests, FATES and such, gameplay is good so long as the RR gateway is in good shape. It is only when 98.25.64.1 starts hitting the 400+ mark, I start seeing the lag spikes in the the general game environment, and then everything begins to become unmanageable. Right now, the only time instanced content becomes unplayable for me is when my local gateways go to crap. The rest of the route is essentially fine---it's all because our local segments have been oversold. Still waiting to hear back from Tier3 support on that issue... but otherwise, they've managed to work this out on their own somehow.
Again... this was done by working with my ISP, not SE. TWC may have been in contact with them, but I haven't.
Granted, instanced content is a mixed bag with issues on both side of the equation. SE has issues that they need to address (hopefully this maintenance will help considerably), but they are getting compounded by our routing issues. If we get the routing cleaned up, the server side lag may be much more manageable. So, if you are having issues with the normal game environment lagging, you definitely need to lean really hard on your ISP's tier3 support to investigate your specific route and address any issues found on their segments or within their partners segments. Having a tracert to your specific server will help tremendously with that effort. IF it is isolated more to your instanced content, may help if you can identify the server address being used and get a trace to that server for submission. I once caught the .31 IP in use during a duty (I use .74 for lobby and .25 for the world), and also included a problematic trace to that server in one of my reports to TWC. Since I began working with them on this, they have been bouncing my route all over the place... but this current route seems to be holding up.
Now, if I could just get them to split us off of that flaky 98.25.64.1 and onto a better gateway...
Edit:
sorry.. didn't mean to go off on a rant there... but everyone keeps sitting around waiting on SE, complaining to the players about their problems. This isn't a support line to SE by the way... it is user to user support. Read the sticky welcoming you to the Tech Support Forum for an explanation. There are things we actually can do about a large part of our problems... just need people to become a little more proactive.
TLDR: DEMAND your ISP escalate your problem to tier3 or higher--there are documented problems in our routes THEY are responsible for addressing
There are documented routing issues that your ISP is contractually obligated to address. They have the power to do this, and some have actually managed to get it addressed and seen dramatic improvement in quality of gameplay-- to a point. There are still some issues SE needs to address on their instance servers, but even with those problems it can be managed for a large portion of content if your ISP cleans it up.
These problems reside deep in the networks, typically with their routing partners and the local guys that answer the phone and the technicians that come on-site cannot address these issues. You need to push further up the support chain (ask for tier3 support, supervisors, etc.) to get them to take a closer look. Getting an email address so you can send traces clearly showing the signs of congestion (lag spikes and timeouts along the route) will help demonstrate where they need to look.
We need to lean on our providers to get our connections cleaned up. After that is fixed and proven not to be a problem--the rest is squarely on SE to address. Until then, the guys on both sides are going to continue to blame the other because they are both at fault until one of them fixes their sh!t. We may not be able to push SE much on that end... but we can lean on our ISP's. Worst case scenario, we can threaten to move to a competitor (provided we have options in our area).