dslreports logo
site
 
    All Forums Hot Topics Gallery
spc

spacer




how-to block ads


Search Topic:
uniqs
8545
share rss forum feed

notfred

join:2012-09-15
reply to HiVolt

Re: [DSL] Network congestion tonight?

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
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.


Phibian

join:2009-06-01
Ottawa, ON
Reviews:
·TekSavvy DSL
reply to TSI Marc
Further logs from the gateway.

Looking at the external interface I see the packets are clearly leaving my end and are not being replied to (not just a really large delay).

listening on ppp0, link-type LINUX_SLL (Linux cooked), capture size 65535 bytes
20:11:44.189584 IP gw1 > speedtest.teksavvy.com: ICMP echo request, id 1, seq 1031, length 1008
20:11:49.188802 IP gw1 > speedtest.teksavvy.com: ICMP echo request, id 1, seq 1032, length 1008
20:11:49.206394 IP speedtest.teksavvy.com > gw1: ICMP echo reply, id 1, seq 1032, length 1008
20:11:50.190888 IP gw1 > speedtest.teksavvy.com: ICMP echo request, id 1, seq 1033, length 1008
20:11:50.210388 IP speedtest.teksavvy.com > gw1: ICMP echo reply, id 1, seq 1033, length 1008
20:11:51.192876 IP gw1 > speedtest.teksavvy.com: ICMP echo request, id 1, seq 1034, length 1008
20:11:56.189157 IP gw1 > speedtest.teksavvy.com: ICMP echo request, id 1, seq 1035, length 1008
20:11:56.206388 IP speedtest.teksavvy.com > gw1: ICMP echo reply, id 1, seq 1035, length 1008
20:11:57.190192 IP gw1 > speedtest.teksavvy.com: ICMP echo request, id 1, seq 1036, length 1008
20:12:02.189473 IP gw1 > speedtest.teksavvy.com: ICMP echo request, id 1, seq 1037, length 1008
20:12:02.206396 IP speedtest.teksavvy.com > gw1: ICMP echo reply, id 1, seq 1037, length 1008

Can you guys setup a tcpdump or similar on your side to see if the packets are making it to your network?

notfred

join:2012-09-15
reply to TSI Marc
How about now, my speed is brutal again:


See above, it was the same last night, but this morning was good. Something is horrifically oversubscribed somewhere in the network.


TypeS

join:2012-12-17
London, ON
kudos:1
Have you tried your ipv4 login like others have? I read above that you said you hadn't tried it yet. Might want to try that first.

keltron

join:2012-12-26
North York, ON
reply to notfred


torobull123

join:2009-06-20
reply to torobull123
Speak of the devil. I was about to re-post on this thread bout the past couple nights of peak hour congestion. Including tonight.

I running on 1/4 sync now.

notfred

join:2012-09-15
reply to TypeS
Good point, just tried it now and what do you know:


So IPv4 is close to perfect right now, going to switch back and forth a couple more times to double check.

notfred

join:2012-09-15
And here's the IPv6 one immediately on switching:


Better than it was but still way below what it should be.

Marc / Gabe, you have a problem with the v6 logins (i.e. @hsiservice.net) hitting congestion that the v4 logins (i.e. @teksavvy.com) are not hitting.

UnixMan

join:2012-10-14
reply to Phibian
Phibian,

As I remember you are one of the active forum users that have MLPPP setup and using a UNIX-like OS (Linux/FreeBSD) for it. I would like to open another forum thread about evenings/weekends problems (Congestions/QoS/Throttling whatsoever ...) I'm seeing with MLPPP and hope you'll be able to help me to figure out what is going on.

Any call to TekSavvy technical support regarding the issue is becoming useless. It's not the first time I called and spoke to a lady who was mostly a customer support person than a technician and was driven by an instruction what to say if somebody had called. By the way her name is Megan (it's for Marc info). Anyway ...

For now I have a simple question. How does it come that you are in Ottawa and I am in GTA seeing some problems with the same gateway: 206.248.154.106?


