Skip to main content
Chrome icon

New! Check service status instantly with our Chrome extension

Add to Chrome External link icon
Firefox icon

New! Check service status instantly with our Firefox extension

Add to Firefox External link icon
magnifying glass icon
magnifying glass icon
  • Can't find service? Request service
    Sign up
    Microsoft Teams icon
    Microsoft Teams icon

    Microsoft Teams outage history

    Collaboration and communication platform for teams.

    There were 47 Microsoft Teams outages since January 2025 which are summarized below, including incident details, duration, and resolution information.

    Not working for you?

    minor icon Minor

    : Users may be unable to connect to multiple Microsoft 365 services

    Detected by StatusGator:
    Officially acknowledged:
    Outage ended: (1 day, 9 hours and 44 minutes)

    Title: Users may be unable to connect to multiple Microsoft 365 services User impact: Users may be unable to connect to multiple Microsoft 365 services. More info: Potentially impacted services include: - Exchange Online - Microsoft Teams - SharePoint Online - Microsoft Copilot 365 - Microsoft Defender XDR Current status: We’re investigating an issue impacting multiple Microsoft 365 services and we've determined the affected infrastructure is experiencing elevated load across multiple regions, which is likely contributing to the connectivity errors. We're restarting and repairing impacted portions of this infrastructure to restore capacity, and reviewing an unexpected increase in a specific type of service traffic to determine whether it's contributing to the elevated load. In parallel, we're evaluating options to redirect traffic to alternate infrastructure to expedite relief. Scope of impact: This issue may affect users attempting to access the affected Microsoft 365 services. Next update by: Thursday, November 12, 2026, at 8:30 PM UTC

    minor icon Minor

    : We're looking into a potential problem impacting Microsoft Teams

    Detected by StatusGator:
    Officially acknowledged:
    Outage ended: (34 minutes)

    Title: We're looking into a potential problem impacting Microsoft Teams User impact: We're checking for potential impact to your users. Current status: We're investigating a potential issue with Microsoft Teams and checking for impact to your organization. We'll provide an update within 30 minutes.

    minor icon Minor

    : Microsoft Teams: messaging delays and image issues

    Detected by StatusGator: (21 minutes earlier)
    Officially acknowledged:
    Outage ended: (33 minutes)

    Impact began around with connectivity issues that degraded messaging and chat performance for many users. StatusGator detected the issue at , roughly 21 minutes before Microsoft Teams acknowledged the problem. The official status then flagged a potential problem affecting images in Microsoft Teams as investigators looked for impact to organizations.

    The issue was elevated to a warning at as Microsoft Teams said they were investigating the problem and would provide updates within about 30 minutes. By the incident had been resolved and services returned to normal. During the outage, users experienced slow performance, messages delayed or not sent, and chat messages arriving out of order. The disruption appeared widespread across regions but did not constitute a full service outage.

    minor icon Minor

    : Microsoft Teams SIP calling outage impacts SIP devices

    Detected by StatusGator:
    Officially acknowledged:
    Outage ended: (9 hours and 30 minutes)

    Beginning around , Microsoft Teams users relying on SIP-based calling faced an outage that prevented making or receiving calls on SIP devices. Sign-in to affected devices could fail with a "Service Unavailable" error, and when a SIP device attempted its next synchronization, it would disconnect, leaving users unable to log back in and thus unable to place or receive calls. The disruption affected SIP endpoints broadly and also impaired calling on Teams web clients in some cases. The impact was observed across regions worldwide, with reports from North America to Europe throughout the day, indicating a broad, global effect.

    Microsoft's status updates documented ongoing degraded calling capabilities across SIP devices and Teams calling flows. The issue persisted for most of the day, with service restored by as indicators returned to normal.

    minor icon Minor

    : Microsoft Teams SIP calling outage affects SIP devices

    Detected by StatusGator:
    Officially acknowledged:
    Outage ended: (45 minutes)

    An issue in Microsoft Teams disrupted SIP-based calling for SIP endpoints, preventing them from making or receiving calls. Calling through the Teams web and desktop clients, or Teams Phone devices, remained unaffected. The problem began at when the status page indicated a degraded SIP calling experience for SIP devices, and was resolved by , lasting roughly 45 minutes. Microsoft Teams noted that affected SIP devices would disconnect on the next synchronization and could not log back in until the issue was resolved.

    minor icon Minor

    : Microsoft Teams town hall join issues redirect users to registration

    Detected by StatusGator:
    Officially acknowledged:
    Outage ended: (11 hours and 25 minutes)

    The outage began at when Microsoft Teams started listing issues joining town hall meetings, with users redirected to a registration page and the Join option sometimes unavailable or unresponsive. This primarily affected town halls created with registration disabled, disrupting live events for attendees and making access to sessions unclear.

    Microsoft Teams issued updates noting a regression and a fix was being developed. By , the team confirmed the fix development was completed and successfully tested. Subsequent updates at and described remediation progress and ongoing testing as the fix rolled out. The service remained in a degraded state until resolution around when the status returned to up.

    User reports were limited (3 total) but noted connectivity issues and slow performance from locations such as Brisbane, Montreal, and Brighton, indicating partial impact rather than a global outage. After remediation, join functionality was restored and attendees could join town halls as normal.

    major icon Major

    : Microsoft Teams meeting join blocked by sign-in errors

    Detected by StatusGator:
    Officially acknowledged:
    Outage ended: (1 day, 8 hours and 30 minutes)

    Starting at , Microsoft Teams users worldwide were unable to join meetings and encountered sign-in errors. Affected users reported a sign-in prompt that would not respond when selecting sign-in, effectively preventing access to meetings for many sessions. As a temporary mitigation, some users could sign out and sign back in to regain entry to meetings in certain cases.

    minor icon Minor

    : Microsoft 365 access via Global Secure Access impacted; recovery underway

    Detected by StatusGator:
    Officially acknowledged:
    Outage ended: (2 hours and 45 minutes)

    Users began experiencing issues accessing multiple Microsoft 365 services when using Global Secure Access (GSA) around . Affected services included Outlook, Outlook on the web, OneDrive, SharePoint Online, Microsoft Teams, and Windows 365 Cloud PCs. The impact appeared across several regions with users reporting outages or degraded access to these services.

    To address the problem, Microsoft implemented traffic management and rerouted requests to healthy infrastructure. Traffic optimizations were deployed at , and traffic was redirected to healthy infrastructure by as engineers validated improvements. A portion of the impacted infrastructure was restarted around , and by the status was back up. The incident reflected multi-region impact, with user reports coming from locations such as Chicago, Brooklyn, and London.

    minor icon Minor

    : Microsoft Teams E911 muting issue disrupts emergency calls

    Detected by StatusGator:
    Officially acknowledged:
    Outage ended: (1 day, 1 hour and 25 minutes)

    Users on Microsoft Teams conference calls involving Emergency 911 (E911) were not automatically muted, and some could not mute themselves. The issue affected organizations relying on Teams for emergency communications, potentially allowing ongoing audio during critical moments. The incident was first noted on when the Teams status page labeled the event as a warning and indicated engineers were analyzing affected meetings and IDs to understand the impact.

    Teams rolled out a code change to address the mismatch causing the muting defect. The deployment began at and, after a series of follow-up updates, the service was restored to normal at . With the fix in place, users on E911 calls could again rely on automatic muting during emergency conferences.

    minor icon Minor

    : Microsoft Teams: HP DirectConnect call drops on Poly MTRA devices

    Detected by StatusGator:
    Officially acknowledged:
    Outage ended: (30 minutes)

    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.

    Microsoft Teams icon

    Looking for more Microsoft Teams outage stats?

    Get real-time insights and historical data on Microsoft Teams outages.

    Microsoft Teams outage stats