Skip to content

Outage tracker / Microsoft Teams

Is Microsoft Teams down?

I'm having a problem

Operationalchecked 1 minute ago

We reached Microsoft Teams from all 10 regions we check.

As of Sep 23, 2026, 9:10 AM UTC, Microsoft Teams answered RealUptime's probes in all 10 regions that returned a reading.

Reachability verified

No outage recorded in the 46 days we have measured Microsoft Teams (since Aug 8, 2026).

our independent probeslive · checked Sep 23, 2026, 9:10 AM UTC
US-East1691 msOperational
US-West846 msOperational
Europe1250 msOperational
Asia-Pacific1905 msOperational
US-Central1878 msOperational
Canada987 msOperational
UK1463 msOperational
Southeast Asia2303 msOperational
Australia1089 msOperational
South America1871 msOperational
their status pagetheir claim, not our reading

Microsoft Teams publishes no status feed we can read, so the only independent reading here is ours on the left.

Microsoft Teams response time, by region

US-East
1.7sp95 · latest
2s1s0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-08-25 UTC: p95 1.7s2026-08-26 UTC: p95 1.4s2026-08-27 UTC: p95 1.4s2026-08-28 UTC: p95 2.0s2026-08-29 UTC: p95 1.7s2026-08-30 UTC: p95 1.6s2026-08-31 UTC: p95 1.6s2026-09-01 UTC: p95 1.8s2026-09-02 UTC: p95 1.8s2026-09-03 UTC: p95 1.9s2026-09-04 UTC: p95 1.4s2026-09-05 UTC: p95 1.1s2026-09-06 UTC: p95 1.5s2026-09-07 UTC: p95 1.1s2026-09-08 UTC: p95 1.3s2026-09-09 UTC: p95 1.6s2026-09-10 UTC: p95 1.5s2026-09-11 UTC: p95 1.7s2026-09-12 UTC: p95 1.3s2026-09-13 UTC: p95 1.4s2026-09-14 UTC: p95 1.2s2026-09-15 UTC: p95 1.2s2026-09-16 UTC: p95 1.6s2026-09-17 UTC: p95 1.5s2026-09-18 UTC: p95 1.4s2026-09-19 UTC: p95 1.2s2026-09-20 UTC: p95 1.5s2026-09-21 UTC: p95 1.3s2026-09-22 UTC: p95 1.4s2026-09-23 UTC: p95 1.7s
Aug 25Sep 8Sep 23
US-West
1.7sp95 · latest
2s1s0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-08-25 UTC: p95 1.0s2026-08-26 UTC: p95 1.3s2026-08-27 UTC: p95 1.7s2026-08-28 UTC: p95 1.3s2026-08-29 UTC: p95 1.4s2026-08-30 UTC: p95 1.2s2026-08-31 UTC: p95 1.2s2026-09-01 UTC: p95 1.1s2026-09-02 UTC: p95 1.4s2026-09-03 UTC: p95 1.6s2026-09-04 UTC: p95 1.3s2026-09-05 UTC: p95 1.4s2026-09-06 UTC: p95 1.2s2026-09-07 UTC: p95 1.1s2026-09-08 UTC: p95 945ms2026-09-09 UTC: p95 894ms2026-09-10 UTC: p95 791ms2026-09-11 UTC: p95 746ms2026-09-12 UTC: p95 769ms2026-09-13 UTC: p95 748ms2026-09-14 UTC: p95 713ms2026-09-15 UTC: p95 1.4s2026-09-16 UTC: p95 1.5s2026-09-17 UTC: p95 1.3s2026-09-18 UTC: p95 1.4s2026-09-19 UTC: p95 1.4s2026-09-20 UTC: p95 1.4s2026-09-21 UTC: p95 1.5s2026-09-22 UTC: p95 1.6s2026-09-23 UTC: p95 1.7s
Aug 25Sep 8Sep 23
Europe
2.1sp95 · latest
2.5s1.3s0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-08-25 UTC: p95 838ms2026-08-26 UTC: p95 987ms2026-08-27 UTC: p95 968ms2026-08-28 UTC: p95 1.1s2026-08-29 UTC: p95 1.5s2026-08-30 UTC: p95 780ms2026-08-31 UTC: p95 1.3s2026-09-01 UTC: p95 1.0s2026-09-02 UTC: p95 1.3s2026-09-03 UTC: p95 1.2s2026-09-04 UTC: p95 1.3s2026-09-05 UTC: p95 1.2s2026-09-06 UTC: p95 795ms2026-09-07 UTC: p95 723ms2026-09-08 UTC: p95 744ms2026-09-09 UTC: p95 1.8s2026-09-10 UTC: p95 1.9s2026-09-11 UTC: p95 1.7s2026-09-12 UTC: p95 1.8s2026-09-13 UTC: p95 1.7s2026-09-14 UTC: p95 1.3s2026-09-15 UTC: p95 1.4s2026-09-16 UTC: p95 2.0s2026-09-17 UTC: p95 2.5s2026-09-18 UTC: p95 1.9s2026-09-19 UTC: p95 2.3s2026-09-20 UTC: p95 2.3s2026-09-21 UTC: p95 2.4s2026-09-22 UTC: p95 2.3s2026-09-23 UTC: p95 2.1s
Aug 25Sep 8Sep 23
Asia-Pacific
2.4sp95 · latest
5s2.5s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-08-25 UTC: p95 2.1s2026-08-26 UTC: p95 1.8s2026-08-27 UTC: p95 1.8s2026-08-28 UTC: p95 2.0s2026-08-29 UTC: p95 2.1s2026-08-30 UTC: p95 1.6s2026-08-31 UTC: p95 1.7s2026-09-01 UTC: p95 1.9s2026-09-02 UTC: p95 1.9s2026-09-03 UTC: p95 2.7s2026-09-04 UTC: p95 2.0s2026-09-05 UTC: p95 1.5s2026-09-06 UTC: p95 1.6s2026-09-07 UTC: p95 1.5s2026-09-08 UTC: p95 1.8s2026-09-09 UTC: p95 1.8s2026-09-10 UTC: p95 1.9s2026-09-11 UTC: p95 1.8s2026-09-12 UTC: p95 1.7s2026-09-13 UTC: p95 1.6s2026-09-14 UTC: p95 2.0s2026-09-15 UTC: p95 2.0s2026-09-16 UTC: p95 1.7s2026-09-17 UTC: p95 2.2s2026-09-18 UTC: p95 2.4s2026-09-19 UTC: p95 2.0s2026-09-20 UTC: p95 2.2s2026-09-21 UTC: p95 2.1s2026-09-22 UTC: p95 2.0s2026-09-23 UTC: p95 2.4s
Aug 25Sep 8Sep 23
US-Central
1.9sp95 · latest
2.5s1.3s0ms
US-Central response time (p95) over the last 30 daysDaily 95th-percentile response time for US-Central, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 2.1s2026-09-04 UTC: p95 2.3s2026-09-05 UTC: p95 2.1s2026-09-06 UTC: p95 1.8s2026-09-07 UTC: p95 1.6s2026-09-08 UTC: p95 1.8s2026-09-09 UTC: p95 1.4s2026-09-10 UTC: p95 1.5s2026-09-11 UTC: p95 1.6s2026-09-12 UTC: p95 1.6s2026-09-13 UTC: p95 1.5s2026-09-14 UTC: p95 1.5s2026-09-15 UTC: p95 1.6s2026-09-16 UTC: p95 1.6s2026-09-17 UTC: p95 1.3s2026-09-18 UTC: p95 1.4s2026-09-19 UTC: p95 1.6s2026-09-20 UTC: p95 1.4s2026-09-21 UTC: p95 1.4s2026-09-22 UTC: p95 1.8s2026-09-23 UTC: p95 1.9s
Aug 25Sep 8Sep 23
Canada
1.5sp95 · latest
2s1s0ms
Canada response time (p95) over the last 30 daysDaily 95th-percentile response time for Canada, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 1.5s2026-09-04 UTC: p95 1.2s2026-09-05 UTC: p95 1.5s2026-09-06 UTC: p95 1.5s2026-09-07 UTC: p95 1.3s2026-09-08 UTC: p95 1.4s2026-09-09 UTC: p95 1.3s2026-09-10 UTC: p95 1.3s2026-09-11 UTC: p95 1.4s2026-09-12 UTC: p95 1.2s2026-09-13 UTC: p95 1.1s2026-09-14 UTC: p95 909ms2026-09-15 UTC: p95 1.2s2026-09-16 UTC: p95 957ms2026-09-17 UTC: p95 886ms2026-09-18 UTC: p95 915ms2026-09-19 UTC: p95 850ms2026-09-20 UTC: p95 888ms2026-09-21 UTC: p95 1.1s2026-09-22 UTC: p95 1.2s2026-09-23 UTC: p95 1.5s
Aug 25Sep 8Sep 23
UK
1.4sp95 · latest
2s1s0ms
UK response time (p95) over the last 30 daysDaily 95th-percentile response time for UK, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 795ms2026-09-04 UTC: p95 780ms2026-09-05 UTC: p95 694ms2026-09-06 UTC: p95 955ms2026-09-07 UTC: p95 810ms2026-09-08 UTC: p95 799ms2026-09-09 UTC: p95 850ms2026-09-10 UTC: p95 1.0s2026-09-11 UTC: p95 831ms2026-09-12 UTC: p95 1.2s2026-09-13 UTC: p95 1.2s2026-09-14 UTC: p95 1.3s2026-09-15 UTC: p95 1.4s2026-09-16 UTC: p95 1.5s2026-09-17 UTC: p95 1.7s2026-09-18 UTC: p95 1.5s2026-09-19 UTC: p95 1.4s2026-09-20 UTC: p95 1.2s2026-09-21 UTC: p95 1.3s2026-09-22 UTC: p95 1.6s2026-09-23 UTC: p95 1.4s
Aug 25Sep 8Sep 23
Southeast Asia
3.4sp95 · latest
5s2.5s0ms
Southeast Asia response time (p95) over the last 30 daysDaily 95th-percentile response time for Southeast Asia, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 2.8s2026-09-04 UTC: p95 2.5s2026-09-05 UTC: p95 2.3s2026-09-06 UTC: p95 2.1s2026-09-07 UTC: p95 2.1s2026-09-08 UTC: p95 1.8s2026-09-09 UTC: p95 1.6s2026-09-10 UTC: p95 2.1s2026-09-11 UTC: p95 2.1s2026-09-12 UTC: p95 2.3s2026-09-13 UTC: p95 2.2s2026-09-14 UTC: p95 2.1s2026-09-15 UTC: p95 2.1s2026-09-16 UTC: p95 2.1s2026-09-17 UTC: p95 1.8s2026-09-18 UTC: p95 2.2s2026-09-19 UTC: p95 2.2s2026-09-20 UTC: p95 2.4s2026-09-21 UTC: p95 2.8s2026-09-22 UTC: p95 3.6s2026-09-23 UTC: p95 3.4s
Aug 25Sep 8Sep 23
Australia
1.6sp95 · latest
5s2.5s0ms
Australia response time (p95) over the last 30 daysDaily 95th-percentile response time for Australia, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 2.6s2026-09-04 UTC: p95 2.8s2026-09-05 UTC: p95 2.4s2026-09-06 UTC: p95 2.4s2026-09-07 UTC: p95 2.0s2026-09-08 UTC: p95 1.6s2026-09-09 UTC: p95 2.0s2026-09-10 UTC: p95 2.0s2026-09-11 UTC: p95 2.4s2026-09-12 UTC: p95 2.0s2026-09-13 UTC: p95 2.6s2026-09-14 UTC: p95 2.3s2026-09-15 UTC: p95 2.3s2026-09-16 UTC: p95 1.5s2026-09-17 UTC: p95 2.1s2026-09-18 UTC: p95 2.4s2026-09-19 UTC: p95 2.9s2026-09-20 UTC: p95 2.4s2026-09-21 UTC: p95 2.5s2026-09-22 UTC: p95 2.3s2026-09-23 UTC: p95 1.6s
Aug 25Sep 8Sep 23
South America
3.3sp95 · latest
5s2.5s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 2.6s2026-09-04 UTC: p95 3.6s2026-09-05 UTC: p95 3.4s2026-09-06 UTC: p95 3.0s2026-09-07 UTC: p95 2.1s2026-09-08 UTC: p95 2.7s2026-09-09 UTC: p95 3.4s2026-09-10 UTC: p95 3.7s2026-09-11 UTC: p95 3.4s2026-09-12 UTC: p95 3.5s2026-09-13 UTC: p95 3.2s2026-09-14 UTC: p95 3.6s2026-09-15 UTC: p95 3.4s2026-09-16 UTC: p95 4.0s2026-09-17 UTC: p95 4.1s2026-09-18 UTC: p95 2.9s2026-09-19 UTC: p95 3.1s2026-09-20 UTC: p95 3.6s2026-09-21 UTC: p95 3.5s2026-09-22 UTC: p95 3.4s2026-09-23 UTC: p95 3.3s
Aug 25Sep 8Sep 23

