My internet (and as a result my phone too) seems to drop out many times a day. This problem started a few weeks ago. I've already swapped out my modem but it doesn't seem to be getting any better. Note that I don't have to do anything to fix it, it just seems to come back on its own. Also note that I've used the xfinity site to 'troubleshoot' and it reboots the modem but it doesn't seem to make any permanent improvement.
Check out the attached ping plot to comcast.net.
Here is information from my modem:
Please post the balance of the downstream channels.
And those log entries are unhelpful as they are the router component's events, not the modem portion's RF error / event log entries.
Also, I'm not sure if this helps but figured I'd mention it. There are times when I ping a site I get an ipv6 reply, and other times I get a ipv4 reply. (to the SAME site, for example, google).
Here's the pingplot to google overnight.
Can't see your pics. Since you are a new poster, they likely need to be approved by a Forum Admin. Or you may need to make a minimum number of posts.
You could try hosting them at one of those free third-party pic hosting sites and post the link to them here.
I have Comcast coming out on Monday to take a look. After I got past the initial customer support person (who didn't know anything and we got into a fight), the 2nd level person indicated she saw something wrong with the line and thought it made sense to send someone out. (I think the fact that I lose my VOIP at the same time as internet proves it has nothing to do with my router, etc.)
The downstream's are o/k. You didn't post the upstream power levels.
See what the tech has to say. Good luck with it ! Please post back with how things turn out.
The upstream is linked in my original post.
It's good !
Yeah. So I guess we'll see what the tech says. The fact that the 2nd level support person quickly indicated that 'yes, there is a line issue' (though couldn't tell me where in terms of it being close to my house or not) is at least comforting.
Is there possible correlation between my connectivity issues and these logs?
|All logs from Last Week|
|FW.IPv6 FORWARD drop , 26 Attempts, 2019/2/17 06:45:47||Firewall Blocked|
|FW.IPv6 INPUT drop , 14 Attempts, 2019/2/17 06:44:59||Firewall Blocked|
|FW.WANATTACK DROP , 5 Attempts, 2019/2/17 02:09:47||Firewall Blocked|
|FW.IPv6 INPUT drop , 14 Attempts, 2019/2/16 14:04:44||Firewall Blocked|
This sounds like more of a signal / connection quality impairment as your phone service is also affected.
As an FYI, there are other signal stat figures that can't be read by the modem. They are the "Upstream Rx Power" (Upstream Receive Power Level), the "Upstream SNR Ch." (Upstream Signal To Noise Ratio), and the "Upstream ICFR" (In Channel Frequency Response). These are as equally important in diagnosing connectivity issues as are the modem's stats. These values can only be read from their end by them polling the CMTS / system at the headend.
So this got pretty interesting.
So the tech came out and couldn't find anything conclusive. He replaced the splitter because they now use a newer model. He suggested that it might be my internal wiring (which didn't make sense to me because I always remained connected to the other computers in the house - had pings going all the time, etc). I also believed it didn't make sense because the phone was going out too - which obviously didn't have anything to do with my ethernet wiring.
Literally about 5 minutes after he left, the internet went out again.
I tried thinking back to see if there was anything that I had done recently to my network that may have affected it because I was out of options.
Turns out I had added an additional switch recently - https://www.monoprice.com/product?c_id=105&cp_id=10521&cs_id=1052104&p_id=15762&seq=1&format=2 . While I have the 8 port version of this switch in 2 places in the house for years, I had recently added this 5 port switch as well.
Once I removed that switch, so far (fingers crossed) everything has been fine. Although I'm not completely sure of the logic, it seems that having this switch at some point causes the modem to reboot? Does this sound remotely logical?
Pinging comcast.net [22.214.171.124] with 32 bytes of data: Reply from 126.96.36.199: bytes=32 time=373ms TTL=57 Request timed out. Request timed out. Reply from 188.8.131.52: bytes=32 time=247ms TTL=57 Request timed out. Request timed out. Request timed out. Reply from 184.108.40.206: bytes=32 time=772ms TTL=57 Request timed out. Reply from 220.127.116.11: bytes=32 time=241ms TTL=57 Request timed out. Request timed out. Reply from 18.104.22.168: bytes=32 time=591ms TTL=57 Request timed out. Reply from 22.214.171.124: bytes=32 time=644ms TTL=57 Request timed out. Request timed out. Reply from 126.96.36.199: bytes=32 time=345ms TTL=57 Request timed out. Reply from 188.8.131.52: bytes=32 time=298ms TTL=57 Request timed out. Reply from 184.108.40.206: bytes=32 time=381ms TTL=57 Request timed out. Reply from 220.127.116.11: bytes=32 time=486ms TTL=57 Request timed out. Reply from 18.104.22.168: bytes=32 time=258ms TTL=57 Request timed out. Reply from 22.214.171.124: bytes=32 time=312ms TTL=57 Request timed out. Request timed out. Reply from 126.96.36.199: bytes=32 time=173ms TTL=57 Request timed out. Reply from 188.8.131.52: bytes=32 time=185ms TTL=57 Ping statistics for 184.108.40.206: Packets: Sent = 33, Received = 14, Lost = 19 (57% loss), Approximate round trip times in milli-seconds: Minimum = 173ms, Maximum = 772ms, Average = 379ms
C:\Users\Dan>tracert comcast.net Tracing route to comcast.net [220.127.116.11] over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms testwifi.here [192.168.86.1]
2 * 185 ms 166 ms 18.104.22.168
3 169 ms 155 ms 201 ms 22.214.171.124
4 202 ms 143 ms 109 ms 126.96.36.199
5 175 ms * 196 ms be-98-ar03.plainfield.nj.panjde.comcast.net [188.8.131.52]
6 * * 263 ms be-800-ar03.ivyland.pa.panjde.comcast.net [184.108.40.206]
7 271 ms 292 ms 494 ms ae100-ur12-d.newcastlerdc.de.panjde.comcast.net [220.127.116.11]
8 232 ms * 243 ms urlrw01.cable.comcast.com [18.104.22.168]
Post the requested info from here;