TSPU Filtering Disrupts Timeweb Cloud Servers: Diagnosis, CDN Failures, and Reverse Proxy Bypass
Russian hosting provider Timeweb Cloud began experiencing selective TSPU filtering in early June that prevented clients from accessing WordPress sites without a VPN. Two commercial sites hosted on the same VPS stopped opening for users in the same city and later for the administrator connecting over a wired connection.
Initial troubleshooting ruled out fail2ban, Google Captcha, registry blocks by Roskomnadzor, and judicial decisions. Competitors on other providers remained accessible, pointing to a provider-specific issue. The observed behavior showed TCP connections on port 443 establishing successfully, followed by a missing Server Hello and a 20-second timeout, while SSH on port 22 and ICMP traffic continued without loss.
The filtering proved dynamic: it initially blocked by SNI at night, later switched to IP-based blocking by midday, and intermittently relaxed in the evening. Timeweb support acknowledged the problem on June 5 in ticket 12068181, attributing it to changes in TSPU settings and noting that the issue varied by operator, region, and browser. Similar reports appeared from Beget and Selectel around the same period.
Obtaining new IP addresses proved ineffective, with filtered behavior recurring on fresh addresses. DNS record updates after IP changes also caused extended outages. Attempts to place Yandex Cloud CDN in front of the origin succeeded for static content but failed for any POST requests, returning 405 errors for wp-login.php, cart operations, and AJAX calls.
A stable workaround used a minimal nginx reverse proxy on a separate Russian cloud VPS. The configuration correctly forwards the Host header and SSL server name, supports all HTTP methods, and includes tuned proxy buffers to prevent 502 errors on large cookie responses from logged-in WordPress administrators. ACME challenge paths are explicitly proxied to allow Let's Encrypt certificate issuance, and a synchronization script copies updated certificates from the origin server.
Testing with curl --resolve allowed validation of both GET and POST functionality before DNS cutover. Additional community suggestions include disabling TLS 1.3 or requesting subnet whitelisting through legal entities, though these were not tested in this case.
Later tickets submitted to Timeweb in July received requests for mtr traces, which cannot detect selective DPI interference because the mechanism allows TCP establishment before dropping TLS packets. Support closed the tickets claiming resolution despite ongoing symptoms reported by clients.
Related articles
Data Masking: 8 Critical Questions Businesses and Developers Ask About Protecting Sensitive Data
Garda expert Dmitry Larin addresses common challenges in data masking during a recent webinar titled 'Data Masking: Battle of Opinions'. The discussion covers why masking remains essential even when encryption is deployed, how to preserve application functionality after anonymization, and the performance trade-offs of processing large databases such as 5 TB PostgreSQL instances. Different masking types including static, dynamic, selective, and streaming are explained with specific use cases for DevOps pipelines, external contractors, and BI systems. The article also examines why machine learning alone is insufficient for discovering personal data and why custom scripts fail at scale across heterogeneous environments like PostgreSQL and Oracle. Practical recommendations include combining masking with encryption, using deterministic transformations for deduplication, and separating replication from masking tasks to avoid production impact.
MAX Desktop Client Tested for VPN Detection on Windows, No Tracking Signs Found
A Habra user named Slava_B conducted an experiment on September 8, 2026, to determine whether the MAX desktop client on Windows could detect or route traffic through a VPN configured at the router level. The setup used a Keenetic router that directed Russian resources directly while sending other connections via an OpenConnect tunnel to a European VPS, with no VPN client or virtual adapter present in Windows itself. Monitoring tools including Process Monitor, Wireshark, TCPView, and tcpdump revealed that MAX.exe and MAX-service.exe processes communicate locally and connect to MAX/ONEME infrastructure along with AppTracer services. The application repeatedly accessed MachineGuid, computer name, proxy settings, device IDs, and microphone/camera information, though these reads may support diagnostics and anti-fraud functions. No connections appeared on the VPN interface, and the client did not attempt to reach IP-checking services, Telegram, or WhatsApp. The researcher noted that TLS traffic was not decrypted, so actual transmission of identifiers could not be confirmed, and results apply only to this router-based configuration.
PII-Guard: Open-Source Detector for Personal Data in Russian Text
Andrey Ivanov, an NLP researcher at red_mad_robot, has released PII-Guard, an open-source system that detects and masks personal data in Russian text before it reaches language models. The tool combines rule-based checks with a fine-tuned ruBert-base NER model to handle names, addresses, phones, passports, INN, SNILS, bank cards and other entities. It replaces detected PII with structured XML-like tags that preserve grammatical information such as gender and entity ID, allowing models to generate coherent responses that are later restored with real values. The hybrid pipeline first applies normalization, pattern matching, Luhn and weighted checksum validation, and context windows with positive and negative keywords, then merges results with model predictions via an arbitration module. Evaluation on four public datasets, including Hivetrace, alexen2 and alrosait, shows PII-Guard outperforming other open solutions on both strict span matching and type-overlap micro-F1 metrics. The project, including datasets and code, is available on GitHub and aims to reduce leakage risks while maintaining downstream model utility.
Google to Add Explicit Content Warnings in Android System Photo Picker
Google is preparing a new safety feature for the system photo picker in Android that will scan images and videos for explicit or nude content. The tool is designed to warn users before they share intimate photographs, whether accidentally or due to a momentary lapse in judgment. This functionality will operate at the system level, meaning it applies across multiple apps that use the built-in photo selector. The feature aims to reduce the risk of unintended distribution of private images that could lead to embarrassment or privacy violations. By integrating the check directly into Android, Google seeks to provide a consistent layer of protection without requiring third-party applications to implement similar logic themselves.