Daily, weekly and monthly backups used to start at a fixed UTC time. For a team in New York that is the evening before. In Sydney it is the middle of the working day.
We are moving them to the night, in your timezone. This is not live for every team yet: we are rolling it out gradually over the coming weeks.
When your backups run
Once your team has moved, these schedules run in a nightly window that opens at 03:00 in your timezone.
| Schedule | Window opens, in your timezone |
|---|---|
| Daily | 03:00 |
| Twice daily | 03:00 and 15:00 |
| Weekly | Saturday at 03:00 |
| Monthly | The 1st at 03:00 |
03:00 is when the window opens, not a fixed start time for every backup. We pace backups across the window so they don't all start on the same minute, which means yours may begin a little after 03:00 and the exact start can shift slightly from one night to the next. Either way, it runs during your night, well before your working day.
If a backup needs to start at an exact time, use a custom schedule. Custom schedules run at the time you set.
We use the schedule's timezone if it has one, and your team's timezone otherwise. Custom schedules are unchanged, and teams on UTC see no difference.
See it on every schedule
Each schedule now shows its window and timezone, for example "Daily at 03:00 (Europe/Paris)". Changing your team's timezone in settings moves when these backups run, and the setting says so.
New teams get their timezone from the browser during onboarding, so they start on local time without changing anything.
Rolling out
We are switching teams over in batches over the coming weeks, so until your team is included, your backups keep their current UTC schedule. Your schedules always show the time they actually run, so you can see when your team has moved.