Quote:
Originally Posted by borked
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  |
Code:
[spudstr@yf~]# traceroute ovh.com
traceroute to ovh.com (213.186.33.34), 30 hops max, 40 byte packets
1 216.14.80.1 (216.14.80.1) 1.442 ms 1.391 ms 1.663 ms
2 te1-1.c00.iad.yellowfiber.net (216.177.148.121) 1.303 ms 1.297 ms 1.276 ms
3 te2-2.c01.iad.yellowfiber.net (216.177.157.30) 1.248 ms 1.227 ms 1.204 ms
4 ash-bb1-link.telia.net (213.248.92.233) 1.186 ms 1.157 ms 1.140 ms
5 prs-bb1-link.telia.net (80.91.252.37) 82.555 ms 82.571 ms 82.557 ms
6 prs-b-link.telia.net (80.91.251.47) 88.340 ms 88.378 ms 88.409 ms
7 * * *
If you honestly think that a traceroute shows the truth path you are sadly misinformed, MPLS is very commonly used and hides several hops along the way.
Listen, I am not saying OVH is bad. Ovh is very large and well known and do a good job at what they do. The main reason OVH offers such pricing is because of their peering relationships with ISPS, yes they have a lot of peering, for things they don't peer they send out their transit lines. I.e bandwidth they buy. For the longest time ovh struggled to lots of places out side of the EU i.e US based ISPS. If you trace to someone like us, or quadranet or related due to peering, a network will send a peering partner their originating prefixes and their _customers_ prefixes. so in your first trace to quadranet you go OVH to mzima then to quadra, I"m pretty confident OVH and Mzima now known as Packet Exchange who is a very large EU network peer in.. wait for it.. Amsterdam in AMS-IX.
Hit end users in various networks in the states, Comcast, Cox, Paetec/Frontier/Cavtel etc. The eyeball networks. Hitting another hosting company is probably going to yield good speeds due to peering relationships.
Lets look at the states.
Code:
traceroute to 204.152.194.186 (204.152.194.186), 30 hops max, 40 byte packets
1 216.14.80.1 (216.14.80.1) 0.767 ms 0.719 ms 0.693 ms
2 te1-1.c00.iad.yellowfiber.net (216.177.148.121) 1.351 ms 1.331 ms 1.305 ms
3 xe-2-0-4.ar2.iad1.us.nlayer.net (69.31.31.85) 1.291 ms 1.263 ms 1.234 ms
4 ae4-40g.cr2.iad1.us.nlayer.net (69.31.31.185) 1.181 ms 1.155 ms 1.134 ms
5 xe-3-3-0.cr1.atl1.us.nlayer.net (69.22.142.105) 65.432 ms 65.442 ms 65.424 ms
6 te1-2.ar1.iah1.us.nlayer.net (69.22.142.117) 28.724 ms 39.446 ms 36.535 ms
7 xe-1-1-0.cr1.lax1.us.nlayer.net (69.22.142.122) 64.101 ms 64.115 ms 64.096 ms
8 ae2-50g.ar1.lax1.us.nlayer.net (69.31.127.142) 64.565 ms ae1-50g.ar1.lax1.us.nlayer.net (69.31.127.138) 64.551 ms 64.531 ms
9 as29761.ae1-320.ar1.lax1.us.nlayer.net (69.31.121.254) 65.401 ms 65.469 ms 65.583 ms
10 lax9-r3.6509.quadranet.com (66.63.163.238) 65.545 ms 65.667 ms 65.508 ms
11 204.152.194.186.static.quadranet.com (204.152.194.186) 65.256 ms 65.320 ms 65.302 ms
your 157ms vs my 65ms this can be a huge impact on lots of applications. While downloading a file between datacenters can be fast, lesser circuits may not be. I am just saying you really should be careful about hosting and place your content where it best suits your target audience, because in the end of the day latency matters.