Conflicts Partial Outage – All Regions - New Search Creation Unavailable

Status: Resolved

Summary: Conflict searches were failing due to a third-party service disruption (LaunchDarkly) that began on July 10, 2026.

What happened:
Our feature flag provider, LaunchDarkly, experienced a global service outage beginning at approximately 12:16 PM EDT on July 10. During this outage, their servers returned authentication errors (HTTP 401) to all connected applications. The LaunchDarkly server-side SDK used by the Conflicts search processing service entered a permanent error state and was unable to self-recover once LaunchDarkly restored service.

Resolution:
All affected application services were restarted across all regions, re-establishing connections to LaunchDarkly. Normal search operations were fully restored by approximately 8:00 PM EDT July 10. . No data was lost, any searches that failed during the incident can be re-run successfully.

**Monitoring** - We have identified that the issue preventing new searches from being created appears to be related to continued impact from a previous LaunchDarkly incident affecting SDK and flag delivery evaluations.

We have re-established the impacted connections and are monitoring the environment to confirm that new search creation remains stable. Customers may begin seeing recovery, though some intermittent impact may continue while monitoring is in progress.

We will provide another update once stability has been confirmed.

We are continuing to investigate this issue.

We are currently investigating an issue preventing new searches from being created.

Existing searches and previously created search results remain available. At this time, the impact appears limited to the creation of new searches only.

Our team is actively investigating the cause and working to restore normal functionality as quickly as possible. We will provide an update as soon as more information is available.

Thank you for your patience.