Skip to content

Outage tracker / Microsoft Teams

Is Microsoft Teams down?

I'm having a problem

Checks passingchecked 2 minutes ago

Our checks of Microsoft Teams pass from all 10 regions we check.

As of Nov 5, 2026, 2:02 PM UTC, RealUptime's checks of Microsoft Teams passed in all 10 regions that returned a reading.

Front-door and live API checks

Our checks of Microsoft Teams did not fail from two or more distant regions in the 89 days we have checked it (since Aug 8, 2026). This does not show Microsoft Teams works for users.

Email me when our checks of Microsoft Teams fail from two or more distant regions

One email when our checks of Microsoft Teams fail from two or more distant regions, and one when they pass, after you confirm the address. No account, no card.

This is our own reading from outside. It is not Microsoft Teams's official status.

our check readinglive · checked Nov 5, 2026, 2:02 PM UTC
US-East3538 msChecks passing
US-West4233 msChecks passing
Europe3065 msChecks passing
Asia-Pacific7210 msChecks passing
US-Central2724 msChecks passing
Canada2781 msChecks passing
UK2431 msChecks passing
Southeast Asia3444 msChecks passing
Australia3122 msChecks passing
South America2640 msChecks passing
their status pagetheir claim, not our reading

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

Microsoft Teams response time, by region

