This is a public Forum  public

Topic

    Jeffrey Apshkrum
    Bad internet route to California
    Topic posted September 16, 2017 by Jeffrey Apshkrum, tagged Internet 
    214 Views, 6 Comments
    Title:
    Bad internet route to California
    Content:

    I recently upgraded to the 175/25 Infinite service. I also use an online backup service called Backblaze. I was expecting to take advantage of the high upload rate but they stay far below what I would have expected. As a test I ran a traceroute to Backblaze's servers, which are located in Southern California. For some reason it appears that my data is going out to Toronto before heading to San Jose. Is that correct, and can this be fixed? The traceroute is below.

    traceroute to backblaze.com (162.244.57.11), 64 hops max, 72 byte packets

     1  pfsense (192.168.1.1)  2.825 ms  3.042 ms  1.982 ms

     2  207-47-165-130.sktn.static.sasknet.sk.ca (207.47.165.130)  9.421 ms  3.319 ms  4.631 ms

     3  207-47-191-249.ngai.static.sasknet.sk.ca (207.47.191.249)  7.797 ms  7.720 ms  8.567 ms

     4  142.165.0.114 (142.165.0.114)  37.107 ms  41.179 ms  42.265 ms

     5  ae0-117.cr0-tor1.ip4.gtt.net (216.221.157.73)  38.951 ms  39.542 ms  38.855 ms

     6  xe-8-1-2.cr0-sjc1.ip4.gtt.net (89.149.136.209)  98.899 ms  97.408 ms  98.690 ms

     7  ip4.gtt.net (173.205.44.34)  78.350 ms  111.141 ms  79.233 ms

     8  162.244.57.11.rdns.backblaze.com (162.244.57.11)  78.350 ms  78.601 ms  78.698 ms

     

    Comment

     

    • Jeffrey Apshkrum

      Can anyone in Sasktel Support look into this or let me know if I am just completely wrong about it?

       

      Thanks.

    • SaskTel Support

      Hi Jeffery, this certainly can happen.

      Once past our network, the 4th hop, routing is beyond our control.

    • Jeffrey Apshkrum

      That is somewhat true but you have choices with whom you peer with. For example if I trace the same route using a cell phone connection with Rogers the route goes west to Seattle, not east to Toronto. I would hope that Sasktel would see a bad route like this as a problem and take steps to fix it. I know your competitors would.

      1  172.20.10.1 (172.20.10.1)  0.632 ms  0.276 ms  0.252 ms

       2  * * *

       3  192.168.111.2 (192.168.111.2)  175.869 ms  215.127 ms  196.113 ms

       4  10.128.102.13 (10.128.102.13)  75.974 ms  42.966 ms  40.044 ms

       5  10.118.48.33 (10.118.48.33)  40.191 ms  39.207 ms  40.079 ms

       6  24.156.157.149 (24.156.157.149)  43.931 ms  47.094 ms  55.715 ms

       7  24.156.146.58 (24.156.146.58)  48.083 ms  42.632 ms  48.126 ms

       8  24.156.157.125 (24.156.157.125)  47.890 ms  46.474 ms  52.049 ms

       9  24.156.147.57 (24.156.147.57)  48.095 ms  47.098 ms  47.871 ms

      10  209.148.227.254 (209.148.227.254)  60.131 ms  85.967 ms  48.050 ms

      11  ix-xe-7-2-1-0.tcore1.00s-seattle.as6453.net (64.86.123.37)  52.061 ms  47.107 ms  47.998 ms

      12  64.86.123.146 (64.86.123.146)  55.911 ms  47.356 ms  48.014 ms

      13  xe-11-0-1.cr0-sjc1.ip4.gtt.net (141.136.111.194)  67.716 ms  67.450 ms  68.042 ms

      14  ip4.gtt.net (173.205.44.34)  67.901 ms  71.748 ms  67.937 ms

      15  162.244.57.11.rdns.backblaze.com (162.244.57.11)  67.911 ms  80.253 ms  71.502 ms

    • Jeffrey Apshkrum

      I even tested the route to www.vancouver.ca . The route is below. It goes to Toronto, Cleveland, Chicago, Kansas City, Denver, Salt Lake City, Seattle, then up to Vancouver. Honestly this is simply wrong. Not only is it a terrible route that adds a huge transit distance, you are allowing my traffic to cross an international border between 2 domestic endpoints. I understand it isn't always possible to keep domestic traffic in Canada, but I'd never expect my traffic between BC and Saskatchewan to go east, then through around 10 states, just to re-emerg in Canada. Something is wrong with your routing. I know some traffic can flow west since routing to www.calgary.ca doesn't show such a bad route. Please fix this and please respond.

       

      traceroute to vancouver.ca (199.175.219.1), 64 hops max, 72 byte packets

       1  pfsense (192.168.1.1)  4.665 ms  3.274 ms  3.145 ms

       2  207-47-165-130.sktn.static.sasknet.sk.ca (207.47.165.130)  894.228 ms  8.149 ms  6.084 ms

       3  207-47-191-249.ngai.static.sasknet.sk.ca (207.47.191.249)  7.691 ms  9.516 ms  7.909 ms

       4  142.165.0.114 (142.165.0.114)  39.245 ms  40.355 ms  40.968 ms

       5  te0-0-0-0.rcr11.b011027-3.yyz02.atlas.cogentco.com (38.122.70.65)  43.216 ms  41.808 ms  39.508 ms

       6  te0-0-0-30.ccr21.yyz02.atlas.cogentco.com (154.54.6.237)  39.561 ms  37.410 ms  39.577 ms

       7  be2993.ccr21.cle04.atlas.cogentco.com (154.54.31.225)  49.467 ms  47.793 ms  46.360 ms

       8  be2717.ccr41.ord01.atlas.cogentco.com (154.54.6.221)  56.452 ms  53.714 ms  53.044 ms

       9  be2831.ccr21.mci01.atlas.cogentco.com (154.54.42.165)  65.987 ms  63.444 ms  63.781 ms

      10  be3035.ccr21.den01.atlas.cogentco.com (154.54.5.89)  77.996 ms  80.070 ms  79.539 ms

      11  be3037.ccr21.slc01.atlas.cogentco.com (154.54.41.145)  67.007 ms  68.228 ms  70.138 ms

      12  be2085.ccr21.sea02.atlas.cogentco.com (154.54.2.197)  78.476 ms  74.108 ms  74.888 ms

      13  38.142.48.234 (38.142.48.234)  75.998 ms  68.082 ms  69.865 ms

      14  * * *

      15  208.181.97.22 (208.181.97.22)  71.754 ms  70.181 ms  72.061 ms

      16  gw.vancouver.ca (199.175.219.1)  73.679 ms  71.175 ms  70.972 ms

       

       

      traceroute to calgary.ca (208.98.229.39), 64 hops max, 72 byte packets

       1  pfsense (192.168.1.1)  3.659 ms  3.281 ms  3.031 ms

       2  207-47-165-130.sktn.static.sasknet.sk.ca (207.47.165.130)  9.983 ms  8.865 ms  8.782 ms

       3  207-47-191-249.ngai.static.sasknet.sk.ca (207.47.191.249)  7.903 ms  7.664 ms  7.859 ms

       4  142.165.60.186 (142.165.60.186)  33.886 ms  32.559 ms  33.041 ms

       5  142.165.60.189 (142.165.60.189)  33.333 ms  35.203 ms  32.059 ms

       6  142.165.0.118 (142.165.0.118)  30.614 ms  31.710 ms  33.221 ms

       7  pix-gw.shaw.ca (206.223.127.2)  30.508 ms  29.647 ms  30.147 ms

       8  rc3no-be11-1.cg.shawcable.net (66.163.72.69)  42.020 ms  41.032 ms  40.273 ms

       9  66.163.71.186 (66.163.71.186)  41.959 ms  41.481 ms  39.015 ms

      10  rx0so-city-of-calgary.cg.bigpipeinc.com (64.141.118.14)  39.402 ms  44.934 ms  41.082 ms

      11  * * *

      12  * * *

      13  rx0so-city-of-calgary.cg.bigpipeinc.com (64.141.118.14)  40.947 ms !X *  41.209 ms !X

    • Jeffrey Apshkrum

      Any comments from someone in Support?

    • Logan

      I checked into this for you with one of our technical guys, he explained a bunch of stuff that went over my head. This is what I took from our conversation.

      There are two potential routes that can be taken, one through Toronto, and one through Vancouver. SaskTel learns of a route to this 162.244.57.11 network via a peer that we have in Vancouver. 

      Unfortunately the provider that Backblaze is using (Unwired) has set their preference to accept traffic from our Vancouver peer as lower than from our peer in Toronto.

      We frequently evaluate all of our peering relationships to ensure the best experience for our customers. If another peer becomes available that is a more desired route to your destination, your traffic could end up taking the Vancouver path.

      You can see if they will change their path influences to make Vancouver the preferred path. This is beyond our control.

      That's everything I can give you, hope it helps