Quote:
Originally Posted by Spudstr
You do realize that OVH's network consists of about 90% peering in EU and their US connectivity has been.. awful.
|
Connectivity to your place for example looks excellent:
Code:
traceroute to yellowfiber.com (67.23.123.226), 30 hops max, 40 byte packets
1 vss-3-6k.fr.eu (188.165.240.254) 1.038 ms * *
2 rbx-g2-a9.fr.eu (94.23.122.94) 1.872 ms 1.876 ms 1.872 ms
3 gsw-2-6k.fr.eu (91.121.131.214) 4.028 ms 4.006 ms *
4 gblx.as3549.fr.eu (213.186.32.129) 4.279 ms 4.286 ms 4.269 ms
5 po2-20G.ar6.DCA3.gblx.net (67.16.136.238) 86.253 ms 86.224 ms 86.224 ms
6 xe-3-0-3.ar1.iad1.us.nlayer.net (69.31.31.230) 95.617 ms 95.892 ms 95.873 ms
7 as40015.xe-6-0-0.ar1.iad1.us.nlayer.net (69.31.30.122) 83.671 ms 83.672 ms 83.661 ms
8 216.177.157.29 (216.177.157.29) 83.639 ms 83.672 ms 83.635 ms
9 te5-2.a00.rst.yellowfiber.net (216.177.148.146) 84.796 ms 84.856 ms 84.840 ms
10 67.23.123.226 (67.23.123.226) 90.418 ms 90.626 ms 90.624 ms
the first 4 hops within their infrastructure, oh look, hop 5 it's already in the US, the by 9 it's in your DC.
How does your traceroute to ovh.com look?
So far, I've tested 2 routes to the US and both have been excellent.
Any more?
Cos if not, your call of US connectivity being awful is well, wrong
--edit
go on then let's test some more:
Code:
traceroute to webair.com (209.200.29.36), 30 hops max, 40 byte packets
1 * * *
2 rbx-g2-a9.fr.eu (94.23.122.94) 0.846 ms 0.851 ms 0.846 ms
3 gsw-2-6k.fr.eu (91.121.131.214) 4.099 ms th1-1-6k.fr.eu (91.121.131.190) 4.098 ms *
4 gsw-1-6k.fr.eu (213.186.32.210) 59.756 ms * *
5 telia.as1299.fr.eu (213.251.130.82) 4.053 ms 4.300 ms 4.041 ms
6 prs-bb1-link.telia.net (80.91.247.50) 4.617 ms 4.583 ms prs-bb1-link.telia.net (80.91.251.113) 4.544 ms
7 nyk-bb1-link.telia.net (80.91.253.122) 76.691 ms nyk-bb2-link.telia.net (80.91.253.126) 78.755 ms 78.733 ms
8 nyk-b4-link.telia.net (80.91.250.97) 78.454 ms 78.451 ms 78.509 ms
9 webair-126294-nyk-b1.c.telia.net (213.248.82.150) 77.922 ms 76.523 ms 77.844 ms
10 csn010.gsc.webair.net (173.239.0.26) 78.935 ms 77.628 ms 77.751 ms
11 dsn011.gsc.webair.net (173.239.11.198) 77.504 ms 100.812 ms 78.178 ms
12 lbn171.gsc.webair.net (173.239.11.234) 78.951 ms 79.247 ms 77.928 ms
hops 1-6, their backbone, 7 and we're in the US, 10, we're in the destination DC.
Code:
traceroute to mojohost.com (64.59.69.66), 30 hops max, 40 byte packets
1 vss-3-6k.fr.eu (188.165.240.254) 161.994 ms * *
2 rbx-g2-a9.fr.eu (94.23.122.94) 1.026 ms 1.028 ms 1.024 ms
3 ams-5-6k.nl.eu (94.23.122.190) 5.855 ms ams-5-6k.nl.eu (91.121.131.174) 5.869 ms *
4 20gigabitethernet1-3.core1.ams1.he.net (195.69.145.150) 5.838 ms 5.836 ms 5.837 ms
5 10gigabitethernet4-1.core1.nyc4.he.net (216.66.24.153) 83.284 ms 10gigabitethernet1-4.core1.lon1.he.net (72.52.92.81) 9.072 ms 10gigabitethernet4-1.core1.nyc4.he.net (216.66.24.153) 83.252 ms
6 10gigabitethernet2-3.core1.nyc4.he.net (72.52.92.77) 79.557 ms 10gigabitethernet2-3.core1.ash1.he.net (72.52.92.86) 94.021 ms 97.056 ms
7 10gigabitethernet5-3.core1.atl1.he.net (184.105.213.110) 106.526 ms 10gigabitethernet2-3.core1.ash1.he.net (72.52.92.86) 89.465 ms 92.185 ms
8 10gigabitethernet3-2.core1.mia1.he.net (72.52.92.41) 116.734 ms 116.738 ms 116.725 ms
9 10gigabitethernet3-2.core1.mia1.he.net (72.52.92.41) 112.036 ms 111.896 ms easyonline.10gigabitethernet1-3.core1.mia1.he.net (209.51.161.102) 119.962 ms
10 easyonline.10gigabitethernet1-3.core1.mia1.he.net (209.51.161.102) 115.276 ms 115.178 ms *
he.net always routes via the NL cos that's their point, but look points 123 their structure to get them to the main transatlantic DC for that route, 5 we're in the US bing done.
Ergo, no problem with hosting with OVH for US-based customers.
Anyone want to send a traceroute of their DC to ovh to see if the same can be said of these US DCs?