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-13 00:00:00 | 23 | 845 ms | 1 025 ms | 0 | 0 |
| 2026-11-13 03:00:00 | 22 | 848 ms | 999 ms | 0 | 0 |
| 2026-11-13 06:00:00 | 23 | 864 ms | 1 026 ms | 0 | 0 |
| 2026-11-13 09:00:00 | 22 | 850 ms | 1 136 ms | 0 | 0 |
| 2026-11-13 12:00:00 | 23 | 830 ms | 1 086 ms | 0 | 0 |
| 2026-11-13 15:00:00 | 22 | 859 ms | 1 116 ms | 0 | 0 |
| 2026-11-13 18:00:00 | 23 | 833 ms | 1 041 ms | 0 | 0 |
| 2026-11-13 21:00:00 | 22 | 901 ms | 1 270 ms | 0 | 0 |
| 2026-11-14 00:00:00 | 23 | 833 ms | 965 ms | 0 | 0 |
| 2026-11-14 03:00:00 | 22 | 858 ms | 1 066 ms | 0 | 0 |
| 2026-11-14 06:00:00 | 23 | 842 ms | 1 060 ms | 0 | 0 |
| 2026-11-14 09:00:00 | 22 | 819 ms | 1 078 ms | 0 | 0 |
| 2026-11-14 12:00:00 | 23 | 822 ms | 973 ms | 0 | 0 |
| 2026-11-14 15:00:00 | 22 | 863 ms | 1 076 ms | 0 | 0 |
| 2026-11-14 18:00:00 | 23 | 848 ms | 1 113 ms | 0 | 0 |
| 2026-11-14 21:00:00 | 22 | 860 ms | 1 135 ms | 0 | 0 |
| 2026-11-15 00:00:00 | 23 | 802 ms | 1 046 ms | 1 | 0 |
| 2026-11-15 03:00:00 | 22 | 824 ms | 1 022 ms | 0 | 0 |
| 2026-11-15 06:00:00 | 22 | 827 ms | 987 ms | 0 | 0 |
| 2026-11-15 09:00:00 | 23 | 861 ms | 1 186 ms | 0 | 0 |
| 2026-11-15 12:00:00 | 22 | 844 ms | 1 288 ms | 0 | 0 |
| 2026-11-15 15:00:00 | 23 | 878 ms | 1 182 ms | 0 | 0 |
| 2026-11-15 18:00:00 | 22 | 881 ms | 1 174 ms | 0 | 0 |
| 2026-11-15 21:00:00 | 23 | 823 ms | 968 ms | 0 | 0 |
| 2026-11-16 00:00:00 | 22 | 822 ms | 1 060 ms | 0 | 0 |
| 2026-11-16 03:00:00 | 23 | 826 ms | 1 042 ms | 0 | 0 |
| 2026-11-16 06:00:00 | 22 | 839 ms | 1 087 ms | 0 | 0 |
| 2026-11-16 09:00:00 | 23 | 832 ms | 979 ms | 0 | 0 |
| 2026-11-16 12:00:00 | 22 | 955 ms | 3 135 ms | 0 | 0 |
| 2026-11-16 15:00:00 | 23 | 870 ms | 1 083 ms | 0 | 0 |
| 2026-11-16 18:00:00 | 23 | 843 ms | 1 038 ms | 0 | 0 |
| 2026-11-16 21:00:00 | 22 | 833 ms | 1 054 ms | 0 | 0 |
| 2026-11-17 00:00:00 | 23 | 828 ms | 1 034 ms | 0 | 0 |
| 2026-11-17 03:00:00 | 23 | 869 ms | 1 039 ms | 0 | 0 |
| 2026-11-17 06:00:00 | 23 | 855 ms | 1 061 ms | 0 | 0 |
| 2026-11-17 09:00:00 | 23 | 853 ms | 1 277 ms | 0 | 0 |
| 2026-11-17 12:00:00 | 23 | 916 ms | 2 303 ms | 0 | 0 |
| 2026-11-17 15:00:00 | 22 | 860 ms | 1 196 ms | 0 | 0 |
| 2026-11-17 18:00:00 | 22 | 910 ms | 1 749 ms | 0 | 0 |
| 2026-11-17 21:00:00 | 15 | 856 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.