Yes, it was a timezone bug. The page was tracking January 20 (but at midnight in UTC timezone), so some people would see Jan 19, some Jan 20. It's now fixed.