Summary

  • Telega's strongest evidence is not conventional access infrastructure. It is a short-lived but visible operating perimeter: a Russian software company, a Telegram-client product, app-store distribution, proxy claims, an LIR object, AS203502, a 130.49.152.0/24 route and a paid-access experiment.
  • The business case depended on a spread between users' willingness to pay for stable Telegram access and the cost of proxy capacity, content delivery, engineering, moderation, support, refunds, security response and platform compliance. A 99-ruble subscription could help capacity expansion, but it was not enough by itself to prove a durable moat.
  • The July 2026 closure is economically decisive. Telega had demand, claimed a multimillion-user audience and created real network-resource evidence, yet it could not keep the distribution, compliance and trust boundary stable enough to continue as a Telegram-client business.

The narrow boundary is not a broadband network

The first discipline in analysing Telega is to define the operating boundary as tightly as the evidence allows. The company is registered as a software developer in Kazan. Its public product was a Telegram client with additional features and proxy-assisted access. Its visible network footprint was an autonomous system, one assigned IPv4 /24 and a route object that was seen in public routing for several months. That is real infrastructure evidence, but it is not the same as a city fibre network, a last-mile broadband franchise or a carrier with its own household access lines.

This distinction changes the economics. A regional ISP earns from broadband subscriptions, business circuits, backhaul and local support. It spends on ducts, fibre, poles, electronics, field technicians, transit, customer premises equipment and churn management. Telega's likely cost stack was different. It needed mobile and desktop engineering, app-store access, proxy servers, content-delivery capacity, payment handling, legal response, trust repair, support operations and enough network control to keep the client reachable when Telegram access was unstable. The customer was not paying for a line into a home.

The customer was paying for a working path to a social graph that Telega did not own.

That makes Telega more like a reliability intermediary than an access operator. The company could create value if users faced unreliable Telegram access, if Telega could make connection recovery simpler than user-managed substitutes, and if enough users paid for priority access or related features to cover capacity and support. It would lose value if official Telegram access recovered, if users preferred VPNs or other clients, if app stores restricted distribution, if security concerns damaged trust, or if the underlying Telegram-client format could not satisfy Russian compliance requirements.

The official record shows all of those forces at once. Telega said the app was based on Telegram's open code and used Telegram infrastructure for messages. It also said it used dedicated proxy servers to improve stability. It claimed more than five million users on the public site and later said it had built a multimillion audience. It opened a waitlist because more people wanted access than the service could connect at once. It then introduced Telega Plus at 99 rubles per month for priority access and a more stable connection. Within weeks, it disabled calls because about 1.5% of users used them and they were expensive to support.

By late June it announced closure from 1 July 2026.

The economic meaning is not that Telega had no demand. It plainly had demand. The meaning is that demand arrived through a stressed access environment and depended on distribution channels, trust and compliance outside Telega's full control. A company can survive expensive infrastructure if it owns the customer relationship and can price reliability. Telega owned only part of the reliability chain. The rest sat with Telegram, app stores, upstream providers, security classifiers, payment services, mobile operating systems and public perception.

Legal identity and brand transition

The legal file points to a young company with a software-company identity. Public registry profiles and the official corporate site identify AO Telega as a Kazan joint stock company with registry number 1251600003753, tax number 1655506819 and a legal address on Spartakovskaya Street. The company was registered on 30 January 2025. Its main activity is computer software development. Public profiles list Alexander Mikhailovich Smirnov as general director from the registration date.

The current legal identity is clean enough for this article's purpose, but the brand transition matters. Public contractor and app-store profiles preserve evidence of the earlier "Dal" naming. RuStore's crawled listing still displayed the developer as AO "Dal", while the current official company site and legal pages identify AO Telega. The package name in app stores also preserved "ru.dahl.messenger". That is not merely cosmetic.

It tells the reader that Telega's market identity was assembled quickly around a consumer product whose legal, product and distribution labels did not all refresh at the same time.

