From Bellingham, there is there really no peering point in Qwest’s backbone to Comcast? It seems preposterous that I takes me 102ms to ping 11 miles. I wish I could brag about biking that fast. But at least I do not have to bike to Florida to get to Ferndale:
traceroute to firewall.candelatech.com (70.89.124.249), 30 hops max, 60 byte packets 1 gateway (192.168.45.1) 0.951 ms 0.703 ms 0.590 ms 2 tukw-dsl-gw66.tukw.qwest.net (63.231.10.66) 23.762 ms 23.282 ms 22.912 ms 3 tukw-agw1.inet.qwest.net (71.217.186.9) 22.525 ms 22.756 ms 22.992 ms 4 nap-edge-04.inet.qwest.net (67.14.29.166) 104.071 ms 104.336 ms 104.139 ms 5 65.122.166.78 (65.122.166.78) 105.126 ms 105.112 ms 106.764 ms 6 be-10-cr01.miami.fl.ibone.comcast.net (68.86.82.114) 106.921 ms be-13-cr01.miami.fl.ibone.comcast.net (68.86.82.126) 105.262 ms 104.893 ms 7 be-15-cr01.ashburn.va.ibone.comcast.net (68.86.84.221) 106.538 ms 107.032 ms 106.481 ms 8 he-0-12-0-0-cr01.losangeles.ca.ibone.comcast.net (68.86.86.117) 111.232 ms 110.836 ms 110.693 ms 9 he-2-8-0-0-cr01.sanjose.ca.ibone.comcast.net (68.86.86.97) 111.653 ms 109.401 ms 109.044 ms 10 68.86.93.30 (68.86.93.30) 106.729 ms 106.942 ms 107.967 ms 11 be-41-sur02.ferndale.wa.seattle.comcast.net (69.139.164.30) 110.153 ms 110.399 ms 110.225 ms 12 te-1-0-0-ten01.ferndale.wa.seattle.comcast.net (68.87.206.242) 116.914 ms 117.572 ms 117.213 ms 13 c-50-135-136-13.hsd1.wa.comcast.net (50.135.136.13) 127.260 ms 154.153 ms 157.281 ms 14 * * *