|
to bulletsam
Re: [IL] Latency issues.Your latency is not bad but your speed is too low if you have 50/5 service. |
|
1 edit |
Latency is not bad? lol, ok. Sure acts bad considering the norm is 25ms. Yes, I have 50/5 service.
I'd say the weather isn't helping, we've had ice precipitation in Illinois and Indiana all day.
|
|
|
|
yeah mine has been horrible all day here in Charleston, I can't even get speedtest to load now to see just how slow it is |
|
jhamps10 |
to bulletsam
you may want to PM mediacom chad or tweet mediacom support, I went to them to see if anyone else had complained of slow sppeds and latency, they sent a reset to the modem and now I'm getting speeds back to normal now |
|
|
Well, it worked. I hate calling support, but I took a chance.
Thanks for the info. |
|
|
heh so do I, hate being bewiltered on the phone by some dummy who thinks I don't know what I'm doing... that's why the first place I go is @mediacomsupport on twitter or their website forums and post there |
|
wth Premium Member join:2002-02-20 Iowa City,IA |
to Anonymous88
said by Anonymous88:Your latency is not bad but your speed is too low if you have 50/5 service. 64ms to Mediacoms hop #3 (172.30.9.189) is way to high. Should be under 30/35ms. |
|
1 edit |
I still stand by my opinion. You obviously can disagree. Below 100ms to Google is OK in my book. |
|
|
said by Anonymous88:Below 100ms to Google is OK in m book. I guess it all depends on what you are accustomed to seeing. If my ping to google (8.8.8.8) suddenly jumped to being over 50ms consistently, I would raise an eyebrow at least. » i632.photobucket.com/alb ··· ping.pngInteresting that my ping to a sever in Des Moines is nearly double that to Google... |
|
NormanSI gave her time to steal my mind away MVM join:2001-02-14 San Jose, CA TP-Link TD-8616 Asus RT-AC66U B1 Netgear FR114P
|
to Anonymous88
said by Anonymous88:I still stand by my opinion. You obviously can disagree. Below 100ms to Google is OK in my book. For HSI connections (DOCSIS or DSL), Google should never be more than 35 ms away in most cases: Tracing route to www.google.com [74.125.224.116]
over a maximum of 30 hops:
1 <1 ms <1 ms 1 ms 192.168.42.1
2 26 ms 26 ms 26 ms 173-228-7-1.dsl.static.sonic.net [173.228.7.1]
3 25 ms 24 ms 25 ms gig1-4.cr1.lsatca11.sonic.net [70.36.243.13]
4 24 ms 24 ms 24 ms 0.xe-5-1-0.gw.pao1.sonic.net [69.12.211.1]
5 26 ms 24 ms 32 ms 0.xe-6-0-0.gw3.equinix-sj.sonic.net [64.142.0.185]
6 25 ms 25 ms 26 ms eqixsj-google-gige.google.com [206.223.116.21]
7 26 ms 26 ms 25 ms 216.239.49.168
8 27 ms 27 ms 27 ms 64.233.174.109
9 27 ms 26 ms 26 ms nuq04s08-in-f20.1e100.net [74.125.224.116]
Trace complete.
|
|
|