64 bytes from sea09s29-in-f14.1e100.net (142.250.217.78): icmp_seq=20 ttl=117 time=35.7 ms64 bytes from sea09s29-in-f14.1e100.net (142.250.217.78): icmp_seq=21 ttl=117 time=33.8 ms64 bytes from sea09s29-in-f14.1e100.net (142.250.217.78): icmp_seq=22 ttl=117 time=36.1 ms64 bytes from sea09s29-in-f14.1e100.net (142.250.217.78): icmp_seq=23 ttl=117 time=36.0 ms64 bytes from sea09s29-in-f14.1e100.net (142.250.217.78): icmp_seq=24 ttl=117 time=1141 ms64 bytes from sea09s29-in-f14.1e100.net (142.250.217.78): icmp_seq=25 ttl=117 time=87.0 ms64 bytes from sea09s29-in-f14.1e100.net (142.250.217.78): icmp_seq=26 ttl=117 time=41.6 ms64 bytes from sea09s29-in-f14.1e100.net (142.250.217.78): icmp_seq=27 ttl=117 time=34.5 ms64 bytes from sea09s29-in-f14.1e100.net (142.250.217.78): icmp_seq=28 ttl=117 time=523 ms
Hi,I am just going to think out loud some ideas to find out more about the issue... Apologies if you have already done all this testing.Does the issue happen almost consistently when pinging different servers?
Have you tried connecting the PC directly to OPNsense to see if the issue persist? (since you said there is a switch in the middle).Do you experience the same from the router itself? Try to do a ping (with a large count) from OPNsense "Interfaces - Diagnostics - Ping" and see what you get.