PDA

View Full Version : JP PSO2 Tracerts from around the world to PSO2 (Large Post)



TsukasaHiiragi
Jun 29, 2014, 02:53 AM
I've been doing various tracerts from servers around the world, and most haven't been able to reach pso2.jp, in fact none from the US reached them. Starting with the most obvious one from Tokyo which should have no problems in reaching the PSO2 servers, and obviously succeeded with no problems, after that I slowly started branching out..

I'm going to condense this information as much as possible since obviously there is a lot of data here.

Hop Time Time Time Target (Tokyo Host)
1 <1 ms <1 ms <1 ms 50.31.252.1.static.vps.net [50.31.252.1]
2 <1 ms <1 ms <1 ms ge-1-1-3.cr2.tko1.jp.scnet.net [75.102.60.21]
3 11 ms 12 ms 2 ms ve701.fr3.tyo.llnw.net [203.77.185.45]
4 2 ms 9 ms 2 ms ve5.fr4.tyo.llnw.net [203.77.184.206]
5 2 ms 2 ms 3 ms ve7.fr3.tyo3.llnw.net [203.77.184.234]
6 1 ms 1 ms 1 ms sbtm.tge8-4.fr4.tyo3.llnw.net [203.77.184.242]
7 1 ms 1 ms 1 ms 143.90.163.69 [143.90.163.69]
8 1 ms 1 ms 2 ms STOrw-26T1-2.nw.odn.ad.jp [143.90.231.206]
9 2 ms 1 ms 1 ms STOrc-02Te0-3-0-2.nw.odn.ad.jp [143.90.164.253]
10 1 ms 1 ms 1 ms STOrw-53Te3-1.nw.odn.ad.jp [143.90.143.174]
11 2 ms 2 ms 1 ms 10.143090054.odn.ne.jp [143.90.54.10]
12 1 ms 1 ms 2 ms ae3-105.tnhcr01.idc.jp [158.205.192.109]
13 2 ms 2 ms 1 ms 172.31.254.78 [172.31.254.78]
14 * * * Timeout
15 * * * Timeout
16 2 ms 3 ms 2 ms 172.31.254.150 [172.31.254.150]
17 3 ms 2 ms 2 ms 158.205.188.253 [158.205.188.253]
18 2 ms 2 ms 2 ms lag3.l303.ta1.eg.idc.jp [158.205.188.250]
19 2 ms 3 ms 2 ms 158.205.104.60 [158.205.104.60]
20 2 ms 2 ms 2 ms 210.189.209.8 [210.189.209.8]

Hop Time Time Time Target (Hong Kong Host)
1 <1 ms <1 ms <1 ms mpr1.g1-16.omccc-7.hkg001.pnap.net [202.56.13.252]
2 1 ms 1 ms 1 ms core1.po2.hkg003.pnap.net [202.56.8.69]
3 1 ms 1 ms <1 ms 203.131.242.189 [203.131.242.189]
4 1 ms 25 ms 16 ms ae-5.r22.tkokhk01.hk.bb.gin.ntt.net [129.250.2.48]
5 53 ms 51 ms 52 ms ae-2.r25.tokyjp05.jp.bb.gin.ntt.net [129.250.2.120]
6 49 ms 50 ms 50 ms ae-2.r00.tokyjp01.jp.bb.gin.ntt.net [129.250.5.95]
7 52 ms 52 ms 50 ms xe-0-4-0-8.r01.tokyjp01.jp.ce.gin.ntt.net [61.213.161.6]
8 50 ms 52 ms 50 ms ae3-105.tnhcr01.idc.jp [158.205.192.109]
9 * * * Timeout
10 * * * Timeout
11 * * * Timeout
12 * * * Timeout
13 54 ms 51 ms 52 ms 158.205.188.253 [158.205.188.253]
14 51 ms 51 ms 50 ms lag3.l303.ta1.eg.idc.jp [158.205.188.250]
1551 ms 51 ms 51 ms 158.205.104.60 [158.205.104.60]
1650 ms 50 ms 50 ms 210.189.209.8 [210.189.209.8]

Whilst it looks like some latency on the final hops at least it managed to reach the host.

Tracing route to pso2.jp executed on: 2014-Jun-29 09:42:11 GMT

