Uptime groups misstate service health during partial outages
Uptime Kuma users want grouped monitors to reflect when a service is degraded rather than treating any child monitor failure as a total outage. All-or-nothing status can misrepresent availability, while users also want thresholds or weights to account for how many components are up and which ones matter most. The signals do not describe a workaround that solves this.
For uptime Kuma administrators. Mentioned from May 2022 to Jun 2025 on GitHub.
5 different people described this problem in 2 separate discussions.
- Indie fit
- 4.0/10
- Pain
- 5.2/10
- Frequency
- 6.5/10
- Willingness to pay
- 0.0/10
- Momentum
- 5.0/10
- Who pays
- Businesses
- Competition
- Medium
- Build difficulty
- Medium
What people said
Quoted word for word. Follow a link to read the whole discussion.
Each group should have a setting on how many % of child needs to be up in order for a group to still show as green / up
One of those being down doesn't really mean the whole service is unavailable, but Uptime Kuma displays it as such: Being able to show this as "Partially degraded" or something would be helpful to show users that this service is not completely down but they may have some issues
Build brief
See what to build and who will buy it
- 2 product ideas with the smallest useful version and pricing
- 3 places to find your first customers
- 3 more quotes from people who have this problem
- Current workarounds, existing solutions and risks