Forum Discussion

Promdates's avatar
Promdates
New Contributor
10 years ago

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...)

  • Tecknowhelp's avatar
    Tecknowhelp
    Valued Contributor II
    10 years ago

    What modem do you have? What are your signal levels?

    Your WinMTR is showing adverage latency on your lan of 36ms and spikes of 1700+. Need more info on your network. Looks like congestion to me. Disconnect your router from the modem and see if they still see latency to the modem.

  • Promdates's avatar
    Promdates
    New Contributor
    10 years ago

    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

  • Tecknowhelp's avatar
    Tecknowhelp
    Valued Contributor II
    10 years ago

    Promdates said:
    And yes, there is an average ping that is low, that isn't the issue

    If you ping 192.168.0.1 what is your average latency? If it's over 1-2ms that is a 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?

    Promdates said:
    https://i.gyazo.com/e385d2bcee673b27c7bfbb66d888fb89.png

    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?

  • Promdates's avatar
    Promdates
    New Contributor
    10 years ago

    Tecknowhelp said:
    If you ping 192.168.0.1 what is your average latency? If it's over 1-2ms that is a 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.

  • Internet_Speed2's avatar
    Internet_Speed2
    New Contributor
    10 years ago
    It comes down to the fact Cox does not care. There so called techs that waste your time by coming to your house know less than I do(they said a 3 foot CAT7 wire was to slow for them). and the So Called "Speed Test" on the cox web site is a scam. If you run it, it will tell what you what to see but if you run what the help desk ask you to do at; "speedtest" the down load is half or more less. As far as gaming the best you can hope for is a good day when Cox is working right and no one is using in the neither hood. Back to your try "namebench" to help with a little faster settings.
  • Tecknowhelp's avatar
    Tecknowhelp
    Valued Contributor II
    10 years ago

    Promdates said:
    I get between 0-1ms when pinging 192.168.0.1

    Then why does the MTR say different. This one here shows the average latency from PC to router as 22ms. Am I reading the data wrong? Or is the data incorrect? Try ping -n 100 192.168.0.1  That will give you a bigger data set.

  • Promdates's avatar
    Promdates
    New Contributor
    10 years ago

    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