Community Forum

Issues with routes going through XO Communications (xo.net)

Frequent Visitor

Issues with routes going through XO Communications (xo.net)

Apparently, there is still an issue with Comcast and XO Communications.  I have not been able to access a site that Comcast apparently routes through XO.

Tracing route to radiosurvivor.com [208.113.144.94]
over a maximum of 30 hops:

Tracing route to radiosurvivor.com [208.113.144.94]
over a maximum of 30 hops:

  1    <1 ms     1 ms     1 ms  10.0.0.1
  2    14 ms    11 ms    12 ms  XXX.XXX.XXX.XXX
  3    15 ms    10 ms    15 ms  xe-1-0-2-sur02.salisbury.md.bad.comcast.net [68.85.147.77]
  4    11 ms    14 ms    10 ms  ae-2-0-sur01.salisbury.md.bad.comcast.net [68.87.128.21]
  5    12 ms    17 ms    15 ms  ae-41-ar01.capitolhghts.md.bad.comcast.net [68.87.136.185]
  6    20 ms    20 ms    21 ms  be-33657-cr02.ashburn.va.ibone.comcast.net [68.86.90.57]
  7    16 ms    18 ms    24 ms  be-10130-pe04.ashburn.va.ibone.comcast.net [68.86.82.214]
  8    40 ms    41 ms    50 ms  50.242.151.190
  9    19 ms    17 ms    20 ms  207.88.14.164.ptr.us.xo.net [207.88.14.164]
 10    20 ms    21 ms    15 ms  207.88.14.181.ptr.us.xo.net [207.88.14.181]

If I try this same tracert from another provider, it works:

traceroute to radiosurvivor.com (208.113.144.94), 30 hops max, 60 byte packets
 1  107.XXX.XX.XXX (107.XXX.XX.XXX)  5.400 ms  5.377 ms 107.XXX.XX.XXX (107.XXX.XX.XXX)  0.266 ms
 2  138.197.248.170 (138.197.248.170)  0.798 ms 138.197.248.172 (138.197.248.172)  0.775 ms 138.197.248.162 (138.197.248.162)  0.720 ms
 3  ce-0-4-0-3.r08.nycmny01.us.bb.gin.ntt.net (157.238.179.153)  0.446 ms  0.420 ms  0.823 ms
 4  ae-2.r25.nycmny01.us.bb.gin.ntt.net (129.250.3.97)  0.602 ms ae-3.r25.nycmny01.us.bb.gin.ntt.net (129.250.6.208)  0.555 ms  0.562 ms
 5  * * *
 6  ae-7.r06.asbnva02.us.bb.gin.ntt.net (129.250.2.121)  6.567 ms  6.481 ms ae-1.r05.asbnva02.us.bb.gin.ntt.net (129.250.2.20)  5.494 ms
 7  ae-1.a03.asbnva02.us.bb.gin.ntt.net (129.250.5.214)  6.421 ms ae-0.a03.asbnva02.us.bb.gin.ntt.net (129.250.5.194)  5.957 ms  6.676 ms
 8  ae-0.dreamhost.asbnva02.us.bb.gin.ntt.net (129.250.196.242)  5.870 ms  33.576 ms  33.527 ms
 9  ip-208-113-156-8.dreamhost.com (208.113.156.8)  8.189 ms  7.514 ms  7.774 ms
10  ip-208-113-156-77.dreamhost.com (208.113.156.77)  6.441 ms  6.403 ms  6.377 ms
11  amanonwine.com (208.113.144.94)  6.318 ms  6.525 ms  6.005 ms

 

 

Gold Problem Solver

Re: Issues with routes going through XO Communications (xo.net)

I can reach the site  ("College Radio Watch: Was WBWC the First Student-Operated Radio Station?"). When one customer cannot reach a site but others can, it usually means something beyond Comcast's network is blocking that customer's public IP. You can look up your IP at https://www.google.com/search?q=IP.

My trace to radiosurvivor.com looks like:

C>tracert -4 radiosurvivor.com

