Mweb, Afrihost Look Here

Tweak

Expert Member
Joined
Jul 10, 2008
Messages
1,658
Reaction score
3
Location
CT
Test Latencies to these gaming Servers please?

213.248.106.30
213.248.106.85
213.248.106.38


Post them here!
 
Afrihost 384k uncapped

All three time out after the 19th hop.

Code:
C:\Documents and Settings\dj_jyno>tracert 213.248.106.80

Tracing route to host-80.battle.net [213.248.106.80]
over a maximum of 30 hops:

  1     1 ms    <1 ms    <1 ms  10.0.0.1
  2    21 ms    22 ms    20 ms  196-210-146-129-tvwt-esr-2.dynamic.isadsl.co.za [196.210.146.129]
  3    43 ms    43 ms    41 ms  cdsl1-rba-vl2460.ip.isnet.net [196.38.72.217]
  4    44 ms    42 ms    42 ms  cdsl1-rba-vl150.ip.isnet.net [196.38.73.17]
  5    44 ms    42 ms    42 ms  core2b-rba-te2-0-0.ip.isnet.net [196.26.0.182]
  6   326 ms   327 ms   327 ms  mi-za-rba-p6-gi2-0-0-306.ip.isnet.net [168.209.164.177]
  7   326 ms   329 ms   326 ms  mi-us-25b-p2-po1-3-3.ip.isnet.net [168.209.160.215]
  8   325 ms   325 ms   323 ms  core2a-ny-gi1-0-19-306.ip.isnet.net [168.209.164.128]
  9   324 ms   323 ms   326 ms  168.209.244.3
 10   321 ms   321 ms   322 ms  xe-6-1.r02.nycmny03.us.bb.gin.ntt.net [129.250.193.253]
 11   322 ms   324 ms   324 ms  ae-1.r00.nycmny03.us.bb.gin.ntt.net [129.250.3.57]
 12   327 ms   327 ms   327 ms  p16-1-1-0.r20.nycmny01.us.bb.gin.ntt.net [129.250.3.82]
 13   321 ms   325 ms     *     po-3.r03.nycmny01.us.bb.gin.ntt.net [129.250.2.11]
 14   323 ms   325 ms   323 ms  nyk-b1-link.telia.net [213.248.69.53]
 15   320 ms   322 ms   324 ms  nyk-bb2-link.telia.net [80.91.248.161]
 16   337 ms   338 ms   336 ms  kbn-bb2-link.telia.net [80.91.247.120]
 17   346 ms   364 ms   346 ms  s-bb2-link.telia.net [80.91.246.108]
 18   351 ms   347 ms   357 ms  s-b1-link.telia.net [80.91.252.125]
 19   346 ms   344 ms   347 ms  80.91.247.33
 20     *        *        *     Request timed out.
 21     *        *        *     Request timed out.
 22     *        *        *     Request timed out.
 23     *        *        *     Request timed out.
 24     *        *        *     Request timed out.
 
same here

mweb 4mb uncapped.

Code:
tracert 213.248.106.30

Tracing route to host-30.battle.net [213.248.106.30]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  Billion.400G [10.0.0.2]
  2    19 ms    14 ms    17 ms  43-172-8-4.dsl.mweb.co.za [431.172.8.4]
  3    27 ms    27 ms    27 ms  tengig-0-0-0-107.vic-ipc-1.mweb.co.za [196.25.16
9.188]
  4    28 ms    28 ms    30 ms  vl-92.vic-hscore-2.mweb.co.za [196.22.189.3]
  5    70 ms    78 ms    63 ms  tengig-0-0-0-0-12.vic-up-1.mweb.co.za [196.22.16
9.241]
  6    36 ms    31 ms    33 ms  tengig-0-3-1-0.mid-1.mweb.co.za [196.22.169.211]

  7   273 ms   273 ms   272 ms  pos-0-0-0-0.lon-1.mweb.co.za [196.22.163.230]
  8   272 ms   271 ms   271 ms  130.117.136.33
  9   271 ms   271 ms   271 ms  te1-2.ccr01.lon02.atlas.cogentco.com [130.117.50
.138]
 10   271 ms   271 ms   271 ms  te4-2.mpd02.lon01.atlas.cogentco.com [130.117.1.
18]
 11   283 ms   446 ms   283 ms  vl3493.mpd01.lon01.atlas.cogentco.com [130.117.2
.17]
 12   273 ms   272 ms   272 ms  ldn-b4-link.telia.net [213.248.70.237]
 13   271 ms   357 ms   271 ms  ldn-bb2-link.telia.net [80.91.254.21]
 14   298 ms   291 ms   289 ms  hbg-bb1-link.telia.net [80.91.250.148]
 15   303 ms   302 ms   302 ms  s-bb2-link.telia.net [80.239.147.169]
 16   303 ms   304 ms   312 ms  s-b1-link.telia.net [80.91.253.228]
 17   310 ms   306 ms   308 ms  80.91.247.33
 18     *        *        *     Request timed out.
 19     *        *        *     Request timed out.
 20     *        *        *     Request timed out.
 21     *        *        *     Request timed out.
 22     *        *        *     Request timed out.
 
Mweb 4mb uncapped:

