Topic 'Re: TorIX Upgrade' in forum 'Start Communications users forum' - dslreports.com

Re: TorIX Upgrade

Wed, 06 Feb 2013 13:09:44 EDT

jmck posted : I did a few tests on two of my servers:

wget -O /dev/null http://proof.ovh.net/files/100Mio.dat

One in NYC off 100mbit HE.net and the other in Montreal at OVH and both were able to get ~80-90Mbit/sec off the Euro OVH test file. Could you post a traceroute or mtr from your server to 24.53.250.37?

A traceroute or mtr to my NYC server would be good too to see the difference with the path (rakis.net).

Re: TorIX Upgrade

Wed, 06 Feb 2013 13:04:15 EDT

jmck posted : Here's mine on Start first with OVH in Montreal (»proof.ovh.ca) :

Download Speed: 64235 kbps (8029.4 KB/sec transfer rate)
Upload Speed: 3919 kbps (489.9 KB/sec transfer rate)
Latency: 21 ms
6 February, 2013 12:59:13 PM EST

Here's with OVH in Europe (»proof.ovh.net) :

Download Speed: 11764 kbps (1470.5 KB/sec transfer rate)
Upload Speed: 3585 kbps (448.1 KB/sec transfer rate)
Latency: 206 ms
6 February, 2013 12:59:42 PM EST

---