Hop Time Time Time Target (London Host)
1 3 ms 1 ms 2 ms CLIENT-OneProvider.serverspace.co.uk [31.24.33.217]
2 <1 ms <1 ms <1 ms v925-dcs1.logo.serverspace.co.uk [77.246.169.131]
3 <1 ms <1 ms <1 ms po1-1207-cr0.thn.uk.as6908.net [78.41.155.25]
4 * * <1 ms po1-1207-cr0.thn.uk.as6908.net [78.41.155.25]
5 * <1 ms * po1-1207-cr0.thn.uk.as6908.net [78.41.155.25]
6 * * * Timeout
7 * * * Timeout
8 * * <1 ms po1-1207-cr0.thn.uk.as6908.net [78.41.155.25]
9 * 1 ms * po1-1207-cr0.thn.uk.as6908.net [78.41.155.25]
10 * * <1 ms po1-1207-cr0.thn.uk.as6908.net [78.41.155.25]
11 * * 1 ms po1-1207-cr0.thn.uk.as6908.net [78.41.155.25]
12 * * * Timeout
19 * * * Timeout
20 1 ms * * po1-1207-cr0.thn.uk.as6908.net [78.41.155.25]
21 * 1 ms * po1-1207-cr0.thn.uk.as6908.net [78.41.155.25]
22 * * * Timeout
23 * 1 ms * po1-1207-cr0.thn.uk.as6908.net [78.41.155.25]
24 * 1 ms * po1-1207-cr0.thn.uk.as6908.net [78.41.155.25]
25 * <1 ms * po1-1207-cr0.thn.uk.as6908.net [78.41.155.25]

** This router is obviously having issues

Hop Time Time Time Target (Sydney Host)
1 3 ms 3 ms 3 ms 27.50.83.1 [27.50.83.1]
2 7 ms 7 ms 8 ms 202.167.227.237 [202.167.227.237]
3 7 ms 4 ms 4 ms xe-1-0-0.gw101.sy1.ap.equinix.com [27.111.240.140]
4 207 ms 207 ms 208 ms 202.68.67.41 [202.68.67.41]
5 184 ms 185 ms 186 ms xe-3-1-0.r00.sydnau02.au.bb.gin.ntt.net [202.68.64.214]
6 227 ms 238 ms 224 ms as-0.r22.tokyjp01.jp.bb.gin.ntt.net [129.250.6.109]
7 236 ms 226 ms 222 ms ae-8.r24.tokyjp05.jp.bb.gin.ntt.net [129.250.3.155]
8 226 ms 225 ms 226 ms ae-2.r01.tokyjp01.jp.bb.gin.ntt.net [129.250.3.243]
9 226 ms 243 ms 246 ms xe-0-4-0-8.r01.tokyjp01.jp.ce.gin.ntt.net [61.213.161.6]
10 226 ms 226 ms 225 ms ae3-105.tnhcr02.idc.jp [158.205.192.113]
11 * * * Timeout
12 * * * Timeout
13 * * * Timeout
14 * * * Timeout
15 236 ms 232 ms 232 ms 158.205.188.253 [158.205.188.253]
16 227 ms 227 ms 227 ms lag3.l303.ta1.eg.idc.jp [158.205.188.250]
17 228 ms 224 ms 224 ms 158.205.104.60 [158.205.104.60]
18 224 ms 223 ms 226 ms 210.189.209.8 [210.189.209.8]

No problems here

Sp-24
Jun 29, 2014, 02:55 AM
Wait... The site's address is actually reachable from some locations? I could never connect to it with pings and trace requests, even years ago, when no IP blocks have been issued yet.

EvilMag
Jun 29, 2014, 02:56 AM
[spoiler-box]http://i.imgur.com/Rip0us0.png[/spoiler-box]
Here's mine. Mine isn't even leaving the country. ISP is AT&T if you are wondering

IndignationSWF
Jun 29, 2014, 02:57 AM
Wait, so you mean to tell me NONE of them from the US reached the site? That's more than a bit conspicuous even with our distance from the Host. Logically at least one should've connected even if it was a fluke. Not a good sign.

