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.
Social networks
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
Мониторинг доступности сервиса X, пользовательских сигналов и технических проверок 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-13 21:00:00 | 22 | 596 ms | 5 005 ms | 0 | 0 |
| 2026-11-14 00:00:00 | 23 | 628 ms | 5 005 ms | 0 | 0 |
| 2026-11-14 03:00:00 | 22 | 570 ms | 5 005 ms | 0 | 0 |
| 2026-11-14 06:00:00 | 23 | 588 ms | 5 005 ms | 0 | 0 |
| 2026-11-14 09:00:00 | 22 | 641 ms | 5 005 ms | 0 | 0 |
| 2026-11-14 12:00:00 | 23 | 399 ms | 787 ms | 0 | 0 |
| 2026-11-14 15:00:00 | 22 | 630 ms | 5 006 ms | 0 | 0 |
| 2026-11-14 18:00:00 | 23 | 638 ms | 5 005 ms | 0 | 0 |
| 2026-11-14 21:00:00 | 22 | 802 ms | 5 006 ms | 0 | 0 |
| 2026-11-15 00:00:00 | 23 | 1 171 ms | 5 007 ms | 0 | 0 |
| 2026-11-15 03:00:00 | 22 | 367 ms | 709 ms | 0 | 0 |
| 2026-11-15 06:00:00 | 22 | 827 ms | 5 007 ms | 0 | 0 |
| 2026-11-15 09:00:00 | 23 | 814 ms | 5 005 ms | 0 | 0 |
| 2026-11-15 12:00:00 | 22 | 857 ms | 5 008 ms | 0 | 0 |
| 2026-11-15 15:00:00 | 23 | 384 ms | 1 264 ms | 0 | 0 |
| 2026-11-15 18:00:00 | 22 | 835 ms | 5 005 ms | 0 | 0 |
| 2026-11-15 21:00:00 | 23 | 798 ms | 5 005 ms | 0 | 0 |
| 2026-11-16 00:00:00 | 22 | 1 416 ms | 5 006 ms | 0 | 0 |
| 2026-11-16 03:00:00 | 23 | 383 ms | 638 ms | 0 | 0 |
| 2026-11-16 06:00:00 | 22 | 371 ms | 531 ms | 0 | 0 |
| 2026-11-16 09:00:00 | 23 | 393 ms | 664 ms | 0 | 0 |
| 2026-11-16 12:00:00 | 22 | 475 ms | 1 253 ms | 0 | 0 |
| 2026-11-16 15:00:00 | 23 | 718 ms | 8 004 ms | 0 | 0 |
| 2026-11-16 18:00:00 | 23 | 432 ms | 1 726 ms | 0 | 0 |
| 2026-11-16 21:00:00 | 22 | 718 ms | 8 004 ms | 0 | 0 |
| 2026-11-17 00:00:00 | 23 | 584 ms | 5 005 ms | 0 | 0 |
| 2026-11-17 03:00:00 | 23 | 396 ms | 726 ms | 0 | 0 |
| 2026-11-17 06:00:00 | 23 | 702 ms | 8 004 ms | 0 | 0 |
| 2026-11-17 09:00:00 | 23 | 406 ms | 1 561 ms | 0 | 0 |
| 2026-11-17 12:00:00 | 23 | 968 ms | 8 005 ms | 0 | 0 |
| 2026-11-17 15:00:00 | 22 | 373 ms | 689 ms | 0 | 0 |
| 2026-11-17 18:00:00 | 22 | 747 ms | 8 005 ms | 0 | 0 |
| 2026-11-17 21:00:00 | 23 | 1 422 ms | 8 004 ms | 0 | 0 |
| 2026-11-18 00:00:00 | 22 | 370 ms | 579 ms | 0 | 0 |
| 2026-11-18 03:00:00 | 23 | 704 ms | 8 004 ms | 0 | 0 |
| 2026-11-18 06:00:00 | 23 | 381 ms | 640 ms | 0 | 0 |
| 2026-11-18 09:00:00 | 23 | 710 ms | 8 005 ms | 0 | 0 |
| 2026-11-18 12:00:00 | 22 | 372 ms | 807 ms | 0 | 0 |
| 2026-11-18 15:00:00 | 23 | 712 ms | 8 004 ms | 0 | 0 |
| 2026-11-18 18:00:00 | 14 | 385 ms | 759 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 X, 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 X 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.