Keep Geeting 90k Error and Unable to connect to server Error for the past week.

[Shinjisake]

Here are todays results of the trace route.


Tracing route to 204.2.229.97 over a maximum of 30 hops

1 1 ms 1 ms 2 ms 192.168.0.1
2 19 ms 11 ms 10 ms 142.254.153.249
3 173 ms 30 ms 30 ms gig4-2.instoh1-rtr1.insight.rr.com [65.24.192.205]
4 76 ms 26 ms 21 ms agg9.wachoh0402h.midwest.rr.com [65.189.106.146]
5 27 ms 23 ms 29 ms be57.clmcohib01r.midwest.rr.com [24.33.161.80]
6 35 ms 31 ms 29 ms be27.clevohek01r.midwest.rr.com [65.29.1.38]
7 36 ms 37 ms 46 ms bu-ether17.vinnva0510w-bcr00.tbone.rr.com [66.109.6.70]
8 44 ms 40 ms 43 ms bu-ether11.asbnva1611w-bcr00.tbone.rr.com [66.109.6.30]
9 36 ms 36 ms 36 ms 0.ae2.pr1.dca10.tbone.rr.com [107.14.17.204]
10 37 ms 37 ms 37 ms ix-ae-17-0.tcore2.aeq-ashburn.as6453.net [216.6.87.149]
11 36 ms 36 ms 36 ms if-ae-2-2.tcore1.aeq-ashburn.as6453.net [216.6.87.2]
12 39 ms 36 ms 36 ms 66.198.154.71
13 39 ms 36 ms 37 ms ae-8.r23.asbnva02.us.bb.gin.ntt.net [129.250.2.23]
14 101 ms 101 ms 101 ms ae-10.r22.snjsca04.us.bb.gin.ntt.net [129.250.6.237]
15 104 ms 105 ms 104 ms ae-40.r02.snjsca04.us.bb.gin.ntt.net [129.250.3.121]
16 105 ms 104 ms 104 ms ae-3.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.11]
17 105 ms 107 ms 107 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129.250.195.46]
18 * 104 ms 105 ms 204.2.229.234
19 105 ms 104 ms 104 ms 204.2.229.97


Tracing route to 204.2.229.97 over a maximum of 30 hops

1 1 ms 1 ms 2 ms 192.168.0.1
2 10 ms 9 ms 10 ms 142.254.153.249
3 24 ms 21 ms 31 ms gig4-2.instoh1-rtr1.insight.rr.com [65.24.192.205]
4 21 ms 28 ms 30 ms agg9.wachoh0402h.midwest.rr.com [65.189.106.146]
5 25 ms 30 ms 29 ms be57.clmcohib01r.midwest.rr.com [24.33.161.80]
6 36 ms 28 ms 30 ms be27.clevohek01r.midwest.rr.com [65.29.1.38]
7 38 ms 37 ms 37 ms bu-ether17.vinnva0510w-bcr00.tbone.rr.com [66.109.6.70]
8 41 ms 38 ms 38 ms bu-ether11.asbnva1611w-bcr00.tbone.rr.com [66.109.6.30]
9 38 ms 37 ms 36 ms 0.ae2.pr1.dca10.tbone.rr.com [107.14.17.204]
10 38 ms 43 ms 36 ms ix-ae-17-0.tcore2.aeq-ashburn.as6453.net [216.6.87.149]
11 38 ms 36 ms 36 ms if-ae-2-2.tcore1.aeq-ashburn.as6453.net [216.6.87.2]
12 37 ms 36 ms 36 ms 66.198.154.71
13 41 ms 38 ms 37 ms ae-8.r23.asbnva02.us.bb.gin.ntt.net [129.250.2.23]
14 101 ms 101 ms 102 ms ae-10.r22.snjsca04.us.bb.gin.ntt.net [129.250.6.237]
15 105 ms 105 ms 105 ms ae-40.r02.snjsca04.us.bb.gin.ntt.net [129.250.3.121]
16 104 ms 105 ms 139 ms ae-3.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.11]
17 105 ms 146 ms 104 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129.250.195.46]
18 106 ms 105 ms 105 ms 204.2.229.234
19 106 ms 105 ms 105 ms 204.2.229.97


Tracing route to 204.2.229.97 over a maximum of 30 hops

