Built with WordPress and Astro, hosted on Cloudflare. Domain registered in 2026.
crontinel.com is built with WordPress, hosted on Cloudflare. It measures traffic with Cloudflare Web Analytics. It sends email through Amazon SES.
| Technology | Version | First seen |
|---|---|---|
| CMS & Site Builders1 | ||
| – | 9 Nov 2026 | |
| JavaScript Frameworks & Libraries1 | ||
| 5.16.2 | 9 Nov 2026 | |
| Frontend Build Tools & CSS1 | ||
| – | 9 Nov 2026 | |
| Web Servers, Languages & Backend Frameworks1 | ||
| – | 9 Nov 2026 | |
| CDN & Hosting1 | ||
| – | 9 Nov 2026 | |
| Analytics & Tag Management1 | ||
| – | 9 Nov 2026 | |
| Transactional Email2 | ||
| – | 9 Nov 2026 | |
| Fonts & Icon Fonts1 | ||
| – | 9 Nov 2026 | |
Registration from the registry's RDAP record, the certificate the site serves, and its rank in public traffic lists.
The crew hasn’t read this site’s colors yet. We read a palette when we capture a site’s screenshot, busiest sites first. Meanwhile, browse palettes from other sites.
Counted from every stack change we've recorded: of the sites we watched running one of this site's tools, how many went on to add another. A pattern across sites, not a forecast for this one.
mx.zoho.commx2.zoho.commx3.zoho.comivy.ns.cloudflare.comanuj.ns.cloudflare.comgoogle-site-verification=NXLscfMhqqXnq2OQgFOw6NgEB1Nd2X-k5BXca5jmBDozoho-verification=zb15462800.zmverify.zoho.comv=spf1 include:zohomail.com ~all# Named AI crawlers may learn from this public site. # Unknown automated clients are rate limited at the edge. User-agent: GPTBot Content-Signal: search=yes, ai-train=yes, ai-input=yes Allow: / User-agent: ChatGPT-User Content-Signal: search=yes, ai-train=yes, ai-input=yes Allow: / User-agent: OAI-SearchBot Content-Signal: search=yes, ai-train=yes, ai-input=yes Allow: / User-agent: ClaudeBot Content-Signal: search=yes, ai-train=yes, ai-input=yes Allow: / User-agent: Claude-SearchBot Content-Signal: search=yes, ai-train=yes, ai-input=yes Allow: / User-agent: Claude-User Content-Signal: search=yes, ai-train=yes, ai-input=yes Allow: / User-agent: anthropic-ai Content-Signal: search=yes, ai-train=yes, ai-input=yes Allow: / User-agent: PerplexityBot Content-Signal: search=yes, ai-train=yes, ai-input=yes Allow: / User-agent: Perplexity-User Content-Signal: search=yes, ai-train=yes, ai-input=yes Allow: / User-agent: Google-Extended Content-Signal: search=yes, ai-train=yes, ai-input=yes Allow: / User-agent: Applebot-Extended Content-Signal: search=yes, ai-train=yes, ai-input=yes Allow: / User-agent: CCBot Content-Signal: search=yes, ai-train=yes, ai-input=yes Allow: / User-agent: Amazonbot Content-Signal: search=yes, ai-train=yes, ai-input=yes Allow: / User-agent: Meta-ExternalAgent Content-Signal: search=yes, ai-train=yes, ai-input=yes Allow: / User-agent: FacebookBot Content-Signal: search=yes, ai-train=yes, ai-input=yes Allow: / User-agent: Bytespider Content-Signal: search=yes, ai-train=yes, ai-input=yes Allow: / User-agent: cohere-ai Content-Signal: search=yes, ai-train=yes, ai-input=yes Allow: / User-agent: YouBot Content-Signal: search=yes, ai-train=yes, ai-input=yes Allow: / User-agent: DuckAssistBot Content-Signal: search=yes, ai-train=yes, ai-input=yes Allow: / User-agent: Diffbot Content-Signal: search=yes, ai-train=yes, ai-input=yes Allow: / User-agent: Googlebot Content-Signal: search=yes, ai-train=yes, ai-input=yes Allow: / User-agent: Bingbot Content-Signal: search=yes, ai-train=yes, ai-input=yes Allow: / User-agent: DuckDuckBot Content-Signal: search=yes, ai-train=yes, ai-input=yes Allow: / User-agent: Applebot Content-Signal: search=yes, ai-train=yes, ai-input=yes Allow: / User-agent: Slurp Content-Signal: search=yes, ai-train=yes, ai-input=yes Allow: / User-agent: * Content-Signal: search=yes, ai-train=yes, ai-input=yes Allow: / Sitemap: https://crontinel.com/sitemap.xml LLMs.txt: https://crontinel.com/llms.txt LLMs-full.txt: https://crontinel.com/llms-full.txt
# Crontinel > Completed is not done. Crontinel tells you when a background job finished without doing the work. Any runtime sends one HTTP receipt. The Laravel package attaches that receipt from the scheduler and can add queue depth and Horizon freshness. ## Core pages - [Home](https://crontinel.com/): Cron and queue monitoring for any framework - [Features](https://crontinel.com/features/): Supervisors, queue depth, cron runs, alerts, and integrations - [Pricing](https://crontinel.com/pricing/): Hosted plans, including a free plan - [FAQ](https://crontinel.com/faq/): Frequently asked questions - [About](https://crontinel.com/about/): The product and the team - [Products](https://crontinel.com/products/): Products in the Crontinel catalog - [Agent](https://crontinel.com/agent/): Using Crontinel from an AI agent - [Full context](https://crontinel.com/llms-full.txt): Detailed plain-text context for AI assistants - [Changelog](https://crontinel.com/changelog/): Product changes - [Security](https://crontinel.com/security/): Security practices and data handling - [Privacy](https://crontinel.com/legal/privacy/): Privacy policy - [Terms](https://crontinel.com/legal/terms/): Terms of service - [Cookie policy](https://crontinel.com/legal/cookies/): Cookie usage and consent ## Blog - [Blog](https://crontinel.com/blog/): Cron monitoring guides, comparisons, and failure write-ups - [Background Job Monitoring: Built-In vs Dedicated vs DIY](https://crontinel.com/blog/background-job-monitoring-comparison/): Compare three ways to monitor Laravel background jobs: framework built-ins, dedicated SaaS monitors, and DIY heartbeat solutions. Find the right fit. - [Better Stack Killed Cron Monitoring: The Replacement](https://crontinel.com/blog/better-stack-cron-monitoring-gone/): Better Stack removed cron monitoring in April 2026. If your scheduler heartbeats stopped working overnight, here's what happened and the free replacement. - [Laravel Cron Job Runs Manually but Not on Schedule](https://crontinel.com/blog/cron-job-runs-manually-but-not-on-schedule/): If a Laravel cron job runs manually but not on schedule, check the crontab, working directory, and scheduler heartbeat. Here's how to find the cause. - [Cron Monitoring Guide 2026: Detect Failures Before Users Do](https://crontinel.com/blog/cron-monitoring-guide/): Complete guide to cron monitoring for engineering teams. Detect missed schedule runs, silent failures, worker stalls, and queue backpressure in any stack. - [Crontinel vs Cronitor vs CronRadar: 2026 Pricing Compared](https://crontinel.com/blog/cron-monitoring-pricing-compared-2026/): Compare cron monitoring pricing for 2026: Crontinel, Cronitor, CronRadar. Free tiers, per-monitor costs, Horizon support, and self-hosting options. - [Cron Scheduler Alternatives for Your Production Stack](https://crontinel.com/blog/cron-scheduler-alternatives/): Compare cron scheduler alternatives for production: system crontab, systemd timers, Kubernetes CronJobs, and Laravel task scheduling. Find the right fit. - [Monitoring Cron Jobs with Datadog: Setup and Limits](https://crontinel.com/blog/datadog-cron-monitoring/): Set up Datadog cron monitoring with dogwrap or DogStatsD, see where it falls short for Laravel and Horizon, and when a purpose-built tool fits better. - [Debugging Laravel Reverb Connection Drops in Production](https://crontinel.com/blog/debug-laravel-reverb-connection-drops/): Intermittent WebSocket drops in Laravel Reverb are hard to catch. Diagnose the root cause, monitor connection stability, and alert when clients drop. - [Debugging Silent Laravel Cron Failures in Production](https://crontinel.com/blog/debugging-silent-laravel-cron-failures/): Silent Laravel cron failures are hard to debug: the job never ran, the log is empty, and nobody got an alert. Find the real cause and make failures loud. - [Detect Cron Job Failures in Laravel: 5 Methods Compared](https://crontinel.com/blog/detect-cron-job-failures-laravel/): Five ways to detect cron job failures in Laravel, from log monitoring to dedicated tools. Each method's strengths, blind spots, and when to use it. - [Detect Laravel Queue Worker Stalls: When Workers Go Silent](https://crontinel.com/blog/detect-laravel-worker-stalls/): A Laravel queue worker that's alive but not processing jobs gives no alert and no error. Learn how to detect stalled workers, common causes, and fixes. - [How to Detect Silent Cron Failures in Laravel](https://crontinel.com/blog/detect-silent-laravel-cron-failures/): Laravel's scheduler runs your cron jobs but doesn't tell you when they fail. Here's how to detect silent failures before they become support tickets. - [Detecting Slow Laravel Queue Jobs Before They Crash Your App](https://crontinel.com/blog/detecting-slow-laravel-jobs/): Detect slow Laravel queue jobs, monitor Horizon performance, and catch degraded workers before users notice, with queue depth alerts and duration tracking. - [Monitoring Laravel Cron Jobs Inside Docker Containers](https://crontinel.com/blog/docker-laravel-cron-monitoring/): How to reliably monitor scheduled tasks when your Laravel app runs inside Docker — covering entrypoint scripts, zombie processes, and signal handling pitfalls. - [Monitoring AWS EventBridge Rules: Catch Silent Failures](https://crontinel.com/blog/eventbridge-cron-monitoring/): How AWS EventBridge cron monitoring works, why scheduled rules fail silently (missed triggers, IAM permissions, DLQ backlogs), and how to catch it. - [Laravel Horizon Paused: Detect It Before Customers Notice](https://crontinel.com/blog/horizon-paused-detection/): Run horizon:pause before a deploy, forget to resume, and jobs queue silently for hours. How to detect the paused state and automate the alert. - [In-Flight Jobs When Horizon Supervisors Restart](https://crontinel.com/blog/horizon-supervisor-restart-job-loss/): When a Horizon supervisor restarts in Laravel, in-flight jobs can be lost, retried, or orphaned. Learn how to detect and prevent job loss during restarts. - [Laravel Horizon Shows Running But Jobs Aren't Processing](https://crontinel.com/blog/horizon-supervisor-stopped-jobs-not-processing/): Horizon's status dashboard says everything is fine. Jobs are silently piling up. Here's why that happens and how to actually detect a dead supervisor. - [How to Monitor Horizon Jobs in Production](https://crontinel.com/blog/how-to-monitor-horizon-jobs-production/): Laravel Horizon has a great dashboard, but in production you must know when supervisors stop, queues pile up, or failed jobs accumulate. Set up monitoring. - [How to Set Up Laravel Cron Monitoring (The Right Way)](https://crontinel.com/blog/how-to-set-up-laravel-cron-monitoring/): A step-by-step guide to Laravel cron monitoring that works. Detect missed schedules, failed tasks, and silent cron failures before your users notice. - [Laravel Background Job Monitoring Checklist: What Teams Miss](https://crontinel.com/blog/laravel-background-job-monitoring-checklist/): A Laravel job monitoring checklist covering Horizon health, queue depth, cron run history, alerting, and deployment safety. Few teams check all five. - [Laravel bootstrap/cache Files Explained: Safe to Delete?](https://crontinel.com/blog/laravel-bootstrap-cache-files-explained/): What config.php, packages.php, services.php and routes-v7.php in Laravel's bootstrap/cache are, which command makes each, and whether it is safe to delete them. - [Detecting Laravel Broadcast Failures Before Users Do](https://crontinel.com/blog/laravel-broadcast-failure-detection/): Broadcasting silently fails in production: Pusher disconnects, Reverb drops, Soketi restarts. Detect broadcast failures and monitor WebSocket health. - [Laravel Cron Job Not Running After Deploy: How to Catch It](https://crontinel.com/blog/laravel-cron-job-not-running-after-deploy/): Your cron jobs worked before the deploy, now they've stopped and the logs are empty. Here's why deploys break cron and how to detect it fast. - [Why Your Laravel Cron Job Isn't Running (And How to Fix It)](https://crontinel.com/blog/laravel-cron-job-not-running/): Laravel cron jobs fail silently in many ways. Diagnose the cause, from misconfigured server cron entries to scheduler bugs and silent exit code failures. - [Laravel Cron Monitoring Across Multiple Microservices](https://crontinel.com/blog/laravel-cron-monitoring-multi-microservices/): Monitor scheduled tasks across distributed Laravel services without losing visibility: unified dashboards, cross-service heartbeats, and failure points. - [Laravel Cron and Queue Monitoring Tools: 2026 Comparison](https://crontinel.com/blog/laravel-cron-queue-monitoring-tools/): Compare Laravel cron and queue monitoring tools for production: Cronitor, Healthchecks.io, Better Stack, Forge Heartbeats, Telescope, Horizon, and Crontinel. - [Laravel Cron Timezone Not Working? Fix ->timezone() Bugs](https://crontinel.com/blog/laravel-cron-timezone-issues/): Your Laravel scheduled task fires at the wrong time in production but works in dev. Why ->timezone() fails with DST and UTC offsets, and how to debug it. - [Laravel Cron vs Queue Monitoring — What's the Difference?](https://crontinel.com/blog/laravel-cron-vs-queue-monitoring/): Generic uptime monitors miss scheduler failures, and queue depth monitors miss Horizon supervisor death. Here's why you need both and what each one covers. - [Cron vs Queue in Laravel: Choosing the Right Pattern](https://crontinel.com/blog/laravel-cron-vs-queue-when-to-use/): Scheduled command or queued job? It depends on trigger source, execution guarantees, and failure recovery. Here's a decision framework with real examples. - [Laravel dispatchSync(): How It Works and When It Fails](https://crontinel.com/blog/laravel-dispatchsync-explained/): What Laravel's dispatchSync() and dispatch_sync() do, why dispatchNow() is gone, and why sync job failures never reach the failed_jobs table. - [Failed Jobs in Laravel: Beyond the failed_jobs Table](https://crontinel.com/blog/laravel-failed-jobs-monitoring/): Your failed_jobs table only tells you a job already died. Here's how to catch rising failure rates before they become an outage. - [Detect and Fix Laravel Horizon Config-Environment Mismatches](https://crontinel.com/blog/laravel-horizon-config-env-mismatch/): When your Horizon config doesn't match the environment (wrong Redis host, stale supervisors, misplaced queues), jobs silently fail. Detect and prevent it. - [Laravel Horizon Workers Idle While Jobs Pile Up? 6 Fixes](https://crontinel.com/blog/laravel-horizon-idle-workers/): Horizon shows workers as running while 2,000 jobs pile up untouched. Here are the 6 real causes — and how to fix each one fast. - [Laravel Job Batching: Monitor and Alert on Failures](https://crontinel.com/blog/laravel-job-batching-monitoring/): How to detect and respond to Laravel job batch failures in production — covering cancellation, timeout, and silent degradation patterns. - [Laravel Nightwatch Monitoring: What It Does, What It Misses](https://crontinel.com/blog/laravel-nightwatch-monitoring/): A practical look at Laravel Nightwatch, the official APM tool: what it tracks for requests, jobs, and the scheduler, and its blind spots for heartbeats. - [Laravel Octane Doesn't Run the Scheduler (How to Catch It)](https://crontinel.com/blog/laravel-octane-scheduler-not-running/): Laravel Octane serves HTTP but does not run the scheduler. Why scheduled tasks silently stop after an Octane deploy, and how to monitor schedule:run. - [Queue Backpressure in Laravel: When Depth Spikes](https://crontinel.com/blog/laravel-queue-backpressure/): Your queue depth is climbing, jobs time out, and retries make it worse. See how backpressure builds in Laravel queues, why it cascades, and how to respond. - [Laravel Queue Depth Monitoring: Alert Before Backlogs](https://crontinel.com/blog/laravel-queue-depth-alert/): Queue depth spikes silently. Learn to query depth for Redis and database drivers, set thresholds per queue, and why oldest-job age is the metric you want. - [Laravel Queue Monitoring: Catch Failures Before Users Do](https://crontinel.com/blog/laravel-queue-monitoring-catch-failures/): Laravel queues fail silently. A job throws, gets buried, and nobody notices until a customer asks about their order. Here's how to monitor queues. - [Laravel Queue Priority: Stop Critical Jobs Getting Stuck](https://crontinel.com/blog/laravel-queue-priority-laravel/): Laravel queues process jobs FIFO by default. Without explicit priority configuration, payment confirmations sit behind welcome emails. Here's how to fix it. - [Laravel Queue Worker Died: How to Detect and Recover](https://crontinel.com/blog/laravel-queue-worker-died-detect-recover/): Queue workers die quietly. OOM kills, segfaults, and restart loops leave no trace while jobs pile up. Here's how to detect a dead worker early. - [Laravel Queue Worker Graceful Shutdown: No Lost Jobs](https://crontinel.com/blog/laravel-queue-worker-graceful-shutdown/): Configure Laravel queue workers for graceful shutdown on deploy so no jobs are lost or duplicated. Covers Horizon, Supervisor, and queue:work. - [Laravel Queue Worker Memory Leaks: Detect Them Early](https://crontinel.com/blog/laravel-queue-worker-memory-leak/): Queue workers run for hours or days and memory climbs until the process is killed. Learn how leaks happen in Laravel workers and how to detect them early. - [Detect Missed Laravel Schedule Runs Before They Cascade](https://crontinel.com/blog/laravel-schedule-missed-run-alert/): A missed Laravel schedule run can silently break your app. Learn to detect missed runs with native tools and heartbeat monitoring, and alert fast. - [Laravel withoutOverlapping(): Prevent Stuck Scheduled Tasks](https://crontinel.com/blog/laravel-schedule-withoutoverlapping-explained/): Learn how Laravel's withoutOverlapping() lock works, why stale mutexes skip jobs, how to clear them, and how to monitor skipped tasks. - [Laravel Scheduler Events: Custom Monitoring With Hooks](https://crontinel.com/blog/laravel-scheduler-events-monitoring/): Laravel's scheduler dispatches events on task start, finish, and failure. Learn to hook into ScheduledTaskFinished and wire real-time failure alerts. - [Laravel Scheduler Timezone Pitfalls: Wrong Cron Times](https://crontinel.com/blog/laravel-scheduler-timezone/): Why Laravel scheduled tasks fire at the wrong hour: how APP_TIMEZONE, schedule_timezone, server TZ, and CRON_TZ interact, the DST trap, and a fix checklist. - [Migrate from Better Stack Cron Monitoring to Crontinel](https://crontinel.com/blog/migrate-from-better-stack-cron-monitoring/): Better Stack removed cron monitoring in 2026. Audit heartbeats, remove dead pings, and switch your Laravel scheduler monitoring to Crontinel. - [How to Monitor Laravel pennant:purge in Production](https://crontinel.com/blog/monitor-laravel-pennant-purge/): A silent pennant:purge failure during deployment leaves users with stale feature flags. Here's how to monitor the purge command and catch failures early. - [How to Monitor Laravel Scheduled Tasks in Production](https://crontinel.com/blog/monitor-laravel-scheduled-tasks-production/): schedule:run failures are silent by default. Wire up event listeners, record exit codes and durations, and alert on missed or failed scheduled tasks. - [Monitoring Laravel Cron Jobs on Kubernetes: Full Guide](https://crontinel.com/blog/monitoring-kubernetes-cron-jobs/): Laravel's scheduler on Kubernetes adds failure modes: pod restarts wipe cron state, scaling creates duplicate runs, and dead pods leave jobs unfinished. - [Monitoring Custom Artisan Commands in Production](https://crontinel.com/blog/monitoring-laravel-artisan-commands/): Custom Artisan commands run critical business logic but are invisible to most monitoring. Instrument exit codes, duration, heartbeats, and alerts. - [Monitoring vs Observability for Laravel Cron Jobs](https://crontinel.com/blog/monitoring-vs-observability/): Monitoring tells you a cron job failed. Observability tells you why. Here's when each matters and how Laravel teams should combine them in production. - [Node.js Cron Monitoring: Detect Task Failures Early](https://crontinel.com/blog/nodejs-cron-monitoring/): Monitor Node.js cron jobs, scheduled tasks, and background workers. Detect missed runs, silent failures, and queue backpressure in node-cron and Bull. - [Open Source, Self Hosted, Free Cron Monitoring for Laravel](https://crontinel.com/blog/open-source-self-hosted-free-cron-monitoring/): Compare open source, self hosted, and free cron monitoring for Laravel. See what each path gives you and when a Laravel-native monitor is worth it. - [PagerDuty + Laravel: Auto-Create Incidents from Alerts](https://crontinel.com/blog/pagerduty-laravel-queue-cron-alerts/): Wire Laravel queue depth alerts and cron failures into PagerDuty with Events API v2. Dedup keys link fire and resolve events to one incident. - [Python Scheduled Task Monitoring: APScheduler, Celery, Cron](https://crontinel.com/blog/python-scheduled-task-monitoring/): Monitor Python scheduled tasks: APScheduler, Celery Beat, system cron, and custom schedulers. Detect missed runs, silent failures, and backpressure early. - [Laravel Queue Worker Memory Limits Without Restart Loops](https://crontinel.com/blog/queue-worker-memory-limit/): How Laravel's queue:work --memory flag differs from PHP memory_limit, how to choose a safe value, and how to configure Supervisor for clean worker recycling. - [What Happens to Horizon When Redis Drops](https://crontinel.com/blog/redis-connection-lost-horizon/): Redis goes down and Horizon loses its connection. Jobs vanish, supervisors crash, and the dashboard goes blank. Here's what breaks and what recovers. - [Cron Monitoring Alert Fatigue: Reduce Notification Noise](https://crontinel.com/blog/reduce-cron-alert-fatigue/): Too many cron alerts desensitize your team to real incidents. Classify severity, set smart grace periods, and cut noise without missing real failures. - [Detect Laravel schedule:run Boot Loops Before Cron Stops](https://crontinel.com/blog/schedule-run-boot-loop-detection/): When schedule:run crashes on boot, Supervisor restarts it every second and your real cron never fires. Learn to detect boot loops and their causes. - [thenping.me Is Dead: What Changed in Cron Monitoring](https://crontinel.com/blog/thenping-me-is-dead/): thenping.me was a go-to cron monitoring tool for Laravel developers until it was archived in January 2025. Here's what happened and what to use now. - [What Happens When Your Laravel Scheduler Stops Running](https://crontinel.com/blog/what-happens-when-laravel-scheduler-stops-running/): The Laravel scheduler depends on a single cron entry. When it breaks or deadlocks, tasks stop and you may not notice for days. Here's how to detect it. - [What is Cron Monitoring and Why Laravel Developers Need It](https://crontinel.com/blog/what-is-cron-monitoring-laravel/): Laravel cron jobs fail silently by default. Here's what that means, why it's dangerous, and how to detect failures before they become production incidents. - [Laravel Horizon Redis Keys Explained](https://crontinel.com/blog/what-laravel-horizon-redis-keys-mean/): A reference of every Redis key Laravel Horizon stores: what each contains, what it means operationally, and how to inspect it with redis-cli. - [Why Generic Cron Monitors Miss Laravel Horizon Failures](https://crontinel.com/blog/why-generic-cron-monitors-miss-horizon-failures/): Cronitor tells you a job ran. It can't tell you your Horizon supervisor is paused. Here's what's actually going on under the hood. - [Why Generic Uptime Monitors Miss Laravel Queue Failures](https://crontinel.com/blog/why-generic-uptime-monitors-miss-queue-failures/): Your uptime monitor shows green while queue depth climbs to 5,000 and customers wait. Here's why HTTP pings can't see Laravel queue failures. ## Use cases - [Use cases](https://crontinel.co
Contact: https://crontinel.com/contact/ Expires: 2027-11-06T00:00:00.000Z Policy: https://crontinel.com/security/ Canonical: https://crontinel.com/.well-known/security.txt Preferred-Languages: en
| – |
| 9 Nov 2026 |