Quote Originally Posted by min99 View Post
I'm on the west coast and my isp is wavecable.

Tracing route to 184.107.107.176 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms www.asusnetwork.net [192.168.1.1]
2 10 ms 9 ms 11 ms 10.30.0.1
3 8 ms 7 ms 8 ms static-24-113-126-225.wavecable.com [24.113.126.
225]
4 32 ms 17 ms 14 ms wave-gw.ae0.sea-bdr1.noanet.net [64.146.252.253]

5 21 ms 17 ms 24 ms xe-0-3-1.3011.ptl-bdr0.noanet.net [64.184.133.12
2]
6 16 ms 13 ms 13 ms te3-3.ccr01.pdx01.atlas.cogentco.com [38.104.104
.181]
7 22 ms 13 ms 14 ms 154.54.89.54
8 26 ms 25 ms 23 ms te4-3.ccr01.boi01.atlas.cogentco.com [154.54.40.
98]
9 35 ms 34 ms 31 ms te0-0-0-8.ccr21.slc01.atlas.cogentco.com [154.54
.40.89]
10 46 ms 42 ms 44 ms be2127.ccr22.den01.atlas.cogentco.com [154.54.25
.69]
11 56 ms 64 ms 52 ms be2129.mpd21.mci01.atlas.cogentco.com [154.54.26
.114]
12 73 ms 67 ms 74 ms te0-4-0-3.mpd22.ord01.atlas.cogentco.com [154.54
.30.177]
13 83 ms 78 ms 81 ms be2079.ccr21.yyz02.atlas.cogentco.com [154.54.27
.182]
14 80 ms 81 ms 80 ms te7-1.mag02.yyz02.atlas.cogentco.com [154.54.40.
166]
15 87 ms 80 ms 80 ms te4-1.ccr01.yyz03.atlas.cogentco.com [154.54.45.
118]
16 88 ms 89 ms 89 ms 38.122.70.182
17 87 ms 90 ms 87 ms te8-2.cr1.mtl.iweb.com [67.205.127.121]
18 96 ms 88 ms 114 ms te7-4.dr9.mtl.iweb.com [184.107.1.110]
19 88 ms 89 ms 88 ms 72.55.128.44
20 88 ms 89 ms 111 ms 184.107.107.176

Trace complete

I don't know very much about this, but I don't see a problem here, and I'm getting very bad lag and disconnects since about 11am pdt.
Your not taking the normal hops that I see. Where are you located? Who is your ISP? You're being routed through a completely different backbone than most. Would you by chance be behind a VPN/Proxy or firewall?

You're hitting two completely different providers:

iweb - http://iweb.com/?sfcid=70130000000lE...FaU9QgodphcAiw
17 87 ms 90 ms 87 ms te8-2.cr1.mtl.iweb.com [67.205.127.121]
18 96 ms 88 ms 114 ms te7-4.dr9.mtl.iweb.com [184.107.1.110]

Cogent - http://www.cogentco.com/

8 26 ms 25 ms 23 ms te4-3.ccr01.boi01.atlas.cogentco.com [154.54.40.
98]
9 35 ms 34 ms 31 ms te0-0-0-8.ccr21.slc01.atlas.cogentco.com [154.54
.40.89]
10 46 ms 42 ms 44 ms be2127.ccr22.den01.atlas.cogentco.com [154.54.25
.69]
11 56 ms 64 ms 52 ms be2129.mpd21.mci01.atlas.cogentco.com [154.54.26
.114]
12 73 ms 67 ms 74 ms te0-4-0-3.mpd22.ord01.atlas.cogentco.com [154.54
.30.177]
13 83 ms 78 ms 81 ms be2079.ccr21.yyz02.atlas.cogentco.com [154.54.27
.182]
14 80 ms 81 ms 80 ms te7-1.mag02.yyz02.atlas.cogentco.com [154.54.40.
166]
15 87 ms 80 ms 80 ms te4-1.ccr01.yyz03.atlas.cogentco.com [154.54.45.
118]

You have a TON of hops in multiple locations around the US. More so than normal:

8 26 ms 25 ms 23 ms te4-3.ccr01.boi01.atlas.cogentco.com [154.54.40.
98] - Boise, ID
9 35 ms 34 ms 31 ms te0-0-0-8.ccr21.slc01.atlas.cogentco.com [154.54
.40.89] - Salt Lake City, UT
10 46 ms 42 ms 44 ms be2127.ccr22.den01.atlas.cogentco.com [154.54.25
.69] - Denver, CO
11 56 ms 64 ms 52 ms be2129.mpd21.mci01.atlas.cogentco.com [154.54.26
.114]
- I have no clue who this is. A quick Google search on it's domain did yield a ton of people unhappy about packet loss through that node.


These are all Houston, TX racks:

12 73 ms 67 ms 74 ms te0-4-0-3.mpd22.ord01.atlas.cogentco.com [154.54
.30.177]
13 83 ms 78 ms 81 ms be2079.ccr21.yyz02.atlas.cogentco.com [154.54.27
.182]
14 80 ms 81 ms 80 ms te7-1.mag02.yyz02.atlas.cogentco.com [154.54.40.
166]
15 87 ms 80 ms 80 ms te4-1.ccr01.yyz03.atlas.cogentco.com [154.54.45.
118]

I get the feeling that you may have trace routed the wrong IP. You don't seem to be hitting Montreal or any known providers Square goes through at all. Can you double check the IP that ffxi.exe is connecting to?