Community Forum

Reporting a routing issue?

Xfinity Forum Archive
About the archive project

Xfinity Forum Archive...

This is an archived section of the community.

Content in this area has been identified as outdated or irrelevant.

This change was done in an effort to make the forum easier to use and to keep only the most helpful and recent content active.

Post your questions in the Xfinity Community

New Poster

Reporting a routing issue?

What's the proper place to report routing problems?  A site I follow has just moved from Bluehost to Dreamhost, and I've found that there's a routing issue between my Xfinity home connection and parts of the Dreamhost network.  Comparing MTRs between my home connection and one of my Linode servers to Dreamhost, the problem is probably closer to Dreamhost, but, of course, I'm not a Dreamhost customer.  Somewhere out there is a Xfinity network engineer who'd probably be interested in the problem report (so he can fix it), but how do I get the problem report there?

Expert

Re: Reporting a routing issue?

This is primarily a customer peer forum, and I'm not an employee but perhaps posting the output of a trace route to the site may reveal a clue ?


I am not a Comcast Employee.
I am a Customer Expert volunteering my time to help other customers here in the Forums.
We ask that you post publicly so people with similar questions may benefit from the conversation.
Was your question answered? Mark the post as Best Answer!
New Poster

Re: Reporting a routing issue?

I was hoping there was a way to get the problem more directly to network admins, but....

 

I prefer MTR to traceroute, so:

 

From a host in my home network, in Marietta, GA:

 

 

oloryn@rivendell:~$ mtr -w sbcvoices.com
Start: 2018-06-04T23:53:57-0400
HOST: rivendell                                         Loss%   Snt   Last   Avg  Best  Wrst StDev
  1.|-- eriador.ln.benshome.net                            0.0%    10    5.3   5.3   1.8  10.0   2.7
  2.|-- 96.120.4.213                                       0.0%    10   11.9  15.5  11.9  20.4   2.9
  3.|-- xe-5-1-0-sur01.B2marietta.ga.atlanta.comcast.net   0.0%    10   18.8  17.3  10.7  34.5   6.8
  4.|-- et-12-0-1-ar01.b0atlanta.ga.atlanta.comcast.net    0.0%    10   25.1  19.4  12.8  29.6   5.3
  5.|-- be-7725-cr02.56marietta.ga.ibone.comcast.net       0.0%    10   21.5  22.5  13.3  30.1   4.6
  6.|-- be-11440-pe01.56marietta.ga.ibone.comcast.net      0.0%    10   28.1  19.5  10.4  28.1   6.0
  7.|-- 50.242.148.190                                     0.0%    10   24.6  22.5  13.2  34.0   7.2
  8.|-- be2848.ccr42.atl01.atlas.cogentco.com              0.0%    10   18.2  19.7  12.8  29.8   5.9
  9.|-- be2736.ccr42.ord01.atlas.cogentco.com              0.0%    10   47.7  35.7  31.7  47.7   4.6
 10.|-- be2832.ccr22.mci01.atlas.cogentco.com              0.0%    10   44.3  43.9  40.0  50.3   3.8
 11.|-- be3036.ccr22.den01.atlas.cogentco.com              0.0%    10   60.8  59.7  54.1  66.4   3.6
 12.|-- be3038.ccr21.slc01.atlas.cogentco.com              0.0%    10   67.8  67.7  65.1  71.4   1.6
 13.|-- be2085.ccr21.sea02.atlas.cogentco.com              0.0%    10   83.9  85.5  80.9  90.1   3.2
 14.|-- be2083.ccr21.sea01.atlas.cogentco.com              0.0%    10   80.1  83.5  79.1  88.2   3.3
 15.|-- be2671.rcr21.pdx01.atlas.cogentco.com              0.0%    10   97.0  93.6  85.5  99.3   4.4
 16.|-- te0-0-1-3.nr11.b069367-0.pdx01.atlas.cogentco.com  0.0%    10   93.5  95.0  91.6  99.4   2.6
 17.|-- ???                                               100.0    10    0.0   0.0   0.0   0.0   0.0

 

For comparison, from one of my Linode servers, in their Atlanta datacenter

 

 

oloryn@shire:~⟫ mtr -w sbcvoices.com
Start: Mon Jun  4 23:58:28 2018
HOST: shire                                             Loss%   Snt   Last   Avg  Best  Wrst StDev
  1.|-- 23.92.28.3                                         0.0%    10    0.6   0.7   0.6   0.9   0.0
  2.|-- 74.207.239.12                                      0.0%    10    0.7   0.8   0.7   0.9   0.0
  3.|-- be4825.ccr41.atl04.atlas.cogentco.com              0.0%    10    1.1   1.1   1.0   1.9   0.0
  4.|-- be2847.ccr41.atl01.atlas.cogentco.com              0.0%    10    0.9   1.0   0.9   1.3   0.0
  5.|-- be2735.ccr41.ord01.atlas.cogentco.com              0.0%    10   18.4  18.3  18.1  18.6   0.0
  6.|-- be2831.ccr21.mci01.atlas.cogentco.com              0.0%    10   30.0  30.2  30.0  30.4   0.0
  7.|-- be3035.ccr21.den01.atlas.cogentco.com              0.0%    10   42.0  41.8  41.5  42.0   0.0
  8.|-- be3037.ccr21.slc01.atlas.cogentco.com              0.0%    10   51.9  52.0  51.8  52.2   0.0
  9.|-- be3284.ccr22.sea02.atlas.cogentco.com              0.0%    10   72.3  72.4  72.3  72.5   0.0
 10.|-- be3055.ccr22.sea01.atlas.cogentco.com              0.0%    10   72.4  72.4  72.4  72.6   0.0
 11.|-- be2670.rcr21.pdx01.atlas.cogentco.com              0.0%    10   76.1  76.1  76.0  76.2   0.0
 12.|-- te0-0-1-3.nr11.b069367-0.pdx01.atlas.cogentco.com  0.0%    10   76.9  76.8  76.7  76.9   0.0
 13.|-- 38.122.20.226                                      0.0%    10   68.9  69.1  68.9  70.2   0.0
 14.|-- pdx1-cr-2.sd.dreamhost.com                         0.0%    10   69.0  69.0  68.9  69.1   0.0
 15.|-- pdx1-a3u27-acc.sd.dreamhost.com                    0.0%    10   72.5  70.4  69.4  72.5   0.8
 16.|-- apache2-xenon.forestgrove.dreamhost.com            0.0%    10   69.0  68.9  68.9  69.0   0.0
oloryn@shire:~⟫

 

 

Note that both paths go to te0-0-1-3.nr11.b069367-0.pdx01.atlas.cogentco.com.  From my Xfinity address, it stops there, from the Linode address, it goes on.  This could be a block on my home ip address, or a block on some section of Xfinity's address space, a bad route for the block my home ip address is in on the edge router for Dreamhosts's network, and more.  This is more likely to be a problem at Dreamhosts end, but I'm not their customer.  An Xfinity network engineer will have tools I don't have to narrow down the cause of the problem.  If the problem is a block on a section of Xfinity's address space,  or a bad route for a section of Xfinity's addess space, then it's a concern for more than just me.  In any case, an Xfinity network engineer is likely to carry more weight with a Dreamhost network engineer than me, some random guy out on the internet.  I may have to end up trying to figure out contacting Dreamhost's network guys, but I figure since I'm Xfinity's customer, I should start there.

 

Ben