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

Middle East Server

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

  • SARKEH
    replied
    Getting 400+ ping in Kuwait.
    It's been a while now and there's still no fix for the Kuwaiti players.

    Leave a comment:


  • Shayan66
    replied
    a new iranian player here, Well i have 200 ping to EU servers but 400 on Dubai! Wired!

    My tracert:

    Tracing route to dxb.valve.net [185.25.183.1]
    over a maximum of 30 hops:

    1 1 ms <1 ms 1 ms 192.168.1.1
    2 7 ms 7 ms 7 ms 94-183-196-3.shatel.ir [94.183.196.3]
    3 6 ms 7 ms 7 ms 172.19.132.3
    4 31 ms 37 ms * 172.19.133.13
    5 40 ms 38 ms 36 ms 85-15-0-43.shatel.ir [85.15.0.43]
    6 25 ms 25 ms 24 ms 85-15-0-1.shatel.ir [85.15.0.1]
    7 25 ms 24 ms 26 ms 85-15-0-58.shatel.ir [85.15.0.58]
    8 32 ms 31 ms 32 ms 78.38.255.89
    9 33 ms 39 ms 33 ms 10.10.53.185
    10 28 ms 26 ms 27 ms 10.201.42.117
    11 199 ms 202 ms 201 ms 82.178.159.225
    12 * * * Request timed out.
    13 * * * Request timed out.
    14 210 ms 210 ms 209 ms 94.205.255.33
    15 228 ms 232 ms 240 ms 185.25.183.1

    Trace complete.

    Leave a comment:


  • theserpent
    replied
    Microsoft Windows [Version 6.1.7600]
    Copyright (c) 2009 Microsoft Corporation. All rights reserved.

    C:\Users\Akshay>tracert dxb.valve.net

    Tracing route to dxb.valve.net [185.25.183.1]
    over a maximum of 30 hops:

    1 <1 ms <1 ms <1 ms router.asus.com [192.168.1.1]
    2 35 ms 34 ms 35 ms abts-kk-dynamic-001.216.178.122.airtelbroadband.
    in [122.178.216.1]
    3 38 ms 33 ms 34 ms abts-kk-static-133.32.166.122.airtelbroadband.in
    [122.166.32.133]
    4 33 ms 33 ms 34 ms abts-kk-static-009.32.166.122.airtelbroadband.in
    [122.166.32.9]
    5 34 ms 36 ms 35 ms 122.175.255.29
    6 108 ms 73 ms 72 ms 182.79.245.26
    7 73 ms 73 ms 74 ms p15412.sgw.equinix.com [202.79.197.12]
    8 159 ms 157 ms 158 ms ge-7-1-0.0.ejr03.sin001.flagtel.com [62.216.128.
    245]
    9 164 ms 162 ms 275 ms so-0-1-2.0.pjr01.mmb004.flagtel.com [85.95.25.97
    ]
    10 165 ms 165 ms 163 ms so-0-0-3.0.pjr01.dxb001.flagtel.com [85.95.25.53
    ]
    11 164 ms 165 ms 165 ms xe-0-0-1.0.pjr03.dxb001.flagtel.com [85.95.26.18
    5]
    12 207 ms 207 ms 157 ms ge-0-2-4.0.pjr04.dxb001.flagtel.com [85.95.26.21
    0]
    13 200 ms 208 ms 207 ms 62.216.144.122
    14 * * * Request timed out.
    15 202 ms 201 ms 203 ms 94.205.255.33
    16 218 ms 218 ms 221 ms 185.25.183.1

    Trace complete.

    C:\Users\Akshay>

    Leave a comment:


  • Aphotic
    replied
    please a server for us Iranians .... and we are alot...having so much bad time and bad pings ...please do us this great favor.

    Leave a comment:


  • mzn928
    replied
    tracerroute from iran:
    Code:
    Tracing route to dxb.valve.net [185.25.183.1]
    over a maximum of 30 hops:
    
      1    39 ms    39 ms    39 ms  10.142.70.34
      2    39 ms    42 ms    39 ms  10.142.70.33
      3  2003 ms  2781 ms  2268 ms  10.140.0.81
      4   661 ms   386 ms   327 ms  10.143.255.202
      5   182 ms    40 ms    39 ms  217.219.0.115
      6    46 ms    82 ms   199 ms  217.218.158.42
      7   503 ms    46 ms    51 ms  10.201.47.222
      8    47 ms    50 ms    46 ms  10.201.42.121
      9     *       85 ms     *     82.178.159.225
     10   237 ms   238 ms   239 ms  94.207.232.53
     11     *        *        *     Request timed out
     12   229 ms   228 ms   228 ms  94.205.255.33
     13     *      229 ms   229 ms  185.25.183.1
    
    Trace complete.
    as you can see the ping is almost fine to oman (85 ms) but after that the ping increase to 238 ms. im not sure if this is a problem with valve servers or my isp

    another tracerroute from a diffrent IP
    this one is Iran > India > Dubai
    Code:
    Tracing route to dxb.valve.net [185.25.183.1]
    over a maximum of 30 hops:
    
      1    39 ms    42 ms    40 ms  10.142.70.34
      2    39 ms     *       51 ms  10.142.70.33
      3     *       39 ms    40 ms  10.140.0.81
      4    39 ms    41 ms    39 ms  10.143.255.202
      5    40 ms    43 ms    43 ms  217.219.0.115
      6    46 ms    46 ms    51 ms  217.218.158.42
      7    57 ms    57 ms    54 ms  10.201.47.222
      8     *       46 ms    47 ms  10.201.42.121
      9   162 ms   162 ms     *     125.18.117.45
     10   256 ms   223 ms     *     182.79.255.14
     11     *      218 ms   215 ms  202.79.197.12
     12     *      305 ms     *     62.216.128.154
     13   311 ms     *        *     62.216.135.225
     14   328 ms     *      319 ms  85.95.26.109
     15   335 ms     *      308 ms  85.95.25.53
     16     *      325 ms     *     85.95.26.214
     17   298 ms     *      304 ms  85.95.26.182
     18     *        *        *     Request timed out.
     19   302 ms     *      303 ms  94.205.255.33
     20   303 ms     *      302 ms  185.25.183.1
    
    Trace complete.
    i can post more traces but i think these 2 routes have the lowest ping to dubai.the other ones goes through europe than dubai
    Last edited by mzn928; 12-18-2014, 09:42 AM.

    Leave a comment:


  • tempster
    replied
    can we get an update on the problem ?

    Leave a comment:


  • JeanLuc
    replied
    Whoops, sorry milton, but I'm going to bug you again. My ISP, Nayatel, actually wanted a reverse trace route to a Pakistani IP getting low pings to Dubai via TW, such as the one Striker posted. If you could provide me with one, I'll be really grateful!

    Leave a comment:


  • milton
    replied
    Based on hop #5 in the trace, traffic is going to the London Exchange (LINX). So this is where all the latency is coming from.

    Prefix Local Pref MED Next Hop AS Path
    101.50.121.0/24 100 90 185.25.183.222 57187 15802 17557 23674 E
    80 100 212.73.253.61 3356 17557 23674 E
    10 100 62.115.40.177 1299 4788 17557 23674 E


    Traceroute to 101.50.121.51 (101.50.121.51)
    Hop RTT Host
    1 1.1 ms 0.5 ms 0.5 ms 185.25.183.222
    2 0.5 ms 0.5 ms 0.5 ms te9-3.bg1.dx1.datamena.ae [ 94.207.33.57 ]
    3 4.4 ms 3.7 ms 3.8 ms 94.205.255.34
    4 149.8 ms 151.1 ms 149.2 ms 10.44.24.210
    5 157.4 ms 157.0 ms 156.0 ms 195.66.225.133
    6 234.1 ms 234.9 ms 234.8 ms khi77.pie.net.pk [ 202.125.134.21 ]
    7 241.2 ms 229.3 ms 232.0 ms static-10GE-KHI275-P01-SwB.pie.net.pk [ 202.125.128.156 ]
    8 258.2 ms 260.3 ms 257.1 ms 221.120.254.13
    9 256.8 ms 256.4 ms 256.6 ms rwp44.pie.net.pk [ 221.120.253.34 ]
    10 183.9 ms 183.8 ms 183.8 ms NUST.rwp44d4.pie.net.pk [ 202.125.149.2 ]
    11 185.6 ms 184.3 ms 185.6 ms 58-65-175-198.nayatel.pk [ 58.65.175.198 ]
    12 * * *

    Originally posted by JeanLuc View Post
    I did email them that trace route. I'm not sure I know why they need a reverse trace route though, I seem to be the only one asking for it on this board, lol. Hopefully milton can provide me with one so I can have Nayatel change the route.

    Leave a comment:


  • JeanLuc
    replied
    I did email them that trace route. I'm not sure I know why they need a reverse trace route though, I seem to be the only one asking for it on this board, lol. Hopefully milton can provide me with one so I can have Nayatel change the route.

    Leave a comment:


  • strikerx921
    replied
    Originally posted by JeanLuc View Post
    I spoke with Nayatel (Islamabad, Pakistan) to shift to TW for their routing to the dubai servers, and they've asked for a reverse trace route. This is the response I received verbatim:


    "Transworld has multiple upstreams and simply shifting to Transworld will only make the latency worse to even Singapore valve servers. Reverse route can tell which upstream Transworld is using to reach dubai (for return path) for such latency. Forward trace is not of much help in this case."

    If I could be provided with a reverse trace route, it would help out Nayatel users. Thanks!
    Did you provide them with a forward trace I posted? And only milton can provide you with a reverse trace
    Code:
    traceroute to dxb.valve.net (185.25.183.1), 30 hops max, 40 byte packets 
     1  FE-3-0-100M-CORE.x.x.x (x.x.x.x)  0.233 ms   0.213 ms   0.174 ms
     2  10.10.80.3 (10.10.80.3)  0.857 ms   0.904 ms   0.637 ms
     3  tw21-static21.tw1.com (117.20.21.21)  7.632 ms   7.111 ms   7.874 ms
     4  tw255-static233.tw1.com (110.93.255.233)  19.724 ms tw255-static101.tw1.com (110.93.255.101)  20.341 ms   20.357 ms
     5  tw255-static6.tw1.com (110.93.255.6)  19.328 ms   19.493 ms   20.206 ms
     6  82.178.32.21 (82.178.32.21)  31.691 ms   30.770 ms   30.742 ms
     7  82.178.33.98 (82.178.33.98)  32.646 ms   32.363 ms   31.329 ms
     8  94.207.232.53 (94.207.232.53)  45.573 ms   47.635 ms   46.500 ms
     9  10.44.152.146 (10.44.152.146)  46.163 ms   45.626 ms   45.679 ms
    10  94.205.255.33 (94.205.255.33)  47.140 ms   46.070 ms   45.735 ms  
    11 185.25.183.1 (185.25.183.1) 46.540 ms 46.407 ms 45.675 ms

    Leave a comment:


  • JeanLuc
    replied
    I spoke with Nayatel (Islamabad, Pakistan) to shift to TW for their routing to the dubai servers, and they've asked for a reverse trace route. This is the response I received verbatim:


    "Transworld has multiple upstreams and simply shifting to Transworld will only make the latency worse to even Singapore valve servers. Reverse route can tell which upstream Transworld is using to reach dubai (for return path) for such latency. Forward trace is not of much help in this case."

    If I could be provided with a reverse trace route, it would help out Nayatel users. Thanks!

    Leave a comment:


  • tempster
    replied
    gah ! its getting so much worse now :/

    ISP: KEMS Country: Kuwait


    C:\Users\Mohammad>tracert dxb.valve.net

    Tracing route to dxb.valve.net [185.25.183.1]
    over a maximum of 30 hops:

    1 <1 ms <1 ms <1 ms 192.168.1.1
    2 9 ms 9 ms 9 ms 80-184-20-1.adsl.kems.net [80.184.20.1]
    3 10 ms 9 ms 9 ms 168.187.0.42
    4 147 ms 147 ms 147 ms 168.187.45.242
    5 149 ms 148 ms 147 ms ldn-b7-link.telia.net [62.115.35.9]
    6 279 ms 278 ms 279 ms dbi-b1-link.telia.net [62.115.136.145]
    7 301 ms 302 ms 301 ms 185.25.183.1

    Trace complete.

    Leave a comment:


  • bellatrikz
    replied
    38 mins searching... still no game

    Leave a comment:


  • strikerx921
    replied
    Be warned though, the server is not populated at all, takes a long time to find a game.

    Leave a comment:


  • strikerx921
    replied
    Call them up and ask to change the route from PTCL to Transworld (TW) for these IPs 185.25.183.1 to 185.25.183.255

    Originally posted by JeanLuc View Post
    hi, been a long time

    heres my tracert:


    Tracing route to dxb.valve.net [185.25.183.1]
    over a maximum of 30 hops:

    1 <1 ms <1 ms <1 ms 192.168.1.1
    2 5 ms 7 ms 6 ms 58-65-175-245.nayatel.pk [58.65.175.245]
    3 5 ms 5 ms 5 ms 58-65-175-197.nayatel.pk [58.65.175.197]
    4 5 ms 4 ms 5 ms s10-1-1-0.rwp44d2.pie.net.pk [202.125.149.1]
    5 8 ms 11 ms 11 ms rwp44.pie.net.pk [221.120.253.33]
    6 30 ms 31 ms 31 ms rwp44.pie.net.pk [221.120.254.38]
    7 28 ms 27 ms 28 ms static-khi-ni01-swa.pie.net.pk [202.125.128.162]

    8 138 ms 133 ms 133 ms 203.208.192.65
    9 113 ms 115 ms 115 ms 203.208.183.89
    10 119 ms 116 ms 115 ms 203.208.172.93
    11 191 ms 191 ms 191 ms ge-0-0-8.0.pjr01.mmb004.flagtel.com [62.216.144.
    233]
    12 215 ms 216 ms 216 ms so-4-0-0.0.pjr01.dxb001.flagtel.com [85.95.25.15
    3]
    13 223 ms 215 ms 213 ms ge-0-2-1.0.pjr04.dxb001.flagtel.com [85.95.26.16
    6]
    14 276 ms 219 ms 275 ms 62.216.144.122
    15 * * * Request timed out.
    16 * 279 ms * 94.205.255.33
    17 280 ms 278 ms 277 ms 94.205.255.33
    18 281 ms 280 ms 277 ms 185.25.183.1

    Trace complete.

    The lowest I've pinged to dubai in game is around 210ms (never played a game on there, this is just from the server select screen).

    What do I need to tell Nayatel to have our routing fixed?

    Thanks!

    Leave a comment:

Working...
X