About
cron-job.org is a hosted cron job scheduler that executes HTTP requests for websites and scripts at configured intervals, from once per minute up to once per year. It supports custom request methods, headers, request bodies, execution previews, execution history, test runs, status notifications, status pages, status badges, multi-factor authentication, and a REST API.
The service is intended for developers who need scheduled URL checks, background HTTP calls, or simple uptime monitoring. The FAQ states that the service is entirely free of charge, allows unlimited cronjobs per account subject to fair usage, and limits execution frequency to 60 times per hour per job.
- Up to 60 executions per hour
- Unlimited cronjobs per account
- Custom HTTP methods and headers
- Execution history and response data
- Status notifications and status pages
- REST API access
- 30-second request timeout
Free Tier Value
This free tier is perpetual and genuinely usable, but it is capped by fair-use limits rather than being unlimited in every dimension. Because the service is entirely free of charge and includes the core scheduling and monitoring features, it is worth a small but real monthly amount—about $2/month as a buyer would value a basic always-free cron service with these limits.
What's included in the free tier
- Entire service is free of charge.
- Unlimited cronjobs per account, subject to fair usage.
- Cronjobs can run up to 60 times per hour, or once per minute.
- Each request times out after 30 seconds.
- Response output is limited to 64 KB.
- Last 50 executions are available per cronjob.
- Response headers and bodies are stored for 2 days.
- SSL/HTTPS cronjobs are supported, including self-signed certificates.
- HTTP authentication is supported for protected URLs.
- Custom headers are supported, except User-Agent and Connection.
- Cookies can be sent via custom Cookie headers.
- Most standard HTTP methods are supported, including POST, PUT, and HEAD.
- Failure email notifications are available for monitoring servers.
- Automatic deactivation can occur after more than 25 consecutive failures.
See cron-job.org pricing for current limits.
