The Server Situation Analysis Thread

[TauAkiou]

I've been quiet for awhile, but that's because I've been continuously analyzing what has been going on with the servers, and because I think we need a dedicated thread to keep our analysis of the situation going.

I will also keep a running list of the working ISPs here, so that people can more easily tell at a glance what the hell is going on, and if they will be able to connect without a VPN.

Reference Threads:
[spoiler-box]
http://www.dslreports.com/forum/r29372477-Phantasy-Star-Online-2-pso2.jp-and-ISP-based-cannot-connect

http://www.dslreports.com/forum/r29370409-Dslextreme-blocking-access-to-phantasy-star-online-2

http://www.dslreports.com/forum/r29370564-ISP-level-block-of-Phantasy-Star-Online-2-servers-
[/spoiler-box]

Connectable ISPs: (Last Updated: 18/7/2014)
[spoiler-box]
Verizon (US)
Time Warner Cable (US)
Hurricane Electric (US)
SFR (France)
Laposte (France)
Virginbox (France)
[/spoiler-box]

If you have another ISP that works, send me a PM with your ENTIRE traceroute from start to finish. You will know your traceroute has succeeded if the last hop (before timeouts) is the IP of the server or website. Use the list below to determine the hostname and IP you are looking for.

You can remove the first two or three hops from your traceroute if you wish.

Server hostname/IP List:
[spoiler-box]Ship 1: gs001.pso2gs.net [210.189.208.1]
Ship 2: gs016.pso2gs.net [210.189.208.16]
Ship 3: gs031.pso2gs.net [210.189.208.31]
Ship 4: gs046.pso2gs.net [210.189.208.46]
Ship 5: gs061.pso2gs.net [210.189.208.61]
Ship 6: gs076.pso2gs.net [210.189.208.76]
Ship 7: gs091.pso2gs.net [210.189.208.91]
Ship 8: gs106.pso2gs.net [210.189.208.106]
Ship 9: gs121.pso2gs.net [210.189.208.121]
Ship 10: gs136.pso2gs.net [210.189.208.136]
pso2.jp: [210.189.209.8]
[/spoiler-box]

Additionally, If you have a good thread you think I should analyze and consider adding, please PM me the link and I will take a look at it.

----

What has been going on? It's difficult to say right now.

I will start by addressing what kind of block it isn't, since this continues to be a point of contention throughout the community.

IP Block: NO

If this was an IP block, no foreign IPs would be able to make a connection. However, foreign IPs can make a connection. Discussion over. Don't call it an IP block.

----

As for what exactly seems to be happening, it seems as though Yahoo.jp did something to our normal operating route. As a direct result, the route has been doing some extremely strange shit, including creating and breaking paths between certain hosts rather frequently, and generally not propagating beyond networks too far from the host.

Something to note: This is not isolated to the PSO2 servers. This is effecting ALL IP addresses in the range, exactly 512 in total. (210.189.208.0 to 210.189.209.255).

I highly doubt SEGA owns 512 IP addresses.

Technically speaking, this is because Yahoo.jp started announcing these 512 (prefix /23 for those of you technically minded) addresses into two separate 256 address blocks (prefix /25), thus announcing their network in a form that most ISPs won't accept. (One of the DSLReports threads has more information on this).

The /23 range still exists and is still being updated, but from what I can tell, the existence of the /25 and the fact that the IP seems to report as being contained within it is causing most of our ISPs to ignore the route. The end result is a route that exists and IS being announced, but is being ignored intentionally, save for the hosts that will willingly go through the /25, or those of them that are only aware of the /23 (such as Hurricane Electric).

The only definitive conclusion I can give right now is that whoever manages the Yahoo.jp backbone is completely incompetent.

----

What we can hope for:

* That Yahoo.ip gets their head out of their ass and stops announcing the /25s, which should cause all traffic to get routed through the /23 again, fixing the problem.

* That SEGA changes ISP to one that knows what the fuck they are doing, such as the one running their corporate website. (Amazon)

* That our ISPs eventually become aware of the /23 on their own and start routing through it rather then the /25.

* That someone else running on one of those IPs complains that foreign clients can't connect to his network anymore and calls them out on their incompetence.

----

More information can be found by looking at the DSLReports reference threads linked in the spoiler box. This thread will be updated as more information becomes available.

