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 05:00:00 | 4 | 899 ms | 980 ms | 0 | 0 |
| 2026-11-17 05:30:00 | 4 | 923 ms | 1 028 ms | 0 | 0 |
| 2026-11-17 06:00:00 | 3 | 983 ms | 1 118 ms | 0 | 0 |
| 2026-11-17 06:30:00 | 4 | 842 ms | 919 ms | 0 | 0 |
| 2026-11-17 07:00:00 | 4 | 923 ms | 939 ms | 0 | 0 |
| 2026-11-17 07:30:00 | 4 | 1 017 ms | 1 296 ms | 0 | 0 |
| 2026-11-17 08:00:00 | 4 | 863 ms | 924 ms | 0 | 0 |
| 2026-11-17 08:30:00 | 4 | 828 ms | 896 ms | 0 | 0 |
| 2026-11-17 09:00:00 | 4 | 808 ms | 868 ms | 0 | 0 |
| 2026-11-17 09:30:00 | 4 | 864 ms | 915 ms | 0 | 0 |
| 2026-11-17 10:00:00 | 4 | 840 ms | 995 ms | 0 | 0 |
| 2026-11-17 10:30:00 | 4 | 935 ms | 1 071 ms | 0 | 0 |
| 2026-11-17 11:00:00 | 3 | 917 ms | 1 039 ms | 0 | 0 |
| 2026-11-17 11:30:00 | 4 | 868 ms | 894 ms | 0 | 0 |
| 2026-11-17 12:00:00 | 4 | 1 229 ms | 1 929 ms | 0 | 0 |
| 2026-11-17 12:30:00 | 4 | 853 ms | 912 ms | 0 | 0 |
| 2026-11-17 13:00:00 | 4 | 895 ms | 965 ms | 0 | 0 |
| 2026-11-17 13:30:00 | 3 | 884 ms | 974 ms | 0 | 0 |
| 2026-11-17 14:00:00 | 4 | 902 ms | 1 091 ms | 0 | 0 |
| 2026-11-17 14:30:00 | 4 | 823 ms | 850 ms | 0 | 0 |
| 2026-11-17 15:00:00 | 4 | 850 ms | 967 ms | 0 | 0 |
| 2026-11-17 15:30:00 | 3 | 878 ms | 977 ms | 0 | 0 |
| 2026-11-17 16:00:00 | 4 | 1 044 ms | 1 166 ms | 0 | 0 |
| 2026-11-17 16:30:00 | 4 | 933 ms | 1 016 ms | 0 | 0 |
| 2026-11-17 17:00:00 | 4 | 1 911 ms | 4 825 ms | 0 | 0 |
| 2026-11-17 17:30:00 | 3 | 923 ms | 1 007 ms | 0 | 0 |
| 2026-11-17 18:00:00 | 4 | 898 ms | 960 ms | 0 | 0 |
| 2026-11-17 18:30:00 | 4 | 1 061 ms | 1 243 ms | 0 | 0 |
| 2026-11-17 19:00:00 | 3 | 967 ms | 1 021 ms | 0 | 0 |
| 2026-11-17 19:30:00 | 4 | 897 ms | 969 ms | 0 | 0 |
| 2026-11-17 20:00:00 | 4 | 993 ms | 1 044 ms | 0 | 0 |
| 2026-11-17 20:30:00 | 3 | 1 885 ms | 2 726 ms | 0 | 0 |
| 2026-11-17 21:00:00 | 4 | 988 ms | 1 050 ms | 0 | 0 |
| 2026-11-17 21:30:00 | 4 | 839 ms | 887 ms | 0 | 0 |
| 2026-11-17 22:00:00 | 3 | 1 023 ms | 1 245 ms | 0 | 0 |
| 2026-11-17 22:30:00 | 4 | 959 ms | 972 ms | 0 | 0 |
| 2026-11-17 23:00:00 | 4 | 938 ms | 1 030 ms | 0 | 0 |
| 2026-11-17 23:30:00 | 4 | 884 ms | 933 ms | 0 | 0 |
| 2026-11-18 00:00:00 | 3 | 936 ms | 996 ms | 0 | 0 |
| 2026-11-18 00:30:00 | 3 | 1 004 ms | 1 341 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.