Is Microsoft Teams down?

homeHistory

Incident history, with updates and resolution

  • chevron_right 2022-09-29 12:48:46: We're investigating an issue preventing users in North American from accessing SharePoint Online and OneDrive for Business content. Please refer to SP440666 and OD440667 in the Microsoft 365 admin center for further details.
    Resolution time: 2h 18m 31s
    Update count: 2link
    • access_time 2022-09-29 13:33:03 - update: We're rerouting traffic to alternative service infrastructure to restore access. Our telemetry shows that affected users are experiencing relief as this process completes. Please refer to SP440666 and OD440667 in the Microsoft 365 admin center for further info.
    • done_all 2022-09-29 15:07:17 - resolution: We've finished rerouting all affected traffic to health infrastructure and after a period of observation, we've confirmed that service is restored. Please refer to SP440666 and OD440667 in the Microsoft 365 admin center for additional details.
  • chevron_right 2022-09-26 04:48:38: We're investigating an issue affecting multiple functions within Microsoft Teams with impact limited to users hosted in South Africa. Please see TM439057 on the Service Health Dashboard in the admin center for more information.
    Resolution time: 1h 10m 08s
    Update count: 1link
    • done_all 2022-09-26 05:58:46 - resolution: We've completed redirecting traffic to healthy infrastructure. After a period of monitoring, we've confirmed the service is restored and the issue is resolved. For additional information, please see TM439057 on the Service Health Dashboard in the admin center.
  • chevron_right 2022-09-07 06:31:16: We're investigating an issue where some users hosted in the Europe region may experience degraded performance with multiple Microsoft 365 services and features. For more details and further updates, please follow the SI MO427469 in your admin center.
    Resolution time: 6h 44m 33s
    Update count: 4link
    • access_time 2022-09-07 07:36:03 - update: We're reviewing network diagnostics to isolate the source of the issue and rerouting connections to alternate database infrastructure to provide relief. Further details can be found under MO427469 in the admin center.
    • access_time 2022-09-07 10:48:40 - update: We continue to reroute connections for the impacted Microsoft 365 services to healthy components to provide relief whilst we investigate the underlying issue. Further info can be found under MO427469 in the admin center.
    • access_time 2022-09-07 11:35:49 - update: We're investigating a potential root cause for this issue and are preparing an action plan to address the impact. In parallel, we're continuing to take supplemental actions to provide relief within the environment. More details can be found in the admin center under MO427469.
    • done_all 2022-09-07 13:15:49 - resolution: We've confirmed that service has been restored after rerouting connections to healthy components. Additional information can be found in the admin center under MO427469.
  • chevron_right 2022-08-24 17:28:59: We're aware of and investigating an issue wherein some users in the Japan region may be unable to access Microsoft Teams using any connection method. More information is available under the post TM419392 within the M365 admin center.
    Resolution time: 16h 27m 50s
    Update count: 6link
    • access_time 2022-08-24 18:12:15 - update: We've determined that this issue could impact any user in the Asia-Pacific-region. We've identified a recent change that may be causing this issue, and we're in the process of rolling it back. More information is available under the post TM419392 within the M365 admin center.
    • access_time 2022-08-24 19:41:25 - update: We've finished reverting our change and are seeing signs of recovery. We will continue to monitor the service to ensure the issue is fully resolved. More information is available under the post TM419392 within the M365 admin center.
    • access_time 2022-08-24 21:43:39 - update: We're currently addressing residual impact related to this event. Additional information can be found under the post TM419392 within the M365 admin center.
    • access_time 2022-08-24 22:48:22 - update: Our monitoring indicates that a majority of previously impacted users have been resolved. If you are experiencing residual impact, please sign out and sign back into your Teams instance. More information is available under the post TM419392 within the M365 admin center.
    • access_time 2022-08-24 23:17:18 - update: We are still addressing residual impact, which we anticipate will take some time to fully resolve. If you are still impacted please refer to our previous tweet or TM419392 within the M365 admin center for additional steps and information.
    • done_all 2022-08-25 09:56:49 - resolution: We've validated that the service has been restored. Additional information about this event can be found in the admin center under TM419392.
  • chevron_right 2022-08-24 07:40:13: We're investigating an issue where some users in Finland and Sweden may be unable to access Microsoft 365 services. Please look for MO419156 in the admin center or visit https://t.co/4yJVZgATZ8.
    Resolution time: 1h 03m 49s
    Update count: 2link
    • access_time 2022-08-24 08:25:22 - update: We're seeing full recovery of the affected services and we're continuing to monitor to confirm the issue is resolved. For additional details, see MO419156 in the admin center or visit https://t.co/4yJVZgRX18.
    • done_all 2022-08-24 08:44:02 - resolution: We've confirmed the issue is resolved. Additional details are available in the admin center under MO419156.
  • chevron_right 2022-08-24 06:53:42: We're investigating an issue where users are experiencing unexpected crashes or freezing when using the Microsoft Forms service. For more details please look for FM419115 in the admin center.
    Resolution time: 3h 27m 18s
    Update count: 2link
    • access_time 2022-08-24 08:03:00 - update: While we continue our analysis of diagnostic data to confirm the root cause, our roll back to a previous good configuration is progressing on schedule. For more information, please look for FM419115 in the admin center.
    • done_all 2022-08-24 10:21:00 - resolution: We identified a recent update to the service that resulted in unexpected impact to the Forms service. We reverted the impact and have performed validation checks to ensure that service has been restored. For more details, please look for FM419115 in the admin center.
  • chevron_right 2022-08-10 05:44:50: We're investigating an issue where some users in the EMEA region are unable to connect to some Microsoft 365 services. More details are available in the admin center under the SI MO411804.
    Resolution time: 6h 50m 16s
    Update count: 3link
    • access_time 2022-08-10 07:17:31 - update: Our investigation is focused on a potential issue where legitimate Microsoft traffic is being blocked across multiple regions. More details are available in your admin center under the SI MO411804.
    • access_time 2022-08-10 11:34:48 - update: We're working with our firewall partners to investigate snort rule 1-60381. We've received confirmation from some affected users that disabling the rule provides immediate relief. Additional information can be found in the admin center under MO411804.
    • done_all 2022-08-10 12:35:06 - resolution: The third-party provider has disabled the affected snort rule and anticipate that the change should fully propagate within 1-2 hours. We've verified that this change will mitigate impact for all users. Additional details are available in the admin center under MO411804.
  • chevron_right 2022-07-28 09:40:53: We've received reports from some admins in North America that they're unable to access the Microsoft 365 admin center. Additional information can be found at https://t.co/lbjX5hSWLp or under MO406459 in the Microsoft 365 admin center.
    Resolution time: 7h 28m 57s
    Update count: 3link
    • access_time 2022-07-28 10:18:09 - update: We're restarting the affected infrastructure to mitigate impact. Further, we've confirmed that impact is not isolated to admins in North America. Additional information can be found at https://t.co/AEUj8uj65N or under MO406459 in the Microsoft 365 admin center, if accessible.
    • access_time 2022-07-28 14:09:58 - update: Our restarts have progressed successfully, and we expect the majority of admins will experience relief from impact at this time. We're restarting the remaining infrastructure to fully resolve the issue, and more details can be found at https://t.co/AEUj8uAGXl or under MO406459.
    • done_all 2022-07-28 17:09:50 - resolution: We've completed our restarts in all remaining infrastructure and have verified that the issue has been resolved. Final details can be found under MO406459 within the admin center.
  • chevron_right 2022-07-20 18:47:50: We've received reports of users being unable to access Microsoft Teams or leverage any features. We're investigating the issue and further updates can be found in your Service Health Dashboard via TM402718.
    Resolution time: 18h 22m 48s
    Update count: 8link
    • access_time 2022-07-20 20:02:05 - update: We've determined that a recent deployment contained a broken connection to an internal storage service, which has resulted in impact. We're working to direct traffic to a healthy service to mitigate impact. Additional information can be found in the admin center under TM402718.
    • access_time 2022-07-20 20:20:29 - update: Some users have reported that they are unable to access the admin center to view updates. Please navigate to https://t.co/AEUj8uAGXl for additional information.
    • access_time 2022-07-20 20:45:27 - update: We've identified downstream impact to multiple Microsoft 365 services with Teams integration, such as Microsoft Word, Office Online and SharePoint Online. We're providing updates for those services via MO402741 in the admin center or through https://t.co/AEUj8uAGXl.
    • access_time 2022-07-20 21:13:22 - update: Our telemetry indicates that Microsoft Teams functionality is beginning to recover. We're continuing our efforts to implement relief within the environment. Additional information can be found under TM402718, MO402741, or at https://t.co/AEUj8uAGXl.
    • access_time 2022-07-20 23:15:10 - update: We are continuing to see improvements to the affected Microsoft Teams functionality. We're focused on mitigating the remaining impact. Additional information can be found under TM402718, MO402741, or at https://t.co/4yJVZgRX18.
    • access_time 2022-07-21 00:57:54 - update: Service availability has mostly recovered with only a few service features still requiring attention. We'll continue to monitor the service while the remaining actions are completed. Additional information can be found under TM402718, MO402741, or at https://t.co/9K8fcFL5Ka.
    • done_all 2022-07-21 05:02:13 - resolution: We believe that the majority of services have recovered. We're continuing to monitor the issue to ensure there is no residual impact. More details can be found under TM402718, MO402741, or at https://t.co/AEUj8uj65N.
    • done_all 2022-07-21 13:10:38 - resolution: We've confirmed healthy service availability via internal telemetry, and observed no further instances of impact following our recovery actions. More details are provided under TM402718 and MO402741 in the admin center.
  • chevron_right 2022-07-18 06:55:05: We're investigating an issue with users accessing or experiencing degraded functionality when using Exchange Online and https://t.co/gk7xXJQBz5 services. More details are available in your admin center under EX401976 and OL401977.
    Resolution time: 2h 35m 58s
    Update count: 2link
    • access_time 2022-07-18 07:44:03 - update: We suspect there may be unexpected network drops which are contributing to the degraded experience and are reviewing diagnostic logs to understand why. More details are available in your admin center under EX401976 and OL401977.
    • done_all 2022-07-18 09:31:03 - resolution: We identified a section of our network infrastructure that was performing below acceptable thresholds. We've rerouted connections to alternate infrastructure and that confirmed the issue is resolved. For more details, please check EX401976 and OL401977 in the admin center