POL-0011 Error.

言語: JP EN DE FR
2010-06-21
New Items
users online
フォーラム » FFXI » General » POL-0011 Error.
POL-0011 Error.
Offline
By Draylo 2020-03-27 00:00:58  
SE support is so useless. There was some weird error on their store page and they double charged me a lot of money. I sent them an email immediately and they told me its too late to cancel the order, even tho it didn't ship? So they told me to refuse it when it arrives. I tried to do that and my bldg can't because the guy signs for every package in the bldg when they come and can't look specifically for mine.

Been sending them emails for a week trying to refund this and nobody responds to me lol. It's a disaster to ever contact them.
[+]
Offline
Posts: 969
By Voren 2020-03-27 00:58:46  
I got the POL-0011 followed by 3001, and then 3100. I gave up and watched netflix
 Carbuncle.Nynja
Offline
サーバ: Carbuncle
Game: FFXI
user: NynJa
Posts: 2219
By Carbuncle.Nynja 2020-03-27 07:31:59  
If this was a problem at SE's servers, EVERYONE would have had connection issues.

People in my LS affected last night:
eastern and western canada, NE USA

unaffected in my LS:
west coast USA, south USA

Dude in NE USA used a VPN to connect from Texas and was able to connect after.

SkyFrog said: »
Trace Route before R0:
C:\>tracert -4 202.67.54.123

Tracing route to 202.67.54.123 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms RT-AC68U-3C18 [192.168.1.1]
2 1 ms <1 ms <1 ms 10.0.0.1
3 9 ms 22 ms 8 ms *.*.*.*
4 10 ms 9 ms 9 ms *.*.*.*
5 10 ms 9 ms 8 ms po-2-rur102.bellevue.wa.seattle.comcast.net [69.139.160.26]
6 11 ms 11 ms 11 ms be-103-ar01.seattle.wa.seattle.comcast.net [69.139.164.77]
7 13 ms 12 ms 9 ms be-33650-cr01.seattle.wa.ibone.comcast.net [68.86.93.165]
8 12 ms 11 ms 10 ms be-10846-pe01.seattle.wa.ibone.comcast.net [68.86.86.90]
9 11 ms 13 ms 10 ms be3014.ccr21.sea02.atlas.cogentco.com [154.54.11.229]
10 29 ms 32 ms 29 ms be3717.ccr22.sfo01.atlas.cogentco.com [154.54.86.209]
11 31 ms 28 ms 29 ms be3670.ccr41.sjc03.atlas.cogentco.com [154.54.43.14]
12 137 ms 136 ms 136 ms be3696.ccr21.tyo01.atlas.cogentco.com [154.54.86.138]
13 137 ms 147 ms 142 ms be3723.rcr51.b060372-1.tyo01.atlas.cogentco.com [154.54.87.190]
14 137 ms 135 ms 136 ms square-enix.demarc.cogentco.com [154.18.1.146]
15 116 ms 115 ms 116 ms 61.195.56.165
16 148 ms 137 ms 137 ms 219.117.144.74
17 135 ms 133 ms 133 ms 219.117.144.53
18 137 ms 135 ms 137 ms 219.117.146.141
19 138 ms 137 ms 137 ms 219.117.147.42
20 138 ms 137 ms 135 ms 202.67.54.123

Trace complete.



Trace Route after R0:

C:\>tracert -4 202.67.54.123

Tracing route to 202.67.54.123 over a maximum of 30 hops

1 <1 ms <1 ms 1 ms RT-AC68U-3C18 [192.168.1.1]
2 1 ms 1 ms 1 ms 10.0.0.1
3 8 ms 9 ms 10 ms *.*.*.*
4 10 ms 8 ms 8 ms *.*.*.*
5 9 ms 9 ms 10 ms po-2-rur102.bellevue.wa.seattle.comcast.net [69.139.160.26]
6 12 ms 11 ms 8 ms be-103-ar01.seattle.wa.seattle.comcast.net [69.139.164.77]
7 13 ms 11 ms 11 ms be-33650-cr01.seattle.wa.ibone.comcast.net [68.86.93.165]
8 12 ms 11 ms 11 ms be-10846-pe01.seattle.wa.ibone.comcast.net [68.86.86.90]
9 12 ms 12 ms 12 ms be3014.ccr21.sea02.atlas.cogentco.com [154.54.11.229]
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.

