dslreports logo
site
 
    All Forums Hot Topics Gallery
spc

spacer




how-to block ads


Search Topic:
uniqs
2403
share rss forum feed

UK_Dave

join:2011-01-27
Powassan, ON
kudos:2

[DSL] Evening slow speeds, North Bay, ON.

Same as quite a few others - slow download speeds in the evening.

I don't know quite what this implies, but my ping goes from 35ms in the daytime, to over 600+ in the evening. Then back down again in the morning when I first log on.


TSI Martin
Premium
join:2006-02-23
Chatham, ON
kudos:33
If you'd like to post in the »TekSavvy Direct forum, we can take a look.

Regards,
Martin

phear00

join:2009-07-23
reply to UK_Dave
Same problem for me in North Bay, ON.

Dave, can you let me know how this turns out for you?

UK_Dave

join:2011-01-27
Powassan, ON
kudos:2

1 edit
dupe......

UK_Dave

join:2011-01-27
Powassan, ON
kudos:2
reply to phear00
Sure thing.

I'm actually in Powassan, around 30k south of The Bay.

I've posted it in Direct, and I'll let you know if anything comes from it.

So far, it seems to be a wider picture, but who knows....


mlebel

@teksavvy.com
reply to UK_Dave
Same here, it's driving me nuts.. and makes me feel like i'm not getting my money's worth!

i'm with TekSavvy in Aylmer QC.

UK_Dave

join:2011-01-27
Powassan, ON
kudos:2
Reviews:
·TekSavvy DSL

1 edit
reply to phear00
Hi Man.

OK, it looks like I'm fixed - thanks to a midnight phone call to a young fellow in Support. It's so good being able to chat to "local" Canadian support.

We unplugged everything (router and modem) from the hydro for 15 minutes. Then, we powered on the ST516 modem and did a hard reset. i.e held the recessed button in for 10 seconds plus, until red lights flashed. I kept the wireless router out of the loop, by plugging directly into the modem via the ethernet port.

We did a series of tests (logging in to test@test via the modem), but everything came up super fast with great line stats. So, everything got plugged back together, and it's worked great (pings back down to 25ms, speed back to 6mb dl) night and day since then.

I don't think I can tell what actually fixed the issue - because with this problem, the very fact of troubleshooting the issue in this way doesnt really make clear whether simply disconnecting my session and reconnecting (i.e 2 clicks of the mouse) would have done the same, and maybe I just got lucky with where I landed.

The young tech suggested the 15min unplugging was relevant, as was the hard reset of the modem. I don't know enough to doubt him. All I know is since then, i'm good.

Anyhow, am sat back streaming the start of the Ryder Cup with a vat of coffee, a bottle of Bailey's, and my ankle strapped up from a rather harsh game of rugby the other night

Hope you can get the same result.... (DSL, not ankle!)

Cheers
Dave

p.s I forgot the young lads name... but given the amount of flak TS support is getting right now, can I just say he was informative, helpful, and was a pleasure to deal with.

I love it when support folks tell me what they expect to happen BEFORE I tell them what has happened. It instills great confidence.

phear00

join:2009-07-23
Cool thanks. Reading the forum, it seems like there's a lot of solutions involving disconnecting for a bit. Seems to be an overloaded Bell infrastructure.
Thanks again for updating me.

UK_Dave