Code:
Tracing route to host-30.battle.net [213.248.106.30]
over a maximum of 30 hops:

  1     1 ms    <1 ms     1 ms  192.168.0.1
  2     *        *        *     Request timed out.
  3    32 ms    32 ms    31 ms  tengig-0-0-0-104.vic-ipc-2.mweb.co.za [196.22.16
3.218]
  4    32 ms    32 ms    33 ms  vl-92.vic-hscore-2.mweb.co.za [196.22.189.3]
  5    62 ms    70 ms    81 ms  tengig-0-0-0-0-12.vic-up-1.mweb.co.za [196.22.16
9.241]
  6    63 ms    61 ms    50 ms  tengig-0-3-1-0.mid-1.mweb.co.za [196.22.169.211]

  7   254 ms   255 ms   255 ms  pos-0-0-0-0.lon-1.mweb.co.za [196.22.163.230]
  8   252 ms   252 ms   251 ms  130.117.136.1
  9   252 ms   251 ms   251 ms  te1-2.ccr01.lon02.atlas.cogentco.com [130.117.50
.138]
 10   252 ms   252 ms   251 ms  te4-2.mpd02.lon01.atlas.cogentco.com [130.117.1.
18]
 11   252 ms   252 ms   266 ms  vl3493.mpd01.lon01.atlas.cogentco.com [130.117.2
.17]
 12   251 ms   252 ms   251 ms  ldn-b4-link.telia.net [213.248.70.237]
 13   252 ms   252 ms   355 ms  ldn-bb1-link.telia.net [80.91.250.234]
 14   271 ms   270 ms   271 ms  hbg-bb1-link.telia.net [80.239.147.182]
 15   289 ms   285 ms   288 ms  s-bb1-link.telia.net [80.239.147.165]
 16   283 ms   287 ms   286 ms  s-b1-link.telia.net [80.91.252.69]
 17   285 ms   284 ms   286 ms  s-hdn-i3-link.telia.net [80.91.251.245]
 
Last edited:
Mweb 4mb uncapped:

Code:
Tracing route to host-30.battle.net [213.248.106.30]
over a maximum of 30 hops:

  1     1 ms    <1 ms     1 ms  192.168.0.1
  2     *        *        *     Request timed out.
  3    32 ms    32 ms    31 ms  tengig-0-0-0-104.vic-ipc-2.mweb.co.za [196.22.16
3.218]
  4    32 ms    32 ms    33 ms  vl-92.vic-hscore-2.mweb.co.za [196.22.189.3]
  5    62 ms    70 ms    81 ms  tengig-0-0-0-0-12.vic-up-1.mweb.co.za [196.22.16
9.241]
  6    63 ms    61 ms    50 ms  tengig-0-3-1-0.mid-1.mweb.co.za [196.22.169.211]

  7   254 ms   255 ms   255 ms  pos-0-0-0-0.lon-1.mweb.co.za [196.22.163.230]
  8   252 ms   252 ms   251 ms  130.117.136.1
  9   252 ms   251 ms   251 ms  te1-2.ccr01.lon02.atlas.cogentco.com [130.117.50
.138]
 10   252 ms   252 ms   251 ms  te4-2.mpd02.lon01.atlas.cogentco.com [130.117.1.
18]
 11   252 ms   252 ms   266 ms  vl3493.mpd01.lon01.atlas.cogentco.com [130.117.2
.17]
 12   251 ms   252 ms   251 ms  ldn-b4-link.telia.net [213.248.70.237]
 13   252 ms   252 ms   355 ms  ldn-bb1-link.telia.net [80.91.250.234]
 14   271 ms   270 ms   271 ms  hbg-bb1-link.telia.net [80.239.147.182]
 15   289 ms   285 ms   288 ms  s-bb1-link.telia.net [80.239.147.165]
 16   283 ms   287 ms   286 ms  s-b1-link.telia.net [80.91.252.69]
 17   285 ms   284 ms   286 ms  s-hdn-i3-link.telia.net [80.91.251.245]

aha!

I used to get 280ms latency on afrihost too.. wonder if it will ever get better?
 
Pinging 213.248.106.30 with 32 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 213.248.106.30:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

{Mweb 318 uncapped}
 
Traceroutes and pinging gaming servers are pointless because of 2 reasons:

1) Traceroute and ping uses the ICMP protocol, while your gaming client uses the UDP or TCP protocol which gets handled differently by mweb/afrihosts shaping policies.
2) This won't make sense to 99% of people so it's probably falling on deaf ears. (eyes?)
 
ok so how does one ping a battle.net europe server?

Blackhand succesfully pinged telia, it is the server where Battle.net is being hosted



owned much? :D
 
ok so how does one ping a battle.net europe server?

Blackhand succesfully pinged telia, it is the server where Battle.net is being hosted



owned much? :D


Incorrect, you are able to ping the router located within telia's backbone, or traceroute to it, but you will never actually get responses from the server directly. Hense after x amount of hops you start getting timeouts, ICMP's are blocked, they are the key source of denial of service attacks.
 
ok so how does one ping a battle.net europe server?

Blackhand succesfully pinged telia, it is the server where Battle.net is being hosted



owned much? :D

Incorrect, you are able to ping the router located within telia's backbone, or traceroute to it, but you will never actually get responses from the server directly. Hense after x amount of hops you start getting timeouts, ICMP's are blocked, they are the key source of denial of service attacks.

pwnd
 
Top
Sign up to the MyBroadband newsletter
X