nginx development
All Findings
5 total
All Findings
5 totalintelligence (5)
QUIC/HTTP3 surge Feb-Mar 2020 follows Rambler criminal case resolution by 6 weeks: largest code push in nginx history after legal crisis clears
Rambler criminal charges formally dropped Jan 15, 2020. Six weeks later (Feb-Mar 2020), the Moscow nginx team executed the largest coordinated code push in nginx history: Kandaurov 14->230 commits for 2020 full year; Homutov 62 commits Feb-Mar alone; Arutyunyan 56 in March alone. This was 10 months post-F5 acquisition. The legal cloud from the December 2019 raid was lifted in January 2020, and the Moscow team immediately accelerated. The QUIC protocol timing is also consistent with QUIC RFC maturity (draft-25 published Jan 2020). The 6-week gap between charge dismissal and surge start is within normal project planning cycles. Innocent explanation: F5 product roadmap drove the timing independent of Rambler resolution.
QUIC/HTTP3 surge Feb-Mar 2020 follows Rambler criminal case resolution by 6 weeks: largest code push in nginx history after legal crisis clears
Rambler criminal charges formally dropped Jan 15, 2020. Six weeks later (Feb-Mar 2020), the Moscow nginx team executed the largest coordinated code push in nginx history: Kandaurov 14->230 commits for 2020 full year; Homutov 62 commits Feb-Mar alone; Arutyunyan 56 in March alone. This was 10 months post-F5 acquisition. Innocent explanation: F5 product roadmap drove timing independent of Rambler resolution; QUIC draft-25 published January 2020.
UTC+3/+4 (Moscow-timezone) commits persist 4 years after F5 closes Moscow office: 182 (2023), 103 (2024), 119 (2025)
F5 closed its Moscow R&D office March 15, 2022 following the Ukraine invasion. Despite the office closure, UTC+3/4 timezone commits continued: 182 in 2023, 103 in 2024, 119 in 2025, 35 in 2026 YTD. Only Kandaurov ([email protected], then @f5.com) and Arutyunyan ([email protected]) remain active. These developers appear to be working from Russia despite the office closure. F5 has no corporate presence in Russia post-2022. If accurate, this represents unauthorized or undisclosed Russia-based development of critical global infrastructure software. The silence period comparison: Ermilov and Homutov both stopped by July 2022; Bartenev moved to wbsrv.ru (Angie fork). Kandaurov and Arutyunyan's continued Russia-based work represents an ongoing exposure.
UTC+3/+4 (Moscow-timezone) commits persist 4 years after F5 closes Moscow office: 182 (2023), 103 (2024), 119 (2025)
F5 closed its Moscow R&D office March 15, 2022 following the Ukraine invasion. Despite the office closure, UTC+3/4 timezone commits continued: 182 in 2023, 103 in 2024, 119 in 2025, 35 in 2026 YTD. Only Kandaurov ([email protected], then @f5.com) and Arutyunyan ([email protected]) remain active. If these developers are Russia-based, this represents unauthorized or undisclosed Russia-based development of critical global infrastructure software by a sanctioned-country workforce.
Moscow-timezone development persists post-office-closure: Despite F5 closing Moscow office March 2022, UTC+3/4 commits continued at 182 (2023), 103 (2024), 119 (2025), 35 (2026 YTD). Kandaurov and Arutyunyan remain the only significant active developers with 341 combined TLS commits and 254 connection commits. F5 Western bench remains thin: 14 f5.com contributors total with only 32 commits combined.