MWEB-Telkom New Routing

M

marjo

Well-Known Member
Joined
Jan 26, 2007
Messages
229
Reaction score
40
Location
Johannesburg
Old
Tracing route to www.telkom.co.za [196.43.22.222]
over a maximum of 30 hops:

1 1 ms 2 ms 1 ms 10.0.1.254
2 10 ms 9 ms 10 ms 41-132-10-1.dsl.mweb.co.za [41.132.10.1]
3 11 ms 11 ms 11 ms tengig-0-0-0-107.vic-ipc-1.mweb.co.za [196.22.169.158]
4 11 ms 12 ms 12 ms vl-92.vic-hscore-1.mweb.co.za [196.22.189.2]
5 12 ms 14 ms 11 ms tengig-0-0-0-0-11.vic-up-1.mweb.co.za [196.22.169.225]
6 * 11 ms 11 ms rrba-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.8.249]
7 11 ms 12 ms 11 ms rrba-ip-esr-1-pos-8-0-0.telkom-ipnet.co.za [196.43.8.146]
8 13 ms 11 ms 12 ms rrba-ip-bssr-1-ge-2-48.telkom-ipnet.co.za [196.43.23.6]
9 14 ms 14 ms 27 ms nbsc-ip-bssr-2-atm-5-0-0-1.telkom-ipnet.co.za [196.43.23.34]
10 18 ms 15 ms 15 ms nbsc-ip-rcache-1-vif2.telkom-ipnet.co.za [196.43.22.222]

Trace complete.

New:
Tracing route to www.telkom.co.za [196.43.22.222]
over a maximum of 30 hops:

1 1 ms 2 ms 2 ms 10.0.1.254
2 10 ms 9 ms 10 ms 41-132-10-1.dsl.mweb.co.za [41.132.10.1]
3 11 ms 11 ms 12 ms tengig-0-0-0-107.vic-ipc-1.mweb.co.za [196.22.169.158]
4 11 ms 12 ms 11 ms vl-92.vic-hscore-1.mweb.co.za [196.22.189.2]
5 12 ms 12 ms 13 ms tengig-0-0-0-0-11.vic-up-1.mweb.co.za [196.22.169.225]
6 68 ms 49 ms 39 ms tengig-0-2-0-0.mid-1.mweb.co.za [196.22.169.219]
7 235 ms 234 ms 234 ms pos-0-0-0-0.lon-1.mweb.co.za [196.22.163.230]
8 238 ms 236 ms 236 ms 149.6.98.17
9 551 ms 237 ms 236 ms te7-2.ccr01.lon01.atlas.cogentco.com [154.54.36.165]
10 * * 234 ms te1-2.mpd01.lon01.atlas.cogentco.com [130.117.3.225]
11 235 ms 234 ms 235 ms te1-1.ccr01.lon05.atlas.cogentco.com [130.117.49.106]
12 217 ms 215 ms 215 ms 149.6.2.194
13 217 ms 216 ms 215 ms rrba-ip-esr-1-ge-6-0-0.telkom-ipnet.co.za [196.43.11.166]
14 216 ms 215 ms 215 ms rrba-ip-bssr-1-ge-2-48.telkom-ipnet.co.za [196.43.23.6]
15 219 ms 218 ms 219 ms nbsc-ip-bssr-2-atm-5-0-0-1.telkom-ipnet.co.za [196.43.23.34]
16 219 ms 219 ms 220 ms nbsc-ip-rcache-1-vif2.telkom-ipnet.co.za [196.43.22.222]

Trace complete.
 
It's actually worse this afternoon. Seems to be longer delays on the 2nd half of the tracert. I suspect Telkom are forcing traffic from inbound international to go via London (reciprocating MWeb's transit cuts). This means that if the original user is local, there are 2 trips to London instead of 1 (which it was earlier today).

Code: 
Tracing route to telkom.co.za [196.43.22.222]
over a maximum of 30 hops:

   1   <10 ms   <10 ms   <10 ms  home.gateway [192.168.1.254]
   2     6 ms     6 ms     6 ms  41-132-48-1.dsl.mweb.co.za [41.132.48.1]
   3     8 ms     8 ms     8 ms  196-28-178-166.adsl.mweb.co.za [196.28.178.166]
   4    30 ms    31 ms    30 ms  gig-0-0-1-vic-hscore-3.mweb.co.za [196.22.169.45]
   5    30 ms    30 ms    30 ms  196.22.169.61
   6    32 ms    34 ms    32 ms  tengig-0-0-0-0-11.vic-up-1.mweb.co.za [196.22.169.225]
   7    31 ms    34 ms    34 ms  tengig-0-2-0-0.mid-1.mweb.co.za [196.22.169.219]
   8   269 ms   270 ms   269 ms  196.22.175.218
   9   262 ms   262 ms   261 ms  149.6.98.5
  10   262 ms   262 ms   261 ms  te7-2.ccr01.lon01.atlas.cogentco.com [154.54.36.165]
  11   261 ms   260 ms   260 ms  te2-2.mpd01.lon01.atlas.cogentco.com [130.117.1.74]
  12   261 ms   261 ms   261 ms  te2-1.ccr01.lon05.atlas.cogentco.com [130.117.49.94]
  13   270 ms   271 ms   270 ms  149.6.2.194
  14   454 ms   454 ms   454 ms  rrba-ip-esr-1-ge-6-0-0.telkom-ipnet.co.za [196.43.11.166]
  15   459 ms   458 ms   460 ms  rrba-ip-bssr-1-ge-2-48.telkom-ipnet.co.za [196.43.23.6]
  16   448 ms   447 ms   447 ms  nbsc-ip-bssr-1-atm-5-0-0-1.telkom-ipnet.co.za [196.43.23.30]
  17   459 ms   461 ms   462 ms  telkom.co.za [196.43.22.222]

Trace complete.
 
This opens a very very interesting question.

How is SAIX now classifying MWEB Traffic.

I know that MWEB Local only accounts can still access SAIX and MTN (even though its going international), can the same be said of the SAIX and MTN accounts? If they can't, it would be interesting to see the relevant terms and conditions and see how they define local only traffic. Because if the definition is in conflict with what is actually happening, a lot of users could have an interesting case against their respective providers.
 
Im still getting the same pings as I was last week: Telkom - Mweb:
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=27ms TTL=123
Reply from 196.2.63.110: bytes=32 time=32ms TTL=123
Reply from 196.2.63.110: bytes=32 time=29ms TTL=123
Reply from 196.2.63.110: bytes=32 time=30ms 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 = 27ms, Maximum = 32ms, Average = 29ms

But have a look @ this tracert:

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


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

1 26 ms 28 ms 30 ms dsl-240-220-01.telkomadsl.co.za [41.240.220.1]
2 28 ms 30 ms 29 ms 196.43.39.62
3 29 ms 29 ms 28 ms tiscali-gw.telkom-ipnet.co.za [196.25.55.178]
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 *
 
nging games.saix.net [196.43.22.222] with 32 bytes of data:
ply from 196.43.22.222: bytes=32 time=471ms TTL=240
ply from 196.43.22.222: bytes=32 time=452ms TTL=240
ply from 196.43.22.222: bytes=32 time=458ms TTL=240
ply from 196.43.22.222: bytes=32 time=454ms TTL=240

Gone
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X