If you searched for t.me domain down this morning, you are not alone. On July 13, 2026, Telegram's main short-link domain stopped resolving in browsers worldwide. Invite links, channel URLs, and bot deep links that start with t.me simply returned errors — even though the Telegram app itself kept working fine.
For agencies running Meta ads into Telegram, that is not a minor inconvenience. It is a hard stop on the funnel. If your ad creative, landing page, or bio still points at a bare t.me link, users hit a dead tab instead of your channel. Spend keeps running. Joins do not.
Ott customers did not hit that wall. Their ads still pointed at Ott tracking links on their own domain — and those links kept delivering users into Telegram while attribution and Meta conversion events continued. Here is what broke, who it affects, and why dynamic links behave differently from static ones.
The .me domain registry placed t.me on a DNS hold, which removed it from global name resolution. In plain terms: browsers could no longer find t.me at all. Profile links, channel invites, and shared short URLs built on that domain stopped working on the web. The Telegram mobile app was unaffected — this was a link-layer outage, not an app outage. Domain watchers reported the change on July 13.
Who is affected by the t.me outage
Anything that still sends traffic directly to t.me is broken until the registry lifts the hold or you replace the link. That includes more than just old bookmarks.
- Meta ad destination URLs pasted as t.me/channel or t.me/+invite
- Instagram, X, and link-in-bio tools pointing at a Telegram channel URL
- Email signatures and QR codes encoded with a static t.me address
- Pinned posts and old campaign assets you have not opened since the outage started
Telegram founder Pavel Durov publicly asked the registry for clarity. As of this writing, there is no official explanation for the suspension. If you depend on Telegram for acquisition, waiting it out with static links is a gamble on spend you are already paying for.
Why Ott tracking links never went offline
Ott does not ask you to put t.me in your ads. You run traffic to a tracking URL on your own domain — for example yourbrand.com/t/signals. That link is yours. It does not disappear when a third-party short domain has DNS trouble.
When someone clicks, Ott captures the Meta click ID, creates a fresh Telegram invite for that visit, and sends the user into your channel. Joins still match back to the ad. Conversions still flow to Meta. The outage hit the last hop — the Telegram short domain — not the tracking layer agencies actually control.
Static t.me links vs Ott tracking links
The difference is not subtle once a domain-level failure happens.
| Static t.me link | Ott tracking link | |
|---|---|---|
| Breaks when t.me DNS fails | ✓ | ✗ |
| Requires manual link swap in every ad | ✓ | ✗ |
| Captures fbclid from Meta ads | ✗ | ✓ |
| Sends join conversions back to Meta | ✗ | ✓ |
| You control the URL in creatives | ✗ | ✓ |
How Ott links work in three steps
No webhooks to babysit in your ad setup — the flow is straightforward for media buyers:
- 1
User clicks your Meta ad
The destination is your Ott tracking URL, not a bare Telegram short link. Meta attaches the click ID your reporting depends on.
- 2
Ott records the visit
Ott stores the attribution data and prepares a one-time Telegram invite for that specific click — so joins can be matched to the right ad later.
- 3
User lands in your channel
Ott redirects into Telegram. During the outage, Ott automatically routed those final redirects through telegram.me instead of t.me, so users still reached the channel without you changing a single creative.
When t.me stopped resolving, Ott switched the final redirect to telegram.me platform-wide — in under two hours. Your ads, slugs, and dashboards stayed the same. Attribution data stayed intact. Clients did not need to re-edit campaigns or replace URLs in Business Manager. That is the point of owning the tracking layer instead of hard-coding someone else's short domain into paid traffic.
What to do if your Telegram links are broken right now
If you are still sending paid traffic to a static t.me URL, you have two practical options today:
Quick fix: replace the link with telegram.me where you control the destination — same path, different hostname. You will still need to update every live ad, bio, and asset by hand, and you will not recover click-level attribution unless you already had a tracking layer in front of Telegram.
Durable fix: move acquisition to Ott Telegram tracking links so your creatives always point at URLs you control, invites are generated per visit, and the platform can route around the next domain surprise without a fire drill. For the full setup picture, see our Telegram conversion tracking guide and bot troubleshooting checklist.
Related reading
Compare approaches in our roundup of Telegram ad tracking tools, or talk to us if you need to migrate live campaigns off static invite links before the next outage.