---
What happened: Two of Russia's big carriers are claiming 5G leadership on the same day. MegaFon says it has switched on 5G in ten cities — Moscow, St. Petersburg, Novosibirsk, Kazan, Krasnodar, Samara, Yekaterinburg, Nizhny Novgorod, Tver, and Veliky Novgorod — with users able to test it on 5G-capable handsets and more cities and tourist sites to follow. MTS counters that it is the first and only operator with gigabit 5G, citing a 4.9 GHz network across five cities including Moscow and St. Petersburg, plus 5G on 2100 MHz LTE frequencies in 16 cities, advertising speeds up to 1.5 Gbps and pitching the buildout as groundwork for cloud, AR/VR, industrial IoT, and autonomous transport.
Why it matters: Both "first" claims can't be true, and neither is independently verified — this is marketing, not measured performance. The 4.9 GHz band gives speed but poor coverage; 2100 MHz gives reach but isn't true standalone 5G. What's actually notable is that Russia is pushing commercial 5G at all under sanctions that have constrained equipment supply. Treat real-world availability and speeds as unconfirmed until third-party testing appears.
What to watch: Independent speed and coverage testing, and whether the two operators' claims converge on a common definition of "5G" — or keep diverging for promotional purposes.
---
What happened: The AI coding platform Cursor stopped working in Russia without notice; users first reported region-based blocks on September 4. The trigger appears to be a new export-control clause in its terms of service referencing US regulations, meaning the service will no longer operate in sanctioned regions. Some users say a foreign IP doesn't restore access, suggesting the service checks connection history or geolocation, not just the current IP.
Why it matters: This is the export-control regime reaching the developer-tool layer. Coding assistants have become core infrastructure for software teams, and losing access mid-project is disruptive in a way a blocked streaming service isn't. The apparent use of connection-history checks also signals a hardening of enforcement — VPN workarounds are getting less reliable, and that pattern is likely to spread to other US AI and dev tools.
What to watch: Whether other AI dev platforms follow with similar clauses, and how Russian developers route around it — domestic alternatives, resold accounts, or relocation of workflows.
---
What happened: Analysts at F6 counted 326 publicly exposed leak incidents involving Russian company clients in 2025 — nearly double the combined total of Latin America, the Middle East, Africa, Asia-Pacific, and the rest of the CIS (164 incidents). Roughly 1.2 billion rows of Russian user data were exposed.
Why it matters: The scale is disproportionate to Russia's population and economy, pointing to systemic security failures rather than bad luck — weak breach disclosure, fragmented infrastructure, and sanctions-driven pressure on security spending. For ordinary users, the practical consequence is that leaked credentials and personal data are abundant and cheap, feeding fraud and account takeover.
What to watch: Whether Russian regulators move from disclosure requirements to actual penalties, and whether the leak rate keeps climbing into 2026.
---
What happened: Micron employees will receive annual bonuses of up to 68 monthly salaries — the largest payouts in company history — on the back of strong memory-chip demand. More than 60,000 people get bonuses; the minimum cash bonus is $53,800 (about 4.5 million rubles), and junior engineers will see roughly $108,000 including stock.
Why it matters: This is a direct readout of the AI-driven memory supercycle. HBM and DRAM demand from data-center buildouts has pushed memory makers from cyclical also-rans to cash machines, and Micron is distributing that windfall to retain talent in a tight semiconductor labor market. The minimum bonus alone exceeds many tech salaries — a signal of how distorted chip-industry compensation has become.
What to watch: Whether the memory boom holds or overshoots — historically these cycles end badly — and whether Samsung and SK Hynix match with comparable payouts.
---
What happened: Apple released documentation for building apps for the iPhone Duo, covering how to adapt interfaces to the device's unconventional proportions, which orientations it supports, and best practices for working with two separate screens.
Why it matters: This is developer documentation for a foldable-style form factor, not a product launch — but it's the clearest signal yet that Apple is preparing its ecosystem for a two-screen device. Getting developers to adapt layouts early is how Apple avoids the app-compatibility mess that has dogged foldables on other platforms.
What to watch: Whether third-party apps actually adopt the two-screen layouts before any hardware ships, and whether Apple pairs the form factor with a software feature that justifies it.
---
What happened: iOS 27 arrives September 14. As with any major OS release, some apps may malfunction or fail to open due to incompatibility. Experts recommend updating essential apps — especially banking apps — to their latest versions beforehand.
Why it matters: Routine, but the banking-app warning is the practical takeaway: financial apps are the most likely to break and the most painful when they do, since they often lag on compatibility updates.
What to watch: Which major apps break in the first 48 hours, and how quickly developers push fixes.
---
Note: No geopolitics or science/medicine items with substantive content in today's sources — omitted rather than padded.
