Virtru Platform Status Page

Apr 2, 2026 · resolved Apr 3

The issue is resolved. Affected users should clear cache and try again.

Mar 12, 2026 · resolved Mar 13

This issue has been resolved. We will post a root cause analysis in the next few days. Thanks for your patience while we worked to resolve this.

Jan 28, 2026 · resolved Feb 5

Deliverability is back to normal levels. If users/recipients do not receive their verification emails we encourage them to still check quarantine, spam, etc.: https://support.virtru.com/hc/en-us/articles/360000459634-Not-receiving-verification-email If the message cannot be found, they should contact Support at https://support.virtru.com/hc/en-us

Jan 22, 2026 · resolved Jan 23

Microsoft has resolved their issue, and emails are delivering as expected.

Nov 21, 2025 · resolved Nov 21

On November 21, 2025, Virtru experienced a brief outage impacting all services. At 20:09 UTC our monitoring alerted us that all applications and APIs were unavailable. Virtru users received “network or service unavailable” error messages for the duration of the outage, which lasted less than 30 minutes. ‌ **What Happened** The outage was caused by a malformed policy that was applied to our runtime protection tool, which protects running workloads from a variety of risks, including enforcing a DNS query allow list. This bad policy blocked a majority of DNS traffic and caused enforcement of the policy to be applied to a majority of pods across all of our clusters.  ‌ **How Virtru Responded** The policy was reverted immediately; however, it was so restrictive that the sensors could not connect back to receive the update. This required additional remediation efforts by Virtru to manually destroy the old policy, resync the good policy, and cycle all the pods. For most of our services, this meant that all functionality was fully restored at 20:38 UTC. All customer data remained secure throughout the duration of the outage. ‌ **Next Steps** We are taking steps to protect ourselves from events like this reoccurring in the future. We will be investigating and implementing controls to: * Automate policy validation to ensure that malformed rules cannot be pushed to production * Create more robust internal scoping policies to prevent malformed rules from propagating globally across our infrastructure * Improving emergency access for redundancy to speed up response times We understand that our customers rely on Virtru for critical security and privacy functions, and we take both this incident and your trust seriously. If you have questions about this incident or experienced specific issues, please contact our support team at [[email protected]](mailto:[email protected]).