MWEB Uncapped Subscribers Feedback

Status
Not open for further replies.
Code: 
>tracert www.vodacombusiness.co.za

ww.vodacombusiness.co.za [41.192.255.41]
30 hops:

 ms     1 ms  192.168.0.1
 ms    15 ms  41-132-4-1.dsl.mweb.co.za [41.132.4.1]
 ms   131 ms  tengig-0-0-0-110.vic-ipc-1.mweb.co.za [196.22.16

 ms    95 ms  vl-92.vic-hscore-1.mweb.co.za [196.22.189.2]
 ms   159 ms  tengig-0-0-0-0-11.vic-up-1.mweb.co.za [196.22.16

 ms   150 ms  rrba-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.8.

 ms   142 ms  vodacom-gw.telkom-ipnet.co.za [196.25.253.110]
 ms   109 ms  41.0.0.23
 ms    82 ms  41.0.4.2
 ms   153 ms  vc-196-207-44-133.3g.vodacom.co.za [196.207.44.1

 ms   155 ms  vc-196-207-44-10.3g.vodacom.co.za [196.207.44.10

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

Does this help?
 
Last edited:
Hi All

I've raised this with our networks team based on the Tracert results provided by Blackhand.

Kind Regards
MWEB Operations
 
Tracing route to games.saix.net [196.43.22.222]
over a maximum of 30 hops:

1 3 ms 1 ms 2 ms 192.*.*.*
2 12 ms 11 ms 11 ms 41-132-2-1.dsl.mweb.co.za [41.132.2.1]
3 102 ms 102 ms 104 ms tengig-0-0-0-107.vic-ipc-1.mweb.co.za [196.22.169.158]
4 75 ms 75 ms 78 ms vl-92.vic-hscore-1.mweb.co.za [196.22.189.2]
5 111 ms 117 ms 112 ms tengig-0-0-0-0-11.vic-up-1.mweb.co.za [196.22.169.225]
6 79 ms 83 ms 82 ms rrba-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.8.249]
7 100 ms 95 ms 94 ms rrba-ip-esr-1-ge-6-0-0.telkom-ipnet.co.za [196.43.11.166]
8 89 ms 86 ms 87 ms rrba-ip-bssr-1-ge-2-48.telkom-ipnet.co.za [196.43.23.6]
9 94 ms 87 ms 86 ms nbsc-ip-bssr-1-atm-5-0-0-1.telkom-ipnet.co.za [196.43.23.30]
10 94 ms 91 ms * nbsc-ip-rcache-1-vif2.telkom-ipnet.co.za [196.43.22.222]
11 97 ms 100 ms 100 ms nbsc-ip-rcache-1-vif2.telkom-ipnet.co.za [196.43.22.222]

Trace complete.


Was getting ping of 160ms off this addie.
 
Will@MWEB said:
Hi BigBear

Can you run a tracert to www.google.co.za for me please and post the results.
Click to expand...

512kbps

Pretoria, SA

PHP: 
Tracing route to www.l.google.com [64.233.179.104]

  2    24 ms     5 ms     4 ms  dsl.mweb.co.za
  3    14 ms    10 ms    13 ms  tengig-0-0-0-104.vic-ipc-1.mweb.co.za [196.22.169.146]
  4    70 ms    13 ms    14 ms  vl-92.vic-hscore-2.mweb.co.za [196.22.189.3]
  5     5 ms    12 ms    11 ms  tengig-0-0-0-0-12.vic-up-1.mweb.co.za [196.22.169.241]
  6     6 ms    11 ms     6 ms  tengig-0-2-0-0.mid-1.mweb.co.za [196.22.169.219]
  7   127 ms   124 ms   145 ms  pos-0-0-0-0.lon-1.mweb.co.za [196.22.163.230]
  8   104 ms   102 ms    72 ms  195.66.224.125
  9    83 ms   190 ms    62 ms  64.233.175.25
 10    84 ms   217 ms   124 ms  72.14.232.95
 11   152 ms   165 ms   257 ms  64.233.174.41
 12    92 ms   133 ms   115 ms  64.233.174.105
 13    99 ms    94 ms   105 ms  cpt01s01-in-f104.1e100.net [64.233.179.104]

Trace complete.


PHP: 
Tracing route to www.vodacombusiness.co.za [41.192.255.41]

  2    13 ms    33 ms    69 ms  .dsl.mweb.co.za
  3    56 ms    68 ms   100 ms  tengig-0-0-0-104.vic-ipc-1.mweb.co.za [196.22.169.146]
  4     5 ms     4 ms     4 ms  vl-92.vic-hscore-1.mweb.co.za [196.22.189.2]
  5     7 ms    20 ms     8 ms  tengig-0-0-0-0-11.vic-up-1.mweb.co.za [196.22.169.225]
  6   147 ms   405 ms   297 ms  rrba-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.8.249]
  7   334 ms   201 ms   243 ms  vodacom-gw.telkom-ipnet.co.za [196.25.253.110]
  8   286 ms     *      282 ms  41.0.0.23
  9     7 ms     8 ms    24 ms  41.0.4.2
 10    36 ms    14 ms    12 ms  vc-196-207-44-133.3g.vodacom.co.za [196.207.44.133]
 11     7 ms     5 ms    11 ms  vc-196-207-44-10.3g.vodacom.co.za [196.207.44.10]
 12     *        *        *     Request timed out.


PHP: 
Tracing route to www.webafrica.co.za [196.220.58.66]

  1    <1 ms    <1 ms    <1 ms  home.gateway
  2   190 ms     4 ms     6 ms  dsl.mweb.co.za
  3   562 ms   801 ms   303 ms  tengig-0-0-0-104.vic-ipc-1.mweb.co.za [196.22.169.146]
  4   267 ms   198 ms   132 ms  vl-92.vic-hscore-1.mweb.co.za [196.22.189.2]
  5    36 ms   144 ms   103 ms  tengig-0-0-0-0-11.vic-up-1.mweb.co.za [196.22.169.225]
  6    71 ms    80 ms    83 ms  rrba-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.8.249]
  7   269 ms   313 ms    95 ms  196.43.51.26
  8    42 ms    24 ms    10 ms  vl102.er.gw.cpt.za.wa.co.za [196.220.59.229]
  9    11 ms     8 ms    10 ms  vl35.cr.gw.cpt.za.wa.co.za [41.185.0.37]
 10    38 ms    31 ms    28 ms  fe0.er1.gw.cpt.za.wadns.net [41.185.0.4]
 11    10 ms    11 ms     8 ms  wa-acc1.wadns.net [196.220.39.253]
 12    47 ms    45 ms     8 ms  196.220.58.66

Trace complete.


PHP: 
Tracing route to www.vodacom.co.za [41.1.224.101]

  1    <1 ms    <1 ms    <1 ms  home.gateway
  2     3 ms     8 ms     5 ms  dsl.mweb.co.za
  3    31 ms     5 ms     5 ms  tengig-0-0-0-104.vic-ipc-2.mweb.co.za [196.22.163.218]
  4    83 ms    15 ms     4 ms  vl-92.vic-hscore-2.mweb.co.za [196.22.189.3]
  5     6 ms     5 ms    22 ms  tengig-0-0-0-0-12.vic-up-1.mweb.co.za [196.22.169.241]
  6    14 ms     6 ms     6 ms  rrba-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.8.249]
  7     8 ms     5 ms     6 ms  vodacom-gw.telkom-ipnet.co.za [196.25.253.110]
  8     9 ms    13 ms     5 ms  41.0.0.23
  9    14 ms     9 ms     7 ms  41.0.4.2
 10    40 ms    31 ms    13 ms  vc-196-207-44-133.3g.vodacom.co.za [196.207.44.133]
 11    12 ms    23 ms     7 ms  10.113.222.133
 12    71 ms    19 ms    14 ms  10.113.222.134
 13     *        *        *     Request timed out.
 14     5 ms    19 ms    21 ms  41.1.224.101

