Error 90000 (90k) and others relating to it

[Kyshietahla]

I ran a pathping because I am getting constant 90k disconnects so much so that it's not even playable. I have had to do cutscene quests multiple times and cannot run any dungeons without getting DCd a handful or more times. My husband also plays but he isn't having any issues with disconnecting. He's playing on the PS4. I play on a windows 8 computer. We both use the same internet and are both wired. I get no packet loss on the line until the end where it is out of my home and service providers control. I'm only pasting the part that has the issue.

Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address

13 62ms 0/ 100 = 0% 0/ 100 = 0% 64.86.85.1
0/ 100 = 0% |
14 63ms 0/ 100 = 0% 0/ 100 = 0% if-10-2.tcore1.TTT-Toronto.as6453.net [64.86.32.33]
0/ 100 = 0% |
15 62ms 0/ 100 = 0% 0/ 100 = 0% if-9-9.tcore1.TNK-Toronto.as6453.net [64.86.33.25]
0/ 100 = 0% |
16 65ms 0/ 100 = 0% 0/ 100 = 0% if-7-2.tcore1.W6C-Montreal.as6453.net [66.198.96.61]
0/ 100 = 0% |
17 --- 100/ 100 =100% 100/ 100 =100% 66.198.96.58
0/ 100 = 0% |
18 --- 100/ 100 =100% 100/ 100 =100% te7-3.dr9.mtl.iweb.com [67.205.127.214]
0/ 100 = 0% |
19 65ms 0/ 100 = 0% 0/ 100 = 0% 72.55.128.44
0/ 100 = 0% |
20 66ms 0/ 100 = 0% 0/ 100 = 0% 184.107.107.176

Trace complete.

So after contacting SE and my ISP I've come to the conclusion that between the two ping tests shown here the problem is the same regardless. Unfortunately, this problem is not in the control of ISPs or SE. The problem is with the hub that the signal is going through. I've tracked down the IP address source. It appears the ones that control the IPs causing the issue is either Tata Communications based in Montreal canada or IWeb Technologies.

If my suspicions are correct, this is possibly the same issue others are having. If anyone that sees this could go to command prompt and type in pathping 184.107.107.176 and paste in here where the packet losses are I'd like to consolidate the results and perhaps notify the source of the problem or hope that SE might be able to.

[Polgara]

11 37ms 0/ 100 = 0% 0/ 100 = 0% 64.86.85.1
0/ 100 = 0% |
12 35ms 0/ 100 = 0% 0/ 100 = 0% if-10-2.tcore1.TTT-Toronto.as6453.
net [64.86.32.33]
0/ 100 = 0% |
13 31ms 0/ 100 = 0% 0/ 100 = 0% if-9-9.tcore1.TNK-Toronto.as6453.n
et [64.86.33.25]
0/ 100 = 0% |
14 44ms 0/ 100 = 0% 0/ 100 = 0% if-7-2.tcore1.W6C-Montreal.as6453.
net [66.198.96.61]
0/ 100 = 0% |
15 --- 100/ 100 =100% 100/ 100 =100% 66.198.96.58
0/ 100 = 0% |
16 --- 100/ 100 =100% 100/ 100 =100% te7-3.dr9.mtl.iweb.com [67.205.127
.214]
0/ 100 = 0% |
17 35ms 0/ 100 = 0% 0/ 100 = 0% 72.55.128.44
0/ 100 = 0% |
18 45ms 0/ 100 = 0% 0/ 100 = 0% 184.107.107.176

Trace complete.

[Chizurui]

Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 Owner-PC.westell.com [10.0.0.24]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% dslrouter.westell.com [10.0.0.1]
0/ 100 = 0% |
2 23ms 0/ 100 = 0% 0/ 100 = 0% mo-76-0-16-1.dhcp.embarqhsd.net [7
6.0.16.1]
0/ 100 = 0% |
3 23ms 0/ 100 = 0% 0/ 100 = 0% mo-69-34-117-89.dhcp.embarqhsd.net
[69.34.117.89]
0/ 100 = 0% |
4 32ms 0/ 100 = 0% 0/ 100 = 0% 208-110-240-186.centurylink.net [2
08.110.240.186]
0/ 100 = 0% |
5 32ms 0/ 100 = 0% 0/ 100 = 0% bb-kscbmonr-jx9-01-ae0.core.centur
ytel.net [206.51.69.5]
0/ 100 = 0% |
6 48ms 0/ 100 = 0% 0/ 100 = 0% bb-dllstx37-jx9-02-xe-11-1-0.core.
centurytel.net [206.51.69.25]

Trace complete.

[Xruptor]

Please see the post further down in this thread for the correct IP.

DO NOT USE 184.107.107.176 That is the wrong IP address.

http://forum.square-enix.com/ffxiv/t...=1#post2180490
-----------------------

try it for yourselves

Windows Start Button -> type 'cmd' (or open a command prompt)

in the command prompt type the following for NA servers

Here is my example. I play on the Adamantoise server so my IP 199.91.189.28
To get the IP of your Server follow the instructions in the link above.


pathping 199.91.189.28 <--- this is for the Adamantoise Server (not a generic IP)

[Kazzera]

Looks like whatever this "iweb.com" datacenter is the one having the issues. Here's my pathping:

3 24ms 0/ 100 = 0% 0/ 100 = 0% te-9-1-ur01.longmont.co.denver.comcast.net [68.85.107.225]

4 25ms 0/ 100 = 0% 0/ 100 = 0% te-0-10-0-5-ar02.denver.co.denver.comcast.net [68.86.103.154]

5 28ms 0/ 100 = 0% 0/ 100 = 0% te-0-4-0-1-ar02.denver.co.denver.comcast.net [68.86.179.154]

6 29ms 0/ 100 = 0% 0/ 100 = 0% te-1-1-0-4-cr01.chicago.il.ibone.comcast.net [68.86.95.205]

7 30ms 0/ 100 = 0% 0/ 100 = 0% xe-4-0-0-0-pe01.910fifteenth.co.ibone.comcast.net [68.86.82.178]

8 28ms 0/ 100 = 0% 0/ 100 = 0% 173.167.58.162

9 49ms 0/ 100 = 0% 0/ 100 = 0% if-4-0-1-0.tcore1.CT8-Chicago.as6453.net [209.58.57.130]

10 52ms 0/ 100 = 0% 0/ 100 = 0% if-22-2.tcore2.CT8-Chicago.as6453.net [64.86.79.1]

11 76ms 0/ 100 = 0% 0/ 100 = 0% if-3-2.tcore1.W6C-Montreal.as6453.net [66.198.96.45]

12 --- 100/ 100 =100% 95/ 100 = 95% 66.198.96.58

13 --- 100/ 100 =100% 95/ 100 = 95% te7-3.dr9.mtl.iweb.com [67.205.127.214]

14 75ms 6/ 100 = 6% 1/ 100 = 1% 72.55.128.44

15 78ms 5/ 100 = 5% 0/ 100 = 0% 184.107.107.176

Trace complete.

[Xruptor]

Looks like whatever this "iweb.com" datacenter is the one having the issues.

It sure seems that way. It can't be coincidence that everyone is getting massive data loss at those two hops.

12 --- 100/ 100 =100% 95/ 100 = 95% 66.198.96.58

13 --- 100/ 100 =100% 95/ 100 = 95% te7-3.dr9.mtl.iweb.com [67.205.127.214]

[Ravenwood]

