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.
Media
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
Мониторинг доступности сервиса PREMIER, пользовательских сигналов и технических проверок 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 00:00:00 | 23 | 519 ms | 984 ms | 0 | 0 |
| 2026-11-13 03:00:00 | 22 | 473 ms | 957 ms | 0 | 0 |
| 2026-11-13 06:00:00 | 23 | 494 ms | 1 090 ms | 0 | 0 |
| 2026-11-13 09:00:00 | 22 | 520 ms | 1 888 ms | 0 | 0 |
| 2026-11-13 12:00:00 | 23 | 574 ms | 1 325 ms | 0 | 0 |
| 2026-11-13 15:00:00 | 22 | 531 ms | 946 ms | 0 | 0 |
| 2026-11-13 18:00:00 | 23 | 606 ms | 1 651 ms | 0 | 0 |
| 2026-11-13 21:00:00 | 22 | 546 ms | 1 577 ms | 0 | 0 |
| 2026-11-14 00:00:00 | 23 | 506 ms | 1 010 ms | 0 | 0 |
| 2026-11-14 03:00:00 | 22 | 589 ms | 1 043 ms | 0 | 0 |
| 2026-11-14 06:00:00 | 23 | 629 ms | 1 712 ms | 0 | 0 |
| 2026-11-14 09:00:00 | 22 | 594 ms | 1 138 ms | 0 | 0 |
| 2026-11-14 12:00:00 | 23 | 619 ms | 1 025 ms | 0 | 0 |
| 2026-11-14 15:00:00 | 22 | 575 ms | 943 ms | 0 | 0 |
| 2026-11-14 18:00:00 | 23 | 842 ms | 5 729 ms | 0 | 0 |
| 2026-11-14 21:00:00 | 22 | 533 ms | 1 977 ms | 0 | 0 |
| 2026-11-15 00:00:00 | 23 | 460 ms | 975 ms | 0 | 0 |
| 2026-11-15 03:00:00 | 22 | 528 ms | 931 ms | 0 | 0 |
| 2026-11-15 06:00:00 | 22 | 543 ms | 932 ms | 0 | 0 |
| 2026-11-15 09:00:00 | 23 | 497 ms | 1 004 ms | 0 | 0 |
| 2026-11-15 12:00:00 | 22 | 617 ms | 1 141 ms | 0 | 0 |
| 2026-11-15 15:00:00 | 23 | 756 ms | 1 056 ms | 0 | 0 |
| 2026-11-15 18:00:00 | 22 | 592 ms | 990 ms | 0 | 0 |
| 2026-11-15 21:00:00 | 23 | 603 ms | 1 074 ms | 0 | 0 |
| 2026-11-16 00:00:00 | 22 | 484 ms | 1 032 ms | 0 | 0 |
| 2026-11-16 03:00:00 | 23 | 599 ms | 1 966 ms | 0 | 0 |
| 2026-11-16 06:00:00 | 22 | 619 ms | 979 ms | 0 | 0 |
| 2026-11-16 09:00:00 | 23 | 607 ms | 992 ms | 0 | 0 |
| 2026-11-16 12:00:00 | 23 | 453 ms | 866 ms | 0 | 0 |
| 2026-11-16 15:00:00 | 22 | 495 ms | 936 ms | 0 | 0 |
| 2026-11-16 18:00:00 | 23 | 587 ms | 1 603 ms | 0 | 0 |
| 2026-11-16 21:00:00 | 23 | 575 ms | 1 074 ms | 0 | 0 |
| 2026-11-17 00:00:00 | 22 | 701 ms | 2 771 ms | 0 | 0 |
| 2026-11-17 03:00:00 | 23 | 604 ms | 1 580 ms | 0 | 0 |
| 2026-11-17 06:00:00 | 23 | 545 ms | 901 ms | 0 | 0 |
| 2026-11-17 09:00:00 | 23 | 538 ms | 1 005 ms | 0 | 0 |
| 2026-11-17 12:00:00 | 23 | 518 ms | 930 ms | 0 | 0 |
| 2026-11-17 15:00:00 | 22 | 495 ms | 1 626 ms | 0 | 0 |
| 2026-11-17 18:00:00 | 22 | 619 ms | 1 513 ms | 0 | 0 |
| 2026-11-17 21:00:00 | 15 | 682 ms | 1 837 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 PREMIER, 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 PREMIER 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.