Telegram’s primary short-link domain stopped resolving globally after the .ME registry placed t.me under serverHold status, cutting web access to links for channels, groups, bots and user profiles.
The t.me registry record was updated on July 13 with the registry-level restriction. ServerHold removes a domain from the DNS zone, preventing browsers and other services from translating it into the address of Telegram’s servers.
The .ME registry defines serverHold as a status imposed by the registry rather than the registrar. Only the registry can remove the restriction and restore the domain to the DNS zone.
Telegram’s mobile and desktop messaging services continued operating, while telegram.org and the longer telegram.me domain remained accessible. The disruption was concentrated around external t.me links opened through browsers, websites, search engines and social platforms.
Channels And Mini Apps Lose Web Entry Point
Telegram uses t.me as the standard entry point for public channels, private group invitations, usernames and bots. The DNS removal breaks links already embedded across websites, social profiles and crypto project documentation.
Telegram has also become a distribution layer for crypto wallets, trading tools and consumer applications built around The Open Network. Products such as the TON-based Predicton mini app use Telegram links to move users from external pages into bots and onchain services.
Existing users can still open channels, bots and mini apps from inside Telegram. New users following t.me links from outside the application may instead receive a DNS error until the registry restores the domain or projects replace their links.
The suspension is separate from government-level access restrictions such as Russia’s 2026 Telegram block, which targeted local connectivity rather than Telegram’s global domain registration.
Durov Asks .ME Registry To Investigate
Telegram founder Pavel Durov acknowledged the outage after the links had remained unavailable for several hours.
“Hey @domainME, t.me links stopped working,” Durov wrote on X. “Can you look into it?”
Domain.ME and technical registry operator Identity Digital had not disclosed the reason for the hold or provided a restoration timeline as of the latest check on July 14.
