@mediatemple Had same problem before. Enabling WP Super Cache seemed to fix it. This seems to be result of a recent (other) plugin update.