Servers offline?
Was just hanging out in my room when all of a sudden, puff, connection lost.
Tried to login again, servers, Unknown... Site pso2.jp also not showing up... Really weird.
Tried with internet over at work, and also not working...
Anyone else having the same issue?
"The only thing necessary for lost data to prevail, is for good men to share nothing."
Alucard, Internet Bible 03:20:1997
The site is up, and the servers apparently too, pso2es is up too.Originally Posted by MDashK
Were you using VPN at home?
No, always used direct-connection from my ISP to the game.
What's weird is that both ISP are not opening the pso2.jp website...
Was just connecting fine this morning, had no trouble doing the TD3.
"The only thing necessary for lost data to prevail, is for good men to share nothing."
Alucard, Internet Bible 03:20:1997
Probably unrelated but digital ocean (san francisco) started having issues around last week. So probably routes propagating or sega breaking stuff
run a tracecert to pso2.jp
Sizustar Fo/Te 75/75 - Ship-2
Screenshot dump
url]https://www.flickr.com/photos/118177547@N08/[/url]
Drawing and junk Twitter https://twitter.com/Sizustar - please don't send blank request-
Just did:
But what's the difference, I don't have the results of when it was working to compare them...
Tracing route to pso2.jp [210.189.209.8]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 192.168.0.1
2 17 ms 10 ms 8 ms 10.3.0.1
3 17 ms 14 ms 14 ms pa1-**-**-*-*.netvisao.pt [**.**.*.*]
4 18 ms 14 ms 15 ms pa1-**-**-*-***.netvisao.pt [**.**.*.***]
5 20 ms 18 ms 17 ms ***-**-***-***.static.net.novis.pt [***.**.***.***]
6 32 ms 32 ms 32 ms ***-**-**-***.net.novis.pt [***.**.**.***]
7 31 ms 36 ms 32 ms ***-**-**-***.net.novis.pt [***.**.**.***]
8 63 ms 54 ms 62 ms ***.***.*.***
9 317 ms 307 ms 310 ms tyo-sa3-i.TYO.JP.NET.DTAG.DE [62.154.5.210]
10 299 ms 300 ms 300 ms as4725.ix.jpix.ad.jp [210.171.224.48]
11 300 ms 299 ms 302 ms STOrc-02Te0-4-0-1.nw.odn.ad.jp [143.90.149.49]
12 301 ms 299 ms 298 ms STOrs-01Te0-0-0-3.nw.odn.ad.jp [143.90.47.42]
13 315 ms 311 ms 313 ms 230.210252167.odn.ne.jp [210.252.167.230]
14 * * * Request timed out.
15 295 ms 295 ms 295 ms softbank221111068022.bbtec.net [221.111.68.22]
16 298 ms 297 ms 297 ms 203.141.47.218
17 310 ms 312 ms 308 ms ae1.tnhcr02.idc.jp [158.205.134.10]
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 313 ms 317 ms 312 ms 158.205.188.253
22 304 ms 299 ms 299 ms lag3.l303.ta1.eg.idc.jp [158.205.188.250]
23 * 302 ms 308 ms 158.205.104.60
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.
@Rupikachu: In Europe.
"The only thing necessary for lost data to prevail, is for good men to share nothing."
Alucard, Internet Bible 03:20:1997
Tried rebooting your PC?
Sizustar Fo/Te 75/75 - Ship-2
Screenshot dump
url]https://www.flickr.com/photos/118177547@N08/[/url]
Drawing and junk Twitter https://twitter.com/Sizustar - please don't send blank request-
Yes, I did...
Hmm... Now that I look closely to the trace.... It seems some of the points changed since the last time I had my connections down due to the DDoS...
Weird... Why did the "way" change?
Just tested the servers with my AWS account, they show up fine...
Also... Somehow, it seems everything occured right at midnight JST....
It seems I am able to reach: 158.205.104.60... But why can't I do the final step and reach 210.189.209.8?
My IP address also didn't change... I guess I'll just have to wait it out some time and see what happens... This is really weird...
Last edited by MDashK; Jul 25, 2014 at 10:46 AM.
"The only thing necessary for lost data to prevail, is for good men to share nothing."
Alucard, Internet Bible 03:20:1997
I was just taking it as an example, that it's not just an on/off thing. Anyway looking at the route, it looks that you can get thru idcf which is the provider sega uses. Can you try another computer/phone on your network? (to discard it being related to the machine you're using). It kinda looks like an ip ban, which is weird.
Posting Permissions
Reply With Quote
Connect With Us