US-East
4.9sp95 · latest
10s5s0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 10s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 1.4s2026-10-08 UTC: p95 1.5s2026-10-09 UTC: p95 1.4s2026-10-10 UTC: p95 1.5s2026-10-11 UTC: p95 1.2s2026-10-12 UTC: p95 1.3s2026-10-13 UTC: p95 1.6s2026-10-14 UTC: p95 1.8s2026-10-15 UTC: p95 2.0s2026-10-16 UTC: p95 2.0s2026-10-17 UTC: p95 3.0s2026-10-18 UTC: p95 4.5s2026-10-19 UTC: p95 4.9s2026-10-20 UTC: p95 3.9s2026-10-21 UTC: p95 4.5s2026-10-22 UTC: p95 3.1s2026-10-23 UTC: p95 3.4s2026-10-24 UTC: p95 4.4s2026-10-25 UTC: p95 4.5s2026-10-26 UTC: p95 6.7s2026-10-27 UTC: p95 4.5s2026-10-28 UTC: p95 3.9s2026-10-29 UTC: p95 3.4s2026-10-30 UTC: p95 3.1s2026-10-31 UTC: p95 4.5s2026-11-01 UTC: p95 4.4s2026-11-02 UTC: p95 5.7s2026-11-03 UTC: p95 4.5s2026-11-04 UTC: p95 4.4s2026-11-05 UTC: p95 4.9s
Oct 7Oct 21Nov 5
US-West
5.4sp95 · latest
10s5s0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 10s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 1.5s2026-10-08 UTC: p95 1.6s2026-10-09 UTC: p95 2.4s2026-10-10 UTC: p95 810ms2026-10-11 UTC: p95 1.1s2026-10-12 UTC: p95 1.1s2026-10-13 UTC: p95 1.8s2026-10-14 UTC: p95 1.7s2026-10-15 UTC: p95 1.8s2026-10-16 UTC: p95 1.8s2026-10-17 UTC: p95 2.6s2026-10-18 UTC: p95 2.9s2026-10-19 UTC: p95 2.8s2026-10-20 UTC: p95 3.2s2026-10-21 UTC: p95 3.9s2026-10-22 UTC: p95 4.7s2026-10-23 UTC: p95 4.4s2026-10-24 UTC: p95 3.9s2026-10-25 UTC: p95 4.3s2026-10-26 UTC: p95 5.6s2026-10-27 UTC: p95 5.1s2026-10-28 UTC: p95 4.9s2026-10-29 UTC: p95 4.8s2026-10-30 UTC: p95 3.9s2026-10-31 UTC: p95 4.1s2026-11-01 UTC: p95 4.2s2026-11-02 UTC: p95 5.3s2026-11-03 UTC: p95 5.3s2026-11-04 UTC: p95 5.4s2026-11-05 UTC: p95 5.4s
Oct 7Oct 21Nov 5
Europe
4.0sp95 · latest
10s5s0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 10s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 1.0s2026-10-08 UTC: p95 1.2s2026-10-09 UTC: p95 1.2s2026-10-10 UTC: p95 1.3s2026-10-11 UTC: p95 1.6s2026-10-12 UTC: p95 1.7s2026-10-13 UTC: p95 764ms2026-10-14 UTC: p95 1.2s2026-10-15 UTC: p95 1.5s2026-10-16 UTC: p95 672ms2026-10-17 UTC: p95 1.6s2026-10-18 UTC: p95 1.7s2026-10-19 UTC: p95 1.9s2026-10-20 UTC: p95 1.8s2026-10-21 UTC: p95 1.4s2026-10-22 UTC: p95 1.5s2026-10-23 UTC: p95 1.7s2026-10-24 UTC: p95 1.6s2026-10-25 UTC: p95 1.6s2026-10-26 UTC: p95 1.8s2026-10-27 UTC: p95 1.9s2026-10-28 UTC: p95 1.8s2026-10-29 UTC: p95 2.2s2026-10-30 UTC: p95 2.1s2026-10-31 UTC: p95 2.1s2026-11-01 UTC: p95 2.4s2026-11-02 UTC: p95 5.2s2026-11-03 UTC: p95 4.1s2026-11-04 UTC: p95 4.6s2026-11-05 UTC: p95 4.0s
Oct 7Oct 21Nov 5
Asia-Pacific
6.0sp95 · latest
10s5s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 10s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 2.2s2026-10-08 UTC: p95 2.1s2026-10-09 UTC: p95 2.7s2026-10-10 UTC: p95 2.6s2026-10-11 UTC: p95 2.4s2026-10-12 UTC: p95 2.2s2026-10-13 UTC: p95 2.2s2026-10-14 UTC: p95 1.9s2026-10-15 UTC: p95 2.4s2026-10-16 UTC: p95 2.2s2026-10-17 UTC: p95 5.8s2026-10-18 UTC: p95 6.2s2026-10-19 UTC: p95 5.4s2026-10-20 UTC: p95 5.4s2026-10-21 UTC: p95 6.3s2026-10-22 UTC: p95 6.9s2026-10-23 UTC: p95 7.2s2026-10-24 UTC: p95 7.0s2026-10-25 UTC: p95 7.2s2026-10-26 UTC: p95 8.8s2026-10-27 UTC: p95 6.7s2026-10-28 UTC: p95 6.5s2026-10-29 UTC: p95 7.0s2026-10-30 UTC: p95 7.0s2026-10-31 UTC: p95 6.6s2026-11-01 UTC: p95 6.9s2026-11-02 UTC: p95 7.7s2026-11-03 UTC: p95 5.9s2026-11-04 UTC: p95 6.1s2026-11-05 UTC: p95 6.0s
Oct 7Oct 21Nov 5
US-Central
2.9sp95 · latest
5s2.5s0ms
US-Central response time (p95) over the last 30 daysDaily 95th-percentile response time for US-Central, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 2.1s2026-10-08 UTC: p95 1.9s2026-10-09 UTC: p95 1.5s2026-10-10 UTC: p95 1.5s2026-10-11 UTC: p95 1.7s2026-10-12 UTC: p95 2.3s2026-10-13 UTC: p95 2.1s2026-10-14 UTC: p95 2.1s2026-10-15 UTC: p95 1.8s2026-10-16 UTC: p95 1.9s2026-10-17 UTC: p95 1.9s2026-10-18 UTC: p95 2.0s2026-10-19 UTC: p95 1.8s2026-10-20 UTC: p95 1.9s2026-10-21 UTC: p95 3.1s2026-10-22 UTC: p95 3.3s2026-10-23 UTC: p95 4.0s2026-10-24 UTC: p95 3.9s2026-10-25 UTC: p95 4.0s2026-10-26 UTC: p95 4.8s2026-10-27 UTC: p95 4.2s2026-10-28 UTC: p95 4.3s2026-10-29 UTC: p95 3.5s2026-10-30 UTC: p95 3.5s2026-10-31 UTC: p95 4.5s2026-11-01 UTC: p95 3.6s2026-11-02 UTC: p95 3.7s2026-11-03 UTC: p95 4.2s2026-11-04 UTC: p95 3.4s2026-11-05 UTC: p95 2.9s
Oct 7Oct 21Nov 5
Canada
2.2sp95 · latest
5s2.5s0ms
Canada response time (p95) over the last 30 daysDaily 95th-percentile response time for Canada, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 1.6s2026-10-08 UTC: p95 1.5s2026-10-09 UTC: p95 1.4s2026-10-10 UTC: p95 1.4s2026-10-11 UTC: p95 1.6s2026-10-12 UTC: p95 1.4s2026-10-13 UTC: p95 1.5s2026-10-14 UTC: p95 1.9s2026-10-15 UTC: p95 2.0s2026-10-16 UTC: p95 1.8s2026-10-17 UTC: p95 2.4s2026-10-18 UTC: p95 2.4s2026-10-19 UTC: p95 2.4s2026-10-20 UTC: p95 2.4s2026-10-21 UTC: p95 3.2s2026-10-22 UTC: p95 3.3s2026-10-23 UTC: p95 3.2s2026-10-24 UTC: p95 3.4s2026-10-25 UTC: p95 3.2s2026-10-26 UTC: p95 3.7s2026-10-27 UTC: p95 3.8s2026-10-28 UTC: p95 3.8s2026-10-29 UTC: p95 3.9s2026-10-30 UTC: p95 3.5s2026-10-31 UTC: p95 4.2s2026-11-01 UTC: p95 4.0s2026-11-02 UTC: p95 3.7s2026-11-03 UTC: p95 2.2s2026-11-04 UTC: p95 3.6s2026-11-05 UTC: p95 2.2s
Oct 7Oct 21Nov 5
UK
2.7sp95 · latest
5s2.5s0ms
UK response time (p95) over the last 30 daysDaily 95th-percentile response time for UK, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 904ms2026-10-08 UTC: p95 721ms2026-10-09 UTC: p95 1.4s2026-10-10 UTC: p95 1.3s2026-10-11 UTC: p95 1.0s2026-10-12 UTC: p95 1.3s2026-10-13 UTC: p95 932ms2026-10-14 UTC: p95 1.2s2026-10-15 UTC: p95 898ms2026-10-16 UTC: p95 928ms2026-10-17 UTC: p95 1.4s2026-10-18 UTC: p95 2.3s2026-10-19 UTC: p95 2.8s2026-10-20 UTC: p95 1.8s2026-10-21 UTC: p95 1.5s2026-10-22 UTC: p95 1.6s2026-10-23 UTC: p95 1.7s2026-10-24 UTC: p95 1.7s2026-10-25 UTC: p95 1.9s2026-10-26 UTC: p95 2.0s2026-10-27 UTC: p95 2.8s2026-10-28 UTC: p95 3.3s2026-10-29 UTC: p95 2.8s2026-10-30 UTC: p95 3.0s2026-10-31 UTC: p95 2.5s2026-11-01 UTC: p95 2.5s2026-11-02 UTC: p95 2.6s2026-11-03 UTC: p95 2.2s2026-11-04 UTC: p95 2.0s2026-11-05 UTC: p95 2.7s
Oct 7Oct 21Nov 5
Southeast Asia
6.4sp95 · latest
10s5s0ms
Southeast Asia response time (p95) over the last 30 daysDaily 95th-percentile response time for Southeast Asia, scaled to a maximum of 10s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 3.0s2026-10-08 UTC: p95 2.2s2026-10-09 UTC: p95 2.2s2026-10-10 UTC: p95 2.5s2026-10-11 UTC: p95 2.8s2026-10-12 UTC: p95 2.7s2026-10-13 UTC: p95 2.7s2026-10-14 UTC: p95 2.5s2026-10-15 UTC: p95 1.7s2026-10-16 UTC: p95 2.2s2026-10-17 UTC: p95 5.8s2026-10-18 UTC: p95 6.1s2026-10-19 UTC: p95 6.9s2026-10-20 UTC: p95 6.1s2026-10-21 UTC: p95 7.3s2026-10-22 UTC: p95 8.0s2026-10-23 UTC: p95 7.1s2026-10-24 UTC: p95 7.5s2026-10-25 UTC: p95 8.4s2026-10-26 UTC: p95 7.7s2026-10-27 UTC: p95 6.5s2026-10-28 UTC: p95 6.0s2026-10-29 UTC: p95 6.3s2026-10-30 UTC: p95 6.5s2026-10-31 UTC: p95 6.2s2026-11-01 UTC: p95 8.2s2026-11-02 UTC: p95 5.7s2026-11-03 UTC: p95 6.1s2026-11-04 UTC: p95 6.2s2026-11-05 UTC: p95 6.4s
Oct 7Oct 21Nov 5
Australia
7.0sp95 · latest
10s5s0ms
Australia response time (p95) over the last 30 daysDaily 95th-percentile response time for Australia, scaled to a maximum of 10s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 1.8s2026-10-08 UTC: p95 2.0s2026-10-09 UTC: p95 2.0s2026-10-10 UTC: p95 1.8s2026-10-11 UTC: p95 2.1s2026-10-12 UTC: p95 2.3s2026-10-13 UTC: p95 2.1s2026-10-14 UTC: p95 1.9s2026-10-15 UTC: p95 1.7s2026-10-16 UTC: p95 1.5s2026-10-17 UTC: p95 3.6s2026-10-18 UTC: p95 3.5s2026-10-19 UTC: p95 3.1s2026-10-20 UTC: p95 4.3s2026-10-21 UTC: p95 3.8s2026-10-22 UTC: p95 3.3s2026-10-23 UTC: p95 3.5s2026-10-24 UTC: p95 4.3s2026-10-25 UTC: p95 6.0s2026-10-26 UTC: p95 6.2s2026-10-27 UTC: p95 6.2s2026-10-28 UTC: p95 4.4s2026-10-29 UTC: p95 4.5s2026-10-30 UTC: p95 4.2s2026-10-31 UTC: p95 5.7s2026-11-01 UTC: p95 3.8s2026-11-02 UTC: p95 4.6s2026-11-03 UTC: p95 5.4s2026-11-04 UTC: p95 7.6s2026-11-05 UTC: p95 7.0s
Oct 7Oct 21Nov 5
South America
8.0sp95 · latest
10s5s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 10s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 2.4s2026-10-08 UTC: p95 2.4s2026-10-09 UTC: p95 2.1s2026-10-10 UTC: p95 2.9s2026-10-11 UTC: p95 3.2s2026-10-12 UTC: p95 2.9s2026-10-13 UTC: p95 2.4s2026-10-14 UTC: p95 2.3s2026-10-15 UTC: p95 2.4s2026-10-16 UTC: p95 2.6s2026-10-17 UTC: p95 5.2s2026-10-18 UTC: p95 5.1s2026-10-19 UTC: p95 5.4s2026-10-20 UTC: p95 6.2s2026-10-21 UTC: p95 7.1s2026-10-22 UTC: p95 5.3s2026-10-23 UTC: p95 8.1s2026-10-24 UTC: p95 5.7s2026-10-25 UTC: p95 5.7s2026-10-26 UTC: p95 5.6s2026-10-27 UTC: p95 5.5s2026-10-28 UTC: p95 6.4s2026-10-29 UTC: p95 5.7s2026-10-30 UTC: p95 5.9s2026-10-31 UTC: p95 6.1s2026-11-01 UTC: p95 5.2s2026-11-02 UTC: p95 7.4s2026-11-03 UTC: p95 7.4s2026-11-04 UTC: p95 8.1s2026-11-05 UTC: p95 8.0s
Oct 7Oct 21Nov 5

