Skip to main content
FAQ: Daylight savings

Learn what to do around daylight savings

Anni avatar
Written by Anni
Updated over a week ago

The system shows times based on your account's timezone and locality when creating entries.

For example, if you set an event for 10:00 am in the "London" timezone, it's:

  • 10:00 am GMT (Greenwich Mean Time) in winter and

  • 10:00 am BST (British Summer Time) in summer.

For recurring events, the time is always 10:00 am, with daylight saving applied automatically—GMT until the clocks change, then BST, and back to GMT.

Some accounts use UTC (Coordinated Universal Time) without daylight saving. In this case, a recurring event set to "10:00 am" will be 10:00 UTC all year round.

  • However, if UTC shows on a 'London' calendar, the event will be 10:00 am GMT in winter and 11:00 am BST in summer.

Time zone vs Local time

💡 To note: The term "Time zone" is not the same as "Local Time", which is why it's best to set your zone as a city and not a generalised timezone. "Time zone" is often used instead of "Local time".

For example:

  • During DST (Daylight Saving Time), two areas like California and Arizona may appear in the same "Time zone" since they show the same time on the clock. California's local time is UTC-8 in Standard Time but becomes UTC-7 during DST. Arizona's local time, always UTC-7, remains on standard time throughout the year as there's no DST.

Important note regarding ticket availability restrictions:

DST (Daylight Saving Time) removes or adds an hour around midnight, which means, for example, any ticket set to become available 24 hours before the event starts will be wrong if it's on the DST change-over.

  • A workaround is to unpublish any dates that occur after the change happens and re-publish them once it has.

💬 Any questions or feedback? There are two ways to get in touch:

Thank you! 🕺

Did this answer your question?