The official corporate site describes the company as a developer of complex IT products and lists hiring roles across Android, iOS, DevOps, backend, C++, UI/UX, QA and security leadership. That looks like a product-engineering organisation, not a local telecom utility. The official app agreement also defines Telega as a client application based on Telegram code, interacting with Telegram through API calls to provide access to Telegram features and Telega-specific functions in Russia. The privacy policy identifies the same operator and lists categories such as profile data, device and technical data, and service-operation purposes.

The financial profile is more revealing than the legal form. Public financial aggregators report 2025 revenue of 101,000 rubles and a 2025 net loss of about 93 million rubles. That is not the pattern of a mature access operator. It is the pattern of a funded product build before meaningful revenue. The 10,000-ruble authorized capital tells the reader little about economic backing. Engineering payroll, server capacity, legal response and app-store operations cannot be funded from nominal capital. The actual business depended on outside resources, founders' prior proceeds, partner capacity, or future user payments.

The official site says founders Fanis Sadykov and Alexander Smirnov had worked together for years, launched an interactive video service and sold it, then put proceeds into Telega. That explains how a very young legal entity could attempt a mass-market communications product before showing accounting revenue. It does not prove long-term capital adequacy. If anything, it sharpens the test: early capital can buy a launch, but the product still needs recurring cash flow to pay for capacity, support, compliance and trust.

The company therefore should not be valued by the fact that it was a joint stock company or had an LIR entry. Those are permissions and operating tools. The question is whether they sat under a business with repeatable economics. The public record suggests a fast experiment: legal company in January 2025, app growth through 2025 and early 2026, network-resource activation in late 2025, paid priority access in May 2026 and closure in July 2026.

What the product actually sold

Telega sold continuity, not a new social graph. Its public copy promised stable access to Telegram, fast synchronization and additional functions. It emphasized that users could sign in with the same phone number, keep their Telegram chats, contacts, channels and settings, and use Telega alongside Telegram. That is attractive because it removes switching friction. It is also economically limiting because the user relationship remains anchored to Telegram.

The product features were sensible for a Telegram client. The home and download pages described a single feed for posts from subscribed channels, parental-control style tools, interface customization, expanded formatting, quick replies and creator tools. The author page pitched Telega to channel administrators who wanted stable access to subscribers, higher reach, support and monetization links. These features are not trivial. They give the app a reason to exist even when pure access improves.

Yet each feature still depends on Telegram's underlying network effects. A creator does not move an audience to Telega; Telega presents the existing Telegram audience in a different client. A parent does not adopt a new independent messaging system; they use an alternate client around a Telegram account. A user does not rebuild contacts; they log into the same account. This is good for acquisition and weak for pricing power.

The waitlist shows the same tension. Telega said more users wanted to join than it could connect at once, so access opened in stages as capacity grew. That is a strong demand signal, but it is also a warning. A waitlist in a software product often looks like scarcity-driven appeal. In a reliability product, it can also reveal that cost scales faster than readiness. If the company cannot connect new users without risking service quality, user growth is not free. Every new user can consume proxy sessions, file traffic, support attention, abuse monitoring and payment service load.

Telega Plus was the direct attempt to solve that problem. At 99 rubles per month, it promised access without waiting, stable proxy connection, priority support and Telega-specific features. The official launch announcement said the first day would make the subscription available to the first one million users from the waitlist. In the best case, this turned demand pressure into capacity funding: people who valued immediate access paid, and the company used cash to expand servers and product work.

The challenge is that 99 rubles is a low price for a product with high fixed trust and platform costs. It can cover some incremental server load if usage is light and payment friction is low. It cannot by itself repair an App Store ban, a security scare, refund obligations, legal work, or a full content-delivery build. It is also fragile because users can treat it as an emergency bridge. If official Telegram access works again or a free workaround is easier, willingness to pay falls quickly.

The call shutdown shows management making the right local decision under pressure. Telega said audio and video calls were used by about 1.5% of users and were among the most complex and expensive functions to support. It shifted resources toward stable app operation and faster sending of photos, video and files through proxy and content delivery. That is a rational pruning move. It also reveals the cost problem. Even a feature that helped Telega stand apart had to be cut when usage did not justify support burden.

