Telegram's short-link domain t.me has been suspended, disrupting the messaging platform's URL shortening service. The suspension raises questions about accessibility and service continuity for millions of users.
Telegram's t.me domain, used for creating shortened links to messages and channels, has been suspended. The domain registrar action affects users relying on the service to share content across platforms.
The suspension comes as Telegram faces increasing regulatory scrutiny worldwide. Recent months have seen pressure from multiple governments over the platform's encryption and moderation policies.
Users can still access Telegram through its primary domain and mobile apps, but the t.me shortener—a convenient tool for sharing links on social media and messaging platforms—is currently unavailable.
The exact reason for the suspension remains unclear. It could stem from registrar policy enforcement, regulatory intervention, or technical issues. Telegram has not issued an official statement regarding the suspension.
This incident highlights the vulnerability of alternative domains and services that depend on third-party registrars and infrastructure. The messaging app's reliance on t.me for link sharing means widespread disruption across its ecosystem until the domain is restored or an alternative is deployed.
The U.S. Cybersecurity and Infrastructure Security Agency has issued a mandate requiring all federal agencies to patch an actively exploited remote code execution vulnerability in Citrix NetScaler appliances by Saturday.
A new Rowhammer attack called GPUThor can bypass error-correcting code (ECC) protections on NVIDIA GPUs, enabling denial-of-service attacks and root-level privilege escalation.
The FBI has dismantled proxy tools used by Chinese hackers in a widespread campaign against NASA, the Federal Reserve, the US Senate, and the Justice Department. The operation marks a significant coordinated response to months of intrusions into critical US infrastructure.
Snowflake is phasing out password authentication for legacy service accounts, requiring organizations to adopt passwordless methods. The real challenge: identifying which accounts exist, who manages them, and what access they hold.