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.
← All services
Search engines
Is Яндекс down? Current status and outages
Доступен из точки NexIPHTTP-проверка из точки NexIP успешна. Доступность из всех регионов не подтверждена.
Understanding the metrics
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
Current state
Outage score
0/100
Statistical assessment
User signals
0
unique in the last 15 minutes
Automatic check
Available
Response: 663 ms
Response time
663 ms
Last local automatic check
User reports over the last 24 hours
Reports submitted to NexIP. One report does not prove a widespread outage.
Reports in selected period
0
No reports during this period.
30-minute intervals · Moscow time · actual dataLast 7 days
Recent incidents
No confirmed large-scale incidents were recorded during the last 7 days.
Observation points
Regional checks
Remote observation points are not connected yet.
Observation history
Latest automatic checks
OUTAGE INTELLIGENCE / SERVICE PROBES
Check history and reliability
Actual NexIP primary probe measurements, not user reports
Full-period overviewAll observations
Latest 40 intervals · CSV includes entire selection
| Time (server) | Checks | Average | Peak | Down | Blocked |
|---|---|---|---|---|---|
| 2026-11-13 08:30:00 | 3 | 587 ms | 622 ms | 0 | 0 |
| 2026-11-13 09:00:00 | 4 | 561 ms | 578 ms | 0 | 0 |
| 2026-11-13 09:30:00 | 4 | 555 ms | 565 ms | 0 | 0 |
| 2026-11-13 10:00:00 | 4 | 665 ms | 896 ms | 0 | 0 |
| 2026-11-13 10:30:00 | 3 | 606 ms | 663 ms | 0 | 0 |
| 2026-11-13 11:00:00 | 4 | 589 ms | 616 ms | 0 | 0 |
| 2026-11-13 11:30:00 | 4 | 590 ms | 637 ms | 0 | 0 |
| 2026-11-13 12:00:00 | 4 | 637 ms | 718 ms | 0 | 0 |
| 2026-11-13 12:30:00 | 3 | 671 ms | 831 ms | 0 | 0 |
| 2026-11-13 13:00:00 | 4 | 669 ms | 871 ms | 0 | 0 |
| 2026-11-13 13:30:00 | 4 | 661 ms | 826 ms | 0 | 0 |
| 2026-11-13 14:00:00 | 4 | 713 ms | 863 ms | 0 | 0 |
| 2026-11-13 14:30:00 | 3 | 579 ms | 589 ms | 0 | 0 |
| 2026-11-13 15:00:00 | 4 | 632 ms | 786 ms | 0 | 0 |
| 2026-11-13 15:30:00 | 4 | 631 ms | 664 ms | 0 | 0 |
| 2026-11-13 16:00:00 | 4 | 654 ms | 707 ms | 0 | 0 |
| 2026-11-13 16:30:00 | 3 | 594 ms | 636 ms | 0 | 0 |
| 2026-11-13 17:00:00 | 4 | 647 ms | 802 ms | 0 | 0 |
| 2026-11-13 17:30:00 | 4 | 555 ms | 565 ms | 0 | 0 |
| 2026-11-13 18:00:00 | 4 | 629 ms | 689 ms | 0 | 0 |
| 2026-11-13 18:30:00 | 3 | 577 ms | 595 ms | 0 | 0 |
| 2026-11-13 19:00:00 | 4 | 597 ms | 616 ms | 0 | 0 |
| 2026-11-13 19:30:00 | 4 | 624 ms | 648 ms | 0 | 0 |
| 2026-11-13 20:00:00 | 4 | 629 ms | 682 ms | 0 | 0 |
| 2026-11-13 20:30:00 | 3 | 579 ms | 595 ms | 0 | 0 |
| 2026-11-13 21:00:00 | 4 | 610 ms | 658 ms | 0 | 0 |
| 2026-11-13 21:30:00 | 4 | 613 ms | 643 ms | 0 | 0 |
| 2026-11-13 22:00:00 | 4 | 569 ms | 599 ms | 0 | 0 |
| 2026-11-13 22:30:00 | 3 | 550 ms | 562 ms | 0 | 0 |
| 2026-11-13 23:00:00 | 4 | 627 ms | 693 ms | 0 | 0 |
| 2026-11-13 23:30:00 | 4 | 542 ms | 555 ms | 0 | 0 |
| 2026-11-14 00:00:00 | 4 | 557 ms | 574 ms | 0 | 0 |
| 2026-11-14 00:30:00 | 3 | 539 ms | 553 ms | 0 | 0 |
| 2026-11-14 01:00:00 | 4 | 545 ms | 566 ms | 0 | 0 |
| 2026-11-14 01:30:00 | 4 | 576 ms | 667 ms | 0 | 0 |
| 2026-11-14 02:00:00 | 4 | 534 ms | 541 ms | 0 | 0 |
| 2026-11-14 02:30:00 | 3 | 533 ms | 546 ms | 0 | 0 |
| 2026-11-14 03:00:00 | 4 | 556 ms | 574 ms | 0 | 0 |
| 2026-11-14 03:30:00 | 4 | 539 ms | 559 ms | 0 | 0 |
| 2026-11-14 04:00:00 | 2 | 612 ms | 663 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.
01:08
01:15
01:24
01:32
01:40
01:48
01:56
02:04
02:12
02:19
02:27
02:35
02:44
02:52
03:00
03:07
03:16
03:24
03:32
03:40
03:48
03:55
04:04
04:12
Last check
2026-11-14 04:12:08
HTTP
200
Response time
561 ms
Your signal
Having a problem with this service?
Tell us. Registration is not required. The same signal will not be counted repeatedly within a short period.
Community reviews
User opinions are separate from the technical outage status.
Your rating
No ratings yet
Leave a comment
Published comments
No comments yet.
Is Яндекс down?
This page tracks the current observed status of Яндекс, recent incidents, automated availability checks and available user reports. NexIP does not treat a single failed check as proof of a global outage.
Additional diagnostics
Ping · Website availability · Website monitoring · All service outages
Frequently asked questions
Is Яндекс down right now?
NexIP shows the current observed status of Яндекс using automated checks, incident data and available user signals. A local connection problem may differ from a large-scale outage.
Why can the service work for some users but not others?
Availability can differ by provider, region, DNS, routing, application version or service component. NexIP therefore separates observed signals from confirmed large-scale incidents.
How can I check whether the problem is on my side?
Check the host with Ping, website availability and your own connection. Comparing several independent checks helps distinguish a local problem from a wider outage.