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.
19 Comments - Last post 21 minutes ago by Foxhack
52 Comments - Last post 2 hours ago by zenarcher
42 Comments - Last post 3 hours ago by Roguedust
5 Comments - Last post 3 hours ago by solodolo1337
13 Comments - Last post 3 hours ago by Fluffster
54 Comments - Last post 6 hours ago by macgamer
93 Comments - Last post 6 hours ago by adambiser
33 Comments - Last post 35 minutes ago by BreadMan
120 Comments - Last post 36 minutes ago by kctan
831 Comments - Last post 1 hour ago by alelau5
5,769 Comments - Last post 1 hour ago by holycate
15,229 Comments - Last post 1 hour ago by Carenard
486 Comments - Last post 1 hour ago by Fitz10024
19 Comments - Last post 1 hour ago by funnyduck99
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.