VIPRE Outage History

Started Oct 15, 2026, 01:02 PM UTC· resolved Oct 15, 2026, 03:38 PM UTC

1. investigating Oct 15, 2026, 01:02 PM UTC

   We have been alerted to an issue affecting some customers logging in to View Archive with SSO. We are working with the Archiving Team to investigate and resolve as soon as possible. Archiving of emails is unaffected, and emails are being processed into the archive as normal.

2. monitoring Oct 15, 2026, 02:40 PM UTC

   Our Archiving Team have diagnosed the problem, and have issued a fix for customers encountering issues logging in to View Archive via SSO. We continue to monitor in the meantime but if you have any questions, please don’t hesitate to reach out to the Support Team. Journaling of emails remains unaffected and emails are indexing into the archive as normal.

3. resolved Oct 15, 2026, 03:38 PM UTC

   The issue for logging in to View Archive via SSO that affected some customers, is now fully resolved. If you still experience an issue or require further support, please don’t hesitate to reach out to our Support Team.

Read the full incident report →

Started Oct 13, 2026, 09:24 AM UTC· resolved Oct 16, 2026, 07:04 AM UTC

1. investigating Oct 13, 2026, 09:24 AM UTC

   We are currently investigating an issue affecting some emails sent from e-Boks that affects a small subset of customers. Our team is actively working on a resolution. This issue is isolated exclusively to some encrypted e-Boks messages being unable to be decrypted; all other email processing continues normally. All affected emails are safely retained, and you will be able to replay them once a fix has been implemented.

2. investigating Oct 13, 2026, 12:34 PM UTC

   Our development team is currently testing a fix internally for the issue affecting emails sent from e-Boks for a small subset of customers. This issue remains isolated exclusively to some encrypted e-Boks messages being unable to be decrypted; all other email processing continues normally. All affected emails are safely retained, and you will be able to replay them once the fix has been implemented.

3. investigating Oct 13, 2026, 02:51 PM UTC

   Our development team are continuing to test a fix for the issue affecting emails sent from e-Boks for a small subset of customers. This issue remains isolated exclusively to some encrypted e-Boks messages being unable to be decrypted; all other email processing continues normally. All affected emails are safely retained, and you will be able to replay them once the fix has been implemented.

4. investigating Oct 15, 2026, 07:15 AM UTC

   Our development team have solved the issue affecting emails sent from e-Boks for a small subset of customers, However before it can be released it needs to go through QA. We expect the release to go out as soon as possible. This issue remains isolated exclusively to some encrypted e-Boks messages being unable to be decrypted; all other email processing continues normally. All affected emails are safely retained, and you will be able to replay them once the fix has been implemented.

5. monitoring Oct 15, 2026, 07:06 PM UTC

   We have now implemented the fix for some encrypted e-Boks messages being unable to be decrypted. All affected emails are safely retained, and you will be able to replay them. We will continue to monitor, and if you have any queries or issues, please don’t hesitate to reach out to our Support Team.

6. resolved Oct 16, 2026, 07:04 AM UTC

   We have confirmed the implemented the fix for some encrypted e-Boks messages being unable to be decrypted and the issue is now resolved. All affected emails are safely retained, and you will be able to replay them. We will continue to monitor, and if you have any queries or issues, please don’t hesitate to reach out to our Support Team.

Read the full incident report →

Started Sep 08, 2026, 10:55 AM UTC· resolved Sep 08, 2026, 04:54 PM UTC

1. investigating Sep 08, 2026, 10:55 AM UTC

   We are experiencing some email processing delays for VIPRE IES up to 8 minutes in length. This is affecting a small subset of customers at this time. We are currently investigating the delay and working on a resolution. Emails are delivering as normal once processed through VIPRE.

2. monitoring Sep 08, 2026, 12:35 PM UTC

   The issue for IES with email processing delayed by 8 minutes for a small subset of customers is now resolved. We remain in monitoring mode for a short time. Messages delivered as normal after the short delay, and mail flow is back to normal levels. If you have any questions, please don’t hesitate to reach out to our support team.

3. resolved Sep 08, 2026, 04:54 PM UTC

   The issue for IES with email processing delayed by 8 minutes for a small subset of customers is resolved. Messages delivered as normal after the short delay, and mail flow is back to normal levels. If you have any questions, please don’t hesitate to reach out to our support team.

Read the full incident report →

Started Sep 04, 2026, 09:34 AM UTC· resolved Sep 04, 2026, 08:11 PM UTC

