Virtru Outage History

We've recieved some reports of users being unable to login to the Virtru Control Center. Impacted users get stuck in a login loop and end up back on the login page even after successfully authenticating. The issue is only present when logging into the Control Center and is not impacting all users. If you are impacted, please clear your cache and try again. That has resolved the issue for some users. Our team is working to implement a fix. We will provide another update as soon as we have one.

We are continuing to work on a fix for the issue.

The issue has been identified and a fix is being implemented. We will provide another update as soon as possible.

We are continuing to work on getting a fix out as soon as possible.

We are continuing to work on getting a fix out as soon as possible. Impacted users should authenticate via one-time verification link or code.

We've received reports of Secure Replies sent by the O365 add-in not displaying fully. Our team has identified the issue and is actively working to patch it. No other Virtru products are impacted. We will provide another update as soon as we have one.

Microsoft is experiencing an outage that is impacting Outlook OWA (and possibly Desktop). Users are reporting intermittent issues accessing OWA. The outage seems to also prevent all Add-ins (including Virtru) from loading. As a result of this upstream issue with Microsoft, users may be unable to access Virtru in Outlook. No other Virtru products are impacted at this time. We are closely monitoring the situation.

We continue to monitor the Microsoft outage. More information can be found here: https://azure.status.microsoft/en-gb/status

We've received reports of users unable to activate Google email accounts in the Virtru for iOS app. We are actively working to resolve this issue and will provide another update as soon as possible. No other products or types of accounts are impacted at this time.

We are continuing to work on a fix for this issue. We will provide another update as soon as we have one.

We've deployed a potential fix and are awaiting Google approval. We are doing everything we can to get the approval expedited. We will provide another update by tomorrow morning (Tuesday, August 26th) unless we have one sooner.

We’ve received reports of some system-generated emails from Virtru.com not being delivered. Most traffic is going through successfully, but it appears Barracuda is rejecting some of these messages. We’ve reached out to Barracuda to get this resolved as quickly as possible. If you are a Barracuda customer, we also recommend opening a ticket with them: https://www.barracuda.com/support/contact This issue primarily impacts email activation/verification for client-side Virtru products (Gmail Extension, Secure Reader, Outlook Add-in & Control Center) as well as Secure Share emails. We’ll continue to provide updates as we have them.

We are continuing to investigate the issue while we wait to hear back from Barracuda.

We are continuing to investigate the issue and explore alternate solutions while waiting to hear back from Barracuda. We'll provide another update in the morning (EST) at the latest.

Google Cloud (GCP) appears to be experiencing a major outage upstream of Virtru. Virtru leverages GCP for various services and functionality. We are currently assessing the impact to Virtru services and will provide another update as soon as we have one.

We've observed degraded performance on the following products: - Virtru Hosted Gateway - Audit - Secure Share (History page) - Control Center (My Data and Org Data Pages) - "Sign in with Google" when authenticating into Virtru products Google has formally acknowledged the incident and is posting updates here: https://status.cloud.google.com/ We will continue to provide updates as soon as we have them.

Please note: Emails are still not being delivered and are being held in a message queue. We're working to resolve this. We will continue to update as things progress.

We're also seeing sporadic errors when decrypting Secure Share files. We are actively working to resolve the issue