Choose your cart
Choose your cart
Receive up to $504 promo credit ($180 w/Welcome Unlimited, $360 w/ 5G Start, or $504 w/5G Do More, 5G Play More, 5G Get More or One Unlimited for iPhone plan (Welcome Unlimited and One Unlimited for iPhone plans can't be mixed w/other Unlimited plans; all lines on the account req'd on respective plans)) when you add a new smartphone line with your own 4G/5G smartphone on an eligible postpaid plan between 2/10/23 and 4/5/23. Promo credit applied over 36 months; promo credits end if eligibility requirements are no longer met.
$699.99 (128 GB only) device payment purchase or full retail purchase w/ new smartphone line on One Unlimited for iPhone (all lines on account req'd on plan), 5G Start, 5G Do More, 5G Play More or 5G Get More plan req'd. Less $699.99 promo credit applied over 36 mos.; promo credit ends if eligibility req’s are no longer met; 0% APR.
The past week or so I've experieced 5% packet loss, which is causing all sorts of glitches in games. This behavior has persisted, despite resetting the FiOS modem a couple of times. Here's a screenshot of PingPlotter running pings every 2.5s to 4.2.2.1 (Level 3 DNS server). You can see the pkt loss is bad, and there is significant jitter.
The hops along the way show that the biggest offender is "lo0-100.washdc-vfttp-316.verizon-gni.net" - some piece of FiOS equipment, I am presuming by the name. Anyone else in the Germantown MD area have trouble? Not sure how to get this resolved. I guess call in CS and wait in the queue like everyone else. 😞
Solved! Go to Correct Answer
Just as a comparison, here's the PingPlotter (5.5.4.3687) graph that I get. I think we are geographically & network topographically (made the word up) close, so this is probably valid.
As discussed in the past. those middle hops with packet loss mean absolutely nothing. The servers in question are set to respond at very low priority to the Pings envolved.
There is something strange in your getting slow response to 192.168.1.1 (i.e. your own router). These are usually <1 ms response and no packet loss.
Thanks for the response. I wasn't aware of the response priority issue, so that's a good data point. These pings were done over the WiFi (albeit within a couple of feet of the router). My next step will be to plug directly into the Ethernet and see what happens.
Just as a comparison, here's the PingPlotter (5.5.4.3687) graph that I get. I think we are geographically & network topographically (made the word up) close, so this is probably valid.