Is it Microsoft Teams, or is it you?

Watching an outage above does not tell you whether your own connection or site is also having a problem. Enter your own URL for one live check, right now, no signup. This checks the site you enter, not Microsoft Teams -- it cannot diagnose Microsoft Teams's own systems.

What are you seeing? (optional)

No account needed, and we never store your IP address. Reports are counted separately from our own measurements and are always shown as unverified.

What we measured, and what people reported

  • North America
    OperationalUS-East, US-West, US-Central, Canada
    • US-East
      Operationallatency: 1691msstatus code: 200checked: Sep 23, 2026, 9:10 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach Microsoft Teams normally. We do not have enough reports from US-East to say anything about what people there are seeing.
    • US-West
      Operationallatency: 846msstatus code: 200checked: Sep 23, 2026, 9:05 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach Microsoft Teams normally. We do not have enough reports from US-West to say anything about what people there are seeing.
    • US-Central
      Operationallatency: 1878msstatus code: 200checked: Sep 23, 2026, 9:09 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-Central probes reach Microsoft Teams normally. We do not have enough reports from US-Central to say anything about what people there are seeing.
    • Canada
      Operationallatency: 987msstatus code: 200checked: Sep 23, 2026, 9:02 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Canada probes reach Microsoft Teams normally. We do not have enough reports from Canada to say anything about what people there are seeing.
  • South America
    Operationallatency: 1871msstatus code: 200checked: Sep 23, 2026, 9:06 AM UTC
    0 people in the last 5 minutesNot enough reports to sayOur South America probes reach Microsoft Teams normally. We do not have enough reports from South America to say anything about what people there are seeing.
  • Europe
    OperationalEurope, UK
    • Europe
      Operationallatency: 1250msstatus code: 200checked: Sep 23, 2026, 9:08 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach Microsoft Teams normally. We do not have enough reports from Europe to say anything about what people there are seeing.
    • UK
      Operationallatency: 1463msstatus code: 200checked: Sep 23, 2026, 9:04 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur UK probes reach Microsoft Teams normally. We do not have enough reports from UK to say anything about what people there are seeing.
  • Asia Pacific
    OperationalAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Operationallatency: 1905msstatus code: 200checked: Sep 23, 2026, 9:07 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach Microsoft Teams normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
    • Southeast Asia
      Operationallatency: 2303msstatus code: 200checked: Sep 23, 2026, 9:01 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Southeast Asia probes reach Microsoft Teams normally. We do not have enough reports from Southeast Asia to say anything about what people there are seeing.
    • Australia
      Operationallatency: 1089msstatus code: 200checked: Sep 23, 2026, 8:55 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Australia probes reach Microsoft Teams normally. We do not have enough reports from Australia to say anything about what people there are seeing.

