Cron Expression for Every 6 Hours (0 */6 * * *)
Schedule summary: 4 times daily at 00:00, 06:00, 12:00, 18:00. Test live US Eastern, Pacific, and UTC execution timestamps below or copy platform-ready configs.
"On the hour, every 6 hours, every day"
Next 10 Scheduled Executions
America/New_York- 1Tue, Nov 17, 2026, 12:00 PM EST
- 2Tue, Nov 17, 2026, 06:00 PM EST
- 3Wed, Nov 18, 2026, 12:00 AM EST
- 4Wed, Nov 18, 2026, 06:00 AM EST
- 5Wed, Nov 18, 2026, 12:00 PM EST
- 6Wed, Nov 18, 2026, 06:00 PM EST
- 7Thu, Nov 19, 2026, 12:00 AM EST
- 8Thu, Nov 19, 2026, 06:00 AM EST
- 9Thu, Nov 19, 2026, 12:00 PM EST
- 10Thu, Nov 19, 2026, 06:00 PM EST
Cron Operator Reference
*Any / every value in this field,Value list separator (e.g., 1,15 runs on 1st & 15th)-Inclusive range (e.g., 9-17 means 9 AM through 5 PM)/Step increment (e.g., */10 runs every 10 units)1-5Monday through Friday in Weekday fieldCopy-Ready Snippets for Linux, GitHub Actions, Kubernetes & AWS
0 */6 * * * /usr/local/bin/run-task.sh >> /var/log/task.log 2>&1
on:
schedule:
- cron: '0 */6 * * *' # Runs in UTC apiVersion: batch/v1 kind: CronJob spec: schedule: "0 */6 * * *" timeZone: "America/New_York"
cron(0 */6 * * ? *)
Production Use Cases & Gotchas
- Periodic SSL certificate renewal checks (Certbot / ACME).
- Four-times-daily sitemap regeneration and CDN cache warming.
- Automated security vulnerability scans in CI/CD pipelines.
Production Note: If your servers operate in UTC, 0 */6 * * * fires at 00:00, 06:00, 12:00, and 18:00 UTC—equivalent to 7:00 PM, 1:00 AM, 7:00 AM, and 1:00 PM EST.
Frequently Asked Questions
How do you write a cron expression for 4 times daily at 00:00, 06:00, 12:00, 18:00? +
Use the 5-field POSIX cron expression "0 */6 * * *" for Linux crontab, Kubernetes CronJobs, and GitHub Actions. In AWS EventBridge (6-field format), use "cron(0 */6 * * ? *)".
What timezone does 0 */6 * * * run in on GitHub Actions and AWS? +
GitHub Actions and AWS EventBridge evaluate "0 */6 * * *" strictly in UTC (Coordinated Universal Time). Kubernetes v1.27+ allows setting spec.timeZone (such as "America/New_York").
What is the biggest gotcha with "0 */6 * * *" in production? +
If your servers operate in UTC, 0 */6 * * * fires at 00:00, 06:00, 12:00, and 18:00 UTC—equivalent to 7:00 PM, 1:00 AM, 7:00 AM, and 1:00 PM EST.