If you tried to open a Telegram invite link today and landed on a dead browser tab, you're not alone. Starting July 13, 2026, every link built on Telegram's signature t.me domain — usernames, channels, group invites, shared messages — stopped resolving across the globe, even though the Telegram app itself kept working normally.
What actually happened
The issue isn't with Telegram's own servers. Domain monitoring accounts and WHOIS lookups show that t.me was hit with a serverHold status, a flag applied directly by the domain registry rather than by Telegram or its registrar, GoDaddy. A serverHold pulls a domain out of the global DNS system entirely, so no browser anywhere can translate "t.me" into a working address — regardless of how healthy Telegram's own infrastructure is.
Because t.me sits under Montenegro's country-code domain (.me), the hold was set by the .me registry's operators, not Telegram. The domain's registration itself is valid for years, ruling out something as simple as an expired renewal. Notably, Telegram's backup domain, telegram.me — which sits in the same .me zone — was unaffected, suggesting the action targeted t.me specifically rather than the entire .me zone.
Telegram founder Pavel Durov publicly flagged the outage on X, tagging the .me registry and asking them to look into it. As of this writing, neither Telegram nor the registry (Identity Digital, which runs the .me zone's technical backend) has issued an official explanation. Some reports point to a possible link to U.S. OFAC compliance requirements, though this remains unconfirmed.
What's actually broken (and what isn't)
- Broken: t.me/username links, channel invite links, group invite links, shared message previews — anywhere the short-link domain is used in a browser or on the open web.
- Working: The Telegram app itself. Existing chats, calls, and in-app navigation continue functioning normally, since the app doesn't rely on t.me resolving in a browser.
- Also affected: Telegram's TON-based ecosystem — Wallet, Mini Apps, and collectible usernames — since many of these are accessed via t.me links.
Telegram has reportedly started redirecting new link generation to the telegram.me domain in the meantime.
The takeaway
This is a useful real-world reminder of a structural risk that's easy to overlook: building critical infrastructure on a single third-party-controlled domain. A registry-level action — unrelated to a company's own servers, code, or security — can instantly break how over a billion users share and access content, with no warning and no clear timeline for resolution. Restoration depends entirely on the registry lifting the hold, which industry precedent suggests can take anywhere from hours to several days.
If your own workflows lean on t.me links (invite links in bios, onboarding flows, affiliate campaigns), it's worth having a fallback — like telegram.me or in-app deep links — ready to go until this is resolved.
What this means for teams running multiple Telegram accounts
Outages like this hit hardest for anyone managing Telegram at scale — agencies running client channels, KOL/campaign managers juggling dozens of accounts, or crypto teams coordinating community and Wallet-linked profiles across markets. When a single shared domain goes down, or when a platform flags accounts for looking too similar to each other, the operational risk multiplies with every account added.
This is exactly the kind of scenario MostLogin is built for. As an anti-detect browser purpose-built for social media management, MostLogin gives each Telegram profile its own isolated browser environment — separate fingerprint, cookies, cache, and proxy — so accounts don't get linked or flagged just because they're being run from the same team or device. For teams managing large batches of channels or accounts, batch profile creation, bulk proxy assignment, and centralized team dashboards make it realistic to operate dozens (or hundreds) of accounts without them tripping over each other.
A few ways this connects directly to the current t.me situation:
- Redundancy by design: With isolated profiles and independent proxy routing per account, teams can keep operating across regions even when a shared point of failure — like a domain-level outage — disrupts access for everyone using the default setup.
- Reduced platform risk at scale: Unique digital fingerprints per profile help prevent the kind of cross-account linking that gets multiple accounts flagged together, which matters even more when an outage already has support teams and moderators on edge.
- Team-wide continuity: Role-based profile sharing and activity logs mean any team member can pick up an account without re-establishing trust signals from scratch.
If your team relies on Telegram as a core channel — for community management, KOL campaigns, or crypto/Web3 engagement — it's worth having infrastructure in place that doesn't put all your accounts behind one fragile link. You can see current plans on the MostLogin pricing page or sign up for free to try it out.
This is a developing story; check for updates as the registry or Telegram release more information.
