Telegram Loses Global Short Links as t.me Domain Disabled Worldwide by .me Registry
On July 13, internet users around the world noticed that Telegram short links using the t.me format had stopped opening in web browsers. The problem was first highlighted by the Russian publication Kode Durova.
Despite the disruption, the messenger itself continues to operate normally. Both the desktop version and mobile applications remain fully accessible, and t.me links continue to work when opened inside the Telegram app. The only affected functionality is external access through regular web browsers.
Technical Cause of the Outage
According to preliminary data, the t.me domain was effectively excluded from the DNS system at the registry level of the .me top-level domain. This domain zone belongs to Montenegro, and its operator is the company doMEn, selected by the local authorities.
Why the registry decided to disable the domain remains unclear. Among the possible reasons are a legal dispute, a compliance check, requests from government agencies, or a violation of the domain zone’s registration rules. No official statements have been issued at the time of publication.
Registration Status
Importantly, the domain remains officially registered to Telegram until 2035. This means the registration period has not expired, and the situation cannot be explained by simple administrative oversight or failure to renew the domain.
The resulting outage has created an unusual situation: Telegram services continue to function, channels and chats work without interruption, yet the familiar short links opened from a browser lead nowhere.
Until the cause is clarified and the domain is restored in the global DNS, users are advised to open t.me links directly through the Telegram application or wait for the technical issue to be resolved.
Related articles
How to Complete the Roskomnadzor Personal Data Notification Form in 2026: Field-by-Field Analysis
The article provides a detailed walkthrough of the current Roskomnadzor notification form for operators processing personal data under Russian law. It explains that the form is an extract from existing internal documents rather than a questionnaire, requiring operators to reference their data processing policy, inventory results, appointment orders, and protection level acts. Key prerequisites include confirming that notification is mandatory after the 2022 amendments removed most exemptions, preparing five core documents, and understanding that the form pulls data directly from those records. The guide covers every section, from operator identification and processing regions to data categories, protection measures, geography, and post-submission obligations. It also addresses common mistakes, the option to save drafts, auto-population features, and liability for non-compliance or inaccurate information. The piece concludes with a checklist mapping each form field to its source document.
OBEP Raids on Russian IT Firms: How to Safeguard Source Code, Servers and Blockchain Assets During Searches
Russian IT companies, Web3 projects and fintech services now face frequent visits from OBEP operatives conducting pre-investigative checks or searches under criminal cases. The article details the legal distinction between operational-search measures and formal searches, emphasizing article 164.1 of the UPK RF that prohibits seizure of physical servers in economic crime investigations. It explains how companies can demand data mirroring instead of hardware removal and how to invoke article 51 of the RF Constitution when pressured for encryption keys. Commercial secret regimes are presented as a tool to raise criminal liability for leaks and to request closed court proceedings. Practical checklists cover document verification, staff instructions, password retention and immediate calls to specialized criminal counsel. The guidance aims to prevent business paralysis while preserving evidence integrity during raids.
RWB Deploys Enterprise-Wide Database Access Control with Trino and Open Policy Agent
RWB has replaced fragmented manual database access processes with a centralized architecture built on Trino as the single entry point and Open Policy Agent for policy enforcement. The system enforces least-privilege access, mandatory auditing, and automated revocation tied to HR records while eliminating anonymous and password-based logins. Access requests now complete in 3–10 minutes instead of an average of four days, with 92 percent handled automatically. Key components include Keycloak for OIDC authentication, Vault for secrets, Kafka for security event streaming to SOC, and Kubernetes orchestration. Responsibility is split across AI & Data Security, Core DevOps, Access Management, SOC, and Trust & Safety teams. More than 1,250 PostgreSQL clusters and 90 projects are now connected, with real-time dashboards tracking adoption and policy health.
Russia Moves to Allow Biometric Data Processing for Suspects and Convicts Without Consent
Russian law enforcement agencies may soon gain the legal right to process biometric data of suspects, accused individuals, and convicted persons without requiring their personal consent. A corresponding draft bill has already been submitted to the government and is scheduled for review at the next cabinet meeting, according to TASS. The measure covers fingerprints, facial images, voice recordings, and other physiological or behavioral characteristics used for identification. If approved, prior permission from the individual will no longer be needed when biometrics are used in criminal proceedings. The change applies not only to those already convicted but also to suspects and accused persons whose guilt has not yet been established by a court. For ordinary citizens, enrollment in the Unified Biometric System remains voluntary and is used for remote identity verification when accessing financial and government services.