1. investigating Sep 04, 2026, 09:34 AM UTC

   We are investigating delays in email delivery to and from Microsoft 365 tenants. Users may experience slower than normal sending and receiving of messages involving Microsoft 365 addresses. No email has been lost. Affected messages are queued on our mail servers and will be delivered automatically once delivery times return to normal. Current indications point to an issue within Microsoft 365’s infrastructure, outside our platform. We are monitoring Microsoft’s service health reports and will update this page as more information becomes available.

2. investigating Sep 04, 2026, 10:33 AM UTC

   We are monitoring delays in email delivery to and from Microsoft 365 tenants. Users may experience slower than normal sending and receiving of messages involving Microsoft 365 addresses. Microsoft 365 is also investigating the issue at themselves, their internal issue ID is EX1467029 No email has been lost. Affected messages are queued on our mail servers and will be delivered automatically once delivery times return to normal. Current indications point to an issue within Microsoft 365’s infrastructure, outside our platform. We are monitoring Microsoft’s service health reports and will update this page as more information becomes available.

3. investigating Sep 04, 2026, 11:07 AM UTC

   We have found if customers who are affected by this issue follow our guide for creating a inbound connector, the problem may be solved within 10-30 minutes of creation. Please follow the guide found here https://helpdesk.vipre.com/hc/en-us/articles/360007336418-Office-365-Receive-connector. In the meantime we will continue to monitor the delays in email delivery to and from Microsoft 365 tenants. We are monitoring Microsoft’s service health reports and will update this page as more information becomes available.

4. investigating Sep 04, 2026, 11:44 AM UTC

   We have found that affected customers can resolve the issue by creating an inbound connector in Microsoft 365. Where this has been applied, delivery typically returns to normal within 10–30 minutes. If you have previously configured a connector, please check it first — we are seeing cases where existing Microsoft 365 connectors have since been disabled. Re-enabling the connector may resolve the issue without further changes. If you do not have a connector configured, follow our setup guide: https://helpdesk.vipre.com/hc/en-us/articles/360007336418-Office-365-Receive-connector In the meantime, we continue to monitor delivery delays to and from Microsoft 365 tenants alongside Microsoft’s service health reports, and will update this page as more information becomes available.

5. monitoring Sep 04, 2026, 01:42 PM UTC

   We are seeing emails being delivered to microsoft, and we are still monitoring the progress of the incident. We still urge affected customers to create an inbound connector in Microsoft 365 as this can prevent this issue from happening in the future. If you do not have a connector configured, follow our setup guide: https://helpdesk.vipre.com/hc/en-us/articles/360007336418-Office-365-Receive-connector In the meantime, we continue to monitor delivery delays to and from Microsoft 365 tenants alongside Microsoft’s service health reports, and will update this page as more information becomes available.

6. monitoring Sep 04, 2026, 02:45 PM UTC

   We are seeing emails successfully delivering to Microsoft 365, and our team continues to closely monitor overall incident resolution. We strongly encourage affected customers to configure an inbound connector in Microsoft 365 to help prevent future delivery disruptions. You can follow our step-by-step setup guide here: Office 365 Receive Connector Guide. In the meantime, we are actively tracking delivery delays alongside Microsoft’s service health reports. We will provide further updates as new information becomes available.

7. monitoring Sep 04, 2026, 04:31 PM UTC

   We are seeing emails successfully delivering to Microsoft 365, though some delivery delays persist. Our team continues to closely monitor overall incident resolution. We strongly encourage affected customers to configure an inbound connector in Microsoft 365 to help prevent future delivery disruptions. You can follow our step-by-step setup guide here: Office 365 Receive Connector Guide. In the meantime, we are actively tracking delivery delays alongside Microsoft’s service health reports and will provide further updates as new information becomes available.

8. resolved Sep 04, 2026, 08:11 PM UTC

   Emails are now delivering normally to Microsoft 365, and delivery delays have fully cleared. Our team has verified that mail flow metrics and queue processing times have returned to baseline levels. To help prevent similar delivery disruptions in the future, we strongly recommend that affected customers configure an inbound connector in Microsoft 365. You can follow our step-by-step instructions in the Office 365 Receive Connector Guide.

Read the full incident report →

Started Aug 31, 2026, 06:44 PM UTC· resolved Sep 04, 2026, 01:33 PM UTC

