O Canada! > Canadian > TekSavvy > [Cable] Slow Speeds - Ottawa

[Cable] Slow Speeds - Ottawa

Looks like you are not using the Teksavvy DNS servers and are getting sent to servers further away.

C:\>tracert appldnld.apple.com
 
Tracing route to a1271.gi3.akamai.net [72.246.43.57]
over a maximum of 30 hops:
 
  1    <1 ms    <1 ms    <1 ms  dlinkrouter [192.168.0.1]
  2     7 ms     7 ms     7 ms  10.125.241.1
  3    34 ms    24 ms    18 ms  69.63.242.13
  4     9 ms     7 ms     7 ms  richmond1.cable.teksavvy.com [24.246.55.14]
  5    14 ms    13 ms    14 ms  richmond2.cable.teksavvy.com [69.196.175.65]
  6    14 ms    15 ms    13 ms  Paix-tor.netarch.akamai.com [198.32.181.127]
  7    14 ms    14 ms    16 ms  a72-247-244-249.deploy.akamaitechnologies.com [72.247.244.249]
  8    15 ms    14 ms    13 ms  a72-246-43-57.deploy.akamaitechnologies.com [72.246.43.57]
 
Trace complete.
 

Swithced my dns from google ( 8.8.8.8 ) to teksavvy ( 206.248.154.22)

Speeds seem better but still half of what Rogers gets with a lower profile:

traceroute to appldnld.apple.com (184.84.239.25), 30 hops max, 60 byte packets
1 * * *
2 69.63.254.141 (69.63.254.141) 21.956 ms 22.923 ms 23.040 ms
3 richmond3.cable.teksavvy.com (24.52.255.74) 12.660 ms richmond1.cable.teksavvy.com (24.246.55.14) 12.680 ms richmond2.cable.teksavvy.com (69.196.175.66) 12.695 ms
4 richmond3.cable.teksavvy.com (24.52.255.73) 18.091 ms * 19.058 ms
5 Paix-tor.netarch.akamai.com (198.32.181.127) 19.231 ms 19.256 ms 19.315 ms
6 a184-84-239-25.deploy.akamaitechnologies.com (184.84.239.25) 19.163 ms 14.580 ms 15.548 ms

sakhter@sakhter-nas:~$ wget »appldnld.apple.com/AppleTV/061-9···ore.ipsw
--2012-11-19 15:58:21-- »appldnld.apple.com/AppleTV/061-9···ore.ipsw
Resolving appldnld.apple.com (appldnld.apple.com)... 184.84.239.42, 184.84.239.25
Connecting to appldnld.apple.com (appldnld.apple.com)|184.84.239.42|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 332470394 (317M) [application/octet-stream]
Saving to: `AppleTV2,1_4.3_8F191m_Restore.ipsw.10'

5% [========> ] 18,993,176 528K/s eta 8m 6s ^

reply to johoja
Feel free to post your account information in the direct forum so we can troubleshoot further.

Yes, I have. Topic is "Cable » TekSavvy - Ottawa -Slow Speeds by johoja" waiting for the ticket to be created.

reply to johoja
I don't expect anything to get resolved in Ottawa.

1) Most government workers will lose their job because of deep cutbacks.
2)The falling housing market will mean a much higher Canadian deficit and higher taxes
3)Canada wide recession in 2013 and probably beyond

Why would any company spend money given this scenario?

During peek times, downloads from akamai servers served by Teksavvy DNS are also slow. these servers seems to be toronto, and the teksavvy link between Ottawa & toronto seems get slow during peek hours.

I think its a good idea for Teksavvy to start peering at Ottawa Internet eXchange , this will help Teksavvy offload the akamai traffic to Federal hosted akamai servers at Ottawa IX

Anyone know if start.ca has any better reliable speeds in Ottawa ?

i'm not seeing any issues in Ottawa (the market) going through St-Laurent phub.

Anything single threaded being downloaded between 6pm and midnight, is absolute sluggish. I was getting 10mbits on the Teksavvy speedtest.net server and around the same on the other 2 Toronto speedtest.net servers.
Around an hour after midnight and later I am able to get speedboosting no problem on single threaded downloads of around 40mbits.
I am able to get 25mbits down using a multithreaded download at pretty much any time of day though.
I am on the 28/1 plan atm - Fallowfield POI.
It is obvious there is a congestion issue.

i'll do some tests tomorrow night and report back.

my 4am testing shows that cdn.plexapp.com is complete junk while the apple one is coming it at full speed. i'll redo these tests tomorrow at peak (9pm):

wget »appldnld.apple.com/AppleTV/061-9···ore.ipsw
--2012-11-21 00:59:05-- »appldnld.apple.com/AppleTV/061-9···ore.ipsw
Resolving appldnld.apple.com... 184.84.239.25, 184.84.239.42
Connecting to appldnld.apple.com|184.84.239.25|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 332470394 (317M) [application/octet-stream]
Saving to: `AppleTV2,1_4.3_8F191m_Restore.ipsw'

