Lately, I have been getting the same issues that happened a year ago (constant pings over 200 during peak hours), as show below:
Tracing route to google.navigation.opendns.com [208.69.36.231] over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 192.168.1.1 2 * * * Request timed out. 3 11 ms 13 ms 13 ms host-72-51-175-5.newwavecomm.net [72.51.175.5] 4 217 ms 206 ms 201 ms sl-gw36-chi-10-2.sprintlink.net [160.81.84.61] 5 209 ms 207 ms 197 ms sl-crs1-chi-0-1-0-2.sprintlink.net [144.232.26.11] 6 205 ms 205 ms 210 ms sl-st20-chi-4-0-0.sprintlink.net [144.232.18.153] 7 219 ms 235 ms 233 ms po4-2.core01.ord03.atlas.cogentco.com [154.54.13.45] 8 204 ms 207 ms 199 ms te4-1.mpd01.ord03.atlas.cogentco.com [154.54.3.242] 9 220 ms 224 ms 223 ms vl3503.na31.b002281-5.ord03.atlas.cogentco.com [38.112.35.122] 10 208 ms 219 ms 216 ms 38.104.102.62 11 234 ms 238 ms 239 ms 208.69.36.231
Trace complete.
I got in touch with their Live Chat support and the representative said they recently got a contract for more bandwidth and the issue should be resolved in the next week or so, no later than Monday April 13 2009.
Heh, good luck. It took me 6 months of complaining to get them to fix the issue. I see you're in an area already on the sprint upstream provider... hopefully they'll be able to rectify it, but I put no faith in Newwave ever doing the right thing for it's customers.