Network evidence: small address space, real routing, short life

The most concrete infrastructure evidence is AS203502 and the 130.49.152.0/24 block. RIPE records show ORG-JSC21-RIPE for JOINT STOCK COMPANY "TELEGA", with LIR status, a Kazan address and the same Russian registry number. The organisation object was created on 21 November 2025. The aut-num object for AS203502 was created on 24 November 2025, with as-name Telega and import/export lines involving AS47764 and AS49281. Public BGP sources identify AS47764 as LLC VK and AS49281 as M100 LLC.

RIPE search records show 130.49.152.0 through 130.49.152.255 assigned to RU-TELEGA on 11 December 2025, with a route object for 130.49.152.0/24 originated by AS203502 created on 15 December. RIPEstat routing status showed the prefix first seen on 17 December 2025 and last seen on 30 June 2026. A query on 25 July 2026 showed zero RIS peers seeing the route, no current announced prefixes and announced false for the AS overview.

That time sequence is economically useful. The route appears shortly after the Telega legal and product build had momentum. It remains visible through the period of heightened demand, controversy, paid-access launch and pre-closure communication. It disappears from RIPEstat visibility at the end of June, immediately before the announced 1 July closure. The route evidence therefore supports the view that Telega had an operating network layer tied to its consumer-service period. It does not support the view that Telega had a deep, continuing access network after closure.

The size of the footprint matters. One /24 means 256 IPv4 addresses. Public AS tools generally showed no IPv6 and no downstream networks. Some third-party tools described Telega as a stub or edge network and cached earlier active announcements. That is consistent with a proxy or application-support footprint, not a carrier-scale network. It can be operationally important without being large.

If one compares 256 IPv4 addresses with Telega's home-page claim of more than five million users, the ratio is about one address for every 19,500 claimed users. That does not mean one IP address handled that many simultaneous sessions. Address space can front load balancers, proxies, control endpoints or other infrastructure. But the ratio still tells the reader that Telega's public IP holdings were small relative to its claimed audience. The product depended on efficient shared infrastructure, upstream providers and cloud or partner capacity rather than a broad address estate.

The upstream signals are also sensitive. RIPE DB listed import/export records with VK and M100. Independent critics and media focused heavily on possible VK links and server routing. Telega publicly denied being a VK product while acknowledging in some responses reported by media that it used commercially available technology from VK-linked services. The safe economic reading is narrower than the political claim: Telega did not control the full stack alone. It depended on important counterparties for network, analytics, calls or server resources, and that dependence raised trust and bargaining risk.

Current routing status should not be overinterpreted. A route that is not visible on 25 July does not prove the company disappeared or that every server was gone. It proves that the public route visible earlier was not active in RIPEstat at that query time. Combined with the closure announcement, that is enough to say the network evidence was real but not durable.

Unit economics: 99 rubles is a contribution, not a moat

The clearest number in Telega's monetization story is 99 rubles per month for Telega Plus. In consumer terms it is inexpensive. In infrastructure terms it is only useful if the company can keep marginal service costs low and avoid expensive failures. For a subscription product that mainly sells priority access and stable connection, the price must pay for capacity, support, payment processing, refunds, customer communication, security work and engineering.

The theoretical upside looked large. If one million waitlisted users had all subscribed at 99 rubles, gross monthly billings would have been 99 million rubles before fees, taxes, refunds and operating costs. If all five million claimed users had paid, the monthly gross figure would approach 495 million rubles. These are sensitivity calculations, not observed revenue. They show why Telega had reason to test payment quickly. A small monthly fee on a large audience can transform a costly proxy product into a fundable service.

The observed financial base was much weaker. Public financial profiles show only 101,000 rubles of 2025 revenue against about 93 million rubles of net loss. That period may predate full monetization, and the 2026 subscription test is not captured there. Still, the figures frame the capital gap. Telega had been spending ahead of revenue. To justify the spend, it needed rapid conversion, low churn, stable distribution and no large refund or legal shock.

