dslreports logo
site
 
    All Forums Hot Topics Gallery
spc

spacer




how-to block ads


Search Topic:
uniqs
8542
share rss forum feed

InvalidError

join:2008-02-03
kudos:5
reply to Phibian

Re: [DSL] Network congestion tonight?

said by Phibian:

One question: Where is the test@test gateway? The remote, the CO or somewhere else?

test@test is the BRAS (the equipment that handles PPPoE termination for Bell's internet subscribers, forwards PPPoE session authentications to 3rd-party ISPs and routes PPPoE session to them over L2TP afterward) or somewhere nearby.

The BRAS would be located in a CO but not necessarily yours since a single BRAS can handle more traffic than what most COs generate.

InvalidError

join:2008-02-03
kudos:5
reply to TSI Marc
said by TSI Marc:

Hey guys, I had a look on our end... there isn't a single link that has any congestion... whatever is going on is something other than on our end.

That's weird.

I reset my PPPoE session last night after posting those results and my speedtest went from 1.5Mbps to 3.8Mbps and pingtest jitter dropped from 41ms to 26ms which seems to indicate there still was some congestion-like 'something' happening, just not as bad.

Like others who are seeing this nightly DSL slowdown, everything looks perfectly fine during the day...




(Same PPPoE session that was giving me 3.8Mbps and 26ms jitter last night.)


TSI Marc
Premium,VIP
join:2006-06-23
Chatham, ON
kudos:28
yeah.. I just dont see it on my end.

we need to figure out what it is though. not cool that you guys are seeing that.

I'll get the gang to follow up with you and see what we can do.
--
Marc - CEO/TekSavvy


squircle

join:2009-06-23
Oakville, ON
said by TSI Marc:

I'll get the gang to follow up with you and see what we can do.

I hope this can all get worked out; 200ms first-hop latency makes VoIP nearly impossible. I have a thread in the direct forum that's been peered at by 9 of your staff with plenty of traceroutes and stuff if that helps.

As if you didn't have enough stuff to keep you guys busy already!


Phibian

join:2009-06-01
Ottawa, ON
Reviews:
·TekSavvy DSL
reply to TSI Marc
Definitely something going on but I appreciate that you need to be able to see it to fix it.

If it is
-not the local lines (doesn't appear to be as stats are good and RCO is 35%)
-not the link from remote to CO (doesn't appear to be if test@test is working)
-not the AGAS
what is left?

-ERX?
-Core switches?
-Peering setup?

I'm game to test whatever I can (I've got two lines so I'm happy to take one down and run tests on it with a spare login) just let me know what is useful.

I've also got smokeping graphs that I'm happy to share if anyone wants.

InvalidError

join:2008-02-03
kudos:5
The night I was getting some 200+ms results on pingtest/speedtest I was seeing the same ~200ms first-hop on traceroute. Pinging the test@test gateway (x.x.x.1) was fine (16ms, no packet loss) so the problem must be somewhere between Bell's BRAS and TSI's ERX.

Speedtest is currently normal but pingtest is a little wobbly tonight...

chex383

join:2003-03-13
Montreal, QC
reply to squircle
Hi:

I am in Montreal on VDSL, and I am having the same issues. I am posting in the Direct forum with support, but they are looking at my upstream high line-noise as being the issue, it so is not. I get 25MB in the mornings, then at nite, I see speeds like this:




I am going to do another test with a bell login in the evenings and check speed there to see if I see the same slow-down. 99% hunch I will not.

My internet is redicously slow at these hours, and I cannot even make a phone call, as VOIP is my only voice system that works well at home. (PublicMobile barely gets into my apartment) .

Frustrated, Stefan
--
Sung to the old New England Telephone Ad Jingle: " We're the only one New Eng-Lund, Hell-Ri-zon Tele-phonnnnne! "


RobinK

join:2004-04-16
Canada
reply to torobull123
I am on 25mbps and can barely pull 1mpbs download right now. I switch to my b1 login and everything is perfect.

This is pathetic. I cannot even watch a 240p stream on twitchtv using my teksavvy login.
--
Argue opinions using facts. Not facts using opinions.

stevey_frac

join:2009-12-09
Cambridge, ON
reply to torobull123


This seems... Less than ideal.

How do we move forward to get this fixed?

chex383

join:2003-03-13
Montreal, QC

1 recommendation

reply to chex383
HI there, so tonight I played with different logins, and I figured out the issue.

I use the IPv6 TSI login '@hsiservice.net' to get connected via PPPOE. When I switched to using the standard V4-only login ' @teksavvy.com ', and did a speed test, my speeds were MUCH better, and my pings almost normal. So the issue for me was that V6 login is overloaded, and TSI needs to figure out the bandwidth on that login. for now I will use the standard login until they get that fixed.

Regards, Stefan
--
Sung to the old New England Telephone Ad Jingle: " We're the only one New Eng-Lund, Hell-Ri-zon Tele-phonnnnne! "

InvalidError

join:2008-02-03
kudos:5

1 recommendation

Humm, I'm using the v6 login too.

Speedtest was fine when I tried around 22h tonight while pingtest was reporting 60ms with 10ms jitter. (vs 23-26ms ping and 0-2ms jitter off-peak.)


Phibian

join:2009-06-01
Ottawa, ON
Reviews:
·TekSavvy DSL
reply to torobull123
I'm using an IPv4 login and it happens to me too. Disconnecting and reconnecting appears to sometimes fix it so the fact that you did so may have been what fixed it rather than the actual switch of logins.

I've seen the issue with both a normal @teksavvy login and an MLPPP @wiredhighspeed login.


Phibian

join:2009-06-01
Ottawa, ON
Reviews:
·TekSavvy DSL
reply to torobull123
Ok so last night I caught it doing it.

Pinging 206.248.154.122 with 1000 bytes of data:
Reply from 206.248.154.122: bytes=1000 time=17ms TTL=127
Reply from 206.248.154.122: bytes=1000 time=77ms TTL=127
Reply from 206.248.154.122: bytes=1000 time=15ms TTL=127
Reply from 206.248.154.122: bytes=1000 time=15ms TTL=127
Reply from 206.248.154.122: bytes=1000 time=15ms TTL=127
Reply from 206.248.154.122: bytes=1000 time=187ms TTL=127
Reply from 206.248.154.122: bytes=1000 time=15ms TTL=127
Reply from 206.248.154.122: bytes=1000 time=15ms TTL=127
Reply from 206.248.154.122: bytes=1000 time=15ms TTL=127
Reply from 206.248.154.122: bytes=1000 time=140ms TTL=127
Reply from 206.248.154.122: bytes=1000 time=140ms TTL=127
Reply from 206.248.154.122: bytes=1000 time=15ms TTL=127
Reply from 206.248.154.122: bytes=1000 time=15ms TTL=127
Reply from 206.248.154.122: bytes=1000 time=31ms TTL=127
Reply from 206.248.154.122: bytes=1000 time=15ms TTL=127
Reply from 206.248.154.122: bytes=1000 time=15ms TTL=127
Reply from 206.248.154.122: bytes=1000 time=31ms TTL=127
Reply from 206.248.154.122: bytes=1000 time=15ms TTL=127
Reply from 206.248.154.122: bytes=1000 time=15ms TTL=127
Reply from 206.248.154.122: bytes=1000 time=62ms TTL=127
Reply from 206.248.154.122: bytes=1000 time=31ms TTL=127
Reply from 206.248.154.122: bytes=1000 time=15ms TTL=127
Reply from 206.248.154.122: bytes=1000 time=15ms TTL=127
Reply from 206.248.154.122: bytes=1000 time=15ms TTL=127
Reply from 206.248.154.122: bytes=1000 time=15ms TTL=127
Reply from 206.248.154.122: bytes=1000 time=15ms TTL=127
Reply from 206.248.154.122: bytes=1000 time=15ms TTL=127
Reply from 206.248.154.122: bytes=1000 time=140ms TTL=127
Reply from 206.248.154.122: bytes=1000 time=31ms TTL=127
Reply from 206.248.154.122: bytes=1000 time=15ms TTL=127
Request timed out.
Reply from 206.248.154.122: bytes=1000 time=15ms TTL=127
Reply from 206.248.154.122: bytes=1000 time=31ms TTL=127
Reply from 206.248.154.122: bytes=1000 time=15ms TTL=127
Reply from 206.248.154.122: bytes=1000 time=30ms TTL=127
Reply from 206.248.154.122: bytes=1000 time=15ms TTL=127
Reply from 206.248.154.122: bytes=1000 time=109ms TTL=127
Reply from 206.248.154.122: bytes=1000 time=15ms TTL=127
Reply from 206.248.154.122: bytes=1000 time=15ms TTL=127
Reply from 206.248.154.122: bytes=1000 time=15ms TTL=127
Reply from 206.248.154.122: bytes=1000 time=133ms TTL=127
Reply from 206.248.154.122: bytes=1000 time=24ms TTL=127
Reply from 206.248.154.122: bytes=1000 time=23ms TTL=127
Reply from 206.248.154.122: bytes=1000 time=24ms TTL=127
Reply from 206.248.154.122: bytes=1000 time=24ms TTL=127
Reply from 206.248.154.122: bytes=1000 time=24ms TTL=127
Reply from 206.248.154.122: bytes=1000 time=24ms TTL=127
Reply from 206.248.154.122: bytes=1000 time=24ms TTL=127
Reply from 206.248.154.122: bytes=1000 time=24ms TTL=127
Reply from 206.248.154.122: bytes=1000 time=24ms TTL=127
Reply from 206.248.154.122: bytes=1000 time=24ms TTL=127
Reply from 206.248.154.122: bytes=1000 time=24ms TTL=127
Reply from 206.248.154.122: bytes=1000 time=55ms TTL=127
Reply from 206.248.154.122: bytes=1000 time=289ms TTL=127
Reply from 206.248.154.122: bytes=1000 time=24ms TTL=127
Reply from 206.248.154.122: bytes=1000 time=24ms TTL=127
Reply from 206.248.154.122: bytes=1000 time=24ms TTL=127
Reply from 206.248.154.122: bytes=1000 time=149ms TTL=127
Reply from 206.248.154.122: bytes=1000 time=39ms TTL=127
Reply from 206.248.154.122: bytes=1000 time=24ms TTL=127
Reply from 206.248.154.122: bytes=1000 time=24ms TTL=127
Reply from 206.248.154.122: bytes=1000 time=24ms TTL=127
Reply from 206.248.154.122: bytes=1000 time=109ms TTL=127
Reply from 206.248.154.122: bytes=1000 time=15ms TTL=127
Reply from 206.248.154.122: bytes=1000 time=15ms TTL=127
Reply from 206.248.154.122: bytes=1000 time=31ms TTL=127
Reply from 206.248.154.122: bytes=1000 time=23ms TTL=127
Reply from 206.248.154.122: bytes=1000 time=24ms TTL=127
Reply from 206.248.154.122: bytes=1000 time=24ms TTL=127
Reply from 206.248.154.122: bytes=1000 time=24ms TTL=127
Reply from 206.248.154.122: bytes=1000 time=133ms TTL=127
Reply from 206.248.154.122: bytes=1000 time=24ms TTL=127
Reply from 206.248.154.122: bytes=1000 time=24ms TTL=127
Reply from 206.248.154.122: bytes=1000 time=24ms TTL=127
Reply from 206.248.154.122: bytes=1000 time=149ms TTL=127
Reply from 206.248.154.122: bytes=1000 time=24ms TTL=127
Reply from 206.248.154.122: bytes=1000 time=24ms TTL=127
Reply from 206.248.154.122: bytes=1000 time=24ms TTL=127
Reply from 206.248.154.122: bytes=1000 time=24ms TTL=127
Reply from 206.248.154.122: bytes=1000 time=24ms TTL=127
Reply from 206.248.154.122: bytes=1000 time=24ms TTL=127
Reply from 206.248.154.122: bytes=1000 time=24ms TTL=127
Reply from 206.248.154.122: bytes=1000 time=24ms TTL=127
Reply from 206.248.154.122: bytes=1000 time=86ms TTL=127
Reply from 206.248.154.122: bytes=1000 time=24ms TTL=127
Reply from 206.248.154.122: bytes=1000 time=39ms TTL=127
Reply from 206.248.154.122: bytes=1000 time=24ms TTL=127
Reply from 206.248.154.122: bytes=1000 time=24ms TTL=127
Reply from 206.248.154.122: bytes=1000 time=180ms TTL=127
Reply from 206.248.154.122: bytes=1000 time=24ms TTL=127
Reply from 206.248.154.122: bytes=1000 time=24ms TTL=127
Reply from 206.248.154.122: bytes=1000 time=24ms TTL=127
Reply from 206.248.154.122: bytes=1000 time=118ms TTL=127
Reply from 206.248.154.122: bytes=1000 time=24ms TTL=127
Reply from 206.248.154.122: bytes=1000 time=24ms TTL=127
Reply from 206.248.154.122: bytes=1000 time=24ms TTL=127
Reply from 206.248.154.122: bytes=1000 time=24ms TTL=127
Reply from 206.248.154.122: bytes=1000 time=24ms TTL=127
Reply from 206.248.154.122: bytes=1000 time=24ms TTL=127
Reply from 206.248.154.122: bytes=1000 time=24ms TTL=127

Ping statistics for 206.248.154.122:
Packets: Sent = 100, Received = 99, Lost = 1 (1% loss),
Approximate round trip times in milli-seconds:
Minimum = 15ms, Maximum = 289ms, Average = 40ms


Pinging 10.7.216.1 with 1000 bytes of data:

Reply from 10.7.216.1: bytes=1000 time=14ms TTL=127
Reply from 10.7.216.1: bytes=1000 time=15ms TTL=127
Reply from 10.7.216.1: bytes=1000 time=15ms TTL=127
Reply from 10.7.216.1: bytes=1000 time=15ms TTL=127
Reply from 10.7.216.1: bytes=1000 time=15ms TTL=127
Reply from 10.7.216.1: bytes=1000 time=13ms TTL=127
Reply from 10.7.216.1: bytes=1000 time=15ms TTL=127
Reply from 10.7.216.1: bytes=1000 time=15ms TTL=127
Reply from 10.7.216.1: bytes=1000 time=15ms TTL=127
Reply from 10.7.216.1: bytes=1000 time=15ms TTL=127
Reply from 10.7.216.1: bytes=1000 time=15ms TTL=127
Reply from 10.7.216.1: bytes=1000 time=15ms TTL=127
Reply from 10.7.216.1: bytes=1000 time=15ms TTL=127
Reply from 10.7.216.1: bytes=1000 time=15ms TTL=127
Reply from 10.7.216.1: bytes=1000 time=15ms TTL=127
Reply from 10.7.216.1: bytes=1000 time=15ms TTL=127
Reply from 10.7.216.1: bytes=1000 time=15ms TTL=127
Reply from 10.7.216.1: bytes=1000 time=15ms TTL=127
Reply from 10.7.216.1: bytes=1000 time=15ms TTL=127
Reply from 10.7.216.1: bytes=1000 time=15ms TTL=127
Reply from 10.7.216.1: bytes=1000 time=77ms TTL=127
Reply from 10.7.216.1: bytes=1000 time=15ms TTL=127
Reply from 10.7.216.1: bytes=1000 time=15ms TTL=127
Reply from 10.7.216.1: bytes=1000 time=15ms TTL=127
Reply from 10.7.216.1: bytes=1000 time=15ms TTL=127
Reply from 10.7.216.1: bytes=1000 time=15ms TTL=127
Reply from 10.7.216.1: bytes=1000 time=15ms TTL=127
Reply from 10.7.216.1: bytes=1000 time=15ms TTL=127
Reply from 10.7.216.1: bytes=1000 time=15ms TTL=127
Reply from 10.7.216.1: bytes=1000 time=31ms TTL=127
Reply from 10.7.216.1: bytes=1000 time=15ms TTL=127
Reply from 10.7.216.1: bytes=1000 time=15ms TTL=127
Reply from 10.7.216.1: bytes=1000 time=15ms TTL=127
Reply from 10.7.216.1: bytes=1000 time=15ms TTL=127
Reply from 10.7.216.1: bytes=1000 time=23ms TTL=127
Reply from 10.7.216.1: bytes=1000 time=24ms TTL=127
Reply from 10.7.216.1: bytes=1000 time=24ms TTL=127
Reply from 10.7.216.1: bytes=1000 time=24ms TTL=127
Reply from 10.7.216.1: bytes=1000 time=24ms TTL=127
Reply from 10.7.216.1: bytes=1000 time=39ms TTL=127
Reply from 10.7.216.1: bytes=1000 time=24ms TTL=127
Reply from 10.7.216.1: bytes=1000 time=15ms TTL=127
Reply from 10.7.216.1: bytes=1000 time=15ms TTL=127
Reply from 10.7.216.1: bytes=1000 time=15ms TTL=127
Reply from 10.7.216.1: bytes=1000 time=15ms TTL=127
Reply from 10.7.216.1: bytes=1000 time=15ms TTL=127
Reply from 10.7.216.1: bytes=1000 time=15ms TTL=127
Reply from 10.7.216.1: bytes=1000 time=15ms TTL=127
Reply from 10.7.216.1: bytes=1000 time=15ms TTL=127
Reply from 10.7.216.1: bytes=1000 time=15ms TTL=127
Reply from 10.7.216.1: bytes=1000 time=15ms TTL=127
Reply from 10.7.216.1: bytes=1000 time=15ms TTL=127
Reply from 10.7.216.1: bytes=1000 time=15ms TTL=127
Reply from 10.7.216.1: bytes=1000 time=15ms TTL=127
Reply from 10.7.216.1: bytes=1000 time=15ms TTL=127
Reply from 10.7.216.1: bytes=1000 time=15ms TTL=127
Reply from 10.7.216.1: bytes=1000 time=15ms TTL=127
Reply from 10.7.216.1: bytes=1000 time=15ms TTL=127
Reply from 10.7.216.1: bytes=1000 time=12ms TTL=127
Reply from 10.7.216.1: bytes=1000 time=15ms TTL=127
Reply from 10.7.216.1: bytes=1000 time=15ms TTL=127
Reply from 10.7.216.1: bytes=1000 time=15ms TTL=127
Reply from 10.7.216.1: bytes=1000 time=15ms TTL=127
Reply from 10.7.216.1: bytes=1000 time=15ms TTL=127
Reply from 10.7.216.1: bytes=1000 time=15ms TTL=127
Reply from 10.7.216.1: bytes=1000 time=15ms TTL=127
Reply from 10.7.216.1: bytes=1000 time=15ms TTL=127
Reply from 10.7.216.1: bytes=1000 time=14ms TTL=127
Reply from 10.7.216.1: bytes=1000 time=15ms TTL=127
Reply from 10.7.216.1: bytes=1000 time=19ms TTL=127
Reply from 10.7.216.1: bytes=1000 time=24ms TTL=127
Reply from 10.7.216.1: bytes=1000 time=24ms TTL=127
Reply from 10.7.216.1: bytes=1000 time=24ms TTL=127
Reply from 10.7.216.1: bytes=1000 time=24ms TTL=127
Reply from 10.7.216.1: bytes=1000 time=24ms TTL=127
Reply from 10.7.216.1: bytes=1000 time=23ms TTL=127
Reply from 10.7.216.1: bytes=1000 time=24ms TTL=127
Reply from 10.7.216.1: bytes=1000 time=24ms TTL=127
Reply from 10.7.216.1: bytes=1000 time=24ms TTL=127
Reply from 10.7.216.1: bytes=1000 time=24ms TTL=127
Reply from 10.7.216.1: bytes=1000 time=24ms TTL=127
Reply from 10.7.216.1: bytes=1000 time=24ms TTL=127
Reply from 10.7.216.1: bytes=1000 time=24ms TTL=127
Reply from 10.7.216.1: bytes=1000 time=24ms TTL=127
Reply from 10.7.216.1: bytes=1000 time=24ms TTL=127
Reply from 10.7.216.1: bytes=1000 time=24ms TTL=127
Reply from 10.7.216.1: bytes=1000 time=24ms TTL=127
Reply from 10.7.216.1: bytes=1000 time=24ms TTL=127
Reply from 10.7.216.1: bytes=1000 time=24ms TTL=127
Reply from 10.7.216.1: bytes=1000 time=24ms TTL=127
Reply from 10.7.216.1: bytes=1000 time=180ms TTL=127
Reply from 10.7.216.1: bytes=1000 time=24ms TTL=127
Reply from 10.7.216.1: bytes=1000 time=24ms TTL=127
Reply from 10.7.216.1: bytes=1000 time=24ms TTL=127
Reply from 10.7.216.1: bytes=1000 time=24ms TTL=127
Reply from 10.7.216.1: bytes=1000 time=24ms TTL=127
Reply from 10.7.216.1: bytes=1000 time=24ms TTL=127
Reply from 10.7.216.1: bytes=1000 time=24ms TTL=127
Reply from 10.7.216.1: bytes=1000 time=24ms TTL=127
Reply from 10.7.216.1: bytes=1000 time=102ms TTL=127

Ping statistics for 10.7.216.1:
Packets: Sent = 100, Received = 100, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 12ms, Maximum = 180ms, Average = 21ms


I also ran a speedtest and what I saw on it was that the speed drops abruptly when it drops a packet and then picks back up. You can see this on the little graph that shows in the speedtest. This was only 1/100 dropped but it is often much worse. I ran it a few times and managed to catch it doing this more than once. I'd love to catch it when it is dropping 10-15/100 but I can't sit infront of it all day every day.

All of this was done from a laptop directly connected to the modem (ethernet not wifi). No applications running. Nothing using the connection otherwise. Speedtest was not run while doing the ping test.

Line is clean. RCO is 35%. Issue is normally worse at peak hours but is not exclusive to peak hours.

Given that there are a number of us reporting very similar sounding issues (and this may be the same issue that people are seeing with youtube, in which case it is not even exclusive to DSL) I think it is pretty clear that this is not an isolated issue.

Thoughts TSI?

InvalidError

join:2008-02-03
kudos:5
reply to torobull123
Here it comes again...



Guess I'll go try the regular IPv4 login and see if that helps.

InvalidError

join:2008-02-03
kudos:5

1 edit
reply to Phibian
Looks like you may be right.

I tried resetting my @hsiservice.net IPv6 PPPoE session a few times, 100+ms pingtest with 10+ms jitter and 1-2Mbps speedtest.

Switched to regular IPv4-only @teksavvy.com login...



It really does look like TSI might be having problems with the equipment handling at least some @hsiservice.net sessions.

Edit: Confirmed problematic @hsiservice.net performance using Windows dialer - previously only used it through WRT54GS/Toastman-IPv6.


Phibian

join:2009-06-01
Ottawa, ON
reply to TSI Marc
Marc any idea when we can expect said follow up?

This is still happening. I've posted and IMed (to Martin) logs of loss as requested.

keltron

join:2012-12-26
North York, ON


25/7 looking ok at 6:10pm around Yonge/Finch

amadues

join:2008-07-01
Toronto, ON
Confirmed that the peak hour latency (200+ ms through erx04) that I have been seeing every evening for the past two weeks was resolved by switching PPPoE login from @hsiservice.net (IPv6) to @dslinternet.ca.


TSI Marc
Premium,VIP
join:2006-06-23
Chatham, ON
kudos:28
reply to Phibian
»[OUTAGE REPORT] March 1st/13

We did some maintenance last night, I'm sure that's not helping anything.
--
Marc - CEO/TekSavvy


HiVolt
Premium
join:2000-12-28
Toronto, ON
kudos:21
I'm not seeing any issues here on VDSL... maxing out on single threaded tests no problem at 8pm.
--
F**K THE NHL. Go Blue Jays 2013!!!

notfred

join:2012-09-15
Reviews:
·TekSavvy DSL
My connection is terrible right now. This is Ottawa on a 25/10 DSL with perfect line stats and:


notfred

join:2012-09-15
Forgot to mention that this is with an hsiservice.net login as per the others above who are seeing poor throughput. It's too late for me to try switching to a plain teksavvy login, but I'll try the speedtest again tomorrow morning.

s0dhi

join:2011-08-02
Brampton, ON
reply to TSI Marc

I've been having intermittent issues for the last couple of days and just recycled the modem per Marc's post. Things are a little better now, but the overall speed is still down slightly and not as consistent as usual.


Phibian

join:2009-06-01
Ottawa, ON
Reviews:
·TekSavvy DSL
reply to TSI Marc
Ok, I tried disconnecting and reconnecting and yes I can see that making a difference (First speedtest was 6/10. After reconnect I get 25/10).

But independent of that I'm still seeing crazy packet loss. 4% right now to 206.248.154.106. Most of the time this is not terribly obvious in web surfing but it certainly starts to impact VoIP. If I was bonding my two lines right now I'd be seeing 8% which is way high!

Anyway I guess that means the two issues (speed & packet loss) don't seem to be completely related (although if packet loss does hit during a speedtest it does have a negative impact).

I see the packet loss both through my @wiredhighspeed and a normal @teksavvy account but never using @test. I also see it both when using windows dialer on a dedicated system directly connected to modem or on my standard setup using a linux box as a firewall/gateway.

Any idea on the packet loss?

notfred

join:2012-09-15
Reviews:
·TekSavvy DSL
reply to notfred
And here's the result in the morning:


Definitely looks like nightly congestion.


Phibian

join:2009-06-01
Ottawa, ON
Reviews:
·TekSavvy DSL
reply to s0dhi
s0dhi can you try a ping -n 100 -l 1000 yourgatewayip? I don't really care about anything other than the summary at the end of it. Perhaps even try a few of them (especially when speed seems to be slow).

I'd like to find someone else who can reproduce the packet loss issue as it really shouldn't be happening and if we can get to the bottom of that it should at least help with the speed issue even if it doesn't fix it outright. Basically if you're surfing the web and you find you have to hit refresh occasionally because something just didn't load you may be seeing packet loss. Otherwise at such low levels it isn't very obvious but it is still a problem and not something that should be happening.


dalkeith74

@teksavvy.com
reply to torobull123
I can't play NHL13 online anymore during the evenings connected through HSI. Lags and choppy. Reconnecting sometimes helps temporarily for a short while.


Phibian

join:2009-06-01
Ottawa, ON
Reviews:
·TekSavvy DSL
reply to torobull123
Ping statistics for 206.248.154.106:
Packets: Sent = 100, Received = 90, Lost = 10 (10% loss),
Approximate round trip times in milli-seconds:
Minimum = 14ms, Maximum = 85ms, Average = 21ms

Today has been terrible. Ranging from 4 to 10% all day.

test@test is always clean.

This is not acceptable. Can someone please tell me what is going on here? I don't know if this is related to logins or what but I'd like it fixed please!


TSI Marc
Premium,VIP
join:2006-06-23
Chatham, ON
kudos:28
hum. I just checked all 30 links manually... none are saturated.

you should try pinging something else though.. pinging a router like that doesn't always produce the best results since it puts a low priority on responding to pings.

maybe try speedtest.teksavvy.com ..ping that and also do a traceroute to it.. see what that shows.
--
Marc - CEO/TekSavvy


Phibian

join:2009-06-01
Ottawa, ON
Reviews:
·TekSavvy DSL
The gateway is what Martin asked me to use which is why I did so.

Using speedtest.teksavvy.com right now I get:

Ping statistics for 206.248.140.50:
Packets: Sent = 100, Received = 96, Lost = 4 (4% loss),
Approximate round trip times in milli-seconds:
Minimum = 14ms, Maximum = 20ms, Average = 17ms

Tracert:

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

1 1 ms 1 ms 1 ms INTERNALSYSTEM [10.1.4.1]
2 17 ms 15 ms 15 ms lo-100.erx06.tor.packetflow.ca [206.248.154.106]
3 17 ms 15 ms 15 ms 2110.ae0.agg01.tor.packetflow.ca [69.196.136.44]
4 17 ms 15 ms 16 ms speedtest.teksavvy.com [206.248.140.50]

Trace complete.

Aside from the dropped packets it all looks quite good.