F5F Stay Refreshed Power Users Networks Network rules and security settings can influence ping performance.

Network rules and security settings can influence ping performance.

Network rules and security settings can influence ping performance.

Pages (2): 1 2 Next
B
Beutelwookie
Member
112
08-22-2025, 12:42 PM
#1
I've organized a smart-home setup with a Netgear CM500 modem, Edgemax-X router, and additional Unifi access points. After familiarizing myself with the interface and setting up firewall rules, I'm facing internet problems. It seems the firewall isn't the issue since connections work fine for all networks. The settings appear standard, but ISP speeds are slow—around 230mbps download and 7mbps upload. Ping times range from 6 to 3800ms, which is problematic for calls or streaming. Basic browsing is slow too. I've tried various fixes: enabling hardware offloading, ensuring wired connections are CAT6-1000, isolating devices, and resetting the router. Still, ping stays over 500ms regularly. It feels like throttling is happening, especially with many users online. I'm wondering if a DoS attack might be the cause and need guidance on how to investigate further.
B
Beutelwookie
08-22-2025, 12:42 PM #1

I've organized a smart-home setup with a Netgear CM500 modem, Edgemax-X router, and additional Unifi access points. After familiarizing myself with the interface and setting up firewall rules, I'm facing internet problems. It seems the firewall isn't the issue since connections work fine for all networks. The settings appear standard, but ISP speeds are slow—around 230mbps download and 7mbps upload. Ping times range from 6 to 3800ms, which is problematic for calls or streaming. Basic browsing is slow too. I've tried various fixes: enabling hardware offloading, ensuring wired connections are CAT6-1000, isolating devices, and resetting the router. Still, ping stays over 500ms regularly. It feels like throttling is happening, especially with many users online. I'm wondering if a DoS attack might be the cause and need guidance on how to investigate further.

M
MarissaGames
Member
216
08-30-2025, 01:30 AM
#2
Run a trace route to a DNS server like Google's and observe the ping across each hop. This may indicate an issue beyond your local network.
M
MarissaGames
08-30-2025, 01:30 AM #2

Run a trace route to a DNS server like Google's and observe the ping across each hop. This may indicate an issue beyond your local network.

P
PewTie
Member
74
09-05-2025, 06:42 PM
#3
We have all public IP addresses available. What we actually require is a traceroute from a private IP to a public IP, allowing us to observe each connection point through the PC, router, firewall, and modem. On Windows, this can be accomplished by entering "tracert IP" in the command line. It’s unclear how to perform this in Linux. Alternatively, you can test individual IP addresses within your network and check the ping results. In this approach, try reaching out to all devices between your PC and the internet—such as routers, firewalls, modems, and access points.
P
PewTie
09-05-2025, 06:42 PM #3

We have all public IP addresses available. What we actually require is a traceroute from a private IP to a public IP, allowing us to observe each connection point through the PC, router, firewall, and modem. On Windows, this can be accomplished by entering "tracert IP" in the command line. It’s unclear how to perform this in Linux. Alternatively, you can test individual IP addresses within your network and check the ping results. In this approach, try reaching out to all devices between your PC and the internet—such as routers, firewalls, modems, and access points.

S
Skythekid1526
Junior Member
17
09-09-2025, 09:32 AM
#4
I'm working on a Mac and can utilize the built-in network tools.
S
Skythekid1526
09-09-2025, 09:32 AM #4

I'm working on a Mac and can utilize the built-in network tools.

K
kevin2010
Member
108
09-09-2025, 11:34 PM
#5
One thing is for certain now; you have an internal network issue. 10.10.10.1 is most likely your router/modem and it should not take almost 2.4 seconds to reach that. Edit: I read that wrong. It's 2.4ms. See below...
K
kevin2010
09-09-2025, 11:34 PM #5

One thing is for certain now; you have an internal network issue. 10.10.10.1 is most likely your router/modem and it should not take almost 2.4 seconds to reach that. Edit: I read that wrong. It's 2.4ms. See below...

C
Crohnsy
Member
58
09-09-2025, 11:43 PM
#6
I believe the timing is 2.4 milliseconds, not 2,400 milliseconds.
C
Crohnsy
09-09-2025, 11:43 PM #6

I believe the timing is 2.4 milliseconds, not 2,400 milliseconds.

X
xISplex
Member
221
09-13-2025, 08:46 PM
#7
My router is connected but it displays a delay of just 1 to 3 milliseconds. The route to 96.120.89.33 is slow, taking more than 800 milliseconds and up to 4.5 seconds.
X
xISplex
09-13-2025, 08:46 PM #7

My router is connected but it displays a delay of just 1 to 3 milliseconds. The route to 96.120.89.33 is slow, taking more than 800 milliseconds and up to 4.5 seconds.

R
Roe56
Member
102
09-13-2025, 10:30 PM
#8
Have you turned off the Netgear modem? I noticed you only talked about resetting the router, but I wanted to double-check.
R
Roe56
09-13-2025, 10:30 PM #8

Have you turned off the Netgear modem? I noticed you only talked about resetting the router, but I wanted to double-check.

J
JustClappy
Junior Member
35
09-14-2025, 03:35 PM
#9
I've experienced this a few times, and it returns to normal (under 30ms latency) for roughly an hour before resuming. I acknowledge the modem heats up when not in an air-conditioned space, but with an IR camera I can confirm it never exceeds 45°C. I've also verified the modem is running the latest firmware, after confirming with my ISP over the phone to update it.
J
JustClappy
09-14-2025, 03:35 PM #9

I've experienced this a few times, and it returns to normal (under 30ms latency) for roughly an hour before resuming. I acknowledge the modem heats up when not in an air-conditioned space, but with an IR camera I can confirm it never exceeds 45°C. I've also verified the modem is running the latest firmware, after confirming with my ISP over the phone to update it.

B
balaey1
Junior Member
35
09-16-2025, 10:40 AM
#10
Typically, temperatures above 50-60°C cause problems. If rebooting the modem helps temporarily, it might point to a line or ISP issue because the signal takes a long time to reach their first hop.
B
balaey1
09-16-2025, 10:40 AM #10

Typically, temperatures above 50-60°C cause problems. If rebooting the modem helps temporarily, it might point to a line or ISP issue because the signal takes a long time to reach their first hop.

Pages (2): 1 2 Next