[Comcast] IP Block Confirmed - Now for the good news

[Atlantis419]

Sega is 100% in control of which traffic it's currently allowing to reach their services. It's neither Comcast nor level 3 the backbone. This was confirmed last maintenance when twc users were allowed to access the site and servers. If you don't know already both Comcast and twc both use the same exact backbone provider. We will all find out after this maintenance whether they will rotate in another isp and rotate out twc or whether they will block or unblock everyone.

[TaigaUC]

Still don't understand why people keep insisting that the problem is on our side, and that our ISPs are doing the blocking.
As I said, I have a friend on the same ISP as myself (same city) that can access the JP site no problem.
I checked both our traceroutes. They run through similar IPs, although not exactly the same.
On roughly the same jump, his trace gets to Japan. Mine times out. Not going to post the results here, for various reasons.

Besides, even if people call their ISPs and get "confirmation", the ISPs could be just as clueless about this whole thing as we are.
I've dealt with a few different ISPs, and they've all been full of shit. Say one thing, turns out to be something else after making everyone waste an assload of time.

[Faranth]

Still don't understand why people keep insisting that the problem is on our side, and that our ISPs are doing the blocking.
As I said, I have a friend on the same ISP as myself (same city) that can access the JP site no problem.
I checked both our traceroutes. They run through similar IPs, although not exactly the same.
On roughly the same jump, his trace gets to Japan. Mine times out. Not going to post the results here, for various reasons.

Besides, even if people call their ISPs and get "confirmation", the ISPs could be just as clueless about this whole thing as we are.
I've dealt with a few different ISPs, and they've all been full of shit. Say one thing, turns out to be something else after making everyone waste an assload of time.

+1 (〃￣ω￣〃ゞ

(couldn't phrase it better) (〃￣ω￣〃ゞ

[Sizustar]

Still don't understand why people keep insisting that the problem is on our side, and that our ISPs are doing the blocking.
As I said, I have a friend on the same ISP as myself (same city) that can access the JP site no problem.
I checked both our traceroutes. They run through similar IPs, although not exactly the same.
On roughly the same jump, his trace gets to Japan. Mine times out. Not going to post the results here, for various reasons.

Besides, even if people call their ISPs and get "confirmation", the ISPs could be just as clueless about this whole thing as we are.
I've dealt with a few different ISPs, and they've all been full of shit. Say one thing, turns out to be something else after making everyone waste an assload of time.

On Reddit, someone contacted their ISP, and thier ISP fixed it and now they can play.
http://www.reddit.com/r/PSO2/comment...rly_sympatico/

[martinmeegan]

And looking at the comments below that, someone else contacted the same ISP and theirs still doesn't work............

[Vandread]

See the thing is, if you follow the tracerts - most are ending in blackhole filters, mine for instance isn't even leaving my state. So the hop that is being filtered is either on the comcast network, or is the hop from comcast network to the Level3 network - unfortunately that information I don't have.

I don't have Comcast, but I have a fairly strong belief that my traffic (from the Netherlands) also routes through the Level 3 network. I reached out to my ISP earlier, and they'll be forwarding the information I gave them to their tech dept. I can't reach those guys directly, so yea... waiting game for me.

If it's indeed routed through Level 3 and they're the ones that have resorted to the black-hole, I'll post whatever happens from hereon out since it seems to impact you guys as well. We might have 2 shots at this now... hopefully.

[reaper527]

Sega is 100% in control of which traffic it's currently allowing to reach their services. It's neither Comcast nor level 3 the backbone.

i suggest you take a class on how the internet works, because this statement is flat out wrong. sega is NOT in 100% control of what traffic gets out of comcast or level 3. sega doesn't have any control over what traffic reaches their network, only what traffic they will discard once it actually reaches their network.

This was confirmed last maintenance when twc users were allowed to access the site and servers. If you don't know already both Comcast and twc both use the same exact backbone provider.

that didn't confirm anything. the only thing that it confirmed was that twc fixed their routing issues.

as far as using "the same exact backbone provider" goes, this is only partially true. comcast uses level3 exclusively. time warner signed on with level 3 to expand their own infrastructure. look at this tracert from a twc customer:

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]

note that it doesn't go through level 3's network at all. comcast however doesn't have the capability to do this, so they are still dead in the water.

[Ezodagrom]

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]

So...the last IP I can ping is the one right before SEGA servers... (158.205.104.60)



I knew I could reach JP IPs, but didn't know the last one I could reach was the one before PSO2...
Feels kinda like I can reach the door to a party, but can't get inside because I'm not invited. =w=;

[reaper527]

that's a bizarre one. i assume you die at the same point pinging the game server as well? (gs016.pso2gs.net)

[gigawuts]

So...the last IP I can ping is the one right before SEGA servers... (158.205.104.60)



I knew I could reach JP IPs, but didn't know the last one I could reach was the one before PSO2...
Feels kinda like I can reach the door to a party, but can't get inside because I'm not invited. =w=;

dats a pcool log

check mine out though

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

  1    <1 ms    <1 ms    <1 ms  somethingsomethingsomething
  2     9 ms     8 ms     8 ms  somethingsomethingsomething
  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.

Trace complete.