‼️BREAKING: Telegram’s core t[.]me domain has been placed on serverHold at the .me registry, a registry-level status that drops it from DNS worldwide and dead-ends every t[.]me link.
Domain records show the change happened today, with no public explanation yet from Telegram, the .me registry, or backend operator Identity Digital.
I tried posting about it on !technology@lemmy.world, but a mod apparently deleted it. We probably need a “network” community, if the technology community guys don’t like it.
Thanks regarding the domain information. That was actually the next thing I was going to ask about, whether there was also a long-form domain.
DownDetector shows a spike in reports starting about three hours ago as of this writing (so about 7:00 PM UTC July 13).
Can’t resolve t.me, either via my ISP’s DNS server or 1.1.1.1 (CloudFlare) or 8.8.8.8 (Google).
A search turns up:
https://x.com/IntCyberDigest/status/2076768143092166801
Fuck! I was wondering why they were down, and this seems suspicious that it’s not just an accident.
For now you can still get some content by going to the url and replacing “t” with “telegram”. For example here’s exilnova using that changed url:
https://telegram.me/s/exilenova_plus
I tried posting about it on !technology@lemmy.world, but a mod apparently deleted it. We probably need a “network” community, if the technology community guys don’t like it.
Thanks regarding the domain information. That was actually the next thing I was going to ask about, whether there was also a long-form domain.
DownDetector shows a spike in reports starting about three hours ago as of this writing (so about 7:00 PM UTC July 13).
https://downdetector.com/status/telegram/
EDIT: Not a human mod, but an automod script. No idea what tripped it.
EDIT2: Both A (IPv4) and AAAA (IPv6) DNS queries fail (returning NXDOMAIN, which is “domain does not exist” in DNS parlance).
EDIT3: Looks like it’s been changed back and is working now.