MWEB Uncapped Subscribers Feedback

kleuter · May 4, 2010

Pta to CPT

This is on a 4mb service,

now tell me there is no problem?

hambone · May 4, 2010

Please could some explain to me whether us in the Eastern Cape are experiencing the same difficulties as those in Cape Town (as described by Gordon_R and Sabrewolfy). Are these pings normal, 'case I'm getting maximum 0.73Mb/s on speedtest, from Grahamstown to Joburg:

Code:

Tracing route to www.l.google.com [209.85.135.104]
over a maximum of 30 hops:

  1     3 ms     1 ms     1 ms  . [192.168.2.1]
  2     *        *        *     Request timed out.
  3   110 ms   111 ms   111 ms  tengig-0-0-0-107.vic-ipc-1.mweb.co.za [196.22.16
9.158]
  4   242 ms   111 ms   109 ms  vl-92.vic-hscore-2.mweb.co.za [196.22.189.3]
  5   151 ms   149 ms   172 ms  tengig-0-0-0-0-12.vic-up-1.mweb.co.za [196.22.16
9.241]
  6   126 ms   126 ms   149 ms  tengig-0-3-1-0.mid-1.mweb.co.za [196.22.169.211]

  7   366 ms   331 ms   330 ms  pos-0-0-0-0.lon-1.mweb.co.za [196.22.163.230]
  8   330 ms   370 ms   357 ms  130.117.136.1
  9   369 ms   403 ms   575 ms  te1-2.ccr01.lon02.atlas.cogentco.com [130.117.50
.138]
 10   328 ms   330 ms   340 ms  te4-2.mpd02.lon01.atlas.cogentco.com [130.117.1.
18]
 11   348 ms   332 ms   331 ms  google.lon01.atlas.cogentco.com [130.117.14.90]

 12   362 ms   330 ms   354 ms  64.233.175.25
 13   341 ms   341 ms   358 ms  209.85.248.80
 14   357 ms   361 ms   358 ms  209.85.250.141
 15   355 ms   362 ms   392 ms  72.14.238.128
 16   353 ms   409 ms   365 ms  209.85.240.223
 17   361 ms   367 ms   373 ms  72.14.239.54
 18   399 ms   430 ms   363 ms  mu-in-f104.1e100.net [209.85.135.104]

Trace complete.

TonyA · May 4, 2010

Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.

Hi my figures for the same trace. from CT with 4mbs line and Mweb 4mbs uncapped. Don't know what figures mean

Tracing route to www.l.google.com [209.85.135.106]
over a maximum of 30 hops:

1 <1 ms 1 ms 1 ms home.gateway [192.168.1.254]
2 * * * Request timed out.
3 89 ms 127 ms 103 ms tengig-0-0-0-104.vic-ipc-1.mweb.co.za [196.22.16
9.146]
4 86 ms 86 ms 232 ms vl-92.vic-hscore-2.mweb.co.za [196.22.189.3]
5 * 119 ms 119 ms tengig-0-0-0-0-12.vic-up-1.mweb.co.za [196.22.16
9.241]
6 109 ms 169 ms 189 ms tengig-0-2-0-0.mid-1.mweb.co.za [196.22.169.219]

7 339 ms 315 ms 305 ms pos-0-0-0-0.lon-1.mweb.co.za [196.22.163.230]
8 312 ms 385 ms 472 ms 130.117.136.1
9 312 ms 385 ms 427 ms te1-2.ccr02.lon02.atlas.cogentco.com [130.117.50
.117]
10 306 ms 311 ms 309 ms te9-2.mpd02.lon01.atlas.cogentco.com [130.117.48
.153]
11 393 ms 308 ms 310 ms google.lon01.atlas.cogentco.com [130.117.14.90]

12 332 ms 407 ms 312 ms 64.233.175.27
13 338 ms 353 ms 347 ms 72.14.233.63
14 337 ms 323 ms 317 ms 209.85.248.183
15 417 ms 333 ms 330 ms 209.85.248.248
16 332 ms 329 ms 330 ms 209.85.241.187
17 389 ms 327 ms 347 ms 209.85.253.26
18 328 ms 331 ms 332 ms mu-in-f106.1e100.net [209.85.135.106]

Trace complete.

C:\Users\Tony>

D34M0n7 · May 4, 2010

I'm in Constantia Park Pretoria, seems to be worse here.