1 2 ms 1 ms 1 ms 192.168.0.1
2 9 ms 10 ms 8 ms 142.254.153.249
3 23 ms 30 ms 30 ms gig4-2.instoh1-rtr1.insight.rr.com [65.24.192.205]
4 31 ms 29 ms 30 ms agg9.wachoh0402h.midwest.rr.com [65.189.106.146]
5 28 ms 30 ms 29 ms be57.clmcohib01r.midwest.rr.com [24.33.161.80]
6 43 ms 30 ms 29 ms be27.clevohek01r.midwest.rr.com [65.29.1.38]
7 40 ms 37 ms 38 ms bu-ether17.vinnva0510w-bcr00.tbone.rr.com [66.109.6.70]
8 145 ms 43 ms 154 ms bu-ether11.asbnva1611w-bcr00.tbone.rr.com [66.109.6.30]
9 207 ms 37 ms 122 ms 0.ae2.pr1.dca10.tbone.rr.com [107.14.17.204]
10 178 ms 36 ms 124 ms ix-ae-17-0.tcore2.aeq-ashburn.as6453.net [216.6.87.149]
11 71 ms 36 ms 36 ms if-ae-2-2.tcore1.aeq-ashburn.as6453.net [216.6.87.2]
12 36 ms 36 ms 37 ms 66.198.154.71
13 38 ms 39 ms 40 ms ae-8.r23.asbnva02.us.bb.gin.ntt.net [129.250.2.23]
14 101 ms 101 ms 104 ms ae-10.r22.snjsca04.us.bb.gin.ntt.net [129.250.6.237]
15 105 ms 108 ms 108 ms ae-40.r02.snjsca04.us.bb.gin.ntt.net [129.250.3.121]
16 105 ms 104 ms 106 ms ae-3.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.11]
17 105 ms 104 ms 105 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129.250.195.46]
18 * 107 ms * 204.2.229.234
19 105 ms 104 ms 104 ms 204.2.229.97


Tracing route to 204.2.229.97 over a maximum of 30 hops

1 1 ms 1 ms 1 ms 192.168.0.1
2 13 ms 12 ms 9 ms 142.254.153.249
3 26 ms 32 ms 28 ms gig4-2.instoh1-rtr1.insight.rr.com [65.24.192.205]
4 25 ms 30 ms 29 ms agg9.wachoh0402h.midwest.rr.com [65.189.106.146]
5 31 ms 30 ms 29 ms be57.clmcohib01r.midwest.rr.com [24.33.161.80]
6 37 ms 36 ms 30 ms be27.clevohek01r.midwest.rr.com [65.29.1.38]
7 41 ms 37 ms 37 ms bu-ether17.vinnva0510w-bcr00.tbone.rr.com [66.109.6.70]
8 47 ms 37 ms 37 ms bu-ether11.asbnva1611w-bcr00.tbone.rr.com [66.109.6.30]
9 36 ms 36 ms 64 ms 0.ae2.pr1.dca10.tbone.rr.com [107.14.17.204]
10 37 ms 36 ms 36 ms ix-ae-17-0.tcore2.aeq-ashburn.as6453.net [216.6.87.149]
11 36 ms 37 ms 36 ms if-ae-2-2.tcore1.aeq-ashburn.as6453.net [216.6.87.2]
12 38 ms 39 ms 36 ms 66.198.154.71
13 40 ms 47 ms 36 ms ae-8.r23.asbnva02.us.bb.gin.ntt.net [129.250.2.23]
14 101 ms 102 ms * ae-10.r22.snjsca04.us.bb.gin.ntt.net [129.250.6.237]
15 107 ms 106 ms 104 ms ae-40.r02.snjsca04.us.bb.gin.ntt.net [129.250.3.121]
16 105 ms 104 ms 106 ms ae-3.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.11]
17 105 ms 105 ms 106 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129.250.195.46]
18 * 105 ms * 204.2.229.234
19 104 ms 105 ms 105 ms 204.2.229.97

[Kerwin]

Here are todays results of the trace route.

14 101 ms 101 ms 101 ms ae-10.r22.snjsca04.us.bb.gin.ntt.net [129.250.6.237]
15 104 ms 105 ms 104 ms ae-40.r02.snjsca04.us.bb.gin.ntt.net [129.250.3.121]
16 105 ms 104 ms 104 ms ae-3.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.11]
17 105 ms 107 ms 107 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129.250.195.46]

14 101 ms 101 ms 102 ms ae-10.r22.snjsca04.us.bb.gin.ntt.net [129.250.6.237]
15 105 ms 105 ms 105 ms ae-40.r02.snjsca04.us.bb.gin.ntt.net [129.250.3.121]
16 104 ms 105 ms 139 ms ae-3.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.11]
17 105 ms 146 ms 104 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129.250.195.46]

14 101 ms 101 ms 104 ms ae-10.r22.snjsca04.us.bb.gin.ntt.net [129.250.6.237]
15 105 ms 108 ms 108 ms ae-40.r02.snjsca04.us.bb.gin.ntt.net [129.250.3.121]
16 105 ms 104 ms 106 ms ae-3.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.11]
17 105 ms 104 ms 105 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129.250.195.46]

14 101 ms 102 ms * ae-10.r22.snjsca04.us.bb.gin.ntt.net [129.250.6.237]
15 107 ms 106 ms 104 ms ae-40.r02.snjsca04.us.bb.gin.ntt.net [129.250.3.121]
16 105 ms 104 ms 106 ms ae-3.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.11]
17 105 ms 105 ms 106 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129.250.195.46]

Yep. That seems accurate. You are hitting the same NTT nodes that have been responsible for causing Square Enix's customer's problems for almost a year now.

Moderators will tell you to contact your ISP and dismiss your ticket.

But this issue is on Square Enix's side. Nothing you can do about it sadly.