Push monitors with long intervals (>24h) fail to detect DOWN status #4670

Open
opened 2026-02-28 04:11:09 -05:00 by deekerman · 0 comments
Owner

Originally created by @trudslev on GitHub (Feb 5, 2026).

Push monitors with long intervals (>24h) fail to detect DOWN status

🛡️ Security Policy

📝 Description

Push monitors with intervals longer than ~24 hours never transition to DOWN state, even after the configured timeout has long passed. The monitor stays UP indefinitely.

👟 Reproduction steps

  1. Create a push monitor with 30-hour interval (108000 seconds)
  2. Send one push to make it UP (green)
  3. Wait >30 hours without sending another push
  4. Observe: Monitor stays UP indefinitely

👀 Expected behavior

Monitor should transition to DOWN (red) after 30 hours without receiving a push.

😓 Actual Behavior

Monitor stays UP (green) forever, never triggering DOWN notifications.

🐻 Uptime-Kuma Version

2.0.0 or 2.0.2 or 2.1.0-beta.3

💻 Operating System and Arch

Linux tanis 6.8.0-94-generic #96-Ubuntu SMP PREEMPT_DYNAMIC Fri Jan 9 20:36:55 UTC 2026 x86_64 x86_64 x86_64 GNU/Linux

🌐 Browser

Brave 1.86.142 (Official Build) (arm64)

🖥️ Deployment Environment

  • Runtime Environment:
    • Docker: Version 27.5.1 (Build 27.5.1-0ubuntu3~24.04.2)
    • Docker Compose: Version 2.37.1
  • Database:
    • SQLite: Embedded
  • Database Storage:
    • Filesystem:
      • Linux: ext4
    • Storage Medium: SSD
  • Uptime Kuma Setup:
    • Number of monitors: 75

📝 Relevant log output


Originally created by @trudslev on GitHub (Feb 5, 2026). ### 📑 I have found these related issues/pull requests Push monitors with long intervals (>24h) fail to detect DOWN status ### 🛡️ Security Policy - [x] I have read and agree to Uptime Kuma's [Security Policy](https://github.com/louislam/uptime-kuma/security/policy). ### 📝 Description Push monitors with intervals longer than ~24 hours never transition to DOWN state, even after the configured timeout has long passed. The monitor stays UP indefinitely. ### 👟 Reproduction steps 1. Create a push monitor with 30-hour interval (108000 seconds) 2. Send one push to make it UP (green) 3. Wait >30 hours without sending another push 4. Observe: Monitor stays UP indefinitely ### 👀 Expected behavior Monitor should transition to DOWN (red) after 30 hours without receiving a push. ### 😓 Actual Behavior Monitor stays UP (green) forever, never triggering DOWN notifications. ### 🐻 Uptime-Kuma Version 2.0.0 or 2.0.2 or 2.1.0-beta.3 ### 💻 Operating System and Arch Linux tanis 6.8.0-94-generic #96-Ubuntu SMP PREEMPT_DYNAMIC Fri Jan 9 20:36:55 UTC 2026 x86_64 x86_64 x86_64 GNU/Linux ### 🌐 Browser Brave 1.86.142 (Official Build) (arm64) ### 🖥️ Deployment Environment - **Runtime Environment**: - Docker: Version `27.5.1` (Build `27.5.1-0ubuntu3~24.04.2`) - Docker Compose: Version `2.37.1` - **Database**: - SQLite: Embedded - **Database Storage**: - **Filesystem**: - Linux: ext4 - **Storage Medium**: SSD - **Uptime Kuma Setup**: - Number of monitors: 75 ### 📝 Relevant log output ```bash session ```
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/uptime-kuma#4670
No description provided.