Packet timeouts at edge routers

Traceroute shows timeouts once packets hit, what appears to be, the edge routers.

So, after 96.110.33.202/96.110.33.206 nothing returned.... after 68.85.176.113 nothing returned.... after 96.110.33.194/96.110.33.198/96.110.33.206 nothing returned.

A traceroute to `youtube.com` will timeout on what appears to be the edge hop, but pick back up the next hop (see image):

Generally, it appears that whenever it hits an edge router, responses time out. This has caused... lots of issues. Things timing out, latency jumping, web pages not fully loading, VPN dropping, etc... For the youtube.com traceroute every router in between returns on a usual day (PITA if you do block ICMP for exposed routers... really).

Normal traffic on network looks fine... it's just once you try leaving the network from any peering point that it starts going haywire. Some peering points are better than others.

Are there any known issues? I've rebooted cable modem and home router just incase there was some stupidity with on network transfer and authenticating instead of just getting connected to the network.

Responses

BruceW

Gold Problem Solver

•

26.3K Messages

2 years ago

Traceroute shows timeouts ...

The trace continues past the timeout at the intermediate hop and reaches the destination, so the timeout is probably not significant. Please see https://www.dslreports.com/faq/14068.

Please be aware that there are 2 kinds of responses in this Forum: Replies and Comments. When you Comment on a post by scrolling down to "Comment on this post here...", I am notified of your response. But if you select Reply, I am NOT notified and may not be aware of your response.

mitharus

Frequent Visitor

•

19 Messages

@BruceW

If you read... I said that it was dependent on the peering point and youtube timed out after the edge router then picked back up. Here's to a reddit.com address which it should reach within 15 hops (if I let it run, it times out all 64 hops).

So, this issue just came up today, and the traceroute weirdness is the only thing I've found. Packet dumps look "pretty" normal (retransmits; some missing ACKs here and there, but from where I tested to "pretty" normal).

Now, if they *ARE* deciding to rate limit ICMP traffic, this is very new. Sure as hell wasn't like that last week when I was needing to debug some traffic. Hell, wasn't like that all of today when some peering points would come back and show the correct hops instead of timing out. Of course ICMP rate limiting doesn't explain at all why youtube videos aren't loading, web pages are timing out loading, etc... So, traffic *is* reaching the destination but it isn't consistent and not all requests are making it, or the response is getting back to me.

(edited)

2 years ago

BruceW

Gold Problem Solver

•

26.3K Messages

2 years ago

... youtube videos aren't loading, web pages are timing out ...

Are you connecting via Wifi or Ethernet? If Wifi, it's best to switch to an Ethernet cable connection if possible for testing. That would allow you to determine whether the problem is the Wifi signal or the link between your modem or gateway and Comcast's network. Network connection problems that affect both Ethernet and Wifi devices are often due to poor coax connections or damaged coax cable, usually in or near your home. Running the cable through a surge protector, a defective splitter, or too many splitters can cause signal problems as well. If there is an amplifier in the line make sure it's getting power.

If you want to troubleshoot this yourself, please see Internet Troubleshooting Tips. If you still need help, please post your Internet plan speed and the following information from your modem or gateway (from http://192.168.100.1 or http://10.0.0.1):

model number
downstream: power levels, SNR (or MER), error counts, and uptime
upstream: power levels
event log, if available (Be sure to remove or blot out any MAC addresses. Forum security processing considers them "personal information" and may prevent the event log from posting if these are present.)

If you can't find the problem or you'd rather have Comcast take care of it and an employee does not respond to your message here, call them at the phone number on your bill or 1-800-Comcast, or use one of the options on https://www.xfinity.com/support/contact-us/. It's not likely they can fix the problem remotely. If not, insist they send a tech out to identify the cause and correct it.

If the tech finds bad coax, splitters, amplifiers, or connections in your home (even if Comcast originally supplied them) you'll probably have to pay for the visit ($70-$100) unless you have their Service Protection Plan ( https://www.xfinity.com/support/articles/service-protection-plan, closed to customers that don't already have it). If the trouble is due to a faulty Comcast rental device or anything outside your home you shouldn't be charged.

Please be aware that there are 2 kinds of responses in this Forum: Replies and Comments. When you Comment on a post by scrolling down to "Comment on this post here...", I am notified of your response. But if you select Reply, I am NOT notified and may not be aware of your response.

Your Home Network

mitharus

Packet timeouts at edge routers

BruceW

Please be aware that there are 2 kinds of responses in this Forum: Replies and Comments. When you Comment on a post by scrolling down to "Comment on this post here...", I am notified of your response. But if you select Reply, I am NOT notified and may not be aware of your response.

mitharus

BruceW

Please be aware that there are 2 kinds of responses in this Forum: Replies and Comments. When you Comment on a post by scrolling down to "Comment on this post here...", I am notified of your response. But if you select Reply, I am NOT notified and may not be aware of your response.

New to the Community?