Our latest database server update decided to play a little game with us, as it would sometimes use an incorrect timezone setting for some of the queries... which means that sometimes the codebase and the database server disagreed about the current time to the tune of 4 hours.

While the rest of the server infrastructure knew it was supposed to run on New York time, the database server sometimes mistakenly hopped over to the default UTC (+0 offset) and introduced a couple of glitches into our API system.

Now that we've localized (heh) the source of the issue, we're already working on a resolution and everything should be back to normal quickly.

Published on: July 27th, 2018

← Previous: Big things coming!

→ Next: Minor API issues... (RESOLVED!)