How do you catch "zombie" cron jobs that hang but don't fail?
A troubleshooting thread in r/sysadmin (26 comments) about something not working as expected with Cronitor.
Collected Jul 11, 2014 – Jun 16, 2026
Distinct communities
Lexicon-coded stance set
Static snapshot, not a live feed
How this was measured: This report summarises 14 public Reddit threads collected across 7 subreddits through the Reddit API. Thread counts, subreddit shares, the weekly trend, and the date range are computed from those threads alone. The sentiment split is measured on the 10 most-discussed threads of them, by reading each thread's replies and weighting them by the upvotes they earned; the labels come from a fixed word list, not from human review. This is a sample of public discussion, not a complete or representative measure of it, and not a customer satisfaction score.
Editorial verdict
Sample verdict
14 public Reddit threads about Cronitor were collected across 7 subreddits, led by r/SideProject. The dominant question type is alternative shopping (3 of 14), and the highest-scoring thread in the sample is "Uptime Robot + SSL Labs + Cronitor + DNS Spy + Oh Dear + Merj". This report summarises those threads only; it is not a measure of Cronitor's overall standing.
Stance mix: 10% positive · 60% neutral · 30% negative across the 10 most-discussed collected threads, labelled by reading each thread's replies against a fixed word list rather than by hand.
Primary decision lens
Where the conversation happens
Most common complaint
Users actively seeking alternatives
Of the 14 threads collected, the questions break down as alternative shopping (3), troubleshooting (2), open shortlist requests (1). That mix indicates which part of the decision Cronitor is usually being weighed on.
2 threads report something not working as expected with Cronitor, ranging from failed actions to unanswered support requests.
Where the conversation happens · What buyers are actually asking · How current the signal is · Users actively seeking alternatives
Sentiment distribution
10%
1 threads
60%
6 threads
30%
3 threads
Recurring themes
Where the conversation happens
Cronitor discussion collected here spans 7 subreddits, led by r/SideProject (50%), r/selfhosted (14%), r/sysadmin (7%). The most-commented thread in the sample is "How do you catch "zombie" cron jobs that hang but don't fail?" (26 comments in r/sysadmin).
Users actively seeking alternatives
The largest negative signal is 3 threads asking for something other than Cronitor, concentrated in r/SideProject.
Review the remaining decision and diligence themes for Cronitor, each tied to a public thread ID.
Already have an account? Log in
Discussion pattern
Community distribution
r/SideProject
r/selfhosted
r/sysadmin
r/webdev
r/devops
r/SaaS
Switching & migration signals
3
Threads asking for alternatives
1
Threads about cost or plans
0
Titles mentioning a switch
0
Titles mentioning cancelling
Source trail
A troubleshooting thread in r/sysadmin (26 comments) about something not working as expected with Cronitor.
A r/selfhosted discussion (5 comments) that references Cronitor in the course of a broader conversation.
An alternatives thread in r/selfhosted (13 comments) where Cronitor is the tool being moved away from or compared against.
Open the remaining direct Reddit posts this report was built from.
Already have an account? Log in
Methodology & limitations
Reader questions
Use RedditMaster Campaign Mode to monitor relevant keywords and surface buyer-intent conversations.