dslreports logo
site
 
    All Forums Hot Topics Gallery
spc

spacer




how-to block ads


Search Topic:
uniqs
245
share rss forum feed

e84

join:2013-03-02

bandwidth issues WINDSOR

I've lost count on how many times this problem has arisen. Last episode I call them a few days ago, wait 45 minutes, and for a couple days my bandwidth goes to what it should be on a 6mb profile (5.3 down, 0.6 up).

So for a couple days everything looks good but once again my bandwidth has once again taken a nose dive.

The quality of service is really getting frustrating. So what's up teksavvy do you guys plan to correct this issue???





ping to router local LAN interface.

C:\Users\hsm>ping 192.168.1.1 -n 25

Pinging 192.168.1.1 with 32 bytes of data:
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64

Ping statistics for 192.168.1.1:
Packets: Sent = 25, Received = 25, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 2ms, Average = 1ms

ping to router WAN interface.

C:\Users\hsm>ping 184.175.13.82 -n 25

Pinging 184.175.13.82 with 32 bytes of data:
Reply from 184.175.13.82: bytes=32 time=2ms TTL=64
Reply from 184.175.13.82: bytes=32 time=2ms TTL=64
Reply from 184.175.13.82: bytes=32 time=2ms TTL=64
Reply from 184.175.13.82: bytes=32 time=2ms TTL=64
Reply from 184.175.13.82: bytes=32 time=2ms TTL=64
Reply from 184.175.13.82: bytes=32 time=2ms TTL=64
Reply from 184.175.13.82: bytes=32 time=2ms TTL=64
Reply from 184.175.13.82: bytes=32 time=2ms TTL=64
Reply from 184.175.13.82: bytes=32 time=2ms TTL=64
Reply from 184.175.13.82: bytes=32 time=2ms TTL=64
Reply from 184.175.13.82: bytes=32 time=2ms TTL=64
Reply from 184.175.13.82: bytes=32 time=3ms TTL=64
Reply from 184.175.13.82: bytes=32 time=2ms TTL=64
Reply from 184.175.13.82: bytes=32 time=2ms TTL=64
Reply from 184.175.13.82: bytes=32 time=2ms TTL=64
Reply from 184.175.13.82: bytes=32 time=3ms TTL=64
Reply from 184.175.13.82: bytes=32 time=2ms TTL=64
Reply from 184.175.13.82: bytes=32 time=2ms TTL=64
Reply from 184.175.13.82: bytes=32 time=2ms TTL=64
Reply from 184.175.13.82: bytes=32 time=2ms TTL=64
Reply from 184.175.13.82: bytes=32 time=2ms TTL=64
Reply from 184.175.13.82: bytes=32 time=2ms TTL=64
Reply from 184.175.13.82: bytes=32 time=2ms TTL=64
Reply from 184.175.13.82: bytes=32 time=2ms TTL=64
Reply from 184.175.13.82: bytes=32 time=2ms TTL=64

Ping statistics for 184.175.13.82:
Packets: Sent = 25, Received = 25, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 2ms, Maximum = 3ms, Average = 2ms

ping to next hop

Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\hsm>ping 206.248.154.104 -n 50

Pinging 206.248.154.104 with 32 bytes of data:
Reply from 206.248.154.104: bytes=32 time=57ms TTL=126
Reply from 206.248.154.104: bytes=32 time=56ms TTL=126
Reply from 206.248.154.104: bytes=32 time=167ms TTL=126
Reply from 206.248.154.104: bytes=32 time=75ms TTL=126
Reply from 206.248.154.104: bytes=32 time=56ms TTL=126
Reply from 206.248.154.104: bytes=32 time=56ms TTL=126
Reply from 206.248.154.104: bytes=32 time=56ms TTL=126
Reply from 206.248.154.104: bytes=32 time=58ms TTL=126
Reply from 206.248.154.104: bytes=32 time=55ms TTL=126
Reply from 206.248.154.104: bytes=32 time=59ms TTL=126
Reply from 206.248.154.104: bytes=32 time=56ms TTL=126
Reply from 206.248.154.104: bytes=32 time=59ms TTL=126
Reply from 206.248.154.104: bytes=32 time=91ms TTL=126
Reply from 206.248.154.104: bytes=32 time=56ms TTL=126
Reply from 206.248.154.104: bytes=32 time=55ms TTL=126
Reply from 206.248.154.104: bytes=32 time=118ms TTL=126
Reply from 206.248.154.104: bytes=32 time=109ms TTL=126
Reply from 206.248.154.104: bytes=32 time=54ms TTL=126
Reply from 206.248.154.104: bytes=32 time=54ms TTL=126
Reply from 206.248.154.104: bytes=32 time=54ms TTL=126
Reply from 206.248.154.104: bytes=32 time=54ms TTL=126
Reply from 206.248.154.104: bytes=32 time=55ms TTL=126
Reply from 206.248.154.104: bytes=32 time=54ms TTL=126
Reply from 206.248.154.104: bytes=32 time=55ms TTL=126
Reply from 206.248.154.104: bytes=32 time=56ms TTL=126
Reply from 206.248.154.104: bytes=32 time=55ms TTL=126
Reply from 206.248.154.104: bytes=32 time=55ms TTL=126
Reply from 206.248.154.104: bytes=32 time=55ms TTL=126
Reply from 206.248.154.104: bytes=32 time=58ms TTL=126
Reply from 206.248.154.104: bytes=32 time=55ms TTL=126
Reply from 206.248.154.104: bytes=32 time=59ms TTL=126
Reply from 206.248.154.104: bytes=32 time=55ms TTL=126
Reply from 206.248.154.104: bytes=32 time=55ms TTL=126
Reply from 206.248.154.104: bytes=32 time=56ms TTL=126
Reply from 206.248.154.104: bytes=32 time=264ms TTL=126
Reply from 206.248.154.104: bytes=32 time=58ms TTL=126
Reply from 206.248.154.104: bytes=32 time=55ms TTL=126
Reply from 206.248.154.104: bytes=32 time=114ms TTL=126
Reply from 206.248.154.104: bytes=32 time=217ms TTL=126
Reply from 206.248.154.104: bytes=32 time=55ms TTL=126
Reply from 206.248.154.104: bytes=32 time=54ms TTL=126
Reply from 206.248.154.104: bytes=32 time=54ms TTL=126
Reply from 206.248.154.104: bytes=32 time=76ms TTL=126
Reply from 206.248.154.104: bytes=32 time=55ms TTL=126
Reply from 206.248.154.104: bytes=32 time=51ms TTL=126
Reply from 206.248.154.104: bytes=32 time=54ms TTL=126
Reply from 206.248.154.104: bytes=32 time=59ms TTL=126
Reply from 206.248.154.104: bytes=32 time=148ms TTL=126
Reply from 206.248.154.104: bytes=32 time=54ms TTL=126
Reply from 206.248.154.104: bytes=32 time=55ms TTL=126

Ping statistics for 206.248.154.104:
Packets: Sent = 50, Received = 50, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 51ms, Maximum = 264ms, Average = 72ms



TSI Martin
Premium
join:2006-02-23
Chatham, ON
kudos:32

Might I suggest you post in the »TekSavvy Direct forum & we can take a closer look at the issue at hand.


e84

join:2013-03-02

Now the download is back to normal, upload is slightly low but I can live with that.