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-17 17:35:00 | 1 | 828 ms | 828 ms | 0 | 0 |
| 2026-11-17 17:45:00 | 1 | 1 196 ms | 1 196 ms | 0 | 0 |
| 2026-11-17 17:50:00 | 1 | 768 ms | 768 ms | 0 | 0 |
| 2026-11-17 18:00:00 | 1 | 827 ms | 827 ms | 0 | 0 |
| 2026-11-17 18:10:00 | 1 | 779 ms | 779 ms | 0 | 0 |
| 2026-11-17 18:15:00 | 1 | 1 749 ms | 1 749 ms | 0 | 0 |
| 2026-11-17 18:25:00 | 1 | 784 ms | 784 ms | 0 | 0 |
| 2026-11-17 18:35:00 | 1 | 950 ms | 950 ms | 0 | 0 |
| 2026-11-17 18:40:00 | 1 | 986 ms | 986 ms | 0 | 0 |
| 2026-11-17 18:50:00 | 1 | 856 ms | 856 ms | 0 | 0 |
| 2026-11-17 18:55:00 | 1 | 964 ms | 964 ms | 0 | 0 |
| 2026-11-17 19:05:00 | 1 | 859 ms | 859 ms | 0 | 0 |
| 2026-11-17 19:15:00 | 1 | 938 ms | 938 ms | 0 | 0 |
| 2026-11-17 19:20:00 | 1 | 1 277 ms | 1 277 ms | 0 | 0 |
| 2026-11-17 19:30:00 | 1 | 861 ms | 861 ms | 0 | 0 |
| 2026-11-17 19:40:00 | 1 | 773 ms | 773 ms | 0 | 0 |
| 2026-11-17 19:45:00 | 1 | 927 ms | 927 ms | 0 | 0 |
| 2026-11-17 19:55:00 | 1 | 809 ms | 809 ms | 0 | 0 |
| 2026-11-17 20:05:00 | 1 | 917 ms | 917 ms | 0 | 0 |
| 2026-11-17 20:10:00 | 1 | 700 ms | 700 ms | 0 | 0 |
| 2026-11-17 20:20:00 | 1 | 836 ms | 836 ms | 0 | 0 |
| 2026-11-17 20:25:00 | 1 | 755 ms | 755 ms | 0 | 0 |
| 2026-11-17 20:35:00 | 1 | 855 ms | 855 ms | 0 | 0 |
| 2026-11-17 20:45:00 | 1 | 834 ms | 834 ms | 0 | 0 |
| 2026-11-17 20:50:00 | 1 | 773 ms | 773 ms | 0 | 0 |
| 2026-11-17 21:00:00 | 1 | 865 ms | 865 ms | 0 | 0 |
| 2026-11-17 21:10:00 | 1 | 759 ms | 759 ms | 0 | 0 |
| 2026-11-17 21:15:00 | 1 | 905 ms | 905 ms | 0 | 0 |
| 2026-11-17 21:25:00 | 1 | 871 ms | 871 ms | 0 | 0 |
| 2026-11-17 21:30:00 | 1 | 816 ms | 816 ms | 0 | 0 |
| 2026-11-17 21:40:00 | 1 | 765 ms | 765 ms | 0 | 0 |
| 2026-11-17 21:50:00 | 1 | 755 ms | 755 ms | 0 | 0 |
| 2026-11-17 21:55:00 | 1 | 765 ms | 765 ms | 0 | 0 |
| 2026-11-17 22:05:00 | 1 | 795 ms | 795 ms | 0 | 0 |
| 2026-11-17 22:10:00 | 1 | 1 231 ms | 1 231 ms | 0 | 0 |
| 2026-11-17 22:20:00 | 1 | 712 ms | 712 ms | 0 | 0 |
| 2026-11-17 22:30:00 | 1 | 932 ms | 932 ms | 0 | 0 |
| 2026-11-17 22:35:00 | 1 | 1 063 ms | 1 063 ms | 0 | 0 |
| 2026-11-17 22:45:00 | 1 | 751 ms | 751 ms | 0 | 0 |
| 2026-11-17 22:55:00 | 1 | 855 ms | 855 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.