Shaw throttling OVH connections Max 1 Mb/s UPLOAD

[DerekWarne]

The issue I and my co worker that are on shaw is that we are capped at 1-2 Mb/s upload on shaw to any OVH server. Our company used OVH to host our dedicated server and are moving files to and from them a lot and these are large files over 1Gig. We have 2 OVH servers running different services and they both have this issue, no matter the server, service, port or protocol the transfer will start at expected speeds then after 30 seconds it will fall below to sub 1 mb/s. If you take those same clients and change nothing exept using Shaw you get full speeds. If you use a TELUS or mobile hotspot connection you get expected speeds, if you are on shaw and use a VPN you also get full speeds. Due to this we expect there is a routing issue with shaw/shaw is throttling uploads to OVH for some reason. The download is unaffected and can pull full gigabit down so we know the bandwidth space is there.

This is what we used for testing.

One server is Ubuntu and one RHEL running different services and they both have a cap on upload. We tested on two different connections from shaw, one running the shaw router the other using a PFsense box and both connections have the same issue. We did a clean install with the out of box fedora image on a new OVH server with nothing else added/edited and still have the issue. This issue was first found on FTP/SFTP connections but then after testing found this issue is on all ports/protocols.

If anyone can suggest a solution as how to fix this issue or if a shaw rep could recommend or call us that would be much appreciated.

[mdk]

@DerekWarne wrote: Due to this we expect there is a routing issue with Shaw throttling uploads to OVH for some reason. The download is unaffected and can pull full gigabit down so we know the bandwidth space is there.

If you suspect a routing issue, use the Windows command-line "tracert.exe" with the "-4" option, to show the IPv4 routing between your computer & the OVH server, and post the results here. Example:

$ tracert -4 www.ovh.net

11 ms 11 ms    rc1wt-be40.wa.shawcable.net [66.163.68.18]
             14 ms     ae22.cr4-sea2.ip4.gtt.net [209.120.141.209]
11 ms 11 ms    sea-b1-link.ip.twelve99.net [213.248.88.190]
11 ms 11 ms    sea-b3-link.ip.twelve99.net [62.115.132.156]
15 ms 15 ms  port-b2-link.ip.twelve99.net [62.115.139.132]
14 ms 17 ms pdx-pdx02-pb1-nc5.oregon.us [192.99.146.52]

Vancouver -> WA(shington state) -> Seattle (WA) -> Portland (Oregon) -> PDX (airport code for Portland airport)

I think that your trace will show a path from Calgary to Vancouver, on Shaw's backbone, and then the same path.

[DerekWarne]

Trace root to our test servers

Tracing route to sv1.slashwarp.com [142.4.212.196]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 10.0.0.1
2 12 ms 9 ms 11 ms 184.66.224.1
3 12 ms 10 ms 10 ms rd2bb-be101-1.no.shawcable.net [64.59.162.141]
4 16 ms 16 ms 10 ms rc1wt-be40.wa.shawcable.net [66.163.68.18]
5      *         *       13 ms ae22.cr4-sea2.ip4.gtt.net [209.120.141.209]
6 13 ms 16 ms 16 ms sea-b1-link.ip.twelve99.net [213.248.88.190]
7 13 ms 12 ms 17 ms sea-b3-link.ip.twelve99.net [62.115.132.156]
8 19 ms 16 ms 16 ms port-b2-link.ip.twelve99.net [62.115.139.132]
9 16 ms 17 ms 16 ms pdx-pdx02-pb1-nc5.oregon.us [192.99.146.52]
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 82 ms * 82 ms be105.chi-ch2-sbb2-8k.il.us [142.44.208.160]
14 80 ms 78 ms 85 ms be103.bhs-g2-nc5.qc.ca [192.99.146.140]
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 80 ms 83 ms 83 ms sv1.slashwarp.com [142.4.212.196]

Trace complete.

Tracing route to sv2.slashwarp.com [142.4.216.6]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 10.0.0.1
2 8 ms 10 ms 10 ms 184.66.224.1
3 9 ms 11 ms 11 ms rd2bb-be101-1.no.shawcable.net [64.59.162.141]
4 12 ms 15 ms 15 ms rc1wt-be40.wa.shawcable.net [66.163.68.18]
5      *      17 ms 15 ms ae22.cr4-sea2.ip4.gtt.net [209.120.141.209]
6 12 ms 14 ms 16 ms sea-b1-link.ip.twelve99.net [213.248.88.190]
7 14 ms 14 ms 15 ms sea-b3-link.ip.twelve99.net [62.115.132.156]
8 20 ms 21 ms 22 ms port-b2-link.ip.twelve99.net [62.115.139.132]
9 18 ms 20 ms 21 ms pdx-pdx02-pb1-nc5.oregon.us [192.99.146.52]
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 75 ms 78 ms 75 ms be103.bhs-g2-nc5.qc.ca [192.99.146.140]
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 80 ms 78 ms 77 ms sv2.slashwarp.com [142.4.216.6]

             -----         OVH main web servers         ----         

