Skip to main content
Microsoft Teams logo

Is Microsoft Teams Down?

No — Microsoft Teams is up

Reachable from all 8 checked regions

Average response time: 780ms

Last checked · checks run every 6 hours

Official status page: https://status.cloud.microsoft

Microsoft Teams uptime

100%
Last 7 days
100%
Last 30 days
100%
Last 90 days
935ms
Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 31 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

31-day clean streak
Aug 22: 100.00% uptime, 32 checks
Aug 23: 100.00% uptime, 40 checks
Aug 24: 100.00% uptime, 24 checks
Aug 25: 100.00% uptime, 32 checks
Aug 26: 100.00% uptime, 32 checks
Aug 27: 100.00% uptime, 32 checks
Aug 28: 100.00% uptime, 32 checks
Aug 29: 100.00% uptime, 32 checks
Aug 30: 100.00% uptime, 32 checks
Aug 31: 100.00% uptime, 32 checks
Sep 1: 100.00% uptime, 32 checks
Sep 2: 100.00% uptime, 24 checks
Sep 3: 100.00% uptime, 29 checks
Sep 4: 100.00% uptime, 32 checks
Sep 5: 100.00% uptime, 24 checks
Sep 6: 100.00% uptime, 28 checks
Sep 7: 100.00% uptime, 21 checks
Sep 8: 100.00% uptime, 53 checks
Sep 9: 100.00% uptime, 32 checks
Sep 10: 100.00% uptime, 32 checks
Sep 11: 100.00% uptime, 32 checks
Sep 12: 100.00% uptime, 32 checks
Sep 13: 100.00% uptime, 24 checks
Sep 14: 100.00% uptime, 31 checks
Sep 15: 100.00% uptime, 32 checks
Sep 16: 100.00% uptime, 32 checks
Sep 17: 100.00% uptime, 32 checks
Sep 18: 100.00% uptime, 32 checks
Sep 19: 100.00% uptime, 32 checks
Sep 20: 100.00% uptime, 16 checks
Aug 22 Today
No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

jnb
2138ms
DNS 340ms TCP 1ms TLS 6ms TTFB 1629ms
lax
349ms
DNS 158ms TCP 9ms TLS 35ms TTFB 347ms
lhr
481ms
DNS 61ms TCP 2ms TLS 10ms TTFB 450ms
nrt
849ms
DNS 102ms TCP 9ms TLS 23ms TTFB 810ms
ord
717ms
DNS 260ms TCP 17ms TLS 42ms TTFB 635ms
sin
715ms
DNS 28ms TCP 1ms TLS 9ms TTFB 702ms
sjc
367ms
DNS 91ms TCP 9ms TLS 35ms TTFB 366ms
syd
626ms
DNS 28ms TCP 1ms TLS 8ms TTFB 602ms

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 18 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.
  • 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. We only change the 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. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when Microsoft Teams goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from up to 18 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required