100% packet loss on iP 74.125.50.214

i've noticed heavy lag and skipping issues when playing online shooters. Computer works fine offline. Started about a month ago and has been getting worse and is now unplayable. Checked out my pingpath and it shows 100% packet loss always stopping at the same IP. i've also attached a picture of my Pathplotter program. It shows the same issue.  Would this cause my constant frame skipping?  it happens with both wifi and direct connections.

 

Computing statistics for 225 seconds... Source to Here This Node/Link Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address 0

Stormtrooper [192.168.1.5] 0/ 100 = 0% | 1 2ms 0/ 100 = 0% 0/ 100 = 0% 192.168.1.1 0/ 100 = 0% | 2 17ms 0/ 100 = 0% 0/ 100 = 0%

mta-70-123-32-1.hot.rr.com [70.123.32.1] 0/ 100 = 0% | 3 25ms 0/ 100 = 0% 0/ 100 = 0%

tge0-0-12.ausgtxlg01h.texas.rr.com [66.68.4.57] 0/ 100 = 0% | 4 17ms 0/ 100 = 0% 0/ 100 = 0%

agg22.ausutxla01r.texas.rr.com [24.175.43.211] 1/ 100 = 1% | 5 26ms 1/ 100 = 1% 0/ 100 = 0%

agg22.dllatxl301r.texas.rr.com [24.175.41.46] 0/ 100 = 0% | 6 25ms 1/ 100 = 1% 0/ 100 = 0% 66.109.1.216 0/ 100 = 0% | 7 41ms 1/ 100 = 1% 0/ 100 = 0%

66.109.5.121 0/ 100 = 0% | 8 25ms 1/ 100 = 1% 0/ 100 = 0%

ix-ae-52-0.tcore2.dt8-dallas.as6453.net [66.110.57.162] 99/ 100 = 99%

| 9 --- 100/ 100 =100% 0/ 100 = 0% 74.125.50.214 Trace complete.

 

packet loss.jpg

 

2 REPLIES 2
Proven Sharer

Re: 100% packet loss on iP 74.125.50.214

If users would just spend a few minutes learning to use WHOIS in addition to Pathplotter, they could quickly find that the IP addresses 74.125.50.214 and also 108.170.230.108 appearing in your Pathplotter listing as Hop #10 both belong to Google LLC, not Spectrum.  Posting your issue here won't get the attention of the networking company shown to be at fault.

Sharer

Re: 100% packet loss on iP 74.125.50.214

Also... not "losing packets" at the rate those hops are likely electing not to respond to the ICMP ECHO. If you were dropping packets at those rates, 100% of your 601 packets would not be making it to the last hop with latency as low as you see there... there would at least be some heavy spikes here and there before they got dropped. Since they are all making it there in reasonable time, it looks like they are forwarding those small packets just fine.

What you see there are points in Google' s networks that are taking on heavy loads, so Google may need their traffic distributed a bit better.

Not much Spectrum can do about that.

What SHOULD be setting off a red flag for you is the spike over 300ms before you leave Texas. As close as that is to your CPE... you may have a localized signal issue that techs may be able to address.

Take a good look at your modem' s signal page and logs for high error rates, low SNR and/or signal levels on downstream, high signal levels on upstream.