| [DSL] Horrible DSL every night - Anyone else? In the past there was talk of many people having poor DSL stats at night time. Am I the only one anymore? I never read of anyone having issues like I still have.
It has gotten to the point now that no one can play any online games, download, Youtube after 5pm or peak times as it is just horrible.
500 ms pings, 0.8 mbps DL, less than 0.08 kbps uploads.
I have ping tests, tracert tests, Speedtest.net results. All suck at night. Daytime (when at work) it is excellent.
I have done the straight to modem tests but everything is fine during the day with IPCop router and giga-switch but in the afternoon when I come home from work the big black hole of Internet suckage gobbles up my connection and sh!ts a brick.
I have in the past gone through the Direct Support, had a Bell tech in the house looking things over but all during day time so of course no issue. It all looks and feels like congestion but I can't see how as I live in the backass of nowhere within 2km of a village with a population of 500 people. The DSL (the only option of course) used to be great but as of the last 6 months to a year has steadily declined to being useless when I'm home.
Anyone else still suffering in DSLell.
Signed,
Suffering Alone in the dark |
|
 TSI AlanPremium
join:2012-11-22
Chatham, ON | Hello,
Sorry to hear of your nightly DSL issues.
Can you post your account details in Direct and we can look into this for you.
Thank you.
--
TSI Alan (E-Services) - TekSavvy Solutions Inc.
Authorized TSI employee
Follow us on Twitter: @TekSavvyCSR; @TekSavvyNetwork |
|
| reply to Jethro86
Did you check the actual "line stats" (mainly attenuation and SNRM) or are your "line stats" only about performance in general?
I have not checked if the nightly performance issues I was seeing a few weeks ago have been resolved but my line stats were perfectly fine while I was experiencing nearly unusable performance very similar to what you described - 200+ms pings, 1-3Mbps download on a 6M/800k sync with 25dB SNRM.
So my line stats are for all intents and purposes perfect but performance was nowhere to be seen. |
|
| When I last attempted to have this resolved TSI check my line stats and said all way fine.
From TSI Martin last year:
"Hello,
Here are current line stats. All looks good on that front.
GAS: 613-###-#### - In Service
Last State Change: 08/24 20:29:58 (Uptime: NA)
Line Profile: al1_d6016-6016-384_u800-800-256
DLM State: DISABLED | Equip. Type: ZSLAM
Sync Rate: d6016.0/u800.0 kbps
RCO: d75.0/u67.0%
Noise Margin: d12.0/u16.0 dB
Power: d4.0/u4.0 dB
Attenuation: d36.0/u23.0 dB (Approx. Distance: 2.61~3.28km)
Block Count: dNA/uNA |
|
| SNRMs are a little low but still plenty high enough to make speed degradation unlikely. Certainly not all the way down to 1-2Mbps.
If you are using an @hsiservice (IPv6) login, you might want to try the regular @teksavvy.com login instead. I stopped using my @hsiservice a few weeks ago because it was slow and laggy to the point of becoming unusable while the normal login was getting close to normal speeds and latency. |
|
Reviews:
 ·TekSavvy DSL
