inDrive Gets "Tens of Thousands" of Driver Applications After Yandex Go Outage in Kazakhstan

inDrive founder Arsen Tomsky has reported "tens of thousands" of applications from new drivers. They came after a surge of users and orders that happened during an outage at Yandex Go in Kazakhstan. The available material does not disclose the exact number of new passengers, the volume of additional orders, or the length of the outage, so for now the scale of the episode can only be judged by the order of magnitude of that one figure.

What is known

The facts are few and fit in a handful of lines. Tomsky speaks of driver applications, not of the number of drivers who have already gone online. According to the statement, the jump in demand fell in a period of problems at inDrive's main competitor in Kazakhstan. The link between the two events is presented as a coincidence in time, not as a proven chain of cause and effect. Nobody in the statement names the root cause of the Yandex Go outage or its duration.

The phrase "tens of thousands" points to a strong spike, but without a baseline it is hard to judge. It is unknown how many applications inDrive receives on an ordinary day. It is also unclear how many of them will make it to going online.

Why one service's outage moves the market

Taxi services run as two-sided marketplaces. Passengers need drivers nearby, and drivers need orders. When one operator's app won't open or won't accept orders, passengers look for a replacement within minutes. Drivers follow the orders, because idle time costs them money. inDrive has an additional quirk: the passenger and the driver negotiate the price of the ride between themselves. That model is appealing in moments of chaos, when the usual fares don't work.

The main bottleneck of such a marketplace is supply. Passengers can be attracted in a day, but a driver has to be vetted, onboarded, and taught to use the app. An application does not yet mean an active driver: document checks, vehicle data, and sometimes in-person verification stand in the way.

What is known and what is not

• Volume of driver applications: "tens of thousands"; the exact number is not disclosed.
• Source of the report: inDrive founder Arsen Tomsky.
• Context: an outage at Yandex Go in Kazakhstan.
• Number of new passengers and orders: not published.
• Duration and cause of the outage: not named.
• Share of applications that became active drivers: unknown.

What to watch next

For the ride-hailing industry, applications matter less than retention. If users who came because of the outage keep riding after it is fixed, that will change the balance in the Kazakhstan market. If they go back to their previous app, the episode will remain a temporary overload.

In practice, four metrics are worth tracking. First: driver onboarding speed, meaning how many applications turn into active accounts within a week. Second: car arrival time and the share of canceled orders during peak hours. Third: app download trends in Kazakhstan 2–4 weeks after the spike. Fourth: the load on customer support and the verification system, since they are the first to hit a ceiling during sharp growth.

For developers and platform operators, the takeaway is practical. A competitor's stability affects your load as much as your own marketing does. Capacity for servers, verification queues, and support should be planned not only for scheduled growth but also for the scenario in which a major player next door goes down. Everything now depends on whether inDrive discloses figures on orders and active drivers: without them, the story remains a loud claim from a founder, not a measurable market shift.