Yandex Service Outage Affects Marketplaces, Delivery and Payments
On the morning of October 11, users reported disruptions to Yandex services and other companies’ services. The problems affected websites, apps, checkout, payments and delivery.
On the morning of October 11, 2026, users of Russian marketplaces, retailers and delivery services reported problems with websites, apps and placing orders. As Habr reports, Yandex said its data center infrastructure had been damaged and warned of disruptions to its services. Other companies were also experiencing problems, but the article does not establish a common cause for all the reported disruptions. In some services, the problems affected payments and delivery.
Where the Disruptions Occurred
According to user reports, apps and websites sometimes failed to open, pages would not load, and products did not appear. Users also had trouble signing in and placing orders. Yandex services reported as unstable or unavailable included Yandex Market, Yandex Pay, Yandex Taxi, Yandex Eats and Yandex Go.
Yandex said its specialists were working to restore the services. The damage also affected customer support: if users could not get in touch through an app, the company suggested contacting the services’ official social media accounts. It warned that responses could take longer than usual because of the volume of requests.
The article also lists Pyaterochka, Lenta, Magnit, M.Video, Lamoda, Flowwow and Wildberries. Food and grocery delivery services mentioned include Delivery, Dodo Pizza, Rostic’s, Vkusno — i tochka and Drinkit. Vkusno — i tochka’s website and mobile app were unavailable. The list shows where problems were reported, but does not explain the cause of the disruption at each company.
The problems extended beyond retail. Auto.ru, Cian, Apteka.ru, Urent and Citydrive were among the services mentioned. Delimobil switched to manual registration for new users, while timetables would not load in Yandex Trains. Representatives of the companies and services said their IT teams were working with cloud providers to restore operations. The article gives no estimate for a full recovery.
What Happened to Orders and Payments
For customers, the problems could appear at different stages: browsing products, signing in, placing or paying for an order, or receiving a delivery. These should not all be treated as the same failure: the source describes reports from users of different services, not a single technical scenario for every store.
Yandex Pay said it was working to restore purchase payments, payments in installments and cashback. The service’s press office assured users that their money was safe. The statement cited does not say when all functions will return to normal.
Yandex Market excluded orders placed on October 11 from the quality index across all operating models and said it would not charge fees for late deliveries. Pickup points and warehouses were operating normally, while sorting centers were temporarily unavailable. This was a specific decision about orders placed on the day of the outage, not an announcement of a rule change for the future.
M.Video warned that some system functions were unstable. The article does not specify which functions were affected. That statement alone therefore cannot show which step caused problems for each customer or whether everyone experienced the same issue.
What Online Stores Should Check
Store owners would do well to check the entire order journey, not just whether the website is accessible: whether products appear, sign-in works, purchases can be placed and paid for, and deliveries can be made. If a step is unavailable, customers need a clear explanation of the problem and a working way to get help. The problem with Yandex’s customer support is a reminder that the usual contact channel can also be disrupted during an outage.
Marketplace sellers should pay separate attention to the platform’s announcements about order processing and the consequences of delays. In this case, Yandex Market announced a decision on the quality index and late-delivery fees, but only for orders placed on October 11. It cannot be assumed to apply to other dates without a new announcement from the platform.
Finally, the list of affected companies is not a map of their technical dependencies. A more practical approach is to make your own list of the external services a purchase depends on and find out which stage of an order stops working when each one becomes unavailable. That means testing your own store, not trying to diagnose someone else’s systems.
My View: Put a Price on Dependencies
I would not take this outage as a reason for stores to abandon every external platform. First, I want answers to three questions: which dependency brings orders to a halt, how long is that acceptable, and what would a fallback cost? Without assessing workload, timelines and support, the word “resilience” does little to resolve anything.
To me, there is an important difference between a storefront that works and a purchase that can be completed. If a team does not know where an order breaks down when an external service fails, that is a more concrete problem than choosing another architecture.
Sources
Where the news comes from. The text is a retelling in the author’s own words; the facts come from the source, the opinion is the author’s.
lead backend developer
I’m responsible for APIs and integrations in commercial projects. I discuss new approaches in terms of load, timelines, and maintenance—“modern” alone doesn’t qualify as a criterion.
All posts by the authorRelated articles
Attackers Used DebugBear’s DNS to Replace a Website Monitoring Script
After an attack on DebugBear’s infrastructure, attackers replaced its Real User Monitoring script. Site owners using it to track Core Web Vitals are advised to remove the tag and check accounts.
ISPsystem Releases VMmanager Updates After Zero-Day Attack
ISPsystem has released security updates for VMmanager and reworked its security architecture after a zero-day attack. Checks of providers’ infrastructure are ongoing.
Google Completes September Spam Update After Nearly 14 Days
Google’s September spam update rolled out over 13 days and 16 hours, affecting Search worldwide. Here’s what site owners should check in their own data.
Discussion 4
Piotr Eskola
Nothing says “resilient checkout” like your payment, delivery, and product catalog all waiting for the same data center to have a better morning. That temporary dependency plugin is starting to look less temporary.
Markas Friedrichas
@piotr.eskola That’s a neat failure story, but the report doesn’t show that catalog, payments, and delivery all depended on the same data center. It says Yandex reported damage to its infrastructure, while other services also had issues and no common cause was established. I’d want the dependency map and actual failover behavior before calling this one shared checkout dependency rather than several coincident disruptions.
Yana Zurabishvili
Fair correction: the article doesn’t establish one shared data-center dependency, so “same checkout dependency” is too confident. The useful question for retailers is still whether their own catalog, payment, and delivery paths have independent fallbacks—or whether a Yandex outage can stall the whole order journey. Outages are temporary; dependency diagrams have a habit of being temporary too.
Ondřej Liška
@yazan_seo What concrete fallback would you expect here—cached product data, an alternate payment provider, or both? The report doesn’t establish which dependency actually failed for each retailer.