PDA

View Full Version : Able to access again



bhaal
Jul 8, 2014, 09:06 PM
10 minutes before maint started i was able to log again to ship03, logging from Mexico using Telmex ISP, and there is a tracert:
1 28 ms 89 ms 98 ms *.*.*.*
2 22 ms 22 ms 21 ms dsl-servicio-l200.uninet.net.mx [200.38.193.226]
3 57 ms 53 ms 56 ms 189.246.220.30
4 52 ms 52 ms 51 ms xe-3-1-1.ar3.dal1.gblx.net [64.214.175.241]
5 97 ms 96 ms 97 ms po6-20G.ar2.PAO2.gblx.net [67.16.131.222]
6 99 ms 106 ms 106 ms 124.215.192.113
7 96 ms 95 ms 123 ms pajbb002.int-gw.kddi.ne.jp [111.87.3.29]
8 221 ms 198 ms 198 ms otejbb206.int-gw.kddi.ne.jp [203.181.100.177]
9 198 ms 198 ms 198 ms cm-ote257.int-gw.kddi.ne.jp [118.155.197.180]
10 202 ms 203 ms 202 ms 125.29.25.94
11 197 ms 197 ms 197 ms 203.141.47.218
12 198 ms 198 ms 198 ms ae1.tnhcr02.idc.jp [158.205.134.10]
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 203 ms 204 ms 204 ms 158.205.188.253
17 216 ms 206 ms 216 ms lag3.l303.ta1.eg.idc.jp [158.205.188.250]
18 201 ms 200 ms 200 ms 158.205.104.60
19 204 ms 204 ms 204 ms 210.189.209.8
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

MegaRocker1987
Jul 8, 2014, 09:08 PM
10 minutes before maint started i was able to log again to ship03, logging from Mexico using Telmex ISP, and there is a tracert:
1 28 ms 89 ms 98 ms *.*.*.*
2 22 ms 22 ms 21 ms dsl-servicio-l200.uninet.net.mx [200.38.193.226]
3 57 ms 53 ms 56 ms 189.246.220.30
4 52 ms 52 ms 51 ms xe-3-1-1.ar3.dal1.gblx.net [64.214.175.241]
5 97 ms 96 ms 97 ms po6-20G.ar2.PAO2.gblx.net [67.16.131.222]
6 99 ms 106 ms 106 ms 124.215.192.113
7 96 ms 95 ms 123 ms pajbb002.int-gw.kddi.ne.jp [111.87.3.29]
8 221 ms 198 ms 198 ms otejbb206.int-gw.kddi.ne.jp [203.181.100.177]
9 198 ms 198 ms 198 ms cm-ote257.int-gw.kddi.ne.jp [118.155.197.180]
10 202 ms 203 ms 202 ms 125.29.25.94
11 197 ms 197 ms 197 ms 203.141.47.218
12 198 ms 198 ms 198 ms ae1.tnhcr02.idc.jp [158.205.134.10]
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 203 ms 204 ms 204 ms 158.205.188.253
17 216 ms 206 ms 216 ms lag3.l303.ta1.eg.idc.jp [158.205.188.250]
18 201 ms 200 ms 200 ms 158.205.104.60
19 204 ms 204 ms 204 ms 210.189.209.8
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

good luck tomorrow if u can still connect

Kondibon
Jul 8, 2014, 09:12 PM
good luck tomorrow if u can still connect

That looks exactly like mine and I can connect.

un1t27
Jul 8, 2014, 09:12 PM
Pso2.jp site loads for me and the exe does also without any errors.

Verizon seems fine now.