TsukasaHiiragi
Jun 29, 2014, 02:58 AM
Hop Time Time Time Target (New Delhi Host)
1 <1 ms <1 ms <1 ms 103.29.234.1 [103.29.234.1]
2 <1 ms 1 ms <1 ms 180.179.192.25 [180.179.192.25]
3 <1 ms 1 ms <1 ms 180.179.197.21 [180.179.197.21]
4 3 ms 4 ms 3 ms 14.140.113.85.static-Delhi-vsnl.net.in [14.140.113.85]
5 * * * Timeout
6 115 ms 117 ms 115 ms ge-101-0-0-42.r01.tkokhk01.hk.ce.gin.ntt.net [203.131.241.158]
7 109 ms 109 ms 109 ms ge-101-0-0-42.r01.tkokhk01.hk.bb.gin.ntt.net [203.131.241.157]
8 116 ms 108 ms 108 ms ae-2.r21.tkokhk01.hk.bb.gin.ntt.net [129.250.6.134]
9 161 ms 163 ms 163 ms as-1.r25.tokyjp05.jp.bb.gin.ntt.net [129.250.4.114]
10 162 ms 158 ms 161 ms ae-2.r01.tokyjp01.jp.bb.gin.ntt.net [129.250.3.243]
11 159 ms 163 ms 153 ms xe-0-4-0-8.r01.tokyjp01.jp.ce.gin.ntt.net [61.213.161.6]
12 162 ms 163 ms 156 ms ae3-105.tnhcr01.idc.jp [158.205.192.109]
13 * * * Timeout
14 * * * Timeout
15 * * * Timeout
16 * * * Timeout
17 159 ms 156 ms 162 ms 158.205.188.253 [158.205.188.253]
18 163 ms 159 ms 169 ms lag3.l303.ta1.eg.idc.jp [158.205.188.250]
19 168 ms 159 ms 157 ms 158.205.104.60 [158.205.104.60]
20 162 ms 160 ms 184 ms 210.189.209.8 [210.189.209.8]

No Problems here

Hop Time Time Time Target (Hamburg Host)
1 <1 ms <1 ms <1 ms 188.94.27.153 [188.94.27.153]
2 <1 ms <1 ms <1 ms ham-l3-r04.apc-l3.hh.nmmn.net [217.114.72.25]
3 <1 ms <1 ms <1 ms mesh.mesh.l3.hh.nmmn.net [83.220.136.89]
4 6 ms 208 ms 6 ms ve3001.edge1-dus1.mesh.eu [213.203.213.70]
5 6 ms 6 ms 6 ms ve1344.edge1-dus4.mesh.eu [213.203.212.94]
6 13 ms 13 ms 13 ms xe-3-1-630.r02.dsdfge01.de.bb.gin.ntt.net [213.198.77.89]
7 263 ms 263 ms 263 ms xe-3-4.r00.dsdfge02.de.bb.gin.ntt.net [129.250.5.173]
8 272 ms 271 ms * xe-0-1-0-3.r02.frnkge03.de.bb.gin.ntt.net [129.250.5.62]
9 14 ms 14 ms 14 ms ae-2.r20.frnkge04.de.bb.gin.ntt.net [129.250.5.217]
10 287 ms 285 ms 281 ms ae-20.r24.tokyjp05.jp.bb.gin.ntt.net [129.250.6.89]
11 278 ms 279 ms 278 ms ae-1.r01.tokyjp01.jp.bb.gin.ntt.net [129.250.3.241]
12 263 ms 264 ms 277 ms xe-0-4-0-8.r01.tokyjp01.jp.ce.gin.ntt.net [61.213.161.6]
13 258 ms 271 ms 274 ms ae3-105.tnhcr02.idc.jp [158.205.192.113]
14 * * * Timeout
15 * * * Timeout
16 * * * Timeout
17 * * * Timeout
18 266 ms 265 ms 295 ms 158.205.188.253 [158.205.188.253]
19 275 ms 266 ms 288 ms lag3.l303.ta1.eg.idc.jp [158.205.188.250]
20 282 ms 282 ms 273 ms 158.205.104.60 [158.205.104.60]
21 272 ms 273 ms 288 ms 210.189.209.8 [210.189.209.8]

No problems here

TsukasaHiiragi
Jun 29, 2014, 03:01 AM
Wait, so you mean to tell me NONE of them from the US reached the site? That's more than a bit conspicuous even with our distance from the Host. Logically at least one should've connected even if it was a fluke. Not a good sign.

I'm still testing, so far I'm 0/3 for the NA hosts I'm using.

