Announcement

Collapse

Forum Rules

  • No flaming or derogatory remarks, directly or through insinuation.
  • No discussion, sharing or referencing illegal software such as hacks, keygen, cracks and pirated software.
  • No offensive contents, including but not limited to, racism, gore or pornography.
  • No excessive spam/meme, i.e. copious one liners in a short period of time, typing with all caps or posting meme responses (text/image).
  • No trolling, including but not limited to, flame incitation, user provocation or false information distribution.
  • No link spamming or signature advertisements for content not specific to Dota 2.
  • No Dota 2 key requests, sell, trade etc.
  • You may not create multiple accounts for any purpose, including ban evasion, unless expressly permitted by a moderator.

  • Please search before posting. One thread per issue. Do not create another thread if there is an existing one already.
  • Before posting anything, make sure you check out all sticky threads (e.g., this). Do not create new threads about closed ones.
  • It is extremely important that you post in correct forum section.

  • Balance discussion only in Misc.
  • All art related (such as hero model) feedbacks go to Art Feedback Forum.
  • All matchmaking feedback should go here: Matchmaking Feedback
  • All report/low priority issues should go here: Commend/Report/Ban Feedback
  • No specific workshop item feedback. These should go to workshop page of that item.
  • When posting in non-bugs section (such as this), use [Bugs], [Discussion] or [Suggestion] prefix in your thread name.



In case you object some action by a moderator, please contact him directly through PM and explain your concerns politely. If you are still unable to resolve the issue, contact an administrator. Do not drag these issues in public.



All rules are meant to augment common sense, please use them when not conflicted with aforementioned policies.
See more
See less

Russia and North Europe Server Support

