I originally noticed an issue when using Amazon streaming on my roku, however, this doesn't seem to be limited by that.
When using speedtest.net I get full speed on some servers 50/25 and very slow speeds on some other servers. 4-6 down, upload is usually fine. It generally seems like speedtesting to rapidsystem servers in Tampa was slow d/l speeds. But, T3 COmunications server in (Ft Myers) test full 55/38 connection speed, excellent.
I did some pings and took some traceroutes. Please convert this to a support issue.
c:\> tracert rapidsys.com
Tracing route to rapidsys.com [209.84.253.40]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms WRT610N [192.168.1.1]
2 4 ms 4 ms 4 ms 10.38.37.86
3 10 ms 6 ms 14 ms G0-3-3-4.TAMPFL-LCR-22.verizon-gni.net [130.81.110.222]
4 6 ms 7 ms 6 ms ae2-0.TPA01-BB-RTR2.verizon-gni.net [130.81.199.82]
5 11 ms 12 ms 11 ms 0.ae2.BR1.MIA19.ALTER.NET [152.63.87.178]
6 64 ms 67 ms 69 ms 204.255.168.30
7 64 ms 66 ms 72 ms be2054.ccr21.mia01.atlas.cogentco.com [154.54.80.41]
8 78 ms 76 ms 72 ms te2-8.ccr01.tpa01.atlas.cogentco.com [154.54.80.222]
9 76 ms 76 ms 76 ms te4-1.mag01.tpa01.atlas.cogentco.com [154.54.1.54]
10 74 ms 72 ms 71 ms L3router.rapidsys.com [38.104.150.50]
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 *
C:\Users\Bob> ping rapidsys.com
Pinging rapidsys.com [209.84.253.40] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 209.84.253.40:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
C:\Users\Bob> ping amazon.com
Pinging amazon.com [72.21.194.212] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 72.21.194.212:
Packets: Sent = 3, Received = 0, Lost = 3 (100% loss),
Control-C
C:\Users\Bob> ping google.com
Pinging google.com [65.196.188.21] with 32 bytes of data:
Reply from 65.196.188.21: bytes=32 time=7ms TTL=59
Reply from 65.196.188.21: bytes=32 time=6ms TTL=59
Reply from 65.196.188.21: bytes=32 time=6ms TTL=59
Reply from 65.196.188.21: bytes=32 time=8ms TTL=59
Ping statistics for 65.196.188.21:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 6ms, Maximum = 8ms, Average = 6ms
C:\Users\Bob> ping microsoft.com
Pinging microsoft.com [64.4.11.37] with 32 bytes of data:
Request timed out.
Request timed out.
Ping statistics for 64.4.11.37:
Packets: Sent = 2, Received = 0, Lost = 2 (100% loss),
Control-C
C:\Users\Bob> ping amazonaws.com
Pinging amazonaws.com [72.21.210.29] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 72.21.210.29:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
C:\Users\Bob> ping netflix.com
Pinging netflix.com [69.53.236.17] with 32 bytes of data:
Reply from 69.53.236.17: bytes=32 time=82ms TTL=244
Reply from 69.53.236.17: bytes=32 time=81ms TTL=244
Reply from 69.53.236.17: bytes=32 time=81ms TTL=244
Reply from 69.53.236.17: bytes=32 time=82ms TTL=244
Ping statistics for 69.53.236.17:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 81ms, Maximum = 82ms, Average = 81ms
C:\Users\Bob> ping infor.com
Pinging infor.com [207.54.49.200] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 207.54.49.200:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
C:\Users\Bob> tracert microsoft.com
Tracing route to microsoft.com [64.4.11.37]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms WRT610N [192.168.1.1]
2 3 ms 4 ms 4 ms 10.38.37.86
3 6 ms 7 ms 7 ms G0-3-3-4.TAMPFL-LCR-21.verizon-gni.net [130.81.109.248]
4 5 ms 29 ms 6 ms ae1-0.TPA01-BB-RTR1.verizon-gni.net [130.81.199.74]
5 11 ms 11 ms * 0.ae2.XL1.MIA19.ALTER.NET [152.63.8.113]
6 11 ms 11 ms 12 ms 0.xe-8-1-0.GW1.MIA19.ALTER.NET [152.63.84.198]
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * C:\Users\Bob>
C:\Users\Bob> tracert amazonaws.com
Tracing route to amazonaws.com [72.21.210.29]
over a maximum of 30 hops:
1 9 ms <1 ms <1 ms WRT610N [192.168.1.1]
2 22 ms 4 ms 4 ms 10.38.37.86
3 9 ms 7 ms 7 ms G0-3-3-4.TAMPFL-LCR-21.verizon-gni.net [130.81.109.248]
4 14 ms 4 ms 6 ms ae1-0.TPA01-BB-RTR1.verizon-gni.net [130.81.199.74]
5 10 ms 11 ms 12 ms 0.ae1.BR1.MIA19.ALTER.NET [152.63.87.162]
6 43 ms 45 ms 44 ms 204.255.168.42
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
C:\Users\Bob> ping mail.google.com
Pinging googlemail.l.google.com [173.194.37.149] with 32 bytes of data:
Reply from 173.194.37.149: bytes=32 time=10ms TTL=57
Reply from 173.194.37.149: bytes=32 time=12ms TTL=57
Reply from 173.194.37.149: bytes=32 time=11ms TTL=57
Reply from 173.194.37.149: bytes=32 time=12ms TTL=57
Ping statistics for 173.194.37.149:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 10ms, Maximum = 12ms, Average = 11ms
C:\Users\Bob> tracert mail.google.com
Tracing route to googlemail.l.google.com [173.194.37.149]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms WRT610N [192.168.1.1]
2 8 ms 4 ms 4 ms 10.38.37.86
3 8 ms 6 ms 7 ms G0-3-3-3.TAMPFL-LCR-21.verizon-gni.net [130.81.185.94]
4 7 ms 7 ms 49 ms ae1-0.TPA01-BB-RTR1.verizon-gni.net [130.81.199.74]
5 11 ms 12 ms 11 ms 0.ae2.XL1.MIA19.ALTER.NET [152.63.8.113]
6 34 ms 39 ms 11 ms 0.xe-8-0-0.GW1.MIA19.ALTER.NET [152.63.84.182]
7 47 ms 46 ms 46 ms google-gw.customer.alter.net [63.65.188.38]
8 14 ms 11 ms 11 ms 209.85.253.120
9 11 ms 11 ms 12 ms 209.85.241.145
10 12 ms 11 ms 11 ms mia05s18-in-f21.1e100.net [173.194.37.149]
Trace Complete
----
These were run on a desktop connected via enternet NOT WiFi. So, wifi dropouts are not an issue. My Roku is also connected via ethernet.
BTW: This could also occur during the day, I'm just not home to know about it.
Please make this a support issue.
thanks,
BOb