This problem appears to be resolved now (the one hour gap is gone).
Starting to question my sanity, since no one really commented here about having the same issues.
But I'd rather think it was a prompt and silent server-side fix (and my ineptitude in attracting public's attention -- only a few would read further with such a poorly-chosen title wording). Many thanks!
The giveaway is still on, though.
Comment has been collapsed.
5 Comments - Last post 49 minutes ago by yush88
30 Comments - Last post 2 hours ago by cpyd
4 Comments - Last post 2 hours ago by Lugum
25 Comments - Last post 2 hours ago by JHartmann
1,038 Comments - Last post 4 hours ago by sensualshakti
43 Comments - Last post 4 hours ago by ZPE
9 Comments - Last post 4 hours ago by Sh4dowKill
8 Comments - Last post 4 minutes ago by Naviis
461 Comments - Last post 6 minutes ago by ClapperMonkey
200 Comments - Last post 9 minutes ago by schmoan
34 Comments - Last post 31 minutes ago by hbarkas
87 Comments - Last post 38 minutes ago by Lugum
2,074 Comments - Last post 39 minutes ago by Daniellejake
371 Comments - Last post 41 minutes ago by VladislavDracula
The only relevant discussion I found in this category was closed a while ago, but the problem is still ongoing (for me at least).
I know for sure that the timezone is set correctly on the system, and multiple websites detect it properly (by offset).
However, the SG account page, while recognizing the timezone itself, applies an incorrect offset when returning the value.
This does appear to be caused
by the messed up Russian legislationby an outdated TZ database, as currently the site behaves as if Moscow has the eternal summer going on, whereas (starting from Oct 26 of 2014) it is now actually winter all year round.Whenever I try to create a giveaway, and set the start time to "Now", SG detects the local time correctly, but immediately after this does not allow saving or reviewing the GA, claiming that "Giveaway must start after the current time" (see the attached image). It goes through only if I add an extra hour. This only started after the SGv2 update.
Comment has been collapsed.