
Within the Tracking & Anti-Detect software segment, the most operationally relevant update during the last 24–48h was the release of Multilogin 12.17. The update adds Facebook-based account registration and delivers a set of infrastructure-level fixes affecting cloud phone operation, profile management, authentication workflows, and proxy-related session stability. While the release does not introduce a new fingerprint engine, it modifies several components directly used by affiliate teams, media buyers, and account operators managing large browser-profile fleets. Source: [https://multilogin.com/release-notes/]
The headline addition is native Facebook sign-up support for Multilogin accounts. From an operations perspective, this reduces dependency on standalone credential management during initial environment provisioning. More importantly for active teams, the release addresses multiple issues affecting cloud phone infrastructure. According to the vendor's release notes, stopped cloud phones and failed launches should no longer consume usage minutes, duplicate billing scenarios have been mitigated, and consecutive launch or restart operations have been stabilized. Source: [https://multilogin.com/release-notes/]
The operational significance lies less in the Facebook registration feature and more in the session-management corrections. Cloud phone resources are increasingly used for mobile-only traffic sources, app promotion flows, and account warm-up operations. Earlier launch failures or inconsistent auto-stop behavior could distort operational costs and create uncertainty during large-scale account management.
Source: [https://multilogin.com/release-notes/]
Discussion across affiliate and anti-detect communities during the release window focused primarily on operational reliability rather than evasion capabilities. The strongest positive signal was the correction of cloud phone minute accounting, which directly affects teams running persistent mobile environments. No widespread reports of fingerprint regressions, major browser-detection anomalies, or traffic-source compatibility issues were identified immediately following the rollout. At the time of writing, no confirmed delivery-impact anomalies connected to the update have been broadly documented in public affiliate communities.
Teams using Multilogin cloud phones should validate billing metrics, verify automated launch workflows, review session restart automation, and confirm that existing authentication procedures remain compatible with the revised account-access logic. Operators leveraging long-running mobile environments may benefit most from the cloud phone accounting corrections, while agencies managing shared workspaces should review the updated 2FA and profile-transfer handling behavior.
Although not a major fingerprinting release, Multilogin 12.17 is a meaningful infrastructure-maintenance update. The practical impact is concentrated around session reliability, cloud phone cost control, and account lifecycle management. For media-buying teams running high-volume account operations, the release reduces friction in environment provisioning and addresses several issues that previously had direct operational cost implications. Root causes behind the corrected cloud phone behaviors were not publicly disclosed by the vendor. Source: [https://multilogin.com/release-notes/]