Hi. Today i tried to use the alarm with “sleep goal 85%” settings between 7:00 and 8:00, but Whoop woke me up at 6:21 in my local time.
So i think something wrong with timezone - in all graphs i see correct local time, but in “data caught up” notification i notice 1hr difference.
Hi @gewoih. Out of curiosity, did this happen on the first night after you changed time zone? I bounce between different time zones quite often, and have noticed that it can take a day for WHOOP to adjust to the change.
For example, on Wednesday 19th (sleep vs sleep needed graph):
I can assure you that I didn’t get 11 hours of sleep, that’s something that I can only dream of… 
So from my experience, your alarm setting should be fine from the second night in your new time zone.
Actually, no. I moved to different timezone almost 2 months ago, but it was the first time using the Alarm feature (also the time difference between current and original timezones is 2hrs, not 1hr).
And yes, i already noticed several times that Whoop doesnt sync the real timezone immediately, but anyway its not my case.
The next night alarm woke me up at 6am. So basically i cant use it at all
I tried to clear all data in Whoop app, but it didnt help.
I think Whoop is trying to use my timezone (Kazakhstan/Almaty UTC+5) with wrong offset (UTC+6).
Well, its definitely a bug - when i set Kazakhstan/Aktobe (GMT+5) on my phone, Whoop displays local time correctly, but when i change timezone to Kazakhstan/Almaty (also GMT+5), Whoop adds +1hr offset.
For a year we have single timezone in Kazakhstan, which is GMT+5
