All Systems Operational
Uptime over the past 90 days. View historical uptime.
Covercloud
Operational
Medicloud
Operational
Exchange
Operational
NBN Internet
Operational
Fibre Internet
Operational
Cloud Phones
Operational
Web Server
Operational
Microsoft 365
Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.
Related
No incidents or maintenance related to this downtime.
Past Incidents
Nov 16, 2026
No incidents reported today.
Nov 15, 2026
No incidents reported.
Nov 14, 2026
No incidents reported.
Nov 13, 2026
Resolved -
Microsoft has completed recovery work across much of the affected infrastructure in the Asia Pacific region, and is seeing improvements in mailbox access and delayed email processing. Some users may still experience intermittent issues while traffic is gradually restored. Microsoft is now extending these recovery actions to other regions and continuing to clear the email backlog, with the 48-hour delivery timeout still in place to protect delayed messages.
FocusNet has confirmed that email is starting to flow again, and we expect it to be back to normal overnight. We will now mark this incident as Resolved from a FocusNet perspective. For any further updates, please refer to Microsoft's status page: https://status.cloud.microsoft/
Nov 13, 19:33 AWST
FocusNet has confirmed that email is starting to flow again, and we expect it to be back to normal overnight. We will now mark this incident as Resolved from a FocusNet perspective. For any further updates, please refer to Microsoft's status page: https://status.cloud.microsoft/
Nov 13, 19:33 AWST
Update -
Recovery is progressing in stages, and Microsoft is seeing gradual improvement across several services.
However, service may still be patchy and capacity is not yet fully back to normal. Microsoft is prioritising the backlog of delayed email, and the 48-hour delivery timeout remains in place so delayed messages should still arrive rather than bounce.
Nov 13, 18:24 AWST
However, service may still be patchy and capacity is not yet fully back to normal. Microsoft is prioritising the backlog of delayed email, and the 48-hour delivery timeout remains in place so delayed messages should still arrive rather than bounce.
Nov 13, 18:24 AWST
Update -
Microsoft is seeing early signs of stabilisation, but capacity is not yet back to normal and service may still be patchy as traffic is gradually reintroduced. Microsoft is working through the affected servers in stages, restarting and fixing them before returning them to service, and is looking at further options to speed up recovery. To protect delayed email, Microsoft has extended its delivery timeout to 48 hours, so messages sent during the outage should still be delivered once service recovers rather than bouncing. There is still no indication of malicious activity, and Microsoft will publish a full Post-Incident Report once recovery is complete.
Nov 13, 17:18 AWST
Nov 13, 17:18 AWST
Update -
Microsoft is seeing early signs of stabilisation, but capacity is not yet back to normal and service may still be patchy as traffic is gradually reintroduced. Microsoft is working through the affected servers in stages, restarting and fixing them before returning them to service, and is looking at further options to speed up recovery. To protect delayed email, Microsoft has extended its delivery timeout to 48 hours, so messages sent during the outage should still be delivered once service recovers rather than bouncing. There is still no indication of malicious activity, and Microsoft will publish a full Post-Incident Report once recovery is complete.
Nov 13, 17:18 AWST
Nov 13, 17:18 AWST
Update -
Microsoft is seeing positive results after applying a patch to part of its infrastructure, with affected servers now more stable. Microsoft is monitoring progress and expanding the patch to more servers as regions come back online. There is currently no indication of malicious activity behind this incident. Microsoft will publish a full Post-Incident Report with the root cause once the issue is resolved.
Nov 13, 16:00 AWST
Nov 13, 16:00 AWST
Update -
Microsoft has seen a surge in traffic between its routing services and backend servers while applying its recovery actions, which is adding to the instability. To address this, Microsoft is adding more server capacity and forcing a recent network change onto servers in a faulty state. Some servers are stuck and aren't picking up the change as expected, so Microsoft is monitoring the results and refining its approach. There is no timeframe for recovery yet.
Nov 13, 13:12 AWST
Nov 13, 13:12 AWST
Update -
Latest update
Microsoft is working to stabilise its servers and improve how traffic flows through its network. This includes adjusting traffic settings, redistributing traffic and temporarily blocking certain types of traffic.
Microsoft is seeing partial recovery in the regions where these changes have been applied, but the recovery isn't holding. They are now reviewing what else they can do to improve overall stability.
Nov 13, 12:24 AWST
Microsoft is working to stabilise its servers and improve how traffic flows through its network. This includes adjusting traffic settings, redistributing traffic and temporarily blocking certain types of traffic.
Microsoft is seeing partial recovery in the regions where these changes have been applied, but the recovery isn't holding. They are now reviewing what else they can do to improve overall stability.
Nov 13, 12:24 AWST
Update -
Latest update
Microsoft is reviewing how traffic flows through its network and the affected servers, looking for ways to route traffic more efficiently. They are also working to confirm exactly why services are failing, so they can take targeted action to improve stability.
Nov 13, 12:03 AWST
Microsoft is reviewing how traffic flows through its network and the affected servers, looking for ways to route traffic more efficiently. They are also working to confirm exactly why services are failing, so they can take targeted action to improve stability.
Nov 13, 12:03 AWST
Update -
Unfortunately, Microsoft has reported a setback in resolving the Microsoft 365 outage. This is a Microsoft-wide issue and is not specific to your environment. FocusNet continues to monitor the situation closely.
Latest update
The changes Microsoft applied to restore its servers have not worked as expected. Microsoft is now looking at alternative ways to increase capacity while traffic across its network remains unbalanced.
What this means for you
Recovery is likely to take longer than previously expected. Email and email-related features should be considered unavailable or unreliable until Microsoft confirms otherwise.
The good news:
- Teams calls, meetings, group chats and channel messages are working
- Files stored in SharePoint can still be accessed
What's affected
- Email (Outlook): Users may be unable to access their mailbox in Outlook desktop, Outlook on the web or on mobile, and email delivery may be delayed.
- Teams: Calendar features (scheduling, invites, viewing and editing meetings) may fail. Creating live or virtual events, adding or syncing contacts, and creating or deleting private or shared channels may also fail.
- Copilot: Copilot Chat may not load or respond, and may be unable to access email, calendar and files.
- Safe Links: Links in Outlook and Teams may not be verified when clicked.
- Microsoft 365 apps: Recently used files may not display.
- Planner and To Do: May not load or may show errors.
- SharePoint: Features that rely on email may be affected.
- Power BI and Fabric: Exporting, updating or opening reports with sensitivity labels may fail. Removing the sensitivity label is a workaround, but only where your data protection policies allow it.
- Intune: Device enrolment, check-in and compliance may be intermittently affected.
- Universal Print: Print jobs may fail to submit.
- Windows 365: Some Cloud PC connections may fail where specific encryption settings are in use.
- Admin and security portals: Some pages in the Microsoft 365 admin center, Defender and Purview may not load. Purview features such as audit searches, eDiscovery and sensitivity labelling may also be affected.
Nov 13, 11:13 AWST
Latest update
The changes Microsoft applied to restore its servers have not worked as expected. Microsoft is now looking at alternative ways to increase capacity while traffic across its network remains unbalanced.
What this means for you
Recovery is likely to take longer than previously expected. Email and email-related features should be considered unavailable or unreliable until Microsoft confirms otherwise.
The good news:
- Teams calls, meetings, group chats and channel messages are working
- Files stored in SharePoint can still be accessed
What's affected
- Email (Outlook): Users may be unable to access their mailbox in Outlook desktop, Outlook on the web or on mobile, and email delivery may be delayed.
- Teams: Calendar features (scheduling, invites, viewing and editing meetings) may fail. Creating live or virtual events, adding or syncing contacts, and creating or deleting private or shared channels may also fail.
- Copilot: Copilot Chat may not load or respond, and may be unable to access email, calendar and files.
- Safe Links: Links in Outlook and Teams may not be verified when clicked.
- Microsoft 365 apps: Recently used files may not display.
- Planner and To Do: May not load or may show errors.
- SharePoint: Features that rely on email may be affected.
- Power BI and Fabric: Exporting, updating or opening reports with sensitivity labels may fail. Removing the sensitivity label is a workaround, but only where your data protection policies allow it.
- Intune: Device enrolment, check-in and compliance may be intermittently affected.
- Universal Print: Print jobs may fail to submit.
- Windows 365: Some Cloud PC connections may fail where specific encryption settings are in use.
- Admin and security portals: Some pages in the Microsoft 365 admin center, Defender and Purview may not load. Purview features such as audit searches, eDiscovery and sensitivity labelling may also be affected.
Nov 13, 11:13 AWST
Update -
We have some positive news on the Microsoft 365 outage.
Latest update
Microsoft is seeing positive results from restarting the affected servers in a controlled, isolated way. They're now monitoring these servers closely to confirm they remain stable. Once stability is confirmed, Microsoft expects to expand this approach more broadly, which should improve availability across the service.
What this means for you
This is the first clear sign of progress, but recovery will be gradual. Email and email-related features may continue to be unavailable or intermittent for some time yet, and services may come back for some users before others.
As a reminder, Teams chat and online meetings are largely working, and files stored in SharePoint can still be accessed.
What you need to do
No action is required at this stage. If you're unable to access email, please try again periodically. There is no need to log a ticket for this issue unless something persists once Microsoft confirms the service is restored.
Microsoft is tracking this under incidents MO1550821 and EX1550543 in the Microsoft 365 admin center, or at status.cloud.microsoft.
We'll send another update as soon as Microsoft reports further progress.
Kind regards,
The FocusNet Team
Nov 13, 10:07 AWST
Latest update
Microsoft is seeing positive results from restarting the affected servers in a controlled, isolated way. They're now monitoring these servers closely to confirm they remain stable. Once stability is confirmed, Microsoft expects to expand this approach more broadly, which should improve availability across the service.
What this means for you
This is the first clear sign of progress, but recovery will be gradual. Email and email-related features may continue to be unavailable or intermittent for some time yet, and services may come back for some users before others.
As a reminder, Teams chat and online meetings are largely working, and files stored in SharePoint can still be accessed.
What you need to do
No action is required at this stage. If you're unable to access email, please try again periodically. There is no need to log a ticket for this issue unless something persists once Microsoft confirms the service is restored.
Microsoft is tracking this under incidents MO1550821 and EX1550543 in the Microsoft 365 admin center, or at status.cloud.microsoft.
We'll send another update as soon as Microsoft reports further progress.
Kind regards,
The FocusNet Team
Nov 13, 10:07 AWST
Update -
Microsoft is continuing to work on the major service incident affecting Microsoft 365. This is a Microsoft-wide issue and is not specific to your environment. FocusNet continues to monitor the situation closely.
Latest update
Microsoft has confirmed the issue is centred on Exchange Online (email). Other Microsoft 365 services are only affected where they rely on Exchange. Features that don't depend on email continue to work.
The good news:
- Teams chat and online meetings are largely working
- Files stored in SharePoint can still be accessed
What's affected
- Email (Outlook): Users may be unable to access their mailbox in Outlook desktop, Outlook on the web or on mobile, and email delivery may be delayed.
- Teams: Calendar and meeting scheduling may fail.
- Copilot: Copilot Chat may not load or respond, and may be unable to access email, calendar and files.
- Safe Links: Links in Outlook and Teams may not be verified when clicked.
- Microsoft 365 apps: Recently used files may not display.
- Planner and To Do: May not load or may show errors.
- SharePoint: Features that rely on email may be affected.
- Power BI and Fabric: Exporting reports with sensitivity labels to PDF or PowerPoint may fail.
- Universal Print: Print jobs may fail to submit.
- Windows 365: Some Cloud PC connections may fail where specific encryption settings are in use.
- Admin and security portals: Some pages in the Microsoft 365 admin center, Defender, Purview and Intune may not load.
Current status
Microsoft has found that a process on the affected servers responsible for establishing secure connections is becoming overwhelmed, causing the servers to stop processing requests.
To resolve this, Microsoft is:
- Testing a configuration fix on a subset of servers before rolling it out more broadly, alongside restarts of the affected infrastructure
- Reverting a recent network change that lines up with when the issue started
- Limiting traffic in specific locations to stabilise servers, then gradually reintroducing more traffic
What you need to do
No action is required at this stage. Teams chat and meetings are a good alternative for internal communication while email is affected. There is no need to log a ticket for this issue unless something persists once Microsoft confirms the service is restored.
Microsoft is tracking this under incidents MO1550821 and EX1550543 in the Microsoft 365 admin center, or at status.cloud.microsoft.
Nov 13, 09:27 AWST
Latest update
Microsoft has confirmed the issue is centred on Exchange Online (email). Other Microsoft 365 services are only affected where they rely on Exchange. Features that don't depend on email continue to work.
The good news:
- Teams chat and online meetings are largely working
- Files stored in SharePoint can still be accessed
What's affected
- Email (Outlook): Users may be unable to access their mailbox in Outlook desktop, Outlook on the web or on mobile, and email delivery may be delayed.
- Teams: Calendar and meeting scheduling may fail.
- Copilot: Copilot Chat may not load or respond, and may be unable to access email, calendar and files.
- Safe Links: Links in Outlook and Teams may not be verified when clicked.
- Microsoft 365 apps: Recently used files may not display.
- Planner and To Do: May not load or may show errors.
- SharePoint: Features that rely on email may be affected.
- Power BI and Fabric: Exporting reports with sensitivity labels to PDF or PowerPoint may fail.
- Universal Print: Print jobs may fail to submit.
- Windows 365: Some Cloud PC connections may fail where specific encryption settings are in use.
- Admin and security portals: Some pages in the Microsoft 365 admin center, Defender, Purview and Intune may not load.
Current status
Microsoft has found that a process on the affected servers responsible for establishing secure connections is becoming overwhelmed, causing the servers to stop processing requests.
To resolve this, Microsoft is:
- Testing a configuration fix on a subset of servers before rolling it out more broadly, alongside restarts of the affected infrastructure
- Reverting a recent network change that lines up with when the issue started
- Limiting traffic in specific locations to stabilise servers, then gradually reintroducing more traffic
What you need to do
No action is required at this stage. Teams chat and meetings are a good alternative for internal communication while email is affected. There is no need to log a ticket for this issue unless something persists once Microsoft confirms the service is restored.
Microsoft is tracking this under incidents MO1550821 and EX1550543 in the Microsoft 365 admin center, or at status.cloud.microsoft.
Nov 13, 09:27 AWST
Update -
Microsoft is still working to resolve the major service incident affecting several Microsoft 365 services. This is a Microsoft-wide issue and is not specific to your environment. FocusNet continues to monitor the situation closely.
Latest update
Some of the servers Microsoft brought back online have become unresponsive again once traffic returned to them. Microsoft is now analysing diagnostic data to identify what is triggering this.
In the meantime, Microsoft is:
- Temporarily limiting the types of traffic that can reach the affected infrastructure in some locations
- Rebuilding a subset of affected servers using a previous configuration, to test whether this stops them becoming unresponsive
What this means for you
Access to affected services may continue to be intermittent, and recovery will likely take longer than first expected. Services may appear to come back and then drop out again while Microsoft works through this.
What's affected
Services that may be impacted include:
- Exchange Online (email)
- Microsoft Teams
- SharePoint Online
- Microsoft 365 Copilot
- Microsoft Defender XDR
- Microsoft Planner
- Microsoft To Do
- Microsoft Intune
- Microsoft Defender for Office 365
- Microsoft Purview (including Data Loss Prevention, Auto Labelling, Communication Compliance and Data Classification)
- Power BI (exporting reports with sensitivity labels to PDF may intermittently fail)
- Microsoft 365 Apps Admin Center (Cloud Update, Cloud Policy and Inventory)
- Universal Print (users may see errors when submitting print jobs)
What you need to do
No action is required at this stage. If you're unable to access a service, please try again periodically. There is no need to log a ticket for this issue unless something persists once Microsoft confirms the service is restored.
For anyone wanting to follow along, Microsoft is tracking this under incidents EX1550543 and MO1550821 in the Microsoft 365 admin center, or at status.cloud.microsoft.
We'll send another update as soon as Microsoft reports meaningful progress.
Kind regards,
The FocusNet Team
Nov 13, 08:08 AWST
Latest update
Some of the servers Microsoft brought back online have become unresponsive again once traffic returned to them. Microsoft is now analysing diagnostic data to identify what is triggering this.
In the meantime, Microsoft is:
- Temporarily limiting the types of traffic that can reach the affected infrastructure in some locations
- Rebuilding a subset of affected servers using a previous configuration, to test whether this stops them becoming unresponsive
What this means for you
Access to affected services may continue to be intermittent, and recovery will likely take longer than first expected. Services may appear to come back and then drop out again while Microsoft works through this.
What's affected
Services that may be impacted include:
- Exchange Online (email)
- Microsoft Teams
- SharePoint Online
- Microsoft 365 Copilot
- Microsoft Defender XDR
- Microsoft Planner
- Microsoft To Do
- Microsoft Intune
- Microsoft Defender for Office 365
- Microsoft Purview (including Data Loss Prevention, Auto Labelling, Communication Compliance and Data Classification)
- Power BI (exporting reports with sensitivity labels to PDF may intermittently fail)
- Microsoft 365 Apps Admin Center (Cloud Update, Cloud Policy and Inventory)
- Universal Print (users may see errors when submitting print jobs)
What you need to do
No action is required at this stage. If you're unable to access a service, please try again periodically. There is no need to log a ticket for this issue unless something persists once Microsoft confirms the service is restored.
For anyone wanting to follow along, Microsoft is tracking this under incidents EX1550543 and MO1550821 in the Microsoft 365 admin center, or at status.cloud.microsoft.
We'll send another update as soon as Microsoft reports meaningful progress.
Kind regards,
The FocusNet Team
Nov 13, 08:08 AWST
Monitoring -
Microsoft is currently experiencing a major service incident that may prevent users from connecting to several Microsoft 365 services. This is a Microsoft-wide issue and is not specific to your environment. FocusNet is monitoring the situation closely and will keep you updated.
What's affected
Services that may be impacted include:
- Exchange Online (email)
- Microsoft Teams
- SharePoint Online
- Microsoft 365 Copilot
- Microsoft Defender XDR
- Microsoft Planner
- Microsoft To Do
- Microsoft Intune
- Microsoft Defender for Office 365
- Microsoft Purview (including Data Loss Prevention, Auto Labelling, Communication Compliance and Data Classification)
- Power BI (exporting reports with sensitivity labels to PDF may intermittently fail)
- Microsoft 365 Apps Admin Center (Cloud Update, Cloud Policy and Inventory)
- Universal Print (users may see errors when submitting print jobs)
Current status
Microsoft has started bringing some of the affected servers back online, and these are remaining stable so far. They have also redirected traffic through alternative pathways where possible, with limited recovery seen in some regions.
Microsoft has streamlined its recovery process to bring the remaining servers back faster. They are also applying traffic management measures in one location to reduce load, and will extend these to other locations if the results are positive. As capacity returns, users should see services recover gradually as their apps reconnect.
Background
Microsoft identified that a core process on the affected servers was becoming overwhelmed, causing the servers to stop responding. Earlier recovery attempts did not provide the expected relief, so Microsoft isolated part of its infrastructure, restarted the affected components and reintroduced traffic gradually to confirm stability before applying the fix more widely.
What you need to do
No action is required at this stage. If you're unable to access a service, please try again periodically, as recovery is happening gradually. There is no need to log a ticket for this issue unless something persists once Microsoft confirms the service is restored.
Next update
Microsoft's next update is expected by 8:30 AM AWST on Friday, 13 November 2026 (12:30 AM UTC). We'll pass on any meaningful changes as they come through.
Kind regards,
The FocusNet Team
Nov 13, 07:27 AWST
What's affected
Services that may be impacted include:
- Exchange Online (email)
- Microsoft Teams
- SharePoint Online
- Microsoft 365 Copilot
- Microsoft Defender XDR
- Microsoft Planner
- Microsoft To Do
- Microsoft Intune
- Microsoft Defender for Office 365
- Microsoft Purview (including Data Loss Prevention, Auto Labelling, Communication Compliance and Data Classification)
- Power BI (exporting reports with sensitivity labels to PDF may intermittently fail)
- Microsoft 365 Apps Admin Center (Cloud Update, Cloud Policy and Inventory)
- Universal Print (users may see errors when submitting print jobs)
Current status
Microsoft has started bringing some of the affected servers back online, and these are remaining stable so far. They have also redirected traffic through alternative pathways where possible, with limited recovery seen in some regions.
Microsoft has streamlined its recovery process to bring the remaining servers back faster. They are also applying traffic management measures in one location to reduce load, and will extend these to other locations if the results are positive. As capacity returns, users should see services recover gradually as their apps reconnect.
Background
Microsoft identified that a core process on the affected servers was becoming overwhelmed, causing the servers to stop responding. Earlier recovery attempts did not provide the expected relief, so Microsoft isolated part of its infrastructure, restarted the affected components and reintroduced traffic gradually to confirm stability before applying the fix more widely.
What you need to do
No action is required at this stage. If you're unable to access a service, please try again periodically, as recovery is happening gradually. There is no need to log a ticket for this issue unless something persists once Microsoft confirms the service is restored.
Next update
Microsoft's next update is expected by 8:30 AM AWST on Friday, 13 November 2026 (12:30 AM UTC). We'll pass on any meaningful changes as they come through.
Kind regards,
The FocusNet Team
Nov 13, 07:27 AWST
Nov 12, 2026
No incidents reported.
Nov 11, 2026
No incidents reported.
Nov 10, 2026
No incidents reported.
Nov 9, 2026
No incidents reported.
Nov 8, 2026
No incidents reported.
Nov 7, 2026
No incidents reported.
Nov 6, 2026
No incidents reported.
Nov 5, 2026
No incidents reported.
Nov 4, 2026
No incidents reported.
Nov 3, 2026
No incidents reported.
Nov 2, 2026
No incidents reported.