18Oct/11
On Wednesday Oct 19 at 12.00 GMT we will update the code responsible for time zone management in Scalr. After this update, all previous log, instance launch, and event timestamps will appear in an incorrect (but consistent) time zone.
By now, you are probably thinking “why on earth are they doing this?”. One of the problems you’ve probably encountered (we have!) using Scalr is that timestamps from different sources use different timezones. Instance launch time might use local time, but logs collected might be remote (thus depending on the server’s location). This makes it difficult to troubleshoot problems.
With this update, we’re converting every timestamp to a single local timezone, and the UI will be in charge of converting it to the timezone of your choice.
We expect this to be completed in the next 5-7 days.