Obviously speedboost kicked in a bit for the Montreal proof server (it would actually be higher but my WRT54GS can't actually go faster than ~60-65Mbit/sec). The test was also done at 1pm which is getting near Europe peak but not NA. As I mentioned I was also previously on TSI until last week and TSI had serious speed issues even at OVH in Montreal.

Lastly you should consider moving your OVH server to the Montreal location if you can, I've had one for a few months and it's been great (»www.ovh.com/ca/en/).

Re: TorIX Upgrade

Wed, 06 Feb 2013 07:11:44 EDT

anon posted : Last Result:
Download Speed: 30981 kbps (3872.6 KB/sec transfer rate)
Upload Speed: 1907 kbps (238.4 KB/sec transfer rate)
Latency: 235 ms
6/2/2013 01:03:11

Last results :
IP Download (kb/s) Upload (kb/s) Latency (ms)
2001:470:1d::xxxx 28555 1608 267

First is my IPv4 and 2nd is my IPv6

Re: TorIX Upgrade

Wed, 06 Feb 2013 00:15:26 EDT

jmck posted : well that's also from france, there's a NA proof server. i was previously on TSI and there's also been issues between TSI and OVH even after the peering at Torix while OVH had a ton of capacity at Torix.

I switched to Start earlier this week and I haven't had performance issues.

Re: TorIX Upgrade

Wed, 06 Feb 2013 00:10:04 EDT

merc782 posted : thanks for checking it out.
It looks like network between Amsterdam and London is overloaded

»weathermap.ovh.net/

Re: TorIX Upgrade

Wed, 06 Feb 2013 00:04:14 EDT

rocca posted : Looks like in OVH's network:

traceroute to proof.ovh.net (188.165.12.106), 30 hops max, 60 byte packets
1 64.140.114.1 (64.140.114.1) 0.326 ms 0.421 ms 0.465 ms
2 gw-ovh.torontointernetxchange.net (206.108.34.189) 0.510 ms * *
3 * * *
4 ldn-5-6k.uk.eu (178.32.135.165) 83.159 ms * *
5 * * *
6 * * *
7 * * rbx-g1-a9.fr.eu (178.33.100.238) 782.365 ms
8 rbx-s3-6k.fr.eu (213.186.32.164) 520.480 ms * 501.159 ms
9 proof.ovh.net (188.165.12.106) 242.337 ms 443.187 ms 427.758 ms

Re: TorIX Upgrade

Tue, 05 Feb 2013 23:54:48 EDT

merc782 posted : »proof.ovh.net/

can some one post current speed test results from start to ovh? As of now ( almost midnight) speeds from Teksavvy to ovh are pathetic, it looks like OVH torix pop is overloaded. if the speed is good from start to ovh, then it will be a big compelling reason for me to switch

Re: TorIX Upgrade

Mon, 04 Feb 2013 15:52:34 EDT

rocca posted : They are a conditional peer at TorIX and don't advertise via the route servers. We're open to peering directly with them, maybe if some of their customers asked they'd take more of an interest.

Re: TorIX Upgrade

Mon, 04 Feb 2013 15:35:25 EDT

vonSchroeder posted : Any plans to get Limelight traffic going directly through TorIX? At the moment it stays in Toronto but passes through HE as a middleman between you and TorIX.

Valve/Steam content server for example:

tracert cdn.steampowered.com Tracing route to valve.vo.llnwd.net [208.111.181.254]over a maximum of 30 hops:   1     7 ms     7 ms     8 ms  10.204.100.1  2    19 ms    19 ms    19 ms  64.140.112.158  3    18 ms    20 ms    18 ms  core1-toronto1-te3-3.net.start.ca [64.140.112.153]  4    19 ms    23 ms    25 ms  v613.core1.tor1.he.net [216.66.23.5]  5    27 ms    24 ms    34 ms  gw-llnw.torontointernetxchange.net [206.108.34.94]  6    22 ms    24 ms    24 ms  ve5.fr4.yyz.llnw.net [69.28.171.142]  7    20 ms    23 ms    19 ms  cdn-208-111-181-254.yyz.llnw.net [208.111.181.254] Trace complete.

And the return from a LLNW Toronto server:

Tracing the route to IP node (108.170.xxx.xxx) from 1 to 30 hops   1    12 ms   <1 ms   <1 ms gw-he.torontointernetxchange.net [206.108.34.112]   2     8 ms    1 ms   <1 ms start-communications.10gigabitethernet3-1.core1.tor1.he.net [216.66.23.6]   3     1 ms    1 ms    1 ms asr-link1-burlington1.net.start.ca [64.140.112.154]   4    24 ms   12 ms   13 ms 10.204.100.1   5    35 ms   21 ms   19 ms dhcp-108-170-xxx-xxx.cable.user.start.ca [108.170.xxx.xxx]

Re: TorIX Upgrade

Mon, 04 Feb 2013 12:17:01 EDT

jmck posted : oops you're right, i had pasted the wrong host :/ a1.g.akamaitech.net shows the right one.

Re: TorIX Upgrade

Mon, 04 Feb 2013 12:04:58 EDT

rocca posted : Ah, that's just www.akamai.com's main web site and not the actual content. The content itself is cached and peered through TorIX.

Re: TorIX Upgrade

Mon, 04 Feb 2013 11:59:54 EDT

jmck posted : I'm using the Start DNS servers. I'm not exactly sure what the return route is, but considering you have Bell Nexxia transit I sort of assumed it was going to return through Bell (if not then it kind of sucks its going the same route as my outbound through Toronto/Chicago/Toronto).

traceroute to www.akamai.com

Tracing route to a152.dscq.akamai.net [67.69.196.18]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms 192.168.1.1
2 8 ms 7 ms 7 ms 10.106.248.129
3 15 ms 14 ms 18 ms 24.156.149.221
4 23 ms 22 ms 22 ms 69.63.249.9
5 15 ms 20 ms 25 ms v613.core1.tor1.he.net [216.66.23.5]
6 28 ms 29 ms 34 ms 10gigabitethernet7-3.core1.chi1.he.net [184.105.
213.150]
7 26 ms 27 ms 28 ms bx5-chicagodt.bell.ca [206.223.119.66]
8 44 ms 42 ms 70 ms newcore1-chicagocp_xe5-0-1_0 [64.230.186.252]
9 46 ms 44 ms 43 ms tcore4-toronto63_POS00-6-0-0.net.bell.ca [64.230
.147.169]
10 44 ms 44 ms 38 ms bx4-toronto63_so-1-0-0.net.bell.ca [64.230.160.1
26]
11 40 ms 43 ms 42 ms 67.69.196.18

Re: TorIX Upgrade

Mon, 04 Feb 2013 11:41:18 EDT

rocca posted : We only have 10G in TorIX but that's plenty right now. ;)

As for the traffic taking Bell, odd. Can you PM me the target IP and traceroute?

Thanks.

Re: TorIX Upgrade

Mon, 04 Feb 2013 11:39:33 EDT

jmck posted : oh, didn't realize you were getting an Akamai region in your datacenter. there's likely still some benefit to peer at TorIX now that you have 20GE in case your cluster ever goes down for maintenance or ever doesn't have enough capacity so it can overflow to TorIX.

right now it seems to be going through Bell Nexxia which is still really good performance, but it might just save you a few pizzas/beers down the road :p

Re: TorIX Upgrade

Mon, 04 Feb 2013 10:23:04 EDT

rocca posted : Not quite yet, we're on the cusp of getting an appliance.

Re: TorIX Upgrade

Mon, 04 Feb 2013 10:08:19 EDT

jmck posted : hey rocca, is Start peering with Akamai at TorIX? right now it seems Akamai is serving me from somewhere else.

Re: TorIX Upgrade

Wed, 30 Jan 2013 04:41:41 EDT

dan mackay posted : such a shame my vps uses internap and routes over he :(

Re: TorIX Upgrade

Wed, 30 Jan 2013 04:07:45 EDT

JCohen posted :

said by rocca:

said by merc782:

sorry for the confusion, was looking for nlayer, confused it with cogent. Tx for the update

nLayer is up too now.

Ping times are looking good through nLayer :)

Tracing route to singlehop.com [184.154.60.210]over a maximum of 30 hops:   1    <1 ms    <1 ms    <1 ms  192.168.1.1  2     8 ms     8 ms     9 ms  10.106.193.1  3    17 ms    19 ms    19 ms  69.63.254.205  4    25 ms    23 ms    23 ms  24.156.146.121  5    17 ms    15 ms    15 ms  ip-69-31-143-105.nlayer.net [69.31.143.105]  6    17 ms    16 ms    26 ms  ge-0-2-9.cr1.mtl1.ca.nlayer.net [69.31.143.24]  7    29 ms    30 ms    29 ms  xe-0-1-1.cr2.ord1.us.nlayer.net [69.22.142.77]  8    31 ms    33 ms    33 ms  ae2-20g.ar1.ord6.us.nlayer.net [69.31.110.254]  9    38 ms    29 ms    29 ms  as32475.ae7.ar1.ord6.us.nlayer.net [69.31.111.30] 10    31 ms    32 ms    29 ms  asw-ds116.ord03.singlehop.net [173.236.77.102] 11    31 ms    29 ms    31 ms  web05.singlehop.net [184.154.60.210] Trace complete. ---------- Pinging singlehop.com [184.154.60.210] with 32 bytes of data:Reply from 184.154.60.210: bytes=32 time=28ms TTL=54Reply from 184.154.60.210: bytes=32 time=29ms TTL=54Reply from 184.154.60.210: bytes=32 time=30ms TTL=54Reply from 184.154.60.210: bytes=32 time=28ms TTL=54 Ping statistics for 184.154.60.210:    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),Approximate round trip times in milli-seconds:    Minimum = 28ms, Maximum = 30ms, Average = 28ms

