Skip to content

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

@trudslev

Description

@trudslev

πŸ“‘ I have found these related issues/pull requests

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions