AnsweredAssumed Answered

Why is routing to OVH so terrible

Question asked by dpsi on Nov 4, 2016
Latest reply on Jan 3, 2017 by dpsi

Routing to OVH (AS 16276) is very poor. For some reason Shaw doesn't use it's own network to route anything across the country. This promotional material from Shaw is very misleading http://assets.aws.shawbusiness.ca/uploadedimages/shawbusiness/images/wholesale/wholesale-map-big-update.png?n=6552 Why advertise such a network if it's not even being used as implied?

Routing to OVH in Montreal or in Amsterdam results in high latency.

3 10 0 11.08 25.62 18.44 rc1bb-tge0-9-0-1-1.vc.shawcable.net [64.59.157.217]

4 10 0 19.17 30.90 23.31 rc1wt-be90.wa.shawcable.net [66.163.76.66]

5 10 0 15.65 26.14 20.03 six.sea.wa.us.ovh.net [206.81.80.214]

6 10 0 32.19 43.09 38.10 po3.snj-2-6k.ca.us [178.32.135.162]

7 10 0 79.07 94.75 84.78 po5.pal-1-6k.ca.us [198.27.73.249]

8 10 0 79.13 87.68 82.96 be100-1236.chi-5-a9.il.us [198.27.73.184]

9 10 0 92.13 125.46 101.10 be10-1313.bhs-g2-a9.qc.ca [198.27.73.198]

10 10 0 94.07 105.55 99.79 vac3-0-a9.qc.ca.vaccum [198.27.73.241]

11 10 0 92.67 109.48 101.82 vac3-1-n7.qc.ca.firewall [198.27.73.242]

12 10 0 94.14 108.04 98.24 vac3-2-n7.qc.ca [198.27.73.235]

13 10 0 82.83 97.54 89.75 vac3-3-n7.qc.ca [198.27.73.237]

14 10 100 0 0 0 [-]

15 10 0 92.93 165.45 104.55 po5.bhs-3b-6k.qc.ca [198.27.73.16]

16 10 0 92.82 103.35 98.20 [192.95.32.93]

Shaw is not picking the optimal path for transit. Since Shaw can't guarantee the quality beyond it's own network, why not do as much of the transit on Shaw's own network. Unless of course Shaw's network isn't as great as they say it is. Telus, Bell and TekSavvy all peer with OVH, why can't Shaw?

Outcomes