Check your own site while you wait on Microsoft Teams

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 we measured, function by function

Microsoft Teams answers on more than one surface, and they can fail apart. Each row is one surface, checked from the same regions. The verdict above follows the web row, because that is the surface we treat as this service's own; a failure on any other row is a partial outage, not a full one.

  • WebprimaryUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
  • APIUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
  • Chat serviceUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
  • Microsoft sign-inUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
  • Teams (free)US-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
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 our checks show, and what people reported

  • North America
    Checks passingUS-East, US-West, US-Central, Canada
    • US-East
      Checks passinglatency: 3538msstatus code: 200checked: Nov 5, 2026, 2:01 PM 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
      Checks passinglatency: 4233msstatus code: 200checked: Nov 5, 2026, 1:55 PM 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
      Checks passinglatency: 2724msstatus code: 200checked: Nov 5, 2026, 2:01 PM 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
      Checks passinglatency: 2781msstatus code: 200checked: Nov 5, 2026, 1:59 PM 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
    Checks passinglatency: 2640msstatus code: 200checked: Nov 5, 2026, 1:59 PM 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
    Checks passingEurope, UK
    • Europe
      Checks passinglatency: 3065msstatus code: 200checked: Nov 5, 2026, 1:58 PM 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
      Checks passinglatency: 2431msstatus code: 200checked: Nov 5, 2026, 1:57 PM 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
    Checks passingAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Checks passinglatency: 7210msstatus code: 200checked: Nov 5, 2026, 2:02 PM 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
      Checks passinglatency: 3444msstatus code: 200checked: Nov 5, 2026, 1:54 PM 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
      Checks passinglatency: 3122msstatus code: 200checked: Nov 5, 2026, 1:56 PM 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 probe events