Somewhere else or not sure: 0 people in the last 5 minutes

These are unverified reports from people using Microsoft Teams, counted separately from what our own probes measure. Anyone can file one, no account is needed, and the region on a report is chosen by the person filing it. We never open, extend or close an outage in our record based on report volume: only our own measurements do that. We have not received any reports for Microsoft Teams yet, which is not evidence that nothing is wrong.

Recent outages

No outages on record yet for Microsoft Teams.

measured entries are our own probes' readings; declared entries are the vendor's. How this check works

We have been measuring Microsoft Teams since August 8, 2026. We show nothing from before that date, and we never add an outage we did not observe ourselves, from any source.

Need this in writing? Generate an SLA evidence report for Microsoft Teams covering any window you pick, with our measurements and Microsoft Teams's own claim at the time, side by side.

Full availability history for Microsoft Teams: 90-day availability by region, month-by-month uptime, and every incident on record.

Monitor your own site the same way

This page shows what we see when we check this service, using the same ten regions, for a site you run. RealUptime Monitor watches your own servers from inside your network, and it starts free.

Start monitoring your own servers

Tell me when this goes down

Get told when we measure this

We will tell you when our probes stop reaching Microsoft Teams, and again when they can reach it again. That is our own measurement from ten regions, not Microsoft Teams's status page. No account, no card.

