How to interpret the monitoring status
Technical measurements reflect observations from the NexIP monitoring location. A failed or restricted request alone does not confirm a widespread outage.
Техническая проверка выявила ошибку или задержку. Массовый сбой не подтверждён.
Technical measurements reflect observations from the NexIP monitoring location. A failed or restricted request alone does not confirm a widespread outage.
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
Мониторинг доступности сервиса Outlook, пользовательских сигналов и технических проверок 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 17:25:00 | 1 | 555 ms | 555 ms | 0 | 0 |
| 2026-11-17 17:35:00 | 1 | 589 ms | 589 ms | 0 | 0 |
| 2026-11-17 17:45:00 | 1 | 644 ms | 644 ms | 0 | 0 |
| 2026-11-17 17:50:00 | 1 | 591 ms | 591 ms | 0 | 0 |
| 2026-11-17 18:00:00 | 1 | 623 ms | 623 ms | 0 | 0 |
| 2026-11-17 18:05:00 | 1 | 600 ms | 600 ms | 0 | 0 |
| 2026-11-17 18:15:00 | 1 | 569 ms | 569 ms | 0 | 0 |
| 2026-11-17 18:25:00 | 1 | 681 ms | 681 ms | 0 | 0 |
| 2026-11-17 18:30:00 | 1 | 956 ms | 956 ms | 0 | 0 |
| 2026-11-17 18:40:00 | 1 | 692 ms | 692 ms | 0 | 0 |
| 2026-11-17 18:50:00 | 1 | 737 ms | 737 ms | 0 | 0 |
| 2026-11-17 18:55:00 | 1 | 549 ms | 549 ms | 0 | 0 |
| 2026-11-17 19:05:00 | 1 | 636 ms | 636 ms | 0 | 0 |
| 2026-11-17 19:15:00 | 1 | 717 ms | 717 ms | 0 | 0 |
| 2026-11-17 19:20:00 | 1 | 758 ms | 758 ms | 0 | 0 |
| 2026-11-17 19:30:00 | 1 | 527 ms | 527 ms | 0 | 0 |
| 2026-11-17 19:40:00 | 1 | 581 ms | 581 ms | 0 | 0 |
| 2026-11-17 19:45:00 | 1 | 1 111 ms | 1 111 ms | 0 | 0 |
| 2026-11-17 19:55:00 | 1 | 720 ms | 720 ms | 0 | 0 |
| 2026-11-17 20:05:00 | 1 | 681 ms | 681 ms | 0 | 0 |
| 2026-11-17 20:10:00 | 1 | 718 ms | 718 ms | 0 | 0 |
| 2026-11-17 20:20:00 | 1 | 678 ms | 678 ms | 0 | 0 |
| 2026-11-17 20:25:00 | 1 | 1 434 ms | 1 434 ms | 0 | 0 |
| 2026-11-17 20:35:00 | 1 | 728 ms | 728 ms | 0 | 0 |
| 2026-11-17 20:45:00 | 1 | 1 081 ms | 1 081 ms | 0 | 0 |
| 2026-11-17 20:50:00 | 1 | 747 ms | 747 ms | 0 | 0 |
| 2026-11-17 21:00:00 | 1 | 675 ms | 675 ms | 0 | 0 |
| 2026-11-17 21:05:00 | 1 | 707 ms | 707 ms | 0 | 0 |
| 2026-11-17 21:15:00 | 1 | 706 ms | 706 ms | 0 | 0 |
| 2026-11-17 21:25:00 | 1 | 545 ms | 545 ms | 0 | 0 |
| 2026-11-17 21:30:00 | 1 | 569 ms | 569 ms | 0 | 0 |
| 2026-11-17 21:40:00 | 1 | 1 161 ms | 1 161 ms | 0 | 0 |
| 2026-11-17 21:50:00 | 1 | 755 ms | 755 ms | 0 | 0 |
| 2026-11-17 21:55:00 | 1 | 553 ms | 553 ms | 0 | 0 |
| 2026-11-17 22:05:00 | 1 | 522 ms | 522 ms | 0 | 0 |
| 2026-11-17 22:10:00 | 1 | 2 314 ms | 2 314 ms | 0 | 0 |
| 2026-11-17 22:20:00 | 1 | 579 ms | 579 ms | 0 | 0 |
| 2026-11-17 22:30:00 | 1 | 580 ms | 580 ms | 0 | 0 |
| 2026-11-17 22:35:00 | 1 | 555 ms | 555 ms | 0 | 0 |
| 2026-11-17 22:45:00 | 1 | 1 087 ms | 1 087 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 Outlook, 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 Outlook 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.