TsukasaHiiragi
Jun 29, 2014, 03:04 AM
Hop Time Time Time Target (Sao Paulo Host)
1 1 ms 1 ms 2 ms 189.1.162.1 [189.1.162.1]
2 1 ms 1 ms 1 ms 10.95.0.247 [10.95.0.247]
3 10 ms 10 ms 9 ms 200.160.199.209 [200.160.199.209]
4 1 ms 1 ms <1 ms 200.160.197.137 [200.160.197.137]
5 4 ms 1 ms 1 ms 200.160.197.182 [200.160.197.182]
6 2 ms 2 ms 2 ms 186.234.253.161 [186.234.253.161]
7 59 ms 2 ms 2 ms 200-147-29-2.static.uol.com.br [200.147.29.2]
8 3 ms 3 ms 2 ms 200-147-29-146.static.uol.com.br [200.147.29.146]
9 130 ms 123 ms 120 ms ve732.r1.mi.hwng.net [205.185.198.133]
10 160 ms 189 ms 170 ms 1-2.r1.at.hwng.net [209.197.0.209]
11 156 ms 147 ms 209 ms 2-3.r1.dc.hwng.net [69.16.190.25]
12 241 ms 234 ms 239 ms 194.25.208.113 [194.25.208.113]
13 393 ms 391 ms 392 ms tyo-sa3-i.TYO.JP.NET.DTAG.DE [62.154.5.210]
14 305 ms 305 ms 305 ms as4725.ix.jpix.ad.jp [210.171.224.48]
15 315 ms 320 ms 315 ms STOrc-01Te0-4-0-2.nw.odn.ad.jp [143.90.149.45]
16 324 ms 325 ms 324 ms STOrw-53Te2-1.nw.odn.ad.jp [143.90.143.170]
17 309 ms 309 ms 310 ms 10.143090054.odn.ne.jp [143.90.54.10]
18 304 ms 304 ms 304 ms ae3-105.tnhcr01.idc.jp [158.205.192.109]
19 * * * Timeout
20 * * * Timeout
21 * * * Timeout
22 * * * Timeout
23 302 ms 302 ms 302 ms 158.205.188.253 [158.205.188.253]
24 321 ms 325 ms 325 ms lag3.l303.ta1.eg.idc.jp [158.205.188.250]
25 310 ms 310 ms 310 ms 158.205.104.60 [158.205.104.60]

The hosts I'm using are restricted to 25 hops, since this did reach JP address I can assume that this would have reached the PSO2 servers from South America.

Chik'Tikka
Jun 29, 2014, 03:12 AM
decided to do another trace route, this time with it set to wait 5000 ms before trying another hop, it just reports unreachable now, but this still doesn't quite confirm anything+^_^+
http://i59.tinypic.com/2hojpdl.png

Sp-24
Jun 29, 2014, 03:12 AM
The hosts I'm using are restricted to 25 hops, since this did reach JP address I can assume that this would have reached the PSO2 servers from South America.
Not necessarily. As I said before, I can get all the way to Tokyo, but the server still rejects me:
[spoiler-box]Don't mind the font, I just had another idiotic theory that didn't work.

http://i.imgur.com/MVO9XUM.png[/spoiler-box]

TsukasaHiiragi
Jun 29, 2014, 03:13 AM
Hop Time Time Time Target (Mexico City Host)
1 <1 ms <1 ms <1 ms ptr1.dimenoc.com [201.151.147.1]
2 1 ms 1 ms 1 ms customer-GDL-254-5.megared.net.mx [187.247.254.5]
3 34 ms 34 ms 34 ms 10.3.0.1 [10.3.0.1]
4 35 ms 35 ms 34 ms 201-174-24-213.transtelco.net [201.174.24.213]
5 * * * Timeout
25 * * * Timeout

Failed

Hop Time Time Time Target (Vancouver Host)
1 <1 ms <1 ms <1 ms 66.199.175.25 [66.199.175.25]
2 4 ms 1 ms 1 ms 64.69.82.233 [64.69.82.233]
3 <1 ms <1 ms <1 ms 216.187.89.90 [216.187.89.90]
4 * * * Timeout
25 * * * Timeout

Failed

Mesarthim
Jun 29, 2014, 03:15 AM
The infinite loop I've yet to see a change in. Doesn't really matter to me until PSO2es is back up.

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

