What the Sunday Guardian actually said
The Sunday Guardian piece asks whether Teams is down in the US and lists possible symptoms. Those symptoms cover sign-in, chat, meetings, audio and video, channels, file sharing, the desktop and mobile apps, and the web client. The article itself says the nature and extent of the problems haven't been independently established. It gives no report count, no Microsoft incident ID and no confirmation from Microsoft. The symptom list describes what an outage could cause. It is not a log of what people observed.
What the monitoring data shows
Third-party trackers give a mixed picture.
- StatusGator was checked at 5:41 PM UTC on November 16. It showed the service as operational and listed 26 user-submitted reports in the past 24 hours. The reports were scattered. They included sign-in problems, an inability to join a meeting, connectivity errors, delayed messages, calendar access and noisy audio on the Windows app. They came from the US, Canada, the UK and Egypt. One Canadian report said the sign-in problem had persisted since the Thursday, November 12 disruption. A tracker's report count is not an audited count of affected users.
- IsDown had recorded zero user reports in the 24 hours before its 05:32 AM EST check on November 16, and called Teams operational.
- Windows Report published on November 16 that Downdetector reports for Outlook, Copilot, Teams and Microsoft Store had spiked. Downdetector showed over 400 reports against a baseline of 23 for the Microsoft 365 aggregate. That outlet also noted that Microsoft hadn't acknowledged an outage on its 365 Status account, and the Service Health page showed everything operational.
So there was a real rise in complaints. Nothing I found shows Microsoft confirming a new Teams incident on November 16.
The confirmed incidents that came before
Several earlier events probably explain why people were primed to report problems.
November 12 Teams messaging incident. Microsoft's incident notice, as reproduced by StatusStack, said some users couldn't access or use Teams. Symptoms were delayed or failed chat messages, errors creating or updating chats, and trouble loading conversations. Microsoft later found that presence status was not affected. Impact was limited to users on Teams services hosted in or routed through the North and South America regions. The window ran from 14:45 to 15:53 UTC, or 1 hour 8 minutes. Microsoft's preliminary cause was resource contention in the underlying service infrastructure. It said mitigation restored service and impact was fully resolved.
The broader Microsoft 365 outage. Microsoft's preliminary post-incident report puts the incident window at November 12, 2026, 16:20 UTC to November 13, 16:10 UTC, or 23 hours 50 minutes. The incident IDs are EX1550543 and MO1550821. According to The Register's reading of the report, a Teams failover to the primary gateway supporting Exchange Online created a load surge. A defect caused lock contention inside an internal Windows process that exhausted CPU and memory. The Register also quotes Microsoft saying its load testing tended to focus on weaker hardware with fewer cores. A Gulf Business report says Microsoft stated there was no indication of malicious activity. That report also says calendar and meeting scheduling were affected in Teams, while core messaging and online meetings remained largely functional. The Windows Forum analysis of the same preliminary report says Teams chats and meetings worked for most of the outage and that Windows PCs themselves were unaffected. That report is still preliminary.
A lingering admin issue. StatusStack lists a separate open advisory that began November 12. Admins may see Windows and Android devices as unmonitored in the Pro Management Portal. The cause given was a spike in request traffic after the earlier outage that overloaded the service. Microsoft's last update said the fix had restored about 95 percent of affected devices. Admins can speed recovery by restarting or bulk-restarting devices in the Teams admin center. This is a management-console issue, not a failure of chat or meetings.
One caution on the Microsoft Q&A thread from November 16. A forum user pasted an admin summary saying services were impacted in the Americas. An independent advisor in that thread replied that EX1550543 had been marked Service Restored. That is the November 12–13 incident, not a new November 16 event. Don't treat that thread as proof of a fresh outage.
How to check whether the problem is real
Downdetector and similar sites show crowd-sourced complaints. They can't tell you the cause or confirm a Microsoft-acknowledged incident. A story about an outage can itself prompt more reports. The reliable check is Microsoft's own service health data.
If you're a Microsoft 365 admin:
- Sign in to the Microsoft 365 admin center with an admin account. Microsoft says the Service Support admin and Helpdesk admin roles can view service health.
- Go to Health > Service health, or select the Service health card on the Home dashboard.
- On the Overview tab, check Teams' health state and the Active issues Microsoft is working on section.
- Check Issues for your organization to act on. This section only appears if something in your own environment needs attention.
- Use the Issue history tab to review incidents resolved in the last 7 or 30 days.
- If your problem isn't listed, select Report an issue. Microsoft says it compares those reports with data from other organizations to decide whether to open an incident.
Microsoft also says its service status page is the place to check if you can't sign in to the admin center, and that the @MSFT365status account on X shares information about certain events. Microsoft's definitions are useful here. An advisory means some users are affected but the service is still available. An incident means a service or major function is unavailable.
Basic checks for an individual user
If you're not an admin, these low-risk steps come from the Sunday Guardian's guidance. They are general troubleshooting, not a Microsoft-confirmed fix for November 16.
- Confirm your internet connection works.
- Refresh the Teams web client or restart the desktop app.
- Try Teams on another device or in another browser. If it works there, the problem is probably local to your device or session. That doesn't prove the cause.
- Update the Teams app to the latest version.
- Sign out and back in if sign-in is the problem.
- Avoid changing account or configuration settings based only on a spike on a tracker.
If the problem persists, note the time, the exact error text and which Teams function failed. Then ask your IT team whether it affects one account, one device, one network or the whole tenant. That detail speeds up diagnosis.
Bottom line
On November 16 there were scattered Teams complaints and a visible rise in Downdetector activity. There was no Microsoft confirmation of a new Teams outage in the evidence I reviewed. The confirmed incidents are from November 12–13, and some lingering effects, like the admin-portal device status issue, may explain a share of the complaints. If Teams is misbehaving for you, check Service health before you start reconfiguring anything.
References
- Microsoft Teams Outage Today: Is Microsoft Teams Down Today in the US? Users Report App, Website, Login, Chat, Video Meeting & Messaging Issues | Microsoft Teams Downdetector Status - The Sunday Guardian The Sunday Guardian · 2026-11-16T16:41:21+00:00
- Microsoft Teams Status. Check if Microsoft Teams is down or having an outage. | StatusGator statusgator.com
- Is Microsoft Teams Down? Microsoft Teams Status & Outages statusstack.com