Faranth
Jul 8, 2014, 09:21 PM
guess the problem was fixed for lots of ppl right before maint (〃 ̄ω ̄〃ゞ

Ash1ey
Jul 8, 2014, 09:31 PM
Verizon Fios and I am able to connect to the launcher & patch my game atm.

BahnKnakyu
Jul 8, 2014, 09:32 PM
A poster on /vg/ said another Mexican ISP can connect too, so it looks like Mexico's backbone providers found a route to Japan. Good to hear.

AlphaBlob
Jul 8, 2014, 09:33 PM
Videotron (Canada), Still unable to connect. Tracert stop at nearest big city.

bhaal
Jul 8, 2014, 09:40 PM
A poster on /vg/ said another Mexican ISP can connect too, so it looks like Mexico's backbone providers found a route to Japan. Good to hear.
was digging for info and found this:


Uninet (Telmex)
Se conecta a internet por medio de estas compaņias gringas:
1.- Verizon Bussines
2.- Ntt America
3.- Level 3 Comunications
4.- Global Crossing
5.- Tata comunications

This mean telmex/uninet (my ISP, tier 3 or at max tier 2) buy access from those tier 1 ISPs, so this must be related to other users of verizon in USA to be able to log too.

TaigaUC
Jul 8, 2014, 09:58 PM
Friend on Telmex just told me he can suddenly access the website.
He tried it several hours ago and couldn't.

Also, I contacted my ISP and they said they can't see anything, PSO2 just looks down to them.
I sent them my friend's traceroute on the same ISP that works. We'll see what happens, I guess.
It looks like certain exchanges are blocking access to pso2.jp and not returning a response.
My friend's traceroute seems to go through an exchange that mine does not.

AnnabellaRenee87
Jul 8, 2014, 10:53 PM
Still down on AT&T wireless and suddenlink communications :-(

Noc Codez
Jul 8, 2014, 11:30 PM
Viva Mexico !! Lol

bhaal
Jul 9, 2014, 02:00 PM
Back from work, still able to log, I will post now 2 new tracerts:
This was made at mid of maint:
[spoiler-box]
Tracing route to pso2.jp [210.189.209.8]
over a maximum of 30 hops:

1 101 ms 99 ms 99 ms *.*.*.*
2 24 ms 22 ms 21 ms dsl-servicio-l200.uninet.net.mx [200.38.193.226]
3 56 ms 55 ms 56 ms 189.246.220.30
4 51 ms 51 ms 52 ms xe-3-1-1.ar3.dal1.gblx.net [64.214.175.241]
5 96 ms 95 ms 96 ms po6-20G.ar2.PAO2.gblx.net [67.16.131.222]
6 101 ms 107 ms 107 ms 124.215.192.113
7 96 ms 96 ms 96 ms pajbb002.int-gw.kddi.ne.jp [111.87.3.29]
8 198 ms 196 ms 198 ms otejbb206.int-gw.kddi.ne.jp [203.181.100.177]
9 197 ms 197 ms 196 ms cm-ote257.int-gw.kddi.ne.jp [118.155.197.180]
10 204 ms 202 ms 202 ms 125.29.25.94
11 198 ms 197 ms 197 ms 203.141.47.218
12 198 ms 197 ms 197 ms ae1.tnhcr02.idc.jp [158.205.134.10]
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 204 ms 205 ms 204 ms 158.205.188.253
17 210 ms 207 ms 215 ms lag3.l303.ta1.eg.idc.jp [158.205.188.250]
18 212 ms 206 ms 271 ms 158.205.104.60
19 206 ms 203 ms 203 ms 210.189.209.8
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.
[/spoiler-box]

This one was made as i was making this post:
[spoiler-box]
Tracing route to pso2.jp [210.189.209.8]
over a maximum of 30 hops:

1 3 ms 99 ms 99 ms *.*.*.*
2 22 ms 20 ms 20 ms dsl-servicio-l200.uninet.net.mx [200.38.193.226]
3 57 ms 55 ms 56 ms 189.246.220.22
4 50 ms 51 ms 50 ms ge-1-2-1.ar3.dal1.gblx.net [64.210.12.77]
5 94 ms 93 ms 94 ms po6-20G.ar2.PAO2.gblx.net [67.16.131.222]
6 100 ms 93 ms 103 ms 124.215.192.113
7 96 ms 96 ms 96 ms pajbb001.kddnet.ad.jp [124.211.34.125]
8 187 ms 203 ms 186 ms otejbb205.int-gw.kddi.ne.jp [203.181.100.1]
9 187 ms 187 ms 187 ms cm-ote257.int-gw.kddi.ne.jp [118.155.197.52]
10 195 ms 195 ms 196 ms 125.29.25.94
11 193 ms 193 ms 193 ms 203.141.47.218
12 197 ms 196 ms 197 ms ae1.tnhcr02.idc.jp [158.205.134.10]
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 194 ms 194 ms 193 ms 158.205.188.253
17 194 ms 195 ms 200 ms lag3.l303.ta1.eg.idc.jp [158.205.188.250]
18 187 ms * 189 ms 158.205.104.60
19 184 ms 184 ms 184 ms 210.189.209.8
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.
[/spoiler-box]
And for compare, a tracert from the days I was unable to log (July 02 to July 08 )

[spoiler-box]
Tracing route to pso2.jp [210.189.209.8]
over a maximum of 30 hops:

1 46 ms 99 ms 99 ms *.*.*.*
2 180 ms 146 ms 154 ms dsl-servicio-l200.uninet.net.mx [200.38.193.226]
3 186 ms 191 ms 183 ms bb-dallas-bryan-10-tge0-14-0-6.uninet.net.mx [201.125.112.170]
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
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 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.
[/spoiler-box]

unfortunately I don't have any tracert from the day the DDoS ended to maint in July 01 (last day I was able to log normaly, but as you can see, the moment " bb-dallas-bryan-10-tge0-14-0-6.uninet.net.mx [201.125.112.170] " was removed from my route all the problems magically fixed, so I think if any of you are still not able to log is time to increase the pressure over yours ISPs until they fix this in their end.

ArataWata
Jul 9, 2014, 02:01 PM
B-b-but... IP Ban doe

Sega racist doe.

ShinMaruku
Jul 9, 2014, 02:07 PM
There was never a IP ban. But the reactions and the tears are glorious.

Chidori
Jul 9, 2014, 02:13 PM
nice :)

Revenya
Jul 9, 2014, 02:13 PM
/hopesforXfinitytoworkeventually

Stealthcmc1974
Jul 9, 2014, 02:31 PM
/hopesforXfinitytoworkeventually

I'm in the same boat pal. There are alternatives if you don't feel like waiting (Although I don't reccommend those public VPNs).

SquashDemon
Jul 9, 2014, 02:51 PM
Centurylink...y u no...

Lumpen Thingy
Jul 9, 2014, 03:12 PM
There was never a IP ban. But the reactions and the tears are glorious.

I know right? :D

Skize
Jul 9, 2014, 07:37 PM
There was never a IP ban. But the reactions and the tears are glorious.

So sadistic!

TsukasaHiiragi
Jul 9, 2014, 07:45 PM
Best thing to do for us peeps currently without access is to keep on bugging your ISP - I plan on contacting comcast again tomorrow - and the day after - and the day after that lol

MDashK
Jul 10, 2014, 11:43 AM
Just to let everyone know that I too can connect from home again.
At least, I can access the website.
Going to try the servers now.

I guess the ISPs are getting back to normal.

bhaal
Jul 29, 2014, 02:02 PM
A little follow up:
Until 2 days ago (sunday, 27-07-14) I was able to log fine, then next day (28-07) in the afternoon I was unable to log again, but since I was busy with work, I had no time to check what was going on, now today, still unable to log or enter pso2.jp, I got this in multiple tracerts :

Tracing route to pso2.jp [210.189.209.8]
over a maximum of 30 hops:

1 49 ms 99 ms 99 ms *.*.*.*
2 174 ms 53 ms 113 ms dsl-servicio-l200.uninet.net.mx [200.38.193.226]
3 229 ms 201 ms 141 ms 189.246.222.90
4 204 ms 119 ms 119 ms xe10-1-1-10G.ar7.dal2.gblx.net [208.48.239.13]
5 262 ms 172 ms 171 ms te4-1-10G.ar2.PAO2.gblx.net [67.16.131.194]
6 205 ms 182 ms 228 ms 124.215.192.113
7 190 ms 179 ms 205 ms pajbb001.int-gw.kddi.ne.jp [111.87.3.5]
8 298 ms 349 ms 329 ms otejbb205.int-gw.kddi.ne.jp [203.181.100.173]
9 271 ms 339 ms 302 ms cm-ote257.int-gw.kddi.ne.jp [118.155.197.52]
10 348 ms 360 ms 377 ms 125.29.25.94
11 234 ms 230 ms 354 ms 203.141.47.218
12 363 ms 224 ms 367 ms ae1.tnhcr02.idc.jp [158.205.134.10]
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 236 ms 241 ms 328 ms 158.205.188.253
17 388 ms 384 ms 249 ms lag3.l303.ta1.eg.idc.jp [158.205.188.250]
18 398 ms 237 ms 246 ms 158.205.104.60
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

Thats is, connection is lost 1 jump before connecting to pso2.jp in what is like Yahoo Jp (http://www.ip-tracker.org/locator/ip-lookup.php?ip=158.205.104.60) server, lets see what this new development in the "I canīt connect" drama result.

solid_snark
Jul 30, 2014, 01:22 PM
Verizon Wireless connects to the main web page and players site fine now. Comcast is ... well, it's still Comcastic.

Zyrusticae
Jul 30, 2014, 01:24 PM
AT&T U-verse here, still no go.

Fortunately I have WTFast to get around that, but yeah. Inconvenient.

Chigun
Jul 30, 2014, 02:23 PM
I had access that I noticed randomly for two days (on Verizon MiFi - A Satellite Internet). Then it went away again. What?

Back to VPN world I go.

HeyItsTHK
Jul 30, 2014, 02:30 PM
South Florida AT&T U-verse, no go.

obsexed
Jul 30, 2014, 05:57 PM
fuk it brb switching to telmex

pkemr4
Jul 30, 2014, 06:18 PM
currently at a hotel in Pennsylvania using AT&T wifi and couldnt connect.

bhaal
Jul 30, 2014, 06:24 PM
fuk it brb switching to telmex

Sadly, Iīm with telmex, but now things look like they are working again.
New tracert:


Tracing route to pso2.jp [210.189.209.8]
over a maximum of 30 hops:

1 39 ms 85 ms 99 ms *.*.*.*
2 30 ms 25 ms 23 ms dsl-servicio-l200.uninet.net.mx [200.38.193.226]
3 60 ms 55 ms 55 ms bb-dallas-stemmons-5-tge0-7-0-13.uninet.net.mx [189.246.222.74]
4 51 ms 52 ms 51 ms xe10-1-1-10G.ar7.dal2.gblx.net [208.48.239.13]
5 95 ms 96 ms 93 ms te4-1-10G.ar2.PAO2.gblx.net [67.16.131.194]
6 98 ms 90 ms 89 ms 124.215.192.113
7 85 ms 86 ms 86 ms pajbb002.kddnet.ad.jp [124.211.34.133]
8 192 ms 194 ms 198 ms otejbb206.int-gw.kddi.ne.jp [203.181.100.209]
9 183 ms 181 ms 179 ms cm-ote257.int-gw.kddi.ne.jp [118.155.197.52]
10 196 ms 186 ms 185 ms 125.29.25.94
11 187 ms 187 ms 187 ms 203.141.47.218
12 183 ms 183 ms 183 ms ae1.tnhcr02.idc.jp [158.205.134.10]
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 191 ms 192 ms 191 ms 158.205.188.253
17 201 ms 200 ms 198 ms lag3.l303.ta1.eg.idc.jp [158.205.188.250]
18 184 ms 184 ms 186 ms 158.205.104.60
19 206 ms 192 ms 192 ms 210.189.209.8
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

obsexed
Jul 30, 2014, 06:35 PM
i have cablecom(metrored) and still can't connect, been able to connect on my sisters house she has cablevision .-. i'm so unlucky

reaper527
Jul 31, 2014, 01:35 PM
i have cablecom(metrored) and still can't connect, been able to connect on my sisters house she has cablevision .-. i'm so unlucky

you could ask her to run a vpn server for you from her machine using openvpn.

Daiyousei
Jul 31, 2014, 01:46 PM
i have cablecom(metrored) and still can't connect, been able to connect on my sisters house she has cablevision .-. i'm so unlucky

So some cablevision can connect then.

Chdata
Jul 31, 2014, 02:49 PM
107

comcast

bhaal
Jul 31, 2014, 03:14 PM
And today I canīt connect again, is like someone is toying with the paths to reach pso2 servers:


Tracing route to pso2.jp [210.189.209.8]
over a maximum of 30 hops:

1 60 ms 99 ms 99 ms *.*.*.*
2 26 ms 24 ms 26 ms dsl-servicio-l200.uninet.net.mx [200.38.193.226]
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
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 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

obsexed
Jul 31, 2014, 03:42 PM
So some cablevision can connect then.

the mexican cablevision, dunno if you're talking about the one in the U.S

DamonKatu
Jul 31, 2014, 05:34 PM
Tracing route to pso2.jp [210.189.209.8]
over a maximum of 30 hops:

1 <1 ms <1 ms 1 ms 192.168.1.1
2 54 ms 59 ms 72 ms 10.123.0.1
3 61 ms 50 ms 51 ms 24.144.1.89
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
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 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

At least Its a SLIGHT improvement....

bhaal
Jul 31, 2014, 06:00 PM
I don't know whats going on or who is toying with us, new tracert:


Tracing route to pso2.jp [210.189.209.8]
over a maximum of 30 hops:

1 27 ms 94 ms 99 ms *.*.*.*
2 25 ms 24 ms 24 ms dsl-servicio-l200.uninet.net.mx [200.38.193.226]
3 54 ms 55 ms 61 ms bb-dallas-stemmons-5-tge0-7-0-8.uninet.net.mx [189.246.222.86]
4 51 ms 51 ms 51 ms xe10-1-1-10G.ar7.dal2.gblx.net [208.48.239.13]
5 95 ms 95 ms 94 ms te4-1-10G.ar2.PAO2.gblx.net [67.16.131.194]
6 92 ms 90 ms 89 ms 124.215.192.113
7 111 ms 88 ms 91 ms pajbb001.int-gw.kddi.ne.jp [111.87.3.5]
8 192 ms 204 ms 180 ms otejbb205.int-gw.kddi.ne.jp [203.181.100.133]
9 187 ms 197 ms 237 ms cm-ote257.int-gw.kddi.ne.jp [118.155.197.52]
10 352 ms 185 ms 184 ms 125.29.25.94
11 194 ms 195 ms 195 ms 203.141.47.218
12 196 ms 196 ms 196 ms ae1.tnhcr02.idc.jp [158.205.134.10]
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 206 ms 200 ms * 158.205.188.253
17 193 ms 199 ms 199 ms lag3.l303.ta1.eg.idc.jp [158.205.188.250]
18 193 ms 185 ms 185 ms 158.205.104.60
19 192 ms 192 ms 192 ms 210.189.209.8
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.