The refund announcement undermines the best-case revenue story. After closure, Telega said active Telega Plus users would receive refunds, with full refunds for purchases after 27 May and pro-rated treatment for some earlier three-month subscriptions. Refunds are appropriate customer treatment, but they convert part of the paid-access launch from revenue into working-capital churn. Money collected to expand capacity can become money returned just as the service winds down.

The cost stack also did not behave like a simple app subscription. Telega said calls had low usage but high support complexity. It named stable sending of photos, video and files through proxy and content delivery as a priority. Those are bandwidth-heavy or engineering-heavy functions. Messaging text is cheap. Media delivery and calls are not. If Telega's value proposition was "Telegram works here when it otherwise may not," heavy users were likely to be the users who cared most and cost most.

Support labour was another cost. The product had a waitlist, store reviews, official channels, bots, creator programmes and refund handling. A communications app under security allegations also needs a public-response function. Telega's official security page listed vendor interactions, explanations of proxy architecture and clarifications about data handling. That kind of trust work consumes senior engineering and leadership time. It is not optional when the product asks users to log into a Telegram account through a third-party client.

The economic judgement on the price is therefore mixed. Telega Plus was the right type of monetization for the capacity problem. It made heavy demand visible and asked urgent users to fund immediate access. But the price was too exposed to events outside ordinary usage: app-store removal, security warnings, official Telegram labels, media allegations, payment refunds and compliance demands. A small subscription can scale a stable service; it cannot carry a trust crisis and platform loss at the same time.

Distribution dependence turned reach into fragility

Telega's reach depended on stores and channels it did not own. Google Play, RuStore, AppGallery, App Store, desktop downloads and Telegram channels each played a role. That gave Telega multiple paths to users, but each path carried its own gatekeeper. A regional broadband company may need pole access or building entry. Telega needed app-store acceptance, signing certificates, platform trust and enough public visibility to reassure users.

The App Store episode made this dependence visible. Media reported Telega disappeared from App Store in April 2026. Telega later said Apple removed the app, blocked the developer account and limited the launch of already installed copies. The company filed a complaint with Russia's Federal Antimonopoly Service. It argued that Apple had not supplied enough technical detail or a useful chance to cure alleged issues. Whatever the final merits, the economic result was immediate: iOS distribution and trust were impaired.

This is a severe risk for a communications app because adoption often depends on the least technical user. Android users may use Google Play, RuStore, AppGallery or a download page. Desktop users may download directly. iPhone users generally rely on App Store. When one major platform removes the app, Telega loses not just downloads but legitimacy. A security warning on a phone has more force than a company blog post. It changes user behaviour before any legal process finishes.

Google Play and RuStore also show the instability. Google Play listed the app with 10 million-plus downloads, a 4.0 rating and about 191,000 reviews in the crawled listing. RuStore showed a 4.5 rating, about 35,300 ratings and 7,695 reviews, but the crawled page said the app was unavailable for download. Store data is not perfectly synchronized, but that mismatch is itself instructive. Telega could have demand and still lack uniform distribution.

The official download page also retained links to different store options and desktop packages while other pages redirected to the closure announcement. This shows how a fast shutdown can leave public surfaces out of phase. For a consumer app, such lag creates confusion. Is the product still available? Are refunds live? Which users can still log in? Which store listing is current? Confusion raises support cost and lowers trust precisely when the company needs calm.

Distribution dependence also shaped the closure rationale. Telega said that, in the Telegram-client format, it could not ensure full localization and compliance with all current requirements, including external restrictions from technology platforms such as removal from App Store. This is not a statement about server cost alone. It is a statement about the entire operating permission set. Telega's economic lane existed only while access demand, platform tolerance, compliance capacity and user trust overlapped. Once that overlap broke, the business closed.

Customer concentration and trust

Telega's apparent audience was large but concentrated around one use case: access to Telegram under difficult conditions. That kind of concentration is easy to underestimate. A five-million-user claim sounds diversified, but if most users arrive for the same reason, the company has correlated demand. The same event that creates the audience can also reverse it.

