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-18 09:00:00 | 8 | 432 ms | 529 ms | 0 | 0 |
| 2026-11-18 10:00:00 | 7 | 443 ms | 602 ms | 0 | 0 |
| 2026-11-18 11:00:00 | 8 | 368 ms | 452 ms | 0 | 0 |
| 2026-11-18 12:00:00 | 7 | 444 ms | 520 ms | 0 | 0 |
| 2026-11-18 13:00:00 | 8 | 418 ms | 568 ms | 0 | 0 |
| 2026-11-18 14:00:00 | 7 | 394 ms | 556 ms | 0 | 0 |
| 2026-11-18 15:00:00 | 8 | 409 ms | 532 ms | 0 | 0 |
| 2026-11-18 16:00:00 | 7 | 415 ms | 562 ms | 0 | 0 |
| 2026-11-18 17:00:00 | 8 | 386 ms | 581 ms | 0 | 0 |
| 2026-11-18 18:00:00 | 7 | 398 ms | 475 ms | 0 | 0 |
| 2026-11-18 19:00:00 | 8 | 474 ms | 723 ms | 0 | 0 |
| 2026-11-18 20:00:00 | 7 | 372 ms | 540 ms | 0 | 0 |
| 2026-11-18 21:00:00 | 8 | 438 ms | 584 ms | 0 | 0 |
| 2026-11-18 22:00:00 | 7 | 351 ms | 419 ms | 0 | 0 |
| 2026-11-18 23:00:00 | 8 | 449 ms | 561 ms | 0 | 0 |
| 2026-11-19 00:00:00 | 7 | 418 ms | 542 ms | 0 | 0 |
| 2026-11-19 01:00:00 | 8 | 451 ms | 537 ms | 0 | 0 |
| 2026-11-19 02:00:00 | 7 | 361 ms | 512 ms | 0 | 0 |
| 2026-11-19 03:00:00 | 8 | 429 ms | 554 ms | 0 | 0 |
| 2026-11-19 04:00:00 | 7 | 387 ms | 503 ms | 0 | 0 |
| 2026-11-19 05:00:00 | 8 | 368 ms | 517 ms | 0 | 0 |
| 2026-11-19 06:00:00 | 7 | 397 ms | 591 ms | 0 | 0 |
| 2026-11-19 07:00:00 | 8 | 373 ms | 457 ms | 0 | 0 |
| 2026-11-19 08:00:00 | 8 | 396 ms | 569 ms | 0 | 0 |
| 2026-11-19 09:00:00 | 7 | 420 ms | 628 ms | 0 | 0 |
| 2026-11-19 10:00:00 | 8 | 392 ms | 592 ms | 0 | 0 |
| 2026-11-19 11:00:00 | 7 | 496 ms | 544 ms | 0 | 0 |
| 2026-11-19 12:00:00 | 7 | 458 ms | 824 ms | 0 | 0 |
| 2026-11-19 13:00:00 | 7 | 408 ms | 535 ms | 0 | 0 |
| 2026-11-19 14:00:00 | 7 | 345 ms | 404 ms | 0 | 0 |
| 2026-11-19 15:00:00 | 8 | 450 ms | 553 ms | 0 | 0 |
| 2026-11-19 16:00:00 | 7 | 426 ms | 600 ms | 0 | 0 |
| 2026-11-19 17:00:00 | 8 | 374 ms | 492 ms | 0 | 0 |
| 2026-11-19 18:00:00 | 7 | 382 ms | 580 ms | 0 | 0 |
| 2026-11-19 19:00:00 | 8 | 432 ms | 567 ms | 0 | 0 |
| 2026-11-19 20:00:00 | 7 | 392 ms | 541 ms | 0 | 0 |
| 2026-11-19 21:00:00 | 8 | 425 ms | 545 ms | 0 | 0 |
| 2026-11-19 22:00:00 | 7 | 466 ms | 593 ms | 0 | 0 |
| 2026-11-19 23:00:00 | 8 | 356 ms | 535 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.