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: 542 ms
Response time
542 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 22:35:00 | 1 | 546 ms | 546 ms | 0 | 0 |
| 2026-11-13 22:40:00 | 1 | 541 ms | 541 ms | 0 | 0 |
| 2026-11-13 22:50:00 | 1 | 562 ms | 562 ms | 0 | 0 |
| 2026-11-13 23:00:00 | 1 | 693 ms | 693 ms | 0 | 0 |
| 2026-11-13 23:05:00 | 1 | 678 ms | 678 ms | 0 | 0 |
| 2026-11-13 23:15:00 | 1 | 560 ms | 560 ms | 0 | 0 |
| 2026-11-13 23:20:00 | 1 | 578 ms | 578 ms | 0 | 0 |
| 2026-11-13 23:30:00 | 1 | 553 ms | 553 ms | 0 | 0 |
| 2026-11-13 23:35:00 | 1 | 555 ms | 555 ms | 0 | 0 |
| 2026-11-13 23:45:00 | 1 | 529 ms | 529 ms | 0 | 0 |
| 2026-11-13 23:55:00 | 1 | 531 ms | 531 ms | 0 | 0 |
| 2026-11-14 00:00:00 | 1 | 557 ms | 557 ms | 0 | 0 |
| 2026-11-14 00:10:00 | 1 | 574 ms | 574 ms | 0 | 0 |
| 2026-11-14 00:15:00 | 1 | 569 ms | 569 ms | 0 | 0 |
| 2026-11-14 00:25:00 | 1 | 526 ms | 526 ms | 0 | 0 |
| 2026-11-14 00:35:00 | 1 | 553 ms | 553 ms | 0 | 0 |
| 2026-11-14 00:40:00 | 1 | 530 ms | 530 ms | 0 | 0 |
| 2026-11-14 00:50:00 | 1 | 533 ms | 533 ms | 0 | 0 |
| 2026-11-14 01:00:00 | 1 | 566 ms | 566 ms | 0 | 0 |
| 2026-11-14 01:05:00 | 1 | 556 ms | 556 ms | 0 | 0 |
| 2026-11-14 01:15:00 | 1 | 538 ms | 538 ms | 0 | 0 |
| 2026-11-14 01:20:00 | 1 | 521 ms | 521 ms | 0 | 0 |
| 2026-11-14 01:30:00 | 1 | 548 ms | 548 ms | 0 | 0 |
| 2026-11-14 01:40:00 | 1 | 667 ms | 667 ms | 0 | 0 |
| 2026-11-14 01:45:00 | 1 | 544 ms | 544 ms | 0 | 0 |
| 2026-11-14 01:55:00 | 1 | 544 ms | 544 ms | 0 | 0 |
| 2026-11-14 02:00:00 | 1 | 536 ms | 536 ms | 0 | 0 |
| 2026-11-14 02:10:00 | 1 | 538 ms | 538 ms | 0 | 0 |
| 2026-11-14 02:15:00 | 1 | 520 ms | 520 ms | 0 | 0 |
| 2026-11-14 02:25:00 | 1 | 541 ms | 541 ms | 0 | 0 |
| 2026-11-14 02:35:00 | 1 | 546 ms | 546 ms | 0 | 0 |
| 2026-11-14 02:40:00 | 1 | 536 ms | 536 ms | 0 | 0 |
| 2026-11-14 02:50:00 | 1 | 518 ms | 518 ms | 0 | 0 |
| 2026-11-14 03:00:00 | 1 | 528 ms | 528 ms | 0 | 0 |
| 2026-11-14 03:05:00 | 1 | 570 ms | 570 ms | 0 | 0 |
| 2026-11-14 03:15:00 | 1 | 551 ms | 551 ms | 0 | 0 |
| 2026-11-14 03:20:00 | 1 | 574 ms | 574 ms | 0 | 0 |
| 2026-11-14 03:30:00 | 1 | 510 ms | 510 ms | 0 | 0 |
| 2026-11-14 03:40:00 | 1 | 544 ms | 544 ms | 0 | 0 |
| 2026-11-14 03:45:00 | 1 | 542 ms | 542 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.
00:44
00:52
01:00
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
Last check
2026-11-14 03:48:07
HTTP
200
Response time
542 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.