1 1 ms 1 ms 1 ms 192.168.1.1
2 34 ms 32 ms 29 ms cpe-98-150-184-1.hawaii.res.rr.com
3 13 ms 15 ms 25 ms tge7-3.klaohias03h.hawaii.rr.com
4 16 ms 15 ms 25 ms
5 19 ms 23 ms 20 ms
6 69 ms 66 ms 67 ms agg31.lsancarc01r.socal.rr.com [72.129.45.0]
7 73 ms 67 ms 67 ms agg10.tustcaft01r.socal.rr.com [66.75.161.48]
8 69 ms 72 ms 70 ms agg1.chwocadq02r.socal.rr.com [72.129.25.3]
9 74 ms 71 ms 72 ms agg10.chwocadq01r.socal.rr.com [72.129.25.4]
10 71 ms 67 ms 68 ms agg24.lsancarc01r.socal.rr.com [72.129.25.0]
11 70 ms 70 ms 81 ms agg10.tustcaft01r.socal.rr.com [66.75.161.48]
12 74 ms 74 ms 76 ms agg1.chwocadq02r.socal.rr.com [72.129.25.3]
13 76 ms 75 ms 74 ms agg10.chwocadq01r.socal.rr.com [72.129.25.4]
14 73 ms 71 ms 76 ms agg24.lsancarc01r.socal.rr.com [72.129.25.0]
15 85 ms 71 ms 77 ms agg10.tustcaft01r.socal.rr.com [66.75.161.48]
16 73 ms 76 ms 75 ms agg1.chwocadq02r.socal.rr.com [72.129.25.3]
17 84 ms 79 ms 79 ms agg10.chwocadq01r.socal.rr.com [72.129.25.4]
18 74 ms 76 ms 80 ms agg24.lsancarc01r.socal.rr.com [72.129.25.0]
19 76 ms 76 ms 75 ms agg10.tustcaft01r.socal.rr.com [66.75.161.48]
20 78 ms 81 ms 77 ms agg1.chwocadq02r.socal.rr.com [72.129.25.3]
21 81 ms 77 ms 79 ms agg10.chwocadq01r.socal.rr.com [72.129.25.4]
22 78 ms 79 ms 79 ms agg24.lsancarc01r.socal.rr.com [72.129.25.0]
23 89 ms 79 ms 80 ms agg10.tustcaft01r.socal.rr.com [66.75.161.48]
24 83 ms 91 ms 83 ms agg1.chwocadq02r.socal.rr.com [72.129.25.3]
25 85 ms 96 ms 82 ms agg10.chwocadq01r.socal.rr.com [72.129.25.4]
26 85 ms 88 ms 87 ms agg24.lsancarc01r.socal.rr.com [72.129.25.0]
27 81 ms 80 ms 83 ms agg10.tustcaft01r.socal.rr.com [66.75.161.48]
28 89 ms 83 ms 88 ms agg1.chwocadq02r.socal.rr.com [72.129.25.3]
29 84 ms 87 ms 84 ms agg10.chwocadq01r.socal.rr.com [72.129.25.4]
30 87 ms 83 ms 89 ms agg24.lsancarc01r.socal.rr.com [72.129.25.0]

TsukasaHiiragi
Jun 29, 2014, 03:18 AM
Hop Time Time Time Target (Toronto Host)
1 <1 ms <1 ms <1 ms 66.11.155.241 [66.11.155.241]
2 1 ms 1 ms 1 ms 66.11.145.82 [66.11.145.82]
3 <1 ms 1 ms <1 ms border2.ge1-11.reliantweb-5.tor001.pnap.net [70.42.26.121]
4 1 ms 1 ms 1 ms core1.te2-2-bbnet2.tor001.pnap.net [70.42.24.193]
5 17 ms 16 ms 17 ms 64.210.12.61 [64.210.12.61]
6 64 ms 74 ms 72 ms 124.215.192.113 [124.215.192.113]
7 74 ms 90 ms 74 ms pajbb001.kddnet.ad.jp [124.211.34.125]
8 168 ms 168 ms 168 ms otejbb205.int-gw.kddi.ne.jp [203.181.100.133]
9 204 ms 171 ms 169 ms cm-ote257.int-gw.kddi.ne.jp [118.155.197.180]
10 169 ms 169 ms 169 ms 125.29.25.94 [125.29.25.94]
11 173 ms 173 ms 173 ms 203.141.47.218 [203.141.47.218]
12 177 ms 177 ms 177 ms ae2.tnhcr02.idc.jp [158.205.134.14]
13 * * * Timeout
14 * * * Timeout
15 * * * Timeout
16 * * * Timeout
17 174 ms 174 ms 174 ms 158.205.188.253 [158.205.188.253]
18 184 ms 178 ms 178 ms lag3.l303.ta1.eg.idc.jp [158.205.188.250]
19 170 ms 170 ms 170 ms 158.205.104.60 [158.205.104.60]
20 177 ms 178 ms 177 ms 210.189.209.8 [210.189.209.8]

Success - with the data gathered so far, it is looking more and more like a routing issue with the NA Backbone.

TsukasaHiiragi
Jun 29, 2014, 03:24 AM
Hop Time Time Time Target (Edinburgh Host)
1 <1 ms <1 ms <1 ms a134-19-161-33.xtrahost.co.uk [134.19.161.33]
2 11 ms 11 ms 11 ms Vlan475.asr1.LBA1.gblx.net [64.215.181.165]
3 149 ms 149 ms 149 ms te6-2-10G.ar2.PAO2.gblx.net [67.16.148.66]
4 152 ms 149 ms 160 ms 124.215.192.113 [124.215.192.113]
5 151 ms 151 ms 151 ms pajbb002.kddnet.ad.jp [124.211.34.133]
6 248 ms 248 ms 268 ms otejbb206.int-gw.kddi.ne.jp [203.181.100.201]
7 243 ms 244 ms 244 ms cm-ote257.int-gw.kddi.ne.jp [118.155.197.52]
8 243 ms 244 ms 243 ms 125.29.25.94 [125.29.25.94]
9 245 ms 245 ms 245 ms 203.141.47.218 [203.141.47.218]
10 260 ms 260 ms 260 ms ae2.tnhcr02.idc.jp [158.205.134.14]
11 * * * Timeout
12 * * * Timeout
13 * * * Timeout
14 * * * Timeout
15 252 ms 251 ms 253 ms 158.205.188.253 [158.205.188.253]
16 262 ms 253 ms 252 ms lag3.l303.ta1.eg.idc.jp [158.205.188.250]
17 252 ms 252 ms 254 ms 158.205.104.60 [158.205.104.60]

