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.
Transport and travel
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
Мониторинг доступности сервиса Яндекс Go, пользовательских сигналов и технических проверок 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-19 19:30:00 | 1 | 567 ms | 567 ms | 0 | 0 |
| 2026-11-19 19:40:00 | 1 | 397 ms | 397 ms | 0 | 0 |
| 2026-11-19 19:45:00 | 1 | 283 ms | 283 ms | 0 | 0 |
| 2026-11-19 19:55:00 | 1 | 538 ms | 538 ms | 0 | 0 |
| 2026-11-19 20:00:00 | 1 | 362 ms | 362 ms | 0 | 0 |
| 2026-11-19 20:10:00 | 1 | 383 ms | 383 ms | 0 | 0 |
| 2026-11-19 20:20:00 | 1 | 379 ms | 379 ms | 0 | 0 |
| 2026-11-19 20:25:00 | 1 | 437 ms | 437 ms | 0 | 0 |
| 2026-11-19 20:35:00 | 1 | 263 ms | 263 ms | 0 | 0 |
| 2026-11-19 20:40:00 | 1 | 541 ms | 541 ms | 0 | 0 |
| 2026-11-19 20:50:00 | 1 | 378 ms | 378 ms | 0 | 0 |
| 2026-11-19 21:00:00 | 1 | 434 ms | 434 ms | 0 | 0 |
| 2026-11-19 21:05:00 | 1 | 545 ms | 545 ms | 0 | 0 |
| 2026-11-19 21:15:00 | 1 | 394 ms | 394 ms | 0 | 0 |
| 2026-11-19 21:20:00 | 1 | 266 ms | 266 ms | 0 | 0 |
| 2026-11-19 21:30:00 | 1 | 400 ms | 400 ms | 0 | 0 |
| 2026-11-19 21:35:00 | 1 | 511 ms | 511 ms | 0 | 0 |
| 2026-11-19 21:45:00 | 1 | 531 ms | 531 ms | 0 | 0 |
| 2026-11-19 21:55:00 | 1 | 321 ms | 321 ms | 0 | 0 |
| 2026-11-19 22:00:00 | 1 | 593 ms | 593 ms | 0 | 0 |
| 2026-11-19 22:10:00 | 1 | 388 ms | 388 ms | 0 | 0 |
| 2026-11-19 22:20:00 | 1 | 535 ms | 535 ms | 0 | 0 |
| 2026-11-19 22:25:00 | 1 | 392 ms | 392 ms | 0 | 0 |
| 2026-11-19 22:35:00 | 1 | 463 ms | 463 ms | 0 | 0 |
| 2026-11-19 22:40:00 | 1 | 555 ms | 555 ms | 0 | 0 |
| 2026-11-19 22:50:00 | 1 | 333 ms | 333 ms | 0 | 0 |
| 2026-11-19 23:00:00 | 1 | 302 ms | 302 ms | 0 | 0 |
| 2026-11-19 23:05:00 | 1 | 359 ms | 359 ms | 0 | 0 |
| 2026-11-19 23:15:00 | 1 | 398 ms | 398 ms | 0 | 0 |
| 2026-11-19 23:20:00 | 1 | 277 ms | 277 ms | 0 | 0 |
| 2026-11-19 23:30:00 | 1 | 378 ms | 378 ms | 0 | 0 |
| 2026-11-19 23:35:00 | 1 | 535 ms | 535 ms | 0 | 0 |
| 2026-11-19 23:45:00 | 1 | 333 ms | 333 ms | 0 | 0 |
| 2026-11-19 23:55:00 | 1 | 266 ms | 266 ms | 0 | 0 |
| 2026-11-20 00:00:00 | 1 | 347 ms | 347 ms | 0 | 0 |
| 2026-11-20 00:10:00 | 1 | 377 ms | 377 ms | 0 | 0 |
| 2026-11-20 00:15:00 | 1 | 524 ms | 524 ms | 0 | 0 |
| 2026-11-20 00:25:00 | 1 | 352 ms | 352 ms | 0 | 0 |
| 2026-11-20 00:35:00 | 1 | 404 ms | 404 ms | 0 | 0 |
| 2026-11-20 00:40:00 | 1 | 340 ms | 340 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 Яндекс Go, 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 Яндекс Go 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.