<div dir="ltr"><div>fwiw, <br></div><div><br></div><div>This shows up in an interesting way looking at the v4 vs. v6 paths for this. I'm also coming from Shaw in Western Canada (BC).</div><div><br></div><div>The v6 path heads from Shaw through to a quick handoff to 1299 via Seattle and then down the west coast:</div><div><br></div><div> Packets Pings<br> Host Loss% Snt Drop Last Avg Best Wrst StDev Jttr<br> 1. AS6327 2604:3d08:427f:3c03:2e0:67ff:fe22:3565 0.0% 254 0 2.7 2.8 2.1 7.0 0.4 0.2<br> 2. AS6327 2604:3d08:1:2::1 0.0% 254 0 17.7 15.1 10.5 44.8 3.5 4.1<br> 3. AS6327 2604:3d00:f040::186 35.6% 254 90 14.9 15.4 8.8 25.6 2.5 0.4<br> 4. (waiting for reply)<br> 5. (waiting for reply)<br> 6. (waiting for reply)<br> 7. AS6327 2001:4e8:0:8150::2 18.1% 254 46 22.1 22.8 18.7 85.9 5.3 0.1<br> 8. AS6327 2001:4e8:0:80b4::1 16.9% 254 43 22.5 21.9 16.5 90.5 5.6 1.2<br> 9. AS1299 <a href="http://sea-b2-link.ip.twelve99.net">sea-b2-link.ip.twelve99.net</a> 88.9% 254 225 16.4 21.3 16.4 26.6 2.2 5.2<br>10. AS1299 <a href="http://sjo-b23-v6.ip.twelve99.net">sjo-b23-v6.ip.twelve99.net</a> 0.0% 254 0 45.0 41.4 34.3 65.2 3.6 5.2<br>11. AS1299 <a href="http://lax-b23-v6.ip.twelve99.net">lax-b23-v6.ip.twelve99.net</a> 0.0% 254 0 46.1 48.3 42.7 90.8 5.1 0.9<br>12. AS1299 <a href="http://las-b24-link.ip.twelve99.net">las-b24-link.ip.twelve99.net</a> 73.4% 253 185 46.6 49.5 42.6 107.6 10.1 0.0<br>13. AS1299 <a href="http://atlantic-ic336064-las-b24.ip.twelve99-cust.net">atlantic-ic336064-las-b24.ip.twelve99-cust.net</a> 0.0% 253 0 49.9 54.0 48.2 91.2 5.1 0.9<br>14. AS29838 2607:f108:d01:8::4 0.0% 253 0 47.8 50.4 44.3 71.5 3.9 1.6<br>15. AS25795 <a href="http://orthanc.ca">orthanc.ca</a> 0.0% 253 0 50.8 48.4 42.3 83.7 3.6 1.0</div><div><br></div><div>Whereas the v4 path heads east to Chicago for a handoff between Shaw and "Atlantic Metro" (looks like "<a href="https://www.peeringdb.com/org/9314">365 Data Centers</a>"?) before coming back west:</div><div><br></div><div> Packets Pings<br> Host Loss% Snt Drop Last Avg Best Wrst StDev Jttr<br> 1. AS??? 10.128.0.65 0.0% 270 0 2.7 2.8 2.0 4.4 0.3 0.7<br> 2. AS6327 70.78.192.1 0.0% 270 0 14.1 14.9 9.0 29.1 2.7 0.1<br> 3. AS6327 <a href="http://rc1bb-be131-1.vc.shawcable.net">rc1bb-be131-1.vc.shawcable.net</a> 0.0% 270 0 15.1 15.5 10.3 36.3 3.1 0.6<br> 4. AS6327 24.244.60.85 0.0% 269 0 21.3 16.9 12.5 35.7 3.3 4.8<br> 5. AS6327 24.83.252.130 27.1% 269 73 17.3 16.8 10.4 54.2 3.7 0.8<br> 6. AS6327 <a href="http://rc1bb-be214.vc.shawcable.net">rc1bb-be214.vc.shawcable.net</a> 0.0% 269 0 15.9 16.7 10.7 90.1 5.1 0.9<br> 7. AS6327 <a href="http://rc3so-be6-1.cg.shawcable.net">rc3so-be6-1.cg.shawcable.net</a> 0.0% 269 0 26.1 28.3 23.1 95.7 4.8 7.9<br> 8. AS6327 66.163.71.42 27.2% 269 73 28.5 28.8 23.7 40.4 2.3 0.2<br> 9. AS6327 <a href="http://rc4ec-be13.il.shawcable.net">rc4ec-be13.il.shawcable.net</a> 0.0% 269 0 57.3 57.2 51.9 77.8 2.7 1.2<br>10. AS46887 <a href="http://equinix-ch2.cr2.ord1.amcbb.net">equinix-ch2.cr2.ord1.amcbb.net</a> 0.0% 269 0 54.5 57.7 52.5 94.4 4.4 0.8<br>11. AS29838 <a href="http://ae1-4.cr1.ord1.atlanticmetro.net">ae1-4.cr1.ord1.atlanticmetro.net</a> 0.0% 269 0 56.4 64.0 51.4 166.3 18.7 0.9<br>12. AS29838 <a href="http://ve521.cr2.lax0.atlanticmetro.net">ve521.cr2.lax0.atlanticmetro.net</a> 0.0% 269 0 109.1 128.4 105.3 472.6 42.3 0.3<br>13. AS29838 <a href="http://xe-0-0-3-0.cr2.lax2.atlanticmetro.net">xe-0-0-3-0.cr2.lax2.atlanticmetro.net</a> 0.0% 269 0 107.9 109.8 103.8 166.1 5.3 0.2<br>14. AS29838 <a href="http://ae3-4.cr2.lax3.atlanticmetro.net">ae3-4.cr2.lax3.atlanticmetro.net</a> 0.0% 269 0 107.1 109.5 105.5 171.7 4.5 9.1<br>15. AS29838 <a href="http://arpnetworks-dmarc.lax3.atlanticmetro.net">arpnetworks-dmarc.lax3.atlanticmetro.net</a> 0.0% 269 0 107.9 110.2 105.0 187.6 5.7 0.5<br>16. AS25795 <a href="http://orthanc.ca">orthanc.ca</a> 0.0% 269 0 105.8 106.5 100.9 142.7 3.1 0.4</div><div><br></div><div>My guess would be the scenic route via Chicago is probably based on some of "Atlantic Metro's" routing policy on the v4 end, or quite possibly some of Shaw's "selective" routing policy cutting off a more direct path through Seattle or e.g. SIX.<br></div><div><div><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div dir="ltr"><font face="monospace"><br></font></div><div dir="ltr"><span style="font-family:arial,sans-serif">-- </span></div><div dir="ltr"><span style="font-family:arial,sans-serif">Hugo Slabbert</span></div><div dir="ltr"><span style="font-family:arial,sans-serif"><br></span></div><div dir="ltr"><span style="font-family:arial,sans-serif;color:rgb(153,153,153)">I
would like to acknowledge that the land on which I work and make my
home is the traditional and unceded territory of Coast Salish Peoples,
specifically the Kwantlen, Semiahmoo, and other Stó:lō Nations.</span><span style="font-family:arial,sans-serif;color:rgb(153,153,153)"><i><br></i></span></div></div></div></div></div></div></div></div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Jan 15, 2024 at 12:29 PM Lyndon Nerenberg (VE7TFX/VE6BBM) via Outages <<a href="mailto:outages@outages.org">outages@outages.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">I didn't have mtr installed on those hosts. The path is definitely<br>
asym: 17 hops YVR-LAX, 10 hops coming back. But both ways the<br>
traffic routes through Chicago, giving me those spectacular 100ms<br>
RTTs :-P<br>
<br>
I ran several traceroutes from the YVR side, and they all pointed<br>
to Calgary as the choke point. But whatever it was has cleared up<br>
now.<br>
<br>
.--lyndon<br>
_______________________________________________<br>
Outages mailing list<br>
<a href="mailto:Outages@outages.org" target="_blank">Outages@outages.org</a><br>
<a href="https://puck.nether.net/mailman/listinfo/outages" rel="noreferrer" target="_blank">https://puck.nether.net/mailman/listinfo/outages</a><br>
</blockquote></div>