Widespread services issues will be provided via this page. If you are experiecing a service outage that is not shown below. Please email help@bothbrains.com or call 09 222 0700
No incidents reported
No incidents reported
No incidents reported
Outage affecting Microsoft 365, across all platforms. Users may be unable to connect to their mailboxes in Exchange Online through multiple connection methods, errors reported across Teams, SharePoint and Copilot also.
Microsoft 365 Suite and Outlook are now operational - a small number of inbound emails received during the outage may be delayed by up to 24 hours. Please email help@bothbrains.com or call +64 9 222 0700 / +61 480 020 094 if you experience any issues following the outage.
We’re starting to see mail flow and Outlook access recover across our customers’ tenants. Some email may be delayed while Microsoft works through the backlog of queued messages.
Microsoft reports that recovery actions have been completed across parts of the affected infrastructure in the Asia Pacific region. Traffic is being gradually restored, with improvements to mailbox access and delayed email processing. Some users may still see intermittent issues while recovery continues.
No action is needed on your end. Delayed emails should arrive without needing to be resent. We will post another (and hopefully the last) outage update at 9am.
No further progress at this stage, Microsoft 365 suite and Outlook remains offline, next update at 10pm NZDT
"We’re continuing to monitor activity across regions to evaluate server status and determine actions that can be taken to improve capacity. This includes reviewing server performance and confirming that developed patches have been applied and working as intended after infrastructure reboots are completed. At this point, we have observed marginal success. In parallel, we’re taking action to expand capacity through the utilization of Virtual Machines."
Further attempted fixes by the Microsoft team have not succeeded. We will continue to pass on updates throughout the evening. Our team will be available overnight and throughout the weekend once services are restored should any isolated issues affect our customers.
"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."
Further update from Microsoft below. Previously alerted restoration efforts were not successful. We are now expecting this worldwide outage to extended into the afternoon/evening, with no clear service recovery information being provided by Microsoft at this stage.
"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."
Update from Microsoft below, services are beginning to restore, users may experience a gradual recovery to full service
"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.
We've streamlined our recovery process to expedite returning the remaining affected servers to service. To further support recovery, we're implementing protective traffic management measures in a specific location to reduce load on the affected infrastructure, and we'll expand these measures to additional locations if we observe positive results. As capacity is restored, users may experience a gradual recovery as their clients reconnect to the service."
Microsoft Update below - No ETA to resolution provided yet, major worldwide outage. OneDrive, Teams and SharePoint are reported working for some customers.
"Current status: We’re continuing to pursue all available pathways to restore service, as our actions taken thus far have not provided the anticipated relief. Our investigation has found that a core process on the affected servers is becoming overwhelmed, which causes the servers to stop responding and contributes to the capacity loss.
To validate a potential recovery approach, we're fully isolating a portion of our service infrastructure, restarting the affected components, and gradually reintroducing traffic to confirm our services remain stable before applying this approach more broadly. We're also analyzing traffic patterns across our entire service infrastructure and evaluating whether isolating traffic within each region may allow affected regions to recover independently."
Update from Microsoft: Health check fix has been validated and is being deployed to additional servers, no resolution ETA provided yet, next update at 11:30am NZDT
"We've validated an alternative health check method on a subset of affected infrastructure, which allowed the servers in that subset to successfully return to service, and we're now applying this change more broadly. We're also preparing an automated recovery process to continually detect and restart unresponsive servers, to help keep them in service while this change progresses. Additionally, our review of recent changes has identified a small number of configuration updates that we're investigating as potential contributors to the issue."
Further update from Microsoft - Exact cause of outage is yet to be identified, engineers are attempting targetted changes to failing health checks to restore availability.
"While we haven't identified any recent changes that correlate with the start of impact, our investigation indicates the failed health checks may originate from a specific component on the affected servers that's responsible for processing them. We're deploying a targeted change to bypass this component on a subset of servers to validate whether this restores availability, and we've taken steps to prevent additional servers from being removed from service while we work to return the affected servers to service. We're also investigating why affected servers are experiencing elevated processor usage while handling requests."
Worldwide issues still persist, with the Microsoft team working to reduce impact. Next update expected 9:30am
Update from Microsoft:
We're aggressively pursuing all pathways to reduce impact. As a precaution, we've paused all deployments and configuration changes while we review recent changes for any correlation to this event. 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.
Microsoft has completed redistributing connection traffic across our worldwide infrastructure, and are moving additional traffic off the affected infrastructure to further reduce load. They are also restarting affected servers to return them to service. Expect to see improvements shortly. Next update expected at 9am NZDT
Microsoft is investigating an issue impacting multiple Microsoft 365 services and have determined the affected infrastructure is experiencing elevated load across multiple regions, which is likely contributing to the connectivity errors. In parallel, Microsoft is evaluating options to redirect traffic to alternate infrastructure to expedite relief.
Expect an update by 8am
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:
Current status: 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.
https://status.cloud.microsoft/m365/referrer=serviceStatusRedirect
No incidents reported
No incidents reported
No incidents reported