Veeam Outage History

Started Oct 13, 2026, 06:06 PM UTC· resolved Oct 14, 2026, 09:36 PM UTC

1. investigating Oct 13, 2026, 06:06 PM UTC

   We are investigating backup failures affecting OneDrive, SharePoint, and Teams across Veeam Data Cloud for Microsoft 365. Affected backups may fail with an “Unknown Error.” Our engineering teams are working with Microsoft to mitigate this issue.

2. identified Oct 13, 2026, 08:25 PM UTC

   Our engineering team has engaged Microsoft Support, who confirmed that the backup failures are related to a recent change within Microsoft’s services. Microsoft is actively working to resolve the issue. We will provide another update when additional information becomes available.

3. resolved Oct 14, 2026, 09:36 PM UTC

   Microsoft has deployed a fix for the issue that caused some OneDrive, SharePoint, and Teams backups to fail with an “Unknown Error” in Veeam Data Cloud for Microsoft 365. We have confirmed that service functionality has recovered, and this incident is now resolved. If you experience any further issues, please contact Veeam Support.

Read the full incident report →

Started Oct 09, 2026, 03:46 PM UTC· resolved Oct 14, 2026, 04:52 PM UTC

1. investigating Oct 09, 2026, 03:46 PM UTC

   We have identified an increase in transient mailbox backup failures across multiple tenants. We have engaged Microsoft and our team is investigating the errors at this time.

2. monitoring Oct 09, 2026, 11:35 PM UTC

   Mailbox backup errors have decreased, and services are showing signs of recovery. We will continue to monitor service health throughout the weekend to ensure continued stability.

3. resolved Oct 14, 2026, 04:52 PM UTC

   We have observed no further errors, and mailbox backup services have remained stable. This issue is now considered resolved. Please contact Veeam Support if you experience any further issues.

Read the full incident report →

Started Sep 16, 2026, 03:26 PM UTC· resolved Sep 16, 2026, 03:26 PM UTC

1. resolved Sep 16, 2026, 03:26 PM UTC

   On September 16 from 7:50 AM to 15:26 UTC, some customers may have experienced failures when requesting Veeam Backup and Replication tokens, including 503 Service Temporarily Unavailable responses. Our investigation confirmed the issue was caused by a widespread Salesforce service incident that impacted Salesforce API availability, which is used as part of product installation validation. Once Salesforce resolved the incident, normal service operation was restored.

Read the full incident report →

Started Aug 19, 2026, 02:57 PM UTC· resolved Aug 19, 2026, 06:31 PM UTC

1. investigating Aug 19, 2026, 02:57 PM UTC

   M365 Self-Service

2. identified Aug 19, 2026, 03:26 PM UTC

   We've identified a race condition regarding CDN resources specifically affecting M365 Self-Service Restore portal logins in the Asia-Pacific region. No admin users are affected nor any other functionality.

3. identified Aug 19, 2026, 04:27 PM UTC

   Updating the incident to show that this is affecting all regions, not only Asia Pacific

4. monitoring Aug 19, 2026, 05:00 PM UTC

   Workaround identified: Self-Service users may directly go to https://cloud.veeam.com/m365 to perform self-service restores.

5. resolved Aug 19, 2026, 06:31 PM UTC

   The fix has been deployed and we have confirmed that M365 Self-Service Restore users can access the portal again. This issue is resolved.

Read the full incident report →

Started Jul 24, 2026, 09:02 PM UTC· resolved Jul 30, 2026, 06:51 PM UTC

1. investigating Jul 24, 2026, 09:02 PM UTC

   We are investigating an issue affecting multiple Microsoft 365 tenants where SharePoint sites and other items may not appear or update as expected when customers create or edit granular backup policies. Our engineering team is working with Microsoft, who has reverted a change that led to this degradation. We are monitoring the system to ensure these issues subside and will provide updates as more information is available.

2. monitoring Jul 28, 2026, 06:02 PM UTC

   Microsoft has rolled back a change that was contributing to system stability issues affecting Microsoft 365 organization data updates and item selection when creating or editing granular backup policies. Since the rollback, we have observed improvements in system behavior. Our engineering team will continue to monitor the system closely for any further issues and will provide additional updates as needed.

3. resolved Jul 30, 2026, 06:51 PM UTC

   Our engineering team has observed significant improvements to system health since Microsoft performed the rollback. We have not observed any further widespread impact related to this issue. If you experience any further issues, please reach out to support.

Read the full incident report →

Started Jul 24, 2026, 05:48 PM UTC· resolved Jul 29, 2026, 06:05 PM UTC

