Malformed JSON files

We have deployed a fix for the issue that was causing JSON log files to be written in a malformed format, and have confirmed that everything is operating as expected.

The issue was active from approximately 1:30 PM ET until the fix was fully deployed to all customers around 6:30 PM ET. During this time, malformed log files were not ingested, which may have temporarily impacted downstream detections or processing.

We believe the affected data can be safely reingested and are currently evaluating the best approach. We will follow up with an additional update once the reingestion plan is finalized.

Thank you for your patience as we work through this.

We have identified the root cause of this malformed JSON log issue and are deploying a fix across customer accounts now.

We will follow up as soon as we confirm that the issue has been resolved.

We are currently investigating an issue where some JSON log files are being written in a malformed state. This may impact log ingestion and downstream detections and searches that rely on these files.

We will update this incident as our investigation and remediation process continues.