1. investigating Aug 31, 2026, 06:44 PM UTC

   Our team has identified that this degradation stems from an issue within Microsoft’s underlying Exchange Online environment. Microsoft’s technical teams are actively investigating the root cause, and we are monitoring their progress closely to ensure services are restored as quickly as possible. We will provide another update as soon as new information becomes available from Microsoft. Thank you for your patience.

2. resolved Sep 04, 2026, 01:33 PM UTC

   Issue is marked as resolved.

Read the full incident report →

Started Jul 08, 2026, 02:29 PM UTC· resolved Jul 15, 2026, 12:11 PM UTC

1. investigating Jul 08, 2026, 02:29 PM UTC

   VIPRE Integrated Email Security is currently experiencing an issue loading data. Our engineering team is actively investigating the problem and working to restore normal service. We will provide an update as soon as more information becomes available.

2. investigating Jul 08, 2026, 04:37 PM UTC

   The UI error has been resolved. However, some customers may still experience issues when viewing message details.Our Engineering team is actively investigating the remaining issue to reach a full resolution. We are closely monitoring system performance.

3. monitoring Jul 08, 2026, 06:42 PM UTC

   Message Details has been confirmed to be operating normally in both regions. We will continue to monitor the service and provide updates if there are any changes.

4. investigating Jul 08, 2026, 08:25 PM UTC

   We are investigating an issue affecting message log processing. Message delivery is operating normally and is not impacted. Customers in North America (NA) and Europe (EU) may experience delays in message logs. Our team is actively working to resolve the issue and restore normal log processing. We will provide another update as soon as more information becomes available.

5. monitoring Jul 09, 2026, 12:33 AM UTC

   A fix has been deployed to the North America (NA) and Europe (EU) regions. We are currently monitoring the service to ensure message log processing has returned to normal and that the issue is fully resolved.

6. resolved Jul 15, 2026, 12:11 PM UTC

   This issue is fully resolved following a monitoring period. If further assistance is still requird, please don’t hesitate to reach out to the Support team.

Read the full incident report →

Started May 08, 2026, 06:24 PM UTC· resolved May 11, 2026, 08:57 PM UTC

1. monitoring May 08, 2026, 06:24 PM UTC

   Users may experience intermittent failures when attempting to connect to their Exchange mailboxes. Summary of Issue: Some users are experiencing connectivity issues due to external ISP routing failures. All internal systems and Exchange services remain fully operational. Technical Details: Our investigation has confirmed that all Exchange servers and internal services are functioning normally. The connectivity disruptions are occurring outside of our network and appear to be isolated to Verizon’s routing infrastructure. Specifically, traffic originating from Verizon is failing to reach our Colorado database clusters. We are continuing to monitor the situation closely and will provide additional updates as more information becomes available.

2. resolved May 11, 2026, 08:57 PM UTC

   The routing issue has now been resolved.

Read the full incident report →

Started Apr 30, 2026, 08:15 AM UTC· resolved Apr 30, 2026, 07:30 PM UTC

1. investigating Apr 30, 2026, 08:15 AM UTC

   We are currently investigating an issue affecting a small subset of customers who are unable to send SecureMail messages. Receiving SecureMail messages is unaffected at this time. Our team is actively working to identify the root cause with the highest priority, and we will provide further updates here as our investigation continues.

2. investigating Apr 30, 2026, 09:20 AM UTC

   We are still investigating an issue affecting a small subset of customers who are unable to send SecureMail messages. Receiving SecureMail messages is still unaffected. Our team is actively working to identify the root cause with the highest priority, and we will provide further updates here as our investigation continues.

3. investigating Apr 30, 2026, 12:55 PM UTC

   We have now identified the root cause of the issue affecting a subset of customers from sending SecureMail messages, and they are actively working on implementing a fix. The receiving of SecureMail message’s is remains unaffected. We will continue to provide updates here as progress is made.

4. resolved Apr 30, 2026, 07:30 PM UTC

   The issue affecting a subset of customers who were unable to send SecureMail messages has been fully resolved. SecureMail sending functionality has been restored and is operating normally. Thank you for your patience while we worked to resolve this issue.

Read the full incident report →

Started Mar 18, 2026, 01:58 AM UTC· resolved Mar 18, 2026, 02:56 AM UTC

1. investigating Mar 18, 2026, 01:58 AM UTC

   We are currently investigating a webmail delivery issue. Message Logs indicate that emails are being processed and marked as Allowed and Delivered, but they are not reaching the intended recipients’ inboxes. We are actively working to identify the root cause and will provide updates as more information becomes available.

