Microsoft Teams status

How we check Microsoft Teams

We watch teams.microsoft.com from all five of our probe regions, every 2 minutes. A region that sees a failure does not make this page say "down" on its own: a second region has to agree first, the same confirmation rule every YoPingMe monitor uses.

We watch Teams' own web client host and pin the response an anonymous request receives, rather than assuming a 2xx. Teams shares its status page with the rest of Microsoft 365 but is operated as its own service with its own components, so a Teams-specific reading is more direct than the bundled dashboard.

What is Microsoft Teams?

Microsoft Teams combines chat, video calls, and file collaboration into one client, and it sits under the same Microsoft 365 umbrella as Outlook and the Office apps while being operated as its own service with its own components on Microsoft's status page. That distinction matters because Teams can have an incident of its own while the rest of Microsoft 365 works fine, and the reverse is equally common.

Joining a meeting is the step most worth separating from the rest of what can go wrong, because it fails for reasons that have nothing to do with whether Teams itself is running. A calendar invite whose time was changed after the link was shared, a lobby the organiser has not opened yet, or a corporate network blocking the ports the Teams client needs will all stop someone from joining while Teams answers normally for everyone else. None of this shows up as an incident, because nothing on Microsoft's side has actually failed.

Once a meeting is underway, it tends to hold up better than the process of getting into one. Establishing a new connection does more work than maintaining an existing one, so a brief platform hiccup more often blocks new joins than it drops people already on a call, and a call that is interrupted typically reconnects on its own rather than needing to be recreated from scratch.

Presence is a specific Teams quirk worth understanding on its own terms. The status shown next to someone's name is calculated from calendar data, whether their Teams window currently has focus, and recent activity, which means it can briefly show "available" for someone who just joined a call, or "in a meeting" for someone who left one a minute ago. This lag is a property of how presence is computed, not a platform fault, and it settles within a minute or two without anyone needing to do anything.

The practical approach to depending on Teams for something that matters, an interview, a client meeting, an all-hands, is to treat most join failures as local rather than platform-wide: check the link, the lobby, and the network before suspecting Teams itself, and use the Microsoft 365 admin center's tenant-specific health page when the question is whether your organisation specifically is affected.

Frequently asked questions

Is Microsoft Teams down right now?

Check the board above; it reflects our own probes against Teams from all five of our regions, refreshed every couple of minutes and confirmed across two regions before this page would call it down.

I cannot join a Teams meeting but this page shows Teams up. What should I check?

Check the meeting link and your own network first, since these stop far more joins than a platform issue does. A meeting scheduled through a calendar that has since had its time changed, a lobby the organiser has not admitted people from, or a restrictive network blocking the ports the Teams client needs will all block a join while Teams itself answers normally.

Does a Teams outage affect calls or meetings already in progress?

Not usually. An established call tends to be more resilient than the process of joining one, so a brief platform issue is more likely to block new joins than to drop people already connected. A dropped call that does happen typically reconnects on its own once the underlying issue clears.

My status shows as available when I am actually in a meeting. Is that a Teams problem?

Rarely a platform one. Presence in Teams is calculated from calendar data, active window focus, and recent activity, and it can lag behind reality by a short window, especially right after a meeting starts or ends. This is a property of how presence is computed rather than a fault, and it corrects itself within a minute or two in most cases.

How is this page different from the Microsoft 365 admin center's service health?

That page reports what Microsoft has confirmed internally, scoped to your own tenant's licensed services, which is more relevant to your organisation than any outside probe could be. This page reports what our own probes measured against Teams specifically, from outside Microsoft's infrastructure, on a fixed schedule, whether or not Microsoft has posted an update yet.