Comcast level 1 hop Pc#
Comcast level 1 hop tv#
Comcast level 1 hop mac#

latency at 50ms with one and 900ms with the other. The difference was orders of magnitude, i.e.

Comcast level 1 hop mac#

I was able to get this to change by having a client with a different MAC address connect to the modem (and being issued a new IP). In short, every time I got issued an IP where the first hop in traceroute was 50.159.241.1 I had a huge latency/speed issue at peak times, however, if the first hope was something else the connection was perfectly fine. Is it possible that Comcast was splitting clients based on MAC addresses, and more specifically the OUI (Organizationally Unique Identifier) part of the MAC address ? I was being issued a different IP address, going through different hops in traces. To my big surprise, connecting a client with an Intel NIC fixed the connection issues, switching back to a Realtek NIC or the default Asus router MAC caused the terrible delay again. Note that it is common knowledge that every time you plug in a different Ethernet client to a cable modem, you have to reboot it so that the MAC address of the new client is recognized and leased an IP address. Comcast reimbursed me $30 for the service issues after I made about 10 calls, but never admitted any issue on their end.Д«eing the tinkering junkie that I am, I did notice something curious after continuous rebooting and switching hardware on my end. The issue dragged on for another couple of weeks and rendered any video streaming and gaming useless, even VoIP was affected. Good connection during the day (testing 30Mbps down / 6 Mbps upstream):Дў 10 ms 14 ms 16 ms. ДЈ 23 ms 16 ms 10 ms. Д¤ 18 ms 18 ms 20 ms. ДҐ 47 ms 25 ms 20 ms. Д¦ 33 ms 39 ms 49 ms. Д§ 46 ms 42 ms 43 ms. Д© 47 ms 58 ms 50 ms. ДЎ0 44 ms 50 ms 45 ms. ДЎ1 55 ms 46 ms 47 ms ДЄs you can see, the difference is night and day, literally (some pun intended).

That is where the issues start (huge lag spikes). Note the bold 50.159.241.1 IP address in the second hop, I refer to it as the 'bad' node below. Bellow are a couple of actual example traces to illustrate the obvious issue.Д«ad connection example at peak times (speedtest: 3.5Mbps down / 1 Mbps up): The tech was knowledgeable, I was able to show him the traceroutes, but my internet problems continued. Signal levels at the modem were very good throughout this whole process, there was nothing marginal. I couldn't convince anyone at Comcast even for a millisecond that there is possibly a problem at their end, something was wrong at their node ? I couldn't convince anyone to even look at the traces at this point.ДЄfter jumping through a few hoops, a tech came out to the house, signal levels looked ok, but he did find a somewhat problematic fiber tap on the street and moved me to another leg.

Comcast level 1 hop Pc#

I did the 'reboot modem' dance a dozen times, I had to unplug my NAT router and use a client PC directly, I listened to 'we don't detect a problem on our end', there is 'no issue in the area', 'your modem is bad and needs to be replaced', and my favorite: 'your cable modem is not supported' (I do have a retail-bought Motorola/Arris SB6141 that is actually DOCSIS 3.1 compliant and on the Comcast recommended list). It was happening every day between ~5pm and midnight.Д¬alling Comcast every day lead me through the usual mindless maze of low-level support tech recipes (even though my modem signal levels were great). I was experiencing terrible speed and latency spikes in peak hours (900+ milliseconds to the first/second hop), as well as speed drops down from ~30 to 3-4Mbps downstream, and from 6Mbps to ~0.3Mbps upstream. A day or two later I noticed my worry-free internet was turning into a nightmare.

Comcast level 1 hop tv#

I had to call the cable company to change some TV package, and we had to reboot/reprovision the modem as well. I was enjoying a great, stable internet connection from Comcast, with the fiber running at the street about 30 feet from my house, with a strong clean signal to my SB6141 modem.