The strongest customers were likely urgent users: people who needed Telegram access without manual configuration, users who could not make calls or media work reliably, channel administrators who feared losing reach, and people willing to pay 99 rubles to skip a waitlist. These customers value uptime. They also have low tolerance for uncertainty about account security. A broadband customer can complain about speed and still keep service because alternatives are weak. A communications-app user can remove an app in seconds if trust fails.

This is why Telega's security narrative had direct economic value. The official security page tried to define the boundary: Telega said it was not an independent messenger platform, did not store correspondence, used Telegram's authorization and message handling, and had no way to access accounts outside normal procedures. It acknowledged dedicated proxy servers and said their unusual pattern led to false security classifications. It also listed several providers that it said had cleared or removed negative classifications after manual review.

Critics and media presented a different risk picture. Technical reports alleged data-center substitution, traffic routing through Telega-controlled or related servers, extra keys, hidden proxy behaviour, links to VK tooling and the possibility of observing communication metadata or content. Telega disputed the strongest claims and said its technology choices did not make it a VK product. The article does not need to adjudicate every claim to draw the economic conclusion. The controversy itself was costly.

Trust risk is asymmetric. If the user believes Telega is safe and reliable, the company earns 99 rubles a month or a large audience. If the user believes the app may expose their account, the company loses the user entirely. The upside is small recurring revenue; the downside is total churn and reputational damage. That is a poor risk-reward ratio unless the company can make its security boundary obvious and independently credible.

The creator channel strategy added another concentration layer. Telega's author pages promised stable access to audiences, a feed that could raise reach, recommendation tools and monetization links. Creator tools can raise engagement, but creators are highly sensitive to platform legitimacy. If subscribers receive warnings or if official Telegram marks unofficial-client users, creators may avoid encouraging adoption. A creator product that depends on trust cannot sit beside unresolved security fears for long.

Supplier and counterparty risk

Telega's business depended on suppliers whose roles were not all visible to ordinary users. The RIPE aut-num object listed import/export relationships with AS47764 and AS49281. Public BGP sources identify those as LLC VK and M100 LLC. The product also referenced proxy servers, content-delivery work, payment by bank card, app-store distribution, security-vendor reviews, support bots and store listings. Each is a counterparty or technical dependency.

The VK question matters economically even if ownership allegations are contested. A dependency on VK-linked systems can be commercially rational. VK operates large Russian internet infrastructure and communications products. Using commercially available SDKs, analytics or network services could reduce build time. But for a third-party Telegram client, the same dependency can damage trust because users may fear that a domestic platform is positioned between them and Telegram. Telega's public denial of being a VK product did not eliminate that perception risk.

M100 is also informative because it appears in RIPE records as a possible routing counterparty. A young app company using a specialised network provider is not unusual. The risk is that the company has limited control over transit quality, route availability and public routing interpretation. Users do not care which AS failed; they care whether messages and media work. When the whole proposition is stable access, supplier trouble becomes product trouble.

App stores are the most powerful suppliers. They control discovery, installation, updates, device warnings and account status. Telega's Apple complaint shows how little bargaining power a young app has when a major platform applies a harsh action. Even if a regulator later agrees that the platform acted unfairly, the customer damage happens immediately. A company with a direct web service can keep selling. A mobile client can lose a major platform overnight.

Security classifiers and certificate providers form another gate. CNews and other outlets reported Cloudflare and GlobalSign-related events, with later reporting or Telega statements saying some classifications were removed after explanation. That sequence shows how a communications product can face cascading risk: a domain is classified, a certificate issue appears, app-store trust changes, media coverage grows, users leave, and support burden rises. Even if each step is reversible, the combined effect can exhaust a small company's operating window.

Payment and refund handling are also suppliers. Telega Plus asked users to pay and provide an email or phone number for receipts. Closure then required automatic refunds and user warnings about fraud. That is a modest operation for a stable subscription business. It is a heavy one when the company is simultaneously closing, disputing platform decisions and managing account-security fears.

