Telegram’s t.me Domain Pulled Offline by .me Registry, Blocking TON Wallet Access

Published by James Harris on July 14, 2026July 14, 2026

The t.me domain, the single short-link address underpinning Telegram’s entire messaging and blockchain ecosystem, was placed on serverHold status by the .me registry on July 13, pulling DNS records offline and cutting access to Telegram’s TON-based Wallet, Mini Apps, collectible usernames, NFT gifts, and every other service that routes through that domain. Neither Telegram nor the .me registry had provided an explanation as of the time of reporting.

The disruption is not a hack or a protocol failure. It is a registry-level administrative action, the kind that gets applied for unpaid dues, verification failures, or suspected fraud or security concerns, per ICANN’s own documentation. That distinction matters because it means Telegram has no direct technical remedy available. The fix has to come from Identity Digital, the technical operator of the .me country-code domain, or from the Montenegro-based commercial registry body that holds the relationship with Telegram under a partnership agreement that made t.me the platform’s canonical short-link domain.

One Domain, One Point of Failure

The architecture here is the problem. Telegram built its entire on-chain access layer on top of a single domain it does not control at the registry level. Users reach the custodial Wallet through t.me/wallet, where they can hold USDT, Bitcoin, and Gram. TON-based collectible usernames and phone numbers are tokenized assets accessed via t.me handles. Telegram Gifts convert to TON NFTs. Mini Apps connect to the blockchain via TON Connect, typically launched through t.me links. Every one of those pathways ran through the same address.

This is a meaningful infrastructure risk that the TON ecosystem’s growth narrative has not had to confront before. Gram was trading at $1.59 on Monday with a market cap of approximately $4.33 billion, ranking 21st on CoinMarketCap, and the token’s value proposition rests almost entirely on Telegram’s distribution scale. TON positions itself as a Layer-1 blockchain built with and for Telegram’s user base. That user base is the moat. An outage that severs the primary access point to the on-chain ecosystem, even temporarily, tests exactly how durable that moat actually is.

Why Registry Dependency Is a Structural Vulnerability

Country-code top-level domains carry jurisdiction-specific risk that generic TLDs do not. The .me domain belongs to Montenegro, and while Identity Digital handles technical operations, the commercial relationship sits with a national registry body operating under its own rules. Telegram’s partnership agreement with that registry granted it the short-link domain, but it did not grant Telegram control over the registry’s administrative authority.

Crypto projects have learned painful lessons about single points of failure before, usually at the smart contract or bridge layer. A registry-level hold is a less familiar attack surface, but it is arguably harder to route around quickly. A compromised bridge can be paused by a multisig. A serverHold status requires the registry to act.

What This Accelerates

The immediate question is whether Telegram moves to establish a backup domain to restore access to its crypto services while the hold remains in place. If it does not, every TON-linked product, the Wallet, NFTs, Mini Apps, and tokenized usernames, remains effectively inaccessible to users who rely on the standard entry points.

For the TON ecosystem broadly, the incident surfaces a concentration risk that institutional participants evaluating the network should now factor in. A blockchain that routes mainstream access through a single third-party-controlled domain is not operating with the censorship resistance its Layer-1 label implies. That gap between the decentralization pitch and the actual access architecture will be harder to ignore after Monday.