Re: TorIX Upgrade

Wed, 30 Jan 2013 01:53:41 EDT

rocca posted :

said by merc782:

sorry for the confusion, was looking for nlayer, confused it with cogent. Tx for the update

nLayer is up too now.

Re: TorIX Upgrade

Tue, 29 Jan 2013 10:54:52 EDT

jmck posted :

said by rocca:

We have a direct peering relationship with OVH now.

that's pretty sweet, glad you're both interested in improving network connectivity like this.

                                                 My traceroute  [v0.80]kif.mckill.ca (0.0.0.0)                                                                        Tue Jan 29 10:56:04 2013Keys:  Help   Display mode   Restart statistics   Order of fields   quit                                                                               Packets               Pings Host                                                                        Loss%   Snt   Last   Avg  Best  Wrst StDev 1. 142.4.213.253                                                             0.0%     1    0.6   0.6   0.6   0.6   0.0 2. bhs-g1-6k.qc.ca                                                           0.0%     1   44.5  44.5  44.5  44.5   0.0 3. mtl-2-6k.qc.ca                                                            0.0%     1    1.8   1.8   1.8   1.8   0.0 4. tor-1-6k.on.ca                                                            0.0%     1    8.6   8.6   8.6   8.6   0.0 5. gw-startcomm.torontointernetxchange.net                                   0.0%     1    8.6   8.6   8.6   8.6   0.0 6. core1-london1-ge1-1801.net.start.ca                                       0.0%     1   12.5  12.5  12.5  12.5   0.0 7. ws01-010.start.ca                                                         0.0%     1   12.5  12.5  12.5  12.5   0.0