No probe events on record yet for Microsoft Teams.

check 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 check readings and Microsoft Teams's own claim at the time, side by side.

Full check history for Microsoft Teams: 90 days of check results by region, month-by-month uptime by our checks, and every probe event on record.

Put this badge in your README

Microsoft Teams uptime by RealUptime's checksLive, from this page's own readings.
[![Microsoft Teams uptime by RealUptime's checks](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 by RealUptime's checks" height="20"></a>

Share of checks passed over 30 days; the window is printed on it. If our readings go stale it says stale, and if we have no readings it says so and shows no color. How the badge works.

To cite this page: RealUptime, "Is Microsoft Teams down?", https://realuptime.io/outages/microsoft-teams. The readings change with every check, so give the date you read them.

How our checks compare with Microsoft Teams's stated SLA

At or above your target

Our checks of Microsoft Teams failed for none over the last 30 days, which is 100% uptime by our checks. A 99.9% target allows 43 minutes over that period.

Our checks show no gap in this period. That does not rule out one you saw.

These figures come from our own checks of one public endpoint per service. They are not the service's real uptime. This is computed from our own checks, 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/
secondaryfunctional: live API
https://graph.microsoft.com/v1.0/
secondary
https://login.microsoftonline.com/common/v2.0/.well-known/openid-configuration
secondary
https://teams.microsoft.com/api/chatsvc/amer/v1/users/ME/conversations
secondary
https://teams.live.com/v2

What our check can and cannot see

A pass means the service's public web page loaded and answered normally. It does not show that the product, the API or sign-in behind it works; a page can load from a cache while the product is down.

Host checked: teams.microsoft.com

RealUptime is not affiliated with Microsoft Teams; the name identifies what we checked, 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. At least one endpoint we check for Microsoft Teams is a real functional API call (marked “functional” above), not just a landing page, so a passing check there says an API answered, though it still does not show that every feature of the service works for you. Read the full methodology.