What does reachable from NexIP mean?
The monitored web endpoint returned a successful HTTP response from the NexIP location. This does not guarantee that messaging, calls, login or other features work for every user or region.
Work and communication
HTTP-проверка из точки NexIP успешна. Доступность из всех регионов не подтверждена.
The monitored web endpoint returned a successful HTTP response from the NexIP location. This does not guarantee that messaging, calls, login or other features work for every user or region.
Reports over 24 hours, signals over 15 minutes and the outage index measure different periods and conditions. Their values may differ without being contradictory.
Service monitoring
Мониторинг доступности сервиса Microsoft Teams, пользовательских сигналов и технических проверок NexIP.
Reports submitted to NexIP. One report does not prove a widespread outage.
No reports during this period.
30-minute intervals · Moscow time · actual dataLast 7 days
Observation points
Observation history
Actual NexIP primary probe measurements, not user reports
| Time (server) | Checks | Average | Peak | Down | Blocked |
|---|---|---|---|---|---|
| 2026-11-17 19:30:00 | 1 | 943 ms | 943 ms | 0 | 0 |
| 2026-11-17 19:35:00 | 1 | 837 ms | 837 ms | 0 | 0 |
| 2026-11-17 19:45:00 | 1 | 840 ms | 840 ms | 0 | 0 |
| 2026-11-17 19:55:00 | 1 | 969 ms | 969 ms | 0 | 0 |
| 2026-11-17 20:05:00 | 1 | 1 010 ms | 1 010 ms | 0 | 0 |
| 2026-11-17 20:10:00 | 1 | 968 ms | 968 ms | 0 | 0 |
| 2026-11-17 20:20:00 | 1 | 950 ms | 950 ms | 0 | 0 |
| 2026-11-17 20:25:00 | 1 | 1 044 ms | 1 044 ms | 0 | 0 |
| 2026-11-17 20:35:00 | 1 | 2 726 ms | 2 726 ms | 0 | 0 |
| 2026-11-17 20:45:00 | 1 | 884 ms | 884 ms | 0 | 0 |
| 2026-11-17 20:50:00 | 1 | 2 046 ms | 2 046 ms | 0 | 0 |
| 2026-11-17 21:00:00 | 1 | 1 050 ms | 1 050 ms | 0 | 0 |
| 2026-11-17 21:05:00 | 1 | 1 040 ms | 1 040 ms | 0 | 0 |
| 2026-11-17 21:15:00 | 1 | 905 ms | 905 ms | 0 | 0 |
| 2026-11-17 21:25:00 | 1 | 958 ms | 958 ms | 0 | 0 |
| 2026-11-17 21:30:00 | 1 | 887 ms | 887 ms | 0 | 0 |
| 2026-11-17 21:40:00 | 1 | 838 ms | 838 ms | 0 | 0 |
| 2026-11-17 21:45:00 | 1 | 788 ms | 788 ms | 0 | 0 |
| 2026-11-17 21:55:00 | 1 | 843 ms | 843 ms | 0 | 0 |
| 2026-11-17 22:05:00 | 1 | 1 009 ms | 1 009 ms | 0 | 0 |
| 2026-11-17 22:10:00 | 1 | 1 245 ms | 1 245 ms | 0 | 0 |
| 2026-11-17 22:20:00 | 1 | 816 ms | 816 ms | 0 | 0 |
| 2026-11-17 22:30:00 | 1 | 956 ms | 956 ms | 0 | 0 |
| 2026-11-17 22:35:00 | 1 | 964 ms | 964 ms | 0 | 0 |
| 2026-11-17 22:45:00 | 1 | 945 ms | 945 ms | 0 | 0 |
| 2026-11-17 22:50:00 | 1 | 972 ms | 972 ms | 0 | 0 |
| 2026-11-17 23:00:00 | 1 | 1 030 ms | 1 030 ms | 0 | 0 |
| 2026-11-17 23:10:00 | 1 | 844 ms | 844 ms | 0 | 0 |
| 2026-11-17 23:15:00 | 1 | 979 ms | 979 ms | 0 | 0 |
| 2026-11-17 23:25:00 | 1 | 899 ms | 899 ms | 0 | 0 |
| 2026-11-17 23:30:00 | 1 | 916 ms | 916 ms | 0 | 0 |
| 2026-11-17 23:40:00 | 1 | 933 ms | 933 ms | 0 | 0 |
| 2026-11-17 23:50:00 | 1 | 828 ms | 828 ms | 0 | 0 |
| 2026-11-17 23:55:00 | 1 | 858 ms | 858 ms | 0 | 0 |
| 2026-11-18 00:05:00 | 1 | 816 ms | 816 ms | 0 | 0 |
| 2026-11-18 00:10:00 | 1 | 995 ms | 995 ms | 0 | 0 |
| 2026-11-18 00:20:00 | 1 | 996 ms | 996 ms | 0 | 0 |
| 2026-11-18 00:30:00 | 1 | 875 ms | 875 ms | 0 | 0 |
| 2026-11-18 00:35:00 | 1 | 1 341 ms | 1 341 ms | 0 | 0 |
| 2026-11-18 00:45:00 | 1 | 796 ms | 796 ms | 0 | 0 |
Success is up or degraded among recorded primary probe checks. This is not a public uptime SLA. Available history can be shorter than the selected range.
Your signal
Tell us. Registration is not required. The same signal will not be counted repeatedly within a short period.
User opinions are separate from the technical outage status.
No ratings yet
No comments yet.
This page tracks the current observed status of Microsoft Teams, recent incidents, automated availability checks and available user reports. NexIP does not treat a single failed check as proof of a global outage.
Ping · Website availability · Website monitoring · All service outages
NexIP shows the current observed status of Microsoft Teams using automated checks, incident data and available user signals. A local connection problem may differ from a large-scale outage.
Availability can differ by provider, region, DNS, routing, application version or service component. NexIP therefore separates observed signals from confirmed large-scale incidents.
Check the host with Ping, website availability and your own connection. Comparing several independent checks helps distinguish a local problem from a wider outage.