Delivery channel

Double opt-in: nothing is sent until you click the link in the confirmation email. One email when a measured outage opens, one when it closes, and a one-click unsubscribe in every one. We do not send anything else to this address.

Put this badge in your README

Microsoft Teams uptime measured by RealUptimeLive, from this page's own readings.
[![Microsoft Teams uptime measured by RealUptime](https://realuptime.io/outages/microsoft-teams/badge.svg?days=30)](https://realuptime.io/outages/microsoft-teams)
<a href="https://realuptime.io/outages/microsoft-teams"><img src="https://realuptime.io/outages/microsoft-teams/badge.svg?days=30" alt="Microsoft Teams uptime measured by RealUptime"></a>

The badge shows the share of our probes that succeeded over the last 30 days, and the window is printed on it so the number always says what period it covers. If our readings go stale it says stale, and if we have no readings it says so: it will not show green on data we cannot vouch for. Free, no account, and it links back here. See how the badge works for every window and the honesty rules behind it.

What Microsoft Teams's SLA implies, from our measurement

At or above your target

We measured none of downtime for Microsoft Teams over the last 30 days, which is 100% uptime by our reading. A 99.9% target allows 43 minutes over that period.

By our measurement there is no shortfall to claim for this period.

This is computed from our own probe measurements, not from Microsoft Teams's SLA instrumentation. Their contract is normally measured against their own systems, with their own exclusions and a claim window, so their figure and ours will differ. Use this to start the conversation and ask for their number. It is not legal advice and it is not a determination of what you are owed.

What we check

primary
https://teams.microsoft.com/
secondary
https://graph.microsoft.com/v1.0/
RealUptime is not affiliated with Microsoft Teams; the name identifies what we measured, and nothing here speaks for Microsoft Teams's own team. We send a single web request to Microsoft Teams from 10 regions on our own schedule and time the response. We do not see inside Microsoft Teams's systems, do not use an account or real transaction, and are not the same signal Microsoft Teams's own team has access to. Treat this as one external data point, not a verdict. What we check for Microsoft Teams proves reachability only: the endpoints above answer, but that does not confirm the underlying product or account features work. Read the full methodology.