Reached the JP Domain but didn't reach the host, same issue with the Sao Paulo host.

TsukasaHiiragi
Jun 29, 2014, 03:28 AM
Hop Time Time Time Target (Paris Host)
1 <1 ms * <1 ms vss-5b-6k.fr.eu [176.31.241.252]
2 1 ms 1 ms 1 ms rbx-g2-a9.fr.eu [178.33.100.117]
3 * 9 ms * fra-5-6k.fr.eu [91.121.131.202]
4 * * * Timeout
5 272 ms 275 ms 275 ms tyo-sa3-i.TYO.JP.NET.DTAG.DE [62.154.5.210]
6 272 ms 270 ms 270 ms as4725.ix.jpix.ad.jp [210.171.224.48]
7 273 ms 273 ms 273 ms STOrc-01Te0-4-0-2.nw.odn.ad.jp [143.90.149.45]
8 255 ms 256 ms 256 ms STOrw-53Te2-1.nw.odn.ad.jp [143.90.143.170]
9 311 ms 264 ms 264 ms 10.143090054.odn.ne.jp [143.90.54.10]
10 255 ms 258 ms 256 ms ae3-105.tnhcr01.idc.jp [158.205.192.109]
11 * * * Timeout
12 * * * Timeout
13 * * * Timeout
14 * * * Timeout
15 258 ms 258 ms 258 ms 158.205.188.253 [158.205.188.253]
16 264 ms 262 ms 258 ms lag3.l303.ta1.eg.idc.jp [158.205.188.250]
17 257 ms 257 ms 257 ms 158.205.104.60 [158.205.104.60]
18 257 ms 257 ms 257 ms 210.189.209.8 [210.189.209.8]

Success

TsukasaHiiragi
Jun 29, 2014, 03:32 AM
Not necessarily. As I said before, I can get all the way to Tokyo, but the server still rejects me:
[spoiler-box]Don't mind the font, I just had another idiotic theory that didn't work.

http://i.imgur.com/MVO9XUM.png[/spoiler-box]

Yes, you are right. Some of these hosts get all the way to Tokyo and then fail on the final hop which is 158.205.104.60 which seems to be Yahoo.JP

http://www.iplocationfinder.com/158.205.104.60

TsukasaHiiragi
Jun 29, 2014, 03:34 AM
Hop Time Time Time Target (Buenos Aires Host)
1 1 ms 1 ms <1 ms 190.105.238.1 [190.105.238.1]
2 4 ms 1 ms 1 ms host41.200.110.130.ifxnw.com.ar [200.110.130.41]
3 1 ms 1 ms 2 ms 250.254.61.190.host.ifxnetworks.com [190.61.254.250]
4 177 ms 197 ms 176 ms ge-2-1-0.ar3.eze1.gblx.net [64.211.83.217]
5 185 ms 179 ms 179 ms po6-20G.ar2.PAO2.gblx.net [67.16.131.222]
6 182 ms 189 ms 182 ms 124.215.192.113 [124.215.192.113]
7 184 ms 180 ms 181 ms pajbb002.int-gw.kddi.ne.jp [111.87.3.29]
8 289 ms 301 ms 287 ms otejbb206.int-gw.kddi.ne.jp [203.181.100.177]
9 283 ms 285 ms 283 ms cm-ote257.int-gw.kddi.ne.jp [118.155.197.180]
10 289 ms 290 ms 288 ms 125.29.25.94 [125.29.25.94]
11 284 ms 283 ms 285 ms 203.141.47.218 [203.141.47.218]
12 282 ms 281 ms 280 ms ae2.tnhcr02.idc.jp [158.205.134.14]
13 * * * Timeout
14 * * * Timeout
15 * * * Timeout
16 * * * Timeout
17 291 ms 289 ms 289 ms 158.205.188.253 [158.205.188.253]
18 289 ms 287 ms 286 ms lag3.l303.ta1.eg.idc.jp [158.205.188.250]
19 290 ms 290 ms 292 ms 158.205.104.60 [158.205.104.60]
20 299 ms 298 ms 299 ms 210.189.209.8 [210.189.209.8]