Phibian

join:2009-06-01
Ottawa, ON
Reviews:
·TekSavvy DSL
I believe that everyone using an @wiredhighspeed login gets funneled through to the same endpoint (.106) on TSI's side (which maybe part pod the issue. Ie something login related). Also all TSI customers (at least in eastern Canada) go through Toronto so location doesn't make a huge difference.

dgass

join:2007-09-27
Etobicoke, ON
kudos:1
Reviews:
·TekSavvy DSL
·Rogers Hi-Speed
reply to notfred
Here is my speed test at ~2pm Sunday. I'll do more this evening to see if I have these same issues.




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

1 4 ms 2 ms 2 ms unknown [192.168.1.1]
2 12 ms 10 ms 12 ms lo-100.erx06.tor.packetflow.ca [206.248.154.106]

3 11 ms 9 ms 9 ms 2110.ae0.agg01.tor.packetflow.ca [69.196.136.44]

4 11 ms 9 ms 9 ms speedtest.teksavvy.com [206.248.140.50]

Trace complete.

amadues

join:2008-07-01
Toronto, ON

@hsiservice
 

@dslinternet
 
It's happening again.

With @hsiservice.net login:

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

1 2 ms 1 ms 1 ms CISCO13522 [192.168.1.1]
2 83 ms 83 ms 82 ms lo-100.erx04.tor.packetflow.ca [206.248.154.103]

3 76 ms 94 ms 78 ms 2120.ae0.bdr01.tor.packetflow.ca [69.196.136.66]

4 145 ms 95 ms 99 ms 2110.ae0.agg01.tor.packetflow.ca [69.196.136.44]

5 109 ms 92 ms 91 ms speedtest.teksavvy.com [206.248.140.50]

High latency and lower throughput were sustained for over 30 minutes. Immediately after authenticating with dslinternet.ca login:

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

1 2 ms 1 ms 1 ms CISCO13522 [192.168.1.1]
2 16 ms 10 ms 11 ms lo-100.lns02.tor.packetflow.ca [206.248.154.122]

3 13 ms 9 ms 11 ms 2110.ae0.agg01.tor.packetflow.ca [69.196.136.44]

4 10 ms 10 ms 9 ms speedtest.teksavvy.com [206.248.140.50]

UnixMan

join:2012-10-14
reply to dgass
I (and I hope we) appreciate all users sending their positive results about "cool" connection they have with TekSavvy.

But ... we are really interested in catching the existing problem based on the professional opinion of some of us. So, PLEASE, do not spam this thread with just results of "speedtest.net".

Sorry and thank you in advance!

dgass

join:2007-09-27
Etobicoke, ON
kudos:1
Reviews:
·TekSavvy DSL
·Rogers Hi-Speed
Who do you think you are? Join date of less than 6 months ago and you know all? I'm posting here to give my results on a VDSL connection with my first test as a baseline during nonprime time.
I use an @wiredhighspeed login.
Here is the same trace and speed test at ~8pm Sunday

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

1 4 ms 2 ms 2 ms unknown [192.168.1.1]
2 12 ms 12 ms 11 ms lo-100.erx06.tor.packetflow.ca [206.248.154.106]

3 12 ms 10 ms 10 ms 2110.ae0.agg01.tor.packetflow.ca [69.196.136.44]

4 11 ms 19 ms 10 ms speedtest.teksavvy.com [206.248.140.50]

Trace complete.




And it's not spam DB.

Edit: I'm one of the people that Doesn't see much of a problem. So this may help TSI track stuff down.


TypeS

join:2012-12-17
London, ON
kudos:1
Are @wiredhighspeed.com logins mlppp logins? I never got around to setting up MLPPP while I still had DSL.

dgass

join:2007-09-27
Etobicoke, ON
kudos:1
Ya.
That also means that I'm always on the same erx, as all MLPP traffic goes through it. Or so I remember. If they have changed it then my mistake.


TypeS