Re: TorIX Upgrade

Tue, 29 Jan 2013 10:43:48 EDT

rocca posted : We have a direct peering relationship with OVH now.

Re: TorIX Upgrade

Sat, 26 Jan 2013 07:56:44 EDT

merc782 posted : sorry for the confusion, was looking for nlayer, confused it with cogent. Tx for the update

Re: TorIX Upgrade

Fri, 25 Jan 2013 23:59:10 EDT

rocca posted : No we've had that forever. nLayer is the new one coming online, it was supposed to be up this week but should be up next. Just completing the cross-connection at 151 Front.

Re: TorIX Upgrade

Fri, 25 Jan 2013 22:54:40 EDT

merc782 posted : Rocca,

Seeing Traffic routing via Cogent

»bgp.he.net/AS40788#_asinfo

is this a new 1gig transit ? plz enlighten us with details

Re: TorIX Upgrade

Tue, 22 Jan 2013 21:32:05 EDT

Johny posted : yeah I donno, started yesterday and is still going on. I'll see if I can get a tracert from the server

Re: TorIX Upgrade

Tue, 22 Jan 2013 20:57:44 EDT

jmck posted :

said by rocca:

Only way to know for sure what's happening is via traceroutes in the opposite direction, ie from that server back to you.

you'll also get a better idea of where the problem is if you run mtr instead of just traceroute, mtr combines ping and traceroute for each hop and you should let it run for ~10-20 seconds.

Re: TorIX Upgrade

Tue, 22 Jan 2013 20:37:23 EDT

rocca posted : Only way to know for sure what's happening is via traceroutes in the opposite direction, ie from that server back to you.

Re: TorIX Upgrade

Tue, 22 Jan 2013 20:35:27 EDT

rocca posted : Hard to say, some times it's great, ie I just pinged that last IP and now it's in 20ms from the core.

core1-toronto1#ping 75.102.43.162

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 75.102.43.162, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 20/24/28 ms

It's possible they have more than one uplink to nLayer and one is saturated and one isn't, if so it'd be hit or miss which return path you'd take depending on LACP/CEF splits.

Re: TorIX Upgrade

Tue, 22 Jan 2013 20:31:30 EDT

DrugTito posted :

said by Johny:

Ah alright. yeah seems like I'm the only one getting the high ping. my friends on rogers and bell are pinging fine

Different route probably ;)

Re: TorIX Upgrade

Tue, 22 Jan 2013 20:27:53 EDT

Johny posted : Ah alright. yeah seems like I'm the only one getting the high ping. my friends on rogers and bell are pinging fine

Re: TorIX Upgrade

Tue, 22 Jan 2013 20:25:04 EDT

rocca posted :

said by Johny:

Hmmm yeah that 8th hop is always hovering 130ms. Nothing on your end rocca? This is poo :(

Sorry, no, we don't have much influence 8 hops out. ;)

Re: TorIX Upgrade

Tue, 22 Jan 2013 20:24:15 EDT

rocca posted : Could also be one hop up:

core1-toronto1>ping 64.202.119.69

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 64.202.119.69, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 16/17/20 ms
core1-toronto1>ping 75.102.43.122

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 75.102.43.122, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 108/113/120 ms

...but whatever it is, looks like it's in scnet's network.

Re: TorIX Upgrade

Tue, 22 Jan 2013 20:23:13 EDT

Johny posted : Hmmm yeah that 8th hop is always hovering 130ms. Nothing on your end rocca? This is poo :(

Re: TorIX Upgrade

Tue, 22 Jan 2013 20:19:08 EDT

rocca posted : nLayer isn't up yet, but the problem you're seeing appears to be with Server Central - ie the link between hop 10 and 11. The higher latency on hop 8 is likely just a lower prioritization on ICMP traffic since the hops behind it are showing good latency and of course traffic to hop 9 had to go through hop 8. :)

Re: TorIX Upgrade

Tue, 22 Jan 2013 20:17:33 EDT

DrugTito posted : They did not.

As you can see its going HE.net then NLAYER.

There is no direct connection to NLayer yet.

Re: TorIX Upgrade

Tue, 22 Jan 2013 20:12:39 EDT

Johny posted : Looks like you guys got nlayer hooked up, and with that I've noticed a 70ms increase to a certain ip range that I use alot. What's up with that?

Tracing route to unknown.iad.scnet.net [75.102.43.162]
over a maximum of 30 hops:

1 16 ms 9 ms 10 ms 10.106.19.129
2 12 ms 11 ms 11 ms 69.63.242.29
3 38 ms 11 ms 23 ms 69.63.249.173
4 17 ms 19 ms 23 ms v514.core1.tor1.he.net [216.66.0.53]
5 13 ms 12 ms 25 ms torix.tge2-3.ar1.tor1.ca.nlayer.net [206.108.34.
53]
6 75 ms 26 ms 25 ms xe-1-0-1.cr1.nyc3.us.nlayer.net [69.22.142.61]
7 32 ms 29 ms 38 ms xe-0-2-1.cr1.iad1.us.nlayer.net [69.22.142.92]
8 134 ms 148 ms 137 ms as23352.xe-1-3-0-101.cr1.iad1.us.nlayer.net [69.
31.30.21]
9 44 ms 60 ms 46 ms 50.ae0.cr2.iad1.us.scnet.net [64.202.119.69]
10 38 ms 33 ms 42 ms as36352.ge-1-1-5.cr2.iad1.us.scnet.net [75.102.4
3.122]
11 119 ms 116 ms 122 ms unknown.iad.scnet.net [75.102.43.162]

Trace complete.

Re: TorIX Upgrade

Sat, 19 Jan 2013 00:04:10 EDT

rocca posted :

said by k3d3:

If I switch to Start, do I incur the setup fee?

No if you have an active cable internet connection at the same address and just transferring it to us then there is no installation fee applicable.

Re: TorIX Upgrade

Fri, 18 Jan 2013 20:43:51 EDT

k3d3 posted : shaded, if start has a fairly little used 10gbit torix link and OVH has a half-used 20gbit (total) link, then you will pretty much be guaranteed a good link. In this case, performance is not the reason Bell is preferred. Also, this is on OVH's end, though you've also mentioned this.

rocca, I am currently with TekSavvy. If I switch to Start, do I incur the setup fee?

Thanks

Re: TorIX Upgrade

Fri, 18 Jan 2013 19:32:35 EDT

rocca posted : BGP makes path selection by prefix size, and then AS path length (not number of hops) and it appears they are directly connected to Bell in their Montreal DC, so their router looks at these options:

577 (Bell) -> 40788 (Start)
11670 (TorIX) -> 40788 (Start)

...so you have equal length paths, one you have to use your backhaul to Toronto for and one you get to dump off in Montreal. Before the holidays we sent them a direct peer request via the TorIX portal, didn't get a response - I'll followup sometime next week. If we did directly peer then the TorIX ASN becomes removed from the equation and it'd just look like:

577 40788
40788

...in which case the later would be selected (assuming they don't pad out their connection to Toronto).

Re: TorIX Upgrade

Fri, 18 Jan 2013 18:57:12 EDT

ultramancool posted : Uhh, trace from teksavvy to OVH, it goes through torix over public peering.

Tracing ...........*T
TTL LFT trace to XXXXXXX.cable.teksavvy.com (XX.XX.XX.XX):80/tcp
1 192.95.27.253 1.4ms
2 bhs-g1-6k.qc.ca (198.27.73.13) 0.5ms
3 mtl-2-6k.qc.ca (198.27.73.4) 2.1ms
4 tor-1-6k.on.ca (178.32.135.70) 9.8ms
5 gw-teksavvy.torontointernetxchange.net (206.108.34.67) 8.9ms
6 2120.ae0.bdr02.tor.packetflow.ca (69.196.136.65) 65.3ms
7 richmond3.cable.teksavvy.com (24.52.255.74) 15.0ms

Re: TorIX Upgrade

Fri, 18 Jan 2013 18:08:05 EDT

jmck posted : i understand that, and usually providers will give preference to public/private peers to cut transit costs too so my concern is that they're avoiding TorIX for performance reasons.

I've talked to OVH network group a bit the last few months and managed to get TSI and OVH to setup a private peer at TorIX to get around bad performance through the public peer. They would likely be open setting up a private peer too with Start. If rocca's interested, he can reach their network group by contacting support@ovh.ca.

Re: TorIX Upgrade

Fri, 18 Jan 2013 16:29:39 EDT

hmph posted : OVH has 2x 10gbit connections to TorIX that generally peak at 10gbits. Start has 10gbit to TorIX with large amounts of spare capacity. I have already opened a ticket with OVH to make the change. In the end this should shave off ~10ms from the route. Why allow Bell to route the traffic all over the place when you can have a direct route between Start and OVH. It's a lot more cost effective and better for all end users performance wise including you. This is what TorIX is for after all...

Re: TorIX Upgrade

Fri, 18 Jan 2013 15:56:38 EDT

jmck posted : are you actually seeing performance issues going from ovh to start? I ran some tests a few weeks ago and saw none. if ovh is having any capacity or performance issues going to start through TorIX you might not want them to statically route it.

Re: TorIX Upgrade

Fri, 18 Jan 2013 15:21:23 EDT

hmph posted : Alright, OVH's fault. Start is routing nicely. Time to complain to OVH...

Re: TorIX Upgrade

Fri, 18 Jan 2013 14:36:40 EDT

rocca posted : traceroute to ## , 30 hops max, 40 byte packets
1 core1-london1-ge1-120.net.start.ca (64.140.120.1) 1.275 ms 0.268 ms 0.281 ms
2 core1-toronto1-te3-2.net.start.ca (64.140.112.86) 4.915 ms 5.778 ms 4.538 ms
3 gw-ovh.torontointernetxchange.net (206.108.34.189) 4.418 ms 7.607 ms 4.282 ms
4 mtl-2-6k.qc.ca (178.32.135.71) 22.669 ms 22.836 ms 22.479 ms
5 bhs-g2-6k.qc.ca (198.27.73.7) 23.755 ms * 23.654 ms
6 bhs-1-6k.qc.ca (198.27.73.14) 59.77 ms * 30.847 ms
7 ## 45.651 ms 23.579 ms 21.713 ms

Re: TorIX Upgrade

Fri, 18 Jan 2013 13:19:51 EDT

hmph posted : merc, it had the same outcome. Start buys Bell transit (at least I think they do considering Bell doesn't connect to anyone unless they are paid quite a bit) so it is still in their BGP mix. It is possible that in this case it could be OVH's fault. Currently waiting for trace from Start->OVH path to determine if both the paths are identical.

Re: TorIX Upgrade

Fri, 18 Jan 2013 12:11:06 EDT

merc782 posted : your IP range is advertised by both your AS and Bell. i think thats the reason for the routing issue

»bgp.he.net/ip/204.101.248.50

@OP, try traceroute to ns1.start.ca 64.140.120.21, this is annouced only by Start, not Bell

Re: TorIX Upgrade

Fri, 18 Jan 2013 00:43:56 EDT

rocca posted : Hard to say, we advertise our space to them via the TorIX fabric, they must have some reason they are selecting our Bell route instead. If you want to PM me your colo box IP I can see what the reverse looks like.

Re: TorIX Upgrade

Fri, 18 Jan 2013 00:39:55 EDT

rocca posted : It's a peering exchange where networks can see each other directly without having to go out to the 'general internet' to pass traffic. Generally this results in shorter paths, lower latency, etc for both networks involved in the transmission.

Re: TorIX Upgrade

Fri, 18 Jan 2013 00:39:28 EDT

hmph posted : I am being routed to your TorIX IP via OVH but only to your TorIX assigned IP, not sure why regular traffic is not routing through there as well.

Goes through TorIX here:
ping 206.108.34.187
PING 206.108.34.187 (206.108.34.187) 56(84) bytes of data.
64 bytes from 206.108.34.187: icmp_req=1 ttl=251 time=8.60 ms
64 bytes from 206.108.34.187: icmp_req=2 ttl=251 time=8.64 ms
64 bytes from 206.108.34.187: icmp_req=3 ttl=251 time=8.71 ms
64 bytes from 206.108.34.187: icmp_req=4 ttl=251 time=8.93 ms

Traceroute is pretty much blocked for this route, so I won't bother.

Goes over bell here:

ping start.ca
PING start.ca (204.101.248.50) 56(84) bytes of data.
64 bytes from ws01-010.start.ca (204.101.248.50): icmp_req=1 ttl=58 time=24.1 ms
64 bytes from ws01-010.start.ca (204.101.248.50): icmp_req=2 ttl=58 time=23.9 ms
64 bytes from ws01-010.start.ca (204.101.248.50): icmp_req=3 ttl=58 time=21.9 ms
64 bytes from ws01-010.start.ca (204.101.248.50): icmp_req=4 ttl=58 time=22.0 ms

start.ca
traceroute to start.ca (204.101.248.50), 30 hops max, 60 byte packets
1 <> (<>) 0.726 ms * *
2 bhs-g1-6k.qc.ca (198.27.73.17) 0.673 ms * *
3 mtl-2-6k.qc.ca (198.27.73.4) 2.206 ms * *
4 198.27.73.178 (198.27.73.178) 146.046 ms * *
5 bx5-chicagodt.bell.ca (206.223.119.66) 17.936 ms 17.947 ms 18.217 ms
6 newcore1-chicagocp_xe-4-0-0_0.net.bell.ca (64.230.186.105) 51.864 ms 33.518 ms newcore1-chicagocp_xe3-1-1.net.bell.ca (64.230.186.81) 31.535 ms
7 tcore4-toronto12_POS0-6-0-0.net.bell.ca (64.230.147.173) 39.216 ms tcore3-toronto12_POS0-6-0-0.net.bell.ca (64.230.147.165) 35.608 ms tcore3-toronto47_POS0-2-0-0.net.bell.ca (64.230.186.125) 37.862 ms
8 CORE1-LONDON14_POS4-0-0.net.bell.ca (64.230.149.225) 35.577 ms CORE2-LONDON14_POS12-0-0.net.bell.ca (64.230.149.221) 34.011 ms CORE1-LONDON14_POS4-0-0.net.bell.ca (64.230.149.225) 35.839 ms
9 dis20-london14_7-0-0.net.bell.ca (64.230.112.6) 69.630 ms 69.593 ms 69.612 ms
10 ws01-010.start.ca (204.101.248.50) 23.782 ms 23.765 ms 23.987 ms