Entrepreneur. Programmer. Absolutely in love with life.
As explained in our other API post from earlier today, we were noticing a sporadic 4-hour time difference between our primary server infrastructure and our API database servers, which was due to a recent update of our database servers.
This issue has now been fully resolved, which also means that the Spin Rewriter API is working flawlessly once again. Hooray! 😀
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.