For me, it seems to be crapping out on the cogentco pipeline from Seattle to SFO.


my tracert last night looked almost the same:
my local network / ISP to ord03 to ord01 (DC) to mci01 (MMM) to den01 (denver) to slc01 (salt lake) and timed out. This morning the connection from slc01 and sfo01 seems to be restored.


8 46 ms 37 ms 33 ms 209.148.235.93
9 36 ms 34 ms 29 ms be812.ccr41.ord03.atlas.cogentco.com [154.54.9.9]
10 37 ms 33 ms 38 ms be2765.ccr41.ord01.atlas.cogentco.com [154.54.45.17]
11 54 ms 49 ms 48 ms be2831.ccr21.mci01.atlas.cogentco.com [154.54.42.165]
12 87 ms 69 ms 60 ms be3035.ccr21.den01.atlas.cogentco.com [154.54.5.89]
13 66 ms 67 ms 74 ms be3037.ccr21.slc01.atlas.cogentco.com [154.54.41.145]
---timed out after here last night)
14 92 ms 88 ms 92 ms be3109.ccr21.sfo01.atlas.cogentco.com [154.54.44.137]
15 84 ms 91 ms 86 ms be3669.ccr41.sjc03.atlas.cogentco.com [154.54.43.10]
16 191 ms 191 ms 189 ms be3696.ccr21.tyo01.atlas.cogentco.com [154.54.86.138]
17 191 ms 197 ms 197 ms be3723.rcr51.b060372-1.tyo01.atlas.cogentco.com [154.54.87.190]
18 190 ms 188 ms 195 ms square-enix.demarc.cogentco.com [154.18.1.146]
19 196 ms 188 ms 194 ms 61.195.56.165
[+]
 
Offline
Posts:
By 2020-03-27 09:12:24
 Undelete | Edit  | Link | 引用 | 返事
 
Post deleted by User.
 Bismarck.Nyaarun
Offline
サーバ: Bismarck
Game: FFXI
user: duo1666
Posts: 1006
By Bismarck.Nyaarun 2020-03-27 17:24:36  
Carbuncle.Nynja said: »
If this was a problem at SE's servers, EVERYONE would have had connection issues.

People in my LS affected last night:
eastern and western canada, NE USA

unaffected in my LS:
west coast USA, south USA

Dude in NE USA used a VPN to connect from Texas and was able to connect after.

SkyFrog said: »
Trace Route before R0:
C:\>tracert -4 202.67.54.123

Tracing route to 202.67.54.123 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms RT-AC68U-3C18 [192.168.1.1]
2 1 ms <1 ms <1 ms 10.0.0.1
3 9 ms 22 ms 8 ms *.*.*.*
4 10 ms 9 ms 9 ms *.*.*.*
5 10 ms 9 ms 8 ms po-2-rur102.bellevue.wa.seattle.comcast.net [69.139.160.26]
6 11 ms 11 ms 11 ms be-103-ar01.seattle.wa.seattle.comcast.net [69.139.164.77]
7 13 ms 12 ms 9 ms be-33650-cr01.seattle.wa.ibone.comcast.net [68.86.93.165]
8 12 ms 11 ms 10 ms be-10846-pe01.seattle.wa.ibone.comcast.net [68.86.86.90]
9 11 ms 13 ms 10 ms be3014.ccr21.sea02.atlas.cogentco.com [154.54.11.229]
10 29 ms 32 ms 29 ms be3717.ccr22.sfo01.atlas.cogentco.com [154.54.86.209]
11 31 ms 28 ms 29 ms be3670.ccr41.sjc03.atlas.cogentco.com [154.54.43.14]
12 137 ms 136 ms 136 ms be3696.ccr21.tyo01.atlas.cogentco.com [154.54.86.138]
13 137 ms 147 ms 142 ms be3723.rcr51.b060372-1.tyo01.atlas.cogentco.com [154.54.87.190]
14 137 ms 135 ms 136 ms square-enix.demarc.cogentco.com [154.18.1.146]
15 116 ms 115 ms 116 ms 61.195.56.165
16 148 ms 137 ms 137 ms 219.117.144.74
17 135 ms 133 ms 133 ms 219.117.144.53
18 137 ms 135 ms 137 ms 219.117.146.141
19 138 ms 137 ms 137 ms 219.117.147.42
20 138 ms 137 ms 135 ms 202.67.54.123