1. monitoring Jul 24, 2026, 05:48 PM UTC

   We are monitoring an issue where a subset of backup jobs for SharePoint Online and OneDrive may fail with the error “Cannot complete this action.” Our investigation indicates this behavior is related to a recent change made by Microsoft. We are working with Microsoft to mitigate the impact and have implemented the recommended fix. We are now monitoring the system to confirm whether the fix has improved job reliability and will provide further updates as more information becomes available.

2. monitoring Jul 28, 2026, 04:08 PM UTC

   Since applying the recommended fix on July 24, we have observed significant improvements in overall system health and backup job reliability for SharePoint Online and OneDrive. Our engineers continue to monitor the environment closely and are working with Microsoft to resolve a small number of remaining minor issues. We will continue to provide updates as additional progress is made.

3. resolved Jul 29, 2026, 06:05 PM UTC

   Since applying the recommended hotfix on July 24th, we have continued to see significant improvements in system health and backup job reliability for SharePoint Online and OneDrive. Our monitoring confirms that the issue has been mitigated, and we are no longer observing widespread impact related to the previously reported failures. Please reach out to support if you experience any further issues.

Read the full incident report →

Started Jul 23, 2026, 05:13 PM UTC· resolved Jul 23, 2026, 08:41 PM UTC

1. investigating Jul 23, 2026, 05:13 PM UTC

   Due to Azure networking issues in the West US region, some customer may experience intermittent backup and restore failures or delays. Azure has implemented mitigations and is monitoring recovery; we are continuing to assess impact and will provide updates as more information becomes available.

2. resolved Jul 23, 2026, 08:41 PM UTC

   Microsoft has mitigated the Azure issue affecting the West US region. We have confirmed that backup and restore services are now functioning as expected for customers. If you experience any further issues, please contact Support.

Read the full incident report →

Started Jul 15, 2026, 03:59 AM UTC· resolved Jul 15, 2026, 03:48 PM UTC

1. identified Jul 15, 2026, 03:59 AM UTC

   We are investigating access issues affecting the Veeam Data Cloud web UI across all production regions starting Tuesday, July 14th at 17:50 UTC. Some customers may see blank or inconsistently loading pages, including the Overview page, particularly when signing in as a new user, using an incognito/private session, or after clearing browser cache. Our engineering team has identified that some UI configuration requests are intermittently failing due to blocking by third-party network services. We are working with our providers and implementing a workaround to restore reliable access, while continuing to monitor closely and will provide updates as recovery is confirmed.

2. monitoring Jul 15, 2026, 04:37 AM UTC

   We have implemented a short-term fix to restore access to core functionality, including accessing backups and performing restores. Some UI features, such as the AI Assistant, may remain unavailable until services are fully restored with our vendor provider. We are continuing to monitor the environment and work with our vendor toward full restoration. We will provide a final update once access has been fully restored through our vendor.

3. resolved Jul 15, 2026, 03:48 PM UTC

   Our vendor partner confirmed the issue and deployed a fix to restore services. After validating service restoration, we removed the short-term workaround implemented yesterday. We have confirmed that the Overview page in the UI, along with previously impacted services such as the AI Assistant, is now fully restored. If you experience any further issues, please contact Support.

Read the full incident report →

Started Jul 03, 2026, 03:09 PM UTC· resolved Jul 03, 2026, 09:41 PM UTC

1. identified Jul 03, 2026, 03:09 PM UTC

   We're investigating an issue affecting some backups of Windows VM that use VSS. A fix has been validated and is currently being deployed to production. We'll provide another update once deployment is complete.

2. resolved Jul 03, 2026, 09:41 PM UTC

   Engineers deployed a fix and as of 21:40 UTC, we are seeing successful operations across affected services. The issue has been resolved and we are no longer observing customer impact. Please contact support if you continue to experience any issues.

Read the full incident report →

Started May 28, 2026, 05:26 PM UTC· resolved May 28, 2026, 08:28 PM UTC

1. identified May 28, 2026, 05:26 PM UTC

   Starting at 19:30 UTC on May 28, some Veeam Data Cloud for Microsoft Entra ID customers may experience service disruptions affecting backup and restore operations. Affected customers will see backup failures and may be unable to perform restores until the issue is resolved. Our engineering teams have identified the issue and are working to implement a fix, which is expected within the next few hours. We will provide updates as they become available.

2. resolved May 28, 2026, 08:28 PM UTC

   Engineers deployed a fix at 20:05 UTC on May 28 and are now seeing successful backup operations across affected services. Backup and restore functionality for Veeam Data Cloud for Microsoft Entra ID has been restored, and we are no longer observing customer impact. Please contact support if you continue to experience any issues.

