UptimeHub
Use case

Laravel Uptime Monitoring for Apps, Queues and the Scheduler

A Laravel app rarely dies all at once. The web tier keeps answering while Horizon sits stopped, the scheduler cron entry vanishes after a server rebuild, or the database drops and /up still says 200. UptimeHub watches each of those from outside your server and pings your team in seconds.

See pricing
2 regions Read-only checks Status page included
ms
timeout
Latency scope · live
Uptime · 30 days
ms
Avg response

Checked from regions with auto-retry. No single-location false alarms.

All systems operational. Steady pulse across every region.

Down · caught in 8s

api.example.com returned no response from all 2 regions. Auto-retry confirmed the outage, then we alerted your team.

Resolved · 4m 12s downtime

api.example.com is back up. The incident is logged to your status page history automatically.

Example, Inc. Status
Operational

90-day uptime · branded · your domain

Live demo · drive it, no signup needed

In short

Laravel uptime monitoring means checking your application from outside the server on a short interval and expecting regular signals from the parts that run in the background. In practice that is an HTTP check on the built-in /up health route (extended to query the database), a heartbeat the scheduler sends after every run through thenPing, and a heartbeat fired from a queued job so you know workers are actually processing. UptimeHub runs the HTTP checks every 30 seconds from two regions with retry confirmation, watches heartbeats for lateness, and covers SSL, DNS and domain expiry on the same plan.

Why teams pick us

Uptime monitoring built for how you actually work

Laravel SaaS teams, agencies that ship Laravel client apps, and solo developers whose revenue depends on queued jobs, scheduled billing runs and a working checkout.

Health route plus database

Point a check at /up and add a DiagnosingHealth listener that runs a cheap query, so a dropped database turns the check red instead of hiding behind a booted framework.

Scheduler and queue heartbeats

One line of thenPing on your schedule and one tiny queued job prove that schedule:run fires every minute and that workers are draining the queue, not just running.

Alerts where your team deploys

Slack, Discord, Microsoft Teams, Telegram, PagerDuty, webhook, email and SMS, with a branded status page that updates itself when a check confirms an outage.

What to monitor in a Laravel application

Most Laravel outages that cost money are partial. The page loads, so a plain ping stays green, but invoices stop sending because the queue worker died after a deploy, or the nightly billing command never ran because the cron line that calls schedule:run was lost when the server was rebuilt. A useful setup checks each layer that can fail on its own.

Laravel already gives you two hooks for this. Since Laravel 11 the framework serves a health route at /up that returns 200 when the app boots and 500 when it throws, and the scheduler can ping a URL before or after a task with pingBefore, thenPing, pingOnSuccess and pingOnFailure. The table maps each failure to the check that catches it.

What breaks What users see Check that catches it Laravel hook
PHP-FPM or Nginx down, 502 from the load balancer Error page HTTP check on /up Built-in health route
Database or Redis unreachable Errors on any page that queries HTTP check on /up with a database query in the listener DiagnosingHealth event
Cron entry for schedule:run missing Nothing, until reports and renewals are late Heartbeat expected every minute thenPing on a minutely task
One scheduled command failing A stale report or an unsent batch Heartbeat per command pingOnSuccess and pingOnFailure
Queue workers stopped or stuck Emails, webhooks and exports never arrive Heartbeat sent from inside a queued job Schedule::job every five minutes
Login or checkout renders an error with status 200 A broken flow that looks fine to a ping Keyword check on the page body None needed
Certificate or domain about to lapse Browser warning or a dead site SSL expiry and domain expiry checks None needed

Domain expiry and DNS checks start on Pro. Every other check type is on every plan.

Keep the /up listener cheap. A single select against the primary database and a get from the cache store is enough, and it runs on every check, so anything heavier shows up as latency on your own monitor.

Wiring the scheduler and queue to heartbeats

Create a cron heartbeat monitor in UptimeHub, copy its ping URL, and add it to a task that runs every minute in routes/console.php, for example Schedule::command('inspire')->everyMinute()->thenPing($url). If that ping stops, schedule:run itself stopped, which is the failure that takes every other scheduled task down with it. Set the grace to two or three minutes so one slow minute does not page anyone.

Give each scheduled command that matters its own monitor with pingOnSuccess, set to the schedule it should follow. A daily billing run gets a 24 hour interval and a grace that covers its normal runtime. A missing ping then names the exact command that failed instead of a vague sense that something is off.

Queues need a different trick, because a worker process can be alive and still not process anything. Schedule a tiny job with Schedule::job(new QueueHeartbeat)->everyFiveMinutes() whose handle method does one HTTP request to a heartbeat URL. The ping only arrives if the scheduler dispatched the job and a worker picked it up, so one monitor covers Redis, Horizon and the workers end to end. Run one per queue name if you split emails, webhooks and exports across queues.

If you already lost a run and want to know why, the cron job not running checklist walks through the usual causes, from a crontab dropped by a rebuild to a path that changed in a deploy.

