Hi @MikeyG23 

Thanks for posting in our business forum.
If you have not changed anything recently, or ever since it was set up, that could be your ISP getting unstable recently.

If the bad packet is referring to the one from the EAP, you should post this on the EAP page. Not the router.

You should test more on the modem before concluding the problem is on the router.

Hi @MikeyG23 

Thanks for posting in our business forum.
Start from the most basic steps:

1. Check if there is a network subnet conflict.

2. Run a 3ft cable from the modem to the router WAN.

3. Examine your DNS.

4. Follow this guide and use ping to test your local host to the gateway latency. See if you have any loss or high latency.

If you need me to see through your case, please upload your screenshots of the ping results.

Please mosaic your sensitive information. Here is a list of information considered sensitive:

1. Public IP address on your WAN if your WAN is.

2. Real MAC address of your device.

3. Your personal information including address, domain name, and credentials.

For troubleshooting purposes, when a WAN IP is needed, please leave some values visible for identification.

Hi @MikeyG23 

Thanks for posting in our business forum.

MikeyG23 wrote

  @Clive_A Thank you for the information and the guide - really helpful.

 

So internal ping shows some variation, although not too bad;

 

Ping statistics for 192.168.0.1:
    Packets: Sent = 77, Received = 77, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 1ms, Maximum = 46ms, Average = 4ms
Control-C
^C

 

 

External ping has packet loss;

 

Ping statistics for 8.8.8.8:
    Packets: Sent = 84, Received = 78, Lost = 6 (7% loss),
Approximate round trip times in milli-seconds:
    Minimum = 3ms, Maximum = 37ms, Average = 5ms
Control-C

 

I then did the next command and found the following; does this mean my IP is not what I thought, 212.132.198.244 but in fact 212.132.198.129?

 

C:\Users\MichaelGarrettG>tracert -w 300 bingcom

Tracing route to bingcom [13.107.21.200]
over a maximum of 30 hops:

  1    11 ms     1 ms     1 ms  192.168.0.1
  2     4 ms     4 ms     3 ms  212.132.198.129
  3     *        5 ms     *     100.127.0.191
  4     4 ms     4 ms     3 ms  lag-1010acc1clalonnetworkas201838net [94.177.138.32]
  5     6 ms     3 ms     3 ms  100.127.64.2
  6     4 ms     3 ms     3 ms  igblmdistc7504ukmsftnet [195.66.224.140]
  7     5 ms     4 ms     4 ms  13.104.187.48
  8     *        *        *     Request timed out.
  9     *        *        *     Request timed out.
 10     *        *        *     Request timed out.
 11     *        *        *     Request timed out.
 12     4 ms     4 ms     4 ms  13.107.21.200

Trace complete.

 

 

About the tracert and why it is not sending to your IP, you should look this up on Google. Google has a better explanation than me. This should be found in Windows official docs about CMD. So, I will not bother explaining this.

In your local network, it should not fluctuate that badly. Avg should be around 1-2 ms because it is a local network.

I'd recommend you check your Ethernet cable. Very likely to be a bad cable. You should check the cables from your router to the PC. Every cable matters.

Second, you should check if you have any loops. It also matters because the local ping to the gateway is not gonna be that high. Loop may be another cause.

Third, high bandwidth-consuming devices may be the perp, too. Check if you have anything using the huge bandwidth in your network.