Telegram Experiences Outage in Kazakhstan as International Peering Points Show Traffic Drop
Users across Kazakhstan encountered significant difficulties accessing Telegram, with complaints officially acknowledged by the Ministry of Artificial Intelligence and Digital Development. The exact cause of the disruption remains undetermined as specialists continue investigating where the messenger lost connectivity.
Traffic monitoring showed a sudden reduction in Telegram data flows at key international peering locations in Frankfurt and Moscow. The same pattern was observed by Kazakhtelecom, the country's primary telecommunications provider.
Within Kazakhtelecom's own network, however, everything remained stable. The company detected no accidents, technical failures, or other issues in its area of responsibility, and services continued in normal mode.
The drop in availability at international nodes suggests the problem lies outside Kazakhtelecom's infrastructure, although definitive conclusions cannot yet be drawn. The operator has submitted a request to Telegram's technical team and awaits official explanations.
Details on the outage's full scope, impacted regions of Kazakhstan, and timelines for complete service restoration are still unavailable. Authorities and the operator have pledged to release further information once Telegram responds.
For context, it was also reported today that a database purportedly holding personal information of 15 million residents of Kazakhstan — roughly three-quarters of the population — has been put up for sale on a shadow forum.
Related articles
Google Testing Optional Google Account Unlock for Forgotten Android PINs
Google is developing a backup unlock method that lets Android users regain access to their devices through a linked Google Account instead of performing a full factory reset. The feature, discovered in Android 17 QPR2 Beta 5, appears under the name Unlock with Google Account and would be disabled by default. Users would need to enable it manually in the Device unlock settings before forgetting their PIN, password, or pattern. The change aims to prevent permanent loss of local data such as photos and documents that lack cloud backups. The mechanism revives a capability removed after Android 4.4, when forgotten patterns could be cleared using Google Account credentials. Factory Reset Protection would remain in place after any reset. The code reference is not yet functional, carries no official announcement, and may be altered or dropped before release.
Implementing 2FA Kubernetes Access via Gateway API, Dex and MULTIDIRECTORY
A Russian cybersecurity company replaced static kubeconfig files with corporate accounts and mandatory 2FA for its Talos Linux Kubernetes clusters. The solution routes all authentication through a single FQDN using NGINX Gateway Fabric, Dex as an OIDC provider connected to MULTIDIRECTORY via LDAP, and kube-oidc-proxy for token validation and impersonation. Groups stored in the directory are passed directly into RBAC bindings, eliminating manual certificate management. A lightweight Python service dynamically generates kubeconfig files that contain no secrets. The team documented several Gateway API migration pitfalls including namespace route restrictions and BackendTLSPolicy hostname validation. The approach keeps the entire configuration in Git and avoids modifying kube-apiserver flags.
Windows File System Tunneling Preserves Old File Metadata for Legacy Compatibility
Microsoft has clarified that Windows sometimes assigns creation dates from deleted files to new ones due to a long-standing mechanism called File System Tunneling. The feature keeps metadata in a short-term cache for about 15 seconds after a file is deleted or renamed. If a new file with the same name is created quickly in the same folder, it inherits the previous file's timestamps and short-to-long name mappings. This behavior exists to support safe saving patterns used by many applications and to maintain compatibility with old DOS-era 8.3 filename formats. The actual file content is never restored, only the metadata. The cache is temporary and clears over time, so the effect does not occur with files deleted long ago. The explanation came after users noticed unexpected dates in Windows Explorer and questioned whether it was a bug.
Amazon Confirms Irrecoverable Data Loss in UAE and Bahrain Data Centers After Drone Attacks
Amazon Web Services has officially confirmed that data stored in specific availability zones within its Middle East regions was permanently destroyed following physical attacks on data centers in the UAE and Bahrain. The incidents began on March 1 and continued through April and July, damaging infrastructure tied to AI development projects. In the UAE region mec1, only zone mec1-az2 was completely destroyed with no external backups, while mec1-az3 suffered severe damage and mec1-az1 remained operational but overloaded. All three zones in the Bahrain region me-south-1 were rendered inoperable. AWS had spent six months attempting recovery before issuing the final statement on September 15, 2026, and has advised customers to migrate workloads to unaffected regions. The event highlights growing risks to data from physical-world attacks beyond traditional network threats.