2. monitoring Mar 18, 2026, 02:18 AM UTC

   The issue impacting webmail delivery has been mitigated. Deliveries should now be reaching recipients’ inboxes as expected. We are continuing to monitor the situation to ensure stability.

3. resolved Mar 18, 2026, 02:56 AM UTC

   The issue affecting webmail delivery has been resolved, and email deliveries are now reaching inboxes as expected.

Read the full incident report →

Started Mar 02, 2026, 10:19 AM UTC· resolved Mar 02, 2026, 01:38 PM UTC

1. investigating Mar 02, 2026, 10:19 AM UTC

   Status Update: Investigating Message Log Discrepancies (EMEA) Current Status: Investigating 🔍 We are currently investigating reports of an issue affecting Message Logs specifically for customers within the EMEA region. Users may encounter error messages or find that log data is failing to populate within the admin dashboard. Key Details Symptoms: “Error fetching data” alerts or empty results when querying message history. Scope: This is confined to customers hosted in our EMEA data centers. Mailflow: Confirmed healthy; no impact on email delivery or security filtering. We appreciate your patience while we restore full visibility.

2. investigating Mar 02, 2026, 11:04 AM UTC

   Current Status: Investigating (High Priority) 🔍 Region: EMEA Only We are continuing to treat reports of Message Log errors and data population issues as a high-priority investigation. Our engineering teams are actively working to restore log visibility for customers in the EMEA region. It is important to emphasize that there is no impact to core services: Mailflow: Emails are being processed, sent, and received normally. Security Enforcement: All security filtering, scanning, and protection protocols remain fully active and unaffected. We appreciate your continued patience as we work to resolve this reporting-only issue.

3. monitoring Mar 02, 2026, 11:45 AM UTC

   ✅ Resolved: Message Log Discrepancies (EMEA) Current Status: Resolved 🟢 Region: EMEA Only The issue affecting Message Logs for customers in the EMEA region has been resolved. Log data is now populating correctly, and the errors previously encountered in the dashboard have been cleared. 🟢 Service Status: Fully Operational As previously noted, mailflow and security enforcement remained fully functional throughout this event. Summary Current Status: Service Restored. Monitoring: Our engineering teams are continuing to monitor the reporting cluster closely to ensure stability across the EMEA region. Impact: Visibility only; no emails were delayed or missed. Thank you for your patience while we restored full reporting visibility.

4. resolved Mar 02, 2026, 01:38 PM UTC

   The issue affecting Message Logs for customers in the EMEA region has been resolved. The errors previously encountered in the dashboard have all been cleared.

Read the full incident report →

Started Feb 04, 2026, 11:50 AM UTC· resolved Feb 26, 2026, 03:30 PM UTC

1. investigating Feb 04, 2026, 11:50 AM UTC

   We are currently investigating reports from customers experiencing an authentication loop when attempting to log in to the Search UI on the EU1 instance of VIPRE Archive. Users may find themselves redirected back to the login screen repeatedly after authentication with the IDP. Our engineering team is actively identifying the root cause—initial signs point to a potential session synchronisation issue on the EU1 cluster. What this means for you: Affected: Customers hosted on the EU1 instance attempting to access the Search UI. Not Affected: Archive ingestion, mail flow, and other regional instances (US/APAC) remain fully operational. We apologise for the interruption and will provide an update as soon as we have more information or a workaround.

2. monitoring Feb 04, 2026, 01:31 PM UTC

   Incident Resolved: Login Issues - EU1 Instance Status: Resolved Components Affected: Search UI (EU1 Instance) ✅ Service Update: Resolution Confirmed The authentication loop affecting the EU1 Search UI has been resolved. Our engineering team has implemented a fix, and all login services are now operating normally. Troubleshooting If you continue to experience login issues, please perform a hard reset of your browser session data: Open your browser’s F12 Developer Tools. Select the Application tab (or Storage in Firefox). Select Clear Site Data. Refresh the page and attempt to log in again. Access Links Please ensure you are accessing the correct interface via the links below: Admin UI: https://[CustomerTag].control.eu1.archive.mailanyone.net Search UI: https://[CustomerTag].outlook.eu1.archive.mailanyone.net Classic Search UI: https://www.eu1.archive.mailanyone.net/vipre/[CustomerTag] We apologize for any inconvenience caused and appreciate your patience.

3. resolved Feb 26, 2026, 03:30 PM UTC

   This has now been resolved

Read the full incident report →