Read the full incident report →

Started Mar 27, 2026, 04:00 PM UTC· resolved Apr 20, 2026, 09:56 PM UTC

1. investigating Mar 27, 2026, 04:00 PM UTC

   We are currently investigating an uptick in errors backing up Exchange Online mailboxes with the message “The HTTP request was forbidden with client authentication scheme ‘Anonymous’" with Microsoft. We will share additional information once we are able. More specific information is at https://www.veeam.com/kb4796.

2. identified Mar 30, 2026, 07:21 PM UTC

   We have identified a mitigation for the Exchange Online backup authentication errors related to Exchange Web Services (EWS) access. Backups are succeeding for customers who enable EWS at both the organization and mailbox levels and allow time for Microsoft 365 replication to complete. We continue to work with Microsoft to investigate a small number of edge cases where issues may persist, and we will provide further updates as more information becomes available. More information on the workaround can be found here: https://www.veeam.com/kb479 "https://www.veeam.com/kb4796": https://www.veeam.com/kb4796

3. monitoring Apr 01, 2026, 09:38 PM UTC

   We continue to see successful backups for customers who have applied the configuration changes outlined in our knowledge base article. Customers who have not yet made these updates should follow the guidance in the article to restore normal backup operation. Please note, due to Microsoft 365 replication timing, it may take up to 24 hours after making these changes for backups to fully return to normal. We are not observing new widespread impact at this time. Knowledge base article: https://www.veeam.com/kb4796

4. resolved Apr 20, 2026, 09:56 PM UTC

   We continue to see successful backups for customers who have applied the configuration changes outlined in our knowledge base article below. We have not observed any new recurrence of this issue. For remaining impacted customers, please refer to our Knowledge base article: https://www.veeam.com/kb4796

Read the full incident report →

Started Mar 26, 2026, 05:11 PM UTC· resolved Mar 26, 2026, 10:44 PM UTC

1. investigating Mar 26, 2026, 05:11 PM UTC

   Starting around 16:00 UTC on March 25, Veeam Data Cloud began experiencing an issue with VDC Azure tenant management for all Azure customers. During this time, customers may experience issues with loading tenant data after selecting a tenant to manage (blank page), which may require multiple refreshes to recover. Veeam engineers are actively working to resolve this issue.

2. resolved Mar 26, 2026, 10:44 PM UTC

   Between 16:00 UTC on March 25 and 17:30 UTC on March 26, Veeam Data Cloud experienced an issue with VDC Azure tenant management. During this time, customers may have experienced issues with loading tenant data after selecting a tenant to manage in OneUI (blank page), which may have required multiple refreshes to recover. Veeam engineers have mitigated the issue and confirmed that services are fully functional. Please reach out to support if you experience any further issues.

Read the full incident report →

Started Mar 20, 2026, 04:09 PM UTC· resolved Apr 20, 2026, 04:07 PM UTC

1. identified Mar 20, 2026, 04:09 PM UTC

   We have identified an issue with the Microsoft Sharepoint & OneDrive API resulting in some restored files to cause errors when opened with Microsoft office. We are currently working on mitigating this issue and are doing a joint investigation with Microsoft.

2. monitoring Mar 22, 2026, 05:02 PM UTC

   As of 12:30 UTC, our engineering team has deployed a fix for the issue impacting the Microsoft SharePoint & OneDrive API. We are no longer observing new errors. However, some customer files that were backed up in recent weeks may continue to exhibit issues during restore until remediation is completed. Our Veeam Data Cloud engineering team is now working to identify and reprocess any files that were impacted during this period.

3. monitoring Mar 25, 2026, 06:01 PM UTC

   As of March 25, we have deployed an update globally and are seeing stable operation. While no new instances of the error are being observed, we are continuing follow-up work to ensure all previously impacted scenarios are fully resolved. An update on this work will be provided as soon as possible.

4. monitoring Apr 03, 2026, 02:57 PM UTC

   As of March 25, we deployed an update globally and continue to see stable service operation. At this time, we are not observing any new instances of this issue. Our engineering team continues follow-up work with Microsoft and internal engineering efforts to ensure all previously impacted scenarios are fully addressed and to drive a permanent resolution. We expect to have additional updates in the next few days and will share another update as soon as we have more information.

5. resolved Apr 20, 2026, 04:07 PM UTC

   We have not observed any recurrence of this issue since the March 25 update. We are closing this incident and will continue working with Microsoft on any remaining items.

Read the full incident report →

Started Mar 18, 2026, 03:36 AM UTC· resolved Mar 18, 2026, 04:50 PM UTC

