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.
Telecom operators
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
Мониторинг доступности сервиса Yota, пользовательских сигналов и технических проверок 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-16 07:00:00 | 8 | 789 ms | 893 ms | 0 | 0 |
| 2026-11-16 08:00:00 | 7 | 866 ms | 993 ms | 0 | 0 |
| 2026-11-16 09:00:00 | 8 | 815 ms | 902 ms | 0 | 0 |
| 2026-11-16 10:00:00 | 7 | 843 ms | 943 ms | 0 | 0 |
| 2026-11-16 11:00:00 | 8 | 838 ms | 979 ms | 0 | 0 |
| 2026-11-16 12:00:00 | 7 | 849 ms | 975 ms | 0 | 0 |
| 2026-11-16 13:00:00 | 8 | 877 ms | 1 110 ms | 0 | 0 |
| 2026-11-16 14:00:00 | 7 | 1 151 ms | 3 135 ms | 0 | 0 |
| 2026-11-16 15:00:00 | 8 | 870 ms | 1 083 ms | 0 | 0 |
| 2026-11-16 16:00:00 | 7 | 893 ms | 1 037 ms | 0 | 0 |
| 2026-11-16 17:00:00 | 8 | 848 ms | 1 076 ms | 0 | 0 |
| 2026-11-16 18:00:00 | 8 | 810 ms | 911 ms | 0 | 0 |
| 2026-11-16 19:00:00 | 7 | 882 ms | 992 ms | 0 | 0 |
| 2026-11-16 20:00:00 | 8 | 843 ms | 1 038 ms | 0 | 0 |
| 2026-11-16 21:00:00 | 7 | 836 ms | 925 ms | 0 | 0 |
| 2026-11-16 22:00:00 | 8 | 858 ms | 1 054 ms | 0 | 0 |
| 2026-11-16 23:00:00 | 7 | 803 ms | 876 ms | 0 | 0 |
| 2026-11-17 00:00:00 | 8 | 818 ms | 866 ms | 0 | 0 |
| 2026-11-17 01:00:00 | 8 | 828 ms | 903 ms | 0 | 0 |
| 2026-11-17 02:00:00 | 7 | 839 ms | 1 034 ms | 0 | 0 |
| 2026-11-17 03:00:00 | 8 | 877 ms | 1 026 ms | 0 | 0 |
| 2026-11-17 04:00:00 | 7 | 884 ms | 974 ms | 0 | 0 |
| 2026-11-17 05:00:00 | 8 | 849 ms | 1 039 ms | 0 | 0 |
| 2026-11-17 06:00:00 | 7 | 868 ms | 1 033 ms | 0 | 0 |
| 2026-11-17 07:00:00 | 8 | 837 ms | 1 007 ms | 0 | 0 |
| 2026-11-17 08:00:00 | 8 | 860 ms | 1 061 ms | 0 | 0 |
| 2026-11-17 09:00:00 | 8 | 818 ms | 883 ms | 0 | 0 |
| 2026-11-17 10:00:00 | 7 | 912 ms | 1 277 ms | 0 | 0 |
| 2026-11-17 11:00:00 | 8 | 836 ms | 938 ms | 0 | 0 |
| 2026-11-17 12:00:00 | 8 | 816 ms | 930 ms | 0 | 0 |
| 2026-11-17 13:00:00 | 7 | 1 003 ms | 2 303 ms | 0 | 0 |
| 2026-11-17 14:00:00 | 8 | 941 ms | 1 186 ms | 0 | 0 |
| 2026-11-17 15:00:00 | 7 | 841 ms | 951 ms | 0 | 0 |
| 2026-11-17 16:00:00 | 8 | 848 ms | 1 061 ms | 0 | 0 |
| 2026-11-17 17:00:00 | 7 | 891 ms | 1 196 ms | 0 | 0 |
| 2026-11-17 18:00:00 | 8 | 987 ms | 1 749 ms | 0 | 0 |
| 2026-11-17 19:00:00 | 7 | 921 ms | 1 277 ms | 0 | 0 |
| 2026-11-17 20:00:00 | 7 | 810 ms | 917 ms | 0 | 0 |
| 2026-11-17 21:00:00 | 8 | 813 ms | 905 ms | 0 | 0 |
| 2026-11-17 22:00:00 | 7 | 906 ms | 1 231 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 Yota, 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 Yota 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.