I would like this thread to remain free from bickering, general negativity, and trolling if possible.

[TauAkiou]

Post reserved for any additional or important information that might not need to be part of the primary post.

[Urbancowgurl777]

Question then... Is it completely possible that Sega continues using Yahoo.jp and that Yahoo.jp never changes back to /23 (or whatever)? Also, what is the possibility of our ISPs eventually becoming aware of /23?

[TauAkiou]

Question then... Is it completely possible that Sega continues using Yahoo.jp and that Yahoo.jp never changes back to /23 (or whatever)? Also, what is the possibility of our ISPs eventually becoming aware of /23?

It is entirely possible that SEGA might never change ISPs, and it is also entirely possible that Yahoo.jp might never change this setup. We can't really control anything that's going on over there, and unless someone over there points this out or complains hard enough, it could never happen.

There is, of course, always the possibility that the PSO2 servers might undergo another IP change, preferably into a range that isn't being managed by a bunch of idiots, but we can't rely on that.

As for becoming aware of /23, I have no idea. It depends on what the individual ISP happens to do. Like the others, it could never happen and is one of those things that is entirely relegated to the domain of luck.

[DamonKatu]

Wow, It has been FOUR YEARS since I actually posted anything on here. But back on subject...

Thanks to social trends like Twitter and tumbler, one can EASILY spread this like wild fire IF done correctly. I'll see if if I can get this retweated, reported, and spread. Not sure if that helps, but, at least we all can get EVERYONE to at least notice this bu sharing this...

Anyways--POOF!! Gone again!

[TauAkiou]

Wow, It has been FOUR YEARS since I actually posted anything on here. But back on subject...

Thanks to social trends like Twitter and tumbler, one can EASILY spread this like wild fire IF done correctly. I'll see if if I can get this retweated, reported, and spread. Not sure if that helps, but, at least we all can get EVERYONE to at least notice this bu sharing this...

Anyways--POOF!! Gone again!

You could, but honestly releasing a bunch of technical information like that will only serve to confuse more people, since not many people really understand the actual, underlying nature of the internet. (I don't even entirely understand what's going on; I've learned enough, however, to understand, more or less, what's going on here, and now.)

We'd be better off trying to ask our ISPs to see if they can route us through the /23, because none of them are ever going to know the /25 exists.

[Poyonche]