1. investigating Mar 18, 2026, 03:36 AM UTC

   Starting at 17:00 UTC on March 17th, Veeam Data Cloud began experiencing an issue with M365 backups failing for some customers in the APJ region. Our engineers have opened a technical support ticket with Microsoft and are actively working alongside their team to resolve the underlying cause as quickly as possible. Further information will be provided as soon as more details are obtained from Microsoft.

2. resolved Mar 18, 2026, 04:50 PM UTC

   Between 17:00 UTC on March 17th and 08:00 UTC on March 18th, Veeam Data Cloud experienced an issue where M365 backups failed for some customers in the APJ region. Our engineers worked closely with Microsoft to identify and resolve the underlying infrastructure issue, and we can now confirm that backup functionality has been fully restored. All systems are operating normally. If you experience any further issues, please reach out to our support team for assistance.

Read the full incident report →

Started Mar 02, 2026, 10:50 PM UTC· resolved Mar 02, 2026, 11:31 PM UTC

1. investigating Mar 02, 2026, 10:50 PM UTC

   Starting around 21:00 UTC, Veeam Data Cloud began experiencing degraded performance for some AMER customers using M365. During this time, some customers may experience issues performing backups or restores. Our engineer team is actively engaged and working to resolve this issue.

2. resolved Mar 02, 2026, 11:31 PM UTC

   Between 21:00 UTC and 23:20 UTC, Veeam Data Cloud experienced an issue with M365 impacting some AMER customers. During this time, some customers may have experienced issues performing restores and backups. Our engineers mitigated this issue and confirmed services are fully functional. If you experience any further issues, please reach out to support for further assistance.

Read the full incident report →

Started Mar 01, 2026, 11:20 PM UTC· resolved Mar 01, 2026, 11:20 PM UTC

1. resolved Mar 01, 2026, 11:20 PM UTC

   Between 18:53 UTC and 23:20 UTC, Veeam Data Cloud experienced a service disruption affecting Microsoft 365 operations for some customers in the APAC region. During this window, some users may have encountered difficulties initiating restores, delays in backup jobs, or seen inaccurate dashboard metrics. Our engineering team has since successfully mitigated the issue and confirmed that all services are fully restored and operating normally. If you experience any further issues please reach out to support for further assistance.

Read the full incident report →

Started Feb 25, 2026, 05:18 AM UTC· resolved Feb 25, 2026, 03:10 PM UTC

1. investigating Feb 25, 2026, 05:18 AM UTC

   Starting around 02:57 UTC on February 25, some EMEA-hosted customers may experience service disruptions affecting dashboard access and restore operations. While backup jobs should continue to run as expected, Microsoft has confirmed that a database issue following scheduled maintenance is causing this impact. Our engineering teams are working closely with Microsoft Support to resolve the issue, and we will provide updates as they become available.

2. resolved Feb 25, 2026, 03:10 PM UTC

   As of 10:53 UTC, service functionality has been fully restored. Following Microsoft's scheduled maintenance, our teams worked closely with their support engineers to resolve the underlying database issues that were affecting dashboard access and restore operations. We have monitored the environment and confirmed that all services are now stable and healthy. If you continue to experience any issues, please reach out to our Support team for assistance.

Read the full incident report →

Started Feb 19, 2026, 04:52 PM UTC· resolved Feb 19, 2026, 04:52 PM UTC

1. resolved Feb 19, 2026, 04:52 PM UTC

   Between 00:00 UTC and 09:00 UTC, Veeam Data Cloud experienced a service disruption impacting M365 customers in the US East region. During this window, users may have encountered difficulties accessing management features, including backup history and policy configurations. Our engineering team has since successfully mitigated the underlying cause, and we have confirmed that all services are now fully restored and operating normally.

Read the full incident report →

Started Feb 15, 2026, 07:31 PM UTC· resolved Feb 16, 2026, 03:32 PM UTC

1. investigating Feb 15, 2026, 07:31 PM UTC

   Starting on Sunday, February 15, Veeam Data Cloud experienced a service disruption impacting Entra ID customers across all regions. During this window, affected users may have encountered intermittent or total backup failures within their environments. Our engineering team identified the root cause and successfully implemented a mitigation to restore functionality as of 17:30 UTC. We are currently monitoring the service closely to ensure stability and prevent any recurrence.

2. monitoring Feb 15, 2026, 07:33 PM UTC

   Starting on Sunday, February 15, Veeam Data Cloud experienced a service disruption impacting Entra ID customers across all regions. During this window, affected users may have encountered intermittent or total backup failures within their environments. Our engineering team identified the root cause and successfully implemented a mitigation to restore functionality as of 17:30 UTC. We are currently monitoring the service closely to ensure stability and prevent any recurrence.