Trace complete.
 
It appears that there may have been some congestion on one of the network links last night, I've looked at some traces from our test bench today and everything seems to be running normally. Our engineers will continue to monitor the situation.
 
Will@MWEB said:
It appears that there may have been some congestion on one of the network links last night, I've looked at some traces from our test bench today and everything seems to be running normally. Our engineers will continue to monitor the situation.
Click to expand...

I hope so, got a clannie tonight :D
 
Hi MWEB Ops:

Are you also shaping ftp protocols--I am busy downloading drivers/firmware for my netgear from their official site, and the connection is crawling at 34K! Have a look at this screenshot; The las t time I was downloading Dell drivers, when this happened 3 days ago--Is this a day time thing or night?
 
Smiley_lauf said:
Hi MWEB Ops:

Are you also shaping ftp protocols--I am busy downloading drivers/firmware for my netgear from their official site, and the connection is crawling at 34K! Have a look at this screenshot; The las t time I was downloading Dell drivers, when this happened 3 days ago--Is this a day time thing or night?
Click to expand...
You do know that downloading drivers from manufacturers are almost always slow...
 
Hi Smiley

ftp sites will sometimes limit the speed per connection. You can try using a download manager that allows multiple threads and see if that helps.
 
*whistle*

Not feeling anything international slow :-)

On a 384k line and been going strong for very long now

*touch wood*
 
4Mbit Uncapped

New Result

943053979.png
 
Last edited:
Status
Not open for further replies.
Back
Top
Sign up to the MyBroadband newsletter
X