Tracing route to www.l.google.com [209.85.135.104]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms home.gateway [192.168.0.1]
2 264 ms 321 ms 482 ms 41-132-30-1.dsl.mweb.co.za [41.132.30.1]
3 711 ms 749 ms 831 ms tengig-0-0-0-104.vic-ipc-1.mweb.co.za [196.22.169.146]
4 846 ms 989 ms 962 ms vl-92.vic-hscore-2.mweb.co.za [196.22.189.3]
5 978 ms 964 ms 722 ms tengig-0-0-0-0-12.vic-up-1.mweb.co.za [196.22.169.241]
6 658 ms 775 ms 700 ms tengig-0-2-0-0.mid-1.mweb.co.za [196.22.169.219]
7 848 ms 864 ms 962 ms pos-0-0-0-0.lon-1.mweb.co.za [196.22.163.230]
8 1058 ms 1069 ms 936 ms 130.117.136.33
9 799 ms 911 ms 882 ms te1-2.ccr01.lon02.atlas.cogentco.com [130.117.50.138]
10 843 ms 855 ms 884 ms te4-2.mpd02.lon01.atlas.cogentco.com [130.117.1.18]
11 1061 ms 1175 ms 1160 ms google.lon01.atlas.cogentco.com [130.117.14.90]
12 1102 ms 1086 ms 1099 ms 64.233.175.27
13 959 ms 842 ms 831 ms 72.14.233.63
14 758 ms 858 ms 965 ms 209.85.248.183
15 1217 ms 1125 ms 967 ms 209.85.248.248
16 1216 ms 1255 ms 1151 ms 209.85.241.187
17 1060 ms 1203 ms 1255 ms 209.85.253.26
18 740 ms 910 ms 1072 ms mu-in-f104.1e100.net [209.85.135.104]

Trace complete.

zeely · May 4, 2010

ja - something is definitely up.downloads from rapidshare dropped to 4k/sec

Gordon_R · May 4, 2010

hambone said:
Please could some explain to me whether us in the Eastern Cape are experiencing the same difficulties as those in Cape Town (as described by Gordon_R and Sabrewolfy). Are these pings normal, 'case I'm getting maximum 0.73Mb/s on speedtest, from Grahamstown to Joburg:

1 3 ms 1 ms 1 ms . [192.168.2.1]
2 * * * Request timed out.
3 110 ms 111 ms 111 ms tengig-0-0-0-107.vic-ipc-1.mweb.co.za [196.22.16
9.158]

MWeb is obviously dependent on SAIX (and perhaps DFA or Neotel) to get the traffic from CT (and elsewehere) up to Jhb, and something is very wrong somewhere.

Until we get an MWeb Network Notice, or a comment from the MWeb person, there is not much point in speculating further.

TonyA said:
Hi my figures for the same trace. from CT with 4mbs line and Mweb 4mbs uncapped. Don't know what figures mean

1 <1 ms 1 ms 1 ms home.gateway [192.168.1.254]
2 * * * Request timed out.
3 89 ms 127 ms 103 ms tengig-0-0-0-104.vic-ipc-1.mweb.co.za [196.22.16
9.146]

Once that 3rd hop (CT-Jhb) takes more than 30ms, you can be sure there is congestion or some network problem!

Beyond hop 3 everything is OK (or as normal as it gets), so you don't have to post the whole tracert...

D34M0n7 said:
I'm in Constantia Park Pretoria, seems to be worse here.

1 <1 ms <1 ms <1 ms home.gateway [192.168.0.1]
2 264 ms 321 ms 482 ms 41-132-30-1.dsl.mweb.co.za [41.132.30.1]
3 711 ms 749 ms 831 ms tengig-0-0-0-104.vic-ipc-1.mweb.co.za [196.22.169.146]

F******, that's really bad...

D34M0n7 · May 4, 2010

zeely said:
ja - something is definitely up.downloads from rapidshare dropped to 4k/sec

You using the free download from rapidshare or do you have a paid account?

