Hello [i]Bungie Team[/i] and [i]Community[/i],
I am writing to bring attention to an ongoing issue that myself and a significant number of players from [b]CIS[/b] countries [i](Russia, Belarus, Kazakhstan, etc.)[/i] have been experiencing for over a week across all platforms [i](PC, Xbox, PSN)[/i]. We are consistently encountering the "[b]Tapir[/b]" error during the initial connection/login phase to Destiny 2 servers.
[b]Our Observations and Analysis:[/b]
1. [b]Workarounds Exist[/b]: The issue can be temporarily bypassed, which is noteworthy:
• [b]On PC[/b]: Using a VPN only during the login phase works. Once authenticated, the VPN can be disconnected, and the game runs perfectly stable without disconnections.
• [b]On Xbox[/b]: Simply changing the DNS servers resolves the problem.
• [b]On PSN[/b]: Changing DNS only works for accounts not registered in Russia. Russian PSN accounts still cannot connect.
2. [b]Diagnostic Evidence[/b] [i](Traceroute)[/i]: We have performed traceroutes to Destiny 2 authentication servers. The trace consistently times out at hops within the Akamai CDN network. This indicates that the connection issue occurs not within our local ISPs or countries, but specifically when reaching the game's infrastructure. Below is a typical example.
[spoiler]Tracing route to [One of the Destiny 2 authentication servers] over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms [My Router]
2 3 ms 4 ms 4 ms [Provider's Network]
3 2 ms 2 ms 2 ms [Provider's Network]
4 3 ms 2 ms 2 ms mag9-cr03-be12.**********-internet.net [~IP~]
5 3 ms 3 ms * mag9-cr02-be13.**********-internet.net [~IP~]
6 3 ms 2 ms 3 ms a433-cr06-eth-***************-internet.net [~IP~]
7 15 ms 15 ms 15 ms mmon-cr02-eth-**************-internet.net [~IP~]
8 27 ms 24 ms 21 ms radio-cr01-*************-internet.net [~IP~]
9 48 ms 47 ms 47 ms de-cix.fra.[b]akamai[/b].prolexic.com [~IP~]
10 46 ms 46 ms 46 ms po110.bs-a.sech-fra.netarch.[b]akamai[/b].com [~IP~]
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
...
30 * * * Request timed out.
Trace complete.[/spoiler]
3. [b]Key Point[/b]: After successfully logging in (via workarounds), the connection to the game world is completely stable. Furthermore, the Bungie website and Destiny Companion app are accessible without any issues.
[b]Our Main Concern and Reason for This Post:[/b]
Initially, Bungie Support agents acknowledged the increase in "Tapir" reports and stated they were investigating. However, recently, the responses have become a standard copy-paste message: "[b]Destiny services are not available where access is restricted by law.[/b]".
This response has left us confused and seeking clarification:
• [b]Which specific law is being referred to?[/b] We are not aware of any laws in our respective countries that restrict access to Destiny 2. The fact that the connection works flawlessly once a VPN or DNS workaround is applied strongly suggests that the block is not originating from a legislative measure on our end.
• [b]Why are multiple CIS countries affected?[/b] If this were a targeted restriction against one specific country, why are players from other, neutral CIS nations like Belarus and Kazakhstan experiencing the exact same problem?
[b]Our Request:[/b] We kindly ask the Bungie team to provide a more detailed comment on this situation. If this is a technical issue (e.g., an unintended block at the Akamai level), we are ready to provide any additional diagnostic data to assist in resolving it. If this is a deliberate policy change, we would appreciate a clear and official statement.
Thank you for your time and attention to this matter. We sincerely hope for a constructive response.
↓ Russian Translation / Перевод на русский ↓
[spoiler]Здравствуйте, команда и сообщество Bungie,
Пишу, чтобы обратить внимание на проблему, с которой я и значительное число игроков из стран СНГ (Россия, Беларусь, Казахстан и др.) сталкиваемся уже более недели на всех платформах. Мы постоянно получаем ошибку "Tapir" на этапе подключения к серверам авторизации Destiny 2.
Наблюдения и анализ:
1. Существуют обходные пути:
• На PC: Использование VPN только на этапе входа работает. После авторизации VPN можно отключить, и игра работает стабильно.
• На Xbox: Проблема решается простой сменой DNS.
• На PSN: Смена DNS работает только для аккаунтов не из России.
2. Диагностика (Трассировка): Трассировка до серверов авторизации стабильно обрывается на узлах сети Akamai CDN, что указывает на проблему на стороне инфраструктуры игры. Пример под спойлером выше.
3. Ключевой момент: После входа в игру подключение стабильно. Сайт и мобильное приложение Bungie также работают нормально.
Главная причина обращения:
Изначально поддержка сообщала об изучении проблемы, но теперь ответы стали шаблонными: "Сервисы Destiny недоступны там, где доступ ограничен законом.".
Этот ответ вызывает вопросы:
• О каком именно законе речь? Нам не известны законы в наших странах, ограничивающие доступ к Destiny 2. Работоспособность обходных путей говорит об обратном.
• Почему проблема затрагивает разные страны СНГ?
Наша просьба: Мы просим дать более развернутый комментарий. Если это техническая неполадка, мы готовы помочь с диагностикой. Если это политика, мы ждем четкого официального разъяснения.
Спасибо за внимание. Искренне надеемся на конструктивный ответ.[/spoiler]
-
Responding as a concerned player. Traceroute shows path your connection takes. The last point of connection could be the cause of the issue. A simple “whois” on the IP on last jump shows the router’s owner/operator details. There are other networking tools a general user can use to further root cause. As stated a VPN will work around this gatekeeper. Certain countries have rules and for some reason black listed the Bungie servers or originating servers. As much as I want to blame Bungie, any stance they take will be met with worse treatment by just naming the law or country blocking them.