Looking at two network traces of connection/login process with psn accs of russian and non-russian origin we can identify several significant differences that may explain the authentication issue(TAPIR) with ru psn acc: 1. The most notable difference is communication pattern of stun servers usage: 1. Ru acc fails: - attempts connections to multiple stun servers in sequence [REDACTED] and [REDACTED]- these resolve to ip addresses like [REDACTED], [REDACTED], [REDACTED], [REDACTED], [REDACTED], etc.; - shows persistent udp traffic on xbox live ports to these stun servers. 2. Non-ru acc suceedd: - much less stun server activity; - fewer dns lookups for stun servers; - less persistent udp communication patterns. 2. Different psn endpoints. Both traces show connections to ps5.np.playstation.net, but the resolved endpoints differ: - ru acc resolves to [REDACTED], [REDACTED]; - non-ru acc resolves to [REDACTED], [REDACTED], [REDACTED], etc. This suggests different cdn endpoints or regional routing. 3. Connection termination patterns: - ru acc shows more abrupt connection terminations with tcp rst packets, particularly in psn connections. - non-ru acc shows more graceful connection closures with proper fin/ack sequences. [b]I.E. [/b] The extensive stun server communication in the ru acc trace suggests the game/system is having difficulty establishing proper nat traversal for peer-to-peer connections. This could indicate: 1. Geolocation-based restrictions - the system may be detecting the ru account origin and applying different network policies. 2. Regional server availability - ru acc might be routed to different potentially restricted servers. 3. Enhanced nat traversal requirements. Additional networking steps may be required for ru acc due to regulatory or technical restrictions. 4. The different psn endpoints suggest regional cdn routing which could be part of geo restrictions affecting ru acc. [b]IN TOTUM[/b] The issue is highly likely related to regional network policies or server routing rather than a simple technical problem, which would explain why the same network setup works for non-ru acc but fails for rus one. So far imo it's more sony rather than bungie. But I'll be glad to be wrong and still hope that this is an unintentional random issue that will be fixed as soon as possible. [spoiler]Moderation Action: IP addresses Redacted for Privacy/Security Concerns[/spoiler]