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!
Connectable ISPs: (Last Updated: 18/7/2014)
Spoiler!
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!
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.
Connect With Us