good bye FFXIV, thanks to the lag, you lost another customer.

[Zantitrach]

That's very fast. If you want a better answer, go into Command Prompt (Start, type cmd, may need to right-click Run as Administrator). Type tracert 199.91.189.57. Then, type ping 199.91.189.57. Post the results (have to right-click the top bar -> Mark -> highlight what you need -> right-click top bar -> Copy). We can help you get a better answer, and frankly, I'm curious as to what path Comcast takes.

If you're wondering why 199.91.189.57: That's your server's IP address, found here.

Because I'm the guy that just has to know, how do I interpret this data. It looks like I should be interested, especially when most of mine are 30-60ms but then there's this one 329/540 that makes me go, huh.

[Clavaat]

Because I'm the guy that just has to know, how do I interpret this data. It looks like I should be interested, especially when most of mine are 30-60ms but then there's this one 329/540 that makes me go, huh.

Now, use http://whois.net/, and look up the IP address of the hop that has the big ms jump. That will tell you the company that owns it, and gives you sign as to who is responsible.

Use ping to that IP to tell you how much % packet loss you have (over 5% or so is really bad). For ms...basically 100 is starting to get kind of bad, so most of the time you're good. That jump is definitely bad.

Either way, you see how easy that was? And how it only took a few minutes? If everyone experiencing these issues did this, and reported this info to SE / their ISP, we might be able to get something going. Knowledge is power~~~~~~*

[Zantitrach]

Now, use http://whois.net/, and look up the IP address of the hop that has the big ms jump. That will tell you the company that owns it, and gives you sign as to who is responsible.

Use ping to that IP to tell you how much % packet loss you have (over 5% or so is really bad). For ms...basically 100 is starting to get kind of bad, so most of the time you're good. That jump is definitely bad.

Either way, you see how easy that was? And how it only took a few minutes? If everyone experiencing these issues did this, and reported this info to SE / their ISP, we might be able to get something going. Knowledge is power~~~~~~*

Just thought I'd share. It was literally painless to do and I kept playing FFXIV in the background. Lol. Also here's AT&T U-Verse if you're curious

1 1 ms 1 ms 1 ms homeportal [Don't think you need this one]
2 30 ms 29 ms 25 ms 108-221-164-2.lightspeed.brhmal.sbcglobal.net [1
08.221.164.2]
3 * * * Request timed out.
4 24 ms 28 ms 25 ms 12.83.101.149
5 29 ms 30 ms 26 ms 12.122.117.121
6 * 329 ms 549 ms ae15.edge5.atlanta2.level3.net [4.68.62.225]
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 190 ms 54 ms 54 ms ae-5-5.car1.Montreal2.Level3.net [4.69.141.5]
14 54 ms 54 ms 54 ms ae-11-11.car2.Montreal2.Level3.net [4.69.141.1]

15 55 ms 55 ms 57 ms ORMUCO-COMM.car2.Montreal2.Level3.net [4.59.178.
74]
16 * * * Request timed out.
17 63 ms 57 ms 59 ms 192.34.76.2
18 59 ms 59 ms 58 ms 199.91.189.234
19 61 ms 59 ms 59 ms 199.91.189.38

Trace complete.

I couldn't get the actual IP address to pull up on that site, but I did try the ae15.etc.etc and it its answer was

WHOIS information for ae15.edge5.atlanta2.level3.net.com:**

Connection Failure

Love it. Lol

[Clavaat]

-snip-

OK, that's pretty much what I thought.

Level3.net is a Content Delivery Network (CDN). AT&T's connection to it appears to be really bad. For me, on Verizon, the CDN is Alter.Net, which Verizon owns. Level3.net is independent as far as I know, but is notoriously terrible to work with. This is all before we hit SE's server node, and the connections between it and Ormuco (SE's ISP), is bad. So level3 in general is fucking up. This isn't necessarily on AT&T or SE's side, but I would recommend notifying both. There is a contact for Level3 whom you can bitch to, but they will most likely not listen because they suck. AT&T and SE would have to harp on them enough, and even then, they like to play the "it's not on our end, it's yours!" game.

The more information you can provide to both the better. This won't just be FFXIV, but anything that hits that hop.

Honestly surprised that in 12 pages, this thread was never referenced.

This is actually not really relevant to this thread. The post was made in November, and is still true, but the current state of lag is being caused by poor hops/nodes. Either way, it is important and good information, so I would recommend everyone read it, just not for this particular topic.