0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% 192.168.1.1
0/ 100 = 0% |
2 --- 100/ 100 =100% 100/ 100 =100% 10.145.16.1
0/ 100 = 0% |
3 7ms 0/ 100 = 0% 0/ 100 = 0% dtr01dlthmn-tge-0-1-1-1.dlth.mn.ch
arter.com [96.34.27.74]
0/ 100 = 0% |
4 7ms 0/ 100 = 0% 0/ 100 = 0% crr01dlthmn-tge-0-0-0-6.dlth.mn.ch
arter.com [96.34.26.40]
0/ 100 = 0% |
5 20ms 0/ 100 = 0% 0/ 100 = 0% crr02stcdmn-bue-1.stcd.mn.charter.
com [96.34.27.166]
0/ 100 = 0% |
6 22ms 0/ 100 = 0% 0/ 100 = 0% bbr01stcdmn-bue-3.stcd.mn.charter.
com [96.34.2.136]
0/ 100 = 0% |
7 37ms 0/ 100 = 0% 0/ 100 = 0% bbr02chcgil-bue-1.chcg.il.charter.
com [96.34.1.149]
0/ 100 = 0% |
8 28ms 0/ 100 = 0% 0/ 100 = 0% 38.122.181.77
0/ 100 = 0% |
9 35ms 0/ 100 = 0% 0/ 100 = 0% be2003.ccr42.ord01.atlas.cogentco.
com [154.54.29.21]
0/ 100 = 0% |
10 40ms 0/ 100 = 0% 0/ 100 = 0% be2080.ccr22.yyz02.atlas.cogentco.
com [154.54.42.6]
0/ 100 = 0% |
11 40ms 0/ 100 = 0% 0/ 100 = 0% te0-0-2-3.rcr11.b011027-3.yyz02.at
las.cogentco.com [154.54.6.242]
0/ 100 = 0% |
12 40ms 0/ 100 = 0% 0/ 100 = 0% 38.122.70.182
0/ 100 = 0% |
13 --- 100/ 100 =100% 100/ 100 =100% ae21.cr6.mtl.iweb.com [67.205.127.
121]
0/ 100 = 0% |
14 --- 100/ 100 =100% 100/ 100 =100% ae0.cr5.mtl.iweb.com [184.107.1.61
]
0/ 100 = 0% |
15 --- 100/ 100 =100% 100/ 100 =100% te7-4.dr9.mtl.iweb.com [184.107.1.
110]
0/ 100 = 0% |
16 52ms 0/ 100 = 0% 0/ 100 = 0% 72.55.128.44
0/ 100 = 0% |
17 49ms 0/ 100 = 0% 0/ 100 = 0% 184.107.107.176

Trace complete.

YEP! Please fix it!

[Gisela_Savage]

I've been getting the 9000 error continuously tonight. I finally decided to have enough.

Here's my ping result:

6 --- 100/ 100 =100% 100/ 100 =100% 139.156.127.2
0/ 100 = 0% |


Trace complete.

Apparently I've got only one 'loss' line.... I'm on EU server...

Can this be fixed a.s.a.p.?

[Mykll]

Pathping does not even complete for me. It is like it hits the first "Request timed out" and stops there.

tracert 184.107.107.176
Tracing route to 184.107.107.176 over a maximum of 30 hops
1 1 ms 1 ms 1 ms
2 77 ms 73 ms 74 ms
3 74 ms 73 ms 74 ms 71.22.6.161
4 * * * Request timed out.
5 114 ms 116 ms 106 ms 4.69.146.17
6 90 ms 133 ms 113 ms ae-81-81.ebr1.Dallas1.Level3.net [4.69.151.150]
7 101 ms 109 ms 107 ms ae-14-14.ebr2.Chicago2.Level3.net [4.69.151.117]
8 116 ms 125 ms 107 ms ae-1-100.ebr1.Chicago2.Level3.net [4.69.132.113]
9 109 ms 99 ms 124 ms ae-6-6.ebr1.Chicago1.Level3.net [4.69.140.189]
10 152 ms * * ae-10-10.car2.Montreal2.Level3.net [4.69.153.86]
11 113 ms 114 ms * 4.59.178.62
12 114 ms 117 ms 114 ms te8-3.dr10.mtl.iweb.com [67.205.127.238]
13 135 ms 100 ms 118 ms 72.55.128.44
14 116 ms 113 ms 119 ms 184.107.107.176
Trace complete.

pathping 184.107.107.176
Tracing route to 184.107.107.176 over a maximum of 30 hops
0
1
2
3 71.22.6.161
4 * * *
Computing statistics for 75 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0
0/ 100 = 0% |
1 1ms 0/ 100 = 0% 0/ 100 = 0%
0/ 100 = 0% |
2 82ms 0/ 100 = 0% 0/ 100 = 0%
0/ 100 = 0% |
3 84ms 0/ 100 = 0% 0/ 100 = 0% 71.22.6.161
Trace complete.

[Xruptor]

EDITED POST

Apparently it turns out that 84.107.107.176 is the WRONG IP.

Please see the following post further down in this thread for more details:

http://forum.square-enix.com/ffxiv/t...=1#post2180490