Cron jobs that report back
Starts, failures, exit codes, logs and jobs that never finish—each signal is visible and alertable.
Monitoring that stays in your account
Uptime and cron-job monitoring that runs free on your own Cloudflare account.
Know when a job misses, a check slows down, or a service fails. StatusPing runs close to your systems and leaves you in control.
No per-monitor bill. No hosted account required.Northstar systems
We’re fully operational
API
99.99%Nightly export
100%Your Cloudflare accountWorkers, D1 and secrets stay under your control.
About one minuteFrom a short setup to a working status page.
Built for failure pathsA separate watcher can alert if Cloudflare is unreachable.
Coverage for the things that quietly break.
One lightweight service watches both public endpoints and the background work your users never see.
HTTP checks with timing
Check an endpoint on schedule and see response time alongside availability, not in a separate tool.
Status pages with boundaries
Publish exactly what belongs on each page. Restrict others with email sign-in, Cloudflare Access or SSO.
Alerts that reach people
Send notifications through Pushover, ntfy or Telegram when a service needs attention.
From config to coverage in three steps.
Deploying creates an independent StatusPing in your account. We don’t hold your monitor data or keep account access.
Configure
Name the page, add your endpoints and cron schedules, then choose who can see it.
Connect Cloudflare
Authorize only the permissions needed to create the Worker, database and its secrets.
Go live
StatusPing is deployed into your account, verified, and then disconnected.
The free plan is enough for a serious small system.
Cloudflare’s free-tier limits matter, so they’re part of the decision—not fine print.
$0
Cloudflare’s free plan is sufficient for typical StatusPing installations. You pay Cloudflare directly if your needs grow.
- 100,000 requests per dayWorker requests on Cloudflare’s free plan.
- 10 ms CPU time per runDesigned for quick checks and state updates.
- 100,000 D1 rows written per dayRetention controls help keep monitor history bounded.
- Use Node if Cloudflare is not your fitThe same application also supports a self-hosted Node deployment.
A focused alternative.
Comparison current as of October 10, 2026. Capabilities and pricing change—verify for your use case.
| Tool | Runs in your account | Cron push checks | Public status page | Managed hosting |
|---|---|---|---|---|
| StatusPing | Yes, Cloudflare or Node | Yes | Yes | Waitlist |
| Uptime Kuma | Yes, self-hosted | Yes | Yes | Community / third party |
| Healthchecks.io | Hosted or self-hosted | Yes | Limited | Yes |
| Better Stack | No | Yes | Yes | Yes |
Questions worth asking before you connect an account.
Do you get access to my Cloudflare account?
Only for the deploy, using a scoped OAuth token. The deployer revokes the token after StatusPing has been verified, and it does not retain it.
Can I delete it?
Yes. The Worker, D1 database and its secrets are yours. Remove them in the Cloudflare dashboard whenever you like.
What happens if Cloudflare is down?
A separate watchdog can run outside Cloudflare and alert when the primary service cannot report in. It covers a different failure domain.
What are the limits?
Cloudflare’s current free-plan request, CPU and D1 write limits apply. For very high-frequency checks or long history, self-host on Node or use a paid Cloudflare plan.
Prefer not to operate it?
We’re measuring interest in a hosted StatusPing. Join the waitlist and we’ll contact you if it becomes available.