Trace complete.



Trace Route after R0:

C:\>tracert -4 202.67.54.123

Tracing route to 202.67.54.123 over a maximum of 30 hops

1 <1 ms <1 ms 1 ms RT-AC68U-3C18 [192.168.1.1]
2 1 ms 1 ms 1 ms 10.0.0.1
3 8 ms 9 ms 10 ms *.*.*.*
4 10 ms 8 ms 8 ms *.*.*.*
5 9 ms 9 ms 10 ms po-2-rur102.bellevue.wa.seattle.comcast.net [69.139.160.26]
6 12 ms 11 ms 8 ms be-103-ar01.seattle.wa.seattle.comcast.net [69.139.164.77]
7 13 ms 11 ms 11 ms be-33650-cr01.seattle.wa.ibone.comcast.net [68.86.93.165]
8 12 ms 11 ms 11 ms be-10846-pe01.seattle.wa.ibone.comcast.net [68.86.86.90]
9 12 ms 12 ms 12 ms be3014.ccr21.sea02.atlas.cogentco.com [154.54.11.229]
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.

For me, it seems to be crapping out on the cogentco pipeline from Seattle to SFO.


my tracert last night looked almost the same:
my local network / ISP to ord03 to ord01 (DC) to mci01 (MMM) to den01 (denver) to slc01 (salt lake) and timed out. This morning the connection from slc01 and sfo01 seems to be restored.


8 46 ms 37 ms 33 ms 209.148.235.93
9 36 ms 34 ms 29 ms be812.ccr41.ord03.atlas.cogentco.com [154.54.9.9]
10 37 ms 33 ms 38 ms be2765.ccr41.ord01.atlas.cogentco.com [154.54.45.17]
11 54 ms 49 ms 48 ms be2831.ccr21.mci01.atlas.cogentco.com [154.54.42.165]
12 87 ms 69 ms 60 ms be3035.ccr21.den01.atlas.cogentco.com [154.54.5.89]
13 66 ms 67 ms 74 ms be3037.ccr21.slc01.atlas.cogentco.com [154.54.41.145]
---timed out after here last night)
14 92 ms 88 ms 92 ms be3109.ccr21.sfo01.atlas.cogentco.com [154.54.44.137]
15 84 ms 91 ms 86 ms be3669.ccr41.sjc03.atlas.cogentco.com [154.54.43.10]
16 191 ms 191 ms 189 ms be3696.ccr21.tyo01.atlas.cogentco.com [154.54.86.138]
17 191 ms 197 ms 197 ms be3723.rcr51.b060372-1.tyo01.atlas.cogentco.com [154.54.87.190]
18 190 ms 188 ms 195 ms square-enix.demarc.cogentco.com [154.18.1.146]
19 196 ms 188 ms 194 ms 61.195.56.165

This. Likely something along the way was undergoing maintenance or had an issue and traffic didnt reroute immediately after, causing repeated DCs and slow connections to anything going through that route. Not all that surprising given places are likely understaffed due to corona threat, so response to problems might not be immediate.
Log in to post.