Reviews:
 ·TekSavvy DSL
| Huge network latency on regular upload Strange network issue(s), that are impacting network gaming play etc
Here is my ping results while running this speedtest
64 bytes from a96-16-44-79.deploy.akamaitechnologies.com (96.16.44.79): icmp_req=12 ttl=59 time=9.09 ms
64 bytes from a96-16-44-79.deploy.akamaitechnologies.com (96.16.44.79): icmp_req=13 ttl=59 time=13.8 ms
64 bytes from a96-16-44-79.deploy.akamaitechnologies.com (96.16.44.79): icmp_req=14 ttl=59 time=12.4 ms
64 bytes from a96-16-44-79.deploy.akamaitechnologies.com (96.16.44.79): icmp_req=15 ttl=59 time=26.6 ms
64 bytes from a96-16-44-79.deploy.akamaitechnologies.com (96.16.44.79): icmp_req=16 ttl=59 time=31.4 ms
64 bytes from a96-16-44-79.deploy.akamaitechnologies.com (96.16.44.79): icmp_req=17 ttl=59 time=14.3 ms
64 bytes from a96-16-44-79.deploy.akamaitechnologies.com (96.16.44.79): icmp_req=18 ttl=59 time=707 ms
64 bytes from a96-16-44-79.deploy.akamaitechnologies.com (96.16.44.79): icmp_req=19 ttl=59 time=1041 ms
64 bytes from a96-16-44-79.deploy.akamaitechnologies.com (96.16.44.79): icmp_req=20 ttl=59 time=1046 ms
64 bytes from a96-16-44-79.deploy.akamaitechnologies.com (96.16.44.79): icmp_req=21 ttl=59 time=630 ms
64 bytes from a96-16-44-79.deploy.akamaitechnologies.com (96.16.44.79): icmp_req=22 ttl=59 time=1015 ms
64 bytes from a96-16-44-79.deploy.akamaitechnologies.com (96.16.44.79): icmp_req=23 ttl=59 time=1041 ms
64 bytes from a96-16-44-79.deploy.akamaitechnologies.com (96.16.44.79): icmp_req=24 ttl=59 time=1007 ms
64 bytes from a96-16-44-79.deploy.akamaitechnologies.com (96.16.44.79): icmp_req=25 ttl=59 time=1021 ms
64 bytes from a96-16-44-79.deploy.akamaitechnologies.com (96.16.44.79): icmp_req=26 ttl=59 time=16.4 ms
64 bytes from a96-16-44-79.deploy.akamaitechnologies.com (96.16.44.79): icmp_req=27 ttl=59 time=1018 ms
64 bytes from a96-16-44-79.deploy.akamaitechnologies.com (96.16.44.79): icmp_req=28 ttl=59 time=1062 ms
64 bytes from a96-16-44-79.deploy.akamaitechnologies.com (96.16.44.79): icmp_req=29 ttl=59 time=928 ms
64 bytes from a96-16-44-79.deploy.akamaitechnologies.com (96.16.44.79): icmp_req=30 ttl=59 time=9.48 ms
64 bytes from a96-16-44-79.deploy.akamaitechnologies.com (96.16.44.79): icmp_req=31 ttl=59 time=1033 ms
64 bytes from a96-16-44-79.deploy.akamaitechnologies.com (96.16.44.79): icmp_req=32 ttl=59 time=1054 ms
64 bytes from a96-16-44-79.deploy.akamaitechnologies.com (96.16.44.79): icmp_req=33 ttl=59 time=930 ms
64 bytes from a96-16-44-79.deploy.akamaitechnologies.com (96.16.44.79): icmp_req=34 ttl=59 time=11.8 ms
64 bytes from a96-16-44-79.deploy.akamaitechnologies.com (96.16.44.79): icmp_req=35 ttl=59 time=10.7 ms
64 bytes from a96-16-44-79.deploy.akamaitechnologies.com (96.16.44.79): icmp_req=36 ttl=59 time=9.57 ms
The poor pings only happen in the upload portion of the test.
Now I understand that this is a result of my upload bandwidth being saturated, and I could take steps on my router to limit my speeds and help alleviate the issue. With this said however is is a newish issue (new as in started sometime in the past 4-6 months). In 2011 and early 2012 this was not an issue. (or at least not one noticeable by 1000+ ping times).
Model Name: SB6120
Vendor Name: Motorola
Firmware Name: SB_KOMODO-1.0.6.1-SCM00-NOSH
Boot Version: PSPU-Boot 1.0.0.4m1
Is this an indication of another issue going on? Or is it a result of some changes Rogers has made recently?
Opinions? |
