Cron every 8 hours

The cron expression for every 8 hours is:

0 */8 * * *

Runs three times a day: 00:00, 08:00 and 16:00.

3 times a day
Standard 5-field cron

Next 10 runs

For 0 */8 * * *, in the timezone you pick. Cron uses the server's timezone.

Times in UTC as of the last site update. They refresh when the page loads in a browser.

#Date and timeWhen
1Oct 30, 2026, 00:00Friday
2Oct 30, 2026, 08:00Friday
3Oct 30, 2026, 16:00Friday
4Oct 31, 2026, 00:00Saturday
5Oct 31, 2026, 08:00Saturday
6Oct 31, 2026, 16:00Saturday
7Nov 1, 2026, 00:00Sunday
8Nov 1, 2026, 08:00Sunday
9Nov 1, 2026, 16:00Sunday
10Nov 2, 2026, 00:00Monday

How to read 0 */8 * * *

0 in the minute field pins the job to minute 0. */8 in the hour field takes every eighth hour, starting at midnight. It is the same as 0 0,8,16 * * *.

FieldValueMeaningAllowed
Minute0At the top of the hour0-59
Hour*/8Every 8 hours, from hour 00-23
Day of month*Every day of the month1-31
Month*Every month1-12 or jan-dec
Weekday*Every day of week0-7 or sun-sat

Watch out for

  • Leaving the minute as * (* */8 * * *) runs the job every minute of those hours.
  • To shift the times, list them: 0 2,10,18 * * * runs at 02:00, 10:00 and 18:00.

Often used for: Jobs that run once per working shift.

Use it in

crontab

0 */8 * * * /path/to/your-script.sh

Edit with crontab -e. Runs in the server's timezone.

Kubernetes CronJob

apiVersion: batch/v1
kind: CronJob
metadata:
  name: my-job
spec:
  schedule: "0 */8 * * *"
  timeZone: "Etc/UTC"
  jobTemplate:
    spec:
      template:
        spec:
          restartPolicy: OnFailure
          containers:
            - name: my-job
              image: busybox:1.36
              command: ["sh", "-c", "date"]

Without timeZone, the schedule follows the timezone of the kube-controller-manager.

GitHub Actions

on:
  schedule:
    - cron: '0 */8 * * *'
      timezone: "Etc/UTC"
jobs:
  run:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - run: ./your-script.sh

Without timezone, GitHub runs schedules in UTC. It runs them at most every 5 minutes, and a run can start late when GitHub is busy.

All cron schedules

Cron does not tell you when a job stops

Know when a job on this schedule does not run.

Your job pings Drumbeats when it finishes. If a ping does not arrive on schedule, you get an alert. No SDK, free for up to 50 monitors.

Free for up to 50 monitors · Setup in 60 seconds · No credit card required