Idk how to PM so i post everything here, the ISP is SFR France (ISP using its network must be able to log in [Laposte Mobile, Virgin Box]

EDIT : Im using Wifi connection of a friend neighbour, my ISP is Free, request time out when i reach Step 5

[Cyber Meteor]

@Poyonche I also have SFR France as my ISP and I can't log in or access the main site. Any idea why?:-? Here are the tracert, it stops just before the last needed step.

[SPOILER-BOX]http://i1318.photobucket.com/albums/t650/CyberMeteor/Login%20IP%20ban%20test/Pso2tracert1_zpscf5d94f5.png~original[/SPOILER-BOX]

[SPOILER-BOX]http://i1318.photobucket.com/albums/t650/CyberMeteor/Login%20IP%20ban%20test/Pso2tracert2_zps25a164fa.png~original[/SPOILER-BOX]

[Cypher_9]

* That our ISPs eventually become aware of the /23 on their own and start routing through it rather then the /25.


I will try this when I call back to them - granted the minutes on my phone - cause Comcast is still oblivious to what is going on when I last called about such. They said that they too weren't able to connect to it so that's a plus when i last called. Only suggested to get the reverse trace from pso2.jp but if its solely yahoo.jp then it should be easier for them to... correct it?

[tuxdude143]

I'm on telecom New Zealand (in new zealand) and I can connect to pso2 just fine.

[Ezodagrom]

@Poyonche I also have SFR France as my ISP and I can't log in or access the main site. Any idea why?:-? Here are the tracert, it stops just before the last needed step.

[spoiler-box]http://i1318.photobucket.com/albums/t650/CyberMeteor/Login%20IP%20ban%20test/Pso2tracert1_zpscf5d94f5.png~original[/spoiler-box]

[spoiler-box]http://i1318.photobucket.com/albums/t650/CyberMeteor/Login%20IP%20ban%20test/Pso2tracert2_zps25a164fa.png~original[/spoiler-box]
I'm in a similar situation, tracert stops before the last needed step.
I live in Portugal, ISP is Cabovisão.

[spoiler-box]http://i.imgur.com/tco1VUZ.jpg[/spoiler-box]

[Cyber Meteor]

@Ezodagrom The thing I don't understand is that people having exactely the same ISP than me can log into the game and access the main site just fine while I can't.

[Miyuki_Kamiko]

@Ezodagrom The thing I don't understand is that people having exactely the same ISP than me can log into the game and access the main site just fine while I can't.

ill say it's either there lying about not using some software to get them on the site/game
or there lying about being able to access it

these forums are full of trolls which like to give people false hope you should take almost everything said with a grain of salt

[Scarlet-Star]

ill say it's either there lying about not using some software to get them on the site/game
or there lying about being able to access it

these forums are full of trolls which like to give people false hope you should take almost everything said with a grain of salt

Exactly, that being said: I am a man.

[Aussei]

Stiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiii iiiiiiiiiiiiiiiiiiiiill think this is SEGA's way of locking us out

[Searaphim]

The fact that SEGA switched to /25 after the DDOS could mean that they or yahoo.jp were aware of the consequences it would have on outsiders. Otherwise why would yahoo.jp switch it suddenly and coincidentally after a DDOS?

[Miyuki_Kamiko]

The fact that SEGA switched to /25 after the DDOS could mean that they or yahoo.jp were aware of the consequences it would have on outsiders. Otherwise why would yahoo.jp switch it suddenly and coincidentally after a DDOS?

by switching it to a /25 it stops a large amount of the DDOS attack as in if the DDOS was mainly coming from any ISP that went through /23 routes that part of the DDOS could no longer reach PSO2

this would result in the servers being able to become stable again

[snowspear123]

Here are my observations..
when I try to ping gs016.pso2gs.net the DNS server translates that to 210.189.208.16 which i then get blocked after 3 hops...
according to this website http://www.the-ghf-clan.de/pso2serverstatus.html ship 2 ip should be 210.129.209.16.

If i tracert this IP I can ACTUALLY GO THROUGH! here is the tracert if I do it via IP.

4 23 ms 25 ms 16 ms gi-1-1-3.gw01.grnsbr.phub.net.cable.rogers.com [24.153.7.5]
5 34 ms 39 ms 39 ms van58-10-228-226.dynamic.rogerstelecom.net [209.148.228.226]
6 38 ms 39 ms 49 ms 10gigabitethernet4-1.core1.chi1.he.NET [206.223.119.37]
7 100 ms 93 ms 86 ms 10ge11-4.core1.pao1.he.net [184.105.222.173]
8 85 ms 89 ms 81 ms 10ge3-1.core1.sjc2.he.net [72.52.92.70]
9 82 ms 89 ms 143 ms pacnet.10gigabitethernet2-2.core1.sjc2.he.net [216.218.192.234]
10 202 ms 201 ms 207 ms gi9-0-0.cr2.nrt1.asianetcom.net [202.147.50.134]

11 201 ms 195 ms 196 ms ge-2-1-0-0.gw3.nrt5.asianetcom.net [202.147.0.18
2]
12 186 ms 196 ms 199 ms YHJ-0002.gw3.nrt5.asianetcom.net [203.192.150.17
4]
13 185 ms 222 ms 185 ms INTEL_CE_LINUX [203.141.47.222]
14 197 ms 199 ms 199 ms ae1.tnhcr02.idc.jp [158.205.134.10]
15 198 ms 193 ms 185 ms ae0.tnhcr01.idc.jp [158.205.192.169]
16 195 ms 199 ms 195 ms po14.ta1ag01.idc.jp [158.205.192.102]
17 190 ms 196 ms 206 ms lag3.l303.ta1.eg.idc.jp [158.205.188.250]
18 195 ms 259 ms 199 ms INTEL_CE_LINUX [158.205.104.60]
19 187 ms 192 ms 199 ms INTEL_CE_LINUX [158.205.104.49]
20 194 ms 194 ms 199 ms INTEL_CE_LINUX [158.205.104.60]
21 203 ms 204 ms 199 ms INTEL_CE_LINUX [158.205.104.49]
22 199 ms 199 ms 199 ms INTEL_CE_LINUX [158.205.104.60]
23 199 ms 199 ms 189 ms INTEL_CE_LINUX [158.205.104.49]
24 198 ms 202 ms * INTEL_CE_LINUX [158.205.104.60]
25 201 ms 198 ms 185 ms INTEL_CE_LINUX [158.205.104.49]

nvm I lied.. it keeps fapping between these two IPs... T_T

[Chik'Tikka]

that's another null route, if they don't time out, then they hop back and forth between routers. this happens to some people that trace routes by the site names as well+^_^+

i can't read German so i don't know how old the info on that site is, or if those are the new IP ranges or the old ones, but our ISPs DNS (or at least my neighbors router and Google's 8.8.8.8) still wants gs016.pso2gs.net to resolve as 210.189.208.16+^_^+

[Poyonche]

@Ezodagrom The thing I don't understand is that people having exactely the same ISP than me can log into the game and access the main site just fine while I can't.

"Dégroupé" ou "Non-Dégroupé" ?

@Miyuki_Kamiko : Idk for other people, BUT I am not lying :(

[TaigaUC]

My ISP got back to me after assigning engineers to investigate the issue for about a week.
They said that SEGA is "selectively advertising their upstream".
If anyone's wondering what that means, it's basically what was confirmed in Miyuki's thread (http://www.pso-world.com/forums/showthread.php?t=220659).
For those too lazy to click the link: SEGA has only revealed their true location to certain routes. That's why most routes don't go anywhere - they don't know where to go.
I sure hope my ISP isn't just regurgitating what's on that link (because I linked it to them).

My ISP confirmed that other people using my same ISP are able to connect, but there's nothing they can do about my specific case.
They said the only option is to contact SEGA and ask them to do something about it.
Which... as we already know, didn't result in anything useful ("service is Japan only, blahblah").

So... guess I'm stuck with alternate methods.

[Arada]

"Dégroupé" ou "Non-Dégroupé" ?

@Miyuki_Kamiko : Idk for other people, BUT I am not lying :(

That could be the reason. One goes through SFR's own network, the other goes through Orange's network (which doesn't reach the servers).

[Miyuki_Kamiko]

"Dégroupé" ou "Non-Dégroupé" ?

@Miyuki_Kamiko : Idk for other people, BUT I am not lying :(

im not targeting you though i'll admit my comment was abit cruel but it doesn't change the fact that there Others lying about how there connecting without software or certain ISPS

anybody with TWC or especially Verizion i believe can connect
Verizion advertises themselves in a way that it sounds like they would support /973642401 route and that doesn't exist i used a completely random number because that's kinda the message i get when i see verizion commercials

[TaigaUC]

I don't think it's a matter of certain ISPs. People are just assuming that.
I have friends on the same ISP as myself who can access PSO2. I can't (from my house internet).
I think it's a matter of certain routes going from each individual person's house.
Although it's possible that each ISP uses different routes (I just sent my ISP a query about that).

Our connection request goes through servers that route us to Japan.
Some of those routing servers aren't being given correct information by SEGA.
If you're lucky and can connect, it just means your specific location's connection is going through a routing server that currently has the correct info.
If you're unlucky and can't connect, it means you're stuck on a route that SEGA has intentionally lied to.

Correct me if I'm wrong.

Something I'd like to point out is: notice that whenever people suddenly found themselves blocked/unblocked, it was only during SEGA's PSO2 maintenance.
I think that pretty much proves SEGA is in complete control of the situation.
Routing servers aren't likely to handle DDoS protection requests from SEGA specifically during PSO2's maintenance.
But if they have a system in place to auto-update routing, SEGA could easily update with correct/incorrect information on the fly.
I suspect that SEGA just sometimes changes which routes they send correct and incorrect information to.
I don't know how much time it takes for routing servers to update their routes, though.

[Cyber Meteor]

@Poyonche and Arada "Dégroupé" through SFR's own network.

[Miyuki_Kamiko]

I don't think it's a matter of certain ISPs. People are just assuming that.
I have friends on the same ISP as myself who can access PSO2. I can't (from my house internet).
I think it's a matter of certain routes going from each individual person's house.
Although it's possible that each ISP uses different routes (I just sent my ISP a query about that).

Our connection request goes through servers that route us to Japan.
Some of those routing servers aren't being given correct information by SEGA.
If you're lucky and can connect, it just means your specific location's connection is going through a routing server that currently has the correct info.
If you're unlucky and can't connect, it means you're stuck on a route that SEGA has intentionally lied to.

Correct me if I'm wrong.

Something I'd like to point out is: notice that whenever people suddenly found themselves blocked/unblocked, it was only during SEGA's PSO2 maintenance.
I think that pretty much proves SEGA is in complete control of the situation.
Routing servers aren't likely to handle DDoS protection requests from SEGA specifically during PSO2's maintenance.
But if they have a system in place to auto-update routing, SEGA could easily update with correct/incorrect information on the fly.
I suspect that SEGA just sometimes changes which routes they send correct and incorrect information to.
I don't know how much time it takes for routing servers to update their routes, though.

that's probable assuming sega actually knows what there doing but that sounds more like something an ISP would control and be doing because

from reading on backbones from a few sites like wikipedia and reading what server techs have been saying there are ISPS that buy that buy the foreign routes directly from other ISPS

so ill use an example if Verizion bought the direct routes that the japanese use from yahoo jp
there would be nothing Sega could do to stop them from entering there servers without an IP ban

[Aussei]

So I sat down and really started to think about it and I came to the conclusion that this is the only explanation for everything.

https://www.youtube.com/watch?v=KMcny_pixDw

Maybe this will help you guys too to understand the current situation and really just cope with it better.

[Scarlet-Star]

So I sat down and really started to think about it and I came to the conclusion that this is the only explanation for everything.

https://www.youtube.com/watch?v=KMcny_pixDw

Maybe this will help you guys too to understand the current situation and really just cope with it better.

You mean with the truth that SEGA never cared about non-japanese people, like many other japanese companies, and really don't give a damn about how we feel, what we want, and how we end up?

Oh I knew that, which is why I still hate SEGA to this day, but I enjoy the game. I just hate SEGA with the rage of Vol dragon's full armor.

[lunarsoul]

Apparently mine traces fine, yet I still cant get on PSO2.JP website or Connect to Ship 2 server, keep getting Error 249. I might give up when my ISP is telling me that they cant help what isint broken on their end. And we all know SEGA wont listen to this Gaijin.

I located in Toronto, Canada, I use Acanac as my ISP which is under Rogers Network.
[SPOILER-BOX]http://i57.tinypic.com/ir7teg.jpg
http://i61.tinypic.com/10qxsf7.jpg[/SPOILER-BOX]

[DamonKatu]

**POOF** Ok, ok, Im back. Here's why living in the south suck. Dispute living near central, the corporation here is just as lost as the locals. I have to print this out next week and show them the issue. Wish me luck. There's a reason "Down South" is used to explain bad situations...

[Urbancowgurl777]

Apparently mine traces fine, yet I still cant get on PSO2.JP website or Connect to Ship 2 server, keep getting Error 249. I might give up when my ISP is telling me that they cant help what isint broken on their end. And we all know SEGA wont listen to this Gaijin.

I located in Toronto, Canada, I use Acanac as my ISP which is under Rogers Network.
[SPOILER-BOX]http://i57.tinypic.com/ir7teg.jpg
http://i61.tinypic.com/10qxsf7.jpg[/SPOILER-BOX]

That's not "just fine". Your connection is going through an infinite loop. It doesn't even leave Canada, let alone connect to pso2.

[Miyuki_Kamiko]

that trace route is probably the worst ive seen so far

[Cypher_9]

* That Yahoo.ip gets their head out of their ass and stops announcing the /25s, which should cause all traffic to get routed through the /23 again, fixing the problem.

* That SEGA changes ISP to one that knows what the fuck they are doing, such as the one running their corporate website. (Amazon)

* That our ISPs eventually become aware of the /23 on their own and start routing through it rather then the /25.

* That someone else running on one of those IPs complains that foreign clients can't connect to his network anymore and calls them out on their incompetence.

Well, I just spoke to another Security Assurance individual at Comcast - even tinyurl'ed this forum to them at the OP. He said that there is nothing that they can do on their end to directly fix the problem but he told me that he would put in a ticket to their engineering team if I heard him correctly. I should of asked much more throughly with this but:

* That Yahoo.ip gets their head out of their ass and stops announcing the /25s, which should cause all traffic to get routed through the /23 again, fixing the problem.

He basically said this; rather this is something that should happen. Anyway, the first guy you can bypass to go to one that knows - perhaps you can explain it better than me upon what Comcast can really do on their end:

1 888 565 4329 <----- Is the number; up to this date I still cannot connect to PSO2 geniunly.

I know I said I wont use a VPN because that will just stroke my laziness if I get what I want which is PSO2 LOL - with the different IPs can mark that I am on the go and what not but, eh it is just the sudden changes from one static to such. Perhaps I would, still thinking about it but, I rather have this issue resolved for the rest of us who are unable to have the 'fun' most are experiencing through other means.

Call it crazy but, I am trying... ; ;



P.S. This is the tinyurl for the reference: http://tinyurl.com/om6lyam [The first post of the thread - give it to the representative for a through look]

[lunarsoul]

That's not "just fine". Your connection is going through an infinite loop. It doesn't even leave Canada, let alone connect to pso2.

Well im at a loss, I dont have the knowledge, and my ISP keeps telling me that they connect just fine, and arent offering support beyond that. :-?

[Scarlet-Star]

Well im at a loss, I dont have the knowledge, and my ISP keeps telling me that they connect just fine, and arent offering support beyond that. :-?

if they're not providing details, you are being conned, and you should change providers.

[SenpaiSilver]

About those connectable ISPs, SFR works but not everywhere in France:

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

1 1 ms 3 ms 2 ms neufbox [192.168.1.1]
2 * * * Request timed out.
3 38 ms 39 ms 39 ms 245.221.65.86.rev.sfr.net [86.65.221.245]
4 39 ms 41 ms 42 ms 213.243.64.86.rev.sfr.net [86.64.243.213]
5 43 ms 39 ms 39 ms 205.140.96.84.rev.sfr.net [84.96.140.205]
6 45 ms 43 ms 43 ms 149.224.65.86.rev.sfr.net [86.65.224.149]
7 46 ms 47 ms 47 ms 70.61.6.109.rev.sfr.net [109.6.61.70]
8 44 ms 47 ms 48 ms 222.29.3.109.rev.sfr.net [109.3.29.222]
9 51 ms 49 ms 51 ms xe-10-0-0.parigi32.par.seabone.net [213.144.183.200]
10 247 ms 261 ms 247 ms xe-0-1-3.singapore2.sin.seabone.net [195.22.218.233]
11 496 ms 462 ms 435 ms kddi.singapore2.sin.seabone.net [213.144.176.86]
12 307 ms 307 ms 330 ms sggjbb001.int-gw.kddi.ne.jp [111.87.6.37]
13 310 ms 308 ms 307 ms otejbb205.int-gw.kddi.ne.jp [59.128.4.61]
14 305 ms 302 ms 311 ms cm-ote257.int-gw.kddi.ne.jp [118.155.197.180]
15 306 ms 306 ms 309 ms 125.29.25.94
16 295 ms 294 ms 299 ms 203.141.47.218
17 320 ms 303 ms 307 ms ae1.tnhcr02.idc.jp [158.205.134.10]
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 296 ms 295 ms 294 ms 158.205.188.253
22 301 ms 300 ms 299 ms lag3.l303.ta1.eg.idc.jp [158.205.188.250]
23 296 ms 315 ms 300 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.

For France OVH works perfectly:

senpaisilver@ovh:~$> traceroute pso2.jp
traceroute to pso2.jp (210.189.209.8), 30 hops max, 60 byte packets
1 rbx-14-m2.fr.eu (91.121.24.252) 1.296 ms 2.262 ms 2.527 ms
2 rbx-1-6k.fr.eu (213.251.191.1) 0.501 ms * *
3 rbx-g1-a9.fr.eu (94.23.122.106) 30.858 ms 30.837 ms 30.764 ms
4 th2-g1-a9.fr.eu (91.121.215.132) 5.083 ms th2-g1-a9.fr.eu (91.121.131.210) 4.785 ms th2-g1-a9.fr.eu (91.121.215.132) 5.029 ms
5 th2-5-6k.fr.eu (213.186.32.201) 4.355 ms * *
6 * * *
7 xe-0-2-3.singapore2.sin.seabone.net (195.22.197.93) 196.473 ms xe-0-1-3.singapore2.sin.seabone.net (195.22.218.233) 244.936 ms xe-0-2-3.singapore2.sin.seabone.net (195.22.197.93) 196.391 ms
8 kddi.singapore2.sin.seabone.net (213.144.176.86) 249.329 ms 249.616 ms 249.598 ms
9 sggjbb001.int-gw.kddi.ne.jp (111.87.6.37) 307.138 ms 312.357 ms 315.353 ms
10 otejbb205.int-gw.kddi.ne.jp (59.128.4.61) 256.788 ms 256.753 ms 256.766 ms
11 cm-ote257.int-gw.kddi.ne.jp (118.155.197.52) 302.952 ms cm-ote257.int-gw.kddi.ne.jp (118.155.197.180) 316.583 ms 267.427 ms
12 125.29.25.94 (125.29.25.94) 254.822 ms 255.053 ms 311.448 ms
13 203.141.47.218 (203.141.47.218) 300.904 ms 249.931 ms 293.835 ms
14 ae1.tnhcr02.idc.jp (158.205.134.10) 250.634 ms 250.408 ms 305.954 ms
15 * * *
16 * * *
17 * * *
18 158.205.188.253 (158.205.188.253) 250.038 ms 293.516 ms 249.897 ms
19 lag3.l303.ta1.eg.idc.jp (158.205.188.250) 263.110 ms 263.082 ms 313.894 ms
20 158.205.104.60 (158.205.104.60) 269.881 ms 269.185 ms 317.581 ms
21 210.189.209.8 (210.189.209.8) 310.873 ms 260.922 ms 260.854 ms
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *

[Cyber Meteor]

I'm also affected by non-working SFR, and it's not a problem of "Dégroupé/non-dégroupé" because I'm in the case where it's supposed to work (Dégroupé), I'm just currently waiting for it to work again, or using pingzapper (it currently disconnects me every 30 mins but I still can do some things except EQ and complete AQ/XQ but some days it works fine).

[Poyonche]

SO it will be the same thing for Laposte and Virgin :(

Could i know where do you live in France ? So maybe we'll know which region are affected by the "non-working SFR"

Im in the north-east of France, Lorraine

[Cyber Meteor]

I'm in Bourgogne 21 (Côte d'Or)

[Poyonche]

For the "non-working SFR"

14 305 ms 302 ms 311 ms cm-ote257.int-gw.kddi.ne.jp [118.155.197.180]

For working SFR
15 305 ms 302 ms 311 ms cm-ote257.int-gw.kddi.ne.jp [118.155.197.52]

Does it matter ? Or it is an useless thing ?

EDIT : The first part (with the rev.sfr) is different since not from the same region (i think so)

[Cyber Meteor]

It doesn't make a difference, look at those tracerts



[SPOILER-BOX]http://i1318.photobucket.com/albums/t650/CyberMeteor/Login%20IP%20ban%20test/Pso2tracert1_zpscf5d94f5.png~original[/SPOILER-BOX]

[SPOILER-BOX]http://i1318.photobucket.com/albums/t650/CyberMeteor/Login%20IP%20ban%20test/Pso2tracert2_zps25a164fa.png~original[/SPOILER-BOX]

As you can see i have "cm-ote257........" at 15th hop, which, if I refer to what you say , is for "working SFR".

[Amakuni]

Hello , i live in france , my ISP is Orange , and so this morning i call them to ask them to reroute their server to pso2.jp , after 2 hours switching people and services a guy finally say this to me :

pso2.jp is blacklisted , write to [email protected] and explain your issue and wait for an answer .



Literally , orange user , we're doomed .

[sarttan]

Could someone sticky this thread? It's got a ton of information for people who are new to the server situation.

[isCasted]

Mods should edit current sticky, at least. It was last edited in June.

[Poyonche]

I heard that EE, Orange and O2 works in UK.


And also some people can connect with Free in France (well just one guy said it)

[Gardios]

Why doesn't O2 Germany work.

God dammit. :(

[Akakomuma]

Probably old, but still good information.

http://www.dslreports.com/forum/r29370409-Dslextreme-blocking-access-to-phantasy-star-online-2

Very simply, this IS Sega's fault - or at least, their responsibility. See, Sega's not properly advertising their IP and routes to the appropriate backbone carriers. I'm sure anyone who's spent enough time here on BBR has at least heard of names like Level3 and Cogent? Sega is SUPPOSED to be in communication with those carriers, and several others... but it isn't. So the 'big boys' like Level3 and Cogent don't know that Sega's PSO2 exists nor how to reach it. Even if you know what the (unchanged) destination IP is, if you don't know the *route* necessary to reach it, it doesn't do you much good.

Right now, testing is indicating that exactly two carriers are aware of PSO2: Asia Pacific Network Information Centre (APNIC) and Hurricane Electric (HE). Two, out of dozens.

As you can see, it's not a problem with ISPs refusing to grant access... it's a problem with Sega not making its presence known. Now, as a short-term work-around, it IS possible for our network engineers to manually set a route to the destination IP... but that's generally not recommended. It'd be a band-aid that might actually cause more problems in the long run, and besides - even if we did that, that would only 'fix' it for customers on DSL Extreme connections (which, while nice for us, wouldn't help you play with friends online if your friends aren't using DSL Extreme too). The REAL solution is for Sega to step it up and publish with the carriers.

[Gama]

I'm in a similar situation, tracert stops before the last needed step.
I live in Portugal, ISP is Cabovisão.

[spoiler-box]http://i.imgur.com/tco1VUZ.jpg[/spoiler-box]

my guess is tht both isp's use the same route...

also Cabovisão is a bish -.-

[NotRankin]

Just forwarding info:

Herro has access to pso2.jp and the game from AT&T in Richmond VA

http://i.imgur.com/yzp86tA.png

[EvilMag]

Just forwarding info:

Herro has access to pso2.jp and the game from AT&T in Richmond VA

http://i.imgur.com/yzp86tA.png

On AT&T still can't connect. :( Nice to see progress is being made.

[Poyonche]

Here is something wrong ?

Cuz I am seeing Verizon in your tracert. :o

[LordKaiser]

Since this thread resurrected i want to leave this here:

http://archive.apnic.net/meetings/22/docs/tut-routing-pres-bgp-bcp.pdf

https://www.nanog.org/meetings/nanog43/presentations/BRGREEN_prefix_filtering_N43.pdf

http://www.cs.princeton.edu/~jrex/papers/policies.pdf

I wonder why Japan IPS companies haven't filtered the /25 prefix yet. if they did then this problem wouldn't exist.

[TauAkiou]

Since this thread resurrected i want to leave this here:

http://archive.apnic.net/meetings/22/docs/tut-routing-pres-bgp-bcp.pdf

https://www.nanog.org/meetings/nanog43/presentations/BRGREEN_prefix_filtering_N43.pdf

http://www.cs.princeton.edu/~jrex/papers/policies.pdf

I wonder why Japan IPS companies haven't filtered the /25 prefix yet. if they did then this problem wouldn't exist.

Honestly, I think Japanese ISPs need a serious wake up call when it comes to embracing proper, practical standards. This is especially true with China's recent string of cyber attacks. (China and Japan still aren't on the best terms with each other, either.)

The bizzare thing about this is that the /25s didn't exist until the day people started reporting problems. I don't know why Yahoo.jp would consider segmenting their prefixes even further, especially when (from what I tried to understand from those powerpoints, and from what I read at DSLReports) these seem to end up causing strain, security issues, and connectivity issues because of the amount of bloat they end up introducing to the routing tables.

I'd actually like to hear how the connectivity has been for Japanese players, since it seems to have become significantly more unstable for us since this 'change'. It would provide some insight if we knew how things have gotten better (or worse) for the natives themselves.

[tet666]

German isp T-Online works fine here don't have the time to post a tracert so i just thought i share this

[lunarsoul]

Possible good news for Canadian PSO2 players. If you havent been able to get on normally until now (like me) I talked to Rogers about not connecting to PSO2.jp and the Game, and they told me they are working on it and it should be resolved within 48 hours, and they would call me when its fixed. If they could get it done than I will shockingly respect Rogers after my old ISP sat on their hands and told me it was my problem.

[Dilan]

we have no route at all in kuwait. our uplink provider also left helping as they requested to check with gaming provider.

[Padium]

I contacted my ISP, and they have begun looking into implementing a solution:

"High Speed Internet – Cable Some customers have been reporting latency issues when using certain online games with our cable internet service during peak-hours. We have reached out to the highest level within our Network Operations department and have been continuously working to improve the experience of our gaming customers. While the issue has been confirmed to be beyond our network and direct control, we have reached out to external sources such as the gaming provider and other local service providers in a collaborative effort to isolate the cause of the issue and find a solution. We apologize for any inconvenience this may cause."

I tried being very specific, I am not sure they get that the problem has already been identified.