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
OAuth Authorization Server Built Without Storing User Profiles
The article details the evolution of an OAuth Authorization Server that deliberately avoids storing user profiles, relying instead on external identity providers for authentication. It addresses three core constraints: hundreds of dynamically created isolated APIs, a public SPA client without a BFF, and the inability of resources to query the AS on every request. The design separates concerns so the AS handles only clients, tenants, grants, audiences, scopes, keys, sessions, and token issuance while the Main API owns profiles and roles. Tokens are managed securely inside a Service Worker using a custom FedCM grant, eliminating races across tabs and reducing XSS exposure. The approach minimizes blast radius, simplifies compliance, and keeps the AS replaceable without affecting product domain logic.
Why a 202-Character License Key Uses ECDSA P-256 Instead of Ed25519 or RSA
A developer building offline license verification for a .NET desktop application evaluated Ed25519, RSA, and ECDSA P-256 before selecting the last option. The decision was driven by the requirement for zero external dependencies, keys short enough for manual entry from email, and support for key rotation without breaking existing licenses. Although Ed25519 offers faster verification and a smaller public key, it is absent from System.Security.Cryptography in both .NET 8 and .NET 10, with API approval only targeted for version 11. RSA-2048 produces signatures too long for practical use, resulting in a 571-character Base32 string that users would find cumbersome. ECDSA P-256 with SHA-256 delivers a fixed 64-byte signature that becomes a manageable 202-character key when encoded in Base32, while remaining fully available in the runtime. The article also covers performance measurements, the risks of ECDSA nonce generation, and the deliberate choice of the IEEE P1363 signature format to guarantee fixed-length output.
Pilcrow Publishes Free Comprehensive Guide on Web Authentication
Author Pilcrow has released a detailed, ad-free handbook covering authentication and authorization practices for web applications. The resource draws on personal experience and includes practical examples in JavaScript and Go. It examines password-based methods, email verification, multi-factor authentication, passwordless flows, and passkeys while highlighting associated risks and usability trade-offs. The book also provides in-depth guidance on session management, token security, expiration policies, and email address handling as account identifiers. Recommendations emphasize choosing methods that match application security requirements and user expectations. Additional context is given on OWASP resources and community support channels.
redb 3.4.0 Adds Replay Checkpoints, Shared Runtime Layer and Declarative Secrets Handling for .NET Ecosystem
redb 3.4.0 delivers operational improvements for the .NET integration platform that includes typed storage over Postgres, MSSQL and SQLite, the redb.Route engine modeled after Apache Camel, the Tsak runtime with dashboard and clustering, and redb.Identity for OIDC and OAuth 2.1. The release focuses on post-deployment resilience with replay checkpoints that capture message state at named points inside routes, allowing safe re-execution of downstream steps without duplicating side effects. A shared runtime layer moves framework assemblies into a separate Libs/shared directory so that individual DLLs can be replaced without rebuilding or redeploying the entire Tsak or Identity packages. Secrets are now declared with a [Sensitive] attribute on endpoint options, ensuring URIs containing passwords or keys are sanitized before they reach logs, metrics or health checks. Additional controls include role-based access to management APIs, persistent audit trails and cryptographic signing of dynamically loaded modules. All Pro features remain free on the entire 3.x line with no licensing server required.