At 8:03am EST, we pushed an API update. Very quickly we realized we had an issue with the API update and began the process to roll it back. The update was rolled back, fixing the issue at 8:35am EST, but there was some caching that caused the issue to linger longer for some users, potentially as long as 8:55am EST.