over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 10.0.0.1
2 14 ms 4 ms 10 ms 184.66.224.1
3 10 ms 15 ms 10 ms rd2bb-be101-1.no.shawcable.net [64.59.162.141]
4 15 ms 16 ms 12 ms rc1wt-be40.wa.shawcable.net [66.163.68.18]
5 17 ms 16 ms 15 ms ae22.cr4-sea2.ip4.gtt.net [209.120.141.209]
6 12 ms 14 ms 15 ms sea-b1-link.ip.twelve99.net [213.248.88.190]
7 16 ms 11 ms 16 ms sea-b3-link.ip.twelve99.net [62.115.132.156]
8 17 ms 18 ms 16 ms port-b2-link.ip.twelve99.net [62.115.139.132]
9 13 ms 21 ms 15 ms pdx-pdx02-pb1-nc5.oregon.us [192.99.146.52]
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 78 ms 80 ms 79 ms be103.bhs-g2-nc5.qc.ca [192.99.146.140]
15 * * * Request timed out.
16 82 ms 77 ms 76 ms be7.bhs-iplb1-a70.qc.ca [178.32.135.81]
17 79 ms 79 ms 78 ms www.ovh.com [198.27.92.1]

Trace complete.

C:\Users\dwarne>tracert ovhcloud.com

Tracing route to ovhcloud.com [54.39.46.56]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 10.0.0.1
2 8 ms 10 ms 10 ms 184.66.224.1
3 12 ms 10 ms 10 ms rd2bb-be101-1.no.shawcable.net [64.59.162.141]
4 15 ms 16 ms 16 ms rc1wt-be40.wa.shawcable.net [66.163.68.18]
5 16 ms 15 ms 16 ms ae22.cr4-sea2.ip4.gtt.net [209.120.141.209]
6 14 ms 17 ms 15 ms sea-b1-link.ip.twelve99.net [213.248.88.190]
7 16 ms 16 ms 15 ms sea-b3-link.ip.twelve99.net [62.115.132.156]
8 16 ms 16 ms 21 ms port-b2-link.ip.twelve99.net [62.115.139.132]
9 16 ms 16 ms 20 ms pdx-pdx02-pb1-nc5.oregon.us [192.99.146.52]
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 81 ms * 81 ms be105.chi-ch2-sbb2-8k.il.us [142.44.208.160]
14 78 ms 184 ms 81 ms be103.bhs-g2-nc5.qc.ca [192.99.146.140]
15 * * * Request timed out.
16 77 ms 77 ms 77 ms be7.bhs-iplb2-a70.qc.ca [178.32.135.133]
17 80 ms 82 ms 78 ms www.ovh.fr [54.39.46.56]

Trace complete.

-------------- Google for controll ---------------------

Tracing route to google.com [142.251.211.238]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 10.0.0.1
2 12 ms 10 ms 10 ms 184.66.224.1
3 11 ms 10 ms 10 ms rd2bb-be101-1.no.shawcable.net [64.59.162.141]
4 14 ms 16 ms 16 ms rc1wt-be40.wa.shawcable.net [66.163.68.18]
5 18 ms 16 ms 15 ms 72.14.221.102
6 19 ms 15 ms 16 ms 142.251.229.137
7 15 ms 16 ms 16 ms 216.239.43.121
8 15 ms 15 ms 15 ms sea30s13-in-f14.1e100.net [142.251.211.238]

Trace complete.

[DerekWarne · Accepted solution]

After about a year of this issue and countless phone calls to shaw/rogers, I fixed the issue by switching to telus...

Issue still with OVH servers as of December 2024, tests again on the same day with the same device, file, and server.I would get 500 kb/s on shaw/rogers switch to the telus connection and getting 100Mb/s. Don't know why shaw/rogers failed to care but far happier with my Telus connection and not having to deal with this issue anymore.

Best of luck to others that have the same issue