Yeah; it actually seems like this is a problem on TWC's end since there was a brief outage before this happened.Originally Posted by auxy
Yeah; it actually seems like this is a problem on TWC's end since there was a brief outage before this happened.
the brief outage could have just been them changing TWC changing something though =[
Could be some of their routers restarting and receiving the bad route that other ISPs have been getting? I dunno. Awfully bad timing on their part regardless, but yeah, there indeed was a nation-wide cable Internet outage less than an hour ago, so I'd say we just gotta sit tight until this stuff clears itself out.
* 98% of people like to put character progress in their signatures. If you're one of the 2% who doesn't, put this in your signature.
If you do a tracert to other japanese servers such as yahoo.jp you can see the route is no longer going through rr.com based servers anymore. Something rather major happened to our normal route to japan for some reason. I think the backbone TWC and brighthouse were going through might have went down.
This is probably related to Lizard Squad and their massive DDoS of Twitch.
possibly yeah, could not have had worse timing though
Do you have a tracert of yahoo.jp before this happened?
Where did it change in this tracert? (Deleted the first few hops) I'm assuming you're talking about route #7. I don't recognize this "Los Angeles" provider or any of the NTT providers.
tracert yahoo.jp
5 61 ms 63 ms 87 ms agg31.lsancarc01r.socal.rr.com [72.129.45.0]
6 58 ms 63 ms 60 ms bu-ether26.lsancarc0yw-bcr00.tbone.rr.com [66.109.6.212]
7 59 ms 57 ms 57 ms 107.14.17.250
8 57 ms 57 ms 57 ms ix-24-0.tcore1.LVW-Los-Angeles.as6453.net [66.110.59.81]
9 58 ms 108 ms 60 ms if-2-2.tcore2.LVW-Los-Angeles.as6453.net [66.110.59.2]
10 60 ms 58 ms 60 ms 64.86.252.134
11 60 ms 58 ms 58 ms ae-2.r20.lsanca03.us.bb.gin.ntt.net [129.250.2.229]
12 170 ms 171 ms * ae-6.r20.osakjp02.jp.bb.gin.ntt.net [129.250.4.39]
13 177 ms 171 ms 170 ms ae-4.r22.osakjp02.jp.bb.gin.ntt.net [129.250.6.188]
14 171 ms 172 ms 170 ms ae-1.a20.osakjp01.jp.ra.gin.ntt.net [61.200.80.130]
15 186 ms 174 ms 187 ms xe-5-1-0.a20.osakjp01.jp.ra.gin.ntt.net [61.200.82.38]
16 190 ms 187 ms 180 ms 124.83.252.242
17 194 ms 189 ms 196 ms 114.111.64.178
18 181 ms 190 ms 190 ms yjpn200.mobile.vip.kks.yahoo.co.jp [183.79.23.196]
* 98% of people like to put character progress in their signatures. If you're one of the 2% who doesn't, put this in your signature.
No, but I do have a tracert to pso2.jp from a reddit thread.
This is what it looked like before:
1 <1 ms <1 ms <1 ms 10.1.1.10 [router]
Hops 2-4 censored for my own privacy.
5 26 ms 31 ms 27 ms rdc-72-230-153-243.wny.east.twcable.com [72.230.153.243] [Regional TWC backbone]
6 31 ms 30 ms 32 ms be35.cr0.chi10.tbone.rr.com [107.14.19.104] [Chicago TWC backbone]
7 89 ms 90 ms 88 ms ae-6-0.cr0.sjc30.tbone.rr.com [66.109.6.14] [San Jose TWC backbone]
8 82 ms 83 ms 84 ms ae-0-0.cr0.sjc10.tbone.rr.com [66.109.6.8] [also San Jose TWC backbone]
9 89 ms 99 ms 87 ms bu-ether13.lsancarc0yw-bcr00.tbone.rr.com [66.109.6.7] [TWC backbone]
10 91 ms 86 ms 87 ms ae-0-0.cr0.lax30.tbone.rr.com [66.109.6.5] [Los Angeles TWC backbone]
11 224 ms 78 ms 80 ms ae2.pr1.lax10.tbone.rr.com [107.14.19.54] [also Los Angeles TWC backbone]
12 137 ms 84 ms 95 ms unk-426d075a.adelphiacom.net [66.109.7.90] [The name is a lie, this is really TWC's transpacific backbone]
13 82 ms 83 ms 80 ms lajbb001.kddnet.ad.jp [59.128.2.69] [from this point forward, these are all Japanese regional backbones]
14 204 ms 203 ms 186 ms otejbb205.int-gw.kddi.ne.jp [203.181.100.125]
15 192 ms 195 ms 194 ms jc-ote302.int-gw.kddi.ne.jp [118.155.197.179]
16 189 ms 187 ms 183 ms 106.187.28.202
17 * * * Request timed out.
18 184 ms 183 ms 184 ms 61.202.251.198
19 181 ms 181 ms 175 ms po14.ta1ag01.idc.jp [158.205.192.102]
20 195 ms 187 ms 186 ms lag3.l303.ta1.eg.idc.jp [158.205.188.250]
21 189 ms 201 ms 190 ms 158.205.104.60
22 178 ms 188 ms 176 ms 210.189.208.16 [AKA ship 2's server, our destination]
A further note, you can actually tracert to 158.205.104.60 and see that it's taking the same path as it does to yahoo.jp, as opposed to this path we see here.
Last edited by Fufufu; Aug 27, 2014 at 03:59 AM.
If I'm on the vita am I doomed? When I get to the ship select screen it just says all of them are in maintenance.
I can't tracert to this. It times out.
Posting Permissions
Reply With Quote
Connect With Us