Telegram t.me Domain Restored After Registry Suspension Broke Links Worldwide

Telegram’s t.me short-link domain is working again after a registry-level suspension temporarily removed it from the Domain Name System and broke links worldwide. The outage affected links to Telegram profiles, channels, groups, bots, posts and invitations, while the main messaging service continued operating.

The .ME Registry placed t.me under serverHold on July 13, 2026, after the U.S. Treasury sanctioned First VPN Service, also known as 1VPNS. In an official statement about the t.me suspension, the registry said a Telegram channel appeared among infrastructure associated with the sanctioned VPN service.

The registry removed the hold on July 14 after Telegram confirmed that it had removed its links and affiliations with 1VPNS. A current Google Public DNS lookup for t.me returns an IPv4 address, confirming that the domain has returned to DNS.

What Happened to Telegram’s t.me Domain?

Public registration records showed that the domain entered serverHold status at approximately 19:24 UTC on July 13. While that status remained active, DNS resolvers could not obtain the records needed to direct browsers to Telegram’s short-link service.

A serverHold status operates above Telegram’s web servers and DNS hosting configuration. Even if Telegram’s servers and authoritative name servers remain available, the registry can stop the domain from appearing in the parent .me zone.

ICANN’s guide to EPP domain status codes states that serverHold comes from the domain’s registry operator and means the domain is not activated in DNS. Registry status codes take priority over status codes applied by a registrar.

Incident detail	Confirmed information
Affected domain	t.me
Status applied	serverHold
Status level	.ME Registry
Hold applied	July 13, 2026
Domain restored	July 14, 2026
Immediate cause	Registry compliance action connected to sanctioned 1VPNS infrastructure
Core Telegram app	Continued operating
Short links	Temporarily failed outside Telegram

OFAC Sanctions Triggered the Registry Action

On July 13, the U.S. Treasury’s Office of Foreign Assets Control designated First VPN Service, its administrator Dmytro Rashevskyi and malware-obfuscation provider Yegeniy Vladimirovich Silayev. Treasury accused the parties of supplying services that supported ransomware operations.

The official OFAC cyber-related designation listed several identifiers for First VPN Service, including domains, email addresses, cryptocurrency addresses and the Telegram channel t[.]me/FirstVPNService.

The .ME Registry said that the presence of a Telegram channel among the identified infrastructure led it to suspend the t.me domain. Telegram itself was not designated, and OFAC did not sanction the entire messaging platform.

Why One Channel Affected Every t.me Link

A domain registry manages names at the domain level. It cannot use serverHold to disable only a URL path such as t[.]me/FirstVPNService. The status applies to the complete t.me domain.

As a result, a compliance concern involving one channel affected unrelated links hosted under the same domain. Links for ordinary users, news organizations, businesses, public groups, bots and other channels stopped resolving until the registry removed the hold.

Resource	Effect during the hold
User profile links	Failed to resolve through the web
Public channel links	Failed to open through t.me
Group invitation links	Could not resolve through the affected domain
Bot and Mini App links	Web access through t.me was disrupted
Shared message links	External links failed
Telegram messaging	Continued operating through Telegram’s separate infrastructure

Telegram temporarily used alternative domains for some links while t.me remained unavailable. Links handled directly inside Telegram clients also continued to work in some situations because the applications could interpret them without relying on a normal browser lookup.

How serverHold Differs From Other Domain Status Codes

Domain registrars and registries use Extensible Provisioning Protocol status codes to control domain operations. Client codes come from registrars, while server codes come from registries.

GoDaddy remained the registrar for t.me, but it could not independently clear a registry-applied serverHold. The .ME Registry had to remove the status before the domain could return to the parent DNS zone.

The ICANN status-code reference distinguishes serverHold from deletion and transfer restrictions:

• serverHold prevents the registry from publishing the domain in DNS.
• clientHold produces a similar DNS effect but comes from the registrar.
• serverDeleteProhibited prevents registry-level deletion and does not disable DNS by itself.
• clientDeleteProhibited prevents the registrar from deleting the domain.
• transfer and update restrictions protect against unauthorized ownership or configuration changes.

The historical appearance of serverDeleteProhibited and clientDeleteProhibited did not cause the outage. The serverHold flag directly stopped normal DNS resolution.

The Registry Restored t.me After Telegram Responded

On July 14, Telegram told the registry that it had removed the relevant links and affiliations with 1VPNS. The registry reviewed the confirmation and then lifted the suspension.

The .ME Registry statement thanked Telegram for its prompt cooperation. The explanation replaced earlier speculation that the hold might have resulted from a security incident, registration error or unrelated legal dispute.

After the hold was removed, DNS records began returning through recursive resolvers. The latest public DNS response for the Telegram domain shows successful resolution, although some users may briefly encounter stale cached failures after a restoration.

What the Incident Means for Telegram Users

Users do not need to change existing t.me links. Once DNS caches refresh, old profile, group, channel and bot links should work again without editing.

Organizations that depend heavily on Telegram links should still check websites, social profiles, support pages and automated messages for failed redirects. Monitoring can identify locations where the temporary outage caused broken-link errors or interrupted customer journeys.

• Retest important Telegram invitation and support links.
• Clear local DNS caches if links continue to fail.
• Try another network or trusted DNS resolver to rule out stale caching.
• Monitor link availability from more than one geographic region.
• Keep an approved alternative Telegram domain available for emergencies.
• Avoid replacing links with unverified third-party redirect services.

The outage did not indicate a compromise of Telegram accounts, chats or encryption. It affected domain resolution for the t.me link layer rather than Telegram’s primary messaging infrastructure.

Lessons for Organizations That Depend on Short Domains

The incident shows how a short domain can become a single point of failure for a much larger service. One registry status change temporarily disabled millions of otherwise unrelated links.

Organizations should monitor domain registration status as closely as server uptime and certificate expiration. Traditional application monitoring may show healthy servers even when a registry action makes the domain unreachable.

1. Monitor RDAP or registration records for unexpected hold statuses.
2. Alert on missing DNS records and repeated NXDOMAIN responses.
3. Maintain alternative domains for critical links and customer access.
4. Document registrar and registry escalation contacts.
5. Track third parties that publish content under company-controlled domains.
6. Build procedures for legal, sanctions and abuse-related domain incidents.

The July 13 OFAC notice remains in force against 1VPNS and the designated individuals. Restoring t.me did not change those sanctions. It only restored the broader Telegram domain after the identified channel and related affiliations were removed.

FAQ