Uptime-Kuma causing ping floods #3394

New issue

Closed

opened 2026-02-28 03:27:58 -05:00 by deekerman · 0 comments

deekerman commented

2026-02-28 03:27:58 -05:00

Owner

Originally created by @MAMedici on GitHub (Jun 7, 2024).

⚠️ Please verify that this question has NOT been raised before.

I checked and didn't find similar issue

🛡️ Security Policy

I agree to have read this project Security Policy

📝 Describe your problem

I've had problems with uptime-kuma triggering IPS blocks due to excessive/abusive traffic. This latest incident I was able to talk to a network engineer who sent me the logs, Looking at the logs I see my IP is pinging them almost every second, instead of 300s as configured in uptime-kuma for this host.

I ran a packet capture on my firewall and indeed see that uptime-kuma is flooding several hosts with unexpectedly-high ICMP traffic.

I double-checked my site and general configuration settings, and everything loose as it should. Most of my entries are set for 5m (300s).

Any idea what might be causing this and how to make it act as expected? This is Uptime-Kuma 1.23.13 on docker 26.10 on a Debian 12 container on Proxmox. Nothing noteworthy appears in the Uptime-Kuma logs. Firewall logs and capture attached.

📝 Error Message(s) or Log

uptime-kuma ping capture.txt

🐻 Uptime-Kuma Version

1.23.13

💻 Operating System and Arch

Debian 12/Linux 6.5.13-5-pve/amd64

🌐 Browser

Firefox 126.0.1

🖥️ Deployment Environment

Runtime: Docker 26.10
Host: lxc Virtualization running Debian GNU/Linux 12 (bookworm) Linux 6.5.13-5-pve
Architecture: x86-64
Database: sqlite
Filesystem used to store the database on:
number of monitors:

Originally created by @MAMedici on GitHub (Jun 7, 2024). ### ⚠️ Please verify that this question has NOT been raised before. - [X] I checked and didn't find similar issue ### 🛡️ Security Policy - [X] I agree to have read this project [Security Policy](https://github.com/louislam/uptime-kuma/security/policy) ### 📝 Describe your problem I've had problems with uptime-kuma triggering IPS blocks due to excessive/abusive traffic. This latest incident I was able to talk to a network engineer who sent me the logs, Looking at the logs I see my IP is pinging them almost every second, instead of 300s as configured in uptime-kuma for this host. I ran a packet capture on my firewall and indeed see that uptime-kuma is flooding several hosts with unexpectedly-high ICMP traffic. I double-checked my site and general configuration settings, and everything loose as it should. Most of my entries are set for 5m (300s). Any idea what might be causing this and how to make it act as expected? This is Uptime-Kuma 1.23.13 on docker 26.10 on a Debian 12 container on Proxmox. Nothing noteworthy appears in the Uptime-Kuma logs. Firewall logs and capture attached. ### 📝 Error Message(s) or Log [uptime-kuma ping capture.txt](https://github.com/user-attachments/files/15744821/uptime-kuma.ping.capture.txt) ### 🐻 Uptime-Kuma Version 1.23.13 ### 💻 Operating System and Arch Debian 12/Linux 6.5.13-5-pve/amd64 ### 🌐 Browser Firefox 126.0.1 ### 🖥️ Deployment Environment Runtime: Docker 26.10 Host: lxc Virtualization running Debian GNU/Linux 12 (bookworm) Linux 6.5.13-5-pve Architecture: x86-64 Database: sqlite Filesystem used to store the database on: number of monitors: