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 03:00:00 | 4 | 550 ms | 565 ms | 0 | 0 |
| 2026-11-17 03:30:00 | 4 | 539 ms | 559 ms | 0 | 0 |
| 2026-11-17 04:00:00 | 3 | 538 ms | 547 ms | 0 | 0 |
| 2026-11-17 04:30:00 | 4 | 537 ms | 567 ms | 0 | 0 |
| 2026-11-17 05:00:00 | 4 | 567 ms | 579 ms | 0 | 0 |
| 2026-11-17 05:30:00 | 4 | 556 ms | 579 ms | 0 | 0 |
| 2026-11-17 06:00:00 | 3 | 563 ms | 590 ms | 0 | 0 |
| 2026-11-17 06:30:00 | 4 | 554 ms | 583 ms | 0 | 0 |
| 2026-11-17 07:00:00 | 4 | 554 ms | 593 ms | 0 | 0 |
| 2026-11-17 07:30:00 | 4 | 561 ms | 579 ms | 0 | 0 |
| 2026-11-17 08:00:00 | 4 | 654 ms | 902 ms | 0 | 0 |
| 2026-11-17 08:30:00 | 4 | 558 ms | 565 ms | 0 | 0 |
| 2026-11-17 09:00:00 | 4 | 595 ms | 646 ms | 0 | 0 |
| 2026-11-17 09:30:00 | 4 | 584 ms | 600 ms | 0 | 0 |
| 2026-11-17 10:00:00 | 4 | 575 ms | 600 ms | 0 | 0 |
| 2026-11-17 10:30:00 | 3 | 563 ms | 582 ms | 0 | 0 |
| 2026-11-17 11:00:00 | 4 | 559 ms | 608 ms | 0 | 0 |
| 2026-11-17 11:30:00 | 4 | 566 ms | 574 ms | 0 | 0 |
| 2026-11-17 12:00:00 | 4 | 561 ms | 578 ms | 0 | 0 |
| 2026-11-17 12:30:00 | 4 | 567 ms | 576 ms | 0 | 0 |
| 2026-11-17 13:00:00 | 4 | 565 ms | 605 ms | 0 | 0 |
| 2026-11-17 13:30:00 | 3 | 596 ms | 613 ms | 0 | 0 |
| 2026-11-17 14:00:00 | 4 | 581 ms | 615 ms | 0 | 0 |
| 2026-11-17 14:30:00 | 4 | 575 ms | 624 ms | 0 | 0 |
| 2026-11-17 15:00:00 | 4 | 600 ms | 666 ms | 0 | 0 |
| 2026-11-17 15:30:00 | 3 | 677 ms | 880 ms | 0 | 0 |
| 2026-11-17 16:00:00 | 4 | 559 ms | 598 ms | 0 | 0 |
| 2026-11-17 16:30:00 | 4 | 551 ms | 561 ms | 0 | 0 |
| 2026-11-17 17:00:00 | 4 | 643 ms | 738 ms | 0 | 0 |
| 2026-11-17 17:30:00 | 3 | 608 ms | 644 ms | 0 | 0 |
| 2026-11-17 18:00:00 | 4 | 618 ms | 681 ms | 0 | 0 |
| 2026-11-17 18:30:00 | 4 | 734 ms | 956 ms | 0 | 0 |
| 2026-11-17 19:00:00 | 3 | 704 ms | 758 ms | 0 | 0 |
| 2026-11-17 19:30:00 | 4 | 735 ms | 1 111 ms | 0 | 0 |
| 2026-11-17 20:00:00 | 4 | 878 ms | 1 434 ms | 0 | 0 |
| 2026-11-17 20:30:00 | 3 | 852 ms | 1 081 ms | 0 | 0 |
| 2026-11-17 21:00:00 | 4 | 658 ms | 707 ms | 0 | 0 |
| 2026-11-17 21:30:00 | 4 | 760 ms | 1 161 ms | 0 | 0 |
| 2026-11-17 22:00:00 | 3 | 1 138 ms | 2 314 ms | 0 | 0 |
| 2026-11-17 22:30:00 | 4 | 706 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.