PSO2 EN (Ship 1): Johana
PSO2 JP (Ship 2): Johana, Ezodagrom, Luppi, Lana, Yukari, Blune, Elysia, Elena
PSU EN/JP: Johana, Blune, Ezodagrom, Luppi/Johana, Lana
Youtube: https://www.youtube.com/c/ezodagrom
Steam: http://steamcommunity.com/id/ezodagrom
@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.
to live you must kill something for food whether it be a plant or an animal all life depends on the cycle of death.
"Life is a fleeting dream but Death is eternal"
Stiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiii iiiiiiiiiiiiiiiiiiiiill think this is SEGA's way of locking us out
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?
to live you must kill something for food whether it be a plant or an animal all life depends on the cycle of death.
"Life is a fleeting dream but Death is eternal"
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
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+^_^+
Connect With Us