High Ping connecting to 192.168.77.1 on pingplotter post .40 update

[SamT98]

As title, what is causing this issue? everything else is averaging 10-12ms ping but hop 1 is abysmal. is this a known issue?

[SamT98]

just done another test lots of packet loss in hop 3 now and a little in hops 4 and 7. Could this be a BT issue now?

[SamT98]

@Netduma Fraser do you have any idea what’s causing this ?

[Netduma Fraser]

The bottom graph is the most important one which is showing great stability and no packet loss. The creators of PingPlotter say themselves the first few hops can read correctly.

Verify it by pinging google in command prompt for example and it should be stable.

[SamT98]

2 hours ago, Netduma Fraser said:

The bottom graph is the most important one which is showing great stability and no packet loss. The creators of PingPlotter say themselves the first few hops can read correctly.

Verify it by pinging google in command prompt for example and it should be stable.

I’ve just reverted back to .23 and ran a pingplotter test. No issues with hop 1. Re downloaded .40 and ran the test again I’m getting an average of 45.6 ping on hop 1 with 38% packet loss. There’s 100% an issue with this latest update with hop 1. Can you investigate and see what it is? 

[Netduma Fraser]

Here is an article from the creators of PingPlotter regarding what I mentioned: https://www.pingman.com/kb/article/initial-hops-100-packet-loss-6.html

If you ping google in command prompt does it appear stable?