New on LowEndTalk? Please Register and read our Community Rules.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Comments
I added the TORIX words for clarification. Thanks!
1 10.8.6.89 (10.8.6.89) 0.848 ms 1.371 ms 1.335 ms
2 10.8.17.209 (10.8.17.209) 0.604 ms 0.668 ms 0.642 ms
3 10.8.43.1 (10.8.43.1) 0.198 ms 0.172 ms 0.159 ms
4 10.8.25.141 (10.8.25.141) 58.812 ms 10.8.25.197 0.221 ms 10.8.25.141 58.726 ms
5 78.152.61.30 (78.152.61.30) 0.642 ms 78.152.57.86 (78.152.57.86) 0.587 ms 0.706 ms
6 eth3-1.edge1.tor1.ca.as5580.net (78.152.45.219) 9.311 ms 13.639 ms 9.268 ms
7 cogeco.ip4.torontointernetxchange.net (206.108.34.27) 4.332 ms 4.308 ms 3.448 ms
8 129-6-226-24.rev.cgocable.net (24.226.6.129) 6.520 ms 6.477 ms 6.448 ms
If you have added TORIX, are you just using Atrato/Hibernia to reach it? That route is just Hibernia's session on the TORIX AS5580, we are also on TORIX.
DIST-AA.TOR01#traceroute 24.226.5.221
Type escape sequence to abort.
Tracing the route to 221-5-226-24.rev.cgocable.net (24.226.5.221)
VRF info: (vrf in name/id, vrf out name/id)
1 cogeco.ip4.torontointernetxchange.net (206.108.34.27) 0 msec 4 msec 4 msec
As a Turkish guy, with nothing to do with Toronto, Canada, or Buffalo
this is a TORIK:
and these are TORIX (TORIKS):
Does that mean LET will now get faster because you directly peer with CloudFlare now?
Is it not already fast?
Nothing is fast at colocrossing, only soon™.
Its just Hibernia transit, they do not actually peer at Torix.
@Mun
Remember how long it took for SSL?
Just wait until ColoCrossing finally gets IPv6.
There won't be any IPv6 addresses left by the time CC adopts IPv6
So much love!
Okay, no need to show off your knowledge of Canadian ISPs ._.
That is Atrato, not CC. You don't seem to have a TORIX link.
Yes, as I mentioned in my initial post "we've partnered with one of our transit providers" this is through our partnership with Hibernia and due to mutual benefit we've been able to get that Toronto peering enabled.
We're conducting some other network related work this weekend which we'll be talking about soon, too.
When do we get to see the new routers and switches and servers? @QuadraNet_Adam beat you guys with the server pictures already...
btw just tested it from my phone... 1.4 ms ping on a bell connection. 7 ms on bell mobility
Seeing no sign of that from OVH GRA.
OVH would rather get rid of you externally than use their limited internal bandwidth across the pond.
traceroute to lg.buf.colocrossing.com (198.12.127.26), 30 hops max, 60 byte packets
1 ----- (------) 1.850 ms 0.660 ms 0.683 ms
2 gra-g2-a9.fr.eu (37.187.231.93) 0.180 ms 0.242 ms 0.240 ms
3 gra-g1-a9.fr.eu (37.187.36.8) 0.534 ms 1.956 ms gra-g2-a9.fr.eu (37.187.36.196) 2.573 ms
4 be100-1196.ams-1-a9.nl.eu (91.121.128.95) 6.734 ms po1.nyk-1-6k.ny.us (213.251.128.29) 6.677 ms 6.728 ms
5 et-11-1-0-v501.edge1.ams2.nl.as5580.net (80.249.208.229) 7.071 ms et-11-1-0-v500.edge1.ams1.nl.as5580.net (80.249.209.229) 6.889 ms 6.647 ms
6 ae06.core02.ams02.nl.as5580.net (78.152.45.67) 93.443 ms ae05.core02.ams02.nl.as5580.net (78.152.53.59) 90.491 ms ae06.core02.ams02.nl.as5580.net (78.152.45.67) 93.255 ms
7 ae01.core02.lon01.uk.as5580.net (78.152.53.228) 93.181 ms 93.275 ms 93.210 ms
8 eth7-1.edge1.nyc4.us.as5580.net (78.152.53.225) 93.022 ms 93.068 ms 92.978 ms
9 eth1-1.edge1.buf1.us.as5580.net (78.152.45.216) 90.524 ms 90.424 ms 90.642 ms
10 78.152.57.87 (78.152.57.87) 87.573 ms 78.152.60.49 (78.152.60.49) 88.523 ms 78.152.61.31 (78.152.61.31) 91.492 ms
11 * * *
12 * * *
13 lg.buf.colocrossing.com (198.12.127.26) 88.982 ms !X 88.988 ms !X 89.013 ms !X
Goes straight to Hibernia via AMS Peering
Where OVH CA is as expected
traceroute lg.buf.colocrossing.com
traceroute to lg.buf.colocrossing.com (198.12.127.26), 30 hops max, 60 byte packets
1 ------- (-----) 1.763 ms 1.752 ms 3.033 ms
2 bhs-g1-a9.qc.ca (198.27.73.93) 0.639 ms bhs-g2-a9.qc.ca (198.27.73.95) 0.730 ms 0.807 ms
3 po2.tor-1-6k.on.ca (178.32.135.70) 8.852 ms po4.tor-1-6k.on.ca (198.27.73.85) 8.982 ms 9.067 ms
4 torix.edge1.tor1.ca.as5580.net (206.108.34.245) 8.254 ms 8.700 ms 8.172 ms
5 eth1-3.edge1.buf1.us.as5580.net (78.152.45.218) 10.402 ms 10.301 ms 10.259 ms
6 78.152.60.49 (78.152.60.49) 14.371 ms 78.152.57.111 (78.152.57.111) 14.347 ms 78.152.57.87 (78.152.57.87) 14.431 ms
7 * * *
8 * * *
9 * * *
10 lg.buf.colocrossing.com (198.12.127.26) 14.634 ms !X 14.646 ms !X 14.631 ms !X
5 43 ms 22 ms 38 ms nrth-bb-1b-ae0-0.network.virginmedia.net [62.254.42.130]
6 17 ms 16 ms 18 ms m674-mp2.cvx1-b.lis.dial.ntli.net [62.254.42.162]
7 * * * Request timed out.
8 86 ms 107 ms 81 ms us-nyc01b-rd2-ae9-0.aorta.net [84.116.140.170]
9 84 ms 82 ms 82 ms us-nyc03a-ri1-et-3-1-0-0.aorta.net [84.116.135.73]
10 83 ms 88 ms 90 ms xe-0-0-0 [204.148.20.177]
11 85 ms 90 ms 89 ms 0.ae1.GW10.EWR6.ALTER.NET [140.222.230.151]
12 83 ms 87 ms 86 ms teliasonera-gw.customer.alter.net [157.130.91.86]
13 161 ms 85 ms 82 ms nyk-bb2-link.telia.net [62.115.134.109]
14 97 ms 95 ms 99 ms buf-b1-link.telia.net [62.115.141.180]
15 97 ms 96 ms 105 ms colocrossing-ic-314281-buf-b1.c.telia.net [62.115.59.90]
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 98 ms 99 ms 98 ms lg.buf.colocrossing.com [198.12.127.26]
Meh routing from the UK
Not at all defending CC, just genuinely curious. But...so what? How is this any different than paying for a link to TORIX? Obviously they aren't going to light up a path in house...
Bleh, routing from SG. Argh so many hops on ISP & XO's network, not surprised
>
Hows it up north? (if I read VM's hops correct)
Around the same latency from BSKYB just Level3 then telia from London.
3 15 ms 11 ms 8 ms 02780b55.bb.sky.com [2.120.11.85]
4 8 ms 13 ms 17 ms ae51.edge3.London15.Level3.net [212.187.193.185]
5 10 ms 10 ms 10 ms ae-123-3509.edge5.London1.Level3.net [4.69.166.33]
6 19 ms 16 ms 14 ms ae-123-3509.edge5.London1.Level3.net [4.69.166.33]
7 7 ms 8 ms 7 ms ldn-b5-link.telia.net [213.248.96.37]
8 9 ms 12 ms 8 ms ldn-bb3-link.telia.net [62.115.141.144]
9 76 ms 78 ms 76 ms nyk-bb1-link.telia.net [213.155.135.65]
10 97 ms 100 ms 104 ms buf-b1-link.telia.net [80.91.246.36]
11 92 ms 90 ms 90 ms colocrossing-ic-314280-buf-b1.c.telia.net [62.115.59.86]
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 90 ms 91 ms 91 ms lg.buf.colocrossing.com [198.12.127.26]
I am not up north actually. Hertfordshire here. Just VM like to bounce me through Luton and the northern network.
We've posted a lot of pictures on our Facebook and Blog
http://blog.colocrossing.com
https://www.facebook.com/colocrossing/photos_stream
Maybe we can convince @sysadmin to post some pictures of our network cage here in Buffalo tomorrow. 9 racks of cable management glory and lots of fancy Juniper and Brocade gear.
Not a good or bad thing, more the fact if they had their own peering port at TORIX of 10Gbps for example that is there's dedicated just for TORIX traffic.
Where there using some of their standard capacity with Hibernia to reach TORIX with a hop or two.
What's the ping like to OVH FR?
We have 80 Gbit of capacity to Hibernia in Buffalo, and they have quite a bit between Buffalo and Toronto nodes.
The reason we worked with Hibernia on this project is they have the clout needed to easily and quickly peer with many big networks. Rogers works more rapidly with Hibernia than they would ColoCrossing for example.
Never meant for that to come over as a bad thing! Just was trying to explain
Didn't take it as a bad thing. Just offering some additional insight.
Nothing surprises me with VM!
But unless Hibernia is overselling their TORIX capacity, it won't make any difference...right?
Well, any link to TORIX would include a hop or two from Buffalo...
Lots of people out there (not saying you) trying to crucify CC (probably rightly so) but this seems like just about the worst thing to bitch about.
Im still waiting for my ipv6.