Home Networking

198 readers

1 users here now

A community to help people learn, install, set up or troubleshoot their home network equipment and solutions.

Rules

Please stay on topic.
Please use the search function to look for keywords related to what you want to ask before posting since most common issues have been answered.
No Ads. This community is for support and discussion. Ads and self promotion are not welcome here.
No product reviews or announcements. If you have a question about a product, be specific about what you want to know.
Be civil. Don't be a jerk. Not being a jerk is surprisingly easy.
No URL shorteners. URL shorteners tend to hide the real use of a link. For this reason, please use normal links, even if they're long.
No affiliate links.
No gatekeeping. With profession shall come professionalism. Extend help without judging others for their ignorance. The same goes for downvoting of comments or posts for "stupid questions" or not being as knowledgeable as others.

founded 1 year ago

MODERATORS

[email protected]

100% packet loss on last hop to ISP (alien.top)

submitted 11 months ago by [email protected] to c/[email protected]

3 comments fedilink hide all child comments

We have issues with rubber-banding in games and sudden spikes in Ping. Often games will kick us. Anything requiring constant connection will lose it multiple times during the day. Speed can still register at or above what we pay for (50 Mbps) but can also fluctuate wildly. We have around 9 devices (including Chromecast and iPhones etc) connected but not all in active use at once.

In trying to get the ISP to help they requested every kind of ping plotter and trace route I can provide. Ping plotter shows a 100% packet loss at the last hop to the ISP. Could this be the reason for our issues? I have tried to get them to explain how this is OK but as yet nothing. The technical team has has said there’s no issue and nothing to fix.

This is a recent example of a command prompt ping (I manually stopped it as it otherwise runs non-stop):

PING iinet.net.au (52.64.91.12): 56 data bytes Request timeout for icmp_seq 0 Request timeout for icmp_seq 1 Request timeout for icmp_seq 2 Request timeout for icmp_seq 3 Request timeout for icmp_seq 4 Request timeout for icmp_seq 5 Request timeout for icmp_seq 6 Request timeout for icmp_seq 7 Request timeout for icmp_seq 8 Request timeout for icmp_seq 9 Request timeout for icmp_seq 10 Request timeout for icmp_seq 11 Request timeout for icmp_seq 12 Request timeout for icmp_seq 13 Request timeout for icmp_seq 14 Request timeout for icmp_seq 15 Request timeout for icmp_seq 16 ^C

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 1 points 11 months ago

I should have mentioned, 1.1.1.1 pings absolutely fine.