A worked example for a Laravel SaaS

Take a typical subscription app on one server, with a separate worker box running Horizon. The monitor list below is what we would set up on day one, and the count decides the plan.

Monitor Type Interval Count
/up with the database listener HTTP 30 seconds 1
Login, pricing and checkout pages Keyword 30 seconds 3
Public API endpoints with a JSON value check HTTP 30 seconds 2
schedule:run every minute Heartbeat 1 minute, 3 minute grace 1
Billing, report and cleanup commands Heartbeat Per schedule 3
Queue heartbeats for default, mail and webhooks Heartbeat 5 minutes, 5 minute grace 3
Main certificate and domain SSL and domain expiry Daily 2
Total 15

Prices read from the UptimeHub pricing page, annual billing.

Fifteen monitors fit inside Starter (20 monitors, one minute checks, $24 a month billed yearly), but the domain expiry check and the 30 second interval need Pro, which is $49 a month billed yearly for 100 monitors. That leaves 85 monitors free for a staging app, a second region of workers or client sites, at about 49 cents per monitor. Month to month the same plans are $49 and $99. See the full plan comparison before you choose.

The interval matters more than it looks. An outage that starts at a random moment waits on average half an interval before the first failed check, so moving from five minute checks to 30 seconds cuts that wait from about two and a half minutes to about 15 seconds, before the retry from a second region confirms it.

Laravel monitoring options compared honestly

There are good Laravel-specific tools, and the right one depends on what you need to see. Some live inside the app and see code, some live outside and see what customers see. Most teams that sell a Laravel product end up with one of each.

Option Runs where What it watches Best for Where it wins
Spatie laravel-uptime-monitor Inside your own Laravel app, as a scheduled command HTTP status and SSL from one location Developers who want a free package and full control No vendor at all. The catch is that it goes down with the server it runs on.
Laravel Nightwatch Agent inside your app, hosted dashboard Requests, exceptions, queries and jobs from inside the framework Finding why a request or job is slow or failing Framework-level detail an outside check cannot see
Oh Dear Hosted, checks from outside Uptime, SSL, broken links, scheduled tasks and status pages Agencies with many small Laravel sites Priced per site with all features on every plan, and it crawls for broken links
UptimeHub Hosted, two regions with retry HTTP, keyword, API, heartbeats, SSL, DNS and domain expiry, plus status pages A Laravel SaaS with many endpoints and background jobs Priced per monitor, so one app with 30 jobs and endpoints costs the same as 30 small sites

Read from each vendor page in November 2026. Oh Dear lists prices in euros, so they are not converted here.

If you run two or three marketing sites and want broken-link crawling, Oh Dear is the better fit, and our Oh Dear pricing breakdown shows where its tiers land. If you self-host everything, read why a monitor on the same server is a blind spot in the Uptime Kuma alternative page. Pair Nightwatch or any in-app tool with an outside check, because an agent inside a dead server cannot report that the server is dead.

Alerts that reach the people who deploy

Laravel teams tend to live in Slack or Discord, and agencies often run client apps for businesses where a broken queue is very visible, such as booking systems, client portals or legal research products like Cases (cases.ai). Every UptimeHub plan includes Slack, Discord, Microsoft Teams, Telegram, PagerDuty, webhooks, email and SMS, so the alert lands in the same channel as your deploy notifications and the on-call phone gets an SMS for the outages that cannot wait.

If your team already uses UptimeRobot and posts alerts to Discord, our breakdown of UptimeRobot Discord alerts by plan shows what changes when you need faster checks. For everything else on routing, escalation and quiet hours, see alerting features, and add a branded status page so customers see the incident before they open a ticket.

FAQ

Questions teams ask about Laravel

Check it from outside the server and expect signals from the parts that run in the background. Point an HTTP check at the /up health route, add a database query in a DiagnosingHealth listener, send a scheduler heartbeat with thenPing, and fire a queue heartbeat from a scheduled job so dead workers trigger an alert.

Attach thenPing with a heartbeat URL to a task that runs every minute. The monitor expects that ping on schedule and alerts you when it is late, which happens when the cron entry for schedule:run is missing, the server clock drifted or PHP fails before the scheduler starts.

Schedule a small job every five minutes whose only work is one HTTP request to a heartbeat URL. The ping arrives only if the job was dispatched and a worker processed it, so it catches stopped Horizon processes, a full Redis instance and stuck workers that are alive but idle.

Not by default. The /up route returns 200 when the framework boots without an exception. To include the database, listen for the DiagnosingHealth event and run a cheap query there. If the query throws, the route returns 500 and an external uptime check turns red within one interval.

Start monitoring in two minutes

Add your first monitor, pick your regions, and get alerts in seconds by Slack, email, SMS, or webhook. Read-only external checks that never touch your servers, plus a branded status page included.

See plans and pricing