Substitutes cap the price

The company could not price Telega Plus as if it owned the destination. The destination was Telegram. Users had alternatives: official Telegram when accessible, built-in proxy settings, VPN services, other third-party clients, mobile network changes, desktop clients, web access, or simply waiting. Telega's advantage was convenience. Convenience is valuable, but it is hard to defend if trust weakens or if access conditions change.

The official Telegram client is the harshest substitute. It owns the brand, the protocol direction, the user relationship and the default trust position. Telega could make access easier in a constrained environment, but it could not credibly claim to be more canonical than Telegram. When Telegram labels unofficial-client users or when media report security concerns, the substitute becomes not just available but safer in users' minds.

VPNs and user-managed proxies are less convenient but more flexible. A technical user can configure alternatives across many apps, not just Telegram. A nontechnical user may prefer Telega because it hides complexity. That gives Telega a market among ordinary users, but it also means the company must maintain simple onboarding. A waitlist, subscription bot, store removal, security warnings and closure notices all damage that simplicity.

Other Telegram clients are partial substitutes. Some have long histories, open communities or niche features. They may not solve the same Russian access problem, but they remind users that Telega did not have monopoly rights over the client idea. Telega's features such as the Wall feed, call options, parental controls and creator support needed to be good enough to keep users after access urgency faded.

Russian messaging products and social platforms are broader substitutes. Store recommendation surfaces around RuStore showed domestic alternatives. These products do not preserve Telegram chats, so they are weaker substitutes for immediate continuity. But for regulators and platforms, they may be preferred domestic options. If policy pressure favours a different domestic messenger, Telega's role as a Telegram bridge becomes politically and commercially awkward.

Substitutes also limited creator monetization. Channel owners want reach. They will use Telega if it helps maintain Telegram audiences. They will not move economics to Telega if the product itself is at risk. Creator tools depend on long-lived audience access. A product that closes within weeks of a subscription launch cannot persuade creators to build a serious channel-revenue layer around it.

Unofficial signals show the tolerance limit

Unofficial signals should be read carefully. Store reviews, forum posts, technical reports and media summaries are not audited measurements. They are still economically useful because they show what users and observers believed. In a trust-heavy communications app, belief affects adoption almost as quickly as formal facts.

Positive signals were substantial. Google Play displayed 10 million-plus downloads in the crawled listing and a large review base. RuStore showed tens of thousands of ratings and a 4.5 score, even while the app was no longer available for download in that view. The official site claimed more than five million users and displayed favourable store-review excerpts. The official Telegram channel snapshot showed millions of subscribers. These signals show real market attention.

The negative signals were also severe. Media reported App Store removal, iOS warnings, Telegram labels for unofficial clients, security classifications and technical concerns. Some technical critics alleged that Telega inserted itself between the client and Telegram servers in a way that could compromise confidentiality. Telega's official pages disputed the strongest conclusions and presented its own security explanation. Again, the commercial point does not require a court-like finding. Once users see credible-looking claims that a communications app may not be safe, the burden of proof shifts to the app.

The comments and reviews around closure also show user backlash over payments. RuStore review snippets around late June included complaints about paid subscriptions and closure. The official refund page tried to address this by saying refunds were automatic and warning users not to follow scam messages. That is good conduct, but it confirms the risk of charging during an unstable period. A paid queue can look fair while the product is alive. It can look exploitative if closure follows quickly.

The route shutdown signal is unusually neat. RIPEstat last saw 130.49.152.0/24 on 30 June 2026, and Telega announced closure from 1 July. This is not a full operational post-mortem. It is still a strong alignment between public routing evidence and the company narrative. The observable network footprint did not grow into a durable carrier asset. It appeared for the service period and then went dark in public routing.

The unofficial signal to watch after closure would be reuse. If AS203502 or the /24 reappears under a different product, then Telega's network assets may still have value. If not, the network resource was a tool for one product's operating window. Either way, the asset was not sufficient to carry the business once the consumer trust and platform layers failed.