Whenever I use rapidshare my downloads are always less than 7kb/s (I'm a free user)... Its slow on both the connections I have, MWEB, Vodacom 3G.

zeely · May 4, 2010

D34M0n7 said:
You using the free download from rapidshare or do you have a paid account?

Whenever I use rapidshare my downloads are always less than 7kb/s (I'm a free user)... Its slow on both the connections I have, MWEB, Vodacom 3G.

i'm a paid RS user

Gordon_R · May 4, 2010

D34M0n7 said:
I'm in Constantia Park Pretoria, seems to be worse here.

1 <1 ms <1 ms <1 ms home.gateway [192.168.0.1]
2 264 ms 321 ms 482 ms 41-132-30-1.dsl.mweb.co.za [41.132.30.1]
3 711 ms 749 ms 831 ms tengig-0-0-0-104.vic-ipc-1.mweb.co.za [196.22.169.146]

I just noticed something rather unusual. If I run a tracert to D34M0n7's DSLAM in Constantia Park, Pretoria, it goes slowly via MWeb, but the last hop goes really fast!

This DSLAM (41.132.30.1) presumably sits on the Telkom exchange, and the fast ping indicates that the SAIX part of the network is running normally AFAIK. So, MWeb, its up to you...

Code:

Tracing route to 41-132-30-1.dsl.mweb.co.za [41.132.30.1]
over a maximum of 30 hops:

   1   <10 ms   <10 ms   <10 ms  home.gateway [192.168.1.254]
   2     8 ms     8 ms     8 ms  41-132-48-1.dsl.mweb.co.za [41.132.48.1]
   3    90 ms    87 ms    87 ms  tengig-0-0-0-101.vic-ipc-1.mweb.co.za [196.22.169.134]
   4    88 ms    87 ms    88 ms  196.22.169.161
   5    37 ms    37 ms    36 ms  41-132-30-1.dsl.mweb.co.za [41.132.30.1]

Trace complete.

TonyA's DSLAM IP address is not shown in his tracert (for some reason?)

SabreWolfy · May 4, 2010

hambone said:
Please could some explain to me whether us in the Eastern Cape are experiencing the same difficulties as those in Cape Town (as described by Gordon_R and Sabrewolfy).
<snip>

I'm in JHB, so 150ms ping/trace to VP is not good at all!

Gordon_R · May 4, 2010

MWeb seem to have just done a network reconfiguration, since around 14h05 I couldn't ping google!? (Said site unknown, LOL ;-)

Now my ping times for local sites are down to 29ms. Anyone else seen an improvement?

SabreWolfy · May 4, 2010

Gordon_R said:
MWeb seem to have just done a network reconfiguration, since around 14h05 I couldn't ping google!? (Said site unknown, LOL ;-)

Now my ping times for local sites are down to 29ms. Anyone else seen an improvement?

MWeb is 150ms away; Google is 260ms away.

Rosaudio · May 4, 2010

My speedtest

Also why does speedtest put my location somewhere in the middle of SA and say im 450 miles away from CT? Im in the Southern subs FFS

SabreWolfy · May 4, 2010

Does this have anything to do with it:

"Seacom's backhaul service provider link is down from Mtunzini to Jhb. We're currently communicating with the backhaul service provider."

From https://twitter.com/SeacomLive/status/13364452207

Gordon_R · May 4, 2010

SabreWolfy said:
Does this have anything to do with it:

"Seacom's backhaul service provider link is down from Mtunzini to Jhb. We're currently communicating with the backhaul service provider."

From https://twitter.com/SeacomLive/status/13364452207

The SEACOM outage has been covered in several other threads, but only happened around 2pm, so I'm not sure which 'it' you're referring to?

hambone · May 4, 2010

Well, no... I want to complain about the above normal latency locally, before Mtunzini gets its pretty town involved.

SabreWolfy · May 4, 2010

Gordon_R said:
The SEACOM outage has been covered in several other threads, but only happened around 2pm, so I'm not sure which 'it' you're referring to?

'It' = slow pings and tracepaths across the country.

Gordon_R · May 4, 2010

SabreWolfy said:
'It' = slow pings and tracepaths across the country.

There could certainly be a connection between the slow pings today, and the SEACOM outage (due to a backhaul failure), since MWeb relies on other providers for connectivity.

I just noticed that tracerts to google are going via SEACOM again, so that path seems to have been restored.

Oh, just noticed that the local pings are back to 90ms, so there is definitely a connection!!

hambone · May 4, 2010

Code:

Tracing route to www.l.google.com [72.14.221.104]
over a maximum of 30 hops:

  1     1 ms     1 ms     1 ms  . [192.168.2.1]
  2     *        *        *     Request timed out.
  3   117 ms   117 ms   119 ms  tengig-0-0-0-110.vic-ipc-1.mweb.co.za [196.22.16
9.170]
  4   118 ms   129 ms   193 ms  vl-92.vic-hscore-2.mweb.co.za [196.22.189.3]
  5   154 ms   136 ms   136 ms  tengig-0-0-0-0-12.vic-up-1.mweb.co.za [196.22.16
9.241]
  6   116 ms   120 ms   118 ms  tengig-0-3-1-0.mid-1.mweb.co.za [196.22.169.211]

  7   343 ms   340 ms   354 ms  pos-0-0-0-0.lon-1.mweb.co.za [196.22.163.230]

...Trace complete.

Surely thats still quite high, at hop 3 and 4? Am I being pedantic?

Rosaudio · May 4, 2010

Tracerts also going via Seacom here

MWEB Uncapped Subscribers Feedback

Active Member

Expert Member

Expert Member

Executive Member

Senior Member

Honorary Master

Executive Member

Senior Member

Honorary Master

Expert Member

Honorary Master

Expert Member

First Officer

Expert Member

Honorary Master

Expert Member

Expert Member

Honorary Master

Expert Member

First Officer