join:2011-01-27
Powassan, ON
kudos:2
Forget everything I said.... :-(

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

Less than 2MB dload, 215ms ping

Right on schedule......


ChuckcZar

@teksavvy.com
reply to UK_Dave
That sounds like Steve's advice. He refers to them as power drains.

UK_Dave

join:2011-01-27
Powassan, ON
kudos:2
Reviews:
·TekSavvy DSL
I've no idea about it - am not a networks kind of IT guy.

I wondered if it was to do with a long disconnect giving me a fresh chance at being dropped onto a less busy hub or whatever....

Anyhow, same problem as before....

At least I got to see the end of Day 2 Ryder cup before it shagged out on me.....

UK_Dave

join:2011-01-27
Powassan, ON
kudos:2

1 edit
Trying to post a tracert here...

Note to self.... I bet it's the brackets that scuppered me.....

:-D

UK_Dave

join:2011-01-27
Powassan, ON
kudos:2
Reviews:
·TekSavvy DSL

1 edit
reply to UK_Dave
1 1 ms 1 ms 1 ms 192.168.1.1
2 1031 ms 1811 ms 1151 ms lo-100.lns02.tor.packetflow.ca [206.248.154.122]
3 1291 ms 1365 ms 1336 ms 2120.ae0.agg01.tor.packetflow.ca [69.196.136.77]
4 887 ms 679 ms 514 ms 206.248.154.117
5 795 ms 878 ms 941 ms SPIDERWEB [206.248.155.70]

Thats the tracert.

Haven't got a clue what it means though.....

Average ping over 100 pings to teksavvy.com is 750ms

LondonOntGuy

join:2004-05-12
London, ON
This slow down is making my internet essentially useless. Why am I paying for a connection that I can barely use? I'm getting better speed with the wifi I'm stealing from a neighbour.

UK_Dave

join:2011-01-27
Powassan, ON
kudos:2
Reviews:
·TekSavvy DSL
And absolutely perfect connection this morning.

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

I'm not in any way blaming TS for this. I'm just logging it to establish the pattern.

And here's the tracert

Tracing route to teksavvy.com [206.248.155.70]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.1.1
2 99 ms 17 ms 17 ms lo-100.lns02.tor.packetflow.ca [206.248.154.122]

3 17 ms 16 ms 16 ms 2120.ae0.agg01.tor.packetflow.ca [69.196.136.77]

4 22 ms 21 ms 21 ms 206.248.155.237
5 22 ms 22 ms 23 ms SPIDERWEB [206.248.155.70]

Trace complete.


TSI Martin
Premium
join:2006-02-23
Chatham, ON
kudos:33
reply to UK_Dave
If you would like to post in the »TekSavvy Direct forum, we can check & see what's going on.

Martin

UK_Dave

join:2011-01-27
Powassan, ON
kudos:2
Reviews:
·TekSavvy DSL

2 edits
Hi Martin,

Sorry, not worth it at the moment. I know i'm going to be asked to unplug the router, reset the modem, log in with test etc etc.

Can't do that at the moment - too hard to get to the router, ankles in a strap from rugby injury at the minute.

I thought I'd post here, because it's becoming such a pattern - but I dont have the knowledge to interpret it. Thought some folks here might be able to.

Both the slow, and the fast connection were obtained going through my wireless router and ST516. It's regular as clockwork, night and day. Although after calling last week, I got 3 days respite. (See above).

Also, when the router HAS been out of the loop (logged in via PPoE in Win7), I still experience the day/night speed issue. So I'm failry sure it's not the router, simply by a process of elimination - but I'm just as happy if I'm wrong.

So does the tracert and ping help at all?

Cheers,
Dave

EDIT : Extra Info.


TSI Martin
Premium
join:2006-02-23
Chatham, ON
kudos:33
If it's an evening thing only, then odds of being the router are a lot less. You can still do the test@test from the router.

If you need the info for the test@test test itself, let me know.

Martin
--
TSI Martin (Escalations / Social Media) - TekSavvy Solutions Inc.
Authorized TSI employee ( »»TekSavvy FAQ »Official support in the forum )
Follow me on Twitter : @TSIMartin

LondonOntGuy

join:2004-05-12
London, ON
reply to UK_Dave
A lot of sites aren't working for me right now as of Monday at 3:22PM. CTV, London Free Press, Tumblr, Youtube. Facebook is slow as mud and barely loads. As you can probably understand, this is very frustrating for me.

Edit: Even this site isn't working, I'm only able to get onto it because of my neighbour's open wifi.

UK_Dave

join:2011-01-27
Powassan, ON
kudos:2
Hi LOG.

You might want to start a new thread. I have no problems whatsoever resolving any sites.

Martin - I logged an email in Direct. Like I say though, can't get at router or modem physically though. We'll pick up there.


petah

join:2002-07-27
L9T
reply to UK_Dave
Bell's side. Congestion at the CO. It happened to me last year.

I've had 5 Bell techs come over to look at the issue as someone thought it was my line.

Good luck. They (Bell) will eventually upgrade. Don't count on TSI to be able to do anything, they couldn't help me.

Edit:
@TSI_Martin... You may want to look into the same thing as my old support ticket/topic I opened quite a while ago.

»[DSL] DSL Extremely slow, high ping

UK_Dave

join:2011-01-27
Powassan, ON
kudos:2
Grim news if true.

If this were the case though, can you account for why I'd suddenly get 3 day's respite right after the hard modem reset (see above)?

Thanks for the input.


petah

join:2002-07-27
L9T
You may get a day here and there were you will experience no or little congestion. Have you tried resetting the modem again and see if it'll last another 3 days without congestion?

Edit: By the way, this is what I said as well last year when I had congestion issue. I have a 6gb dataplan with my cell phone so I tethered if I need to use the internet.
said by LondonOntGuy:

This slow down is making my internet essentially useless. Why am I paying for a connection that I can barely use? I'm getting better speed with the wifi I'm stealing from a neighbour.


UK_Dave

join:2011-01-27
Powassan, ON
kudos:2
Nope. Can't get to it at the moment. I will be doing though.

UK_Dave

join:2011-01-27
Powassan, ON
kudos:2
Reviews:
·TekSavvy DSL
OK, here's the plan so far.

Courtesy of another member here, I'm running a script that runs a tracert to teksavvy.com. That script is located on a server which shares the first leg into teksavvy.... for us, that leg is:

lo-100.lns02.tor.packetflow.ca (206.248.154.122)

When I run my local tracert to teksavvy.com, I am also running that remote script.

The thinking is, that if they are getting good responses, and I am getting a poor one, then we can say the trouble is NOT with the TSI network.

I'll keep folks posted.

UK_Dave

join:2011-01-27
Powassan, ON
kudos:2
Reviews:
·TekSavvy DSL
and here is my ping to the gateway on 10.x.x.1 after logging in as test@test at the router.

C:\Users\david>ping 10.11.201.1 -n 100

Pinging 10.11.201.1 with 32 bytes of data:
Reply from 10.11.201.1: bytes=32 time=1147ms TTL=126
Reply from 10.11.201.1: bytes=32 time=1165ms TTL=126
Reply from 10.11.201.1: bytes=32 time=1117ms TTL=126
Reply from 10.11.201.1: bytes=32 time=1022ms TTL=126
Reply from 10.11.201.1: bytes=32 time=845ms TTL=126
Reply from 10.11.201.1: bytes=32 time=898ms TTL=126
Reply from 10.11.201.1: bytes=32 time=847ms TTL=126
Reply from 10.11.201.1: bytes=32 time=631ms TTL=126
Reply from 10.11.201.1: bytes=32 time=464ms TTL=126
Reply from 10.11.201.1: bytes=32 time=479ms TTL=126
Reply from 10.11.201.1: bytes=32 time=584ms TTL=126
Reply from 10.11.201.1: bytes=32 time=637ms TTL=126
Reply from 10.11.201.1: bytes=32 time=540ms TTL=126
Reply from 10.11.201.1: bytes=32 time=572ms TTL=126
Reply from 10.11.201.1: bytes=32 time=722ms TTL=126
Reply from 10.11.201.1: bytes=32 time=853ms TTL=126
Reply from 10.11.201.1: bytes=32 time=894ms TTL=126
Reply from 10.11.201.1: bytes=32 time=911ms TTL=126
Reply from 10.11.201.1: bytes=32 time=727ms TTL=126
Reply from 10.11.201.1: bytes=32 time=826ms TTL=126
Reply from 10.11.201.1: bytes=32 time=832ms TTL=126
Reply from 10.11.201.1: bytes=32 time=921ms TTL=126
Reply from 10.11.201.1: bytes=32 time=726ms TTL=126
Reply from 10.11.201.1: bytes=32 time=719ms TTL=126
Reply from 10.11.201.1: bytes=32 time=842ms TTL=126
Reply from 10.11.201.1: bytes=32 time=843ms TTL=126
Reply from 10.11.201.1: bytes=32 time=762ms TTL=126
Reply from 10.11.201.1: bytes=32 time=800ms TTL=126
Reply from 10.11.201.1: bytes=32 time=903ms TTL=126
Reply from 10.11.201.1: bytes=32 time=917ms TTL=126
Reply from 10.11.201.1: bytes=32 time=825ms TTL=126
Reply from 10.11.201.1: bytes=32 time=658ms TTL=126
Reply from 10.11.201.1: bytes=32 time=621ms TTL=126
Reply from 10.11.201.1: bytes=32 time=576ms TTL=126
Reply from 10.11.201.1: bytes=32 time=690ms TTL=126
Reply from 10.11.201.1: bytes=32 time=726ms TTL=126
Reply from 10.11.201.1: bytes=32 time=650ms TTL=126
Reply from 10.11.201.1: bytes=32 time=523ms TTL=126
Reply from 10.11.201.1: bytes=32 time=629ms TTL=126
Reply from 10.11.201.1: bytes=32 time=710ms TTL=126
Reply from 10.11.201.1: bytes=32 time=756ms TTL=126
Reply from 10.11.201.1: bytes=32 time=817ms TTL=126
Reply from 10.11.201.1: bytes=32 time=584ms TTL=126
Reply from 10.11.201.1: bytes=32 time=635ms TTL=126
Reply from 10.11.201.1: bytes=32 time=586ms TTL=126
Reply from 10.11.201.1: bytes=32 time=817ms TTL=126
Reply from 10.11.201.1: bytes=32 time=774ms TTL=126
Reply from 10.11.201.1: bytes=32 time=683ms TTL=126
Reply from 10.11.201.1: bytes=32 time=650ms TTL=126
Reply from 10.11.201.1: bytes=32 time=1971ms TTL=126
Reply from 10.11.201.1: bytes=32 time=748ms TTL=126
Reply from 10.11.201.1: bytes=32 time=770ms TTL=126
Reply from 10.11.201.1: bytes=32 time=823ms TTL=126
Reply from 10.11.201.1: bytes=32 time=1006ms TTL=126
Reply from 10.11.201.1: bytes=32 time=934ms TTL=126
Reply from 10.11.201.1: bytes=32 time=957ms TTL=126
Reply from 10.11.201.1: bytes=32 time=729ms TTL=126
Reply from 10.11.201.1: bytes=32 time=641ms TTL=126
Reply from 10.11.201.1: bytes=32 time=768ms TTL=126
Reply from 10.11.201.1: bytes=32 time=863ms TTL=126
Reply from 10.11.201.1: bytes=32 time=944ms TTL=126
Reply from 10.11.201.1: bytes=32 time=779ms TTL=126
Reply from 10.11.201.1: bytes=32 time=715ms TTL=126
Reply from 10.11.201.1: bytes=32 time=933ms TTL=126
Reply from 10.11.201.1: bytes=32 time=837ms TTL=126
Reply from 10.11.201.1: bytes=32 time=676ms TTL=126
Reply from 10.11.201.1: bytes=32 time=752ms TTL=126
Reply from 10.11.201.1: bytes=32 time=865ms TTL=126
Reply from 10.11.201.1: bytes=32 time=885ms TTL=126
Reply from 10.11.201.1: bytes=32 time=786ms TTL=126
Reply from 10.11.201.1: bytes=32 time=713ms TTL=126
Reply from 10.11.201.1: bytes=32 time=882ms TTL=126
Reply from 10.11.201.1: bytes=32 time=902ms TTL=126
Reply from 10.11.201.1: bytes=32 time=889ms TTL=126
Reply from 10.11.201.1: bytes=32 time=945ms TTL=126
Reply from 10.11.201.1: bytes=32 time=1064ms TTL=126
Reply from 10.11.201.1: bytes=32 time=976ms TTL=126
Reply from 10.11.201.1: bytes=32 time=1206ms TTL=126
Reply from 10.11.201.1: bytes=32 time=1285ms TTL=126
Reply from 10.11.201.1: bytes=32 time=1130ms TTL=126
Reply from 10.11.201.1: bytes=32 time=1110ms TTL=126
Reply from 10.11.201.1: bytes=32 time=1145ms TTL=126
Reply from 10.11.201.1: bytes=32 time=1091ms TTL=126
Reply from 10.11.201.1: bytes=32 time=1189ms TTL=126
Reply from 10.11.201.1: bytes=32 time=1130ms TTL=126
Reply from 10.11.201.1: bytes=32 time=1114ms TTL=126
Reply from 10.11.201.1: bytes=32 time=1050ms TTL=126
Reply from 10.11.201.1: bytes=32 time=910ms TTL=126
Reply from 10.11.201.1: bytes=32 time=1016ms TTL=126
Reply from 10.11.201.1: bytes=32 time=1010ms TTL=126
Reply from 10.11.201.1: bytes=32 time=1067ms TTL=126
Reply from 10.11.201.1: bytes=32 time=993ms TTL=126
Reply from 10.11.201.1: bytes=32 time=999ms TTL=126
Reply from 10.11.201.1: bytes=32 time=1192ms TTL=126
Reply from 10.11.201.1: bytes=32 time=1271ms TTL=126
Reply from 10.11.201.1: bytes=32 time=1243ms TTL=126
Reply from 10.11.201.1: bytes=32 time=1187ms TTL=126
Reply from 10.11.201.1: bytes=32 time=1299ms TTL=126
Reply from 10.11.201.1: bytes=32 time=1337ms TTL=126
Reply from 10.11.201.1: bytes=32 time=1268ms TTL=126

Ping statistics for 10.11.201.1:
Packets: Sent = 100, Received = 100, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 464ms, Maximum = 1971ms, Average = 880ms

Thats usual for me after around 7pm..... :-(


petah

join:2002-07-27
L9T
hate to tell you.. it is congestion at the CO. Unless you have 4 others on the same CO as you that have opened a ticket with Teksavvy you'll have to wait it out or switch over to cable internet.

Funny how Bell used to have commercials saying that cable internet is "shared" and DSL is dedicated.... EH.

Do a ping test between 5pm & 8pm and you'll notice the ping time will increase when congestion starts to where it is unusable.

OneWorld9

join:2010-12-09
East York, ON
reply to UK_Dave
Very likely as petah See Profile suggested. Good luck!

It's somewhat tricky to set up properly, but you might want to also do this:

Line Monitoring

Very helpful for monitoring your line, and you don't have to run manual tests all the time. TekSavvy really does need better / automated ways of doing this.

UK_Dave

join:2011-01-27
Powassan, ON
kudos:2
Reviews:
·TekSavvy DSL

4 edits
reply to petah
You see what I mean by unuseable.... those speeds make almost anything other than mail impossible.

When you say CO, what is that? Is there a reason why it would suddenly get like this?

Would / Can / Does Bell deliberately affect me out of spite for moving to TS?

I say this not to be inflammatory, but this was not the case when I was with (spit!) Bell.

I moved away from them for reasons of conscience, not poor connections.

I'm damn well not going back to the feckers though.

Cheers,
Dave


xsbell

join:2008-12-22
Canada
kudos:8
Reviews:
·Primus Telecommu..
said by UK_Dave:

You see what I mean by unuseable.... those speeds make almost anything other than mail impossible.

When you say CO, what is that? Is there a reason why it would suddenly get like this?

Would / Can / Does Bell deliberately affect me out of spite for moving to TS?

I say this not to be inflammatory, but this was not the case when I was with (spit!) Bell.

I moved away from them for reasons of conscience, not poor connections.

I'm damn well not going back to the feckers though.

Cheers,
Dave

By CO, he means the Central Office. More than likely the uplink to the DSLAM is congested, or the BAS itself.

No, every customer (Bell/TSI/etc) on that DSLAM will have the same issues.