Endpoint Detection and Response Process Lineage and Incident Data Issue

The issue with Process Lineage and Incident data has been addressed. This incident is now resolved.

We are continuing to monitor the service after the fix was implemented and backlog is now clearing. New requests will complete as expected.

We are closely monitoring the service and will provide update as soon as new information becomes available.

As of 22:00 UTC, we have deployed a fix. Previously generated backlogs have started processing. Backlog processing is expected to take approximately 8 hours to catch up.

We are closely monitoring the service and will provide an update as soon as new information is available.

We are still working on finalizing the production deployment. We will provide an update as soon as new information is available.

We have completed the required testing in QA environment and are in the process of preparing for production deployment.

We will provide an update as soon as new information is available. No other aspect of the service is impacted by this issue.

We continue to work on a fix. Impacted customers may experience slowness while creating incidents and lineage.

We will provide an update as soon as new information is available.

We are continuing to validate the fix through testing and will provide an update when new information becomes available.

We have identified a fix and currently testing to confirm this fixes the issue. Once the fix has been tested and passed validation we will provide an update.

As a reminder this is impacting Endpoint Detection and Response Process Lineage and Incident data. Impacted customers may experience slowness while creating incidents and lineage.

We are currently investigating an issue with Endpoint Detection and Response Process Lineage and Incident data. Impacted customers may experience slowness while creating incidents and lineage.

We have identified the cause of this issue and are working on a fix. We will provide an update as soon as new information is available. No other aspect of the service is impacted by this issue.