Cron every 10 minutes

*/10 * * * * runs a job every ten minutes, around the clock. */10 in the minute field means “every minute that divides by 10”: 0, 10, 20, 30, 40 and 50.

When it fires

On the clock, at :00, :10, :20, :30, :40 and :50 of every hour, not ten minutes after you install it. Checked at 09:58 UTC, the next five runs are:

10:00  10:10  10:20  10:30  10:40

Many jobs land on round minutes, so a shared server is busiest then. Move yours off them with a start before the step: 3-59/10 * * * * runs at :03, :13, :23 and so on.

Variations

*/10 8-18 * * 1-5    every 10 minutes, 08:00 to 18:50, Monday to Friday
0,10,20,30,40,50 * * * *   the same as */10, written out

The same schedule elsewhere

• GitHub Actions: cron: '*/10 * * * *', in UTC; busy periods can delay a run.
• Kubernetes CronJob: schedule: "*/10 * * * *".
• AWS EventBridge: rate(10 minutes), or cron(0/10 * * * ? *).
• systemd timer: OnCalendar=*:0/10.
• Spring @Scheduled: 0 */10 * * * *.