Does HE have a link to TorIX in the works or planned? Without a link to TorIX having a local tunnelbroker POP provides essentially no incentive for anyone to move existing tunnels or even create new tunnels on the new POP. It would also be very beneficial to anyone using HE for transit.
We are waiting on TORIX to provide a 10GE port.
Yes, anybody considering moving their tunnel to Toronto should wait until our TORIX port is live.
Quote from: testmonster on September 21, 2008, 10:08:45 AM
We are waiting on TORIX to provide a 10GE port.
Able to get the port and link up yet?
Poked them some more, and they promised more information for us by Weds. next week, about finalizing the exchange connection. ;D
Quote from: broquea on October 01, 2008, 06:18:16 PM
Poked them some more, and they promised more information for us by Weds. next week, about finalizing the exchange connection. ;D
ping. :)
Quote from: brad on October 08, 2008, 02:47:17 PM
ping. :)
Emailed them today since Wednesday came and passed with no update from them.
When there is an update or any kind of information that needs sharing, I'll let you guys know.
Port on the exchange has been allocated for us.
We're ordering the cross-connect right now, and will get peering sessions up ASAP.
FYI: since getting the port live this week, we've been turning up a bunch of IPv4/IPv6 peering. We're far from done, but making progress on getting sessions up.
Yes, I noticed that. My co-lo provider already has a v4 session up and at least one major DSL provider in the area that I'm aware of. At the moment I'm interested in seeing a session turned up with Primus Telecommunications -- AS 6407, currently they have a session with HE at NYIIX.
FYI, I know it is only cosmetic but there are still some missing DNS records for some of the network infrastructure in Toronto...
$ traceroute6 www.he.net
traceroute6 to he.net (2001:470:0:76::2) from 2001:470:b01e:3:216:41ff:fe17:6933, 64 hops max, 12 byte packets
1 2001:470:b01e:3::2 0.376 ms 0.295 ms 0.324 ms
2 2001:470:1c:8e::1 25.65 ms 25.501 ms 25.524 ms
3 2001:470:0:c0::1 25.823 ms 25.521 ms 25.198 ms
4 2001:470:0:ae::1 41.432 ms 42.202 ms 40.787 ms
5 10gigabitethernet1-4.core1.nyc1.he.net 41.421 ms 41.911 ms 50.654 ms
6 10gigabitethernet1-1.core1.nyc4.he.net 41.917 ms 42.198 ms 41.257 ms
7 10gigabitethernet3-1.core1.sjc2.he.net 121.159 ms 121.312 ms 121.013 ms
8 gige-g1-1.core1.fmt1.he.net 121.632 ms 123.661 ms 123.501 ms
9 he.net 121.173 ms 121.469 ms 121.175 ms
Otherwise looking good.
Tracing off the Rogers broadband network in Mississauga (neighboring Toronto), the Toronto POP is actually has the third worst RTT of any North American POP at 45.7ms and the most complicated route with 11 hops.
Looking at the traceroute it would appear to travel through NY before heading back into Toronto.
Host Loss% Snt Last Avg Best Wrst StDev
1. ???
2. vl-201.gw03.wlfdle.phub.net.cable.rogers.com 0.0% 6 8.3 8.8 7.7 11.9 1.6
3. 64.71.241.89 0.0% 6 12.0 8.9 7.8 12.0 1.7
4. 64.71.241.85 0.0% 6 8.0 8.7 7.6 10.6 1.3
5. 66.185.83.62 0.0% 6 24.2 22.1 21.4 24.2 1.1
6. equinix-ash.he.net 0.0% 6 22.9 22.8 22.2 23.5 0.4
7. 10gigabitethernet1-2.core1.nyc4.he.net 0.0% 5 28.6 28.0 27.1 29.5 1.0
8. 10gigabitethernet1-2.core1.nyc1.he.net 0.0% 5 38.6 31.8 27.2 38.6 5.5
9. 10gigabitethernet1-1.core1.nyc5.he.net 0.0% 5 29.2 28.3 27.4 29.2 0.7
10. 10gigabitethernet1-1.core1.tor1.he.net 0.0% 5 48.3 45.1 43.4 48.3 2.1
11. tserv21.tor1.ipv6.he.net 0.0% 5 43.7 44.0 42.8 45.5 1.0
Quote from: spiffed on November 23, 2008, 10:55:06 PM
Tracing off the Rogers broadband network in Mississauga (neighboring Toronto), the Toronto POP is actually has the third worst RTT of any North American POP at 45.7ms and the most complicated route with 11 hops.
Looking at the traceroute it would appear to travel through NY before heading back into Toronto.
Host Loss% Snt Last Avg Best Wrst StDev
1. ???
2. vl-201.gw03.wlfdle.phub.net.cable.rogers.com 0.0% 6 8.3 8.8 7.7 11.9 1.6
3. 64.71.241.89 0.0% 6 12.0 8.9 7.8 12.0 1.7
4. 64.71.241.85 0.0% 6 8.0 8.7 7.6 10.6 1.3
5. 66.185.83.62 0.0% 6 24.2 22.1 21.4 24.2 1.1
6. equinix-ash.he.net 0.0% 6 22.9 22.8 22.2 23.5 0.4
7. 10gigabitethernet1-2.core1.nyc4.he.net 0.0% 5 28.6 28.0 27.1 29.5 1.0
8. 10gigabitethernet1-2.core1.nyc1.he.net 0.0% 5 38.6 31.8 27.2 38.6 5.5
9. 10gigabitethernet1-1.core1.nyc5.he.net 0.0% 5 29.2 28.3 27.4 29.2 0.7
10. 10gigabitethernet1-1.core1.tor1.he.net 0.0% 5 48.3 45.1 43.4 48.3 2.1
11. tserv21.tor1.ipv6.he.net 0.0% 5 43.7 44.0 42.8 45.5 1.0
That is to be expected until HE and Rogers (or other local ISPs) turn up peering session(s) at TorIX.
$ traceroute tserv21.tor1.ipv6.he.net
traceroute to tserv21.tor1.ipv6.he.net (216.66.38.58), 64 hops max, 40 byte packets
1 208.68.88.153 (208.68.88.153) 0.538 ms 0.396 ms 0.360 ms
2 bb1.yyz01.spdnetwork.net (208.68.88.1) 0.592 ms 0.670 ms 0.514 ms
3 gw-he.torontointernetxchange.net (198.32.245.112) 0.891 ms 0.513 ms 0.978 ms
4 tserv21.tor1.ipv6.he.net (216.66.38.58) 1.653 ms 1.295 ms 1.293 ms
Quote from: brad on November 06, 2008, 07:26:32 PM
Yes, I noticed that. My co-lo provider already has a v4 session up and at least one major DSL provider in the area that I'm aware of. At the moment I'm interested in seeing a session turned up with Primus Telecommunications -- AS 6407, currently they have a session with HE at NYIIX.
broquea, able to comment on my request for HE to also turn up a session with Primus @ TorIX?
we sent out emails to all torix participants. we've gotten a lot of replies, but still have to wait on others. i believe this is one of the ones we are waiting on, even after our second mailing.
Quote from: brad on November 27, 2008, 08:27:46 PM
Quote from: brad on November 06, 2008, 07:26:32 PM
Yes, I noticed that. My co-lo provider already has a v4 session up and at least one major DSL provider in the area that I'm aware of. At the moment I'm interested in seeing a session turned up with Primus Telecommunications -- AS 6407, currently they have a session with HE at NYIIX.
broquea, able to comment on my request for HE to also turn up a session with Primus @ TorIX?
Also AS 812 - Rogers Communications?
Quote from: brad on November 27, 2008, 08:27:46 PM
Quote from: brad on November 06, 2008, 07:26:32 PM
Yes, I noticed that. My co-lo provider already has a v4 session up and at least one major DSL provider in the area that I'm aware of. At the moment I'm interested in seeing a session turned up with Primus Telecommunications -- AS 6407, currently they have a session with HE at NYIIX.
broquea, able to comment on my request for HE to also turn up a session with Primus @ TorIX?
HE now peers with Primus @ TorIX.
Could HE please look into peering with Rogers (AS812) in Toronto? Currently HE is peering with Rogers in Ashburn, Chicago and New York.
Host Loss% Snt Last Avg Best Wrst StDev
1. ???
2. vl-201.gw03.wlfdle.phub.net.cable.rogers.com 0.0% 6 8.3 8.8 7.7 11.9 1.6
3. 64.71.241.89 0.0% 6 12.0 8.9 7.8 12.0 1.7
4. 64.71.241.85 0.0% 6 8.0 8.7 7.6 10.6 1.3
5. 66.185.83.62 0.0% 6 24.2 22.1 21.4 24.2 1.1
6. equinix-ash.he.net 0.0% 6 22.9 22.8 22.2 23.5 0.4
7. 10gigabitethernet1-2.core1.nyc4.he.net 0.0% 5 28.6 28.0 27.1 29.5 1.0
8. 10gigabitethernet1-2.core1.nyc1.he.net 0.0% 5 38.6 31.8 27.2 38.6 5.5
9. 10gigabitethernet1-1.core1.nyc5.he.net 0.0% 5 29.2 28.3 27.4 29.2 0.7
10. 10gigabitethernet1-1.core1.tor1.he.net 0.0% 5 48.3 45.1 43.4 48.3 2.1
11. tserv21.tor1.ipv6.he.net 0.0% 5 43.7 44.0 42.8 45.5 1.0
Quote from: brad on September 12, 2009, 03:39:25 PM
Could HE please look into peering with Rogers (AS812) in Toronto? Currently HE is peering with Rogers in Ashburn, Chicago and New York.
Just fired off an email to them.
Quote from: broquea on September 12, 2009, 04:39:35 PM
Just fired off an email to them.
Thank you. Could HE also please look into peering with Cogeco Cable (AS7992) at TorIX?
$ traceroute 216.66.38.58
traceroute to 216.66.38.58 (216.66.38.58), 64 hops max, 40 byte packets
1 192.168.1.1 (192.168.1.1) 2.558 ms 1.657 ms 1.603 ms
2 10.76.0.1 (10.76.0.1) 9.988 ms 9.156 ms 10.56 ms
3 d226-9-73.home.cgocable.net (24.226.9.73) 10.871 ms 14.803 ms 11.913 ms
4 113-0-226-24.cgocable.net (24.226.0.113) 14.728 ms 13.568 ms 12.825 ms
5 qix-tor-gw.peer1.net (69.28.230.245) 14.156 ms 13.102 ms 12.718 ms
6 10ge.xe-0-0-0.tor-1yg-cor-1.peer1.net (216.187.114.133) 15.295 ms 16.882 ms 12.363 ms
7 oc48-po5-0.chi-eqx-dis-1.peer1.net (216.187.114.141) 24.823 ms 33.333 ms 24.31 ms
8 10gigabitethernet4-1.core1.chi1.he.net (206.223.119.37) 23.208 ms 39.683 ms 26.866 ms
9 10gigabitethernet2-4.core1.nyc4.he.net (72.52.92.101) 38.529 ms 37.400 ms 43.389 ms
10 10gigabitethernet1-2.core1.nyc1.he.net (72.52.92.46) 38.769 ms 38.12 ms 43.20 ms
11 10gigabitethernet1-1.core1.nyc5.he.net (72.52.92.154) 37.840 ms 37.58 ms 37.855 ms
12 10gigabitethernet1-1.core1.tor1.he.net (72.52.92.166) 54.66 ms 52.145 ms 53.572 ms
13 tserv21.tor1.ipv6.he.net (216.66.38.58) 54.333 ms 53.13 ms 53.928 ms
I might also suggest looking into peering with Peer1 (AS13768) in Toronto although they don't connect to TorIX for some strange reason. They have their own PIX public exchanges in the Canadian cities with POPs that being Toronto, Montreal, Vancouver.
http://www.peer1.com/infrastructure/peering.php
http://www.peer1.com/infrastructure/pix.php
I see Peer1 is also at Switch and Data Toronto. Most likely they have PIX Toronto accessible from their Switch and Data infrastructure.
Please also look into Shaw Communications @ TorIX (AS6327) whom you already peer with in at least Ashburn, Chicago and New York and Videotron Ltd (AS5769).
Rogers, Shaw, Cogeco, Videotron, as well as Mountain Cable and Eastlink (whom you already peer with at TorIX) are the major cable co's in Canada.
Looking at the current session list HE has good coverage for the majority of the rest of the carriers, hosting providers and independent ISPs in Canada via TorIX.
Quote from: brad on September 12, 2009, 03:39:25 PM
Could HE please look into peering with Rogers (AS812) in Toronto? Currently HE is peering with Rogers in Ashburn, Chicago and New York.
Thanks. HE has turned up peering with Rogers in Toronto.
Quote from: brad on September 12, 2009, 08:26:10 PM
Thank you. Could HE also please look into peering with Cogeco Cable (AS7992) at TorIX?
Thanks. HE has turned up peering with Cogeco in Toronto.
Quote from: brad on September 12, 2009, 09:11:11 PM
Please also look into Shaw Communications @ TorIX (AS6327) whom you already peer with in at least Ashburn, Chicago and New York and Videotron Ltd (AS5769).
Able to get in contact with anyone at the above carriers?
Quote from: brad on October 30, 2009, 06:57:35 PM
Quote from: brad on September 12, 2009, 09:11:11 PM
Please also look into Shaw Communications @ TorIX (AS6327) whom you already peer with in at least Ashburn, Chicago and New York and Videotron Ltd (AS5769).
Able to get in contact with anyone at the above carriers?
Both carriers were (are constantly) contacted about peering. I just can't get into the details of the discussions.
Keep in mind that we cannot give you any more information about peering other than what you can discern for yourself from our looking glass (it's up or not basically.) But I do lurk here looking for routing / peering issues so please keep posting any potential network adjacency you would like to see. There's a lot of discussion and work that goes on behind the scenes to get these setup (especially the larger the network) so please don't get discouraged by a lack of response from us on peering issues.
Please also attempt to establish peering with Bell Canada (AS 577) and Telus Communications (AS 852).