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
Marketplaces
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: 589 ms
Response time
589 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-11 00:00:00 | 23 | 621 ms | 780 ms | 0 | 0 |
| 2026-11-11 03:00:00 | 22 | 667 ms | 1 399 ms | 0 | 0 |
| 2026-11-11 06:00:00 | 23 | 727 ms | 1 873 ms | 0 | 0 |
| 2026-11-11 09:00:00 | 22 | 735 ms | 1 096 ms | 0 | 0 |
| 2026-11-11 12:00:00 | 23 | 740 ms | 1 671 ms | 0 | 0 |
| 2026-11-11 15:00:00 | 22 | 740 ms | 1 007 ms | 0 | 0 |
| 2026-11-11 18:00:00 | 23 | 752 ms | 1 623 ms | 0 | 0 |
| 2026-11-11 21:00:00 | 23 | 662 ms | 1 337 ms | 0 | 0 |
| 2026-11-12 00:00:00 | 22 | 610 ms | 716 ms | 0 | 0 |
| 2026-11-12 03:00:00 | 22 | 624 ms | 795 ms | 0 | 0 |
| 2026-11-12 06:00:00 | 23 | 676 ms | 839 ms | 0 | 0 |
| 2026-11-12 09:00:00 | 22 | 740 ms | 2 569 ms | 0 | 0 |
| 2026-11-12 12:00:00 | 23 | 717 ms | 1 171 ms | 0 | 0 |
| 2026-11-12 15:00:00 | 22 | 760 ms | 1 073 ms | 0 | 0 |
| 2026-11-12 18:00:00 | 23 | 806 ms | 2 224 ms | 0 | 0 |
| 2026-11-12 21:00:00 | 22 | 659 ms | 833 ms | 0 | 0 |
| 2026-11-13 00:00:00 | 22 | 743 ms | 3 308 ms | 0 | 0 |
| 2026-11-13 03:00:00 | 23 | 622 ms | 691 ms | 0 | 0 |
| 2026-11-13 06:00:00 | 22 | 628 ms | 869 ms | 0 | 0 |
| 2026-11-13 09:00:00 | 23 | 707 ms | 1 790 ms | 0 | 0 |
| 2026-11-13 12:00:00 | 22 | 643 ms | 759 ms | 0 | 0 |
| 2026-11-13 15:00:00 | 23 | 598 ms | 810 ms | 0 | 0 |
| 2026-11-13 18:00:00 | 22 | 625 ms | 1 046 ms | 0 | 0 |
| 2026-11-13 21:00:00 | 23 | 596 ms | 786 ms | 0 | 0 |
| 2026-11-14 00:00:00 | 22 | 595 ms | 677 ms | 0 | 0 |
| 2026-11-14 03:00:00 | 23 | 578 ms | 641 ms | 0 | 0 |
| 2026-11-14 06:00:00 | 22 | 585 ms | 808 ms | 0 | 0 |
| 2026-11-14 09:00:00 | 23 | 653 ms | 2 035 ms | 0 | 0 |
| 2026-11-14 12:00:00 | 22 | 605 ms | 1 101 ms | 0 | 0 |
| 2026-11-14 15:00:00 | 23 | 600 ms | 782 ms | 0 | 0 |
| 2026-11-14 18:00:00 | 22 | 654 ms | 1 715 ms | 0 | 0 |
| 2026-11-14 21:00:00 | 23 | 616 ms | 717 ms | 0 | 0 |
| 2026-11-15 00:00:00 | 22 | 576 ms | 650 ms | 0 | 0 |
| 2026-11-15 03:00:00 | 23 | 594 ms | 758 ms | 0 | 0 |
| 2026-11-15 06:00:00 | 22 | 551 ms | 638 ms | 0 | 0 |
| 2026-11-15 09:00:00 | 23 | 595 ms | 680 ms | 0 | 0 |
| 2026-11-15 12:00:00 | 22 | 630 ms | 1 258 ms | 0 | 0 |
| 2026-11-15 15:00:00 | 23 | 643 ms | 1 542 ms | 0 | 0 |
| 2026-11-15 18:00:00 | 22 | 599 ms | 685 ms | 0 | 0 |
| 2026-11-15 21:00:00 | 14 | 605 ms | 702 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.
19:42
19:50
19:58
20:06
20:14
20:22
20:30
20:38
20:46
20:54
21:02
21:10
21:18
21:26
21:34
21:42
21:50
21:58
22:06
22:14
22:22
22:30
22:38
22:46
Last check
2026-11-15 22:46:13
HTTP
200
Response time
589 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.