Tracing route to radiosurvivor.com [208.113.144.94] over a maximum of 30 hops:

  1   8 ms   2 ms   1 ms router1 [192.168.1.1]
  2   9 ms   9 ms   9 ms 96.120.9.181 [96.120.9.181]
  3 11 ms 10 ms 11 ms te-0-6-0-0-sur02.york.pa.pitt.comcast.net [162.151.68.57]
  4 11 ms 11 ms 11 ms be-50-ar01.lancaster.pa.pitt.comcast.net [162.151.20.33]
  5 22 ms 20 ms 21 ms be-34-ar01.mckeesport.pa.pitt.comcast.net [69.139.168.141]
  6 28 ms 26 ms 26 ms be-7016-cr02.ashburn.va.ibone.comcast.net [68.86.91.25]
  7 25 ms 25 ms 25 ms be-10130-pe04.ashburn.va.ibone.comcast.net [68.86.82.214]
  8 24 ms 26 ms 26 ms 50.242.151.190
  9 27 ms 27 ms 25 ms 207.88.14.164.ptr.us.xo.net [207.88.14.164]
10 26 ms 26 ms 24 ms 207.88.14.181.ptr.us.xo.net [207.88.14.181]
11 25 ms 24 ms 24 ms 209.48.43.58
12 27 ms 25 ms 25 ms ip-208-113-156-4.dreamhost.com [208.113.156.4]
13 24 ms 27 ms 26 ms ip-208-113-156-77.dreamhost.com [208.113.156.77]
14 25 ms 25 ms 26 ms amanonwine.com [208.113.144.94]

Trace complete.

Comcast may be able to help you with this, but Radio Survivor's webhost might be able to do more.

Frequent Visitor

Re: Issues with routes going through XO Communications (xo.net)

Here's another one and I would appreicate an official response from a Comcast person before this one gets blown off:

 

Tracing route to jacl.org [173.236.245.139]
over a maximum of 30 hops:

  1    <1 ms    <1 ms     1 ms  10.0.0.1
  2    11 ms    12 ms    14 ms  96.120.105.157
  3    22 ms    12 ms    12 ms  xe-1-0-2-sur02.salisbury.md.bad.comcast.net [68.85.147.77]
  4    13 ms    12 ms    10 ms  ae-2-0-sur01.salisbury.md.bad.comcast.net [68.87.128.21]
  5    13 ms    29 ms    23 ms  ae-41-ar01.capitolhghts.md.bad.comcast.net [68.87.136.185]
  6    22 ms    22 ms    19 ms  be-33657-cr02.ashburn.va.ibone.comcast.net [68.86.90.57]
  7    16 ms    20 ms    13 ms  be-10130-pe04.ashburn.va.ibone.comcast.net [68.86.82.214]
  8    19 ms    18 ms    19 ms  50.242.151.190
  9    16 ms    26 ms    28 ms  207.88.14.164.ptr.us.xo.net [207.88.14.164]
 10    18 ms    17 ms    20 ms  207.88.14.181.ptr.us.xo.net [207.88.14.181]
 11     *        *        *     Request timed out.
 12     *        *        *     Request timed out.
From another box (not on comcast):
traceroute to jacl.org (173.236.245.139), 30 hops max, 60 byte packets
 1  107.170.XX.XXX (107.170.XX.XXX)  0.338 ms  0.324 ms  0.310 ms
 2  138.197.248.154 (138.197.248.154)  0.357 ms 138.197.248.148 (138.197.248.148)  0.355 ms 138.197.248.172 (138.197.248.172)  0.335 ms
 3  ce-0-4-0-3.r08.nycmny01.us.bb.gin.ntt.net (157.238.179.153)  0.823 ms ce-0-3-0-2.r07.nycmny01.us.bb.gin.ntt.net (157.238.179.69)  0.814 ms ce-0-4-0-3.r08.nycmny01.us.bb.gin.ntt.net (157.238.179.153)  0.830 ms
 4  ae-2.r25.nycmny01.us.bb.gin.ntt.net (129.250.3.97)  1.704 ms ae-3.r25.nycmny01.us.bb.gin.ntt.net (129.250.6.208)  1.694 ms *
 5  ae-9.r22.asbnva02.us.bb.gin.ntt.net (129.250.2.149)  5.978 ms  6.394 ms  6.281 ms
 6  ae-7.r06.asbnva02.us.bb.gin.ntt.net (129.250.2.121)  5.784 ms ae-1.r05.asbnva02.us.bb.gin.ntt.net (129.250.2.20)  5.410 ms  5.937 ms
 7  ae-0.a03.asbnva02.us.bb.gin.ntt.net (129.250.5.194)  5.716 ms  5.625 ms  7.230 ms
 8  ae-0.dreamhost.asbnva02.us.bb.gin.ntt.net (129.250.196.242)  5.286 ms  5.789 ms  5.802 ms
 9  ip-208-113-156-8.dreamhost.com (208.113.156.8)  7.859 ms  7.237 ms  7.215 ms
