O Canada! > Canadian > TekSavvy > [Cable] Whys everything so slow tonight

[Cable] Whys everything so slow tonight

I'm crawling as well.
London POI.

»www.speedtest.net/result/2548769326.png

reply to Robleh
I thought it was my modem. Checked modem and stuff, everything's fine. Was ready to call tech support. Then I thought to test my remote server. Almost full speed from it, getting ~1.7MB from 50 simultaneously connections, should be getting ~2MB. Not indicative of any serious problem. Pings are fine. No packet loss. But Speedtest.net is all over the place from 3 to 12Mbps. Bell speed test not that great either.

DSL/Montreal here.
--
My blog. Wanna Git My Ball on Blogspot.

reply to Robleh


Yup...

Even after a DHCP release and renew which typically solves any slow downs, still the same:

It's the speedtest server, at least for some of us. My connection is fine, but the TSI speed test server makes it look horrible. Make sure to choose the server manually and if you're in the GTA, try Beanfield.

TSI:

i just went to www.speedtest.net and picked the best server for me.. can't get over 200kbps in my dls :/

reply to The Mongoose
Hmmm pretty good catch Mongoose:

reply to Robleh

reply to Robleh
»puu.sh/2bM1a there u go picked the right server ugh

That's the Nexicom server....but I'm getting good results on that one so looks like you've got something else going on unfortunately.

I don't think the POI is overloaded...is this the first night of this?

reply to Robleh
Yeah first time seeing speeds like this, on weekends i used to get 20/28mbps..

reply to Robleh
Try Bayfield. Getting 95% of max DL.

»www.speedtest.net/result/2548836674.png

-edit- Note: We're all in Toronto as far as the internet is concerned.

--
My blog. Wanna Git My Ball on Blogspot.

reply to Robleh

reply to Robleh
tatus Code: Operational
Software Version: STAC.02.50
Software Model: a81a
Bootloader: 2.3.1

Cable Signal Details
Forward Path:
Channel Frequency Power SNR BER Modulation
1 663.0 MHz -3.7 dBmV 40.3 dB 0.000 % 256 QAM
2 615.0 MHz -3.8 dBmV 40.3 dB 0.000 % 256 QAM
3 621.0 MHz -3.3 dBmV 40.2 dB 0.000 % 256 QAM
4 633.0 MHz -3.6 dBmV 40.7 dB 0.000 % 256 QAM
5 639.0 MHz -3.6 dBmV 40.4 dB 0.000 % 256 QAM
6 645.0 MHz -3.5 dBmV 40.8 dB 0.000 % 256 QAM
7 651.0 MHz -3.4 dBmV 40.6 dB 0.000 % 256 QAM
8 657.0 MHz -3.3 dBmV 40.3 dB 0.000 % 256 QAM
Return Path:
Channel ID Frequency Power Modulation
3 22.1 MHz 42.5 dBmV 16 QAM
1 31.3 MHz 44.5 dBmV 16 QAM
2 25.3 MHz 42.5 dBmV 16 QAM
4 38.6 MHz 42.5 dBmV 16 QAM
Data Service Details
Provisioned Address: Yes
Provisioned Time: Yes
Provisioned Configuration: Yes
Registered: Yes
BPI: Enabled

seems ok

Yeah, better than mine.

What's really interesting is that your ping is still good...which really makes me wonder about this. I'll post anything I can come up with, in the meantime I'd post that speedtest in the direct forum and see if they know of trouble in your area.

reply to The Mongoose
Tracing route to speedtest.teksavvy.com [206.248.140.50] over a maximum of 30 hops:

1 1 ms 1 ms 1 ms [192.168.0.2]
2 7 ms 7 ms 13 ms 10.124.165.1
3 11 ms 11 ms 11 ms 24.156.151.145
4 10 ms 9 ms 9 ms 24-52-255-166.cable.teksavvy.com [24.52.255.166]
5 13 ms 12 ms 11 ms london1.cable.teksavvy.com [24.246.55.25]
6 189 ms 74 ms 64 ms 2110.ae0.agg01.tor.packetflow.ca [69.196.136.44]
7 68 ms 73 ms 61 ms speedtest.teksavvy.com [206.248.140.50]

Trace complete.

Seems to be that packetflow hop.

Ping statistics for 69.196.136.44:
Packets: Sent = 20, Received = 19, Lost = 1 (5% loss),
pproximate round trip times in milli-seconds:
Minimum = 63ms, Maximum = 94ms, Average = 70ms

And possibly anything going through 206.248.155.125. (in my case I was trying to download content from another provider peered at torix)

Tracing route to 206.248.155.125 over a maximum of 30 hops

1 1 ms 1 ms 1 ms [192.168.0.2]
2 7 ms 7 ms 8 ms 10.124.165.1
3 12 ms 15 ms 11 ms 24.156.151.145
4 34 ms 9 ms 9 ms 24-52-255-166.cable.teksavvy.com [24.52.255.166]
5 12 ms * 13 ms 24-52-255-165.cable.teksavvy.com [24.52.255.165]
6 53 ms 53 ms 58 ms 206.248.155.125

Trace complete.

Ping statistics for 206.248.155.125:
Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 48ms, Maximum = 79ms, Average = 59ms

Seems fixed. Wonder what the problem was.

»www.speedtest.net/result/2548953405.png

Ping statistics for 69.196.136.44:
Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 10ms, Maximum = 53ms, Average = 16ms

Ping statistics for 206.248.155.125:
Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 11ms, Maximum = 77ms, Average = 17ms

improvement

reply to Robleh
Scarlett POI has been crawling for a while now since after »[OUTAGE REPORT] Feb 22nd, 2013 06:40PM

Tracing route to google.ca [74.125.226.55]
over a maximum of 30 hops:
 
  1    12 ms     *        9 ms  N3500L [192.168.0.1]
  2   797 ms   757 ms   785 ms  10.126.180.1
  3   974 ms   914 ms   867 ms  24.156.150.161
  4   840 ms   812 ms   565 ms  24-52-255-50.cable.teksavvy.com [24.52.255.50]
  5   978 ms  1003 ms  1059 ms  scarlett1.cable.teksavvy.com [24.246.55.105]
  6   566 ms   392 ms   142 ms  gw-google.torontointernetxchange.net [206.108.34
.6]
  7   487 ms   576 ms   388 ms  216.239.47.114
  8   588 ms   471 ms     *     64.233.175.132
  9   694 ms   743 ms   654 ms  yyz06s06-in-f23.1e100.net [74.125.226.55]
 
Trace complete.
 
 

reply to Robleh
Glad to hear it's looking better, if the issue recurs please post in the direct forum here:»TekSavvy Direct and we can investigate further with you.

Thank you,
Keith
--
TSI Keith (E-Services) - TekSavvy Solutions Inc.
Authorized TSI employee ( »TekSavvy FAQ »Official support in the forum )