ContributionsMost RecentMost LikesSolutionsRe: High latency internet and terrible speeds. Pinging 192.168.0.1 with 32 bytes of data: Reply from 192.168.0.1: bytes=32 time<1ms TTL=64 Reply from 192.168.0.1: bytes=32 time<1ms TTL=64 Reply from 192.168.0.1: bytes=32 time<1ms TTL=64 Reply from 192.168.0.1: bytes=32 time<1ms TTL=64 Reply from 192.168.0.1: bytes=32 time<1ms TTL=64 Reply from 192.168.0.1: bytes=32 time<1ms TTL=64 Reply from 192.168.0.1: bytes=32 time<1ms TTL=64 Reply from 192.168.0.1: bytes=32 time<1ms TTL=64 Reply from 192.168.0.1: bytes=32 time<1ms TTL=64 Reply from 192.168.0.1: bytes=32 time<1ms TTL=64 Reply from 192.168.0.1: bytes=32 time<1ms TTL=64 Reply from 192.168.0.1: bytes=32 time=1ms TTL=64 Reply from 192.168.0.1: bytes=32 time<1ms TTL=64 Reply from 192.168.0.1: bytes=32 time<1ms TTL=64 Reply from 192.168.0.1: bytes=32 time<1ms TTL=64 Reply from 192.168.0.1: bytes=32 time<1ms TTL=64 Reply from 192.168.0.1: bytes=32 time<1ms TTL=64 Reply from 192.168.0.1: bytes=32 time=1ms TTL=64 Reply from 192.168.0.1: bytes=32 time<1ms TTL=64 Reply from 192.168.0.1: bytes=32 time<1ms TTL=64 Reply from 192.168.0.1: bytes=32 time<1ms TTL=64 Reply from 192.168.0.1: bytes=32 time<1ms TTL=64 Reply from 192.168.0.1: bytes=32 time<1ms TTL=64 Reply from 192.168.0.1: bytes=32 time<1ms TTL=64 Reply from 192.168.0.1: bytes=32 time<1ms TTL=64 Reply from 192.168.0.1: bytes=32 time<1ms TTL=64 Reply from 192.168.0.1: bytes=32 time<1ms TTL=64 Reply from 192.168.0.1: bytes=32 time<1ms TTL=64 Reply from 192.168.0.1: bytes=32 time<1ms TTL=64 Reply from 192.168.0.1: bytes=32 time<1ms TTL=64 Reply from 192.168.0.1: bytes=32 time<1ms TTL=64 Reply from 192.168.0.1: bytes=32 time<1ms TTL=64 Reply from 192.168.0.1: bytes=32 time<1ms TTL=64 Reply from 192.168.0.1: bytes=32 time<1ms TTL=64 Reply from 192.168.0.1: bytes=32 time<1ms TTL=64 Reply from 192.168.0.1: bytes=32 time<1ms TTL=64 Reply from 192.168.0.1: bytes=32 time<1ms TTL=64 Reply from 192.168.0.1: bytes=32 time<1ms TTL=64 Reply from 192.168.0.1: bytes=32 time<1ms TTL=64 Reply from 192.168.0.1: bytes=32 time<1ms TTL=64 Reply from 192.168.0.1: bytes=32 time<1ms TTL=64 Reply from 192.168.0.1: bytes=32 time<1ms TTL=64 Reply from 192.168.0.1: bytes=32 time<1ms TTL=64 Reply from 192.168.0.1: bytes=32 time<1ms TTL=64 Reply from 192.168.0.1: bytes=32 time<1ms TTL=64 Reply from 192.168.0.1: bytes=32 time<1ms TTL=64 Reply from 192.168.0.1: bytes=32 time<1ms TTL=64 Reply from 192.168.0.1: bytes=32 time<1ms TTL=64 Reply from 192.168.0.1: bytes=32 time=2ms TTL=64 Reply from 192.168.0.1: bytes=32 time<1ms TTL=64 Reply from 192.168.0.1: bytes=32 time<1ms TTL=64 Reply from 192.168.0.1: bytes=32 time<1ms TTL=64 Reply from 192.168.0.1: bytes=32 time=3ms TTL=64 Reply from 192.168.0.1: bytes=32 time<1ms TTL=64 Reply from 192.168.0.1: bytes=32 time<1ms TTL=64 Reply from 192.168.0.1: bytes=32 time<1ms TTL=64 Reply from 192.168.0.1: bytes=32 time<1ms TTL=64 Reply from 192.168.0.1: bytes=32 time<1ms TTL=64 Reply from 192.168.0.1: bytes=32 time<1ms TTL=64 Reply from 192.168.0.1: bytes=32 time<1ms TTL=64 Reply from 192.168.0.1: bytes=32 time<1ms TTL=64 Reply from 192.168.0.1: bytes=32 time<1ms TTL=64 Reply from 192.168.0.1: bytes=32 time<1ms TTL=64 Reply from 192.168.0.1: bytes=32 time<1ms TTL=64 Reply from 192.168.0.1: bytes=32 time<1ms TTL=64 Reply from 192.168.0.1: bytes=32 time<1ms TTL=64 Reply from 192.168.0.1: bytes=32 time<1ms TTL=64 Reply from 192.168.0.1: bytes=32 time<1ms TTL=64 Reply from 192.168.0.1: bytes=32 time=1ms TTL=64 Reply from 192.168.0.1: bytes=32 time<1ms TTL=64 Reply from 192.168.0.1: bytes=32 time<1ms TTL=64 Reply from 192.168.0.1: bytes=32 time<1ms TTL=64 Reply from 192.168.0.1: bytes=32 time<1ms TTL=64 Reply from 192.168.0.1: bytes=32 time<1ms TTL=64 Reply from 192.168.0.1: bytes=32 time<1ms TTL=64 Reply from 192.168.0.1: bytes=32 time<1ms TTL=64 Reply from 192.168.0.1: bytes=32 time<1ms TTL=64 Reply from 192.168.0.1: bytes=32 time<1ms TTL=64 Reply from 192.168.0.1: bytes=32 time<1ms TTL=64 Reply from 192.168.0.1: bytes=32 time<1ms TTL=64 Reply from 192.168.0.1: bytes=32 time<1ms TTL=64 Reply from 192.168.0.1: bytes=32 time<1ms TTL=64 Reply from 192.168.0.1: bytes=32 time<1ms TTL=64 Reply from 192.168.0.1: bytes=32 time<1ms TTL=64 Reply from 192.168.0.1: bytes=32 time<1ms TTL=64 Reply from 192.168.0.1: bytes=32 time<1ms TTL=64 Reply from 192.168.0.1: bytes=32 time=1ms TTL=64 Reply from 192.168.0.1: bytes=32 time<1ms TTL=64 Reply from 192.168.0.1: bytes=32 time<1ms TTL=64 Reply from 192.168.0.1: bytes=32 time<1ms TTL=64 Reply from 192.168.0.1: bytes=32 time<1ms TTL=64 Reply from 192.168.0.1: bytes=32 time<1ms TTL=64 Reply from 192.168.0.1: bytes=32 time<1ms TTL=64 Reply from 192.168.0.1: bytes=32 time<1ms TTL=64 Reply from 192.168.0.1: bytes=32 time<1ms TTL=64 Reply from 192.168.0.1: bytes=32 time<1ms TTL=64 Reply from 192.168.0.1: bytes=32 time<1ms TTL=64 Reply from 192.168.0.1: bytes=32 time<1ms TTL=64 Reply from 192.168.0.1: bytes=32 time<1ms TTL=64 Reply from 192.168.0.1: bytes=32 time<1ms TTL=64 Ping statistics for 192.168.0.1: Packets: Sent = 100, Received = 100, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 3ms, Average = 0ms Re: High latency internet and terrible speeds. Tecknowhelp said: If you ping 192.168.0.1 what is your average latency? If it's over 1-2ms that isa problem. The gateway is a modem and router combined. The modem provides the WAN connection, and the router inside provides the LAN, or network. If you have something causing latency on your LAN, then that needs to be fixed first IMO. Do you have a stand alone modem you can try? I get between 0-1ms when pinging 192.168.0.1. I have no stand alone modem to try, unless I go buy one at the store. It did once spike up to 7ms though. Tecknowhelp said: Looking at your signal levels, I see uncorrectables on downstream channel 8. I also notice your only bonding on 3 channels, not 4. Is this normal? I honestly can't say if that's normal, because this modem was just put in on Friday afternoon by the tech that came out. Re: High latency internet and terrible speeds. The router is the modem. It's one of the ones that Cox has provided to me. It's also one of the last 4 that the company has provided to me in the last year. It is currently a Ubee DOCSIS 3.0 DDW365. And yes, there is an average ping that is low, that isn't the issue. The issue is the very large spikes that are pretty frequent and cause latency issues. edit:https://i.gyazo.com/e385d2bcee673b27c7bfbb66d888fb89.png High latency internet and terrible speeds. I have been back and forth between twitter CS, phone CS, and having "techs" come out to my house. So far, nothing has been fixed, and all I keep hearing is "everything is showing good" T2 Tech: "I see where you are having packet loss, I'm going to schedule someone to come out and take a look." 4 days later "I ran some tests, and everything is showing good and passing." Twitter CS: "I am seeing an 8% packet loss on the ping to the modem" Twitter CS 3 days later: "The modem is up and running with a good signal" Generally, most of my time spent on the computer is either playing games or coding. My normal in-game latency is around 40-50ms on a regular basis for the primary game that I play. It is a multi player game, that people expect me to be available for certain periods of time on certain nights. For the past week (November 24, 2015 until today November 28, 2015) I've been getting periodic latency spikes and packet drops. It's happens quite often and so far have been unable to figure out the cause. At the present, I've replaced my modem with another one, but have yet to have someone come out and actually take a look at the line to the house. In fact, I've replaced my modem a number of times in the last year and have had repeated visits by "techs" who have come out and have only had small fixes for whatever problem I'm seeing. At the present, my internet is spotty and is even taking webpages to have long load times. Now, considering this isn't an issue directly related to the server of the games that I play, but it affects the internet as a whole at my house, as you can see if you view the bottom screen caps directed between google.com and the servers. You can see that it's not due to bad routing to one server, but that it's affecting everything that I connect with. I am extremely frustrated with this and so is my fiancee. https://gyazo.com/948418cccb48bf206ebd53695c090ea5 6:55p https://gyazo.com/04c87766a9f088f0b0bea18cbc98f90a https://gyazo.com/bf65897335050694a1d1dbee96bcd04d https://gyazo.com/195cbe1baa4e606e807acbc7d77d0619 https://gyazo.com/ce9c2caee9bed00b9c04cecaeba5ad97 https://gyazo.com/b96e418cae097c1211385c033b9b3bd7 https://gyazo.com/5e6af750c929a6476464a2bfc552d733 https://gyazo.com/e0b6de7b7225ece138581d96675a07fa 106 https://gyazo.com/05d613351d24803663c7e005bc5c8d1c https://gyazo.com/6dd48c8838d519e67dff0c4107c90e7f Here are some screen caps from WinMTR showing ping traces to google.com and to the game's servers. Google.com: https://gyazo.com/9143eea1ff3f10c32d3ee25b1c5d80a2 https://gyazo.com/072029f2de7147205085d8604ed2e627 Cox.net: https://gyazo.com/f4e5c76813965b92490364bf0811da0a (Oh look, 2k+ pings and 6-9% packet loss to Cox.net address) Blizzard Servers: https://gyazo.com/9e2715185006dbeaabd773a3be70566f https://gyazo.com/cdde86347e55e534307385edf695366b Speed tests: https://gyazo.com/b50e3909162d4652b4982cf35f5aa462 Cox (looks decent) https://gyazo.com/744e21df42bd7a9aa9ab630339a3d553 Speedof.me (shows actual proof that it's terrible, even little graph at bottom shows where it was back in september vs now) https://gyazo.com/eaca6dc1d13f1d098260b8ea8d1a5f76 Speedtest.net (again, terrible speed... why is cox site only one showing good when everyone else is showing what it really is like? Hrm...) Re: Upload speed spotty, huge packet lost. This is something that I"m having issues with too. Not only am I getting continually lower speeds compared to what I should be getting, but I'm getting large ms spikes and packet loss. I too have had a tech come out and nothing was done other than swapping my modem out for a different one. Re: Upload speeds slower This computer is attached to Ethernet Port #3, but it doesn't make a difference when I check it against any other port. In fact, since I've been out of town, now my upload is SUB 1 mb/s. The simple fact that the connection has gotten worse is seriously making me not want to have Cox anymore. This has been a continual issue for months now. I either need someone to come out and fix it, replace the modem/router combo that was given to me by one of the techs, upgrade my account (which won't make a difference, because if 5mb/s up is what I have now and I'm getting less than 1 then going to 10mb/s up should give me 2!) Re: Upload speeds slower There might be a splitter inside of the Cox box on the wall outside the house where it comes in from the pole. After that point, it goes through a small wall right to the modem. So I couldn't even test it if I wanted because it's inside of that box. Re: Upload speeds slower Hard wire. Re: Upload speeds slower I'm on the preferred plan, and should be getting 5 up. I used to get that speed, but in the past month I've gotten between 1-3. I stream a lot when I'm on the computer at night (during non-peak times) and it makes it impossible to stream at a good quality. I've called into tech support for this issue at least twice, and all I've gotten was "You're connection seems fine". As of a moment ago,http://i.imgur.com/4dLuhN3.png that was my dl/ul speeds. Even going with testmy.net, it shows that my upload is considerably less than I should be getting at about 3-3.5. I find this very unacceptable. I was even considering going up to the premier plan and getting double the upload speed (but honestly, only getting 5mb on preferred and 10mb on premier is very lackluster.) If it wasn't for the fact that Cox is the only high-speed internet that's remotely decent in my area, I would go somewhere else.