Around 2:30am PDT we rolled out an update to our content API. That deploy contained a regression that affected certain requests to our content API that contained targeting parameters. This could result in content being returned that did not match the specific query. Once the regression was recognized, we rolled back the update to fix the issue at 10:08am PDT.