said by Belial :This is happening for most ISPs right now. Just give it a week or two there are various reasons why you may not be able to connect. It seems certain ISPs may be preventing outgoing routes to those IPs due to the recent DDOS. It's not an IP block from Japan's side as if you do a traceroute you'll see that you likely don't even leave your state/country of residence.
In order to traceroute either to a tracert "IP" or if on Mac use traceroute "IP" from your cmd or terminal.
I figured it out, and it's an ugly story.
No, it's because the network provider announcing the route for 210.189.209.8 (per the linked posts, the GAME actually connects into 210.189.208.0/24 as well) is a bunch of fucking idiots: it's idc.jp AKA Yahoo Japan, btw.
Registry: whois.nic.ad.jp
Network Information:
[Network Number] 210.189.208.0-210.189.229.255
[Network Name]
[Organization] Yahoo Japan Corporation
[Administrative Contact] TO8496JP
[Technical Contact] YT8719JP
[Abuse] abuse@idc.jp
[Allocated Date] 1999/07/16
[Last Update] 2014/06/10 13:03:47(JST)
That range has the following prefixes:
210.189.208.0/20
210.189.224.0/22
210.189.228.0/23
The 210.189.209.8 IP is in the /20.
route-views>sh ip bgp 210.189.208.0/20 lo
BGP table version is 711556819, local router ID is 128.223.51.103
Status codes: s suppressed, d damped, h history, * valid, > best, i - internal,
r RIB-failure, S Stale
Origin codes: i - IGP, e - EGP, ? - incomplete
Network Next Hop Metric LocPrf Weight Path
* 210.189.208.0/25 202.249.2.86 0 7500 2516 23816 4694 i
* 208.51.134.254 2523 0 3549 2516 23816 4694 i
*> 203.181.248.168 0 7660 2516 23816 4694 i
* 193.0.0.56 0 3333 1257 2516 23816 4694 i
* 210.189.208.0/23 202.232.0.2 0 2497 17676 4694 4694 i
* 203.181.248.168 0 7660 9355 4694 i
* 202.249.2.86 0 7500 7660 9355 4694 i
*> 216.218.252.164 0 6939 4694 i
* 114.31.199.1 0 0 4826 6939 4694 i
* 210.189.208.128/25
203.181.248.168 0 7660 2516 23816 4694 i
*> 202.249.2.86 0 7500 2516 23816 4694 i
* 193.0.0.56 0 3333 1257 2516 23816 4694 i
* 208.51.134.254 2523 0 3549 2516 23816 4694 i
* 210.189.209.0/25 208.51.134.254 2523 0 3549 2516 23816 4694 i
* 203.181.248.168 0 7660 2516 23816 4694 i
* 193.0.0.56 0 3333 1257 2516 23816 4694 i
*> 202.249.2.86 0 7500 2516 23816 4694 i
AS4694 (the originating ASN) is Yahoo Japan.
The IP in question is contained in a globally announced /25 - something that the VAST MAJORITY of the world's backbone providers WILL NOT ACCEPT: Go google some almost 20-year-old history as to why (Sean Doran/SprintLink putting his foot down on routing table bloat, dropping everything smaller than a /22 under the floor unless you were in an ERX block, where you were allowed to have a /24 max , and the rest of the world quickly following his lead, because the routing table pains were everyone's, not just SprintLink's).
Now there's ALSO 210.189.208.0/23 , which at least theoretically should become the capturing route, HOWEVER that prefix seems to be VERY unstable:
»
stat.ripe.net/widget/bgp ··· type=bgpIf you took the time to at least begin to understand what is displayed there (playing the animation too) :
The peering routes of Yahoo Japan into 2914 (Verio/ntt.net North America) and 6939 (he.net) seem to be disappearing at times, and are NOT seen via many peers, and the paths are unstable. No other big North American ASNs seems to peer with Yahoo Japan directly. Likewise AS 3320 (DTAG - Deutsche Telekom), a major path to Europe is only indirectly connected via another AS in between: 4725 (Softbank Japan).
In other words: that site is poor, no: piss-poorly connected to the rest of the world, it's connectivity is fundamentally unstable - and BGP4 routine instability is being punished with route-flap dampening the world over.
With the /25 not being seen by the majority of the world's ISPs, and the /23 being unstable (and likely suppressed for extended periods of time due to route-flap!), don't be surprised that you can't reach it.
Don't expect ISPs to magically deviate from the "maximum prefix length" rules for the sake of reaching such unstable corners of the Internet: strong adherence to such rules increases routing stability and an ISP's overall service availability.
And to the OP: go tell pso2.jp to grow a spine and arrange for some actually working hosting/routing for their game network. Knowing the Japanese, they're only going to wake up from their communal sleep of "what me? I'm not responsible!" if you scream into their face at the top of your lungs (or upper-case letters) what a bunch of incompetent idiots they are. Good luck.