Success (I'll do a couple more since already collected a large amount of data)

TsukasaHiiragi
Jun 29, 2014, 03:41 AM
Hop Time Time Time Target (Tampa USA Host)
1 5 ms <1 ms <1 ms 66-232-106-193.static.hvvc.us [66.232.106.193]
2 9 ms <1 ms <1 ms 10.253.0.225 [10.253.0.225]
3 6 ms 6 ms 6 ms xe-7-2-0-63.mia10.ip4.tinet.net [77.67.77.145]
4 * * * Timeout
5 * * * Timeout
6 * * * Timeout
7 * * * Timeout
8 * * * Timeout
9 * * * Timeout
10 6 ms 6 ms 6 ms xe-7-2-0-63.mia10.ip4.tinet.net [77.67.77.145]
11 6 ms 6 ms 6 ms xe-7-2-0-63.mia10.ip4.tinet.net [77.67.77.145]
12 6 ms 6 ms 6 ms xe-7-2-0-63.mia10.ip4.tinet.net [77.67.77.145]
13 * * * Timeout
14 * * * Timeout
15 6 ms 6 ms 6 ms xe-7-2-0-63.mia10.ip4.tinet.net [77.67.77.145]
16 6 ms 6 ms 6 ms xe-7-2-0-63.mia10.ip4.tinet.net [77.67.77.145]
17 * * * Timeout
18 * * * Timeout
19 6 ms * * xe-7-2-0-63.mia10.ip4.tinet.net [77.67.77.145]
20 * 6 ms 6 ms xe-7-2-0-63.mia10.ip4.tinet.net [77.67.77.145]
21 6 ms 6 ms 6 ms xe-7-2-0-63.mia10.ip4.tinet.net [77.67.77.145]
22 * * * Timeout
23 * * * Timeout
24 * * * Timeout
25 * * 6 ms xe-7-2-0-63.mia10.ip4.tinet.net [77.67.77.145]

Another obvious infinite loop failure.

Neirene
Jun 29, 2014, 04:01 AM
pso2.jp [210.189.209.8] へのルートをトレースしています
経由するホップ数は最大 30 です:

1 <1 ms <1 ms <1 ms LIVEBOX [192.168.1.1]
2 22 ms 22 ms 37 ms XX.XX.XX.XX [hidden]
3 21 ms 21 ms 22 ms 10.255.244.73
4 25 ms 30 ms 30 ms 10.255.244.65
5 22 ms 22 ms 21 ms 10.34.192.22
6 23 ms 23 ms 23 ms 10.34.192.5
7 21 ms 45 ms 22 ms 10.34.34.2
8 22 ms 21 ms 22 ms 10.34.34.1
9 * 30 ms 25 ms 10.34.34.2
10 22 ms 22 ms 22 ms 10.34.34.1
11 100 ms 23 ms 22 ms 10.34.34.2
12 28 ms * 33 ms 10.34.34.1
13 23 ms 26 ms 23 ms 10.34.34.2
14 23 ms 32 ms 31 ms 10.34.34.1
15 22 ms 23 ms 24 ms 10.34.34.2
16 22 ms 23 ms 28 ms 10.34.34.1
17 24 ms 23 ms 22 ms 10.34.34.2
18 23 ms 23 ms 35 ms 10.34.34.1
19 24 ms 24 ms 34 ms 10.34.34.2
20 23 ms 24 ms 28 ms 10.34.34.1
21 23 ms 24 ms 23 ms 10.34.34.2
22 25 ms 26 ms 32 ms 10.34.34.1
23 23 ms * 24 ms 10.34.34.2
24 38 ms 23 ms 26 ms 10.34.34.1
25 36 ms 24 ms 23 ms 10.34.34.2
26 28 ms 24 ms 69 ms 10.34.34.1
27 23 ms 24 ms 24 ms 10.34.34.2
28 26 ms 23 ms 24 ms 10.34.34.1
29 25 ms 24 ms 24 ms 10.34.34.2
30 24 ms 24 ms 24 ms 10.34.34.1

トレースを完了しました。


ISP: Orange
Country: Spain

KakuRoze
Jun 29, 2014, 04:31 AM
Tracing route to 210.189.208.121 over a maximum of 30 hops (Persumably Ship 09's IP)

1 7 ms 7 ms 9 ms ***.bredband.comhem.se [***]
2 orb-bbr-2-be20-10.net.comhem.se [213.200.164.143] reports: Destination net
unreachable.

Trace complete.


Tracing route to 210.189.209.8 over a maximum of 30 hops

1 9 ms 9 ms 7 ms ***.bredband.comhem.se [***]
2 * orb-bbr-2-be20-10.net.comhem.se [213.200.164.143] reports: Destin
ation net unreachable.

Trace complete.

When using SoftEther:

Tracing route to 210.189.208.121 over a maximum of 30 hops

1 331 ms 337 ms 319 ms 10.211.254.254
2 314 ms 390 ms 372 ms 192.168.254.254
3 338 ms 349 ms 356 ms datacenter8gw.softether.co.jp [114.160.71.145]
4 360 ms 383 ms 385 ms 118.23.8.160
5 385 ms 395 ms 394 ms 118.23.10.5
6 369 ms 363 ms 406 ms 222.146.43.241
7 470 ms 361 ms 421 ms 122.1.246.181
8 408 ms 413 ms 441 ms 60.37.27.89
9 365 ms 429 ms 411 ms 210.163.230.238
10 419 ms 407 ms 384 ms ae-11.r24.tokyjp05.jp.bb.gin.ntt.net [61.213.162
.165]
11 371 ms 372 ms 402 ms ae-1.r00.tokyjp01.jp.bb.gin.ntt.net [129.250.5.9
3]
12 388 ms 377 ms 401 ms xe-0-4-0-8.r01.tokyjp01.jp.ce.gin.ntt.net [61.21
3.161.6]
13 419 ms 372 ms 387 ms ae3-105.tnhcr02.idc.jp [158.205.192.113]
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * 382 ms 415 ms 158.205.188.253
19 375 ms 372 ms 388 ms lag3.l303.ta1.eg.idc.jp [158.205.188.250]
20 379 ms 382 ms 369 ms 158.205.104.60
21 386 ms 370 ms 387 ms 210.189.208.121
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.

Rayden
Jun 29, 2014, 05:27 AM
Here's mine, with Virgin Media:


>tracert pso2.jp

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

1 7 ms 4 ms 4 ms redacted.cable.virginm.net [redacted IP]
2 * * * Request timed out.
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
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.

Maenara
Jun 29, 2014, 05:40 AM
Around the world in 30 tracerts.

CircinusPrime
Jun 29, 2014, 06:01 AM
Left is from the Netherlands, right is from BT Infinity (UK)
[spoiler-box]http://puu.sh/9P4NS/ce855ef821.jpg[/spoiler-box]

Polantaris
Jun 29, 2014, 07:12 AM
I'm still testing, so far I'm 0/3 for the NA hosts I'm using.

Can I ask what the IP you specify is?

I tried just "tracert www.pso2.jp", and it stopped at some random Verizon server, which is definitely wrong...but I can connect to pso2.jp as well, so I'm definitely not being blocked. I just want to know how it ends up, what it goes through, etc. It only goes through 11 hops, too, so I'm not hitting the default cap or anything like that.

Shinamori
Jun 29, 2014, 07:23 AM
Did a tracert from my gs5
I have sprint. Timed out. Did a ping test and 100% packet loss.

PrinceBrightstar
Jun 29, 2014, 08:32 AM
Let me clear something up. Just because you get a timeout it doesn't mean there's an issue. If it progresses after that it simply means that server doesn't respond to ping requests which is what a tracert does.

kurisutina
Jun 29, 2014, 09:38 AM
I'm able to connect from the US using Verizon in Columbia, Maryland [spoiler-box]http://puu.sh/9PguW/237e97a2e7.png[/spoiler-box]

Macman
Jun 29, 2014, 03:10 PM
From a few days ago:
[SPOILER-BOX]http://i.imgur.com/2rarF0q.png

http://i.imgur.com/o9ZbB8t.png[/SPOILER-BOX]

Also note that I did it to pso2.swiki.jp as well and took the same route for the first 3 hops, and went through a bunch more AT&T routers after that before eventually reaching Japan. It's most likely either the talked about anti-DDoS measures or an unpropagated route due to a network change at Sega.

KakuRoze
Jul 2, 2014, 03:10 PM
I have called my ISP and they say they can't even reach the servers themselves, so my and my friends guess currently is that Sega has demanded that their ISP send out a command using the RIP routing protocol which tells all other routers in a network to classify that one or a range as dead and not even try to route packages to it, just drop them as fast as possible, then certain IPs have been told to reestablish communications, thus why some can access the services and most cannot.

My understanding of low level networking is marginal at best, but this problem can most likely only be solved by Sega or Sega's ISP, your regular ISPs probably dont even know the link have been broken or what to do about it.

So just have faith and please do correct me if I'm wrong about something