The judgement

Telega created economic value as an emergency convenience product, but the public record does not support a durable standalone business. The company had a real user problem to solve, real app distribution, real software development, real network-resource evidence and a plausible subscription lever. Its weakness was not absence of demand. Its weakness was control.

Telega did not control the destination network effect. Telegram did. It did not control iOS distribution. Apple did. It did not control how security services, media and users interpreted its proxy architecture. It could respond, but it could not force trust. It did not control all upstream and service dependencies. It could contract for capacity, but not remove counterparty perception. It did not control the regulatory boundary of operating as a Telegram client in Russia. Its closure statement says that boundary became untenable.

The strongest version of Telega's model would have been a paid reliability layer for Russian Telegram users: free basic access for scale, Telega Plus for priority entry and stability, creator tools for channel economics, proxy and content-delivery capacity for performance, and transparent security documentation to preserve trust. If the product had kept iOS distribution, converted a moderate share of urgent users, contained support cost and shown recurring revenue above infrastructure spend, it could have become a profitable bridge product.

The actual record points the other way. Public 2025 financials show heavy loss and negligible revenue before the subscription test. The network footprint was small and later inactive. Calls were cut because high complexity did not match low usage. Paid access launched in May, refund terms followed in June, and closure started in July. App Store removal and security controversy hit the product's weakest point: user trust. These are not small operating issues. They are core business failures for a third-party communications client.

The judgement is therefore negative on durability and mixed on execution. Telega appears to have identified a real gap faster than larger incumbents served it. It attracted attention and built something users tried at scale. But it tried to monetize reliability without owning enough of the reliability stack. A 99-ruble subscription can fund servers. It cannot buy immunity from platform removal, security suspicion, official-client warnings or compliance constraints.

The route evidence reinforces the judgement. AS203502 and 130.49.152.0/24 show Telega had a measurable internet footprint, but the footprint was narrow, recent and short-lived. It helped prove that the company operated more than a marketing site. It did not prove an ISP business with defensible customer economics. The asset was a support layer for a software product. When the product closed, the route vanished from current public visibility.

For investors, suppliers or policymakers, the lesson is simple. Infrastructure evidence must be matched with economic control. Telega had addresses, routing, app listings and users. It lacked stable control over distribution, trust and the underlying communications graph. Those are the assets that determine pricing power. Without them, infrastructure becomes a cost centre attached to someone else's platform.

What would change the view

The first favourable fact would be audited 2026 subscription data showing that Telega Plus converted a meaningful share of users before closure and that refunds were small relative to gross billings. That would not reverse the closure, but it would prove willingness to pay. The second would be cost data showing that proxy and media-delivery costs per active user were low enough for a 99-ruble price to carry healthy contribution margin.

The third favourable fact would be independent technical verification that Telega's proxy architecture preserved confidentiality in the way the company described, with no undisclosed access to message content and clear limits on metadata handling. The fourth would be evidence of stable post-closure reuse of Telega's network assets for another product with a clearer legal and platform boundary. The fifth would be a final regulatory or platform outcome confirming that App Store removal was erroneous and that reinstatement would have been possible on workable terms.

Facts that would worsen the view are easier to name. If final 2026 filings show large losses, refunds and no durable revenue, Telega becomes a costly growth experiment. If technical allegations are later confirmed in their strongest form, trust risk becomes a product design failure rather than a perception problem. If suppliers or platform partners had unpriced termination rights, the business was even more fragile than public records suggest. If the AS and /24 remain inactive, the network-resource layer was a disposable operating tool rather than an asset.

The most realistic conclusion, using only public evidence, is that Telega proved a market pain point but not a business. It showed that Russian users wanted a simpler route to Telegram under unstable access conditions. It showed that a small team could produce a widely noticed client and briefly attach payment to urgency. It also showed that a communications intermediary cannot survive on convenience alone when the trust, platform and compliance boundary breaks. The economics were visible. They were not defensible enough.

Sources