Microsoft Teams service status
Check whether the provider lists a problem with the feature you use. Look at the update time and any affected regions.
Live Domain Check
Run a live reachability check for teams.microsoft.com. Compare the regional responses with the problem you see in Microsoft Teams.
Find Microsoft Teams help and reporting links, specific checks, and step-by-step guidance below the live result.
Checking reachability from multiple regions.
Share a quick update and see what other visitors are experiencing.
What’s happening? Choose one to send your report.
Loading community reports…
—problem reports
—working reports
No problems reported in this period.
Visitor reports are separate from our automated checks and don’t confirm an outage. How reports work · Privacy
Teams chat, meeting join, calling and file access can have different service dependencies.
The checker above requests teams.microsoft.com from eight configured locations and shows the responses and measurement times. Compare those observations with the actual Microsoft Teams action that failed. A homepage response alone cannot verify an account, app workflow or transaction.
Distinguish Microsoft account access from mail, storage and meetings using the relevant product check: Microsoft Account status check, Microsoft Entra status check, Microsoft 365 status check. Compare results separately; these links do not establish a shared outage.
Looking for another service? Browse messaging checks.
Check whether the provider lists a problem with the feature you use. Look at the update time and any affected regions.
An authorised administrator may need tenant-specific Service Health and support.
Open the website in your browser and compare it with the result above.
Open Microsoft Teams help / reporting. Use the provider's customer-service or account-help route for the affected product. Sign-in may be required for private account questions.
Tenant, meeting/chat/call action, client version, UTC time and available error/correlation ID.
Attach the checker’s downloaded JSON if it helps show the hostname, regional responses and original timestamps. Describe what happened in your browser or app as well. A report sent to WebsiteDown.org is not automatically forwarded to Microsoft Teams.
These are troubleshooting comparisons, not claims that Microsoft Teams is currently experiencing a particular incident.
Record which action fails and compare the same organisation in the web client and an already signed-in app.
Check the relevant tenant service-health information; for files, test the linked SharePoint/OneDrive item separately.
A 403 Forbidden or 429 Too Many Requests means the host answered but refused or limited that request. A timeout gives no HTTP response. Keep those outcomes separate and check the available-region count before treating the result as broad evidence.
Use these local troubleshooting steps after the down-check workflow when Microsoft Teams seems broken only for you. This section focuses on app, browser, account, and network fixes.
Open teams.microsoft.com in your current browser, then test in a private window or second browser. If only one session fails, compare its account, cookie and extension context before assuming the entire service is unavailable.
Keep an existing working session and preserve unsaved work. For a sign-in failure, use the official account-help route. Avoid repeated password or security resets until you confirm this is not a broader Microsoft Teams issue.
If possible, compare Wi-Fi with mobile data and note which one fails. Leave any required work VPN or security settings in place.
Save timestamp, device, network type, exact error, final URL, and status code. Use the check workflow above before contacting Microsoft Teams support.
Run the teams.microsoft.com check and compare its original timestamps and responses with your actual error. Teams chat, meeting join, calling and file access can have different service dependencies.
Use the community buttons on this page to share whether the service works for you. For help from Microsoft Teams, use the official help/reporting resource linked above. An authorised administrator may need tenant-specific Service Health and support.
Record which action fails and compare the same organisation in the web client and an already signed-in app. Check the relevant tenant service-health information; for files, test the linked SharePoint/OneDrive item separately.
Tenant, meeting/chat/call action, client version, UTC time and available error/correlation ID.