Is Microsoft Teams Down?

No — Microsoft Teams is up

Microsoft Teams's status page: Not available · we could not read it
FlareWarden checks: Website reachable · 8 of 8 regions · 850 ms

Right now

We could not read Microsoft Teams's status page, so the verdict rests on our checks. Check it yourself How we decide

FlareWarden checks

cloud.microsoft from 8 regions · when you open this page (at most every 30 minutes), otherwise every 6 hours

Reachable

Regions up: 8 of 8
Response: 850 ms
Checked: 4 hours ago

By region

Ashburn reachable, 395 ms
Chicago reachable, 1007 ms
Frankfurt reachable, 513 ms
Johannesburg reachable, 1980 ms
London reachable, 298 ms
Los Angeles reachable, 544 ms
São Paulo reachable, 1435 ms
Tokyo reachable, 635 ms

Timing by region

Connection timing for each region that loaded the page
Region	DNS	TCP	TLS	TTFB
Ashburn	119 ms	2 ms	11 ms	381 ms
Chicago	291 ms	20 ms	43 ms	1007 ms
Frankfurt	49 ms	3 ms	11 ms	487 ms
Johannesburg	357 ms	2 ms	9 ms	1461 ms
London	32 ms	2 ms	8 ms	234 ms
Los Angeles	196 ms	10 ms	28 ms	501 ms
São Paulo	195 ms	3 ms	11 ms	919 ms
Tokyo	100 ms	9 ms	25 ms	634 ms

We check that cloud.microsoft loads, not every feature behind it. Test it yourself

History

Microsoft Teams website availability

Measured by FlareWarden · cloud.microsoft

Last 7 days: 100%
Last 30 days: 100%
Last 90 days: 100%
Avg response, 30 days: 1024ms

Last 30 days

77-day clean streak

Oct 7 Today

No downtime Partial Downtime Not measurable No data

Measured by FlareWarden's own checks of cloud.microsoft from multiple regions every 6 hours. Microsoft Teams's status page sets the verdict above when it reports trouble, but never these figures. Percentages count only checks that returned an availability answer — 77 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

What Microsoft Teams does

Microsoft Teams carries chat, meetings, calling and shared files for organisations on Microsoft 365. It sits on the same identity and service fabric as Exchange Online and SharePoint, so it is rarely the only thing affected when something breaks. For many companies it is the default channel for internal communication, which makes an outage visible to everyone at once.

What an outage looks like

Messages sit with a pending marker and never send, or arrive out of order once the backlog clears. Meetings fail to join with a generic connection error, or join with audio but no video and no screen share. Presence indicators freeze on an old state. Files shared in a channel will not open because the underlying SharePoint site is affected too. The desktop client keeps showing cached history.

What to do about it

status.cloud.microsoft is the page to use when you cannot sign in to your tenant at all. Everything tenant-specific sits behind Health then Service health in the Microsoft 365 admin center, which needs an admin account. Microsoft calls an issue an advisory when some users are affected but the service works, and an incident when a major function is unavailable. Planned maintenance never appears there; it goes to the Message center.

Is it down for everyone, or just you?

If this page says Microsoft Teams is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 17 cities across three regions to find out where it breaks.

Test it yourself

Related services

Microsoft Teams outage FAQ

Is Teams down for everyone or just my organisation?

Microsoft splits this deliberately. The public page at status.cloud.microsoft carries known issues that stop tenants signing in, while incidents scoped to your own tenant appear only in the Microsoft 365 admin center under Health then Service health. An issue affecting your company alone will never show on the public page, so an all-clear there does not mean your users are fine.

What do the statuses on Microsoft's service health page mean?

Microsoft uses a fixed set: Investigating while it gathers scope, Service degradation when a feature is slow or intermittent, Service interruption when users cannot access the service at all, Restoring service once corrective action is under way, and Extended recovery when the fix is applied but has not reached every system. Service restored closes it, and False positive means no impact was found.

Will messages I sent during an outage be lost?

Messages stuck with a pending marker have not left the client and will usually send once connectivity returns, arriving with their original timestamps. The risk is duplication rather than loss, because retyping a message that later flushes leaves two copies. Give the client time to drain its queue before repeating yourself, and check the channel afterwards.

Does a Teams outage mean Outlook and SharePoint are affected too?

Frequently, because they share identity and platform services underneath. The Service health overview lists every Microsoft 365 service side by side for exactly this reason, and a shared dependency failing tends to light up several rows at once. If only Teams is affected while Exchange Online and SharePoint stay healthy, the fault is narrower.

How can I be told about the next one automatically?

Admins can subscribe within the admin center by choosing Customize then Email under Service health, selecting notifications for incidents or advisories and naming up to two addresses per admin account. Notifications can also be set for one active issue at a time. Microsoft also posts broad events to @MSFT365Status on X.

How we measure this

We request Microsoft Teams's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them. When you open this page and our last check is more than 30 minutes old, we check again on the spot; those checks update the verdict, never the availability figures.
A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
A single failing region is treated as probe noise. Our checks only change their verdict when two consecutive cycles agree.
Response times average only the regions that actually served the page, so a timeout never inflates the number.
Where Microsoft Teams publishes an official status feed we read it too, and the verdict is the worse of what it reports and what our checks see: a major outage of Microsoft Teams itself is Down, trouble with one part of it is Degraded, problems at a few of a provider's many locations change nothing, and a security notice that marks nothing down is shown but changes nothing either. A reading counts for 45 minutes; we read the feed again within minutes of any change to its incidents. The availability figures above are our measurement alone.

Get alerted when Microsoft Teams goes down

We check Microsoft Teams every 6 hours, and again when you open this page if that was more than 30 minutes ago. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring

Free plan available No credit card required