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-15 03:00:00 | 23 | 403 ms | 518 ms | 0 | 0 |
| 2026-11-15 06:00:00 | 22 | 408 ms | 558 ms | 0 | 0 |
| 2026-11-15 09:00:00 | 23 | 422 ms | 556 ms | 0 | 0 |
| 2026-11-15 12:00:00 | 22 | 432 ms | 594 ms | 0 | 0 |
| 2026-11-15 15:00:00 | 23 | 393 ms | 534 ms | 0 | 0 |
| 2026-11-15 18:00:00 | 22 | 456 ms | 584 ms | 0 | 0 |
| 2026-11-15 21:00:00 | 23 | 394 ms | 549 ms | 0 | 0 |
| 2026-11-16 00:00:00 | 22 | 416 ms | 553 ms | 0 | 0 |
| 2026-11-16 03:00:00 | 23 | 385 ms | 542 ms | 0 | 0 |
| 2026-11-16 06:00:00 | 22 | 408 ms | 524 ms | 0 | 0 |
| 2026-11-16 09:00:00 | 23 | 409 ms | 548 ms | 0 | 0 |
| 2026-11-16 12:00:00 | 22 | 425 ms | 570 ms | 0 | 0 |
| 2026-11-16 15:00:00 | 23 | 419 ms | 605 ms | 0 | 0 |
| 2026-11-16 18:00:00 | 22 | 434 ms | 569 ms | 0 | 0 |
| 2026-11-16 21:00:00 | 23 | 412 ms | 573 ms | 0 | 0 |
| 2026-11-17 00:00:00 | 23 | 400 ms | 601 ms | 0 | 0 |
| 2026-11-17 03:00:00 | 22 | 399 ms | 638 ms | 0 | 0 |
| 2026-11-17 06:00:00 | 24 | 414 ms | 553 ms | 0 | 0 |
| 2026-11-17 09:00:00 | 23 | 428 ms | 553 ms | 0 | 0 |
| 2026-11-17 12:00:00 | 23 | 424 ms | 576 ms | 0 | 0 |
| 2026-11-17 15:00:00 | 22 | 402 ms | 592 ms | 0 | 0 |
| 2026-11-17 18:00:00 | 22 | 461 ms | 820 ms | 0 | 0 |
| 2026-11-17 21:00:00 | 23 | 448 ms | 595 ms | 0 | 0 |
| 2026-11-18 00:00:00 | 22 | 390 ms | 527 ms | 0 | 0 |
| 2026-11-18 03:00:00 | 23 | 404 ms | 544 ms | 0 | 0 |
| 2026-11-18 06:00:00 | 23 | 411 ms | 576 ms | 0 | 0 |
| 2026-11-18 09:00:00 | 23 | 413 ms | 602 ms | 0 | 0 |
| 2026-11-18 12:00:00 | 22 | 419 ms | 568 ms | 0 | 0 |
| 2026-11-18 15:00:00 | 23 | 403 ms | 581 ms | 0 | 0 |
| 2026-11-18 18:00:00 | 22 | 417 ms | 723 ms | 0 | 0 |
| 2026-11-18 21:00:00 | 23 | 415 ms | 584 ms | 0 | 0 |
| 2026-11-19 00:00:00 | 22 | 412 ms | 542 ms | 0 | 0 |
| 2026-11-19 03:00:00 | 23 | 395 ms | 554 ms | 0 | 0 |
| 2026-11-19 06:00:00 | 23 | 389 ms | 591 ms | 0 | 0 |
| 2026-11-19 09:00:00 | 22 | 434 ms | 628 ms | 0 | 0 |
| 2026-11-19 12:00:00 | 21 | 403 ms | 824 ms | 0 | 0 |
| 2026-11-19 15:00:00 | 23 | 416 ms | 600 ms | 0 | 0 |
| 2026-11-19 18:00:00 | 22 | 403 ms | 580 ms | 0 | 0 |
| 2026-11-19 21:00:00 | 23 | 413 ms | 593 ms | 0 | 0 |
| 2026-11-20 00:00:00 | 6 | 391 ms | 524 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.