This incident has been resolved.

We released some improvements to how we load configuration for our services, but unfortunately our detections scheduler had a JSON unmarshaling error that was uncaught in testing. We're adding tests to ensure this doesn't happen again.

Current detections would be delayed at most one hour. A release fixing the issue has been deployed and we're now caught up again.