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
Building a Minimal Open Source Security Stack for Infrastructure Protection
The article outlines a practical approach to assembling a basic cybersecurity stack using open source tools for organizations with limited budgets. It covers endpoint protection with ClamAV, network perimeter defense via pfSense including Snort and Suricata integration, centralized logging with ELK Stack or Wazuh, and identity management through Keycloak. The guide emphasizes that these solutions provide foundational capabilities but require careful configuration, regular updates, and community validation to avoid risks from unmaintained projects. Detailed installation steps, rule configuration examples, and integration advice are provided for each component. The author stresses that open source options serve as an entry point rather than a full replacement for commercial platforms like Kaspersky or Symantec.
Russian Researchers Achieve First Qubit Operations on Planar Ion Traps
Scientists from Rosatom’s Quantum project have for the first time in Russia performed qubit operations using planar ion traps. The technology replaces traditional three-dimensional electromagnetic traps with flat electrode chips that can hold more than 100 ions while integrating optical readout components. Two independent teams demonstrated the approach: one at the Physical Institute of RAS led by Ilya Semerikov using ytterbium-171 ions, and another at the Quantum Center under Kirill Lakhmansky using calcium ions. Both groups successfully captured, moved, and performed single-qubit gates on the trapped ions. Rosatom views the planar architecture as a key step toward scalable industrial ion-trap quantum computers capable of solving practical problems. The teams now aim to advance from individual operations to high-fidelity, multi-zone systems with over 100 controllable qubits by 2030.
OSINT for the Lazy Part 17: Versatile Framework Acts as Swiss Army Knife for Investigators
The article continues the series on tools for lazy OSINT practitioners by reviewing a multifunctional online toolkit hosted at htdark.com. This minimalistic yet powerful platform aggregates data across usernames, email addresses, phone numbers, IP addresses, cryptocurrency, social networks, and media files. It wraps Censys search capabilities into a more convenient interface while adding features such as JSON report export and basic relationship graphing. The tool checks 20 social platforms including Reddit and Spotify but omits Chinese and Russian resources, marking absent accounts in red and requiring manual verification for others. An Advanced section functions as a dork builder supporting Baidu and Naver with time-range filters and exclusion operators. While no single toolkit replaces specialized solutions, this framework provides broad initial visibility and helps analysts choose focused follow-up directions based on accumulated data rather than random checks.
AS2 in .NET Without Separate Java Gateway: Native EDI Exchange Directly in Application Routes
redb.Route.AS2 introduces native AS2 protocol support for .NET applications, eliminating the need for separate commercial gateways or Java-based servers like OpenAS2. The library integrates AS2 handling as a standard step in Apache Camel-style routes, allowing signed and encrypted S/MIME exchanges with partners such as Walmart directly within a single .NET process. It supports both synchronous and asynchronous MDN receipts for non-repudiation, using MimeKit and Bouncy Castle for cryptography. Developers can configure partners via As2ConnectionFactory objects that define certificates, AS2 identifiers, algorithms, and MDN modes. The solution handles X12 and EDIFACT documents with compression, signing, and encryption while exposing metadata like MIC values and signature validation results to the routing pipeline. This approach consolidates deployment, observability, and processing compared to external gateways or JVM processes.