Power Outage at Major Russian Telecom Node Disrupts Reg.ru Services and Affects Runet Nationwide
A major power outage at a large communication node triggered widespread disruptions across the Russian internet on August 17, affecting services provided by hosting provider and domain registrar Reg.ru.
Users were unable to access the company's main website or log into their personal accounts. The problems quickly spread to numerous other sites that rely on Reg.ru infrastructure, many of which either became completely unavailable or operated intermittently.
Technical analysis of the failures suggests that DNS servers were likely impacted. These servers handle the critical task of converting human-readable domain names into the corresponding network addresses required to reach the actual servers. When this system fails, websites effectively disappear from the internet even if the underlying servers remain operational.
Complaints continued to arrive through monitoring services throughout the day. At the same time, users reported outages affecting banking applications, messengers, social networks, and various other Russian online resources. However, there is still no confirmation that every reported issue was caused by the problems at Reg.ru; multiple independent failures may have occurred simultaneously within the Runet.
At the time of initial reporting, Reg.ru had not disclosed the root cause, full scope, or expected time for complete service restoration.
Update: Company representatives later clarified that the problems were not on Reg.ru's side or within its own infrastructure. The outage resulted from an electricity supply failure at a major communication node, which rendered many resources unavailable regardless of their hosting provider. The company stated it hopes for rapid restoration of the node's functionality.
Related articles
CryptoLab: Interactive Educational Platform Turns Cryptographic Protocols Course into Hands-On Alice, Bob and Mallory Experiments
A university instructor developed CryptoLab, an educational testbed that lets students run live cryptographic protocol experiments with active attackers instead of simple encrypt-decrypt exercises. The platform models the classic Alice-Mallory-Bob scenario where each participant runs as a separate application mode, allowing inspection, modification, dropping, and replay of packets. The first lab focuses on AES-GCM, AEAD properties, nonce reuse, replay protection, weak RNGs, key rotation, and metadata leakage. Students can operate in interactive mode to manually attack traffic or execute automated scenarios that verify expected security outcomes. Experiments demonstrate that modifying ciphertext triggers authentication failure and that a valid authentication tag does not guarantee message freshness without additional replay defenses. The tool also includes Python 3.10 assignments for correctly using cryptographic primitives rather than implementing algorithms from scratch. CryptoLab currently supports Windows x64 and macOS Apple Silicon builds and serves as the foundation for upcoming labs on symmetric encryption modes, asymmetric cryptography, key exchange, and TLS.
From Scanner Overload to Manual Insight: A Bug Bounty Hunter's Journey
A young researcher recounts his transition from automated scanning to thoughtful manual analysis in Bug Bounty programs. After completing a broad information security course covering cryptography, networks, Docker, databases, and OWASP Top 10, he initially approached real-world targets with the same scanner-heavy mindset used in labs. Months of fruitless results led to burnout and a six-month break working in construction. Returning with a new focus, he studied hundreds of public HackerOne reports to understand researcher reasoning and anomaly detection. This shift enabled his first valid, unreported finding and fundamentally changed his methodology. Today the 18-year-old university student balances Bug Bounty with reconnaissance, machine learning, and personal projects while emphasizing deep application understanding over tool volume.
Bypassing Paid Export on AI 3D Generation Sites via Browser Network Inspection
A detailed walkthrough shows how users can retrieve AI-generated 3D models in GLB format from services that normally require a paid subscription for export. The method relies on opening the browser developer console, filtering network requests for .glb files after model generation completes, and opening the intercepted asset in a new tab. Examples using Tripo3D and Hi3D demonstrate that the generated model and textures are already present on the client side even when the export button remains disabled. Additional steps address compatibility issues with 3ds Max by recommending conversion through gltf.report with Draco compression before import. The technique also covers post-processing in ZBrush for auto-retopology and format conversion to OBJ. The article notes that such workarounds exist because many AI platforms limit free exports while still rendering full models locally.
National Platform Max Begins Testing Advertising Tools to Monetize User Attention
The Russian national platform Max has started internal testing of new advertising instruments designed to convert user attention into sellable ad inventory. According to the company's press service, the tests are already underway inside the application, although the exact placement, visual format, and eligibility criteria for advertisers remain undisclosed. The move marks a significant shift for the platform, which previously operated without visible commercial advertising. Observers note that Max could become one of the largest domestic digital advertising channels if the tests prove successful. No timeline has been given for a public rollout or for the publication of detailed advertising policies.