| reply to Jethro86
There does appear to be an issue with DSL. It is not 100% clear if the issue is on the Bell side or the TSI side of things. It does seem to vary depending on which AGAS link you are on. Some seem to be worse than others (which would point to it being congestion on the links, but TSI has stated that the links are "generally" not suffering from congestion). I'm currently on a good link and only see minor issues every night. Before my last reconnect I was on a really bad link and was seeing 1-10% packet loss from about 12:00 to 24:00.
Try disconnecting and reconnecting a few times and see if it helps. You may need to wait a bit while disconnected. |
|
| reply to Jethro86
I have recently noticed my speeds on DSL have been between 300 to 1000 from as early as 2:30 in the afternoon lasting until midnight.
While I am seeing reduced download speeds my ping and upload are both where they should be. At least it's still running smoothly during this period so I can't quite call it horrible.
Today at 2:30pm for example, running just fine.
|
|
|
|
| reply to Jethro86
I was experiencing the same thing as you. Fortunately Cable via the new Cogeco offerings became available to me right about the same time so I am now enjoying the 20/2 Unlimited TSI cable package.
We did do some troubleshooting, but nothing jumped out on my line either as to why stats were so awful during prime hours.
--
Matt |
|
| reply to Jethro86
Here's my April 1st All DSL Fools day Speedtest.net results
4/1/2013 7:21 AM EDT 69.196.191.77 4.99 Mb/s 0.50 Mb/s 18 ms Toronto, ON --- Beautiful.. nice and fast but off to work.
4/1/2013 6:33 PM EDT 69.196.191.77 2.94 Mb/s 0.29 Mb/s 345 ms Toronto, ON --- Home again.. let's play some Planetside 2.... Oh wait.. why are tanks flying?
4/1/2013 8:00 PM EDT 69.196.191.77 1.27 Mb/s 0.20 Mb/s 506 ms Toronto, ON --- Maybe now?
4/1/2013 8:47 PM EDT 69.196.191.77 0.37 Mb/s 0.23 Mb/s 555 ms Toronto, ON --- How about now?
4/1/2013 9:05 PM EDT 69.196.191.77 0.32 Mb/s 0.21 Mb/s 583 ms Toronto, ON --- I'm gonna go watch TV |
|
warren
join:2008-02-28
St Catharines, ON | reply to Jethro86
I've experienced the same problem off and on. I was hoping it'd get fixed when switching to VDSL2 but it doesn't seem to have. My pings don't get affected, just download.
I just got 25/10 installed yesterday, checked speedtest in the morning, maxed out my connection (was around 8:00am - the tech's weren't supposed to come around until 12-5pm). Came home around 8:00pm last night, ran another speed test got 15/9.94, started to creep back up later in the night.
Upstream on last one is lower than what it should - I'm RDPing in home.
4/3/2013 3:51 PM GMT 76.10.179.xx 25.18 Mb/s 9.36 Mb/s 0 ms Toronto, ON 50 mi Image
4/3/2013 2:43 AM GMT 76.10.179.xx 20.05 Mb/s 9.80 Mb/s 0 ms Toronto, ON 50 mi Image
4/3/2013 2:13 AM GMT 76.10.179.xx 22.79 Mb/s 10.04 Mb/s 0 ms Toronto, ON 50 mi Image
4/3/2013 2:13 AM GMT 76.10.179.xx 20.31 Mb/s 9.21 Mb/s 0 ms Oakville, ON 50 mi Image
4/2/2013 11:50 PM GMT 76.10.179.xx 15.06 Mb/s 9.94 Mb/s 5 ms Toronto, ON 50 mi Image
4/2/2013 5:01 PM GMT 76.10.179.xx 25.16 Mb/s 10.02 Mb/s 5 ms Toronto, ON 50 mi Image
4/2/2013 12:03 PM GMT 76.10.179.xx 25.17 Mb/s 10.04 Mb/s 3 ms Toronto, ON 50 mi |
|
warren
join:2008-02-28
St Catharines, ON | sigh...
4/4/2013 2:06 AM GMT 76.10.179.xx 11.73 Mb/s 9.67 Mb/s 0 ms Toronto, ON 50 mi Image
4/3/2013 10:38 PM GMT 76.10.179.xx 25.14 Mb/s 10.07 Mb/s 0 ms Toronto, ON 50 mi Image |
|
| Thanks for hijacking my thread warren but I don't see how you "only" getting 10 or 15mbp download on your 25mbps is in anyway related how my 6mbps only gets 0.3mbps.
I would lick a cat's ass to "only" get 10 or 15mbps and your *sigh* for getting 25mbps download at 9:30pm? Come on.
That just adds fuel to my angry fire and does nothing to help my situation.
I am just waiting for the day when Bell finally comes out (or Teksavvy catches them) and says "Oh ya we were doing that." like they did with the torrent throttling. Then I will feel vindicated. |
|
 apvm
join:2003-02-14
London, ON
kudos:1 | reply to Jethro86
Same here, for the past months, it starts to slow down at around 4:30-5pm and will pick up speed again at around 9:30-10pm. I have 6M DSL and my usual speed is around 5.7M but will slow down to less than 1M (around 0.5M) at night.
TSI checked my line last month and told me all ok but I think their server is seriously overload. |
|
| reply to Jethro86
Current Situation: Looks like local issue as it's even before I can get out to Internet.
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
>ping www.teksavvy.com
Pinging www.teksavvy.com [206.248.155.70] with 32 bytes of data:
Reply from 206.248.155.70: bytes=32 time=481ms TTL=124
Reply from 206.248.155.70: bytes=32 time=525ms TTL=124
Reply from 206.248.155.70: bytes=32 time=580ms TTL=124
Reply from 206.248.155.70: bytes=32 time=585ms TTL=124
Ping statistics for 206.248.155.70:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 481ms, Maximum = 585ms, Average = 542ms
>tracert www.teksavvy.com
Tracing route to www.teksavvy.com [206.248.155.70]
over a maximum of 30 hops:
1 ping www.google.ca
Pinging www.google.ca [173.194.43.120] with 32 bytes of data:
Reply from 173.194.43.120: bytes=32 time=408ms TTL=58
Reply from 173.194.43.120: bytes=32 time=478ms TTL=58
Reply from 173.194.43.120: bytes=32 time=522ms TTL=58
Reply from 173.194.43.120: bytes=32 time=505ms TTL=58
Ping statistics for 173.194.43.120:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 408ms, Maximum = 522ms, Average = 478ms
>tracert www.google.ca
Tracing route to www.google.ca [173.194.43.120]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 192.168.2.1
2 573 ms 608 ms 688 ms lo-100.lns02.tor.packetflow.ca [206.248.154.122]
3 546 ms 513 ms 521 ms 2120.ae0.bdr01.tor.packetflow.ca [69.196.136.66]
4 658 ms 647 ms 657 ms gw-google.torontointernetxchange.net [206.108.34.6]
5 518 ms 530 ms 511 ms 209.85.255.232
6 468 ms 476 ms 499 ms 72.14.239.73
7 533 ms 584 ms 538 ms yyz08s10-in-f24.1e100.net [173.194.43.120]
Trace complete. |
|
Reviews:
·Primus Telecommu..
| reply to Jethro86
You're still on Bell's legacy ATM network. Could be the SLAM's uplink or the BRAS. Either way, use the test@test account if you haven't already done so and run latency tests to 10.x.x.1. Send that info the Teksavvy and hope Bell doesn't give you a timeline of three to six months for the fix. |
|
| The OP's ping results are very similar to what I was seeing on the @hsiservice domain a few weeks ago. Pings to the test@test gateway were perfectly fine and pings to the internet using the regular @teksavvy domain were much better than when using @hsiservice.
Next time I need to mess with my router, I'll try to remember trying @hsiservice again, see if any of TSI's maintenance over the last couple of weeks helped anything. |
|
