Microsoft Teams outage history

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.

An issue in Microsoft Teams blocked some users from creating or publishing town hall and webinar events that include guest users. The disruption began at Jul 29, 2026 7:51 AM UTC and persisted through most of the next day, with organizers reporting they could not schedule or publish events involving external guests. While many other Teams features remained available, the guest-event workflow was the primary area of impact, and user reports also described related login or joining problems in some cases. The incident appeared across multiple regions, indicating a global impact limited to event creation for guest participants rather than a full service outage.

Microsoft Teams' status updates attributed the root cause to a code regression introduced by a recent standard service update. A fix was developed and validated, and deployment to affected environments began. Progress updates described ongoing validation and staged rollout, with some deployment attempts briefly delaying full restoration. By Jul 30, 2026 5:26 PM UTC the team stated that the fix had been validated and deployed and the incident was resolved, restoring guest-event creation for affected users.

Users across the globe experienced an outage that prevented joining or creating Microsoft Teams meetings and calls, with widespread disruption to transcripts, 1:1 and group calling, meeting join, and meeting scheduling, as well as PSTN calls. The issue affected desktop and mobile clients, hampering workflows for teams trying to connect. Impact began around 12:37 AM UTC, and StatusGator detected the issue about 1 hour 44 minutes before the official acknowledgment. The incident generated a large volume of user reports as the disruption spread in the early hours.

Microsoft Teams posted updates starting at 2:21 AM UTC noting an impacted set of scenarios and telemetry confirming the issue; a follow-up at 2:26 AM UTC reaffirmed the degraded service. The incident was resolved by 3:21 AM UTC, with recovery taking place over roughly three hours. In the interim, users reported ongoing difficulties joining meetings and making or receiving calls, with many experiencing intermittent connectivity or failing to load meeting links.

Users across the North America region faced degraded Microsoft 365 services with Microsoft Teams affected, along with intermittent OneDrive and SharePoint Online access. People reported trouble joining meetings, viewing and sharing documents, and loading images or attachments, with some messages delayed. Impact began around 2:51 PM UTC; Microsoft acknowledged the issue at 6:00 PM UTC and noted a recent network configuration change may be contributing to the disruption as traffic was rerouted.

Users of Microsoft Teams experienced a messaging outage that prevented sending or receiving messages and caused delays across mobile, web, and desktop clients. Reports spanned numerous U.S. regions with some international locations also affected, indicating a broad impact on chat functionality. The outage began at 1:57 PM UTC and persisted for a little over an hour, with many users reporting slow message delivery and chats failing to load or send.

Microsoft did not publish an official incident update on the Office 365 status page during the event. StatusGator recorded an Early Warning Signal starting at Jul 7, 2026 1:57 PM UTC for problems sending and receiving messages, ending at 3:09 PM UTC. The incident shows a clear pattern of user-reported outages across multiple regions, while the provider's status feed remained silent during the incident.

Impact began around 12:15 AM UTC and was largely resolved by 1:37 AM UTC. During the window, users reported widespread inability to access Teams features such as chat, meetings, and calls. Many saw the generic outage message: 'Our services aren't available right now. We're working to restore all services as soon as possible. Please check back soon.' The disruption was global, with affected users across North America, Europe, Asia-Pacific, and South America.

StatusGator detected the issue at Jun 24, 2026 12:15 AM UTC, ahead of any official acknowledgment on the Microsoft Teams status page. No official Teams status updates appear in the provided feed. User reports surged from around 1:00 AM UTC and continued through 1:30 AM UTC, with people in Tokyo, Auckland, Sydney, Lima, and other cities reporting outages and reconnect attempts. The outage appears global in scope, affecting core collaboration features for a broad set of customers.

From Feb 11, 2026 9:00 AM UTC to Feb 11, 2026 2:34 PM UTC UTC, users across Europe, the United Kingdom, and North America reported that the Microsoft Teams Assignments module would not load, preventing viewing or submitting assignments. Reports described assignment pages failing to load, timeouts, and blank screens, disrupting classroom workflows for students and educators. The outage appeared centered on the Assignments feature within Microsoft Teams, with other Teams functionality largely unaffected.

The outage began at 4:56 PM UTC and was resolved by 6:01 PM UTC. Microsoft Teams, part of Microsoft 365, experienced degraded messaging, chat failures, and video call issues during this period. User reports from the United States and Europe described chat not sending, laggy calls, and intermittent connectivity across Teams. The outage lasted about 1 hour and 5 minutes before services returned to normal.

Microsoft's official status updates acknowledged an investigation into a potential issue affecting Microsoft 365 services and noted that updates would be provided within 30 minutes. The incident concluded with services returning to normal by 18:01 UTC.

The outage began at Dec 19, 2025 7:08 PM UTC and was resolved by Dec 19, 2025 8:35 PM UTC. StatusGator detected the issue at Dec 19, 2025 7:08 PM UTC, ahead of any official acknowledgment. During the incident, Microsoft Teams users experienced an outage impacting messaging and image loading, with reports of delayed messages, inability to send messages, and images not displaying; some users also had trouble joining meetings. The outage lasted approximately 1 hour and 27 minutes.

There were no official status updates posted on the Office 365 status page during the incident. The incident drew a high volume of user reports across multiple regions, indicating broad geographic reach in North America and parts of Europe, with widespread performance degradation and intermittent outages across messaging, image loading, and meeting features.