Anyone of SAIX local only?

I'll try at home, don't have my telkom details at work.

I can tell you that myBB was very slow on my telkom account (capped) yesterday.
 
I should be on local only within the hour. :o

I'll report back.
 
Gimli said:
Hi Bwana, is it possible to do a tracert for us?

Thanks
Click to expand...
It times out at 196.41.144.36

traceroute to www.mweb.co.za (196.2.63.110), 64 hops max, 52 byte packets
1 dsl-144-10-01 (41.144.10.1) 31.191 ms 48.727 ms 61.352 ms
2 196.43.39.58 (196.43.39.58) 29.927 ms 26.735 ms 26.166 ms
3 tiscali-gw.telkom-ipnet.co.za (196.25.55.178) 27.738 ms 28.297 ms 28.674 ms
4 196.41.144.36 (196.41.144.36) 27.982 ms 28.489 ms 74.570 ms
5 *
 
bwana said:
It times out at 196.41.144.36

traceroute to www.mweb.co.za (196.2.63.110), 64 hops max, 52 byte packets
1 dsl-144-10-01 (41.144.10.1) 31.191 ms 48.727 ms 61.352 ms
2 196.43.39.58 (196.43.39.58) 29.927 ms 26.735 ms 26.166 ms
3 tiscali-gw.telkom-ipnet.co.za (196.25.55.178) 27.738 ms 28.297 ms 28.674 ms
4 196.41.144.36 (196.41.144.36) 27.982 ms 28.489 ms 74.570 ms
5 *
Click to expand...

It's possible that MWeb have turned off ping responses, particularly to addresses outside its own range.

I'm on MWeb, and 196.41.144.36 is also my 4th hop, so I think you're nearly there (certainly not going via London).
 
The Mweb site doesnt seem to be on their network try pinging one of their game servers: 196.28.33.137

C:\Users\Brian>ping mweb.co.za

Pinging mweb.co.za [196.2.63.110] with 32 bytes of data:
Reply from 196.2.63.110: bytes=32 time=26ms TTL=123
Reply from 196.2.63.110: bytes=32 time=27ms TTL=123
Reply from 196.2.63.110: bytes=32 time=26ms TTL=123
Reply from 196.2.63.110: bytes=32 time=26ms TTL=123

Ping statistics for 196.2.63.110:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 26ms, Maximum = 27ms, Average = 26ms

Mweb Gaming servers (Gamezone):

Pinging 196.28.33.136 with 32 bytes of data:
Reply from 196.28.33.136: bytes=32 time=502ms TTL=111
Reply from 196.28.33.136: bytes=32 time=494ms TTL=111
Reply from 196.28.33.136: bytes=32 time=512ms TTL=111
Reply from 196.28.33.136: bytes=32 time=490ms TTL=111

Ping statistics for 196.28.33.136:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 490ms, Maximum = 512ms, Average = 499ms

tracert 196.28.33.136

Tracing route to elf.games.mweb.co.za [196.28.33.136]
over a maximum of 30 hops:

1 19 ms 18 ms 22 ms dsl-240-220-01.telkomadsl.co.za [41.240.220.1]
2 21 ms 20 ms 18 ms 196.43.35.33
3 23 ms 29 ms 29 ms 196.43.35.33
4 47 ms 49 ms 49 ms 196.43.10.130
5 45 ms 50 ms 51 ms 196.43.33.5
6 247 ms 246 ms 252 ms lon-ip-dir-telecity-gig-4-0-1025.telkom-ipnet.co
.za [196.43.18.121]
7 257 ms 293 ms 256 ms 1329.xe-3-2-0.mpr2.lhr3.uk.above.net [213.161.92
.181]
8 264 ms 276 ms 280 ms ge-4-2-0.mpr1.lhr3.uk.above.net [64.125.27.157]

9 283 ms 289 ms 273 ms so-0-0-0.mpr1.lhr2.uk.above.net [64.125.27.225]

10 248 ms 246 ms 261 ms 79.141.38.38.available.above.net [79.141.38.38]

11 505 ms 490 ms 492 ms pos-0-0-0-0.mid-1.mweb.co.za [196.22.163.229]
12 497 ms 528 ms 543 ms tengig-0-0-0-0-42.vic-up-2.mweb.co.za [196.22.16
9.218]
13 608 ms 559 ms 530 ms vl-11.vic-hscore-1.mweb.co.za [196.22.169.227]
14 523 ms 511 ms 531 ms tengig-3-1.vic-core-sw1.mweb.co.za [196.22.169.6
6]
15 498 ms 500 ms 526 ms elf.games.mweb.co.za [196.28.33.136]

Trace complete.
 
bwana said:
It times out at 196.41.144.36

traceroute to www.mweb.co.za (196.2.63.110), 64 hops max, 52 byte packets
1 dsl-144-10-01 (41.144.10.1) 31.191 ms 48.727 ms 61.352 ms
2 196.43.39.58 (196.43.39.58) 29.927 ms 26.735 ms 26.166 ms
3 tiscali-gw.telkom-ipnet.co.za (196.25.55.178) 27.738 ms 28.297 ms 28.674 ms
4 *
5 *
Click to expand...

Mine times out at the telkom ipnet?
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X