|
to rocca
Re: TorIX UpgradeAlright, OVH's fault. Start is routing nicely. Time to complain to OVH... |
|
|
jmckformerly 'shaded' join:2010-10-02 Ottawa, ON |
jmck
Member
2013-Jan-18 3:56 pm
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. |
|
1 edit |
hmph
Member
2013-Jan-18 4:29 pm
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... |
|
jmckformerly 'shaded' join:2010-10-02 Ottawa, ON |
jmck
Member
2013-Jan-18 6:08 pm
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. |
|
|
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 |
|
roccaStart.ca Premium Member join:2008-11-16 London, ON |
rocca to hmph
Premium Member
2013-Jan-18 7:32 pm
to hmph
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). |
|
|
to jmck
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 |
|
roccaStart.ca Premium Member join:2008-11-16 London, ON |
rocca
Premium Member
2013-Jan-19 12:04 am
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. |
|
rocca |
rocca to hmph
Premium Member
2013-Jan-29 10:43 am
to hmph
We have a direct peering relationship with OVH now. |
|
jmckformerly 'shaded' join:2010-10-02 Ottawa, ON |
jmck
Member
2013-Jan-29 10:54 am
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 2013
Keys: 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
|
|
|
to rocca
» 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 |
|
roccaStart.ca Premium Member join:2008-11-16 London, ON |
rocca
Premium Member
2013-Feb-6 12:04 am
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 |
|
1 edit |
thanks for checking it out. It looks like network between Amsterdam and London is overloaded » weathermap.ovh.net/ |
|
jmckformerly 'shaded' join:2010-10-02 Ottawa, ON |
to rocca
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. |
|