they know we care because we keep paying them our subs lol
they will fix it soon just give them time
they are a Jap based company and its hard to work for the NA/EU servers
A response needs to be demanded by everyone from SE
Printable View
-
10-01-2013, 07:02 AMCeelo_Mage
-
10-01-2013, 07:29 AMNoah_you are joking right?Quote:
Originally Posted by Ceelo_Mage
just because they are Japanese company doesn't mean they can offer this kind of crappy service to other countries, if they want to expand business over seas they need to be prepared, instead us NA/EU players are treated like second class citizens, this issue has been going on for a month for some, and not one word from SE, their tech support close tickets without answering or redirect players to these forums where they want you to seek help from other players lol
all players are paying the same sub, NA/EU players should NEVER have been treated this way, not to mention the silence from SE about this issue, there is no excuse. -
10-01-2013, 07:35 AMRaist
You guys need to double check the IP you are tracing to to make sure it is the one your game is actually using. I've been seeing an IP out there touted as the datacenter, but that is NOT what your client is using when you are playing. Chasing the wrong tail there.
Also, the problem with the routing is happening on a third party's segment. As has been documented in other threads, there are groups that keep popping up with dramatically increased delays--at times even complete timeouts (not just one star, but * * * and a full retry at times). Three very common providers in those traces: Cogent, i-Web, and TATA. Do a whois lookup on the IP's of your most problematic hops and check who is listed for ownership/administration in ARIN. There is a pretty strong chances that at least one of these 3 names will show up. These segments are NOT managed by SE, nor Ormuco (who manages the IPS that SE's servers are on)--these are completely outside the scope of SE's power, and likely your ISP as well. About all they can do is lean on them to clean up their act, or alter routes to avoid the offensive segments (the latter would be your ISP's responsibility, by the way... not SE's).
Note also, that these hops are physically located either near the US/CA border, or are stationed around Montreal. So, it simply appears to be in large part a regional routing/congestion issue first, potentially compounded by server congestion. If you look closely at your tracerts to your actual world servers, you will notice a specific pattern where the delays are reduced when you get to the SE endpoint---it goes "tits up" (to quote some AU players) when you are entering or cutting across Canada. Even if SE were to pinpoint and resolve congestion and such at the server level--you will STILL be having packet loss and high latency issues because it is a problem in the third party routing.
In order to hopefully better illustrate the issues with the traces, I will paste in two I just took from my laptop. First is to the 184 IP, the second is to the actual IP that XIV uses when I play on Midgard.
Note the IP's where things get worst in BOTH of those traces:Quote:
Tracing route to 184.107.107.176 over a maximum of 30 hops
<local hops removed for security>
4 24 ms 24 ms 24 ms ge-3-0-0.chrlncpop-rtr1.southeast.rr.com [24.93.64.62]
5 30 ms 30 ms 31 ms bu-ether44.atlngamq46w-bcr00.tbone.rr.com [107.14.19.46]
6 38 ms 30 ms 27 ms ae-0-0.pr0.atl20.tbone.rr.com [66.109.6.171]
7 78 ms 76 ms 72 ms te0-0-0-10.ccr21.atl02.atlas.cogentco.com [154.54.12.109]
8 76 ms 76 ms 80 ms be2052.mpd21.atl01.atlas.cogentco.com [154.54.40.249]
9 89 ms 90 ms 90 ms te0-1-0-6.mpd21.dca01.atlas.cogentco.com [154.54.1.226]
10 97 ms 92 ms 95 ms te0-0-0-14.mpd21.jfk02.atlas.cogentco.com [154.54.42.34]
11 118 ms 112 ms * be2108.ccr21.ymq02.atlas.cogentco.com [154.54.3.134]
12 69 ms 69 ms 69 ms 38.122.42.122
13 68 ms 69 ms 68 ms te7-3.dr9.mtl.iweb.com [67.205.127.214]
14 69 ms 68 ms 69 ms 72.55.128.44
15 71 ms 69 ms 68 ms 184.107.107.176
Trace complete.
Tracing route to 199.91.189.74 over a maximum of 30 hops
<local hops removed for security>
4 23 ms 20 ms 24 ms xe-7-0-0.chrlncpop-rtr1.southeast.rr.com [24.93.64.42]
5 31 ms 31 ms 29 ms bu-ether14.atlngamq46w-bcr00.tbone.rr.com [66.109.6.82]
6 27 ms 27 ms 27 ms ae-0-0.pr0.atl20.tbone.rr.com [66.109.6.171]
7 80 ms 89 ms 77 ms te0-0-0-10.ccr21.atl02.atlas.cogentco.com [154.54.12.109]
8 80 ms 78 ms 79 ms be2052.mpd21.atl01.atlas.cogentco.com [154.54.40.249]
9 92 ms 91 ms 87 ms te0-0-0-7.mpd21.dca01.atlas.cogentco.com [154.54.28.197]
10 94 ms 94 ms 98 ms te0-7-0-14.ccr21.jfk02.atlas.cogentco.com [154.54.41.6]
11 114 ms 112 ms 113 ms be2108.ccr21.ymq02.atlas.cogentco.com [154.54.3.134]
12 69 ms 69 ms 78 ms 38.122.42.34
13 69 ms 78 ms 68 ms 10.2.2.1
14 116 ms 67 ms 68 ms 192.34.76.2
15 70 ms 68 ms 67 ms 199.91.189.234
16 69 ms 68 ms 79 ms 199.91.189.74
Trace complete.
154.54.12.109 (Washington, DC: http://myip.ms/info/whois/154.54.12.109)
154.54.3.134 (Washington, DC: http://myip.ms/info/whois/154.54.3.134
Interesting to note that both traces to different servers both had issues in the same subnet, that happen to fall under the same goup. Here's the ARIN info for the entire subnet (154.54.0.0 - 154.54.255.255)--and it is NOT Square-Enix at fault here:
http://whois.arin.net/rest/net/NET-154-54-0-0-1/pft
It's under Cogent Communications, and PSINet, Inc., out of WASHINGTON... NOTHING to do with Square-Enix.
I myself have already forwarded tracerts and such to the Tech and Admin emails I have found for some of their IP's that have been posted in other threads, but have not received a response (didn't really expect to, but I had to try), as well as forwarded details to TWC's NOC and others. A handful of others have taken up this fight as well, and started submitting traces to their ISP's and documented offenders.
But, just a handful of people isn't going to cut it. EVERYBODY needs to get pro-active with this fight.
Load resmon, expand the TCP Connections section to get the actual active IP of your Canadian server (the 124 address is JP, and is idle for the most part once in game). Run traces to it, noting the failing segment and forward the details it to your ISP, noting the name of the group that is responsible for your troubled segments (you can go to www.arin.net and search the IP address to get the report I linked above). You can also go one step further and submit a ticket to SE with the trace and deatils of the failing segment as well, just in case. But, your ISP is the one who may actually have the power to ultimately change your routing, or at the very least perhaps to lean on the ones actually responsible for correcting the problems occurring in route. This may seem like only half the battle, but it is a MAJOR problem that needs to be addressed... not to mention it takes SE's stance of blaming the ISP's off the table if we can clean up the routing problems. -
10-01-2013, 07:43 AMbonniebru5
the amount of subs lost because of this should give SE something to think about lol
-
10-01-2013, 07:48 AMMaza
I appreciate the informative post you made there Raist thank you. Thing is I made a computer (not cheap) and bought an online ce mmo 2 years ago. I pay for the best internet service I can get (once again, not cheap) and paid for 90 service ahead of time, next couple of days after that gameplay goes titsup on me. Once again thanks for the info but I've already done my part and paid my price, I won't be doing SE's and my ISP's job too so I guess I will be waiting and letting my money go to waste /shrug
-
10-01-2013, 07:52 AMNoah_
Hi Raist, thank you again for the info about this, you keep saying it is not SE's fault, I can understand that, but is it really not their fault? plenty of players have no such issue playing other MMOs with the very same ISP they have at home/work, ONLY happen with ARR, why is that?? is it because that SE placed their data center that is handling both NA and EU player base in Montreal? If so, how is this not their fault?? do you think if they had put one data center inside US, and one in EU, would people have the same routing issue?
-
10-01-2013, 07:52 AMRaistThe problem is, if everyone relies on someone else to contact the people who can actually effect a solution to the problem and just gripes and complains to those who can't do anything to fix it.... it may never get resolved.Quote:
Originally Posted by Maza
It's almost like the non-voter complaining about what their elected officials are doing... -
10-01-2013, 07:57 AMMazaIf there is a problem with my motorcycle I will fix it myself because I know how to do it. If there is a problem with my internet I pay someone else to fix it because I know nothing about network stuff. I'm not complaining, I said I would wait, I am patient. I would be glad to pay someone that know how to fix this or wait until someone on these forums for instance figures out exactly what to do. So I'm sorry to dissapoint you sir.Quote:
Originally Posted by Raist
-
10-01-2013, 08:09 AMRaistYes, and no. They could have been provided the same assurances in the US as they were in CA, and run into the same problems. Did you not notice that the problematic segments in those traces are actually in the US?Quote:
Originally Posted by Noah_
It should also be noted that these Ormuco IP's the world servers are using were formerly registered to EIDOS, which is now owned by SE. So, they more or less set this up in-house, of sorts.
http://whois.arin.net/rest/net/NET-199-91-189-0-1/pft
The thing is, once it is on SE's side, the connection appears sound---it is a group of hops between your ISP and SE's provider that is failing.
Note, that it is also affected by where you are coming from and how your ISP is routing. To date, I have had issues only ONCE since beta4 at my house. But, when I tried to hit it from a TWC Business class line only 8 minutes from my house, it went to crap. I'm in SC and on TWC Residential, routed through Charlotte, while the Business Class made a b-line for Atlanta.
These kinds of things are completely out of SE's hands, and they have no way of predicting such problems. When these problem come up outside of their network or their contracted providers, it pretty much is not SE's responsibility to resolve it. If it was something on their end, or with whom they contracted with---that's a different story. But, this particular issue does not actually fall in their court--if anything, it's on your ISP to negotiate with their routing partners to resolve it.
While it's not unreasonable to ask SE to help put pressure on the third parties once we've identified them---it's not entirely fair to outright demand they themselves fix it. The problem is... not enough people are working to actually identify where the problems are, and who is actually at fault. Everyone wants to blame SE for something for which a completely unrelated company is responsible.
We need to finger the right people to get this issue resolved. -
10-01-2013, 08:20 AMRaistThat's just it... we have figured out what needs to be done to get it resolved. Unfortunately, it requires player participation to get the ball rolling.Quote:
Originally Posted by Maza
In the scenario of your motorcycle, if it was something you could not fix yourself and you needed to take it to someone to fix it... just what is your course of action? Do you just call someone and say it's broke, fix it... or do you arrange to get the motorcycle to a mechanic, and describe your problems in detail, perhaps giving specific details on how to reproduce your problem?
That is what we need to do here. The tracert clearly details the problem, where it lies, and in and of itself provides clues for courses of action for your ISP to take. Without that important piece of information, all you are telling them otherwise is "my internet doesn't work right for a certain program". That does NOTHING to effectively troubleshoot/fix your problem. Providing a tracert DOES.
All I'm saying is if you aren't willing/able to participate/contribute to that solution, don't go crying foul when SE does not fix something for which they are not responsible, and also has no power to fix. -
10-01-2013, 10:23 AMMazaOkay dangit Raist ; ) I looked it up and learnt some stuff and here is my tracert (minus my addy) to ffxiv na. What do I do from here please?Quote:
Originally Posted by Raist
http://i116.photobucket.com/albums/o...7-46-03-19.jpg -
10-01-2013, 11:14 AMRaist
Need to trace to the Canadian server. There should be at least 2 connections opened by FFXIV--that one is to Japan, and typically those are not causing problems for those having issues with the NA/EU servers that are in Canada.
As mentioned earlier, the 124 address is the JP one that spends most of it's time idle for those on the NA servers. The problems seem to be with the more active session to the CA server. So far, the ones I have seen posted have started with 199, but that's been for NA users--EU might be in a different subnet. Considering you are coming through the Louisiana area, I'm guessing you are in the US, or at least hiting a NA server? If so, look for another session being used by FFXIV that starts with 199 and trace to that IP and open a support ticket with your ISP (and optionally SE), forwarding that trace to them. If the other FFXIV session doesn't start with 199, but something other than 124 or 202 (another JP block, houses SE's DNS servers among other things)--try tracing to that one instead.
It might be helpful to include the name of the group that manages the bad segments if you can. You may see these show up: cogentco, i-web, or as6453. The first two are the actual names of the providers, the last is used by TATA for a lot of their hops. Probably 90% or more of the time, it winds up being one of those three companies that is having issues--Cogent, i-Web, or TATA. Sometimes the i-Web hops won't say i-web though, as well as some of the TATA won't say as6453--but cogentco is pretty consistent for Cogent Communications. You can search on the IP address at www.arin.net and get the name of the group if you want to include it in your support request, as well as lots of other information. Makes it a bit easier to keep up with who keeps showing up when you make note of those common names, so you may know at a glance if they've done something different with your routing after you submit a ticket.
People can "poo-poo" on this as much as they want, but it CAN actually bring about a change in your routing-hopefully for the better as a whole. Back when TWC was partnered with RR, I had a direct email and phone to tech's in both Myrtle Beach and Columbia, and when I found failing segments in Virginia and Nova Scotia that were affecting my FFXI connections (separate instances, years ago), they switched my DHCP and DNS on my modem and routed me differently. Ever since they started homing me out of Charlotte a few years back, I haven't had any need to have it redone. I'm sometimes getting a little more latency then when I was on a closer network for my 4th hop, but it has had fewer problems with packet loss and such. -
10-01-2013, 12:00 PMLjonesjActually comcast is one of the ones that limit bandwidth to a lot of people in the United states after you hit a certain data limitQuote:
Originally Posted by Appleh4x
-
10-01-2013, 12:10 PMHoroBoro
So... Just my 2 cents here. Not a network engineer.
But the traces your running don't seem to matter. I don't feel 150 ms of lag.
From the videos it seems to me like 1000 ms of lag. Or more.
I mean I can run stuff through Wireshark and check out what's going on behind the scenes, but... I kinda feel like it's on SE to resolve the issue. It's not just 1 or 2 people. It's a lot. We have pages and pages of people concerned about this problem.
The most effective way would be for them reach out to us. Acknowledge there is some sort of problem. Ask us to do tests so we can provide them with feedback. Then provide us with feedback. I doubt it, but heck, but thousands of people could be incorrectly routed to horrible internet connections.
That's not happening so we're in the dark. Which is OK with them apparently. That's my biggest concern. -
10-01-2013, 12:16 PMAppleh4xDepends on the location, in my area they have no limiting policies. I can download 500 terabytes and they won't shut me off.Quote:
Originally Posted by Ljonesj
-
10-01-2013, 12:33 PMRaistThat's just it though... people have been posting traces with 400ms+ delays and timeouts in route. As I stated earlier, I have only experienced issues once. This past weekend I had some choppiness and when I traced I had timeouts around the DC hop (which is where my trace typically flirts with the 100ms mark). I've stated in multiple treads that I have good traces, and don't experience the lag--but there are posted traces with really bad hops in route. The problem is there's dozens of threads out there, and it's hard to find the examples at this point to link or quote them into other threads.Quote:
Originally Posted by HoroBoro
-
10-01-2013, 12:34 PMMazaI'm in Arizona with Cox hispeed. The first numbers from my isp are single digit. I input na.finalfantasyxiv.com to get that. I don't know enough to check other traces? It's cool, i'll get on the horn with cox and see what I can do. Thanks for all the info though.Quote:
Originally Posted by Raist
-
10-01-2013, 12:37 PMIstymWhen you say we, do you really mean you?Quote:
Originally Posted by Raist
Regardless I been down the tracert road hundreds of times. And when its taking 10 seconds to cast my fishing rod after pressing the cast button tracert shows zero issues. The common denominator however seems to be when the servers are, you know, creaking at capacity.
To state SE are in no way responsible, well I just have to question your motives tbh. -
10-01-2013, 01:00 PMRaistno.. a lot of people have been posting/reviewing trace postings in other threads and have spotted patterns. A good bit had been posted in the sticky about the P2P throttling, but there's been a bunch of other threads over the last couple weeks in both the Tech Support and General sections. But, if you haven't been following the lag/latency debate threads you probably missed them.Quote:
Originally Posted by Istym
{Edit}: Teebz tried to get a thread going to consolidate links to the various discussions, but it's just a small portion of what is out there:
http://forum.square-enix.com/ffxiv/t...connect-Issues
And I never said that they are in no way responsible---I've stated they aren't responsible for issues that occur in route when it occurs on segments they have no influence over. I've also stated that if we can manage to get some action taken to resolve such issues, than SE can no longer use the tactic of blaming the ISP's for the problem. Even specifically pointed out several times across threads that even IF SE pinpoints and corrects issues within their own infrastructure---there will still be the issues that are happening in route.
All of this is about pinpointing problems in peering on the way to the endpoint, and forwarding it to people that might actually be able to get someone to resolve those issues. No matter how good the servers are, if your route is FUBAR, you will still have problems. This is something that we actually stand a chance at impacting---issues on SE's end are completely up to them to resolve. This particular part of the problem is NOT on their end, but in between us and them. -
10-01-2013, 01:09 PMIstym
And what I am saying is... if I have no problems on the way to the end point why do I still have problems with major lag in game? And why for example was it fine for the whole week prior to this weeks maintainence.
I understand your angle here but I'm really failing to see the correlation and believe me I would love too, because then I too could go banging on the doors I need to in order to realise resolution.
I agree maybe many have routing issues.
My point is also many don't.
And regardless SquareEnix have a duty of care to engage their customers in a more professional manner because the apparent lack of support via many channels is borderline none existent and frankly arrogant. -
10-01-2013, 01:09 PMRaistSomeone had posted a simplified how-to in one of the threads, will see if I can find it and edit it in. It involves using Resource Monitor to easily find the IP, and then running the tracert in DOS and such.Quote:
Originally Posted by Maza
-
10-01-2013, 01:12 PMIstym
run netstat -a from a cmd window and it will show whatever open connections you have currently on the machine.
FFXIV will be connecting to ports > 50k -
10-01-2013, 01:23 PMRaistAre you sure you are tracing to your server? Your profile shows you are on Moogle, yet I've seen you post traces to the same IP I've been using, and I'm on Midgard? Unless perhaps we are all shooting through the same front-end and no longer going directly to separate servers like we were before... Those traces you posted were also in off peak, so that may have been part of it too. However, you did have your delays triple/quadruple when you got to a certain point in the route, so if things were to get flaky intermittently (as they are prone to do), it could get pretty ugly.Quote:
Originally Posted by Istym
There are definite issues out there with some groups and their routers---some are continually reported as being lossy/laggy. It's not just an FFXIV thing (you can find WoW threads about it going back several years with these same companies), and knowing this it's a pretty good bet that it is an important factor here. -
10-01-2013, 01:26 PMIstym
I used all the IPs returned by a netstat report so we must all be going through the same front end then as these are the IP's I am connected to and I will repost tomorrow during peak times as I see minimal change in any tracert values during peak times.
And I did state i was aware it is currently off peak when i posted the tracert reports.
I restate server capacity as the sole reason for my issue. -
10-01-2013, 01:38 PMRaist
bah.. can't find the how-to. Sucks too.. it had screenshots too.
Basically, run resmon--this can be from the Run or Search box off your Start Menu and such. Once that is running, expand the section for Networking or TCP Connections (depending on your Windows version, you may have only one or both--pick which view works best for you). This section will list running programs and the addresses they are linking to (may give the names or just the IP address). Launch FFXIV, may want to configure it for windowed mode in case your system has problems with alt-tabbing. Once you are in game for about a minute, alt-tab back to Resource Monitor and look for the FFXIV executibles (you can click on the list's "Image" heading to sort by name). There should be at least two instances running, each with different IP addresses listed. The one starting with 199 should be the NA server it is using.
Now you can run tracerts and such in a DOS prompt or in any number of other diagnostic tools. Depending on how dedicated your ISP support is, you might even be able to get away with just handing the IP off to them and they can telnet into your modem and do the research for you (may be rare though...but you never know). -
10-01-2013, 01:40 PMFreyar
Hell, some routers can even do these things.
-
10-01-2013, 01:43 PMIstym
And gz on deviating the focus of the thread from its original purpose, getting a response from SquareEnix, to directing people to harass their ISP's instead.
-
10-01-2013, 01:45 PMFreyarBecause gathering information on WHY there are issues isn't helpful to solving the issue. Not everyone has the same problem, and sometimes it's useful for some to check their own before they look elsewhere.Quote:
Originally Posted by Istym
-
10-01-2013, 02:00 PMDano
this and the issue with AoEs hitting while you're outside of it is a big issue here.
-
10-01-2013, 02:06 PMFreyar...Stone Vigil, so bad for that.Quote:
Originally Posted by Dano
-
10-01-2013, 02:07 PMPhyrexianwrathBecause you aren't capable of making your own thread to discuss the problems and gather information. Istym is completely right. This wasn't intended to be a thread for discussion. It had a simple and very pointed purpose. To get a response from SE. Take your discussions and theorycrafting to another thread please.Quote:
Originally Posted by Freyar
-
10-01-2013, 02:11 PMFreyarGetting information before getting a response from SE means we can push for something relevant as opposed to a copy of what we already know. You seem high-strung though, so eh.. enjoy your day. :PQuote:
Originally Posted by Phyrexianwrath
-
10-01-2013, 02:21 PMRaistSo... you would rather them harass instead a company that might not be able to do anything at all to remedy a particular problem, that has a definite impact on the situation in question? Guess you just aren't getting it...Quote:
Originally Posted by Istym
Have you not even considered that perhaps you are asking for a response from the wrong people?
The routers that have been called into question within the scope of FFXIV traffic have been documented elsewhere as having issues. In other words, they are known to cause these kinds of problems with other games and applications. Why not try to get action on what is known to be a problem, and has a known means for affecting change... versus clamoring for a response from someone who may not even be able to provide the answers you seek? I mean seriously... look at all the IP's in that subnet that openly respond to pings:
IP Ping Hostname Ports
199.91.189.1 203*ms [n/a] [n/s]
199.91.189.2 197*ms [n/a] [n/s]
199.91.189.3 186*ms [n/a] [n/s]
199.91.189.4 176*ms [n/a] [n/s]
199.91.189.5 163*ms [n/a] [n/s]
199.91.189.9 126*ms [n/a] [n/s]
199.91.189.10 116*ms [n/a] [n/s]
199.91.189.11 75*ms [n/a] [n/s]
199.91.189.17 68*ms [n/a] [n/s]
199.91.189.18 69*ms [n/a] [n/s]
199.91.189.19 68*ms [n/a] [n/s]
199.91.189.20 69*ms [n/a] [n/s]
199.91.189.21 69*ms [n/a] [n/s]
199.91.189.22 69*ms [n/a] [n/s]
199.91.189.23 69*ms [n/a] [n/s]
199.91.189.24 69*ms [n/a] [n/s]
199.91.189.25 78*ms [n/a] [n/s]
199.91.189.26 69*ms [n/a] [n/s]
199.91.189.27 79*ms [n/a] [n/s]
199.91.189.28 70*ms [n/a] [n/s]
199.91.189.29 69*ms [n/a] [n/s]
199.91.189.30 74*ms [n/a] [n/s]
199.91.189.31 69*ms [n/a] [n/s]
199.91.189.32 69*ms [n/a] [n/s]
199.91.189.33 69*ms [n/a] [n/s]
199.91.189.34 69*ms [n/a] [n/s]
199.91.189.35 69*ms [n/a] [n/s]
199.91.189.36 69*ms [n/a] [n/s]
199.91.189.37 69*ms [n/a] [n/s]
199.91.189.38 69*ms [n/a] [n/s]
199.91.189.39 70*ms [n/a] [n/s]
199.91.189.40 70*ms [n/a] [n/s]
199.91.189.41 73*ms [n/a] [n/s]
199.91.189.42 77*ms [n/a] [n/s]
199.91.189.43 70*ms [n/a] [n/s]
199.91.189.44 71*ms [n/a] [n/s]
199.91.189.45 72*ms [n/a] [n/s]
199.91.189.46 71*ms [n/a] [n/s]
199.91.189.47 75*ms [n/a] [n/s]
199.91.189.48 68*ms [n/a] [n/s]
199.91.189.49 69*ms [n/a] [n/s]
199.91.189.50 70*ms [n/a] [n/s]
199.91.189.51 72*ms [n/a] [n/s]
199.91.189.52 68*ms [n/a] [n/s]
199.91.189.53 69*ms [n/a] [n/s]
199.91.189.54 70*ms [n/a] [n/s]
199.91.189.55 69*ms [n/a] [n/s]
199.91.189.56 70*ms [n/a] [n/s]
199.91.189.57 69*ms [n/a] [n/s]
199.91.189.58 69*ms [n/a] [n/s]
199.91.189.59 69*ms [n/a] [n/s]
199.91.189.60 70*ms [n/a] [n/s]
199.91.189.61 69*ms [n/a] [n/s]
199.91.189.62 69*ms [n/a] [n/s]
199.91.189.65 71*ms [n/a] [n/s]
199.91.189.66 70*ms [n/a] [n/s]
199.91.189.67 72*ms [n/a] [n/s]
199.91.189.68 78*ms [n/a] [n/s]
199.91.189.69 79*ms [n/a] [n/s]
199.91.189.70 81*ms [n/a] [n/s]
199.91.189.71 69*ms [n/a] [n/s]
199.91.189.72 75*ms [n/a] [n/s]
199.91.189.74 78*ms [n/a] [n/s]
199.91.189.75 76*ms [n/a] [n/s]
199.91.189.76 70*ms [n/a] [n/s]
199.91.189.77 71*ms [n/a] [n/s]
199.91.189.78 72*ms [n/a] [n/s]
199.91.189.79 69*ms [n/a] [n/s]
199.91.189.80 69*ms [n/a] [n/s]
199.91.189.81 70*ms [n/a] [n/s]
199.91.189.82 69*ms [n/a] [n/s]
199.91.189.83 70*ms [n/a] [n/s]
199.91.189.84 70*ms [n/a] [n/s]
199.91.189.85 68*ms [n/a] [n/s]
199.91.189.86 71*ms [n/a] [n/s]
199.91.189.87 69*ms [n/a] [n/s]
199.91.189.88 69*ms [n/a] [n/s]
199.91.189.89 70*ms [n/a] [n/s]
199.91.189.97 69*ms [n/a] [n/s]
199.91.189.98 69*ms [n/a] [n/s]
199.91.189.99 69*ms [n/a] [n/s]
199.91.189.102 69*ms dns-n1.na.square-enix.net[n/s]
199.91.189.103 69*ms dns-n2.na.square-enix.net[n/s]
199.91.189.104 71*ms [n/a] [n/s]
199.91.189.105 87*ms [n/a] [n/s]
199.91.189.110 69*ms [n/a] [n/s]
199.91.189.209 69*ms [n/a] [n/s]
199.91.189.210 69*ms [n/a] [n/s]
199.91.189.211 69*ms [n/a] [n/s]
199.91.189.212 71*ms [n/a] [n/s]
199.91.189.225 69*ms [n/a] [n/s]
199.91.189.226 69*ms [n/a] [n/s]
199.91.189.229 70*ms [n/a] [n/s]
199.91.189.230 76*ms [n/a] [n/s]
199.91.189.233 72*ms [n/a] [n/s]
199.91.189.234 75*ms [n/a] [n/s]
199.91.189.237 70*ms [n/a] [n/s]
199.91.189.238 73*ms [n/a] [n/s]
199.91.189.241 69*ms [n/a] [n/s]
199.91.189.242 69*ms [n/a] [n/s]
199.91.189.245 69*ms [n/a] [n/s]
199.91.189.246 68*ms [n/a] [n/s]
Who knows how many of those are game servers. Now consider how many players are involved. Do you really expect SE to single-handedly back trace everyone's session to see if they have communication issues, and if so where does it lie, and who do they contact to fix it?
It just seems much more practical for those experiencing communications problems to take a few simple steps to generate a short report that may provide the bulk of those answers (or at least decent clues), then pass it off to people who might be able to take some action.
And it might not have gotten so derailed if not for people disputing the validity of an established problem that is impacting communications. -
10-01-2013, 02:34 PMFreyar
At the same time, we know that Cogent Communications is impacting Comcast and potentially Verizon customers.
-
10-01-2013, 02:40 PMIstym
No, I expect SquareEnix to engage with their customers regardless instead of flat out ignoring them. And as already stated I have not seen the routing issues you are quick to diagnose.
We can argue back and forth about this until the end of days so lets get back on track with the original intent of the OP.
Because currently the community is being ignored by SquareEnix and gathering whatever fancy reports you like will not change that!Quote:
This is a plea to other players. We need SE to respond, we need something to restore a modicum of faith in the company. Don't just reply with your IP, location, etc in that other thread. Reply here or make your own threads. Keep it as civil as you can. But we all know frustration needs to be expressed, to let them know how much we care.
-
10-01-2013, 02:59 PMKisaiTenshiCogent is known for generally being the go-to ISP for low quality bulk bandwidth (think CDN's and Youtube) not game traffic/VoIP.Quote:
Originally Posted by Freyar
http://gigaom.com/2013/06/20/verizon...cogents-fault/
http://gigaom.com/2013/09/16/video-i...ry-giants-are/ -
10-01-2013, 03:05 PMFreyarEither way, they do play a part here (as well as for League of Legends.)Quote:
Originally Posted by KisaiTenshi
Quote:
Tracing route to 199.91.189.27 over a maximum of 30 hops
- 1 <1 ms <1 ms <1 ms 10.64.4.254
- 2 1 ms <1 ms <1 ms 10.1.10.1
- 3 37 ms 22 ms 12 ms 96.80.148.1
- 4 11 ms 10 ms 12 ms te-0-6-0-5-sur03.saltlakecity.ut.utah.comcast.net [68.85.39.49]
- 5 11 ms 11 ms 15 ms 162.151.9.213
- 6 27 ms 25 ms 21 ms pos-2-1-0-0-cr01.denver.co.ibone.comcast.net [68.86.90.237]
- 7 25 ms 24 ms 20 ms te3-5.ccr01.den03.atlas.cogentco.com [154.54.10.33]
- 8 27 ms 22 ms 23 ms te0-6-0-3.ccr21.den01.atlas.cogentco.com [154.54.45.181]
- 9 68 ms 68 ms 79 ms be2129.mpd21.mci01.atlas.cogentco.com [154.54.26.114]
- 10 81 ms 84 ms 79 ms te0-0-0-4.mpd21.ord01.atlas.cogentco.com [154.54.30.169]
- 11 120 ms 110 ms 101 ms be2079.ccr21.yyz02.atlas.cogentco.com [154.54.27.182]
- 12 117 ms 112 ms 110 ms be2090.ccr21.ymq02.atlas.cogentco.com [154.54.30.206]
- 13 120 ms 116 ms 115 ms 38.122.42.34
- 14 * * * Request timed out.
- 15 71 ms 71 ms 73 ms 192.34.76.2
- 16 71 ms 75 ms 73 ms 199.91.189.234
- 17 70 ms 71 ms 71 ms 199.91.189.27
-
10-01-2013, 03:43 PMPhyrexianwrath
I'm asking again, please take your discussions to another thread. Some of you may not have bothered reading the original post. This isn't for discussing what is wrong or how it should be fixed, because none of us know.
-
10-01-2013, 04:21 PMFreyar
They already indirectly said something by accepting the report as a proper bug report.
-
10-01-2013, 05:51 PMSargon
You can fix this issue by using a vpn, but then SE thinks you're getting hacked and you have to change your password on a regular basis.
I'm not a pro with these issues, but if a freeware can fix the problem, I can't see why a huge company like SE couldn't...