Home Internet Tariffs in Russia Rise Up to 20% in First Half of 2026 Amid Rising Costs and Surging Demand
Tariffs on home internet in Russia have risen noticeably faster than in previous periods. In the first half of 2026, prices increased by an average of 8-10%, with some estimates reaching up to 20% depending on the region and provider. For comparison, the full-year growth in 2025 was limited to just 5-7%.
Large operators have also adjusted their pricing. Rostelecom raised selected tariffs by approximately 50-60 rubles, while ER-Telecom increased prices by around 100 rubles. In certain cases, archived plans have become more expensive, and fees for connection services that were previously offered free of charge have been introduced.
According to reports from Izvestia, the main reasons include rising costs of equipment and electricity, higher wages, increased rental expenses for infrastructure, and greater spending on network modernization. An additional factor was the spring season of mobile internet restrictions, which caused many users to switch to fixed home Wi-Fi, resulting in significantly higher traffic volumes that providers had to accommodate.
The era when fixed broadband could be offered at nearly the same price for years has ended. While basic tariffs once cost 400-500 rubles per month, current prices in some cities are noticeably higher. Smaller regional operators still offer plans in the 400-600 ruble range for those seeking more affordable options.
The Ministry of Digital Development and the Federal Antimonopoly Service have stated they are monitoring the justification for these price increases and are prepared to conduct inspections if necessary. Market participants, however, caution that tariffs could rise by another 12-15% in the second half of the year if infrastructure access costs continue to grow.
A more moderate forecast suggests that growth may slow because most potential customers have already connected to broadband services. Nevertheless, the overall trend is clear: home internet pricing is no longer static, and this change is increasingly visible in monthly bills.
Related articles
Why HTTP to HTTPS Redirects Fall Short: Risks of Exposed Requests and the Role of HSTS Preload
A simple HTTP to HTTPS redirect satisfies basic audit requirements but leaves the initial request fully exposed in plaintext. The request carries the full path, query parameters, and cookies lacking the Secure flag, allowing observers on open Wi-Fi or compromised routers to read or tamper with traffic before TLS begins. Modern browsers such as Chrome since version 90 attempt HTTPS first, yet legacy clients, explicit http:// links in emails, scripts, and failed HTTPS fallbacks continue to send unprotected requests. HSTS instructs browsers to use HTTPS after the first successful visit, yet the header itself travels over HTTPS and cannot protect the very first connection from a new device or cleared cache. Preloading embeds the rule directly in the browser, eliminating the initial plaintext request entirely, but demands includeSubDomains and a one-year max-age, making the change effectively irreversible for months. The article recommends verifying Secure flags on all cookies, ensuring single-step redirects to the same host, and testing HSTS incrementally before considering preload.
OSINT for the Lazy Part 18: Extracting Value from Wayback Machine Archives for Bug Bounty and Security Research
The article explores passive reconnaissance techniques using web archive tools to uncover forgotten endpoints, configuration files, and sensitive parameters without directly interacting with target systems. It highlights three command-line utilities—waybackurls, gau, and waymore—that query public archives such as Wayback Machine, Common Crawl, AlienVault OTX, and URLScan to retrieve historical URLs. These tools help bug bounty hunters and penetration testers discover old API endpoints, admin panels, backup files, and JavaScript with hardcoded secrets that may still be exploitable. Installation instructions, usage examples, and filtering options are provided for each tool to maximize efficiency and reduce noise in results. The piece emphasizes that all methods remain fully passive, minimizing detection risk while requiring proper authorization before any active testing. Advanced users are advised to combine the tools for broader coverage and deeper analysis of archived responses.
OSINT Investigation Exposes Fraudulent Russian Garlic Investment Scheme Masquerading as Local Production
An in-depth OSINT probe into a Russian agricultural investment project promising 50-70% annual returns from garlic farming has revealed a likely import arbitrage operation sourcing produce from China and Uzbekistan. The project claimed ownership of over 300 hectares of fields, a proprietary seed fund, and guaranteed sales to major retailers including Magnit, Perekrestok, Pyaterochka, and Svetofor, yet public records show minimal profitability and heavy debt. Financial statements from linked cooperatives indicated just 2.2% net margin alongside loans exceeding annual revenue fourfold, pointing to reliance on continuous new investor capital. Registry checks confirmed no financial licenses, no seed-breeding status, and actual cultivated land far below advertised figures. Import declarations and equipment registrations further indicated the operation functions as a repackaging hub for foreign garlic sold under private labels. The parent group has been placed on the Bank of Russia blacklist, with related sites blocked by Roskomnadzor while Telegram channels continue aggressive marketing.
Deploying Self-Hosted Hysteria 2 Proxy on Debian-Based Linux VPS via Terminal
A detailed guide explains how to set up a personal Hysteria 2 proxy server on a KVM VPS running Debian or Ubuntu without any web panels. The process begins with generating ed25519 SSH keys, hardening the sshd_config file, and restricting access with ufw to only TCP port 22 and UDP port 443. Hysteria 2 is downloaded from GitHub, made executable, and configured using a TOML file that enables salamander obfuscation and a self-signed TLS certificate. A custom systemd unit ensures the service restarts on failure. The client configuration includes SHA256 pinning of the server certificate to prevent MITM attacks. The guide emphasizes manual CLI operations that apply equally to other services such as Nginx and stresses checking local laws before deployment.