10  ip-208-113-156-73.dreamhost.com (208.113.156.73)  6.452 ms  6.219 ms  5.884 ms
11  ps550428.dreamhost.com (173.236.245.139)  5.740 ms  6.318 ms  6.228 ms
Frequent Visitor

Re: Issues with routes going through XO Communications (xo.net)


Tracing route to radio.macinmind.com [208.113.169.146]
over a maximum of 30 hops:

  1     1 ms     1 ms     2 ms  10.0.0.1
  2    13 ms    15 ms    11 ms  96.120.105.XXX
  3     9 ms    16 ms    11 ms  xe-1-0-2-sur02.salisbury.md.bad.comcast.net [68.85.147.77]
  4    14 ms    15 ms    11 ms  ae-2-0-sur01.salisbury.md.bad.comcast.net [68.87.128.21]
  5    16 ms    15 ms    20 ms  ae-41-ar01.capitolhghts.md.bad.comcast.net [68.87.136.185]
  6    18 ms    20 ms    18 ms  be-33657-cr02.ashburn.va.ibone.comcast.net [68.86.90.57]
  7    17 ms    17 ms    19 ms  be-10130-pe04.ashburn.va.ibone.comcast.net [68.86.82.214]
  8    20 ms    19 ms    16 ms  50.242.151.190
  9    19 ms    25 ms    14 ms  207.88.14.164.ptr.us.xo.net [207.88.14.164]
 10    21 ms    18 ms    16 ms  207.88.14.181.ptr.us.xo.net [207.88.14.181]
 11     *        *        *     Request timed out.
 12     *        *        *     Request timed out.
Frequent Visitor

Re: Issues with routes going through XO Communications (xo.net)

Aaaaand... here's another one...

Tracing route to fair.org [208.97.185.203]
over a maximum of 30 hops:

  1    <1 ms    <1 ms     1 ms  10.0.0.1
  2    13 ms    10 ms    14 ms  96.120.105.XXX
  3    15 ms    13 ms    14 ms  xe-1-0-2-sur02.salisbury.md.bad.comcast.net [68.85.147.77]
  4    17 ms    11 ms    16 ms  ae-2-0-sur01.salisbury.md.bad.comcast.net [68.87.128.21]
  5    16 ms    15 ms    15 ms  ae-41-ar01.capitolhghts.md.bad.comcast.net [68.87.136.185]
  6    16 ms    20 ms    19 ms  be-33657-cr02.ashburn.va.ibone.comcast.net [68.86.90.57]
  7    20 ms    19 ms    17 ms  be-10130-pe04.ashburn.va.ibone.comcast.net [68.86.82.214]
  8    22 ms    15 ms    20 ms  50.242.151.190
  9    44 ms    16 ms    21 ms  207.88.14.164.ptr.us.xo.net [207.88.14.164]
 10    23 ms    23 ms    19 ms  207.88.14.181.ptr.us.xo.net [207.88.14.181]
 11     *        *        *     Request timed out.
 12     *        *        *     Request timed out.
 13     *        *        *     Request timed out.
 14     *        *        *     Request timed out.
 15     *    
Gold Problem Solver

Re: Issues with routes going through XO Communications (xo.net)

As before, I can reach all 4 of the sites you posted using my Comcast Internet connection. I can post the traceroutes if you like (all 4 complete to the destination). Since all the sites appear to be hosted on DreamHost IPs, you may want to consider contacting DreamHost if you haven't already.

 

ARIN WhoIs info:

  jacl.org                      173.236.245.139  https://whois.arin.net/rest/net/NET-173-236-128-0-1/pft?s=173.236.245.139
  radiosurvivor.com         208.113.144.94   https://whois.arin.net/rest/net/NET-208-113-128-0-1/pft?s=208.113.144.94
  radio.macinmind.com  208.113.169.146  https://whois.arin.net/rest/net/NET-208-113-128-0-1/pft?s=208.113.169.146
  fair.org                        208.97.185.203   https://whois.arin.net/rest/net/NET-208-97-128-0-1/pft?s=208.97.185.203