Constant Latency Variation and Time Nudge

OskooI_007​ Connected to the one satellite on the system. I just gave the Orbi a full reboot and am still having issues.

Sorry to step in oskool hope you dont mind.

NameWasWayTooLon​  

Verify orbi firmware is up to date, verify QOS settings are on. It may be called SQM on orbi.

It could just be degradation of the orbi mesh.

Firmware updates also adjust the rf power to antennas to increase lifespan of the device or resolve heat issues which could be the case as well. They also do this on the fly which could cause some latency spikes. 

As oskool asked, he was leading towards; if you are connected via ethernet to a satellite orbi you are still relying on 6ghz wireless in the connection chain. You could improve the quality of connection by connecting ethernet to gateway orbi(the orbi connected to your modem). I know this is not easy and requires installation of an ethernet from den to office though, and is not always feasible on your own. 

TheRugDealer34​

Number of hops seems high to me at 15 although if your passing from country to country then this could be normal. The packet loss along the route is worth questioning. This may be a ISP routing issue. IP lookup the addresses with loss and see who owns them, nothing along the route should be private. 

Hey Trichomecookin,

This is an RBR750 mesh system so no QOS settings. Just sets it automatically. Firmware is up to date on satellite and router. I can try hardwiring into the router and see if problems persist. Will have to order an XL ethernet cord to get here after the holidays.

NameWasWayTooLon​ 

Ahh I see, and understood.

This is the last optimization that can be done on your end. Mesh systems are the greatest wifi invention of the last decade, especially for streaming media and with the End Of Life for cable tv across the country(assuming you're US based) they are 100% necessary imo, but still can be a weak point in the flow for gaming. I hope this helps and isn't too intrusive for you.  Best wishes!  

Trichomecookin​ I welcome the help! I don't notice any packet loss on my home router with PingPlotter running on Win11 version 25H2.

PingPlotter starts off by running a traceroute and then switches to pinging all the IP addresses.

Now that you understand how traceroute works, we can talk about how PingPlotter works. When you first start a trace in PingPlotter, it initiates a traceroute so that it can find all of the hops between the computer and the intended target. Once it finds all of those hops, PingPlotter starts pinging each of those hops every 2.5 seconds. Every so often it will run another traceroute to see if the route to the final destination has changed.

https://www.pingman.com/kb/article/traceroute-vs-pingplotter-160.html

NameWasWayTooLon​ having the PC connected to a satellite means the satellite is acting as the PC's wifi network card. I would try connecting the PC directly to the router like Trichomecookin recommended and see of that fixes the ping spikes.

The best way to deploy a wifi mesh network is to have each satellite connected to the router with ethernet cables. That way each satellite has a wired backhaul connection to the router which doubles the satellite's wireless speed.

Of course having a wired connection is inconvenient in most circumstances, but it does boost performance greatly.

OskooI_007​ That makes sense. Going to order some MOCA adapters, a filter, and a splitter and get that set up. Moved the satellite to a more elevated position and that seems to have cleared up a decent amount. Ran another Ping Plotter test and am seeing 75% packet loss at a Comcast server(?) I believe. https://share.pingplotter.com/5yMDnfiZEKR

NameWasWayTooLon​ the ping times look much better. Not as many ping spikes.

Hop 8 shows packet loss but hop 9 doesn't show any packet loss.

So I wouldn't worry about the packet loss on hop 8 since it's not causing any packet loss on hop 9.

I know I said earlier that low number hops can cause packet loss on high number hops. That's true they can, but it's considered a false reading if it's not affecting higher number hops downstream.

Interesting, if that's how ping plotter works, it seems that the traceroutes go through and display in the "cur" column, but the pings will not. Falsely displaying as packet loss. I'm going to consider this a non issue and not worry about it.