Toronto POP

[brad]

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.

[testmonster]

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.

[brad]

We are waiting on TORIX to provide a 10GE port.

Able to get the port and link up yet?

[broquea]

Poked them some more, and they promised more information for us by Weds. next week, about finalizing the exchange connection.  ;D

[brad]

Poked them some more, and they promised more information for us by Weds. next week, about finalizing the exchange connection.  ;D

ping. :)

[broquea]

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.

[broquea]

Port on the exchange has been allocated for us.
We're ordering the cross-connect right now, and will get peering sessions up ASAP.

[broquea]

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.

[brad]

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.

[brad]

FYI, I know it is only cosmetic but there are still some missing DNS records for some of the network infrastructure in Toronto...

Code Select Expand


$ 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.

[spiffed]

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.

Code Select Expand

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


[brad]

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.

Code Select Expand

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.

Code Select Expand


$ 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


[brad]

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?

[broquea]

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.

[brad]

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?