Slow Internet Speed Due to Sys-Net

Today I noticed that my internet is slow. I ran some speed tests. Instead of 100, I’m only getting about 10 Mbps.
I’ve ruled out all possible sources of error.
I restarted the router.
I restarted sys-firewall and sys-net.
I measured the speed using another computer. Everything is fine there.
I switched the router ports.
I also ran a speed test on sys-net. The problem exists directly on sys-net as well.

Where can I look for more information?

I saw with ip -s link show that there are a lot of dropped and missed entries.

2: ens6: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP mode DEFAULT group default qlen 1000
    link/ether 08:bf:b8:19:a0:2e brd ff:ff:ff:ff:ff:ff
    RX:  bytes packets errors dropped  missed   mcast           
     226526543  305508      0    8818   18706      94 
    TX:  bytes packets errors dropped carrier collsns           
     253238759  160882      0      15       0       0 
    altname enp0s6
    altname enx08bfb819a02e

Is that normal?

I put the host into suspended mode and then brought it back online. Now the internet speed is working again.
How can I figure out what caused this?
Which log files should I check?

ip -s link show shows 0 again for missed. Only dropped is not 0. But that doesn’t seem to have any effect.

5: ens6: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP mode DEFAULT group default qlen 1000
    link/ether 08:bf:b8:19:a0:2e brd ff:ff:ff:ff:ff:ff
    RX:  bytes packets errors dropped  missed   mcast           
     394038875  330130      0    1822       0      18 
    TX:  bytes packets errors dropped carrier collsns           
     164892061  144780      0       0       0       0 
    altname enp0s6
    altname enx08bfb819a02e

Could it be your network adapter doing strange things?

Perhaps use something like ethtool to check/control its connection speed. You can also see “Speed” in connection information - right click the NetworkManager Applet icon.

@qubist Thanks!
Everything looks fine in ethtool. But since the problem no longer exists, that’s obviously no longer relevant.

If I run into this problem again, I’ll hopefully check ethtool right away.