Telegram's core t.me links went dark worldwide today, then came back a few hours later

[StringTheory97]

Every Telegram link on the internet stopped working, with no warning

Telegram's t.me short link domain, the address behind every channel invite, bot link, and shared profile, was placed on serverHold status by the .me registry on July 13, dropping it from the global domain name system and dead ending every t.me link worldwide. A serverHold is a registry level suspension, meaning it does not matter how healthy Telegram's own servers are, browsers everywhere simply lose the ability to translate t.me into an actual address

Founder Pavel Durov appeared to learn about it in real time, posting on X asking the registry directly, hey domainME, t.me links stopped working, can you look into it. Domain records showed the registration was paid up through 2035, ruling out a simple lapse, and the outage did not affect the Telegram app itself, existing chats, channels and calls kept working normally, this was purely a browser facing link problem

The likely cause, and the resolution

Speculation initially ranged from a legal dispute to a policy fight to plain administrative error, with some pointing to Durov's ongoing legal situation in France, where he was reportedly questioned by investigators for a fourth time just last week. By the time the domain came back online a few hours later, the registry operator DomainME confirmed the real reason directly to TechCrunch, the domain had been placed on hold due to OFAC compliance, a reference to the US Treasury's sanctions enforcement arm, and it was restored once that was resolved

Why this mattered beyond mild annoyance

The .me top level domain is Montenegro's country code extension, and it is used well beyond Telegram, PayPal, WordPress, and Meta's own family of apps all lean on .me shortlinks too, so a registry level suspension is a different kind of failure than a normal outage, it sits above the level any individual company can fix on their own. For a platform with roughly a billion monthly active users that leans on t.me links for onboarding, trading bot coordination, and crypto project announcements, even a few hours of broken links was enough to ripple through crypto community coordination specifically, since Telegram is effectively crypto's default town square

TechCrunchtechcrunch.com

Cybernewscybernews.com

[DarkAvenger45]

A registry level hold instead of a normal server outage is such a different failure mode, no amount of Telegram's own engineering effort could have fixed this on their end

[alwaysRock40]

The OFAC compliance explanation makes way more sense than the wild speculation about Durov's French legal case, glad DomainME actually gave a real answer instead of staying silent

[Dave]

PayPal, WordPress and Meta's apps also relying on .me shortlinks is the detail that makes this feel like a bigger structural risk than just a Telegram problem specifically

[Peter]

Durov finding out about his own platform's core infrastructure being cut with zero advance notice is a wild way to run something this critical, no heads up at all

[Matt_81]

The core app staying fully functional while only the browser facing links broke is a good reminder how layered internet infrastructure actually is, one small piece failing doesn't take down everything

[Amber Drifter]

Crypto's reliance on Telegram as the default coordination hub really shows here, a few hours of broken links rippling through trading groups and project announcements

[Forge40]

Good example of how fast a plausible sounding rumor spreads before the actual boring bureaucratic explanation catches up with it

[Amber84]

That is one of those outages that sounds small until you realize how much depends on it.

t.me is basically the front door to a huge chunk of Telegram's ecosystem.

Take that away and suddenly everything feels broken even if the service itself is still running.

[HiggsField]

Feels like a classic single point of failure situation.

All roads lead through one short link domain, so when it goes down, everything downstream gets hit.

Convenient until it is not

[WaveFunction34]

The crypto angle is wild.

So many trading groups, signals, and project comms rely on Telegram links.

A few hours of downtime probably caused more confusion than most people realize.

Markets do not like uncertainty.

[Hollow85]

There is something slightly ironic about decentralized communities relying on a very centralized link system.

One domain goes down and the whole coordination layer wobbles.

Not exactly resilient design.

[Mike40]

Reminds me of when DNS issues take down half the internet.

The underlying services are fine, but the pathways to reach them disappear.

Feels similar here, just on a smaller scale.

[Murky Courier]

People underestimate how important link infrastructure is.

Short links, redirects, and domains are invisible until they fail.

Then suddenly everything depends on them

[WWFGareth98]

A backup system for links would probably help.

Even something simple like alternative domains or fallback routing.

Not perfect, but better than a total blackout.

[ModelCoreWhale]

There is also a user behavior aspect.

Everyone shares t.me links by default without thinking about redundancy.

No one keeps direct handles or alternative contact methods.

Convenience wins until it breaks.

[Harbour17]

Bots and automation must have taken a hit too.

Anything relying on those links for onboarding or triggers would just fail.

That ripple effect is easy to overlook.

[Quasar Ruby]

Some groups probably had to scramble to communicate via other platforms.

Discord, Twitter, even email lists suddenly looking useful again.

Crisis reveals backup plans pretty quickly.

[MiniElliot]

There is a lesson here about over-centralization.

Even in systems that feel distributed, key components can become choke points.

Those are the parts that need the most resilience.