7% [=> ] 23,708,724 3.89M/s eta 70s ^C

wget »cdn.plexapp.com/PlexMediaServer/···i386.deb
--2012-11-21 00:58:30-- »cdn.plexapp.com/PlexMediaServer/···i386.deb
Resolving cdn.plexapp.com... 108.59.4.180
Connecting to cdn.plexapp.com|108.59.4.180|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 63410134 (60M) [application/octet-stream]
Saving to: `plexmediaserver_0.9.6.9.240-8fd9c6a_i386.deb'

7% [==> ] 4,931,888 68.0K/s eta 6m 14s ^C

Hey shaded,

What speeds do you get in possible congested times to the apple server ? i.e) 7am-12pm? Just want to see what you are getting during these times, and if it is in line with me i.e) 600K/s

typically from fast sources (akamai, apple, etc) i'll get my usual full speed even at peak. like i said earlier tho, i'll redo the same test at 9m tonight and report back.

Awesome thanks, looking forward to it. Want to see if its a congestion in the TSI network or if its a congestion localized to my area.

Jst saw you are in st. laruent poi., I go through richmond according to my traceroute.

BTW it's interesting to see that rogers is able to get 1M/s to plex while teksavvy can't break 100K/s

shaded , also what modem do you use ?

reply to johoja
1) +1 for linux!

2) What times did you do the testing? Everyday weekday afternoon, I'd say from 6pm to 11pm, slow downs are to be expected. It's when the most amount of people are online.

To be honest, it's not even slow then...I just get what I am actually allocated (28mbps) instead of bursting at 40mbps like I normally do at offpeak hours.
--
www.613websites.com ● Budget Canadian Web Design and Hosting

reply to johoja
sorry for being away last 2 days, i will do the test tomorrow (friday evening). i haven't had the chance to do more testing for you since i've been out of town.

my modem is a TSI provided DMC476.

here's more results, wasn't able to do it on Friday as planned but did do it just now at 7:25pm on Saturday. Interesting results since apple is lower while plex is higher:

Apple-TV:~ root# wget »appldnld.apple.com/AppleTV/061-9···ore.ipsw
--2012-11-24 16:24:22-- »appldnld.apple.com/AppleTV/061-9···ore.ipsw
Resolving appldnld.apple.com... 72.246.43.57, 72.246.43.50
Connecting to appldnld.apple.com|72.246.43.57|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 332470394 (317M) [application/octet-stream]
Saving to: `AppleTV2,1_4.3_8F191m_Restore.ipsw'

18% [==============> ] 61,319,098 1.25M/s eta 3m 15s ^C

Apple-TV:~ root# wget »cdn.plexapp.com/PlexMediaServer/···i386.deb
--2012-11-24 16:25:10-- »cdn.plexapp.com/PlexMediaServer/···i386.deb
Resolving cdn.plexapp.com... 108.59.11.198
Connecting to cdn.plexapp.com|108.59.11.198|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 63410134 (60M) [application/octet-stream]
Saving to: `plexmediaserver_0.9.6.9.240-8fd9c6a_i386.deb'

88% [=========================================================================> ] 55,898,592 1.28M/s eta 5s ^C

after seeing the speeds were really close, i ran a test on speedtest.net to TSI's server and seeing this:



I usually do a test every 2-3 days to TSI's speediest servers and i always see ~30mbit/sec so this is strange since it's matching roughly the same speeds to apple/plex. this means TSI Rogers or Rogers SLNT1 is saturated/slow or my modem is set to a slower speed.

starting to see some really slow speeds now that i've actually decided to test it at peak, tonight at 10pm I can only get 8mbit/sec from TSI's speedtest.net server, getting 2-5mbit from plex and apple too.

Well TSI made me buy a new 'supported' D3 modem as the '-SMCD3GN-RRR' is not supported but the -SMCD3GN-RES is , the -SMCD3GN-RRR is an ex rogers modem so ...whatever I bought a SB6120, to prove to TSI that they have network congestion issues, and Rogers doesn't.

shaded: thanks for the testing, I think it proves that TSI has some serious congestion issues, in their core network.