join:2012-12-17
London, ON
kudos:1
Reviews:
·TekSavvy Cable
So perhaps everyone on the MLPPP (@wirehighspeed.com) and IPv6 (@hsiservice.net) logins experiencing slow speeds in the evening should try their regular @teksavvy.com logins if they have not yet? Would be useful information for TekSavvy as it establishes a pattern.

s0dhi

join:2011-08-02
Brampton, ON
Reviews:
·TekSavvy DSL
reply to Phibian
Hi Phibian,

My ping results were as follows:

Ping statistics for 206.248.154.104:
Packets: Sent = 100, Received = 100, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 11ms, Maximum = 485ms, Average = 52ms


RobinK

join:2004-04-16
Canada
reply to torobull123
I just ran some speed tests. Switched several times to confirm. Results are consistent.

@hsiservice.net



@teksavvy.com



Teksavvy, any update?
--
Argue opinions using facts. Not facts using opinions.

dgass

join:2007-09-27
Etobicoke, ON
kudos:1
Reviews:
·TekSavvy DSL
·Rogers Hi-Speed
reply to dgass
Tracing route to speedtest.teksavvy.com [206.248.140.50]
over a maximum of 30 hops:
1 4 ms 3 ms 3 ms unknown [192.168.1.1]
2 12 ms 11 ms 12 ms lo-100.erx06.tor.packetflow.ca [206.248.154.106]
3 11 ms 10 ms 10 ms 2110.ae0.agg01.tor.packetflow.ca [69.196.136.44]
4 11 ms 11 ms 10 ms speedtest.teksavvy.com [206.248.140.50]
Trace complete.






With my Wiredhighspeed login so no issues Sunday after 11:30

I will only post most if my results over the next few evenings are different. Hope this helps.


Jethro86

join:2005-05-27
Winchester, ON
Reviews:
·TekSavvy DSL
reply to torobull123

Re: [DSL] Network congestion tonight? Anyone have an idea!!

Another confusing night (late afternoon @ 5pm) of crappy pings even though DL speeds were "OK"?
Adequate ping but not great
»speedtest.net/result/2550846585.png
And then...
»speedtest.net/result/2550876073.png
----------------
>ping teksavvy.speedtest.net

Ping statistics for 74.209.160.12:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 166ms, Maximum = 244ms, Average = 197ms
----------------------
ping teksavvy.speedtest.net -n 100

Ping statistics for 74.209.160.12:
Packets: Sent = 100, Received = 99, Lost = 1 (1% loss),
Approximate round trip times in milli-seconds:
Minimum = 167ms, Maximum = 568ms, Average = 363ms
-----------------------
ping teksavvy.speedtest.net -n 10

Ping statistics for 74.209.160.12:
Packets: Sent = 10, Received = 8, Lost = 2 (20% loss),
Approximate round trip times in milli-seconds:
Minimum = 152ms, Maximum = 352ms, Average = 236ms
--------------------------
>tracert teksavvy.speedtest.net

Tracing route to teksavvy.speedtest.net [74.209.160.12]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.2.1
2 377 ms 224 ms 329 ms lo-100.lns02.tor.packetflow.ca [206.248.154.122]

3 279 ms 274 ms 276 ms 2120.ae0.bdr01.tor.packetflow.ca [69.196.136.66]

4 267 ms 260 ms 259 ms 10gigabitethernet4-3.core1.tor1.he.net [216.66.3
6.97]
5 264 ms 255 ms 273 ms 10gigabitethernet7-3.core1.chi1.he.net [184.105.
213.150]
6 77 ms 76 ms 68 ms 10gigabitethernet3-2.core1.den1.he.net [184.105.
213.86]
7 202 ms 217 ms 190 ms 10gigabitethernet3-4.core1.sea1.he.net [184.105.
213.41]
8 177 ms 218 ms 264 ms six.netriver.net [206.81.80.160]
9 150 ms 176 ms 145 ms static-74-209-160-12.lynnwood.netriver.net [74.2
09.160.12]

Trace complete.