Update - Microsoft has not cleared the incident yet, but most services appear to be operational.
Nov 13, 2026 - 16:09 MST
Nov 13, 2026 - 16:09 MST
Update - Functionality is being restored and services are coming online. The O365 Team will monitor until Microsoft lists the issue as resolved.
Further updates can be found here:
https://status.cloud.microsoft/
Nov 13, 2026 - 09:11 MST
Further updates can be found here:
https://status.cloud.microsoft/
Nov 13, 2026 - 09:11 MST
Monitoring - A fix has been implemented and we are monitoring the results.
MS Update:
Current Status: We're observing sustained improvements in service availability as recovery progresses across affected Microsoft 365 services. While service functionality continues to improve, some users may still experience intermittent connectivity issues or delayed email delivery.
Our efforts are increasingly focused on resolving the remaining issues and restoring consistent service for all affected users. We're validating recovery across different connection methods and monitoring service stability to confirm that improvements are sustained.
Nov 13, 2026 - 08:03 MST
MS Update:
Current Status: We're observing sustained improvements in service availability as recovery progresses across affected Microsoft 365 services. While service functionality continues to improve, some users may still experience intermittent connectivity issues or delayed email delivery.
Our efforts are increasingly focused on resolving the remaining issues and restoring consistent service for all affected users. We're validating recovery across different connection methods and monitoring service stability to confirm that improvements are sustained.
Nov 13, 2026 - 08:03 MST
Update - MS Update:
Current Status: We're seeing continued recovery progress across affected regions, with broader improvements now observed in North America and sustained improvements across much of Europe. We're also seeing encouraging recovery signals in Asia Pacific, although some users may continue to experience intermittent access issues or delayed email delivery as mitigation progresses across the remaining affected infrastructure.
Our focus remains on stabilizing recovered infrastructure, completing mitigation in the remaining impacted areas, and reducing delayed email queues and backlogs. We're closely monitoring service consistency and validating recovery across different connection methods as we work toward full mitigation.
At this time, we have no evidence of malicious activity associated with this incident. We will continue to treat this with urgency until full mitigation, and we will share a full Post-Incident Report with root cause and defense-in-depth actions after mitigation is complete.
Scope of impact: This issue may affect users attempting to access the affected Microsoft 365 services.
Next update by: Friday, November 13, 2026, at 2:00 PM UTC
Nov 13, 2026 - 06:28 MST
Current Status: We're seeing continued recovery progress across affected regions, with broader improvements now observed in North America and sustained improvements across much of Europe. We're also seeing encouraging recovery signals in Asia Pacific, although some users may continue to experience intermittent access issues or delayed email delivery as mitigation progresses across the remaining affected infrastructure.
Our focus remains on stabilizing recovered infrastructure, completing mitigation in the remaining impacted areas, and reducing delayed email queues and backlogs. We're closely monitoring service consistency and validating recovery across different connection methods as we work toward full mitigation.
At this time, we have no evidence of malicious activity associated with this incident. We will continue to treat this with urgency until full mitigation, and we will share a full Post-Incident Report with root cause and defense-in-depth actions after mitigation is complete.
Scope of impact: This issue may affect users attempting to access the affected Microsoft 365 services.
Next update by: Friday, November 13, 2026, at 2:00 PM UTC
Nov 13, 2026 - 06:28 MST
Update - MS Update:
Current status: We've made additional progress toward service recovery, with recovery actions completed across portions of the affected infrastructure in the Asia Pacific region. Traffic is being gradually restored, and we're seeing improvements in key customer scenarios, including mailbox access and delayed email processing. However, some users may continue to experience intermittent issues.
Our focus is now on extending these recovery actions across affected infrastructure in other regions, while continuing stabilization efforts and adding supporting capacity to improve service consistency.
Reducing email queues and backlogs remains a priority, and the extended 48-hour email timeout window remains in place to help protect delayed messages as delivery catches up.
At this time, we have no evidence of malicious activity associated with this incident. We will continue to treat this with urgency until full mitigation, and we will share a full Post-Incident Report with root cause and defense-in-depth actions after mitigation is complete.
Scope of impact: This issue may affect users attempting to access the affected Microsoft 365 services.
Next update by: Friday, November 13, 2026, at 12:00 PM UTC
Nov 13, 2026 - 04:17 MST
Current status: We've made additional progress toward service recovery, with recovery actions completed across portions of the affected infrastructure in the Asia Pacific region. Traffic is being gradually restored, and we're seeing improvements in key customer scenarios, including mailbox access and delayed email processing. However, some users may continue to experience intermittent issues.
Our focus is now on extending these recovery actions across affected infrastructure in other regions, while continuing stabilization efforts and adding supporting capacity to improve service consistency.
Reducing email queues and backlogs remains a priority, and the extended 48-hour email timeout window remains in place to help protect delayed messages as delivery catches up.
At this time, we have no evidence of malicious activity associated with this incident. We will continue to treat this with urgency until full mitigation, and we will share a full Post-Incident Report with root cause and defense-in-depth actions after mitigation is complete.
Scope of impact: This issue may affect users attempting to access the affected Microsoft 365 services.
Next update by: Friday, November 13, 2026, at 12:00 PM UTC
Nov 13, 2026 - 04:17 MST
Update - MS Update:
Current status: As part of our investigation into the sustained traffic management imbalances, we’re reviewing traffic flows and affected infrastructure to identify opportunities to optimize routing. This includes verifying the reasons for service failures so we can develop specific actions to improve stability.
We will continue to share more information as soon as we have it, and for now we can confirm that there is no indication this is the result of malicious activity. We’ll continue to apply learnings towards remediation actions as we confirm effectiveness mitigation actions.
Previous status: We’ve monitored the status of the changes applied to improve serviceability and confirmed that change is not taking as expected. We’re identifying alternate workstreams that can be applied to increase capacity in the face of sustained traffic management imbalances.
Nov 12, 2026 - 21:17 MST
Current status: As part of our investigation into the sustained traffic management imbalances, we’re reviewing traffic flows and affected infrastructure to identify opportunities to optimize routing. This includes verifying the reasons for service failures so we can develop specific actions to improve stability.
We will continue to share more information as soon as we have it, and for now we can confirm that there is no indication this is the result of malicious activity. We’ll continue to apply learnings towards remediation actions as we confirm effectiveness mitigation actions.
Previous status: We’ve monitored the status of the changes applied to improve serviceability and confirmed that change is not taking as expected. We’re identifying alternate workstreams that can be applied to increase capacity in the face of sustained traffic management imbalances.
Nov 12, 2026 - 21:17 MST
Update - MS Update
Current status: We’re applying infrastructure capacity improvements where possible in an effort to help support traffic in regions coming online. We’re continuing to monitor the results of changes applied so we can identify strategic actions that can help to improve service health across all affected regions.
Nov 12, 2026 - 19:46 MST
Current status: We’re applying infrastructure capacity improvements where possible in an effort to help support traffic in regions coming online. We’re continuing to monitor the results of changes applied so we can identify strategic actions that can help to improve service health across all affected regions.
Nov 12, 2026 - 19:46 MST
Update - MS Update:
Current status: While the servers we've returned to service initially remain healthy, we've observed that they can become unresponsive again once they begin receiving traffic. We're analyzing diagnostic data from these servers with our networking and platform experts to determine what's triggering this behavior.
Nov 12, 2026 - 17:19 MST
Current status: While the servers we've returned to service initially remain healthy, we've observed that they can become unresponsive again once they begin receiving traffic. We're analyzing diagnostic data from these servers with our networking and platform experts to determine what's triggering this behavior.
Nov 12, 2026 - 17:19 MST
Update - MS Update:
Current status: We've begun returning a portion of the affected servers to service, and they're remaining stable so far. We’ve also shifted traffic and connections to alternative pathways wherever possible and have observed limited recovery in some regions.
Nov 12, 2026 - 17:02 MST
Current status: We've begun returning a portion of the affected servers to service, and they're remaining stable so far. We’ve also shifted traffic and connections to alternative pathways wherever possible and have observed limited recovery in some regions.
Nov 12, 2026 - 17:02 MST
Update - MS update:
We’re opening all available pathways to restore service, as our actions taken thus far have not provided the anticipated relief. We found a core process on affected servers is becoming overwhelmed, causing capacity loss. To validate a potential recovery, we're isolating a portion of infrastructure, restarting affected components, and reintroducing traffic to confirm the services remain stable before applying the change more broadly.
Nov 12, 2026 - 15:56 MST
We’re opening all available pathways to restore service, as our actions taken thus far have not provided the anticipated relief. We found a core process on affected servers is becoming overwhelmed, causing capacity loss. To validate a potential recovery, we're isolating a portion of infrastructure, restarting affected components, and reintroducing traffic to confirm the services remain stable before applying the change more broadly.
Nov 12, 2026 - 15:56 MST
Update - Update from MS:
We've validated an alternative service health check method, which allowed a subset of affected servers to successfully return to service. We're now applying this change more broadly. We're also preparing automated recovery systems to continually detect and restart unresponsive servers, to maintain service stability while this change progresses.
Nov 12, 2026 - 14:17 MST
We've validated an alternative service health check method, which allowed a subset of affected servers to successfully return to service. We're now applying this change more broadly. We're also preparing automated recovery systems to continually detect and restart unresponsive servers, to maintain service stability while this change progresses.
Nov 12, 2026 - 14:17 MST
Update - MS update:
We've not identified any recent change correlated with the start of impact; however, our investigation indicates the failed health checks may originate from a specific component that's responsible for processing server health. We've taken steps to prevent additional servers from being impacted while we work to return the affected servers to service.
While validating the targeted change, we found that many of the affected servers have become unresponsive, which is preventing us from confirming whether the change is effective. We're restarting these servers so they can come back online with the change in place, and we're applying the same approach to additional affected portions of our infrastructure to validate the results more broadly.
Nov 12, 2026 - 14:04 MST
We've not identified any recent change correlated with the start of impact; however, our investigation indicates the failed health checks may originate from a specific component that's responsible for processing server health. We've taken steps to prevent additional servers from being impacted while we work to return the affected servers to service.
While validating the targeted change, we found that many of the affected servers have become unresponsive, which is preventing us from confirming whether the change is effective. We're restarting these servers so they can come back online with the change in place, and we're applying the same approach to additional affected portions of our infrastructure to validate the results more broadly.
Nov 12, 2026 - 14:04 MST
Update - Update from MS:
We're testing a configuration change to address a problem that's causing servers to fail automated health checks and become unavailable. In parallel, we've initiated a restart of all affected servers and are monitoring health as they return to service.
Nov 12, 2026 - 13:10 MST
We're testing a configuration change to address a problem that's causing servers to fail automated health checks and become unavailable. In parallel, we've initiated a restart of all affected servers and are monitoring health as they return to service.
Nov 12, 2026 - 13:10 MST
Update - We are continuing to work on a fix for this issue.
Nov 12, 2026 - 12:48 MST
Nov 12, 2026 - 12:48 MST
Update - Microsoft update:
Nov 12, 2026, 12:18 PM MST
We've determined that the elevated load isn't driven by an overall increase in traffic, but by a large number of servers being unexpectedly unavailable, which is shifting load onto the remaining infrastructure. We're investigating what's causing these servers to become unavailable while we work to safely return them to service. This quick update is designed to give the latest information on this issue.
Nov 12, 2026 - 12:47 MST
Nov 12, 2026, 12:18 PM MST
We've determined that the elevated load isn't driven by an overall increase in traffic, but by a large number of servers being unexpectedly unavailable, which is shifting load onto the remaining infrastructure. We're investigating what's causing these servers to become unavailable while we work to safely return them to service. This quick update is designed to give the latest information on this issue.
Nov 12, 2026 - 12:47 MST
Identified - The issue has been identified and a fix is being implemented.
Nov 12, 2026 - 11:07 MST
Nov 12, 2026 - 11:07 MST
Investigating - From Microsoft:
Users may be unable to connect to their mailboxes in Exchange Online through multiple connection methods
Issue ID: EX1550543
Affected services: Exchange Online
Status: Service degradation
Issue type: Incident
Start time: Nov 12, 2026, 9:17 AM MST
User impact
Users may be unable to connect to their mailboxes in Exchange Online through multiple connection methods.
More info
Potentially impacted connection methods may include:
- Outlook on the web
- Messaging API (MAPI)
- Exchange ActiveSync (EAS)
- Representational State Transfer (REST) API
Scope of impact
This issue may affect users in North America, Latin America, Canada, and Chile.
Current status
Nov 12, 2026, 10:45 AM MST
We’ve identified connectivity errors occurring on a portion of Exchange Online infrastructure which receives and processes users’ access requests. We’ve collected networking logs to review to further investigate the source of these errors and confirm our next steps.
Next update by:
Thursday, November 12, 2026 at 1:00 PM MST
Nov 12, 2026 - 11:07 MST
Users may be unable to connect to their mailboxes in Exchange Online through multiple connection methods
Issue ID: EX1550543
Affected services: Exchange Online
Status: Service degradation
Issue type: Incident
Start time: Nov 12, 2026, 9:17 AM MST
User impact
Users may be unable to connect to their mailboxes in Exchange Online through multiple connection methods.
More info
Potentially impacted connection methods may include:
- Outlook on the web
- Messaging API (MAPI)
- Exchange ActiveSync (EAS)
- Representational State Transfer (REST) API
Scope of impact
This issue may affect users in North America, Latin America, Canada, and Chile.
Current status
Nov 12, 2026, 10:45 AM MST
We’ve identified connectivity errors occurring on a portion of Exchange Online infrastructure which receives and processes users’ access requests. We’ve collected networking logs to review to further investigate the source of these errors and confirm our next steps.
Next update by:
Thursday, November 12, 2026 at 1:00 PM MST
Nov 12, 2026 - 11:07 MST
Point of Sale
Operational
POS
Operational
ESL (Electronic Scheduling Log)
Operational
Hitch Scheduling Log (HSL)
Operational
CSF (Customer Service Form)
Operational
POS Console
Operational
Showroom Sales
Operational
WebBEST
Operational
U-Haul Messenger
Operational
Backup POS
Operational
UBOX
Operational
POS Mobile (Dashboard)
Operational
Product Receiving
Operational
Contract Close
Operational
Payments
Operational
Card Authorizations
Operational
Cheque Processing
Operational
uhaul.com and Truck Share
Operational
Live Verification
Operational
uhaul.com
Operational
Truck Share
Operational
Rates and Distribution
Operational
Web AMT
Operational
RMC (Rotation Management Console)
Operational
uhaul.net
Operational
Cross Contact
Operational
Contract Lookup
Operational
Reports
Operational
e-Alert
Operational
Tools
Operational
Miniroute
Operational
Accounts Payable
Operational
Contact Center
Operational
Roadside
Operational
CAF (Customer Action File)
Operational
Alvaria
Operational
Dealer Network
Operational
uhauldealer.com
Operational
Repair
Operational
RepairHub
Operational
Network
Operational
Internet Connectivity
Operational
Meraki (Center Networks)
Operational
WiFi
Operational
VPN
Operational
VoIP
Operational
Finesse (Traffic & Contact Center)
Operational
Center Phones
Operational
Email/O365 applications
Operational
Email
Operational
Teams
Operational
Office 365 Online Apps
Operational
Moving Help
Operational
Control-D Reports
Operational
Workday / U-Haul life
Operational
Time clock
Operational
U-Haul University
Operational
TEST
Operational
WebSelfStorage
Operational
Alarm System
Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance