Xink incident
Xink Add-in - Signature is showing details of other users
Xink experienced a notice incident on February 14, 2023 affecting Outlook Add-in, lasting 6h 15m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Feb 14, 2023, 08:23 AM UTC
Some clients have reported that their signatures are showing an information of another user from another company
- investigating Feb 14, 2023, 12:31 PM UTC
We are continuing to investigate this issue.
- investigating Feb 14, 2023, 12:31 PM UTC
We are continuing to investigate this issue.
- identified Feb 14, 2023, 12:36 PM UTC
The issue has been identified and a fix is being implemented. We disabled add-in while we working on implementation.
- resolved Feb 14, 2023, 02:38 PM UTC
This incident has been resolved.
- postmortem Feb 15, 2023, 02:13 PM UTC
## RCA **What happened?** During a high load pick hours add-in instance were scaled up to add more instances to optimize performance. Add-in were not prepared to handle multiple connections and caused two random signatures to show for some users in their outlook. We identified these two user signatures, and no one else are affected. **How did we respond?** For better performance we upgraded dependencies to the latest and stable version of .NET6. We implemented multiple instances to handle high loads. We made a several changes to add-in codebase to make connections properly disposed of between user sessions to eliminated other signatures sync. **How do we improve and prevent this in the future?** We add additional test frameworks and more emphasis on QA.