mirror of
https://github.com/louislam/uptime-kuma.git
synced 2026-03-02 22:57:00 -05:00
Push monitors with long intervals (>24h) fail to detect DOWN status #4670
Labels
No labels
A:accessibility
A:api
A:cert-expiry
A:core
A:dashboard
A:deployment
A:documentation
A:domain expiry
A:incidents
A:maintenance
A:metrics
A:monitor
A:notifications
A:reports
A:settings
A:status-page
A:ui/ux
A:user-management
Stale
ai-slop
blocked
blocked-upstream
bug
cannot-reproduce
dependencies
discussion
duplicate
feature-request
feature-request
good first issue
hacktoberfest
help
help wanted
house keeping
invalid
invalid-format
invalid-format
question
releaseblocker 🚨
security
spam
type:enhance-existing
type:new
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/uptime-kuma#4670
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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
📝 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
👀 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
27.5.1(Build27.5.1-0ubuntu3~24.04.2)2.37.1📝 Relevant log output