cronpimo
Did your backup finish?
Your script checks in with Cronpimo. If an expected check-in is missing or it reports a failure, you get notified.
Sample dataNightly backupCheck-in overdue
— Cron jobs & monitoring
Your jobs and services.
On time. In sight.
Schedule automated tasks, monitor services and certificates, and find out when an expected check-in is missing.
From recurring API calls to nightly backups: keep track of executions, connectivity and check-ins.
Run history · sample dataEvery five minutes
Response time: 0–990 ms
SuccessFailureResult unknownSkippedIn progressNo measurement
Height: response time, scaled per chart. In your dashboard, each bar opens the run details.
Between executions, too
Keep an eye on your services
Renew certificates in time
Get reminders before your SSL certificates expire. You choose the days and notification destinations.
Sample dataexample.comValid for another 14 days
Are your services reachable?
Check publicly reachable TCP services, such as your mail server or SSH endpoint.
Sample datamail.example.com:587Reachable
In your dashboard
Your automations at a glance
| Cron jobs | Schedule | Last 24 runs | Status |
|---|---|---|---|
| Update inventoryexample.com/inventory | Every five minutes*/5 * * * * | Response time: 0–990 ms | Success |
| Generate daily reportexample.com/report | Weekdays at 08:000 8 * * 1-5 | Response time: 0–990 ms | Failure |
| Warm up cacheexample.com/cache | Every 15 minutes*/15 * * * * | Response time: 0–990 ms | Paused manually |
| Synchronize dataexample.com/sync | Every hour0 * * * * | Response time: 0–980 ms | Result unknown |
Incidents
What happened. And what happens next.
Find out when a task fails and review its cause and history. A recovery notification tells you when it succeeds again.
Open incident
See when a failure began, how long it has lasted and which notifications were sent.
- Failure
- Notification after your chosen number of failures
- Success
- Recovery notification when the cron job succeeds again
- Result unknown
- Check the outcome before repeating the request manually. Future scheduled runs remain in place.
Run details
Clear states
Each run shows its scheduled and actual start, response time and execution location.
- Schedule
- Scheduled time and start
- HTTP
- Result and duration
- Region
- Execution location
Maintenance windowsPro · Max
Maintenance planned? Cronpimo knows.
Pause jobs or suppress notifications during planned maintenance. Once or on a recurring schedule.
Sundays · 02:00–03:00 · Alerts pausedSample data
Availability reportsMax
How reliable were your checks?
Compare the success rate of your checks across multiple days. View a chart in your dashboard or receive scheduled email reports.
Schedule · Test · Observe · Alert
From schedule to notificationSchedule
Choose an HTTP request, TCP check or SSL check and set a schedule. With heartbeats, your own script checks in with Cronpimo.
Test
Test requests and checks before activating them. For a heartbeat, send an initial check-in from your script.
Understand
See each run’s status, response time and execution location. Open the run details to investigate a failed request.
Respond
Connect your team’s notification channel and choose which tasks should notify you about failures and recovery.
EmailSlackDiscordTeamsTelegramWebhookPagerDutyincident.io
Common questions
- Does a test really make a request?
- Yes. A manual test calls the configured URL using your saved settings and selected HTTP method. POST, PUT, PATCH and DELETE can create, change or delete data. Even a GET URL can trigger an action if your application is configured that way.
- Which HTTP method should I use?
- GET retrieves data, while POST often starts an action. PUT and PATCH update data; DELETE removes it. Follow the requirements of your API. HTTP methods with examples →
- What does “result unknown” mean?
- The outcome of a request could not be confirmed. It may already have run and changed data. Check your application before starting it again manually. Future scheduled runs remain in place.
- Are failed requests retried automatically?
- A failed request or one with an unknown outcome is not retried automatically. Your cron job runs again at its next scheduled time as long as it is active.
- Which schedules are supported?
- Choose fixed intervals or cron schedules and your time zone. Preview the upcoming times, including around daylight saving changes.
- Do I need my own server?
- HTTP tasks need a reachable endpoint; TCP and SSL checks need a publicly reachable service. Heartbeats can also be sent to Cronpimo from a private network. You continue to host your own application.
- What is a heartbeat?
- A check-in from your script, sent to its personal Cronpimo URL. Use it to monitor backups or data imports, for example. If an expected check-in does not arrive within your chosen grace period, Cronpimo notifies you.
- When will I be reminded about an expiring certificate?
- Choose 30, 14 or 7 days before expiry and individual days from 6 down to 1. You can select multiple reminders, sent to your chosen notification destinations.
- What happens during a maintenance window?
- Choose whether to pause executions or only suppress notifications for each job. Regular operation resumes after the maintenance window.
01
02
03
04
05
06
07
08
09
Start with your first job
Try Cronpimo for free. Compare plans for more jobs and additional monitoring features.