Collapse
This is a sticky topic.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • We played a ranked Game.

    Suddenly all of us got a DC. We were not able to rejoin.


    In the past 2 days, this happened 4 times!

    Comment


    • Packet loss 10-20% in EU server.


      Console log:
      Code:
            client  146.66.156.182:27049[0]:  high packet loss detected flow incoming:    0ms latency,    43/  305 dropped (14.1%)
            client  146.66.156.182:27049[0]:  high packet loss detected flow incoming:    0ms latency,    40/  307 dropped (13.0%)
            client  146.66.156.182:27049[0]:  high packet loss detected flow incoming:    0ms latency,    37/  300 dropped (12.3%)
            client  146.66.156.182:27049[0]:  high packet loss detected flow incoming:    0ms latency,    51/  303 dropped (16.8%)
            client  146.66.156.182:27049[0]:  high packet loss detected flow incoming:    0ms latency,    36/  307 dropped (11.7%)
            client  146.66.156.182:27049[0]:  high packet loss detected flow incoming:    0ms latency,    43/  304 dropped (14.1%)
            client  146.66.156.182:27049[0]:  high packet loss detected flow incoming:    0ms latency,    49/  302 dropped (16.2%)
            client  146.66.156.182:27049[0]:  high packet loss detected flow incoming:    0ms latency,    63/  308 dropped (20.5%)
            client  146.66.156.182:27049[0]:  high packet loss detected flow incoming:    0ms latency,    51/  305 dropped (16.7%)
      C:Gamerules: entering state 'DOTA_GAMERULES_STATE_GAME_IN_PROGRESS'
            client  146.66.156.182:27049[0]:  high packet loss detected flow incoming:    0ms latency,    42/  289 dropped (14.5%)
            client  146.66.156.182:27049[0]:  high packet loss detected flow incoming:    0ms latency,    35/  300 dropped (11.7%)
      Tracert Stockholm server:
      Code:
      Трассировка маршрута к sto.valve.net [146.66.156.1]
      с максимальным числом прыжков 30:
      
        1    <1 мс    <1 мс    <1 мс  192.168.1.1 [192.168.1.1]
        2     3 ms     1 ms     2 ms  gw.pppoe.spdop.ru [158.255.160.1]
        3     5 ms     2 ms     3 ms  10.254.242.25 [10.254.242.25]
        4     7 ms     7 ms     7 ms  ss-cr04-be12.51.msk.stream-internet.net [212.188.1.5]
        5     8 ms     7 ms     7 ms  a197-cr04-be5.77.msk.stream-internet.net [195.34.59.106]
        6    16 ms    17 ms    16 ms  oct-cr03-be1.78.spb.stream-internet.net [212.188.2.37]
        7    27 ms    28 ms    29 ms  bro-cr01-be5.78.stk.stream-internet.net [212.188.2.93]
        8    36 ms     *       37 ms  netnod-ix-ge-a-sth-1500.valvesoftware.com [194.68.123.224]
        9    36 ms    36 ms    35 ms  146.66.156.1
      Tracert Stockholm 2:
      Code:
      C:\Users\Денис>tracert 185.25.180.1
      
      Трассировка маршрута к 185.25.180.1 с максимальным числом прыжков 30
      
        1    <1 мс    <1 мс    <1 мс  192.168.1.1 [192.168.1.1]
        2     3 ms     3 ms     2 ms  gw.pppoe.spdop.ru [158.255.160.1]
        3     7 ms     7 ms     7 ms  10.254.242.25 [10.254.242.25]
        4     2 ms     3 ms     3 ms  ss-cr04-be12.51.msk.stream-internet.net [212.188.1.5]
        5     7 ms     6 ms     7 ms  a197-cr04-be5.77.msk.stream-internet.net [195.34.59.106]
        6    15 ms    16 ms    16 ms  oct-cr03-be1.78.spb.stream-internet.net [212.188.2.37]
        7    28 ms    27 ms    28 ms  bro-cr01-be5.78.stk.stream-internet.net [212.188.2.93]
        8    37 ms    37 ms    37 ms  netnod-ix-ge-b-sth-1500.valvesoftware.com [194.68.128.224]
        9    80 ms    89 ms     *     185.25.180.1
       10    63 ms    70 ms    60 ms  185.25.180.1
      VALVE PLS FIX THIS.
      Attached Files
      Last edited by eRison; 09-26-2015, 12:09 PM.

      Comment


      • When I search game in Russia or play custom game with dedicated server in Stockholm, I can't connect to server, it simply don't want to respond me. All's well for my friends. I've checked dota2.ru forum, lots of people gets the same problem. The most funniest part is all other servers are OK, so now me and lots of russians have to search games in EU, instead of Russia.

        // When I'm trying to connect, I'm getting this
        CL: Sending connect to 146.66.156.73:27060 // (or any other RU server IP)
        CL: Sending connect to 146.66.156.73:27060
        CL: Sending connect to 146.66.156.73:27060
        CL: Sending connect to 146.66.156.73:27060
        CL: Sending connect to 146.66.156.73:27060
        CL: Sending connect to 146.66.156.73:27060
        CL: Sending connect to 146.66.156.73:27060
        CL: Sending connect to 146.66.156.73:27060
        CL: Sending connect to 146.66.156.73:27060
        // Then I'm getting error that after several attemps to connect server didn't respond
        ty for broken reborn and broken servers valve

        Comment


        • After taking the game, I get the boot screen, then throws to the main menu with the words, I could not connect to the server. Although I have a good Internet.

          Comment


          • CL: Sending connect to =[A:1:2717355011:6205]
            Attempt to send to proxied gameserver =[A:1:2717355011:6205] via steam datagram, but we don't have an authorization ticket!

            After that i lost MMR and got LP... Thats not awesome...
            I really dont see the sense of playing if i can get in the same situation and lose more time.
            Dota 2 Content

            Comment


            • Valve Team, please pay attention to thread http://dev.dota2.com/showthread.php?t=185832. We badly need your comments and/or clarifications
              Dota has become totally unplayable because of this problem - "Receiving uncompressed update from server"

              You are well aware of the problem I believe since you have already fixed it several times, for example in September 2014

              Dota 2 Workshop Tools Alpha Update

              Product Update - Valve

              18 сен, 2014

              Fixed shutdown crash
              Fixed crash when loading and combining wearable items that had no model
              Fixed crash in IsValidTeamPlayer
              Fixed crash on connection after "CL: Receiving uncompressed update from server" message
              Fixed missing particle systems in Asset Browser
              Updated Multi-Team Example addon to make team assignment more robust
              Last edited by Palych; 12-25-2015, 05:10 AM.

              Comment


              • Microsoft Windows [Version 6.1.7601]
                (c) Корпорация Майкрософт (Microsoft Corp.), 2009. Все права защищены.

                C:\Windows\System32>tracert sto.valve.net

                Трассировка маршрута к sto.valve.net [146.66.156.2]
                с максимальным числом прыжков 30:

                1 <1 мс <1 мс <1 мс D-link.HomeGateway [192.168.1.1]
                2 9 ms 17 ms 136 ms ppp78-36-98-1.pppoe.komi.dslavangard.ru [78.36.9
                8.1]
                3 14 ms 13 ms 13 ms xe-1-1-0-10g.MX960-2-SYKT.nwtelecom.ru [212.48.1
                95.146]
                4 14 ms 13 ms 14 ms 188.254.78.152
                5 68 ms 69 ms 60 ms 87.226.133.25
                6 62 ms 61 ms 61 ms 162-254-198-244.valve.net [162.254.198.244]
                7 * * * Превышен интервал ожидания для запроса.
                8 70 ms 69 ms 69 ms sto.valve.net [146.66.156.2]

                Трассировка завершена.

                C:\Windows\System32>ping sto.valve.net -t

                Обмен пакетами с sto.valve.net [146.66.156.2] с 32 байтами данных:
                Ответ от 146.66.156.2: число байт=32 время=61мс TTL=57
                Превышен интервал ожидания для запроса.
                Ответ от 146.66.156.2: число байт=32 время=62мс TTL=57
                Ответ от 146.66.156.2: число байт=32 время=61мс TTL=57
                Ответ от 146.66.156.2: число байт=32 время=60мс TTL=57
                Превышен интервал ожидания для запроса.
                Ответ от 146.66.156.2: число байт=32 время=68мс TTL=57
                Ответ от 146.66.156.2: число байт=32 время=61мс TTL=57
                Ответ от 146.66.156.2: число байт=32 время=63мс TTL=57
                Превышен интервал ожидания для запроса.
                Ответ от 146.66.156.2: число байт=32 время=68мс TTL=57
                Ответ от 146.66.156.2: число байт=32 время=61мс TTL=57
                Ответ от 146.66.156.2: число байт=32 время=68мс TTL=57
                Ответ от 146.66.156.2: число байт=32 время=60мс TTL=57
                Ответ от 146.66.156.2: число байт=32 время=68мс TTL=57
                Ответ от 146.66.156.2: число байт=32 время=62мс TTL=57
                Ответ от 146.66.156.2: число байт=32 время=68мс TTL=57
                Превышен интервал ожидания для запроса.
                Ответ от 146.66.156.2: число байт=32 время=61мс TTL=57
                Ответ от 146.66.156.2: число байт=32 время=63мс TTL=57
                Ответ от 146.66.156.2: число байт=32 время=68мс TTL=57
                Ответ от 146.66.156.2: число байт=32 время=61мс TTL=57
                Превышен интервал ожидания для запроса.
                Ответ от 146.66.156.2: число байт=32 время=69мс TTL=57
                Ответ от 146.66.156.2: число байт=32 время=62мс TTL=57
                Превышен интервал ожидания для запроса.
                Ответ от 146.66.156.2: число байт=32 время=68мс TTL=57
                Ответ от 146.66.156.2: число байт=32 время=69мс TTL=57
                Ответ от 146.66.156.2: число байт=32 время=61мс TTL=57
                Ответ от 146.66.156.2: число байт=32 время=61мс TTL=57
                Ответ от 146.66.156.2: число байт=32 время=62мс TTL=57
                Превышен интервал ожидания для запроса.
                Ответ от 146.66.156.2: число байт=32 время=68мс TTL=57
                Ответ от 146.66.156.2: число байт=32 время=68мс TTL=57
                Ответ от 146.66.156.2: число байт=32 время=68мс TTL=57
                Ответ от 146.66.156.2: число байт=32 время=68мс TTL=57
                Ответ от 146.66.156.2: число байт=32 время=61мс TTL=57
                Ответ от 146.66.156.2: число байт=32 время=69мс TTL=57
                Ответ от 146.66.156.2: число байт=32 время=69мс TTL=57
                Ответ от 146.66.156.2: число байт=32 время=66мс TTL=57

                Статистика Ping для 146.66.156.2:
                Пакетов: отправлено = 40, получено = 33, потеряно = 7
                (17% потерь)
                Приблизительное время приема-передачи в мс:
                Минимальное = 60мсек, Максимальное = 69 мсек, Среднее = 64 мсек
                Control-C
                ^C


                17% packetloss eu west/russian server
                rostelekom

                last 2 days

                Comment


                • 2 days 20-30% packet losses. fix this!

                  Comment


                  • Same thing here.

                    >tracert 146.66.156.71

                    Tracing route to 146.66.156.71
                    over a maximum of 30 hops:

                    1 1 ms 1 ms 1 ms RT-G32.lo [192.168.0.1]
                    2 3 ms 3 ms 3 ms 192.168.65.201
                    3 5 ms 5 ms 5 ms 81.177.114.26
                    4 22 ms 34 ms 22 ms 179-126-126-017.xd-dynamic.algartelecom.com.br [
                    179.126.126.17]
                    5 25 ms 24 ms 23 ms 179-126-126-016.xd-dynamic.algartelecom.com.br [
                    179.126.126.16]
                    6 24 ms 24 ms 26 ms 81.177.115.252
                    7 85 ms 67 ms 70 ms 87.226.133.133
                    8 68 ms 70 ms 85 ms 162-254-198-244.valve.net [162.254.198.244]
                    9 * * * Request timed out.
                    10 * 102 ms 88 ms 192.168.180.35
                    11 71 ms 82 ms 72 ms 146.66.156.71
                    Last edited by Kirimechan; 12-27-2015, 06:38 AM.

                    Comment


                    • I'm having the same packet loss issues.

                      Looking at the readouts as it happens, I'm getting 60fps, 36 ping and 0% packet loss which is all fine.

                      I'm also failing to connect when trying to watch live games over the past week or so. It occasionally works if I restart steam and dota, if not it just says failed to connect after several attempts. I'm also getting the packet loss when watching live games too.

                      It's currently impossible to play the game online as a result. Right click once, it freezes, jumps forward, then you're dead.
                      Last edited by laughsofgreed; 01-03-2016, 08:12 AM.

                      Comment


                      • Got some freezes while playing in ranked/unranked. In lobby there are no freezes. don't have packet losses. Vsync is on. Tried with Vsync off, didn't help. What's the problem?

                        Comment


                        • Originally posted by xeewie View Post
                          Got some freezes while playing in ranked/unranked. In lobby there are no freezes. don't have packet losses. Vsync is on. Tried with Vsync off, didn't help. What's the problem?
                          hm, tested in lobby with stockholm server, got 2% packet loss. but using tracert in cmd shows no losses.

                          Comment


                          • У меня такая проблема. Дота начала безбожно лагать и глючить и в то время как я пытался исправить ошибки мне защитали выход из игры! И не смотря на то что я вернулся в игру и полноценно играл дальше когда я поборол зависания и даже моя команда победила мне не засчитали победу в испытании всех героев. Прошу засчитать мне мою игру, а выходы из игры считать только тем кто намеренно стоит афк и ливает из игры, а не повторно запускает игру и решает технические проблемы с игрой!

                            Comment


                            • I've had consistently bad ping on EU west since around late December. It doesn't fluctuate due to time of day and always stays around 140-150ms. EU East and Russia are both always <50ms.

                              Tracing route to 146.66.158.1 over a maximum of 30 hops

                              1 1 ms <1 ms <1 ms 192.168.2.1
                              2 15 ms 9 ms 8 ms cpc3-donc12-2-0-gw.17-1.cable.virginm.net [92.238.208.1]
                              3 9 ms 9 ms 8 ms brad-core-2a-ae7-621.network.virginmedia.net [81.97.82.117]
                              4 * * * Request timed out.
                              5 13 ms 15 ms 17 ms manc-bb-1c-ae2-0.network.virginmedia.net [62.254.42.114]
                              6 27 ms 23 ms 21 ms ae0.man11.ip4.gtt.net [77.67.65.141]
                              7 29 ms 27 ms 27 ms xe-9-2-0.fra61.ip4.gtt.net [141.136.111.254]
                              8 30 ms 28 ms 34 ms valve-gw.ip4.gtt.net [46.33.91.178]
                              9 * * * Request timed out.
                              10 161 ms 150 ms 188 ms 146.66.158.1

                              Comment


                              • Trace complete.

                                >tracert 146.66.158.1

                                Tracing route to 146.66.158.1 over a maximum of 30 hops

                                1 1 ms 1 ms 1 ms 192.168.0.1
                                2 * * * Request timed out.
                                3 8 ms 9 ms 8 ms 89-75-20-222.infra.chello.pl [89.75.20.222]
                                4 40 ms 38 ms 41 ms pl-krk01a-rd3-ae24-1455.aorta.net [84.116.192.10
                                2]
                                5 57 ms 50 ms 52 ms 84.116.193.26
                                6 38 ms 39 ms 39 ms pl-ktw01a-rd4-ae0-2190.aorta.net [84.116.253.98]

                                7 95 ms 36 ms 34 ms pl-waw26b-rc1-ae11-1412.aorta.net [84.116.253.18
                                5]
                                8 40 ms 40 ms 39 ms de-fra04a-rc1-ae22-0.aorta.net [84.116.137.17]
                                9 46 ms 43 ms 42 ms 84.116.140.190
                                10 35 ms 34 ms 35 ms 213.46.177.46
                                11 * * * Request timed out.
                                12 44 ms 54 ms 54 ms 146.66.158.1

                                Trace complete.

                                Random spicked of packet loss/ping on every EU/Russian server

                                Comment

                                Working...
                                X