3. resolved Feb 16, 2026, 03:32 PM UTC

   Between 20:03 UTC on February 14th and 17:23 UTC on February 15th, Veeam Data Cloud experienced a service disruption impacting Entra ID customers. During this period, some customers may have experienced failed backup jobs. Our engineering team has mitigated the issue and confirmed through overnight monitoring that service stability has returned to normal levels. Please reach out to support if you experience any further issues.

Read the full incident report →

Started Feb 12, 2026, 06:38 PM UTC· resolved Feb 17, 2026, 03:35 PM UTC

1. identified Feb 12, 2026, 06:38 PM UTC

   Starting around 06:00 UTC on February 09, Veeam Data Cloud began experiencing service performance issues for backups on M365. Our engineering teams are engaged and actively working to restore functionality. We appreciate your patience and will provide updates as soon as more information is available.

2. monitoring Feb 12, 2026, 09:19 PM UTC

   Our engineers implemented a fix as of 21:09 UTC. Previously impacted backup service functionality has been restored for all M365 customers. We will continue to monitor service health overnight to ensure stability and confirm that no further issues arise.

3. monitoring Feb 13, 2026, 11:19 PM UTC

   Since our initial fix at 21:09 UTC on February 12th, the majority of our services have remained stable and healthy. However, because we have observed a small number of intermittent errors, we are continuing to monitor over the weekend to ensure stability.

4. resolved Feb 17, 2026, 03:35 PM UTC

   We have confirmed that all services, including backup functionality, have remained stable and fully operational since February 12 at 21:09 UTC. Our engineering team has closely monitored the environment and no further errors have been observed.

Read the full incident report →

Started Feb 08, 2026, 08:36 PM UTC· resolved Feb 10, 2026, 02:11 AM UTC

1. investigating Feb 08, 2026, 08:36 PM UTC

   Some backups may be experiencing degraded performance. We are actively investigating the issue.

2. resolved Feb 10, 2026, 02:11 AM UTC

   As of 00:45 UTC on February 09, full functionality has been restored for all backups previously impacted by service interruptions. The issue originated from a widespread Microsoft outage that affected our underlying infrastructure, but all systems are now performing as expected. Please reach out to support if you experience any further issues.

Read the full incident report →

Started Feb 07, 2026, 07:05 PM UTC· resolved Feb 08, 2026, 04:45 AM UTC

1. investigating Feb 07, 2026, 07:05 PM UTC

   Starting at 08:00 UTC, Veeam Data Cloud began experiencing issues due to a widespread outage in Microsoft Azure impacting customers in the US West region. Customers in the West US region may see some failed backups. More information regarding this outage can be found on Microsoft’s status page here: https://azure.status.microsoft/en-us/status Further updates will be provided when more information is obtained from Microsoft.

2. resolved Feb 08, 2026, 04:45 AM UTC

   Between 08:00 UTC on February 06 and 02:15 UTC on February 07, Veeam Data Cloud experienced issues due to a widespread outage with Microsoft Azure that impacted customers in the US West region. Microsoft has confirmed that all Azure services are now healthy. Veeam Data Cloud engineers have also confirmed service restoration. For more information on the Microsoft Azure outage, please refer to Microsoft's status page: https://azure.status.microsoft/en-us/status

Read the full incident report →

Started Feb 06, 2026, 04:20 PM UTC· resolved Feb 10, 2026, 03:43 PM UTC

1. investigating Feb 06, 2026, 04:20 PM UTC

   We are currently investigating an issue where some customers may experience failures or delays when exporting data to PST. At this time, restore functionality remains fully operational and is not impacted. Our engineering teams are actively debugging the issue, which appears to be related to a recent Microsoft update affecting PST background processing. We are working to mitigate the impact and will provide further updates as more information becomes available.

2. monitoring Feb 06, 2026, 09:49 PM UTC

   Targeted changes were applied to mitigate the current PST export failures. The system and associated changes will continue to be monitored and we will provide additional updates as the situation evolves.

3. monitoring Feb 10, 2026, 02:14 AM UTC

   Our engineers have applied a fix as of 12:00 UTC to address the recent service interruptions. We have confirmed that systems are currently performing as expected and will continue to monitor service health overnight to ensure ongoing stability. The next update will be provided around 16:00 UTC after further observation.

4. resolved Feb 10, 2026, 03:43 PM UTC

   Our engineers have monitored system health overnight and confirmed that platform stability has returned to normal. The previous failures and delays encountered when exporting data to PST have been fully resolved.

Read the full incident report →