Cian Relaunches Website and App in Limited Mode After Partner's Infrastructure Outage

The real estate service Cian has brought its website and mobile app back online, but only in limited mode. The cause of the failure was an outage at an infrastructure partner's facility. As of the morning of 12 October 2026, the company confirms three things: both access channels partially work, data is being moved from backups to new capacity, and there is no timeline for full recovery. The announcement gives no figures on the length of the downtime, the number of affected users, or the volume of data.

The phrase "outage at an infrastructure partner's facility" says more about the architecture than it appears to. The platform's key services are apparently hosted at a third-party provider's site, whether a data center or a cloud operator. When that site goes down, the problem immediately becomes the customer's problem. The company does not say what exactly happened at the facility, so speculating about causes is pointless.

What is known so far

The facts are few and fit in a short list:

• Status: the website and mobile app are running in limited mode.
• Cause: an outage at an infrastructure partner's facility.
• What is being done now: data is being moved from backups to new capacity, and the platform is being checked for operability.
• Timeline for full recovery: not given.
• Not disclosed: which functions are unavailable, whether any data was lost, and which partner was affected.

The word "limited" explains nothing by itself. It could mean a read-only mode, a disabled user account area, unavailable viewing requests, or a stripped-down search. Until the company clarifies which one applies, it is too early to draw conclusions.

Why recovery from backups drags on

Moving data from backups to new capacity is the heaviest recovery scenario. The platform is not simply restarted; it is rebuilt from scratch in a different location. The chain that follows usually looks like this: provision compute and network, load the data, verify integrity, bring up dependent services, warm up caches and indexes, run checks. For a platform with millions of listings, photos and user accounts, each step takes time. This is the general logic of such operations, not data about Cian's internal workings.

Another difficulty is that a backup always lags behind the live system. The less frequently backups were taken, the more recent changes will have to be reconstructed some other way or written off as lost. The company has not spoken publicly about this, and the question remains open.

Here, uncertainty about timing is more a sign of honesty than of weakness. Promising an exact time while data is still being verified at the new site risks a second missed deadline.

What companies with a similar dependency should check

This story is useful to anyone whose business relies on a single partner site. A few practical steps:

1. Set explicit targets: how quickly the service must come back (RTO) and how much data you can afford to lose (RPO). Without these numbers, the recovery plan exists only on paper.

2. Test recovery in practice. A backup that has never been fully restored is still a hypothesis.

3. Find out whether your backups and your production system sit at the same site. If they do, that is one point of failure instead of two.

4. Plan a degraded mode in advance. It is better for users to see search and listing pages in read-only mode than a blank page.

5. Prepare your communication. A clear message about what works and what does not reduces the load on support.

If you are an agent, realtor or developer who works through the platform, it makes sense to keep a backup channel for reaching clients: contacts outside the service, exports of your current listings, and arrangements for handling requests manually. Until Cian gives a timeline, it is better to plan for a prolonged outage.

Two signals are worth watching next: an official list of restored functions and an explanation of the outage's causes. The second will determine whether this remains a one-off incident or becomes a reason for the market to reconsider its dependence on individual sites.