Microsoft Teams outage history

A subset of users on Poly Microsoft Teams Rooms on Android (MTRA) devices using HP DirectConnect mode experienced call drops after about 30 seconds. The error message "Different Versions on the Touch Panel detected, ending call shortly" appeared before the call ended, disrupting meetings for those affected. The issue was limited to this setup and persisted for about half an hour.

Users in Germany, the United Kingdom, and the United States experienced outages affecting access to Microsoft Teams, with audio and video calls failing to connect and problems joining or initiating meetings. The issue showed up as an Early Warning Signal before the provider acknowledged it; StatusGator detected the issue at Sep 21, 2026 1:23 PM UTC, about 34 minutes ahead of the official acknowledgment. The Microsoft Teams status page listed the incident starting around 1:57 PM UTC, with ongoing telemetry review as engineers investigated the impact.

Users on macOS devices running the macOS 27.2 beta experienced unexpected crashes in Microsoft Teams. The impact began around 3:01 PM UTC and lasted about an hour and a half before service returned to normal for affected users. The issue appeared limited to the macOS 27.2 beta environment rather than a broader Teams outage.

Status page updates show the situation evolved: at 3:41 PM UTC the team noted the impact was limited to MacOS 27.2 beta and that the crashes were linked to video background functionality. By 4:31 PM UTC the incident was resolved and Teams was back to normal for affected users.

Users of Microsoft Teams encountered intermittent failures when launching the app from both web and desktop clients. Some users could not start Teams at all, and occasional error messages such as “Server is busy” appeared when attempting to send messages. The impact began around Sep 17, 2026 5:16 AM UTC and continued through the following day as engineers worked to restore access; service availability improved and was back to normal by Sep 18, 2026 5:01 AM UTC.

Users across Microsoft Teams faced interruptions beginning around 4:46 AM UTC as some Mac users were unable to join calls or meetings. A broader UI issue followed with the Teams chat icon missing for many users in the new chat and channels experience, affecting clients across platforms. The disruption stretched across most of the day and was resolved by 2:56 PM UTC.

Users were unable to access or manage Microsoft Teams channels, and some with active licenses could not sign in. Admins also faced difficulties accessing organization-wide settings. The issue appeared to involve channel-management APIs returning 500 and 503 errors and initially affected users in North America attempting to interact with channels.

Many Microsoft Teams users in the Asia-Pacific region experienced issues joining and creating meetings, with related features such as Live Events, 1:1 Calling, PSTN Calling, and Town Hall functionality also impacted. StatusGator detected an issue at Aug 26, 2026 1:04 AM UTC, about 44 minutes before the official acknowledgment at 1:49 AM UTC. Microsoft attributed the disruption to maintenance work on Asia-Pacific infrastructure, and reports of degraded meeting access came from major APAC cities including Tokyo, Hong Kong, Taipei, Osaka, and Manila. The incident unfolded as a widespread partial outage affecting multiple Teams capabilities for many users.

Users experienced degraded video quality when screensharing in Microsoft Teams beginning around 8:11 AM UTC. The issue affected a subset of users and persisted through the afternoon as Teams analyzed logs and telemetry to isolate the root cause, with reports describing choppy video and reduced clarity during screensharing sessions.

Microsoft Teams attributed the impact to a recent update related to meeting performance optimization and deployed a configuration update to remediate. Telemetry was monitored as the change rolled out, and by 5:36 PM UTC the deployment was completed and validation with affected users indicated the issue was remediated.

Users across North and South America reported Microsoft Teams was not loading, with additional reports of intermittent audio and video problems. The outage affected Teams across desktop and web experiences, with users seeing apps fail to load or disconnect during calls. Impact began at 2:22 PM UTC and persisted through 2:48 PM UTC as activity peaked around 2:30 PM UTC to 2:45 PM UTC, with reports from Medellín, Bogotá, Miami, Toronto, and other cities indicating a broad but not universal effect.

StatusGator detected the issue at Aug 19, 2026 2:22 PM UTC, about 27 minutes before Microsoft acknowledged the problem on its status page. There were no official status updates from Microsoft Teams during the outage. The incident presented as a partial outage with regional impact rather than a full service disruption, with symptoms including app loading failures, not loading, connectivity breaks, and intermittent audio/video across multiple locations.

During the evening, users attempting to join Microsoft Teams Live Events on the iOS mobile app could not join, while Android, desktop, and web clients remained usable. Affected users encountered errors such as “The video player stopped working,” with the issue first noted around 8:06 PM UTC as the status page moved to a degraded state. The impact persisted for about two and a half hours as Teams engineers investigated and worked to remediate. Workarounds involved using Android, desktop, or web clients to participate in Live Events during the disruption.