Microsoft Teams outages and problems
In the past 24 hours, 32 user reports came in for Microsoft Teams. Counting only the 15-minute windows with a spike big enough to count as an outage, that comes to 100.00% uptime for the day.
The busiest 15-minute window had 2 reports, about 23 hours ago. That stays below our outage threshold, so it doesn't count as downtime.
What people can report about Microsoft Teams
What went wrong
What people said was wrong in recent problem reports for Microsoft Teams worldwide.
Share of 7 recent reports that said what was wrong, from every country listed below.
Microsoft Teams reports around the world
In the last 24 hours, 166 problem reports about Microsoft Teams came in from 24 countries. Right now reports are at the usual level in every country.
- Outage now
- Problems now
- Normal
| Country | Now | Last hour | 24 hours |
|---|---|---|---|
| The US numbers above | Normal | 2 | 49 |
| Japan | Normal | 0 | 33 |
| The UK | Normal | 0 | 15 |
| Brazil | Normal | 0 | 15 |
| Canada | Normal | 0 | 10 |
| The Netherlands | Normal | 0 | 7 |
| India | Normal | 0 | 5 |
| Australia | Normal | 0 | 4 |
| Mexico | Normal | 0 | 4 |
| The Philippines | Normal | 0 | 4 |
| Germany | Normal | 0 | 3 |
| Bulgaria | Normal | 0 | 3 |
Each country's status compares its reports with the usual level there. 36 more countries had 14 reports in the last 24 hours. Map outlines: Natural Earth.
Microsoft Teams problem spikes, last 30 days
Since 5 October, Microsoft Teams had 2 outage spikes and 12 periods of elevated reports. The longest lasted 52 min, on 29 October.
- Sat 3 Oct: no data
- Sun 4 Oct: no data
- Mon 5 Oct: 4 reports
- Tue 6 Oct: 11 reports
- Wed 7 Oct: 7 reports
- Thu 8 Oct: 24 reports
- Fri 9 Oct: 8 reports
- Sat 10 Oct: 2 reports
- Sun 11 Oct: 0 reports
- Mon 12 Oct: 10 reports
- Tue 13 Oct: 7 reports
- Wed 14 Oct: 13 reports
- Thu 15 Oct: 5 reports
- Fri 16 Oct: 2 reports
- Sat 17 Oct: 3 reports
- Sun 18 Oct: 0 reports
- Mon 19 Oct: 28 reports
- Tue 20 Oct: 9 reports
- Wed 21 Oct: no data
- Thu 22 Oct: 1 report
- Fri 23 Oct: 7 reports
- Sat 24 Oct: 4 reports
- Sun 25 Oct: 1 report
- Mon 26 Oct: 28 reports
- Tue 27 Oct: 22 reports (elevated reports that day)
- Wed 28 Oct: 227 reports (elevated reports that day)
- Thu 29 Oct: 756 reports (outage spike that day)
- Fri 30 Oct: 503 reports
- Sat 31 Oct: 32 reports
- Sun 1 Nov: no data
-
Elevated reports
Thu 29 Oct, 23:19–23:48Lasted 30 min11peak reports
-
Elevated reports
Thu 29 Oct, 21:03–21:31Lasted 28 min24peak reports
-
Elevated reports
Thu 29 Oct, 19:41–20:02Lasted 20 min23peak reports
-
Outage
Thu 29 Oct, 18:41–19:07Lasted 27 min36peak reports
-
Outage
Thu 29 Oct, 15:27–16:19Lasted 52 min45peak reports
-
Elevated reports
Thu 29 Oct, 14:48–15:04Lasted 15 min27peak reports
-
Elevated reports
Thu 29 Oct, 02:09–02:39Lasted 30 min14peak reports
-
Elevated reports
Wed 28 Oct, 22:08–22:36Lasted 28 min18peak reports
6 earlier spikes in this period.
By country
Each square is one day in the countries with the most reports: red when reports stayed at outage level for half an hour or more, amber when they stayed above the usual level for an hour or more, grey otherwise.
- The US1,511
- The UK372
- Japan331
- Brazil238
- Germany222
- Canada141
- The Netherlands133
- Poland102
Country history starts on 28 October 2026. Days run from midnight to midnight, Central European time.
A spike is a sharp rise in problem reports from users, kept exactly as this page showed it at the time. This history starts on 5 October 2026. Monthly reports for all services
How to fix Microsoft Teams not working
Microsoft Teams is up on our end, so if it won't work for you, the problem is most likely on your side. Work through these in order:
Your browser tries to reach microsoft.com over your own connection, right now. Nothing is sent to us or stored.
Restart Teams
Quit the app fully, then open it again. On Windows, right-click its icon in the notification area and choose Quit; on Mac, right-click the dock icon and choose Quit. A stuck call or a frozen window often clears after a fresh start.
Sign out of Teams
Choose Sign out from your profile picture, then sign in again with the same work or school account. This refreshes the token that chat and calls rely on. Use it when the app says you are not signed in or keeps returning you to the sign-in screen.
Test Teams audio and camera
Open Settings and more (...) > Settings > Devices. Pick your audio devices and camera, then select Make a test call. The test call records a short message and plays it back so you can hear whether your audio works; if the camera does not appear, check that no other app is using it and that Windows or browser privacy settings allow camera access.
Clear Teams cache and reinstall
Quit the app, then open Settings and more (...) > Settings > Files and links > Clear cache. Reopen the app and sign in. If the problem stays, uninstall it and install it again after a restart.
While Microsoft Teams is down: what to use instead
- Web version in a browser If the desktop app hangs on the loading screen or keeps asking you to sign in, open the web version in Edge or Chrome, since a corrupted cache or broken local install won't follow you to the browser.
- Outlook email Mail often keeps flowing when chat and channels stall, so send the urgent message by email and copy everyone from the thread.
- Meeting dial-in number When the invite lists a phone number and conference ID, you can call in from any phone and still hear the meeting while the app won't connect.
- Zoom or Google Meet For a call that can't wait, start one there and send the link by email or text.
Fix Microsoft Teams on Windows, Mac, Android and iPhone
Microsoft Teams on Windows
- Fix
- To fix Microsoft Teams on Windows, close the app completely from the system tray and clear the Teams cache folder in your AppData directory. Alternatively, try using the web version in a browser to bypass desktop app issues.
- Check
- Check if Microsoft Teams is down by visiting the Microsoft 365 Service Health page or checking the official Microsoft 365 Status Twitter account. If you cannot log in via the web client either, the service is likely down.
ping microsoft.comTest whether Microsoft Teams's servers replynslookup microsoft.comCheck that Microsoft Teams's DNS resolvestracert microsoft.comTrace where the connection dropsipconfig /flushdnsClear the DNS cache, then reloadMicrosoft Teams on Mac
- Fix
- Fix Microsoft Teams on macOS by force quitting the app and clearing its cache files located in the Library folder. You can also check for and install any pending updates using the Microsoft AutoUpdate tool.
- Check
- To tell if Microsoft Teams is down on Mac, try signing into the web app using Safari or Chrome. If the web portal fails to load alongside the desktop client, Microsoft is likely experiencing a wider outage.
ping -c 4 microsoft.comTest whether Microsoft Teams's servers replynslookup microsoft.comCheck that Microsoft Teams's DNS resolvestraceroute microsoft.comTrace where the connection dropssudo dscacheutil -flushcache; sudo killall -HUP mDNSResponderFlush the macOS DNS cache, then reloadMicrosoft Teams on Android
- Fix
- Fix Microsoft Teams on Android by clearing the app's cache and storage data in your device's Settings, then restarting the app. If the issue persists, check the Google Play Store for updates or reinstall the app.
- Check
- To check if Microsoft Teams is down on Android, switch from Wi-Fi to mobile data to see if it is a local network issue. You can also check if other Microsoft 365 apps are failing to connect on your device.
Microsoft Teams on iPhone and iPad
- Fix
- Fix Microsoft Teams on iOS by offloading and reinstalling the app from the App Store, or restarting your iPhone or iPad. Ensuring your iOS software is up to date can also resolve connection and launch failures.
- Check
- Determine if Microsoft Teams is down on iOS by attempting to access the service through a mobile web browser. If the app refuses to connect while your internet works fine on other apps, Teams is likely facing an outage.
Biggest Microsoft Teams problems so far
-
1
OutageLasted 52 min45reports in 15 min
-
2
OutageLasted 27 min36reports in 15 min
-
3
Elevated reportsLasted 15 min31reports in 15 min
Ranked by the most problem reports in one 15-minute window. Our archive started on 5 October 2026, so earlier problems are not counted. Times are Central European time.
Problems at the same time as Microsoft Teams
Since 5 October, all 14 of Microsoft Teams's spikes in problem reports overlapped a spike at another service.
When several services get problem reports at once, something they share, such as a cloud host or a network, can be the real cause. Matching times alone do not prove it.
Most often at the same time
- ESPN Fantasy Football14 times
- ADP14 times
- USPS12 times
- Archive of Our Own10 times
- 3 (Three)10 times
- Spark Driver10 times
How many of Microsoft Teams's spikes overlapped one of theirs.
During the latest spike
Microsoft Teams: Thu 29 Oct, 23:19 to 23:48
- ESPN Fantasy Football, outage,27 Oct 19:50 to 30 Oct 05:40
- Archive of Our Own, outage,07:55 to 1 Nov 00:04
- Eir, outage,20:11 to 30 Oct 00:53
- FedEx, outage,20:22 to 30 Oct 00:18
- Sling, outage,20:45 to 30 Oct 04:02
- BBC iPlayer, outage,21:23 to 30 Oct 00:16
- Amazon Web Services, outage,21:45 to 30 Oct 01:21
- Santander, outage,21:49 to 23:52
43 more services. Red dot: outage. Amber dot: elevated reports.
A spike is a sharp rise in problem reports from users, as the live pages showed it. Times are Central European time.
When people report Microsoft Teams problems
The busiest hour for reports about Microsoft Teams is 14:00 to 15:00 Central European time, and the busiest day is Thursday.
By hour of the day
- 00:00 to 01:00: 1.3 reports on an average day
- 01:00 to 02:00: 0.73 reports on an average day
- 02:00 to 03:00: 0.62 reports on an average day
- 03:00 to 04:00: 0.84 reports on an average day
- 04:00 to 05:00: 0.42 reports on an average day
- 05:00 to 06:00: 0.25 reports on an average day
- 06:00 to 07:00: 0.21 reports on an average day
- 07:00 to 08:00: 0.39 reports on an average day
- 08:00 to 09:00: 0.72 reports on an average day
- 09:00 to 10:00: 1.3 reports on an average day
- 10:00 to 11:00: 1.9 reports on an average day
- 11:00 to 12:00: 1 report on an average day
- 12:00 to 13:00: 1.1 reports on an average day
- 13:00 to 14:00: 3.4 reports on an average day
- 14:00 to 15:00: 5.8 reports on an average day
- 15:00 to 16:00: 4.6 reports on an average day
- 16:00 to 17:00: 5.2 reports on an average day
- 17:00 to 18:00: 5.2 reports on an average day
- 18:00 to 19:00: 3.7 reports on an average day
- 19:00 to 20:00: 5.3 reports on an average day
- 20:00 to 21:00: 4.5 reports on an average day
- 21:00 to 22:00: 3.6 reports on an average day
- 22:00 to 23:00: 2.7 reports on an average day
- 23:00 to 00:00: 1.7 reports on an average day
By day of the week
- Monday: 21 reports on an average Monday
- Tuesday: 12 reports on an average Tuesday
- Wednesday: 69 reports on an average Wednesday
- Thursday: 169 reports on an average Thursday
- Friday: 130 reports on an average Friday
- Saturday: 10 reports on an average Saturday
- Sunday: 0.33 reports on an average Sunday
Each bar is the average number of user reports in that hour, or on that day of the week, from 24 days of reports since 5 October 2026. The busiest bar is highlighted. Spikes in reports are left out, so one outage does not set the pattern.
What happens when Microsoft Teams goes down
Microsoft Teams is chat, meetings, calls and file sharing that offices, schools and remote crews use to run the workday when email is too slow. You lose meetings first.
Chat goes first for many outages because messages stick on sending while older threads still load. You can join a meeting but get no audio or black video. You wait in lobbies. Large failures hit the desktop and web apps together, though calls and presence can fail in a region while chat works for crews in another.
Microsoft Teams IP address, servers and network
- IPv4 address
- 23.52.181.212
- IPv6 addresses
- 2a02:26f0:3400:184::356e
Show all 4
- 2a02:26f0:3400:18d::356e
- 2a02:26f0:3400:19a::356e
- 2a02:26f0:3400:19d::356e
- Network
- AS16625 · Akamai Technologies, Inc., registered in the United States
- Served through
- Microsoft Azure Front Door
- DNS hosted by
- Microsoft Azure DNS
- HTTPS certificate
- Issued by Microsoft Corporation, valid until 30 Jan 2027 (90 days)
- HTTP/3
- Not advertised
- Our check
- Answered in 78 ms
Checked from our server in Frankfurt, Germany, 3 days ago, for www.microsoft.com. A service behind a CDN answers from many data centres, usually the one nearest to you, so these addresses are where its traffic enters, not where its own servers stand. Visitors elsewhere may see different addresses.
Checked from 11 places around the world
None of check-host.net's 11 servers got an answer from www.microsoft.com (connection timed out), but our own check from Frankfurt did, 3 days ago. That usually means the site drops automated checks from those servers, not that it is down.
Checked with check-host.net from 11 cities 3 days ago, for www.microsoft.com.
Microsoft Teams FAQ
Is Microsoft Teams down right now?
Why do my Direct Messages fail to send in Teams while channel posts still go through?
Why does Teams say my account does not have permission to open a tab or file?
Why does screen sharing freeze or lag in the Teams desktop app but work in the browser?
Why does Teams keep signing me out on my phone or show missed call notifications late?
Service updates from @MicrosoftTeams
No posts about problems from @MicrosoftTeams in the last 14 days. The latest is from .
How we track Microsoft Teams
The status on this page comes from user-submitted problem reports for Microsoft Teams, counted in 15-minute windows over the last 24 hours. Each window is compared with the normal level for Microsoft Teams, so a few complaints on a quiet day don't trigger anything, but a sudden jump well above normal does.
When reports climb well above normal, the status here changes to partial outage or major outage and the chart moves with it. This is separate from Microsoft Teams's official status page: user reports tend to show a problem early, while the official page confirms the cause. If the two disagree, check both.